Megaplex-4100

Megaplex-4100
INSTALLATION AND
OPERATION MANUAL
Megaplex-4100
Next Generation Multiservice Access Node
Version 2.0
The Access Company
Megaplex-4100
Next Generation Multiservice Access Node
Version 2.0
Installation and Operation Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD").
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the Megaplex-4100
and any software components contained therein are proprietary products of RAD protected
under international copyright law and shall be and remain solely with RAD.
The Megaplex-4100 product name is owned by RAD. No right, license, or interest to such
trademark is granted hereunder, and you agree that no such right, license, or interest shall be
asserted by you with respect to such trademark. The RAD name, logo, logotype, and the terms
EtherAccess, TDMoIP and TDMoIP Driven, and the product names Optimux and IPmux, are
registered trademarks of RAD Data Communications Ltd. All other trademarks are the property of
their respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
Megaplex-4100. You are prohibited from, and shall not, directly or indirectly, develop, market,
distribute, license, or sell any product that supports substantially similar functionality as the
Megaplex-4100, based on or derived in any way from the Megaplex-4100. Your undertaking in
this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the Megaplex-4100 package and shall continue
until terminated. RAD may terminate this Agreement upon the breach by you of any term hereof.
Upon such termination by RAD, you agree to return to RAD the Megaplex-4100 and all copies
and portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters
RAD Data Communications Ltd.
North America Headquarters
RAD Data Communications Inc.
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel: 972-3-6458181
Fax: 972-3-6498250, 6474436
E-mail: [email protected]
900 Corporate Drive
Mahwah, NJ 07430, USA
Tel: (201) 5291100, Toll free: 1-800-4447234
Fax: (201) 5295777
E-mail: [email protected]
© 1988–2008 RAD Data Communications Ltd.
Publication No. 464-200-12/08
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the Megaplex-4100 to be delivered
hereunder shall be free of defects in material and workmanship under normal use and service for
a period of twelve (12) months following the date of shipment to DISTRIBUTOR.
If, during the warranty period, any component part of the equipment becomes defective by
reason of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect,
RAD shall have the option to choose the appropriate corrective action: a) supply a replacement
part, or b) request return of equipment to its plant for repair, or c) perform necessary repair at
the equipment's location. In the event that RAD requests the return of equipment, each party
shall pay one-way shipping costs.
RAD shall be released from all obligations under its warranty in the event that the equipment has
been subjected to misuse, neglect, accident or improper installation, or if repairs or
modifications were made by persons other than RAD's own authorized service personnel, unless
such repairs by others were made with the written consent of RAD.
The above warranty is in lieu of all other warranties, expressed or implied. There are no
warranties which extend beyond the face hereof, including, but not limited to, warranties of
merchantability and fitness for a particular purpose, and in no event shall RAD be liable for
consequential damages.
RAD shall not be liable to any person for any special or indirect damages, including, but not
limited to, lost profits from any cause whatsoever arising from or in any way connected with the
manufacture, sale, handling, repair, maintenance or use of the Megaplex-4100, and in no event
shall RAD's liability exceed the purchase price of the Megaplex-4100.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to Megaplex-4100 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the Megaplex-4100 are provided "as is" and without warranty of any
kind. RAD disclaims all warranties including the implied warranties of merchantability and fitness
for a particular purpose. RAD shall not be liable for any loss of use, interruption of business or
indirect, special, incidental or consequential damages of any kind. In spite of the above RAD
shall do its best to provide error-free software products and shall offer free Software updates
during the warranty period under this Agreement.
RAD's cumulative liability to you or any other party for any loss or damages resulting from any
claims, demands, or actions arising out of or relating to this Agreement and the Megaplex-4100
shall not exceed the sum paid to RAD for the purchase of the Megaplex-4100. In no event shall
RAD be liable for any indirect, incidental, consequential, special, or exemplary damages or lost
profits, even if RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal
waste at the end of its life cycle. Upon termination of the unit’s use,
customers should provide for its collection for reuse, recycling or other form
of environmentally conscientious disposal.
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or service
personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the
product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building
protective ground bus.
Warning
Some products may be equipped with a laser diode. In such cases, a label with the
laser class and other warnings as applicable will be attached near the optical
transmitter. The laser warning symbol may be also attached.
Please observe the following precautions:
•
Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the transmitter.
•
Do not attempt to adjust the laser drive current.
•
Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
•
The use of optical devices with the equipment will increase eye hazard.
•
Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
Handling Energized Products
General Safety Practices
Do not touch or tamper with the power supply when the power cord is connected. Line voltages
may be present inside certain products even when the power switch (if installed) is in the OFF
position or a fuse is blown. For DC-powered products, although the voltages levels are usually
not hazardous, energy hazards may still exist.
Before working on equipment connected to power lines or telecommunication lines, remove
jewelry or any other metallic object that may come into contact with energized parts.
Unless otherwise specified, all products are intended to be grounded during normal use.
Grounding is provided by connecting the mains plug to a wall socket with a protective ground
terminal. If a ground lug is provided on the product, it should be connected to the protective
ground at all times, by a wire with a diameter of 18 AWG or wider. Rack-mounted equipment
should be mounted only in grounded racks and cabinets.
Always make the ground connection first and disconnect it last. Do not connect
telecommunication cables to ungrounded equipment. Make sure that all other cables are
disconnected before disconnecting the ground.
Some products may have panels secured by thumbscrews with a slotted head. These panels may
cover hazardous circuits or parts, such as power supplies. These thumbscrews should therefore
always be tightened securely with a screwdriver after both initial installation and subsequent
access to the panels.
Connecting AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A. The circuit breaker in the building installation should have high breaking
capacity and must operate at short-circuit current exceeding 35A.
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be
readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
DC units should be installed in a restricted access area, i.e. an area where access is authorized
only to qualified service and maintenance personnel.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A. The circuit breaker in the building installation should have high breaking
capacity and must operate at short-circuit current exceeding 35A.
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF
position. When connecting the DC supply wires, first connect the ground wire to the
corresponding terminal, then the positive pole and last the negative pole. Switch the circuit
breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Connecting Data and Telecommunications Cables
Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port
differs from the standard one, a notice will be given in the manual.
Ports
Safety Status
V.11, V.28, V.35, V.36, RS-530, X.21,
10 BaseT, 100 BaseT, Unbalanced E1,
E2, E3, STM, DS-2, DS-3, S-Interface
ISDN, Analog voice E&M
SELV
xDSL (without feeding voltage),
Balanced E1, T1, Sub E1/T1
TNV-1 Telecommunication Network Voltage-1:
FXS (Foreign Exchange Subscriber)
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
(with feeding voltage), U-Interface
ISDN
TNV-3 Telecommunication Network Voltage-3:
Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are possible.
Safety Extra Low Voltage:
Ports which do not present a safety hazard. Usually
up to 30 VAC or 60 VDC.
Ports whose normal operating voltage is within the
limits of SELV, on which overvoltages from
telecommunications networks are possible.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line
cords.
Attention
Pour réduire les risques s’incendie, utiliser seulement des conducteurs de
télécommunications 26 AWG ou de section supérieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In
such cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Electromagnetic Compatibility (EMC)
The equipment is designed and approved to comply with the electromagnetic regulations of
major regulatory bodies. The following instructions may enhance the performance of the
equipment and will provide better protection against excessive emission and better immunity
against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially
for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be
installed on certain cables. In such cases, special instructions are provided in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines
is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal
conversion loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with
plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines.
Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive
wrist strap.
FCC-15 User Information
This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Canadian Emission Requirements
This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulation.
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel
brouilleur du Canada.
Warning per EN 55022 (CISPR-22)
Warning
Avertissement
Achtung
This is a class A product. In a domestic environment, this product may cause radio
interference, in which case the user will be required to take adequate measures.
Cet appareil est un appareil de Classe A. Dans un environnement 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.
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.
Français
Mise au rebut du produit
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.
•
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.
Français
Certains produits peuvent être équipés d'une diode laser. Dans de tels cas, 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 :
Français
Connexion au courant du secteur
Assurez-vous que l'installation électrique est conforme à la réglementation locale.
Branchez toujours la fiche de secteur à une prise murale équipée d'une borne protectrice de mise
à la terre.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du bâtiment devrait avoir une capacité
élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A.
Branchez toujours le câble d'alimentation en premier à l'équipement puis à la prise murale. Si un
commutateur est fourni avec l'équipement, fixez-le en position OFF. Si le câble d'alimentation ne
peut pas être facilement débranché en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est installé dans l'installation du bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si le système de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par
rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.
A cause de la capacité de courant des systèmes à alimentation CC, des précautions devraient
être prises lors de la connexion de l'alimentation CC pour éviter des courts-circuits et des risques
d'incendie.
Les unités CC devraient être installées dans une zone à accès restreint, une zone où l'accès n'est
autorisé qu'au personnel qualifié de service et de maintenance.
Assurez-vous que l'alimentation CC est isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation locale.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du bâtiment devrait avoir une capacité
élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A.
Avant la connexion des câbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'équipement et fixez-le
en position OFF. Lors de la connexion de câbles d'alimentation CC, connectez d'abord le
conducteur de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le
pôle négatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
Declaration of Conformity
Manufacturer's Name:
RAD Data Communications Ltd.
Manufacturer's Address:
24 Raoul Wallenberg St., Tel Aviv 69719,
Israel
declares that the product:
Product Name:
Megaplex-4100
conforms to the following standard(s) or other normative document(s):
EMC:
Safety:
EN 55022:1998 +
A1:2000, A2:2003
Information technology equipment – Radio
disturbance characteristics – Limits and
methods of measurement.
EN 50024:1998 +
A1:2000, A2:2003
Information technology equipment – Immunity
characteristics – Limits and methods of
measurement.
EN 60950: 2000
Information technology equipment – Safety –
Part 1: General requirements
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC, the Low
Voltage Directive 2006/95/EC and the R&TTE Directive 99/5/EC for wired equipment. The product
was tested in a typical configuration.
Tel Aviv, 7 August, 2007
Haim Karshen
VP Quality
European Contact: RAD Data
Ottobrunn-Riemerling, Germany
Communications
GmbH,
Otto-Hahn-Str.
28-30,
85521
Contents
Chapter 1. Introduction
1.1
1.2
1.3
Overview.................................................................................................................... 1-1
Product Options...................................................................................................... 1-1
Common Logic (CL) Modules ............................................................................... 1-1
Power Supply ..................................................................................................... 1-2
Applications ............................................................................................................ 1-2
Main Features ....................................................................................................... 1-10
Physical Description ................................................................................................. 1-12
System Structure .................................................................................................. 1-12
Equipment Description .......................................................................................... 1-13
I/O Modules .......................................................................................................... 1-14
Common Logic (CL) Modules ................................................................................. 1-18
Power Supply (PS) Modules ................................................................................... 1-20
Functional Description.............................................................................................. 1-21
System Functional Block Diagrams ........................................................................ 1-22
DS0 Cross-Connect Matrix ..................................................................................... 1-26
Handling the Payload of I/O Modules ................................................................ 1-26
Cross-Connect Modes....................................................................................... 1-27
Handling of CAS Information ............................................................................ 1-28
Handling of PDH Port Payload........................................................................... 1-28
Full Timeslot versus Split Timeslot Assignment .................................................. 1-29
Unidirectional Broadcast Function..................................................................... 1-29
SDH/SONET Subsystem (CL.1/155 and CL.1/155GbE) ............................................. 1-30
SDH/SONET Network Port Interfaces................................................................. 1-32
SDH/SONET Framer Subsystem and HO (STS-1) Cross-Connect Matrix ............... 1-32
SDH/SONET Link Protection Mechanisms........................................................... 1-33
Mapping Matrix ................................................................................................ 1-34
E1/T1 Framers and Mappers ............................................................................. 1-34
SDH/SONET Timing Subsystem.......................................................................... 1-34
Integration of SDH/SONET Subsystem with Ethernet Traffic Subsystem (CL.1/155GbE)
............................................................................................................................ 1-36
GbE Ethernet Switch ............................................................................................. 1-37
GbE Port Interfaces .......................................................................................... 1-38
Flow Control Options........................................................................................ 1-38
Forwarding Algorithms and VLAN Support ......................................................... 1-39
Using Virtual Concatenation (CL.1/155GbE) ........................................................... 1-39
Encapsulation Functions ................................................................................... 1-39
VCG Mapper Functions ...................................................................................... 1-40
Support for LCAS .............................................................................................. 1-41
Megaplex-4100 Ethernet Services ......................................................................... 1-41
Ethernet Service Model..................................................................................... 1-41
Ethernet Services Subsystem ............................................................................ 1-43
Timing Subsystem ................................................................................................. 1-47
System Timing Modes....................................................................................... 1-48
Data Channel Timing Modes ............................................................................. 1-55
ISDN Channel Timing Modes ............................................................................. 1-56
Redundancy Options ............................................................................................. 1-58
CL Module Redundancy .................................................................................... 1-58
Redundancy for SDH/SONET Network Connections (CL.1/155, CL.1/155GbE) ..... 1-59
Management Subsystem ....................................................................................... 1-74
Megaplex-4100 Ver. 2.0
i
Table of Contents
1.4
Installation and Operation Manual
Management Alternatives ................................................................................. 1-75
Remote Software and Configuration Updating .................................................. 1-76
Supervisory Port Capabilities............................................................................. 1-76
Out-of-Band Access via CL Ethernet Management Port ..................................... 1-76
Inband Management Access through TDM Networks ......................................... 1-77
Inband Management Access through PSN Networks .......................................... 1-78
Performance Monitoring Statistics .................................................................... 1-79
Alarm Collection and Reporting ......................................................................... 1-79
Diagnostic Functions ............................................................................................. 1-80
Power Supply Subsystem ...................................................................................... 1-80
PS Modules ...................................................................................................... 1-80
Feed and Ring Voltage Sources ......................................................................... 1-80
Technical Specifications............................................................................................ 1-81
Chapter 2. Installation
2.1
2.2
2.3
2.4
2.5
ii
Safety ........................................................................................................................ 2-1
General Safety Precautions ..................................................................................... 2-1
Grounding .............................................................................................................. 2-2
Laser Safety ........................................................................................................... 2-3
Protection against ESD............................................................................................ 2-3
Proper Handling of Modules .................................................................................... 2-4
Site Requirements ...................................................................................................... 2-4
AC Power Requirements .......................................................................................... 2-4
DC Power Requirements.......................................................................................... 2-4
Payload Connections ............................................................................................... 2-5
Connections to E1 and T1 Ports ......................................................................... 2-5
Connections to SHDSL Ports ............................................................................... 2-6
Connections to SDH/SONET Ports ....................................................................... 2-6
Connections to Ethernet Ports............................................................................ 2-7
Optical Cable Requirements ................................................................................ 2-7
Connections to Station Clock .................................................................................. 2-7
Management Connections ....................................................................................... 2-8
Ethernet Connections to CL Modules .................................................................. 2-8
Connection to Serial Port.................................................................................... 2-8
Connections to Alarm Port ...................................................................................... 2-9
Front and Rear Panel Clearance ............................................................................... 2-9
Ambient Requirements ........................................................................................... 2-9
Electromagnetic Compatibility Considerations .......................................................... 2-9
Package Contents .................................................................................................... 2-10
Required Equipment ................................................................................................. 2-10
Mounting the Megaplex-4100 Unit ........................................................................... 2-11
Familiarization with Megaplex-4100 ...................................................................... 2-11
Rear View......................................................................................................... 2-11
Front Panel ...................................................................................................... 2-12
Installing PS Modules ............................................................................................ 2-13
Module Panels .................................................................................................. 2-13
Internal Jumpers ............................................................................................... 2-14
Installing a PS Module....................................................................................... 2-16
Removing a PS Module ..................................................................................... 2-16
Installing CL Modules............................................................................................. 2-16
Module Panels .................................................................................................. 2-16
Preparing CL.1/155 and CL.1/155GbE Modules for Installation........................... 2-19
Installing a CL Module ....................................................................................... 2-20
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
2.6
Table of Contents
Removing a CL Module ..................................................................................... 2-21
Replacing a CL Module During Equipment Operation –Megaplex-4100 Chassis with
two CL Modules................................................................................................ 2-21
Replacing a CL Module During Equipment Operation –Megaplex-4100 Chassis with
Single CL Module .............................................................................................. 2-22
Installing I/O Modules............................................................................................ 2-23
Installing Blank Panels ........................................................................................... 2-23
Installing the Megaplex-4100 Enclosure ................................................................. 2-23
Installing in 19” Rack ........................................................................................ 2-23
Installing in 23” Rack ........................................................................................ 2-24
Connecting to Megaplex-4100 .................................................................................. 2-24
Grounding the Megaplex-4100 .............................................................................. 2-24
Connecting to Power ............................................................................................ 2-25
Connecting to External Feed and Ring Voltages ..................................................... 2-25
Connecting Cables to Megaplex-4100 CL Ports ...................................................... 2-25
Connecting Cables to CL.1/155 and CL.1/155GbE SDH Links .................................. 2-26
Connection Instructions for Optical Cables ........................................................ 2-26
Connecting Coaxial Cables to CL.1/155 and CL.1/155GbE SDH Links .................. 2-27
Connecting to I/O Modules .................................................................................... 2-27
Chapter 3. Operation
3.1
3.2
3.3
3.4
3.5
Turning Megaplex-4100 On ........................................................................................ 3-1
Indications ................................................................................................................. 3-3
System Indications .................................................................................................. 3-3
CONTROL ETH Interface Status Indications .............................................................. 3-3
SDH/SONET Interface Status Indications (CL.1/155 and CL.1/155GbE Only) .............. 3-3
GbE Interface Status Indications (CL.1/GbE and CL.1/155GbE Only) .......................... 3-3
CL CLOCK Interface Status Indications ..................................................................... 3-4
Default Settings ......................................................................................................... 3-4
Configuration and Management Alternatives .............................................................. 3-7
Access Levels for Configuration and Management ................................................... 3-8
Working with Supervision Terminal .......................................................................... 3-8
Preliminary Configuration Sequence.................................................................. 3-10
Configuring Megaplex-4100 via Supervisory Terminal ............................................. 3-15
Preparing New Configuration Parameters.......................................................... 3-15
Validity Checks ................................................................................................. 3-16
Megaplex-4100 Power-up Process .................................................................... 3-17
Organization of Terminal Screens ..................................................................... 3-17
General Supervision Terminal Operating Procedures .......................................... 3-19
Saving Changes to Configuration Database ....................................................... 3-20
Ending a Terminal Configuration Session........................................................... 3-21
Menu Structure of Supervision Utility ................................................................ 3-21
Working with Telnet .............................................................................................. 3-42
General Telnet Operating Procedures................................................................ 3-42
Working with Web Browsers.................................................................................. 3-43
Guidelines for Using Web Browsers................................................................... 3-43
Preparations for Using Web Browsers ............................................................... 3-43
General Web Browsers Operating Procedures ................................................... 3-43
Navigating the ConfiguRAD Menus .................................................................... 3-44
Working with SNMP Management Stations ............................................................ 3-44
Support for SNMP Management ........................................................................ 3-44
Preparing for SNMP Management ..................................................................... 3-45
Turning the Megaplex-4100 Off................................................................................ 3-46
Megaplex-4100 Ver. 2.0
iii
Table of Contents
Installation and Operation Manual
Chapter 4. Configuration
4.1
4.2
4.3
iv
Configuring MP-4100 for Management ....................................................................... 4-1
Quick Setup ............................................................................................................ 4-1
Configuring the Control Ports .................................................................................. 4-3
Configuring the Serial Ports ................................................................................ 4-3
Changing the User Authorizations and Security Parameters of the Serial Ports .... 4-4
Configuring the Ethernet (ETH) Port ................................................................. 4-10
Configuring Host IP Parameters and SNMP Communities (with SNMPv3 Disabled) ... 4-11
Configuring Management Access ........................................................................... 4-14
Configuring the Manager List (with SNMPv3 Disabled) ........................................... 4-15
Configuring System Logistic Information................................................................ 4-18
Configuring Megaplex-4100 for SNMPv3 Management .............................................. 4-19
Overview of SNMPv3 Capabilities ........................................................................... 4-19
User-Based Security Model (USM) ..................................................................... 4-20
SNMP Security Levels........................................................................................ 4-20
SNMPv3 Administrative Features ...................................................................... 4-20
View-Based Access Control Model (VACM)......................................................... 4-21
Configuring SNMP Engine ID .................................................................................. 4-21
Enabling/Disabling SNMPv3 Security Features ........................................................ 4-23
Configuring for SNMP Management with SNMPv3 Security Features ....................... 4-24
SNMPv3 Configuration Sequence ...................................................................... 4-24
Configuring Authorized User Security Parameters ............................................. 4-26
Configuring SNMPv3 Management Attributes .................................................... 4-29
Configuring Target Parameters ......................................................................... 4-30
Configuring Notification Tags ........................................................................... 4-32
Configuring Target Transport Parameters.......................................................... 4-34
Configuring SNMPv1/v3 Mapping ...................................................................... 4-35
Viewing the Summary User Table ...................................................................... 4-36
Viewing the Summary Target Table ................................................................... 4-36
Configuring Megaplex-4100 for Operation ................................................................ 4-38
Managing Megaplex-4100 Configuration Databases ............................................... 4-38
Overview of DB Tools Menu .............................................................................. 4-39
Database Management .................................................................................... 4-39
Configuring System Parameters............................................................................. 4-44
Programming Modules .......................................................................................... 4-51
Configuring System Clock Sources ......................................................................... 4-52
Configuring Station Clock Parameters .................................................................... 4-56
Preparing Signaling Profiles ................................................................................... 4-59
Configuring Physical Layer Parameters................................................................... 4-61
Configuring the CL Physical Layer .......................................................................... 4-64
Configuring the Physical Layer Parameters of GbE Ports ........................................ 4-65
Configuring SDH/SONET Network Ports ................................................................. 4-70
Task Selection .................................................................................................. 4-71
Card Configuration ........................................................................................... 4-71
Configuring Common PDH LVC Parameters ........................................................ 4-74
Configuring SDH/SONET Link Parameters .......................................................... 4-74
Configuring DCC Parameters ............................................................................. 4-75
Configuring All Links ......................................................................................... 4-77
Configuring the Logical Layer ................................................................................ 4-78
Selecting a Specific I/O Module Virtual Port to be Configured ............................ 4-83
Configuring Logical Layer on SDH/SONET Links ...................................................... 4-84
Selecting the Specific CL Virtual Port to be Configured ...................................... 4-84
Configuring Virtual PDH Ports ........................................................................... 4-85
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
4.4
Table of Contents
Configuring HVC Virtual Ports ............................................................................ 4-94
Configuring Ethernet Services ............................................................................. 4-101
Configuring HDLC Bundles for Ethernet Services ............................................. 4-103
Configuring MLPPP Bundles for Ethernet Services ............................................ 4-108
Configuring Virtual Concatenation Groups ....................................................... 4-111
Configuring Ethernet Flows............................................................................. 4-127
Configuring APS for SDH/SONET Links ................................................................. 4-138
Configuring Timeslot Assignment ........................................................................ 4-140
Configuring Payload Mapping to SDH/SONET Links ............................................... 4-151
Typical Mapping Procedure ............................................................................. 4-152
Using the Menu Mapping Mode....................................................................... 4-154
Bypassing between Links................................................................................ 4-156
Mapping Ports with Path Protection Enabled ................................................... 4-158
Configuring Fault Propagation ............................................................................. 4-159
Additional Tasks ..................................................................................................... 4-162
Setting the Internal Date & Time ......................................................................... 4-162
Performing File Transfers to CL Modules .............................................................. 4-163
File Utilities Menu ........................................................................................... 4-163
Before Starting File Transfers ......................................................................... 4-164
File Transfers to CL Modules ........................................................................... 4-164
Updating the CL Management Software .......................................................... 4-165
Downloading a Configuration File ................................................................... 4-167
Uploading a Configuration File ........................................................................ 4-168
File Transfers to I/O Modules and SDH/SONET Subsystems .................................. 4-168
Using the Dir Function .................................................................................... 4-172
Deleting Files ................................................................................................. 4-173
Viewing Logistic (Inventory) Information ............................................................. 4-174
Displaying System Inventory Information ........................................................ 4-174
Displaying SW/HW Revision Information .......................................................... 4-175
Reloading Factory Defaults ................................................................................. 4-176
Reset Device ....................................................................................................... 4-177
Chapter 5. Configuring Typical Applications
5.1
5.2
Overview.................................................................................................................... 5-1
Outline of Preliminary Configuration Sequence ........................................................ 5-1
General Configuration Sequence ............................................................................. 5-2
Configuration Procedure for Typical Ethernet Transport Application ............................ 5-5
Overview ................................................................................................................ 5-5
Configuration Sequence .......................................................................................... 5-6
Preliminary Configuration (All Sites) ........................................................................ 5-6
Configuring the Primary Site (Location A) ................................................................ 5-7
Configuring the Clock Sources ............................................................................ 5-7
Configuring the Physical Layer ............................................................................ 5-8
Configuring Bundles ........................................................................................... 5-9
Interconnecting Bundles to Form Flows ............................................................ 5-12
Connecting Bundle to the E1 Ports ................................................................... 5-17
Configuring Equipment at Location B..................................................................... 5-19
Configuring the Clock Source ............................................................................ 5-19
Configuring the Physical Layer .......................................................................... 5-20
Configuring Bundles ......................................................................................... 5-21
Interconnecting Bundles to Form Flows ............................................................ 5-24
Connecting Bundles to the E1 Ports .................................................................. 5-29
Configuring Equipment at Location C ..................................................................... 5-31
Megaplex-4100 Ver. 2.0
v
Table of Contents
5.3
Installation and Operation Manual
Configuring the Clock Source ............................................................................ 5-31
Configuring the Physical Layer .......................................................................... 5-32
Configuring Bundles ......................................................................................... 5-33
Interconnecting Bundles to Form Flows ............................................................ 5-36
Connecting Bundle to the E1 Ports ................................................................... 5-41
Configuration Procedure for Typical SONET Transport Application ............................. 5-44
Overview .............................................................................................................. 5-44
Configuration Sequence ........................................................................................ 5-45
Preliminary Configuration (All Sites) ...................................................................... 5-45
Configuring Equipment at Location A..................................................................... 5-46
Configuring SDH/SONET Subsystems................................................................. 5-46
Configuring OC-3 Physical Layer........................................................................ 5-47
Configuring System Clock Sources .................................................................... 5-48
Configuring and Mapping the PDH Ports ........................................................... 5-48
Configuring I/O Ports on Other Modules............................................................ 5-50
Configuring Ethernet Bundles ........................................................................... 5-52
Assign Timeslots on PDH Port 1 ........................................................................ 5-55
Configuration Equipment at Location B ................................................................. 5-56
Configuring SDH/SONET Subsystems................................................................. 5-56
Configuring OC-3 Physical Ports ........................................................................ 5-57
Configuring the Timing and Clock Sources ......................................................... 5-58
Configuring and Mapping the PDH Ports ........................................................... 5-58
Configuring the I/O Ports of M8T1 Modules ...................................................... 5-60
Configuring I/O Ports on Other Modules............................................................ 5-61
Configuring Ethernet Bundles ........................................................................... 5-66
Assign Timeslots on CL PDH Port 1 ................................................................... 5-68
Assign Timeslots on M8T1 Ports ....................................................................... 5-69
Configuration Equipment at Location C.................................................................. 5-70
Configuring SDH/SONET Subsystems................................................................. 5-70
Configuring OC-3 Physical Ports ........................................................................ 5-70
Configuring the Timing and Clock Sources ......................................................... 5-71
Bypassing PDH Ports ........................................................................................ 5-72
Chapter 6. Troubleshooting and Diagnostics
6.1
vi
Monitoring Performance ............................................................................................. 6-1
Overview of Monitoring Menu ................................................................................. 6-2
Selecting a System Monitoring Task ........................................................................ 6-7
Displaying the Active Alarms ................................................................................... 6-7
Monitoring the Timing Source Status ..................................................................... 6-12
Monitoring the CL Module Status .......................................................................... 6-12
Monitoring the Megaplex-4100 Remote Agents ..................................................... 6-13
Monitoring the APS Status .................................................................................... 6-14
Selecting Virtual Ports for Monitoring .................................................................... 6-15
Monitoring Virtual Ports on I/O Modules ................................................................ 6-16
Selecting a Virtual Port or Bundle for Monitoring ............................................... 6-16
Displaying I/O Virtual Port Monitoring Data ....................................................... 6-17
Monitoring Virtual Ports on CL Modules ................................................................. 6-22
Selecting a CL Virtual Port for Monitoring .......................................................... 6-22
Monitoring SDH/SONET Virtual Ports ................................................................. 6-24
Monitoring – VC-4 and STS-1 Virtual Ports ........................................................ 6-25
Monitoring – VC-3 Virtual Ports......................................................................... 6-30
Monitoring – VC-12 or VT1.5 Virtual Ports ......................................................... 6-32
Displaying WAN Intervals Parameters ................................................................ 6-36
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
6.2
6.3
6.4
6.5
Table of Contents
VCG WAN Side Statistics – LAPS Encapsulation .................................................. 6-37
WAN Side Statistics – GFP Encapsulation .......................................................... 6-38
Displaying LCAS Path Info Parameters for Virtual Ports ...................................... 6-41
Monitoring Physical Layer Parameters ................................................................... 6-42
Selecting the Class of Physical Ports ................................................................. 6-42
Monitoring I/O Physical Layer Parameters .............................................................. 6-43
Displaying I/O TDM Physical Layer Monitoring Data ........................................... 6-45
Displaying I/O Ethernet Physical Port Monitoring Data ....................................... 6-53
Monitoring CL Physical Ports ................................................................................. 6-59
Selecting the Class of CL Physical Ports for Monitoring ...................................... 6-59
Displaying Monitoring Data for Station Clock Port ............................................. 6-60
Displaying Monitoring Data for the SDH/SONET Subsystem ............................... 6-62
Displaying SDH/SONET Subsystem Timing Information ...................................... 6-62
Displaying Monitoring Data for an SDH/SONET Link ........................................... 6-64
Displaying Path Protection Monitoring Data for an SDH/SONET Link .................. 6-70
Displaying Monitoring Data for the GbE Ethernet Subsystem ............................. 6-72
Displaying Monitoring Data for a GbE Port ........................................................ 6-72
Detecting Errors ....................................................................................................... 6-78
Handling Alarms and Traps ....................................................................................... 6-95
Alarm Collection and Reporting ............................................................................. 6-95
Alarm Buffer .................................................................................................... 6-95
Alarm Relays .................................................................................................... 6-95
Customizing Alarm Handling (Alarm Configuration) ................................................ 6-95
Displaying Alarms................................................................................................ 6-108
Interpreting Alarm Messages ............................................................................... 6-109
Traps Generated by Megaplex-4100 .................................................................... 6-132
Troubleshooting ..................................................................................................... 6-136
Preliminary Checks .............................................................................................. 6-136
Troubleshooting Procedure ................................................................................. 6-136
Testing Megaplex-4100 Operation .......................................................................... 6-139
Description of Test and Loopback Functions ....................................................... 6-139
Local Loopback on I/O Port of I/O Module ....................................................... 6-142
Remote Loopback on I/O Port of I/O Module ................................................... 6-143
Local Loopback on E1 or T1 Port of I/O Module............................................... 6-143
Remote Loopback on E1 or T1 Port of I/O Module .......................................... 6-143
Local Loopback on Timeslots of E1 or T1 I/O Module Port ............................... 6-144
Remote Loopback on Timeslots of E1 or T1 I/O Module Port ........................... 6-144
Local Loopback on SDH/SONET Link (CL.1/155 and CL.1/155GbE only) ............ 6-144
Remote Loopback on SDH/SONET Link (CL.1/155 and CL.1/155GbE only) ........ 6-145
Local Loopback (LLB) on LVC (CL.1/155 and CL.1/155GbE only) ....................... 6-145
Remote Loopback on LVC (CL.1/155 and CL.1/155GbE only) ........................... 6-146
Global PDH Local Loopback (CL.1/155 and CL.1/155GbE only) ......................... 6-146
Global PDH Remote Loopback (CL.1/155 and CL.1/155GbE only) ..................... 6-146
Local Loopback on PDH Port (CL.1/155 and CL.1/155GbEonly) ........................ 6-146
Remote Loopback on PDH Port (CL.1/155 and CL.1/155GbEonly) .................... 6-147
Local Loopback on PDH Port Timeslots (CL.1/155 and CL.1/155GbE only) ........ 6-147
Remote Loopback on PDH Port Timeslots (CL.1/155 and CL.1/155GbEonly)..... 6-147
Activating Tests and Loopbacks........................................................................... 6-148
Overview of Diagnostics Menu ............................................................................ 6-148
Diagnosing Physical Layer ................................................................................... 6-150
Diagnosing the I/O Module Physical Layer ....................................................... 6-151
Diagnosing the CL.1/155 and CL.1/155GbE Modules ....................................... 6-151
Diagnosing the Virtual Ports ................................................................................ 6-155
Diagnosing the I/O Module Virtual Ports.......................................................... 6-156
Megaplex-4100 Ver. 2.0
vii
Table of Contents
6.6
Installation and Operation Manual
Diagnosing the CL.1/155 and CL.1/155GbE Virtual Ports ................................. 6-157
PDH Global Loop Test ..................................................................................... 6-158
Tests on a Selected PDH Port ......................................................................... 6-159
Ping Test ............................................................................................................ 6-162
Technical Support .................................................................................................. 6-163
Appendix A. Connection Data
Appendix B. Installing New Software Releases
Appendix C. Operating Environment
viii
Megaplex-4100 Ver. 2.0
Quick Start Guide
If you are familiar with the Megaplex-4100, use this guide to prepare it for operation,
starting from its factory-default configuration.
Before performing the procedures described below, review the safety precautions
given in Chapter 2.
Warning
Installing Megaplex-4100
1. Refer to the site installation plan and install the Megaplex-4100 enclosure in
the prescribed position.
2. Install modules in accordance with the site installation plan (slot utilization is
identified below).
3. When necessary, install the prescribed SFPs on the CL modules.
12
LASER
CLASS
1
72V
48V
24V
ON
POWER
POWER
ON
ON
OFF
OFF
CH.
CH.
1-12
1-12
ACT
LINK
ACT
LINK
ACT
LINK
I/O Slots
PS Slots
L
I
N
K
LASER
CLASS
1
E
T ACT
H
LINK
1
E
T ACT
H
LINK
2
E
T ACT
H
LINK
3
C
L
O
C
K
E
T
H
E
T
H
1
E
T
H
2
LOS
A
L
A
R
M
D
C
E
L
I
N
K
2
ON LINE
L
O
S
O
N
A
C
T
LOS
ON LINE
LOS
E
X
L
I
N
K
A
L
A
R
M
E
T
H
3
ACT
G
b
E
2
C
L
O
C
K
E
T
H
L
I
N
K
C
O
N
T
R
O
L
LINK
ETH1
ETH2
LINK ACT
D
C
E
S
H
D
S
L
L
O
S
O
N
A
C
T
L
I
N
K
C
O
N
T
R
O
L
LASER
CLASS
1
E
T
H
1
E
T
H
2
E
T
H
3
CL Slots
TX
12
ON LINE
E
X
G
b
E
2
ACT
I/O 10
STATUS
2
1
4
3
6
5
8
7
RX
11
LINK
1-8
LINK
G
b
E
1
TX
10
11
LINK
1-8
LOS
L
I
N
K
1
ALM
ACT
RX
10
ON LINE
L
I
N
K
2
ON LINE
G
b
E
1
ON LINE
LOS
LINK
TX
9
I/O 9
M8SL
RX
9
TX
8
RX
7
8
ALM
ACT
TX
6
7
ON LINE
ON LINE
LOS
LINK
RX
6
I/O 6 I/O 7 I/O 8 I/O 9 I/O 10
I/O 6
CL-1
1 5 5/GbE
L
I
N
K
L
I
N
K
1
TX
5
CL-B
CL-B
CL-1
1 5 5/GbE
TX
ON
-
4
5
L
I
N
K
RX
+
+
+
3
4
L
I
N
K
LOS
TX
24V
-
3
TST
STATUS
2
1
4
3
6
5
7
8
RX
-
72V
48V
1
2
STATUS
2
1
4
3
6
5
7
8
TX
+
+
+
CH
CL-A
CL-A
M8T1
RX
-
LOS
1
2
I/O 5
M8E1
TX
VDC-IN
VDC-IN
TST
HSU-12
TX
CH
I/O 4
I/O 3
HSU-12
RX
I/O 2
RX
I/O 1 I/O 2 I/O 3 I/O 4 I/O 5
I/O 1
PS-200/DC
RX
PS-B
PS-B
PS-200/DC
TX
PS-A
PS-A
RX
Slot
AC T
LINK
I/O Slots
4. Refer to the site installation plan, and connect the prescribed cables to the
Megaplex-4100 modules.
Megaplex-4100 Ver. 2.0
1
Quick Start Guide
Installation and Operation Manual
Configuration Instructions
Turn On
Caution
When an external feed and ring voltage source is connected to the PS modules
installed in the Megaplex-4100, always turn that source on only after the PS
module(s) have been turned on.
1. Set the POWER switch(es) on the rear panel(s) of the PS module(s) to ON,
and monitor the power-up initialization process.
2. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active CL module lights in green and that of the
other CL module flashes slowly in green.
Preparations for Configuration
1. Connect a terminal to the CONTROL DCE connector of the active CL module
(use a straight cable).
Note
You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CL modules installed in the Megaplex-4100, using a Y-cable.
You may use any standard ASCII terminal (dumb terminal or personal
computer emulating an ASCII terminal) equipped with an RS-232
communication interface. Make sure to use VT-100 terminal emulation.
2. Configure the terminal for communication with the Megaplex-4100.
If the Megaplex-4100 default configuration has not yet been changed,
configure the terminal for 115.2 kbps, one start bit, eight data bits, no parity,
and one stop bit. Select the full-duplex mode, echo off, and disable any type
of flow control.
3. Press <Enter> once to obtain the log-in screen.
If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for the prompt: In
order to start working - press the ENTER button for few times before
pressing <Enter>.
4. Log in as administrator.
If the Megaplex-4100 default user name and password have not yet been
changed, log in as administrator using su as the user name and 1234 for
password.
5. If your password is accepted, you will see the Megaplex-4100 main menu.
2
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Quick Start Guide
Preliminary Configuration Sequence
The table below provides the preliminary configuration sequence.
Step
Action
Using …
1
Select the default database, 1
Configuration>DB Tools>Default DB
2
If the Megaplex-4100 is equipped with all
the modules, load the hardware
configuration.
Configuration>DB Tools>Load HW
Alternatively, configure the modules and
then reload the factory-default parameters
installed in the Megaplex-4100. You can
also program modules not yet installed in
the chassis
Configuration>System>Card Type
3
Configure the preliminary set of IP
communication parameters
Configuration>Quick Setup
4
Configure CONTROL DCE port parameters
Configuration>System>Control Port>Serial Port
5
Configure CONTROL ETH port parameters
Configuration>System>Control Port>ETH
6
Configure the Megaplex-4100 management
agent
Configuration>System>Management>Host IP
7
Configure Megaplex-4100 management
access
Configuration>System>Management>Mng Access
8
Configure specific management stations
(optional)
Configuration>System>Management>Manager List
9
Set Megaplex-4100 real-time clock
(optional)
Configuration>System>Date & Time
10
Save the configured information in
database 1
Configuration>DB Tools>Update DB 1
or
Type %
Megaplex-4100 Ver. 2.0
3
Quick Start Guide
Installation and Operation Manual
General Application Configuration Sequence
The table below provides the general application configuration sequence for
Megaplex-4100. Skip steps not applicable to your particular application.
Step
Action
Using …
1
Configure Megaplex-4100 signaling profiles
Configuration>System>Signaling Profile
2
Configure the CL modules physical ports:
•
Station clock ports
•
GbE (LAN) ports (make sure to configure
the GbE port redundancy parameters)
•
Configuration>Physical Ports>CL>CL-A, CL-B>Station
Clock
Configuration>Physical Ports>CL>CL-A, CL-B>LAN
SDH/SONET ports (make sure to configure
Configuration>Physical Ports>CL>CL-A, CL-B>
the frame structure)
SDH/SONET
3
Configure the physical ports of the I/O
modules (E1, T1, SHDSL, Ethernet, etc.)
4
Configure the Logical Layer on the
SDH/SONET ports of the CL modules:
Configuration>Physical Ports>I/O>I/O-1 to I/O-10
•
PDH ports
Configuration>Logical Layer>CL>PDH
•
High-order VCs
Configuration>Logical Layer>CL>HVC>CL-A, CL-B
5
Configure the Logical Layer of the I/O module Configuration>Logical Layer>I/O>I/O-1 to I/O-10
internal ports
6
Prepare the Megaplex-4100 for SNMP
management:
1. Select the SNMP support mode
Configuration > System > Management > SNMPv3
(enable/disable SNMPv3).
If SNMP support mode is changed, save to
activate the change before continuing.
2. When SNMPv3 is Disabled, configure
Configuration > System > Management > Host IP
SNMPv1 community names.
3. When SNMPv3 is Enabled, configure
parameters in the following order:
– SNMP Engine ID
– SNMPv3 users
– SNMPv3 targets and notifications
– Configure SNMPv1/SNMPv3 mapping
4
Configuration > System > Management
ID
Configuration > System > Management
Setting > Users
Configuration > System > Management
Setting > Targets & Notify
Configuration > System > Management
Setting > SNMPv1/v3 Mapping
> SNMP Engine
> SNMPv3
> SNMPv3
> SNMPv3
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Step
7
Action
Quick Start Guide
Using …
Configure Ethernet services in the following
order:
•
Configure the prescribed bundles
on I/O module ports, and on PDH ports
•
Configure the prescribed virtually
Configuration>Logical Layer>CL>CL-A, CL-B>VCAT
concatenated groups on SDH/SONET links,
and where necessary configure virtually
concatenated group redundancy
•
Configure the Ethernet flows
Configuration>Logical Layer>Bundles
Configuration>Applications>Ethernet Services>Flows
8
Configure the inband management flow
Configuration>System>Management>Flow
9
Configure path protection parameters for
each virtual and I/O module internal port
Configuration> Logical Layer>IO
10
Configure clock sources and timing flow
Configuration>System>Clock Source
11
Configure APS groups
Configuration>System>APS
12
Configure internal cross-connections
Configuration>System>TS Assignment
13
Configure internal mapping
Configuration>System>Mapping
14
Configure fault propagation
Configuration>System>Fault Propagation
15
Configure Megaplex-4100 alarm handling
Configuration>System>Alarms Configuration
16
Save the final configuration as a database
Configuration>DB Tools>Update DB
17
If necessary, prepare additional databases
(up to 10)
To start from an existing database, use
Configuration>DB Tools>Load DB. Repeat the relevant
steps as needed to create a new database
Megaplex-4100 Ver. 2.0
5
Quick Start Guide
6
Installation and Operation Manual
Megaplex-4100 Ver. 2.0
Chapter 1
Introduction
1.1
Overview
Megaplex-4100 is a highly versatile, high-capacity next-generation multiservice
access node with advanced management capabilities. In its full configuration,
Megaplex-4100 provides high-capacity, non-blocking 4/1/0 cross-connect with
SDH/SONET terminal (TM) and add-drop (ADM) functionality, Ethernet services
per Metro Ethernet Forum, and Ethernet gateway capabilities up to GbE rates.
Megaplex-4100 consists of a compact, fully modular chassis providing a flexible
and scalable node that supports a wide range of user services and provides
effective cross-connect and flexible transport options. The available services
include a wide range of voice services; data from low speed (sub-DS0) to high
speed at up to 2 Mbps; ISDN and ISDL; E1, T1, and E1 over two-wire SHDSL; fiber
multiplexing; pseudowire connectivity; multilink STM-1/OC-3, as well as multilink
Fast Ethernet and Gigabit Ethernet. Special services such as omnibus and party
line voice services, teleprotection channels, etc., are also available.
Redundancy with hot swapping is supported for all the critical subsystems (most
interfaces, common logic timing, and power supply), thereby achieving
carrier-class availability.
Advanced systems design confers the flexibility needed to meet the requirements
of practically every TDM and Ethernet application. Full redundancy for all the
critical subsystems ensures high availability for continuous, reliable service.
Extensive management capabilities, starting with supervision terminals and Telnet
hosts and up to SNMP-based network management, confer complete control over
all aspects of equipment operation, and support efficient provisioning and rapid
response to changing requirements. To protect network operations against
unauthorized access, Megaplex-4100 supports SNMP management with
authentication and privacy per SNMPv3, with continued support for SNMPv1.
Product Options
Common Logic (CL) Modules
Megaplex-4100 can be ordered with one or two common logic (CL) modules.
Currently, the following CL models are offered:
•
CL.1: common logic and cross-connect module with basic functionality.
•
CL.1/155: common logic and cross-connect module with two STM-1/OC-3
links, includes a complete SDH/SONET traffic handling subsystem.
Megaplex-4100 Ver. 2.0
Overview
1-1
Chapter 1 Introduction
Installation and Operation Manual
•
CL.1/GbE: common logic and cross-connect module with two GbE links for
connection to packet switched networks.
•
CL.1/155GbE: common logic and cross-connect module with two STM-1/OC-3
and two GbE links. This module includes both SDH/SONET and Ethernet traffic
handling subsystems.
The GbE ports can be ordered with one of the following interfaces:
•
10/100/1000BASE-T copper ports. This type of ports support
auto-negotiation, with user-specified advertised data rate (10, 100 or
1000 Mbps) and operating mode (half- or full-duplex).
•
SFP sockets, for installing SFP plug-in modules.
Power Supply
Megaplex-4100 can be ordered with AC or DC power supply modules. It can also
be ordered with one power supply module, or with two power supply modules,
for redundancy.
Applications
Figure 1-1 shows a typical access node application for a Megaplex-4100 equipped
with CL.1/155 modules.
In this application, a Megaplex-4100 located at a point-of-presence (PoP) serves
as a multiservice access node: the ports of the I/O modules installed in the
Megaplex-4100 provide the Last Mile connections over E1, T1, and SHDSL lines to
the customers’ equipment, for example, to dedicated FCD, ASMi, or DXC units
offered by RAD.
A single STM-1 or OC-3 link connecting the Megaplex-4100 to the ADM at the PoP
can carry all the payload that can be used by I/O modules installed in the chassis
(up to 63 E1 streams, or 84 T1 streams), with flexible mapping. In addition, the
DS0/DS1 cross-connect matrix of the chassis can also provide cross-connect
services among the I/O modules installed in the chassis. Since a single STM-1 or
OC-3 link is sufficient, only one CL.1/155 module must be installed in the
Megaplex-4100.
For better protection against transmission failures on the SDH/SONET link
between the Megaplex-4100 and the SDH/SONET backbone, APS (automatic
protection switching) should be used. This is achieved by enabling the two
SDH/SONET ports of the CL.1/155 module, connecting them by two STM-1 or
OC-3 links to two appropriately configured ADM ports, and configuring the
CL.1/155 ports as one APS group. For ensuring good service quality, protection
switching can be configured to also occur in case of signal degradation.
Availability can be significantly increased by installing two CL.1/155 modules: this
provides redundancy for the Megaplex-4100 management and system timing
subsystems, and also permits using STM-1 or OC-3 ports on different CL.1/155
modules as APS partners, for hardware redundancy, in addition to the
transmission path redundancy available with a single CL module.
1-2
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
POP
SHDSL
n x E1/T1
E1
HS
CPE
IDSL
DXC-30
PBX
n x E1/T1
CPE
MP-2100
E1/T1
POP
FCD-E1LC
STM-1/
OC-3
SDH/
SONET
CPE
SHDSL
ASMi-52
MP-4100
E1
CPE
FE1
DXC-4
E1
Figure 1-1. Megaplex-4100 as a Versatile Multiservice Access Node
The application of Figure 1-1 uses only two of the SDH/SONET ports that can be
installed in the Megaplex-4100 (the maximum is four, two on each CL module).
For better utilization of the link between the Megaplex-4100 and the ADM in the
PoP, this link can also be used to carry traffic for additional Megaplex-4100 units.
Figure 1-2 illustrates how to extend the application of Figure 1-1 to enable
additional Megaplex-4100 units to use the same SDH/SONET link (and thus, the
same ADM ports), using a chain topology. In the application of Figure 1-2, the
two SDH/SONET ports on CL module A provide an APS-protected link to the ADM,
with a total payload capacity of one STM-1/OC-3. CL module A is configured as
the active CL module, and therefore its internal cross-connect matrix provides the
add/drop function for the I/O ports installed in the chassis that need to connect
to the SDH/SONET backbone. The unused capacity of the protected link can be
bypassed to the desired link of CL module B, which provides STM-1 or OC-3 links
to other equipment, for example, to other Megaplex-4100 units.
Megaplex-4100 Ver. 2.0
Overview
1-3
Chapter 1 Introduction
Installation and Operation Manual
Megaplex-4100 B
Link 1
Megaplex-4100 A
SDH/SONET
Link 1
Link 1
Link 2
Link 2
STM-1/OC-3
CL-A CL-B
Megaplex-4100 C
Link 1
Figure 1-2. Megaplex-4100 in Chain Applications
When protection of the SDH/SONET link as illustrated in Figure 1-2 is not
required, each SDH/SONET port in the chassis can be independently used,
provided a few restrictions (explained in the SDH/SONET Subsystem (CL.1/155
and CL.1/155GbE) section) are observed:
•
The total number of E1s or T1s that can be connected to internal I/O ports:
63 for SDH interfaces, 84 for SONET interfaces.
Note that all the connections to internal I/O ports are performed only by
means of the cross-connect matrix of the active CL module: the standby CL
module cannot provide any connections, although its SDH/SONET subsystem
is fully operational and its utilization is controlled by performing the desired
mapping for any other services
•
The capacity of the internal bypass links between the SDH/SONET subsystems
on the two CL modules, a capacity which is equivalent to two STM-1/OC-3
links. These links are used for redundancy (APS) between SDH/SONET ports
on different modules (one link for each APS group comprising STM-1/OC-3
ports on different CL modules, and for LVC path protection (in this case, only
a number of low-order VCs equal to the number of VCs protected by means
of the adjacent CL module is used), and therefore only the remaining
bandwidth can be used for bypassing. However, the flexible mapping
capabilities of the Megaplex-4100 enable full utilization of the available
bandwidth on the bypassing links.
A few topologies that illustrate applications that require independent SDH/SONET
links are presented below:
•
Figure 1-3 shows a topology that enables connecting several Megaplex-4100
via SDH/SONET links to an SDH/SONET ring
•
Figure 1-4 shows a topology that enables connecting a Megaplex-4100 to
two SDH/SONET rings, with the local I/O ports connected to the desired ring,
in accordance with the active CL module. The four SDH/SONET links can be
used in two main ways: the two links of each CL module can be configured as
an APS group, or a bypass can be configured between two links, one on each
CL module (in this case, Megaplex-4100 bridges traffic between the two
rings).
1-4
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Note that for satisfactory performance, the two SDH/SONET rings must either
use a common timing reference (synchronous timing), or their timing sources
must be primary sources (plesiochronous timing).
Figure 1-5 shows a topology that enables connecting several Megaplex-4100
•
via SDH/SONET links to two SDH/SONET rings. As in the application of
Figure 1-4, some traffic can be bridged between the two rings, and other
traffic can be directed to local I/O ports. The timing requirements described
for the application of Figure 1-4 also apply to this application.
Megaplex-4100 B
Megaplex-4100 A
STM-1/OC-3
SDH/SONET
Link 1
Link 1
Link 2
Link 2
CL-A CL-B
Megaplex-4100 C
Megaplex-4100 D
Figure 1-3. Connecting Several Megaplex-4100 Units to a SDH/SONET Backbone
via Single STM-1/OC-3 Link
Megaplex-4100
Link 1
SDH/SONET
Ring A
Link 1
STM-1/OC-3
SDH/SONET
Ring B
STM-1/OC-3
Link 2
Link 2
To Local Users
Figure 1-4. Megaplex-4100 Interconnecting two SDH/SONET Rings
Megaplex-4100 A
SDH/SONET
Ring A
STM-1/OC-3
Link 1
Link 1
Link 2
Link 2
STM-1/OC-3
SDH/SONET
Ring B
CL-A CL-B
Megaplex-4100 B
Megaplex-4100 C
Figure 1-5. Connecting Several Megaplex-4100 to two SDH/SONET Rings
Instead of connecting to the SDH/SONET ring via an ADM (as in Figure 1-1),
Megaplex-4100 can be directly attached to an SDH/SONET ring, as shown in
Megaplex-4100 Ver. 2.0
Overview
1-5
Chapter 1 Introduction
Installation and Operation Manual
Figure 1-6. The SDH/SONET ring carries both TDM (“legacy”) traffic, and Ethernet
traffic, with the connection to the MPLS transport network being provided by an
FCD-155E unit. The traffic reaches Megaplex-4100 through its SDH/SONET links,
and is distributed to the headquarters’ internal services network, and well as to
remotely located customer offices.
MPLS
Customer Offices
FCD-155
STM-1/OC-3
Control Center
FE/GbE
ETX-102/
ETX-202
FE/GbE
FCD-155E
MP-4100
FCD-155E
n x E1/T1
RICi-4E1/4T1
RICi-8E1/8T1
SDH/SONET
ASMi-52
SHDSL
FCD-155E
E1/T1
PBX
FCD-IP
SCADA
Internal Services
Voice
E1/T1
MP-2104
Figure 1-6. Megaplex-4100 in a Typical Ethernet and TDM Termination Application
This application utilizes the Megaplex-4100 Ethernet and TDM termination
capabilities to provide a flexible and scalable solution in a central access node.
Ethernet traffic reaching I/O modules with Ethernet subsystem, for example,
M8E1, M8T1, M8SL, is handled as follows:
•
Megaplex-4100 TDM I/O ports can receive Ethernet traffic processed by WAN
interfacing equipment such as ASMi-52 (over SHDSL), or FCD-E1LC, FCD-IP,
(over E1/T1), etc.
In each I/O module, the bundles carrying this HDLC-encapsulated Ethernet
traffic are terminated, their payload converted back to Ethernet, and then
forwarded to the destination (CL module or another I/O module).
In addition to the encapsulated Ethernet traffic, the I/O module can also
receive Ethernet traffic via its external Ethernet ports (Figure 1-6 shows
ETX-102/ETX-202 units connected to Megaplex-4100 Ethernet I/O ports). This
traffic is also forwarded to the destination (CL module or another I/O
module).
•
The I/O module Ethernet switch determines the destination of each frame in
accordance with the configured flows. The classification of each user network
is based on the VLAN ID, or on the port, if no C-VLAN ID is configured. Traffic
from locally-terminated bundles can be forwarded to local Ethernet ports, or
to CL modules, or other I/O modules.
The CL module can forward the traffic either to the I/O module handling the
traffic to the specified destination, or to one of the GbE ports (on the same
CL module, or on the adjacent module), or encapsulate the traffic for
1-6
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
transmission over SDH/SONET using a virtually concatenated group (for
CL.1/155GbE modules – see also the application of Figure 1-8.
As in the application of Figure 1-1, a single CL.1/155 or CL.1/155GbE module is
required. However, for highest availability, two CL modules should be installed.
Figure 1-7 shows an application that provides a complete solution for corporate
communications based on Megaplex-4100 equipment. In this application,
Megaplex-4100 units are used both as STM-1/OC-3 add/drop multiplexers in the
backbone network, and as terminal multiplexers located at each service location.
The application of Figure 1-7 can be expanded to include access to packet
switched networks, for example, Internet or metropolitan Ethernet networks: this
is achieved by installing CL.1/155GbE modules, which provide Ethernet and GbE
links, in the Megaplex-4100.
Figure 1-8 shows a typical access node application for a Megaplex-4100 equipped
with CL.1/155GbE modules.
CPE
SDH/
SONET
Central Site
STM-1/
OC-3
STM-1/OC-3
MP-4100
MP-4100
E1/T1
PSTN
MP-4100
E1/T1/SHDSL
MP-4100
STM-1/OC-3
Ring
CPE
E1/T1
STM-1/OC-3
MP-4100
E1/T1/SHDSL
FCD-155
POP
MP-4100
E1/T1
STM-1
DXC-10A/30
Figure 1-7. Single Node Corporate Solution
Megaplex-4100 Ver. 2.0
Overview
1-7
Chapter 1 Introduction
Installation and Operation Manual
Figure 1-8. Single Node Corporate Solution Expanded to Provide PSN Access
In the application of Figure 1-8, Megaplex-4100 has an Ethernet termination
capacity of 1 Gbps, that is, Ethernet users connected to the Megaplex-4100 I/O
modules can get a total bandwidth of up to 1 Gbps on the external GbE links. This
capacity can be distributed over up to four GbE links, or up to two GbE links with
redundancy protection. However, Megaplex-4100 can provide a total bandwidth
of 2 Gbps on its GbE links, where 1 Gbps is provided to the internal I/O modules,
and an additional 1 Gbps is provided to other equipment. This capability is
illustrated in Figure 1-9:
•
The connection to the PSN is provided by the two GbE ports on one of the CL
modules, for a total capacity of 2 Gbps. The internal GbE switch of this CL
module is used to distribute up to 1 Gbps of the Ethernet traffic to the
internal I/O modules (each module can get up to 100 Mbps via the internal
Fast Ethernet buses connecting it to the CL modules).
•
In addition to the internal flows from this CL module to the I/O modules, an
additional flow can be configured between one of its GbE ports, and a GbE
port on the other CL module (actually, several flows can be configured, as
long as the total bandwidth does not exceed the capacity of the GbE bypass
link between the two CL modules, which is 1 GbE). The external GbE ports of
the other CL module are then connected to the other equipment.
Megaplex-4100
PSN
GbE1
Megaplex-4100
GbE1
GbE2
GbE2
CL-A CL-B
Figure 1-9. Higher Capacity Connection to PSN
1-8
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The CL module connecting to the PSN can be equipped with long-haul optical
SFPs, whereas the other CL module can have copper interfaces, for connection to
local equipment (for example, to another Megaplex-4100, which can then also
use copper interfaces for its GbE ports).
The modular, distributed architecture of the Megaplex-4100 chassis enables
redundancy at different levels of the network, and provides a resilient system
with no single point of failure. CL.1/155 and CL.1/155GbE modules provide
STM-1/OC-3 links with automatic switchover between the two links for 1+1
unidirectional protection against network or cable failure, and in addition can
provide path protection for selected services. The GbE links can also be protected
by configuring 1+1 bidirectional protection.
The single-node solution illustrated in Figure 1-7 can also be used even when
some corporate locations use North American standards, and other locations use
the European, as shown in Figure 1-10:
•
The network side of the Megaplex-4100 can be configured to use either SDH
or SONET links
•
M8E1 modules are used at the SDH side, and M8T1 modules are used at the
SONET side
•
The CL modules automatically perform companding law conversion (A-law to
μ-law, and vice versa) for voice channels.
MP-4100
US Offices
European
Offices
MP-4100
STM-1/OC-3
84×T1
International
SDH/SONET
Network
STM-1
63×E1
Figure 1-10. Multinational Solutions
Megaplex-4100 can also be used in SNCP applications, as shown in Figure 1-11. In
this application, Megaplex-4100 are inserted in the subnet ring, which provides
SNCP for the main ring.
ADM
ADM
Megaplex-4100
Megaplex-4100
Megaplex-4100
Megaplex-4100
Figure 1-11. Megaplex-4100 in Typical SNCP Application
Megaplex-4100 Ver. 2.0
Overview
1-9
Chapter 1 Introduction
Installation and Operation Manual
Main Features
The services supported by the modules offered for Megaplex-4100 include:
•
PDH access: E1/T1 and fractional E1/T1 level, including access over 2-wire
SHDSL, with up to 80 E1/T1/SHDSL ports per chassis
•
Data services: multichannel sub-DS0 low speed data, 64-kbps codirectional
G.703 channels, teleprotection channels, multichannel ISDN access (up to 120
ISDN “U” and/or “S” type ports per chassis), optical multiplexing, and
n×64 kbps high speed data (up to 2.048 Mbps for E1 environments, or up to
1.544 Mbps for T1 environments)
•
Voice services: analog and digital voice (up to 2400 voice channels per chassis
for E1 ports, up to 1920 voice channels for T1 ports), and support for special
services such as omnibus and party lines. Voice channel processing can
include A/μ companding law conversions, and user-defined signaling
translations.
•
SDH/SONET services: up to four separately configurable STM-1 or OC-3 links
per node, and support for 1+1 unidirectional APS (Automatic Protection
Switching) per ITU-T Rec. G.842 for line redundancy.
•
Ethernet Layer 2 services complying with Metro Ethernet Forum (MEF)
specifications, supported by 10/100 Mbps Ethernet ports and Ethernet
switches on M8E1, M8T1, M8SL, MPW-1, OP-108C, OP-106C and ASMi-54C I/O
modules, and GbE ports and Ethernet switch with classifier on CL modules. Up
to three separately configurable Ethernet ports are available per I/O module;
each CL module has two GbE ports, for up to four separately configurable GbE
ports per chassis, with support for 1+1 bidirectional redundancy for pairs of
ports. Megaplex-4100 can provide Ethernet traffic termination for transport
over E1, T1, SHDSL, and low-order SDH/SONET VC-12/VC1.5 virtual
containers, and can also serve as Ethernet access concentrator with GbE and
virtually concatenated group uplinks.
Flexible Ethernet transport options over TDM links provide full support for
Ethernet services over existing TDM infrastructures with efficient bandwidth
utilization for each type of application, and also enable cost-effective
migration to packet switched transport. The available Ethernet transport
options include:
ƒ
HDLC bundles with selectable number of timeslots over individual external
E1 and T1 links, and internal PDH ports of the SDH/SONET subsystem
ƒ
Wideband, multilink MLPPP bundles over E1 links, with a bandwidth of up
to 16.384 Mbps (the equivalent of eight E1 links)
ƒ
Virtually concatenated groups over SDH/SONET links, with selectable
granularity down to VC-12/VT1.5, Megaplex-4100 supports low-order and
high-order virtual concatenation, including GFP encapsulation per ITU-T
Rec. G.7041 or LAPS per ITU-T Rec. X.85/X.86. For reliable transmission,
Megaplex-4100 also supports LCAS per ITU-T Rec. G.7042.
The current SDH/SONET transport options include STM-1 or OC-3 links (the link
standard being user-selectable), with independent mapping for each link, and
configurable bypassing between links. Support for standard SFP optical
transceivers for the SDH/SONET link interfaces (copper interfaces are also
1-10
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
available) enables selecting the optimal interface for each application.
High-performance SFPs available from RAD can achieve ranges up to 80 km/50
miles.
The 10/100 Mbps Ethernet ports on the I/O modules, and the GbE ports on the
CL modules, may be equipped with optical SFPs, or ordered with copper
interfaces.
The Megaplex-4100 SDH/SONET subsystem can be configured as a terminal (TM)
or add/drop (ADM) multiplexer, and it supports ring topologies, 1+1 unidirectional
multiplex section protection (MSP) with automatic protection switching (APS) for
the STM-1/OC-3 level, and path (SNCP) protection for the E1/T1 level. Protection
switching occurs within less than 50 msec.
Internal signal routing is performed by a built-in non-blocking 4/1/0 cross-connect
matrix. The matrix supports DS0/DS1 cross-connect with a capacity of 80 E1/T1
for the internal ports (160 Mbps equivalent bandwidth), and in addition also
supports 63 E1 links towards the SDH interfaces, or 84 T1 links towards the
SONET interfaces. This matrix can therefore directly perform TDM cross-connect
from the DS0 to the STM-1/OC-3 level, and therefore can groom traffic from any
I/O channel directly to any aggregated link, including the STM-1/OC-3 links. For
efficient multiplexing of sub-DS0 channels, the matrix also supports split timeslot
assignment.
For applications that do not require access to SDH/SONET networks, the
Megaplex-4100 can be ordered without TDM interfaces: in this case, SHDSL ports
can be used to distribute traffic to user’s equipment located at ranges of up to
several kilometers. With this option, the Megaplex-4100 effectively serves as a
high-capacity E1/T1 digital cross-connect (DXC) unit with multiplexing capabilities.
Efficient handling of Ethernet traffic is made possible by Ethernet interfaces with
local Ethernet switches on I/O modules, and by the GbE ports and Ethernet
switches with classifier located on CL modules. The Ethernet services can operate
independently of the TDM services, however Megaplex-4100 Ethernet services
subsystem can also handle Ethernet traffic transported over TDM links, both over
PDH (E1/T1) and over virtually concatenated groups carried by SDH/SONET links.
Internal traffic forwarding is controlled by configuring flows, with classification in
accordance with VLANs.
Megaplex-4100 ability to handle a broad range of data, Ethernet, and voice
services and various network technologies in a single, compact managed node
makes it a versatile and cost-effective next-generation multiservice access node.
Flexible timing options enable reliable distribution of timing together with flexible
selections of timing sources, including support for an external station clock
interface that enables daisy-chaining the clock signals to other equipment. When
equipped with SDH/SONET links, Megaplex-4100 also provides traceable timing
quality and supports automatic selection of best-quality timing reference.
A wide range of inband and out-of-band management options provide
organizations with the means needed to integrate the equipment within the
organizational management network, as well as transfer their management traffic
seamlessly through the Megaplex-4100-based network.
Megaplex-4100 can be powered from AC and/or DC sources. Only a single power
supply module is required to provide power to a fully equipped Megaplex-4100,
however, for redundancy, Megaplex-4100 can be equipped with two power
Megaplex-4100 Ver. 2.0
Overview
1-11
Chapter 1 Introduction
Installation and Operation Manual
supply modules. When ISDN and/or analog voice modules are installed in the
chassis, it may be necessary to supply feed and ring generation voltage: for this
purpose, the power supply modules support the connection of an external ringer,
for example, a Ringer-2200N/ISDN standalone unit offered by RAD.
Megaplex-4100 units, as a whole, are cooled by free air convection: air intake
vents are located on the bottom and exhaust vents are located on the top. In
addition, the power supply modules have miniature cooling fan installed on their
front panels that operate only when the ambient temperature is high.
1.2
Physical Description
System Structure
Megaplex-4100 units use a modular chassis. The chassis has physical slots in
which modules are installed by the user to obtain the desired equipment
configuration.
Megaplex-4100 configuration includes the following main subsystems:
•
I/O subsystem, provides interfaces to the user’s equipment. The number of
user interfacing modules that can be installed in a chassis is up to 10
•
Multiplexing, timing, and control subsystem, located on the common logic and
cross-connect (CL) modules. CL modules may also include optional network
interface subsystems (SDH/SONET and/or Ethernet), in accordance with the
ordered version
•
Power supply subsystem, located on the power supply (PS) modules
•
Chassis. The main function of the chassis is to provide interconnections
between the various modules, and in particular to connect between the user
interfacing (I/O) modules, and the CL modules that provide the multiplexing
function and the optional connections to SDH/SONET and/or Ethernet
networks.
CL and PS modules are always installed in their dedicated chassis slots, whereas
the user interfacing modules can be installed in any of the other chassis slots
(called I/O slots).
Any operational Megaplex-4100 system must include at least one CL module and
one PS module. These modules are thus referred to as system modules. User
interfacing modules, called I/O modules, are added to this basic configuration.
Megaplex-4100 system modules are critical components, because a failure in any
one of these modules could disable the whole system, whereas a failure in an I/O
module affects only a small part of the system, and can be generally overcome by
using alternate routes, putting unused capacity into service, etc. Therefore, in
most applications Megaplex-4100 units should be equipped with an additional
redundant system module of each type. Redundancy is also available for the
network interfacing subsystems.
The Megaplex-4100 system is designed to automatically put a redundant module
or subsystem in service in case the corresponding system component fails,
thereby ensuring continuous system operation in the event of any single module
1-12
Physical Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
failure. Moreover, redundant modules may be inserted or removed even while the
system operates, without disrupting the traffic or degrading system performance.
Equipment Description
Figure 1-12 shows a general view of the Megaplex-4100 enclosure.
Megaplex-4100 is built in a 4U-high enclosure that is intended for installation in
19” and 23” racks, using brackets attached to the sides of the enclosure, near the
front or rear panel. Thus, a Megaplex-4100 can be installed in accordance with the
specific requirements of each site, either with the Megaplex-4100 front panel
toward the front of the rack (per ETSI practice), or with the module panels
toward the front (per ANSI practice).
System status indicators are located on both the front panels and on the CL
module panels. Additional indicators are located on the module panels. The cable
connections are made directly to the module panels.
10 I/O Modules
2 CL Modules
2 PS Modules
Figure 1-12. Typical Megaplex-4100 Enclosure, General View
Figure 1-13 shows a typical rear view of the Megaplex-4100 enclosure that
identifies the slots and their utilization. The enclosure has 14 slots:
•
Two slots are reserved for power supply (PS) modules
•
Two slots are reserved for CL modules
•
The other 10 slots, arranged in two groups of 5 each, are intended for I/O
modules. Each I/O slot can accept any type of I/O module.
Megaplex-4100 Ver. 2.0
Physical Description
1-13
Chapter 1 Introduction
10
10
11
11
12
12
ON
POWER
POWER
ON
ON
OFF
OFF
ON LINE
E
X
LASER
CLASS
1
72V
48V
24V
CH.
CH.
1-12
1-12
AC T
LINK
AC T
LINK
AC T
LINK
I/O Slots
PS Slots
L
I
N
K
LASER
CLASS
1
E
T AC T
H
LINK
1
E
T AC T
H
LINK
2
E
T AC T
H
LINK
3
LOS
C
L
O
C
K
A
L
A
R
M
D
C
E
G
b
E
2
L
I
N
K
2
L
O
S
O
N
A
C
T
LOS
ON LINE
LOS
E
X
L
I
N
K
C
O
N
T
R
O
L
LIN K
ACT
G
b
E
2
C
L
O
C
K
E
T
H
L
I
N
K
A
L
A
R
M
ETH1
ETH2
LINK ACT
G
b
E
1
TX
ON LINE
ACT
ALM
ACT
TX
L
I
N
K
1
ON LINE
LIN K
RX
G
b
E
1
LOS
RX
LIN K
E
T
H
E
T
H
1
E
T
H
2
LOS
ON LINE
S
H
D
S
L
L
O
S
O
N
A
C
T
LASER
CLASS
1
L
I
N
K
D
C
E
E
T
H
1
C
O
N
T
R
O
L
E
T
H
2
E
T
H
3
E
T
H
3
CL Slots
TX
9
L
I
N
K
2
LINK
1-8
ALM
ACT
STATUS
2
1
4
3
6
5
8
7
RX
9
ON LINE
LINK
1-8
ON LINE
LIN K
TX
8
L
I
N
K
1
LOS
I/O 10
M8SL
L
I
N
K
ON LINE
RX
7
8
I/O 9
CL-1
1 5 5/GbE
TX
7
CL-1
1 5 5/GbE
RX
6
I/O 6 I/O 7 I/O 8 I/O 9 I/O 10
I/O 6
TX
-
5
6
CL-B
CL-B
RX
ON
+
4
5
L
I
N
K
TX
24V
-
+
+
3
4
L
I
N
K
LOS
RX
72V
48V
3
TST
TX
-
1
2
M8T1
STATUS
2
1
4
3
6
5
7
8
RX
+
CH
M8E1
TX
-
+
+
LOS
1
2
CL-A
CL-A
STATUS
2
1
4
3
6
5
7
8
TX
VDC-IN
VDC-IN
TST
HSU-12
I/O 5
RX
HSU-12
CH
I/O 4
I/O 3
RX
PS-200/DC
I/O 2
TX
PS-200/DC
I/O 1 I/O 2 I/O 3 I/O 4 I/O 5
I/O 1
RX
PS-B
PS-B
TX
PS-A
PS-A
RX
Slot
Installation and Operation Manual
ACT
LINK
I/O Slots
Figure 1-13. Megaplex-4100 Enclosure, Typical Rear View
I/O Modules
Table 1-1 lists the I/O modules currently offered for the Megaplex-4100. Contact
RAD Marketing for information on additional modules that may be available for
your specific application requirements.
Note
• Some of the I/O modules (indicated by Yes in the Megaplex-2100 Compatible
Hardware column) use the same hardware as the Megaplex-2100 modules
with the same name. Note however that software updating may be required.
Contact RAD Technical Support Department for details.
• The minimum hardware and software versions of I/O modules supported by
the current Megaplex-4100 version is indicated next to each module. Contact
RAD Technical Support Department for details on other versions.
Table 1-1. Megaplex-4100 I/O Modules
Megaplex-2100
Compatible
Hardware
Module
Description
M8E1
Module with eight E1 interfaces and user-selectable DSU or LTU mode, and
three 10/100 Mbps Ethernet license-controlled ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a 100
Mbps Fast Ethernet connection to the CL module.
No
Includes a non-blocking full cross-connect matrix that supports direct bypassing
of timeslots and associated signaling information between the E1 links without
requiring bandwidth on the internal chassis buses for bypassing; together with
the CL module, this matrix also enables free routing of timeslots from any I/O
channel or from other module ports to any E1 timeslot.
1-14
Physical Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Megaplex-2100
Compatible
Hardware
Module
Description
M8T1
Module with eight T1 interfaces and user-selectable DSU or CSU mode, and
three 10/100 Mbps Ethernet license-controlled ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a 100
Mbps Fast Ethernet connection to the CL module.
No
Includes a non-blocking full cross-connect matrix that supports direct bypassing
of timeslots and associated signaling information between the T1 links without
requiring bandwidth on the internal chassis buses for bypassing; together with
the CL module, this matrix also enables free routing of timeslots from any I/O
channel or from other module ports to any T1 timeslot.
M8SL
Module with eight SHDSL interfaces, supports E1 and fractional E1 payloads,
and three 10/100 Mbps Ethernet license-controlled ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a 100
Mbps Fast Ethernet connection to the CL module.
No
Each module port has an independent multi-rate SHDSL modem, supporting
user-selectable data rates in the range of 192 kbps to 2048 kbps. Has internal
non-blocking full cross-connect matrix similar to M8E1 and M8T1 modules.
SHDSL interface type (STU-C or STU-R ) and mode are user-selectable (ITU-T
Rec. G.991.2 Annex A for compatibility with North American networks, or Annex
B for compatibility with European networks).
Compatible with other RAD equipment having STU-R SHDSL interfaces, such as
the ASMi-52 SHDSL Modems. M8SL modules will also operate in a link with
991.2-compatible STU-R units from other vendors.
MPW-1
No
Pseudowire server I/O module that provides TDM pseudowire access gateway
services over packet-switched networks (Ethernet, IP, and MPLS) for TDM traffic
(E1, T1, SHDSL, ISDN, high-speed and low-speed data, voice) received via the
Megaplex-4100 TDM buses from other modules.
The Megaplex-4100 module has eight independently-configurable internal DS1
ports, each capable of handling 32 timeslots, for a total processing capacity of
256 timeslots (the equivalent of 8 E1, or 2.048 Mbps, streams).
No
ASMi-54C Eight-port SHDSL.bis modules with two Ethernet ports, enable transporting
digital data to customer premises over the existing copper infrastructure of the
distribution network while eliminating the need for repeaters. It multiplexes
Ethernet over 1, 2, and 4 pairs of SHDSL.bis copper lines. Each SHDSL port can
operate in a link with an ASMi-54 standalone unit offered by RAD.
All the ASMi-54C modules have eight SHDSL.bis independently configurable
external ports for SHDSL services, and two 10/100 Mbps Ethernet ports, for
packet-based services.
The module can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R)
SHDSL.bis Terminal Unit for use opposite up to 8 ASMi-54 standalone devices
or another ASMi-54C module.
Megaplex-4100 Ver. 2.0
Physical Description
1-15
Chapter 1 Introduction
Installation and Operation Manual
Module
Description
OP-108C
Dual E1 and Ethernet multiplexer, where each multiplexer operates
independently and can operate in a link with the Optimux-108 4 E1 and
Ethernet Multiplexer standalone unit offered by RAD.
Megaplex-2100
Compatible
Hardware
No
Each multiplexer is capable of transparently transporting four independent E1
data streams and one 100BASE-TX Ethernet channel over one optical link. Each
link has two optical ports, with user-configurable redundancy between the two
ports.
The optical ports can be equipped with field-replaceable SFPs. Support for
standard SFP optical transceivers for the SDH/SONET link interfaces enables
selecting the optimal interface for each application. High-performance SFPs
available from RAD can achieve ranges up to 120 km/75 miles.
OP-106C
Dual T1 and Ethernet multiplexer with characteristics similar to OP-108C, except
that it supports 4 T1 instead of 4 E1 streams.
Each multiplexer operates independently and can operate in a link with the
Optimux-106 4 T1 and Ethernet Multiplexer standalone unit offered by RAD.
LS-6N,
LS-12
Data sub-multiplexer modules with BERT support, provide 6, respectively 12,
synchronous or asynchronous data channels with ITU-T Rec. V.24/EIA RS-232
interfaces, each having an independently selectable data rate in the range of
2.4 to 64 kbps. Support end-to-end transmission of control line per channel.
LS-12 channels can be bundled into two groups, each independently routed to
a different destination.
Yes
Current Megaplex-4100 version supports LS-6N modules with minimum
hardware version 1 and minimum software version 12; for LS-12 modules, the
minimum hardware version is 10 and the minimum software version is 9
HS-RN
Yes
Low-speed data module, provides 4 synchronous or asynchronous data
channels with ITU-T Rec. V.24/EIA RS-232 interfaces, each having independently
selectable data rate in the range of 0.6 kbps up to 38.4 kbps in the
asynchronous mode, and up to 64 kbps in the synchronous mode. HDLC-based
end-to-end control signals are also supported.
Current Megaplex-4100 version supports HS-RN modules with minimum
hardware version 6 and minimum software version 54
HS-6N,
HS-12N
High-speed data interface module, provides 6, respectively 12, high-speed V.35 Yes
or RS-530/V.11 data channels, and supports the BERT function. Channel data
rates are user-selectable in the range of n×56 kbps or n×64 kbps, where n is up
to 24 for T1 operation, and up to 31 for E1 operation (maximum 1984 kbps).
Supports enhanced clock modes and BERT. Any channel can be directed to any
E1 or T1 link or internal PDH port.
Current Megaplex-4100 version supports HS-6N and HS-12N modules with
minimum hardware version 2 and minimum software version 6
HS-703
High-speed data sub-channel interface module, provides four 64 kbps
codirectional ITU-T Rec. G.703 data channels.
Yes
Current Megaplex-4100 version supports HS-703 modules with minimum
hardware version 2 and minimum software version 3
1-16
Physical Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Megaplex-2100
Compatible
Hardware
Module
Description
HSF-2
Interface module for teleprotection equipment, complying with IEEE C37.94
requirements. Provides two ports with 850 nm multimode fiber interfaces, with a
capacity of up to 10 × 64 kbps per port.
Yes
Current Megaplex-4100 version supports HSF-2 modules with minimum
hardware version 4 and minimum software version 1.05
HS-S
ISDN basic rate access interface module with four type “S” interfaces. Performs
submultiplexing and data rate adaptation on B channels in accordance with ITU-T
Rec. I.460.
Yes
This module is intended for extension of ISDN lines over Megaplex-4100 links, and
can provide phantom feed to user's equipment.
Current Megaplex-4100 version supports HS-S modules with minimum hardware
version 6 and minimum software version 12
HS-U-6,
HS-U-12
ISDN basic rate access interface module with 6, respectively 12, type “U”
interfaces. Performs submultiplexing and data rate adaptation on B channels per
ITU-T Rec. I.460. The module supports two operation modes:
•
/I: intended for extension of ISDN lines, can provide phantom feed to user's
equipment. Supports 2B + D channels, and the channel data rates are
user-selectable (16, 32, and 64 kbps for each B channel, and 16 kbps for the D
channel).
•
/1: intended for use over leased lines, and can be used as dedicated line
termination units for the ASM-31 and ASMi-31 short-range modem offered
by RAD. Supports user channel data rates of 4.8, 9.6, 19.2, 48, 56, and
64 kbps over each B channel, and 128 kbps by combining the two B
channels. The D channel is ignored.
Yes
Current Megaplex-4100 version supports HS-U-6 and HS-U-12 modules with
minimum hardware version 0 and minimum software version 3.06
VC4/OMNI
“Omnibus” E&M voice interface module providing four toll-quality voice
channels. Intended for broadcast applications, in which a master site needs to
communicate with multiple remote stations simultaneously (such as to
broadcast an important message). Also enables providing party-line service.
Yes
Current Megaplex-4100 version supports VC-4/OMNI modules with minimum
hardware version 0 and minimum software version 1.08
VC-16,
VC-8,
VC-4
Analog voice interface module, provides 16, 8 or 4 PCM-encoded toll-quality
voice channels.
Yes
The modules are available in three models:
•
E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464 Types I, II,
III and V, and BT SSDC5.
•
FXS: 2-wire interfaces for direct connection to telephone sets.
•
FXO: 2-wire interfaces for direct connection to PBX extension lines.
Current Megaplex-4100 version supports VC-4, VC-8, VC-16 modules with
minimum hardware version 10 and minimum software version 13
Megaplex-4100 Ver. 2.0
Physical Description
1-17
Chapter 1 Introduction
Installation and Operation Manual
Megaplex-2100
Compatible
Hardware
Module
Description
VC-8A,
VC-4A
Analog voice interface module similar to VC-8 and VC-4 modules, except that
also support ADPCM.
Yes
Current Megaplex-4100 version supports VC-4A and VC-8A modules with
minimum hardware version 10 and minimum software version 13
Common Logic (CL) Modules
Currently, the following CL models are offered:
•
CL.1: common logic and cross-connect module. Provides the following
functionality:
ƒ
Basic multiplexing functions up to the E1 and T1 level (including signaling
processing, user-defined signaling format translations, companding law
conversions (A-law to μ-law, and vice versa), etc.)
ƒ
1/0 cross-connect functionality
ƒ
Nodal timing for TDM ports
ƒ
Ethernet services: only for M8E1, M8T1, M8SL modules with enabled
Ethernet ports. Support only for bundles from local Ethernet ports
terminated on the TDM ports of the same module
ƒ
Management access via the local serial and Ethernet ports, and inband
management via dedicated management timeslot over E1, T1 or SHDSL
ports.
A Megaplex-4100 equipped with CL.1 modules (see functional block diagram
in Figure 1-14) can replace Megaplex-2100 units (and other equipment from
the Megaplex-2100 family) in applications that require higher port capacity
and enhanced transport of Ethernet traffic over E1, T1, and SHDSL
infrastructure.
•
1-18
CL.1/155: common logic and cross-connect module with two STM-1/OC-3
links, includes a complete SDH/SONET traffic handling subsystem. Offers
expanded functionality beyond that of the CL.1 module, as follows:
ƒ
Selectable link standard (SDH or SONET)
ƒ
Multiplexing functions up to the SDH/SONET level
ƒ
SDH/SONET terminal and add/drop multiplexer functionality
ƒ
1+1 unidirectional APS (Automatic Protection Switching) per ITU-T
Rec. G.783 for SDH/SONET line redundancy
ƒ
4/1/0 cross-connect functionality
ƒ
Independent SDH/SONET timing subsystem, and extended nodal timing
for all the ports (including PDH and SDH/SONET ports)
ƒ
Ethernet services: same as for the CL.1 module
Physical Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
ƒ
Chapter 1 Introduction
Management access: all the options available for the CL.1 module, and in
addition inband management via the DCC over SDH/SONET links.
A Megaplex-4100 equipped with CL.1/155 modules (see functional block
diagram in Figure 1-16) supports E1 and T1 links, and in addition serves as a
SDH/SONET multiplexer, with enhanced transport of Ethernet traffic over E1,
T1, and SHDSL infrastructure.
•
CL.1/GbE: common logic and cross-connect module (see functional block
diagram in Figure 1-15) with two GbE links for connection to packet switched
networks. This CL module version provides the same TDM services as the CL.1
module, and in addition includes an Ethernet traffic handling subsystem
complying with Metro Ethernet Forum (MEF) specifications for providing
Ethernet Layer 2 services. The forwarding of Ethernet payload within the
Megaplex-4100 is configured by defining flows (a generic type of Ethernet
virtual connections). The current Megaplex-4100 version supports E-line flows
(an E-line is a type of Ethernet virtual connection that interconnects exactly
two bridge ports and functions as a virtual bridge). CL.1/GbE modules support
the following types of bridge ports:
ƒ
External Ethernet ports of I/O modules, and bundles configured on TDM
ports of I/O modules
ƒ
External GbE ports of CL.1/GbE modules, for a maximum of 4 GbE links per
Megaplex-4100, and a total transport capacity up to 2 Gbps. To enhance
availability, pairs of GbE ports can be configured to use 1+1 bidirectional
protection.
A Megaplex-4100 equipped with CL.1/GbE modules supports Ethernet bundles
and E1, T1, and SHDSL links, and it provides Ethernet gateway services for
Ethernet traffic from I/O modules (either from the Ethernet ports, or
transported by bundles over E1, T1, and SHDSL infrastructure) toward the
packet switched network.
•
CL.1/155GbE: common logic and cross-connect module with two STM-1/OC-3
and two GbE links. This module includes both SDH/SONET and Ethernet traffic
handling subsystems.
Therefore, a Megaplex-4100 equipped with CL.1/155GbE modules (see
functional block diagram in Figure 1-17) provides all the services supported
by CL.1/155 and CL.1/GbE modules, and in addition supports low-order
(VC-12/VT1.5 and VC-3), and high-order virtual concatenation (VC-4 or
STS-1), with multiple virtually concatenated groups per SDH or SONET link
respectively (up to eight low-order virtually concatenated groups). Each
virtually concatenated group can be used as a virtual bridge port. Both GFP
and LAPS encapsulation are supported, with or without LCAS.
Note
In this manual, the generic term CL module is used when the information is
applicable to all the CL models. The complete module designation is used only for
information applicable to a specific model.
All the CL module models provide the following main management functions:
•
Megaplex-4100 Ver. 2.0
Control over all the aspects of Megaplex-4100 system operations, including
the system timing aspects.
Physical Description
1-19
Chapter 1 Introduction
Installation and Operation Manual
•
Interfacing with the supervision terminal and other management systems
(Telnet hosts, SNMP-based management stations and Web browsers).
•
Storage of application software, which determines the Megaplex-4100
capabilities and features. This software is stored in flash memory, and
therefore can be remotely downloaded and updated through the
management link without taking the equipment off-line.
•
Storage of configuration databases. This information is stored in non-volatile
memory. The configuration databases can also be uploaded and downloaded
through the management link.
•
Collection of operational history (alarms, performance statistics, etc.).
Only one CL module is necessary per chassis, however the chassis has two slots
dedicated to this type of module. The second slot can be used to install a
redundant CL module of the same type, thereby providing a hot-standby
capability for the Megaplex-4100 system control functions.
Power Supply (PS) Modules
The Megaplex-4100 chassis can use both AC and DC power supply modules. The
current PS module versions are listed below:
•
DC-powered modules: PS/48 and PS/24. These 250W power supply modules
operate on -48 VDC and +24 VDC, respectively (nominal voltage is marked on
the module panel), and can provide line feed and ring voltages (-48 or
+24 VDC) to the I/O modules installed in the chassis, through an internal bus.
These voltages are sufficient for most types of voice modules, however when
a higher voltage is required (for example, for ISDN modules), it must be
provided by an external source.
•
AC-powered module, PS/AC: 200W power supply module, operates on
110 VAC and 230 VAC, 50/60Hz (nominal voltage is marked on the module
panel). When a phantom feed voltage must be supplied, it is always
necessary to use an external voltage source.
The recommended external feed and ring generation voltage source is the
Ringer-2200N/ISDN standalone unit offered by RAD.
The Megaplex-4100 chassis has two PS slots, thereby enabling the installation of
two PS modules. Normally a single PS module per unit is sufficient.
However, a second PS module may be added, for redundancy: both modules must
be of the same type (either standard, or low power), however it is allowed to
install an AC-powered and a DC-powered module. With a redundant PS module,
both modules are connected to power and share the load when the system is
operating. In case of failure or loss of input power, the remaining module
continues to supply the power alone. Switch-over is thus automatic and does not
disturb normal operation.
1-20
Physical Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
1.3
Chapter 1 Introduction
Functional Description
As shown in Figure 1-13, the Megaplex-4100 chassis has 14 slots (2 for PS
modules, 2 for CL modules, and 10 for I/O modules). These slots are
interconnected by means of a bus subsystem located on the backplane.
The bus subsystem on the backplane uses a dual-star topology, which comprises
two essentially identical sets of buses, each using a star topology (one star to
each CL module). The buses included in the backplane bus subsystem have the
following main functions:
•
PCM buses: carry E1 and T1 TDM traffic between the I/O modules and each of
the two CL modules. The PCM buses use a star topology, in which each I/O
module is connected by 6 buses, each operating at 8 Mbps, to both CL
modules.
This results in a total TDM capacity of 24 × 32 timeslots per I/O module.
•
Fast Ethernet data buses: carry Ethernet traffic between the I/O modules and
each of the two CL modules. The PCM buses use a star topology, in which
each I/O module is connected by 2 buses to each CL module.
The total payload bandwidth per I/O module is 100 Mbps. However, when
evaluating the bandwidth available to Ethernet payload generated by an I/O
module, this bandwidth should be interpreted as an average bandwidth; the
peak traffic handling value may be higher, considering the statistical
characteristics of the Ethernet traffic reaching the I/O module ports, and the
effects of activating the flow control option (independently configurable for
each external Ethernet port of an I/O module).
•
•
Timing buses: Megaplex-4100 has a dual timing bus system that has two
functions:
ƒ
Carry reference signals from the I/O modules and the SDH/SONET
subsystem to the timing subsystem
ƒ
Carry nodal clock signals from the timing subsystem to all the other
modules.
Control buses. The control buses carry control signals from the management
subsystem of each CL module to each I/O module installed in the chassis, and
transfer status and monitoring data from the I/O modules to the
management subsystem.
In addition to these sets of buses, the CL modules are interconnected by two
additional types of buses:
•
GbE bus for exchanging Ethernet traffic, and for traffic protection
•
STM-4/OC-12 bus for SDH/SONET traffic protection.
Megaplex-4100 Ver. 2.0
Functional Description
1-21
Chapter 1 Introduction
Installation and Operation Manual
System Functional Block Diagrams
The functions available from a Megaplex-4100 chassis depend on two factors:
•
The type of CL modules installed in the chassis. The capabilities of each type
of CL module are described in the Common Logic (CL) Modules section on
page 1-18.
•
The types of I/O modules installed in the chassis.
The resulting functionality is described by means of functional block diagrams:
•
Figure 1-14 shows the functional block diagram of a Megaplex-4100 unit
equipped with CL.1 modules
Megaplex-4100
I/O Subsystem
CL.1
I/O Module
TDM
I/O
Ports
PCM
Buses
Cross-Connect
Matrix
DS0
DS0
Cross-Connect
Cross-Connect
Timing
Buses
DS0
Timing
Cross-Connect
Subsystem
CLOCK
10
1 2
Power Suppy
Subsystem
AC
or
DC
Power
Power Supply
Module
Control and Status
DS0
Management
Cross-Connect
Subsystem
ETH
DCE
CONTROL
ALARMS
Figure 1-14. Functional Block Diagram – Megaplex-4100 with CL.1 Modules
•
Figure 1-15 shows the functional block diagram of a unit with CL.1/GbE
modules
•
Figure 1-16 shows the functional block diagram of a unit with CL.1/155
modules
•
Figure 1-17 shows the functional block diagram of a unit with CL.1/155GbE
modules
1-22
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Megaplex-4100
CL.1/GbE
I/O Subsystem
Ethernet Traffic Subsystem
ETH1
ETH ETH2
I/O
Ports ETH3
Fast
Ethernet
Buses
Ethernet
Switch
GbE Ethernet
GbE Ethernet
Switch
Switch
GbE
Ports
Ethernet
Termination
and
Processing
I/O Module
TDM
I/O
Ports
PCM
Buses
Cross-Connect
Matrix
DS0
DS0
Cross-Connect
Cross-Connect
Timing
Buses
DS0
Timing
Cross-Connect
Subsystem
CLOCK
10
1
Power Suppy
Subsystem
AC
or
DC
Power
Power Supply
Module
2
Control and Status
DS0
Management
Cross-Connect
Subsystem
ETH
DCE
CONTROL
ALARMS
Figure 1-15. Functional Block Diagram – Megaplex-4100 with CL.1/GbE Modules
Megaplex-4100 Ver. 2.0
Functional Description
1-23
Chapter 1 Introduction
Installation and Operation Manual
Megaplex-4100
CL.1/155
I/O Subsystem
SDH/SONET Subsystem
EX Port
PCM
Buses
PDH
PDH
Mapper
Mapper
DS0
DS0
Cross-Connect
Cross-Connect
I/O Module
(same as
Figure 1-14)
TDM
I/O
Ports
LO/HO
LO/HO
CrossCrossConnect
Connect
SDH/
SONET
Interface
Links
Timing
Buses
DS0
Timing
Cross-Connect
Subsystem
CLOCK
10
1
2
Control and Status
Power Suppy
Subsystem
AC
or
DC
Power
DS0
Management
Cross-Connect
Subsystem
Power Supply
Module
ETH
DCE
CONTROL
ALARMS
Figure 1-16. Functional Block Diagram – Megaplex-4100 with CL.1/155 Modules
Megaplex-4100
I/O Subsystem
CL.1/155GbE
Ethernet Traffic Subsystem
GbE
Ports
Fast
Ethernet
Buses
1
GbE
Ethernet
Switch
ETH1
Encapsulation
GFP
VCAT
Mapper
ETH ETH2
I/O
Ports ETH3
LAPS
8
VCG 1
to
VCG 8 SDH/SONET Subsystem
I/O Module
(same as
Figure 1-15)
EX Port
PCM
Buses
DS0
DS0
Cross-Connect
Cross-Connect
TDM
I/O
Ports
PDH
PDH
Mapper
Mapper
LO/HO
LO/HO
CrossCrossConnect
Connect
SDH/
SONET
Interface
Timing
Buses
DS0
Timing
Cross-Connect
Subsystem
1
2
CLOCK
10
Power Suppy
Subsystem
AC
or
DC
Power
Links
Power Supply
Module
Control and Status
DS0
Management
Cross-Connect
Subsystem
ETH
DCE
CONTROL
ALARMS
Figure 1-17. Functional Block Diagram – Megaplex-4100 with CL.1/155GbE Modules
1-24
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
A Megaplex-4100 system may include some, or all, of the following main
subsystems:
•
I/O subsystem: provides interfaces to the user’s equipment. See list of I/O
modules and their main characteristics in Table 1-1. You can find functional
descriptions of the I/O modules in their Installation and Operation Manuals.
•
DS0 cross-connect matrix: handles the TDM traffic. The matrix also handles
the signaling information associated with TDM traffic.
•
SDH/SONET subsystem (CL.1/155 and CL.1/155GbE only): includes the circuits
needed to interface to an SDH/SONET network:
•
ƒ
PDH mapper: handles the TDM traffic directed to the network, and
enables mapping any E1 or T1 port to any VC-12, respectively VT1.5.
ƒ
Low-order/high-order (LO/HO) cross-connect matrix: controls the routing
of VCs/VTs at all the levels among the PDH mapper, and the SDH/SONET
links. Also provides automatic protection switching (APS) for the network
links, and path protection. Supports an expansion (EX) port, an option
not used in the current version.
ƒ
SDH/SONET interfaces: provide the physical interfaces for the SDH/SONET
links.
Ethernet traffic handling subsystem (CL.1/GbE and CL.1/155GbE only):
includes the circuits needed to interface to a packet-switched network. The
Ethernet traffic handling subsystem located on CL.1/GbE and CL.1/155GbE
modules includes:
ƒ
GbE Ethernet switch: controls the forwarding of Ethernet traffic within
the Megaplex-4100, including forwarding from internal ports (bundles,
and for Megaplex-4100 with CL.1/155GbE modules – also virtually
concatenated groups) to external Ethernet ports
ƒ
GFP or LAPS encapsulation, and group mapper (CL.1/155GbE only):
handles the Ethernet traffic directed for transport over the SDH/SONET
network by means of virtually concatenated groups.
ƒ
GbE interfaces: provide the physical interfaces for the packet switched
network links.
In addition to the Ethernet traffic handling subsystem components located on
the CL.1/GbE and CL.1/155GbE modules, I/O modules with Ethernet ports (for
example, M8E1, M8T1, M8SL) also include a local Ethernet handling
subsystem (its functional block diagram is included in Figure 1-15). This
subsystem includes:
Megaplex-4100 Ver. 2.0
ƒ
Ethernet port interfaces: provide 10/100 Mbps physical interfaces for
external Ethernet links.
ƒ
Layer 2 Ethernet switch: provides the local Ethernet classification and
switching functions.
ƒ
Fast Ethernet data ports, used only when CL.1/GbE or CL.1/155GbE
modules are installed in the chassis: each port connects to the Ethernet
traffic handling subsystem of one CL module.
Functional Description
1-25
Chapter 1 Introduction
Installation and Operation Manual
When neither CL.1/GbE, nor CL.1/155GbE modules, are installed in the
chassis, Ethernet traffic can flow only between Ethernet ports and E1/T1
ports of the same I/O module.
ƒ
Note
Ethernet termination and processing: provides the interface between the
Layer 2 Ethernet switch and the local cross-connect matrix. In the
direction from the switch to the matrix, Ethernet frames are terminated
and processed for transmission through the appropriate bundles, that is,
over TDM media. In the inverse direction, the payload received from TDM
media is packetized and inserted in Ethernet frames for transmission to
the appropriate Ethernet port.
The Ethernet termination and processing function can also serve Ethernet traffic
carried through PDH ports of CL.1/155GbE modules.
For a detailed description of I/O module Ethernet traffic handling subsystem,
refer to the corresponding I/O module Installation and Operation Manual.
•
Timing subsystem: provides timing signals to all the Megaplex-4100 circuits,
and external (station) clock interfaces. For redundancy, two independent
subsystems, each located in a CL module, are used.
•
Management subsystem: controls Megaplex-4100 operation, stores its
software and configuration, and provides interfaces for local and remote
management, and for alarm reporting. The management subsystem is also
redundant: two independent subsystems, each located in a CL module, are
used.
•
Power supply subsystem: includes power supply modules that provide power
to the internal circuits, and an interface for external line feed. For
redundancy, two power supply modules can be installed in the chassis.
DS0 Cross-Connect Matrix
Handling the Payload of I/O Modules
The DS0 cross-connect matrix provides fully non-blocking 1/0 cross-connect
among I/O modules. This matrix operates in coordination with the cross-connect
matrices located on most types of I/O modules.
For CL.1/155 and CL.1/155GbE, fully non-blocking 1/0 cross-connect is also
supported among any combination of I/O module ports and virtual PDH ports of
the SDH/SONET subsystem, as described in the Handling of CAS Information
section below.
Note
In Megaplex-4100 with CL.1/155 and CL.1/155GbE modules, the operation of the
DS0 cross-connect matrix is fully coordinated with the operation of the LO/HO
cross-connect matrix, resulting in fully non-blocking 4/1/0 cross-connect.
The DS0 cross-connect matrix has a capacity of 240 × 32 DS0 (64 kbps timeslots)
for the I/O side, and therefore it supports the maximum number of E1 and T1 I/O
ports that can be installed in the Megaplex-4100 (80 when the chassis has 10
modules), and can also be used to route the associated signaling.
1-26
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The DS0 cross-connect matrix provides full control over the routing of individual
timeslots. This is needed for handling the payload of E1 ports with G.704
framing, T1 ports with SF or ESF framing, and for the inband management
timeslot. The traffic associated with ISDN ports is always handled in the DS0
mode. Accordingly, Megaplex-4100 distinguishes among three main types of
payload per timeslot:
•
Voice: timeslots carrying PCM-encoded payload, with A-law companding for
E1 ports and μ-law companding for T1 ports. Therefore, such timeslots
undergo conversion when transferred between ports with different standards
(E1 versus T1). The conversion is performed on the CL module.
Channel-associated signaling (CAS) information is always associated with
voice timeslots, and therefore it must also be converted when
cross-connecting timeslots from ports using different standards.
•
Data: data timeslots are transparently transferred from port to port. In
general, it is assumed that no CAS is associated with data timeslots.
•
Management: one timeslot can be assigned in any E1 or T1 port to carry
inband management traffic to the end user’s equipment. Such timeslots are
always directed to the CL management subsystem, for processing.
The flow of payload carried by data and voice timeslots is normally bidirectional
(full duplex connection). However, for individual timeslots, it is also possible to
define unidirectional flows, called unidirectional broadcasts, from one source (a
timeslot of a source port) to multiple destinations (each destination being a
selected timeslot of another port). See the Unidirectional Broadcast Function
section below.
Megaplex-4100 enables the user to individually route each timeslot. However, a
more efficient timeslot connection mode is also supported: a user-specified
group of consecutive timeslots can be cross-connected by specifying for the
source port the starting timeslot and the number of timeslots to be connected,
and the starting timeslot for the destination port. The same is true for a group of
consecutive cross-connected timeslots: they can also be disconnected as a group.
Cross-Connect Modes
The DS0 cross-connect matrix supports two cross-connect modes, selectable at
the level of the individual E1 and T1 port:
•
DS0 cross-connect mode – used when it is necessary to control the routing
of individual timeslots, and therefore it is relevant only when using a framed
mode. This cross-connect mode is also needed for handling the inband
management timeslot. In the DS0 cross-connect mode, Megaplex-4100
enables connecting payload and signaling between E1 to T1 ports; it also
enables connecting timeslots between E1 ports and SONET PDH ports, and
between T1 ports and SDH ports.
•
DS1 cross-connect mode – this cross-connect mode is used when it is
necessary to transparently transfer whole E1 or T1 streams. This is needed
for unframed streams, and for streams using proprietary framing; for E1
streams, it can also be used with ports using the basic G.704 framing mode
(G.732N and G.732N-CRC4) to transparently transfer all the payload timeslots
to a single destination. In the DS1 cross-connect mode, E1 ports can be
Megaplex-4100 Ver. 2.0
Functional Description
1-27
Chapter 1 Introduction
Installation and Operation Manual
mapped only to other E1 ports (including SDH PDH ports), and T1 ports can
be mapped only to to other T1 ports (including SONET PDH ports).
Handling of CAS Information
When CAS is used, the signaling information of each channel is carried by means
of up to four bits (signaling bits), designated by the applicable standards as bits
A, B, C, and D.
The number of bits actually available for carrying signaling information, and the
data rate at which signaling information can be transferred depend on the port
(E1 or T1) and the framing mode being used, which are determined by the
applicable international standards.
The information appearing in the signaling bits can be provided either by the voice
interface modules installed in the Megaplex-4100, or by digital PBXs or local
exchange trunks connected by E1 or T1 trunks to one of the E1 or T1 ports of the
Megaplex-4100.
Digital PBXs and local exchanges often use dedicated signaling protocols to
exchange the signaling information through the E1 or T1 trunk bits assigned to
CAS, and therefore may interpret the state of CAS bits in proprietary ways.
Megaplex-4100 can perform signaling protocol conversions, for example – to
enable the termination of PBX timeslots by a voice module installed in an I/O slot,
to connect a PBX to PSTN lines, etc.
For this purpose, the format of the signaling information is defined by specifying a
profile. A profile enables the user to specify translation rules for each individual
signaling bit. The available selections are A, B, C, D (value copied from the
corresponding incoming bit), ~A, ~B, ~C, ~D (inverted value of corresponding
incoming bit), 0 (always 0), and 1 (always 1). In addition to the translation of
individual bits, the receive path conversion section can also be used to define the
signaling bit patterns that indicate the busy and idle states.
The user can assign a separate profile to each TDM (E1 or T1) port, and therefore
each port, and even individual timeslots of a port, can use different receive and
transmit translation rules. Up to 5 different profiles, each covering a different set
of interoperability requirements, can be defined and stored in the Megaplex-4100
configuration databases.
Handling of PDH Port Payload
The cross-connect matrix of CL.1/155 and CL.1/155GbE modules also controls the
routing of payload carried by the PDH ports of the SDH/SONET subsystem located
on the same module. Note that when two CL.1/155 or CL.1/155GbE modules are
installed in the chassis, only the cross-connect matrix of the active (online) CL
module provides the cross-connect functions, and therefore only PDH payload
from the SDH/SONET links of the online CL module can be used.
For the PDH ports, the cross-connect matrix supports the two cross-connect
modes described above, DS0 and DS1 (the cross-connect mode is selectable at
the level of the individual PDH port). The main difference is that PDH ports
cannot operate in the unframed mode: therefore, in the DS1 mode the
cross-connect matrix is used to transparently transfer all the payload timeslots of
a PDH port to a single destination.
1-28
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The result is that the following services are available for the traffic flowing
through the PDH ports:
•
Services related to the TDM traffic:
ƒ
Connection of timeslots from I/O ports (channels) or virtual ports of other
modules installed in the Megaplex-4100 to the desired PDH port. When
using channel-associated signaling (CAS), the matrix also routes the
signaling information associated with each channel in parallel with the
channel data.
ƒ
Bypassing timeslots among the PDH ports, or among ports located on
other modules and the PDH ports located on the CL module.
ƒ
Unidirectional routing of timeslots, and broadcasting from one timeslot to
multiple destinations.
In addition to payload routing, the cross-connect matrix is also used to
activate local and remote loopbacks at the timeslot level on the CL PDH ports
(loopbacks should not be activated on timeslots assigned to bundles).
•
Connection of Ethernet payload (received from other I/O modules) to virtual
ports, called bundles, defined on the local PDH ports.
Full Timeslot versus Split Timeslot Assignment
For user ports that do not require a full timeslot (eight bits, equivalent to a
bandwidth of 64 kbps), Megaplex-4100 also permits split timeslot assignment,
that is, assignment of individual bits in a selected timeslot.
Split timeslot assignment increases the bandwidth utilization efficiency for TDM
modules or channels, because it enables the allocation of link bandwidth in
smaller (sub-DS0) units: the split timeslot assignment unit is 16 kbps (a pair of
consecutive bits in a timeslot).
Split timeslot assignment is supported by low-speed data modules and by ISDN
modules (see corresponding module Installation and Operation Manual).
The split timeslot assignment is performed in coordination with the modules
having sub-DS0 ports. It is not possible, nor practical, to mix bits from different
modules in the same DS0 timeslot.
Unidirectional Broadcast Function
The unidirectional broadcast mode enables a user at a central location to send
data or voice to multiple users connected to remote ports via the Megaplex-4100
links (simplex communication). In this mode, any message is simultaneously
received by all the remote unidirectional users, but none of them can send back
data to the originator.
This capability is achieved by separating the handling of the receive and transmit
paths for timeslots assigned to unidirectional channels.
When using the unidirectional broadcast mode, it is necessary to instruct each
port how to handle the traffic flow and signaling information. This is performed
by defining the timeslot type. For regular bidirectional channels, the timeslot
types are data, voice, and management. The additional selections available for
the unidirectional broadcast mode are as follows:
Megaplex-4100 Ver. 2.0
Functional Description
1-29
Chapter 1 Introduction
Installation and Operation Manual
•
Unidirectional broadcast – data: the timeslot is handled as a data channel.
This means that any signaling information associated with the channel is
ignored.
•
Unidirectional broadcast – voice: the timeslot is handled as a voice channel.
This means that:
1. It is necessary to select a link framing mode that supports channel
associated signaling, e.g., G.704 multiframe (G.732S) for E1, SF (D4) or
ESF for T1.
2. The signaling information of the channel is routed (automatically) in
parallel with the channel payload.
The unidirectional broadcast capabilities depend on the module type:
•
Modules with E1 and T1 ports ( for example, M8E1, respectively M8T1
modules): the payload received by a unidirectional broadcast timeslot is
distributed in parallel to multiple destination timeslots of other E1 or T1 links,
or to modules with unidirectional receive capabilities.
•
Voice and data I/O modules: not all the modules can support unidirectional
capabilities, but only modules which require a single timeslot per channel, and
that do not require handshaking for setting up a link. Therefore,
unidirectional broadcast is supported by VC-16/8/4 voice modules with E&M
interfaces, or by HS-12/6 or HS-R data modules; ISDN interface modules
cannot support this capability.
For I/O modules, the user can specify the operating mode of each
unidirectional channel either as unidirectional transmit, or unidirectional
receive:
ƒ
Unidirectional transmit: the I/O channel transmits, but cannot receive (its
receive path is disconnected). The information transmitted by the channel
can be routed to any number of other compatible ports in the same
Megaplex-4100 chassis, as well as to E1 or T1 ports for distribution to
multiple remote Megaplex-4100 units.
Only one timeslot is required on the internal PCM buses for each I/O
channel using this mode, because each destination port extracts the
payload from the same bus timeslot.
The selection of the destination timeslot at each of the other ports
connected to a unidirectional transmit channel is made during the
configuration of timeslot utilization at each destination.
ƒ
Unidirectional receive: the I/O channel receives, but cannot transmit (its
transmit path is disconnected). The user can select the source port (E1,
T1 or compatible I/O port) from which the channel receives, and the
specific timeslot. The same source port or bundle can be connected to
several channels operating in the unidirectional receive mode.
SDH/SONET Subsystem (CL.1/155 and CL.1/155GbE)
Figure 1-18 shows the functional block diagram of the complete SDH/SONET
subsystem, as integrated within the CL.1/155 modules. Figure 1-18 also presents
1-30
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
the APS and path protection connections between two CL.1/155 modules, and
the connections to the PCM and timing buses in the Megaplex-4100 chassis.
CONTROL ETH
CONTROL DCE
CL.1/155 A
Management Subsystem
Network Interface
Mapping
EX Port Interface
(Not Used)
63 E1/84 T1
PCM
Buses
DS0
CrossConnect
Matrix
E1/T1
Framer
LO
(VC-12/VT1.5/
VC-3)
Cross-Connect
Matrix
E1/T1
Mapper
STM-1 or OC-3
Dual Framer
(STM-1 or STS-3)
and
HO (STS-1)
Cross-Connect
Matrix
Timing
Buses
EX
Port 1
LINK 1
Port 2
LINK 2
Clock Signals
SDH/SONET
PDH
APS
Timing
Subsystem
CLOCK
Timing
Subsystem
CLOCK
PDH
SDH/SONET
Clock Signals
Mapping
Network Interface
APS
EX Port Interface
(Not Used)
63 E1/84 T1
PCM
Buses
DS0
CrossConnect
Matrix
E1/T1
Framer
E1/T1
Mapper
LO
(VC-12/VT1.5/
VC-3)
Cross-Connect
Matrix
Dual Framer
(STM-1 or STS-3)
and
HO (STS-1)
Cross-Connect
Matrix
EX
STM-1 or OC-3
Port 1
LINK 1
Port 2
LINK 2
Management Subsystem
CL.1/155 B
CONTROL ETH
CONTROL DCE
Figure 1-18. Megaplex-4100 SDH/SONET Subsystem
CL.1/155GbE modules have a similar SDH/SONET subsystem, which is integrated
with the Ethernet traffic subsystem (see Figure 1-20), and in addition have a
Megaplex-4100 Ver. 2.0
Functional Description
1-31
Chapter 1 Introduction
Installation and Operation Manual
virtual concatenation subsystem, explained in Using Virtual Concatenation
(CL.1/155GbE) section.
The SDH/SONET subsystem includes the following main sections:
•
•
•
Network interface, comprising:
ƒ
Network port interfaces
ƒ
SDH/SONET framers and high-order (HO – STS-1) cross-connect matrix.
Mapping section, comprising:
ƒ
E1/T1 framers
ƒ
E1/T1 mapper
ƒ
Low-order (LO – VC-12/VT1.5/VC-3) cross-connect matrix.
SDH/SONET timing subsystem.
For Megaplex-4100 equipped with two CL.1/155 or CL.1/155GbE modules, both
SDH/SONET subsystems are active: they operate independently of other CL
module subsystems that are switched to standby on the inactive (off-line) CL
module (although only the cross-connect matrix of the online CL module provides
service – see the Handling of PDH Port Payload section on page 1-28).
SDH/SONET Network Port Interfaces
Each CL.1/155 or CL.1/155GbE module has two STM-1/OC-3 ports. Each port has
an SFP socket that provides the physical interface. RAD offers a wide range of
SFPs covering requirements from short-range low-cost optical interfaces to longrange, high-performance interfaces. Optical SFPs are terminated in LC connectors.
RAD also offers SFPs with electrical interfaces for intra-office applications.
The port interfaces support the enhanced digital diagnostic monitoring interface
per SFF-8472, which enables collecting status and performance data from the
SFPs, as well as alerting in case abnormal conditions may cause damage or
performance degradation.
For safety, Megaplex-4100 uses automatic laser shut-down (ALS), which protects
against accidental exposure to laser radiation in case of fiber breaks or
disconnections. This is achieved by automatically switching off the transmitter of
an SDH/SONET interface when the receiver of the same interface reports loss of
the optical signal. To enable automatic recovery, the transmitter is periodically
turned back on, for a short time: if the receive signal does not reappear, the
transmitter is turned back off, whereas if the receive signal reappears the
transmitter remains (normal operation).
SFPs are hot-swappable, and can be replaced in the field. This enables upgrading
the network port interface characteristics as network topology changes.
SDH/SONET Framer Subsystem and HO (STS-1) Cross-Connect
Matrix
The SDH/SONET framer subsystem provides the frame assembly/disassembly
services and SDH/SONET overhead processing for the link to the network. The
framers also handle the routing of the payload between the two CL modules, via
the automatic protection switching (APS) bus.
1-32
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The STS-1 cross-connect matrices in the two CL.1/155 and CL.1/155GbE modules,
which are integrated with the SDH/SONET framers, provide the functions needed
to route the high-order payload in the SONET mode.
Note
The additional expansion port, terminated in the EX port, is not used in this
Megaplex-4100 release.
The framer operating mode, SDH or SONET, is selected by software configuration.
The two modules must always use the same mode, and therefore selecting the
mode for one module automatically switches the other to the same mode.
The following network interface operating modes can be configured, depending
on the hardware installed in the Megaplex-4100:
•
•
When a single CL.1/155 or CL.1/155GbE module is installed, it is possible to
use the two ports of the installed module in one of the following ways:
ƒ
As two independent ports, to provide more bandwidth on the links to the
SDH/SONET network, or for connection to an SDH/SONET ring
ƒ
Configure the two ports as a protection group, where at any time one
port serves the working link and the other serves the protection link.
When two CL.1/155 or CL.1/155GbE modules are installed, a total of four
SDH/SONET ports are available. When protection of SDH/SONET links is not
required, each SDH/SONET port in the chassis can be independently used,
provided a few restrictions are observed:
ƒ
The total number of E1s or T1s that can be connected to local I/O ports is
63 for SDH interfaces, and 84 for SONET interfaces. These E1s or T1s are
always taken from the SDH/SONET links of the active CL module
ƒ
The capacity of the internal bypass links between the SDH/SONET
subsystems on the two CL modules is not exceeded.
However, it is also possible to activate APS on pairs of two ports, as
explained in the CL Module Redundancy section starting on page 1-58). Each
pair can provide one fully protected link, for example, for a terminal
multiplexer application.
SDH/SONET Link Protection Mechanisms
Megaplex-4100 units with at least two SDH/SONET links support the 1+1
MSP/APS (multiplex section protection with automatic protection switching)
physical layer protection mechanism. This mechanism can be activated on links on
the same CL.1/155 or CL.1/155GbE module, as well as between links on different
CL.1/155 or CL.1/155GbE modules (see the CL Module Redundancy section
starting on page 1-58).
The mechanism provides single-ended protection (also called unidirectional
protection for SDH, and unidirectional linear protection switching for SONET), for
the connection to the SDH/SONET network.
The reason the protection mode is called unidirectional is that each of the two
units at the end of the multiplex section can switch to protection after detecting
a signal failure or degradation, without any handshaking with the other end.
Therefore, switching to protection is fast (within 50 msec).
Megaplex-4100 Ver. 2.0
Functional Description
1-33
Chapter 1 Introduction
Installation and Operation Manual
Although the unidirectional protection mode does not use the K1 and K2 bytes in
the STM-1/OC-3 overhead, the switching end will update the K1 and K2 bytes
sent to the network, to indicate the actual protection switching status.
The APS bus interconnecting the two SDH/SONET framers is capable of carrying
the full traffic load, and therefore supports both APS and path protection. The
bandwidth on the APS bus is configured with VC-12/VT1.5 granularity.
Mapping Matrix
The LO cross-connect matrix is used to perform the mapping of the traffic on the
SDH/SONET links. This is a non-blocking cross-connect matrix that controls the
mapping of payload and overhead to these interfaces. The matrix supports
low-order cross-connections (VC-12 and VC-3 for SDH links, VT1.5 for SONET
links).
E1/T1 Framers and Mappers
The TDM payload directed to the network is structured by the DS0 cross-connect
matrix and applied to the E1/T1 framers. Each framer behaves as a virtual PDH
port, with user-selectable framing: each CL.1/155 or CL.1/155GbE module can
have up to 63 E1 ports, or up to 84 T1 ports, in accordance with the SDH/SONET
framing mode.
The operation mode of each framer can be configured by the user:
•
For SDH network interfaces, E1 ports are supported
•
For SONET network interfaces, T1 ports are supported.
The frame type is also selectable, separately for each port:
•
For E1 ports, either basic G.704 framing (identified as G732N) or G.704
multiframe (G.732S) can be selected.
•
For T1 ports, the selections are SF (D4) and ESF.
Each framer adds the appropriate overhead and creates the frame structure.
The data stream provided by each framer is applied to the E1/T1 mappers:
•
For E1 ports, the mapper enables mapping the port data stream to any of the
63 VC-12 in the STM-1 signal.
•
For T1 ports, the mapper enables mapping the port data stream to any of the
84 VT1.5 in the OC-3 signal.
SDH/SONET Timing Subsystem
The timing subsystem of each CL.1/155 or CL.1/155GbE module generates a clean
clock signal (the S-subsystem clock signal) for use by the SDH/SONET subsystem
circuits. This signal can also be configured as reference source for the
Megaplex-4100 system timing subsystem (refer to Timing Subsystem section for
details). The functional block diagram of the SDH/SONET timing subsystem is
shown in Figure 1-19.
The SDH/SONET timing subsystem can be configured to use the following
reference sources:
1-34
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 1 Introduction
•
The recovered receive clock signals of the local SDH/SONET ports
•
The system nodal clock
When the system (nodal) clock must be locked to the S-subsystem timing, never
select the system clock as reference for the SDH/SONET timing generator, or an
unstable clock will result.
•
The Megaplex-4100 internal clock.
Receive Clocks
from Local
SDH/SONET
Links
Main
Fallback
Internal
Clock
SDH/SONET
Reference
Selector
Main
Fallback
SDH/SONET
Subsystem
Timing
Generator
SDH/SONET
(S-Subsystem)
Clock
System Clock
(2048 kHz)
Figure 1-19. SDH/SONET Timing Subsystem
Two sources can be specified: a higher-priority main source, and a fallback source
used in case the main source fails. Alternatively, when using the recovered
receive clocks of SDH/SONET ports as reference sources, the SDH/SONET timing
subsystem can be configured to automatically select the best timing source in
accordance with the contents of the SSM message received from the SDH/SONET
ports (the SSM message is carried in the S1 byte of the SDH/SONET overhead). In
this case, the SSM sent by the Megaplex-4100 to the network links reflects the
quality of the selected source. This provides clock traceability.
The station clock can also be configured to serve as a clock source with traceable
quality, based on SSM in this case, the station clock must be configured as
system clock source, and the reception of SSM messages on the station clock
interface must be enabled. The system clock can then be used as reference
source for the SDH/SONET subsystem (see additional information in the Station
Timing section starting on page 1-52).
Note that automatic SSM-based selection should be used only when at least two
suitable sources are active. This minimum number can consist of two different
SDH/SONET links (this is always the case in a ring topology), or one SDH/SONET
link and one station clock interface.
Only one SDH/SONET subsystem timing reference is generated by each CL
module, because at any time only one timing subsystem is active. When two CL
modules are installed, the active module is selected to provide the reference
timing: this is the master timing source. The other CL module is automatically
used as fallback source.
Megaplex-4100 Ver. 2.0
Functional Description
1-35
Chapter 1 Introduction
Installation and Operation Manual
Integration of SDH/SONET Subsystem with Ethernet Traffic Subsystem
(CL.1/155GbE)
Figure 1-20 shows the functional block diagram of the complete SDH/SONET and
Ethernet traffic subsystems, as integrated within a CL.1/155GbE module.
To Other CL
CL.1/155GbE
APS
Mapping
SDH/SONET Network
Interface
EX Port Interface
(Not Used)
63 E1/84 T1
Dual Framer
(STM-1 or STS-3)
and
HO (STS-1)
Cross-Connect
Matrix
PCM
Buses
DS0
CrossConnect
Matrix
E1/T1
Framer
E1/T1
Mapper
LO
(VC-12/VT1.5/
VC-3)
Cross-Connect
Matrix
EX
STM-1 or OC-3
Port 1
LINK 1
Port 2
LINK 2
Clock Signals
SDH/SONET
PDH
To
Timing
Buses
Timing
Subsystem
Ethernet Traffic Subsystem
CLOCK
Ethernet Mappers
Encapsulation
VCG 1
GFP
VCG
Mapper
GbE
Ethernet
Switch
10 Fast Ethernet
Traffic Buses
to I/O Modules
VCG 8
LAPS
GbE Ports
(SFP Sockets
or RJ-45)
SFP or
Copper
Interface
GbE Interfaces to
Other CL.1/155GbE
GbE 1
SFP or
Copper
Interface
GbE 2
Management Subsystem
10 Fast Ethernet Management
Ethernet
Management Buses
to I/O Modules
Switch
Management Subsystem
LAN
Interface
Serial RS-232
Interface
CONTROL ETH
CONTROL DCE
ALARM
Figure 1-20. CL.1/155GbE Module with SDH/SONET and Ethernet Traffic Subsystem
1-36
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 1 Introduction
•
The interaction between the SDH/SONET subsystems located on different
CL.1/155GbE modules is as shown in Figure 1-18.
•
The interaction between the two Ethernet traffic subsystems located on
different CL.1/155GbE modules is made via two internal GbE interfaces
For CL.1/GbE modules, the Ethernet traffic subsystem does not support virtual
concatenation, and therefore it does not include the encapsulation and virtually
concatenated group mapper (see Megaplex-4100 functional block diagram in
Figure 1-15).
The connection of Ethernet traffic from I/O modules to the CL.1/155GbE is made
through a set of 10 Fast Ethernet buses, one from each I/O slot. Another set of
Fast Ethernet buses is used for the management traffic.
The forwarding of the Ethernet traffic within the Megaplex-4100 is controlled by
the GbE Ethernet switch. For example, any Ethernet traffic between different I/O
modules uses the services of this switch.
GbE Ethernet Switch
The GbE Ethernet switch is a high-capacity Ethernet switch with classifier, capable
of handling a wide range of forwarding algorithms, and provides extensive
support for QoS features. The switch has memory-based switch fabric with true
non-blocking switching performance, and collects a wide range of performance
monitoring parameters, which can be read by management.
The Ethernet switch has 24 Fast Ethernet ports and 4 GbE ports, which are used
as follows:
•
Two external GbE ports, one connected to the GbE 1 interface and the other
to the GbE 2 interface. The two ports can be configured to operate as a
redundancy pair, using hardware-based path and link failure for rapid
switching to the backup link (see the Redundancy for PSN Connections
section starting on page 1-63 for details).
•
10 Fast Ethernet ports are used for Ethernet traffic from I/O modules, one
from each I/O slot.
•
Two GbE ports are internally connected to the GbE switch of the other CL
module installed in the Megaplex-4100.
•
Each switch port is supported by an independent MAC controller that
performs all the functions required by the IEEE 802.3 protocol. The maximum
frame size supported by the basic Ethernet switch is 1600 bytes.
•
The frames passed by the MAC controllers are analyzed by the ingress policy
controller of the corresponding port before being transferred, through the
switch fabric, to an internal queue controller, which controls the frame egress
priorities and inserts them in separate queues. The switch supports up to
four transmission classes for the Fast Ethernet ports, and up to eight
transmission classes for the GbE ports. The queues are connected to the
ports through port egress policy controllers. This approach provides full
control over traffic flow, and ensures that congestion at one port does not
affect other ports.
Megaplex-4100 Ver. 2.0
Functional Description
1-37
Chapter 1 Introduction
•
Installation and Operation Manual
The switch includes a flow classification engine categorizing packets into
flows in accordance with user-defined classification rules. Multiple rules may
be applied to each flow. Classification takes place at full wire speed. The
switch recognizes standard frame types. Using this mechanism for Ethernet
services provided by Megaplex-4100 is described in the Megaplex-4100
Ethernet Services section.
GbE Port Interfaces
The GbE ports provide the physical connection to the packet switched network.
These ports can be ordered with one of the following interfaces:
•
10/100/1000BASE-T copper ports. This type of ports support
auto-negotiation, with user-specified advertised data rate (10, 100 or
1000 Mbps) and operating mode (half- or full-duplex).
The ports also support automatic polarity and crossover detection, and
polarity correction, for connection through any type of cable to any type of
Ethernet port (hub or station).
Alternatively, auto-negotiation can be disabled and the rate and operating
mode be directly specified.
•
SFP sockets, for installing SFP plug-in modules. Support for standard SFP
optical transceivers for the GbE link interfaces enables selecting the optimal
interface for each application. RAD offers a wide range of SFPs covering
requirements from short-range low-cost optical interfaces to long-range,
high-performance interfaces.
This type of ports should be configured to operate without autonegotiation,
in the 1000 Mbps full duplex mode.
Flow Control Options
The user can enable flow control for the GbE ports. When flow control is enabled,
it is always activated only on the port (or ports) involved in congestion: other
ports are not affected.
Flow control is available in both the half-duplex and full-duplex modes:
•
In the half-duplex mode, flow control uses a collision-based scheme to
throttle the connected stations when the free buffer space of the
corresponding port is too low, to avoid discarding frames during network
congestion (this approach is called back pressure). When the buffer space of
a port is almost full, its MAC controller forces a collision in the input port
when an incoming frame is sensed (the alternative, without flow control, is to
discard the incoming frame).
•
In the full-duplex mode, the standard flow control method defined in IEEE
802.3x is used, which is based on pause frames and enables stopping and
restoring the transmission from the remote node. However, this method can
only be used when auto-negotiation is enabled on the port, and the node
attached to the port supports pause frames.
The Ethernet switch internal MAC controllers discard all the received IEEE 802.3x
pause frames, even when full-duplex flow control is disabled or the port is in the
half-duplex mode.
1-38
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Forwarding Algorithms and VLAN Support
The Ethernet switch operates as a MAC bridge that automatically learns the MAC
addresses, and the port through which frames addressed to a foreign destination
are to be transmitted.
Only active MAC address/port number mappings are actually stored: after a
user-defined aging interval, inactive mappings are removed from the switch
memory.
The Ethernet switch can use both port information and the frame VLAN
information to select the ports among which traffic can be forwarded. Using only
the port information is referred to as the VLAN-unaware mode; any mode which
uses VLAN information is called VLAN-aware.
The VLAN mode can be separately selected for the customer’s edge side (toward
the I/O modules) and for the service provider side (toward the GbE ports and
virtually concatenated groups), in accordance with the specific application
requirements.
Note
In the Megaplex-4100, the switch operates in the IEEE 802.1Q shared (SVL)
learning mode.
Using Virtual Concatenation (CL.1/155GbE)
Virtual concatenation (VCAT) is available for Megaplex-4100 equipped with
CL.1/155GbE modules (see Figure 1-20). Refer to Appendix C for background
information on virtual concatenation.
The Ethernet mapper subsystem handles all the functions related to the use of
virtual concatenation, and the preparation of Ethernet traffic for efficient
transport over the SDH/SONET network.
The Ethernet mapper subsystem includes the following functions:
•
LAPS encapsulation
•
GFP encapsulation
•
Virtually concatenated group mapper.
Megaplex-4100 also supports the Link Capacity Adjustment Scheme (LCAS),
covered by ITU-T Rec. G.7042.
Encapsulation Functions
Ethernet frames must be encapsulated before transport over the SDH/SONET
network. Two types of encapsulation are supported (see Appendix C for
additional details):
•
LAPS (Link Access Protocol – SDH) encapsulation in accordance with ITU-T
Rec. X.86
•
GFP (Generic Framing Procedure) encapsulation in accordance with ITU-T Rec.
G.7041, using the framed mode.
Megaplex-4100 Ver. 2.0
Functional Description
1-39
Chapter 1 Introduction
Installation and Operation Manual
The user can select the desired encapsulation mode, independently, for each
virtually concatenated group. The encapsulation parameters can also be
configured, for best performance in specific applications.
The encapsulated frames of each virtually concatenated group are applied to the
virtually concatenated group (VCG) mapper.
VCG Mapper Functions
The mapper maps the Ethernet traffic for transmission over the SDH/SONET
network, and creates the virtually concatenated groups (VCGs) that enable the
user to control the utilization of the bandwidth available on the link to the
SDH/SONET network.
Note
For compatibility with equipment from other vendors, the user can configure the
mapper to simulate the use of virtual concatenation even when the group
comprises a single virtual container/SPE.
Alternatively, when a group comprises a single virtual container/SPE, the virtual
concatenation can be disabled: in this case, the Ethernet traffic from the port
connected to the mapper is assigned a whole TU/TUG on the network link.
Link bandwidth utilization is configured by selecting the type and number of
VCs/VTs allocated to each group. Following are several examples of bandwidth
allocation enabled by virtual concatenation:
•
When using VC-3: maximum of two virtually concatenated groups per
Megaplex-4100. For example, assuming that it is necessary to support
streaming payload over full duplex Ethernet, a virtually concatenated group
using two VC-3 can be used to carry the full traffic load of one 100BASE-TX
Ethernet port.
•
When using VC-12: the 63 VC-12s can be divided as required to create up to
8 virtually concatenated groups. For example, for streaming payload, a group
using 5 VC-12 can be used to carry the full traffic load of a 10BASE-T
Ethernet port over SDH; 50 VC-12 are needed to carry the full traffic load of a
100BASE-TX Ethernet port.
For other types of payload, the statistical distribution of the traffic and the
optional use of flow control, reduce the bandwidth requirements in
accordance with the long-term average data rate.
•
When using VT1.5: the 84 VT1.5s can be divided as required to create up to 8
groups. For example, a group using 7 VT1.5 can be used to used to carry the
full traffic load of a 10BASE-T Ethernet port over SONET. However, the
maximum number of VT1.5s in any group cannot exceed 64 (this number is
sufficient for carrying the full traffic load of a 100BASE-TX Ethernet port).
When virtual concatenation is not used, one group can be assigned the full VC-4
bandwidth.
It is allowed to build several virtually concatenated groups using different types
of VCs/VTs: for example, when using VC-12 to carry PDH traffic, one or two
groups can use VC-3s, and the remaining bandwidth (17 VC-12) can be assigned
to one or two additional virtually concatenated groups.
1-40
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The routing of the VCG payload is defined by means of mapping (mapping is the
selection of specific VCs/VTs to be used to carry each virtually concatenated
group, in the number needed to provide the required bandwidth). This operation
creates the trails that are needed to connect the local users to remote locations
through the SDH/SONET network.
Support for LCAS
Each virtually concatenated group with two or more VCs/VTs can be configured to
support LCAS.
With LCAS, the capacity of a virtually concatenated group can be hitlessly
decreased when one of the VCs/VTs fails; when the failure is no longer present,
the group will automatically and hitlessly recover to return to the normal capacity.
Another LCAS advantage is that it allows setting up a link even when the number
of VCs/VTs at the two endpoints, or anywhere along the trail followed by the VCG,
is not equal.
The user can configure various LCAS protocol parameters, and can also specify a
minimum number of VCs/VTs for the group capacity: if the number of VCs/VTs
decreases below this minimum, an alarm will be generated.
Megaplex-4100 Ethernet Services
Ethernet Service Model
In typical applications, Megaplex-4100 enables customers connected to its ports
to access a remote service provider, or the Internet, over an Ethernet network.
The Megaplex-4100 Ethernet subsystem supports two main categories of
services:
•
Ethernet gateway services: the Megaplex-4100 collects customer’s traffic
from the Ethernet ports located on I/O modules, and forwards the traffic
through the GbE ports located on CL.1/GbE or CL.1/155GbE modules toward
the service provider PoP, or to an Internet access node
•
Ethernet transport services: traffic received from the Ethernet ports located
on I/O modules, and GbE ports located on CL.1/155GbE modules, is
transported over TDM links (by means of bundles over E1 and T1 links, and
virtually concatenated groups over SDH/SONET links)
The two categories are simultaneously supported, as explained below in the
Ethernet Services Subsystem section.
The service model is best described in the terms used by the Metro Ethernet
Forum (MEF), which specifies clearly-defined service standards for providing
Ethernet services over metropolitan Ethernet networks. The MEF service model,
adapted to the Megaplex-4100, is illustrated in Figure 1-21.
Megaplex-4100 Ver. 2.0
Functional Description
1-41
Chapter 1 Introduction
Installation and Operation Manual
Ethernet Ports
on
I/O Modules
GbE Ports
on
CL Modules
Metropolitan
Ethernet
Network
Customer
Network
Megaplex-4100
Service
Provider (SP)
Edge
Customer (C)
Edge
Figure 1-21. Megaplex-4100 as Access Node to Ethernet Services
Note
The term customer’s edge refers to the physical or logical point at which
customer’s traffic is handed over to a network interface, for transport over the
network.
The service provider edge is the point at which customer’s traffic (received
through a customer’s edge network interface and processed for transport) is
handed over to a service provider access point or PoP.
MEF describes two Ethernet services types:
•
E-line service: provides a point-to-point Ethernet virtual connection (EVC).
Within Megaplex-4100, E-line services can be provided between a customer
and a service provider’s PoP (Figure 1-22.A), or between two customers
(Figure 1-22.B).
Megaplex-4100
To Service
Provider (SP)
Customer’s
Equipment
(CE)
E-Line
A. E-Line from Customer’s Equipment to Service Provider PoP
Megaplex-4100
Customer’s
Equipment
(CE)
E-Line
Customer’s
Equipment
(CE)
B. E-Line between two Customers
Figure 1-22. Megaplex-4100 E-Line Service Configurations
For simplicity, Figure 1-22 shows the customers connected directly to I/O
module Ethernet ports, and the link to the service provider’s PoP – directly
1-42
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
connected to a GbE port on a CL module. However, the connections can also
be made over bundles on E1 or T1 links (including bundles on PDH ports of CL
modules with SDH/SONET subsystems), or over virtually concatenated groups
(supported by CL module with SDH/SONET subsystems).
•
Note
E-LAN service: provides multipoint connectivity, i.e., may connect two or more
Ethernet users, in a way similar to that achieved by connection to a LAN. An
E-LAN implemented within Megaplex-4100 is illustrated in Figure 1-23.
The current Megaplex-4100 software revision supports only E-Line services.
Megaplex-4100
To Service
Provider (SP)
E-LAN
Customer’s
Equipment
(CE)
Customer’s
Equipment
(CE)
Customer’s
Equipment
(CE)
Figure 1-23. Megaplex-4100 E-LAN Service Configuration
Ethernet Services Subsystem
Structure
Ethernet services are provided by means of the Megaplex-4100 I/O modules with
Ethernet ports (M8E1, M8T1, M8SL), which can serve as customer’s edge network
interfaces, and by means of the CL.1/GbE and CL.1/155GbE modules, which
provide GbE ports that can serve as service provider’s edge interfaces.
The structure of the complete Megaplex-4100 Ethernet services subsystem is
shown in Figure 1-24.
The customer’s edge traffic accepted by Ethernet ports on I/O modules is
directed to other interfaces that can transfer the traffic to the transport
network. These interfaces are as follows:
•
Bundles (a type of virtual port) defined on the local I/O module E1 or T1
ports, or on other modules with E1 or T1 ports (this includes PDH ports on
CL.1/155 and CL.1/155GbE modules).
Two types of bundles can be defined on E1 and T1 ports:
ƒ
Megaplex-4100 Ver. 2.0
Bundles using HDLC as the Layer 2 protocol. The bandwidth assigned to a
HDLC bundle depends on the number of timeslots assigned by the user
(any even number of timeslots, up to a maximum of 30 for E1 ports, up
to 24 for T1 ports. Up to four HDLC bundles can be defined on a framed
port, where each bundle is assigned the desired fraction (number of
timeslots) of the port bandwidth, in accordance with user’s bandwidth
requirements.
Functional Description
1-43
Chapter 1 Introduction
Installation and Operation Manual
An unframed E1 port supports a single HDLC bundle, which occupies the
whole port bandwidth (2048 kbps, equivalent to 32 timeslots).
PDH ports also support HDLC bundles, but CL modules do not include the
Ethernet termination subsystem needed to support Ethernet bundles:
only I/O modules with Ethernet ports (M8E1, M8T1, M8SL) have the
required subsystem. Therefore, the PDH port timeslots assigned to an
Ethernet bundle must be sent for processing to a user-selected I/O
module, via the Megaplex-4100 PCM buses, and the resulting Ethernet
traffic is returned to the CL module via the Fast Ethernet traffic bus of
that I/O module.
Fast Ethernet
Connections
I/O Module 1
(M8E1, M8T1, M8SL)
TDM Ports
(E1/T1)
1
CL.1/155GbE
GbE 1
Bundle
Termination
1
GbE 2
VCG 1
8
32
GbE
Ethernet
Switch
Ethernet
Layer 2
Switch
VCG 8
Motherboard
ETH1
ETH2
ETH3
Encapsulation, SDH/SONET
Virtual
LINK 1
Concatenation
Mapper, and
LINK 2
SDH/SONET
Framer
CL.1/155GbE
GbE 1
GbE 2
VCG 1
GbE
Ethernet
Switch
VCG 8
Encapsulation, SDH/SONET
Virtual
LINK 1
Concatenation
Mapper, and
LINK 2
SDH/SONET
Framer
I/O Module 10
Figure 1-24. Ethernet Services Subsystem (Megaplex-4100 with CL.1/155GbE
Modules)
ƒ
1-44
Bundles using MLPPP as the Layer 2 protocol. MLPPP is an extension of
the PPP protocol that uses the PPP Link Control Protocol (LCP) and Bridge
Control Protocol (BCP) to bind two or more links to provide increased
bandwidth. For the current Megaplex-4100 version, only unframed E1
ports support MLPPP bundles, i.e., ports of M8E1 and M8SL modules; for
these modules, the user can configure the bundle to extend over any
number of E1 ports (all operating in the unframed mode), up to the
maximum supported by the module (8 ports). The bandwidth
automatically assigned to an MLPPP bundle depends on the selected
number of ports: therefore, the maximum bandwidth of an MLPPP bundle,
achieved when the bundle uses all the 8 ports of the module in the
unframed mode, is 8×2048 kbps (16384 kbps). Only one MLPPP bundle
may be active at any time on an I/O module.
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The maximum number of bundles that may be defined on an I/O module
(M8E1, M8T1, or M8SL) is 32.
•
Virtually concatenated groups, defined on the SDH/SONET links of CL.1/155
and CL.1/155GbE modules
•
GbE ports located on the Megaplex-4100 CL.1/GbE and CL.1/155GbE modules
Each of the above-mentioned interfaces (either customer’s edge or service
provider’s edge interface) is generically referred to as a bridge port. The Ethernet
traffic flows (is forwarded) among the desired bridge ports in accordance with
user-configured rules that define Ethernet Virtual Connections (flows). The total
number of bridge ports supported by a Megaplex-4100 is 370, as follows:
•
For I/O modules with Ethernet ports:
ƒ
One bridge port can be defined on each Ethernet physical interface.
ƒ
One bridge port can be defined on each bundle.
Therefore, the maximum number of bridge ports that can be defined on any
I/O module with Ethernet ports is up to 35 (3 bridge ports on Ethernet
physical interfaces, and 32 bridge ports defined on bundles).
•
For CL modules:
ƒ
One bridge port can be defined on each GbE physical interface
ƒ
One bridge port can be defined on each bundle, up to a maximum of four
HDLC bundles per port
ƒ
One bridge port can be defined on each virtually concatenated group
configured on an SDH/SONET port, up to a maximum of eight virtually
concatenated groups per SDH/SONET subsystem.
Using Flows to Control Ethernet Traffic Forwarding
As explained in the Ethernet Service Model section starting on page 1-41, the
forwarding of Ethernet traffic is controlled by configuring flows. A flow
interconnects at least two bridge ports, however a given bridge port can serve as
the termination point of several flows. The maximum number of traffic flows that
can be defined on a Megaplex-4100 is 250.
Note
An additional flow, 251, can be added to carry management traffic.
Ethernet switching occurs at Layer 2 (based on MAC addresses), and is basically
configured by first mapping bridge ports as termination points for flows, and
then specifying classification rules. Alternatively, forwarding can use only the
bridge port information (see the Forwarding Algorithms and VLAN Support section
starting on page 1-39).
A flow functions as a virtual bridge. The switching functionality is actually
distributed between the I/O module Ethernet switches, and the switches located
on CL.1/GbE and CL.1/155GbE modules, and is implemented in accordance with
the following rules:
•
Megaplex-4100 Ver. 2.0
The I/O module Ethernet switch can handle alone local flows, i.e., flows
between local Ethernet ports and bundles located on the same module. It will
not allow E-line flows between Ethernet ports on the same module.
Functional Description
1-45
Chapter 1 Introduction
Installation and Operation Manual
Whenever a flow is directed to another module, the I/O module Ethernet
switch sends the payload to the GbE Ethernet switch on the CL module via
the Fast Ethernet traffic connection.
As a result, the total Ethernet traffic handling capacity of an I/O module is a
maximum of 16 Mbps for traffic directed to local TDM ports via bundles, and a
maximum of 100 Mbps for traffic directed to other modules, that is, traffic
directed to another I/O module, to SDH/SONET ports, and/or GbE ports on
the CL modules.
Note
The above-mentioned capacities should be interpreted as long-term average
capacities; considering the statistical characteristics of the customer’s Ethernet
traffic reaching the module ports, the short-term peak traffic handling value may
be much higher (because excess payload is temporarily stored in Ethernet switch
buffers), and the effects of activating the flow control option (independently
configurable for each Ethernet port).
•
The CL module GbE Ethernet switch handles the flows terminated at GbE
ports, at the virtually concatenated groups on SDH/SONET links, and flows
between different modules (for example, flows between I/O modules, and
flows between the two CL modules). The CL module Ethernet switch also
allows flows between GbE ports on the same module.
The traffic between the two GbE Ethernet switches on the two CL modules
passes through two internal GbE ports; the capacity of this interconnection
ensures that there is no limitation when traffic must be transferred between
the CL modules.
The GbE Ethernet switch also enables using redundancy between the GbE
ports (refer to the Redundancy for PSN Connections section starting on page
1-63 for details). Note that when GbE port redundancy is enabled, all the
traffic is configured on the primary GbE port (no configuration can be
performed on the GbE port configured as secondary).
A flow connects only the user-mapped bridge ports, that is, transfers Ethernet
frames with user-specified characteristics only between these bridge ports and
prevents transfer of such frames to any bridge port which is not part of the same
flow (this is rather similar to what is expected of a virtual private network (VPN)).
Therefore, each flow must discriminate (be aware of) among the Ethernet frames
reaching an associated bridge port in order to determine how to handle
customers’ traffic. Although this discrimination can be made simply by defining
closed sets of ports (exactly two for the E-line service, two or more for the E-LAN
service), this approach does not permit Ethernet switching to take place. When
Ethernet switching is needed, the discrimination is mainly based on the
customer’s edge and service provider’s edge VLAN identifiers (C-VLAN ID and
SP-VLAN ID, respectively) received in each frame – a forwarding mode referred to
as VLAN-aware, and is supplemented by specifying the relevant ports. Another
forwarding mode, referred to as VLAN-unaware, is used to correctly forward
untagged frames, priority-tagged frames, and frames with unknown VLAN IDs
among user-specified ports.
The range of VLAN IDs that can be used for Ethernet traffic with IEEE 802.Q tags
is 1 to 4094.
1-46
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The following configuration rules apply to flows and bridge ports:
1. A bridge port can terminate only one flow (EVC) classified as unaware (i.e.,
which does not discriminate Ethernet traffic in accordance with customer’s
and service provider’s VLANs).
2. When a bridge port is mapped to more than one EVC, the bridge port can
terminate several EVCs with specific VLAN IDs, but only one EVC classified as
unaware.
3. A bridge port can terminate any number of EVCs with specific VLAN IDs
(aware mode), up to the maximum supported per system.
4. It is not possible to configure E-line flows between Ethernet ports on the
same I/O module.
5. For E-line flows, the following VLAN assignment rules apply:
1. The bridge ports terminating an EVC (flow) must use the same VLAN
mode (either unaware or aware).
2. When using the aware mode, the same VLAN IDs must be configured at
both bridge ports. For example, this means that flows between two GbE
bridge ports must use the same SP-VLAN ID.
OAM Support
To enable personnel to identify problems in metropolitan Ethernet networks, it is
necessary to check connectivity at Layer 2 for each traffic-carrying link. For this
purpose, the standards define a link operations and maintenance (OAM) protocol.
The link OAM protocol uses special OAM protocol data units (PDUs) to check
connectivity between each bridge port and the attached equipment. The protocol
can be enabled on physical Ethernet ports, and on bundles carrying Ethernet
traffic over the TDM network: to be effective, the protocol must be enabled at
both ends of a link. For bundles, only one end can initiate the exchange of OAM
PDUs (the active endpoint), and the other (passive) endpoint only reacts to the
OAM PDUs sent by the active endpoint.
Timing Subsystem
Megaplex-4100 timing subsystem is a fully redundant system, i.e., each CL
module has its own timing subsystem, and can supply all the clock signals
required by the system via the chassis timing bus. However, at each time, only
one CL module (the active module) actually drives the timing bus, while the other
(standby) module is disconnected from the bus, but continuously monitors the
state of the main module timing subsystem. In case a problem is detected in the
active timing subsystem, the standby subsystem hitlessly takes over.
Figure 1-25 shows the functional block diagram of the timing subsystems for a
Megaplex-4100 equipped with SDH/SONET subsystems, and the connections to
the chassis timing bus.
Megaplex-4100 Ver. 2.0
Functional Description
1-47
Chapter 1 Introduction
Installation and Operation Manual
CL-A
Main
Receive Clocks
from
I/O Channels
Fallback
Timing
Bus
to all
Chassis
Cards
Main
PDH Receive
Clocks
From Local
SDH/SONET
Subsystem
Fallback
Main
SDH/SONET
(S-Subsystem)
Clock
System
Reference
Selector
Fallback
On-Line/Standby
Internal
Clock
Input
CLOCK
Output
Transmit (System)
System
Timing
Clock
(Nodal)
Bus
Clock
2.048 MHz
Interface
Generator
Station
Clock
Interface
CL-B
Main
Receive Clocks
from
I/O Channels
Fallback
Main
PDH Receive
Clocks
From Local
SDH/SONET
Subsystem
Fallback
Main
SDH/SONET
(S-Subsystem)
Clock
System
Reference
Selector
Fallback
Internal
Clock
Input
CLOCK
Output
Transmit (System)
System
Timing
Clock
(Nodal)
Bus
Clock
2.048 MHz
Interface
Generator
On-Line/Standby
Station
Clock
Interface
Figure 1-25. Functional Block Diagram of Megaplex-4100 Timing Subsystem (Unit with SDH/SONET
Subsystems)
System Timing Modes
Megaplex-4100 requires a system (nodal) clock source, and in addition it can use
separate, independent clocks for the SDH/SONET subsystem, and another for the
PDH subsystem. Therefore, for the SDH/SONET traffic a higher accuracy clock can
be provided; however, the PDH subsystem may also be synchronized to the
SDH/SONET timing.
1-48
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Appropriate configuration permits hierarchical dissemination of timing throughout
the communication systems, and ensure use of reliable timing sources even in
case of transmission faults or equipment malfunctions.
A timing source is defined by specifying the slot and the port to be used. The
source slot can be any I/O slot with a module having ports capable of recovering
a clock signal, or a CL slot.
For flexibility, you can select master timing sources and fallback timing sources: a
fallback source is automatically selected when none of the preconfigured master
sources is capable of providing a good timing reference.
The Megaplex-4100 timing subsystem can use the following types of reference
sources:
•
Internal Megaplex-4100 oscillator
•
Clock signal derived from the receive clock of a specified user port, internal
DS1 port or pseudowire (Rx timing mode)
•
S-subsystem clock signal, provided by the timing subsystem of the
SDH/SONET subsystems located CL.1/155 and CL.1/155GbE modules.
•
Station clock, a special case of Rx timing, which uses an external clock signal
supplied to the CL module CLOCK connector
Table 1-2 lists the reference clock sources that can be configured, together with
the types of Megaplex-4100 modules that can provide a timing reference signal.
For each module, the table also lists the type of ports, and when applicable – the
operating mode that must be selected for a port to be able of providing a timing
reference signal.
Table 1-2. Clock Reference Sources
Source Type
Module Type
Selectable Ports
Specific Operating Mode
Internal
Not applicable
Not applicable
Not applicable
Station (external)
CL
Station clock
Not applicable
M8E1, M8T1
External T1 or E1 ports
Not applicable
M8SL
External SHDSL ports
STU-R mode
MPW-1
Pseudowire ID
Not for HDLCoPSN
pseudowires
RX Clock from
Local User Port
Megaplex-4100 Ver. 2.0
OP-108C/OP-106C Internal DS1 ports
Not applicable
HS-6N, HS-12N
External ports
DTE timing
HS-U-6, HS-U-12
External ports
NT mode
HS-S
External ports
TE mode
HS-703
External ports
Not applicable
LS-6N, LS-12
External ports
DTE timing mode, provided the
channel data rate is a multiple
of 8 kbps
Functional Description
1-49
Chapter 1 Introduction
Installation and Operation Manual
Source Type
Module Type
Selectable Ports
Specific Operating Mode
RX Clock from
Remote User Port
CL.1/155,
CL.1/155GbE
Internal T1 or E1 PDH
ports
Not applicable
Line (STM-1/OC-3) Signal from
SDH/SONET Subsystem
CL.1/155,
CL.1/155GbE
Link port
Not applicable
Internal Timing Mode
As listed in the Technical Specifications, the internal oscillator quality depends on
the presence of a SDH/SONET subsystem. When an SDH/SONET subsystem is
installed (CL.1/155 and CL.1/155GbE models), a higher quality internal oscillator is
used to provide a reference clock with characteristics suitable for SDH/SONET
equipment. Nevertheless, in most applications, the internal Megaplex-4100
oscillator is used mainly for maintenance purposes, because usually an external
clock source is used.
The internal oscillator is also used as a last recourse fallback source: it is
automatically selected when no master, nor fallback source is capable of
providing a good timing reference. Therefore, when you select the internal
oscillator, no fallback source can be selected.
Rx Timing Mode
In the Rx timing mode, the reference signal is derived from the receive (RX) clock
of a specified user port:
•
Megaplex-4100 always permits locking the system (nodal) timing to a local
user (that is, a user directly connected to a port of an I/O module installed in
the chassis) from which a stable clock signal can be obtained. See Table 1-2.
•
Megaplex-4100 units equipped with CL.1/155 or CL.1/155GbE modules also
permit locking the nodal timing to a remote user, that is, a user connected to
an internal (virtual) PDH port of the local Megaplex-4100 via the SDH/SONET
network.
Two lists of timing sources can be defined, one including master sources and the
other including fallback sources. Each list can include up to 10 different sources.
Each source port is assigned an index number in its list, which specifies its priority
relative to the other sources in the same list. The master sources have priority
over the fallback sources.
The algorithm that selects the Megaplex-4100 timing reference source is based
on these user-defined priorities, and works to automatically select the
operational port with the highest priority as the nodal timing reference. The
selection criteria are as follows:
1. Normally, Megaplex-4100 selects the operational port with the highest
available priority from the list of master sources.
2. If the currently-selected port can no longer provide a clock signal (for
example, because of loss of signal, malfunction, module replacement, etc.),
Megaplex-4100 selects the master source with the next highest priority.
3. If no master source is available, the operational fallback port with the highest
priority is selected.
1-50
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
The switching is revertive: whenever a timing source with a higher priority
than the current source becomes available, it is automatically selected.
4. If no operational port can be found in both the master and fallback lists, the
Megaplex-4100 switches to the holdover mode. In this mode, the timing
subsystem selects the frequency used 26 msec before the fault condition
that caused the switching to the fallback mode (this is assumed to be a safe
selection, at which the subsystem operated normally at the correct
frequency). This frequency is maintained until one of the user-specified
sources can again be selected as reference, in accordance with the criteria
listed above. If a long time expires without any of the user-specified clock
sources returning to normal, Megaplex-4100 switches to the internal
oscillator.
S-Subsystem Timing Mode
In the S-subsystem timing mode, Megaplex-4100 uses the clock supplied by the
SDH/SONET timing subsystem (see details in the SDH/SONET Timing Subsystem
section starting on page 1-34).
The interaction between the system (nodal) timing generator, and the
SDH/SONET timing generator, is shown in Figure 1-26.
Local SDH/SONET Timing Subsystem
(CL.1/155, CL.1/155GbE Only)
Link Receive
Clocks
Internal Clock
SDH/SONET
Subsystem
Timing
Generator
SDH/SONET
(S-Subsystem)
Clock
System
(Nodal)
Timing
Generator
System Clock
(2048 kHz)
PDH
Receive
Clocks
Receive Reference
Clocks from
I/O Channels
Input
Output
CLOCK
Internal Clock
System Timing Subsystem
(All CL Versions)
Figure 1-26. Interaction between System (Nodal) Timing Generator and
SDH/SONET Timing Generator
Megaplex-4100 Ver. 2.0
Functional Description
1-51
Chapter 1 Introduction
Installation and Operation Manual
The SDH/SONET timing subsystem can be configured to use as reference source
one of the following:
Note
•
A recovered receive clock signal of a local SDH/SONET link
•
The internal clock
•
The system (nodal) clock. The system clock itself may be locked to the station
clock (see Station Timing section below).
When the system (nodal) clock must be locked to the S-subsystem timing, never
select the system clock as reference for the SDH/SONET timing generator, or an
unstable clock will result.
Station Timing
In the station timing mode, the Megaplex-4100 system (nodal) timing is
synchronized to an external clock signal, supplied to the dedicated station clock
interface located on each CL module. This signal is usually provided by a
highly-accurate master clock source, which is often available in communication
facilities (for example, a signal provided by a GPS-based timing source, an
independent primary clock source, clock signals provided by an SDH/SONET ADM, or
other suitable clock source). The clock signal frequency is user-selectable:
2.048 MHz, 2048 Mbps, or 1.544 Mbps.
When the SDH/SONET subsystem timing uses automatic source selection based
on SSM (see SDH/SONET Timing Subsystem section on page 1-34), it is possible
to include the station clock in the automatic selection scheme. For this purpose,
the user can enable the reading of SSM messages received within the station
clock signal stream (this capability is available only for the 2.048 Mbps and
1.544 Mbps options). For E1 ports, this requires to specify the national bit (one
of the Sa4 to Sa8 bits in timeslot 0) that carries the SSM message; for T1 ports, the
SSM message is carried by the FDL.
Each CL module can be connected to a separate station clock source, and
therefore each module can provide a separate reference signal. Therefore, when
both CL modules are connected to station clock sources, one can serve as master
source, and the other as fallback source.
The station clock interface has jumper-selectable interfaces:
•
ITU-T Rec. G.703 interface. The clock interface (balanced/unbalanced) and
sensitivity (long or short range) are also user-selectable
•
RS-422 interface for squarewave signals, which is the recommended interface
when timing quality is critical. Note however that this interface is suitable for
short cable runs, interconnecting equipment units located in close proximity.
The station clock interface also provides an output clock signal, for chaining
applications (see Application Considerations for Station Timing section on next
page). The source of the output clock is selectable:
1-52
•
The external clock signal applied to the station clock interface.
•
The external clock signal, after regeneration and filtering by a jitter
attenuator
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
•
Chapter 1 Introduction
The Megaplex-4100 system (nodal) clock. In this case, only a 2.048 Mbps
signal can be provided (the frequency of the system clock is always
2.048 MHz).
The SSM message can be provided only by CL models with an SDH/SONET
subsystem, and is determined as follows:
ƒ
When using the internal clock as the system timing reference, the SSM
message is SEC (SDH) or SMC (SONET).
ƒ
When the system timing is derived from the SDH/SONET subsystem
timing, the SSM message is derived from the SSM received from the
SDH/SONET link that serves as the timing reference.
Application Considerations for Station Timing
The structure of the external clock interface provides a convenient way to
distribute clock signals to several equipment units installed in close proximity,
e.g., in the same equipment rack.
Typically, the external clock interface connectors can be simply connected in a
daisy-chain configuration, as shown in Figure 1-27. In this application, the clock
source is connected to the external clock input in the station clock interface, and
serves as the system (nodal) timing reference. The station output clock is
configured to use the system timing as reference. The clock signal appearing at
the external clock output is connected to the external clock input of the next
Megaplex-4100, and so on.
To protect the other equipment, the station clock interface has a bypass relay
that connects directly the input line to the output when the Megaplex-4100 is
not powered.
To minimize waveform degradation, it is recommended to use the RS-422
squarewave interface, and use high-quality shielded cables, as short as practical.
Note that only the first Megaplex-4100 unit receives the reference signal: the
other units receive the clock signal from the Megaplex-4100 nodal timing
subsystem, whose characteristics depend on the specific CL module model.
Station Clock Source
(GPS-Based Timing Source,
SDH/SONET ADM, etc.)
CLOCK
CLOCK
CLOCK
CLOCK
Megaplex-4100
Figure 1-27. Clock Distribution Using the Megaplex-4100 Station Clock Interface
Another application for the station timing mode is to enable locking the timing of
an SDH/SONET ring network to a master clock, while ensuring that at any time
the ring timing uses the best quality clock available. This is achieved by using
automatic source selection based on SSM (see SDH/SONET Timing Subsystem
section on page 1-34). A typical application topology is illustrated in Figure 1-28.
In the topology of Figure 1-28, the timing references are configured as follows:
•
Megaplex-4100 Ver. 2.0
System timing reference: for all the Megaplex-4100 units, except Unit A, the
system timing reference is configured as S-subsystem, with automatic SSM--
Functional Description
1-53
Chapter 1 Introduction
Installation and Operation Manual
based selection. Unit A is configured to use the station clock as its system
timing reference (with SSM reception enabled for the station clock interfaces)
•
SDH/SONET subsystem timing reference: for all the units, except Unit A, is
configured as Rx timing, using an SDH/SONET link as reference. To provide a
preferred timing flow direction within the ring, the master and the fallback
timing sources are selected in accordance with the normal payload transport
direction of the ring. Unit A is configured to use the system (nodal) clock as
reference.
Assuming that the station clock supplied to Unit A has superior timing quality, it is
selected as source and determines the timing quality of its SDH/SONET links. The
other units read the received SSM and select an SDH/SONET link as timing
reference. The resulting timing flow is illustrated in Figure 1-28.
If one of the links in the ring fails, the ring heals itself by changing the signal flow
direction. As a result, the timing reference of the links may change, but it remains
locked to the station clock supplied to Unit A.
System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock
Master: Link 2
Fallback: Link 1
System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock
Master: Link 2
Fallback: Link 1
B
System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock
Master: Link 2
Fallback: Link 1
D
C
Link 1
Link 2
Link 2
Link 1
Link 2
Link 1
Link 1
Link 2
SDH/SONET Ring
Link 2
Link 1
A
Link 1
Link 2
F
System Timing: Station
SDH/SONET Tx Clock: System
Station
Clock Source
System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock
Master: Link 2
Fallback: Link 1
E
System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock
Master: Link 2
Fallback: Link 1
Legend
STM-1/OC-3 Subsystem
CL Module
Normal Timing Flow
Main Path
Alternative Path
Figure 1-28. SDH/SONET Ring Using Station-Clock Derived Timing (Timing Flow in Normal Operation)
To enhance resiliency in rings containing many units, it is possible to configure an
additional unit, located midway along the ring (say Unit D in Figure 1-28), to also
1-54
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
use station timing as its second priority source, even if the available timing
quality of the station signal that can be supplied to Unit D is not equal to that of
Unit A. The SSM-based selection mechanism will always prefer the better quality
timing from Unit A as long as it is available, and will switch to the station clock
supplied to Unit D when Unit A timing source fails, or its quality is degraded.
Data Channel Timing Modes
Data channels operating in the asynchronous mode always use the nodal clock as
their rate generator clock.
For data channels operating in the synchronous mode, the user can select the
channel timing mode in accordance with the application requirements. The
various channel timing modes are described below.
DCE Timing Mode
In the DCE mode, the Megaplex-4100 data channel provides transmit and receive
clocks for the equipment connected to the data channel, as shown in Figure 1-29.
The clock signals are derived from the nodal clock.
This mode is usually required for connection to DTE equipment.
Asynchronous data channels also use the DCE timing mode for their internal timing.
Megaplex-4100
DTE
XMIT Clock
RCV Clock
Figure 1-29. DCE Channel Timing Mode
External DCE Timing Mode
In the external DCE mode, the Megaplex-4100 data channel sends data
accompanied by a receive clock to the connected equipment, and accepts
transmit data from the equipment according to the equipment clock. The flow of
timing signals in the external DCE mode is shown in Figure 1-30.
Megaplex-4100
DCE
XMIT Clock
RCV Clock
Tail-End
Circuit
Figure 1-30. External DCE Timing Mode
The external DCE mode requires the equipment connected to the corresponding
channel to use loopback timing, because its transmit timing must be locked to the
Megaplex-4100 nodal timing.
The external DCE timing mode is often required for “tail end” connections, where a
modem (DCE) is connected to a data channel. In this case, the remote terminal
Megaplex-4100 Ver. 2.0
Functional Description
1-55
Chapter 1 Introduction
Installation and Operation Manual
(DTE) connected to the remote end of the modem link must use loopback timing,
thereby ensuring that the rate of data applied to the Megaplex-4100 channel
transmit input is equal to the receive rate.
DTE Timing Mode
In the DTE mode, the Megaplex-4100 data channel transmits and receives data
according to the clock supplied by the connected equipment. To support this
mode, the Megaplex-4100 unit must use external timing, with the channel
operating in the DTE mode being selected as the timing reference source.
The flow of timing signals in a DTE timing application is shown in Figure 1-31.
The DTE timing mode is required in applications such as data channels connected
to a digital data switch or to a data carrier network: since the data switch
provides the timing reference for the whole network, is must be able to provide
clock signals for both the Megaplex-4100 and the equipment connected to it.
When operating channels in the DTE timing mode, one of the data channels can
be selected as the external source for the entire system timing. To compensate
for jitter and short-term instabilities, FIFO buffers are used at the input of each
channel. FIFO length is user-selectable, provided the channel is not used as an
external clock source.
Megaplex-4100
DTE
XMIT Clock
XMIT Clock
Digital Data
Network
RCV Clock
RCV Clock
Master Clock
Figure 1-31. DTE Timing Mode
ISDN Channel Timing Modes
When a Megaplex-4100 link is used to connect remote ISDN equipment to the
ISDN network, it is necessary to ensure that the timing of the remote equipment
is locked to the network timing. Therefore, the operating mode of the
Megaplex-4100 units must enable dissemination of the ISDN network timing
through the Megaplex-4100 link. The various timing modes supported by ISDN
channels are described below.
In all the modes described below, the receive timing of a port is derived from the
incoming ISDN signal, and the transmit timing is derived from the Megaplex-4100
nodal clock.
1-56
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Timing Modes for ISDN Channels with “S” Interface
ISDN channels with “S” interfaces support two timing modes, TE and NT. The TE
mode is used to connect an ISDN channel with “S” interface to the network, and
the NT mode is used at the remote end.
Figure 1-32 shows the flow of timing signals in a typical application, and the
relationship between the two timing modes.
Terminal
Equipment
NT
Transmit Timing
Locked to
ISDN Channel
ISDN
Switch
~
Megaplex-4100
Loopback
Timing
~
Megaplex-4100
HS-S Module
(TE Mode)
HS-S Module
(NT Mode)
Figure 1-32. Timing Modes for ISDN Channels with “S” Interface
The characteristics of the two timing modes are described below:
•
TE Mode. In the TE mode, the receive clock of one of the ISDN channels,
which is recovered from the line signal received from the network termination
unit to which the channel is connected, must be selected as reference for the
Megaplex-4100 nodal timing.
As a result, the nodal timing is locked to the network timing, and can be
distributed to the remote Megaplex-4100 unit. This also ensures that the
channel transmit timing is also locked to the network timing.
•
Note
NT Mode. In the NT mode, the Megaplex-4100 nodal timing determines the
timing of the data transmitted to the user's terminal equipment connected to
the “S” interfaces. The receive timing is recovered from the line signal received
from the user's terminal equipment. Therefore, to ensure that the same timing
is used on the receive direction (from the user's terminal equipment to the “S”
interface), the user's terminal equipment must operate with loopback timing.
When the ISDN network timing is available at the two Megaplex-4100 sites from
other sources, for example, from clock distribution units, it is also possible to use
the station clock mode at both ends of the link, instead of the timing modes
described above.
Timing Modes for ISDN Channels with “U” Interface
In general, ISDN channels with “U” interfaces support two timing modes: LT and
NT. When the channels are used to connect remote equipment to a network, the
channels must operate in the /I mode (see description of this mode in the
HS-U-6, HS-U-12 Installation and Operation Manual). The NT-I mode is used to
connect an ISDN channel to the network, and the LT mode is used at the remote
end.
Megaplex-4100 Ver. 2.0
Functional Description
1-57
Chapter 1 Introduction
Installation and Operation Manual
Figure 1-33 shows the flow of timing signals in a typical application of ISDN
channels with “U” interfaces.
Terminal
Equipment
LT
Transmit Timing
Locked to
ISDN Channel
ISDN
Switch
~
Megaplex-4100
HS-U-6/12 Module
(NT-I Mode)
Loopback
Timing
~
Megaplex-4100
HS-U-6/12 Module
(LT-I Mode)
Figure 1-33. Timing Modes for ISDN Channels with “U” Interface
•
NT-I Mode: In the NT-I mode, the receive clock of one of the ISDN channels,
which is recovered from the line signal received from the line termination unit
to which the channel is connected, must be selected as reference for the
Megaplex-4100 nodal timing. As a result, the nodal timing is locked to the
network timing, and can be distributed to the remote Megaplex-4100 unit.
This also ensures that the channel transmit timing is also locked to the
network timing.
•
LT-I Mode. In the LT-I mode, the Megaplex-4100 nodal timing determines the
timing of the data transmitted to the user's terminal equipment connected to
the “U” interfaces. The receive timing is recovered from the line signal received
from the user's terminal equipment.
Therefore, to ensure that the same timing is used on the receive direction
(from the user's terminal equipment to the “U” interface), the user's terminal
equipment must operate with loopback timing.
Note
When the ISDN network timing is available at the two Megaplex-4100 sites from
other sources, for example, from clock distribution units, it is also possible to use
the station clock mode at both ends of the link, instead of the modes described
above.
Redundancy Options
Megaplex-4100 supports redundancy for the connections to the SDH/SONET
network and to the PSN, for virtually concatenated groups, and also for the E1
and T1 ports.
The following sections present the redundancy options for each type of
connections.
CL Module Redundancy
Only one CL module is necessary per chassis, however the chassis has two slots
dedicated to this type of module. The second slot can be used to install a
redundant CL module of the same type, thereby providing a hot-standby
capability for the Megaplex-4100 system control functions.
1-58
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
When a second CL module is installed, the two modules operate as a
master/slave pair; one module is the active (online) module, and the other is
off-line and serves as a hot standby.
Only the online CL module communicates with the management station/terminal
and actively manages the Megaplex-4100 system. The off-line CL module is
automatically updated by the online module with all the configuration and status
data, and therefore the off-line can take over at any time without disrupting
system operation. The switch-over to the off-line module occurs automatically
upon detection of failure in the online module, or upon removing the online
module from the chassis.
The slave CL module communicates only with the online module. Moreover, the
transmit line in the slave supervisory port connector is disabled, to enable
physical connection in parallel (e.g., by means of a Y cable) to a supervision
terminal or to a modem, and the CL Ethernet port is also disabled, and therefore
the Ethernet connectors of the two CL modules can be simultaneously connected
to the same LAN.
Note
The SDH/SONET and/or Ethernet traffic subsystems located on the CL modules
operate independently of the management subsystems, and therefore the
redundancy switching of the management subsystems does not affect
SDH/SONET and/or Ethernet traffic.
Redundancy for SDH/SONET Network Connections (CL.1/155,
CL.1/155GbE)
SDH/SONET Link Redundancy Options
Megaplex-4100 supports 1+1 unidirectional (line) protection with APS per ITU-T
Rec. G.842 for the links to the SDH/SONET network.
Redundancy is activated by configuring APS groups using 1+1 unidirectional
protection. The supported APS configurations are as follows:
•
When one CL module is installed in the chassis: one APS group including the
two ports of the CL module. In this case, the total bandwidth of the link to
the SDH/SONET network is one STM-1/OC-3.
•
When two CL modules are installed in the chassis: two APS groups. In this
case, the total bandwidth of the links to the SDH/SONET network is two
STM-1/OC-3, in accordance with the following options:
ƒ
APS group including the LINK 1 ports of the two CL modules, and another
group including the LINK 2 ports.
ƒ
APS group including the two ports of one CL modules, and another group
including the two ports of the other.
Note that when redundancy is used, only one mapping is required for each link to
the network, because the ports must have identical configurations for line
redundancy to work. Therefore, the mapping can be configured only on the
primary port of an APS group (actually, the secondary port cannot be included in
an APS group before its mapping is deleted).
Megaplex-4100 Ver. 2.0
Functional Description
1-59
Chapter 1 Introduction
Installation and Operation Manual
Operation of 1+1 Unidirectional Protection Function
Figure 1-34 illustrates the operation of the 1+1 unidirectional protection function
on a Megaplex-4100 using a single CL module.
1+1 unidirectional protection works as follows:
•
Both the working and protection ports of an APS group simultaneously
transmit the same data toward the remote end, via two different paths.
•
At each side, the signal received by each port of an APS group is evaluated in
accordance with the alarm weighting criteria specified in ITU-T Rec. G.707, to
determine the best signal (the signal with the lowest total alarm weight). The
results of this evaluation are used to select the receive signal actually
connected to the corresponding telecom bus (these tasks are performed by a
processing function identified as an internal protection switch). Figure 1-34.A
shows the normal operating conditions, under which the signal received
through the working port is selected for processing.
•
When a fault occurs, protection switching takes place. Figure 1-34.B shows the
change in case the working signal path ending at the LINK 1 port of the West
Megaplex-4100 fails: the received signal is now taken from LINK 2. Note that
the same action would be taken in response to any problem along this path
(fault at location A, fault at location B, transmit failure at the East LINK 1
port, or receive failure at the West LINK 1 port).
Internal
Protection
Switch
Internal
Protection
Switch
Megaplex-4100
Megaplex-4100
LINK 1
SDH/SONET
Network
LINK 2
LINK 1
LINK 2
CL.1/GbE or
CL.1/155GbE
Module
CL.1/GbE or
CL.1/155GbE
Module
Legend
Working link
Protection link
A. Normal Operation
1-60
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Internal
Protection
Switch
Internal
Protection
Switch
B
Megaplex-4100
A
LINK 1
LINK 2
SDH/SONET
Network
Megaplex-4100
LINK 1
LINK 2
CL.1/GbE or
CL.1/155GbE
Module
CL.1/GbE or
CL.1/155GbE
Module
Legend
Working link
Protection link
B. Operation after Protection Switching due to Fault in Path to one Port
Figure 1-34. Operation of 1+1 Unidirectional Protection Function
The basic 1+1 unidirectional protection configuration shown in Figure 1-34 can be
extended to a dual-link configuration, by installing two CL modules at each side.
In this case, protection switching replaces the working port with the
corresponding protection port of the APS group (in the example given above, a
fault in the path ending at LINK 1 of one CL module would switch the traffic to
LINK 1 of the second CL module). In the same way, a hardware failure in one CL,
or a break in the optical cable connecting to an CL, would switch the traffic to the
other module.
With 1+1 unidirectional protection, each side independently selects the best
signal (in Figure 1-34.B, no change occurred at the East Megaplex-4100), and
therefore no protocol is needed to coordinate protection switching with the
remote side. For example, in Figure 1-34.B, the East side would also switch to the
protection port (LINK 2) if the West side problem is a break in both fibers
connected to the West LINK 1 port.
The alarm criteria taken into consideration for protection switching are as follows
(listed in decreasing weight order):
•
The module with the other port in the APS group is not installed.
•
Forced-flip command.
•
Critical alarm. A critical alarm is caused by the detection of one or more of
the following fault conditions: loss of SDH/SONET line signal, reception of AIS
signal on the line, loss of SDH/SONET frame, or clock failure.
•
Major alarm. A major alarm is caused by EED (excessive error degradation).
The EED threshold can be selected by the user.
•
Minor alarm. A minor alarm is caused by an SD (signal degraded) condition,
where the threshold can be selected by the user. However, the user can
configure APS parameters to ignore the SD criterion.
•
Revert request (only when the revertive recovery mode is selected).
Megaplex-4100 Ver. 2.0
Functional Description
1-61
Chapter 1 Introduction
Installation and Operation Manual
The working port always carries the traffic, as long as its total alarm weight does
not exceed that of the protection. The user can however force switching (flipping)
to the other port by a manual flip command: such command is always executed,
except when the other port in the APS group by a manual command, except when
it is located on a module not installed in the chassis.
The two ports in an APS group can be assigned priorities: Megaplex-4100 will
generate alarm messages to notify managers (supervision terminal, Telnet hosts,
management stations, etc.) that protection switching from the high priority port to
the low priority port, or vice versa, occurred.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
•
Non-revertive mode – the CL module will not automatically flip back after the
failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
However, as explained above, the user can always initiate flipping back by a
manual flip command.
•
Revertive mode – the CL module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
To prevent switching under marginal conditions, the user can specify a
restoration time, which is the minimum interval before flipping back to the
original port. During the restoration time, alarms with the same weight, or with
lower weights, are ignored. As a result, the module starts evaluating the criteria
for protection switching (flipping) only after the restoration time expires, thereby
ensuring that another flip cannot occur before the specified time expires.
However, if an alarm with a weight exceeding that of the alarm which caused
flipping appears, immediate flipping will take place, even if the restoration time
has not yet expired.
Path Protection for SDH/SONET Payload (CL.1/155, CL.1/155GbE)
Path (trail) protection is available for user-specified payload units (VC-12 and
VC-3 for SDH links, or VT1.5 and STS-1 for SONET links). Figure 1-35 shows the
path protection topology.
When path protection is enabled, the protected payload unit is assigned
bandwidth on both network links:
•
The same payload is transmitted on both links.
•
The receive interfaces of the two links continuously evaluate the received
signals. As long as the primary path operates satisfactorily, its signal is
selected for processing. When the primary path signal fails, or is degraded,
the receive side rapidly selects the other signal (shown in dashed lines in
Figure 1-35) for processing.
By provisioning appropriate alternative paths through the network, it is possible
to ensure that in case of a fault anywhere along the active path the traffic is
automatically switched to the standby path.
The protected payload positions can be manually configured on each link, and
therefore may be different.
1-62
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Internal Path
Protection
Switch
Internal Path
Protection
Switch
Megaplex-4100
Megaplex-4100
LINK 1
SDH/SONET
Network
LINK 1
LINK 2
LINK 2
CL.1/GbE or
CL.1/155GbE
Module
CL.1/GbE or
CL.1/155GbE
Module
Figure 1-35. Operation of Path Protection
Redundancy for PSN Connections (CL.1/GbE, CL.1/155GbE)
Redundancy can be enabled for GbE ports of CL.1/GbE or CL.1/155GbE modules,
to provide protection for the connection to the PSN. Any pair of GbE ports can be
configured to form a redundancy pair, and therefore it is possible to protect
against hardware failures, as well as against transmission path failures.
When redundancy is enabled, the pair of GbE ports operate as a single PSN
interface. The protection mode is 1+1 redundancy, The recovery mode (revertive
or non-revertive) can be selected in accordance with the application
requirements. In the revertive mode, it is also possible to specify a wait-torestore interval, which delays the return to the original port after it immediately
returns to normal.
Two topologies can be used for the connections to the GbE ports of a
redundancy pair (for simplicity, only ports located on the same CL module are
shown in Figure 1-36 and Figure 1-37):
•
Connection of both GbE ports to the same switch/router (Figure 1-36).
Megaplex-4100
Megaplex-4100
PSN
GbE1
GbE1
GbE2
GbE2
CL.1/GbE or
CL.1/155GbE
Module
CL.1/GbE or
CL.1/155GbE
Module
Figure 1-36. Connection of Redundant GbE Ports to Same Switch/Router
•
Megaplex-4100 Ver. 2.0
Connection of the GbE ports to different switch/routers, as shown in
Figure 1-37. The main advantage of this topology is its higher availability,
because each port can be routed along a different path through the network.
Functional Description
1-63
Chapter 1 Introduction
Installation and Operation Manual
Megaplex-4100
Megaplex-4100
GbE1
GbE1
PSN
CL.1/GbE or
CL.1/155GbE
Module
GbE2
GbE2
CL.1/GbE or
CL.1/155GbE
Module
Legend
On-line link
Off-line link
Figure 1-37. Connection of Redundant GbE Ports to Different Switches/Routers
With 1+1 redundancy, at any time only one of the ports is actively carrying the
GbE traffic, and the other port serves as the backup port. The redundancy
algorithm uses loss of GbE signal to detect line failure.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
•
Non-revertive mode – the GbE module will not automatically flip back after
the failed port returns to normal operation, but only when the currently used
port fails, or after a manual flip command.
•
Revertive mode – the GbE module will flip back to the original port after it
returns to normal operation.
The equipment connected to the GbE ports must use compatible switching
criteria for redundancy to be available:
•
For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface (in the
topology of Figure 1-37, this will be an interface of a different router). After
learning again the MAC interface, connectivity is automatically restored.
•
For networks using Layer 3 routing: the router must support some form of
redundancy, and the network must be able to accept the same IP subnet
from different interfaces.
Virtually Concatenated Group Redundancy Options
Megaplex-4100 equipped with CL.1/155GE modules support 1+1 redundancy for
virtually concatenated groups, thereby protecting against transmission failures on
the SDH/SONET links.
Any pair of virtually concatenated groups can be configured as a redundancy pair,
even if they have different capacity, or even use different encapsulation
methods, and/or parameters. Only the recovery mode (non-revertive or
revertive), and the restoration delay in the revertive mode, must be the same.
To use virtually concatenated group redundancy, both the primary (protected)
virtually concatenated group and the secondary (protection) virtually
concatenated group must be assigned bandwidth (mapped) on the desired links.
By provisioning appropriate trails through the network, it is possible to ensure
1-64
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
that in case of a fault anywhere along the primary group path, its traffic is
automatically switched to the standby group and will follow a different path
through the SDH/SONET network, thereby ensuring that the payload can still be
transported end-to-end.
Depending on the desired protection level, the redundancy partners can be
mapped to the same link, to different links on the same CL module, or to a link
on the other (adjacent) CL module.
The virtually concatenated group 1+1 redundancy mode operates as follows:
•
Note
During normal operation, the payload is directed to the primary virtually
concatenated group, and transmitted only over the bandwidth assigned to
this group.
Only the primary virtually concatenated group can be included in a flow (the
secondary virtually concatenated group will not appear in the list of available
bridge ports).
•
In case an alarm condition is detected on the primary group, the payload is
directed to the secondary group, and transmitted over its bandwidth. The
alarm criteria taken into consideration for redundancy switching include
physical port failures and virtually concatenated group failures (when using
LCAS, this also includes a decrease in available bandwidth below the specified
minimum).
The recovery mode after a redundancy switching can be selected in accordance
with the application requirements:
•
Non-revertive mode – the traffic will not be automatically redirected back
after a failed group returns to normal operation, but only when the currently
used group fails.
•
Revertive mode – the traffic will be automatically redirected back to the
original group when it returns to normal operation.
To prevent switching under marginal conditions, the user can specify a
restoration time, which is the minimum interval before flipping back to the
original port. However, if a more severe alarm appears, immediate flipping will
take place, even if the restoration time has not yet expired.
Redundancy for E1 and T1 Links
One of the simplest methods to protect against link and hardware failure is to
use the link redundancy function.
Redundancy provides two main advantages:
•
Automatically restores service within a short time without user’s intervention
•
In case of technical failure, allows service to continue while technical staff
finds the source of the failure and corrects it.
Moreover, when redundancy is used, planned maintenance for example, updating
software versions, or installing modules with enhanced capabilities, can also be
performed without disrupting service, provided a few precautions are taken:
•
Megaplex-4100 Ver. 2.0
To minimize disruptions to traffic, do not simply pull module out but first
check that the module does not serve as the master. If one of the module
Functional Description
1-65
Chapter 1 Introduction
Installation and Operation Manual
ports serves as the master, first force redundancy flipping by means of a
RESET command.
•
After removing a module, wait at least 10 seconds before inserting a module
in the same slot.
Three different redundancy approaches are supported: dual-cable redundancy,
Y-cable redundancy and E1/T1 ring redundancy.
Dual Cable (Parallel TX) Redundancy
For this type of redundancy, two ports of the same type (either E1 or T1) are
connected to the remote unit via two parallel links. By defining these two links as
a redundant pair, it is possible to ensure that traffic carrying capacity is available
even if one of the links fails.
Figure 1-38 shows a typical system configuration using dual-cable redundancy. The
user can select the module ports operating as a redundant pair. When operating
with dual cable redundancy, the redundant port is configured with basically the
same parameters as the primary port (there may be differences in parameters
related to the link physical configuration parameters). Both ports process as usual
the transmit and receive signals, but the receive output of the redundant port is
disconnected.
During normal operation, the operational state of the redundant port is
continuously monitored, to ensure that it is operating O.K. If the primary link
fails, the corresponding port is disconnected, and the redundant port takes over.
The switching time between main and backup ports is maximum 50 msec, and
therefore redundancy switching will ensure essentially uninterrupted service for
all the types of applications (in particular, it will not cause the disconnection of
voice calls).
Note
50 msec redundancy switching is not available on modules with SHDSL interfaces,
because of the long times needed to detect failure and put in service a standby
port (this is caused by the SHDSL link setup protocols specified by the
standards).
I/O Module with
E1 or T1 Ports
I/O Module with
E1 or T1 Ports
Primary (Active) Link
Redundant (Standby) Link
Megaplex-4100
Megaplex-4100
Figure 1-38. E1/T1 Link Redundancy Using Dual Cables
Y-Cable Redundancy
For Y-cable redundancy, two module ports with the same type of physical and
electrical interfaces are connected to the same communication link by a single Y
cable. For this type of redundancy to be effective, the two ports must be located
on different modules because it provides protection mainly for technical failures
in the module hardware. A typical configuration is shown in Figure 1-39.
1-66
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
When operating with a Y cable, the redundant module port must be configured
with the same parameters as the primary module port.
During normal operation, the transmit output of the redundant module is
electrically disconnected from the link. Nevertheless, its operational state is
continuously monitored, to ensure that it is operating O.K. If the primary module
fails, it is disconnected from the link and from the internal buses, and the
redundant module takes over.
I/O Module with
E1 or T1 Ports
I/O Module with
E1 or T1 Ports
Transmission Link
Megaplex-4100
Megaplex-4100
Figure 1-39. E1/T1 Link Redundancy Using Y-Cable
E1/T1 Ring Redundancy
The E1/T1 ring redundancy is a RAD proprietary topology suitable for
Megaplex-4100 equipment that provides higher availability for critical applications
at the E1 and T1 level, with fast protection switching time (the switching time for
E1/T1 ring redundancy is less than 50 msec).
Figure 1-40 illustrates this topology in Figure 1-41. The links comprising the ring
can include E1 and T1 physical links, as well as E1 links implemented over SHDSL.
The different types of links can be intermixed along the same ring, without
requiring any media converters or modems. For example, the ring paths
interconnecting Megaplex-4100 units A, B, and C of the E1 ring illustrated in
Figure 1-41 can run between physical E1 ports of M8E1 modules, and the ring
closing path (between Megaplex-4100 units D and A) may run over SHDSL, which
provides the additional E1 link. To support this option, one free M8SL port is
required in each of the Megaplex-4100 units D and A (in addition to the M8E1
modules which must be anyhow installed in these units to provide connectivity
between units A, B, and C).
MP-4100 B
MP-4100 A
MP-4100 C
Primary Ring
(E1, T1 or SHDSL)
Secondary Ring
(E1, T1 or SHDSL)
MP-4100 D
Figure 1-40. E1/T1 Ring Topology
Megaplex-4100 Ver. 2.0
Functional Description
1-67
Chapter 1 Introduction
Installation and Operation Manual
E1/T1 ring redundancy is based on the use of two transmission paths, each
requiring a single twisted pair: one pair, called the primary, is used instead of the
legacy transmit pair, and the other, called the secondary, is used instead of the
legacy receive pair. Therefore, E1/T1 ring redundancy can use the same cabling
infrastructure as regular point-to-point links, but provides several significant
advantages:
•
There is no single point of failure
•
Rapid switching time in case of failure (within 50 msec)
•
Uses the full bandwidth of the E1 or T1 link
•
Does not require additional hardware: actually, any daisy chain topology can
be converted to an E1/T1 ring topology by connecting two additional pairs
between the E1, T1 or SHDSL port on the Megaplex-4100 at the end of the
chain to the E1/T1/SHDSL port beginning the chain (on the first
Megaplex-4100)
•
Flexible solution:
•
ƒ
Supports any number of nodes along the ring
ƒ
Any Megaplex-4100 unit in the ring can connect to additional rings, and
allows timeslot cross-connect between the rings
Simple to configure: requires the same timeslot assignment as a chain
topology, except that at each node it is necessary to bypass timeslots that
are not used for local payload between the primary and secondary E1/T1
ports.
The E1/T1 ring redundancy topology can be efficiently implemented by any pair of
physical or internal (virtual) E1 or T1 ports, as available on M8E1, M8T1, M8SL,
etc. Any pair of ports, even ports located on different modules, can be configured
as a redundancy pair. To enable handshaking between Megaplex-4100 units in an
E1/T1 ring, it is necessary to use the RAD proprietary RIP protocol, with inband
management carried over a dedicated timeslot.
Figure 1-41 shows a typical application that uses the ring redundancy topology.
Primary Ring
Secondary Ring
TS 13 MNG
TS 1-3 Local (3 TS)
TS 4-12 Bypass
TS 13 MNG
TS 1-12 Local
Primary
Primary
RX
Port 2
TX
TX
Port 1
RX
Central
RX
Port 2
TX
TS 13
MNG
TS 4-6
Local (3 TS)
TS 1-3, 7-12 Bypass
Primary
TX
Port 1
RX
A
HS-6N
RX
Port 2
TX
TS 13
MNG
TS 7-9
Local (3 TS)
TS 1-6, 10-12 Bypass
Primary
TX
Port 1
RX
B
HS-6N
RX
Port 2
TX
TS 13
MNG
TS 10-12 Local (3 TS)
TS 1-9
Bypass
Primary
TX
Port 1
RX
C
HS-6N
RX
Port 2
TX
TX
Port 1
RX
D
HS-6N
A B C D
User's Equipment
User's Equipment
User's Equipment
User's Equipment
User's Equipment
Figure 1-41. E1/T1 Ring Redundancy – Signal Flow during Normal Operation
In each Megaplex-4100 unit on the ring, two E1 or T1 ports (identified as port 1
and port 2 in Figure 1-41) are defined as a redundancy pair. One port of each
unit (in this example, port 2) is configured as primary port: under normal
1-68
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
conditions, each Megaplex-4100 transmits data to the next node through the
primary port, and receives through the secondary port. Timeslots not connected
to local channels are bypassed.
The payload is handled as follows:
•
Primary ring: at each unit, timeslots used at the local unit are dropped from
the receive side of the secondary port, and added to the transmit side of the
primary port. Timeslots used by the other Megaplex-4100 units are bypassed
directly between these two ports.
•
Secondary ring: all the timeslots received by port 2 are bypassed to the
transmit side of port 1.
When one of the segments in the ring fails (see Figure 1-42), the CL modules of
the two Megaplex-4100 units adjacent to the failure point detect the loss of
signal and change the signal routing within the corresponding units. Therefore,
now each unit receives and transmits only through the synchronized port.
Timeslots previously bypassed between the ports are now transferred between
the receive and transmit sides of the active port by a connection similar to the
remote loopback, thereby preserving transmission path continuity.
Primary Ring
Secondary Ring
Primary
RX
Port 2
TX
TS 13
MNG
TS 4-6
Local
TS 1-3, 7-12 Remote Loop
TS 13 MNG
TS 1-3 Local
TS 4-12 Bypass
TS 13 MNG
TS 1-12 Local
Primary
TX
Port 1
RX
Port 2
TX
RX
Central
Primary
TX
Port 1
RX
A
HS-6N
Port 2
TX
Primary
TX
Port 1
RX
B
RX
Port 2
TX
TS 13
MNG
TS 10-12 Local
TS 1-9 Bypass
Primary
TX
Port 1
RX
C
RX
Port 2
TX
TX
Port 1
RX
D
HS-6N
HS-6N
HS-6N
HS-6N
User's Equipment
User's Equipment
User's Equipment
User's Equipment
A B C D
User's Equipment
RX
TS 13
MNG
TS 7-9
Local
TS 1-6, 10-12 Remote Loop
Figure 1-42. E1/T1 Ring Redundancy – Signal Flow after Segment Failure
Note that all the other Megaplex-4100 units do not change their operating
configuration: only the units that are connected to the failed segment take action
in response to the failure.
Notes
• To prevent unnecessary switching to the redundant path, do not activate
remote loopbacks, nor loopbacks on timeslots, on ports connected to the ring.
• When it is necessary to perform local bypassing (on the same module)
between another port to one of the ports participating in ring redundancy,
you can do that only for the primary port; for the redundancy port, you get an
error message.
Timing Considerations for E1/T1 Ring Redundancy Applications
When using ring redundancy, it is necessary to ensure that the same reference
timing can always be used at all the units on the ring.
•
Megaplex-4100 Ver. 2.0
Using an External Reference Signal. At sites where Megaplex-4100 equipment
is connected through ADMs to the SDH/SONET backbone (or has CL modules
Functional Description
1-69
Chapter 1 Introduction
Installation and Operation Manual
with SDH/SONET subsystems and is configured to use S-subsystem timing), or
at sites using a GPS-based timing reference, a common timing reference is
always available.
When this common timing reference is available at all the sites along the ring,
it is recommended to use this external signal as the nodal timing reference
for all the units on the ring.
The main advantage of this approach is that it is not necessary to change the
timing reference when redundancy switching takes place.
•
Using other Timing Reference. As an alternative, the equipment can be
configured so that the timing reference is distributed in a controlled way to
all the equipment units, for example, by locking the nodal timing to the clock
signal of a selected port (Rx timing mode). This requires:
ƒ
Selecting appropriate timing reference sources
ƒ
Configuring the main and fallback sources in a way that takes into
consideration the change in the direction of timing flow caused by
recovery from failure.
For example, in Figure 1-41 the timing flows clockwise through the whole ring
(the main timing source is port 1, and the fallback is port 2), whereas after
recovery from segment failure (Figure 1-42), in some parts of the ring the
direction of reference timing flow must be reversed. Figure 1-43 and
Figure 1-44 show the timing reference flow before and after recovery.
The timing state of the ring is carried by the periodic RIP update messages
(part of the RAD proprietary RIP protocol, which is mandatory for ring
redundancy to work). Typically, these update messages are sent every 30
seconds.
The ring redundancy protocol uses a special fault indication message (CLOCK
FAILURE IN THE RING) to notify other units in the ring that a fault event
occurred on the ring:
Note
1-70
ƒ
The reception of the NOT OK indication via a link configured as a master
timing source causes the receiving unit to switch from master to fallback
timing.
ƒ
A unit that must switch to fallback will not select as source a link from
which NOT OK indications are received.
ƒ
The NOT OK indication is ignored when a unit does not use a link as its
timing source.
The switching of the traffic to the secondary ring takes place as soon as a fault
occurs, without requiring any handshaking with other units.
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Port 1: Master
Port 2: Fallback
RX
Port 2
TX
TX
Port 1
RX
Port 2
TX
RX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
Clock
Reference
(Station)
Figure 1-43. E1/T1 Ring Redundancy Topology – Normal Timing Reference Flow
Port 1: Master
Port 2: Fallback
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
RING CLOCK FAILURE
Clock
Reference
(Station)
Figure 1-44. E1/T1 Ring Redundancy Topology – Timing Reference Flow after Segment Failure
Since the fault indication is carried by the periodic RIP update messages, it
takes time for the fault notification to propagate through the ring. During the
propagation time, frame slips may occur.
For long rings including a large number of units, it is possible to reduce the
propagation time by distributing the same timing reference in two directions
through the ring. Note however that this approach must be analyzed with
respect to the maximum accumulating jitter.
Figure 1-45 shows an implementation of this alternative arrangement: the
corporate ring uses the PBX as the timing reference for the whole ring. For
redundancy, the PBX provides the timing signal to two units, Megaplex-4100
1 and Megaplex-4100 6. The timing sources configured for each unit, as well
as the flow of the timing information during normal conditions, are both
indicated in the figure. Figure 1-45 also shows how the clock status
messages (OK for all the units) reach all the units in the ring.
Megaplex-4100 Ver. 2.0
Functional Description
1-71
Chapter 1 Introduction
Installation and Operation Manual
The recovery from faults is illustrated in Figure 1-46 and Figure 1-47:
ƒ
In case a fault occurs on the ring (Figure 1-46), Megaplex-4100 unit 3 can
no longer use its master timing. Therefore, the CLOCK FAILURE ON THE
RING alarm state is declared, and the following exchange of messages
takes place:
1. Megaplex-4100 unit 2 does not need to report any clock problem (it
only switches the traffic).
2. Megaplex-4100 3 loses the link signal to which its timing is locked,
and therefore NOT OK indications are sent by Megaplex-4100 3 to the
next unit it can reach, Megaplex-4100 4.
3. Since Megaplex-4100 4 master timing is also lost when
Megaplex-4100 3 cannot provide its reference, Megaplex-4100 4 also
sends NOT OK indications to the next unit, Megaplex-4100 5.
4. Megaplex-4100 5 has a stable timing reference, and therefore, it can
continue reporting OK to the other units. Therefore, the
counterclockwise propagation of the NOT OK state stops.
5. Since Megaplex-4100 5 reports OK to Megaplex-4100 4, the latter unit
can select its signal as reference (that is, it can switch to its can also
be used as reference.
6. Megaplex-4100 3 now switches to fallback, and uses the
Megaplex-4100 4 signal as reference.
At this stage, Megaplex-4100 3 and 4 units have both reacquired stable
timing by switching to their fallback sources. The resulting timing flow is
also illustrated in Figure 1-46.
After the ring fault is corrected, the timing flow can return to normal: this
operation is triggered by the transmission of OK indications instead of
NOT OK by Megaplex-4100 3 and Megaplex-4100 4.
ƒ
In case the fault occurs in the connection to the PBX (Figure 1-47),
Megaplex-4100 1 loses its master timing source. Therefore, the CLOCK
FAILURE ON THE RING alarm state is declared, and the following exchange
of messages takes place:
1. Megaplex-4100 1 reports NOT OK toward Megaplex-4100 6 (it will not
report NOT OK toward Megaplex-4100 2, because this is not relevant:
Megaplex-4100 1 uses the RX clock from the PBX as master source, not
the timing signal from the link connecting to Megaplex-4100 2).
2. Megaplex-4100 1 can switch to fallback (the signal from Megaplex-4100
6), because Megaplex-4100 6 reports OK.
At this stage, Megaplex-4100 1 has reacquired stable timing by switching
to the fallback sources.
The resulting timing flow is also illustrated in Figure 1-47.
1-72
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
5
3
4
Master: Port 1
Fallback: Port 2
Master: Port 1
Fallback: Port 2
Port 2
Port 2
Port 1
OK
OK
OK
OK
Master: Port 2
Fallback: RX Clock
Port 1
OK
OK
OK
Port 2
Port 1
Master: Port 1
Fallback: Port 2
OK
Port 1
Port 2
Master: RX Clock
Fallback: Port 2
Port 2
Port 1
OK
OK
OK
OK
Port 1
Port 2
Master: Port 1
Fallback: Port 2
6
1
2
PBX
Figure 1-45. E1/T1 Ring Redundancy Topology – Alternative Timing Flow
5
3
4
Master: Port 1
Fallback: Port 2
Master: Port 1
Fallback: Port 2
Port 2
Port 1
OK
OK
OK
OK
Port 2
NOT OK
OK
Port 2
Port 1
Port 2
Master: Port 1
Fallback: Port 2
Port 1
OK
OK
Port 1
Master: RX Clock
Fallback: Port 2
Master: Port 2
Fallback: RX Clock
6
Port 1
Port 2
OK
NOT OK
OK
OK
Port 1
Port 2
Master: Port 1
Fallback: Port 2
1
2
PBX
Figure 1-46. Timing Recovery Scenario – after a Ring Fault
Megaplex-4100 Ver. 2.0
Functional Description
1-73
Chapter 1 Introduction
Installation and Operation Manual
5
3
4
Master: Port 1
Fallback: Port 2
Master: Port 1
Fallback: Port 2
Port 2
Port 2
Port 1
OK
OK
OK
OK
Port 1
OK
NOT OK
Port 2
Port 2
Master: Port 1
Fallback: Port 2
6
Port 1
OK
OK
OK
OK
OK
OK
Port 1
Port 1
Master: RX Clock
Fallback: Port 2
Master: Port 2
Fallback: RX Clock
Port 2
Port 1
Port 2
Master: Port 1
Fallback: Port 2
1
2
PBX
Figure 1-47. Timing Recovery Scenario – after Loss of Master Reference
Management Subsystem
The Megaplex-4100 management subsystem provides all the functions needed to
configure, control, and monitor the operation of the Megaplex-4100. The main
management subsystem functions are as follows:
•
Interfacing with supervision terminals, SNMP network management stations,
and other types of external managers.
•
Configuring the Megaplex-4100.
•
Controlling the Megaplex-4100 system operation.
•
Monitoring the Megaplex-4100 status, and reading its performance
monitoring statistics.
•
Performing Megaplex-4100 tests and diagnostics.
•
Collection of operational history (alarms, events, performance statistics, etc.
The collected information can be read by maintenance personnel through the
management link.
A real-time clock provides time stamps for all the collected information.
1-74
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
•
Storage of the application software, which determines the capabilities and
features provided by the Megaplex-4100. This software can be remotely
downloaded and updated through the management link without taking the
equipment off-line. The stored software includes both system software, run
by the CL module, and software for the other modules installed in the chassis
that support internal software downloading.
•
Storage of configuration databases. The configuration databases can also be
uploaded and downloaded through the management link.
The application software, as well as the configuration databases, are stored in
flash memory.
In addition, the management subsystem also enables signaling the
Megaplex-4100 alarm status to bay alarm panels or remote operator consoles by
means of two sets of dry relay contacts (one for major alarms, the other for
minor alarms) included in the dedicated front-panel ALARM connector.
Megaplex-4100 units can also be managed by the RADview EMS, an SNMP-based
Element Management System offered by RAD.
Management Alternatives
The Megaplex-4100 supervision and configuration activities can be performed
using one of the following methods:
•
Supervision terminal (for example, implemented using a PC running ASCII
terminal emulation), or connected to the serial control port of a CL module.
No configuration information need be stored by the terminal
•
Telnet hosts (using the same procedures as the supervision terminal utility),
Web browsers (using the ConfiguRAD utility run by the Megaplex-4100
management subsystem), and SNMP-based network management stations,
for example, RADview. The following access options are supported:
Megaplex-4100 Ver. 2.0
ƒ
Out-of-band access via the dedicated Ethernet management port of the
CL module(s)
ƒ
Inband access through TDM networks, supported by E1 or T1 ports (using
a dedicated management timeslot), or by the DCC carried in the
STM-1/OC-3 link overhead.
ƒ
Inband access through the PSN, using a dedicated management VLAN.
This type of inband access is supported by Ethernet ports, virtually
concatenated groups, and bridge ports configured on bundles.
ƒ
Management by SNMP-based network management stations, using the
access options described above for Telnet hosts. Megaplex-4100 includes
an internal SNMP agent that enables full SNMP management by SNMPbased network management stations. The internal agent supports the
SNMPv3 authentication and privacy features, with continued support for
SNMPv1.
ƒ
Web browsers (using the ConfiguRAD utility run by the Megaplex-4100
management subsystem), using the access options described above for
Telnet hosts
Functional Description
1-75
Chapter 1 Introduction
Installation and Operation Manual
Except for the supervisory port, all the other management access ports use
IP-based communications, where a single IP address (the host IP address) is
assigned to the management subsystem. All the ports use the same IP and SNMP
communication parameters, and therefore management traffic can reach the
Megaplex-4100 management subsystem through any available access port.
Remote Software and Configuration Updating
The management subsystem supports TFTP for remote software updating and
downloading, in addition to cold software downloading using an ASCII terminal
directly connected to the Megaplex-4100.
TFTP can also be used to upload and download the Megaplex-4100 configuration
database. Network administrators can use the download capability to distribute
verified configuration files to all the managed Megaplex-4100 units in the
network from a central location. To further expedite the process, it is also
possible to upload the configuration data stored by an Megaplex-4100 unit to the
management station as a disk file, and then distribute this file to other units
which use a similar configuration.
Supervisory Port Capabilities
All the Megaplex-4100 supervision and configuration functions, and in particular
the preliminary configuration activities, can be performed using a “dumb” ASCII
terminal (or a PC running a terminal emulation program) directly connected to the
Megaplex-4100 serial RS-232 asynchronous supervisory port, located on its front
panel. The terminal is controlled by the program stored in the Megaplex-4100. No
information has to be stored in the terminal.
The supervisory port enables performing the preliminary configuration of the
Megaplex-4100. After the preliminary configuration is completed, Megaplex-4100
can also be managed by the other means, for example, Telnet hosts, Web
browsers, and SNMP network management stations.
The supervisory port has a DCE interface, and supports data rates in the range of
9.6 to 115.2 kbps.
Out-of-Band Access via CL Ethernet Management Port
All the CL models have a CONTROL ETH port with a 10BASE-T/100BASE-TX
Ethernet interface. This interface supports MDI/MDIX crossover, and therefore the
port can always be connected through a “straight” (point-to-point) cable to any
other type of 10/100BASE-T Ethernet port (hub or station).
The CL Ethernet management port supports IP communications, using the host IP
address of the Megaplex-4100 management subsystem.
The CONTROL ETH ports of both CL modules can be simultaneously connected to
the same LAN, through standard Ethernet hubs or switches (see the CL Module
Redundancy section on page 1-58.
To support out-of-band management, management stations, Telnet hosts, etc.,
can be attached to the same LAN, or to any LAN from which IP communication
with the CL module Ethernet ports is possible.
1-76
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Inband Management Access through TDM Networks
Figure 1-48 illustrates the inband management access capabilities through TDM
networks.
Megaplex-4100
CL
Megaplex-4100
Inband Management Traffic
to Other Equipment
CL
E1
Megaplex-4100
SDH/SONET
Network
E1, T1
or SHDSL
Module
Megaplex-4100
TDM
Network
CL
Network
Management
Station
E1
E1, T1
or SHDSL
Module
CL
Megaplex-4100
E1, T1
or SHDSL
Module
CL
Figure 1-48. Inband Management Access through TDM Networks
The following access methods are available:
Note
•
Access via E1 and T1 ports (including internal ports of SHDSL I/O modules)
using a framed mode: in this case, management access is provided by
configuring a dedicated management timeslot.
•
Access via the Data Communication Channel (DCC) carried in the SDH/SONET
overhead. Each SDH/SONET link can have its DCC used for management. DCC
ports use the host IP address of the Megaplex-4100 management subsystem.
Inband management can also support more complex topologies, for example,
rings. However, this is possible only if the carrier’s SDH/SONET network provides
access to the DCC and enables transparent transfer of user’s data through the
DCC. In this case, a Telnet host or an SNMP-based network management station
connected to one of the Megaplex-4100 units in the network can manage all the
other units, inband.
Typically, the Telnet host or management station is connected to a CL
Ethernet port of the local Megaplex-4100 unit. To enable remote
management, the management traffic not addressed to the internal
management subsystem of the Megaplex-4100 is also connected by this
subsystem to the DCCs carried by the other SDH/SONET links connected to
the Megaplex-4100.
Megaplex-4100 Ver. 2.0
Functional Description
1-77
Chapter 1 Introduction
Installation and Operation Manual
At the remote Megaplex-4100 units, the management traffic is extracted
from the DCC and connected to the local unit management subsystem. This
arrangement enables the management station to manage each remote
Megaplex-4100 unit.
As mentioned above, the inband management traffic is carried in the DCC
bytes, part of the SDH/SONET overhead. The user can select the DCC bytes to
carry the traffic:
ƒ
Regenerator section DCC bytes (D1, D2, D3), which provide a 192 kbps
channel terminated at SDH/SONET regenerator section terminating
equipment
ƒ
Multiplex section DCC bytes (D4 to D12), which provide a 576 kbps
channel terminated at SDH/SONET multiplex section terminating
equipment.
The user can also select the encapsulation and routing protocols used for
inband management parameters:
ƒ
Two encapsulation options are available: HDLC, or PPP over HDLC in
accordance with RFC1661 and RFC1662.
For compatibility with particular implementations of the HDLC
encapsulation protocol for management purposes, the user can select the
Type 1 flavor (for this flavor, the LCP (Link Control Protocol) packets do
not include address and control fields in their overhead).
ƒ
Two options are also available for the management traffic routing
protocol:
…
…
RAD proprietary protocol. This protocol is sufficient for managing any
RAD equipment and should always be used with HDLC encapsulation.
RIP2: the Megaplex-4100 transmits RIP2 routing tables. This permits
standard RIP routers to reach the Megaplex-4100 SNMP agent
through the inband (DCC) channel.
Inband Management Access through PSN Networks
Figure 1-49 illustrates the inband management access capabilities through PSN
networks. As shown in Figure 1-49, management traffic received through the PSN
is also available on the TDM ports, to integrate the various management options.
To control the flow of management traffic through the PSN, a dedicated
management VLAN is normally used.
Within the Megaplex-4100, management traffic routing is controlled by
configuring a dedicated management flow, which is always assigned the flow
identifier 251 (see the Using Flows to Control Ethernet Traffic Forwarding section
starting on page 1-45 for a description of Ethernet flows).
Three types of bridge ports can be included in the internal management flow:
1-78
•
Ethernet ports, including GbE ports
•
Bridge ports configured on unframed bundles (both HDLC and MLPPP
bundles)
•
Virtually concatenated groups configured on SDH/SONET ports
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
To avoid forming loops in the Ethernet communication topology when same
management traffic can be received through more than one bridge port, the user
can specify which bridge ports will accept management traffic from network
management stations (such ports are referred to as host NMS sources), and the
management subsystem selects one of these ports as the active port.
PSN
Inband Management Traffic
to Other Equipment
E1
Network
Management
Station
n x E1
CL
M8E1
TDM
Network
n x E1
E1
n x E1
n x E1
Megaplex-4100
M8E1
Megaplex-4100
Legend
Dedicated Management VLAN
Figure 1-49. Inband Management Access through PSN
Performance Monitoring Statistics
Megaplex-4100 management subsystem collects performance data, which
enables the network operator to monitor the transmission performance and thus
the quality of service provided to users, as well as identify transmission problems.
Performance parameters for all the active entities are continuously collected
during equipment operation.
Alarm Collection and Reporting
The Megaplex-4100 management subsystem continuously monitors critical signals
and signal processing functions, and also performs automatic self-test upon
power-up. In case a problem is detected, the Megaplex-4100 generates
time-stamped alarm messages. The time stamp is provided by an internal
real-time clock.
For continuous system monitoring, the user can monitor alarm messages through
the supervisory port. Alarm messages can also be automatically sent as traps to
the user-specified network management stations.
The alarms can be read on-line by the network administrator using a Telnet host, a
Web browser, SNMP-based network management station, or a supervision terminal.
Note
The Megaplex-4100 can also monitor one external sense input, and will report its
activation as any other internally-detected alarm.
In addition to the alarm collection and reporting facility, the Megaplex-4100 has
two alarm relays with floating change-over contacts: one relay for indicating the
Megaplex-4100 Ver. 2.0
Functional Description
1-79
Chapter 1 Introduction
Installation and Operation Manual
presence of major alarms and the other for minor alarms. Each relay changes
state whenever the first alarm is detected, and returns to its normal state when
all the alarms of the corresponding severity disappear. The relay contacts can be
used to report internal system alarms to outside indicators, e.g., lights, buzzers,
bells, etc., located on a bay alarm or remote monitoring panel.
To expedite the handling of alarms, the user can use several tools:
•
Masking of alarm conditions, to prevent continuous reporting of known alarm
conditions, e.g., during maintenance activities.
•
Inversion of selected alarm indications provided to the local operator by the
alarm indicators, and by the two alarm relays. “Inverted” alarms are ignored
while they are present, therefore the user will be alerted only upon return to
normal operation.
•
Filtering of alarms, to prevent unnecessary reporting of alarms during
marginal conditions, which cause frequent changes in alarm states.
Diagnostic Functions
When a problem occurs, Megaplex-4100 offers a set of diagnostic functions that
permit to efficiently locate the problem (in the Megaplex-4100 chassis, one of
Megaplex-4100 modules, a connecting cable, or external equipment) and rapidly
restore full service.
The diagnostic functions are based on the activation of loopbacks at various
ports. These loopbacks enable to identify whether a malfunction is caused by the
Megaplex-4100 or by an external system component (for example, an equipment
unit, cable, or transmission path connected to the Megaplex-4100). A detailed
description of the test and loopback functions is given in Chapter 5, as well as in
the Installation and Operation Manuals of each module.
Power Supply Subsystem
PS Modules
Megaplex-4100 can be ordered with either AC or DC power supply modules.
Two PS modules can be installed in the chassis. Only one PS module is required to
provide power to a fully equipped Megaplex-4100, and therefore installing a
second module provides redundancy. While both modules operate normally, they
share the load; in case one fails or does not receive power, the other module
continues to provide power alone. Switch-over is thus automatic and does not
disturb normal operation.
Feed and Ring Voltage Sources
Megaplex-4100 PS modules support the connection of an external feed and ring
generation voltage source, for example, the Ringer-2200N standalone unit offered by
RAD. The connection is made as follows:
•
1-80
AC-powered PS modules have a separate connector for feed and ring voltage.
Functional Description
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
•
Chapter 1 Introduction
DC-powered modules derive the -48 VDC or +24 VDC feed voltage from the
DC input voltage (in accordance with the nominal input voltage of the
module). In addition, the power input connector also includes a +72 VDC
input for ISDN modules, and for the ring voltage needed by some types of
voice interface modules.
RAD offers the standalone Ringer-2200N unit, intended for installation in 19” racks,
for providing the required feed voltages. For additional details, refer to the
Ringer-2200N Installation and Operation Manual.
1.4
Note
Technical Specifications
For module technical specifications, refer to the module Installation and
Operation Manuals.
STM-1/OC-3 Ports
Number of Ports
• 2 per CL module
• 4 per chassis
Bit Rate
155.52 Mbps
Timing
• Internal clock
• Clock recovered from the STM-1/OC-3
interface
• External clock recovered from TDM interfaces
• External clock recovered from any tributary
within STM-1/OC-3 links
Compliance
• SDH: ITU-T G.957, G.783, G.798
• SONET (option): GR-253-CORE
Internal Clock
Characteristics
• CL.1/155, CL.1/155GbE: Stratum 3 according
to ITU-T Rec. G.813 option 1 and 2, and
GR-253-CORE SMC
• CL.1, CL.1/GbE: Stratum 4E
Framing
• SDH: ITU-T Rec. G.707, G.708, G.709, G.783
• SONET: ANSI T1.105-1995, GR-253-CORE
Protection
1+1 unidirectional APS (G.842)
Connectors
SFP-based in accordance with Table 1-3
Note: For detailed specifications of SFP transceivers,
see the RAD SFP Transceivers data sheet.
Megaplex-4100 Ver. 2.0
Technical Specifications
1-81
Chapter 1 Introduction
Installation and Operation Manual
Table 1-3. SFP Connector Modules for STM-1/OC-3 Interfaces
Transceiver Wavelength
Fiber Type
Type
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
(min)
(m ax)
(min)
(max)
(km)
(miles)
LC
-30
-14
-20
-14
2
1.2
Laser
LC
-28
-8
-15
-8
15
9.3
Laser
LC
-34
-10
-5
0
40
24.8
Laser
LC
-34
-10
-5
0
80
49.7
—
Mini-BNC
—
—
—
—
0.135
0.08
62.5/125 μm, VCSEL
SFP-1
Input power
Transmitter Connector
multi-mode
SFP-2
1310 nm
9/125 μm,
single mode
9/125 μm,
SFP-3
single mode
SFP-4
1550 nm
9/125 μm,
single mode
SFP-11
Copper Link
75Ω coaxial
cable
GbE Ports
over RG-59B/U
• 2 per CL module
Number of Ports
• 4 per chassis
External Ports
In accordance with order:
• Two GbE ports with SFP modules
• Two GbE ports with copper (RJ-45) interfaces
Optical GbE Port
Interface
Characteristics
Interface Type
1000 Mbps full-duplex port
Link Connectors
SFP-based in accordance with Table 1-4
Table 1-4. SFP Connector Modules for GbE Interfaces
Transceiver Wavelength
SFP-5
850 nm
Fiber Type
50/125 μm,
Transmitter Connector
Type
Input power
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
(min)
(max)
(min)
(max)
(km)
(miles)
VCSEL
LC
-17
0
-9.5
0
0.55
0.3
Laser
LC
-20
-3
-9.5
-3
10
6.2
Laser
LC
-22
-3
0
+5
80
49.7
Laser
LC
-21
-3
0
-4
40
24.8
multi-mode
SFP-6
1310 nm
9/125 μm,
single mode
SFP-7
1550 nm
9/125 μm,
single mode
SFP-8d
1310 nm
9/125 μm,
single mode
Copper GbE Port
Interface
Characteristics
1-82
Interface Type
10/100/1000BASE-T port, full-duplex, with
autonegotiation
Link Connector
RJ-45 shielded
Technical Specifications
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Serial Control Port
(CONTROL DCE)
Chapter 1 Introduction
Interface
RS-232/V.24 (DCE)
Data Rate
9.6, 19.2, 38.4, 57.6, 115.2 kbps asynchronous
Ethernet
Management Port
(CONTROL ETH)
Interface
10/100BaseT with autonegotiation
Connector
RJ-45
Station Clock
Interface
Rate
• 2.048 MHz
• 2.048 Mbps
• 1.544 Mbps
Interface
Jumper-selectable:
• RS-422 squarewave
• ITU-T Rec. G.703, HDB3 coding for 2.048 MHz
and 2.048 Mbps
• ITU-T Rec. G.703, B8ZS coding for 1.544 Mbps
Diagnostics
Connector
RJ-45
Tests
Local and remote loopbacks per link and per
timeslot
Alarms
• Time and date stamped
• Last 256 alarms stored in RAM on CL module,
readable by management system or terminal
• Current alarms status
Statistics
• AT&T statistics when using ESF framing for T1
trunks or CRC-4 with G.704 multiframing for
E1 trunks
• Performance statistics for bundles and LAN
ports
• SDH/SONET link monitoring
• Ethernet port statistics
Indicators
ON LINE indicator
• Lights green on the master (active) module
• Lights yellow on the master (active) module if
a test exists.
• Flashes green when this module is standby or
during software download
• Flashes yellow when software is
decompressed
Megaplex-4100 Ver. 2.0
Technical Specifications
1-83
Chapter 1 Introduction
Installation and Operation Manual
ALM indicator
• Flashes red when a major or critical alarm
exists in the Megaplex-4100 system
• Lights red when any alarm (not minor or
critical) exists in the Megaplex-4100 system
Station CLOCK Interface
Indicators
• ON (green) – Port is connected
Ethernet Interface
Indicators (per port)
• LINK (green) – LAN link integrity
STM-1/OC-3 Interface
Indicators (per port)
LOS (red) – STM-1/OC-3 link signal loss
• LOS (red) – Signal loss on the port
• ACT (yellow) – LAN data activity
ON LINE:
• Lights green when the link is active
• Lights yellow if a test exists
Alarm Relay Port
Port Functions
• 1 inbound RS-232 alarm input
• 2 outbound (dry contact) relays triggered by
any user-selected Megaplex-4100 alarm
Power Supply
Operation
Normally open, normally closed, using different
pins
Connector
9-pin, D-type, female
Model
Input
PS/AC
Wide-range operation: 110/115, 220/230 VAC
Range: 100 to 240 VAC, 50/60Hz
Maximum output power: 200W + power supplied
for ring and feed voltage purposes (drawn
directly from external supply)
PS/48
• -48 VDC (allowed range: -36 to -72 VDC)
PS/24
• +24 VDC (allowed range: +18 to +40 VDC)
• Maximum input power: 250W + power
supplied for ring and feed voltage purposes
(drawn directly from external supply)
Caution
1-84
For PS/48 and PS/24, the DC input voltage can be floated with respect to
Megaplex-4100 ground by means of field-selectable jumpers. Internal jumpers can
also be set to match operational requirements that need either the + (positive)
or – (negative) terminal of the power source to be grounded. Contact RAD
Technical Support Department for detailed information.
Technical Specifications
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 1 Introduction
Max. Power Supply Output Currents
PS/AC, PS/48, PS/24
Physical
Megaplex-4100 Ver. 2.0
+3.3V
+5V
-5V
+12V
-12V
30A
40A
6.5A
2A
2A
Height
18 cm/7 in (4U)
Width
44 cm/17 in
Depth
33 cm/13 in
Weight (fully equipped
chassis)
15.3 kg / 33.8 lb max.
Technical Specifications
1-85
Chapter 1 Introduction
1-86
Technical Specifications
Installation and Operation Manual
Megaplex-4100 Ver. 2.0
Chapter 2
Installation
This Chapter provides installation instructions for the Megaplex-4100.
The Chapter presents the following information:
•
General description of equipment enclosure and its panels.
•
Mechanical and electrical installation instructions for the enclosure itself and
for system modules, that is, PS and CL modules.
After installing the system, it is necessary to configure it in accordance with the
specific user's requirements:
•
The preliminary system configuration is always performed by means of a
supervision terminal (procedures for using the terminal are given in
Chapter 3). The software necessary for using the terminal is stored in the CL
module: if the CL module is not yet loaded with the required software, refer
to Appendix B for detailed software installation instructions.
•
After the preliminary configuration, the system can also be managed by
means of Telnet hosts, Web browsers, and/or SNMP-based network
management stations, e.g., RADview. Refer to the User's Manual of the
network management station for operating instructions.
2.1
Safety
General Safety Precautions
Warning
No internal settings, adjustment, maintenance, and repairs may be performed by
either the operator or the user; such activities may be performed only by a skilled
technician who is aware of the hazards involved. Always observe standard safety
precautions during installation, operation, and maintenance of this product.
Caution
Megaplex-4100 modules contain components sensitive to electrostatic discharge
(ESD). To prevent ESD damage, always hold the module by its sides, and do not
touch the module components or connectors.
Megaplex-4100 Ver. 2.0
Safety
2-1
Chapter 2 Installation
Installation and Operation Manual
Caution Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the Megaplex-4100 modules. To prevent physical damage:
• Always keep modules in their protective packaging until installed in the
Megaplex-4100 chassis, and return them to the packaging as soon as they are
removed from the enclosure.
• Do not stack modules one above the other, and do not lay any objects on
PCBs.
• When inserting a module into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the module PCB does not
touch the adjacent module, nor any part of the chassis. If resistance is felt
before the module fully engages the mating backplane connector, retract the
module, realign it with the slot guides and then insert again.
Grounding
Grounding
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the lines connected to the equipment, the Megaplex-4100 case must be
properly grounded (earthed) at any time. Any interruption of the protective
(grounding) connection inside or outside the equipment, or the disconnection of
the protective ground terminal can make this equipment dangerous. Intentional
interruption is prohibited.
Dangerous voltages may be present on the electrical cables connected to the
Megaplex-4100 and its modules.
Warning
• Never connect cables to Megaplex-4100 if not properly installed and
grounded.
• Disconnect all the cables connected to the electrical connectors of the
Megaplex-4100 before disconnecting its grounding connection.
Before connecting any other cable and before applying power to this equipment,
the protective ground (earth) terminal of the equipment must be connected to
protective ground. Megaplex-4100 grounding terminals are located on the
Megaplex-4100 PS module panels.
Whenever Megaplex-4100 units are installed in a rack, make sure that the rack is
properly grounded and connected to a reliable, low-resistance grounding system,
because the rack can also provide a connection to ground.
In addition, the grounding connection is also made through each one of the AC
power cables. Therefore, the AC power cable plug must always be inserted in a
socket outlet provided with a protective ground.
Caution When working with VC-4/4A/8/8A/16 modules with FXS interfaces, refer to the
Frequently Asked Questions section in the VC-4/4A/8/8A/16 Installation and
Operation Manual for additional information on ground connections.
2-2
Safety
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Laser Safety
Warning
Megaplex-4100 modules may be equipped with a laser diode. In such cases, a
label with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may be also attached.
For your safety:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the optical transmitter.
• Do not use broken or unterminated fiber-optic cables/connectors.
• Do not look straight at the laser beam, and do not directly into the optical
connectors while the unit is operating.
• Do not attempt to adjust the laser drive current.
• The use of optical instruments with this product will increase eye hazard.
Laser power up to 1 mW at 1300 nm and 1550 nm could be collected by an
optical instrument.
• Use of controls or adjustment or performing procedures other than those
specified herein may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
Megaplex-4100 modules equipped with laser devices provided by RAD comply with
laser product performance standards set by governmental agencies for Class 1 laser
products. The modules do not emit hazardous light, and the beam is totally enclosed
during all operating modes of customer operation and maintenance.
In some cases, the users may insert their own SFP laser transceivers into
Megaplex-4100 modules. Users are alerted that RAD cannot be held responsible
for any damage that may result if non-compliant transceivers are used. In
particular, users are warned to use only agency approved products that comply
with the local laser safety regulations for Class 1 laser products.
Wherever applicable, Megaplex-4100 modules are shipped with protective covers
installed on all the optical connectors. Do not remove these covers until you are
ready to connect optical cables to the connectors. Keep the covers for reuse, to
reinstall the cover over the optical connector as soon as the optical cable is
disconnected.
Protection against ESD
An electrostatic discharge occurs between two objects when an object carrying
static electrical charges touches, or is brought near enough, the other object.
Static electrical charges appear as result of friction between surfaces of insulating
materials, separation of two such surfaces and may also be induced by electrical
fields. Routine activities such as walking across an insulating floor, friction
between garment parts, friction between objects, etc. can easily build charges up
to levels that may cause damage, especially when humidity is low.
Megaplex-4100 Ver. 2.0
Safety
2-3
Chapter 2 Installation
Installation and Operation Manual
Caution Megaplex-4100 modules contain components sensitive to electrostatic discharge
(ESD). To prevent ESD damage, always hold a module by its sides, and do not
touch the module components or connectors. If you are not using a wrist strap,
before touching a module, it is recommended to discharge the electrostatic
charge of your body by touching the frame of a grounded equipment unit.
Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistance,
yet are not insulators.
Proper Handling of Modules
Megaplex-4100 modules include small components installed on both sides of the
printed circuit boards. These components are exposed as long as the modules are
not installed in the chassis, are therefore may be unintentionally damaged. To
prevent physical damage to modules:
1. Always keep the modules in their protective shipping containers until installed
in the chassis. These containers also protect against ESD.
2. Avoid piling up modules.
3. While inserting modules in their chassis slots, support the modules and make
sure their components do not touch the chassis structure, nor other modules
while sliding into position.
2.2
Site Requirements
Warning
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
AC Power Requirements
AC-powered Megaplex-4100 units should be installed within 1.5m (5 feet) of an
easily-accessible grounded AC outlet capable of furnishing 110/115 or 230 VAC,
(nominal), 50/60 Hz.
DC Power Requirements
DC-powered Megaplex-4100 units require a -48 VDC (36 to -72 VDC) or 24 VDC
(20 to 40 VDC) power source (in accordance with the nominal mains voltage of the
ordered PS module).
2-4
Site Requirements
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Caution Megaplex-4100 PS modules which do not have a power ON/OFF switch start
operating as soon as power is applied. Therefore, an external power ON/OFF
switch is required (for example, the circuit breaker that protects the power line
can also serve as an ON/OFF switch).
Caution 1. It is not allowed to install DC-powered PS modules operating on different
voltages (i.e., 24 VDC and -48 VDC) in the same Megaplex-4100 chassis.
2. Internal jumpers on the DC PS modules can be set to match operational
requirements that need either the + (positive) or – (negative) terminal of the
power source to be grounded. The normal factory setting is for a power
source with the +(positive) terminal grounded (the power supply module
jumpers are installed in the BGND=FGND and GND=FGND positions). When it
is necessary to use a power source with the – (negative) terminal grounded,
or a floating power source, the jumpers must be disconnected (set to NO).
Check the position of jumpers in the Megaplex-4100 power supply module
(see Figure 2-5) before connecting the DC supply voltage.
Certain I/O modules may still cause BGND to be connected to FGND or GND,
even after setting the jumpers to NO. Refer to the Installation and Operation
Manuals of the modules installed in the chassis for proper setting of their
ground-control jumpers.
3. If the Megaplex-4100 chassis must be operated with floating ground, it may
also be necessary to disconnect the ground reference on the power supply
modules, and check the ground and shield wiring on the cables connected to
the chassis. This may require replacing the cables with cables suitable to your
specific application.
4. Megaplex-4100 chassis must always be connected to FGND (protective
ground).
Special ordering options with preconfigured floating ground settings are available.
Contact your local distributor for more information. When working with FXS voice
modules, see also Frequently Asked Questions section in the VC-4/4A/8/8A/16
Installation and Operation Manual.
Payload Connections
For information regarding connections to port types not covered below, refer to
the corresponding module Installation and Operation Manual.
Connections to E1 and T1 Ports
Megaplex-4100 systems may be equipped with external E1 and T1 ports. The
maximum allowable line attenuation between a Megaplex-4100 port and the
network interface depends on the type of port interface, and therefore it is given
in the Installation and Operation Manual of each specific module.
The electrical E1 and T1 interfaces of Megaplex-4100 systems must not be
connected directly to unprotected public telecommunication networks. Use
primary protectors in the MDF or IDF for additional protection.
Megaplex-4100 Ver. 2.0
Site Requirements
2-5
Chapter 2 Installation
Installation and Operation Manual
The E1 and T1 ports located on Megaplex-4100 M8E1 and M8T1 modules are
terminated in 44-pin female D-type connectors. RAD offers special adapter cables
for terminating the ports in standard RJ-45 or BNC connectors (see the module
Installation and Operation Manuals).
Connections to SHDSL Ports
The SHDSL ports of a M8SL module have ITU-T Rec. G.991.2 interfaces terminated
in a 40-pin female SCSI connector. RAD offers special adapter cables for
terminating the ports in standard RJ-45 connectors (see the Installation and
Operation Manuals of the specific modules).
Each SHDSL port requires one unloaded 24 AWG or 26 AWG twisted pair. The
maximum range depends on the data rate and pair gage. Table 2-1 lists typical
ranges over 2-wire 24 AWG and 26 AWG lines versus the payload data rate. Note
that because of the widely varying characteristics of actual twisted pairs, the
actual range on any particular pair may deviate from the data presented in the
table.
Table 2-1. Typical SHDSL Ranges over 24 AWG and 26 AWG Lines
Data Rate
[kbps]
24 AWG
[km]
[miles]
26 AWG
[km]
[miles]
256
9.0
5.5
7.1
4.4
512
7.7
4.7
5.9
3.6
768
7.0
4.3
5.6
3.5
1024
6.2
3.8
4.4
2.7
1536
4.7
2.9
3.9
2.4
2048
4.0
2.4
3.5
2.1
Connections to SDH/SONET Ports
SDH/SONET ports have STM-1/OC-3 ports. Each port has a socket for installing
the desired type of SFP transceiver. RAD offers SFPs that meet a wide range of
system requirements, including:
•
Optical interfaces: SFPs with 1310 nm short-haul interfaces for use over
multimode fibers, or 1310 and 1550 nm long-haul interfaces for use over
single-mode fibers.
•
Electrical interfaces, for use over 75 Ω coaxial cables. The SFPs offered by
RAD for this interface are terminated in two mini-BNC connectors.
RAD also offers an adapter cable, CBL-MINIBNC-BNC, that connects to the
mini-BNC connectors and is terminated in BNC connectors, for connection to
patch panels or equipment with BNC connectors.
SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends to order modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
2-6
Site Requirements
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Connections to Ethernet Ports
Gigabit Ethernet (GbE) payload ports are located on CL.1/155GbE modules, and
10/100 Mbps Ethernet payload ports are located on M8E1, M8T1, and M8SL
modules. These ports either have sockets for installing the desired type of SFP
transceiver, or have fixed UTP interfaces.
RAD offers SFPs that meet a wide range of system requirements, for example,
SFPs with 850 or 1310 nm short-haul interfaces for use over multimode fibers, or
1310 and 1550 nm long-haul interfaces for use over single-mode fibers.
SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends to order modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Fixed UTP interfaces (either GbE or 10BASE-T/100BASE-TX) are terminated in an
RJ-45 connector. GbE interfaces always support auto-negotiation;
10BASE-T/100BASE-TX interfaces support MDI/MDIX crossover and therefore can
always be connected through a “straight” (point-to-point) cable to any other
type of 10/100BASE-T Ethernet port (hub or station).
Optical Cable Requirements
The cables connected to Megaplex-4100 optical ports should use 2-mm optical
fibers terminated in the corresponding type of connectors.
When routing fibers, make sure to observe the minimum bending radius (35 mm).
RAD recommends installing plastic supports on each cable connector: these
supports determine the fiber bending radius at the connector entry point and
also prevent stress at this point.
Connections to Station Clock
The station clock ports located on the CL modules can accept 2.048 MHz or
1.544 MHz signals (framed 2.048 Mbps or 1.544 Mbps signals are also accepted).
The port can also output the clock signal: this output provides a convenient
means for distributing clock signals, including the Megaplex-4100 nodal clock
signal, to other equipment.
The station clock port is terminated in one RJ-45 connector, designated CLOCK,
which supports two interfaces:
•
100 Ω/120 Ω balanced interface for operation over two twisted pairs
•
75 Ω unbalanced interface for operation over coaxial cables. This interface
can be used only for 2.048 MHz or 2.048 Mbps clock signals.
At any time, only one interface is active. The selection of the active interface is
made by the user. In addition, provisions are made to sense the type cable
connected to the port:
•
Megaplex-4100 Ver. 2.0
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.
Site Requirements
2-7
Chapter 2 Installation
Note
One of the contacts in the station clock connector is used to sense the
connection of the unbalanced adapter cable (see Appendix A). Therefore, do not
connect cables with more than two pairs when you want to use the balanced
interface.
•
Note
Installation and Operation Manual
To connect to equipment with unbalanced interface, it is necessary to convert
the CL RJ-45 connector to the standard pair of BNC female connectors used
for unbalanced ITU-T Rec. G.703 interfaces. For this purpose, RAD offers a
15-cm long adapter cable, CBL-RJ45/2BNC/E1/X. This cable has one RJ-45 plug
for connection to CL station clock connector, and two BNC female connectors
at the other end.
When using redundant CL modules, only one of the two station clock ports must be
connected to a station clock source. For best protection, it is recommended to
connect the two station ports to two separate station clock sources.
When only one clock source is available, you can have better protection by
connecting the station clock inputs in parallel, by means of a simple Y-cable. In this
case, configure the CL module to use a Y-cable: this configuration ensures that at
any time only one station clock interface (that of the active module) is active.
Management Connections
Ethernet Connections to CL Modules
The CL modules have 10BASE-T/100BASE-TX Ethernet interfaces terminated in
RJ-45 connectors, designated CONTROL ETH.
These interfaces support MDI/MDIX crossover and therefore the ports can always
be connected through a “straight” (point-to-point) cable to any other type of
10/100BASE-T Ethernet port (hub or station).
Connection to Serial Port
The CL supervisory port has a serial RS-232 asynchronous DCE interface
terminated in a 9-pin D-type female connector, designated CONTROL DCE.
This port can be directly connected to terminals using a cable wired
point-to-point. A cross cable is required to use the DTE mode, for example, for
connection through modems or digital multiplexer channels.
Note
When using redundant CL modules, you can connect the terminal, respectively the
modem, in parallel to the corresponding serial port connectors of the two modules
by means of a simple Y-cable, because at any time only one serial port (that of the
active module) is active.
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.
2-8
Site Requirements
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Connections to Alarm Port
The alarm port is terminated in a 9-pin D-type female connector located on the
CL module, designated ALARM. This port includes:
•
Caution
Floating change-over dry-contact outputs for the major and minor alarm
relays. The alarm relay contacts are rated at maximum 60 VDC/30 VAC across
open contacts, and maximum 1 ADC through closed contacts (total load
switching capacity of 60 W).
Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
•
+5V auxiliary voltage output (through a 330 Ω series resistor).
•
External alarm sense input. The input accepts an RS-232 input signal; it can
also be connected by means of a dry-contact relay to the auxiliary voltage
output.
Front and Rear Panel Clearance
Allow at least 90 cm (36 inches) of frontal clearance for operator access.
Allow the same clearance at the rear of the unit for interface cable connections
and module replacement.
Ambient Requirements
The ambient operating temperature range of the Megaplex-4100 is 0 to +45°C (32
to 113°F), at a relative humidity of up to 90%, non-condensing.
Most of the Megaplex-4100 modules are cooled by free air convection. The PS
power supply modules have a miniature cooling fan installed on their front
panels: this fan operates only when the temperature is high.
Cooling vents are located in the bottom and upper covers. Do not obstruct these
vents. When the Megaplex-4100 is installed in a 19" rack, allow at least 1U of
space below and above the unit.
Electromagnetic Compatibility Considerations
The Megaplex-4100 is designed to comply with the electromagnetic compatibility
(EMC) requirements of Sub-Part J of FCC Rules, Part 15, for Class A electronic
equipment, and additional applicable standards such as EN55022 and EN55024.
Megaplex-4100 also complies with all the requirements of the CE mark.
To meet these standards, it is necessary to perform the following actions:
•
Megaplex-4100 Ver. 2.0
Connect the Megaplex-4100 case to a low-resistance grounding system.
Site Requirements
2-9
Chapter 2 Installation
Installation and Operation Manual
•
Install blank panels to cover all empty slots. Appropriate blank panels can be
ordered from RAD.
•
Whenever possible, use shielded telecommunication cables.
In particular, it is recommended to use a shielded RS-232 to connect to the
CL module serial control port.
Note
The serial control port is normally used only during preliminary configuration, and
for maintenance purposes. If you cannot obtain a shielded control cable, make
sure to connect the cable only for the minimum time required for performing the
task.
•
In certain cases, the use of shielded cables or twisted pairs, or use of ferrite
cores, is recommended. Refer to the individual module Installation and
Operation Manual for details.
Covering all empty slots is also required for reasons of personal safety.
Warning
2.3
Package Contents
The Megaplex-4100 package includes the following items:
•
Megaplex-4100 chassis, including CL and PS modules in accordance with order
•
Power cables in accordance with order (for the DC power cable, also includes
a DC plug)
•
Supervision terminal cable, CBL-DB9F-DB9M-STR
•
Rack installation kit in accordance with order:
•
ƒ
RM-MP-MX-23/19: hardware kit for installing one Megaplex-4100 in either
a 19-inch or 23-inch rack
ƒ
MP-4100-RM-ETSI/19: hardware kit for installing one Megaplex-4100 in a
23-inch ETSI rack (can also be used for installation in 19-inch rack)
Technical documentation CD.
I/O modules are shipped either separately, or preinstalled in the chassis, in
accordance with your order.
2.4
Required Equipment
The additional cables you may need to connect to the Megaplex-4100 depend on
the Megaplex-4100 application.
You can use standard cables or prepare the appropriate cables yourself in
accordance with the information given in Appendix A, and in the Installation and
Operation Manuals of the installed modules.
2-10
Required Equipment
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
2.5
Chapter 2 Installation
Mounting the Megaplex-4100 Unit
This section presents instructions for installing Megaplex-4100 units. To help you
familiarize with the equipment, it also presents a physical description of the
Megaplex-4100 versions.
Do not connect any cables to the Megaplex-4100 before it is installed in the
designated position.
Warning
Familiarization with Megaplex-4100
Figure 2-1 shows a general view of the Megaplex-4100 enclosure.
10 I/O Modules
2 CL Modules
2 PS Modules
Figure 2-1. Megaplex-4100 Enclosure, General View
The enclosure has 14 module slots: two of them are reserved for PS modules,
and two for CL modules. The other 10 slots are intended for I/O modules. Each
I/O slot can accept any type of I/O module. The modules are inserted from the
rear side.
The Megaplex-4100 enclosure can be ordered with brackets for installation in racks.
The brackets are attached to the sides of the enclosure, near the front or rear panel.
Rear View
Figure 2-2 shows a typical rear view of the Megaplex-4100 enclosure and
identifies the slots and their use. Note the labels which designate the type of
module that can be installed in each slot; in addition, each slot is keyed,
therefore it is not possible to install the wrong module type.
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-11
Chapter 2 Installation
Installation and Operation Manual
Caution To prevent physical damage to the electronic components assembled on the two
sides of the module printed circuit boards (PCB) while it is inserted into its
chassis slot, support the module while sliding it into position and make sure that
its components do not touch the chassis structure, nor other modules.
Sl ot
PS- A
-
P S-B
-
-
I /O 1 I/O 2 I /O 3 I/O 4 I /O 5
C L-A
CL-B
I/O 6 I/O 7
I/O 8 I/O 9 I/O 10
-
PS Slo ts
I/O Slots
CL Slots
I/O Slots
Figure 2-2. Megaplex-4100 Enclosure, Typical Rear View
Front Panel
The front panel of the Megaplex-4100 enclosure includes labels for the system
status indicators.
Figure 2-3 identifies the front panel indicators, and Table 2-2 describes indicator
functions.
POWER SUPPLY
A
B
SYSTEM
ALARM
TEST
MEGAPLEX-4100
Figure 2-3. Megaplex-4100 Enclosure, Front Panel
2-12
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Table 2-2. Megaplex-4100 Front Panel Indicators
Indicator
Function
POWER SUPPLY A, B
Lights in green when the corresponding PS module is on, provided one of the CL
modules is active
SYSTEM TEST
Lights in yellow when a test (or loopback) is being performed in the Megaplex-4100
SYSTEM ALARM (red)
Flashes in red when a major and/or critical alarm has been detected in the
Megaplex-4100
Note
The indicator functions listed in Table 2-2 are the default functions. When the
alarm masking and/or alarm inversion functions are used (see Chapter 4 for
details), the meaning of the various alarm indications may change.
Installing PS Modules
Warning
High
Voltage
Dangerous voltages are present inside the PS module when it is connected to
power. Do not connect the PS module to power before it is properly installed
within the Megaplex-4100 enclosure. Always disconnect the input power from
the PS module before removing it from the enclosure. The installation and
preparation of the module shall be done by a qualified person who is aware of
the hazards involved.
Module Panels
The following PS versions are offered for Megaplex-4100:
•
DC-powered modules, PS/24 and PS/48: 250W modules, operating on 24 VDC
and -48 VDC (nominal), respectively
•
AC-powered module, PS/AC: 200W module, operates on 110 VAC or 230 VAC,
50/60Hz (nominal voltage is marked on the module panel).
Typical PS panels are shown in Figure 2-4. PS modules which do not include a
power on/off switch will start operating as soon as power is applied. It is
recommended to use an external power on/off switch, for example, the circuit
breaker used to protect the supply line to the Megaplex-4100 may also serve as
the on/off switch.
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-13
Chapter 2 Installation
Grounding
Screw
Installation and Operation Manual
Gr ounding
Screw
PS/AC
PS/DC
P S/DC
Fan
Fa n
DC Input
Connec tor
DC Input
Connector
VDC-IN
Power
Switch
RTN
+72
VDC-IN
-48
-
+
P
O
W
E
R
100-120VAC
200-240VAC
Input Voltage
Range Marking
+
V DC-IN
-
72 V
48 V
ON
Input V oltages
ON Indicat or
-
+
+
-
72 V
24 V
ON
Grounding
Screw
AC Power
Connector
AC-Powered Module
-48 VDC-Powered Module
24 VDC-Powered Module
Figure 2-4. Typical Megaplex-4100 PS Module Panels
The PS modules support the connection of an external feed and ring voltage
source, e.g., a Ringer-2000 standalone unit offered by RAD:
•
The AC-powered PS versions have a separate connector, designated VDC-IN,
for the external -48 VDC and +72 VDC voltages.
•
The connection of the +72 VDC voltage to the DC-powered PS versions is
made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
The PS modules have a miniature cooling fan on the front panel. Make sure to
keep the fan opening free of obstructions.
Internal Jumpers
The PS modules include two internal jumpers that control the connection of
frame ground to the internal ground lines.
2-14
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Caution
Chapter 2 Installation
If the Megaplex-4100 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local distributor for more information.
The jumpers of a typical PS module (PS/DC or PS/AC) are identified in Figure 2-5.
BGND = FGND
YES
48/24 VDC Positive
Line Connected
to Frame Ground
48/24 VDC Positive
Line not Connected
to Frame Ground
NO
GND = FGND
YES
NO
NO
YES
NO
YES
Signal Ground
Connected
to Frame Ground
Signal Ground not
Connected
to Frame Ground
Figure 2-5. Typical PS Module, Location of Internal Jumpers
Note
•
Jumper designated GND=FGND. This jumper controls the connection between
the internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
•
Jumper designated BGND=FGND. This jumper controls the connection
between the positive (+) line of the external 24/48 VDC voltage and the
frame (enclosure) ground. The module is normally delivered with the jumper
set to YES. If necessary, you can set the jumper to NO to float the external
24/48 VDC positive line with respect to the frame ground. This is usually
necessary when the DC voltage is used to feed or ring voltages.
PS/DC and PS/AC modules can also use a positive supply voltage. In this case,
always disconnect BGND from FGND (set the jumper to NO).
If two power supply modules are installed, make sure that the internal
jumpers are set to the same position on both modules.
Caution Certain I/O modules may still cause BGND to be connected to FGND or GND, even
after setting the jumpers to NO. Refer to the Installation and Operation Manuals
of the modules installed in the chassis for proper setting of their ground-control
jumpers.
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-15
Chapter 2 Installation
Installation and Operation Manual
Installing a PS Module
Warning
Do not connect the power and/or ring and feed voltage cable(s) to a PS module
before it is inserted in the Megaplex-4100 chassis, and disconnect the cable(s)
from the module before it is removed from the chassis.
1. Make sure the module POWER switch is set to OFF.
2. Insert the PS module in the PS-A slot, and fasten it with the two screws.
3. Connect the power cable.
4. If an additional redundant module is used, install it in the PS-B slot.
Note
You can install a redundant module in an operating enclosure without turning the
Megaplex-4100 power off. In this case:
• First insert the module in its slot
• Connect its power cable
• For modules with POWER switch – set the module POWER switch to ON.
Removing a PS Module
1. For modules with POWER switch – set the module POWER switch to OFF.
2. Disconnect the power cable(s) connected to the module.
3. Release the two module screws
4. Pull the PS module out.
Installing CL Modules
Module Panels
The Megaplex-4100 chassis can be equipped with two CL modules. At any time,
only one module is active, and the other serves as hot standby.
Note
When only one CL module is installed in the chassis, it must always be installed in
slot CL-A.
Moreover, if CL module B is programmed, CL module A must also be programmed
in the chassis.
The following types of CL modules are offered:
2-16
•
CL.1: basic version, includes the chassis management and timing subsystem,
and a cross-connect matrix for TDM traffic
•
CL.1/155: in addition to the functions provided by the CL.1 version, includes
two SDH/SONET ports with STM-1/OC-3 interfaces, and the capability to route
traffic to/from the STM-1/OC-3 links to the modules installed in the chassis.
•
CL.1/155GbE: in addition to the functions provided by the CL.1/155 version,
includes two GbE ports (with SFPs or with copper interfaces, in accordance
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
with order), and has the capability to route packet traffic to/from modules
with Ethernet payload ports installed in the chassis.
•
CL.1/GbE: in addition to the functions provided by the CL.1 version, includes
two GbE ports (with SFPs or with copper interfaces, in accordance with
order), and has the capability to route packet traffic to/from modules with
Ethernet payload ports installed in the chassis.
Figure 2-6 shows typical CL module panels. Table 2-3 describes the functions of
the panel components.
E
T
H
D
C
E
L
O
S
O
N
A
C
T
CL.1
TX
E
X
L
I
N
K
C
LOS L
O
C
K
E
T
H
A
L
A
R
M
D
C
E
CL.1/155
L
O
S
O
N
A
C
T
ON LINE
E
X
L
I
N
K
C
L
O
C
K
E
T
H
L
I
N
K
C
O
N
T
R
O
L
LOS
A
L
A
R
M
D
C
E
L
I
N
K
1
G
b
E
2
L
I
N
K
2
ACT
ON LINE
L
O
S
O
N
A
C
T
ON LINE
E
X
L
I
N
K
CL.1/GbE with Copper
GbE Interfaces
LOS
LINK
LOS
C
L
O
C
K
E
T
H
L
I
N
K
C
O
N
T
R
O
L
ON LINE
LINK
A
L
A
R
M
ALM
ACT
G
b
E
1
RX
G
b
E
1
LOS
TX
ON LINE
ACT
TX
ALM
ACT
RX
LINK
LOS
RX
ON LINE
L
I
N
K
C
O
N
T
R
O
L
ON LINE
LINK
ALM
RX
ON LINE
L
I
N
K
2
C
L
O
C
K
ON LINE
TX
L
I
N
K
1
LOS
TX
ON LINE
RX
ALM
CL-1
155/GbE
TX
ON LINE
A
L
A
R
M
CL-1/GbE
CL-1
155
RX
CL-1
D
C
E
G
b
E
2
L
O
S
O
N
A
C
T
L
I
N
K
C
O
N
T
R
O
L
CL.1/155GbE with
Optical GbE Interfaces
Figure 2-6. Typical CL Module Panels
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-17
Chapter 2 Installation
Installation and Operation Manual
Table 2-3. Module CL, Panel Components
Item
Function
ON LINE Indicator
Provides the following indications:
ALM Indicator
•
Master/standby status: lights in green on the master (active) CL module,
and flashes slowly in green on the standby CL module
•
Test status: on the master (active) CL module, lights in yellow if a test is
being performed on the Megaplex-4100
•
Software downloading: flashes rapidly in green
•
Software decompression: flashes in yellow
On the master CL module, provides the following indications (see also NOTE
below):
•
Flashes in red when at least one major or critical alarm has been detected
in the Megaplex-4100.
•
Lights in red when alarms have been detected in the Megaplex-4100, but
the highest alarm severity is minor or warning.
On the standby CL module, this indicator is always off, even while an alarm
condition is present
CLOCK Connector
RJ-45 connector for the station clock input and output signals.
The built-in indicators (active only on the master CL module) provide the
following indications:
ON Indicator
Lights in green when the station clock port is configured as connected
LOS Indicator
Lights in red to indicate a loss-of-signal condition at the station clock port,
when configured as connected
CONTROL ETH Connector
RJ-45 connector for the CL 10/100BASE-T Ethernet management port.
The built-in indicators (active only on the master CL module) provide the
following indications:
LINK Indicator
Lights in green when the port is connected to an active Ethernet hub or switch
ACT Indicator
Lights in yellow when this port transmits and/or receives data
CONTROL DCE Connector
9-pin D-type female connector with RS-232 DCE interface, for connection to
system management. Connector pin allocation is given in Appendix A
ALARM Connector
9-pin D-type female connector, for connection to the Megaplex-4100 alarm
relay outputs, and an external alarm input. Connector pin allocation is given in
Appendix A
LINK 1, 2 Connectors
(CL.1/155 and CL.1/155GbE
versions only)
2-18
Sockets for installing SFP transceivers for the corresponding STM-1/OC-3 ports
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Item
Function
LINK Indicators – per port
(CL.1/155 and CL.1/155GbE
versions only)
Status indicators for STM-1/OC-3 ports. These indicators are active only when
the corresponding port is equipped with an SFP and configured as connected:
ON LINE Indicator
Lights in green when the corresponding port is active (that is, carries
SDH/SONET traffic, and there is no major alarm condition, nor any test on this
port).
Lights in yellow when a test is active on the port
LOS Indicator
Lights in red to indicate loss-of-signal at the corresponding port.
Any other alarm condition related to SDH/SONET traffic handled by the port is
indicated only by the CL general alarm (ALM) indicator
GbE 1, 2 Connectors
(CL.1/GbE and CL.1/155GbE
version only)
Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors
GbE 1, 2 Indicators – per
port (CL.1/155GbE version
only)
Status indicators for the corresponding GbE port.
These indicators are active only when the corresponding port is configured as
connected, and for optical ports – when the port is equipped with an SFP:
LINK Indicator
Lights in green when the port is connected to an active Ethernet hub or switch
ACT Indicator
Lights in yellow when the port transmits and/or receives data
Note
The ALM indicator functions listed in Table 2-3 are the default functions. When
the alarm masking and/or alarm inversion functions are used (see Chapter 4 for
details), the meaning of the various indications may change.
Preparing CL.1/155 and CL.1/155GbE Modules for Installation
Before installing a CL.1/155 or CL.1/155GbE module, you may have to install the
prescribed types of SFPs:
•
To install an SFP, use the procedure given in the Installing an SFP section.
•
To replace an SFP, use the procedure given in the Replacing an SFP section.
Installing an SFP
When installing an optical SFP in an operating module, be aware that it may
immediately start generating laser radiation.
Warning
Caution
During the installation of an SFP with optical interfaces, make sure that all optical
connectors are closed by protective caps.
Do not remove the covers until you are ready to connect optical fibers to the
connectors. Be aware that when inserting an SFP into a working module, the SFP
transmitter may start transmitting as soon as it is inserted.
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-19
Chapter 2 Installation
Installation and Operation Manual
Note
All the following procedures are illustrated for SFPs with optical interfaces.
However, the same procedures apply for SFPs with electrical (copper) interfaces.
³
To install the SFP:
•
Note
Lock the latch wire of the SFP module by lifting it up until it clicks into place,
as illustrated in Figure 2-7.
Some SFP models have a plastic door instead of a latch wire.
Figure 2-7. Locking the Latch Wire of a Typical SFP
1. Carefully remove the dust covers from the corresponding SFP socket of the
CL.1/155 module, and from the SFP electrical connector.
2. Orient the SFP as shown in Figure 2-6, and then insert the rear end of the
SFP into the module socket.
3. Push SFP slowly backwards to mate the connectors, until the SFP clicks into
place. If you feel resistance before the connectors are fully mated, retract the
SFP using the latch wire as a pulling handle, and then repeat the procedure.
4. If necessary, repeat the procedure for the other SFP.
Replacing an SFP
SFPs can be hot-swapped. It is always recommended to coordinate SFP
replacement with the system administrator. During the replacement of SFPs with
optical interfaces, only the traffic on the affected link is disrupted (the other link
can continue to carry traffic).
³
To replace an SFP:
1. If necessary, disconnect any cables connected to the SFP connectors.
2. Push down the SFP locking wire, and then pull the SFP out.
3. Reinstall protective covers on the SFP electrical and optical connectors.
4. Install the replacement SFP in accordance with the Installing an SFP section.
Installing a CL Module
CL modules are installed in the CL-A and/or CL-B slots (see also Note on page
2-16). When two CL modules are installed, redundancy is available. In this case,
the module installed in slot CL-A will be automatically selected as the master
2-20
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
module, provided that it operates normally and stores all the required
configuration parameters.
³
To install a CL module:
1. Check that the two fastening screws of the module are free to move.
2. Insert the CL module in its chassis slot and slide it backward as far as it goes.
3. Simultaneously press the extractor handles toward the center of the module
to fully insert its rear connector into the mating connector on the backplane.
4. Secure the CL module by tightening its two screws.
³
To interconnect the expansion ports of CL.1/155 modules:
•
Connect the expansion cable between the EX LINK connectors of the two
modules.
Removing a CL Module
³
To remove a CL module:
1. Fully release the two screws fastening the module to the chassis.
2. Simultaneously push the extractor handles outward, to disengage the rear
connector.
3. Pull the module out.
Replacing a CL Module During Equipment Operation –
Megaplex-4100 Chassis with two CL Modules
In a Megaplex-4100 equipped with two good CL modules, the standby module
can be removed/replaced with minimal disruption of Megaplex-4100 services:
when you replace the on-line CL module, the Megaplex-4100 will automatically
switch to the standby module, provided that module is OK.
The expected disruptions can be minimized in the following ways:
•
An active CL module also provides routing services and clock signals to other
Megaplex-4100 subsystems, as well as an out-of-band connection to
management. Simply removing the active CL module will therefore cause a
disruption, however short, in all the services provided by the Megaplex-4100
chassis. It is therefore important to prevent this type of disruption, and this
can be achieved by first switching (flipping) to the standby CL module before
replacing the on-line CL module.
•
For CL.1/155 and CL.1/155GbE modules, which have additional traffic
interfaces, removing a module always disconnects the traffic carried by the
active payload interfaces (GbE and/or STM-1/OC-3) located on the replaced
module. Note that these traffic interfaces can be active even on the standby
CL module, and therefore the only way to avoid traffic disconnections is to
use automatic protection for these interfaces: for example, APS can be used
to protect SDH/SONET traffic, and 1+1 redundancy can be used to protect
Ethernet traffic.
You can identify the active and standby modules by their ON LINE indicators.
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-21
Chapter 2 Installation
Installation and Operation Manual
Caution To prevent service disruption, check that the ON LINE indicator of the CL module
you want to remove is flashing. If not, use the supervisory terminal (or any other
management facility) to reset the module to be replaced, and wait for execution
of this command before continuing: this will cause the Megaplex-4100 to flip to
the other CL module within 50 msec.
³
To flip to the other CL module using the supervision terminal:
1. Identify the on-line CL module: this is the module with the lit ON LINE
indicator.
2. Whenever possible, connect the supervision terminal directly to the CONTROL
DCE connector of the on-line CL module, and log in as administrator.
3. Use the Configuration>System>Reset Device screen to send a reset command
to the module to be replaced.
4. Wait for the flipping to be executed. After it is executed, the ON LINE
indicator of the CL module the supervision terminal is connected to starts
flashing, while that of the other module stops flashing and lights steadily.
Note
The command will not be executed if a fault is detected in the module that is to
become the on-line module. In this case, the ON LINE indicators state will not
change.
5. You can now disconnect the supervision terminal, and remove the module.
6. After installing again a CL module in the slot of the removed module, you may
cause flipping to the original module by resetting the current on-line CL
module.
Replacing a CL Module During Equipment Operation –
Megaplex-4100 Chassis with Single CL Module
In a Megaplex-4100 equipped with a single CL module, before replacing the CL
module it is recommended that a good CL module of the same type be installed
in the free CL slot. The replacement can be temporary.
In this case, after inserting the additional CL module, first it is necessary to let it
update its database from the information provided by the existing CL module:
1. If necessary, program the additional module in the Megaplex-4100 database.
2. Enter the database update command, #, and then wait until the alarm CL DB
CHECKSUM IS DIFFERENT is off.
3. At this stage, continue in accordance with the steps listed above for a
Megaplex-4100 with two CL modules.
If the only CL module in the chassis is replaced, Megaplex-4100 services will
always be disrupted to some extent while no CL module is present. Therefore, be
prepared and perform the replacement as rapidly as possible.
Among other steps, make sure to upload the existing configuration database to a
host, using TFTP. After replacement is completed, download the database to the
new CL module, to continue normal operation in accordance with the previous
configuration.
2-22
Mounting the Megaplex-4100 Unit
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Installing I/O Modules
Install each I/O module in the prescribed I/O slot, in accordance with the
installation plan.
For installation instructions, refer to the corresponding I/O module Installation
and Operation Manual.
Installing Blank Panels
Install blank panels in all the chassis slots that are not occupied by modules.
Installing the Megaplex-4100 Enclosure
The Megaplex-4100 is intended for installation on shelves and racks. Do not
connect power to the enclosure before it is installed in the designated position.
Installing in 19” Rack
For rack installation, it is necessary to install two brackets to the sides of the
unit. As illustrated in Figure 2-8, you may install the brackets in two ways, to
orient the unit in accordance with your requirements (either with the
Megaplex-4100 front panel toward the front of the rack, or the module panels
toward the front).
Install Brackets Here if
You Want the Front Panel
toward the Front of the Rack
Figure 2-8. Attachment of Brackets to Megaplex-4100 Case for Installing in 19” Rack
Megaplex-4100 Ver. 2.0
Mounting the Megaplex-4100 Unit
2-23
Chapter 2 Installation
Installation and Operation Manual
Installing in 23” Rack
The same set of brackets can also be used to install the Megaplex-4100 unit in a
23” rack. Figure 2-9 shows how to attach the brackets for installation in 23”
racks (only front installation is shown in this figure).
Figure 2-9. Attachment of Brackets for Installation of Megaplex-4100 Unit in 23” Rack
After attaching the brackets, fasten the enclosure to the rack by four screws
(two on each side).
After installing the enclosure, check and install the required modules, in
accordance with the installation plan.
2.6
Connecting to Megaplex-4100
Grounding the Megaplex-4100
Warning
2-24
Before connecting any cables and before switching on this instrument, the
protective ground terminals of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Make sure that only fuses of the required rating are used for replacement. The
use of repaired fuses and the short-circuiting of fuse holders is forbidden.
Whenever it is likely that the protection offered by fuses has been impaired, the
instrument must be made inoperative and be secured against any unintended
operation.
Connecting to Megaplex-4100
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Connect a short, thick copper braid between the grounding screw on each PS
module panel and a nearby grounding point.
Connecting to Power
Caution Megaplex-4100 does not have a power on/off switch. Therefore, when
Megaplex-4100 is equipped with PS modules without power on/off switch, it will
start operating as soon as power is applied to at least one of its PS modules. It is
recommended to use an external power on/off switch to control the connection
of power to the Megaplex-4100. For example, the circuit breaker used to protect
the supply line to the Megaplex-4100 may also serve as the on/off switch.
Power should be connected only after completing cable connections.
Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Note
When redundant power supply modules are used, it is recommended to connect
the power cables to outlets powered by different circuits.
Connecting to External Feed and Ring Voltages
External feed and ring voltages are required by voice modules and by ISDN
interface modules.
The recommended source for external voltages is the Ringer-2200N offered by
RAD. The Ringer-2200N is a standalone unit intended for rack mounting, capable
of providing power for up to twenty voice channels. Refer to the Ringer-2200N
Installation and Operation Manual for connection instructions.
Caution
Turn on the Ringer-2200N external voltage source, or connect the external
voltages, only after the Megaplex-4100 is turned on.
Turn off the Ringer-2200N external voltage source, or disconnect the external
voltages, only after the Megaplex-4100 is turned off.
Connecting Cables to Megaplex-4100 CL Ports
This section provides information on the connections required by the various CL
module versions.
³
To connect to the CONTROL DCE port:
The connections to the CONTROL DCE connector are made as follows:
•
Connection to a supervision terminal with 9-pin connector: by means of a
straight cable (a cable wired point-to-point).
•
Connection to modem with 9-pin connector (for communication with remote
supervision terminal): by means of a crossed cable.
Additional connection options are presented in Appendix A.
Megaplex-4100 Ver. 2.0
Connecting to Megaplex-4100
2-25
Chapter 2 Installation
³
Installation and Operation Manual
To connect to an ASCII terminal:
1. Connect the male 9-pin D-type connector of CBL-DB9F-DB9M-STR straight
cable available from RAD to the CONTROL DCE connector.
2. Connect the other connector of the CBL-DB9F-DB9M-STR cable to an ASCII
terminal.
Caution
³
Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to supervisory
terminal port.
To connect to a management station, Telnet host or Web browser:
The link to network management stations using SNMP, to Telnet hosts and/or
Web browsers is made to the RJ-45 connector designated CONTROL ETH.
You can use any standard cable (straight or crossed) to connect to any type of
Ethernet port (hub or station).
³
To connect to the ALARM connector:
The connection to the ALARM connector is made by means of a cable provided by
the customer, in accordance with the specific requirements of each site. Refer to
Appendix A for connector pin functions.
Caution
To prevent damage to the internal alarm relay contacts, it is necessary to limit, by
external means, the maximum current that may flow through the contacts
(maximum allowed current through closed contacts is 1A). The maximum voltage
across the open contacts must not exceed 60 VDC.
Connecting Cables to CL.1/155 and CL.1/155GbE SDH Links
Connection Instructions for Optical Cables
The optical fibers intended for connection to equipment installed in a rack should
pass through fiber spoolers, located at the top or bottom of the rack, in
accordance with the site routing arrangements (overhead or under-the-floor
routing). The spoolers must contain enough fiber for routing within the rack up to
the CL optical connectors, and for fiber replacement in case of damage (splicing
repairs).
From the spoolers, the optical fibers should be routed through cable guides
running along the sides of the rack frame to the level of the equipment to which
they connect.
When connecting optical cables, make sure to prevent cable twisting and avoid
sharp bends (unless otherwise specified by the optical cable manufacturer, the
minimum fiber bending radius is 35 mm). Always leave some slack, to prevent
stress. RAD recommends installing plastic supports on each cable connector:
these supports determine the fiber bending radius at the connector entry point
and also prevent stress at this point.
2-26
Connecting to Megaplex-4100
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 2 Installation
Caution Make sure all the optical connectors are closed at all times by the appropriate
protective caps, or by the mating cable connector.
Do not remove the protective cap until an optical fiber is connected to the
corresponding connector, and immediately install a protective cap after a cable is
disconnected.
Before installing optical cables, it is recommended to clean thoroughly their
connectors using an approved cleaning kit.
³
To connect optical cables to the CL.1/155 and CL.1/155GbE SDH links:
1. For each optical interface, refer to the site installation plan and identify the
cables intended for connection to the SFP serving the corresponding
interface.
2. Where two fibers are used, pay attention to TX and RX connections, and
leave enough slack to prevent strain:
ƒ
Connect the prescribed transmit fiber (connected to the receive input of
the remote equipment) to the TX connector of the SFP.
ƒ
Connect the prescribed receive fiber (connected to the transmit output of
the remote equipment) to the RX connector of the SFP serving the same
interface.
Connecting Coaxial Cables to CL.1/155 and CL.1/155GbE SDH
Links
The SFPs offered by RAD for the CL.1/155 SDH links are equipped with two
mini-BNC connectors, one identified as TX (transmit output) and the other as RX
(receive input).
To convert to BNC connectors, RAD offers the CBL-MINIBNC-BNC adapter cable,
terminated in two BNC connectors.
³
To connect coaxial cables to the CL.1/155 and CL.1/155GbE SDH links:
1. For each electrical interface, identify the cables intended for connection to
this interface in accordance with the site installation plan.
Note
If you are using the CBL-MINIBNC-BNC adapter cable, first connect its mini-BNC
connectors to the corresponding connectors of the SDH links (note TX and RX
designations), and then proceed with the connection of the external cables.
2. Connect the prescribed coaxial transmit cable (connected to the receive input
of the remote equipment) to the TX connector of the interface.
3. Connect the prescribed coaxial receive cable (connected to the transmit
output of the remote equipment) to the RX connector of the same interface.
Connecting to I/O Modules
Refer to corresponding module Installation and Operation Manual.
Megaplex-4100 Ver. 2.0
Connecting to Megaplex-4100
2-27
Chapter 2 Installation
2-28
Connecting to Megaplex-4100
Installation and Operation Manual
Megaplex-4100 Ver. 2.0
Chapter 3
Operation
This Chapter provides general operating instructions and preliminary configuration
instructions for Megaplex-4100 units.
The information presented in this Chapter is organized as follows:
•
Turning on: Section 3.1
•
Indications: Section 3.2
•
Default settings: Section 3.3
•
Configuration and management alternatives for Megaplex-4100: Section 3.4
•
Turning off: Section 3.5
3.1
Turning Megaplex-4100 On
When turning the Megaplex-4100 on, it is useful to monitor the power-up
sequence.
You can monitor the power-up sequence using any standard ASCII terminal (dumb
terminal or personal computer emulating an ASCII terminal) equipped with an
RS-232 communication interface (same terminal that can be used to control the
Megaplex-4100 operation).
³
To monitor the Megaplex-4100:
1. Configure the terminal for 115.2 kbps, one start bit, eight data bits, no
parity, and one stop bit.
2. Select the full-duplex mode, echo off, and disable any type of flow control.
Make sure to use VT-100 terminal emulation: using a different terminal type
will cause display problems, for example, the cursor will not be located at the
proper location, text may appear jumbled, etc.
³
To prepare the Megaplex-4100 for first-time turn-on:
1. Before first-time turn-on, inspect Megaplex-4100 installation and check that
the required cable connections have been correctly performed in accordance
with Chapter 2.
3. To monitor the Megaplex-4100 during power up and to perform preliminary
configuration procedures, connect a terminal to the CONTROL DCE connector
of the CL module installed in Megaplex-4100 slot CL-A (this module will be, by
default, the active CL module). Use a straight (point-to-point) cable.
Megaplex-4100 Ver. 2.0
Turning Megaplex-4100 On
3-1
Chapter 3 Operation
Note
³
Caution
Installation and Operation Manual
You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CL modules installed in the Megaplex-4100, using a Y-cable.
To turn the Megaplex-4100 on:
When an external feed and ring voltage source is connected to the PS modules
installed in the Megaplex-4100, always turn that source on only after the PS
module(s) have been turned on.
1. Set the POWER switch(es) on the rear panel(s) of the PS module(s) to ON.
If you are using DC-powered PS modules without a POWER switch, it is
necessary to use an external power ON/OFF switch, for example, the circuit
breaker used to protect the power lines.
2. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
ƒ
After a few seconds, Megaplex-4100 starts decompressing its software.
ƒ
After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as the Megaplex-4100
performs its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4100. A typical display is shown in Figure 3-1.
Loading ...
Decompressing to RAM.
Processing archive: FLASH
Extracting MPCLX.BIN
.................................................................. CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
Figure 3-1. Typical Power-Up Display
Note
The name of the file displayed on your Megaplex-4100 screen may be different.
4. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active (master) CL module lights in green and
that of the other CL module flashes slowly in green. At this stage, the
indicators display the actual Megaplex-4100 status.
3-2
Turning Megaplex-4100 On
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
3.2
Chapter 3 Operation
Indications
The indications provided during normal operation are described below.
Note
For a complete description of Megaplex-4100 indicator functions, refer to
Chapter 2.
System Indications
1. As long as the Megaplex-4100 is powered, all its POWER indicators light
steadily.
2. The ON LINE indicator of one of the CL modules must light steadily.
3. The front panel TEST indicator must be off, unless a test has been activated
on the Megaplex-4100 (in this case, the ON LINE indicator of the master CL
module also lights in yellow).
4. The front panel ALARM indicators and the CL ALM indicators must be off.
However, they may flash or light, as long as one or more of the
Megaplex-4100 ports is not connected to operational equipment.
CONTROL ETH Interface Status Indications
If a Megaplex-4100 CONTROL ETH port is not yet connected to an active LAN, the
corresponding LINK and ACT indicators are off.
After connecting the CONTROL ETH port to an active LAN, the corresponding LINK
indicator must light. The ACT indicator of the port will flash, or appear to light
steadily, in accordance with the traffic.
SDH/SONET Interface Status Indications (CL.1/155 and CL.1/155GbE
Only)
The ON LINE indicator lights in green to indicate that the corresponding link is
active.
If an SDH/SONET port is not yet connected to operational equipment, the
corresponding port LOS indicator lights. However, if the equipment at the other
end of the link is operational and the link is physically connected, the port LOS
indicator must turn off.
GbE Interface Status Indications (CL.1/GbE and CL.1/155GbE Only)
If a GbE port is not yet connected to an active LAN, the corresponding LINK and
ACT indicators are off.
After connecting the GbE port to an active LAN, the corresponding LINK indicator
must light. The ACT indicator of the port will flash, or appear to light steadily, in
accordance with the traffic.
Megaplex-4100 Ver. 2.0
Indications
3-3
Chapter 3 Operation
Installation and Operation Manual
CL CLOCK Interface Status Indications
The ON indicator lights when the corresponding station clock interface is enabled
and connected to an operational clock source. In this case, the LOS indicator of
the corresponding station clock interface must be off.
3.3
Default Settings
Table 3-1 lists the Megaplex-4100 factory default parameters.
For factory default parameters of I/O modules, refer to the corresponding module
Installation and Operation Manual.
Table 3-1. Megaplex-4100 Factory Default Parameters
Parameter
Factory Default Value
Path
Admin Status
Down
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Admin Status
Down
Configuration>Physical Layer>CL>
CL-A(B)>Ethernet>All Ports(GBE 1,
GBE 2)
Admin Status
Up
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(2)
Alarm ID[1 - 2104]
3
Configuration>System>Alarms
Configuration>Trap Masking
Auto Negotiation
Disable
Configuration>Physical Layer>CL>
CL-A(B)>Ethernet>All Ports(GBE 1,
GBE 2)
Baud Rate
115.2 KBPS
Configuration>System>Control
Port>Serial Port
BP
1
Configuration>Applications>Ethernet
Services>Flows>Bridge Port MappingFlow
BP User Name
Empty string
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
Clock Rate
2048 KBPS
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Contact Person
Name of contact person
Configuration>System>Management>
Device Info
C-VLAN ID
1
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
C-VLAN Type
Unaware
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
3-4
Default Settings
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Parameter
Factory Default Value
Path
Default Gateway
0.0.0.0
Configuration>System>Management>
Host IP
Device Name
Empty string
Configuration>System>Management>
Device Info
EED Threshold
1E-3
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(2)
Fault Propagation
Enable
Configuration>System>Fault
Propagation
Flow
251
Configuration>System>Management>
Flow
Flow Control
Disable
Configuration>Physical Layer>CL>
CL-A(B)>Ethernet>All Ports(GBE 1,
GBE 2)
Frame Structure
STM-1
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Card
Configuration
In Band Management
Off
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(Link 2,
All Links)>DCC Configuration
Interface Type
Balance
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
IP Address
0.0.0.0
Configuration>System>Management>
Host IP
Line Code
HDB3
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Managers ID
First free index number
Configuration>System>Management>
Manager List
Object ID
radMP4100
Configuration>System>Management>
Device Info
Password
1234
Configuration>System>Control
Port>Serial Port>Change Password
Port
First bridge port of first slot available for
connection to flow
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
Profile Number
1
Configuration>System>Signaling
Profile
Rate
100 Mbps
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
RDI on Fail
Enable
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(2)
Megaplex-4100 Ver. 2.0
Default Settings
3-5
Chapter 3 Operation
Installation and Operation Manual
Parameter
Factory Default Value
Path
RDI on path trace
Disable
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Card
Configuration>Common PDH LVC
Parameters
RDI on signal label
Disable
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Card
Configuration>Common PDH LVC
Parameters
Read Community
public
Configuration>System>Management>
Host IP
Rx Busy[0 - f]
0F
Configuration>System>Signaling
Profile
Rx Gain Limit
Short Haul
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Rx Idle[0 - f]
00
Configuration>System>Signaling
Profile
SD Threshold
1E-6
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(2)
Security Timeout
None
Configuration>System>Control
Port>Serial Port
Slot
First slot on which a bridge port is
available for connection to flow
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
SNMP
Enable
Configuration>System>Management>
Mng Access
SNMPv3
Disabled
Source
Internal
Configuration>System>Management
Configuration>System>Clock Source
Speed & Duplex
1000 MBPS Full Duplex
Configuration>Physical Layer>CL>
CL-A(B)>Ethernet>All Ports(GBE 1,
GBE 2)
SP-VLAN
0
Configuration>Applications>Etherne
Services>Flows>Bridge Port MappingFlow
SSM
Disable
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Subnet Mask
0.0.0.0
Configuration>System>Management>
Host IP
Sys Description
Depends on equipment version
Configuration>System>Management>
Device Info
Enable
Configuration>System>Management>
Mng Access
Telnet
3-6
Default Settings
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Parameter
Chapter 3 Operation
Factory Default Value
Path
Configuration>Physical Layer>CL>
CL-A(B)>Station Clock
Transmit Timing Source
> (System)
Trap Community
public
Configuration>System>Management>
Host IP
Trap Send
Yes
Configuration>System>Alarms
Configuration>Trap Masking
Tx Clock Based on SSM
Yes
Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Card
Configuration
VLAN ID [1 - 4094]
100
Configuration>System>Management>
Flow
VLAN Priority Tag [0 7]
7
Configuration>System>Management>
Flow
WEB
Enable
Configuration>System>Management>
Mng Access
private
Configuration>System>Management>
Host IP
Write Community
3.4
Configuration and Management Alternatives
The Megaplex-4100 configuration activities can be performed by means of the
following:
Note
•
Supervision terminal
•
Telnet
•
Web browser, using the ConfiguRAD utility
•
SNMP-based network management systems, e.g., the RADview network
management system (refer to the RADview User's Manual for instructions).
Megaplex-4100 also supports SNMPv3, which provides authentication and privacy
capabilities that replace the basic SNMP community-based authentication
available under SNMPv1.
The user can select whether to enable management by means of Telnet, SNMP,
and/or Web browsers: only the supervision terminal is always able to configure
the Megaplex-4100.
The capabilities of the four options listed above are similar, except that before
using Telnet, Web browsers and/or network management systems, it is necessary
to perform preliminary configuration using the supervision terminal.
The Megaplex-4100 supports simultaneous management sessions: it is user’s
responsibility to prevent access conflicts and configuration errors that may occur
when multiple users simultaneously access the same equipment.
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-7
Chapter 3 Operation
Installation and Operation Manual
Access Levels for Configuration and Management
Megaplex-4100 supports three access levels, which determine the functions the
users can perform using supervisory terminals, Telnet hosts, and Web browsers.
Note
When SNMPv3 security features are enabled, the term user refers to an SNMP
management station using part, or all of the SNMPv3 security features, and the
users’ authorizations are determined by configuring the parameters related to
the view-based security model (VACM) aspect of SNMPv3. Refer to Section 0 and
Chapter 4 for details.
The access level is determined by the user name, and the protection against
unauthorized access is conferred by passwords. The access levels supported by
Megaplex-4100 are described in Table 3-2.
Table 3-2. Megaplex-4100 Access Levels
Access Level
User Name
Menus Accessible at this Level
Administrator
su
All the menus
Technician
tech
Alarm Configuration (on Configuration menu),
Inventory, Monitoring, Diagnostics
Monitor
user
Inventory, Monitoring
The default passwords for all the levels are identical, 1234. The passwords can be
changed at the administrator level, using Configuration>System>Control Port>
Serial Port>Change Password.
Notes
P
• The password is not case-sensitive.
• If the administrator password has been changed and is not known, contact
RAD Technical Support Department for help.
Working with Supervision Terminal
Configuration activities are performed by means of an ASCII terminal (or a PC
running a terminal emulation program) directly connected to one of the CL
CONTROL DCE connectors. A supervision terminal also permits performing the
preliminary configuration that enables other types of management access.
Any standard ASCII terminal (dumb terminal or personal computer emulating an
ASCII terminal) equipped with an RS-232 communication interface can be used to
configure and control the Megaplex-4100 operation.
The software necessary to run the Megaplex-4100 supervision program is
contained in the Megaplex-4100 CL modules. Moreover, the Megaplex-4100 CL
modules store all the configuration information generated or altered during the
communication with the terminal: no information is stored in the terminal.
3-8
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 3 Operation
For proper display of screens on terminals, you must:
1. Select a fixed-pitch system font for the display. Use your operating system
documentation to find how to select a proper font.
2. Configure the terminal utility to use VT-100 terminal emulation. If you are
using the Hyper Terminal utility available with Windows(™), configure the
utility to use the 132-column mode (Properties > Settings > Terminal Setup >
132 column mode).
³
To log in with a supervision terminal:
1. Connect a terminal to one of the Megaplex-4100 CONTROL DCE connectors.
2. If necessary, turn the Megaplex-4100 on as described in Section 3.1.
Note
• The CONTROL DCE port default data rate can be configured for any standard
rate in the range of 0.3 to 115.2 kbps (the factory-default data rate is
115.2 kbps).
• If the terminal is configured to use a word format differing from the CONTROL
DCE port (one start bit, 8 data bits, no parity and one stop bit), you may see
only random strings of characters, or there will be no response to the pressing
of the <Enter> key. Make sure you use the correct word format.
3. If the terminal has been configured to use the default parameters, after the
power-up initialization it will display the cursor (a blinking underscore) at the
home position of the screen (top left-hand corner).
4. Establish communication with the Megaplex-4100 by pressing <Enter> several
times in sequence (this enables automatic rate identification). You may see a
few status messages, and then you will see the log-in screen. A typical screen
is shown in Figure 3-2.
MP-4100
USER NAME:
PASSWORD:
ESC - clear; & - exit
0 M/ 1 C
-----------------------------------------------------------------------------
Figure 3-2. Terminal Log-In Screen
5. If the Megaplex-4100 default user name and password have not yet been
changed, log in as follows:
Megaplex-4100 Ver. 2.0
ƒ
Type the default user name, su, and then press <Enter>.
ƒ
Type the default password, 1234, and then press <Enter>.
Configuration and Management Alternatives
3-9
Chapter 3 Operation
Installation and Operation Manual
6. If your password is accepted, you will see the Megaplex-4100 main menu. A
typical main menu screen is shown in Figure 3-3.
If your log-in is not accepted, after pressing <Enter> the user name and
password fields are cleared. In this case, try entering the user name and
password again.
MP-4100
Main Menu
1.
2.
3.
4.
5.
Inventory
Configuration
Monitoring
Diagnostics
File Utilities
>
>
>
>
>
>
Please select item <1 to 5>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output;
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 3-3. Megaplex-4100 Main Menu
Preliminary Configuration Sequence
The purpose of the preliminary configuration session is to prepare the minimal
set of parameters needed to manage the Megaplex-4100 using a supervision
terminal.
In particular, during preliminary configuration you can enable access by Telnet
hosts and Web browsers. However, after the preliminary configuration,
management access is possible only by hosts that are attached to a LAN directly
connected to the CONTROL ETH (Ethernet) port of the active CL module, or at a
remote location from which IP communication to the CL module Ethernet ports is
possible.
Note
To enable management access to the Megaplex-4100 from any relevant location,
it is necessary to fully configure the Megaplex-4100: only full configuration can
permit management traffic to reach the Megaplex-4100 via inband paths.
The steps usually included in the preliminary configuration, as necessary when
starting from the factory defaults, are described in Table 3-3.
For detailed operating instructions, refer to the Chapter 4 section describing each
activity.
3-10
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Table 3-3. General Megaplex-4100 Configuration Sequence
Step Action
Using …
1
Select the default database
Configuration>DB Tools>Default DB
2
If the Megaplex-4100 is equipped with all the
necessary modules, load the hardware
configuration.
Configuration>DB Tools>Load HW
Alternatively, configure the modules and then Configuration>System>Card Type
reload the factory default parameters
installed in the Megaplex-4100. You can also
program modules not yet installed in the
chassis
3
Configure the preliminary set of IP
communication parameters
Configuration>Quick Setup
4
Configure CONTROL DCE port parameters
Configuration>System>Control Port>Serial Port
5
Configure CONTROL ETH port parameters
Configuration>System>Control Port>ETH
6
Configure Megaplex-4100 management agent Configuration>System>Management>Host IP
7
Configure management access
Configuration>System>Management>Mng Access
8
Configure specific management stations
Configuration>System>Management>Manager List
9
Set Megaplex-4100 real-time clock
Configuration>System>Date & Time
10
Configure Megaplex-4100 signaling profiles
Configuration>System>Signaling Profile
11
Configure the CL modules physical ports:
•
Station clock ports
•
SDH/SONET ports (make sure to configure
the frame structure)
•
Configuration>Physical Ports>CL>CL-A, CL-B>ETHERNET
GbE ports (make sure to configure the GbE
port redundancy parameters)
Configuration>Physical Ports>CL>CL-A, CL-B>Station
Clock
12
Configure the physical ports of the I/O
modules (E1, T1, SHDSL, Ethernet, etc.)
13
Configure the virtual ports on the SDH/SONET
ports of the CL modules:
14
Configuration>Physical Ports>CL>CL-A, CL-B>
SDH/SONET
Configuration>Physical Ports>I/O>I/O-1 to I/O-10
•
PDH ports
Configuration>Virtual Ports>CL>PDH
•
High-order VCs
Configuration>Virtual Ports>CL>HVC>CL-A, CL-B
Configure the virtual ports of the I/O modules Configuration>Virtual Ports>I/O>I/O-1 to I/O-10
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-11
Chapter 3 Operation
Installation and Operation Manual
Step Action
15
Using …
Configure Ethernet services in the following
order:
•
Configure the prescribed bundles
on I/O module ports, and on PDH ports
•
Configure the prescribed virtually
Configuration>Virtual Ports>CL>VCAT>CL-A, CL-B
concatenated groups on SDH/SONET links,
and where necessary, also configure
virtually concatenated group redundancy
•
Configure the Ethernet flows
Configuration>Virtual Ports>Bundles
Configuration>Applications>Ethernet Services>Flows
16
Configure the inband management flow
Configuration>System>Management>Flow
17
Configure path protection parameters for
each virtual and I/O module internal port
Configuration>Virtual Ports>IO
18
Configure clock sources and timing flow
Configuration>System>Clock Source
19
Configure APS groups
Configuration>System>APS
20
Configure internal cross-connections
Configuration>System>TS Assignment
21
Configure Megaplex-4100 internal mapping
Configuration>System>Mapping
22
Configure fault propagation
Configuration>System>Fault Propagation
23
Configure Megaplex-4100 alarm handling
Configuration>System>Alarms Configuration
24
Save the final configuration as a database
Configuration>DB Tools>Update DB
25
If necessary, prepare additional databases
To start from an existing database, use
Configuration>DB Tools>Load DB. Repeat the relevant
steps as needed to create a new database
Note
• All the following menus are reached after opening the Configuration menu.
• During the configuration procedure, save the changed values, but update the
database only after completing the configuration activities.
³
Select the default database:
1. Open the DB Tools menu.
2. Select Default DB.
3. Select the default database number, 1.
³
Initialize the Megaplex-4100:
1. Select Load HW on the DB Tools menu.
2. Select Update DB on the DB Tools menu to activate the default configuration
for all the hardware installed in the Megaplex-4100. When prompted to
confirm, type Y.
3-12
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
The new database takes effect immediately. You will see the message
Configuration File Update is in Process while the database is saved in the CL
module flash memory.
³
Reload the factory defaults:
1. Select Factory Default on the Configuration>System menu.
³
To program modules not yet installed in the Megaplex-4100 chassis:
1. Select Card Type on the System menu.
2. Move the cursor to the desired slot.
3. The selections supported for each slot are automatically displayed under the
slots table. Type the item number corresponding to the desired selection and
then press <Enter>.
4. Repeat Steps 2, 3 for each slot.
³
Configure the serial port parameters:
1. Open Control Port on the System menu.
2. Open Serial Port on the Control Port submenu.
3. Select the desired value for Speed (recommended value: 115200).
³
Configure the Megaplex-4100 management agent parameters:
1. Open Host IP on the System>Management menu.
2. Configure the prescribed values for the following parameters:
ƒ
IP Address. Enter the IP address of the Megaplex-4100 management
agent, using the dotted-quad format (four groups of digits in the range
of 0 through 255, separated by periods).
ƒ
IP Mask. Enter the IP subnet mask of the Megaplex-4100 management
agent. Make sure to select a subnet mask compatible with the selected IP
address, and whose binary representation consists of consecutive
“ones”, followed by the desired number of consecutive “zeroes”.
ƒ
Default Gateway. Specify the IP address (usually an IP router port) to
which the Megaplex-4100 management agent will send packets when the
destination IP address is not within the subnet specified in the Mask field.
Type the desired IP address, using the dotted-quad format. Make sure
that the IP address is within the subnet of the host IP address. The
default value, 0.0.0.0, means that no default gateway is defined.
ƒ
Communities: to configure SNMP management when SNMPv3 is Disabled,
enter the prescribed Read, Write, and Trap community names, or leave
the defaults unchanged.
When SNMPv3 is Enabled¸ the community fields are not displayed.
Note
The community names are case-sensitive.
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-13
Chapter 3 Operation
³
Installation and Operation Manual
Configure the Ethernet port parameters:
1. Open Control Port on the System menu.
2. Open ETH on the Control Port submenu.
3. For each CL module, select UP for Admin Status. You may also assign a user
name (up to 10 characters) to each port.
4. At this stage, you may leave None for Routing Protocol.
³
Configure management access options:
1. Open Management on the System menu.
2. Open Mng Access on the Management submenu.
3. Select Enable or Disable, as prescribed, for SNMP, Telnet and Web.
³
Configure specific management stations:
1. Open Management on the System menu.
2. Open Manager List on the Management submenu.
3.
Type a (add) and then press <Enter> to start the configuration of a new
management station.
4. Select the prescribed values for each parameter.
5. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new station. To display the Manager List
again, press ESC.
6. Repeat the process until all the desired management stations have been
defined.
³
Set the Megaplex-4100 real-time clock:
1. Open the System menu.
2. Select Date & Time on the System menu.
3. Open Set Date Format screen, and select the desired date format.
Note
dd stands for day, mm for month and yyyy for year.
4. When done, save and then set each component of the time-of-day and date.
To change, select the desired item and then type the desired value. Confirm
each change by pressing <Enter>.
Notes
• Time must be entered in the 24-hour format.
• It is recommended to set the time about one minute beyond the desired time,
and then press <Enter> at the correct instant.
³
Save the changes to the default database:
•
On the DB Tools menu, select Update DB to save and activate the new
configuration.
You may also use the % shortcut.
3-14
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Configuring Megaplex-4100 via Supervisory Terminal
Megaplex-4100 operating mode and all of its functions are controlled by a set of
configuration parameters organized as a database, which is stored in the flash
memory on the Megaplex-4100 CL module. The parameters in the database are
selected by the user in accordance with the requirements of each specific
application.
To provide a starting point for the user, RAD provides a fixed set of
factory-default parameters. The factory defaults are not modified by user
configuration activities, and therefore these factory-defaults can be reloaded
whenever needed.
The preparation of the desired set of configuration parameters is made in
accordance with a set of rules, which together form the Megaplex-4100
supervision utility, or user interface. The supervision utility is used to
communicate with the central control subsystem of the Megaplex-4100 located in
the CL modules, using a supervision terminal connected to the control port of the
CL module. The same user interface can also be used by Telnet hosts.
Alternative ways to change the configuration parameters are by means of SNMP
management stations, for example, RADview, and Web browsers.
Preparing New Configuration Parameters
Normally, only one database is needed to store the configuration parameters;
when necessary, one or more additional databases with alternative
configurations may also be prepared and stored in the Megaplex-4100 flash
memory. Megaplex-4100 databases are assigned index numbers in the range of 1
to 10.
At any time, one of the stored databases (the database assigned index number
1) serves as the active (online) database, and it is also the database
automatically loaded upon power-up. Since the active database is stored in flash
memory, the latest configuration parameters are always available upon power-up.
During the preparation of configuration parameters, the central control
subsystem of the Megaplex-4100 dedicates a section of its RAM, called editing
buffer, to this process. The editing buffer contains a copy of a user-selected
database (any of the databases stored by the Megaplex-4100, including the
currently-active database), and only this copy is modified by the commands
entered by the user. Therefore, you can make configuration changes and cancel
them as required without affecting the traffic flow through the Megaplex-4100.
Any changes to configuration parameters remain temporary, and thus are lost if
Megaplex-4100 is powered off or reset, until they are saved to one of the
databases in Megaplex-4100 flash memory. You can decide in which database to
save the changes: this also determines whether the changes take effect
immediately or not.
Two options are available:
•
Megaplex-4100 Ver. 2.0
Normally, changes are saved to the active, or online, database. In this case,
the changes are also automatically activated, that is, Megaplex-4100 starts
using the new parameters. As mentioned above, the number of the active
Configuration and Management Alternatives
3-15
Chapter 3 Operation
Installation and Operation Manual
database is always 1, irrespective of the number of the database loaded into
the edit buffer as a basis for changes.
•
Note
Alternatively, you can specify the number of another database, using the
Update DB command, in which to store the edit buffer contents. If the
database whose index is specified in the Update DB command is not yet
stored in the flash memory, a database with this index number is created and
the edit buffer contents are stored in it.
The storage space used by databases increases after each change. Sometimes,
the remaining storage space is not sufficient to save the updated database, and
you will see Save of Configuration File Failed. In this case, it is necessary to delete
unused databases.
Note that alternative databases may be assigned any desired number, except 1,
because 1 is reserved for the active database.
When preparing alternative databases, it is convenient to change the default
database, that is, the database which is updated when you use the shortcut
% - DB Update:
•
If you do not select a specific default database, the shortcut updates the
active database (database 1).
•
If you specify another database stored in the flash memory as default, the
shortcut updates the default database. In this case, after preparing the
alternative database, it is recommended to return the default to database 1.
Validity Checks
The Megaplex-4100 control subsystem automatically checks the validity of each
new subset of parameters selected by the user as soon as an attempt to save
them is made, alerts the user to potential conflicts, and rejects erroneous
selections.
The “sanity check” is performed on the configuration parameters stored in the
editing buffer.
This function provides messages which help identify incomplete configuration,
unconnected timeslots, conflicting parameters, inconsistent selection of related
parameter values, etc., so that the parameters can be corrected before
proceeding.
Only after all the validity and sanity checks are successfully passed, can the user
save the new (or modified) set of configuration parameters as a database (this is
made by means of the Update DB command). If the new set is saved under the
number of the active configuration database, the Megaplex-4100 system will
start operating in accordance with the new configuration.
Since the last validated sets of configuration parameters are stored in flash memory,
Megaplex-4100 configuration is not affected when the power is turned off.
However, any changes not yet saved are lost if the Megaplex-4100 is reset or
powered down.
3-16
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Megaplex-4100 Power-up Process
Upon turn-on, the Megaplex-4100 central control subsystem always loads
database 1, and checks the validity of the configuration data. If everything is OK,
it loads the data into the working memory and reconfigures the system
accordingly. Therefore, the Megaplex-4100 is ready for operation in accordance
with the last configuration stored in database 1 immediately after power is
applied.
If necessary, after power-up another database can be loaded by means of the
Load DB command, and then activated by means of the shortcut % - DB Update.
This database will be assigned index number 1 (that is, will become database 1).
If the configuration data is not valid, the database will not be activated; instead,
a database with factory-default values will be activated. This database will be
assigned index number 1 (that is, will become database 1).
After the operating parameters have been loaded, a process called configuration
set-up, the Megaplex-4100 no longer requires operator attendance.
Organization of Terminal Screens
The Megaplex-4100 is managed via a simple, menu-driven utility that uses a basic
terminal user interface. Figure 3-4 shows a typical utility screen with most types
of items.
MP-4100
Configuration>Physical Ports>IO>I/O 1 (M8E1)>Link 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Admin Status
User Name
Line Type
Idle Code [0 - ff]
Redundancy
Rx Gain
Data OOS [0 - ff]
Restoration Time
Cross Connect
In Band Management
Interface Type
Time Slot Assignment
...
>
...
>
>
...
>
>
(Up)
()
(G.732N-CRC4)
(7F)
(None)
(Short Haul)
(00)
(CCITT)
(DS0)
(Off)
(Balance)
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 3-4. Typical Megaplex-4100 Supervision Utility Screen
Each screen includes the following main items (refer to Figure 3-4 for typical
appearance):
•
Header: identifies the device being configured (Megaplex-4100).
•
Status indicator: status indicators may appear in the top right-hand corner to
indicate one or more of the following conditions:
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-17
Chapter 3 Operation
•
Installation and Operation Manual
ƒ
Alarm Indicator (e.g., MAJ): indicates highest severity of the alarm
conditions present in the Megaplex-4100.
ƒ
B followed by a three-digit number: indicates the number of messages
currently stored in the alarm buffer. B000 means that no messages are
currently in the buffer: this generally occurs only after clearing alarms.
ƒ
ERROR: displayed after the user action is rejected, for example, because
of an invalid selection or out-of-range value. The indicator disappears
after a valid action is performed.
Work area: includes a description of the screen, followed by the items
available for the current screen. Each selectable item has its own number.
The screen description identifies the screen (in this example: Link 1), and
also displays navigation data, that is, the path through the Megaplex-4100
menu structure that has been traversed to reach this screen (Configuration>
Physical Ports>I/O>I/O 1>Link 1). If the full path is too long, its beginning is
truncated, in which case an ellipsis … appears.
In addition, the work area includes the terminal prompt, >. The item number
you type appears to the right of the prompt.
The lower part of the work area is also used to display a concise explanation
of the available options and prompts regarding the actions available to you. It
may also display messages that request you to confirm operations such as
configuration changes, resetting, etc., or alerts that errors have been
detected during the evaluation of the parameters selected by you (in this
case, you will see a $ – Sanity option).
•
% – DB Update, # – DB Undo : after you make a configuration change, you
must either save it in one of the databases, or undo (cancel) it.
When you press the % hotkey, the changes are saved to the default
database, which is usually database 1, unless you selected a different default
database.
Changes that have been saved to a database using the Update DB command
will take effect only after that database is selected as active database.
•
Save: after you make configuration changes on certain screens, you must
temporarily save the changes in the edit buffer, or undo (cancel). Changes
that have been saved can take effect only after the current database is
updated.
The indication that changes have been made is provided by the appearance
of the S – Save item in the bottom line of the configuration screen. After
saving, the S – Save item disappears.
•
3-18
Bottom line: displays the keys used for navigation.
ƒ
ESC
returns to the previous screen (not relevant for main menu)
ƒ
!
returns directly to the main menu (not relevant for main menu)
ƒ
&–
ends the utility and displays the log-in screen again.
ƒ
@–
increases the area dedicated to the on line display.
ƒ
?–
displays additional help specific to the current screen.
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
In addition, the number of management connections (C) and the number of
managers (M) currently connected to the Megaplex-4100 is shown at the
lower right-hand corner (in Figure 3-4, this is 1 manager via one management
connection). The managers’ number indicates the total number of
management sessions active at the instant the screen was displayed,
irrespective of type (terminal, Telnet, SNMP or Web browser). If no user is
logged in, the number of managers is 0.
•
Note
The last two rows are reserved for displaying the last two alarms, or user
prompts.
It is normal to see at least a RESET OCCURRED event after power up. If not all of
the Megaplex-4100 ports are connected to operating equipment, you may also
see alarms reporting loss of signals, etc.
General Supervision Terminal Operating Procedures
³
How to use the terminal to perform a desired activity:
•
To select a menu item, type the corresponding line number and then press
<Enter>. This will either …
… display a submenu or a parameter selection screen …
ƒ
or …
… let you type the (free text) parameter value in the same row
ƒ
or …
… toggle the current value of the corresponding parameter (relevant to
ENABLE/DISABLE or ON/OFF selections).
ƒ
•
•
•
Megaplex-4100 Ver. 2.0
The type of response to be expected after selecting a menu item is indicated
as follows:
>
Selecting that item will display a submenu or a parameter
selection screen (see for example item 6 in Figure 3-4).
...
Selecting that item will let you type the desired value in the
same line (see for example item 1 in Figure 3-4).
Nothing
When neither symbol is displayed, selecting that item will toggle
the current selection, now shown in brackets (for example, this
will change ENABLE to DISABLE or vice versa).
When a menu does not fit on one screen (because it includes too many
lines), it is displayed on two consecutive pages. In this case, you will see …(N)
after the last line on the first page and …(P) after the last line on the second
page:
ƒ
While on the first page, press N to display the second page
ƒ
While on the second page, press P to return to the first page.
When a configuration screen is organized as a table, a special set of keys is
used for navigation within the table (such screens always have a ? (help)
Configuration and Management Alternatives
3-19
Chapter 3 Operation
Installation and Operation Manual
option that displays these keys). The following keys may be used for
navigation within tables:
Left Arrow (←) – move to the left
Right arrow (→) – move to the right
Down Arrow (↓) –move down
Up Arrow (↑) – move up
^D – scroll down
^U – scroll up
F – next
B – previous
In addition, the following shortcuts are also available:
•
ƒ
Tab – select the next cell that may be changed
ƒ
M – switch to the menu mode
ƒ
G followed by <row number>,<col number> – select a specific cell. For
example, type G2,5 to select the fifth cell in the second row.
The current value of a parameter is listed within parentheses ( ). To change a
parameter value on a parameter selection screen:
ƒ
Type the line number corresponding to the desired value, and then press
<Enter>
ƒ
To enter a value which requires free text entry, type in the desired string
and then press <Enter>. Use backspace to erase the current string.
Note that whenever applicable, the allowed range of values of a
parameter is listed within square brackets [ ].
•
The entry is checked after pressing <Enter>, and it is accepted only if it is
valid. If you make an error, for example, if you press a key not active on the
current screen or select an invalid parameter value, an ERROR indicator
appears in the upper right-hand corner. This indicator disappears as soon as
you make a correct operation.
•
When done with the current screen, press ESC to return to the previous
screen, or type ! to return directly to the main menu.
Saving Changes to Configuration Database
To save all the pending changes, type % (DB Update). You will be prompted to
confirm: type y to continue or n to cancel.
After confirming, the new database takes effect immediately. You will see the
message Configuration File Update is in Process while the database is saved in
the CL module flash memory.
Note
If you save the changes to the default database, the changes will be activated,
that is, the operation mode of the Megaplex-4100 changes in accordance with
the new parameters values. In this case, press <Enter> several times in sequence
to reestablish communication with the Megaplex-4100.
•
To undo (cancel) all the as-yet unsaved changes, type # – DB Undo and then
confirm.
Any unsaved changes are lost when the Megaplex-4100 is powered down.
3-20
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Ending a Terminal Configuration Session
³
To end the current terminal session:
Type & and then press <Enter>.
In addition, Megaplex-4100 will automatically terminate the current session after
no activity is detected for a user-selected time-out interval (default – 3 minutes,
can be increased to 10 minutes). The automatic session termination can however
be disabled. The time-out option is selected using Configuration>System>
Control Port>Serial Port>Security Timeout.
After a session is ended, it is necessary to enter again a valid user name and
password to start a new session.
Menu Structure of Supervision Utility
Figure 3-5 shows the structure of the main menu.
Main Menu
1. Inventory
2. Configuration
3. Monitoring
4. Diagnostics
5. File Utilities
Inventory
1. System
2. SW/HW Rev
Configuration
1.
2.
3.
4.
5.
6.
Quick Setup
System
Physical Layer
Logical Layer
Applications
DB Tools
Monitoring
1. System
2. Physical Layer
3. Logical Layer
Diagnostics
1. Physical Layer
2. Logical Layer
3. Active Tests
File Utilities
1. S/W & File Transfer CL
2. S/W & File Transfer I/O & S-Subsystem
Figure 3-5. Main Menu Structure
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-21
Chapter 3 Operation
Installation and Operation Manual
The functions of the various main menu items are as follows:
Displays logistics information on the Megaplex-4100. See
Inventory
Chapter 4 for details.
Configuration
Configure Megaplex-4100 operational parameters, and
manage its database files. See Chapter 4 for details.
Monitoring
Display Megaplex-4100 alarms, events and status, and the
performance monitoring statistics. See Chapter 5 for details.
Diagnostics
Activate tests and loopbacks on the various ports, and check
IP connectivity. See Chapter 5 for details.
File Utilities
Use the file transfer utilities. See Chapter 4 for details.
Figure 3-6 through Figure 3-27 show the detailed menu structure of the
supervision utility.
You may use these figures to find the screen used for any desired activity. For
additional details, refer to the Chapter listed in the description of the main menu,
where you will find a detailed view and a description of the functions and
parameters available on each screen.
Note
Unless specifically stated otherwise, where menu details depend on the frame
structure, STM-1 or OC-3, used by CL.1/155 and CL.1/155GbE modules for the
network links, the following figures illustrate menu structures for Megaplex-4100
using the STM-1 frame structure.
The frame structure, and thus the operating standard, SDH or SONET, is selected
by means of Configuration>Physical Ports>CL>Card Configuration screen.
The differences between SDH and SONET are described in Appendix C of this
manual.
Inventory
1. System
2. SW/HW Rev
System
SW/HW Rev
Figure 3-6. Inventory Menu Structure
3-22
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Configuration
1.
2.
3.
4.
5.
6.
Quick Setup
System
Physical Layer
Logical Layer
Applications
DB Tools
Quick Setup
1. Host IP address
2. Subnet Mask
3. Default Gateway
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
12. Alarms Configuration
13. Fault Propagation
Physical Layer
1. IO
2. CL
Logical Layer
1. IO
2. CL
3. Bundles
Applications
1. Ethernet Services
DB Tools
1.
2.
3.
4.
5.
6.
Load DB
Default DB
Load HW
Update DB
DB List
Delete DB
Figure 3-7. Configuration Menu Structure
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-23
Chapter 3 Operation
Installation and Operation Manual
System
Card Type
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
12. Alarms Configuration
13. Fault Propagation
Clock Source
1. Source
2. Master Port
3. Fallback Port
Slot: PS-A
Card:
PS
PS-B
PS
Slot: IO-4
Card: M8SL
IO-5
HSU-12
IO-7
HSU-12
IO-1
M8E1
IO-8
HSU-12
IO-2
M8E1
IO-3
M8SL
IO-9
IO-10
VC-16/FXS VC-16/E&M
Source
Master Port/Fallback Port
TS Assignment
1. IO
2. CL
Mapping
IO-6
HSU-12
CL-B
CL1/155
1. Internal
2. Rx Clock
3. S Subsystem
Rx Clock only
1. CL-A
2. CL-B
CL-A
CL1/155
See Sheet 2
or Sheet 3
Entry Num
1
2
| 3
v4
5
6
7
Slot
NONE
NONE
NONE
NONE
NONE
NONE
NONE
1. CL-A (CL1/155)
2. CL-B (CL1/155)
3. IO-1 (M8E1)
Port
4. IO-2 (M8E1)
5. IO-3 (M8SL)
6. IO-4 (M8SL)
7. IO-5 (HSU-12)
8. IO-6 (HSU-12)
9. IO-7 (HSU-12)
10. IO-8 (HSU-12)
13. NONE
11. IO-9 (VC-16/FXS)
12. IO-10 (VC-16/E&M)
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
See Sheet 4
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
See
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 3-8. Typical Configuration>System Menu Structure (Sheet 1 of 6)
3-24
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
Link 1
IO
See
Sheet 1
I/O-1
1. I/O-1
2. I/O-2
3. I/O-3
1. Link 1
2. Link 2
3. Link 3
..
.
..
.
12. Alarms Configuration
13. Fault Propagation
or
CL
1. PDH 1 (Up)>
2. PDH 2 (Up)>
3. PDH 3 (Up)>
4. PDH 4 (Up)>
5. PDH 5 (Up)>
.
.
.
Clock Source
1. Source
2. Master Port
3. Fallback Port
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
Rx Clock only
..
.
TS Assignment
12. PDH 12 (Up)>
13. PDH 13 (Up)>
14. PDH 14 (Up)>
15. PDH 15 (Up)>
16. PDH 16 (Up)>
.
.
.
23. PDH 23 (Up)>
24. PDH 24 (Up)>
25. PDH 25 (Up)>
26. PDH 26 (Up)>
27. PDH 27 (Up)>
.
.
.
..
.
PDH 1
34. PDH 34 (Up)>
35. PDH 35 (Up)>
36. PDH 36 (Up)>
37. PDH 37 (Up)>
38. PDH 38 (Up)>
.
.
.
..
.
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
..
.
(See below)
1. IO
2. CL
Display Time Slots
Mapping
Ts#
1. CL-A
2. CL-B
Ts#
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
1
2
3
4
5
6
7
8
02:01:01 02:01:02 02:01:04 02:BND01 02:BND01 02:BND01 03:BND15 03:BND15
9
-----
10
-----
11
-----
12
-----
13
-----
..
.
Control Port
15
-----
16
-----
Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
See Sheet 4
or Sheet 5
Slot
IO-2 (M8E1)
IO-2 (M8E1)
IO-2 (M8E1)
IO-2 (M8E1)
..
.
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
14
-----
Port
Link 1
Link 1
Link 1
BND 1
Ts
1
2
4
--
Type
DATA
DATA
DATA
DATA
Connect Time Slots
PDH 1
1. Start TS
2. Slot
3. Port
4. Number of TS
5. Type
6. Destination Start TS
7. Save Configuration
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (per Slot and Port)
5. Delete TS (Number of TS)
6. Split
1. Serial Port
2. ETH
Delete TS (per Slot and Port)
1. Slot
2. Port
3. Save Configuration
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Delete TS (Number of TS)
1. Start TS
2. Number of TS
3. Save Configuration
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
TS3
Split
1. Bit 1
... (01:IN03)
2. Bit 2
... (01:IN03)
3. Bit 3
... (------)
4. Bit 4
... (------)
5. Bit 5
... (------)
6. Bit 6
... (------)
7. Bit 7
... (------)
8. Bit 8
... (------)
9. Check Split Sanity
1. TS3
2. TS15
..
.
See
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
CL-A
1. Link 1
2. Link 2
Link 1
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Fault Propagation
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TUG3 3
TUG3 2
TUG3 1
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
1. Fault Propagation
2. Interfaces
Figure 3-9. Typical Configuration>System Menu Structure – SDH Only (Sheet 2 of 5)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-25
Chapter 3 Operation
Installation and Operation Manual
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
Link 1
IO
1. I/O-1
2. I/O-2
3. I/O-3
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
1. Link 1
2. Link 2
3. Link 3
..
.
See
Sheet 1
..
.
or
CL
12. Alarms Configuration
13. Fault Propagation
1. PDH 1 (Up)>
2. PDH 2 (Up)>
3. PDH 3 (Up)>
4. PDH 4 (Up)>
5. PDH 5 (Up)>
.
.
.
Clock Source
1. Source
2. Master Port
3. Fallback Port
I/O-1
..
.
Rx Clock only
12. PDH 12 (Up)>
13. PDH 13 (Up)>
14. PDH 14 (Up)>
15. PDH 15 (Up)>
16. PDH 16 (Up)>
.
.
.
23. PDH 23 (Up)>
24. PDH 24 (Up)>
25. PDH 25 (Up)>
26. PDH 26 (Up)>
27. PDH 27 (Up)>
.
.
.
..
.
PDH 1
34. PDH 34 (Up)>
35. PDH 35 (Up)>
36. PDH 36 (Up)>
37. PDH 37 (Up)>
38. PDH 38 (Up)>
.
.
.
..
.
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
..
.
(See below)
TS Assignment
1. IO
2. CL
Display Time Slots
Ts#
Mapping
Ts#
1. CL-A
2. CL-B
1
2
3
4
5
6
7
8
02:01:01 02:01:02 02:01:04 02:BND01 02:BND01 02:BND01 03:BND15 03:BND15
9
-----
Ts#
TS 01
TS 02
| TS 03
v TS 04
See Sheet 4
or Sheet 5
12
-----
13
-----
..
.
14
-----
15
-----
16
-----
Slot
IO-2 (M8T1)
IO-2 (M8T1)
IO-2 (M8T1)
IO-2 (M8T1)
..
.
Port
Link 1
Link 1
Link 1
BND 1
Ts
1
2
4
--
Type
DATA
DATA
DATA
DATA
Connect Time Slots
PDH 1
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
11
-----
Manual
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
10
-----
1. Start TS
2. Slot
3. Port
4. Number of TS
5. Type
6. Destination Start TS
7. Save Configuration
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (per Slot and Port)
5. Delete TS (Number of TS)
6. Split
Delete TS (per Slot and Port)
1. Slot
2. Port
3. Save Configuration
Control Port
1. Serial Port
2. ETH
Delete TS (Number of TS)
Date & Time
1. Start TS
2. Number of TS
3. Save Configuration
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
TS3
Split
1. TS3
2. TS15
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
..
.
See
Sheet 6
CL-A
1. Link 1
2. Link 2
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
1. Bit 1
... (01:IN03)
2. Bit 2
... (01:IN03)
3. Bit 3
... (------)
4. Bit 4
... (------)
5. Bit 5
... (------)
6. Bit 6
... (------)
7. Bit 7
... (------)
8. Bit 8
... (------)
9. Check Split Sanity
Link 1
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
STS1-1
TU1 TU2 TU3 TU4
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
STS1-2
TU1 TU2 TU3
None None None
None None None
None None None
None None None
None None None
None None None
None None None
TU4
None
None
None
None
None
None
None
STS1-3
TU1 TU2 TU3 TU4
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 3-10. Typical Configuration>System Menu Structure – SONET Only (Sheet 3 of 5)
3-26
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Figure 3-11. Typical Configuration>System Menu Structure (Sheet 4 of 6)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-27
Chapter 3 Operation
Installation and Operation Manual
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
See
Sheet 1
APS Group ID
12. Alarms Configuration
13. Fault Propagation
1. A1-A2
2. B1-B2
3. A1-B1
4. A2-B2
Clock Source
1. Source
2. Master Port
3. Fallback Port
Rx Clock only
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Users
Mapping
1.
2.
3.
4.
5.
1. CL-A
2. CL-B
APS
Authentication Protocol
Security Name
Authentication Protocol
Privacy Protocol
Authentication Password
Privacy Password
1. usmNoAuthProtocol
2. usmHMACMD5AuthProtocol
3. usmHMACSHAAuthProtocol
With Authentication
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
Privacy Protocol
1 usmNoPrivProtocol
2. usmDESPrivProtocol
Only with Authentication
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Targets & Notify
SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Only with Privacy
See
Sheet 4
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
SNMPv3 Factory Defaults
Summary User Table
Summary Target Table
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
Targets Params
1.
2.
3.
4.
5.
Name
Message Processing Model
Security Model
Security Name
Security Level
1.
2.
3.
4.
SNMPv1
SNMPv2c
SNMPv2u
SNMPv3
1.
2.
3.
4.
5.
Any
SNMPv1
SNMPv2c
USM
Not defined
Security Model
Target Address
1.
2.
3.
4.
Name
IP Address
Params Name
Tag List
Security Level
1. noAuthNoPriv
2. authNoPriv
3. authPriv
Notify
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
Message Processing
Model
See
Sheet 6
Trap
SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Summary User Table
User
Security Model
Security Level
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Summary Target Table
Address MPModel SecModel SecName SecLevel
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 3-12. Typical Configuration>System Menu Structure (Sheet 5 of 6)
3-28
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
See
Sheet 1
12. Alarms Configuration
13. Fault Propagation
Clock Source
1. Source
2. Master Port
3. Fallback Port
Rx Clock only
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping
1. CL-A
2. CL-B
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
See Sheet 4
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3 - Enabled
8. SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Baud Rate
For Administrator
Serial Port
Change Password
1. Baud Rate
2. Change Password
3. Security Timeout
1. Change User Details
2. Show all Users
Change User Details
Show all Users
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
Security Timeout
ETH
CL-A
1. CL-A
2. CL-B
Routing Protocol
1. Admin Status
2. Routing Protocol
3. User Name
1. None
2. RIP 2
3. Proprietary RIP
Set Date Format
1. DD-MM-YYYY
2. MM-DD-YYYY
3. YYYY-DD-MM
4. YYYY-MM-DD
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Profile Number
Rx Signaling
Tx Signaling
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Interfaces
Interfaces
Fault Propagation
1. Fault Propagation
2. Interfaces
Slot A
IO-1
Port A
ETH 1
Slot B
IO-5
Port B
ETH 2
Add
Mode
BiDirectional (A<->B)
1. Slot A
2. Port A
3. Slot B
4. Port B
5. Mode
Figure 3-13. Typical Configuration>System Menu Structure (Sheet 6 of 6)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-29
Chapter 3 Operation
Installation and Operation Manual
Physical Layer
1. I/O
2. CL
I/O
E1
I/O-1
1. I/O-1
2. I/O-2
3. I/O-3
..
..
1. Link 1
1. E1
2. Ethernet
..
..
.
8. Link 8
9. All Links
Transmit Timing
Source
Ethernet
1. ETH1
2. ETH2
3. ETH3
4. All Ports
1. System
2. Station RCLK
3. Station RCLK after JA
Clock Rate
Station Clock
CL
1. 2048 KBPS
2. 1544 KBPS
2. 2048 KHZ
1. Admin Status
2. Transmit Timing Source
3. Clock Rate
4. Interface Type
5. Line Code
6. Rx Gain Limit
7. SSM
8. Rx Source
1. CL-A
2. CL-B
Short Haul
Long Haul
Disable
Rx
Sa4
Sa5
Sa6
Sa7
Sa8
1. Station Clock
2. Ethernet
3. SDH/SONET
GbE
1. Admin Status
2. Auto Negotiation
3. Speed & Duplex
4. Flow Control
5. User Name
6. Redundancy
1. GbE 1
2. GbE 2
3. All Ports
1. Card Configuration
2. Link 1
3. Link 2
4. All Links
1544 KBPS only
2048 KBPS, 2048 KHZ
1. AMI
2. HDB3
3. B8ZS
Ethernet
SDH/SONET
Balance
Unbalance
Line Code
Only for SSM = Rx
CL-A
Not for
SYSTEM Source
Card Configuration
1. Frame Structure
– STM-1
2. Tx Clock Based on SSM – YES
3. Common PDH LVC Parameters
Common PDH
LVC Parameters
1. RDI on Signal Label
2. RDI on Path Trace
or
Card Configuration
1. Frame Structure
– STM-1
2. Tx Clock Based on SSM – NO
3. SDH Tx Clock
4. Master Port
RX CLOCK only
5. Fallback Port
6. Common PDH LVC Parameters
1. Off
2. PPP Over HDLC
3. HDLC
Routing Protocol
Link 1
1. Admin Status
2. User Name
3. RDI on Fail
4. EED Threshold
5. SD Threshold
6. DCC Configuration
In Band Management
1. None
2. RIP 2
3. Proprietary RIP
DCC Configuration
1. In Band Management
2. Routing Protocol
3. Management DCC
4. Deviation Type
Management DCC
Standard
Type 1
1. D1-D3
2. D4-D12
Figure 3-14. Typical Configuration>Physical Layer Menu Structure (SDH)
3-30
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Figure 3-15. Typical Configuration>Physical Ports Menu Structure (SONET)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-31
Chapter 3 Operation
Installation and Operation Manual
Figure 3-16. Typical Configuration>Virtual Ports Menu Structure (SDH) (Sheet 1 of 2)
3-32
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Logical Layer
1. IO
2. CL
3. Bundles
CL
See
Sheet 1
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
Port 1
1. Port 1
2. Port 2
3. All Ports
VC-4
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. J1 Path Trace
5. Padding
6. EED Threshold
7. SD Threshold
8. Signal Label
Bundles
1. Slot
2. Bundle
MLPPP Bundle
(Unframed E1 Ports Only)
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot
11. Source Port
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. MLPPP MTU
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Number of Links
11. Source Slot
12. Source Port
CL
I/O
For CL
.
.
.
PDH Selection Screen
For I/O Modules
Link Selection Screen
Figure 3-17. Typical Configuration>Logical Layer Menu Structure (SDH) (Sheet 2 of 2)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-33
Chapter 3 Operation
Installation and Operation Manual
Logical Layer
IO
1. IO
2. CL
3. Bundles
I/O-1 (HS-U12)
1. I/O-1
2. I/O-2
..
..
I/O-2 (M8SL)
1. E1 1
2. E1 2
3. E1 3
4. E1 4
5. E1 5
6. E1 6
7. E1 7
8. E1 8
9. All Ports
1. IN 1
2. IN 2
3. IN 3
4. IN 4
5. IN 5
6. IN 6
7. IN 7
8. IN 8
9. IN 9
10. IN 10
11. IN 11
12. IN 12
13. IN 13
14. IN 14
15. IN 15
16. IN 16
17. IN 17
18. IN 18
19. IN 19
20. IN 20
21. IN 21
22. IN 22
23. IN 23
24. IN 24
25. IN 25
26. IN 26
27. IN 27
28. IN 28
29. IN 29
30. IN 30
31. IN 31
32. IN 32
33. IN 33
34. IN 34
35. IN 35
36. IN 36
T1 Ports
PDH 1
PDH
CL
1. PDH 1
..
.
..
.
.
1. PDH
2. VCAT
3. HVC
84. PDH 84
85. All PDHs
VCAT
1. Admin Status
2. User Name
3. Frame Type
4. Redundancy
5. Restoration Time
6. Idle Code
7. Cross Connect
8. In Band Management
9. Routing Protocol
10. LVC Configuration
1. CL-A
2. CL-B
VC Type
1. VT-1.5
2. STS-1/SPE
CL-A
1. VCG-1
2. VCG-2
3. VCG-3
4. VCG-4
5. VCG-5
6. VCG-6
7. VCG-7
8. VCG-8
9. All VCGs
For VCG.1 to
VCG.8 only
GFP Encapsulation
Typical
VCG-1
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. LVC Configuration
11. GFP Configuration
or
Redundancy = 1+1
VCG-1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. Revertive
HVC
Encapsulation
1. GFP
2. LAPS
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. First Sequence Indicator
7. Extended Signal Label
8. RDI on Payload label
9. RDI on Path Trace
GFP Configuration
1. FCS
2. PTI for Client Data
3. UPI for Client Data
4. Delta
5. Core Scrambling
6. Payload Scrambling
11. Wait to Restore
12. Redundancy Slot
13. Redundancy Port
14. LVC Configuration
15. GFP Configuration
1. CL-A
2. CL-B
Bundles
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. Protection Mode
7. Mapping Mode
8. Protection Partner
9. Payload Label
LAPS Encapsulation
Typical
VCG 1
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Redundancy
9. LVC Configuration
10. LAPS Configuration
For VCG.1 to
VCG.8 only
or
Redundancy = 1+1
VCG 1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Redundancy
9. Revertive
10. Wait to Restore
11. Redundancy Slot
12. Redundancy Port
13. LVC Configuration
14. LAPS Configuration
LAPS Configuration
1. Address
2. Control
3. SAPI Value
See
Sheet 2
1. Slot
2. Bundle
Figure 3-18. Typical Configuration>Virtual Ports Menu Structure (SONET) (Sheet 1 of 2)
3-34
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Logical Layer
1. IO
2. CL
3. Bundles
See
Sheet 1
CL
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
Port 1
1. Port 1
2. Port 2
3. All Ports
4. Common Parameters
1. STS1-1
2. STS1-2
3. STS1-3
STS1-1
1. J1 Path Trace
2. Padding
3. Signal Label
Bundles
Common Parameters
1. Slot
2. Bundle
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. EED Threshold
5. SD Threshold
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot
11. Source Port
CL
I/O
For CL
PDH Selection Screen
For I/O Modules
Link Selection Screen
Figure 3-19. Typical Configuration>Virtual Ports Menu Structure (SONET) (Sheet 2 of 2)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-35
Chapter 3 Operation
Installation and Operation Manual
Applications
1. Ethernet Services
Flows
Ethernet Services
1. Flow
2. User Name
3. Flow Type
4. Bridge Port Mapping
1. Flows
Flow Type
1. E-LINE
2. E-LAN
Reserved
Bridge Port Mapping
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
Display List (U)
Add (A)
Bridge Port Mapping
Flow
Flow User Name
C-VLAN ID
SP-VLAN
Bridge Port Mapping
C-VLAN Type
BP
1. C-VLAN Type
C-VLAN ID
2. SP-VLAN
3. Slot
Port
Rate
BP User Name
1. Unaware
2. Aware
Figure 3-20. Typical Configuration>Applications Menu
Load DB
DB Tools
1.
2.
3.
4.
5.
6.
Load DB
Default DB
Load HW
Update DB
DB List
Delete DB
Default DB
Update DB
DB List
Delete DB
Figure 3-21. Configuration>DB Tools Menu
3-36
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Figure 3-22. Typical Monitoring Menu Structure (SDH) (Part 1 of 2)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-37
Chapter 3 Operation
Installation and Operation Manual
Figure 3-23. Typical Monitoring Menu Structure (SDH) (Part 2 of 2)
3-38
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Monitoring
All Alarms
Active Alarms (ON)
1. All Alarms
2. Slot Alarms
1. System
2. Physical Layer
3. Logical Layer
Slot Alarms
All Alarms
Active Alarms (ALL)
1. All Alarms
2. System Alarms
3. Slot Alarms
System Alarms
System
Slot Alarms
1. Active Alarms (ON)
2. Active Alarms (ALL)
3. Clear Alarms
4. History Alarms
5. Timing
6. CL Status
7. Remote Agents
8. APS
History Alarms
Timing
CL Status
Remote Agents
I/O-1
APS
1. CH1
2. CH2
I/O
Logical Layer
1. I/O
2. CL
1. I/O-1 (HS-U12)
2. I/O-2 (M8SL)
3. I/O-3 (M8SL)
..
..
CL
SDH/SONET
1. CL-A
2. CL-B
1. Link 1
2. Link 2
CL-A
1. SDH/SONET
2. PDH
3. VCAT
..
.
Interface Info
I/O-3
Bundles (Selection)
1. Bundles
Link 1
VT1.5
1. VT1.5
2. STS1-1
3. STS1-2
4. STS1-3
1. Port Status
2. Port Statistics
1. PDH 1
..
..
..
.
84. PDH 84
85. All PDHs
Port Status
Port Statistics
1. Current Interval
2. Select Interval
3. Total
PDH
Bundle (Statistics)
PDH 1
Current Interval
Select Interval
Total
1. Current Interval
2. Select Interval
3. Total
VCAT
1. VCG 1
2. VCG 2
3. VCG 3
4. VCG 4
5. VCG 5
6. VCG 6
7. VCG 7
8. VCG 8
VCG 1
1. WAN Intervals
2. LCAS Path Info
WAN Intervals
1. Current Interval
2. Select Interval
3. Total
Current Interval
Select Interval
Total
LCAS Path Info
Physical Layer
See
Part 2
1. I/O
2. CL
Figure 3-24. Typical Monitoring Menu Structure (SONET) (Part 1 of 2)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-39
Chapter 3 Operation
Installation and Operation Manual
Monitoring
1. System
2. Physical Layer
3. Logical Layer
System
1. Active Alarms (ON)
2. Active Alarms (ALL)
3. Clear Alarms
4. History Alarms
5. Timing
6. CL Status
7. Remote Agents
8. APS
See
Part 1
Typical
I/O-3
1. Link 1
2. Link 2
3. Link 3
Logical Layer
..
..
1. I/O
2. CL
M8E1, M8T1, M8SL
Link 1
Status
1. Status
2. Statistics
Link 1
I/O
Physical Layer
M8E1, M8T1, M8SL
1. I/O-1 (HS-U12)
2. I/O-2 (M8T1)
3. I/O-3 (M8T1)
1. I/O
2. CL
..
..
Current Interval
1. Current (15 min)
2. Select Interval (15 min)
3. Current (24 hours)
4. Select Interval (24 hours)
5. Clear Statistics
I/O-2
1. E1 or T1 or SHDSL
2. Ethernet
Redundancy
Only
Select Interval
Total
Select Interval
SHDSL Only
Ethernet
1. ETH 1
2. ETH 2
3. ETH 3
ETH 1
Status
1. Status
2. Statistics
Statistics
CL
1. CL-A
2. CL-B
Station Clock
Ethernet
1. GbE 1
2. GbE 2
CL-A
1. Station Clock
2. Ethernet
3. SDH/SONET
Port Status
GbE 1
1. Port Status
2. ETH Counters
Timing
Link 1
SDH/SONET
1. Timing
2. Link 1
3. Link 2
4. Path Protection
1. Link Status
2. Link Statistics
3. DCC Statistics
4. Optical Parameters
Path Protection
ETH Counters
Link Status
Link Statistics
1. Current Interval
2. Select Interval
3. Total
Current Interval
Select Interval
Total
DCC Statistics
Optical Parameters
Figure 3-25. Typical Monitoring Menu Structure (SONET) (Part 2 of 2)
3-40
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
Figure 3-26. Typical Diagnostics Menu Structure (SDH and SONET)
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-41
Chapter 3 Operation
Installation and Operation Manual
File Utilities
S/W & File Transfer CL
1. S/W & File Transfer CL
2. S/W & File Transfer I/O & S-Subsystem
TFTP
1. TFTP
TFTP State
Command
1. File Name
2. Server IP
3. Command
S/W & File Transfer I/O &
S-Subsystem
1. TFTP
2. Download to Cards
3. Download Status
4. Dir
5. Delete File
1. SW Download
2. Config Download
3. Config Upload
4. No Command
TFTP
TFTP State
TFTP Error
1. File Name
2. Server IP
3. File #
4. S/W Download (To Flash)
File #
1. File-1
2. File-2
Download to Cards
Download Status
Dir
Delete File
Figure 3-27. Typical File Utilities Menu Structure
Working with Telnet
Typically, the Telnet host is a PC or a UNIX station with the appropriate suite of
TCP/IP protocols. To enable a Telnet host to communicate, it is necessary to
configure the IP address of the Megaplex-4100 management subsystem. After
this preliminary configuration, you can use a Telnet host directly connected to
the CONTROL ETH port of the active or standby CL module in the managed
Megaplex-4100 to perform additional configuration tasks.
However, after configuring the communication parameters of the Megaplex-4100
management subsystem, you may also use a Telnet host located at a remote site,
the only requirement being that IP communication be established between the
LAN serving that site and the LAN connected to the Megaplex-4100 CONTROL
ETH port.
For inband Telnet access via E1 and T1 links, you also need to configure
dedicated management (MNG) timeslots.
General Telnet Operating Procedures
Telnet uses the terminal utility screens for configuration. The only difference is
that Telnet management access is possible only after performing a preliminary
configuration of the Megaplex-4100 (see Table 3-3).
³
To prepare for using Telnet:
1. Configure the Megaplex-4100 host IP address.
3-42
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 3 Operation
When the Telnet host is not on a LAN directly connected to a Megaplex-4100
CONTROL ETH port, it is necessary to configure all the IP communication
parameters appearing on the Configuration>System>Management>Host IP
screen.
2. Enable Telnet access using Configuration>System>Management>Mng
Access>Telnet.
Working with Web Browsers
You may use any Web browser to access the Megaplex-4100 supervision utility
from any location that enables access to the Megaplex-4100 using Internet
protocols, for example:
•
Internet Explorer 6.0 and up, running on Windows™
•
Netscape Communicator 7.0 and up, running on Windows™, HPOV or Linux
•
Firefox 1.0.4 and up, running on Windows™
•
Mozilla 1.4.3 and up, running on Linux.
However, before using Web access, it is necessary to perform a preliminary
configuration of the Megaplex-4100 (see Table 3-3).
Guidelines for Using Web Browsers
When using a Web browser, pay attention to the following points:
•
Enable scripts
•
Configure the firewall that is probably installed on your PC to allow access to
the destination IP address (that is, the Megaplex-4100 management address)
•
Disable pop-up blocking software (such as Google Popup Blocker); you may
also have to configure your spyware/adware protection program to accept
traffic from/to the destination IP address.
•
Browsers store the last viewed pages in a special cache. To prevent
configuration errors, it is absolutely necessary to flush the browser’s cache
whenever you return to the same screen.
Preparations for Using Web Browsers
³
To prepare for using Web access:
1. Configure the Megaplex-4100 host IP address and all the IP communication
parameters (use the Configuration>System>Management>Host IP screen).
2. Enable Web browser access using Configuration>System>Management>
Mng Access>WEB.
General Web Browsers Operating Procedures
Before starting, obtain the Megaplex-4100 management (host) IP address.
1. Open the Web browser.
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-43
Chapter 3 Operation
Installation and Operation Manual
2. Enter the IP address of the Megaplex-4100 in the address field of the
browser in the following format: http://’IP address’ (‘IP address’ stands for
the actual Megaplex-4100 IP address).
3. After entering the address, press <Enter> to command the browser to
connect.
4. After the opening window of the ConfiguRAD utility is displayed, click LOGIN.
5. Perform log-in as described above for the supervision terminal.
6. You will see the main ConfiguRAD menu.
7. Use standard browser operating procedures to perform the desired activities.
Navigating the ConfiguRAD Menus
ConfiguRAD is a Web-based remote access terminal management software. It
provides a user-friendly interface for configuring, monitoring and performing
diagnostic tests on the Megaplex-4100 units.
³
To choose an option:
1. Click a link in the ConfiguRAD screen to display the next menu.
2. Once the target screen is displayed, select a value from the drop-down box or
enter it in a text box.
3. At the left-hand bottom corner, ConfiguRAD provides some auxiliary
management tools:
ƒ
Status – shows the number of users currently managing Megaplex-4100
ƒ
Trace – opens an additional pane for system messages, progress
indicators (ping, software and configuration file downloads) and alarms.
It is recommended to keep the trace pane open all the time.
ƒ
Refresh All – refreshes all ConfiguRAD display elements.
Working with SNMP Management Stations
Support for SNMP Management
Megaplex-4100 can be configured by any SNMP-based network management
station, including third-party network management stations, provided IP
communication is possible with the management station.
Megaplex-4100 supports several management information bases (MIBs). A MIB
(Management Information Base) is a hierarchically-organized database of
managed objects, where each characteristic of the element to be managed is
defined as an object in the MIB.
Megaplex-4100 support the following standard MIBs:
3-44
•
IANAifType-MIB (ifType table)
•
RFC4188 (bridge MIB)
•
RFC3418 (SNMPv2 MIB)
Configuration and Management Alternatives
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 3 Operation
•
RFC3592 (SONET-MIB)
•
RFC3635 (EtherLike-MIB)
•
RFC3636 (MAU-MIB)
•
RFC4133 (ENTITY-MIB – physicalTable)
•
RFC2819 (RMON MIB)
•
RFC2863 (IF-MIB)
•
RFC4805 (DS1-MIB)
•
RFC4319 (HDSL2-SHDSL-LINE-MIB)
•
RFC3273 (HC-RMON-MIB)
•
RFC4878 (DOT3-OAM-MIB)
•
SNMPv1 definitions are covered by the following documents:
•
ƒ
RFC3418
ƒ
RFC2578 (SMIV2)
ƒ
RFC2579 (Textual Conventions SMIV2)
ƒ
RFC2580 (Conformance SMIV2).
SNMPv3 definitions are covered in RFC 3413 to RFC 3418.
Megaplex-4100 also support the RAD private MIB.
Additional MIB information can be obtained from your local RAD Authorized
Business Partner.
For information on traps, see Chapter 6.
Preparing for SNMP Management
To enable SNMP management, it is necessary to enable SNMP access, and
configure the minimal SNMP management parameters.
The required parameters depend on the required security level:
³
To prepare for SNMP management without SNMPv3 security features:
1. If necessary, configure SNMPv3 to Disabled. If the previous state has been
Enabled, you will be requested to confirm.
2. If necessary, configure the Megaplex-4100 host IP address.
Note
When the SNMP station is not on a LAN directly connected to a Megaplex-4100
CONTROL ETH port, it is necessary to configure all the IP communication
parameters appearing on the Configuration > System > Management > Host IP
screen.
3. Configure the SNMP community names on the Host IP screen.
4. Enable SNMP access using Configuration > System > Management > Mng
Access > SNMP.
Megaplex-4100 Ver. 2.0
Configuration and Management Alternatives
3-45
Chapter 3 Operation
³
Installation and Operation Manual
To prepare for SNMP management with SNMPv3 security features:
1. If necessary, configure SNMPv3 to Enabled. If the previous state has been
Disabled, you will be requested to confirm.
2. If necessary, configure the Megaplex-4100 host IP address.
3. Configure SNMPv3 access using Configuration > System > Management > Mng
Access > SNMPv3 Setting, using the instructions given in Chapter 4.
4. Enable SNMP access using Configuration > System > Management > Mng
Access > SNMP.
For SNMP management instructions, refer to the User’s Guide of the desired
SNMP station.
3.5
³
Caution
Turning the Megaplex-4100 Off
To turn the Megaplex-4100 off:
When a feed and ring voltage source is connected to the Megaplex-4100
enclosure, always turn that source off before turning the PS module(s) off.
•
Set the ON/OFF switch(es) of the PS module(s) to OFF.
If the Megaplex-4100 is equipped with DC-powered PS modules without
POWER switch, disconnect the DC power by means of an external switch or
circuit breaker.
3-46
Turning the Megaplex-4100 Off
Megaplex-4100 Ver. 2.0
Chapter 4
Configuration
This Chapter provides detailed configuration instructions for the Megaplex-4100.
As part of these instructions, you can find:
•
The purpose of each screen
•
The parameters that can be selected on the each screen, considerations
regarding the selection of specific parameter values, and where applicable,
the effects of parameters selected on other screens
•
Instructions for using each screen.
You can find a complete collection of supervision utility navigation maps in
Chapter 3. For your convenience, the relevant navigation map also appears in the
beginning section of each main configuration activity.
The configuration instructions are presented in the order the configuration
activities are performed when a new Megaplex-4100 is prepared for service (see
Chapter 5 for a detailed configuration sequence).
However, after performing the preliminary configuration of the Megaplex-4100 in
accordance with Chapter 3, the same configuration activities can also be
performed by means of a Telnet host, or Web browser.
You may also want to review Chapter 1, which presents technical and functional
descriptions of the Megaplex-4100, and Appendix C, which describes the
Megaplex-4100 operating environment and provides background information that
will help you understand the various Megaplex-4100 configuration parameters.
If you configure Megaplex-4100 for SNMP management as explained in this
Chapter, SNMP management stations using the appropriate SNMP version and
compatible parameters will also be able to configure and manage Megaplex-4100
units.
Note
Unless otherwise specified, all the parameter values appearing in the following
screens are given for illustration purposes only. They do not reflect recommended
values.
4.1
Configuring MP-4100 for Management
Quick Setup
When starting the configuration of a new Megaplex-4100, you can use the Quick
Setup screen to prepare the preliminary set of Megaplex-4100 IP communication
parameters:
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-1
Chapter 4 Configuration
Installation and Operation Manual
•
The management IP address (mandatory)
•
The associated IP subnet (mandatory)
•
Default IP gateway (optional).
The IP information can also be defined or modified by means of the
Configuration>System>Management>Host IP screen.
To navigate to the required screen, use Configuration>Quick Setup.
A typical Quick Setup screen is shown below.
MP-4100
Configuration>Quick Setup
1. Host IP Address ... (176.123.1.102)
2. Subnet Mask
... (255.255.255.0)
3. Default Gateway ... (0.0.0.0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-1. Typical Quick Setup Screen
To configure a parameter on the Quick Setup screen, select the corresponding
item by typing its number and then pressing <Enter>. You can then type the
desired value in the same line.
To confirm your entry, press <Enter>.
³
To configure the Megaplex-4100 management IP address:
1. Select Host IP address.
2. Enter the prescribed IP address of the Megaplex-4100 management agent, in
the dotted quad format, and then press <Enter>.
3. Select Subnet Mask.
4. Enter the IP subnet mask to be used by of the Megaplex-4100 management
agent, in the dotted quad format, and then press <Enter>. Make sure that the
subnet mask is compatible with the specified IP address, and that it represents
a string of consecutive 1s, followed by consecutive 0s.
5. You may also specify a default gateway. The default gateway is used by the
Megaplex-4100 management agent to send packets with destinations not
located on a local LAN. To specify a default gateway, select Default Gateway,
enter the IP address of the desired router port in the dotted-quad format, and
then press <Enter>. The default gateway IP address must be within the same IP
subnet as the management IP address. The default value, 0.0.0.0, means that
no default gateway is defined.
4-2
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 4 Configuration
To save and activate the new configuration:
Type % and then type y to confirm the action.
Configuring the Control Ports
Megaplex-4100 has two types of control ports:
•
Serial control ports
•
Ethernet control ports.
The following sections explain the configuration procedures for both types of
ports.
To navigate to the required screen, use Configuration>System>Control Port.
³
To select a control port:
1. Type its number and then press <Enter>.
MP-4100
Configuration>System>Control Port
1. Serial Port>
2. ETH
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-2. Control Port Selection Screen
Configuring the Serial Ports
The Configuration>System>Control Port>Serial Port screen is used to configure
the communication parameters of the serial RS-232 port, CONTROL DCE, located
on the CL modules, the authorizations of the users allowed to manage the
Megaplex-4100 via the serial port, and the security features.
The same set of parameters are used by both CL modules.
A typical Serial Port screen is shown in Figure 4-3.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-3
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Control Port>Serial Port
1. Baud Rate
2. Change Password
3. Security Timeout
>
>
>
(115.2
KBPS)
(None)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-3. Typical Serial Port Screen
³
To configure the serial port parameters:
1. Type the number corresponding to the desired parameter and then press
<Enter>.
2. You will see the serial port parameter selection screen. The parameters that
can be configured are explained in Table 4-1.
Table 4-1. Serial Port Parameters
Parameter
Function
Values
Baud Rate
Selects the supervisory port data rate
The available selections are 0.3, 1.2, 2.4, 4.8,
9.6, 19.2, 38.4, 57.6 and 115.2 KBPS.
Default: 115.2 KBPS
Security
Timeout
Controls the idle disconnect time of the
CONTROL DCE port
NONE – Automatic session disconnection
disabled. To disconnect the session, use the &
(exit) command.
3 MIN – Automatic disconnection after 3 minutes
if no input data is received by the CONTROL DCE
port.
10 MIN – Automatic disconnection after
10 minutes if no input data is received by the
CONTROL DCE port.
Default: NONE
Changing the User Authorizations and Security Parameters of
the Serial Ports
The Megaplex-4100 supports three access levels for supervision terminal, Telnet,
and Web browser users, explained in Chapter 3. The unit is delivered with three
factory-default user names, one for each access level, and with default
passwords.
4-4
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Use the Change Password item on the Serial Port screen to perform the following
tasks:
Note
³
•
Manage the users’ list (add/delete users),
•
Change access levels for added users
•
Assign passwords to the various users.
When SNMPv3 security features are enabled, the term user refers to an SNMP
management station, and the users’ authorizations are determined by configuring
the parameters related to the view-based security model (VACM) aspect of
SNMPv3. Refer to the Configuring for SNMP Management with SNMPv3 Security
section for details.
To access the users’ security functions:
1. Type 2 on the Serial Port screen to display the Change Password submenu
(Figure 4-4).
MP-4100
Configuration>System>Control Port>Serial Port>Change Password
1. Change User details
2. Show all users
>
[]>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-4. Typical Change Password Screen
2. Type the number corresponding to the desired task:
Note
³
•
To change the current password assigned to a user, select Change User
Details
•
To add/delete users, select Show All Users.
It is not possible to change the access level of the three factory default users: su,
tech, user, but only the access levels of added users.
To change the current password of a factory default user:
1. Select Change User Details on the Change Password screen and pressing
<Enter>. You will see the Change User Details screen.
2. On the Change User Details screen, select Enter UserName and then press
<Enter>. You can type now the desired user name. When done, press <Enter>
to continue.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-5
Chapter 4 Configuration
Installation and Operation Manual
Password characters are not displayed on the screen (only an asterisk * appears
for each character you type). The string changes to 8 asterisks after pressing
<Enter>, irrespective of the number of characters typed.
Note
3. After specifying a factory default user name, the New Password field appears.
Select New Password and then type the new password (4 to 8 characters).
4. After pressing <Enter>, the screen is updated, and a Confirm Password field
appears.
A typical Change User Details screen, as seen after Step 4, is shown in
Figure 4-5.
MP-4100
...>System>Control Port>Serial Port>Change Password>Change User details
Enter UserName (to change)
New Password
1. Confirm Password
... (su)
... (********)
... ()
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-5. Typical Change User Details Screen (Factory Default User)
5. Select Confirm Password and then type the new password a second time for
confirmation. Press <Enter> when done.
After confirming password, the following message appears: Password has
been changed!! Update DB to finalize process!!
6. To activate the new password, type % to update the database and then
confirm the action.
³
To change the current password of an added user:
1. Select Change User Details on the Change Password screen and pressing
<Enter>. You will see the Change User Details screen.
2. On the Change User Details screen, select Enter UserName and then press
<Enter>. Now you can type the desired user name. When done, press <Enter>
to continue.
3. After specifying an added user name, the screen is updated to enable two
actions:
4-6
•
Change the access level of the selected user
•
Change the password of the selected user. Skip to Step 4 if that is what
you want to do.
•
To change the access level, select Access Level and then press <Enter>.
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
•
You will see a selection screen with four access levels (Figure 4-6). Note
that the Operator level is not defined for Megaplex-4100 (it has the same
capabilities as the Monitor). See Chapter 3 for details on the capabilities of
each access level.
•
At this stage, type the number corresponding to the desired level, and then
press <Enter> to return to the screen of Figure 4-5.
MP-4100
...nge Password>Change User details> Change Access Level (Administrator)
1.
2.
3.
4.
Monitor
Technician
Operator
Administrator
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-6. Typical Change Access Level Selection Screen for Added Users
Note
Password characters are not displayed on the screen (only an asterisk * appears
for each character you type). The string changes to 8 asterisks after pressing
<Enter>, irrespective of the number of characters typed.
4. After specifying a new access level, the New Password field appears. Select
New Password and then type the new password (4 to 8 characters).
5. After pressing <Enter>, the screen is updated, and a Confirm Password field
appears.
A typical Change User Details screen, as seen after pressing <Enter>, is
shown in Figure 4-7.
MP-4100
...>System>Control Port>Serial Port>Change Password>Change User details
Enter UserName (to change)
New Password
1. Change Access Level
2. Confirm Password
...
...
...
...
(oper)
(********)
(Technician)
()
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-7. Typical Change User Details Screen (Added User)
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-7
Chapter 4 Configuration
Installation and Operation Manual
6. Select Confirm Password and then type the new password a second time for
confirmation. Press <Enter> when done.
After confirming password, the following message appears: Password has
been changed!! Update DB to finalize process!!
7. To activate the new user details, type % to update the database and then
confirm the action.
³
To manage the users list:
1. Select Show All Users on the Change Password screen and then press <Enter>
to display the current list of users. Figure 4-8 shows a typical screen with
factory defaults.
MP-4100
...ation>System>Control Port>Serial Port>Change Password>Show all users
User ID
1
2
3
4
UserName
su
user
tech
oper
Access Level
Administrator
Monitor
Technician
Administrator
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-8. Typical Show All Users Screen
Note
To see the options available for this screen, display the help screen by typing ?.
2. To delete an existing user, move the cursor to the appropriate row and then
type R. You will be required to confirm.
3. To add a new user, type A. You will see the Add New User screen. A typical
screen is shown in Figure 4-9.
4-8
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
...ation>System>Control Port>Serial Port>Change Password>Show all users
User ID
1. UserName
2. Access Level
(5)
... (new user)
>
(Operator)
>
#-Db Undo; S-Save
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-9. Typical Add New User Screen
4. Select UserName and type the desired user name (up to 8 characters).
5. If necessary, change the access level, which by default is Monitor (see Chapter
3 for details on the capabilities of each access level).
•
To change the access level, select Access Level and then press <Enter>.
•
You will see a selection screen with four access levels (Figure 4-10). The
Operator level is not defined for Megaplex-4100 (it has the same
capabilities as the Monitor).
MP-4100
...rt>Serial Port>Change Password>Show all users>Access Level (Monitor)
1.
2.
3.
4.
Monitor
Technician
Operator
Administrator
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-10. Typical Access Level Selection Screen
•
Type the number corresponding to the desired level, and then press
<Enter>.
6. To confirm the changes, select Save (type S).
7. You will see a User has been added!! Update DB to finalize process!! message.
Press any key to return to the Show All Users screen, updated with the new
user name and access level.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-9
Chapter 4 Configuration
Note
Installation and Operation Manual
The new user is assigned the factory default password, 1234. To change it, use
the procedure described on page 4-5.
8. To add or delete all the required users, repeat the process described above as
required.
9. To activate the updates users, type % to update the database and then
confirm the action.
Configuring the Ethernet (ETH) Port
Navigate to Configuration>System>Control Port>ETH to configure the parameters
of the Ethernet management ports, CONTROL ETH, located on the CL modules.
Each CONTROL ETH port can be assigned its own parameters. However, both
ports use the management IP address of the Megaplex-4100, configured by
means of the Quick Setup or Host IP screen.
Figure 4-11 shows a typical ETH port selection screen.
MP-4100
Configuration>System>Control Port>ETH
1. CL-A>
2. CL-B>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-11. Typical ETH Port Selection Screen
³
To select the ETH port to be configured:
Type the number of the port on the ETH screen, and then press <Enter>. You will
see the port configuration screen. A typical screen is shown in Figure 4-12.
4-10
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
`
MP-4100
Configuration>System>Control Port>ETH>CL-A
1. Admin Status
2. Routing Protocol
3. User Name
>
(Up)
>
(None)
... ()
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-12. Typical ETH Configuration Screen
³
To define the CONTROL ETH port parameters:
Select the number of the desired parameter and then press <Enter>. The
parameters are explained in Table 4-2.
Table 4-2. ETH Configuration Parameters
Parameter
Function
Values
Admin Status
Used to enable/disable the flow
of management traffic through
the selected Ethernet port
DOWN – The flow of management traffic is disabled. This
state should be selected as long as the configuration of
the corresponding port has not yet been completed, or
when it is necessary to stop traffic flow through the port.
UP – The flow of management traffic is enabled.
Default: UP
Routing
Protocol
Selects the routing protocol for
management traffic carried
through the CONTROL ETH port
NONE – Dynamic routing of management traffic is not
supported.
PROPRIETARY RIP – The management traffic is routed
using the RAD RIP proprietary routing protocol.
RIP 2 – The management traffic is routed using the RIP2
protocol.
Default: NONE
User Name
Used to enter a logical name for
the selected CONTROL ETH port
Up to 10 characters.
Default: Empty string
Configuring Host IP Parameters and SNMP Communities (with SNMPv3
Disabled)
Use the following procedure to define the Megaplex-4100 management agent IP
communication parameters (the management agent is referred to as the host) –
the same parameters that can be configured using Configuration > Quick Setup.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-11
Chapter 4 Configuration
Installation and Operation Manual
Note that only one IP address need be assigned to the Megaplex-4100
management agent, because at any time only one of the CL modules is online
(this IP address is automatically “moved” when the online CL module is changed).
When SNMPv3 security features are disabled (see Section 4.2) and you want to
enable SNMP management, you must also configure the SNMP community names.
However, before starting, first you may have to disable the SNMPv3 security
features, as explained below, because otherwise it is not possible to directly
configure SNMP community names.
³
To disable the SNMPv3 security features:
1. Navigate to Configuration > System > Management.
A typical Management screen with SNMPv3 security features enabled is
shown in Figure 4-13.
Megaplex-4100
Configuration>System>Management
1.
2.
3.
4.
5.
6.
7.
8.
Device Info
Host IP
Manager List
Mng Access
Flow
SNMP Engine ID
SNMPv3
SNMPv3 Setting
>
>
[]>
>
>
>
(Enabled))
>
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-13. Typical Management Screen (SNMPv3 Enabled)
2. To change the state, select the state is toggled to Disabled, and you are
prompted to confirm by a message that explains the effects: Current
configuration of SNMP agent will be deleted! Continue? (Options: Y/N):
To abort, type n
To confirm, type y.
3. The screen is refreshed and the SNMPv3 Setting item is removed.
³
To define the host IP communication parameters:
1. Navigate to the Configuration > System > Management > Host IP screen.
A typical Host IP screen, as seen when SNMPv3 is Disabled, is shown
below.
4-12
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Megaplex-4100
Configuration>System>Management>Host IP
1.
2.
3.
4.
5.
6.
IP address
Subnet Mask
Default Gateway
Read Community
Write Community
Trap Community
...
...
...
...
...
...
(172.17.171.234)
(255.255.255.0)
(172.17.171.1)
(public)
(private)
(public)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-14. Typical Host IP Screen (SNMPv3 Security Features Disabled)
1. Refer to Table 4-3, and configure the Host IP parameters.
Table 4-3. Host IP Parameters
Parameter
Function
Values
Host IP Address
Used to enter the IP address of the
Megaplex-4100 management agent
Type the desired IP address, using the
dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
periods).
Default: 0.0.0.0
Subnet Mask
Used to enter the IP subnet mask of the
Megaplex-4100 management agent
Type the desired IP subnet mask, using the
dotted-quad format. Make sure to select a
subnet mask compatible with the selected IP
address, and whose binary representation
consists of consecutive “ones”, followed by
the desired number of consecutive “zeroes”.
Default: 0.0.0.0
Default Gateway Used to specify the IP address (usually an IP
router port) to which the Megaplex-4100
management agent will send packets when
the destination IP address is not within the
subnet specified in the Mask field.
Type the desired IP address, using the
dotted-quad format. Make sure the IP
address address is within the subnet of the
host IP address.
Default: 0.0.0.0
The default value, 0.0.0.0, means that no
default gateway is defined
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-13
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Read
Enter here the read-only SNMP community Enter the desired alphanumeric string (pay
name to be accepted by the Megaplex-4100 attention to case).
management agent.
Default: public
SNMP-based management stations using
this community will not be able to modify
the Megaplex-4100 configuration, nor
initiate diagnostic activities.
This parameter is displayed only when
SNMPv3 is Disabled
Write
Enter here the read-and-write SNMP
community name to be accepted by the
Megaplex-4100 management agent.
Enter the desired alphanumeric string (pay
attention to case).
Default: private
Use this community for SNMP-based
management stations that must be able to
perform all the activities.
This parameter is displayed only when
SNMPv3 is Disabled
Trap
Enter here the SNMP community name that
will be specified by the Megaplex-4100
management agent in the traps sent to
SNMP-based management stations.
Enter the desired alphanumeric string (pay
attention to case).
Default: public
This parameter is displayed only when
SNMPv3 is Disabled
Configuring Management Access
Use the following procedure to control globally the access to the Megaplex-4100
management agent using Telnet, SNMP management stations, and/or Web
browsers. This procedure enables to block the desired access options at the
Megaplex-4100 level, overriding the access rights of any user that may be logged
on the Megaplex-4100.
The supervisory terminal can always be used to access the Megaplex-4100
management agent.
To navigate to the required screen, use Configuration>System>Management>
Mng Access.
A typical Mng Access screen is shown below.
4-14
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Megaplex-4100
Configuration>System>Management>Mng Access
1. Telnet>
2. WEB
>
3. SNMP >
(Enable )
(Enable )
(Enable )
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-15. Typical Mng Access Screen
³
To change the global access rights:
1. Type the number corresponding to the management means to be modified,
and then press <Enter> to display the corresponding selection screen.
2. On the selection screen, type the number of the desired option and then press
<Enter>. The selection screen closes.
3. Repeat the process until all the desired management access means have been
defined.
4. The new selections are automatically saved.
Configuring the Manager List (with SNMPv3 Disabled)
Use the following procedure to define the IP addresses of Telnet hosts and Web
browsers that may manage the Megaplex-4100.
For SNMP management stations, the authorized managers are defined as follows:
•
When SNMPv3 is Disabled¸ this procedure also defines the IP addresses of
SNMP management stations, and specifies whether a station will receive or
not traps generated by the local Megaplex-4100.
•
When SNMPv3 is Enabled, refer to Section 4.2 for instructions.
To navigate to the required screen, use Configuration>System>Management>
Manager List.
A Manager List screen, as seen when first opened, is shown in Figure 4-16.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-15
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Management>Manager List
Managers ID
IP Address
Alarms Trap
>
A-Add;%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-16. Typical Factory Default Manager List Screen
Note
³
To see the navigation keys available for this screen, type ? (help).
To add a new management station:
1. Type a and then press <Enter> to display the new station configuration screen.
A typical screen with the factory defaults is shown in Figure 4-17.
MP-4100
Configuration>System>Management>Manager List
Managers ID
1. IP Address
2. Alarms Trap
(1)
... (0.0.0.0)
>
(Enable)
>
#-Db Undo; S-Save
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-17. Add New Manager Screen
2. Select each parameter in sequence, and configure the desired value using the
guidelines in Table 4-4.
Table 4-4. Manager List Parameters
Parameter
Function
Values
Managers ID Index number of management station, 1 to 10 Automatically assigned when a new manager is
added.
Default: Next free index
4-16
Configuring MP-4100 for Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
IP Address
Used to enter the IP address of the
management station
Type the desired IP address, using the
dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
periods).
Default: 0.0.0.0
Alarms Trap Specifies whether traps will be sent to the
management station, in case an alarm report
is configured to result in the generation of a
trap (for configuration instructions, refer to
Chapter 6).
ENABLE — The Megaplex-4100 will send traps
to this management station.
DISABLE— The Megaplex-4100 will not send
traps to this management station.
Default: ENABLE
Other types of traps are always sent to all the
configured managers
3. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new station. To display the Manager List
again, press ESC.
MP-4100
Configuration>System>Management>Manager List
Managers ID
1
Ip Address
172.123.102.8
1. Change cell
Alarms Trap
Enable
... (172.123.102.8)
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-18. Typical Manager List Screen after Adding First Management Station
4. Repeat the process until all the desired management stations have been
defined. A new page is automatically added when the number of stations
exceeds the maximum that can be displayed on the first page.
5. When done, the configuration is automatically saved.
³
To edit an existing management station:
1. Use the left and right arrows to move the selection block to the desired cell in
the row of the management station to be edited.
2. Select Change cell to open the corresponding field for editing. Use the
procedure described above to select a new value for the selected field.
Megaplex-4100 Ver. 2.0
Configuring MP-4100 for Management
4-17
Chapter 4 Configuration
Installation and Operation Manual
Configuring System Logistic Information
Use the following procedure to specify logistic information to be used to identify
the specific Megaplex-4100 unit, provide contact information, etc.
To navigate to the required screen, use Configuration>System>Management>
Device Info.
A typical Device Info screen is shown in Figure 4-19. The information that can be
defined using this screen is described in Table 4-5.
MP-4100
Configuration>System>Management>Device Info
Sys Description...
Object ID
...
1. Device Name
...
2. Contact Person ...
3. Location ID
...
(Sys type:MP-4100 Sys Ver:1.01 Chassis Revision:0)
(radMP4100)
()
(Name of contact person)
(The location of this device)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
Figure 4-19. Typical Device Info Screen
To configure an entry, select its number and then type the desired text. When
done, press <Enter>.
Table 4-5. Device Info Parameters
Parameter
Function
Values
Sys Description
Displays a fixed string that identifies the system type,
its version and the chassis revision
Depends on equipment version
Object ID
Displays the formal Megaplex-4100 object identifier
(its MIB root)
radMP4100
Device Name
Used to assign an identification string to this unit
Up to 22 characters.
Default: Empty string
Contact Person
Used to enter the name of the person to be contacted Up to 46 characters.
in matters pertaining to this equipment unit
Default: Name of contact person
Location ID
Used to enter a description of the physical location of
this equipment unit
4-18
Configuring MP-4100 for Management
Up to 34 characters.
Default: The location of this device
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
4.2
Chapter 4 Configuration
Configuring Megaplex-4100 for SNMPv3
Management
This section presents the main SNMPv3 capabilities, and explains the following
procedures:
•
How to enable the SNMPv3 security features
•
How to configure Megaplex-4100 for management with SNMPv3 security
features.
•
How to configure Megaplex-4100 for compatibility with management stations
that cannot use the SNMPv3 security features, to ensure compatibility with
SNMP support in previous Megaplex-4100 software and management station
versions. This is performed by mapping SNMPv1 settings to SNMPv3 settings.
You can find below a concise description of the main SNMPv3 capabilities
applicable to Megaplex-4100, and descriptions of terms related to the SNMPv3
configuration parameters of Megaplex-4100.
Overview of SNMPv3 Capabilities
The basic SNMP protocol (SNMP version 1, or SNMPv1) can neither authenticate
the source of a management message, nor provide privacy (encryption). The
SNMP version 2 of the protocol (SNMPv2) adds some functional improvements
and extensions to SNMPv1, but does not address security problems.
To overcome the security shortcomings of SNMPv1 and SNMPv2, Megaplex-4100
can be configured to use the security features of SNMP protocol version 3
(SNMPv3).
SNMPv3 provides a security framework for SNMPv1 and SNMPv2 that adds the
following main capabilities:
•
Authentication – checks the integrity of management data, and also verifies
its origin to ensure that unauthorized users will not masquerade as
authorized users
•
Privacy – ensures that unauthorized users cannot monitor the management
information passing between managed systems and management stations
•
Authorization and access control – ensures that only authorized users can
perform SNMP network management functions and contact the managed
systems.
To support these additional capabilities, SNMPv3 also includes specific
administrative features, such as naming, security policies, user and key
management, and selectable notification capabilities.
Note
Key management requires the using organization to implement an appropriate
key distribution method, which is beyond the scope of SNMPv3, and therefore is
also not covered in this manual. It is the responsibility of the using organization
to maintain appropriate key management and distribution channels.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-19
Chapter 4 Configuration
Installation and Operation Manual
User-Based Security Model (USM)
SNMPv3 authentication and privacy services are provided by means of the
User-Based Security Model (USM), defined in RFC2272. Proper use of USM
protects against modification of information in transit from an authorized entity
(including modification of message order, delaying or replaying of valid messages
to change their effect, etc.), prevents an unauthorized entity from performing
management operations by assuming the identity of an authorized entity, and
prevents disclosure of the contents of the messages exchanged between a
management station and an agent.
To achieve these goals, USM uses authentication to check the integrity of
transmitted messages, and encryption to prevent disclosure:
•
Authentication mechanisms. Mechanisms that provide integrity checks based
on a secret key are usually called message authentication codes (MAC).
Typically, message authentication codes are used between two parties that
share a secret key in order to validate the information transmitted between
these parties. Therefore, an SNMP engine requires an authentication key and
a privacy key (actually, for each management session, a set of one-time
session keys are generated). Separate values of these two keys are
maintained for each local and remote user, and their values must be stored
by each user, because the keys are not accessible via SNMP.
USM authentication protocol is based on the key-Hashing Message
Authentication Code (HMAC), described in RFC2104. HMAC uses a userselected secure hash function and a secret key to produce a message
authentication code. USM allows the use of one of two alternative
authentication protocols, where both generate a 96-bit output that is used
to check message integrity:
HMAC-MD5-96: HMAC is used with MD5 (Message Digest algorithm 5) as the
underlying hash function.
HMAC-SHA-96: HMAC is used with SHA-1 (Secure Hashing Algorithm 1).
•
Encryption mechanism. USM uses the cipher block chaining (CBC) mode of the
Data Encryption Standard (DES) for encryption, with a key length of 56 bits.
SNMP Security Levels
The USM capabilities enable the user to select the level of security at which SNMP
messages can be sent or with which operations are being processed. The
available options are as follows:
•
No authentication and no privacy (encryption) – the lowest protection.
•
With authentication, but without privacy
•
With authentication and with privacy – the best protection level.
SNMPv3 Administrative Features
The administrative features of SNMPv3 enable determining the entities that are
allowed to manage an entity, for example, the Megaplex-4100. There are two
administrative aspects:
4-20
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 4 Configuration
•
User management. During SNMPv3 configuration, it is necessary to define
allowed users and their security attributes. For each user, it is possible to
select the security level, and the passwords used for each type of protection
(authentication and/or privacy) needed at the selected level.
•
Target and notification management. As part of the SNMPv3 configuration,
you can also define the notification capabilities for a list of entities referred
to as targets (of notification messages). For each target, you can specify a
message processing model, a security model, and the required security level.
You can also define a list of notifications that can be sent to the
corresponding target.
Megaplex-4100 supports only the sending of traps for notification purposes.
View-Based Access Control Model (VACM)
SNMP manager authorizations are defined by means of the view-based access
security model (the name of the model is derived from the method used to
define the authorizations: control over the MIB parts that can be viewed by each
manager).
VACM makes it possible to configure each SNMPv3 agent to allow different levels
of access to different managers: for example, the Megaplex-4100 SNMPv3 agent
may restrict some managers to view only the Megaplex-4100 performance
statistics, and allow others to view and update Megaplex-4100 configuration
parameters. Moreover, the SNMPv3 agent can also limit what a manager can do
by accepting only commands that invoke parameters included in certain parts of
the relevant MIBs (for example, read-only access to the configuration parameters
part of a MIB, and read-write access to the diagnostics part).
The access control policy used by the agent for each manager must be
preconfigured (the policy essentially consists of a table that details the access
privileges of each authorized manager). For Megaplex-4100, the configuration of
the VACM parameters can only be made by means of a MIB browser, and/or by
SNMP commands.
Note
RAD also offers a dedicated SNMPv3 Manager utility to help you edit parameters
not covered by the supervision terminal screens. For additional information,
contact RAD Technical Support.
Configuring SNMP Engine ID
The SNMP engine ID is a parameter defined in relation with SNMPv3, whose
primary function is to provide a unique and unambiguous identifier of the local
SNMP engine (processor), which is part of the Megaplex-4100 management
subsystem. Thus, it thus also identifies the local Megaplex-4100.
SNMPv3 bases the generation of session keys on several parameters, one of
them being the SNMP engine ID. Therefore, the SNMP engine ID must always be
configured before configuring any other SNMPv3 parameters, and in particular –
before configuring users (if you change the SNMP engine ID, you must also
reconfigure the users). Thus, you can configure the SNMP engine ID even when
SNMPv3 support is disabled.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-21
Chapter 4 Configuration
Installation and Operation Manual
The SNMP engine ID is a string that has three components:
³
•
An automatically-generated, fixed part
•
A part that identifies the configuration type (method) used to derive the
user-defined part is selectable.
•
A user-defined part, which must be unique within the SNMP-managed
network. The method used to configure this part depends on the
configuration type.
To specify the SNMPv3 Engine ID:
1. Navigate to Configuration > System > Management.
2. Select SNMPv3 Engine ID.
A typical SNMP Engine ID screen, as seen when using the text
configuration type, is shown in Figure 4-20. The current SNMP engine ID
string appears in the Engine ID field: whenever the Engine ID Config Type
is changed, the string is automatically updated.
3. To change the user-defined part and/or the configuration method used to
derive the user-defined part, select Engine ID Config Type and/or Rest Bytes,
(the appropriate procedure is described below). Megaplex-4100 supports the
following configuration types:
IPv4
The user-defined part is based on the host IP address. This
ensures that the user-defined part is unique within the
SNMP-managed network.
After selecting this option, the Engine ID field is updated to
reflect the automatically assigned user part (based on the
Megaplex-4100 host IP address), and the Rest Bytes field
disappears.
MAC Address
The user-defined part is based on the host MAC address.
This option also ensures that the user-defined part is
unique.
After selecting this option, the Engine ID field is updated to
reflect the automatically assigned user part (based on the
Megaplex-4100 host MAC address), and the Rest Bytes
field disappears.
Text
The user-defined part is entered as a text string, which
must comprise 4 to 27 alphanumeric characters.
After selecting this option, the Engine ID field is reset to
display only the fixed part and the configuration type part,
and a Rest Bytes field appears.
To modify the user-defined part, select Rest Bytes, and
then type the prescribed string.
When done, press <Enter> to confirm. The string is added
to the Engine ID field (if the string is too long for the
available display space, it is truncated, in which case the
last digits are replaced by an ellipsis …)
4-22
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
4. After making changes on the SNMP Engine ID screen, a new item, S – Save, is
added: to activate the new engine ID, type s.
MP-4100
Configuration>System>Management>SNMP Engine ID
Engine ID
... (800000a40400000000 )
1. Engine ID Config Type >
(Text)
2. Rest Bytes
... ()
>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-20. Typical SNMP Engine ID Screen
Enabling/Disabling SNMPv3 Security Features
When starting the SNMP configuration activities, the first action is to select
whether to enable or disable the SNMPv3 security features: this action effects all
the other SNMP parameters except SNMP Engine ID.
When changing the SNMPv3 mode, all the SNMPv3 settings are erased, and the
factory defaults are restored. As explained in the Configuring Authorized User
Security Parameters section, starting from the factory defaults will enable
preparing a new set of SNMPv3 settings in accordance with your specific
application requirements.
To enable configuring the SNMPv3 parameters, you must enable SNMPv3.
³
To enable the SNMPv3 security features:
1. Navigate to Configuration > System > Management.
A typical Management screen with SNMPv3 security features disabled (the
factory default state) is shown in Figure 4-21.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-23
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Management
1.
2.
3.
4.
5.
6.
7.
Device Info
Host IP
Manager List
Mng Access
Flow
SNMP Engine ID
SNMPv3
>
>
[]>
>
>
>
(Disabled))
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-21. Typical Management Submenu (SNMPv3 Disabled)
2. To change the state, select SNMPv3: you are prompted to confirm by a
message that explains the effects: Current configuration of SNMP agent will be
deleted! Continue? (Options: Y/N):
To abort, type n
To confirm, type y.
3. After typing y, the SNMPv3 state is toggled to Enabled, and a S – Save item is
added.
4. To activate the selection, type s. The screen is refreshed and the SNMPv3
Setting item, used to access the SNMPv3 configuration tasks (see the
Configuring for SNMP Management with SNMPv3 Security section) is added.
Note
The same sequence is used to disable SNMPv3 (see also the Configuring Host IP
Parameters and SNMP Communities (with SNMPv3 Disabled) section).
Configuring for SNMP Management with SNMPv3 Security Features
SNMPv3 Configuration Sequence
Note
Before starting, make sure to configure the SNMP engine ID and enable SNMPv3
as explained above.
The SNMPv3 configuration sequence is as follows:
1. Configure security attributes for the prescribed users (management
stations).
2. Add the prescribed notification tags.
3. Assign traps to each notification tag, to create a tag list.
4. Specify for each target its IP address, define its parameter set, and assign
notification tags.
5. Add target (management stations) parameters.
4-24
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 4 Configuration
With SNMPv3, the managers configured by means of the Manager List screen (see
the Configuring the Manager List (with SNMPv3 Disabled) section) are no longer
relevant: only the configured targets are managers.
However, to enable synchronizing the managers configured in the Manager List
table with SNMPv3 managers, all the IP addresses configured in the Manager List
table are automatically added to the target list when SNMPv3 is enabled (they
can be seen in the Summary Target Table – see the Viewing the Summary Target
Table section), but they are not active until their security and management
parameters are defined.
The SNMPv3 parameters are configured by means of the SNMPv3 Setting
submenu. A typical submenu is shown Figure 4-22. The parameters displayed on
the submenu and the tasks that can be initiated are explained in Table 4-6.
Note
In addition to the parameters that can be configured using the SNMPv3 Setting
submenu, Megaplex-4100 supports additional parameters used to customize
SNMPv3 management in accordance with the application requirements. These
parameters can only be configured by means of a MIB browser, and/or SNMP
commands (RAD may also offer a dedicated SNMPv3 Manager utility to help you
edit the additional parameters). For additional information, contact RAD Technical
Support.
MP-4100
Configuration>System>Management>SNMPv3 setting
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
SNMPv3 Factory Defaults
Summary User Table
Summary Target Table
(4)
(370)
... (1500)
>
>
>
[]
[]
>
Please select item <1 to 6>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-22. Typical SNMPv3 Setting Submenu
Table 4-6. SNMPv3 Setting Submenu
Parameter
Function
Values
Engine Boots
Displays the number of times that the
SNMP engine has been reinitialized since
the SNMP Engine ID was last configured
The display range is 1 to 2147483647.
Megaplex-4100 Ver. 2.0
Default: 0
Configuring Megaplex-4100 for SNMPv3 Management
4-25
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Engine Time
Displays the time, in seconds, that expired The display range is 0 to 2147483647.
since the value of the Engine Boots field
Default: 0
was last changed (that is, the time since
the last SNMP engine reinitialization)
SNMP Message
Size
Displays the maximum allowed length, in
octets, of the SNMP messages that the
Megaplex-4100 can send or receive, and
process.
The allowed range is 484 to 2147483647.
Default: 1500
In addition to the maximum supported by
the Megaplex-4100 SNMP engine, the
message size must be supported by all the
transport links available to communicate
with the SNMP engine
See Table 4-7
Users
Opens the Users submenu, used to
configure the USM parameters to be used
by the authorized SNMPv3 users
Targets & Notify
Opens the Targets & Notify submenu, used See Table 4-8 to Table 4-11
to configure the parameters of the targets
(management stations that can manage
the Megaplex-4100), and configure
notifications of Megaplex-4100 events
SNMPv1/v3
Mapping
Opens the SNMPv1/v3 Mapping submenu,
used to configure the mapping of SNMPv1
security parameters to SNMPv3
parameters, to enable the Megaplex-4100
to support all the SNMP versions
See Table 4-11
SNMPv3 Factory
Defaults
Used to reload the SNMPv3 factory default
parameters.
To restore defaults, select SNMPv3 Factory
Defaults, and then confirm the action
This is useful for erasing the existing
configuration parameters and restoring the
SNMP engine to a known state.
In particular, this function is needed to
recover from configuration errors that may
prevent SNMP management
Summary User
Table
Displays information on the existing users
and their main configuration data
See the Viewing the Summary User Table
section
Summary Target
Table
Displays information on the existing
targets, and their main configuration data
See the Viewing the Summary Target Table
section
Configuring Authorized User Security Parameters
Megaplex-4100 supports up to ten SNMPv3 managers, each having
independently-configurable authorizations and security attributes. The security
attributes needed by the USM to protect the SNMP traffic between
4-26
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Megaplex-4100 and the prescribed managers are configured by means of Users
screen.
Megaplex-4100 has a single factory-default user, designated by the security
name initial, which is configured for non-secure operations (that is, no
authentication and no privacy). Non-secure operations are essential as a starting
point for preliminary configuration, but additional users with appropriate
authorizations and security attributes must be configured as soon as possible, to
avoid defeating the very purpose of SNMPv3.
When several users are already defined, you can scroll the Security Name names
by typing f (forward) or b (backward). Always remove a user when you must
change its security parameters, and then define a new user with the desired
parameters.
You can view the existing users, and their authorizations and security attributes
by selecting Summary User Table, as explained in the Viewing the Summary User
Table section.
Note
³
User access control policies are defined via the vacmSecurityToGroupTable
and vacmAccessTable tables, which can be accessed only as explained in the
Note on page 4-25.
To configure USM parameters for new users:
1. Navigate to Configuration > System > Management > SNMPv3 Setting > Users.
A typical SNMPv3 Setting screen with the factory-default user parameters
is shown in Figure 4-23. The user configuration parameters are explained
in Table 4-7.
MP-4100
Configuration>System>Management>SNMPv3 setting>Users
1. Security Name
2. Authentication Protocol
... (initial)
>
(usmNoAuthProtocol)
>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-23. Typical Factory-Default Users Screen
2. To add a new user, select Security Name and then type the desired user name,
to replace the displayed user name.
3. Select Authentication Protocol, and then select one of the options listed in
Table 4-7.
4. Additional fields, explained in Table 4-7, are displayed automatically after you
make selections (and press <Enter> to confirm) for the Authentication Protocol
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-27
Chapter 4 Configuration
Installation and Operation Manual
and Privacy Protocol. Figure 4-24 shows a typical new user configuration
screen, as seen after making all the necessary selections.
MP-4100
Configuration>System>Management>SNMPv3 setting>Users
1.
2.
3.
4.
5.
Security Name
Authentication Protocol
Privacy Protocol
Authentication Password
Privacy Password
... (User1)
>
(usmHMACMD5AuthProtocol)
>
(usmDESPrivProtocol)
...
...
>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
----------------------------------------------------------------------------
Figure 4-24. Typical Users Screen for New User
5. Repeat the configuration steps for the other users. When done, save the
configuration.
Table 4-7. SNMPv3 Users Security Parameters
Parameter
Function
Values
Security Name
Used to select the user name (the security
name and the user name are equivalent
under SNMPv3).
Alphanumeric string of up to 32 characters.
Default: userName
This security name is used to tie the USM
security attributes with management
attributes, in particular, the authorizations
configured by means of the Target Param
screen, the IP address configured by means
of the Target Address screen, etc.
Authentication
Protocol
Used to select the authentication protocol
for this user.
usmNoAuthProtocol – no authentication
protocol. This also prevents the use of
privacy (encryption) for this user.
SNMPv3 uses the key-Hashing Message
Authentication Code (HMAC) authentication usmHMACMD5AuthProtocol – use of
method, described in RFC2104
authentication protocol enabled. The
authentication protocol is HMAC-MD5-96
(HMAC with MD5 (Message Digest algorithm
5) as the underlying hash function)
usmHMACSHAAuthProtocol – use of
authentication protocol enabled. The
authentication protocol is HMAC-SHA-96
(HMAC with SHA-1 (Secure Hashing Algorithm
1 as the underlying hash function).
Default: usmNoAuthProtocol
4-28
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Privacy Protocol
Used to select the privacy (encryption)
protocol for this user.
usmNoPrivProtocol – no privacy protocol.
This parameter is not displayed when
Authentication Protocol is
usmNoAuthProtocol
usmDESPrivProtocol – use of privacy protocol
enabled. SNMPv3 uses the cipher block
chaining (CBC) mode of the Data Encryption
Standard (DES) for encryption, with a key
length of 56 bits.
Default: usmNoPrivProtocol
Authentication
Password
Used to enter the password to be used by
the authentication protocol.
Alphanumeric string of up to 32 characters.
Default: Empty string
Make sure to check, and if necessary
correct, your entry before pressing <Enter>
to confirm: after pressing <Enter>, the
typed string is removed.
This parameter is not displayed when
Authentication Protocol is
usmNoAuthProtocol
Privacy
Password
Used to enter the password required to use Alphanumeric string of up to 32 characters.
privacy.
Default: Empty string
Make sure to check, and if necessary
correct, your entry before pressing <Enter>
to confirm: after pressing <Enter>, the
typed string is removed.
This parameter is displayed only when
Privacy Protocol is usmDESPrivProtoco
³
To remove an existing user:
1. Display the required Security Name by scrolling with f (forward) or b
(backward).
2. Type r and then confirm.
Configuring SNMPv3 Management Attributes
A typical Targets & Notify submenu is shown in Figure 4-25. The activities started
from this submenu supplement the user security attributes by enabling to define
the additional attributes needed for management.
The submenu tasks are listed below:
•
Target Params: used to configure a general set of parameters for each target,
and associate it with a particular set of user security attributes (identified by
specifying a Security Name already configured in accordance with Table 4-7).
Each target is assigned a unique logistic identifier, the target Name, for
identifying the associated set of parameters (see Table 4-8). Note however
that in Table 4-10 this identifier is referred to as Params Name
•
Target Address: used to configure the IP address and notification parameters
for a selected target logistic Name (Table 4-10). The IP address is associated
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-29
Chapter 4 Configuration
Installation and Operation Manual
with the Params Name (defined in Table 4-8) for identification, and with a
Tag List for identifying the set of notification parameters (see Table 4-9)
•
Notify: used to configure notification tags (see Table 4-9). Each set of
notification parameters is assigned a unique Tag name for identification.
Note however that in Table 4-10 this identifier is referred to as Tag List
•
Trap: used to select traps included in the list of each selected notification tag
You can view the existing targets and their management attributes by selecting
Summary Target Table, as explained in the Viewing the Summary Target Table
section.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
>
>
>
>
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-25. Typical Targets & Notify Submenu
Configuring Target Parameters
³
To configure a new set of target parameters:
1. Navigate to Configuration > System > Management > SNMPv3 Setting > Targets
& Notify.
2. Select Target Params.
A typical Target Params screen is shown in Figure 4-26.
3. Configure the target parameters, and then type s to save. The parameters that
can be configured are explained in Table 4-8.
4-30
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
...ation>System>Management>SNMPv3 setting>Targets & Notify>Target Params
1.
2.
3.
4.
5.
Name
Message Processing Model
Security Model
Security Name
Security Level
...
>
>
...
>
()
()
()
()
()
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-26. Typical Targets Params Screen
Table 4-8. Target Params Parameters
Parameter
Function
Values
Name
Used to enter the unique logistic name
assigned to the target (also referred to as
Params Name on other screens).
Alphanumeric string of up to 32 characters.
Default: Empty string
To enter a new target name, type the
desired name in this field
Message
Processing
Model
Used to select the message processing
model to be used when generating and
processing SNMP messages for this target
The available selections are: SNMPv1, SNMPv2c
(SNMPv2 with community-based security
model), SNMPv2u (SNMPv2 with user-based
security model (USM)), and SNMPv3.
Default: SNMPv3
Security Model Used to select the security model to be
The available selections are: Any, SNMPv1,
used when generating and processing SNMP SNMPv2c, USM (User-Based Security Model),
messages for this target
and Not Defined.
Default: USM
Security Name
Used to select the security name which
identifies the security attributes applicable
to SNMP traffic exchanged with this target.
Alphanumeric string of up to 32 characters.
Default: Empty string
Use one of the names configured by means
of the Users screen
Security Level
Used to select the level of security to be
used when generating SNMP messages for
this target
The available selections are:
noAuthNoPriv – No authentication, no privacy.
authNoPriv – With authentication, no privacy.
authPriv – With authentication and privacy.
Default: noAuthNoPriv
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-31
Chapter 4 Configuration
Installation and Operation Manual
When several targets are already defined, you can scroll the target logistic Name
by typing f (forward) or b (backward). Always remove a target when you must
change one of its management attributes, and then define a new target with the
desired parameters.
³
To remove an existing target:
1. Display the required Name by scrolling with f (forward) or b (backward).
2. Type r and then confirm.
Configuring Notification Tags
A notification tag identifies a list of traps that can be sent to selected targets.
The configuration of a new notification tag is performed in two steps:
1. Adding a new notification tag.
2. Selecting the list of traps identified by the notification tag.
³
To add a new notification tag:
1. Navigate to Configuration > System > Management > SNMPv3 Setting > Targets
& Notify.
2. Select Notify.
3. Configure the parameters as explained in Table 4-9, and then type s to save.
A typical Notify screen, as seen after configuring a new notification tag,
is shown in Figure 4-27. The Type field is displayed only after selecting a
Name.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Notify
Type
1. Name
2. Tag
>
(trap)
... (notify_set_1)
... (v3traps)
>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-27. Typical Notify Screen
4-32
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-9. Notify Parameters
Parameter
Function
Values
Type
Displays the type of notifications generated
for the selected notification tag.
The only option is Trap.
Default: Trap
The type is always set to Trap, the only option
supported by Megaplex-4100
Name
Used to enter the logistic identifier associated
with this notification tag (also referred to as
Notify Name on other screens).
Alphanumeric string of up to 32 characters.
Default: Empty string
To enter a new target name, type the desired
name in this field
Tag
Used to enter the notification tag name, which Alphanumeric string of up to 32 characters.
is used to select entries for the events
Default: Empty string
associated with the Tag List in Table 4-10
When several notification tags are already defined, you can scroll their names by
typing f (forward) or b (backward). Always remove a notification tag when you
must change one of its attributes, and then define a new notification tag with
the desired parameters.
³
To remove an existing notification tag:
1. Display the required notification tag Name by scrolling with f (forward) or b
(backward).
2. Type r and then confirm.
³
To configure the trap and notification tag associations:
1. Navigate to Configuration > System > Management > SNMPv3 Setting > Targets
& Notify.
2. Select Trap.
A typical Trap screen is shown in Figure 4-28.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Trap
1. Trap Name
2. Notify Name
>
>
(link Up)
(notify_set_1)
>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-28. Typical Trap Screen
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-33
Chapter 4 Configuration
Installation and Operation Manual
Using the Trap screen, you can associate traps with the names appearing the
Notify screen (see Table 4-9). When done, type s to save.
Trap Name
Used to select a trap name for association with the
notification tag.
The selection is made on a separate screen, which list the
available traps. Each trap has an index number: type the
index number and then press <Enter> to associate the trap
with the notification tag.
Notify Name
Used to specify the corresponding notification tag (enter a
Name defined in Table 4-9).
The selection is made on a separate screen, which list the
available notification tags defined by means of Table 4-9.
Each name has an index number: type the index number
and then press <Enter> to select the notification tag.
³
To remove a trap from the list associated with a notification tag:
1. Display the required Trap by scrolling with f (forward) or b (backward).
2. Type r and then confirm.
Configuring Target Transport Parameters
The Target Address screen is used to configure the IP address and select a tag list
for a selected target.
³
To configure the target transport parameters:
1. Navigate to Configuration > System > Management > SNMPv3 Setting > Targets
& Notify.
2. Select Target Address.
A typical Target Address screen is shown in Figure 4-29.
MP-4100
...tion>System>Management>SNMPv3 setting>Targets & Notify>Target Address
1.
2.
3.
4.
Name
IP Address
Params Name
Tag List
...
...
...
...
()
()
()
()
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-29. Typical Target Address Screen
4-34
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
3. Configure the target transport parameters, and then type s to save. The
parameters that can be configured are explained in Table 4-10.
Table 4-10. Target Address Parameters
Parameter
Function
Values
Name
Used to enter the logistic name assigned to
the desired target transport parameters
Alphanumeric string of up to 32 characters.
Specifies the IP address of this target
Enter the prescribed IP address, in the dottedquad format.
IP Address
Default: Empty string
Default: Empty string
Params
Name
Specifies the logistic name used to identify the Alphanumeric string of up to 32 characters.
set of SNMP parameters to be used when
Default: Empty string
generating messages to be sent to this
transport address.
Use a Name defined in the Target Params
table (Table 4-8)
Tag List
Specifies a list of tag values which are used to
select target addresses for a particular
operation.
Alphanumeric string of up to 32 characters.
Default: Empty string
Use a Tag defined in the Notify table
(Table 4-9)
Configuring SNMPv1/v3 Mapping
This screen is used to configure the mapping of SNMPv1 security parameters
(communities) to SNMPv3 security parameters, to enable the Megaplex-4100 to
support all the SNMP versions.
A typical SNMPv1/v3 Mapping screen is shown in Figure 4-30. The parameters
that can be configured are explained in Table 4-11.
MP-4100
Configuration>System>Management>SNMPv3 setting>SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
...
...
...
...
()
()
()
()
>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-30. Typical SNMPv1/v3 Mapping Screen
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for SNMPv3 Management
4-35
Chapter 4 Configuration
Installation and Operation Manual
Table 4-11. SNMPv1/v3 Mapping Parameters
Parameter
Function
Values
Community
Index
Used to enter a unique index for this
mapping item
Alphanumeric string of up to 32 characters.
Community
Name
Used to enter the community string (a
Alphanumeric string of up to 32 characters.
SNMPv1 security parameter) to be mapped to Default: Empty string
a security name.
Default: Empty string
The community string is case-sensitive
Security Name
Specifies the security name (which identifies
a set of security attributes) to be used in
SNMPv3 messages for the selected
community name.
Alphanumeric string of up to 32 characters.
Default: Empty string
Use a Security Name already configured in
accordance with Table 4-7
Transport Tag
Specifies the IP address (manager) from
which SNMPv1 management requests will be
accepted for this community name.
Enter the prescribed IP address, in the
dotted-quad format.
Default: Empty string
Use a IP Address already configured in
accordance with Table 4-10
Viewing the Summary User Table
The Summary User Table screen displays information on the existing users and
their main configuration data. A typical Summary User Table screen is shown in
Figure 4-31. The user parameters are explained in Table 4-7.
MP-4100
Configuration>System>Management>SNMPv3 setting>Summary User Table
User
initial
Security Model
USM
Security Level
noAuthNoPriv
>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-31. Typical Summary User Table Screen
Viewing the Summary Target Table
The Summary Target Table screen displays information on the existing targets,
and their main configuration data:
4-36
Configuring Megaplex-4100 for SNMPv3 Management
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
•
Address – target IP address
•
MPModel – message processing model
•
SecModel – security model
•
SecName – security name
•
SecLevel – security level
All the managers configured in the Manager List table are automatically added to
this table when SNMPv3 is enabled, but if no security and management
parameters have been defined for the corresponding target address, all the table
fields in the corresponding row, except Address, remain empty.
A typical Summary Target Table screen is shown in Figure 4-32. The target
parameters are explained in Table 4-8 and Table 4-10.
MP-4100
Configuration>System>Management>SNMPv3 setting>Summary Target Table
Address
MPModel SecModel SecName
SecLevel
>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-32. Typical Summary Target Table Screen
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-37
Chapter 4 Configuration
4.3
Installation and Operation Manual
Configuring Megaplex-4100 for Operation
Managing Megaplex-4100 Configuration Databases
Before starting configuration activities, it is important to understand the
Megaplex-4100 database tools (reached from the DB Tools menu), used to
manage Megaplex-4100 databases.
Normally, only one database is needed to store the Megaplex-4100 configuration
parameters. However, Megaplex-4100 can store a few databases in the CL
module flash memory, and therefore, when necessary, it is possible to prepare
additional databases with alternative configurations, and store them in the
Megaplex-4100 flash memory for immediate availability. Megaplex-4100
databases are assigned index numbers in the range of 1 to 10.
Therefore, the following terms are used in respect to Megaplex-4100 databases:
•
Online database file: one database file, which is always assigned index
number 1, serves as the current online (active) database. This is the file
from which parameters have been downloaded to the Megaplex-4100
modules, and therefore it determines the current Megaplex-4100 operation
configuration.
•
All the other database files are simply stored in the flash memory. These
files may have been created by the user using the database tools or the
file system utilities, or received by TFTP from a remote host or
management station.
Any authorized user (including operators of management stations, etc.) can work
on the edit buffer without affecting the online database, for example:
•
Make changes to the database copy located in the edit buffer
•
Replace the edit buffer contents with the factory defaults
•
Load into the edit buffer another database file, thus also replacing the
current contents with new contents.
A desired database can be created or updated by a dedicated Update DB
command, which performs the following actions:
4. Initiates a sanity check on the edit buffer contents, and reports errors and
warnings.
5. If no errors are detected, saves the edit buffer contents to a specified
database (the database number is selected by the user).
4-38
•
Normally, changes are saved to the active, or online, database. In this case,
after successfully saving the buffer contents to flash memory,
configuration messages are automatically sent to the Megaplex-4100
subsystems to change their operating mode in accordance with the new
online database. As mentioned above, the number of the active database
is always 1, irrespective of the number of the database loaded into the edit
buffer as a basis for changes.
•
Alternatively, you can specify the number of another database, using the
Update DB command, in which to store the edit buffer contents. If the
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
database whose index is specified in the Update DB command is not yet
stored in the flash memory, a database with this index number is created
and the edit buffer contents are stored in it.
Note that alternative databases may be assigned any desired number,
except 1, because 1 is reserved for the active database.
6. When preparing alternative databases, it is convenient to change the default
database, that is, the database which is updated when you use the shortcut
% - DB Update:
•
If you do not select a specific default database, the shortcut updates the
active database (database 1)
•
If you specify another database stored in the flash memory as default, the
shortcut updates the default database. In this case, after preparing the
alternative database, it is recommended to return the default selection to
database 1.
Overview of DB Tools Menu
Figure 4-33 shows the structure of the DB Tools menu, used to manage the
Megaplex-4100 databases.
Load DB
DB Tools
1.
2.
3.
4.
5.
6.
Load DB
Default DB
Load HW
Update DB
DB List
Delete DB
Default DB
Update DB
DB List
Delete DB
Figure 4-33. DB Tools Menu Structure
Database Management
A typical DB Tools menu is shown in Figure 4-34. The functions performed by
means of the various options available on the DB Tools menu are explained in
Table 4-12.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-39
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>DB Tools
1.
2.
3.
4.
5.
Load DB
Default DB
Load HW
Update DB
Delete DB
>
>
(1)
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-34. Typical DB Tools Menu
Table 4-12. DB Tools Menu Functions
Item
Action
Load DB
Load a selected database into the edit buffer.
This database is now the candidate for becoming the online database (this
will occur after a successful database update)
Default DB
Select the default database. This is the database to which parameters will
be saved when using the % – DB Update hotkey.
The factory defaults are provided as database 1
Load HW
Load the factory defaults into the edit buffer, and then read the hardware
(modules) installed in the Megaplex-4100, and update the list of
programmed hardware accordingly
Update DB
Copy the contents of the edit buffer to a selected database in the flash
memory. This function can also be used to create and store a new database.
If you save the changes to the default database, the changes will be
activated, that is, the operation mode of the Megaplex-4100 changes in
accordance with the new parameter values.
Delete DB
Delete a database stored in the Megaplex-4100
The following sections explain how to use the commands available on the DB
Tools menu to perform typical activities. For typical applications of these
commands, refer to the preliminary configuration instructions given in Chapter 3.
³
To load a selected database into the edit buffer:
1. Select Load DB on the DB Tools menu.
2. On the Load DB screen (Figure 4-35), type the number of the desired
database. Note that only the numbers of the existing databases are displayed
on the screen.
4-40
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>DB Tools>Load DB
1. 1
2. 2
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-35. Typical Load DB Screen
3. Press <Enter>: after a short delay, the execution is confirmed by the following
message Database # was loaded. Press any key to continue, where # stands
for the number of the selected database.
4. Press any key: you will see the DB Tools menu again.
³
To select the default database:
1. Select Default DB on the DB Tools menu.
2. On the Default DB screen (Figure 4-36), type the desired database index
number, and then press <Enter>. Note that you can select any index number,
even if the corresponding database is not yet stored in the flash memory.
MP-4100
Configuration>DB Tools>Default DB (1)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
1
2
3
4
5
6
7
8
9
10
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-36. Typical Default DB Screen
Note
On the next % (DB Update) command, the Megaplex-4100 will copy from the edit
buffer to the selected default database, provided the edit buffer configuration
passes successfully the sanity check.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-41
Chapter 4 Configuration
Installation and Operation Manual
To initialize the Megaplex-4100 database:
³
1. Select Load HW on the DB Tools menu.
2. You will see a “The DB will reset to default. Do you want to proceed – Y/N?”
message.
3. Type Y to confirm. You can now go back to the main menu and start the
configuration activities.
To update a desired database with the edit buffer configuration:
³
1. Select Update DB on the DB Tools menu.
2. On the Update DB screen (Figure 4-37), type the desired database index
number, and then press <Enter>. Note that you can select any index number,
even if the corresponding database is not yet stored in the flash memory. The
databases in use are identified on the displayed list.
MP-4100
Configuration>DB Tools>Update DB
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
1 (in use)
2 (in use)
3
4
5
6
7
8
9
10
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-37. Typical Update DB Screen
3. You are requested to confirm by Are you sure you want to update active
database – Y/N?, or by Are you sure you want to update selected database –
Y/N?, depending on whether you update the active database, or other
database:
•
Type n to cancel the request. The changes made to the database in the
edit buffer are not affected, and therefore you can either continue editing,
or simply postpone the update. However, take into consideration that any
unsaved changes are lost when the Megaplex-4100 is powered down.
•
Type y to confirm. In this case, a sanity check is automatically performed
on the edited database.
4. The continuation depends on the results of the sanity check:
•
4-42
If neither errors, nor warnings are detected by the sanity check, then you
will see a Configuration File Update is in Process message.
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Wait for the message to disappear before continuing (this takes a few
seconds): although you can press <ESC> and return to the menu to
continue entering new commands, this is not recommended. In particular,
do not reset the Megaplex-4100 before the update is completed: this will
cause the configuration data to be lost. Neither should Megaplex-4100
power be disconnected during this interval.
Note
The storage space used by databases increases after each change. Sometimes,
the remaining storage space is not sufficient to save the updated database, and
you will see Save of Configuration File Failed. In this case, it is necessary to delete
unused databases.
After a short delay, the specified database is updated (or a new database
with the selected index number is created). If you had updated the active
database, the changes will be activated, that is, the operation mode of
the Megaplex-4100 changes in accordance with the new parameters
values.
Note
If the updated active database includes changes to the serial port communication
parameters, you need to press <Enter> several times in sequence to reestablish
communication with the Megaplex-4100.
•
If only warnings are detected by the sanity check, then you are notified by
a Warnings exist. Database update started message, however the specified
database is updated, as explained above.
You can request to see the warnings by typing $ (the show sanity
command), even as the configuration file update proceeds (in this case,
first press <ESC>), and then correct the configuration accordingly.
•
If errors have been detected, the updating request is rejected, and you see
Errors in configuration. Do you want to see errors?
…
…
³
You can type y to confirm. In this case, you will see the Errors and
Warnings screen. Refer to Chapter 5 for error explanations and
corrective actions.
Alternatively, type n to cancel and abort the update.
To delete an existing database:
1. Select Delete DB on the DB Tools menu.
2. You will see the DB screen (Figure 4-38). Note that only the numbers of the
existing databases are displayed on the screen.
3. Type the number of the desired database, and confirm.
You are requested to confirm: “Do you want to delete DB-#– Y/N?”. Type Y
to confirm, N to cancel.
4. You will see a Database deleted successfully. Press any key to exit screen.
After pressing any key, you return to the DB Tools menu. In parallel, you will
see a Configuration File Update is in Process message, which disappears when
the configuration file is successfully updated.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-43
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>DB Tools>Delete DB
1. 1
2. 2
3. 10
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-38. Typical Delete DB Screen
Configuring System Parameters
³
To configure the system parameters:
1. Use Configuration>Quick Setup to configure the basic Megaplex-4100 IP
communication parameters.
2. Use the Configuration>System menu to perform the following activities:
1. If necessary, reload factory defaults to start the configuration from a
known baseline.
2. Program the modules installed in the Megaplex-4100 chassis.
3. Configure the Megaplex-4100 serial control port, and the authorizations
of the users allowed to use the serial port.
4. Configure the Megaplex-4100 Ethernet control port.
5. Select the SNMP support mode (SNMPv3 security features enabled or
disabled).
6. Configure Megaplex-4100 management parameters, and management
access authorizations.
Note
Configuration instructions for SNMP management appear in Section 4.2.
7. Configure system logistics information.
8. Set system time-of-day and date.
9. Configure the signaling profiles.
The System menu provides access to additional system-level configuration
activities that should be performed after configuring other parameters
(Figure 4-39 to Figure 4-44).
4-44
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
System
Card Type
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
12. Alarms Configuration
13. Fault Propagation
Clock Source
1. Source
2. Master Port
3. Fallback Port
Slot: PS-A
Card:
PS
PS-B
PS
Slot: IO-4
Card: M8SL
IO-5
HSU-12
IO-7
HSU-12
IO-1
M8E1
IO-8
HSU-12
IO-2
M8E1
IO-3
M8SL
IO-9
IO-10
VC-16/FXS VC-16/E&M
Source
Master Port/Fallback Port
TS Assignment
1. IO
2. CL
Mapping
IO-6
HSU-12
CL-B
CL1/155
1. Internal
2. Rx Clock
3. S Subsystem
Rx Clock only
1. CL-A
2. CL-B
CL-A
CL1/155
See Sheet 2
or Sheet 3
Entry Num
1
2
| 3
v4
5
6
7
Slot
NONE
NONE
NONE
NONE
NONE
NONE
NONE
1. CL-A (CL1/155)
2. CL-B (CL1/155)
3. IO-1 (M8E1)
Port
4. IO-2 (M8E1)
5. IO-3 (M8SL)
6. IO-4 (M8SL)
7. IO-5 (HSU-12)
8. IO-6 (HSU-12)
9. IO-7 (HSU-12)
10. IO-8 (HSU-12)
13. NONE
11. IO-9 (VC-16/FXS)
12. IO-10 (VC-16/E&M)
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
See Sheet 4
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
See
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 4-39. Typical Configuration>System Submenu Structure (Sheet 1 of 6)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-45
Chapter 4 Configuration
Installation and Operation Manual
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
Link 1
IO
See
Sheet 1
I/O-1
1. I/O-1
2. I/O-2
3. I/O-3
1. Link 1
2. Link 2
3. Link 3
..
.
..
.
12. Alarms Configuration
13. Fault Propagation
or
CL
1. PDH 1 (Up)>
2. PDH 2 (Up)>
3. PDH 3 (Up)>
4. PDH 4 (Up)>
5. PDH 5 (Up)>
.
.
.
Clock Source
1. Source
2. Master Port
3. Fallback Port
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
Rx Clock only
..
.
TS Assignment
12. PDH 12 (Up)>
13. PDH 13 (Up)>
14. PDH 14 (Up)>
15. PDH 15 (Up)>
16. PDH 16 (Up)>
.
.
.
23. PDH 23 (Up)>
24. PDH 24 (Up)>
25. PDH 25 (Up)>
26. PDH 26 (Up)>
27. PDH 27 (Up)>
.
.
.
..
.
PDH 1
34. PDH 34 (Up)>
35. PDH 35 (Up)>
36. PDH 36 (Up)>
37. PDH 37 (Up)>
38. PDH 38 (Up)>
.
.
.
..
.
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
..
.
(See below)
1. IO
2. CL
Display Time Slots
Mapping
Ts#
1. CL-A
2. CL-B
Ts#
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
1
2
3
4
5
6
7
8
02:01:01 02:01:02 02:01:04 02:BND01 02:BND01 02:BND01 03:BND15 03:BND15
9
-----
10
-----
11
-----
12
-----
13
-----
..
.
Control Port
15
-----
16
-----
Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
See Sheet 4
or Sheet 5
Slot
IO-2 (M8E1)
IO-2 (M8E1)
IO-2 (M8E1)
IO-2 (M8E1)
..
.
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
14
-----
Port
Link 1
Link 1
Link 1
BND 1
Ts
1
2
4
--
Type
DATA
DATA
DATA
DATA
Connect Time Slots
PDH 1
1. Start TS
2. Slot
3. Port
4. Number of TS
5. Type
6. Destination Start TS
7. Save Configuration
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (per Slot and Port)
5. Delete TS (Number of TS)
6. Split
1. Serial Port
2. ETH
Delete TS (per Slot and Port)
1. Slot
2. Port
3. Save Configuration
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Delete TS (Number of TS)
1. Start TS
2. Number of TS
3. Save Configuration
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
TS3
Split
1. Bit 1
... (01:IN03)
2. Bit 2
... (01:IN03)
3. Bit 3
... (------)
4. Bit 4
... (------)
5. Bit 5
... (------)
6. Bit 6
... (------)
7. Bit 7
... (------)
8. Bit 8
... (------)
9. Check Split Sanity
1. TS3
2. TS15
..
.
See
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
CL-A
1. Link 1
2. Link 2
Link 1
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Fault Propagation
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TUG3 3
TUG3 2
TUG3 1
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
1. Fault Propagation
2. Interfaces
Figure 4-40. Typical Configuration>System Submenu Structure – SDH Only (Sheet 2 of 6)
4-46
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
Link 1
IO
1. I/O-1
2. I/O-2
3. I/O-3
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
1. Link 1
2. Link 2
3. Link 3
..
.
See
Sheet 1
..
.
or
CL
12. Alarms Configuration
13. Fault Propagation
1. PDH 1 (Up)>
2. PDH 2 (Up)>
3. PDH 3 (Up)>
4. PDH 4 (Up)>
5. PDH 5 (Up)>
.
.
.
Clock Source
1. Source
2. Master Port
3. Fallback Port
I/O-1
..
.
Rx Clock only
12. PDH 12 (Up)>
13. PDH 13 (Up)>
14. PDH 14 (Up)>
15. PDH 15 (Up)>
16. PDH 16 (Up)>
.
.
.
23. PDH 23 (Up)>
24. PDH 24 (Up)>
25. PDH 25 (Up)>
26. PDH 26 (Up)>
27. PDH 27 (Up)>
.
.
.
..
.
PDH 1
34. PDH 34 (Up)>
35. PDH 35 (Up)>
36. PDH 36 (Up)>
37. PDH 37 (Up)>
38. PDH 38 (Up)>
.
.
.
..
.
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (Per Slot and Port)
5. Delete TS (Number of TS)
6. Split
..
.
(See below)
TS Assignment
1. IO
2. CL
Display Time Slots
Ts#
Mapping
Ts#
1. CL-A
2. CL-B
1
2
3
4
5
6
7
8
02:01:01 02:01:02 02:01:04 02:BND01 02:BND01 02:BND01 03:BND15 03:BND15
9
-----
Ts#
TS 01
TS 02
| TS 03
v TS 04
See Sheet 4
or Sheet 5
12
-----
13
-----
..
.
14
-----
15
-----
16
-----
Slot
IO-2 (M8T1)
IO-2 (M8T1)
IO-2 (M8T1)
IO-2 (M8T1)
..
.
Port
Link 1
Link 1
Link 1
BND 1
Ts
1
2
4
--
Type
DATA
DATA
DATA
DATA
Connect Time Slots
PDH 1
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
11
-----
Manual
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
10
-----
1. Start TS
2. Slot
3. Port
4. Number of TS
5. Type
6. Destination Start TS
7. Save Configuration
1. Display Time Slots
2. Manual
3. Connect Time Slots
4. Delete TS (per Slot and Port)
5. Delete TS (Number of TS)
6. Split
Delete TS (per Slot and Port)
1. Slot
2. Port
3. Save Configuration
Control Port
1. Serial Port
2. ETH
Delete TS (Number of TS)
Date & Time
1. Start TS
2. Number of TS
3. Save Configuration
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
TS3
Split
1. TS3
2. TS15
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
..
.
See
Sheet 6
CL-A
1. Link 1
2. Link 2
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
1. Bit 1
... (01:IN03)
2. Bit 2
... (01:IN03)
3. Bit 3
... (------)
4. Bit 4
... (------)
5. Bit 5
... (------)
6. Bit 6
... (------)
7. Bit 7
... (------)
8. Bit 8
... (------)
9. Check Split Sanity
Link 1
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
STS1-1
TU1 TU2 TU3 TU4
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
STS1-2
TU1 TU2 TU3
None None None
None None None
None None None
None None None
None None None
None None None
None None None
TU4
None
None
None
None
None
None
None
STS1-3
TU1 TU2 TU3 TU4
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
None None None None
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 4-41. Typical Configuration>System Submenu Structure – SONET Only (Sheet 3 of 6)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-47
Chapter 4 Configuration
Installation and Operation Manual
Figure 4-42. Typical Configuration>System Submenu Structure (Sheet 4 of 6)
4-48
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
See
Sheet 1
APS Group ID
12. Alarms Configuration
13. Fault Propagation
1. A1-A2
2. B1-B2
3. A1-B1
4. A2-B2
Clock Source
1. Source
2. Master Port
3. Fallback Port
Rx Clock only
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Users
Mapping
1.
2.
3.
4.
5.
1. CL-A
2. CL-B
APS
Authentication Protocol
Security Name
Authentication Protocol
Privacy Protocol
Authentication Password
Privacy Password
1. usmNoAuthProtocol
2. usmHMACMD5AuthProtocol
3. usmHMACSHAAuthProtocol
With Authentication
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
Privacy Protocol
1 usmNoPrivProtocol
2. usmDESPrivProtocol
Only with Authentication
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Targets & Notify
SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Only with Privacy
See
Sheet 4
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
SNMPv3 Factory Defaults
Summary User Table
Summary Target Table
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
Targets Params
1.
2.
3.
4.
5.
Name
Message Processing Model
Security Model
Security Name
Security Level
1.
2.
3.
4.
SNMPv1
SNMPv2c
SNMPv2u
SNMPv3
1.
2.
3.
4.
5.
Any
SNMPv1
SNMPv2c
USM
Not defined
Security Model
Target Address
1.
2.
3.
4.
Name
IP Address
Params Name
Tag List
Security Level
Notify
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
Message Processing
Model
See
Sheet 6
1. noAuthNoPriv
2. authNoPriv
3. authPriv
Trap
SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Summary User Table
User
Security Model
Security Level
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Summary Target Table
Address MPModel SecModel SecName SecLevel
Fault Propagation
1. Fault Propagation
2. Interfaces
Figure 4-43. Typical Configuration>System Submenu Structure (Sheet 5 of 6)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-49
Chapter 4 Configuration
Installation and Operation Manual
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
See
Sheet 1
12. Alarms Configuration
13. Fault Propagation
Clock Source
1. Source
2. Master Port
3. Fallback Port
Rx Clock only
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping
1. CL-A
2. CL-B
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD
See Sheet 4
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3 - Enabled
8. SNMPv3 Setting
Baud Rate
For Administrator
Serial Port
Control Port
Change Password
1. Baud Rate
2. Change Password
3. Security Timeout
1. Serial Port
2. ETH
Change User Details
1. Change User Details
2. Show all Users
Show all Users
Date & Time
1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9
11. IO-10
Security Timeout
ETH
CL-A
1. CL-A
2. CL-B
Routing Protocol
1. Admin Status
2. Routing Protocol
3. User Name
1. None
2. RIP 2
3. Proprietary RIP
Set Date Format
1. DD-MM-YYYY
2. MM-DD-YYYY
3. YYYY-DD-MM
4. YYYY-MM-DD
Signaling Profile
Profile Number
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Rx Signaling
Tx Signaling
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Interfaces
Interfaces
Fault Propagation
1. Fault Propagation
2. Interfaces
Slot A
IO-1
Port A
ETH 1
Slot B
IO-5
Port B
ETH 2
Add
Mode
BiDirectional (A<->B)
1. Slot A
2. Port A
3. Slot B
4. Port B
5. Mode
Figure 4-44. Typical Configuration>System Menu Structure (Sheet 6 of 6)
4-50
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Programming Modules
Use the following procedure to program modules in the Megaplex-4100 chassis.
You can program modules even if they are not installed in the chassis.
Note
When only one CL module is installed in the chassis, it must always be installed in
slot CL-A.
Moreover, if CL module B is programmed, CL module A must also be programmed
in the chassis.
To navigate to the required screen, use Configuration>System>Card Type.
A typical Card Type screen is shown in Figure 4-45.
MP-4100
Configuration>System>Card Type
Slot:
Card:
PS-A
PS
PS-B
PS
CL-A
CL1/155
CL-B
CL1/155
IO-1
M8E1
Slot:
Card:
IO-4
M8SL
IO-5
HSU-12
IO-6
HSU-12
IO-7
HSU-12
IO-8
HSU-12
IO-2
M8E1
IO-3
M8SL
IO-9
IO-10
VC-16/FXS VC-16/E&M
1. --------2. PS
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-45. Typical Card Type Screens
Note
³
To see the navigation keys available for this screen, type ? (help).
To program modules in the Megaplex-4100 chassis:
1. Move the cursor to the desired slot.
2. The selections supported for the selected slot are automatically displayed
under the slots table. Type the item number corresponding to the desired
selection and then press <Enter>.
Note
It is not allowed to program different types of CL modules in the chassis, even if
only one CL module is currently installed.
3. When done, type % to update the current Megaplex-4100 database. You will
get warnings whenever you program modules not yet installed in the chassis:
at this stage, the warnings can be ignored.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-51
Chapter 4 Configuration
Installation and Operation Manual
Configuring System Clock Sources
Use the following procedure to configure the system (nodal) clock timing
references signals (sources) for the Megaplex-4100 timing subsystem.
Appropriate configuration permits hierarchical dissemination of timing throughout
the communication systems, and use of reliable timing sources even in case of
transmission faults or equipment malfunctions.
In addition to the system clock sources, for Megaplex-4100 with CL.1/155 and
CL.1/155GbE modules it is also necessary to configure the timing reference for
the SDH/SONET subsystem (see Configuring SDH/SONET Network Ports starting
on page 4-70).
Review the Megaplex-4100 Timing Subsystem section in Chapter 1 for a
description of the timing subsystem.
A timing source is defined by specifying the slot and the port to be used. The
source slot can be any I/O slot with a module having ports capable of recovering
a clock signal, or a CL slot. For flexibility, you can select master timing sources
and fallback timing sources: a fallback source is automatically selected when none
of the preconfigured master sources is capable of providing a good timing
reference.
Only ports that are fully configured and with Admin Status=UP can be configured.
The Megaplex-4100 timing subsystem can use the following types of reference
sources:
•
Internal Megaplex-4100 oscillator.
•
Clock signal derived from the receive clock of a specified user port (Rx
timing mode).
•
S-subsystem clock signal, provided by the timing subsystem of the
SDH/SONET subsystems located CL.1/155 and CL.1/155GbE modules.
•
Station clock, a special case of Rx timing, which uses an external clock
signal supplied to the CL module CLOCK connector.
Table 4-13 lists the reference clock sources that can be configured, together with
the types of Megaplex-4100 modules that can provide a timing reference signal.
For each module, the table also lists the type of ports, and when applicable – the
operating mode that must be selected for a port to be able of providing a timing
reference signal.
Table 4-13. Clock Reference Sources
Source Type
Module Type
Selectable Ports
Specific Operating Mode
Internal
Not applicable
Not applicable
Not applicable
Station (external)
CL
Station clock
Not applicable
4-52
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Source Type
Chapter 4 Configuration
Module Type
Selectable Ports
Specific Operating Mode
M8E1, M8T1
External T1 or E1 ports
Not applicable
M8SL
External SHDSL ports
STU-R mode
MPW-1
Pseudowire ID
Not for HDLCoPSN
pseudowires
OP-108C/OP-106C Internal DS1 ports
Not applicable
HS-6N, HS-12N
External ports
DTE timing
HS-U-6, HS-U-12
External ports
NT mode
HS-S
External ports
TE mode
HS-703
External ports
Not applicable
LS-6N, LS-12
External ports
DTE timing mode, provided the
channel data rate is a multiple
of 8 kbps
RX Clock from
Remote User Port
CL.1/155,
CL.1/155GbE
Internal T1 or E1 PDH
ports
Not applicable
Line (STM-1/OC-3) Signal from
SDH/SONET Subsystem
CL.1/155,
CL.1/155GbE
Link port
Not applicable
RX Clock from
Local User Port
To navigate to the required screen, use Configuration>System>Clock Source.
A typical Clock Source screen with the default source, Internal, is shown in
Figure 4-46.
MP-4100
Configuration>System>Clock Source
1. Source
>
(Internal)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-46. Typical Clock Source Screen
³
To select the timing reference mode (source type):
1. To start the nodal timing configuration, select Source to display the source
type selection screen (see Figure 4-47).
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-53
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Clock Source>Source (Internal)
1. Internal
2. Rx Clock
3. S Subsystem
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-47. Selection Screen for Clock Source Type
2. The available selections are as follows:
Internal
Timing locked to the Megaplex-4100 internal oscillator.
Rx Clock
Timing locked to the receive clock signal of a user-selectable
interface.
S Subsystem
Timing locked to the clock signal provided by the SDH/SONET
subsystem (refer to the Card Configuration section starting
on page 4-71 for details).
Do not select S Subsystem when the system SDH/SONET TX
Clock (see Configuring SDH/SONET Network Ports starting on
page 4-70) is SYSTEM, because this will result in unstable
timing.
Select the desired type and then press <Enter>.
3. After making your selection, the source selection screen closes and the new
source appears on the Clock Source screen.
³
To select RX timing sources:
1. If you selected Rx Clock, the Clock Source screen changes to enable selecting
master and fallback sources. A typical screen is shown in Figure 4-48.
The list includes only slots in which modules with ports capable of providing a
timing reference are installed and/or programmed.
4-54
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>System>Clock Source
1. Source
2. Master Port
3. Fallback Port
>
(Rx Clock)
[]>
[]>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-48. Typical Selection Screen for RX Clock Mode
2. Select Master Port to start the selection of the master timing sources. For each
source, you must specify a slot and a port. A typical slot selection screen is
shown in Figure 4-49 and a typical port selection screen – in Figure 4-50.
When the list extends on several pages, use the arrow keys or
CTRL+U/CTRL+D to scroll among the pages (for navigation help, use the
?-help item).
The screen includes a table with 3 columns:
Entry Num
The index number, 1 to 10, which determines the relative
priority (1 is the highest priority).
Only the first 7 entries appear on the first page: scroll down to
display the other entries.
Slot
The slot on which the source port is located. The slot is selected
on a list displayed under the table when the selection block is
moved to the Slot column.
Port
The identifier of the desired port within the module installed in
the selected slot. The port is selected on a list displayed under
the table, when the selection block is moved to the Port
column. The list shows only the ports that can be used as
reference source on the module installed, or programmed, in
the selected slot.
3. To define a master source, move the cursor to the desired number, and select
the prescribed slot and port. You can skip priorities, that is, select NONE
wherever desired. You can also select NONE to delete a configured source
without changing the relative priorities of the remaining ports.
4. When done, press ESC to return to the Clock Source screen.
5. To select a fallback source, select Fallback Port and repeat the same actions.
Make sure to select different sources: you cannot select again a source already
included in the Master Port list.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-55
Chapter 4 Configuration
Installation and Operation Manual
6. To update the active database, and thus activate the new user definitions,
type % and then confirm the action.
MP-4100
Configuration>System>Clock Source>Master Port
Entry Num Slot
1
CL-A(CL1/155GbE)
2
CL-B(CL1/155GbE)
| 3
IO-1 (M8E1)
v 4
None
5
None
6
None
7
None
1. CL-A(CL1/155GbE)
2. CL-B(CL1/155GbE)
3. IO-1 (M8E1)
Port
Clock
PDH 1
Link 5
-
4. IO-2 (M8E1)
5. IO-3 (M8T1)
6. IO-5 (M8SL)
7. None
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-49. Typical Master Port Screen – Selection of Source Slot
MP-4100
Configuration>System>Clock Source>Master Port
Entry Num Slot
1
CL-A(CL1/155GbE)
2
CL-B(CL1/155GbE)
| 3
IO-1 (M8E1)
v 4
None
5
None
6
None
7
None
1. Link 1
2. Link 2
3. Link 3
4. Link 4
5. Link 5
6. Link 6
Port
Clock
PDH 1
Link 5
7. Link 7
8. Link 8
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-50. Typical Master Port Screen – Selection of Source Port
Configuring Station Clock Parameters
Use the following procedure to configure the physical layer parameters of the
station clock port located on a selected CL module.
4-56
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
For Megaplex-4100 equipped with two CL modules, each station clock port can be
separately configured.
To navigate to the required screen, use Configuration>Physical Layer>CL>CL-A or
CL-B>Station Clock.
Figure 4-51 shows a typical Station Clock screen. The station clock port
configuration parameters are explained in Table 4-14.
MP-4100
Configuration>Physical Layer>CL>CL-A>Station Clock
1. Admin Status
(Up)
2. Transmit Timing Source
>
(System)
3. Clock Rate
>
(2048 KBPS)
4. Interface Type
(Balance)
5. Line Code
>
(HDB3)
6. Rx Gain Limit
(Short Haul)
7. SSM
(Enable)
8. Rx Source
(Sa4)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-51. Typical Configuration>Physical Layer>CL>Station Clock Screen (2048 KBPS Clock Rate
³
To define the station clock port parameters:
Select the number of the desired parameter, and then press <Enter> to display
the appropriate parameter selection screen, or toggle the current selection.
Table 4-14. Station Clock Parameters
Parameter
Function
Values
Admin Status
Used to enable/disable the station
clock interface
DOWN – The station clock interface on the
corresponding CL module is disabled. This state should
be selected as long as the port configuration has not
yet been completed, or to stop using this port.
UP – The station clock interface on the corresponding
CL module is enabled.
Default: DOWN
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-57
Chapter 4 Configuration
Parameter
Function
Transmit Timing Selects the source of the clock
Source
output signal provided in the
station clock connector, for
connection to other equipment
Installation and Operation Manual
Values
SYSTEM – the output (transmit) clock is derived from
the Megaplex-4100 nodal timing. In this case, the
nominal frequency of the output clock is always
2048 kbps, irrespective of the Clock Rate selection.
STATION RCLK – the external clock signal applied to the
station clock receive input is returned through the
transmit output.
STATION RCLK AFTER JA – the external clock signal
applied to the station clock receive input is regenerated
and filtered by a jitter attenuator, before being
returned through the transmit output.
Default: SYSTEM
Clock Rate
Selects the rate and type of signal
accepted and transmitted via the
station clock port
2048 KBPS – 2.048 Mbps signal per ITU-T Rec. G.703
Para. 6.
2048 KHZ – 2.048 MHz signal per ITU-T Rec. G.703
Para. 10.
1544 KBPS – 1.544 Mbps signal per ITU-T Rec. G.703
Para. 2. This option is not available when Transmit
Timing Source is SYSTEM.
Default: 2048 KBPS
Interface Type
Selects the clock signal interface
type
BALANCE – balanced interface (nominal impedance of
100 Ω for 1544 KBPS, and 120 Ω for 2048 KBPS and
2048 kHz).
UNBALANCE – 75 Ω unbalanced (coaxial) interface. This
selection is available only for 2048 KBPS and 2048 kHz.
Default: BALANCE
Line Code
Selects the line code
The available selections depend on Clock Rate:
•
When Clock Rate is 2048 KBPS or 2048 kHz, the
only selection is HDB3.
•
When Clock Rate is 1544 KBPS:
• AMI – alternate mark inversion coding
• B8ZS – Binary-8 zero suppression coding
Default: HDB3
Rx Gain Limit
Determines the maximum
attenuation of the receive signal
that can be compensated for by
the station port receive path
SHORT HAUL – Maximum allowable attenuation of
10 dB, relative to the nominal transmit level (similar to
DSU capabilities).
LONG HAUL – Maximum allowable attenuation of 34 dB,
relative to the nominal transmit level (similar to DSU
capabilities).
Default: SHORT HAUL
4-58
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
SSM
Enables/disables the use of SSM
messages received through this
station clock interface
DISABLE – SSM messages received through this station
clock interface are ignored.
RX – SSM messages received through this station clock
interface are taken into account when the SDH/SONET
subsystem uses automatic SSM-based clock source
selection (see Tx Clock Based on SSM in Table 4-17).
Default: DISABLE
Rx Source
Specifies the national bit (located
in timeslot 0 of E1 streams) from
which the SSM message is read.
Sa4, Sa5, Sa6, Sa7, Sa8 – the national bit carrying the
SSM.
Default: Sa4
This parameter is displayed only
when Clock Rate is 2048 KBPS and
SSM is Rx Source
Preparing Signaling Profiles
Use the following procedure to modify the signaling translation rules contained in
the five signaling profiles supported by Megaplex-4100, in accordance with your
specific application requirements.
To navigate to the required screen, use Configuration>System> Signaling Profile.
A typical signaling profile configuration screen is shown in Figure 4-52.
MP-4100
Configuration>System>Signaling Profile
1.
2.
3.
4.
5.
6.
Profile Number>
Rx Signaling >
Tx Signaling >
Rx Busy[0 - f]...
Rx Idle[0 - f]...
Profile Name ...
(1)
(0F)
(00)
()
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-52. Typical Signaling Profile Configuration Screen
You can specify different transmission rules for the receive and transmit
directions:
•
Megaplex-4100 Ver. 2.0
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
Configuring Megaplex-4100 for Operation
4-59
Chapter 4 Configuration
Installation and Operation Manual
actually sent to each module which needs the signaling information
received by a main link).
In addition to the translation of individual bits, the receive path section can
also be used to define the signaling bit patterns that indicate the busy and
idle states.
•
Transmit direction: defines the translation of the internal signaling bits to
the signaling bits transmitted through the external port.
To modify a signaling profile:
³
1. Select Profile Number, type the desired number, 1 to 5, and then press
<Enter>.
2. To change the translation rule for the receive or transmit direction, select Rx
Signaling or Tx Signaling, respectively, to display the bit selection screen.
A typical screen is shown in Figure 4-53. The screen lists the four signaling
bits, A to D, together with their current translations.
MP-4100
Configuration>System>Signaling Profile>Rx Signaling
1.
2.
3.
4.
A>
B>
C>
D>
(
(
(
(
A)
B)
C)
D)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-53. Typical Signaling Bit Selection Screen
To change the translation rule of a bit, select it and then press <Enter>. On
this screen, you can select for each internal signaling bit the method used to
determine its value. The available selections are as follows:
A, B, C, D
Bit value copied from the corresponding incoming bit
(no translations).
~A, ~B, ~C, ~D
Inverted bit value, related to the corresponding incoming
bit.
0
Bit value is always 0.
1
Bit value is always 1.
The defaults are no translation.
3. To change the incoming pattern to be interpreted internally as the busy state,
select Rx Busy, and then type the appropriate value. The pattern is specified by a
hexadecimal digit (0 to 9, A to F), which when converted to binary format yields
the ABCD sequence.
4-60
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Example: if the busy state is indicated by the incoming sequence 1000, select 8.
Default: 0
4. To change the incoming signaling bit pattern to be interpreted internally as the
idle state, select Rx Busy, and then type the appropriate value.
The pattern is specified by a hexadecimal digit (0 to 9, A to F), which when
converted to binary format yields the ABCD sequence.
Default: 0
5. You can also assign a name to the profile: select Profile Name, and then type
the desired name (up to 12 alphanumerical characteristics).
Configuring Physical Layer Parameters
³
To configure Megaplex-4100 physical ports:
1. For each CL module: configure the station clock interface.
2. For each CL module with SDH/SONET subsystem (CL.1/155 and CL.1/155GbE):
•
Configure the general module parameters and system timing sources
•
Configure the physical link parameters
•
When inband management is used: configure DCC parameters.
3. For each CL module with Ethernet traffic subsystem (CL.1/GbE and
CL.1/155GbE):
•
Configure the GbE physical ports parameters
•
Configure the GbE redundancy.
4. Configure the required I/O physical ports in accordance with the Installation
and Operation Manual of each module programmed in Megaplex-4100.
For your convenience, the structure of the Physical Layer submenu for SDH and
SONET links is shown in Figure 4-54 and Figure 4-55, respectively.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-61
Chapter 4 Configuration
Installation and Operation Manual
Physical Layer
1. I/O
2. CL
I/O
E1
I/O-1
1. I/O-1
2. I/O-2
3. I/O-3
..
..
1. Link 1
1. E1
2. Ethernet
..
..
.
8. Link 8
9. All Links
Transmit Timing
Source
Ethernet
1. ETH1
2. ETH2
3. ETH3
4. All Ports
1. System
2. Station RCLK
3. Station RCLK after JA
Clock Rate
CL
Station Clock
1. 2048 KBPS
2. 1544 KBPS
2. 2048 KHZ
1. Admin Status
2. Transmit Timing Source
3. Clock Rate
4. Interface Type
5. Line Code
6. Rx Gain Limit
7. SSM
8. Rx Source
1. CL-A
2. CL-B
Short Haul
Long Haul
Disable
Rx
Sa4
Sa5
Sa6
Sa7
Sa8
1. Station Clock
2. Ethernet
3. SDH/SONET
GbE
1. Admin Status
2. Auto Negotiation
3. Speed & Duplex
4. Flow Control
5. User Name
6. Redundancy
1. GbE 1
2. GbE 2
3. All Ports
1. Card Configuration
2. Link 1
3. Link 2
4. All Links
1544 KBPS only
2048 KBPS, 2048 KHZ
1. AMI
2. HDB3
3. B8ZS
Ethernet
SDH/SONET
Balance
Unbalance
Line Code
Only for SSM = Rx
CL-A
Not for
SYSTEM Source
Card Configuration
1. Frame Structure
– STM-1
2. Tx Clock Based on SSM – YES
3. Common PDH LVC Parameters
Common PDH
LVC Parameters
1. RDI on Signal Label
2. RDI on Path Trace
or
Card Configuration
1. Frame Structure
– STM-1
2. Tx Clock Based on SSM – NO
3. SDH Tx Clock
4. Master Port
RX CLOCK only
5. Fallback Port
6. Common PDH LVC Parameters
1. Off
2. PPP Over HDLC
3. HDLC
Routing Protocol
Link 1
1. Admin Status
2. User Name
3. RDI on Fail
4. EED Threshold
5. SD Threshold
6. DCC Configuration
In Band Management
1. None
2. RIP 2
3. Proprietary RIP
DCC Configuration
1. In Band Management
2. Routing Protocol
3. Management DCC
4. Deviation Type
Management DCC
Standard
Type 1
1. D1-D3
2. D4-D12
Figure 4-54. Typical Configuration>Physical Layer Submenu Structure (SDH)
4-62
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Figure 4-55. Typical Configuration>Physical Layer Submenu Structure (SONET)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-63
Chapter 4 Configuration
Installation and Operation Manual
The configuration of the physical layer parameters for the modules programmed
in the various Megaplex-4100 slots is started by selecting the class of ports to be
configured on the Physical Layer menu.
A typical Physical Layer type selection screen is shown in Figure 4-56. This screen
includes two options:
³
IO
For configuring the physical layer parameters of modules installed in
I/O slots. Configuration instructions for these modules can be found
in the Installation and Operation Manual of each module.
CL
For configuring the physical layer of the ports located on the CL
modules.
To select the class of physical ports to be configured:
Select the desired type and then press <Enter>.
MP-4100
Configuration>Physical Layer
1. IO >
2. CL >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-56. Typical Physical Layer Class Selection Screen
Configuring the CL Physical Layer
Use the following procedure to configure the CL Physical Layer parameters.
To navigate to the required screen, use Configuration>Physical Layer>CL.
³
To select the CL configuration task:
1. Select CL on the Physical Layer menu. A typical CL module selection screen is
shown in Figure 4-57. This screen is used to select between the two CL
modules that can be installed in the Megaplex-4100.
4-64
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Physical Layer>CL
1. CL-A>
2. CL-B>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-57. Configuration>Physical Layer>CL Selection Screen
2. Select the desired CL module and then press <Enter> to display the
configuration task selection screen for the selected CL module.
A typical screen, which shows all the available options, is shown in
Figure 4-58. The displayed options depend on the CL module model.
MP-4100
Configuration>Physical Layer>CL>CL-A
1. Station Clock>
2. Ethernet
>
3. SDH/SONET
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-58. Configuration>Physical Layer>CL Task Selection Screen
Configuring the Physical Layer Parameters of GbE Ports
Use the following procedure to configure the physical layer parameters of the
GbE ports located on the CL.1/GbE and CL.1/155GbE modules, and control the
use of the 1+1 redundancy feature.
To navigate to the required screen, use Configuration>Physical Layer>CL>CL-A or
CL-B>Ethernet.
³
To configure the physical layer parameters of the GbE ports:
1. Open the Configuration>Physical Layer>CL screen, and then select the desired
CL module to display the CL module task selection screen.
2. On the CL module task selection screen (Figure 4-58), select the Ethernet
configuration option. A typical Ethernet port selection screen is shown in
Figure 4-59.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-65
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet
1. GbE 1(Up)>
2. GbE 2(Up)>
3. All Ports>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-59. Typical Ethernet Port Selection Screen
3. Select a specific GbE port to configure its physical layer parameters.
Alternatively, first preconfigure both ports with the same basic parameters
(All Ports option), and then sequentially select each port and change its
parameters as required.
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 1(Up)
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Speed & Duplex
Flow Control
User Name
Redundancy
(Up)
(Disable)
>
(1000 MBPS Full Duplex)
(Enable)
... ()
>
(None)
>
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-60. Typical Ethernet Port Configuration Screen (No Redundancy)
Table 4-15 describes the GbE port configuration parameters.
4-66
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-15. GbE Port Physical Layer Configuration Parameters
Parameter
Function
Values
Admin Status
Used to enable/disable the flow of
traffic through the selected GbE port
DOWN – The flow of traffic is disabled. This
state should be selected as long as the
configuration of the corresponding port has not
yet been completed, or when it is necessary to
stop traffic flow through the port.
UP – The flow of traffic is enabled.
Default: DOWN
Auto Negotiation Controls the use of auto-negotiation for ENABLE – Auto-negotiation is enabled. This is
the selected GbE port.
the normal operation mode. It is not
recommended
to use this option for GbE ports
Auto-negotiation is used to select
equipped
with
SFPs.
automatically the mode providing the
highest possible traffic handling
capability
DISABLE – Auto-negotiation is disabled. This is
the recommended state for the GbE ports
equipped with SFPs.
Default: DISABLE
Max. Capability
Advertised
When Auto Negotiation is ENABLE,
selects the highest traffic handling
capability to be advertised during the
auto-negotiation process. The operating
mode selected as a result of
auto-negotiation cannot exceed the
advertised capability.
When Auto Negotiation is DISABLE, this
parameter is replaced by Speed &
Duplex.
Only CL modules with copper GbE ports
support the full range of rate and mode
options. GbE ports equipped with SFPs
support only 1000Mbps full duplex (any
other selection will result in a
Hardware/Software Mismatch alarm)
Speed & Duplex
When Auto Negotiation is DISABLE,
selects the data rate and the operating
mode of the selected GbE port.
The available selections are listed in ascending
order of capabilities:
10Mbps half duplex – Half-duplex operation at
10 Mbps.
10Mbps full duplex – Full-duplex operation at
10 Mbps.
100Mbps half duplex – Half-duplex operation at
100 Mbps.
100Mbps full duplex – Full-duplex operation at
100 Mbps.
1000Mbps half duplex – Half-duplex operation at
1000 Mbps.
1000Mbps full duplex – Full-duplex operation at
1000 Mbps.
Default: 1000Mbps full duplex
Same selections as for the Max. Capability
Advertised parameter.
For GbE ports equipped with SFPs, the only
When Auto Negotiation is ENABLE, this
allowed selection is 1000Mbps full duplex (any
parameter is replaced by Max. Capability other selection will result in a
Advertised
Hardware/Software Mismatch alarm).
Default: 1000Mbps full duplex
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-67
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Flow Control
Controls the use of flow control for the
selected GbE port (when operating in
the full duplex mode), or back pressure
(when operating in the half-duplex
mode)
ENABLE – Flow control or back pressure is
enabled. In this case, when the offered Ethernet
traffic exceeds the available transmission
bandwidth, the port forces the source to reduce
its traffic volume.
DISABLE – Flow control and back pressure are
disabled.
Default: DISABLE
User Name
Redundancy
Used to enter a logical name for the
selected GbE port
Up to 10 alphanumeric characters.
Controls the use of 1+1 redundancy for
the selected port
NONE – No redundancy.
Default: Empty string
1+1 – 1+1 redundancy is enabled.
Default: NONE
³
Note
To configure GbE port redundancy:
When configuring the redundancy parameters, always start from the GbE port
that is to serve as the primary port of the pair.
If you must reconfigure the redundancy partners, it is recommended to first
select Redundancy = NONE for the current primary port, and then reconfigure all
the redundancy parameters.
1. On the Ethernet port selection screen (Figure 4-59), select the GbE port that
will serve as the primary port of the redundancy pair.
2. Select Redundancy, and then select 1+1 to enable redundancy. The screen
changes to display the additional parameters related to redundancy, and a
Primary (Yes) indicator appears at the top of the screen.
3. Configure the primary port parameters in accordance with the information
appearing in Table 4-16. A typical screen with all the redundancy-related
parameters is shown in Figure 4-61.
4-68
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 1(Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Primary
Admin Status
Auto Negotiation
Max Capability Advertised
Flow Control
User Name
Redundancy
Revertive
Wait To Restore[0 - 999]
Redundancy Slot
Redundancy Port
>
(Yes)
(Up)
(Enable)
>
(1000 MBPS Full Duplex)
(Enable)
... ()
>
(1+1)
>
(Yes)
... (300)
>
(CL-A )
>
(GbE 2 )
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-61. Typical Screen for the Primary GbE Port of a Redundancy Pair
4. At this stage, configure the remaining parameters of the other GbE port (the
secondary port of the redundancy pair). A typical screen with all the
redundancy-related parameters for the secondary GbE port is shown in
Figure 4-62.
Note
The other port, which is specified in the Redundancy Slot and Redundancy
Channel fields of the primary port, is automatically configured with compatible
parameters, and only the remaining parameters can be configured manually.
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 2
1.
2.
3.
4.
Admin Status
Redundancy
Primary
Revertive
Wait To Restore[0 - 999]
Redundancy Slot
Redundancy Port
Auto Negotiation
Max Capability Advertised
Flow Control
User Name
(Up)
(1+1)
(No)
(Yes)
(300)
(CL-A )
(GbE 1 )
(Enable)
>
(1000 MBPS Full Duplex)
(Enable)
... ()
>
>
>
...
>
>
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-62. Typical Screen for the Secondary GbE Port of a Redundancy Pair
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-69
Chapter 4 Configuration
Installation and Operation Manual
Table 4-16. GbE Port Redundancy Configuration Parameters
Parameter
Function
Values
Revertive
Selects the protection mode.
NO – Switching is non-revertive, that is, the
Megaplex-4100 will not flip back to the primary
port after the failed link returns to normal
operation, but only when the currently used link
fails.
This parameter is not displayed when
Redundancy is NONE
YES – Switching is revertive: the Megaplex-4100
will automatically return to the original port
when it returns to normal operation.
Default: NO
Wait to Restore
Specifies the time following the last
redundancy switching (flipping) during
which alarms are ignored.
The supported range is 0 to 999 seconds.
Default: 300
Therefore, the module starts evaluating
the criteria for redundancy switching
(flipping) only after this interval expires.
This ensures that another flipping
cannot occur before the specified
interval expires.
This parameter is not displayed when
Redundancy is NONE
Redundancy Slot Selects the slot in which the other
You can select either the same CL slot, or the
module of a redundancy pair is installed. other CL slot (provided a CL module with GbE
ports is programmed in the other slot).
The selection must always be
symmetrical.
Default: Same CL slot
This parameter is not displayed when
Redundancy is NONE
Redundancy Port Selects the other port of a redundancy
pair.
The selection must always be
symmetrical.
The available selections depend on the module
selected by means of the Redundancy Slot
parameter:
•
If the Redundancy Slot specifies the CL
module on which the primary port is located,
the only selection is the other GbE port on
the same module.
•
If the Redundancy Slot specifies the other CL
module, you can select any desired GbE port,
provided its Admin Status is Up.
This parameter is not displayed when
Redundancy is NONE
Default: – (None)
Configuring SDH/SONET Network Ports
Use the following procedure to configure the physical layer parameters of the
SDH or SONET ports and links located on the CL.1/155 and CL.1/155GbE modules.
Each SDH or SONET port can be separately configured.
4-70
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
This option is available only for Megaplex-4100 with CL.1/155 or CL.1/155GbE
modules.
To navigate to the required screen, use Configuration>Physical Layer>CL>CL-A or
CL-B>SDH/SONET
Task Selection
Figure 4-63 shows a typical SDH/SONET configuration task selection screen.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET
1.
2.
3.
4.
Card Configuration>
Link 1
>
Link 2
>
All Links>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-63. Configuration>Physical Layer>CL>SDH/SONET Task Selection Screen
³
To select a configuration task:
Select the number of the desired parameter, and then press <Enter> to display
the appropriate task:
Card Configuration
Configure the SDH/SONET operating mode.
Link 1
Configure the parameters of link 1 of the selected
CL module.
Link 2
Configure the parameters of link 2 of the selected
CL module.
All Links
Configure the same parameters for both links of
the selected CL module.
Even when it is necessary to select different
parameters for each link, you can use the common
configuration as a starting point, and modify the
parameters of each link as required.
Card Configuration
Figure 4-64 shows a typical Card Configuration screen. The parameters actually
displayed on the screen are automatically adjusted after each major selection.
Note
After changing the Frame Structure, the CL.1/155 and CL.1/155GbE subsystems
will be automatically reset when the database is updated, and the factory
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-71
Chapter 4 Configuration
Installation and Operation Manual
defaults for the new frame structure are automatically loaded. Therefore, it is not
recommended to perform this configuration change while the Megaplex-4100 is
connected to an operating network, and carries payload traffic.
The user is prompted to confirm the update by a DB values will change to
defaults, CL will restart after DB UPD. Are you sure Y/N message. Type y to
confirm.
³
To define the Card Configuration parameters:
Select the number of the desired parameter and then press <Enter>:
•
For the SDH/SONET Tx Clock, Master Port and Fallback Port, Common LVC
Parameters items, you will see separate parameters selection screens for
each link. The relevant parameters are explained in Table 4-17.
•
For the Common PDH LVC Parameters item, refer to page 4-74.
•
For the other items, the selection is toggled.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1.
2.
3.
4.
5.
6.
Frame Structure
Tx Clock Based on SSM
SDH/SONET Tx Clock
Master Port
Fallback Port
Common PDH LVC Parameters
>
>
>
(STM-1)
(No)
(Rx Clock)
(Link 1)
(Link 2)
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-64. Configuration>Physical Layer>CL-A>SDH/SONET>Card Configuration Screen
Table 4-17. SDH/SONET Card Configuration Parameters
Parameter
Function
Values
Frame Structure
Selects the set of standards defining the
operating mode of the SDH/SONET.
Make sure to select the same value for both
CL modules, although a change in one CL
module automatically changes the frame
structure of the other CL module (the last
selection governs)
STM-1 – Operation in accordance with the
SDH standards.
4-72
Configuring Megaplex-4100 for Operation
OC-3 – Operation in accordance with the
SONET standards.
Default: STM-1
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Tx Clock Based
on SSM
Controls the selection mode of the
STM-1/OC-3 transmit clock reference
YES – Automatic selection of the timing
reference, using the SSM received in the S1
byte of the STM-1 or OC-3 overhead. This
option can be selected only when both STM1/OC-3 links are connected.
This option should be used only when the
Megaplex-4100 is equipped with two CL
modules.
You can extend the selection to include the
station clock, by enabling the reception of
SSM messages for station clock interfaces as
explained in the Configuring Station Clock
Parameters on page 4-56.
NO – The selection of the timing reference
does not use the SSM.
Default: YES
SDH/SONET Tx
Clock
Selects the timing reference source of the
SDH/SONET transmit clock.
SYSTEM – The SDH/SONET transmit clock is
locked to the Megaplex-4100 nodal timing.
This parameter is displayed only when
Tx Clock Based on SSM is NO
Do not select SYSTEM when the system Clock
Source (see page 4-54) is S-SUBSYSTEM,
because this will result in unstable timing.
INTERNAL – The SDH/SONET transmit clock is
derived from the Megaplex-4100 internal
oscillator.
RX CLOCK – The SDH/SONET transmit clock is
locked to the clock recovered from the signal
received by the STM-1/OC-3 links.
Default: SYSTEM
Master Port
Selects the master timing reference source.
The available selections are LINK 1 and
This parameter is displayed only when when LINK 2.
the SDH/SONET transmit clock is RX CLOCK
Default: LINK 1
Fallback Port
Selects the fallback timing reference source. The available selections are LINK 1 and
This parameter is displayed only when when LINK 2. Always select the link not selected as
master port.
the SDH/SONET transmit clock is RX CLOCK
Default: LINK 2
Note
When an APS group is configured on the links specified as master and fallback
source, make sure to configure the corresponding redundancy partners with the
same clock priority, for example, if link 1 is a master clock source, then its partner
must also be included in the master clock lists.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-73
Chapter 4 Configuration
Installation and Operation Manual
Configuring Common PDH LVC Parameters
Figure 4-65 shows a typical Common PDH LVC Parameters screen. The parameters
are explained in Table 4-18.
MP-4100
...Ports>CL>CL-A>SDH/SONET>Card Configuration>Common PDH LVC Parameters
1. RDI on signal label
2. RDI on path trace
(Enable)
(Enable)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-65. Card Configuration – Common LVC Parameters Screens
Table 4-18. Card Configuration – Common PDH LVC Parameters
Parameter
Function
Values
RDI on Signal
Label
Controls the sending of RDI indications by the
port, in case the received signal label (OC-3
overhead byte C2) is different from the
expected signal label.
ENABLE – RDI is sent when a signal label
mismatch is detected.
DISABLE – RDI is not sent when signal label
mismatch is detected. Nevertheless, AIS and
Make sure to configure the same value for
RDI are still sent in case of LOP (loss of
links configured as redundancy partners in an pointer) or unequipped signal label
APS group
condition.
Default: DISABLE
RDI on Path
Trace
Controls the sending of RDI indications by the
port, in case the received path trace label
(carried in OC-3 overhead byte J1) is different
from the expected path trace label.
ENABLE – RDI is sent in case a signal label
mismatch is detected.
DISABLE – RDI is not sent when a signal
label mismatch is detected. Nevertheless,
Make sure to configure the same value for
RDI is still sent in case a LOP (loss of
links configured as redundancy partners in an pointer) or unequipped signal label
APS group
condition is detected.
Default: DISABLE
Configuring SDH/SONET Link Parameters
Figure 4-66 shows a typical Link 1 screen (the same parameters are also included
on the Link 2 screen). The parameters that can be configured are explained in
Table 4-19.
4-74
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Up)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-66. Typical SDH/SONET Link Screen
Table 4-19. SDH/SONET Link Parameters
Parameter
Function
Values
Admin Status
Used to enable/disable the
corresponding link interface
DOWN – The link interface on the
corresponding CL module is disabled. This
state should be selected as long as the port
configuration has not yet been completed, or
to stop using this port.
UP – The link interface on the corresponding
CL module is enabled.
Default: UP
User Name
RDI on Fail
Assign a logic name to the link
connected to this port
Alphanumeric string of up to 10 characters.
Controls the sending of RDI (remote
defect indication) in case of failure
ENABLE – RDI sending is enabled.
Default: Empty string
DISABLE – RDI sending is disabled.
Default: ENABLE
EED Threshold
Selects the BER value, which if exceeded The available selections are 3 (BER threshold of
results in the generation of the error
10-3), 4 (10-4) or 5 (10-5).
rate degradation alarm for the port
Default: 3 (BER of 10-3)
SD Threshold
Selects the BER value, which if exceeded The available selections are 6 (BER threshold of
results in the generation of the
10-6), 7 (10-7), 8 (10-8) or 9 (10-9).
signal-degraded alarm for the port
Default: 6 (BER of 10-6)
Configuring DCC Parameters
A typical DCC Configuration screen is shown in Figure 4-67. This screen is used to
configure the parameters needed to use the DCC for carrying inband
management traffic.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-75
Chapter 4 Configuration
Note
Installation and Operation Manual
The DCC can be used to carry management traffic only when it is passed
transparently by the SDH/SONET equipment providing the links between the
Megaplex-4100 units. Contact RAD Technical Support Department for additional
information on this issue.
A typical screen is shown in Figure 4-67. The parameters that can be configured
are explained in Table 4-20.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration
1.
2.
3.
4.
In Band Management>
Routing Protocol >
Management DCC
>
Deviation Type
(PPP Over HDLC)
(RIP 2)
(D1-D3)
(Standard)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-67. Typical DCC Configuration Screen
Note
When you select In Band Management as OFF, no additional parameters are
displayed.
Table 4-20. DCC Configuration Parameters
Parameter
Function
Values
In Band
Management
Selects the encapsulation protocol
used for inband management traffic
carried over the DCC
OFF – No encapsulation protocol selected; inband
management is not possible.
PPP OVER HDLC – PPP over HDLC encapsulation.
This protocol is compatible with some RAD
equipment, and equipment from other vendors.
HDLC – HDLC encapsulation. This protocol is
compatible with all the RAD equipment.
Default: OFF
4-76
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Routing Protocol
Selects the routing protocol for
management traffic carried over the
DCC
NONE – Dynamic routing of management traffic is
not supported. In this case, static routing is used,
and you must specify the information needed for
routing the management traffic.
PROPRIETARY RIP – The management traffic is
routed using the RAD RIP proprietary routing
protocol.
RIP 2 – The management traffic is routed using
the RIP2 protocol.
Default: NONE
Management DCC Selects the DCC bytes used to carry
inband management traffic
D1 – D3 – The management traffic is carried by
the regenerator section DCC bytes (D1, D2, D3).
The available bandwidth is therefore 192 kbps.
D4 – D12 – The management traffic is carried by
the multiplex section DCC bytes (D4 to D12). The
available bandwidth is therefore 576 kbps.
Default: D1 – D3
Deviation Type
Selects the PPP over HDLC flavor
supported by the Megaplex-4100.
STANDARD – PPP over HDLC in accordance with
RFC1661 and RFC1662.
This field, which affects the
protection loader format, is displayed
only when In Band Management is
HDLC or PPP OVER HDLC
TYPE 1 – PPP over HDLC based on RFC1661 and
RFC1662, but LCP (Link Control Protocol) packets
do not include address and control fields in their
overhead.
Default: STANDARD
Configuring All Links
Figure 4-66 shows a typical All Links screen, which is used to configure the
SDH/SONET links of both CL modules with similar parameters. The parameters
that can be configured are explained in Table 4-19 and Table 4-20.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>All Links
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Up)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
>
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-68. Typical SDH/SONET All Links Screen
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-77
Chapter 4 Configuration
Installation and Operation Manual
Configuring the Logical Layer
³
To configure Megaplex-4100 Logical Layer:
1. For Megaplex-4100 with CL.1/155 and CL.1/155GbE modules: configure the CL
low-order (PDH) and high-order (HVC) virtual ports. Refer to Configuring Logical
Layer on SDH/SONET Links for instructions.
2. Configure the required I/O virtual ports, in accordance with the Installation and
Operation Manual of the corresponding module.
3. Configure virtual ports for Ethernet services (relevant only for Megaplex-4100
with CL.1/GbE and CL.1/155GbE modules). Configuring a Megaplex-4100 for
providing Ethernet services is described in Configuring Ethernet Services below.
The virtual ports configuration activities are started from the Configuration>
Logical Layer submenu.
Figure 4-69 to Figure 4-72 show the structure of the Logical Layer submenu for
SDH and SONET links, respectively, and include typical virtual ports selection
screens. The options appearing on the selection screens depend on the modules
installed in the chassis.
4-78
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Logical Layer
IO
1. IO
2. CL
3. Bundles
I/O-1 (HS-U12)
1. I/O-1
2. I/O-2
..
..
I/O-2 (M8SL)
1. E1 1
2. E1 2
3. E1 3
4. E1 4
5. E1 5
6. E1 6
7. E1 7
8. E1 8
9. All Ports
1. IN 1
2. IN 2
3. IN 3
4. IN 4
5. IN 5
6. IN 6
7. IN 7
8. IN 8
9. IN 9
10. IN 10
11. IN 11
12. IN 12
13. IN 13
14. IN 14
15. IN 15
16. IN 16
17. IN 17
18. IN 18
19. IN 19
20. IN 20
21. IN 21
22. IN 22
23. IN 23
24. IN 24
25. IN 25
26. IN 26
27. IN 27
28. IN 28
29. IN 29
30. IN 30
31. IN 31
32. IN 32
33. IN 33
34. IN 34
35. IN 35
36. IN 36
E1 Ports
PDH 1
PDH
CL
1. PDH 1
.
.
.
..
.
.
1. PDH
2. VCAT
3. HVC
63. PDH 63
64. All PDHs
VCAT
1. Admin Status
2. User Name
3. Frame Type
4. Redundancy
5. Restoration Time
6. Idle Code
7. Cross Connect
8. In Band Management
9. Routing Protocol
10. LVC Configuration
VC Type
1. CL-A
2. CL-B
GFP Encapsulation
Typical
CL-A
VCG-1
1. VCG-1
2. VCG-2
3. VCG-3
4. VCG-4
5. VCG-5
6. VCG-6
7. VCG-7
8. VCG-8
9. All VCGs
1. Admin Status
2. VC Type
3. LCAS
4. Number of VCs
5. Encapsulation
6. Minimum Number of VCs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. LVC Configuration
11. GFP Configuration
For VCG.1 to
VCG.8 only
or
Redundancy = 1+1
VCG-1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VCs
5. Encapsulation
6. Minimum Number of VCs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. Revertive
11. Wait to Restore
12. Redundancy Slot
13. Redundancy Port
14. LVC Configuration
15. GFP Configuration
HVC
1. CL-A
2. CL-B
Bundles
1. VC12
2. VC3
3. VC4
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. Protection Mode
7. Mapping Mode
8. Protection Partner
9. Payload Label
LAPS Encapsulation
Typical
VCG 1
Encapsulation
1. GFP
2. LAPS
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. First Sequence Indicator
7. Extended Signal Label
8. RDI on Payload label
9. RDI on Path Trace
GFP Configuration
1. FCS
2. PTI for Client Data
3. UPI for Client Data
4. Delta
5. Core Scrambling
6. Payload Scrambling
1. Admin Status
2. VC Type
3. LCAS
4. Number of VCs
5. Encapsulation
6. Minimum Number of VCs
7. User Name
8. Redundancy
9. LVC Configuration
10. LAPS Configuration
For VCG.1 to
VCG.8 only
or
Redundancy = 1+1
VCG 1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VCs
5. Encapsulation
6. Minimum Number of VCs
7. User Name
8. Redundancy
9. Revertive
10. Wait to Restore
11. Redundancy Slot
12. Redundancy Port
13. LVC Configuration
14. LAPS Configuration
LAPS Configuration
1. Address
2. Control
3. SAPI Value
See
Sheet 2
1. Slot
2. Bundle
Figure 4-69. Typical Configuration>Logical Layer Submenu Structure (SDH) (Sheet 1 of 2)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-79
Chapter 4 Configuration
Installation and Operation Manual
Logical Layer
1. IO
2. CL
3. Bundles
CL
See
Sheet 1
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
Port 1
1. Port 1
2. Port 2
3. All Ports
VC-4
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. J1 Path Trace
5. Padding
6. EED Threshold
7. SD Threshold
8. Signal Label
Bundles
1. Slot
2. Bundle
MLPPP Bundle
(Unframed E1 Ports Only)
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot
11. Source Port
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. MLPPP MTU
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Number of Links
11. Source Slot
12. Source Port
CL
I/O
For CL
.
.
.
PDH Selection Screen
For I/O Modules
Link Selection Screen
Figure 4-70. Typical Configuration>Logical Layer Submenu Structure (SDH) (Sheet 2 of 2)
4-80
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Logical Layer
IO
1. IO
2. CL
3. Bundles
I/O-1 (HS-U12)
1. I/O-1
2. I/O-2
..
..
I/O-2 (M8SL)
1. E1 1
2. E1 2
3. E1 3
4. E1 4
5. E1 5
6. E1 6
7. E1 7
8. E1 8
9. All Ports
1. IN 1
2. IN 2
3. IN 3
4. IN 4
5. IN 5
6. IN 6
7. IN 7
8. IN 8
9. IN 9
10. IN 10
11. IN 11
12. IN 12
13. IN 13
14. IN 14
15. IN 15
16. IN 16
17. IN 17
18. IN 18
19. IN 19
20. IN 20
21. IN 21
22. IN 22
23. IN 23
24. IN 24
25. IN 25
26. IN 26
27. IN 27
28. IN 28
29. IN 29
30. IN 30
31. IN 31
32. IN 32
33. IN 33
34. IN 34
35. IN 35
36. IN 36
T1 Ports
PDH 1
PDH
CL
1. PDH 1
..
.
..
.
.
1. PDH
2. VCAT
3. HVC
84. PDH 84
85. All PDHs
VCAT
1. Admin Status
2. User Name
3. Frame Type
4. Redundancy
5. Restoration Time
6. Idle Code
7. Cross Connect
8. In Band Management
9. Routing Protocol
10. LVC Configuration
1. CL-A
2. CL-B
VC Type
1. VT-1.5
2. STS-1/SPE
GFP Encapsulation
Typical
CL-A
VCG-1
1. VCG-1
2. VCG-2
3. VCG-3
4. VCG-4
5. VCG-5
6. VCG-6
7. VCG-7
8. VCG-8
9. All VCGs
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. LVC Configuration
11. GFP Configuration
For VCG.1 to
VCG.8 only
or
Redundancy = 1+1
VCG-1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Virtual Concatenation
9. Redundancy
10. Revertive
11. Wait to Restore
12. Redundancy Slot
13. Redundancy Port
14. LVC Configuration
15. GFP Configuration
HVC
1. CL-A
2. CL-B
Bundles
Encapsulation
1. GFP
2. LAPS
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. First Sequence Indicator
7. Extended Signal Label
8. RDI on Payload label
9. RDI on Path Trace
GFP Configuration
1. FCS
2. PTI for Client Data
3. UPI for Client Data
4. Delta
5. Core Scrambling
6. Payload Scrambling
LVC Configuration
1. J2 Rx Path Trace
2. J2 Path Trace
3. Padding
4. EED Threshold
5. SD Threshold
6. Protection Mode
7. Mapping Mode
8. Protection Partner
9. Payload Label
LAPS Encapsulation
Typical
VCG 1
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Redundancy
9. LVC Configuration
10. LAPS Configuration
For VCG.1 to
VCG.8 only
or
Redundancy = 1+1
VCG 1
Primary
1. Admin Status
2. VC Type
3. LCAS
4. Number of VTs
5. Encapsulation
6. Minimum Number of VTs
7. User Name
8. Redundancy
9. Revertive
10. Wait to Restore
11. Redundancy Slot
12. Redundancy Port
13. LVC Configuration
14. LAPS Configuration
LAPS Configuration
1. Address
2. Control
3. SAPI Value
See
Sheet 2
1. Slot
2. Bundle
Figure 4-71. Typical Configuration>Logical Layer Submenu Structure (SONET) (Sheet 1 of 2)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-81
Chapter 4 Configuration
Installation and Operation Manual
Logical Layer
1. IO
2. CL
3. Bundles
CL
See
Sheet 1
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
1. Port 1
2. Port 2
3. All Ports
4. Common Parameters
Port 1
1. STS1-1
2. STS1-2
3. STS1-3
STS1-1
1. J1 Path Trace
2. Padding
3. Signal Label
Bundles
Common Parameters
1. Slot
2. Bundle
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. EED Threshold
5. SD Threshold
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot
11. Source Port
CL
I/O
For CL
PDH Selection Screen
For I/O Modules
Link Selection Screen
Figure 4-72. Typical Configuration>Logical Layer Menu Structure (SONET) (Sheet 2 of 2)
The configuration of the virtual port parameters for the modules programmed in
the various Megaplex-4100 slots is started from the Logical Layer submenu. This
screen is used to select the class of virtual ports to be configured.
To navigate to the required screen, use Configuration>Logical Layer.
4-82
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
A typical Logical Layer screen for a Megaplex-4100 equipped with CL.1/155 and
CL.1/155GbE modules is shown in Figure 4-73. This screen includes the following
options:
I/O
For configuring the virtual port parameters of modules installed in I/O
slots. Configuration instructions for these modules can be found in
the Installation and Operation Manual of each module.
Note however that not all the I/O modules have virtual ports.
CL
For configuring the parameters of the virtual ports located on the
CL.1/155 and CL.1/155GbE modules.
Note that the CL.1 module does not have virtual ports.
Bundles
For configuring Ethernet services bundles on E1 and T1 ports
(including PDH ports on CL.1/155 and CL.1/155GbE modules).
MP-4100
Configuration>Logical Layer
1. IO
>
2. CL
>
3. Bundles>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-73. Typical Logical Layer Class Selection Screen
³
To select the type of virtual ports to be configured:
Type the corresponding item number and then press <Enter>.
Selecting a Specific I/O Module Virtual Port to be Configured
The selection of a virtual I/O port to be configured is made in two steps:
1. Select a specific I/O module.
2. Select a specific port on the selected module.
³
To select a virtual port on an I/O module:
1. On the screen of Figure 4-73, select IO and then press <Enter>.
2. You will see the I/O module selection screen. A typical screen is shown in
Figure 4-74. The screen includes only modules programmed in the chassis that
have virtual ports.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-83
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>IO
1.
2.
3.
4.
5.
6.
I/O
I/O
I/O
I/O
I/O
I/O
1
2
3
6
7
8
(HS-U12)>
(M8SL)>
(M8SL)>
(HS-U12)>
(HS-U12)>
(HS-U12)>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-74. Typical I/O Logical Layer Module Selection Screen
3. Select a module from the list by typing the number corresponding to its slot,
and then press <Enter>.
4. You will see the Slot port selection screen for the selected module. The ports
appearing on the screen depend on the module type. Refer to the Installation
and Operation Manual of the module for configuration instructions.
Configuring Logical Layer on SDH/SONET Links
Selecting the Specific CL Virtual Port to be Configured
The selection of the CL virtual port to be configured is made in two steps:
1. Select the type of ports to be configured.
2. Select a specific port of the selected type.
³
To select a virtual port on a CL.1/155 or CL.1/155GbE module:
1. On the screen of Figure 4-73, select CL and then press <Enter>.
2. You will see the CL port type selection screen. A typical screen is shown in
Figure 4-75.
The screen includes the following options:
4-84
PDH
Configure the parameters of the internal PDH ports.
VCAT
Configure the virtually concatenated groups on the SDH/SONET links
(available only on CL.1/155GbE modules). See Configuring Ethernet
Services for instructions.
HVC
Configure the parameters of the high-order virtual containers in the
SDH/SONET link frame.
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL
1. PDH >
2. VCAT>
3. HVC >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-75. Typical CL Logical Layer Type Selection Screen
3. Select the desired option, and then press <Enter>.
Configuring Virtual PDH Ports
Use the following procedure to configure the parameters of the virtual PDH ports
of the CL.1/155 or CL.1/155GbE modules, and assign the port timeslots (instead
of using Configuration>System>TS Assignment). It is not necessary to select a
specific CL.1/155 or CL.1/155GbE module; at any time, only the PDH mapper of
the active CL module is used to carry traffic, and therefore only one set of
configuration parameters is used for both CL modules.
For convenience, you can simultaneously configure the parameters of all the PDH
ports (except for redundancy parameters and timeslot assignment, which cannot
be simultaneously configured for all the ports). You can then change the
configuration of individual PDH ports as required.
To navigate to the required screen, use Configuration>Logical Layer>CL>PDH.
Configuring PDH Parameters
1. On the screen of Figure 4-73, select CL and then press <Enter>.
2. On the CL Logical Layer screen, select PDH and then press <Enter>.
3. You will see the PDH ports selection screen. A typical screen is shown in
Figure 4-76. The screen includes two pages: use N and P to scroll among the
two pages. The current Admin Status of each port appears next to its name.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-85
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>CL>PDH
1.
2.
3.
4.
5.
6.
7.
8.
9.
0.
1.
...
>
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
(N)
1 (Down)>
2 (Down)>
3 (Down)>
4 (Down)>
5 (Down)>
6 (Down)>
7 (Down)>
8 (Down)>
9 (Down)>
10 (Down)>
11 (Down)>
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
12
13
14
15
16
17
18
19
20
21
22
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
23
24
25
26
27
28
29
30
31
32
33
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
(Down)>
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
PDH
34
35
36
37
38
39
40
41
42
43
44
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
Down)>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-76. Typical PDH Port Selection Screen
Note
The number of ports appearing on the second page depends on the port type:
• For SDH links, the total number of PDH ports is 63, and all the ports simulate
internal E1 ports
• For SONET links, the total number of PDH ports is 84, and all the ports
simulate internal T1 ports.
The last item on the second page is All Ports.
4. Select the number of the desired port, for example, 1 for PDH 1 and then press
<Enter> to display the parameters configuration screen.
You can also select All Ports: in this case, Redundancy is a read-only
parameter, and is set to None.
5. You will see the corresponding PDH configuration screen. Typical PDH
configuration screens with default values are shown in Figure 4-77 and
Figure 4-78. Table 4-21 lists the port configuration parameters of E1 ports on
SDH links, and Table 4-22 lists the parameters of T1 ports on SONET links.
6. To configure the port parameters, select the desired item and then press
<Enter> to display the corresponding parameter selection screen, or toggle the
current selection.
For LVC Configuration instructions, see page 4-92.
For Time Slot Assignment instructions, see Configuring Timeslot Assignment
on page 4-140.
4-86
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Admin Status
User Name
Frame Type
Redundancy
Restoration Time
Idle Code[0 - ff]
Cross Connect
In Band Management
LVC Configuration
Time Slot Assignment
...
>
>
>
...
>
>
>
(Up)
()
(G.732S)
(None)
(CCITT)
(FF)
(DS0)
(Off)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-77. Typical PDH Configuration Screen (E1 Port on SDH Link)
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Frame Type
Redundancy
FDL Type
Restoration Time
Idle Code[0 - ff]
Cross Connect
In Band Management
LVC Configuration
Time Slot Assignment
...
>
>
>
>
...
>
>
>
(Down)
()
(ESF)
(None)
(Response)
(10 Seconds (62411))
(FF)
(DS0)
(Off)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-78. Typical PDH Configuration Screen (T1 Port on SONET Link)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-87
Chapter 4 Configuration
Installation and Operation Manual
Table 4-21. PDH Virtual Port Parameters – E1 Ports (SDH Links)
Parameter
Function
Values
Admin Status
Used to enable/disable the flow of
traffic through the selected port
UP – The flow of traffic is enabled.
DOWN – The flow of traffic is disabled. This state
should be selected as long as the port
configuration has not yet been completed, or
when it is necessary to stop traffic flow through
the port.
Default: DOWN
User Name
Frame Type
Used to assign a logical name to the
selected port
Up to 25 alphanumerical characters.
Selects the port framing mode.
G.732N – The port handles the traffic as a basic
G.704 framed signal. The port terminates the E1
overhead.
Do not select G.732S or G.732S-CRC4
framing for ports used by Ethernet
services: if you intend to configure
Ethernet bundles on this port, you must
select G.732N or G.732N-CRC4 framing.
Default: Empty String
G.732N-CRC4 – The port handles the traffic as a
basic G.704 framed signal, with the CRC-4 option
enabled. The port terminates the E1 overhead.
It is recommended to select a mode that G.732S – The port handles the traffic as a G.704
supports CRC-4, to enable the collection framed signal with multiframe structure based
of performance monitoring data
on timeslot 16. The port terminates the E1
overhead.
G.732S-CRC4 – The port handles the traffic as a
G.704 framed signal with multiframe structure
based on timeslot 16, with the CRC-4 option
enabled. The port terminates the E1 overhead.
Default: G.732S
Redundancy
Controls the use of port redundancy.
NONE – Redundancy disabled for the port being
configured.
When redundancy is enabled,
Megaplex-4100 uses the revertive mode. DUAL CABLE P. TX – Redundancy function is
enabled. Each of the two ports in the
Therefore, make sure to select an
redundancy pair is connected through a separate
appropriate Wait to Restore value.
After redundancy is enabled, additional connection to the remote equipment, and both
ports transmit in parallel the same data.
read-only fields appear to provide
information on the redundancy partner Therefore, a remote Megaplex-4100 unit can
independently select an active port, and does
slot and channel (port), and the
redundancy status of the port (primary not have to flip to synchronize its selection with
that of the local Megaplex-4100 unit.
or not). The first port of a redundancy
pair always becomes the primary port,
therefore make sure to plan ahead the
order in which ports are configured.
Default: NONE
See redundancy configuration guidelines
in the Note on page 4-92
4-88
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Parameter
Chapter 4 Configuration
Function
Values
Restoration Time Used to change the frame
synchronization algorithm, to reduce the
time required for the port to return to
normal operation after local loss of
synchronization
1 SECOND (FAST) – After 1 second.
10 SECONDS (62411) – Similar to the
requirements of AT&T TR-62411 (after
10 seconds).
CCITT – Complies with ITU-T Rec. G.732.
Default: CCITT
Idle Code
Selects the code transmitted to fill idle
(unused) timeslots in the frames
transmitted through this port.
The available selections are 00 to FF (hexa).
Do not select 00, 08, 10, 12, 21, 24, 42, 49, 84,
or 92 as the idle code.
Default: 7F
Cross Connect
Selects the handling of the data passing DS0 – Enables routing each individual timeslot
through the port
from this port to other module ports or bundles.
Also supports split timeslot assignment.
DS1 – All the payload timeslots are transparently
connected.
Default: DS0
Destination Slot
Specifies the module (I/O slot) to which
the data stream handled by the port is
routed.
The available selections are the CL modules
installed in the chassis, and I/O modules IO-1 to
IO-10.
When the port serves as termination
point of an Ethernet services bundle, it
is not necessary to select a destination
slot.
Default: – (None)
This parameter is displayed only when
using the DS1 cross-connect mode
Destination Port
Specifies the port to which the data
stream handled by the port is routed.
When the port serves as termination
point of an Ethernet services bundle, it
is not necessary to select a destination
port.
The available selections are 1 to 8 for external or
internal ports, or 1 to 63 for PDH ports (actual
range depends on the destination module).
Default: – (None)
This parameter is displayed only when
using the DS1 cross-connect mode
Redundancy Slot Selects the slot in which the other
The available selections are the CL modules
module of a redundancy pair is installed. installed in the chassis, and I/O 1 to I/O 10.
For ports on which Ethernet service
bundles are defined, another PDH port,
or another module with Ethernet ports,
for example, M8E1 or M8SL, must be
selected.
Default: CL
The selection must always be
symmetrical.
This parameter is not displayed when
Redundancy is NONE
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-89
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Redundancy
Channel
Selects the other port of a redundancy
pair.
The available selections are 1 to 8 for external or
internal ports, or 1 to 63 for PDH ports (actual
range depends on the destination module).
The selection must always be
symmetrical.
Default: – (None)
This parameter is not displayed when
Redundancy is NONE
Wait to Restore
Specifies the time following the last
redundancy switching (flipping) during
which alarms are ignored.
The supported range is 0 to 999 seconds.
Default: 300
Therefore, the module starts evaluating
the criteria for redundancy switching
(flipping) only after this interval expires.
This ensures that another flipping
cannot occur before the specified
interval expires.
This parameter is not displayed when
Redundancy is NONE
Inband
Management
Controls the transfer of inband
management traffic through this port
OFF – The transfer of management traffic is
disabled.
DEDICATE PPP – The transfer of management
traffic is enabled. The management traffic is
transferred in a dedicated timeslot, using
synchronous PPP over HDLC encapsulation.
DEDICATE FR – The transfer of management
traffic is enabled. The management traffic is
transferred in a dedicated timeslot, using Frame
Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
Default: OFF
Routing Protocol When the transfer of inband
management traffic is enabled, controls
the transmission of RIP2 routing tables.
Transmitting these tables enables other
equipment to use the RIP2 routing
protocol for management traffic carried
through this port.
This parameter is not displayed when
Inband Management is OFF
NONE – Routing of management traffic not
supported.
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.
PROP RIP NO NMS TX – Same as RIP2, but the
routing tables transmitted through this port do
not include information on the network
management stations (NMS) learned by the
Megaplex-4100.
Default: NONE
4-90
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Primary
Displays the port function in a
redundancy pair. Configuration
parameters prepared for the primary
port are automatically copied to the
other port as soon as the other port is
specified.
YES — This port serves as the primary port of a
redundancy pair.
NO — This port serves as the alternative port of
a redundancy pair.
Default: NO
This parameter is not displayed when
Redundancy is NONE
Table 4-22. PDH Virtual Port Parameters – T1 Ports
Parameter
Function
Admin Status
See Table 4-21
User Name
See Table 4-21
Frame Type
Determines the framing mode for this
port
Values
SF (D4) – The port handles the traffic as an SF
framed signal with robbed bit signaling (12
frames per multiframe).
ESF – The port handles the traffic as an ESF
framed signal with robbed bit signaling (24
frames per multiframe).
Default: ESF
Redundancy
See Table 4-21
FDL Type
Controls the operating mode of the FDL. RESPONSE – The Megaplex-4100 only answers
commands received through the FDL, and thus
This option can be selected only when
the framing mode is ESF, otherwise this does not initiate FDL traffic.
field shows N/A, and cannot be changed COMMAND – The Megaplex-4100 can initiate
polling by sending commands through the FDL.
NONE – FDL is ignored.
Default: RESPONSE
Restoration Time Used to change the frame
synchronization algorithm, to reduce the
time required for the port to return to
normal operation after local loss of
synchronization
1 SECOND (FAST) – After 1 second.
Idle Code
The available range is 60 to 7F, and C0 to FF
(hexa).
Selects the code transmitted to fill idle
(unused) timeslots in frames
transmitted through the port
10 SECONDS (62411) – Similar to the
requirements of AT&T TR-62411 (after
10 seconds).
Default: 10 SECONDS (62411)
Do not select 84 or 92 as the idle code.
Default: 7F
Cross Connect
See Table 4-21
Destination Slot
See Table 4-21
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-91
Chapter 4 Configuration
Parameter
Function
Destination Port
See Table 4-21.
Installation and Operation Manual
Values
The available selections are 1 to 8 for
external ports, or 1 to 84 for PDH ports
(actual range depends on the
destination module)
Redundancy Slot See Table 4-21
For ports on which Ethernet service
bundles are defined, another PDH port,
or another module with Ethernet ports,
for example, M8T1, must be selected
Redundancy
Channel
See Table 4-21.
The available selections are 1 to 8 for
external ports, or 1 to 84 for PDH ports
(actual range depends on the
destination module)
Wait to Restore
See Table 4-21
Inband
Management
See Table 4-21
Routing Protocol See Table 4-21
See Table 4-21
Primary
Note
When using the redundancy feature, it is necessary to select the same values for
the following parameters of the two ports configured as a redundancy pair:
• Admin Status
• Restoration Time
• Frame Line
• Inband Management
• Redundancy
• Routing Protocol
• Idle Code
• Cross Connect
However, you can select different Wait to Restore times, because the times
selected at the two ends should be different.
To save duplication of configuration parameters, all the parameters listed above
are selectable only for the primary port, and therefore make sure to configure
first the primary port of a redundancy pair. The parameters of the other
(alternative) port are automatically copied from the primary port after the
configuration of the primary port has been completed, even before the database
has been updated (you can display the port configuration parameters using the
Monitoring menu).
The same is true with respect to timeslot assignment: only the primary port must
be configured.
Configuring the LVC Parameters
A typical LVC Configuration screen is shown in Figure 4-77. The parameters that
can be configured are explained in Table 4-23. Note that in addition to the
4-92
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
parameters configured by means of the LVC Configuration screen, there is a
common set of LVC parameters, configured as port of the SDH/SONET physical
port parameters, by means of the Common PDH LVC Parameters screen (see
Configuring Common PDH LVC Parameters section starting on page 4-74).
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1 (Up)>LVC Configuration
1.
2.
3.
4.
5.
6.
7.
8.
9.
J2 Rx path trace
J2 path trace
Padding
EED Threshold
SD Threshold
Protection Mode
Mapping Mode
Protection Partner
Payload Label
[0 – 7]
(Enable)
... (www.rad.com)
(NULLs)
>
(1E-3)
>
(1E-6)
>
(Path Protection)
>
(Auto)
>
(Adjacent CL)
... (2)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-79. Typical LVC Configuration Screen for PDH Ports
Table 4-23. LVC Configuration Parameters for CL.1/155 and CL.1/155GbE PDH Ports
Parameter
Function
Values
J2 Rx Path Trace
Controls the checking of the received ENABLE – Path trace label is checked.
path trace label by the corresponding DISABLE – Path trace label is not checked.
group
Default: DISABLE
J2 Path Trace
Specifies the path trace label.
Alphanumeric string of 15 characters. If not
This parameter is relevant only when all of the 15 characters are needed for the
prescribed label, make sure to specify the
J2 Rx Path Trace is ENABLE
appropriate Padding method.
Default: www.rad.com
Padding
Specifies the type of characters used NULLS – NUL characters.
to pad the path trace label, when it
SPACES – Space characters.
is shorter than the required length of
Default: NULLS
15 characters
EED Threshold
Selects the BER value, which if
The available selections are 1E-3 (BER
exceeded results in the generation of threshold of 10-3), 1E-4 (10-4) or 1E-5 (10-5).
the error rate degradation alarm for Default: 1E-3 (BER of 10-3)
the port
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-93
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
SD Threshold
Selects the BER value, which if
The available selections are 1E-6 (BER
exceeded results in the generation of threshold of 10-6), 1E-7 (10-7), 1E-8 (10-8) or
the signal-degraded alarm for the
1E-9 (10-9).
port
Default: 1E-6 (BER of 10-6)
Protection Mode
Selects the traffic protection mode
OFF – No protection.
Path Protection – Path protection enabled.
Default: OFF
Mapping Mode
Select the mapping mode of the TU
AUTO – Automatic mapping: the mapping of
carrying the payload of the PDH port. the PDH port selected as primary on one
This parameter is not displayed when SDH/SONET link is automatically copied to the
same TU on the other SDH/SONET link. AUTO
Protection Mode is OFF
cannot be selected when the PDH port is
already mapped (the mapping must be
manually performed, or perform the mapping
only after the Path Protection mode is
selected).
MANUAL – Manual mapping. The port is
mapped manually to different TUs of the
same link, or on different links.
Default: AUTO
Protection Partner
Specifies the link serving as the
protection link for link being
configured.
ADJACENT CL – The protection link is the
SDH/SONET link with the same number
located on the other CL module. For example,
This parameter is not displayed when if you are configuring link A of the CL module
A, the corresponding protection partner is
Protection Mode is OFF
link A of the CL module B.
LOCAL CL – The protection link is the other
SDH/SONET link on the same CL module. For
example, if you are configuring link A of the
CL module A, the corresponding protection
partner is link B of the CL module A.
Default: LOCAL CL
Payload Label
Specifies the expected signal label
(one byte)
Number in the range of 0 to 7.
Default: 2
Configuring HVC Virtual Ports
Use the following procedure to configure the parameters of the virtual high-order
ports (VC-4 virtual container for SDH links, or STS-1 SPE for SONET links) of the
CL.1/155 or CL.1/155GbE modules installed in the Megaplex-4100.
Separate parameters can be configured for each high-order port on each CL
module.
For convenience, you can simultaneously configure the parameters of all STS-1
ports of a CL module; you can then change the configuration of each port as
required.
4-94
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
To navigate to the required screen, use Configuration>Logical Layer>CL>HVC.
Selecting the CL.1/155 or CL.1/155GbE to be Configured
1. Select HVC on the CL menu. You will see the screen used to select between the
two CL modules that can be installed in the Megaplex-4100. A typical CL
module selection screen is shown in Figure 4-80.
MP-4100
Configuration>Logical Layer>CL>HVC
1. CL-A>
2. CL-B>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-80. Configuration>Logical Layer>CL>HVC>CL Selection Screen
2. Select the desired CL module and then press <Enter> to display the
configuration task selection screen for the selected CL module.
Configuring HVC Ports for CL.1/155 or CL.1/155GbE with SDH Links
For CL.1/155 or CL.1/155GbE modules with SDH links, you must select the target
port: all the ports on the selected CL module, or only the HVC port of a specific
SDH link.
Figure 4-81 shows a typical HVC task selection screen for the selected CL.1/155
or CL.1/155GbE module.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A
1. Port 1
2. Port 2
3. All Ports
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-81. Typical HVC Selection Screen for CL.1/155 or CL.1/155GbE Module with SDH Links
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-95
Chapter 4 Configuration
³
Installation and Operation Manual
To select the HVC to be configured (SDH links):
1. Select the number of the desired task, and then press <Enter> to display the
appropriate configuration screen:
Port 1
Configure the VC-4 parameters of port 1 of the selected CL
module.
Port 2
Configure the VC-4 parameters of port 2 of the selected CL
module.
All Ports
Configure the same parameters for both SDH ports of the
selected CL module.
When it is necessary to select different parameters for each
port, you can use the common configuration as a starting point,
and then modify the parameters of each port as required.
³
To configure HVC parameters (SDH links):
A typical VC-4 configuration screen with factory defaults for HVC Logical Layer is
shown in Figure 4-82.
The parameters that can be configured by means of the VC-4 screen are
described in Table 4-24.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1
1.
2.
3.
4.
5.
6.
7.
VC-4
RDI on signal label
RDI on path trace
J1 Rx path trace
J1 path trace
...
EED Threshold
>
SD Threshold
>
Signal Label[0 - ff]...
(Disable)
(Disable)
(Disable)
(www.rad.com)
(1E-3)
(1E-6)
(02)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-82. Typical VC-4 Configuration Screen for Logical Layer (SDH Links)
4-96
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-24. Configuration – VC-4 Parameters (CL with SDH Links)
Parameter
Function
Values
RDI on Signal
Label
Controls the sending of RDI indications by the ENABLE – RDI is sent when a signal label
port, in case the received signal label is
mismatch is detected.
different from the expected signal label
DISABLE – RDI is not sent when signal label
mismatch is detected. Nevertheless, RDI is
still sent in case of LOP (loss of pointer) or
unequipped signal label condition.
Default: DISABLE
RDI on Path
Trace
Controls the sending of RDI indications by the
port, in case the received path trace label
(carried in SDH overhead byte J1) is different
from the expected path trace label
ENABLE – RDI is sent in case a signal label
mismatch is detected.
DISABLE – RDI is not sent when a signal
label mismatch is detected. Nevertheless,
RDI is still sent in case a LOP (loss of
pointer) or unequipped signal label
condition is detected.
Default: DISABLE
J1 Rx Path Trace
Controls the checking of the received path
trace label by the port
ENABLE – Path trace label is checked.
DISABLE – Path trace label is not checked.
Default: DISABLE
J1 Path Trace
Specifies the path trace label.
This parameter is relevant only when J1 Rx
Path Trace is ENABLE
Alphanumeric string of up to 15 characters.
If not all of the 15 characters are needed
for the prescribed label, make sure to
specify the appropriate Padding method.
Default: www.rad.com
EED Threshold
SD Threshold
Selects the BER value, which if exceeded
results in the generation of the error rate
degradation alarm for the port
The available selections are 1E-3 (BER
threshold of 10-3), 1E-4 (10-4), 1E-5 (10-5).
Default: 1E-3 (BER of 10-3)
Selects the BER value, which if exceeded
results in the generation of the
signal-degraded alarm for the port
The available selections are 1E-6 (BER
threshold of 10-6), 1E-7 (10-7), 1E-8 (10-8) or
1E-9 (10-9).
Default: 1E-6 (BER of 10-6)
Signal Label
Specifies the expected signal label (one byte) Hexadecimal number in the range of 0 to FF
(two digits).
Default: 02
Configuring HVC Ports for CL.1/155 or CL.1/155GbE with SONET
Links
For CL.1/155 or CL.1/155GbE modules with SONET links, you must select the
target port: all the ports on the selected CL module, or only the HVC ports of a
specific SONET link. In addition, you need to configure common HVC parameters
for each SONET port.
Figure 4-83 shows a typical HVC task selection screen for the selected CL.1/155
or CL.1/155GbE module.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-97
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A
1.
2.
3.
4.
Port 1
>
Port 2
>
All Ports
>
Common Parameters>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-83. Typical HVC Task Selection Screen for CL Module with SONET Links
³
To select the HVC to be configured (SONET links):
1. Select the desired task:
Port 1
Configure the STS-1 parameters used only for SONET port 1
of the selected CL module.
Port 2
Configure the STS-1 parameters used only for SONET port 2
of the selected CL module.
All Ports
Configure the same parameters for all the STS-1s on both
SONET ports of the selected CL module.
When necessary to select different parameters for each
STS-1, you can use the common configuration as a starting
point, and then modify the parameters of each STS-1 as
required.
Common
Parameters
Configure the parameters that must have identical values for
all the STS-1s of the same CL module.
2. After selecting a specific SONET port, you must select a specific STS-1. The
STS-1 selection (Figure 4-85) screen opens after pressing <Enter>.
³
To configure HVC parameters (SONET links):
1. Select Common Parameters on the HVC selection screen. A typical screen is
shown in Figure 4-84. The parameters that can be configured by means of the
Common Parameters screen are described in Table 4-25.
4-98
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Common Parameters
1.
2.
3.
4.
5.
RDI on signal label
RDI on path trace
J1 Rx path trace
EED Threshold
>
SD Threshold
>
(Disable)
(Disable)
(Disable)
(1E-3)
(1E-6)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-84. Typical HVC Common Parameters Screen for CL with SONET Links
Table 4-25. Configuration – Common Parameters (CL.1/155 with SONET Links)
Parameter
Function
Values
RDI on Signal
Label
Controls the sending of RDI indications, in
case the received signal label is different
from the expected signal label
ENABLE – RDI is sent when a signal label
mismatch is detected.
DISABLE – RDI is not sent when signal label
mismatch is detected. Nevertheless, RDI is still
sent in case of LOP (loss of pointer) or
unequipped signal label condition.
Default: DISABLE
RDI on Path
Trace
Controls the sending of RDI indications by
the ports, in case the received path trace
label (carried in SONET overhead byte J1)
is different from the expected path trace
label
ENABLE – RDI is sent in case a signal label
mismatch is detected.
DISABLE – RDI is not sent when a signal label
mismatch is detected. Nevertheless, RDI is still
sent in case a LOP (loss of pointer) or
unequipped signal label condition is detected.
Default: DISABLE
J1 Rx Path Trace
Controls the checking of the received path ENABLE – Path trace label is checked.
trace label by the ports
DISABLE – Path trace label is not checked.
Default: DISABLE
EED Threshold
SD Threshold
Selects the BER value, which if exceeded
results in the generation of the error rate
degradation alarm for the STS-1 ports
Selects the BER value, which if exceeded
results in the generation of the
signal-degraded alarm for the STS-1 ports
Megaplex-4100 Ver. 2.0
The available selections are 1E-3 (BER
threshold of 103), 1E-4 (104), 1E-5 (105).
Default: 1E-3 (BER of 103)
The available selections are 1E-6 (BER threshold
of 106), 1E-7 (107), 1E-8 (1-8) or 1E-9 (109).
Default: 1E-6 (BER of 106)
Configuring Megaplex-4100 for Operation
4-99
Chapter 4 Configuration
Installation and Operation Manual
2. Select the desired CL SONET port (Port 1 or Port 2), or All Ports on the HVC
task selection screen. If you select a specific SONET port, you will see the
STS-1 selection screen (Figure 4-85).
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1
1. STS1-1
2. STS1-2
3. STS1-3
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-85. Typical STS-1 Selection Screen (CL with SONET Links)
3. After selecting the desired STS-1 port on the STS-1 selection screen, or All
Ports, you will see the STS-1 configuration screen. A typical screen is shown
in Figure 4-86. The parameters that can be configured by means of the STS-1
screen are described in Table 4-26.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1>STS1-1
1. J1 path trace
2. Padding
3. Signal Label
... (www.rad.com)
(Nulls)
... (02)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-86. Typical STS-1 Configuration Screen (CL with SONET Links)
4-100
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-26. Configuration – STS-1 Parameters (CL with SONET Links)
Parameter
Function
Values
J1 Path Trace
Specifies the path trace label.
Alphanumeric string of up to 15 characters.
If not all of the 15 characters are needed
for the prescribed label, make sure to
specify the appropriate Padding method.
This parameter is relevant only when J1 Rx
Path Trace is ENABLE
Default: www.rad.com
Padding
Specifies the type of characters used to pad
the path trace label, when it is shorter than
the required length of 15 characters.
The selected value overrides the Common
Parameters selection
Signal Label
NULLS – NUL characters.
SPACES – Space characters.
Default: NULLS
Specifies the expected signal label (one byte) Hexadecimal number in the range of 0 to FF
(two digits).
Default: 02
Configuring Ethernet Services
Using the Metropolitan Ethernet Forum terms, Ethernet traffic is forwarded (or
flows) among specified bridge ports in accordance with user-configured rules that
define Ethernet Virtual Connections (flows). Therefore, Ethernet services are
configured by defining flows within the Megaplex-4100. A flow interconnects at
least two bridge ports, however a given bridge port can serve as the termination
point of several flows. The maximum number of flows that can be defined on a
Megaplex-4100 is 250.
Note
For an overview of the MEF definition of Ethernet services, refer to Appendix C.
The current Megaplex-4100 version supports E-line flows per Metro Ethernet
Forum (MEF) specifications (an E-line is a type of Ethernet virtual connection that
interconnects exactly two bridge ports).
The following types of bridge ports can be defined:
•
Logical ports configured on E1 or T1 ports (including PDH ports), called
bundles (M8E1, M8T1, and M8SL modules). Bundles use a special protocol
to support the flow of Ethernet traffic. Two types of bundle protocols can
be used: HDLC and MLPPP.
•
Each Ethernet physical port (of the type located on M8E1, M8T1, M8SL,
MPW-1, OP-108C, OP-106C, or ASMi-54C modules) can also serve as a
bridge port.
•
Each Internal Eth port of the OP-108C or OP-106C modules
•
Each active PCS of the ASMi-54C module
•
Virtually concatenated groups, defined on the SDH/SONET links of
CL.1/155GbE modules
•
GbE ports located on the Megaplex-4100 CL.1/GbE and CL.1/155GbE
modules
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-101
Chapter 4 Configuration
Installation and Operation Manual
The total number of bridge ports supported by a Megaplex-4100 is as follows.
•
For I/O modules with Ethernet ports:
• One bridge port exists on each Ethernet physical interface.
• One bridge port exists on each bundle (M8E1, M8T1, and M8SL modules).
• Two internal Ethernet bridge ports exist on each OP-108C or OP-106C
module
• 8 bridge ports exist on each PCS of the ASMi-54C module
• 100 bridge ports exist on the router interface of the MPW-1 module.
The maximum number of bridge ports that exist on each module with
Ethernet interface is summarized in Table 4-27.
Table 4-27. Maximum Number of Bridge Ports for Megaplex-4100 Modules
Module Name
External Ports
Other
M8E1, M8T1, M8SL
3
32 (Bundles)
MPW-1
3
100 (Router interface)
ASMi-54
2
8 (PCS)
OP-108C, OP-106C
2
2 (Internal Ethernet)
•
For CL modules:
• One bridge port exists on each GbE physical interface
• One bridge port exists on each virtually concatenated group, up to a
maximum of eight virtually concatenated groups per SDH/SONET
subsystem.
Each of these bridge ports can be connected to any other bridge port within the
Megaplex-4100, for example, to another bundle or Ethernet port on any module
(including GbE ports on CL modules), to a virtually concatenated group (VCG), etc.
³
To configure a Megaplex-4100 for providing Ethernet services:
1. After configuring the required physical ports, use Configuration>Logical Layer
to:
•
Configure the prescribed Ethernet bundles on I/O module ports, and on
PDH ports
•
Configure the prescribed virtually concatenated groups on SDH/SONET links
2. Use Configuration>Applications to configure Ethernet flows.
Figure 4-87 shows the detailed structure of the Applications menu.
4-102
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Applications
1. Ethernet Services
Flows
Ethernet Services
1. Flow
2. User Name
3. Flow Type
4. Bridge Port Mapping
1. Flows
Flow Type
1. E-LINE
2. E-LAN
Reserved
Bridge Port Mapping
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
Display List (U)
Add (A)
Bridge Port Mapping
Flow
Flow User Name
C-VLAN ID
SP-VLAN
Bridge Port Mapping
BP
1. C-VLAN Type
C-VLAN ID
2. SP-VLAN
3. Slot
Port
Rate
BP User Name
C-VLAN Type
1. Unaware
2. Aware
Figure 4-87. Typical Configuration>Applications Menu Structure
Configuring HDLC Bundles for Ethernet Services
For framed E1 and T1 ports (including PDH ports located on CL modules), you can
configure up to four HDLC bundles for each port, where each bundle can be
assigned the desired fraction (number of timeslots) of the port bandwidth.
Moreover, you can select specific timeslots to be assigned to each bundle. The
number of timeslots assigned to a bundle must always be even, which means
that the bundle bandwidth is a multiple of 128 kbps, up to a maximum of
1920 kbps (30 × 64 kbps) for E1 ports, or 1536 kbps (24 × 64 kbps) for T1 ports.
For unframed ports, the port bandwidth cannot be split among multiple bundles,
and therefore the whole port bandwidth must be assigned to only one bundle.
Note
This Megaplex-4100 version supports the unframed mode only for E1 ports.
The maximum number of bundles that can be defined on an eight-port I/O
module (M8E1, M8T1, M8SL) is 32, which is the maximum number of bundles that
may be configured when all the ports use a framed mode.
The CL modules do not include an Ethernet bundle termination function – only I/O
modules with Ethernet ports (M8E1, M8T1, M8SL) have this capability. Therefore,
when you plan to use Ethernet bundles on PDH ports, you must also select an I/O
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-103
Chapter 4 Configuration
Installation and Operation Manual
module on which to perform Ethernet bundle termination (all the Ethernet
bundles of a given PDH port must be terminated on the same I/O module). This
I/O module must fulfill the following requirements:
1. The additional bundle is counted within the total number of bundles processed
by the selected I/O module (maximum 32).
2. Sufficient bandwidth must be available on the PCM buses connecting to the
selected I/O module to carry the bundle timeslots.
3. Sufficient bandwidth must be available on the Fast Ethernet traffic bus
connecting the selected I/O module to the CL module to carry the Ethernet
traffic of the bundle.
³
To configure an HDLC bundle:
1. Open the Configuration>Logical Layer menu, and select Bundles.
Note
When you open the Bundles screen, it shows the parameters of the last
configured bundle. If you reach the screen after starting a new session, it shows
parameters for the first bundle that can be configured on the slot with the
lowest I/O number.
In both cases, you can sequentially scroll through all the existing bundles by
pressing the F or B key: first, this action will scroll the bundle numbers for the
current slot, and then will automatically move to the next slot, and scroll through
its bundles, and so on, cyclically.
2. Select Slot, and then press <Enter> to display the slot selection screen. The
slot selection screen displays only slots in which I/O modules that support
bundles are installed or programmed.
3. Select the desired slot, and then press <Enter> to return to the bundle
configuration screen. At this stage, you can either:
• Add a new bundle on the selected slot: type A (Add). The next free bundle
number is automatically assigned and appears in the Bundle field.
• Edit an existing bundle. The desired bundle number can be either typed
directly in the Bundle field, or can sequentially scroll through the Bundle
field by pressing the F or B key.
• Delete an existing bundle: first make sure to display the desired bundle
(check both the Slot and the Bundle fields), and then type D (Delete),
and confirm by pressing <Enter>.
4-104
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>Bundles
Rate(Kbps)[128 - 16384]
(128)
1. Slot
>
(IO-1 (M8E1))
2. Bundle[1 - 32]
... (1)
3. Admin Status
(Up)
4. User Name
... ()
5. L2 Protocol
>
(HDLC)
6. Number Of TS[2 - 32]
... (2)
7. Link OAM
(Enable)
8. Link OAM Mode
(Active)
9. Remote Terminal
(Disable)
10. Source Slot
>
(IO-1)
11. Source Port
>
(Link 1)
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B-Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. Bundle on I/O Module
MP-4100
Configuration>Logical Layer>Bundles
Rate(Kbps)[128 - 16384]
(128)
1. Slot
>
(IO-1 (M8E1))
2. Bundle[1 - 32]
... (2)
3. Admin Status
(Up)
4. User Name
... ()
5. L2 Protocol
>
(HDLC)
6. Number Of TS[2 - 32]
... (2)
7. Link OAM
(Enable)
8. Link OAM Mode
(Active)
9. Remote Terminal
(Disable)
10. Source Slot
>
(CL)
11. Source Port
>
(PDH 1 )
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B-Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. Bundle on PDH Port
Figure 4-88. Typical HDLC Bundle Configuration Screens
4. When you add a new bundle, or edit an existing one, you must also select the
Layer 2 protocol in the L2 Protocol field. For HDLC bundles, select HDLC and
the data form fields are immediately updated.
5. At this stage, select the HDLC bundle configuration parameters. The fields
displayed on the screen automatically adjust to the selected values.
Table 4-28 lists the available parameters for HDLC bundles.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-105
Chapter 4 Configuration
Installation and Operation Manual
Table 4-28. HDLC Bundle Parameters
Parameter
Function
Values
Slot
Selects the I/O slot number of the bundle
on which the bundle Ethernet traffic
termination is performed:
Selected on a screen that opens when the
Slot field is selected, or sequentially changed
by pressing the F or B key.
•
For a bundle using the local E1 or T1
ports for the transport of the Ethernet
bundle traffic, this is also the I/O slot
number of the bundle.
Both methods display only slots in which I/O
modules that support bundles are installed or
programmed.
•
When you are configuring a HDLC
bundle on a PDH port, this parameter
specifies the I/O module that
processes the bundle traffic
Bundle
Selects an existing bundle number, or
displays the automatically assigned
number for a new bundle
Admin Status
Used to enable/disable the bundle
Default: I/O-1
1 to 32.
Default: 1
DOWN – The bundle is disabled. This state
should be selected as long as the
configuration of the corresponding bundle
has not yet been completed, when you want
to prepare a bundle for future applications
that is not yet to become active, or when it is
necessary to stop the bundle traffic flow.
UP – The bundle is active and can support
traffic flow. However, traffic can flow only if
the Admin Status of the source port used by
the bundle is also UP.
Default: DOWN
User Name
Number of TS
Used to enter a logical name for the
selected bundle
Up to 25 alphanumeric characters.
Selects the number of timeslots assigned
to the bundle. This number determines
the bandwidth available to the bundle.
The allowed range depends on the source
port type and framing mode:
Default: Empty string
•
2, 4, 6, …, 30 for bundles defined on E1
ports using a framed mode (including PDH
ports). Do not select odd values (1, 3, …,
etc. ).
•
2, 4, 6, …, 24 for bundles defined on T1
ports using a framed mode. Do not select
odd values (1, 3, …, etc. ).
•
32 for bundles defined on UNFRAMED E1
ports (not relevant for PDH ports).
The number of timeslots must always be
even
Default: 2
4-106
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Rate
Displays the nominal bandwidth assigned
to the bundle.
The values applicable to HDLC bundles are as
follows:
The displayed value, which is a multiple of •
128 kbps, is automatically adjusted to the
previously selected parameters
•
•
128 to 1920 kbps when Number of TS is
in the range of 2 to 30.
128 to 1536 kbps when Number of TS is
in the range of 2 to 24.
2048 kbps when Number of TS is 32 (not
relevant for PDH ports).
Default: 128 kbps
L2 Protocol
Selects the bundle Layer 2 protocol
HDLC – HDLC protocol. The bundle can be
defined on framed or unframed ports, and its
maximum bandwidth is that of a single port.
MLPPP – MLPPP protocol. The bundle can be
defined only on unframed ports, and its
maximum bandwidth is a multiple of the port
bandwidth (2048 kbps for E1 ports). The
multiple is selected by the Number of Links
field. For configuration details, refer to the
Configuring MLPPP Bundles for Ethernet
Services section starting on page 4-108.
Default: HDLC
Link OAM
Link OAM Mode
Remote Terminal
Used to enable/disable the link OAM
functionality for the selected bundle.
DISABLE – Link OAM functionality is disabled.
The link OAM functionality covers the link
segment between the local bundle
endpoint (which in this case is the
internal framer serving the port circuits),
and the remote bundle endpoint
Default: DISABLE
Selects the link OAM mode at the local
endpoint of the bundle. Different modes
must be selected for each bundle
endpoint.
ACTIVE – The local endpoint of the bundle
initiates all the OAM PDU exchanges.
This field is displayed only when the
bundle Link OAM is ENABLE
Default: ACTIVE
Enables terminal access to a remote unit
that receives the bundle traffic.
DISABLE – The remote terminal functionality
is disabled.
This field is displayed only when the
bundle Link OAM is ENABLE
ENABLE – The remote terminal functionality is
enabled.
ENABLE – Link OAM functionality is enabled.
PASSIVE – The local endpoint of the bundle
only responds to the received OAM PDUs.
Default: DISABLE
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-107
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Source Slot
Selects the source slot for the bundle.
You can specify either an I/O module, or a CL
module.
When you are configuring a bundle on a
PDH port, select here the corresponding
CL module
If the source port is located on an I/O
module, the selected slot must be identical to
the value selected for the Slot field above.
Selected on a screen that opens when the
Slot field is selected
Source Port
Selects the source TDM port of the bundle The available range is as follows:
on the currently selected source slot.
• 1 to 8 for I/O modules
The source port cannot be included in a
• 1 to 63 for E1 PDH ports on SDH links
redundancy configuration
• 1 to 84 for T1 PDH ports on SONET links.
Selected on a screen that opens when a
Source Slot field is selected.
Default: 1
A HDLC bundle defined on an unframed E1 port is automatically assigned all the
port bandwidth (the equivalent of 32 timeslots). Management traffic can be
carried inband, as part of the Ethernet traffic, using the dedicated management
VLAN configured for the Megaplex-4100 host.
However, to complete the configuration of a HDLC bundle on a framed E1 or T1
port, it is necessary to specify the individual port timeslots that are served by the
bundle (this action is referred to as timeslot assignment). The source port of the
bundle is selected during bundle configuration.
Make sure to assign a number of timeslots equal to the number selected in the
Number of TS field.
Note
The total number of timeslots that can be assigned to HDLC bundles configured
on the same source port is 30 for E1 ports, and 24 for T1 ports, and this number
can be split as required between the various port users; for example, when only
one HDLC bundle is configured on the port, it can be assigned all the 30 or 24
timeslots.
Any given port timeslot can be assigned to only one use (a HDLC bundle, TDM
traffic, or to management). Timeslots assigned to bundles are always Data
timeslots.
For the supervision terminal, use Configuration>System>TS Assignment (see
Configuring Timeslot Assignment).
Configuring MLPPP Bundles for Ethernet Services
M8E1 and M8SL modules support one active MLPPP bundle per module, that is,
only one MLPPP bundle on an M8E1 or M8SL module can have its Admin Status as
Up. You may however configure additional MLPPP bundles on that module, as
long as their Admin Status is Down.
An MLPPP bundle can use 2 to 8 links, and all of them must be located on the
same module. All the links (ports) used by the MLPPP bundle must have identical
4-108
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
physical layer parameters, and their Line Type must be configured as Unframed.
Therefore, each bonded link adds 2048 kbps to the available bandwidth, for a
total of 4096 kbps for 2 links, and up to 16384 kbps for 8 links.
Management traffic can be carried inband, as part of the Ethernet traffic, using
the dedicated management VLAN configured for the Megaplex-4100 host (see
Management Flow Configuration Procedure section starting on page 4-133).
Note that links (ports) used by MLPPP bundles cannot be part of a redundancy
pair. On the other hand, some redundancy is inherent in the MLPPP protocol,
because if one of the bonded links is out-of-service, the result is only a reduction
in the available transmission bandwidth.
³
To configure an MLPPP bundle:
1. Open the Configuration>Logical Layer menu, and select Bundles.
2. Select a slot for the MLPPP bundle in the same way as for HDLC bundles (see
page 4-103). You can select only modules that support unframed ports, i.e.,
M8E1 or M8SL modules.
3. At this stage, you can either add a new MLPPP bundle on the selected slot, edit
or delete an existing bundle (see page 4-103). After you select a specific
bundle, or add a new one, the screen displays the complete bundle
configuration data form. This form has two pages, as shown in Figure 4-89.
4. When you add a new bundle, or edit an existing one, you must also select the
Layer 2 protocol in the L2 Protocol field. For MLPPP bundles, select MLPPP and
the data form fields are immediately updated.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
>
Rate(Kbps)[128 - 16384]
Slot
Bundle[1 - 32]
Admin Status
User Name
L2 Protocol
MLPPP MTU[80 - 1600]
Link OAM
Link OAM Mode
Remote Terminal
Number Of Links[1 - 8]
(N)
(4096)
>
(IO-1 (M8E1))
... (1)
(Down)
... ()
>
(MLPPP)
... (250)
>
(Enable)
>
(Active)
(Disable)
... (2)
#-Db Undo; A-Add; D-Delete; F-Fwd; B - Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-109
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
... (P)
11. Source Slot
12. Source Port
13. Source Port
>
>
>
(IO-1)
(Link 1)
(Link 2)
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B - Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 4-89. Typical MLPPP Bundle Configuration Screen
5. At this stage, select the MLPPP bundle configuration parameters. The fields
displayed on the screen automatically adjust to the selected values.
Table 4-29 lists the available parameters for MLPPP bundles.
Table 4-29. MLPPP Bundle Parameters
Parameter
Function
Values
Rate
Displays the nominal bandwidth assigned
to the bundle.
The range includes the multiples of 2048kbps
in the range of 2048 kbps (1 × 2048kbps) to
16384 kbps (8 × 2048 kbps), in accordance
with the Number of Links field.
The displayed value is automatically
adjusted
Default: 2048 kbps
Selects the I/O slot number for the bundle Selected on a screen that opens when the
Slot field is selected, or sequentially changed
(see Step 2 above)
by pressing the F or B key.
Slot
Both methods display only slots in which
modules that support bundles are installed or
programmed
Bundle
See Table 4-28
Admin Status
See Table 4-28
User Name
See Table 4-28
4-110
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
L2 Protocol
Selects the bundle Layer 2 protocol
HDLC – HDLC protocol. The bundle can be
defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1
port. See the Configuring HDLC Bundles for
Ethernet Services section starting on
page 4-103 for configuration details.
MLPPP – MLPPP protocol. The bundle can be
defined only on unframed ports, and its
maximum bandwidth is a multiple of
2048 kbps. The multiple is selected by the
Number of Links field.
Default: HDLC
MLPPP MTU
Selects the Ethernet maximum
transmission unit (MTU) for the MLPPP
bundle
Remote Terminal
See Table 4-28
Link OAM
See Table 4-28
Link OAM Mode
See Table 4-28
Number of Links
Selects the number of links (E1 ports)
used by the MLPPP bundle.
The supported range is 80 to 1600 bytes.
Default: 250
The available range is 1 to 8.
Default: 1
You should select at least two links
Source Port
Selects the bundle source ports.
The available range is LINK 1 to LINK 8.
Several Source Port fields are displayed:
the total number is determined by the
Number of Links field. All these ports
must have identical physical layer
parameters
The port is selected on a screen that opens
when a Source Slot field is selected.
Default: LINK 1
Configuring Virtual Concatenation Groups
Virtually concatenated groups can be configured on SDH/SONET links of
CL.1/155GbE modules. Refer to Appendix C for background information on virtual
concatenation.
To prepare Ethernet traffic for efficient transport over the SDH/SONET network,
the traffic is encapsulated using LAPS or GFP encapsulation, before being
transmitted over a virtually concatenated group. Megaplex-4100 also supports
the Link Capacity Adjustment Scheme (LCAS), covered by ITU-T Rec. G.7042.
Megaplex-4100 also supports 1+1 redundancy for virtually concatenated groups,
as described in Section 1.8. Refer to the Configuring Virtually Concatenated Group
Redundancy section starting on page 4-122 for instructions.
Selecting the Virtually Concatenated Groups to be Configured
You can perform virtually concatenated group configuration in two ways:
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-111
Chapter 4 Configuration
Installation and Operation Manual
•
Configure the parameters of a specific virtually concatenated group. After
configuring a virtually concatenated group, make sure to map its VCs/VTs
using Configuration>System>Mapping.
•
Configure all the currently-defined virtually concatenated groups with
similar parameters. You can change the parameters of each virtually
concatenated group as required.
The virtually concatenated group parameters depend on the link type (SDH or
SONET), and on the encapsulation method used on the group (or groups) being
configured: LAPS or GFP.
To navigate to the required screen, use Configuration>Logical Layer.
A full VCAT group selection screen is shown in Figure 4-90.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A
1.
2.
3.
4.
5.
6.
7.
8.
9.
VCG
VCG
VCG
VCG
VCG
VCG
VCG
VCG
All
1
2
3
4
5
6
7
8
VCG
>
>
>
>
>
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-90. Typical VCAT Virtually Concatenated Group Selection Screen
³
To select a specific virtually concatenated group to be configured:
1. On the Logical Layer class selection screen (Figure 4-73), select CL and then
press <Enter>.
2. On the CL Logical Layer screen, select VCAT and then press <Enter>.
3. You will see the CL module selection screen.
4. Select the desired CL module, and then press <Enter>. You will see the virtually
concatenated group selection screen (a typical screen is shown in Figure 4-90).
5. Type the corresponding virtually concatenated group number, 1 to 8, and then
press <Enter>.
³
To configure all the virtually concatenated groups with similar parameters (except
for Redundancy):
1. Perform Steps 1 to 4 above.
2. On the virtually concatenated group selection screen, select All VCG and then
press <Enter>.
4-112
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
To navigate to the required screen, use Configuration>Logical Layer>CL>VCAT>
CL-A or CL-B.
Using LAPS Encapsulation for Virtually Concatenated Groups on SDH
Links
A typical individual VCG screen for a Megaplex-4100 with SDH links that uses LAPS
encapsulation over VC-12 is shown in Figure 4-91. The selected group is
identified in the screen header.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
VC type
LCAS
Number of VCs [1 - 63]
Encapsulation
User Name
Redundancy
LVC Configuration
LAPS Configuration
(Up)
(VC12)
(No)
... (3)
>
(LAPS)
... ()
(None)
>
>
>
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-91. Typical VCG Configuration Screen for LAPS Encapsulation over VC-12 (SDH Links)
If you selected All VCGs on the VCAT screen, the header in Figure 4-91 is All VCGs.
The parameters that can be configured by means of the VCG screen are described
in Table 4-30. When a selection screen is used, the Values column in Table 4-30
also lists the options displayed on the selection screen.
³
To configure a virtually concatenated group using LAPS encapsulation:
1. Type the number corresponding to the desired parameter, and then press
<Enter>.
2. For LVC Configuration and LAPS Configuration, separate configuration screens
are used.
On the selection screen, type the number of the desired option and then
press <Enter>. The selection screen closes, and the new value appears in the
VCG screen.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-113
Chapter 4 Configuration
Installation and Operation Manual
Table 4-30. Configuration>Logical Layer>VCG Screen Parameters – LAPS Encapsulation over SDH
Parameter
Function
Values
Admin Status
Used to enable/disable the flow of traffic
through the selected virtually concatenated
group
DISABLE – The flow of traffic is disabled. This
state should be selected as long as the
configuration of the corresponding group has
not yet been completed, or when it is
necessary to stop traffic flow through the
group.
ENABLE – The flow of traffic is enabled.
Default: DISABLE
VC Type
LCAS
Selects the type of VC used to carry the
corresponding virtually concatenated group.
The available selections are VC-12, VC-3 and
VC-4.
This parameter is one of the parameters that
determine the bandwidth made available to
the virtually concatenated group
Default: VC-12
Used to enable/disable use of the Link
Capacity Adjustment Scheme (LCAS) on the
corresponding group.
NO – The use of LCAS is disabled.
LCAS is relevant only when the group includes
2 or more VCs, and therefore it is not
displayed when selecting VC-4 for the VC Type
Number of VCs Selects the number of VCs of the type
selected by VC Type used to carry the
corresponding virtually concatenated group.
This is another parameter that determines
the bandwidth made available to the virtually
concatenated group.
When you select the All VCGs option, take
into consideration that the number selected
by you is allocated to each active virtually
concatenated group. When selecting VC-4 for
VC Type, the number is always 1
Encapsulation
Selects the encapsulation standard used by
the virtually concatenated group
YES – The use of LCAS is enabled.
Default: NO
The available range for each type are as
follows:
•
For VC-12: 1 to 63
•
For VC-3: 1, 2 or 3. The number that can
be selected also depends on the mapping
of lower-order VCs assigned to other
groups: any groups using lower-order VCs
must be mapped in a way that leaves one
or two whole VC-3s free.
•
For VC-4: 1.
Default: 1
LAPS – Link Access Procedure for SONET/SDH
protocols per ITU-T Rec. X.85/X.86 draft.
GFP – Generic Framing Procedure in
accordance with ITU-T Rec. G.7041, framed
mode. See configuration instructions in the
Using GFP Encapsulation for Virtually
Concatenated Groups on SDH Links section
starting on page 4-120.
Default: GFP
4-114
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Parameter
Chapter 4 Configuration
Function
Values
Virtual
Used to enable/disable the use of the virtual
Concatenation concatenation format when the number of
VCs in the group is 1.
This parameter is displayed only when 1 is
selected in the Number of VCs field. This
parameter is not displayed when selecting
VC-4 for VC Type
NO – The use of the virtual concatenation
format is disabled.
YES – The use of the virtual concatenation
format is enabled. This selection is necessary
only for compatibility with equipment from
other vendors.
Default: YES
Minimum
Selects the minimum allowed number of
The allowed range is 1 to 63 for VC-12, and 1
Number of VCs operational VCs that must remain in
to 3 for VC-3.
operation. If the number decreases below the Make sure to select a number not exceeding
selected value, an alarm is generated.
the specified Number of VCs.
This parameter is displayed only when LCAS is Default: 1
enabled. This parameter is not displayed
when selecting VC-4 for VC Type
User Name
Redundancy
Used to enter a logical name for the selected
group
Up to 15 characters.
Controls the use of 1+1 redundancy for the
selected virtually concatenated group
NONE – No redundancy.
Default: Empty string
1+1 – 1+1 redundancy is enabled. See the
Configuring Virtually Concatenated Group
Redundancy section for details.
Default: NONE
LVC
Configuration
Used to configure the parameters of the LVC
used to transport the group payload. This
parameter is not displayed when selecting
VC-4 for VC Type
See procedure below
LAPS
Configuration
Used to configure the LAPS encapsulation
parameters
See Table 4-33
³
To configure the LVC parameters of a virtually concatenated group (or groups):
1. Select LVC Configuration. A typical LVC Configuration screen showing the
default values for groups using VC-12 is shown in Figure 4-92; Figure 4-93
shows the screen for groups using VC-3. The parameters that can be
configured by means of the LVC Configuration screen are described in the
following tables:
• For groups using VC-12: Table 4-31
• For groups using VC-3: Table 4-32.
2. Type the desired item number and then press <Enter>:
• For items 1, 3, 7, 8, the selection is toggled as soon as you press <Enter>.
• For items 2 and 6, you can type the desired value in the same line. When
done, press <Enter>.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-115
Chapter 4 Configuration
Installation and Operation Manual
• For the other items, you will see the corresponding selection screen. In this
case, the Values column in Table 4-31 or Table 4-32 lists the options
displayed on the selection screen.
On the selection screen, type the number of the desired option and then
press <Enter>. The selection screen closes and the new value appears in
the LVC Configuration screen.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>LVC Configuration
1.
2.
3.
4.
5.
6.
7.
8.
J2 Rx path trace
(Disable)
J2 path trace
... (www.rad.com)
Padding
(Nulls)
EED Threshold
>
(1E-3)
SD Threshold
>
(1E-6)
Extended Signal Label[0 - ff]... (0D)
RDI on payload label
(Disable)
RDI on path trace
(Disable)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-92. Typical LVC Configuration Screen for Virtually Concatenated Groups Using VC-12
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 3>LVC Configuration
1.
2.
3.
4.
5.
6.
7.
8.
J1 Rx path trace
(Disable)
J1 path trace
... (www.rad.com)
Padding
(Nulls)
EED Threshold
>
(1E-3)
SD Threshold
>
(1E-6)
Payload Label
[0 - ff]... (1B)
RDI on payload label
(Disable)
RDI on path trace
(Disable)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-93. Typical VC Configuration Screen for Virtually Concatenated Groups Using VC-3
4-116
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-31. Configuration>VCG>LVC Configuration Parameters for VC Type – VC-12
Parameter
Function
Values
J2 Rx Path Trace
Controls the checking of the received
path trace label by the corresponding
group
ENABLE – Path trace label is checked.
J2 Path Trace
DISABLE – Path trace label is not checked.
Default: DISABLE
Specifies the path trace label.
This parameter is relevant only when J2
Rx Path Trace is enabled
Alphanumeric string of 15 characters. If not all of
the 15 characters are needed for the prescribed
label, make sure to specify the appropriate
Padding method.
Default: www.rad.com
Padding
EED Threshold
SD Threshold
Payload label
Selects the type of characters used to
pad the path trace label, when it is
shorter than the required length of 15
characters
NULLS – NULL characters.
Selects the BER value, which if exceeded
results in the generation of the error
rate degradation alarm for the
corresponding group
The available selections are 1E-3 (BER threshold
of 10-3), 1E-4 (10-4), 1E-5 (10-5).
SPACES – Space characters.
Default: NULLS
Selects the BER value, which if exceeded
results in the generation of the
signal-degraded alarm for the
corresponding group
Default: 1E-3 (BER of 10-3)
The available selections are 1E-6 (BER threshold
of 10-6), 1E-7 (10-7), 1E-8 (10-8) or 1E-9 (10-9).
Default: 1E-6 (BER of 10-6)
Hexadecimal number in the range of 0 to FF (two
digits).
Specifies the expected payload label
(one byte)
Default: 0D for groups with a single VC-12
(Virtual Concatenation=YES)
05 for other (Virtual Concatenation=NO)
Extended Signal
Label
Selects the extended payload label,
which is part of the SDH overhead when
virtual concatenation is used.
Two hexadecimal digits, in the range of 00 to FF.
Default: 0D
The default value, 0D, is the standard
value used to indicate the use of virtual
concatenation and therefore should not
be changed unless specifically required.
This parameter is displayed only when
the value selected in the Number of VCs
field is different from 1; if the value is 1,
the parameter is displayed only when
the Virtual Concatenation field is YES
RDI on Payload
Label
Controls the sending of RDI indications
by the corresponding group, in case the
received payload label is different from
the expected payload label
ENABLE – RDI is sent when a payload label
mismatch is detected.
DISABLE – RDI is not sent when payload label
mismatch is detected. Nevertheless, RDI is still
sent in case of LOP (loss of pointer) condition.
Default: DISABLE
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-117
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
RDI on Path
Trace
Controls the sending of RDI indications
by the corresponding group, in case the
received path trace label (carried in SDH
overhead byte J2) is different from the
expected path trace label
ENABLE – RDI is sent in case a path trace
mismatch is detected.
DISABLE – RDI is not sent when a path trace
mismatch is detected. Nevertheless, RDI is still
sent in case a LOP (loss of pointer) condition is
detected.
Default: DISABLE
Table 4-32. Configuration>VCG>LVC Configuration Parameters for VC Type – VC-3
Parameter
Function
Values
J1 Rx Path Trace
Controls the checking of the received
path trace label by the corresponding
group
ENABLE – Path trace label is checked.
Specifies the path trace label
J1 Path Trace
DISABLE – Path trace label is not checked.
Default: DISABLE
Alphanumeric string of 15 characters. If not all of
the 15 characters are needed for the prescribed
label, make sure to specify the appropriate
Padding method.
Default: www.rad.com
Padding
See Table 4-31
EED Threshold
See Table 4-31
SD Threshold
See Table 4-31
Payload Label
See Table 4-31
Extended Signal
Label
See Table 4-31
RDI on Payload
Label
See Table 4-31
RDI on Path
Trace
Controls the sending of RDI indications
by the corresponding group, in case the
received path trace label (carried in SDH
overhead byte J1) is different from the
expected path trace label
Default: 1B
ENABLE – RDI is sent in case a path trace
mismatch is detected.
DISABLE – RDI is not sent when a path trace
mismatch is detected. Nevertheless, RDI is still
sent in case a LOP (loss of pointer) condition is
detected.
Default: DISABLE
³
To configure the LAPS parameters:
1. Select LAPS Configuration. A typical LAPS Configuration screen is shown in
Figure 4-94.
4-118
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>LAPS Configuration
1. Address [0 - ff]
... (00)
2. Control [0 - ff]
... (00)
3. SAPI value [0 - ffff]... (0030)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-94. Typical LAPS Configuration Screen
2. The parameters displayed on the LAPS Configuration screen are explained in
Table 4-33.
Note
Any changes to the default values should be carefully considered, to ensure
compatibility with other equipment.
Table 4-33. LAPS Configuration Parameters
Parameter
Function
Values
Address
Selects the HDLC address to be used by the
LAPS protocol for handshaking.
Two hexadecimal digits, in the range of 00
to FF.
The standardized HDLC address for Ethernet
encapsulated with LAPS is 4
Default: 00
Selects the HDLC control address to be used
by the LAPS protocol for handshaking.
Two hexadecimal digits, in the range of 00
to FF.
The standardized HDLC control value for
Ethernet encapsulated with LAPS is 3
Default: 00
Selects the service access point identifier
(SAPI) for the LAPS protocol.
Four hexadecimal digits, in the range of
0000 to FFFF.
The standardized SAPI for the Ethernet MAC
is FE01
Default: 0030
Control
SAPI Value
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-119
Chapter 4 Configuration
Installation and Operation Manual
Using GFP Encapsulation for Virtually Concatenated Groups on SDH
Links
A typical individual VCG screen for a Megaplex-4100 with SDH link that uses GFP
encapsulation is shown in Figure 4-95.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
VC type
LCAS
Number of VCs [1 - 63]
Encapsulation
User Name
Redundancy
LVC Configuration
GFP Configuration
(Up)
(VC12)
(No)
... (3)
>
(GFP)
... ()
(None)
>
>
>
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-95. Typical VCG Configuration Screen for GFP Encapsulation
The selected group is identified in the screen header. When you select All VCGs,
the header is All VCGs.
The parameters that can be configured by means of the VCG configuration screen
are the same as described in Table 4-30 for LAPS encapsulation, except that the
LAPS Configuration item is replaced by the GFP Configuration item, used to
configure the GFP encapsulation parameters.
³
To configure the GFP configuration parameters:
1. Select GFP Configuration. A typical GFP Configuration screen is shown in
Figure 4-96.
4-120
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>GFP Configuration
1.
2.
3.
4.
5.
6.
FCS
(Yes)
PTI For Client Data[0 - 8]
... (0)
UPI For Client Data[1 - 255] ... (1)
Delta
[1 - 7]
... (1)
Core Scrambling
>
(Both Side)
Payload Scrambling
>
(Both Side)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-96. Typical GFP Configuration Screen
2. The parameters displayed on the GFP Configuration screen are explained in
Table 4-34.
Note
Any changes to the default values should be carefully considered, to ensure
compatibility with other equipment.
Table 4-34. GFP Configuration Parameters
Parameter
Function
Values
FCS
Controls the use of error detection for
the payload
NO – Payload error detection disabled.
YES – Payload error detection enabled. In this case,
a frame checksum is calculated, using the 32-bit
polynomial recommended by ITU-T, and added to
the GFP frame structure.
Default: YES
PTI For Client
Data
Selects the payload type identifier (PTI)
inserted in GFP frames
The allowed range is 0 to 8.
Default: 0 (user data)
UPI For Client Selects the user payload identifier (PTI)
Data
inserted in GFP frames
The allowed range is 0 to 255.
Delta
The allowed range is 1 to 7.
Selects the number of error-free frame
headers that must be received before
frame synchronization is declared
Megaplex-4100 Ver. 2.0
Default: 1 (frame-mapped Ethernet)
Default: 1
Configuring Megaplex-4100 for Operation
4-121
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Core
Scrambling
Controls the use of frame core data
scrambling
BOTH SIDES – Core scrambling enabled for both the
transmit and receive directions.
ONLY TRANSMIT – Core scrambling performed only
on transmitted frames. No descrambling performed
on the received core data.
ONLY RECEIVE – Core descrambling performed on
the received core data. No scrambling for the core
data inserted in the transmitted frames.
DISABLED – Core scrambling disabled for both the
transmit and receive directions.
Default: BOTH SIDES
Payload
Scrambling
Controls the use of payload data
scrambling, before insertion in frames
BOTH SIDES – Payload scrambling enabled for both
the transmit and receive directions.
ONLY TRANSMIT – Payload scrambling performed
only on transmitted frames. No descrambling
performed on the received payload.
ONLY RECEIVE – Payload descrambling performed on
the received core data. No scrambling for the
payload inserted in the transmitted frames.
DISABLED – Payload scrambling disabled for both
the transmit and receive directions.
Default: BOTH SIDES
Configuring Virtually Concatenated Group Redundancy
This section provides instructions for configuring redundancy for pairs of virtually
concatenated groups. The same procedures can be used for any pair of virtually
concatenated groups, even if they use different concatenation parameters.
The following screens provide configuration examples for virtually concatenated
groups using GFP encapsulation over SDH links, however the same configuration
procedures are used for other combinations of parameters, and for SONET links.
³
Note
To configure virtually concatenated group redundancy:
When configuring the redundancy parameters, always start from the virtually
concatenated group that is to serve as the primary port of the pair.
If you must reconfigure the redundancy partners, it is recommended to first
select Redundancy = NONE for the current primary port, and then reconfigure all
the redundancy parameters.
1. On the virtually concatenated group selection screen (Figure 4-90), select the
virtually concatenated group that will serve as the primary port of the
redundancy pair.
2. On the virtually concatenated group configuration screen, select Redundancy,
and then select 1+1 to enable redundancy. The screen changes to display the
4-122
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
additional parameters related to redundancy, and a Primary (Yes) indicator
appears at the top of the screen.
3. Configure the primary virtually concatenated group redundancy parameters in
accordance with the information appearing in Table 4-35, in accordance with
the encapsulation method in use. A typical screen, with all the redundancyrelated parameters, comprising two pages, is shown in Figure 4-97.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
>
Primary
>
(Yes)
Admin Status
(Up)
VC type
>
(VC12)
LCAS
(Yes)
Number of VCs [1 - 63]
... (3)
Encapsulation
>
(GFP)
Minimum Number Of VCs[1 - 63]... (1)
User Name
... ()
Redundancy
(1+1)
Revertive
(Yes)
Wait To Restore[0 - 999]
... (300)
(N)
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
...
11.
12.
13.
14.
(P)
Redundancy Slot
Redundancy Port
LVC Configuration
GFP Configuration
>
>
>
>
(CL-A )
(VCG 3)
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 4-97. Typical Screen for the Primary Virtually Concatenated Group of a Redundancy Pair
(GFP Encapsulation)
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-123
Chapter 4 Configuration
Note
Installation and Operation Manual
The other port, which is specified in the Redundancy Slot and Redundancy
Channel fields of the primary port, is automatically configured with compatible
parameters, and only the remaining parameters can be configured manually.
4. At this stage, configure the remaining parameters of the other virtually
concatenated group (the secondary port of the redundancy pair). A typical
screen with all the redundancy-related parameters for the secondary virtually
concatenated group, comprising two pages, is shown in Figure 4-98.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 3
1.
2.
3.
4.
...
>
Admin Status
Redundancy
Primary
Revertive
Wait To Restore[0 - 999]
Redundancy Slot
Redundancy Port
VC type
LCAS
Number of VCs [1 - 63]
Encapsulation
(N)
(Up)
(1+1)
>
(No)
(Yes)
... (300)
>
(CL-A )
>
(VCG 1)
>
(VC12)
(No)
... (1)
>
(GFP)
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 3
...
5.
6.
7.
8.
(P)
User Name
Virtual Concatenation
LVC Configuration
GFP Configuration
... ()
(Yes)
>
>
>
#-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 4-98. Typical Screen for the Secondary Virtually Concatenated Group of a Redundancy Pair
(GFP Encapsulation)
4-124
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-35. Virtually Concatenated Group Redundancy Configuration Parameters
Parameter
Function
Values
Revertive
Selects the protection mode.
NO – Switching is non-revertive, that is, the
Megaplex-4100 will not flip back to the primary
VCG after the failed VCG returns to normal
operation, but only when the currently used VCG
fails.
This parameter is not displayed when
Redundancy is NONE
YES – Switching is revertive: the Megaplex-4100
will automatically return to the original VCG when
it returns to normal operation.
Default: NO
Wait to Restore
Specifies the time following the last
redundancy switching (flipping) during
which alarms are ignored.
The supported range is 0 to 999 seconds.
Default: 0
Therefore, Megaplex-4100 starts
evaluating the criteria for redundancy
switching (flipping) only after this
interval expires. This ensures that
another flipping cannot occur before the
specified interval expires.
This parameter is not displayed when
Redundancy is NONE
Redundancy Slot Selects the slot in which the other
module of a virtually concatenated
group redundancy pair is installed.
The selection must always be
symmetrical.
You can select either the same CL slot, or the
other CL slot (provided a CL module with
available virtually concatenated groups is
programmed in the other slot).
Default: Same CL slot
This parameter is not displayed when
Redundancy is NONE
Redundancy Port Selects the other VCG of a redundancy
pair.
The selection must always be
symmetrical.
This parameter is not displayed when
Redundancy is NONE
The available selections depend the virtually
concatenated groups available on the module
selected by means of the Redundancy Slot
parameter.
Default: – (None)
Configuring VCG Parameters for Virtually Concatenated Groups on
SONET Links
This section covers the virtually concatenated group configuration activities
available when the Megaplex-4100 uses the SONET links.
For operating instructions and configuration guidelines, see Using LAPS
Encapsulation for Virtually Concatenated Groups on SDH Links and Using GFP
Encapsulation for Virtually Concatenated Groups on SDH Links sections,
respectively, except for the differences listed below, which also depend on the
encapsulation method used on the group (or groups) being configured: LCAS or
GFP:
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-125
Chapter 4 Configuration
•
Installation and Operation Manual
A typical individual VCG screen for a Megaplex-4100 with SONET links that
uses GFP encapsulation over VT1.5 SPEs is shown in Figure 4-99. The
selected group is identified in the screen header.
The screen is similar to that of a Megaplex-4100 with SDH links, except for
the following differences:
• VC Type is replaced by VT Type, and the available selections are as follows:
…
STS1/SPE – STS-1 SPE
…
VT1.5 – VT1.5 virtual tributary. This is the default selection.
• Number of VCs: the available selections are as follows:
…
For STS-1 SPEs: 1, 2 or 3
…
For VT1.5: 1 to 64.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
(Up)
VC Type
>
(VT1.5)
LCAS
(Yes)
Number of VTs [1 - 64]
... (4)
Encapsulation
>
(GFP)
Minimum Number Of VCs[1 - 64]... (2)
User Name
... ()
LVC Configuration
>
GFP Configuration
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-99. Typical VCG Configuration Screen (GFP Encapsulation on SONET Link)
•
4-126
A typical individual VCG screen for a Megaplex-4100 with SONET links that
uses LAPS encapsulation is shown in Figure 4-100. The difference, relative
to the screen of Figure 4-99 is that the GFP Configuration item is replaced
by the LAPS Configuration item, used to configure the GFP encapsulation
parameters.
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
(Up)
VC type
>
(VT1.5)
LCAS
(Yes)
Number of VTs [1 - 64]
... (4)
Encapsulation
>
(LAPS)
Minimum Number Of VCs[1 - 64]... (2)
User Name
... ()
LVC Configuration
>
LAPS Configuration
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-100. Typical VCG Configuration Screen (LAPS Encapsulation on SONET Link)
Configuring Ethernet Flows
After performing the configuration activities listed above, you can configure the
Ethernet services flows.
Two types of flows can be configured:
•
Traffic flows
•
Management flows.
For background information, refer to the Megaplex-4100 Ethernet Services
section in Chapter 1.
Traffic Flow Configuration Guidelines
The maximum number of traffic flows that can be defined on a Megaplex-4100 is
250 (an additional flow, assigned the identifier 251, can be configured for
management only). The following configuration rules apply to flows and bridge
ports:
1. A bridge port can terminate either only traffic flows from local ports, or only
traffic flows from other modules.
2. A bridge port can terminate only one traffic flow classified as unaware (i.e.,
which does not discriminate Ethernet traffic in accordance with customer’s and
service provider’s VLANs).
3. When a bridge port is mapped to more than one traffic flow, the bridge port
can terminate several traffic flows with specific VLAN IDs, but only one traffic
flow classified as unaware.
4. A bridge port can terminate any number of traffic flows with specific VLAN IDs
(aware mode), up to the maximum supported per system.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-127
Chapter 4 Configuration
Installation and Operation Manual
5. An I/O module can be configured to support either E-line flows, or E-LAN flows,
but not both.
Note
The current Megaplex-4100 version does not support E-LAN flows.
6. It is not possible to configure flows between Ethernet ports on the same I/O
module.
7. For E-line flows, the following VLAN assignment rules apply:
•
The bridge ports terminating a flow must use the same VLAN mode (either
unaware or aware).
•
When using the aware mode, the same VLAN IDs must be configured at
both bridge ports. For example, this means that flows between two GbE
bridge ports must use the same SP-VLAN ID.
Traffic Flow Configuration Procedure
³
To add a new traffic flow:
1. On the Configuration>Applications menu, select Ethernet Services.
2. On the Ethernet Services screen, select Flows.
You will see the traffic flow configuration screen. A typical screen is shown in
Figure 4-101. If no flow is yet defined, it is always necessary to add a new
flow.
If traffic flows are already defined, the screen displays the first flow, and its
parameters. However, if you have already configured a flow in the current
management session, the screen displays the last configured flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (2)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete; F-Fwd; B-Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-101. Typical Traffic Flow Configuration Screen
3. Type A (Add) to add a new flow. The flow is automatically assigned the next
free index number. The maximum allowed is 250: to free up index numbers,
delete an unnecessary traffic flow entry, or edit an unused flow.
4-128
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 4 Configuration
If flows are already configured, you can also select an existing flow number to
modify or delete. You can select directly the flow number, or press F or B to scroll
among the existing flows.
4. Select the traffic flow type as E-LINE.
5. Assign a logical name to the traffic flow by selecting User Name: you can enter
up to 25 alphanumeric characters. When done, press <Enter>.
³
To map bridge ports to the traffic flow:
1. To map bridge ports to the selected flow (either a new one, or an existing flow
that is being modified), select Bridge Port Mapping in Figure 4-101.
2. The Bridge Port Mapping screen is displayed.
A typical screen is shown in Figure 4-102. If no bridge port has been mapped
to the selected flow, the screen is empty.
If the screen displays data for an already configured flow (see for example
Figure 4-105), you can change some of the flow parameters, for example,
C-VLAN Type, by bringing the cursor to the desired field: the available options
are then displayed under the list of the bridge ports.
Note
For E-Line flows, you must configure exactly two bridge ports.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
>
A-Add;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-102. Typical Bridge Port Mapping Screen for Traffic Flow (Before Configuration)
3. On the Bridge Port Mapping screen, type A (Add) to add a new bridge port.
4. You will see the bridge port mapping data form. A typical screen with the
default values is shown in Figure 4-103.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-129
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
BP[1 - 512]
1. C-VLAN Type
C-VLAN ID[1 - 4094]
2. SP-VLAN[0 - 4094]
3. Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(351)
(Unaware)
(0)
(0)
(CL-A)
(VCG 1)
(6.3Mbps)
()
>
#-Db Undo; F-Fwd; B-Bkwd; S-Save
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-103. Typical Bridge Port Mapping Data Form for Traffic Flow
5. Start by selecting an available bridge port, by pressing F or B: the Slot and Port
fields are automatically scrolled to display the available bridge ports.
•
The Slot field displays only slots of modules on which bridge ports are still
available.
•
The Port field displays the port type (link, Ethernet or GbE port, bundle, or
virtually concatenated group (VCG)), followed by its index number on the
selected slot. Bridge ports that are already not available are automatically
skipped as you configure flows, for example:
1. Any bridge port configured as VLAN-unaware in one flow cannot be
reused in another flow. A sanity error message will be generated if
you try including the same bridge port in another flow.
2. When a GbE port or VCG is included in a redundancy pair, only the
primary port or VCG can be selected (the secondary port/VCG cannot
be independently used, it only serves as standby for the primary
port/VCG traffic)
3. The maximum number of traffic flows allowed on a GbE port of a CL
module is 250, the same maximum as for the whole Megaplex-4100,
and therefore after reaching this number, no more flows can be
added.
Alternatively, select manually the desired Slot number, and scroll the bridge
ports available on the selected module.
6. Select the prescribed flow parameters, taking into consideration the
configuration guidelines presented on page 4-127. Table 4-36 lists the
available parameters. The fields displayed on the screen automatically adjust to
the selected values.
4-130
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Table 4-36. Traffic Flow Bridge Port Mapping Parameters
Parameter
Function
Values
BP
Displays the internal index number of
the bridge port being defined. The
port number is automatically assigned
by the Megaplex-4100 management
subsystem.
The available range is 1 to 512.
Default: 1
The index number indicates the
location and type of the bridge port
for the internal processor, and
therefore it changes when you make
changes to the Slot field
C-VLAN Type
Specifies the classification method for
customer’s edge traffic arriving at the
selected bridge port
The selection is made on a submenu with the
following options:
AWARE – Only frames with the VLAN ID selected
in the C-VLAN ID field are accepted by this
bridge port.
UNAWARE – All frames are accepted.
Default: UNAWARE
C-VLAN ID
Specifies the VLAN ID accepted when
the C-VLAN Type is AWARE.
The allowed range is 1 to 4094. The selected
VLAN ID must be unique per bridge port, but can
be reused on different bridge ports.
This field can be modified only when
C-VLAN Type is AWARE
0 means that no VLAN ID has been selected (this
is also the only value displayed when C-VLAN
Type is UNAWARE).
Default: 1
SP-VLAN
Specifies the service provider’s edge
VLAN ID for the traffic at the selected
bridge port
The allowed range is 1 to 4094. The selected
VLAN ID must be unique per Megaplex-4100 GbE
ports.
0 means that no VLAN ID has been selected but
you should not use this value.
Default: 0
Slot
Port
Selects the number of the slot on
which the selected bridge port is
defined
The allowed range is I/O 1 to I/O 10, CL-A and
CL-B.
Displays the port on which the
selected bridge port is defined
The allowed port types include Ethernet ports
(ETH or GbE), bundles (Bnd), and virtually
concatenated groups (VCG), as available on the
selected slot.
Only slots on which bridge ports are available for
connection to the selected flow are displayed
Only bridge port types available for connection
to the selected flow are displayed
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-131
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Rate
Displays the nominal bandwidth
assigned to the bridge port
The actual data rate is as configured for the
selected bridge port, for example:
BP User Name
Displays the logical name for the port
indicated by the Slot and Port fields
•
128 to 1920 kbps for an HDLC bundle on a
framed E1 port, 128 to 1536 kbps for an
HDLC bundle on a framed T1 port, and
2048 kbps for an HDLC bundle on an
unframed E1 port.
•
For an MLPPP bundle: multiples of 2048 kbps
in the range of 2048 kbps (1 × 2048 kbps) to
16384 kbps (8 × 2048 kbps)
•
100 Mbps for Ethernet (ETH) ports
•
1000 Mbps for GbE ports
•
Virtually concatenated groups can provide
any bandwidth from one VC-12 or VT1.5, up
to the whole SDH/SONET port bandwidth
(155 Mbps)
Up to 25 alphanumeric characters.
Default: Empty string
7. When you select a bridge port, you can check whether it is already included in
a flow, together with the flow details, by pressing U. Figure 4-104 displays a
typical bridge port information screen (the selected bridge port index number
appears in the header).
Press <ESC> to close the bridge port information form and return to the
bridge port configuration screen.
MP-4100
...tion>Applications>Ethernet Services>Flows>Bridge Port Mapping>
Flow
2
Flow User Name
C-VLAN ID
1
SP-VLAN
12
>
#-Db Undo
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-104. Typical Bridge Port Information Form for Traffic Flow
8. After ending the mapping of the first bridge port, press <ESC> to return to the
Bridge Port Mapping screen, which now displays the mapped bridge port.
9. Repeat the bridge port mapping process for the second bridge port of the
E-line flow being configured. Typical Bridge Port Mapping screens as seen after
configuration is ended, are shown in Figure 4-105.
4-132
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP C-VLAN Type
351 Aware
359 Aware
C-VLAN ID
1
1
SP-VLAN
12
12
Slot
CL-A
CL-A
Port
VCG 1
GbE 1
Rate
6.3Mbps
1Gbps
BP User Name
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical Traffic Flow between GbE Port and Virtually Concatenated Group
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
68
36
C-VLAN Type
Unaware
Unaware
C-VLAN ID
0
0
SP-VLAN
0
0
Slot
IO-2
IO-2
Port
ETH 1
Bnd 1
Rate
100Mbps
6144Kbps
BP User Name
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
B. Typical Traffic Flow between Ethernet Port and MLPPP Bundle
Figure 4-105. Typical Bridge Port Mapping Screen (After Traffic Flow Configuration)
Management Flow Configuration Procedure
Management traffic flowing through Ethernet connections is normally assigned a
dedicated VLAN. Within the Megaplex-4100, inband management traffic can reach
the management subsystem on the CL modules through Ethernet ports, through
virtually concatenated groups, or through bundles carrying Ethernet traffic
(including MLPPP bundles).
To control the flow of Ethernet inband management traffic within Megaplex-4100
and enable its distribution, through the Megaplex-4100 ports, to other
equipment, it is necessary to configure a dedicated management flow, which is
always assigned the flow identifier 251. In addition to selecting the bridge ports
connected to the management flow, when the same management traffic can be
received through more than one bridge port, it is also necessary to specify which
bridge ports may accept management traffic from network management stations
(such ports are referred to as host NMS sources). If management communication
through the currently selected port fails, another port is automatically selected.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-133
Chapter 4 Configuration
Installation and Operation Manual
When selecting host NMS source ports, make sure to plan ahead how to avoid
forming loops in the Ethernet communication topology.
Note
³
The traffic flow configuration rules listed in the Traffic Flow Configuration
Guidelines section on page 4-127 also apply to the management flow.
To configure the management flow:
1. On the Configuration>System>Management menu, select Flow.
You will see the management flow configuration screen. A typical screen, as
seen before a flow is configured, is shown in Figure 4-106. If no flow is yet
defined, it is always necessary to add this flow.
MP-4100
Configuration>System>Management>Flow
>
%-Db Update; #-Db Undo; $-Sanity; A-Add
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-106. New Management Flow Configuration Screen
2. Type A (Add) to add the new flow. The flow is automatically assigned the index
number 251.
MP-4100
Configuration>System>Management>Flow
1.
2.
3.
4.
Flow
>
User Name
...
VLAN ID[1 - 4094]
...
VLAN Priority Tag[0 - 7]...
Bridge Port Mapping
[]>
(251)
()
(1)
(0)
>
%-Db Update; #-Db Undo; $-Sanity; D-Delete
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-107. Typical Management Flow Configuration – Add Screen
4-134
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
3. Assign a logical name to the management flow by selecting User Name: you
can enter up to 25 alphanumeric characters. When done, press <Enter>.
4. Select VLAN ID, and specify the management VLAN number (in the range of 1
to 4094).
5. Select VLAN Priority Tag, and then specify the priority of the management
VLAN traffic, in the range of 1 to 7, where 1 is the lowest priority. For
wideband ports, you may increase the priority, however, in general you should
leave the default priority, 1, unchanged.
³
To map bridge ports to the management flow:
1. To map bridge ports to the selected management flow (either a new one, or an
existing flow that is being modified), select Bridge Port Mapping in Figure 4107.
2. The Bridge Port Mapping screen is displayed. A typical screen is shown in
Figure 4-108.
•
If no bridge port has been mapped to the selected flow, the screen is
empty.
•
If the flow already includes bridge ports, you can remove an existing bridge
port by bringing the cursor to the desired row and typing R (you cannot
change parameters for an existing bridge port, but can remove it from the
flow and then configure a new one as required).
MP-4100
Configuration>System>Management>Flow>Bridge Port Mapping-Flow251
BP
Host NMS Source
Slot
Port
Rate
BP User Name
>
A-Add;%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-108. Typical Bridge Port Mapping Screen for Management Flow (Before Configuration)
3. On the Bridge Port Mapping screen, type A (Add) to add a new bridge port.
4. You will see the bridge port mapping data form. A typical screen with the
default values is shown in Figure 4-103.
Table 4-37 lists the available parameters. The fields displayed on the screen
automatically adjust to the selected values.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-135
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Management>Flow>Bridge Port Mapping-Flow251
BP[1 - 512]
1. Host NMS Source
2. Slot
Port
Rate
BP User Name
...
>
>
>
>
...
(1)
(Yes)
(IO-1)
(Bnd 1)
(6144Kbps)
()
>
#-Db Undo; F-Fwd; B-Bkwd; S-Save
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-109. Typical Bridge Port Mapping Data Form for Management Flow
5. Start by selecting an available bridge port, by pressing F or B: the Slot and Port
fields are automatically scrolled to display the bridge ports available for
connection to the management flow.
•
The Slot field displays only slots of modules on which bridge ports are still
available.
•
The Port field displays the port type, and its index number on the selected
slot. The available port types are Ethernet ports and bundles (HDLC and
MLPPP) on I/O modules, GbE ports and virtually concatenated groups on CL
modules, Bridge ports that are already not available are automatically
skipped as you configure flows.
Alternatively, select manually the desired Slot number, and scroll the bridge
ports available on the selected module.
6. Select Host NMS Source, and select Yes if you want to allow reception of
management traffic from the NMS through this port.
Table 4-37. Management Flow Bridge Port Mapping Parameters
Parameter
Function
Values
BP
Displays the internal index number of
the bridge port being defined. The
port number is automatically assigned
by the Megaplex-4100 management
subsystem.
The available range is 1 to 512.
Default: 1
The index number indicates the
location and type of the bridge port
for the internal processor, and
therefore it changes when you make
changes to the Slot field
4-136
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Parameter
Function
Values
Host NMS Source
Specifies whether Megaplex-4100
management subsystem may access
management traffic from the NMS
through this port
NO – Megaplex-4100 management subsystem
will not accept management traffic from the
NMS through this port.
YES - Megaplex-4100 management subsystem
can accept management traffic from the NMS
through this port. However, the port that is
actually used to communicate with the NMS is
automatically by the management subsystem.
Default: NO
Slot
Port
Selects the number of the slot on
which the selected bridge port is
defined
The allowed range is I/O 1 to I/O 10, CL-A and
CL-B.
Displays the port on which the
selected bridge port is defined
The allowed port types include Ethernet ports
(ETH or GbE), bundles (Bnd), and virtually
concatenated groups (VCG), as available on the
selected slot.
Only slots on which bridge ports are available for
connection to the management flow are
displayed
Only bridge port types available for connection
to the management flow are displayed
Rate
BP User Name
Displays the nominal bandwidth
assigned to the bridge port
The actual data rate is as configured for the
selected bridge port, for example:
Displays the logical name for the port
indicated by the Slot and Port fields
•
128 to 1920 kbps for an HDLC bundle on a
framed E1 port, 128 to 1536 kbps for an
HDLC bundle on a framed T1 port, and
2048 kbps for an HDLC bundle on an
unframed E1 port.
•
For an MLPPP bundle: multiples of 2048 kbps
in the range of 2048 kbps (1 × 2048 kbps) to
16384 kbps (8 × 2048 kbps)
•
100 Mbps for Ethernet (ETH) ports
•
1000 Mbps for GbE ports
•
Virtually concatenated groups can provide
any bandwidth from one VC-12 or VT1.5, up
to the whole SDH/SONET port bandwidth
(155 Mbps)
Up to 25 alphanumeric characters.
Default: Empty string
7. After ending the mapping of the first bridge port, press <ESC> to return to the
Bridge Port Mapping screen, which now displays the mapped bridge port.
8. Repeat the bridge port mapping process for the other bridge ports to be
connected to the management flow. A typical Bridge Port Mapping screen, as
seen after configuration is ended, is shown in Figure 4-105.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-137
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Management>Flow>Bridge Port Mapping-Flow251
BP Host NMS Source
1
Yes
359
No
379
Yes
351
No
34
No
Slot
IO-1
CL-A
CL-B
CL-A
IO-1
Port
Bnd 1
GbE 1
GbE 1
VCG 1
ETH 2
Rate
6144Kbps
1Gbps
1Gbps
6.3Mbps
100Mbps
BP User Name
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-110. Typical Management Flow Bridge Port Mapping Screen (After Management Flow
Configuration)
Configuring APS for SDH/SONET Links
The APS function is used to select the protection mode for the network
STM-1/OC-3 connection. This option is relevant only for Megaplex-4100 with
CL.1/155 and CL.1/155GbE modules.
For details on the APS function, see the Redundancy Options section in
Chapter 1.
Currently, two options are supported:
•
No protection. In this case, each link operates independently.
•
1+1 uni-directional protection with automatic switching (Yes). In this mode,
one CL.1/155 or CL.1/155GbE link serves as backup for the working link.
APS is configured by selecting an APS (Automatic Protection Switching) group
that includes the appropriate CL.1/155 or CL.1/155GbE ports.
For a Megaplex-4100 with two CL.1/155 or CL.1/155GbE modules, there are four
APS group options, and two groups can be active at the same time, provided they
are defined on different pairs of ports.
The recovery mode (revertive or non-revertive), and the restoration time in the
revertive mode, can be selected in accordance with the application requirements.
Note
After adding an APS protection group without enabling the protection (Protection
is NO), the APS group operates in the forced mode, that is, the working port of
the APS group selected on the screen is forced to be the active port.
To navigate to the required screen, use Configuration>System>APS.
4-138
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Typical APS group configuration screens are shown in Figure 4-111 and
Figure 4-112. The configuration parameters appearing on these screens are
described in Table 4-38.
MP-4100
Configuration>System>APS
1.
2.
3.
4.
APS Group Id
Protection
Working Port
Flip Upon SD
>
>
(A1-A2)
(No)
(CL-A Link 1)
(No)
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-111. Typical APS Group Configuration Screen with Protection Disabled
MP-4100
Configuration>System>APS
1.
2.
3.
4.
5.
6.
7.
APS Group Id
Protection
Revertive
Working Port
Protection Port
WTR time(Sec)[1 - 720]
Flip Upon SD
>
(B1-B2)
(Yes)
(Yes)
>
(CL-B Link 1)
>
(CL-B Link 2)
... (60)
(No)
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-112. Typical APS Group Configuration Screen with Protection Enabled
Table 4-38. APS Configuration Parameters
Parameter
Function
Values
APS Group ID
Selects the CL links configured as an A1-A2 – Link 1 of CL A with link 2 of CL A.
APS group
B1-B2 – Link 1 of CL B with link 2 of CL B.
A1-B1 – Link 1 of CL A with link 1 of CL B.
A2-B2 – Link 2 of CL A with link 2 of CL B.
Default: A1-A2
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-139
Chapter 4 Configuration
Installation and Operation Manual
Parameter
Function
Values
Protection
Enables/disables the APS function
NO – The APS group operates in the forced mode.
YES – MSP 1+1 unidirectional protection with
automatic switching.
Default: YES
Revertive
Selects the protection mode
NO – Switching is non-revertive, that is, the
Megaplex-4100 will not flip back after the failed link
returns to normal operation, but only when the
currently used link fails.
YES – Switching is revertive: the Megaplex-4100 will
return to the original link when it returns to normal
operation.
Default: NO
Working Port
Selects the working link
Provides two selections, in accordance with the links
included in the configured APS group.
Default: the first link in the APS group designation
Protection Port
Selects the protection link
The only option is the other link included in the
configured APS group.
Default: the second link in the APS group designation
WTR Time
When protection switching is
The supported range is 1 to 720 seconds.
enabled and a link interface
Default: 60
becomes active, specifies the time
during which all the alarms reported
by the link will be ignored.
This field is displayed only when the
protection mode is Revertive=YES
Flip Upon SD
Controls switching to protection
when a signal-degraded (SD)
condition is detected
NO – Protection switching on SD condition is
disabled.
YES – Protection switching on SD condition is
enabled.
Default: NO
Configuring Timeslot Assignment
The following menus provide a central point of access for configuring the utilization
(assign timeslots) of E1 and T1 ports. This configures the internal routing (DS0
cross-connects) within the Megaplex-4100.
Any type of E1 or T1 port, either internal (virtual) or external, supports timeslot
assignment. For a Megaplex-4100 with CL.1/155 or CL.1/155GbE modules, it is also
possible to assign timeslots on internal (virtual) PDH ports, for transport over the
SDH or SONET network.
Timeslots can also be bypassed among E1 or T1 ports, including between E1 and T1
ports, and SDH or SONET PDH ports.
4-140
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 4 Configuration
While configuring a specific E1, T1, or PDH port, you can directly access the TS
Assignment facility for the port being configured directly from the
Configuration>Physical Port screen of the port, without going through the
Configuration>System menu.
When starting a timeslot assignment task, first you use a TS Assignment submenu
to select the type of port: module installed in an I/O slot, or CL module, and then
you select a specific port on a module of the corresponding type. Only active
ports using the DS0 cross-connect mode can be selected.
Timeslots can be assigned to TDM ports and channels, to inband management, and
to Ethernet bundles using the HDLC port.
For user ports that do not require a full timeslot (eight bits, equivalent to a
bandwidth of 64 kbps), Megaplex-4100 permits split timeslot assignment, that is,
assignment of individual bits in a selected timeslot. Split timeslot assignment
increases the utilization efficiency of link bandwidth for TDM modules or
channels, because it enables the allocation of link bandwidth in smaller units
(16 kbps, carried by pairs of consecutive bits).
Timeslot assignment is designed to minimize errors:
•
The various screens help you avoid assignment errors by presenting only
the relevant types of modules, ports and bundles, and ensuring that at
each stage only free timeslots can be assigned.
•
The final assignment is checked for consistency, for example:
•
It is checked that a given user port has indeed been assigned all the
timeslots (or bits in a split timeslot) needed to carry its payload, and that
all the timeslots are assigned on the same destination port.
•
When timeslots are bypassed between ports, it is checked that the
assignment is symmetrical.
To navigate to the required screen, use Configuration>System>TS Assignment.
³
To select a port:
1. Select TS Assignment on the System menu. A typical TS Assignment submenu is
shown in Figure 4-113.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-141
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>TS Assignment
1. IO >
2. CL >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-113. Typical TS Assignment Submenu
2. Select the type of modules, I/O or CL, and then press <Enter>. For I/O modules,
you will see the slot selection screen, whereas if you select CL you will proceed
directly to the PDH port selection screen (only one set of PDH ports, 63 or 84,
in accordance with the SDH/SONET link framing mode, is available for add/drop
traffic).
A typical screen for selecting an I/O module is shown in Figure 4-114. Only
I/O modules with E1 or T1 ports that are programmed in the chassis appear
on the screen.
MP-4100
Configuration>System>TS Assignment>IO
1.
2.
3.
4.
5.
I/O-2
I/O-3
I/O-4
I/O-5
I/O-6
(M8E1)>
(M8SL)>
(M8T1)>
(M8E1)>
(M8SL)>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-114. Typical IO Slot Selection Screen
3. Select a specific module, and then press <Enter> to continue to the port
selection screen. A typical screen for selecting ports on an I/O module is shown
in Figure 4-115; Figure 4-116 shows a typical CL port selection screen. Only
active ports (with Admin Status=UP) using a framed mode appear on the
screen.
4-142
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
For CL modules, the port selection screen (reached after selecting CL on the
submenu of Figure 4-113) displays the internal (virtual) PDH ports.
Note
The total number of ports depends on their framing: 63 when the CL module PDH
ports are configured as E1 ports, and 84 when configured as T1 ports. It is not
possible to mix E1 and T1 ports.
MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)
1.
2.
3.
4.
Link
Link
Link
Link
1>
5>
6>
8>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-115. Typical CL Port Selection Screen for I/O Module
MP-4100
Configuration>System>TS Assignment>CL
1.
2.
3.
4.
5.
PDH
PDH
PDH
PDH
PDH
1(Up)
2(Up)
5(Up)
12(Up)
21(Up)
>
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-116. Typical CL Port Selection Screen
4. Select a specific port, and then press <Enter> to continue to the timeslot
assignment task selection screen. A typical screen is shown in Figure 4-117.
Note
If you select an unframed port, you will see a No Map – Unframed Port message.
5. Select the desired task and then press <Enter> to display the corresponding
screen.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-143
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)>Link 1
1.
2.
3.
4.
5.
6.
Display Time Slots
Manual
Connect Time Slots
Delete TS (Per Slot and Port)
Delete TS (Number Of TS)
Split
[]
[]>
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-117. Typical Timeslot Assignment Task Selection Screen
The following tasks can be selected:
³
Display Time Slots
Display the current timeslot assignment for the selected
port.
Manual
Assign or deassign individual timeslots, and configure
timeslots for use with split timeslot assignment. This also
determines the handling of the payload carried by each
timeslot.
Connect Time Slots
Assign a group of consecutive timeslots on the selected port
(such a group is also called bundle, but this is not related to
Ethernet bundles).
Delete Time Slots
(Per Slot and Port)
Deassign all the timeslots on a selected port of a specified
module.
Delete Time Slots
(Number of TS)
Deassign a bundle of timeslots on the current port.
Split
Assign the individual bits in a timeslot configured to use split
assignments.
To display the current timeslot assignment for a selected port:
1. Select Display Time Slots and then press <Enter>. A typical screen is shown in
Figure 4-118.
4-144
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
...System>TS Assignment>IO >I/O-2 (M8E1)>Link 1>Display Time Slots
Ts#
1
01:IN01
2
01:IN02
3
SPLIT
4
------
5
MNG
6
------
7
------
8
------
Ts#
9
------
10
------
11
------
12
------
13
------
14
------
15
------
16
------
Ts#
17
------
18
------
19
------
20
------
21
------
22
------
23
------
24
------
Ts#
25
------
26
------
27
------
28
------
29
------
30
------
31
------
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-118. Typical Display Time Slots Screen
The screen displays a map of the port timeslots. For E1 ports, the map includes
31 timeslots; for T1 ports, the map includes 24 timeslots.
For each timeslot, you can see its current assignment:
³
––––
The timeslot is not assigned.
SS:PP
The timeslot is assigned to the port PP of the module installed in slot
SS.
MNG
The timeslot carries inband management traffic.
SPLIT
The timeslot is configured to use split assignment, and its utilization
can be seen by selecting it on the list opened by means of the Split
item on the timeslot assignment task selection screen.
UNI BRD V
The timeslot is unidirectionally broadcast to several ports, and is
handled as a voice channel (that is, with channel-associated
signaling).
UNI BRD D
The timeslot is unidirectionally broadcast to several ports, and is
handled as a data channel (that is, without channel-associated
signaling).
RESERVED
Timeslot reserved for future assignment. Assigning a RESERVED
timeslot has no effect on traffic.
To assign individual timeslots:
1. Select Manual on the timeslot assignment task selection screen. A typical
screen is shown in Figure 4-119.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-145
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)>Link 1>Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
Slot
IO-1 (HS-U12)
IO-1 (HS-U12)
Split
IO-1 (HS-U12)
---IO-2 (M8E1)
IO-2 (M8E1)
IO-2 (M8E1)
1. ---... (N)
>
Port
IN 1
IN 2
IN 34
---BND 2
BND 2
BND 2
2. Split
Ts
---------
Type
DATA
DATA
DATA
DATA
MNG
DATA
DATA
DATA
3. CL (CL1/155GbE)
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-119. Typical Manual Timeslot Assignment Screen
2. The screen displays a table with the following columns. The meaning of the
fields appearing in this table, and the method used to select the desired
values, are explained below:
Ts#
The number of the timeslot on the selected port. Each page contains
8 timeslots: to see the additional timeslots, scroll down to the
appropriate page (to see the various navigation options, select the
? (help) option).
The total number of timeslots is 31 for E1 ports, and 24 for T1 ports.
Slot
The destination slot, followed by the name of the module
programmed in the corresponding slot.
The destination slot is displayed in a list that appears under the table
when the selection block is within this column. The list includes only
the modules that can be selected as destinations.
You can also select Split, to configure the timeslot for split timeslot
assignment (see page 4-150).
If no slot has been selected, you will see – – – – . Note however that
no slot can be selected when the corresponding timeslot carries
inband management (that is, the timeslot Type is MNG).
Port
The destination port, within the selected Slot. The destination port is
displayed in a list that appears under the table when the selection
block is within this column. The list includes only the ports that can
be selected on the module installed in the destination slot, and any
HDLC Ethernet bundle configured on the selected slot.
If no slot or port has been selected, you will see ----. Note however
that no slot can be selected when the corresponding timeslot carries
inband management, nor for Split timeslots.
4-146
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
Ts
The destination timeslot on the destination port. This selection is
relevant only when bypassing timeslots between two E1 (or T1)
ports: for other selections, you cannot select a destination timeslot.
Type
Selects the type of traffic and the handling of its payload. The
selection is made on a list that appears under the table when the
selection block is within this column. The available types depend on
the destination port.
DATA
Data timeslot. This is the default timeslot type. It is
assumed that no signaling information is associated with
a channel carrying data.
DATA is the only allowed selection for bundles.
VOICE
Voice timeslot, that is, a timeslot with channel-associated
signaling information. This option is relevant only for E1
ports with G.704 multiframe (G.732S) framing and for T1
ports.
MNG
Timeslot dedicated to inband management. If the
selected port is configured for inband management, you
must select one timeslot as management timeslot; if the
port inband management is off, MNG is not available.
Note that only one timeslot of any port can be defined
as management timeslot. Therefore, you can reach MNG
only if all the previous fields have been left empty
(----), and no other timeslot of the current port has
been configured as MNG.
UNI BRD D Unidirectional broadcast timeslot carrying data.
UNI BRD V
Unidirectional broadcast timeslot carrying voice.
RESERVED
Reserved for future assignment.
3. To assign/deassign a timeslot, move the selection block to the desired Ts# row,
and then move it to each of the columns in this row to select the desired value
as explained in Step 2 above. Note the exceptions for Split and MNG values.
4. Repeat the process for each timeslot.
5. When done, select % to update the database. The timeslot assignment is
automatically checked for validity. If errors are detected, a detailed list of
errors is displayed by the Sanity function. The list identifies omissions, double
assignments and incorrect assignment, for example, channels which require
more timeslots. If the assignment is not correct, it is not possible to update
the database.
³
To assign a bundle of timeslots:
1. Select Connect Time Slots on the timeslot assignment selection screen. You will
see the bundle assignment screen for the selected port. A typical screen is
shown in Figure 4-120.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-147
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
...ration>System>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Connect Time Slots
1.
2.
3.
4.
5.
6.
7.
Start TS[1 - 31]
...
Slot
>
Port
>
Number of TS[1 - 31]...
Type
>
Destination Start TS...
Save Configuration
(5)
(CL (CL1/155GbE))
(PDH 1 )
(6)
(DATA)
(1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-120. Typical Connect Time Slots Screen
2. Select Start TS and specify the starting timeslot of the bundle on the selected
port. The range depends on the port type (maximum 31 for an E1 port, and
maximum 24 for a T1 port); you must also take into consideration the number
of timeslots to be connected to the destination port.
3. Select Slot: you will see a selection screen with the list of slots in which
modules that can accept a bundle of timeslots are programmed. When a
CL.1/155 or CL.1/155GbE module is installed, the list also includes the CL slot.
4. Select the desired module (the module type appears next to the chassis slot),
and then press <Enter>.
5. Select Port: you will see a selection screen with the list of ports on the module
programmed in the selected Slot. Select the desired port and then press
<Enter>.
6. Select Number of TS, enter the number of timeslots to be connected, and then
press <Enter>.
7. Select Type and then press <Enter>. You will see a selection screen for the
type of the timeslots in the bundle. Select the desired type and then press
<Enter>.
8. Select Destination Start TS and specify the position of the first timeslot of the
bundle in the destination port frame. Make sure to take into consideration the
number of timeslots to be connected to the destination port.
9. When done, you can either select Save Configuration and continue the timeslot
assignment tasks, or select $ to check timeslot assignment, and if OK – to save
and update the database.
Note
4-148
The Save Configuration option updates only the temporary timeslot assignment
tables, without performing any sanity check.
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 4 Configuration
To delete all the timeslots of a selected port:
1. Select Delete TS (Per Slot and Port) on the timeslot assignment task selection
screen. You will see the timeslot deassignment data form configuration screen
for the selected port. A typical screen is shown in Figure 4-121.
2. Select Slot: you will see a selection screen with the list of slots in which
modules that can accept a bundle of timeslots are programmed. When a
CL.1/155 or CL.1/155GbE module is installed, the list also includes the CL slot.
Select the desired module (the module type appears next to the chassis slot),
and then press <Enter>.
3. Select Port: you will see a selection screen with the list of ports on the module
programmed in the selected Slot. Select the desired port and then press
<Enter>.
MP-4100
..>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Delete TS (Per Slot and Port)
1. Slot
2. Port
3. Save Configuration
>
>
(IO-2 (M8E1))
(Link 2)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-121. Typical Delete TS (Per Slot and Port) Screen
4. When done, you must select Save Configuration and continue the timeslot
assignment tasks, and then select % to save and update the database.
³
To delete a bundle of timeslots on the selected port:
1. Select Delete TS (Number of TS) on the timeslot assignment task selection
screen. You will see the delete-bundle configuration screen for the selected
port. A typical screen is shown in Figure 4-122.
2. Select Start TS and specify the starting timeslot of the bundle on the selected
port. The range depends on the port type (maximum 31 for an E1 port, and
maximum 24 for a T1 port.
3. Select Number of TS, enter the number of timeslots to be connected, and then
press <Enter>.
4. When done, you must select Save Configuration and continue the timeslot
assignment tasks, and then select % to save and update the database.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-149
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
...stem>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Delete TS (Number Of TS)
1. Start TS[1 - 31]
2. Number of TS[1 - 31]
3. Save Configuration
... (1)
... (1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-122. Typical Delete TS (Number of TS) Screen
³
To perform split timeslot assignment:
1. Select Split on the timeslot assignment task selection screen. You will see a
screen that includes the list of timeslots reserved for split assignment: in this
example, the list includes only TS3. A typical screen is shown in Figure 4-123.
MP-4100
Configuration>System>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Split
1. TS 3>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------
Figure 4-123. Typical Split Timeslot Selection Screen
2. Select the desired timeslot and then press <Enter>. You will see the selection
screen on which you can select the user’s port to be connected to each bit. For
each port, you must configure the bits that will carry the payload of a user’s
port that needs split timeslot assignment.
You must select either 2, 4, or 8 consecutive bits, starting at bit 1, 3, 5, or 7,
in accordance with the following list:
Number of Bits
4-150
Allowed Starting Bit
2
1, 3, 5, 7
4
1, 5
8
1
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 4 Configuration
Do not mix bits from timeslots of different slots in the same link timeslot.
Figure 4-124 shows a typical screen after configuring the split timeslot
assignment.
MP-4100
Configuration>System>TS Assignment>IO>I/O-1 (M8E1)>Link 1>Split>TS 3
1.
2.
3.
4.
5.
6.
7.
8.
9.
Bit 1
...
Bit 2
...
Bit 3
...
Bit 4
...
Bit 5
...
Bit 6
...
Bit 7
...
Bit 8
...
Check Split Sanity
(01:IN03)
(01:IN03)
(------)
(------)
(------)
(------)
(------)
(------)
>
Insert IO Slot and Port in the next format: 2:1 or 2:IN1
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-124. Typical Split Assignment Screen
3. When done, select Check Split Sanity to check the assignment. Correct the
assignment as required, and then continue the timeslot assignment tasks, or
select % to save and update the database.
Configuring Payload Mapping to SDH/SONET Links
Use the following procedure to map the payload from the various Megaplex-4100
interfaces to specific TUs or SPEs, for transmission through the SDH/SONET
network link.
Mapping is relevant only for Megaplex-4100 equipped with CL.1/155 or
CL.1/155GbE modules.
The mapping functions include:
•
Mapping of internal PDH ports
•
Mapping of virtually concatenated groups (only for Megaplex-4100 with
CL.1/155GbE modules)
•
Mapping of protection ports for PDH ports and virtually concatenated
groups
•
Bypassing between links.
When APS is being configured, all the ports mapped to the protection link are
automatically disconnected, and all the ports mapped to the working link are
protected.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-151
Chapter 4 Configuration
Installation and Operation Manual
Path protection (see Configuring the LVC Parameters starting on page 4-92) is
always available, even on links included in an APS group: in this case, path
protection provides an additional protection layer at the lower level (the LVC
level).
The mapping screen has been especially designed to help you avoid errors:
Note
•
The screen displays the map of the TU/SPEs of the selected link, which
reflects the current mapping
•
The mapping is automatically adjusted for the operating network link
standard (SDH or SONET).
The following screens illustrate the mapping process for SDH links, however the
same procedures apply to SONET links.
•
The PDH ports that can be mapped/bypassed, and where applicable, the
virtually concatenated groups that have been configured, appear in a list
which is displayed under the map of the selected link.
The list also includes the None option, for unmapping a mapped/bypassed
port, and items for all the other links to which bypassing is possible
•
Only enabled ports (Admin Status = UP) appear in the list
•
The list automatically includes the PDH protection ports associated with
those PDH ports on which path protection has been enabled.
To navigate to the required screen, use Configuration>System>Mapping.
Figure 4-125 shows a typical Mapping selection screen for a Megaplex-4100 with
two CL modules.
MP-4100
Configuration>System>Mapping
1. CL-A
2. CL-B
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-125. Typical Mapping Selection Screen
Typical Mapping Procedure
³
To map the CL internal (virtual) ports:
1. Open the Configuration>System screen, and select Mapping.
4-152
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
2. On the Configuration> System>Mapping screen, select the desired CL module,
and then select the desired link on the CL screen.
3. On the Configuration>System>Mapping>CL>Link screen, select the mapping of
each internal (virtual) port, starting with PDH1: move the cursor to the desired
position on the map, and then select the number corresponding to the internal
port to be mapped. The mapping is identified by TUG-3:TUG-2:TU-12: in this
example, 1:1:1 means that PDH1 is mapped to TU-12 number 1, in TUG-2
number 1, in TUG-3 No. 1.
Figure 4-126.A shows an SDH mapping screen after selecting the PDH1
position, and Figure 4-126.B shows a SONET mapping screen (Figure 4-126.B
shows only the lefthand part of the screen is shown: to see the missing
columns, use the navigation keys explained after selecting ?-help).
When a TUG-3 is mapped as a whole, a dashed line appears around the area
occupied by the TUG-3, instead of the individual Tus/VTs.
MP-4100
Configuration>System>Mapping>CL-A>Link 1
TUG3-1
TUG3-2
TU1
TU2
TU3
TU1
TU2
TUG2-1 PDH1
None
None
None
None
TUG2-2 None
None
None
None
None
TUG2-3 None
None
None
None
None
TUG2-4 None
None
None
None
None
TUG2-5 None
None
None
None
None
TUG2-6 None
None
None
None
None
TUG2-7 None
None
None
None
None
1. PDH1
... (N)
>
2. PDH2
3. PDH3
4. PDH4
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. PDH5
TUG3-3
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
6. VCG1
1:1:1 -> PDH1
1:1:1
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
A. Mapping Display for Typical SDH Link
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-153
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Mapping>CL-A>Link 1
STS1-1
TU1
TU2
TU3
TU4
TU1
TUG2-1 PDH1
None
None
None
None
TUG2-2 None
None
None
None
None
TUG2-3 None
None
None
None
None
TUG2-4 None
None
None
None
None
TUG2-5 None
None
None
None
None
TUG2-6 None
None
None
None
None
TUG2-7 None
None
None
None
None
->>
1. PDH1
... (N)
>
2. PDH2
3. PDH3
4. PDH4
STS1-2
TU2
TU3
None
None
None
None
None
None
None
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
5. VCG1
TU1
None
None
None
None
None
None
None
6. VCG2
1:1:1 -> PDH1
1:1:1
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
B. Mapping Display for Typical SONET Link (Lefthand Area)
Figure 4-126. Typical Mapping Screens
4. Repeat the process until all the required ports are mapped. When done,
select % to save and update the database.
Using the Menu Mapping Mode
As an alternative to the map display mode, you can switch to the menu mode, by
typing m (refer to the ?-help screens of Figure 4-126). Figure 4-127 shows a
typical map mode display, and Figure 4-128 shows the corresponding menu mode
display when the cursor is located on the top lefthand corner of the map.
4-154
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>System>Mapping>CL-A>Link 1
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
TUG3-1
TU2
VCG1
None
None
None
None
None
None
TU1
VCG1
None
None
None
None
None
None
1. None
2. VCG1
3. VCG4
4. L1B-TU3
TU3
VCG1
None
None
None
None
None
None
TUG3-2
TU2
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. L2B-TU3
6. L1B-TU
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TUG3-3
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
7. L2B-TU
>
->VCG1
1:1:1
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-127. Typical Map Mode Display
MP-4100
Configuration>System>Mapping>CL-A>Link 1
1.
2.
3.
4.
5.
6.
7.
8.
9.
>
>
>
>
>
>
>
>
>
TUG3-1
TUG3-2
TUG3-3
(TUG2-1)
(VCG1)
(VCG1)
(VCG1)
(None)
(None)
(None)
(None)
(None)
(None)
>
#-Db Undo
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-128. Typical Menu Mode Display
³
To perform mapping using the menu mode:
1. Move the cursor to the desired TU, and then type its number to display the
available mapping selections. A typical mapping selections screen is shown in
Figure 4-129.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-155
Chapter 4 Configuration
MP-4100
Configuration>System>Mapping>CL-A>Link 1>
1.
2.
3.
4.
5.
6.
7.
Installation and Operation Manual
(VCG1)
None
VCG1
VCG4
L1B-TU3
L2B-TU3
L1B-TU
L2B-TU
>
Please select item <1 to 7>
#-Db Undo
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-129. Typical Mapping Selections Screen for Menu Mapping Mode
2. Type the number corresponding to the desired selection, and then press
<Enter>.
3. Repeat the process until all the required ports are mapped.
4. At any time, you can return to the map display (for example, Figure 4-127) by
pressing <ESC>.
Bypassing between Links
A bypass connection between two links has a bandwidth of one TUG-3 or STS-1.
Therefore, it is possible to bypass individual PDH ports, TUs or VTs, as well as a
whole TUG-3 or STS-1.
Bypassing is always made to the same position in the other link, for example,
TUG-3 No. 2 or STS-1 No. 2 of link A is always bypassed to TUG-3 No. 2/STS-1
No.2 of link B.
Any ports mapped to the bypassed TU/VT or TUG-3/STS-1 are automatically
unmapped on both links.
Figure 4-130 shows a typical mapping screen illustrating the bypassing procedure
on SDH links (for SONET links, TUs are replaced by VTs, for example, L1B-TU is
replaced by L1B-VT, and the total number of PDH ports is 84 instead of 63). The
bypassing selections (one for each of the other enabled links on the
Megaplex-4100) are always located at the end of the list; for clarity, the screen
shows an example in which no PDH port is enabled (all PDH ports have Admin
Status = DOWN).
4-156
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>System>Mapping>CL-A>Link 1
TUG3
1
TUG3
TU1
TU2
TU3
TU1
TU2
TUG2-1 None
None
None
None
None
TUG2-2 None
None
None
None
None
TUG2-3 None
None
None
None
None
TUG2-4 None
None
None
None
None
TUG2-5 None
None
None
None
None
TUG2-6 None
None
None
None
None
TUG2-7 None
None
None
None
None
1. None
2. L2A-TU3
3. L1B-TU3
4. L2B-TU3
5. L1B-TU
6. L2A-TU
2
TU3
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TUG3
TU2
None
None
None
None
None
None
None
3
TU3
None
None
None
None
None
None
None
7. L1B-TU
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-130. Typical Mapping Screen with Bypassing Options (SDH Links)
³
To bypass ports between links:
1. Move the cursor to the map position corresponding to the TU to be bypassed.
2. You will see the available bypassing options. For example, when nothing is yet
bypassed and all links are enabled, the bypassing options for CL A link 1 are
L1B-TU3 (map whole TUG-3 to the same TUG-3 on link 1 of the other CL), L1BTU, L2A-TU3 (map whole TUG-3 to the same TUG-3 on link 2 of the same CL),
L2A-TU, L2B-TU3, L2B-TU. Enabled PDH ports will also appear.
3. Type the number corresponding to the other link, and then press <Enter>.
Figure 4-131 shows an SDH mapping screen for link 1 of CL A, with the
selection cursor positioned on the TU-12 identified as 1:2:1, before entering
the Set command. The screen also displays additional bypass connections; for
example, note the bypass connection to L2B-TU3: when you open the
mapping display of link 2 of CL B, you will see L2A-TU3 for TUG-3 No. 2.
For SONET links, you will see a similar screen, except that the TUG3 are
replaced by STS, the maximum number of PDH ports is 84, and the total
number of TUs is 84 (3 columns of 28 TUs each).
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-157
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Mapping>CL-A >Link 1
TUG2-1
TUG2-2
TUG2-3
TUG2-4
TUG2-5
TUG2-6
TUG2-7
TUG3-1
TU2
PDH2
None
None
None
None
None
None
TU1
PDH1
L2A-TU
None
L2B-TU
None
None
None
1. None
2. PDH1
TUG3-2
TU3
PDH3
None
None
None
None
None
None
3. PDH2
4. PDH3
--|
|
|
|
|
---
5. L2A-TU3
6. L1B-TU3
----
--|
|
L2B-TU3
|
|
|
-----7. L2B-TU3
8. L1B-TU
TUG3-3
TU2
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
9. L2A-TU
10. L2B-TU
>
Bypass from L1-A-TU 1:2:1 to L2-A-TU 1:2:1
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-131. Typical Mapping Screen after Bypassing has been Configured (SDH Links)
4. The mapping selection list is replaced by the SET command. To confirm, press
<Enter>. The new mapping takes effect and the mapping display is updated.
³
To cancel bypassing between links:
1. Move the cursor to the label of the bypassed TUG-3/STS-1.
2. Select None.
3. The bypassed path is automatically unmapped.
Mapping Ports with Path Protection Enabled
Path protection is enabled at the level of the individual PDH port, by means of
the Configuration>Logical Layer>CL>PDH>LVC Configuration screen of the port(s)
to be protected.
³
To enable path protection for a PDH port:
1. On the LVC Configuration screen of the port to be protected, select Path
Protection for the port Protection Mode.
2. The last selection needed is the Mapping Mode:
•
4-158
Auto – this is the default selection, and it means that the protection port
is automatically mapped in the same position as the protected port, but on
the automatically selected protection link:
…
For Local CL: on the other link on the same CL module
…
For Adjacent CL: on the same link on the other CL module.
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
After confirming the selection, the corresponding P-PDH protection port
appears on the above-mentioned mapping screen. You can latter
manually change the mapping, even if its origin is automatic mapping.
•
Note
Manual – in this case, you map the protection port (P-PDH) manually, as
explained in the Typical Mapping Procedure section on page 4-152.
The Protection Partner field is not displayed when Mapping Mode is Manual.
3. A Protection Partner field appears, used to select the CL.1/155 or CL.1/155GbE
module on which the protection port will be located. When two CL.1/155 or
CL.1/155GbE modules are installed, you can select between Local CL and
Adjacent CL, otherwise the only selection is Local CL.
Note
At this stage, a protection port selection item is added to the selection list
appearing under the map of the appropriate protection link, as explained below.
The protection ports appear near the end of the selection list, just before the
bypassing selections.
For example, if the protected port is PDH3, the protection port is identified a PPDH3.
4. Repeat the process for each additional port to be protected.
To manually map a protection port, or change an automatic mapping, use the
basic mapping procedure, as explained in the Typical Mapping Procedure section
on page 4-152, for the P-PDH ports.
Configuring Fault Propagation
The fault propagation function can be used to notify equipment at a far end port
that a fault condition has been detected at a local port connected to it.
Fault propagation is supported for compatible types of ports:
•
Interconnected E1 ports (including internal E1 ports of M8SL modules)
•
Interconnected T1 ports
•
Between the TDM and Ethernet ends of a bundle, for example M8E1
modules support fault propagation for its Ethernet ports. MLPPP bundles
use the BCP Fail alarm to report fault conditions: in response to this alarm,
the corresponding port is closed to traffic.
Fault propagation cannot be enabled for ports with redundancy enabled.
³
To configure fault propagation:
1. On the Configuration>System menu, select Fault Propagation, and then press
<Enter>.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-159
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
Configuration>System>Fault Propagation
1. Fault Propagation
(Enable)
2. Interfaces
[]>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-132. Fault Propagation, Task Selection Screen
2. Select Fault Propagation to toggle the selection: to configure fault
propagation, select ENABLE.
3. Select Interfaces to display the interface configuration screen. A typical screen
is shown in Figure 4-133. If no interfaces has yet been mapped for fault
propagation, the screen is empty.
4. To add fault propagation between a new pair of interfaces, type A (Add) and
then press <Enter>.
You will see the Interface configuration data form. A typical screen is
shown in Figure 4-134.
5. Select the first endpoint, Slot A: you will see a submenu which lists the I/O
slots in which modules with ports that support fault propagation are installed,
or at least programmed.
6. After selecting the desired slot, select Port A: you will see a submenu which
lists the ports that can serve as one end of a fault propagation link.
7. After selecting the desired port, repeat the selections for the other endpoint
(Slot B and Port B).
4-160
Configuring Megaplex-4100 for Operation
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Configuration>System>Fault Propagation>Interfaces
Slot A
IO-1
Port A
ETH 1
Slot B
IO-5
Port B
ETH 2
Mode
BiDirectional(A<->B)
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-133. Typical Fault Propagation Interfaces Screen
MP-4100
Configuration>System>Fault Propagation>Interfaces
1.
2.
3.
4.
5.
Slot
Port
Slot
Port
Mode
A
A
B
B
>
>
>
>
>
(IO-1)
(ETH 1)
(IO-1)
(ETH2)
(UniDirectional(A->B))
>
#-Db Undo; S-Save
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-134. Typical Fault Propagation Interfaces, Interface Configuration Screen
8. After specifying the two endpoints, select the fault propagation direction by
means of the Mode field:
•
UniDirectional(A->B): fault conditions are reported only from endpoint A to
endpoint B.
•
BiDirectional(A<->B): fault conditions are reported in both directions.
9. After completing the configuration, the new set of endpoints appear on the
Interfaces screen.
10. Repeat the procedure for any additional endpoints.
Megaplex-4100 Ver. 2.0
Configuring Megaplex-4100 for Operation
4-161
Chapter 4 Configuration
4.4
Installation and Operation Manual
Additional Tasks
Setting the Internal Date & Time
Use the following procedure to update the time-of-day and date of the
Megaplex-4100 internal real-time clock, and select the date format displayed on
the Megaplex-4100 screens.
You can set time and date up to the end of 2099. The screen also displays the
current time and date provided by the Megaplex-4100 clock.
To navigate to the required screen, use Configuration>System>Date & Time.
A typical Date & Time screen is shown in Figure 4-135.
MP-4100
Configuration>System>Date & Time
1.
2.
3.
4.
Display Date & Time
Set Date Format
Set Date
Set Time
>
>
>
>
(DD-MM-YYYY)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-135. Typical Date & Time Screen
³
To display the current date and time:
1. Select Display Date & Time and then press <Enter>.
2. You will see the time and date retrieved from the Megaplex-4100 at the
instant the command has been received by the equipment.
³
To change the date format:
1. Select Set Date Format, and then press <Enter> to display the Set Date Format
selection screen.
2. On the Set Date Format selection screen, type the number corresponding to
the desired date format and then press <Enter>.
Note
³
DD stands for day, MM for month and YYYY for year.
To change the time:
1. Select Set Time, and then press <Enter>.
4-162
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
2. Each component of the time of day is separately set. To change, select the
desired item and then type the desired value.
Notes
• Time must be entered in the 24-hour format.
• It is recommended to set the time about one minute beyond the desired time,
and then press <Enter> at the correct instant.
3. Confirm each change by pressing <Enter>.
³
To change the date:
1. Select Set Date, and then press <Enter>.
2. Each component of the time of day is separately set. To change, select the
desired item and then type the desired value.
3. Confirm each change by pressing <Enter>.
Performing File Transfers to CL Modules
File Utilities Menu
The File Utilities menu enables using TFTP to perform the following operations:
•
Download software to the Megaplex-4100. This enables you to update the
Megaplex-4100 software when a new release becomes available, download
again the software in case the stored software has been corrupted,
download software to a new or repaired CL module, and download
software to I/O modules that support this capability.
In addition to the information appearing in this Section, you can find detailed
software downloading instructions in Appendix B.
•
Download a configuration parameters file to the Megaplex-4100.
•
Upload the configuration parameters file of the local Megaplex-4100.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-163
Chapter 4 Configuration
Installation and Operation Manual
Figure 4-136 shows the structure of the File Utilities menu.
File Utilities
1. S/W & File Transfer CL
2. S/W & File Transfer I/O & S-Subsystem
S/W & File Transfer CL
1. TFTP
TFTP
TFTP State
Command
1. File Name
2. Server IP
3. Command
S/W & File Transfer I/O &
S-Subsystem
1. TFTP
2. Download to Cards
3. Download Status
4. Dir
5. Delete File
1. SW Download
2. Config Download
3. Config Upload
4. No Command
TFTP
TFTP State
TFTP Error
1. File Name
2. Server IP
3. File #
4. S/W Download (To Flash)
File #
1. File-1
2. File-2
Download to Cards
Download Status
Dir
Delete File
Figure 4-136. Typical File Utilities Menu Structure
All the file transfer operations accessed from the File Utilities menu are
performed by means of the TFTP protocol. Appendix B explains what you need to
do to use TFTP.
Before Starting File Transfers
1. Obtain the list of software distribution files to be downloaded, and check that
the required distribution files are stored on the TFTP server.
2. Make sure that the TFTP server can communicate with the Megaplex-4100, for
example, by sending pings to the IP address assigned to the
Megaplex-4100 management entity (the host IP address).
File Transfers to CL Modules
File transfers to the CL modules are managed by means of the S/W & File
Transfer CL submenu. Valid software image files have the extension .img, and
configuration files have the extension .dat.
³
To select a file transfer task:
1. Open the File Utilities menu. A typical screen is shown in Figure 4-137.
4-164
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
File Utilities
1. S/W & File Transfer CL
>
2. S/W & File Transfer I/O & S-Subsystem >
>
File system and File transfer operations
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-137. Typical File Utilities Menu
2. Select S/W & File Transfer CL on the File Utilities menu. You will see the S/W &
File Transfer CL submenu. A typical screen is shown in Figure 4-138.
MP-4100
File Utilities>S/W & File Transfer CL
1. TFTP
>
>
File Transfer operations
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-138. Typical S/W & File Transfer CL Submenu
Updating the CL Management Software
The following procedure is separately performed on each CL module, starting with
the on-line module.
Note
³
The following procedure also updates the Ethernet subsystem software of
CL.1/GbE and CL.1/155GbE modules.
To start a TFTP transfer:
1. On the S/W & File Transfer CL screen, select TFTP to display the TFTP control
screen. Initially, the screen includes only the File Name and Server IP items.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-165
Chapter 4 Configuration
Installation and Operation Manual
2. On the TFTP control screen, select each of the items to define the parameters
needed to perform the TFTP transfer:
•
Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). When done, press
<Enter> to continue.
•
Select Server IP, and enter the IP address of the server that will download
the software distribution file. Enter the desired IP address in the dotted
quad format, and then <Enter> to continue.
•
After the previous two items are configured, a third item, Command,
appears, together with a TFTP State field that displays the state of the
TFTP operations. Initially, this field displays NoOp (no operation).
A typical screen is shown in Figure 4-139 as seen after Step 2 is
completed.
MP-4100
File Utilities>S/W & File Transfer CL>TFTP
TFTP State
1. File Name
2. Server IP
3. Command
>
(NoOp)
... (cx150.img)
... (172.17.65.12)
>
>
TFTP operations
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-139. Typical TFTP Control Screen (S/W & File Transfer CL)
•
4-166
Select Command to display the Command task selection screen (see typical
screen in Figure 4-140). The screen provides the following selections:
SW Download
Download a software distribution file from the specified
TFTP server to the Megaplex-4100.
Config Download
Download a configuration parameters file from the
specified TFTP server to the Megaplex-4100.
Config Upload
Upload the current configuration parameters file of the
Megaplex-4100 to the specified TFTP server.
No Command
Do not perform any operation.
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
File Utilities>S/W & File Transfer CL>TFTP>Command
1.
2.
3.
4.
SW Download
Config Download
Config Upload
No Command
>
Please select item <1 to 4>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-140. Typical TFTP Command Screen (S/W & File Transfer CL)
3. On the Command screen, select SW Download to start the software
downloading.
If no errors are detected, the downloading process starts, and its
progress is displayed in the TFTP State field. Errors (for example, a
protocol time-out) are reported in a separate TFTP Error field: if you see
an error message, check and correct the error cause, and then select
again the SW Download command.
4. After the transfer is successfully completed, the active CL module stores the
file in its flash memory. Now the Megaplex-4100 is automatically reset and the
new software is decompressed. After the resetting is successfully completed,
you will see the Megaplex-4100 log in screen again.
Note
If downloading failed, repeat the whole procedure.
5. Log in with the default parameters as follows:
•
In the User Name field, type the default user name, su, and then press
<Enter>
•
In the Password field, type the default, 1234, and then press <Enter>.
6. You will see the main menu screen. The Megaplex-4100 now uses the
downloaded software.
7. Repeat the transfer to download the same file to the other CL module. For this
purpose, first switch the other CL module on-line (use Config>System>Reset
Device to send a reset command to the on-line module).
Downloading a Configuration File
Configuration files are downloaded to the Megaplex-4100 flash memory.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-167
Chapter 4 Configuration
³
Installation and Operation Manual
To download a configuration file:
•
Perform Steps 1, 2, 3 of the Updating the CL Management Software
procedure (starting on page 4-165), but in Step 3 select Config Download.
After the transfer is successfully completed, the CL module stores the file
in its flash memory, replacing all the previously stored databases, and the
DB1 database automatically becomes the active one.
Note
If downloading failed, repeat the whole procedure.
Uploading a Configuration File
The contents of the Megaplex-4100 edit buffer can also be uploaded to the
management station as a standard disk file. The management station can then
distribute this file, as a configuration file, to other units which use similar
configuration. The configuration of each unit can then be customized as required.
³
To upload a configuration file:
Perform Steps 1, 2, 3 of the Updating the CL Management Software procedure
(starting on page 4-165), but in Step 3 select Config Upload.
File Transfers to I/O Modules and SDH/SONET Subsystems
In addition to the CL module software (which also includes the software
controlling the Ethernet traffic handling subsystem used by CL.1/GbE and
CL.1/155GbE modules), the current Megaplex-4100 version also enables
downloading software to I/O modules that support this feature (for example, to
the I/O modules with E1, T1, SHDSL, and Ethernet interfaces, M8E1, M8T1,
M8SL), and to the SDH/SONET traffic handling subsystem located on CL.1/155
and CL.1/155GbE modules. Each of these modules or subsystems can be
independently updated, using separate software image files.
The CL module flash memory includes two dedicated software storage areas
(identified as File 1 and File 2 on the supervision terminal screens), where each
area can store two independent image files, in accordance with user’s
requirements: for example, each area can hold a different version of I/O modules
software, or one area can be dedicated to I/O modules software, and the other
to SDH/SONET software. Moreover, the user can specify from which area to
download software to each module or subsystem.
Note
The contents of these storage areas are not checked for consistency between
the two CL modules.
File transfers to I/O modules and to the SDH/SONET subsystems are managed by
means of the S/W & File Transfer I/O & S-Subsystem submenu. This submenu is
used to download the required software image to a selected software storage
area of the CL modules, and then download the stored software image to each
I/O module or SDH/SONET subsystem. The required steps differ slightly, in
accordance with the type of software:
•
4-168
For SDH/SONET subsystems, you need to download the required software
image to a selected software storage area of the active CL module, and
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
then download the stored software image from the active CL module to
the SDH/SONET subsystem of the same CL module.
•
For I/O modules, a single CL module (the on-line module) can download
software to any number of I/O modules. Therefore, it is not mandatory to
download I/O modules software to both CL modules (but this is still a
recommended procedure). Moreover, the CL module can be configured to
download the software to the desired modules in one step (the
downloading itself is sequentially performed).
After the software is successfully downloaded to an SDH/SONET subsystem or I/O
module, that subsystem/module is automatically reset, and then starts using the
new software version. This process momentarily disrupts the traffic flowing
through the SDH/SONET subsystem or I/O module that is being updated (if the
updated component provides the Megaplex-4100 nodal timing reference, flipping
to another timing reference may also occur).
³
To download an I/O module or SDH/SONET software image to a CL module:
1. Open the File Utilities menu.
2. Select the S/W & File Transfer I/O and S-Subsystem option on the File Utilities
menu.
You will see the S/W & File Transfer I/O and S-Subsystem submenu. A
typical submenu is shown in Figure 4-141.
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem
1.
2.
3.
4.
5.
TFTP
Download To Cards
Download Status
Dir
Delete File
>
>
>
>
>
>
Please select item <1 to 5>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-141. Typical S/W & File Transfer I/O & S-Subsystem Submenu
3. On the S/W & File Transfer I/O and S-Subsystem submenu, select TFTP to
display the TFTP control screen (a typical screen is shown in Figure 4-142).
Initially, the screen includes only the File Name, Server IP, and File # items.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-169
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>TFTP
1.
2.
3.
4.
Tftp State
File Name
Server IP
File #
S/W Download (To Flash)
>
...
...
>
(NoOp)
(mlx150.img)
(172.171.55.75)
(File-1)
>
Please select item <1 to 4>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-142. Typical TFTP Control Screen (S/W & File Transfer I/O and S-Subsystem)
4. On the TFTP control screen, select each of the items to define the parameters
needed to perform the TFTP transfer:
•
Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). When done, press
<Enter> to continue.
•
Select Server IP, and enter the IP address of the server that will download
the software distribution file. Enter the desired IP address in the dotted
quad format, and then <Enter> to continue.
•
Select File # to open the storage area selection screen for the current CL
module. Select the desired storage area, File-1 or File-2, and then <Enter>
to continue.
•
After the previous items are configured, a fourth item, S/W Download (To
Flash), appears, together with a TFTP State field that displays the state of
the TFTP operations. Initially, this field displays NoOp (no operation).
5. On the TFTP control screen, select SW Download (To Flash), to start the
software downloading.
If no errors are detected, the downloading process starts, and its
progress is displayed in the TFTP State field. Errors (for example, a
protocol time-out) are reported in a separate TFTP Error field: if you see
an error message, check and correct the error cause, and then select
again SW Download (To Flash).
6. After the transfer is successfully completed, the active CL module stores the
file in the selected storage area of its flash memory.
Note
If downloading failed, repeat the whole procedure.
7. Repeat the transfer to download the same file to the other CL module. For this
purpose, first switch the other CL module on-line (use Config>System>Reset
Device to send a reset command to the on-line module).
4-170
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 4 Configuration
To load a software image to an I/O module or SDH/SONET subsystem:
1. On the File Utilities menu, select S/W & File Transfer I/O and S-Subsystem.
2. On the S/W & File Transfer I/O and S-Subsystem screen, select Download to
Cards to display the downloading target selection screen. A typical screen is
shown in Figure 4-143.
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Download To Cards
1. S-Subsystem CL-A
2. I/O-2
3. I/O-5
>
>
>
(Disable)
(Disable)
(Disable)
>
Please select item <1 to 3>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-143. Typical Download to Cards Screen
3. On the Download to Cards screen, select the desired target, and then press
<Enter> to open the source storage area selection screen.
4. The source storage area selection screen provides the following selections:
Disable
No software downloading to the corresponding target.
FIle-1
The software downloaded to the corresponding target is
taken from the File-1 storage area.
File-2
The software downloaded to the corresponding target is
taken from the File-2 storage area.
Select the storage area (File-1 or File-2) that stores the desired file, and then
press <Enter>.
Note
If you are not sure of the image file location, use Config>S/W & File Transfer I/O
& S-Subsystem>Dir (page 4-172) to find it.
5. Repeat Steps 3, 4 for each I/O module, as necessary, or continue to Step 6.
6. After Step 4, an additional item, SW Download, appears on the Download to
Cards screen. When ready to start the software downloading, select SW
Download.
If no errors are detected, the downloading process starts. You can select
Download Status on the S/W & File Transfer I/O and S-Subsystem screen
to display the progress (a typical screen, as seen after successfully
downloading the software, is shown in Figure 4-144). If you see an error
message, check and correct the error cause, and then select again the SW
Download command.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-171
Chapter 4 Configuration
Installation and Operation Manual
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Download Status
I/O-2
>
(Successful)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-144. Typical Download Status Screen
7. After the transfer is successfully completed, the SDH/SONET subsystem or I/O
module is automatically reset and the new software is decompressed. After
the resetting is successfully completed, the SDH/SONET subsystem or I/O
module is again ready to carry traffic.
Note
If downloading failed, repeat the whole procedure.
8. For SDH/SONET subsystems, it is necessary to repeat the procedure for the
other SDH/SONET subsystem.
Using the Dir Function
The Dir screen is used to display the flash memory contents of the on-line CL
module.
³
To display the flash memory directory:
1. On the File Utilities menu, select S/W & File Transfer I/O and S-Subsystem.
2. On the S/W & File Transfer I/O and S-Subsystem screen, select Dir to display
the list of files stored in the flash memory. A typical screen is shown in
Figure 4-145.
4-172
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Dir
... (File-1 mp4ms18e.img)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-145. Typical Dir Screen
Deleting Files
The Delete File screen is used to delete a file stored in the flash memory of the
on-line CL module.
To delete a file from the flash memory:
³
1. On the File Utilities menu, select S/W & File Transfer I/O and S-Subsystem.
2. On the S/W & File Transfer I/O and S-Subsystem screen, select Delete File to
display the file selection screen. A typical Delete File screen is shown in
Figure 4-146.
MP-4100
ile Utilities>S/W & File Transfer I/O & S-Subsystem>Delete File
1. File-1
>
Please select item <1 to 1>
#-Db Undo
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-146. Typical Delete File Screen
3. Select the file to be deleted (File-1 or File-2), and then press <Enter>.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-173
Chapter 4 Configuration
Installation and Operation Manual
Viewing Logistic (Inventory) Information
The Inventory menu is used to display logistic information on the Megaplex-4100
system, and its subsystems.
The information displayed by means of the Inventory menu is automatically
retrieved from the various system components and from the Megaplex-4100
configuration and software files. Therefore, it cannot be directly modified.
³
To display the Inventory menu:
Select Inventory on the main menu and then press <Enter>.
A typical Inventory menu is shown in Figure 4-147.
MP-4100
Inventory
1. System
[]>
2. SW/HW Rev[]>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-147. Typical Inventory Menu
The menu includes two items:
•
System: displays a list of the main components installed in the
Megaplex-4100 unit, and provides general logistic information.
•
SW/HW Rev: displays information on the modules installed in each chassis
slot, together with the software version and hardware revision. Also
presents the module programmed for each slot.
Displaying System Inventory Information
³
To display the System Inventory screen:
Select System on the Inventory menu.
The System screen includes several pages, where each page can be scrolled to
view additional fields, beyond those displayed as a default (the leftmost section
of the screen). A typical first page of the System screen is shown in Figure 4-148.
4-174
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
MP-4100
Inventory>System
|
v
Description
1 RAD.MP4100.PS-A.PS
2 RAD.MP4100.PS-B.------------3 RAD.MP4100.CL-A.CL1/155GbE
4 RAD.MP4100.CL-B.----------5 RAD.MP4100.IO-1.------------6 RAD.MP4100.IO-2.M8E1
7 RAD.MP4100.IO-3.M8T1
->>
SW Version
HW Revision
1.50B0/ 1.217
1. 0/ 0.0
1.51
1.UNDEF
1
1
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-148. Typical System Information Screens
The screen provides general logistics information for the main components of the
Megaplex-4100 system, starting with the chassis slots. Use the arrow keys to
scroll between screen pages (you can see additional navigation options by
selecting the ?-help option).
The main parameters appearing for each screen row are explained in Table 4-39.
In addition to these parameters, there are additional fields needed only by
management stations, or by support personnel. In particular, you can find, on the
rightmost screen, a Firmware field, which lists the firmware revision for the
corresponding component, when applicable.
Table 4-39. Main System Information Parameters
Parameter
Description
Description
Displays the formal name of the component. ----- appearing in this column indicates
that no item is installed in the corresponding position, or that no information is available
SW Version
Lists the software version for the corresponding component, when applicable (for
example, when a module is installed in the corresponding slot)
HW Revision
Lists the hardware revision for the corresponding component, when applicable (for
example, when a module is installed in the corresponding slot)
Displaying SW/HW Revision Information
³
To display the SW/HW Rev screen:
Select SW/HW Rev on the Inventory menu.
The SW/HW Rev screen includes two pages. A typical first page of the System
screen is shown in Figure 4-149.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-175
Chapter 4 Configuration
Installation and Operation Manual
The screen displays the software and hardware versions for each module
installed in the Megaplex-4100 system, and also the module programmed for
each position in the currently active database. You can use this information to
rapidly check for inconsistencies between the modules installed in the chassis,
and those programmed in the active database.
MP-4100
Inventory>SW/HW rev
Slot
PS-A
PS-B
| CL-A
v CL-B
IO-1
IO-2
IO-3
IO-4
IO-5
IO-6
IO-7
IO-8
Installed Card
PS
------------CL1/155GbE
----------------------M8E1
M8T1
------------M8SL
-------------------------------------
HW Revision
SW Version
1. 2/ 0.0
2.0B0/ 0.0
1
1
1.51
1.UNDEF
1
1.50
Programmed Card
PS
PS
CL1/155GbE
CL1/155GbE
M8E1
M8E1
M8T1
VC-16/E&M
M8SL
HS-12N
HS-U12
HS-S
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-149. Typical SW/HW Rev Screen
The information presented in Figure 4-149 displays logistics data that may be
needed by RAD technical support personnel when servicing the unit. The
information is retrieved from the modules installed in chassis.
Table 4-40. SW/HW Rev Information Parameters
Parameter
Description
Slot
Displays the chassis slot designation
Installed Card
Lists the module installed in the corresponding chassis slot.
----- in this column indicates that no module is installed in the corresponding slot
HW Revision
When a module is installed in the corresponding slot, lists its hardware revision
SW Version
When a module is installed in the corresponding slot, lists its software version
Programmed Card
Lists the module programmed in the currently active database for the corresponding
chassis slot
Reloading Factory Defaults
Use the following procedure to reload the factory default configuration, instead
of the user’s configuration, in the edit buffer.
4-176
Additional Tasks
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 4 Configuration
This action can be used to create a clean, known starting point, or delete the
existing configuration before starting configuring the Megaplex-4100 for
operation in a new application.
To avoid changing parameters that could cause loss of management
communication with the Megaplex-4100, the following parameters are not
modified:
•
IP addresses, and all the management parameters
•
Control port parameters
•
STM-1/OC-3 frame structure
•
Admin Status of the SDH/SONET link, if the DCC is used for management.
To navigate to the required screen, use Configuration>System>Factory Default.
³
To reload the factory default parameters:
1. Select Factory Default on the System menu.
2. You will see DB values will change to defaults. Are you sure?:
•
To abort, type n.
•
To confirm, type y.
3. If you confirmed, you must save the new configuration before it is actually
activated:
•
If you change your mind, undo by typing #.
•
To activate the default configuration, type % (the DB Update command). In
this case, You will see Are you sure you want to update active database –
Y/N? and therefore you must confirm again:
…
To abort, type n.
…
To confirm, type y.
4. At this stage, the Megaplex-4100 switches to the default parameters.
Note
Usually, you must press <Enter> before you see again the menu.
However, if the Megaplex-4100 did not use the default supervisory port
communication parameters, then before you can establish again communication
with the Megaplex-4100 you must change the supervisory terminal
communication parameters to the default values: 115.2 kbps, one start bit, eight
data bits, no parity, one stop bit and VT-100 terminal emulation.
Reset Device
Use the following procedure to reset the Megaplex-4100 (that is, reset all the
modules installed in the chassis, including the CL modules), or a specific I/O
module. Resetting does not affect the configuration data changed by the user,
not even if it has not yet saved.
To navigate to the required screen, use Configuration>System>Reset Device.
Megaplex-4100 Ver. 2.0
Additional Tasks
4-177
Chapter 4 Configuration
³
Installation and Operation Manual
To reset the Megaplex-4100:
1. Select Reset Device on the System menu.
2. Select CL-A or CL-B on the list (only the active CL module can be selected), and
then press <Enter>.
3. You will see The device will restart. Do you want to proceed – Y/N?:
•
To abort, type n.
•
To confirm, type y.
4. At this stage, the Megaplex-4100 is reset.
³
To reset an I/O module:
1. Select Reset Device on the System menu.
2. Select the desired I/O module on the list, and then press <Enter>. only
modules installed in the chassis can be reset.
3. You will see The device will restart. Do you want to proceed – Y/N?:
•
To abort, type n.
•
To confirm, type y.
4. At this stage, the corresponding I/O module is reset.
4-178
Additional Tasks
Megaplex-4100 Ver. 2.0
Chapter 5
Configuring Typical
Applications
5.1
Overview
This Chapter provides configuration guidelines for Megaplex-4100 systems in
typical applications.
To cover the wide range of possible applications, the Chapter presents two
examples, one for SDH environments and the other for SONET environments:
Note
•
Section 5.2 presents an application that enables transporting Ethernet traffic
over E1 links
•
Section 5.3 presents an application that enables transporting TDM and
Ethernet traffic over a SONET ring.
Unless otherwise specified, all the parameter values appearing in the following
screens are given for illustration purposes only, for the specific configuration
examples presented in this Chapter. They do not reflect recommended values for
other operating conditions.
The configuration activities presented in this Chapter assume that Megaplex-4100
is being configured using a standard ASCII terminal, and that you are familiar with
the Megaplex-4100 management, as described in Chapter 3. Detailed descriptions
and instructions for using each screen identified below appear in Chapter 4.
Note
In Appendix C, you can find concise descriptions of the Megaplex-4100 operating
environment, and technical background information on many Megaplex-4100
configuration parameters.
For your convenience, you can find below outlines of the preliminary
configuration sequence, and of the general configuration sequence
Outline of Preliminary Configuration Sequence
The purpose of the preliminary configuration is to prepare the minimal set of
parameters needed to manage the Megaplex-4100. In particular, after preliminary
configuration you will enable management access by Telnet hosts and
management stations, for example, RADview TDMoIP Service Center, that are
attached to a LAN directly connected to the Ethernet port of the Megaplex-4100
Megaplex-4100 Ver. 2.0
Overview
5-1
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
CONTROL module, or at a remote location from which IP communication with the
CONTROL module is possible.
After completing the preliminary configuration, you may also use Telnet hosts
and SNMP-based management stations to manage the Megaplex-4100.
Note
To enable management access to the Megaplex-4100 from any relevant location,
it is necessary to fully configure the Megaplex-4100: only full configuration can
permit management traffic to reach the Megaplex-4100 via inband paths.
The steps usually included in the preliminary configuration, when starting from
the factory defaults, are described in Table 5-1. For detailed operating
instructions, refer to the Chapter 4 section describing each activity.
Table 5-1. Megaplex-4100, Outline of Preliminary Configuration Procedure
Step
Action
Using …
1
Select the default database, 1
Configuration>DB Tools>Default DB
2
If the Megaplex-4100 is equipped with all the
modules, load the hardware configuration.
Configuration>DB Tools>Load HW
Alternatively, configure the modules and then
reload the factory-default parameters installed in Configuration>System>Card Type
the Megaplex-4100. You can also program
modules not yet installed in the chassis
3
Configure CONTROL DCE port parameters
Configuration>System>Control Port>Serial Port
4
Configure CONTROL ETH port parameters
Configuration>System>Control Port>ETH
5
Configure the Megaplex-4100 management agent Configuration>System>Management>Host IP
6
Configure Megaplex-4100 management access
Configuration>System>Management>Mng Access
7
Configure specific management stations
(optional)
Configuration>System>Management>Manager List
8
Set Megaplex-4100 real-time clock (optional)
Configuration>System>Date & Time
9
Save the configured information in the selected
database
Configuration>DB Tools>Update DB
General Configuration Sequence
Table 5-2 lists the additional steps needed to configure a Megaplex-4100 for
typical applications.
For detailed operating instructions, refer to the Chapter 4 section describing each
activity.
5-2
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
Table 5-2. Outline of Configuration Sequence for Typical Applications
Step
Action
1
Configure Megaplex-4100 signaling profiles
2
Configure the CL modules physical ports:
Using …
Configuration>System>Signaling Profile
•
SDH/SONET ports (make sure to configure
the frame structure)
Configuration>Physical Layer>CL>CL-A, CL-B>
SDH/SONET
•
GbE ports (make sure to configure the GbE
port redundancy parameters)
Configuration>Physical Layer>CL>CL-A, CL-B>
ETHERNET
•
Station clock ports
Configuration>Physical Layer>CL>CL-A, CL-B>Station
Clock
3
Configure the physical ports of the I/O modules
(E1, T1, SHDSL, Ethernet, etc.)
4
Configure the virtual ports on the SDH/SONET
ports of the CL modules:
Configuration>Physical Layer>I/O>I/O-1 to I/O-10
•
PDH ports
Configuration>Logical Layer>CL>PDH
•
High-order VCs
Configuration>Logical Layer>CL>HVC>CL-A, CL-B
5
Configure the virtual ports of the I/O modules
6
Prepare the Megaplex-4100 for SNMP
management:
1. Select the SNMP support mode
Configuration>Logical Layer>I/O>I/O-1 to I/O-10
Configuration > System > Management > SNMPv3
(enable/disable SNMPv3).
If SNMP support mode is changed, save to
activate the change before continuing.
2. When SNMPv3 is Disabled, configure SNMPv1
community names.
Configuration > System > Management > Host IP
3. When SNMPv3 is Enabled, configure
parameters in the following order:
– SNMP Engine ID
– SNMPv3 users
– SNMPv3 targets and notifications
– Configure SNMPv1/SNMPv3 mapping
7
Configuration > System > Management
Engine ID
Configuration > System > Management
Setting > Users
Configuration > System > Management
Setting > Targets & Notify
Configuration > System > Management
Setting > SNMPv1/v3 Mapping
> SNMP
> SNMPv3
> SNMPv3
> SNMPv3
Configure Ethernet services in the following
order:
•
Configure the prescribed bundles
on I/O module ports, and on PDH ports
Configuration>Logical Layer>Bundles
•
Configure the prescribed virtually
concatenated groups on SDH/SONET links,
and where necessary configure virtually
concatenated group redundancy
Configuration>Logical Layer>CL>VCAT>CL-A, CL-B
•
Configure the Ethernet flows
Configuration>Applications>Ethernet Services>Flows
Megaplex-4100 Ver. 2.0
Overview
5-3
Chapter 5 Configuring Typical Applications
Step
Action
Installation and Operation Manual
Using …
8
Configure the inband management flow
Configuration>System>Management>Flow
9
Configure path protection parameters for each
virtual and I/O module port
Configuration>Logical Layer>IO
10
Configure clock sources and timing flow
Configuration>System>Clock Source
11
Configure APS groups
Configuration>System>APS
12
Configure internal cross-connections (timeslot
assignment on framed ports)
Configuration>System>TS Assignment
13
Configure mapping to the SDH/SONET links
Configuration>System>Mapping
14
Configure fault propagation
Configuration>System>Fault Propagation
15
Configure Megaplex-4100 alarm handling
Configuration>System>Alarms Configuration
16
Save the final configuration as a database
Configuration>DB Tools>Update DB
17
If necessary, prepare additional databases
To start from an existing database, use
Configuration>DB Tools>Load DB. Repeat the
relevant steps as needed to create a new database
5-4
Overview
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
5.2
Chapter 5 Configuring Typical Applications
Configuration Procedure for Typical Ethernet
Transport Application
Overview
This section provides detailed configuration procedures for a typical
Megaplex-4100 application that enables transporting Ethernet traffic over TDM
infra-structure. The application topology is shown in Figure 5-1.
Location B
GbE
GbE
GbE
GbE
Location A
VLAN 1,2,3 to Location A
VLAN 7,8,9 to Location C
Megaplex-4100 B
20 E1
20 E1
VLAN 1,2,3 to Location B
VLAN 4,5,6 to Location C
Megaplex-4100 A
GbE
GbE
GbE
GbE
NMS
20 E1
VLAN 4,5,6 to Location A
VLAN 7,8,9 to Location B
Megaplex-4100 C
GbE
GbE
GbE
GbE
Location C
Figure 5-1. Network Topology for Configuration Example
In this application, the three Megaplex-4100 units are interconnected by
point-to-point links, each having a capacity of 20 E1 trunks, used to transport
Ethernet traffic over MLPPP bundles.
In addition to the E1 trunks, a protective ring topology is built by connecting the
Megaplex-4100 units to a packet-switched network, using the GbE ports of the CL
modules (the ring is represented by the dashed lines in Figure 5-1. For this
purpose, each group of 8 E1 streams is sent via one bridge port and the
corresponding flow is assigned one VLAN. The total number of bridge ports
needed for 20 E1 trunks is 3 (each bridge port supporting 8 E1, 8 E1 and 4 E1,
respectively). A total of 6 VLANs are therefore needed for each Megaplex-4100.
The routers bind the VLANs into a trunk. The routing protocol provides load
sharing for the traffic, which in effect provides ring functionality.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-5
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Network management is performed by an SNMP-based network management
station, for example, RADview NMS PC, using an out-of-band connection via a
serial or Ethernet port.
Configuration Sequence
For each of the 3 sites (Location A, Location B, Location C, in that order), the
configuration sequence is as follows:
1. Preliminary configuration.
2. Configuring the clock sources.
3. Configuring the physical ports.
4. Adding bundles.
5. Interconnecting bundles to form flows.
6. Connecting the bundles to their E1 ports.
Preliminary Configuration (All Sites)
1. Connect a terminal to the CONTROL DCE connector of the active CL module.
Make sure to use VT-100 supervision terminal emulation.
2. Configure the supervision terminal for communication with the
Megaplex-4100. Megaplex-4100 default configuration is as follows:
115.2 kbps, one start bit, eight data bits, no parity, one stop bit. Select
full-duplex mode, echo off, and disable flow control.
3. If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for a few seconds,
and then press <Enter> several times.
4. Type the default user name (su) and password (1234).
MP-4100
USER NAME:
PASSWORD:
su
****
5. Set the factory default parameters for the Megaplex-4100, using
Configuration>System>Factory Default.
6. Press Y to confirm.
7. Set the time and date, using Configuration>System>Date & Time.
8. Load the hardware configuration (the installed modules), using
Configuration>DB Tools>Load HW, and then press Y to confirm.
9. To save and activate the new configuration, press the % key, and then press
Y to confirm.
Configuration File Update Is In Process will appear at the bottom of the
screen while the database is being saved (a few seconds).
10. Check the modules installed in the Megaplex-4100 chassis, using
Inventory>SW/HW Rev.
5-6
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Inventory>SW/HW Rev
Slot
PS-A
PS-B
| CL-A
v CL-B
IO-1
IO-2
IO-3
IO-4
IO-5
IO-6
IO-7
IO-8
Installed Card
PS
PS
CL1/155GbE
CL1/155GbE
M8E1
M8E1
M8E1
M8E1
M8E1
M8E1
-------------------------
HW Revision
SW Version
0. 2/ 0.1
0. 2/ 0.1
1
1
1
1
1
1
1.50B2/ 1.13
1.50B2/ 1.13
1.54
1.54
1.54
1.54
1.54
1.54
Programmed Card
PS
PS
CL1/155GbE
CL1/155GbE
M8E1
M8E1
M8E1
M8E1
M8E1
M8E1
-------------------------
11. Configure the Megaplex-4100 management IP address and other IP
communication parameters, using Configuration>Quick Setup.
MP-4100
Configuration>Quick Setup
1. Host IP Address... (172.17.191.100)
2. Subnet Mask
... (255.255.255.0)
3. Default Gateway... (172.17.191.153)
12. Configure the Megaplex-4100 IP agent name, using Configuration>System>
Management>Device Info.
MP-4100
Configuration>System>Management>Device Info
Sys Description...
Object ID
...
1. Device Name
...
2. Contact Person ...
3. Location ID
...
(Sys type:MP-4100 Sys Ver:1.50A0 Chassis Revision:0)
(radMP4100)
(MP4100)
(Name of contact person
)
(The location of this device
)
Configuring the Primary Site (Location A)
Configuring the Clock Sources
1. Configure the system clock source of Megaplex-4100 A to Internal, using
Configuration>System>Clock Source.
As a result, Megaplex-4100 A serves as the timing reference for the
whole E1 network.
MP-4100
Configuration>System>Clock Source
1. Source
Megaplex-4100 Ver. 2.0
>
(Internal)
Configuration Procedure for Typical Ethernet Transport Application
5-7
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring the Physical Layer
1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>CL>
CL-A>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>CL>
CL-B>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-B>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration>Physical
Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
4. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
5. Repeat the same configuration steps for I/O slots 2, 4 and 5.
6. Activate the first 4 E1 ports on I/O slots 3 and 6, starting with link 1. Use
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1.
5-8
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-3 (M8E1))
(-)
(Balance)
7. Repeat Step 6 for links 2 to 4.
8. Repeat the same procedure (Steps 5, 7) for I/O slot 6.
Configuring Bundles
1. Add an MLPPP bundle with eight E1 links to I/O slot 1:
1. Open Configuration>Logical Layer>Bundles.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-1)
... (1)
2. Type a to add a bundle to the M8E1 module in I/O slot 1.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-1)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-1)
(Link 1)
3. Type N to display next page, which displays the other source ports.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-9
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
...
11.
12.
13.
14.
15.
16.
17.
(P)
Source
Source
Source
Source
Source
Source
Source
Port
Port
Port
Port
Port
Port
Port
>
>
>
>
>
>
>
(Link
(Link
(Link
(Link
(Link
(Link
(Link
2)
3)
4)
5)
6)
7)
8)
2. Add an MLPPP bundle with eight E1 links to I/O slot 2 (type P for previous
page):
1. Select Slot>IO-2.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-2)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 2.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-2)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-2)
(Link 1)
3. Add an MLPPP bundle with eight E1 links to I/O slot 3:
1. Select Slot>IO-3.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-3)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 3.
5-10
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-3)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-3)
(Link 1)
4. Add an MLPPP bundle with eight E1 links to I/O slot 4:
1. Select Slot>IO-4.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-4)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 4.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-4)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-4)
(Link 1)
5. Add an MLPPP bundle with eight E1 links to I/O slot 5:
1. Select Slot>IO-5.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-5)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 5.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-11
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-5)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-5)
(Link 1)
6. Add an MLPPP bundle with eight E1 links to I/O slot 6:
1. Select Slot>IO-6.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-6)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 6.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-6)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-6)
(Link 1)
Interconnecting Bundles to Form Flows
1. Connect BND1 on I/O slot 1 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250]
... (1)
2. Type a to add a flow.
5-12
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(1)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Use F to scroll among the available ports.
6. Type S to save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(1)
(Aware)
(1)
(0)
(IO-1)
(Bnd 1)
(16384Kbps)
()
8. Type S to save and then type <ESC>.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-13
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP C-VLAN Type
359 Aware
1
Aware
C-VLAN ID
1
1
SP-VLAN
0
0
Slot Port Rate
BP User Name
CL-A
GbE 1 1Gbps
IO-1
Bnd 1 16384Kbps
1. Unaware
2. Aware
9. Type <ESC>.
2. Connect BND1 on I/O slot 2 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
2. Type a to add a flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (2)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
5-14
...
>
...
...
>
>
>
...
(359)
(Aware)
(2)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(36)
(Aware)
(2)
(0)
(IO-2)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
3. Connect BND1 on I/O slot 3 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(3)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(71)
(Aware)
(3)
(0)
(IO-3)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice.
4. Connect BND1 on I/O slot 4 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-15
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(4)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(4)
(0)
(IO-4)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
5. Connect BND1 on I/O slot 5 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(5)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
5-16
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(5)
(0)
(IO-5)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
6. Connect BND2 on I/O slot 6 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(6)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(142)
(Aware)
(6)
(0)
(IO-5)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice.
Connecting Bundle to the E1 Ports
1. Connect the E1 ports of the modules in slots I/O 1 to I/O 4 to the bundles
configured above:
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-17
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
1. Open Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links>Destination Port (-)
1.
2.
3.
4.
5.
6.
7.
8.
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
3. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
2. Repeat the procedure for I/O slots 2, 4 and 5.
3. Connect the E1 ports 1 to 4 on I/O slot 5 to BND1:
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Up).
MP-4100
Configuration>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-5 (M8E1))
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
5-18
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...on>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)>Destination Port (-)
1.
2.
3.
4.
5.
6.
7.
8.
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
4. Repeat the same procedure for I/O slot 6.
5. To save and activate the new configuration, press %.
6. Press Y to confirm. Configuration File Update Is In Process will appear at the
bottom of the screen for the time the database is being saved (a few
seconds).
Configuring Equipment at Location B
Configuring the Clock Source
1. Configure the system clock source to use the recovered clock signal of E1
link 1 of the M8E1 in I/O slot 1, using Configuration>System>Clock
Source>Source>Rx Clock>Master Port.
MP-4100
Configuration>System>Clock Source>Master Port
Entry Num Slot
1
IO-1 (M8E1)
2
None
| 3
None
v 4
None
5
None
6
None
7
None
Port
Link 1
-
2. Type <ESC> for previous screen, and then select Fallback Port to configure
the fallback clock source to use the recovered clock signal of E1 link 1 of the
M8E1 in I/O slot 6.
MP-4100
Configuration>System>Clock Source>Fallback Port
Entry Num Slot
1
IO-6 (M8E1)
2
None
| 3
None
v 4
None
5
None
6
None
7
None
Megaplex-4100 Ver. 2.0
Port
Link 1
-
Configuration Procedure for Typical Ethernet Transport Application
5-19
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring the Physical Layer
1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>
CL>CL-A>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>
CL>CL-B>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-B>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration> Physical
Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
4. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
5. Repeat the same configuration steps for I/O slot 2, 4 and 5.
6. Activate the first 4 E1 ports on I/O slots 3 and 6, starting with link 1. Use
Configuration> Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down).
5-20
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-3 (M8E1))
(-)
(Balance)
7. Repeat Step 6 for links 2 to 4.
8. Repeat Step 6 for I/O slot 6.
Configuring Bundles
1. Add an MLPPP bundle with eight E1 links to I/O slot 1:
1. Open Configuration>Logical Layer>Bundles.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
>
(IO-1)
2. Bundle[1 - 32]
... (1)
2. Type a to add a bundle to the M8E1 module in I/O slot 1.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-1)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-1)
(Link 1)
3. Type N to display next page, which displays the other source ports.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-21
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
...
11.
12.
13.
14.
15.
16.
17.
(P)
Source
Source
Source
Source
Source
Source
Source
Port
Port
Port
Port
Port
Port
Port
>
>
>
>
>
>
>
(Link
(Link
(Link
(Link
(Link
(Link
(Link
2)
3)
4)
5)
6)
7)
8)
2. Add an MLPPP bundle with eight E1 links to I/O slot 2 (type P for previous
page):
1. Select Slot>IO-2.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-2)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 2.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-2)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-2)
(Link 1)
3. Add an MLPPP bundle with eight E1 links to I/O slot 3:
1. Select Slot>IO-3.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-3)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 3.
5-22
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-3)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-3)
(Link 1)
4. Add an MLPPP bundle with eight E1 links to I/O slot 4:
1. Select Slot>IO-4.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-4)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 4.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-4)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-4)
(Link 1)
5. Add an MLPPP bundle with eight E1 links to I/O slot 5:
1. Select Slot>IO-5.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-5)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 5.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-23
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-5)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-5)
(Link 1)
6. Add an MLPPP bundle with eight E1 links to I/O slot 6:
1. Select Slot>IO-6.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-6)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 6.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-6)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-6)
(Link 1)
Interconnecting Bundles to Form Flows
1. Connect BND1 on I/O slot 1 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250]
5-24
... (1)
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
2. Type a to add a flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(1)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Use F to scroll among the available ports.
6. Type S to save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(1)
(Aware)
(1)
(0)
(IO-1)
(Bnd 1)
(16384Kbps)
()
8. Type S to save and then type <ESC>.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-25
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP C-VLAN Type
359 Aware
1
Aware
C-VLAN ID
1
1
SP-VLAN
0
0
Slot
CL-A
IO-1
Port
GbE 1
Bnd 1
Rate BP User Name
1Gbps
16384Kbps
1. Unaware
2. Aware
9. Type <ESC>.
2. Connect BND1 on I/O slot 2 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
2. Type a to add a flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (2)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
5-26
...
>
...
...
>
>
>
...
(359)
(Aware)
(2)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(36)
(Aware)
(2)
(0)
(IO-2)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
3. Connect BND1 on I/O slot 3 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(3)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(71)
(Aware)
(3)
(0)
(IO-3)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice.
4. Connect BND1 on I/O slot 4 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-27
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(7)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(7)
(0)
(IO-4)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
5. Connect BND1 on I/O slot 5 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(8)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
5-28
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(8)
(0)
(IO-5)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
6. Connect BND2 on I/O slot 6 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(9)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(142)
(Aware)
(9)
(0)
(IO-5)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice.
Connecting Bundles to the E1 Ports
1. Connect the E1 ports of the modules in slots I/O 1 to I/O 4 to the bundles
configured above:
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-29
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
1. Open Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
>Destination Port (-)
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
3. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
2. Repeat the procedure for I/O slots 2, 4 and 5.
3. Connect the E1 ports 1 to 4 on I/O slot 5 to BND1:
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1> Link 1 (Up).
MP-4100
Configuration>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-5 (M8E1))
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
5-30
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...on>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)>Destination Port (-)
1.
2.
3.
4.
5.
6.
7.
8.
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
4. Repeat the same procedure (Steps 5, 7) for I/O slot 6.
5. To save and activate the new configuration, press the % key.
6. Press Y to confirm. Configuration File Update Is In Process will appear at the
bottom of the screen for the time the database is being saved (a few
seconds).
Configuring Equipment at Location C
Configuring the Clock Source
1. Configure the system clock source to use the recovered clock signal of E1
link 1 of the M8E1 in I/O slot 1, using Configuration>System>Clock
Source>Source>Rx Clock>Master Port.
MP-4100
Configuration>System>Clock Source>Master Port
Entry Num Slot
1
IO-1 (M8E1)
2
None
| 3
None
v 4
None
5
None
6
None
7
None
Port
Link 1
-
2. Type <ESC> for previous screen, and then select Fallback Port to configure
the fallback clock source to use the recovered clock signal of E1 link 1 of the
M8E1 in I/O slot 6.
MP-4100
Configuration>System>Clock Source>Fallback Port
Entry Num Slot
1
IO-6 (M8E1)
2
None
| 3
None
v 4
None
5
None
6
None
7
None
Megaplex-4100 Ver. 2.0
Port
Link 1
-
Configuration Procedure for Typical Ethernet Transport Application
5-31
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring the Physical Layer
1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>
CL>CL-A>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>
CL>CL-B>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-B>LAN>GbE 1
1.
2.
3.
4.
5.
6.
Admin Status
Auto Negotiation
Max Capability Advertised >
Flow Control
User Name
...
Redundancy
>
(Up)
(Enable)
(1000 MBPS Full Duplex)
(Disable)
()
(None)
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration>Physical
Layer>IO> I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
4. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
5. Repeat the same configuration steps for I/O slots 2, 4 and 5.
6. Activate the first 4 E1 ports on I/O slots 3 and 6, starting with link 1. Use
Configuration> Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down).
5-32
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-3 (M8E1))
(-)
(Balance)
7. Repeat Step 6 for links 2 to 4.
8. Repeat Step 6 for I/O slot 6.
Configuring Bundles
1. Add an MLPPP bundle with eight E1 links to I/O slot 1:
1. Open Configuration>Logical Layer>Bundles.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-1)
... (1)
2. Type a to add a bundle to the M8E1 module in I/O slot 1.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-1)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-1)
(Link 1)
3. Type N to display next page, which displays the other source ports.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-33
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
...
11.
12.
13.
14.
15.
16.
17.
(P)
Source
Source
Source
Source
Source
Source
Source
Port
Port
Port
Port
Port
Port
Port
>
>
>
>
>
>
>
(Link
(Link
(Link
(Link
(Link
(Link
(Link
2)
3)
4)
5)
6)
7)
8)
2. Add an MLPPP bundle with eight E1 links to I/O slot 2 (type P for previous
page):
1. Select Slot>IO-2.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-2)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 2.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-2)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-2)
(Link 1)
3. Add an MLPPP bundle with eight E1 links to I/O slot 3:
1. Select Slot>IO-3.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-3)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 3.
5-34
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-3)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-3)
(Link 1)
4. Add an MLPPP bundle with eight E1 links to I/O slot 4:
1. Select Slot>IO-4.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-4)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 4.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(16384)
(IO-4)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-4)
(Link 1)
5. Add an MLPPP bundle with eight E1 links to I/O slot 5:
1. Select Slot>IO-5.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-5)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 5.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-35
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-5)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(8)
(IO-5)
(Link 1)
6. Add an MLPPP bundle with eight E1 links to I/O slot 6:
1. Select Slot>IO-6.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-6)
... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 6.
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
MLPPP MTU[80 - 1600] ...
Link OAM
Number Of Links[1 - 8]...
Source Slot
>
Source Port
>
(N)
(8192)
(IO-6)
(1)
(Up)
()
(MLPPP)
(250)
(Disable)
(4)
(IO-6)
(Link 1)
Interconnecting Bundles to Form Flows
1. Connect BND1 on I/O slot 1 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications> Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250]
... (1)
2. Type a to add a flow.
5-36
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(4)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Use F to scroll among the available ports.
6. Type S to save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(1)
(Aware)
(4)
(0)
(IO-1)
(Bnd 1)
(16384Kbps)
()
8. Type S to save and then type <ESC>.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-37
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP C-VLAN Type
359 Aware
1
Aware
C-VLAN ID
4
4
SP-VLAN
0
0
Slot
CL-A
IO-1
Port
GbE 1
Bnd 1
Rate BP User Name
1Gbps
16384Kbps
1. Unaware
2. Aware
9. Type <ESC>.
2. Connect BND1 on I/O slot 2 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
2. Type a to add a flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (2)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(5)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
5-38
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow2
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(36)
(Aware)
(5)
(0)
(IO-2)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
3. Connect BND1 on I/O slot 3 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(359)
(Aware)
(6)
(0)
(CL-A)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(71)
(Aware)
(6)
(0)
(IO-3)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice.
4. Connect BND1 on I/O slot 4 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-39
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(7)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow4
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(7)
(0)
(IO-4)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
5. Connect BND1 on I/O slot 5 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(8)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
5-40
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow5
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(106)
(Aware)
(8)
(0)
(IO-5)
(Bnd 1)
(16384Kbps)
()
7. Type S to save and then type <ESC> twice.
6. Connect BND2 on I/O slot 6 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
2. Type a to add a flow.
3. Select Bridge Port Mapping.
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
1.
2.
3.
4.
BP[1 - 512]
C-VLAN Type
C-VLAN ID[1 - 4094]
SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(379)
(Aware)
(9)
(0)
(CL-B)
(GbE 1)
(1Gbps)
()
5. Type S to save and then type <ESC>.
6. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow6
BP[1 - 512]
1. C-VLAN Type
2. C-VLAN ID[1 - 4094]
3. SP-VLAN[0 - 4094]
Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(142)
(Aware)
(9)
(0)
(IO-5)
(Bnd 1)
(8192Kbps)
()
7. Type S to save and then type <ESC> twice
Connecting Bundle to the E1 Ports
1. Connect the E1 ports of the modules in slots I/O 1 to I/O 4 to the bundles
configured above:
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-41
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
1. Open Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Redundancy
Admin Status
User Name
Line Type
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
>
(None)
(Up)
... ()
>
(Unframed)
>
(Short Haul)
... (00)
>
(CCITT)
(DS1)
>
(IO-1 (M8E1))
>
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links>Destination Port (-)
1.
2.
3.
4.
5.
6.
7.
8.
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
2. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
3. Repeat the procedure for I/O slots 2, 4 and 5.
4. Connect the E1 ports 1 to 4 on I/O slot 5 to BND1:
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Up).
MP-4100
Configuration>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Redundancy
Rx Gain
Data OOS[0 - ff]
Restoration Time
Cross Connect
Destination Slot
Destination Port
Interface Type
...
>
>
>
...
>
>
>
(Up)
()
(Unframed)
(None)
(Short Haul)
(00)
(CCITT)
(DS1)
(IO-5 (M8E1))
(-)
(Balance)
2. Type 9 to change Destination Port to Bundle 1.
5-42
Configuration Procedure for Typical Ethernet Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
...on>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)>Destination Port (-)
1.
2.
3.
4.
5.
6.
7.
8.
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
Link 8
Bundle 1
5. Repeat the same procedure (Steps 5, 7) for I/O slot 6.
6. To save and activate the new configuration, press %.
7. Press Y to confirm. Configuration File Update Is In Process will appear at the
bottom of the screen for the time the database is being saved (a few
seconds).
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical Ethernet Transport Application
5-43
Chapter 5 Configuring Typical Applications
5.3
Installation and Operation Manual
Configuration Procedure for Typical SONET
Transport Application
Overview
This section provides detailed configuration procedures for a typical
Megaplex-4100 application that enables transport of TDM and Ethernet traffic in
a SONET ring. The application topology is shown in Figure 5-2.
Location B
Location A
Link 1
on CL A
Link 1
on CL B
Link 1
on CL A
SONET
Ring
Megaplex-4100 B
Megaplex-4100 A
Link 1
on CL B
Location C
Megaplex-4100 C
Link 1
on CL A
Link 1
on CL B
Figure 5-2. Network Topology for SONET Application
In this application, three Megaplex-4100 units are interconnected in a SONET
ring. To achieve both link and hardware protection, the connection to the ring is
made via OC-3 ports located on different CL modules (one OC-3 port on CL
module A, and the other on CL module B).
The ring operates as a stand-alone network, and therefore its timing source, as
well as the timing service of the SDH/SONET subsystem, is the internal oscillator
of the Megaplex-4100 at Location A. The other sites will lock their system (nodal)
time to the timing recovered from the SONET line signal.
The I/O modules installed at Location A and B are connected through PDH port 1;
bypass connections at Location C ensure ring connectivity. The traffic carried by
PDH 1 also includes HDLC bundles with a bandwidth of 128 kbps, supported by
means of the M8T1 module in I/O slot 1.
For maximum protection, path protection is enabled for PDH 1, with the
protection partner located on the adjacent CL module.
Network management is performed by an SNMP-based network management
station, for example, RADview NMS PC, using an out-of-band connection via a
5-44
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
serial or Ethernet port. Management communication to other Megaplex-4100
units is transferred inband, over the SONET links, through the DCC.
Configuration Sequence
For each of the 3 sites (Location A, Location B, Location C, in that order), the
configuration sequence is as follows:
1. Preliminary configuration.
2. Configuring the SDH/SONET subsystem of the CL modules for SONET (OC-3
framing).
3. Configuring the clock sources.
4. Configuring the physical ports and assigning timeslots to I/O ports and
bundles.
5. Mapping the PDH ports to the OC-3 ports.
6. Adding bundles.
7. Interconnecting bundles to form flows.
8. Connecting the bundles to their T1 ports.
Preliminary Configuration (All Sites)
1. Connect a terminal to the CONTROL DCE connector of the active CL module.
Make sure to use VT-100 supervision terminal emulation.
2. Configure the supervision terminal for communication with the
Megaplex-4100. Megaplex-4100 default configuration is as follows:
115.2 kbps, one start bit, eight data bits, no parity, one stop bit. Select
full-duplex mode, echo off, and disable flow control.
3. If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for a few seconds,
and then press <Enter> several times.
4. Type the default user name (su) and password (1234).
MP-4100
USER NAME:
PASSWORD:
su
****
5. Set the factory default parameters for the Megaplex-4100, using
Configuration>System>Factory Default.
6. Press Y to confirm.
7. Set the time and date, using Configuration>System>Date & Time.
8. Load the hardware configuration (the installed modules), using
Configuration>DB Tools>Load HW, and then press Y to confirm.
9. To save and activate the new configuration, press the % key, and then press
Y to confirm.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-45
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuration File Update Is In Process will appear at the bottom of the
screen while the database is being saved (a few seconds).
10. Check the modules installed in the Megaplex-4100 chassis, using
Inventory>SW/HW Rev.
MP-4100
Inventory>SW/HW Rev
Slot
PS-A
PS-B
| CL-A
v CL-B
IO-1
IO-2
IO-3
IO-4
IO-5
IO-6
IO-7
IO-8
Installed Card
PS
PS
CL1/155
CL1/155
M8T1
M8T1
HSF-2
HS-12/N
HS-R/N
VC-8/FXO
VC-8/FXS
VC-8/E&M
HW Revision
SW Version
0. 1/ 0.1
0. 1/ 0.1
1
1
4
2
6
2
10
10
1.50A0/ 1.9
1.50A0/ 1.9
1.2
1.2
1.05
6.00
55.00
8.00
13.00
13.00
Programmed Card
PS
PS
CL1/155
CL1/155
M8T1
M8T1
HSF-2
HS-12/N
HS-R/N
VC-8/FXO
VC-8/FXS
VC-8/E&M
11. Configure the Megaplex-4100 management IP address and other IP
communication parameters, using Configuration>Quick Setup.
MP-4100
Configuration>Quick Setup
1. Host IP Address... (172.17.191.100)
2. Subnet Mask
... (255.255.255.0)
3. Default Gateway... (172.17.191.153)
12. Configure the Megaplex-4100 IP agent name, using Configuration>System>
Management>Device Info.
MP-4100
Configuration>System>Management>Device Info
Sys Description...
Object ID
...
1. Device Name
...
2. Contact Person ...
3. Location ID
...
(Sys type:MP-4100 Sys Ver:1.50A0 Chassis Revision:0)
(radMP4100)
(MP4100)
(Name of contact person
)
(The location of this device
)
Configuring Equipment at Location A
Configuring SDH/SONET Subsystems
1. Configure the SDH/SONET subsystems on the CL modules to work with OC-3
framing, using Configuration> Physical Layer>CL>CL-A>SDH/SONET>Card
Configuration. Your selection is automatically copied to the other CL module.
5-46
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1. Frame Structure
2. Tx Clock Based on SSM
3. Common PDH LVC Parameters >
(OC-3)
(Yes)
2. You will be asked to confirm: press Y.
3. Configure the timing mode of the SDH/SONET subsystem of CL module A to
Internal (first, select No for Tx Clock Based on SSM).
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1.
2.
3.
4.
Frame Structure
Tx Clock Based on SSM
SONET Tx Clock
Common PDH LVC Parameters >
(OC-3)
(No)
(Internal)
4. You may leave the Common PDH LVC Parameters default values unchanged.
5. Configure CL module B the same as CL module A (repeat Steps 3, 4 on CL-B).
Configuring OC-3 Physical Layer
1. Enable OC-3 port 1 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Up)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
2. Configure the OC-3 port 1 of CL module A for inband management using the
RAD proprietary management protocol, over DCC bits D4 to D12. Use
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration
1.
2.
3.
4.
In Band Management>
Routing Protocol >
Management DCC
>
Deviation Type
(HDLC)
(Proprietary RIP)
(D4-D12)
(Standard)
3. Disable OC-3 port 2 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 2.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-47
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 2
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Down)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
4. Repeat Steps 1, 2, 3 above for the OC-3 ports of CL module B, using
Configuration>Physical Layer>CL>CL-B>SDH/SONET>Link 1 and Link 2.
Configuring System Clock Sources
Configure the system to use the timing of the SDH/SONET subsystem as the clock
source, using Configuration>System>Clock Source.
MP-4100
Configuration>System>Clock Source
1. Source
>
(S Subsystem)
Configuring and Mapping the PDH Ports
1. Activate PDH port 1 (which is the port used to carry the TDM and Ethernet
traffic in this example), using Configuration>Logical Layer>CL>PDH>PDH 1.
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Frame Type
Redundancy
FDL Type
Restoration Time
Idle Code[0 - ff]
Cross Connect
In Band Management
LVC Configuration
Time Slot Assignment
...
>
>
>
>
...
>
>
>
(Up)
()
(ESF)
(None)
(Response)
(10 Seconds(62411))
(7F)
(DS0)
(Off)
2. Configure the LVC parameters of PDH 1, and enable path protection with
automatic mapping on the adjacent CL (CL module B), using
Configuration>Logical Layer> CL>PDH>PDH 1>LVC Configuration.
Note
5-48
Timeslot assignment for PDH 1 will be performed after configuring the Ethernet
bundles, and the physical ports of the I/O modules that will connect to PDH 1.
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Up)>LVC Configuration
1.
2.
3.
4.
5.
6.
7.
8.
9.
J2 Rx path trace
J2 path trace
Padding
EED Threshold
SD Threshold
Protection Mode
Mapping Mode
Protection Partner
Payload Label
(Disable)
... (www.rad.com)
(Nulls)
>
(1E-3)
>
(1E-6)
>
(Path Protection)
>
(Auto)
>
(Adjacent CL)
[0 - 7] ... (2)
3. Map PDH 1 to the desired TUG of OC-3 link 1 of CL-A, using
Configuration>System>Mapping> CL-A>Link 1.
MP-4100
Configuration>System>Mapping>CL-A>Link 1
STS1-1
TU1
TU2
TUG2-1 PDH1
None
TUG2-2 None
None
TUG2-3 None
None
TUG2-4 None
None
TUG2-5 None
None
TUG2-6 None
None
TUG2-7 None
None
->>
1. None
3. L2A-TU3
2. PDH1
4. L2B-TU3
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. L2A-VT
6. L2B-VT
4. Since automatic protection mapping is enabled, the protection PDH for PDH 1
of CL module A is mapped to the same PDH on CL module B, link 1. Check
using Configuration>System>Mapping>CL-B>Link 1.
MP-4100
Configuration>System>Mapping>CL-B>Link 1
TU1
TUG2-1 P-PDH1
TUG2-2 None
TUG2-3 None
TUG2-4 None
TUG2-5 None
TUG2-6 None
TUG2-7 None
->>
1. None
3.
2. PDH1
4.
Megaplex-4100 Ver. 2.0
STS1-1
TU2
None
None
None
None
None
None
None
L2A-TU3
L2B-TU3
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. L2A-VT
6. L2B-VT
Configuration Procedure for Typical SONET Transport Application
5-49
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring I/O Ports on Other Modules
1. Activate HSF-2 ports 1 and 2, set each port to 64 kbps (1 x 64 kbps), and
connect the ports to CL port PDH 1, using Configuration>Physical Layer>IO>
I/O-3 (HSF-2)>All Ports.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>All Ports
1.
2.
3.
4.
Admin Status
Rate
Destination Slot
Destination Port
>
>
>
(Up)
(1 Ts)
(CL(CL1/155))
(PDH 1)
2. You will be asked to confirm: press Y.
3. Activate HS-6/N ports 1 and 2, set them for 128 kbps (2 x 64 kbps), and
connect them to CL port PDH 1:
1. Open Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
Admin Status
Rate
Clock Mode
CTS
Fifo Size
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
>
>
(Up)
(2x64 )
(DCE)
(ON)
(AUTOMATIC)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
2. Select Port 2 and repeat the procedure.
4. Activate HS-R/N ports 1 and 2, set them for 9.6 kbps, and connect them to
CL port PDH 1:
1. Open Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Admin Status
Format
>
Rate
>
Encapsulation Mode
CTS
>
DCD & DSR
>
Clock Mode
>
Operation Mode
>
Destination Slot >
Destination Port >
(Up)
(SYNC)
(9.6 KBPS)
(Bandwidth Optimized)
(ON)
(Local)
(DCE)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
2. Select Port 2 and repeat the procedure.
5. Configure the VC-8/FXO card:
5-50
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
1. Configure the VC-8/FXO card parameters, using Configuration>Physical
Layer>IO> I/O-6 (VC-8/FXO)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration
1.
2.
3.
4.
Coding Law
Signaling
Encoding
Metering
>
>
(u LAW)
(RBMF SIGNALING)
(PCM)
(12K)
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Port 1 (Down)
1. Admin Status
(Up)
2. Transmit Level
>
(0.0)
3. Receive Level
>
(0.0)
4. Wires Number
(2 WIRES)
5. Interface
(LOOP START)
6. Signaling Feedback>
(No)
7. Echo Canceler
(Disable)
8. Operation Mode
>
(BI-DIR)
9. Destination Slot >
(CL(CL1/155))
10. Destination Port >
(PDH 1)
3. Configure Port 2 and connect it to CL port PDH 1, using the same
procedure.
6. Configure the VC-8/FXS card:
1. Configure the VC-8/FXS card parameters, using Configuration>Physical
Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration
1.
2.
3.
4.
Coding Law
Signaling
Encoding
Metering
>
>
(u LAW)
(RBMF SIGNALING)
(PCM)
(12K)
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Interface
Echo Canceler
Operation Mode
Destination Slot
Destination Port
Megaplex-4100 Ver. 2.0
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(LOOP START)
(Disable)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
Configuration Procedure for Typical SONET Transport Application
5-51
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
3. Configure Port 2 and connect it to CL port PDH 1, using the same
procedure.
7. Configure the VC-8/E&M card:
1. Configure the VC-8/E&M card parameters, using Configuration>Physical
Layer>IO>I/O-8 (VC-8/E&M)> Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration
1. Coding Law
2. Signaling
3. Encoding
CL:
>
(u LAW)
(RBMF SIGNALING)
(PCM)Open ports 1 and 2 and relate them to PDH 1 of the
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Port 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Echo Canceler
Type
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(Disable)
(SSDC5)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
3. Configure Port 2 and connect it to CL port PDH 1, using the same
procedure.
Configuring Ethernet Bundles
1. Enable the ETH port on the M8T1 card in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1(Down)
1.
2.
3.
4.
5.
6.
Admin Status
(Up)
User Name
... ()
Auto Negotiation
(Enable)
Max Capability Advertised >
(100 Mbps Full Duplex)
Flow Control
(Disable)
Link OAM(802.3ah)
(Disable)
2. Add a HDLC bundle on the PDH 1 port, supported by means of the M8T1
module in I/O slot 1:
4. Open Configuration>Logical Layer>Bundles.
5-52
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
2. Bundle[1 - 32]
>
(IO-1)
... (1)
5. Type a and add a HDLC bundle, with a bandwidth of 128 kbps (two
timeslots).
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
Number Of TS[1 - 32] ...
Link OAM
Source Slot
>
Source Port
>
(128)
(IO-1)
(1)
(Up)
()
(HDLC)
(2)
(Disable)
(CL-A)
(PDH 1)
6. Type a and add a second HDLC bundle, with a bandwidth of 128 kbps
(two timeslots).
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
Number Of TS[1 - 32] ...
Link OAM
Source Slot
>
Source Port
>
(128)
(IO-1)
(2)
(Up)
()
(HDLC)
(2)
(Disable)
(CL-A)
(PDH 1 )
3. Configure a flow for bundle 1:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250]
... (1)
2. Type a to add a new flow.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-53
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping to map the required bridge ports to the flow:
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP[1 - 512]
1. C-VLAN Type
C-VLAN ID[1 - 4095]
SP-VLAN[0 - 4095]
2. Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(1)
(Unaware)
(0)
(0)
(IO-1)
(Bnd 1)
(128Kbps)
()
5. Use F to scroll among the available ports.
6. Type S for save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP[1 - 512]
1. C-VLAN Type
C-VLAN ID[1 - 4095]
SP-VLAN[0 - 4095]
2. Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(33)
(Unaware)
(0)
(0)
(IO-1)
(ETH 1)
(100Mbps)
()
8. Type S for save and then type <ESC>.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
1
33
5-54
C-VLAN Type
Unaware
Unaware
C-VLAN ID
0
0
SP-VLAN
0
0
Slot
IO-1
IO-1
Port
Bnd 1
ETH 1
Configuration Procedure for Typical SONET Transport Application
Rate
128Kbps
100Mbps
BP User Name
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
4. Configure an additional flow for bundle 2, using the same procedure as for
the first flow.
Assign Timeslots on PDH Port 1
1. Open the timeslot assignment menu for PDH port 1, and select Manual
assignment (Configuration>System>TS Assignment>CL>PDH 1>Manual).
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
Slot
-------------------------
1. ---... (N)
Port
-------------------------
2. Split
Ts
---------
Type
-
3. CL (CL1/155)
2. Assign the prescribed timeslots to each I/O port or Ethernet bundle (use the
keyboard arrow keys to move the cursor):
1. Start by moving the cursor to the desired PDH port timeslot, in the Ts#
column.
2. Move the cursor to the Slot column in the same row, and then select the
desired I/O module from the list of modules that require mapping to PDH
port 1 (displayed at the bottom of the page.
3. If the timeslot must use split timeslot allocation, then select Split in this
row, and skip to the next PDH port timeslot.
4. Move the cursor to the Port column in the same row, and then select the
desired port from the list of ports of the selected I/O module that require
mapping to PDH port 1 (displayed at the bottom of the page).
5. Move the cursor to the Ts column in the same row (the first timeslot that
is a candidate for being connected to the PDH port is automatically
displayed), and then select the prescribed I/O module timeslot.
6. Move the cursor to the Type column in the same row (the timeslot type
that should be selected is automatically displayed by default), and then
select the prescribed timeslot type.
7. Repeat the process for all the ports and bundles that must be connected
to PDH port 1.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-55
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Manual
|
v
|
v
Ts#
TS 01
TS 02
TS 03
TS 04
TS 05
TS 06
TS 07
TS 08
TS 09
TS 10
TS 11
TS 12
TS 13
TS 14
TS 15
TS 16
TS 17
TS 18
Slot
IO-3 (HSF-2)
IO-3 (HSF-2)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
Split
Split
IO-6 (VC-8/FXO)
IO-6 (VC-8/FXO)
IO-7 (VC-8/FXS)
IO-7 (VC-8/FXS)
IO-8 (VC-8/E&M)
IO-8 (VC-8/E&M)
IO-1 (M8T1)
IO-1 (M8T1)
IO-1 (M8T1)
IO-1 (M8T1)
Port
CH 1
CH 2
CH 1
CH 1
CH 2
CH 2
CH 1
CH 2
CH 1
CH 2
CH 1
CH 2
BND 1
BND 1
BND 2
BND 2
Ts
-------------------
Type
DATA
DATA
DATA
DATA
DATA
DATA
DATA
DATA
VOICE
VOICE
VOICE
VOICE
VOICE
VOICE
DATA
DATA
DATA
DATA
3. On the timeslot assignment menu for PDH port 1, select Split assignment,
and configure the bits in timeslot 7 using Configuration>System>TS
Assignment>CL>PDH 1>Split>TS 7.
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Split>TS 7
1.
2.
3.
4.
5.
6.
7.
8.
9.
Bit 1
...
Bit 2
...
Bit 3
...
Bit 4
...
Bit 5
...
Bit 6
...
Bit 7
...
Bit 8
...
Check Split Sanity
(05:01)
(05:01)
(------)
(------)
(------)
(------)
(------)
(------)
4. On the timeslot assignment menu for PDH port 1, select Split assignment,
and configure the bits in timeslot 8 using Configuration>System>TS
Assignment>CL>PDH 1>Split>TS 8.
5. To save and activate the new configuration, press the % key, and then press
Y to confirm. Configuration File Update is in Process will appear in the bottom
of the screen while the database is being updated (a few seconds).
Configuration Equipment at Location B
Configuring SDH/SONET Subsystems
1. Configure the SDH/SONET subsystems on the CL modules to work with OC-3
framing, using Configuration> Physical Layer>CL>CL-A>SDH/SONET>Card
Configuration. Your selection is automatically copied to the other CL module.
5-56
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1. Frame Structure
2. Tx Clock Based on SSM
3. Common PDH LVC Parameters >
(OC-3)
(Yes)
2. You will be asked to confirm: press Y.
3. You may leave the Common PDH LVC Parameters default values unchanged.
4. Configure CL module B the same as CL module A (repeat Steps 2, 3 on CL-B).
Configuring OC-3 Physical Ports
1. Enable OC-3 port 1 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Up)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
2. Configure the OC-3 port 1 of CL module A for inband management using the
RAD proprietary management protocol, over DCC bits D4 to D12. Use
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration
1.
2.
3.
4.
In Band Management>
Routing Protocol >
Management DCC
>
Deviation Type
(HDLC)
(Proprietary RIP)
(D4-D12)
(Standard)
3. Disable OC-3 port 2 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 2.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 2
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Down)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
4. Repeat Steps 1, 2, 3 above for the OC-3 ports of CL module B, using
Configuration>Physical Layer>CL>CL-B>SDH/SONET>Link 1 and Link 2.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-57
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring the Timing and Clock Sources
1. Configure the timing mode of the SDH/SONET subsystem of CL module A to
use the recovered clocks from the active SONET link as reference source,
using Configuration> Physical Layer>CL>CL-A> SDH/SONET>Card
Configuration:
1. Select No for Tx Clock Based on SSM.
2. Select Rx Clock for SONET Tx Clock. The Master and Fallback sources are
automatically set to Link 1 (the only active link of the module).
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1.
2.
3.
4.
5.
6.
Frame Structure
Tx Clock Based on SSM
SONET Tx Clock
Master Port
Fallback Port
Common PDH LVC Parameters
(OC-3 )
(No)
(Rx Clock)
(Link 1)
(Link 1)
>
>
>
>
2. Configure CL module B the same as CL module A (repeat Step 1 on CL-B).
3. Configure the system to use the timing of the SDH/SONET subsystem as the
clock source, using Configuration>System>Clock Source.
MP-4100
Configuration>System>Clock Source
1. Source
>
(S Subsystem)
Configuring and Mapping the PDH Ports
1. Activate PDH port 1 (which is the port used to carry the TDM and Ethernet
traffic in this example), using Configuration>Logical Layer>CL>PDH>PDH 1.
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Frame Type
Redundancy
FDL Type
Restoration Time
Idle Code[0 - ff]
Cross Connect
In Band Management
LVC Configuration
Time Slot Assignment
...
>
>
>
>
...
>
>
>
(Up)
()
(ESF)
(None)
(Response)
(10 Seconds(62411))
(7F)
(DS0)
(Off)
2. Configure the LVC parameters of PDH 1, and enable path protection with
automatic mapping on the adjacent CL (CL module B), using
Configuration>Logical Layer> CL>PDH>PDH 1>LVC Configuration.
5-58
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Note
Chapter 5 Configuring Typical Applications
Timeslot assignment for PDH 1 will be performed after configuring the Ethernet
bundles, and the physical ports of the I/O modules that will connect to PDH 1.
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Up)>LVC Configuration
1.
2.
3.
4.
5.
6.
7.
8.
9.
J2 Rx path trace
J2 path trace
Padding
EED Threshold
SD Threshold
Protection Mode
Mapping Mode
Protection Partner
Payload Label
(Disable)
... (www.rad.com)
(Nulls)
>
(1E-3)
>
(1E-6)
>
(Path Protection)
>
(Auto)
>
(Adjacent CL)
[0 - 7] ... (2)
3. Map PDH 1 to the desired TUG of OC-3 link 1 of CL-A, for example, TUG-2 1
(this mapping must match the mapping at the far end of the link). Use
Configuration>System>Mapping> CL-A>Link 1.
MP-4100
Configuration>System>Mapping>CL-A>Link 1
STS1-1
TU1
TU2
TUG2-1 PDH1
None
TUG2-2 None
None
TUG2-3 None
None
TUG2-4 None
None
TUG2-5 None
None
TUG2-6 None
None
TUG2-7 None
None
->>
1. None
3. L2A-TU3
2. PDH1
4. L2B-TU3
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. L2A-VT
6. L2B-VT
4. Since automatic protection mapping is enabled, the protection PDH for PDH 1
of CL module A is mapped to the same PDH on CL module B, link 1. Check
using Configuration>System>Mapping>CL-B>Link 1.
MP-4100
Configuration>System>Mapping>CL-B>Link 1
TU1
TUG2-1 P-PDH1
TUG2-2 None
TUG2-3 None
TUG2-4 None
TUG2-5 None
TUG2-6 None
TUG2-7 None
->>
1. None
3.
2. PDH1
4.
Megaplex-4100 Ver. 2.0
STS1-1
TU2
None
None
None
None
None
None
None
L2A-TU3
L2B-TU3
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. L2A-VT
6. L2B-VT
Configuration Procedure for Typical SONET Transport Application
5-59
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
5. To save and activate the new configuration, press the % key, and then press
Y to confirm. Configuration File Update is in Process will appear in the bottom
of the screen while the database is being updated (a few seconds).
Configuring the I/O Ports of M8T1 Modules
1. Activate T1 port 1 on the M8T1 module in I/O slot 1 (the port used to carry
the TDM and Ethernet traffic in this example), and configure it to use
dual-cable parallel Tx redundancy, with the same port of the M8T1 module in
I/O slot 2. Use Configuration>Physical Layer>IO> I/O-1 (M8T1)> T1>Link 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>T1>Link 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
Primary
Admin Status
User Name
Line Type
Signaling Profile
Idle Code[0 - ff]
Redundancy
Voice OOS[0 - ff]
Data OOS[0 - ff]
OOS Signaling
Restoration Time
(N)
>
...
>
>
...
>
...
...
>
>
(Yes)
(Up)
()
(ESF)
(1)
(7F)
(Dual Cable P. TX)
(00)
(FF)
(Forced Idle)
(10 Seconds(62411))
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>T1>Link 1 (Down)
...
11.
12.
13.
14.
15.
16.
17.
18.
19.
(P)
Cross Connect
In Band Management
Routing Protocol
Redundancy Slot
Redundancy Channel
Wait To Restore[0 - 999]
Line Code
Line Interface
Attenuation(CSU)/Length (DSU)
>
>
>
>
...
>
>
>
(DS0)
(Dedicated FR)
(None)
(IO-2 (M8T1))
(Link 1)
(0)
(B8ZS)
(CSU)
(0 dB)
2. Activate T1 port 2 on the M8T1 module in I/O slot 1 (the port is used to carry
Ethernet traffic in this example). Use Configuration>Physical Layer>IO> I/O-1
(M8T1)> T1>Link 2.
5-60
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>T1>Link 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Admin Status
User Name
Line Type
Signaling Profile
Idle Code[0 - ff]
Redundancy
Voice OOS[0 - ff]
Data OOS[0 - ff]
OOS Signaling
Restoration Time
Cross Connect
...
>
>
...
>
...
...
>
>
(Up)
()
(ESF)
(1)
(7F)
(None)
(00)
(00)
(Forced Idle)
(10 Seconds(62411))
(DS0)
3. Check that the T1 port parameters of the M8T1 module in I/O slot have been
copied to the redundancy partner port (T1 port 1 of the M8T1 module in I/O
slot 2), using Configuration> Physical Layer>IO>I/O-2 (M8T1)>T1>Link 2.
4. To save and activate the new configuration, press the % key, and then press
Y to confirm. Configuration File Update is in Process will appear in the bottom
of the screen while the database is being updated (a few seconds).
Configuring I/O Ports on Other Modules
1. Activate HSF-2 port 1, set it to 64 kbps (1 x 64 kbps), and connect the port
to CL port PDH 1, using Configuration>Physical Layer>IO> I/O-3 (HSF-2)> Port
1.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>Port 1 (Down)
1.
2.
3.
4.
Admin Status
Rate
Destination Slot
Destination Port
>
>
>
(Up)
(1 Ts)
(CL(CL1/155))
(PDH 1)
2. Activate HSF-2 port 2, set it to 64 kbps (1 x 64 kbps), and connect the port
to T1 port 1 of the M8T1 module in I/O slot 1, using Configuration> Physical
Layer>IO> I/O-3 (HSF-2)> Port 2.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>Port 2 (Down)
1.
2.
3.
4.
Admin Status
Rate
Destination Slot
Destination Port
>
>
>
(Up)
(1 Ts)
(IO-1 (M8T1))
(Link 1)
3. Activate HS-6/N port 1, set it for 128 kbps (2 x 64 kbps), and connect the
port to CL port PDH 1, using Configuration>Physical Layer>IO>I/O-4
(HS-6/N)>Port 1.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-61
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
Admin Status
Rate
Clock Mode
CTS
Fifo Size
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
>
>
(Up)
(2x64 )
(DCE)
(ON)
(AUTOMATIC)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
4. Activate HS-6/N port 2, set it for 128 kbps (2 x 64 kbps), and connect the
port to T1 port 1 of the M8T1 module in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 2.
MP-4100
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
Admin Status
Rate
Clock Mode
CTS
Fifo Size
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
>
>
(Up)
(2x64 )
(DCE)
(ON)
(AUTOMATIC)
(BI-DIR)
(IO-1 (M8T1))
(Link 1)
5. Activate HS-R/N port 1, set it for 9.6 kbps, and connect the port to CL port
PDH 1, using Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Admin Status
Format
>
Rate
>
Encapsulation Mode
CTS
>
DCD & DSR
>
Clock Mode
>
Operation Mode
>
Destination Slot >
Destination Port >
(Up)
(SYNC)
(9.6 KBPS)
(Bandwidth Optimized)
(ON)
(Local)
(DCE)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
6. Activate HS-R/N port 2, set it for 9.6 kbps, and connect the port to T1 port 1
of the M8T1 module in I/O slot 1, using Configuration>Physical Layer>IO>
I/O-5 (HS-R/N)>Port 2.
5-62
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Admin Status
Format
>
Rate
>
Encapsulation Mode
CTS
>
DCD & DSR
>
Clock Mode
>
Operation Mode
>
Destination Slot >
Destination Port >
(Up)
(SYNC)
(9.6 KBPS)
(Bandwidth Optimized)
(ON)
(Local)
(DCE)
(BI-DIR)
(IO-1 (M8T1))
(Link 1)
7. Configure the VC-8/FXO card:
1. Configuration the VC-8/FXO card parameters, using
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration
1.
2.
3.
4.
Coding Law
Signaling
Encoding
Metering
>
>
(u LAW)
(RBMF SIGNALING)
(PCM)
(12K)
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Port 1 (Down)
1. Admin Status
(Up)
2. Transmit Level
>
(0.0)
3. Receive Level
>
(0.0)
4. Wires Number
(2 WIRES)
5. Interface
(LOOP START)
6. Signaling Feedback>
(No)
7. Echo Canceler
(Disable)
8. Operation Mode
>
(BI-DIR)
9. Destination Slot >
(CL(CL1/155))
10. Destination Port >
(PDH 1)
3. Configure Port 2 and connect it to T1 port 1 of the M8T1 module in I/O
slot 1, using the same procedure.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-63
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Port 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Admin Status
Transmit Level
>
Receive Level
>
Wires Number
Interface
Signaling Feedback>
Echo Canceler
Operation Mode
>
Destination Slot >
Destination Port >
(Up)
(0.0)
(0.0)
(2 WIRES)
(LOOP START)
(No)
(Disable)
(BI-DIR)
(IO-1 (M8T1))
(Link 1)
8. Configure the VC-8/FXS card:
1. Configure the VC-8/FXS card parameters, using Configuration>Physical
Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration
1.
2.
3.
4.
Coding Law
Signaling
Encoding
Metering
>
>
(u LAW)
(RBMF SIGNALING)
(PCM)
(12K)
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 1 (Up)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Interface
Echo Canceler
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(LOOP START)
(Disable)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
3. Configure Port 2 and connect it to T1 port 1 of the M8T1 module in I/O
slot 1, using the same procedure.
5-64
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Interface
Echo Canceler
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(LOOP START)
(Disable)
(BI-DIR)
(IO-1 (M8T1))
(Link 1)
9. Configure the E&M card parameters:
1. Configure the VC-8/E&M card parameters, using Configuration>Physical
Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration
1. Coding Law
2. Signaling >
3. Encoding
CL:
(u LAW)
(RBMF SIGNALING)
(PCM)Open ports 1 and 2 and relate them to PDH 1 of the
2. Configure Port 1 and connect it to CL port PDH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Port 1 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Echo Canceler
Type
Operation Mode
Destination Slot
Destination Port
>
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(Disable)
(SSDC5)
(BI-DIR)
(CL(CL1/155))
(PDH 1)
3. Configure Port 2 and connect it to T1 port 1 of the M8T1 module in I/O
slot 1, using the same procedure.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Port 2 (Down)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Admin Status
Transmit Level
Receive Level
Wires Number
Echo Canceler
Type
Operation Mode
Destination Slot
Destination Port
Megaplex-4100 Ver. 2.0
>
>
>
>
>
>
(Up)
(0.0)
(0.0)
(2 WIRES)
(Disable)
(SSDC5)
(BI-DIR)
(IO-1 (M8T1))
(Link 1)
Configuration Procedure for Typical SONET Transport Application
5-65
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
Configuring Ethernet Bundles
1. Enable the ETH port on the M8T1 card in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1(Down)
1.
2.
3.
4.
5.
6.
Admin Status
(Up)
User Name
... ()
Auto Negotiation
(Enable)
Max Capability Advertised >
(100 Mbps Full Duplex)
Flow Control
(Disable)
Link OAM(802.3ah)
(Disable)
2. Add a HDLC bundle on the CL PDH 1 port, supported by means of the M8T1
module in I/O slot 1:
1. Open Configuration>Logical Layer>Bundles.
MP-4100
Configuration>Logical Layer>Bundles
1. Slot
>
(IO-1)
2. Bundle[1 - 32]
... (1)
2. Type a to add a HDLC bundle on the CL PDH 1 port, with a bandwidth of
128 kbps (two timeslots).
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
Number Of TS[1 - 32] ...
Link OAM
Source Slot
>
Source Port
>
(128)
(IO-1)
(1)
(Up)
()
(HDLC)
(2)
(Disable)
(CL-A)
(PDH 1)
3. Type a and add a second HDLC bundle on the T1 port 2 of the M8T1 module
in I/O slot 1, with a bandwidth of 128 kbps (two timeslots).
5-66
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Logical Layer>Bundles
1.
2.
3.
4.
5.
6.
7.
8.
9.
Rate(Kbps)[64 - 16384]
Slot
>
Bundle[1 - 32]
...
Admin Status
User Name
...
L2 Protocol
>
Number Of TS[1 - 32] ...
Link OAM
Source Slot
>
Source Port
>
(128)
(IO-1)
(2)
(Up)
()
(HDLC)
(2)
(Disable)
(IO-1)
(Link 2)
4. Configure a flow for bundle 1:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250]
... (1)
2. Type a to add a new flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1.
2.
3.
4.
Flow[1 - 250]
... (1)
User Name
... ()
Flow Type
>
(E-LINE)
Bridge Port Mapping[]>
3. Select Bridge Port Mapping to map the required bridge ports to the flow:
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
C-VLAN Type
C-VLAN ID
SP-VLAN
Slot
Port
Rate
BP User Name
4. Type a to add the first bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP[1 - 512]
1. C-VLAN Type
C-VLAN ID[1 - 4095]
SP-VLAN[0 - 4095]
2. Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(1)
(Unaware)
(0)
(0)
(IO-1)
(Bnd 1)
(128Kbps)
()
5. Use F to scroll among the available ports.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-67
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
6. Type S for save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP[1 - 512]
1. C-VLAN Type
C-VLAN ID[1 - 4095]
SP-VLAN[0 - 4095]
2. Slot
Port
Rate
BP User Name
...
>
...
...
>
>
>
...
(33)
(Unaware)
(0)
(0)
(IO-1)
(ETH 1)
(100Mbps)
()
8. Type S for save and then type <ESC>.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow1
BP
1
33
C-VLAN Type
Unaware
Unaware
C-VLAN ID
0
0
SP-VLAN
0
0
Slot
IO-1
IO-1
Port
Bnd 1
ETH 1
Rate
128Kbps
100Mbps
BP User Name
1. Unaware
2. Aware
5. Configure an additional flow for bundle 2, using the same procedure as for
the first flow.
Assign Timeslots on CL PDH Port 1
1. Open the timeslot assignment menu for CL PDH port 1, and select Manual
assignment, using Configuration>System>TS Assignment>CL>PDH 1>Manual.
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
1. ---... (N)
Slot
-------------------------
Port
-------------------------
2. Split
Ts
---------
Type
-
3. CL (CL1/155)
2. Manually assign the prescribed timeslots to each I/O port or Ethernet bundle
(use the keyboard arrow keys to move the cursor), using the procedure
described on page 5-55.
5-68
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Manual
|
v
|
v
Ts#
TS 01
TS 02
TS 03
TS 04
TS 05
TS 06
TS 07
TS 08
TS 09
TS 10
TS 11
TS 12
TS 13
TS 14
TS 15
TS 16
TS 17
TS 18
Slot
IO-3 (HSF-2)
IO-3 (HSF-2)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
IO-4 (HS-12/N)
Split
Split
IO-6 (VC-8/FXO)
IO-6 (VC-8/FXO)
IO-7 (VC-8/FXS)
IO-7 (VC-8/FXS)
IO-8 (VC-8/E&M)
IO-8 (VC-8/E&M)
IO-1 (M8T1)
IO-1 (M8T1)
IO-1 (M8T1)
IO-1 (M8T1)
Port
CH 1
CH 2
CH 1
CH 1
CH 2
CH 2
CH 1
CH 2
CH 1
CH 2
CH 1
CH 2
BND 1
BND 1
BND 2
BND 2
Ts
-------------------
Type
DATA
DATA
DATA
DATA
DATA
DATA
DATA
DATA
VOICE
VOICE
VOICE
VOICE
VOICE
VOICE
DATA
DATA
DATA
DATA
3. On the timeslot assignment menu for PDH port 1, select Split assignment,
and configure the bits in timeslot 7 using Configuration>System>
TS Assignment>CL>PDH 1>Split>TS 7.
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Split>TS 7
1.
2.
3.
4.
5.
6.
7.
8.
9.
Bit 1
...
Bit 2
...
Bit 3
...
Bit 4
...
Bit 5
...
Bit 6
...
Bit 7
...
Bit 8
...
Check Split Sanity
(05:01)
(05:01)
(------)
(------)
(------)
(------)
(------)
(------)
4. On the timeslot assignment menu for PDH port 1, select Split assignment,
and configure the bits in timeslot 8 using Configuration>System>TS
Assignment>CL>PDH 1>Split>TS 8.
5. To save and activate the new configuration, press the % key, and then press
Y to confirm. Configuration File Update is in Process will appear in the bottom
of the screen while the database is being updated (a few seconds).
Assign Timeslots on M8T1 Ports
1. Open the timeslot assignment menu for T1 port 1, and perform manual
timeslot assignment to the various I/O ports using Configuration>System>TS
Assignment>IO>I/O-1 (M8T1)> Link 1>Manual. Use the procedure described
on page 5-55.
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-69
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>System>TS Assignment>IO>I/O-1 (M8T1)>Link 1>Manual
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
Slot
-------------------------
Port
-------------------------
Ts
---------
Type
-
2. Open the timeslot assignment menu for T1 port 2, and perform manual
timeslot assignment for the Ethernet bundles, using
Configuration>System>TS Assignment>IO>I/O-1 (M8T1)> Link 2>Manual. Use
the procedure described on page 5-55.
3. To save and activate the new configuration press the % key.
4. Press Y to confirm. Configuration File Update Is In Process will appear in the
bottom of the screen while the database is being saved (a few seconds).
Configuration Equipment at Location C
Configuring SDH/SONET Subsystems
1. Configure the SDH/SONET subsystems on the CL modules to work with OC-3
framing, using Configuration> Physical Layer>CL>CL-A>SDH/SONET>Card
Configuration. Your selection is automatically copied to the other CL module.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1. Frame Structure
2. Tx Clock Based on SSM
3. Common PDH LVC Parameters >
(OC-3)
(Yes)
2. You will be asked to confirm: press Y.
3. You may leave the Common PDH LVC Parameters default values unchanged.
4. Configure CL module B the same as CL module A (repeat Steps 3, 4 on CL-B).
Configuring OC-3 Physical Ports
1. Enable OC-3 port 1 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 1.
5-70
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Up)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
2. Configure the OC-3 port 1 of CL module A for inband management using the
RAD proprietary management protocol, over DCC bits D4 to D12. Use
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration
1.
2.
3.
4.
In Band Management>
Routing Protocol >
Management DCC
>
Deviation Type
(HDLC)
(Proprietary RIP)
(D4-D12)
(Standard)
3. Disable OC-3 port 2 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 2.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 2
1.
2.
3.
4.
5.
6.
Admin Status
User Name
RDI on Fail
EED Threshold
SD Threshold
DCC Configuration
(Down)
... ()
(Enable)
>
(1E-3)
>
(1E-6)
>
4. Repeat Steps 1, 2, 3 above for the OC-3 ports of CL module B, using
Configuration>Physical Layer>CL>CL-B>SDH/SONET>Link 1 and Link 2.
Configuring the Timing and Clock Sources
1. Configure the timing mode of the SDH/SONET subsystem of CL module A to
use the recovered clocks from the active SONET link as reference source,
using Configuration> Physical Layer>CL>CL-A> SDH/SONET>Card
Configuration:
1. Select No for Tx Clock Based on SSM.
2. Select Rx Clock for SONET Tx Clock. The Master and Fallback sources are
automatically set to Link 1 (the only active link of the module).
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-71
Chapter 5 Configuring Typical Applications
Installation and Operation Manual
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1.
2.
3.
4.
5.
6.
Frame Structure
Tx Clock Based on SSM
SONET Tx Clock
Master Port
Fallback Port
Common PDH LVC Parameters
(OC-3 )
(No)
(Rx Clock)
(Link 1)
(Link 1)
>
>
>
>
2. Configure CL module B the same as CL module A (repeat Step 1 on CL-B).
3. Configure the system to use the timing of the SDH/SONET subsystem as the
clock source, using Configuration>System>Clock Source.
MP-4100
Configuration>System>Clock Source
1. Source
>
(S Subsystem)
Bypassing PDH Ports
1. To close the protection path through the SONET ring, it is necessary the
bypass the prescribed TUs between CL-A to CL-B. In this example, it is
necessary to bypass the TUs that carry the PDH 1 payload from Location A to
Location B. Start from OC-3 link 1 of the CL module A, using
Configuration>System>Mapping>CL-A>Link 1.
MP-4100
Configuration>System>Mapping>CL-A>Link 1
STS1-1
TU1
TU2
TUG2-1 None
None
TUG2-2 None
None
TUG2-3 None
None
TUG2-4 None
None
TUG2-5 None
None
TUG2-6 None
None
TUG2-7 None
None
->>
1. None
3. L1B-TU3
2. L2A-TU3
4. L2B-TU3
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
5. L1B-VT
6. L2A-VT
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
7. L2B-VT
3. Use the keyboard arrow keys to move the cursor to the TU to be
bypassed to CL module B.
4. Select L1B-VT. After pressing <Enter>, you will see the map of the other
active link, link 1 of CL module B.
5-72
Configuration Procedure for Typical SONET Transport Application
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 5 Configuring Typical Applications
MP-4100
Configuration>System>Mapping>CL-B>Link 1
TU1
TUG2-1 None
TUG2-2 None
TUG2-3 None
TUG2-4 None
TUG2-5 None
TUG2-6 None
TUG2-7 None
->>
1. SET
STS1-1
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
STS1-2
TU2
None
None
None
None
None
None
None
TU3
None
None
None
None
None
None
None
TU4
None
None
None
None
None
None
None
TU1
None
None
None
None
None
None
None
5. Use the keyboard arrow keys to move the cursor to the TU to be
bypassed to CL module A.
6. Select SET.
7. To save and activate the new configuration, press the % key.
8. Press Y to confirm. Configuration File Update Is In Process will appear at
the bottom of the screen while the database is being saved (a few
seconds).
Megaplex-4100 Ver. 2.0
Configuration Procedure for Typical SONET Transport Application
5-73
Chapter 5 Configuring Typical Applications
5-74
Configuration Procedure for Typical SONET Transport Application
Installation and Operation Manual
Megaplex-4100 Ver. 2.0
Chapter 6
Troubleshooting and
Diagnostics
This Chapter describes the Megaplex-4100 monitoring and diagnostic functions.
The available functions include:
•
Detection of configuration (sanity) errors
•
Alarm and event collection, and reporting of relevant alarms
•
Configuration error (sanity) messages
•
Collection of performance monitoring data
•
Diagnostic tests for checking transmission paths and IP connectivity.
These functions can be used to identify problems in the network incorporating
Megaplex-4100 units, test the proper operation of each Megaplex-4100 unit, and
locate rapidly the cause of the fault: within the Megaplex-4100 itself, in its
connections to the network or to a user’s equipment unit, or in the another
network component.
In addition to the general Megaplex-4100 functions described in this Chapter, you
can find information on the module-specific diagnostic functions in the
Installation and Operation Manual of each module.
If you need additional support for this product, see Section 6.6 for technical
support information.
6.1
Monitoring Performance
Megaplex-4100 supports the following types of monitoring activities:
•
Display performance monitoring statistics for the Megaplex-4100 physical and
virtual ports. The collected data enables the system administrator to monitor
the transmission performance, and thus the quality of service provided to
users, for statistical purposes. In addition, when problems are reported by
users served by Megaplex-4100, the collected data can be used for diagnostic
purposes, because it can help identify the source of the problem.
The data is continuously collected during equipment operation. For TDM
ports, the basic performance data is calculated for each second, and
accumulated and displayed over a 15-minute (900 second) interval. The data
accumulated within the last 24-hour interval is also stored and displayed.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-1
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
•
Display status information for system timing and control subsystems and for
physical and virtual ports
•
Display the current APS and path protection status for Megaplex-4100 with
CL.1/155 and CL.1/155GbE modules.
•
Read the alarm history recorded in the log file, and clear desired alarms
•
Read the current alarms. You can select the type of alarms to be displayed,
using various cross-sections to filter the relevant alarms.
The monitoring tasks are organized in accordance with three main types:
•
System
•
Physical Layer
•
Logical Layer.
The selection of the desired type of monitoring activity is made on the
Monitoring task selection screen. A typical screen is shown in Figure 6-1.
MP-4100
Monitoring
1. System
>
2. Physical Layer >
3. Logical Layer >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-1. Monitoring – Task Selection Screen
³
To select a monitoring activity:
Type its number and then press <Enter>.
Overview of Monitoring Menu
Figure 6-2 to Figure 6-5 show the typical structure of the Monitoring menu.
6-2
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Figure 6-2. Typical Monitoring Menu Structure (SDH) (Part 1 of 2) layer
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-3
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Figure 6-3. Typical Monitoring Menu Structure (SDH) (Part 2 of 2)
6-4
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Figure 6-4. Typical Monitoring Menu Structure (SONET) (Part 1 of 2)
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-5
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Monitoring
1. System
2. Physical Layer
3. Logical Layer
System
1. Active Alarms (ON)
2. Active Alarms (ALL)
3. Clear Alarms
4. History Alarms
5. Timing
6. CL Status
7. Remote Agents
8. APS
Typical
See
Part 1
I/O-3
1. Link 1
2. Link 2
3. Link 3
..
..
Logical Layer
Only for
E1 and T1 Ports
with CAS
1. I/O
2. CL
I/O Modules with
Ethernet
I/O
Physical Layer
1. I/O-1 (HS-U12)
2. I/O-2 (M8T1)
3. I/O-3 (M8T1)
1. I/O
2. CL
Link 1
1. E1 or T1 or SHDSL
2. Ethernet
SHDSL Only
Redundancy
Only
Status
1. Status
2. Statistics
3. Signaling
Signaling
Link 1
I/O-2
..
..
I/O Modules with
Ethernet
Current Interval
1. Current (15 min)
2. Select Interval (15 min)
3. Current (24 hours)
4. Select Interval (24 hours)
5. Clear Statistics
Select Interval
Total
Select Interval
Ethernet
1. ETH 1
2. ETH 2
3. ETH 3
ETH 1
Status
1. Status
2. Statistics
Statistics
CL
1. CL-A
2. CL-B
Station Clock
Ethernet
1. GbE 1
2. GbE 2
CL-A
1. Station Clock
2. Ethernet
3. SDH/SONET
Port Status
GbE 1
1. Port Status
2. ETH Counters
Timing
Link 1
SDH/SONET
1. Timing
2. Link 1
3. Link 2
4. Path Protection
1. Link Status
2. Link Statistics
3. DCC Statistics
4. Optical Parameters
Path Protection
ETH Counters
Link Status
Link Statistics
1. Current Interval
2. Select Interval
3. Total
Current Interval
Select Interval
Total
DCC Statistics
Optical Parameters
Figure 6-5. Typical Monitoring Menu Structure (SONET) (Part 2 of 2)
6-6
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Selecting a System Monitoring Task
Use the following procedure to select a desired system-level monitoring task.
There are two main groups of tasks:
•
Alarm handling tasks
•
Status monitoring tasks, regarding the timing subsystem, CL module status,
information regarding the remote management agents known to the
Megaplex-4100 management agent, and APS status when APS is in use.
To navigate to the required screen, use Monitoring>System.
A typical System task selection submenu is shown in Figure 6-6.
MP-4100
Monitoring>System
1.
2.
3.
4.
5.
6.
7.
8.
Active Alarms (ON) >
Active Alarms (ALL)>
Clear Alarms
>
History Alarms
[]
Timing
>
CL Status
[]
Remote Agents
[]
APS
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-6. Typical System Task Selection Submenu
³
To select the type of system-level monitoring task:
Type the desired number and then press <Enter>.
For details, refer to following Sections.
Displaying the Active Alarms
You can display the currently active state alarms by means of the Active Alarms
(ON) item.
Note
• A state alarm is an alarm that is in the ON state while a certain condition is
present, and automatically changes to OFF when the condition is no longer
present. This type of alarm cannot be cleared (removed from the alarm buffer)
while it is in the ON (active) state.
• An event alarm is an alarm that records the occurrence of an event. This type
of alarm can be cleared at any time.
Each alarm is displayed in a separate row, which lists from left to right:
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-7
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
•
The alarm code
•
The module, and where applicable, the port for which the alarm is reported
•
The alarm description – a short string that concisely explains the meaning of
the alarm code
•
The alarm severity
•
The number of times the alarm occurred
•
The masking status of the alarm: an M to the right of the alarm row indicates
that the corresponding alarm has been masked.
For a description of the alarms, refer to Handling Alarms and Traps.
³
To select the type of active alarms (ON) to be displayed:
1. Select Active Alarms (ON) on the Monitoring>System menu, and then press
<Enter>.
2. You will see the alarm screen. A typical screen is shown in Figure 6-7.
Note
To see the navigation options for this screen, select the ? (help) option.
MP-4100
Monitoring>System>Active Alarms (ON)
Alarm Description
(0026)PS-B
(2021)CL-A
| (0026)CL-B
v (2007)IO-1
(0026)IO-2
(2007)IO-3
(0026)IO-4
MODULE TYPE MISMATCH
CL FAN FAILURE
MODULE TYPE MISMATCH
BUS CLOCK FAILURE
MODULE TYPE MISMATCH
BUS CLOCK FAILURE
MODULE TYPE MISMATCH
MAJOR
MAJOR
MAJOR
MAJOR
MAJOR
MAJOR
MAJOR
1
1
1
1
1
1
1
M
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
Figure 6-7. Typical Active Alarms (ON) Screen
3. You can clear the alarm buffer by typing C (clear). In response, you will see an
ALARM BUFFER CLEANED message, and the number of alarms in the buffer,
appearing at the top right-hand corner of the screen, decreases accordingly.
³
To display the active alarms (ON):
An alternative display mode for the currently active alarms is the ALL mode, which
includes both state alarms and event alarms.
You can display the currently active alarms in three cross-sections:
6-8
•
All the alarms
•
Alarms at the system level
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
•
Chapter 6 Troubleshooting and Diagnostics
Alarms related to a specific chassis slot.
In addition, you can mask alarms, and clear the alarm buffer. For a description of
all the alarms, refer to Section 6.3.
³
To select the type of active alarms (ALL) to be displayed:
1. Select Active Alarms (ALL) on the Monitoring>System menu, and then press
<Enter>.
2. You will see the Active Alarms (ALL) type selection screen. A typical screen is
shown in Figure 6-8. Next to each option, you can see the highest alarm
severity that is currently active.
MP-4100
Monitoring>System>Active Alarms (ALL)
1. All Alarms
(MAJOR)
2. System Alarms (EVENT)
3. Slot Alarms
[]>
[]>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-8. Typical Active Alarms (ALL) Type Selection Screen
3. Type the desired alarm type number, and then press <Enter>.
Note
³
To see the navigation options for this screen, select the ? (help) option.
To display all alarms, and system alarms:
1. A typical screen for the All Alarms selection is shown in Figure 6-9. The
System Alarms screen is similar.
In most cases, the number of alarms exceeds the maximum that can be
displayed on one page, and therefore you may have to scroll down to the
page containing the alarm of interest.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-9
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>System>Active Alarms (ALL)>All Alarms
Alarm Description
(0001)
(0026)PS-B
| (2021)CL-A
v (0026)CL-B
(2007)IO-1
(0022)IO-1
(0026)IO-2
Installation and Operation Manual
(MAJOR)
MODULE TYPE MISMATCH
CL FAN FAILURE
MODULE TYPE MISMATCH
BUS CLOCK FAILURE
MODULE WAS INSERTED
MODULE TYPE MISMATCH
OFF
MAJOR
MAJOR
MAJOR
MAJOR
EVENT
MAJOR
0
1
1
1
1
1
1
Alarm Mask
No
Temporary
No
No
No
No
No
1. No
2. Temporary
3. Permanent
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-9. Typical Active Alarm (ALL) – All Alarms Screen
2. Each alarm is displayed in a separate row, which lists from left to right:
ƒ
The alarm code
ƒ
The module and port for which the alarm is reported
ƒ
The alarm description – a short string that concisely explains the meaning
of the alarm code
ƒ
The alarm severity
ƒ
The number of times the alarm occurred.
The screen has an additional field, Alarm Mask, which displays the current
attribute of each alarm: Normal, Temporary, Permanent.
The description of the various attributes appears in the Use – Selecting the
Alarms Attribute section of Chapter 4.
Note
To see the navigation options for this screen, select the ? (help) option.
3. After displaying the desired set of alarms, you have the option to modify the
attribute of each alarm. The attribute modification menu is located under the
alarms list.
Note
ƒ
To change the attribute of an alarm, scroll to the desired alarm
ƒ
Type the number of the desired attribute. The corresponding attribute of
the currently selected alarm changes to reflect the new selection.
It is not possible to invert event alarms, but only state alarms.
4. You can clear the alarm buffer by typing C (clear). In response, you will see an
ALARM BUFFER CLEANED message, and the number of alarms in the buffer,
appearing at the top right-hand corner of the screen, decreases accordingly.
6-10
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 6 Troubleshooting and Diagnostics
To display slot alarms:
1. For the Slot Alarms option, you will see the slot alarm status screen. A typical
screen is shown in Figure 6-10.
The screen lists the highest alarm severity present in each slot.
MP-4100
Monitoring>System>Active Alarms (ALL)>Slot Alarms
PS-A
PS-B
CL-A
CL-B
IO-1
IO-2
IO-3
(OFF) (PS)
(OFF) (PS)
(MAJOR) (CL1/155GbE)
(MAJOR) (CL1/155GbE)
(MAJOR) (M8E1)
(MAJOR) (M8E1)
(MAJOR) (M8T1)
>
>
>
>
>
>
>
IO-4
IO-5
IO-6
IO-7
IO-8
IO-9
IO-10
(MAJOR) (M8E1)
(MAJOR) (M8SL)
(OFF) (-------------)
(OFF) (-------------)
(OFF) (-------------)
(OFF) (-------------)
(OFF) (-------------)
>
>
>
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-10. Typical Slot Alarms Status Screen
³
To clear the history alarms:
1. Select Clear Alarms on the Monitoring>System menu, and then press <Enter>.
³
To display the recent history alarms:
1. Select History Alarms on the Monitoring>System menu, and then press
<Enter>.
2. You will see the History Alarms screen. A typical History Alarms screen is
shown in Figure 6-11.
MP-4100
Monitoring>System>History Alarms
Alarm Description
(0020)CL-A
INTERNAL ERROR (26990649)
(0003)
ACTIVE DB HAS BEEN UPDATED
| (0025)IO-3
NOT PROGRAMMED MODULE
v (0025)IO-2
NOT PROGRAMMED MODULE
(0026)IO-1
MODULE TYPE MISMATCH
(0026)CL-B
MODULE TYPE MISMATCH
EVENT
EVENT
OFF
OFF
MAJOR
MAJOR
13-08-2099
13-08-2099
13-08-2099
13-08-2099
13-08-2099
13-08-2099
02:33:08
02:15:09
02:15:09
02:15:09
02:15:09
02:15:09
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-11. Typical History Alarms Screen
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-11
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
3. To view the alarms, scroll as required. You can see all the navigation options
for this screen by selecting the ? (help) option.
Monitoring the Timing Source Status
Use the following procedure to display information on the current Megaplex-4100
timing source.
To navigate to the required screen, use Monitoring>System>Timing.
³
To display the timing:
1. Select Timing on the Monitoring>System menu, and then press <Enter>.
2. You will see the Timing screen. The information displayed on the screen
depends on the currently used timing source. A typical Timing monitoring
screen is shown in Figure 6-12.
For a description of the information displayed on this screen, refer to the
Configuring System Clock Sources section in Chapter 4.
MP-4100
Monitoring>System>Timing
Timing
.... (S Subsystem)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-12. Typical Timing Monitoring Screen
Monitoring the CL Module Status
Use the following procedure to display information on the CL modules installed in
the Megaplex-4100, and the system status information.
To navigate to the required screen, use Monitoring>System>CL Status.
³
To display the CL module status:
1. Select CL Status on the Monitoring>System menu, and then press <Enter>.
2. You will see the CL Status screen. A typical CL Status screen is shown in
Figure 6-13.
6-12
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>System>CL Status
System Control Activity
Test Status
Alarm Severity
Configuration File Usage (%)
Active DB
DB Checksum
Last DB Update
CL Temperature (C)
CL-A
ON LINE
OFF
OFF
10
1
1467
01/12/05 00:02:16
32
CL-B
NOT EXISTS
OFF
OFF
0
-0
00/00/00 00:00:00
0
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-13. Typical CL Status Screen
3. The screen displays the following information:
System Control
Activity
Displays the state of each CL module used by the
system:
• ON LINE – indicates the active (master) module.
• OFF LINE – indicates the standby (slave) module.
• NOT EXISTS – the module is not installed.
Test Status
Indicates whether tests are present in the system.
Alarm Severity
Indicates the type of the most severe alarm that exists
in the system: CRITICAL, MAJOR, MINOR, or EVENT. OFF
means that no alarm has been reported.
Configuration File
Usage
Displays the percentage of the total capacity of the
corresponding CL module flash memory currently
assigned to configuration files.
Active DB
Displays the database number currently in use.
DB Checksum
Displays the database checksum, used to detect
corruption.
Last DB Update
Indicates the date and time of the last database update.
CL Temperature
The internal temperature of the CL module, in degrees
Celsius, as indicated by an internal temperature sensor.
Monitoring the Megaplex-4100 Remote Agents
Use the following procedure to display information on the remote management
agents known to the management agent of the Megaplex-4100.
To navigate to the required screen, use Monitoring>System>Remote Agents.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-13
Chapter 6 Troubleshooting and Diagnostics
³
Installation and Operation Manual
To display the remote agents:
1. Select Remote Agents on the Monitoring>System menu, and then press
<Enter> to display the Remote Agents screen. A typical screen is shown in
Figure 6-14.
MP-4100
Monitoring>System>Remote Agents
IP Address
MUX Name
Physical Distance
Logical Distance
Interface
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-14. Typical Remote Agents Screen
2. The screen shows the following information:
IP Address
The IP address of the corresponding remote agent.
Mux Name
The logical name (maximum 8 alphanumeric characters)
assigned to the corresponding agent.
Physical
Distance
Metric that indicates the number of hops (through the
management network) to the corresponding remote agent.
Logical
Distance
Metric that indicates the logical distance (through the
management network) to the remote agent; used, among
other factors, in the selection of the optimal route to be used
for the management traffic. The distance calculation also takes
into account the quality of the line.
Interface
Slot and port through which the communication with the
corresponding remote agent has been established.
Monitoring the APS Status
Use the following procedure to display information on the APS function on this
Megaplex-4100.
To navigate to the required screen, use Monitoring>System>APS.
³
To display APS status:
1. Select APS on the Monitoring>System screen, and then press <Enter>. A
typical screen is shown in Figure 6-15.
6-14
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>System>APS
APS Group Id
>
APS Mode
>
Current Working Slot >
Current Working Port >
(A1-A2)
(1+1 Uni-Directional)
(CL-A)
(Link 1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-15. Typical APS Monitoring Screen
2. The screen provides information on the configured APS group, the state of
the APS function, and the configured working module slot and port.
Refer to the Configuration – APS section in Chapter 4 for a description of the
displayed parameters.
Selecting Virtual Ports for Monitoring
Use the following procedure to select the type of virtual ports for which
monitoring information will be displayed.
To navigate to the required screen, use Monitoring>Virtual Ports.
A typical Logical Layer submenu is shown in Figure 6-16. This screen includes two
options:
I/O
For displaying performance monitoring for the virtual ports of the
modules installed in I/O slots. The parameters available for these
modules depend on the module type.
For additional information, refer to the Monitoring Virtual Ports on I/O
Modules section.
Note
CL
Megaplex-4100 Ver. 2.0
Some I/O modules do not have virtual ports, or no
monitoring activities are available for their ports.
For displaying performance monitoring and status parameters for the
virtual ports located on the CL.1/155 or CL.1/155GbE modules. Refer
to Monitoring Virtual Ports on CL Modules section on page 6-19.
Monitoring Performance
6-15
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Logical Layer
1. I/O>
2. CL >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-16. Typical Logical Layer Type Selection Submenu
³
To select the type of virtual ports to be monitored:
Type the desired number and then press <Enter>.
Monitoring Virtual Ports on I/O Modules
Selecting a Virtual Port or Bundle for Monitoring
Use the following procedure to select the I/O virtual port for which you want to
display the performance monitoring data.
The selection is made in two steps:
1. Select a specific I/O module
2. Select a specific virtual port or bundle terminated on the selected I/O module.
To navigate to the required screen, use Monitoring>Logical Layer>I/O
³
To select a virtual port on an I/O module:
1. On the screen of Figure 6-16, select I/O and then press <Enter>.
2. You will see the I/O module selection screen. A typical screen is shown in
Figure 6-17. The screen includes only I/O modules installed in the chassis that
have virtual ports.
6-16
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Logical Layer>I/O
1. I/O 1 (HS-U12)>
2. I/O 2 (M8SL)>
3. I/O 3 (M8SL)>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-17. Typical I/O Slot Selection Screen for Modules with Virtual Ports
3. Select a module from the list by typing the number corresponding to its slot,
and then press <Enter>.
4. You will see the virtual port selection screen for the selected module. The
ports appearing on the screen depend on the module type. For I/O modules
with Ethernet ports, you may also see a Bundles option: this option appears
when bundles are configured on the module ports. The screen includes only
active ports and/or bundles (Admin Status=UP).
A typical screen for an M8SL module with bundles terminated on its internal
E1 ports is shown in Figure 6-18.
MP-4100
Monitoring>Logical Layer >I/O>I/O 3 (M8SL/E1)
1.
2.
3.
4.
E1 1
E1 5
E1 6
Bundles
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-18. Typical I/O – Virtual Port Selection Screen
Displaying I/O Virtual Port Monitoring Data
Use the following procedure to select the desired performance statistics view,
and clear statistics for the corresponding port.
The supported performance views include:
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-17
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
•
Current 15-minute interval
•
A previous 15-minute interval within the last 24 hours, for which valid
performance data exists
•
Current 24-hour interval
•
For SHDSL ports: a previous 24-hour interval within the last 7 days, for which
valid performance data exists.
For E1 ports of M8SL modules that use CAS (that is, G.732S or G.732S-CRC4
framing), you can also display the signaling information associated with each
timeslot.
To navigate to the required screen, use Monitoring>Logical Layer>I/O.
Displaying Performance Monitoring Statistics for I/O Module Virtual
Ports
³
To select the I/O module performance monitoring interval:
1. On the Slot screen, select the desired port, and then press <Enter>.
2. You will see the port monitoring interval selection screen. A typical selection
screen, which shows all the supported selections, appears in Figure 6-19.
MP-4100
Monitoring>Logical Layer>I/O>I/O 3 (M8SL)>E1 1
1.
2.
3.
4.
5.
Current (15 min)
>
Select Interval(15 min) >
Current (24 hours)
>
Select Interval(24 hours)>
Clear Statistics
>
*
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-19. Typical Virtual Port I/O Performance Monitoring Interval Selection Screen
3. The information displayed after selecting a specific performance view
depends on the module type. Refer to the module Installation and Operation
Manual for detailed information.
4. To clear (reset to 0) the performance statistics counters for the selected
port, select Clear Statistics: after pressing <Enter>, you will see a
confirmation message. Press <ESC> to continue.
Note
6-18
Clearing the statistics counters does not clear the data collected for other ports.
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Displaying Signaling Information for I/O Module E1 Virtual Ports
³
To monitor the signaling information for an E1 virtual port (M8SL modules only):
1. On the port selection screen of an M8SL module (Figure 6-18), select the
desired E1 port, and then press <Enter>.
2. On the E1 port task selection screen of the selected E1 port, select Signaling
and then press <Enter>.
3. You will see the Signaling monitor screen.
The screen includes several pages, where each page presents the signaling
information for 8 timeslots. A typical first page is shown in Figure 6-20: scroll
down to see the other pages (to see the navigation options, select? (help)).
The screen presents information only for connected voice timeslots: for other
timeslots, you will see only ––––.
MP-4100
Monitoring>Logical Layer>I/O>I/O-5 (M8SL)>E1 1>Signaling
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
Rx From Link
------------0000
0000
-------
Tx To CL
------------0101
0101
-------
Rx From CL
------------0000
0000
-------
Tx To Link
------------0000
0000
-------
Type
DATA
VOICE
VOICE
-
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-20. Typical Signaling Monitor Screen for E1 Virtual Port
Table 6-1. Signaling Monitoring Parameters
Parameter
Description
Ts#
The timeslot number within the E1 frame
Rx from Link
The ABCD signaling bits received from the E1 link
Tx to CL
The ABCD signaling bits transmitted to the CL module, after processing by the E1
port in accordance with the signaling profile configured for the corresponding port
Rx from CL
The ABCD signaling bits received from the CL module, intended for transmission
through the E1 port (after processing in accordance with the signaling profile
configured for the corresponding port)
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-19
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Parameter
Description
Tx to Link
The ABCD signaling bits transmitted through the E1 port (after processing in
accordance with the signaling profile configured for the corresponding port)
Type
The configured timeslot type:
•
DATA – Data timeslot (no signaling is associated with this type of
timeslot)
•
VOICE – Voice timeslot (timeslot with channel-associated signaling)
•
MNG – Timeslot dedicated to inband management (no signaling is
associated with this type of timeslot)
•
UNI BRD D – Unidirectional broadcast timeslot carrying data (no signaling
is associated with this type of timeslot)
•
UNI BRD V – Unidirectional broadcast timeslot carrying voice (timeslot with
channel-associated signaling)
•
RESERVED – Reserved for future assignment (no signaling is associated
with this type of timeslot).
4. The displayed signaling status is correct at the time the request had been
received by the Megaplex-4100: to refresh the display, press <ESC> to return
to the E1 port task selection screen and then to send again the request.
Displaying Performance Monitoring Statistics for I/O Module
Bundles
1. On the port selection screen (Figure 6-18), select Bundles.
2. You will see the Bundles selection screen, which lists the bundles terminated
in the selected I/O module.
3. Select the desired bundle, and then press <Enter>. A typical bundle
performance monitoring screen is shown in Figure 6-21.
The information displayed on the screen, which is accumulated continuously,
is automatically refreshed every few seconds. You can type F or B to scroll
between the other bundles on the selected I/O module.
You can clear the displayed statistics (that is, reset the displayed
performance monitoring counters) by typing C. The counters are also reset
when the Megaplex-4100 is powered up.
The performance monitoring counters displayed on the screen are explained
in Table 6-2. In addition to these counters, you can also read the time (as
retrieved from the Megaplex-4100 internal real-time clock) at which the
counters have been last reset.
6-20
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Logical Layer>I/O>I/O-2 (M8E1)>Bundles>Bundle 1
E1
=============
Rx statistics
=============
Total Frames
Total Octets
Total Errors
... (1)
... (0)
... (0)
... (0)
Tx statistics
=============
Total Frames
...
Total Octets
...
Total Errors
...
Congestion Dropped...
(0)
(0)
(0)
(0)
>
C-Clear; %-Db Update; #-Db Undo; F-Fwd; B-Bkwd
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-21. Typical Bundle Performance Monitoring Screen
Table 6-2. Bundle Performance Monitoring Statistics
Parameter
Description
Rx Statistics – Total
Frames
Total number of frames received through the bundle
Rx Statistics – Total
Octets
Total number of data octets carried by all the frames received through the bundle
Rx Statistics – Total
Errors
Total number of frames with error received through the bundle
Tx Statistics – Total
Frames
Total number of frames transmitted through the bundle
Tx Statistics – Total
Octets
Total number of data octets carried by all the frames transmitted through the bundle
Tx Statistics – Total
Errors
Total number of frames with error transmitted through the bundle
Tx Statistics –
Congestion Dropped
Total number of valid frames that were intended for transmission through the
bundle that have been discarded because congestion at the output
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-21
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Monitoring Virtual Ports on CL Modules
Selecting a CL Virtual Port for Monitoring
Virtual ports are located only on CL.1/155 and CL.1/155GBE modules.
³
To select the CL.1/155 or CL.1/155GBE virtual ports for performance monitoring:
1. Select a specific CL module. This selection is necessary only when the
Megaplex-4100 is equipped with two CL.1/155 or CL.1/155GbE modules.
2. Select a type of port on the selected module.
3. Select a specific virtual port on the selected module. The available selections
depend on the link standard, SDH or SONET, and on the use of virtual
concatenation.
To navigate to the required screen, use Monitoring>Logical Layer>CL.
A typical CL selection screen is shown in Figure 6-22.
MP-4100
Monitoring>Logical Layer>CL
1. CL-A >
2. CL-B >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-22. Typical Virtual Port CL Module Selection Screen
³
To select a CL module virtual port:
1. Select the desired CL module on the CL module selection screen, and then
press <Enter>.
2. You will see the port type selection screen for the corresponding CL module.
A typical screen for CL-A is shown in Figure 6-23. VCAT appears only when
virtually concatenated groups have been configured and mapped on the
corresponding CL module.
6-22
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Logical Layer>CL>CL-A
1. SDH/SONET
2. PDH
3. VCAT
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-23. Typical CL Virtual Port Type Selection Screen
3. After selecting a port type, select a specific virtual port on the corresponding
screen:
ƒ
A typical screen for SDH/SONET virtual ports is shown in Figure 6-24.
ƒ
A typical screen for PDH virtual ports is shown in Figure 6-25. The screen
includes several pages: use the N and P keys to scroll.
ƒ
A typical screen for virtually concatenated groups is shown in Figure 6-26.
The screen displays only the configured virtually concatenated groups
(maximum 8).
MP-4100
Monitoring>Logical Layer>CL>CL-A >SDH/SONET
1. Link 1
2. Link 2
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-24. Typical SDH/SONET Virtual Port Selection Screen
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-23
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Logical Layer>CL>CL-A >PDH
1.
2.
3.
4.
5.
6.
PDH
PDH
PDH
PDH
PDH
PDH
1
2
3
5
7
9
>
>
>
>
>
>
... (N)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-25. Typical PDH Virtual Port Selection Screen
MP-4100
Monitoring>Logical Layer>CL>CL-A>VCAT
1.
2.
3.
4.
5.
6.
VCG
VCG
VCG
VCG
VCG
VCG
1>
2>
3>
6>
7>
8>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-26. Typical VCG Virtual Port Selection Screen
Monitoring SDH/SONET Virtual Ports
Megaplex-4100 supports the collection of monitoring data for the following
SDH/SONET virtual ports:
•
High-order virtual ports: VC-4 for SDH links, and STS-1 for SONET links
•
Low-order virtual ports: VC-3 and VC-12 for SDH links and VT1.5 for SONET
links.
Typical screens are shown in Figure 6-27. When VT1.5 virtual ports are used, the
VC-12 option is replaced by VT1.5/VC-12.
6-24
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Logical Layer>CL>CL-A >SDH/SONET>Link 1
1. VC-4>
2. VC-3>
3. VC-12>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. SDH Links
MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1
1.
2.
3.
4.
VT1.5
STS1-1
STS1-2
STS1-3
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. SONET Links
Figure 6-27. Typical Logical Layer Link Statistics Selection Screens
Monitoring – VC-4 and STS-1 Virtual Ports
The VC-4 and STS-1 virtual port monitoring tasks include:
•
Display port status
•
Display port performance monitoring statistics for the VC-4 or STS-1 level.
The performance data is collected over 15-minute intervals, and up to 97 of
the most current intervals are stored for retrieval. The performance
monitoring information is lost when the Megaplex-4100 is powered down.
A typical VC-4 port task selection screen is shown in Figure 6-28. The STS-1
screen is similar, except that it also identifies the specific STS-1 (1, 2, or 3). The
type of port is identified in the screen header.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-25
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
VC4
1. Port Status
>
2. Port Statistics >
>
The statistic is for connected ports
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-28. Typical VC-4 or STS-1 Port Task Selection Screen
³
To display the status of the VC-4 or STS-1 virtual port:
1. Select Port Status on the VC-4 or STS-1 Port task selection screen and then
press <Enter>.
2. You will see the Port Status screen. A typical Port Status screen is shown in
Figure 6-29.
MP-4100
Port Status
B249
J1 Received... ()
C2 Received[0 - 255]... (0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-29. Typical VC-4 or STS-1 Port Status Virtual Port Screen
The parameters displayed on the Port Status screen are explained in Table 6-3.
Table 6-3. VC-4 or STS-1 Port Status Virtual Port Parameters
³
Parameter
Description
J1 Received
Displays the received J1 string
C2 Received
Displays the received C2 byte (signal label)
To display the VC-4 or STS-1 virtual port statistics:
1. Select Port Statistics on the VC-4 or STS-1 Port task selection screen and
then press <Enter>.
2. You will see the VC-4 or STS-1 statistics interval selection screen. The STS-1
screen is similar, except that it also identifies the specific STS-1 (1, 2, or 3). A
typical VC-4 interval selection screen is shown in Figure 6-30.
6-26
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Port Statistics
1. Current Interval>
2. Select Interval >
3. Total
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-30. Typical VC-4 or STS-1 Interval Selection Screen
³
To display VC-4 or STS-1 performance monitoring data for the current interval:
1. Select Current Interval and then press <Enter>.
2. You will see the Current Interval performance monitoring screen for the VC-4.
A typical screen is shown in Figure 6-31. The STS-1 screen is similar, except
that it also identifies the specific STS-1 (1, 2, or 3).
MP-4100
Current Interval
Valid Intervals [0 - 96]... (48)
Elapsed time
... (00:00:00)
ES
... (0)
SES
... (0)
UAS (SEFS)
... (0)
CV
... (0)
>
C - Clear
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-31. Typical Current Interval VC-4 or STS-1 Performance Monitoring Screen
The information displayed on the performance monitoring screen is explained in
Table 6-4.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-27
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-4. Virtual Port Performance Monitoring Data
Parameter
Description
Valid Intervals
The number of intervals (up 96 intervals) for which performance monitoring information
can be displayed.
Elapsed Time
The elapsed time (minutes and seconds) since the beginning of the current interval, in
seconds. The range is 1 to 15 minutes.
ES
Displays the number of errored seconds (ES) in the current interval.
An errored second is any second containing one or more of the following types of errors:
•
ƒ
A SEF defect is declared after detection of four contiguous errored frame
alignment words.
ƒ
The SEF defect is terminated when two contiguous error-free frame words are
detected.
•
Loss of Signal (LOS) defect:
ƒ
A LOS defect is declared after when no transitions are detected in the incoming
line signal (before descrambling) during an interval of 2.3 to 100 microseconds.
ƒ
The LOS defect is terminated after a 125-microsecond interval (one frame) during
which no LOS defect is detected.
•
SES
Severely Errored Frame (SEF) defect (also called Out-of-Frame (OOF) event):
Loss of Pointer (LOP) defect:
ƒ
A LOP defect is declared after no valid pointer is detected in eight consecutive
frames. The LOP defect will not be reported while an AIS signal is present.
ƒ
The LOP defect is terminated after a valid pointer is detected.
•
Alarm Indication Signal (AIS) received in the SDH overhead.
•
Coding Violation (CV): a coding violation is declared when a Bit Interleaved
Parity (BIP) error is detected in the incoming signal. The BIP information is
collected using the B1 byte in the Section Overhead.
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second during which multiple error events of the types taken into
consideration for an ES have occurred.
UAS (SEFS)
Displays the number of unavailable seconds (UAS (SEFS)) in the current interval.
An unavailable second is any second in which one or more SEF defects have been
detected.
CV
Displays the number of coding violations (CV) in the current interval.
Interval Number
The number of the 15-minute interval to be displayed, in the range of 1 to 96. This field
appears only for the Select Interval screen.
The default value is “1”, which designates the current interval. However, you can also
select another interval, by typing its number (0 to 96) and then pressing <Enter>: you can
then enter the desired interval number, up to the number displayed in the Valid Intervals
field.
The information displayed on the screen for the current interval is automatically
refreshed every five seconds.
6-28
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
You can clear the displayed parameters (that is, reset the displayed performance
monitoring counters) by typing C. Note however that clearing the data does not
clear the VC-4 or STS-1 data collected for other intervals or for other VCs, nor the
number of valid intervals and the start time.
³
To display VC-4 or STS-1 performance monitoring data on a selected interval:
1. Select Select Interval on the VC-4 interval selection screen (Figure 6-30) and
then press <Enter>.
2. You will see the Select Interval performance monitoring screen for the VC-4. A
typical screen is shown in Figure 6-32. The STS-1 screen is similar, except
that it also identifies the specific STS-1 (1, 2, or 3).
MP-4100
Select Interval
Valid Intervals [0 - 96]... (48)
Elapsed time
... (00:00:00)
ES
... (0)
SES
... (0)
UAS (SEFS)
... (0)
CV
... (0)
1. Interval Number [0 - 96]... (0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-32. Typical Select Interval VC-4 or STS-1 Performance Monitoring Screen
3. Select the desired interval, by typing 1 and pressing <Enter>: you can then
enter the desired interval number, up to the number displayed in the Valid
Intervals field.
4. After pressing <Enter>, the data displayed on the screen is updated in
accordance with your selection.
For a description of the displayed parameters, refer to Table 6-4.
You can clear the displayed parameters (that is, reset the displayed performance
monitoring counters) for the current interval by typing C. Note however that
clearing the data does not clear the data collected for other intervals, nor the
total data.
³
To display the totaled VC-4 or STS-1 performance monitoring data:
1. Select Total on the VC-4 or STS-1 interval selection screen (Figure 6-30) and
then press <Enter>.
2. You will see the Total performance monitoring screen for the VC-4 or STS-1.
A typical screen is shown in Figure 6-33.
For a description of the displayed parameters, refer to Table 6-4.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-29
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Total
Valid Intervals [0 - 96]... (48)
Elapsed time
... (00:00:00)
ES
... (0)
SES
... (0)
UAS (SEFS)
... (0)
CV
... (0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-33. Typical Total VC-4 or STS-1 Performance Monitoring Screen
Monitoring – VC-3 Virtual Ports
The VC-3 virtual port monitoring tasks include:
•
Display the port status of a selected VC-3
•
Display of port performance monitoring statistics for a selected VC-3. You can
display performance monitoring statistics only on connected (mapped) VC-3
ports.. The performance data is collected over 15-minute intervals, and up to
97 of the most current intervals are stored for retrieval. The performance
monitoring information is lost when the Megaplex-4100 is powered down.
A typical VC-3 task selection screen is shown in Figure 6-34.
MP-4100
VC-3
1. Port Status
2. Port Statistics
>
>
>
The statistic is for connected ports
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-34. Typical VC-3 Virtual Port Task Selection Screen
³
To display the status of a VC-3 virtual port:
1. Select Port Status on the VC-3 Port task selection screen and then press
<Enter>.
6-30
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
2. You will see the Port Status screen. A typical Port Status screen is shown in
Figure 6-35.
MP-4100
Port Status
J1 Received
...
C2 Received
...
1. VC Port[1 – 3] ...
(48)
(0)
(1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-35. Typical VC-3 Port Status Virtual Port Screen
The information displayed on the Port Status screen includes the following items:
³
•
VC Port: used to select the VC-3 port for which the port statistics data is
displayed. The allowed range is 1 to 3, however only connected (mapped)
ports may be selected. If you select an unconnected port, the Valid Intervals
field displays Error.
•
The other items are explained in Table 6-3.
To display the VC-3 virtual port statistics:
1. Select Port Statistics on the VC-3 Port task selection screen and then press
<Enter>.
2. You will see the VC-3 statistics interval selection screen. Figure 6-36 shows a
typical VC-3 interval selection screen.
MP-4100
Port Statistics
1. Current Interval>
2. Select Interval >
3. Total
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-36. Typical VC-3 Interval Selection Screen
³
To display VC-3 performance monitoring data for the current interval:
1. Select Current Interval on the VC-3 interval selection screen and then press
<Enter>.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-31
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
2. You will see the Current Interval port statistics screen for VC-3s. A typical
screen is shown in Figure 6-37.
The information displayed for the current interval port statistics screen includes
the following items:
³
•
Item 1 – VC Port: used to select the VC-3 port for which the port statistics
data is displayed. The allowed range is 1 to 3, however only connected ports
may be selected. If you select an unconnected port, the Valid Intervals field
displays Error.
•
The other items are explained in Table 6-4.
To display VC-3 performance monitoring data on a selected interval:
Select Select Interval on the VC-3 interval selection screen and then press
<Enter>.
Except for first selecting a specific VC-3 port, use the procedure described on
page 6-29 for VC-4.
³
To display totaled VC-3 performance monitoring data:
Select Total on the VC-3 interval selection screen and then press <Enter>.
Except for first selecting a specific VC-3 port, use the procedure described on
page 6-30 for VC-4.
MP-4100
Current Interval
Valid Interval
Elapsed time
ES
SES
UAS (SEFS)
CV
1. VC Port[1 - 3]
...
...
...
...
...
...
...
(52)
(00:00:00)
(0)
(0)
(0)
(0)
(48)
>
C - Clear
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-37. Typical Current Interval Port Statistics Screen for VC-3s
Monitoring – VC-12 or VT1.5 Virtual Ports
The low-order virtual port monitoring tasks include:
6-32
•
Display the port status of a selected VC-12 or VT1.5
•
Display of port performance monitoring statistics for a selected VC-12 or
VT1.5. You can display performance monitoring statistics only on connected
(mapped) VC-12 or VT1.5 ports. The performance data is collected over
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
15-minute intervals, and up to 97 of the most current intervals are stored for
retrieval. The performance monitoring information is lost when the
Megaplex-4100 is powered down.
A typical VC-12 or VT1.5 task selection screen is shown in Figure 6-38.
MP-4100
VC-12
1. Port Status
>
2. Port Statistics>
>
The statistic is for connected ports
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-38. Typical VC-12 or VT1.5 Virtual Port Task Selection Screen
³
To display the status of a VC-12 or VT1.5 virtual port:
1. Select Port Status on the VC-12 or VT1.5 port task selection screen and then
press <Enter>.
2. You will see the Port Status screen. Typical Port Status screens are shown in
Figure 6-39 and Figure 6-40.
MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1>VC-12>Port Status
J2 Received
... (10)
V5 (Bits 5-7) Received... (48)
1. VC Port[1 - 63]
... (1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-39. Typical VC-12 Port Status Virtual Port Screen (Megaplex-4100 with E1 Ports)
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-33
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1>VT1.5>Port Status
J2 Received
... (Error)
V5 (Bits 5-7) Received... (Error)
1. VT Port[1 - 84]
... (1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-40. Typical VT1.5 Port Status Virtual Port Screen (Megaplex-4100 with T1 Ports)
The information displayed on the Port Status screen includes the following items:
•
VC Port or VT port: used to select the VC-12 or VT1.5 port for which the port
statistics data is displayed.
The allowed range is 1 to 63 when the Megaplex-4100 uses SDH links, and 1
to 84 when Megaplex-4100 uses SONET links. Note however that only
connected ports may be selected. If you select an unconnected port, the
Valid Intervals field displays Error.
•
J2 Received: explained in Table 6-5
•
V5 (Bits 5-7) Received: explained in Table 6-5.
Table 6-5. VC-12 Port Status Virtual Port Status Parameters
³
Parameter
Description
J2 Received
Displays the received J2 string
V5 (Bits 5-7) Received
Displays the bits 5 to 7 of the received V5 byte, which carry
the signal label
To display the VC-12 or VT1.5 virtual port statistics:
1. Type Port Statistics on the VC-12 or VT1.5 Port task selection screen and
then press <Enter>.
2. You will see the VC-12 or VT1.5 statistics interval selection screen. A typical
interval selection screen is shown in Figure 6-41.
6-34
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Port Statistics
1. Current Interval>
2. Select Interval >
3. Total
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-41. Typical Interval Selection Screen
³
To display VC-12 or VT1.5 performance monitoring data for the current interval:
1. Select Current Interval and then press <Enter>.
2. You will see the Current Interval port statistics screen for VC-12s or VT1.5s.
A typical screen is shown in Figure 6-42. The STS-1 screen is similar, except
that it also identifies the specific STS-1 (1, 2, or 3).
MP-4100
Current Interval
Valid Intervals...
Elapsed time
...
ES
...
SES
...
UAS (SEFS)
...
CV
...
1. VC Port[1 - 63]...
2. Interval Number...
(48)
(00:00:00)
(0)
(0)
(0)
(0)
(0)
(0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-42. Typical Current Interval Port Statistics Screen for VC-12s
The information displayed for the current interval port statistics screen includes
the following items:
•
VC Port or VT Port: used to select the VC-12 port for which the port statistics
data is displayed. The allowed range is 1 to 63 when the Megaplex-4100 is
equipped with SDH links, and 1 to 84 for a Megaplex-4100 with SONET links.
Note however that only connected ports may be selected. If you select an
unconnected port, the Valid Intervals field displays Error.
•
The other items are explained in Table 6-4.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-35
Chapter 6 Troubleshooting and Diagnostics
³
Installation and Operation Manual
To display VC-12 or VT1.5 performance monitoring data on a selected interval:
1. Select Select Interval and then press <Enter>.
2. Except for first selecting a specific VC-12 or VT1.5 port, use the procedure
described on page 6-29 for VC-4 or STS-1.
³
To display totaled VC-12 or VT1.5 performance monitoring data:
1. Select Total and then press <Enter>.
2. Except for first selecting a specific VC-12 or VT1.5 port, use the procedure
described on page 6-30 for VC-4 or STS-1.
Displaying WAN Intervals Parameters
The performance monitoring statistics for the WAN side of the selected virtually
concatenated group depend on the encapsulation mode selected for the group:
LAPS or GFP.
Note
When using GFP multiplexing, only the statistics of the primary group can be
displayed. This is sufficient for performance monitoring, because these statistics
represent the WAN side transmission performance for all the groups handled by
the corresponding GFP multiplexer.
The statistics are collected over 15-minute intervals, and up to 97 of the most
current intervals are stored for retrieval. The performance monitoring information
is lost when the Megaplex-4100 is powered down.
A typical WAN Intervals selection screen is shown in Figure 6-43.
MP-4100
Monitoring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals
1. Current Interval>
2. Select Interval >
3. Total
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-debug
1M/1C
-----------------------------------------------------------------------------
Figure 6-43. Typical WAN Intervals Selection Screen
³
To display WAN side performance monitoring data for the current interval:
1. Type 1 and then press <Enter>.
2. You will see the first page of the Current Interval performance monitoring
screen for the WAN side. The Current Interval screen includes a large number
of items and therefore it consists of two pages:
6-36
ƒ
To continue from the first page to the second page, type n (next)
ƒ
To return from the second page to the first page, type p (previous).
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 6 Troubleshooting and Diagnostics
To display WAN side performance monitoring data on a selected interval:
Type 2 and then press <Enter>.
³
To display totaled WAN side performance monitoring data:
Type 3 and then press <Enter>.
³
To clear the accumulated statistics (reset all the counters, except items 2, 3, 4):
Type C and then press <Enter>.
VCG WAN Side Statistics – LAPS Encapsulation
The two pages of a typical WAN side statistics screen for a virtually concatenated
group using LAPS encapsulation are shown in Figure 6-44 and Figure 6-45. The
WAN side statistics parameters for groups using LAPS encapsulation are described
in Table 6-6.
MP-4100
oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
1. Interval Number
[0 - 96]... (0)
2. Valid Intervals
[0 - 96]... (1)
3. Elapsed time
... (00:08:40)
4. Number of Total Rx Frames
... (0)
5. Number of Total Tx Frames
... (0)
6. Rx Payload Max length violation
... (0)
7. Rx Payload Min length violation
... (0)
8. FCS error
... (0)
9. Receive Abort Frames
... (0)
10. Byte De-stuffing violations
... (0)
... (N)
>
C - Clear
ESC-prev.menu; !-main menu; &-exit; @-debug
1M/1C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-44. Typical WAN Side Statistics Screen – LAPS Encapsulation (First Page)
MP-4100
oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
...
11.
12.
13.
(P)
Receive address field mismatch counter... (0)
Receive control field mismatch counter... (0)
Receive SAPI field mismatch counter
... (0)
>
C - Clear
ESC-prev.menu; !-main menu; &-exit; @-debug
1M/1C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-45. Typical WAN Side Statistics Screen – LAPS Encapsulation (Second Page)
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-37
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-6. WAN Side Statistics – LAPS Encapsulation
Parameter
Description
Interval Number
The number of the 15-minute interval to be displayed, in the range of 1 to 96.
To select a different interval, type 1 and then press <Enter>: you can then enter the
desired interval number, up to the number displayed in the Valid Intervals field
Valid Intervals
The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed
Elapsed Time
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds
Number of Total Rx
Frames
Total number of frames received from the WAN
Number of Total Tx
Frames
Total number of frames transmitted to the WAN
Rx Payload Max
Length Violation
Total number of frames received with payload fields exceeding the maximum allowed
number of bytes
Rx Payload Min
Length Violation
Total number of frames received with payload fields shorter than the minimum
allowed number of bytes
FCS Error
Total number of frames received with frame checksum errors
Receive Abort
Frames
Total number of frames whose reception has been aborted
Byte De-stuffing
Violations
Total number of byte destuffing violations detected during the processing of received
frames
Receive Address
Field Mismatch
Counter
Total number of valid received LAPS frames with mismatching address field
Receive Control
Field Mismatch
Counter
Total number of valid received LAPS frames with mismatching control field
Receive SAPI Field
Mismatch Counter
Total number of valid received LAPS frames with mismatching SAPI field
WAN Side Statistics – GFP Encapsulation
The two pages of a typical WAN side statistics screen for a virtually concatenated
group using GFP encapsulation are shown in Figure 6-46 and Figure 6-47.
The WAN side statistics parameters for groups using GFP encapsulation are
described in Table 6-7.
6-38
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
...oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
...
>
Interval Number
Valid Intervals
Elapsed time
Number of Total Rx Frames
Number of Total Tx Frames
Rx Payload Max length violation
FCS error
Receive Idle frame error
Receive cHEC single bit error
Receive PTI mismatch
(N)
[0 - 96]... (0)
[0 - 96]... (7)
... (00:08:25)
... (0)
... (0)
... (0)
... (0)
... (0)
... (0)
... (0)
C - Clear
ESC-prev.menu; !-main menu; &-exit; @-debug
1M/1C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-46. Typical WAN Side Statistics Screen – GFP Encapsulation (First Page)
MP-4100
...oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
...
11.
12.
13.
14.
15.
16.
17.
(P)
Receive
Receive
Receive
Receive
Receive
Receive
Receive
EXI mismatch
UPI mismatch
tHEC single bit error
tHEC multi bit error
CID mismatch
eHEC single bit error
eHEC multi bit error
...
...
...
...
...
...
...
(0)
(0)
(0)
(0)
(0)
(0)
(0)
>
C - Clear
ESC-prev.menu; !-main menu; &-exit; @-debug
1M/1C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-47. Typical WAN Side Statistics Screen – GFP Encapsulation (Second Page)
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-39
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-7. WAN Side Statistics – GFP Encapsulation
Parameter
Description
Interval Number
The number of the 15-minute interval to be displayed, in the range of 1 to 96.
To select a different interval, type 1 and then press <Enter>: you can then
enter the desired interval number, up to the number displayed in the Valid
Intervals field.
Valid Intervals
The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed.
Elapsed Time
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds.
Start Time
The time at which the current interval was initiated, in accordance with the
Megaplex-4100 internal real-time clock.
Since the Megaplex-4100 time may not be coordinated with the network
management station time, or they may be located in different time zones, you
should compare the Megaplex-4100 internal time (displayed by means of the
Configuration – System – Date & Time Update) with the station time.
Number of Total Rx Frames
Total number of GFP frames received from the WAN.
Number of Total Tx Frames
Total number of GFP frames transmitted to the WAN.
Rx Payload Max Length
Violation
Total number of GFP frames received with payload fields exceeding the
maximum allowed number of bytes.
FCS Error
Total number of GFP frames received with frame checksum errors.
Receive Idle Frame Error
Total number of GFP IDLE frames received with errors error.
Receive cHEC Single Bit
Error
Total number of received GFP frames that are detected to have only single-bit
errors in the GFP Core header (cHEC field).
Receive PTI Mismatch
Total number of received GFP frames with a mismatch in the PTI field (i.e., PTI
value not corresponding to the Client Data or Management frame).
Receive EXI Mismatch
Total number of received GFP frames with a mismatch in the EXI field (i.e.,
value of EXI is not equal to NULL or LINEAR modes).
Receive UPI Mismatch
Total number of received GFP frames with a mismatch in the UPI field (i.e., EXI
value not equal to 00000001).
Receive tHEC Single Bit
Error
Total number of received GFP frames with single-bit errors only in the GFP Type
header (tHEC field).
Receive tHEC Multi Bit Error
Total number of received GFP frames with multi-bit errors in the GFP Type
header (tHEC field).
Receive CID Mismatch
Total number of received GFP frames with a mismatch or unsupported value in
the GFP CID field.
Receive eHEC Single Bit
Error
Total number of received GFP frames with only single-bit errors in the GFP
Extension header (eHEC field).
Receive eHEC Multi Bit Error Total number of received GFP frames that are detected to only have multi-bit
errors in the GFP Extension header (eHEC field).
6-40
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Displaying LCAS Path Info Parameters for Virtual Ports
For virtually concatenated groups configured to use LCAS, you can display
information on the LCAS status for the selected virtually concatenated group.
A typical LCAS Path Info selection screen is shown in Figure 6-48.
MP-4100
Monitoring>Virtual Ports>VCAT>VCG 1>LCAS PATH info
Index
0
1
2
VC
L1
L1
L1
Number
1:1:1
1:1:2
1:1:3
Source State
Add
Add
Add
Sink State
Fixed
Fixed
Fixed
>
ESC-prev.menu; !-main menu; &-exit; @-debug ; ?-help
1M/1C
-----------------------------------------------------------------------------
Figure 6-48. Typical LCAS Path Info Screen
The parameters displayed by means of the LCAS Path Info screen are as follows:
Index
Displays the index number of the VC within the selected virtually
concatenated group. The index number is automatically assigned.
VC Number
Identifies the position of the corresponding VC or VT within the
STM-1 or STS-3 frame, using the TUG-3:TUG-2:TU format
described in Table 6-8 and Table 6-9.
The VC Number also includes the identification of the link, L1 or
L2.
Source State
Displays the state of the corresponding VC or VT on the local end
of the path serving the selected virtually concatenated group
(that is, the end located on the Megaplex-4100 to which the
supervisory terminal is connected):
• FIXED – the end uses the fixed bandwidth (not LCAS)
• ADD – the corresponding VC or VT is about to be added to the
virtually concatenated group
• NORM – normal transmission state
• EOS – end-of-sequence indication
• IDLE – the corresponding VC or VT is not part of the virtually
concatenated group, or is about to be removed from the
group
• DNU – do not use the corresponding VC or VT, for example,
because the sink side reported a failure.
The state is correct at the time the command to display this
screen has been received by the Megaplex-4100.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-41
Chapter 6 Troubleshooting and Diagnostics
Sink State
Installation and Operation Manual
Same as above for the sink side (remote end of the path).
For each current parameter value, you can also see the allowed range of values.
Table 6-8. Identification of VC-12 Position in STM-1 Frame
TU Type
TUG-3 No. 1
TUG-3 No. 2
TUG-3 No. 3
TU 1
TU 2
TU 3
TU 1
TU 2
TU 3
TU 1
TU 2
TU 3
TUG-2 No. 1
1
2
3
22
23
24
43
44
45
TUG-2 No. 2
4
5
6
25
26
27
46
47
48
TUG-2 No. 3
7
8
9
28
29
30
49
50
51
TUG-2 No. 4
10
11
12
31
32
33
52
53
54
TUG-2 No. 5
13
14
15
34
35
36
55
56
57
TUG-2 No. 6
16
17
18
37
38
39
58
59
60
TUG-2 No. 7
19
20
21
40
41
42
61
62
63
Table 6-9. Identification of VT1.5 Position in STS-3 Frame
TU Type
STS-1 No. 1
STS-1 No. 2
STS-1 No. 3
TU 1
TU 2
TU 3
TU 4
TU 1
TU 2
TU 3
TU 4
TU 1
TU 2
TU 3
TU 4
TUG-2 No. 1
1
2
3
4
29
30
31
32
57
58
59
60
TUG-2 No. 2
5
6
7
8
33
34
35
36
61
62
63
64
TUG-2 No. 3
9
10
11
12
37
38
39
40
65
66
67
68
TUG-2 No. 4
13
14
15
16
41
42
43
44
69
70
71
72
TUG-2 No. 5
17
18
19
20
45
46
47
48
73
74
75
76
TUG-2 No. 6
21
22
23
24
49
50
51
52
77
78
79
80
TUG-2 No. 7
25
26
27
28
53
54
55
56
81
82
83
84
Monitoring Physical Layer Parameters
Selecting the Class of Physical Ports
Select a class of physical ports for which monitoring information will be displayed.
This screen includes two options:
I/O
For displaying performance monitoring and status parameters for the
physical ports of the modules installed in I/O slots. The parameters
available for these modules depend on the module type.
For additional information, refer to the Monitoring I/O Physical Layer
Parameters section.
CL
For displaying performance monitoring and status parameters for the
physical ports located on the CL modules. See Monitoring CL Physical
Ports section.
To navigate to the required screen, use Monitoring>Physical Layer.
A typical Physical Layer submenu is shown in Figure 6-49.
6-42
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer
1. I/O>
2. CL>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-49. Typical Physical Layer Selection Submenu
³
To select a class of physical ports:
Type the desired number and then press <Enter>.
Monitoring I/O Physical Layer Parameters
The Physical Layer submenu is used to monitor the physical layer status and
display performance statistics for the desired module and/or port. The selection
of a monitoring task is made in the following steps:
³
•
Selection of the target type
•
Selection of a specific I/O module
•
Selection of a specific port on the selected I/O module. For modules that
have more than one type of ports, first you must select a port type
(depending on the type of ports available on the module), and then a specific
port
•
Selection of a specific monitoring task.
To start physical layer monitoring:
1. After opening the Monitoring>Physical Layer submenu, you will see the
Physical Layer type selection screen (a typical screen is shown in
Figure 6-50): select IO (I/O modules), and then press <Enter>.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-43
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Physical Layer
1. IO >
2. CL >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-50. Typical Physical Layer Class Selection Screen
2. After selecting IO (I/O modules), you will see the I/O module selection screen.
A typical screen is shown in Figure 6-51. The screen includes only the
modules installed in the chassis.
MP-4100
Monitoring>Physical Layer>I/O
1. I/O 1 (M8E1)>
2. I/O 2 (M8E1)>
3. I/O 3 (M8SL)>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-51. Typical I/O Module Selection Screen
3. Select a module from the list by typing the number corresponding to its slot,
and then press <Enter>.
4. For I/O modules that have more than one type of physical ports, you will see
the port type selection screen.
For example, for M8E1 and M8T1 modules you can select between E1,
respectively T1, and Ethernet ports, and for M8SL modules you can select
between SHDSL and Ethernet ports.
5. You will see the port selection screen for the selected module. The ports
appearing on the screen depend on the selected module type, but only
configured modules with Admin Status = UP are included.
6-44
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
A typical screen for TDM links is shown in Figure 6-52, and a typical screen
for Ethernet ports is shown in Figure 6-53.
Note the Active label next to Link 1 in Figure 6-52: this label indicates the
redundancy status for a port that is part of a redundancy pair (in this
example, the Standby port is on another module).
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1
1.
2.
3.
4.
Link
Link
Link
Link
1(Active)
3
4
6
B257
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-52. Typical I/O Physical Port Selection Screen (E1, T1, or SHDSL Ports)
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet
1. ETH 1
2. ETH 3
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-53. Typical I/O Physical Port Selection Screen (Ethernet Ports)
Displaying I/O TDM Physical Layer Monitoring Data
Use the following procedure to select the desired monitoring data view (status or
performance statistics) for TDM I/O module ports, and clear statistics for the
corresponding port.
The supported performance views include:
•
Megaplex-4100 Ver. 2.0
Current 15-minute interval (interval 0)
Monitoring Performance
6-45
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
•
A previous 15-minute interval within the last 24 hours, for which valid
performance data exists
•
Current 24-hour interval
•
For SHDSL ports: a previous 24-hour interval within the last 7 days, for which
valid performance data exists.
For E1 ports using CAS (that is, G.732S, G.732S-CRC4 framing) and for framed T1
ports, you can also display the signaling information associated with each voice
timeslot.
To navigate to the required screen, use Monitoring>Physical Layer>I/O>E1 or T1
or SHDSL
³
To select a TDM port monitoring task:
1. On the Slot screen, select the desired port, and then press <Enter>.
2. You will see the port monitoring task selection screen. A typical selection
screen, which shows all the supported selections, appears in Figure 6-54:
ƒ
The Status item is displayed only for a port that is part of a redundancy
pair.
ƒ
The Signaling item is displayed only for a framed port using CAS.
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1>Link 1(Active)
1. Status
>
2. Statistics>
3. Signaling >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-54. Typical Monitoring Task Selection Screen for I/O TDM Physical Port
³
To display the TDM port status:
1. Select Status, and then press <Enter>. A typical screen is shown in
Figure 6-55.
2. The screen displays the current function of the selected port within the
redundancy pair:
6-46
Active
The port is the active port (the port carrying the traffic).
Standby
The port is in standby, and does not carry traffic.
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Status
Redundancy State>
(Active)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-55. Typical I/O TDM Physical Port Status Screen
³
To display the I/O TDM port performance monitoring statistics:
1. Select Statistics, and then press <Enter>.
2. You will see the port statistics interval selection screen. A typical interval
selection screen is shown in Figure 6-56. The Select Interval (24 hours) is
displayed only for SHDSL ports (on M8SL modules).
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8SL)>E1>Link 1(Active)>Statistics
1.
2.
3.
4.
5.
Current (15 min)
>
Select Interval
>
Total (24 hours)
>
Select Interval (24 hours)>
Clear Statistics
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-56. Typical I/O TDM Physical Port Statistics Interval Selection Screen (M8SL Port)
³
To display the I/O TDM physical port performance monitoring statistics for the
current interval:
1. Select Current (15 min), and then press <Enter>.
2. You will see the Current (15 min) statistics screen for the selected port. The
information displayed after selecting a specific performance view depends on
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-47
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
the module type: refer to the module Installation and Operation Manual for
detailed information.
A typical screen for E1 ports is shown in Figure 6-57; the same parameters
are also used for T1 ports. SHDSL ports have additional performance
parameters that cover the performance of the SHDSL subsystem. The
selected port is identified in the screen header. If the port is part of a
redundancy pair, a label next to the port identification indicates the
redundancy status of the port (Active or Standby).
MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Current (15 min)
CRC Error Per Second ... (0)
CRC Average Error/Sec... (0)
Current ES
... (0)
Current UAS
... (441)
Current SES
... (0)
Current BES
... (0)
Current LOFC
... (0)
Current CSS
... (0)
Current Timer
... (441)
Num Of Intervals
... (41)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-57. Typical I/O TDM Physical Port Current Interval Statistics Screen (E1 Ports)
The information displayed on the screen, which is accumulated continuously, is
automatically refreshed every few seconds. To stop refreshing, type CTRL+B.
You can clear the displayed statistics (that is, reset the displayed performance
monitoring counters) by typing C. The counters are also reset when the
Megaplex-4100 is powered up.
The performance monitoring counters displayed on the E1 and T1 Statistics
screens are explained in Table 6-10, and the parameters displayed for SHDSL
ports are explained in Table 6-11.
Table 6-10. E1 and T1 Physical Port Statistics Parameters – 15-Minute Intervals
Parameter
Description
Interval Number
The number of the 15-minute interval to be displayed, in the range of 0 to 96.
0 is the current interval.
Num of Intervals
The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed.
Current Time
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
6-48
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Parameter
Description
CRC Error per
Second
Displays the total number of CRC errors detected in the current second.
CRC Average Error
per Second
Displays the average number of CRC errors per second detected in the current
measurement interval. Available only for E1 links.
ESF Error
Displays the number of ESF error events in the current 15-minute interval.
A CRC error is any CRC error detected by the CRC-4 function. Available only for E1
links.
An ESF error event is any extended super-frame containing a CRC error and/or OOF
event. Available only for T1 links.
Current ES
Displays the number of errored seconds (ES) in the current interval.
An errored second is any second which is not declared a UAS that contains one or
more Out-of-Frame (OOF) events and/or CRC errors.
Current UAS
Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
Current SES
•
Any second following 10 consecutive SES seconds
•
A second for which any of the previous 10 consecutive seconds was also a
UAS and any of the previous 10 consecutive seconds was a SES.
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second which is not declared a UAS that contains more than 320 CRC
errors.
Current BES
Displays the number of bursty errored seconds (BES) in the current interval.
An BES is any second which is not declared a UAS that contains 2 to 319 CRC errors.
Current Loss of
Frame Counter
(LOFC)
The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Current Slip
Second Counter
(CSS)
Displays the number of controlled slip errored seconds (CSS) in the current 15-minute
interval.
A CSS is a second with one or more controlled slip events.
Table 6-11. SHDSL Physical Port Statistics Parameters – 15-Minute Intervals
Parameter
Description
Interval Number
See Table 6-10
Num of Intervals
See Table 6-10
Current Time
See Table 6-10
Current ES
Displays the number of SHDSL errored seconds (ES) in the current interval.
An SHDSL ES is a second during which one or more CRC anomalies are declared,
and/or one or more LOSW defects are declared
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-49
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Parameter
Description
Current UAS
Displays the number of SHDSL unavailable seconds (UAS) in the current interval.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The SHDSL line
becomes unavailable at the onset of 10 contiguous SESs (the 10 SESs are included in
the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10 contiguous
seconds with no SESs (the 10 seconds with no SESs are excluded from the unavailable
time)
Current SES
Displays the number of SHDSL severely errored seconds (SES) in the current interval.
The SHDSL SES is any second which is not declared a UAS, during which at least 50
CRC anomalies are declared, or one or more LOSW defects are declared
Current CRC
Anomalies
Displays the number of CRC anomalies in the current interval.
Current LOSWS
Displays the number of SHDSL LOSW seconds (LOSWS) in the current interval.
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.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW defects are
declared
Current LOSW
Displays the number of loss of SHDSL synchronization word (LOSW) events in the
current interval.
An LOSW failure is declared after 2.5 ± 0.5 seconds of contiguous LOSW defect. The
LOSW failure is cleared when the LOSW defect is absent for 20 seconds, but not less
than 2 seconds
Loop Attenuation
Displays the loop attenuation, in dB, measured in the current interval
SNR Margin
Displays the signal/noise margin, in dB, measured in the current interval
Actual Power
Backoff
Displays the transmit power backoff, in dB, used in the current interval
³
To display I/O TDM port performance monitoring statistics for a selected interval:
1. Select Select Interval on the port statistics interval selection screen, and then
press <Enter>.
2. You will see the Select Interval performance monitoring screen. A typical
screen is shown in Figure 6-58. The selected port is identified in the screen
header. If the port is part of a redundancy pair, a label next to the port
identification indicates the redundancy status of the port (Active or Standby).
3. Select the desired interval, by typing 1 and pressing <Enter>: you can then
enter the desired interval number, up to the number displayed in the Num of
Intervals field (see Figure 6-57).
4. After pressing <Enter>, the data displayed on the screen is updated in
accordance with your selection.
The performance monitoring counters displayed on the E1 and T1 Statistics
screens are explained in Table 6-10, and the parameters displayed for SHDSL
ports are explained in Table 6-11.
6-50
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Select Interval
Current ES
Current UAS
Current SES
Current BES
Current LOFC
Current CSS
1. Interval [1-96]
...
...
...
...
...
...
...
(0)
(900)
(0)
(0)
(0)
(0)
(1)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-58. Typical I/O TDM Physical Port Select Interval Statistics Screen (E1 Ports)
³
To display totaled I/O TDM port performance monitoring statistics for last
24-hour interval:
1. Select Total on the TDM port statistics interval selection screen and then
press <Enter>.
2. You will see the Total performance monitoring screen for the selected TDM
port. A typical screen is shown in Figure 6-58. The selected port is identified
in the screen header. If the port is part of a redundancy pair, a label next to
the port identification indicates the redundancy status of the port (Active or
Standby).
MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Total (24 hours)
ES
UAS
SES
BES
LOFC
CSS
Current 24 Hour Degraded min
Last 24 Hour Degraded min
...
...
...
...
...
...
...
...
(0)
(36900)
(0)
(0)
(1)
(1)
(0)
(0)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-59. Typical I/O TDM Physical Port Total (24 Hours) Statistics Screen (E1 Ports)
The performance monitoring counters displayed on the E1 and T1 Statistics
screens are explained in Table 6-12, and the parameters displayed for SHDSL
ports are explained in Table 6-13.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-51
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-12. E1 and T1 Physical Port Statistics Parameters – 24-Hour Totals
Parameter
Description
ES
Displays the total number of errored seconds (ES) in the 24-hour interval.
UAS
Displays the total number of unavailable seconds (UAS) in the 24-hour interval.
SES
Displays the total number of severely errored seconds (SES) in the 24-hour interval.
BES
Displays the total number of bursty errored seconds (BES) in the 24-hour interval.
LOFC
Displays the total number of LOF events (BES) in the 24-hour interval.
CSS
Displays the total number of controlled slip errored seconds (CSS) in the 24-hour
15-minute interval.
Current Degraded
Minutes
Displays the total number of degraded minutes in the current 24-hour interval. A
Last Degraded
Minutes
-6
degraded minute is a minute in which the bit error rate (BER) exceeded 1×10 . This
number is updated every minute.
Displays the total number of degraded minutes in the last 24-hour interval. This
number is updated every 24 hours.
Table 6-13. SHDSL Physical Port Statistics Parameters – 24-Hour Totals
Parameter
Description
Current ES
Displays the total number of SHDSL errored seconds (ES) in the last 24-hour interval.
Current UAS
Displays the total number of SHDSL unavailable seconds (UAS) in the last 24-hour
interval.
Current SES
Displays the total number of SHDSL severely errored seconds (SES) in the last 24-hour
interval.
Current CRC
Anomalies
Displays the total number of CRC anomalies in the last 24-hour interval.
Current LOSWS
Displays the total number of SHDSL LOSW seconds (LOSWS) in the last 24-hour
interval.
³
To display totaled I/O SHDSL port performance monitoring statistics for a
selected 24-hour interval:
1. Select Select Interval (24 Hours) on the TDM port statistics interval selection
screen and then press <Enter>.
2. Select the desired interval, by typing 1 and pressing <Enter>: you can then
enter the desired interval number, up to 7.
3. After pressing <Enter>, the data displayed on the screen is updated in
accordance with your selection. The selected port is identified in the screen
header. If the port is part of a redundancy pair, a label next to the port
identification indicates the redundancy status of the port (Active or Standby).
The performance monitoring counters are explained in Table 6-13.
³
To monitor the signaling information for an E1 or T1 physical port:
1. On the physical port selection screen (Figure 6-49), select the desired E1
port, and then press <Enter>.
6-52
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
2. On the port task selection screen of the selected port (Figure 6-54), select
Signaling and then press <Enter>.
3. You will see the Signaling monitor screen.
The screen includes several pages, where each page presents the signaling
information for 8 timeslots. A typical first page is shown in Figure 6-20: scroll
down to see the other pages (to see the navigation options, select? (help)).
The screen presents information only for connected voice timeslots: for other
timeslots, you will see only ––––.
MP-4100
Monitoring>Physical Layer>I/O>I/O-1 (M8E1)>Link 1>Signaling
Ts#
TS 01
TS 02
| TS 03
v TS 04
TS 05
TS 06
TS 07
TS 08
Rx From Link
------------0000
0000
-------
Tx To CL
------------0101
0101
-------
Rx From CL
------------0000
0000
-------
Tx To Link
------------0000
0000
-------
Type
DATA
VOICE
VOICE
-
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-60. Typical Signaling Monitor Screen for Physical Port
For a description of the Signaling monitoring parameters, refer to Table 6-1.
Displaying I/O Ethernet Physical Port Monitoring Data
Use the following procedure to select the desired monitoring data view (status or
performance statistics) for I/O module Ethernet ports, and clear statistics for the
corresponding port.
Statistics can be displayed only for enabled ports: if the Ethernet port is not
enabled, its monitoring display is empty.
The information is accumulated continuously while the Megaplex-4100 operates,
and is automatically refreshed every few seconds. The performance monitoring
information is lost when the Megaplex-4100 is powered down.
To navigate to the required screen, use Monitoring>Physical Layer>I/O>Ethernet.
³
To select an I/O Ethernet port monitoring task:
1. On the Slot screen (Figure 6-54), select the desired Ethernet port, and then
press <Enter>.
2. You will see the Ethernet port monitoring task selection screen. A typical
selection screen appears in Figure 6-61.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-53
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1
1. Status
>
2. Statistics>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-61. Typical Monitoring Task Selection Screen for I/O Module Ethernet Physical Port
³
To display the I/O Ethernet port status:
1. Select Status, and then press <Enter>.
2. You will see the Port Status screen for the selected Ethernet port. A typical
screen is shown in Figure 6-62.
The parameters displayed on the Ethernet port Status screen are explained in
Table 6-14.
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Status
Connector Type >
Operation Status>
Auto Negotiation>
Speed & Duplex >
(SFP)
(Up)
(Disabled)
(100 Mbps Full Duplex)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-62. Typical I/O Ethernet Physical Port Status Screen
Table 6-14. I/O Physical Port Ethernet Port Status Parameters
Parameter
Description
Connector Type
Displays the port connector type:
6-54
•
RJ-45 – RJ-45 connector for copper interface.
•
SFP – in accordance with the installed SFP.
•
Missing – port equipped with SFP socket, but no SFP is installed.
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Parameter
Description
Operation Status
Displays the Ethernet port status:
Auto Negotiation
Speed and Duplex
³
Chapter 6 Troubleshooting and Diagnostics
•
Up – the port is connected to a LAN and operating normally
•
Down – the port does not carry traffic, e.g., it is not connected to an active
LAN
Displays the auto-negotiation status:
•
Configuring – the port uses auto-negotiation, and is currently performing the
negotiation process needed to select the operating rate and mode
•
Complete – the port completed the negotiation process and the operating
rate and mode has been selected
•
Disabled – the port operating rate and mode is manually selected
Displays the port current rate and mode:
•
10Mbps half duplex – Half-duplex operation at 10 Mbps.
•
10Mbps full duplex – Full-duplex operation at 10 Mbps.
•
100Mbps half duplex – Half-duplex operation at 100 Mbps.
•
100Mbps full duplex – Full-duplex operation at 100 Mbps.
To display the I/O Ethernet port performance monitoring statistics:
1. Select Statistics in Figure 6-61, and then press <Enter>.
2. You will see the Statistics screen for the selected Ethernet port. The screen
includes a large number of items and therefore it consists of three pages:
ƒ
To continue from the first page to the next page, type n (next)
ƒ
To return from the second page to the previous page, type p (previous).
Typical Statistics screens are shown in Figure 6-63. Table 6-15 explains the
statistics parameters.
The information displayed on the screen, which is accumulated continuously, is
automatically refreshed every few seconds. You can clear the displayed statistics
(that is, reset the displayed performance monitoring counters) by typing C. The
counters are also reset when the Megaplex-4100 is powered up.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-55
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Statistics
RX Statistics
TX Statistics
=============
=============
Total Frames
... (0)
Total Frames
... (0)
Total Octets
... (0)
Total Octets
... (0)
Correct Frames
... (0)
Correct Frames
... (0)
FCS Errors
... (0)
Jabber Errors
... (0)
Fragments Errors ... (0)
Pause Frames
... (0)
Undersized Frames... (0)
Oversized Frames ... (0)
... (N)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
A. First Page
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Statistics
... (P)
RX Statistics
TX Statistics
=============
=============
Collisions
... (0)
Discard Frames
... (0)
Discard Frames
... (0)
Errors
... (0)
Unicast Frames
... (0)
Unicast Frames
... (0)
MultiCast Frames ... (0)
MultiCast Frames ... (0)
Broadcast Frames ... (0)
Broadcast Frames ... (0)
64 Octets
... (0)
65-127 Octets
... (0)
128-255 Octets
... (0)
... (N)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
B. Second Page
6-56
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Statistics
... (P)
RX Statistics
TX Statistics
=============
=============
256-511 Octets
... (0)
512-1023 Octets ... (0)
1024-long Octets ... (0)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
C. Third Page
Figure 6-63. Typical I/O Ethernet Physical Port Statistics Screen
Table 6-15. I/O Ethernet Physical Port Performance Monitoring Statistics
Parameter
Description
Rx Total Frames
Total number of frames received through the corresponding Ethernet port
Rx Total Octets
Total number of data octets carried by all frames received through the
corresponding Ethernet port
Rx Correct Frames
Total number of good frames received through the corresponding Ethernet
port
Rx FCS Errors
Total number of frames received by the corresponding Ethernet port which
has an invalid FCS, but met the following conditions:
•
Frame data length is between 64 bytes, and 1518 or 1536 bytes
(depending on mode)
•
Collision event has not been detected
•
Late collision event has not been detected
Rx Jabber Errors
Total number of frames received by the corresponding Ethernet port during
jabber (such frames are frames with a data field length exceeding 1518 or
1536 bytes, and also having invalid CRC)
Rx Fragment Errors
Number of fragmented frames received at the corresponding Ethernet port (a
fragmented frame is a frame with a data field length less than 64 bytes and
invalid CRC, for which no collision event and no late collision event have not
been detected during its reception)
Rx Pause Frames
Total number of pause frames (used for flow control) received through the
corresponding Ethernet port
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-57
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Parameter
Description
Undersized Frames
Total number of frames with size less than 64 bytes received through the
corresponding Ethernet port
Oversized Frames
Total number of frames with size more than the maximum allowed received
through the corresponding Ethernet port
Rx Discard Frames
Total number of valid frames received by the corresponding Ethernet port
that have been discarded because of a lack of buffer space. This includes
frames discarded at ingress, as well as those dropped due to priority and
congestion considerations at the output queues
Rx Errors
Total number of frames received by the corresponding Ethernet port that had
other types of errors
Rx Unicast Frames
Total number of good unicast frames received through the corresponding
Ethernet port
Rx Multicast Frames
Total number of good multicast frames received through the corresponding
Ethernet port
Rx Broadcast Frames
Total number of good broadcast frames received through the corresponding
Ethernet port
Rx 64 Octets
Total number of 64-byte frames received through the corresponding Ethernet
port
Rx 65-127 Octets
Total number of frames with size of 65 to 127 bytes received through the
corresponding Ethernet port
Rx 128-255 Octets
Total number of frames with size of 128 to 255 bytes received through the
corresponding Ethernet port
Rx 256-511 Octets
Total number of frames with size of 256 to 511 bytes received through the
corresponding Ethernet port
Rx 512-1023 Octets
Total number of frames with size of 512 to 1023 bytes received through the
corresponding Ethernet port
Rx 1024-long Octets
Total number of frames with size of 1024 up to 1600 bytes received through
the corresponding Ethernet port
Tx Total Frames
Total number of good frames transmitted by the corresponding Ethernet port
Tx Total Octets
Total number of data octets carried by all the good frames transmitted by the
corresponding Ethernet port
Tx Correct Frames
Total number good frames transmitted by the corresponding Ethernet port
Tx Total Collisions
Total number of collisions detected at the corresponding Ethernet port
Tx Unicast Frames
Total number of good unicast frames transmitted by the corresponding
Ethernet port
Tx Multicast Frames
Total number of good multicast frames transmitted by the corresponding
Ethernet port
Tx Broadcast Frames
Total number of good broadcast frames transmitted by the corresponding
Ethernet port
6-58
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Monitoring CL Physical Ports
Selecting the Class of CL Physical Ports for Monitoring
Use the following procedure to select the class of CL physical ports for which you
want to display the performance monitoring data. There are three classes of
physical ports:
•
External (station) clock port
•
SDH/SONET physical ports. SDH/SONET physical ports are located only on
CL.1/155 and CL.1/155GbE modules.
•
GbE physical ports. SDH/SONET physical ports are located only on CL.1/GbE
and CL.1/155GbE modules.
The selection is made in three steps:
•
Selection of a specific CL module. This selection is necessary only when the
Megaplex-4100 is equipped with two CL modules.
•
Selection of a type of port on the selected module.
•
For SDH/SONET and GbE ports: selection of a specific port on the selected
module.
In addition to port performance and status data, you can also display the current
timing reference source for the SDH/SONET side.
To navigate to the required screen, use Monitoring>Physical Layer>CL.
A typical CL class selection screen is shown in Figure 6-64.
MP-4100
Monitoring>Physical Layer>CL
1. CL-A >
2. CL-B >
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-64. Typical Physical Port CL Module Selection Screen
³
To select a class of CL physical ports:
1. Select the desired CL module on the CL module selection screen, and then
press <Enter>.
2. You will see the port type selection screen for the corresponding CL module.
A typical screen for CL-A is shown in Figure 6-65.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-59
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Physical Layer>CL>CL-A
1. Station Clock>
2. Ethernet
>
3. SDH/SONET
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-65. Typical CL Physical Port Selection Screen
Displaying Monitoring Data for Station Clock Port
A typical physical port monitoring screen for the CL station clock interface is
shown in Figure 6-66. You can see this screen only if the Admin Status of the
clock interface on the selected CL module is Up.
MP-4100
Monitoring>Physical Layer>CL>CL-A >Station Clock
Status
Cable Type
Rx SSM
>
>
>
(Normal)
(Balance)
(SEC)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-66. Typical Station Clock Physical Port Monitoring Screen
The information displayed on the Station Clock monitoring screen is explained in
Table 6-16.
6-60
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Table 6-16. Station Clock Physical Port Monitoring Parameters
Parameter
Description
Status
Displays the status of the station clock interface :
Cable Type
Rx SSM
•
Normal – normal operation.
•
Loss of Signal – no input signal. Often, this occurs when the input signal
is not connected, or the connected cable type (see Cable Type below)
does not match the selected interface.
•
Loss of Sync – interface could not lock to the input signal. Often, this
occurs when the input signal frequency is different from the configured
frequency.
Displays the type of cable actually connected to the station clock interface:
•
Balance – cable suitable for use with a balanced interface.
•
Unbalance – cable suitable for use with an balanced interface.
Displays the SSM message received by the clock interface. This parameter is
displayed only when using the 2048 kbps or 1544 kbps clock rate, provided clock
interface is configured to read the received SSM message.
The values available for SDH operation (relevant for 2048 KBPS) are as follows:
PRC – Primary source per ITU-T Rec. G.811 (associated SSM: 0010).
SSU-T – transit (T-type) secondary synchronization source per ITU-T Rec. G.812
(associated SSM: 0100).
SSU-L – Local (L-type) secondary synchronization source per ITU-T Rec. G.812
(associated SSM: 1000).
SEC – SDH equipment clock per ITU-T Rec. G.813 (associated SSM: 1011).
Unknown – unknown quality (associated SSM: 0000).
DNU – Do not use (associated SSM: 1111).
The values available for SONET operation per Telcordia GR-436-CORE (relevant for
1544 KBPS) are as follows:
ST1 – Stratum 1 traceable reference source (associated SSM: 0001).
TNC – Transit mode clock, traceable (associated SSM: 0100).
ST2 – Stratum 2 traceable reference source (associated SSM: 0111).
ST3 – Stratum 3 traceable reference source (associated SSM: 1010).
SMC – SONET Minimum Clock, Traceable (sub Stratum 3 quality – associated SSM:
1100).
Unknown – unknown quality (associated SSM: 0000).
Default: Unknown
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-61
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Displaying Monitoring Data for the SDH/SONET Subsystem
Megaplex-4100 equipped with CL.1/155 or CL.1/155GbE modules can provide
monitoring data for the SDH/SONET subsystem current clock source, and for each
physical link of the SDH/SONET subsystem.
When path protection is used, you can also display the current protection status.
A typical task selection screen is shown in Figure 6-67.
MP-4100
Monitoring>Physical Layer>CL>CL-A >SDH/SONET
1.
2.
3.
4.
Timing
Link 1
Link 2
Path Protection
>
>
>
>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-67. Typical SDH/SONET Physical Layer Monitoring Task Selection Screen
³
To select a SDH/SONET physical port monitoring task:
Select the desired task, and then press <Enter>.
Displaying SDH/SONET Subsystem Timing Information
³
To display the SDH/SONET subsystem current clock source:
1. Select Timing and then press <Enter>.
2. You will see the Timing screen for the selected port. The information
presented on the screen depends on the timing mode configured in
accordance with the Configuring System Clock Sources section in Chapter 4.
Typical screens are shown in Figure 6-68.
6-62
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Timing
Based on SSM
Tx Clock Source
Holdover
1. Port
2. Rx SSM
3. Tx SSM
>
>
>
>
>
>
(Yes)
(Internal)
(No)
(LINK 1)
(UNKNOWN)
(SEC)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical Screen for Automatic SSM-Based Timing Selection
MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Timing
Based on SSM
Mode
Tx Clock Source
Holdover
1. Port
2. Rx SSM
3. Tx SSM
>
>
>
>
>
>
>
(No)
(Master)
(CL-A Link 1)
(Yes)
(LINK 1)
(UNKNOWN)
(SEC)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
B. Typical Screen for Preconfigured Timing Selection
Figure 6-68. Typical Timing Screens
The parameters displayed on the Timing screen are explained in Table 6-17.
Table 6-17. SDH/SONET Subsystem Timing (Physical Ports) Parameters
Parameter
Description
Based on SSM
Displays the selection mode of the link transmit clock reference:
Megaplex-4100 Ver. 2.0
•
Yes – The selection of the timing reference uses the SSM received in the S1
byte of the STM-1 or OC-3 overhead.
•
No – The selection of the timing reference does not use the SSM.
Monitoring Performance
6-63
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Parameter
Description
Tx Clock Source
Displays the source that provides the SDH/SONET subsystem transmit clock reference:
Holdover
•
A CL module port: displays the module (CL A or CL B) followed by the port
(Link 1 or Link 2)
•
Internal – the internal oscillator has been selected
•
System – the Megaplex-4100 nodal clock
Displayed only when Based on SSM is Yes:
•
Yes – the SDH/SONET timing subsystem switched to the hold-over mode,
because no suitable reference source is available. If the problem persists for
more than 24 hours, the subsystem will switch to the Internal mode.
•
No – normal operation
Port
Type 1 and then press <Enter> to select a CL module port for which you want to display
the SSM parameters. After selecting a port, press <Enter> to display the current SSM
parameters
Rx SSM
Displays the SSM received by the selected port. See Table 6-16 for the list of SSM
values.
When you see a number next to this field, you can display a help screen containing the
list of SSM by typing the number and then pressing <Enter>.
Tx SSM
Display the SSM transmitted by the selected port.
When you see a number next to this field, you can display a help screen containing the
list of SSM by typing the number and then pressing <Enter>.
Displaying Monitoring Data for an SDH/SONET Link
After selecting a specific link on the screen of Figure 6-67, you can select the
desired monitoring data on a task selection submenu:
•
Link status and manufacturer-provided data for the installed SFP
•
Link performance monitoring statistics
•
DCC transmission statistics
•
Current optical parameters of the SFP serving the link interface
A typical task selection submenu for SDH/SONET link monitoring data is shown in
Figure 6-69.
6-64
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Link 1
1.
2.
3.
4.
Link Status
>
Link Statistics
>
DCC Statistics
>
Optical Parameters>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-69. Typical SDH/SONET Link Monitoring Task Selection Submenu
³
To display the SDH/SONET link status:
1. Select Link Status on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Link Status screen for the selected port. A typical Link Status
screen is shown in Figure 6-70.
MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>Link Status
Section Status>
Line Status
>
S1 Value
>
1. SFP
>
(Normal)
(Normal)
(0)
>
ESC-prev.menu; !-main menu; &-exit; @-Output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-70. Typical Link Status (Physical Layer) Screen
The parameters displayed on the Link Status screen are explained in Table 6-18.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-65
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-18. Link Status (Physical Layer) Parameters
Parameter
Description
Section Status
Displays the status of the SDH or SONET section (see Figure 6-71) terminated at the
selected link interface:
•
Normal – normal operation
•
LOS – loss of signal
•
LOF – loss of frame alignment
•
LOS and LOF – loss of signal and loss of frame alignment
Displays the status of the SDH or SONET line (see Figure 6-71) terminated at the
selected link interface:
Line Status
•
Normal – normal operation
•
AIS – reception of AIS (alarm indication signal)
•
RDI – reception of RDI (remote defect indication)
•
AIS and RDI – reception of AIS and RDI
S1 Value
Displays the value of the S1 byte of the STM-1 or OC-3 overhead
SFP
Type 1 and then press <Enter> to display the manufacturer-provided SFP characteristics,
as retrieved from the SFP serving the selected link interface:
•
Connector Type – displays the optical connector type, usually LC. MISSING
means that no SFP is inserted in the link SFP socket, or that the SFP cannot
provide the required information.
•
Manufacturer Name – a concise identification of the SFP manufacturer
•
Typical Max Range (km) – the maximum range to be expected in a typical
application, for a link terminated by two SFPs operating over the
recommended fiber
•
Wave Length (nm) – nominal operating wavelength, in nm
•
Fiber Type – SINGLE MODE or MULTI MODE fiber
No information can be displayed without an SFP inserted in the link SFP socket
Figure 6-71 explains the difference between an SDH/SONET section and
SDH/SONET line:
•
An SDH/SONET section is a connection between two section termination
equipment units, that is, between units that handle only the section
overhead bytes carried in the SDH/SONET frames.
Equipment such as repeaters (regenerators) that regenerate the SDH/SONET
signal but do not process other parts of the SDH/SONET frames can serve
only as section termination units.
•
An SDH/SONET line is a connection between two line termination units. Such
units handle both the section and line overhead bytes carried in the
SDH/SONET frames, and can also add and remove payload. A line can include
one or more sections.
Line termination equipment always serves also as section termination
equipment.
6-66
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Line
Line
Section
SDH/SONET
Multiplexer
(Path
Termination)
..
.
Section
Section
Add-Drop
Multiplexer
SDH/SONET Repeaters
(Regenerators)
SDH/SONET
Multiplexer
(Path
Termination)
..
.
Figure 6-71. Structure of Transmission Path in SDH/SONET Network
³
To display the SDH/SONET link physical port statistics:
1. Select Link Statistics on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Link Statistics interval selection screen. A typical Port
Statistics interval selection screen is shown in Figure 6-72.
MP-4100
...oring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>Link Statistics
1. Current Interval>
2. Select Interval >
3. Total
>
>
ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-72. Typical Interval Selection Screen
³
To display SDH/SONET link performance monitoring statistics for the current
interval:
1. Select Current Interval and then press <Enter>.
2. You will see the Current Interval performance monitoring screen for the
selected link. A typical screen is shown in Figure 6-73. The selected port is
identified in the screen header.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-67
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
...sical Ports>CL>CL-A>SDH/SONET>Link 1>Link Statistics>Current Interval
Valid Intervals[0 - 96]... (0)
Elapsed time
... (00:11:38)
ES
... (0)
SES
... (0)
UAS(SEFS)
... (689)
CV
... (0)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-73. Typical SDH/SONET Link Statistics>Current Interval Screen
The information displayed on the screen is automatically refreshed every few
seconds.
The performance monitoring counters displayed on the Link Statistics screen are
explained in Table 6-4.
³
To display SDH/SONET link performance monitoring statistics for a selected
interval:
1. Select Select Interval on the link statistics interval selection screen, and then
press <Enter>.
2. You will see the Select Interval performance monitoring screen for the
SDH/SONET link. This screen is similar to the screen for the current interval
shown in Figure 6-73, respectively, except for its header, Select Interval.
3. Select the desired interval, by typing 1 and pressing <Enter>: you can then
enter the desired interval number, up to the number displayed in the Valid
Intervals field.
4. After pressing <Enter>, the data displayed on the screen is updated in
accordance with your selection.
³
To display totaled SDH/SONET link performance monitoring statistics:
1. Select Total on the link statistics interval selection screen and then press
<Enter>.
2. You will see the Total performance monitoring screen for the selected
SDH/SONET link. This screen is similar to the screen for the current interval
shown in Figure 6-73, respectively, except for its header, Total, and the
number of the 15-minute intervals to be displayed, which is by default 97,
which means all the intervals.
6-68
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
³
Chapter 6 Troubleshooting and Diagnostics
To display the SDH/SONET link DCC performance monitoring statistics:
1. Select DCC Statistics on the screen of Figure 6-69, and then press <Enter>.
2. You will see the DCC Statistics screen. A typical screen is shown in
Figure 6-74.
The information displayed on the screen, which is accumulated continuously, is
automatically refreshed every few seconds.
The statistics displayed on the DCC Statistics screen are explained in Table 6-19.
MP-4100
...toring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>DCC Statistics
Rx
Rx
Rx
Rx
Tx
Tx
Total Frames
Total Bytes
CRC Error
Dropped
Total Frames
Total Bytes
...
...
...
...
...
...
(0)
(0)
(0)
(0)
(0)
(0)
>
C - Clear
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-74. Typical DCC Statistics Screen
Table 6-19. DCC Statistics Performance Monitoring Statistics
Parameter
Description
Rx Total Frames
Total number of frames received through the DCC
Rx Total Bytes
Total number of data octets carried by all the frames received through the DCC
Rx CRC Error
Total number of frames with invalid CRC received through the DCC
Rx Dropped
Total number of valid frames received through the DCC that have been dismoduleed
because of a lack of buffer space. This includes frames discarded at ingress, as well as
those dropped due to priority and congestion considerations at the output queues
Tx Total Frames
Total number of frames transmitted through the DCC
Tx Total Bytes
Total number of data octets carried by all the frames transmitted through the DCC
³
To display the port Optical Parameters screen:
1. Select Link Status on the screen of Figure 6-69, and then press <Enter>.
2. A typical link Optical Parameters screen is shown in Figure 6-75. The
information displayed on the screen is explained in Table 6-20.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-69
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Link 1>Optical Parameters
SFP inserted
>
TX Optical Power(dBm) ...
LASER Bias (mA)
...
LASER Temp C(F)[0 - 25...
RX Optical Power (dBm)...
Supply Voltage(V)
>
(Yes)
(-2)
(5)
(40)
(-12)
(3)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-75. Typical Link Optical Parameters Screen
Table 6-20. Typical Link Optical Parameters
Parameter
Description
SFP Inserted
Displays Yes when an SFP is installed in the port connector.
If no SFP is inserted, the next fields are not displayed
Tx Optical Power(dBm)
The current optical power, in dBm, transmitted by the SFP
Laser Bias (mA)
The measured SFP laser bias current, in mA
Laser Temp C(F)
The measured SFP laser temperature, in °C or °F
Rx Optical Power(dBm)
The current optical power, in dBm, received by the SFP
Supply Voltage (V)
The measured SFP laser supply voltage, in volts
Displaying Path Protection Monitoring Data for an SDH/SONET
Link
³
To display the current path protection situation:
1. Select Path Protection on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Path Protection screen port selection screen. The screen
presents the list of PDH ports for which path protection has been configured.
6-70
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Path Protection
1. PDH
[]
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-76. Typical SDH/SONET Path Protection PDH Port Selection Screen
3. Select the desired PDH ports, and then press <Enter> to display the path
protection information.
A typical screen is shown in Figure 6-77. The information displayed on the Path
Protection screen is explained in Table 6-21.
MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Path Protection>PDH 1
#
1
Payload
PDH3
Working
LA1:2:6:3
Protection
LB1:3:2:1
Current
Protection3
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-77. Typical SDH/SONET Path Protection Screen
Table 6-21. SDH/SONET PDH Port Path Protection Monitoring Data
Parameter
Description
#
Index number
Payload
Identifies the payload (PDH) port mapped to the corresponding TU-12 or VT1.5
Working
Identification of the configured working port in the following format:
LX:TUG3:TUG2:TU12 for SDH, and L:STS-1:TUG2:VT1.5 for SONET, where X is the CL
module identification, A or B, and L is the link number, L1 or L2.
The TUG-3:TUG-2:TU format is described in Table 6-8 and Table 6-9.
Protection
Identification of the configured protection port (same format)
Current
Identification of the current protection port: Working or Protection
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-71
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Displaying Monitoring Data for the GbE Ethernet Subsystem
Megaplex-4100 equipped with CL.1/GbE or CL.1/155GbE modules can provide
monitoring data for each physical port of the GbE subsystem.
A typical port selection screen is shown in Figure 6-78.
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet
1. GbE 1>
2. GbE 2>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-78. Typical Ethernet Physical Layer Monitoring Task Selection Screen
³
To select a GbE port for monitoring:
Select the desired port, and then press <Enter>.
Displaying Monitoring Data for a GbE Port
After selecting a specific link on the screen of Figure 6-78, you can select the
desired monitoring data on a task selection submenu:
•
Port status.
•
Ethernet performance monitoring counters
For ports equipped with SFP sockets, you can also display information on the SFP
serving the port interface.
A typical task selection submenu for GbE port monitoring data is shown in
Figure 6-69.
6-72
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet
1. GbE 1>
2. GbE 2>
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 6-79. Typical GbE Link Monitoring Task Selection Submenu
³
To display the GbE port status:
1. Select Port Status on the screen of Figure 6-79, and then press <Enter>.
2. You will see the Port Status screen for the selected port. A typical Port Status
screen, for a GbE port with electrical interface (RJ-45 connector), is shown in
Figure 6-80.
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>Port Status
Admin Status>
Link Status >
Rate
>
Rdn status >
(Up)
(Link Up)
(1000 Mbps Full Duplex)
(No redundancy)
>
%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
----------------------------------------------------------------------------Automatic Refresh Is Activated !
Figure 6-80. Typical GbE Port Status (Physical Layer) Screen
The parameters displayed on the Link Status screen are explained in Table 6-22.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-73
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-22. GbE Port Status (Physical Layer) Parameters
Parameter
Description
Admin Status
Displays the GbE port administrative status:
Link Status
•
Up – the port is enabled, and can carry traffic
•
Down – the port is disabled, and cannot carry traffic
Displays the status of the link connected to the GbE port:
Rate
•
Up – the link is operating normally, and carrying traffic
•
Down – the link does not carry traffic, e.g., because it is not connected to an
active LAN
Displays the port current rate and mode:
Rdn Status
•
10Mbps Half Duplex – Half-duplex operation at 10 Mbps.
•
10Mbps Full Duplex – Full-duplex operation at 10 Mbps.
•
100Mbps Half Duplex – Half-duplex operation at 100 Mbps.
•
100Mbps Full Duplex – Full-duplex operation at 100 Mbps.
•
1000Mbps Half Duplex – Half-duplex operation at 1000 Mbps
•
1000Mbps Full Duplex – Full-duplex operation at 1000 Mbps
Displays the redundancy status of the port:
SFP
•
No Redundancy – the port is not part of a redundancy pair
•
Active – 1+1 redundancy is used, and the port is the active port of the
redundancy pair
•
Standby – 1+1 redundancy is used, and the port is the standby port of the
redundancy pair
This item appears only when the port is equipped with an SFP, and is used to display
the manufacturer-provided SFP characteristics, as retrieved from the SFP serving the
selected port. To display the SFP characteristics, type 1 and then press <Enter>:
•
Connector Type – displays the optical connector type, usually LC
•
Manufacturer Name – a concise identification of the SFP manufacturer
•
Typical Max Range (km) – the maximum range to be expected in a typical
application, for a link terminated by two SFPs operating over the
recommended fiber
•
Wave Length (nm) – nominal operating wavelength, in nm
•
Fiber Type – SINGLE MODE or MULTI MODE fiber
No information can be displayed without an SFP inserted in the port SFP socket
³
To display the GbE port Ethernet counters:
1. Select ETH Counters on the screen of Figure 6-79, and then press <Enter>.
2. You will see the ETH Counters screen for the selected port. The screen
includes two pages: use N and P to scroll between two pages. A typical ETH
Counters screen is shown in Figure 6-81.
6-74
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>ETH Counters
RX Statistics
=============
Rx Total Frames
...
Rx Broadcast Frames ...
Rx Multicast Frames ...
Rx Correct Frames
...
Rx Total Bytes
...
Rx Dropped
...
Rx Jabber Frames
...
Rx Invalid CRC Frames...
Rx Fragment Frames
...
... (N)
TX Statistics
=============
Tx Total Frames
Tx Unicast Frames
Tx Total Bytes
Tx Correct Frames
Tx Discard Frames
Total Collision
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
...
...
...
...
...
...
(0)
(0)
(0)
(0)
(0)
(0)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>ETH Counters
... (P)
RX Statistics
=============
Rx 64b Frames
...
Rx 65b-127b Frames ...
Rx 256b-511b Frames ...
Rx 512b-1023b Frames...
Rx 1024b-max Frames ...
Rx Pause Frames
...
Rx Undersized Frames...
Rx Oversized Frames ...
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output
1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 6-81. Typical GbE Port ETH Counters (Physical Layer) Screens
Table 6-23 explains the statistics parameters.
The information displayed on the screen, which is accumulated continuously, is
automatically refreshed every few seconds. You can clear the displayed statistics
(that is, reset the displayed performance monitoring counters) by typing C. The
counters are also reset when the Megaplex-4100 is powered up.
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-75
Chapter 6 Troubleshooting and Diagnostics
Installation and Operation Manual
Table 6-23. GbE Port ETH Counters (Physical Layer) Performance Monitoring Statistics
Parameter
Description
Rx Total Frames
Total number of frames received through the Gbe port
Rx Broadcast Frames
Total number of good broadcast frames received through the Gbe port
Rx Multicast Frames
Total number of good multicast frames received through the Gbe port
Rx Correct Frames
Total number of frames with correct FCS that have been received through the
Gbe port
Rx Total Bytes
Total number of data octets carried by all frames received through the Gbe
port
Rx Dropped
Total number of valid frames received by the Gbe port that have been
discarded because of a lack of buffer space. This includes frames discarded at
ingress, as well as those dropped due to priority and congestion
considerations at the output queues.
Frames dropped at egress due to excessive collisions are not included in this
count, but are counted by the Excessive Collision counter
Rx Jabber Frames
Total number of frames received by the Gbe port during jabber (such frames
are frames with a data field length exceeding 1518 or 1536 bytes, and also
having invalid CRC)
Rx Invalid CRC Frames
Total number of frames received by the Gbe port which met the following
conditions:
•
Frame data length is between 64 bytes, and 1518 or 1536 bytes
(depending on mode)
•
Frame has invalid CRC
•
Collision event has not been detected
•
Late collision event has not been detected
Rx Fragment Frames
Number of fragmented frames received at the Gbe port (a fragmented frame
is a frame with a data field length less than 64 bytes and invalid CRC, for
which no collision event and no late collision event have not been detected
during its reception)
Rx 64b Frames
Total number of 64-byte frames received through the Gbe port
Rx Frames 65b-127b
Frames
Total number of frames with size of 65 to 127 bytes received through the
Gbe port
Rx Frames 128b-255b
Frames
Total number of frames with size of 128 to 255 bytes received through the
Gbe port
Rx Frames 256b-511b
Frames
Total number of frames with size of 256 to 511 bytes received through the
Gbe port
Rx Frames 512b-1023b
Frames
Total number of frames with size of 512 to 1023 bytes received through the
Gbe port
Rx Frames 1024b-max
Frames
Total number of frames with size of 1024 to 1600 bytes received through the
Gbe port
Rx Pause Frames
Total number of pause frames received through the Gbe port
6-76
Monitoring Performance
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Parameter
Description
Rx Undersized Frames
Total number of frames shorter than 64 bytes received through the Gbe port
Rx Oversized Frames
Total number of frames longer than 1600 bytes received through the Gbe
port
Tx Total Frames
Total number of good frames transmitted by the Gbe port
Tx Unicast Frames
Total number of good unicast frames transmitted by the Gbe port
Tx Total Bytes
Total number of data octets carried by all the good frames transmitted by the
Gbe port
Tx Correct Frames
Total number of correct frames that have been transmitted by the Gbe port
Tx Discard Frames
Total number of valid frames that were intended for transmission through the
bundle that have been discarded because congestion at the output
Total Collision
Total number of collisions detected at the Gbe port
Megaplex-4100 Ver. 2.0
Monitoring Performance
6-77
Chapter 6 Troubleshooting and Diagnostics
6.2
Installation and Operation Manual
Detecting Errors
The Megaplex-4100 includes an extensive subsystem that checks the validity of
the user’s configuration activities and reports any conflicts and errors.
Table 6-24 lists the error messages generated by Megaplex-4100, and explains
their interpretation (such messages are referred to as “sanity errors”, because
they are detected by the so-called sanity check automatically performed to
confirm correct configuration of the equipment).
Two types of messages are generated:
Warning
Minor errors that do not prevent using the Megaplex-4100.
For example, you will get a warning when a programmed
module is not installed in the chassis.
Error
Errors that prevent proper operation of the Megaplex-4100
in its intended application (for example, invalid or timeslot
assignment).
The messages are listed in ascending order of their codes.
Table 6-24. Error Messages
Code
Type
Syntax
Meaning
Global Sanity Messages
000 to N/A
099
Reserved
N/A
100
Error
AT LEAST ONE PS CARD MUST
BE DEFINED
Check that at least one power supply module is defined in
the system configuration
101
N/A
Reserved
N/A
102
Error
AT LEAST ONE CL CARD MUST
BE DEFINED
At least one CL module must be defined in the system
configuration
103,
104
N/A
Reserved
N/A
105
Error
ILLEGAL CLOCK SOURCE FOR
MASTER CLOCK
The selected master clock source is invalid for one of the
following reasons:
106 to N/A
108
6-78
Reserved
Detecting Errors
•
The configured module port cannot supply a
reference clock
•
The configured port number is invalid for the
selected module
•
The port rate is not suitable for use as clock
source (e.g., LS-12 channel operating at a rate
of 14.4 kbps)
N/A
Megaplex-4100 Ver. 2.0
Installation and Operation Manual
Chapter 6 Troubleshooting and Diagnostics
Code
Type
Syntax
Meaning
109
Error
ILLEGAL MASTER CLOCK
SOURCE MODE
The I/O module port is selected as master clock source,
but its interface type is not DTE
110
Warning MODULE TYPE MISMATCH
Differences have been found between the modules
actually installed in the equipment, and the modules
programmed in the database
111
Error
MASTER CLOCK NOT
CONNECTED
When configuring the master clock source to be locked to
the receive clock of a module/channel, the source
module/channel must be connected
112
Error
FALLBACK CLOCK NOT
CONNECTED
When configuring the fallback clock source to be locked
to the receive clock of a module/channel, the source
module/channel must be connected
113
Error
ILLEGAL CLOCK SOURCE FOR
FALLBACK CLOCK
The selected fallback clock source is invalid for one of the
following reasons:
•
The configured module port cannot supply a
reference clock
•
The configured port number is invalid for the
selected module
•
The port rate is not suitable for use as clock
source (e.g., LS-12 channel operating at a rate
of 14.4 kbps)
114
N/A
Reserved
N/A
115
Error
ILLEGAL FALLBACK CLOCK
SOURCE MODE
The I/O module port has been selected as fallback clock
source, but its interface type is not DTE
116
N/A
Reserved
N/A
117
Error
ILLEGAL MASTER CLOCK
SOURCE INTERFACE
The interface of the ISDN channel selected as master
clock reference cannot provide a reference clock.
For HSU-6/HSU-12 modules, the channel must be
configured as NT
118
Error
ILLEGAL FALLBACK CLOCK
SOURCE INTERFACE
The interface of the ISDN channel selected as fallback
clock reference cannot provide a reference clock.
For HSU-6/HSU-12 modules, the channel must be configured
as NT
119
N/A
Reserved for future use
N/A
120
N/A
Reserved
N/A
121
Warning INTERFACE HW/SW MISMATCH
The interface type configured by the management system
differs from the interface selected by means of jumpers
122
N/A
Reserved
N/A
123
Error
DIFFERENT CL CARDS FOR
REDUNDANCY
Different CL module types have been installed in slots
CL-A and CL-B, and therefore CL redundancy is not
available
Reserved for future use
N/A
124 to N/A
139
Megaplex-4100 Ver. 2.0
Detecting Errors
6-79
Chapter 6 Troubleshooting and Diagnostics
Code
Type
Installation and Operation Manual
Syntax
Meaning
Global Module Sanity Messages
140 to N/A
144
145
Error
146 to N/A
151
152
Reserved
N/A
CLOCK MODE/CLOCK SOURCE
MISMATCH
The EXT-DCE clock mode cannot be selected when the
port interface is configured as LT-1 (applicable only for
HSU-6 and HSU-12 modules)
Reserved
N/A
Warning RESTORATION TIME DOES NOT For T1 links, the restoration time should be 10 seconds,
MATCH THE STD
according to the standard.
For E1 links, the restoration time should be in accordance
with ITU-T recommendations
153
N/A
Reserved
N/A
154
Error
ILLEGAL NUMBER OF WIRES
Voice modules with /FXO and /FXS interfaces support only
the two-wire interface.
Only for voice modules with /E&M interface, is it possible
to select between two-wire and four-wire interfaces. In
addition, for VC-4/8/16 modules with /E&M interface, you
must select the same interface type for consecutive pairs
of channels (for example, 1, 2 or 15, 16)
155 to N/A
161
Reserved
N/A
162
Error
ROUTING PROTOCOL/
MNG TYPE MISMATCH
You can enable the RIP 2 protocol on an I/O module port
only when the inband management method is configured
for DEDICATE PPP or DEDICATE FR
163,
164
N/A
Reserved
N/A
Reserved for future