Survey
* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project
Download megaplex-4 5.0 system mn
Document related concepts
no text concepts found
Transcript
INSTALLATION AND
OPERATION MANUAL
Megaplex-4
Next Generation Multiservice Access Node
Version 5.0
Megaplex-4
Next Generation Multiservice Access Node
Version 5.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-4 and
any software components contained therein are proprietary products of RAD protected under
international copyright law and shall be and remain solely with RAD.
The Megaplex-4 product name is owned by RAD. The Megaplex-4 product name is owned by RAD.
No right, license, or interest to such trademark is granted hereunder, and you agree that no such
right, license, or interest shall be asserted by you with respect to such trademark. RAD
products/technologies are protected by registered patents. To review specifically which product is
covered by which patent, please see ipr.rad.com. The RAD name, logo, logotype, and the product
names MiNID, Optimux, Airmux, IPmux, and MiCLK are registered trademarks of RAD Data
Communications Ltd. All other trademarks are the property of their respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
Megaplex-4. You are prohibited from, and shall not, directly or indirectly, develop, market,
distribute, license, or sell any product that supports substantially similar functionality as the
Megaplex-4, based on or derived in any way from the Megaplex-4. Your undertaking in this
paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the Megaplex-4 package and shall continue until
terminated. RAD may terminate this Agreement upon the breach by you of any term hereof. Upon
such termination by RAD, you agree to return to RAD the Megaplex-4 and all copies and portions
thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters
RAD Data Communications Ltd.
North American 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–2018 RAD Data Communications Ltd.
Publication No. 464-201-08/18
Front Matter
Installation and Operation Manual
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the Megaplex-4 to be delivered hereunder shall
be free of defects in material and workmanship under normal use and service for a period of twelve
(12) months following the date of shipment to DISTRIBUTOR.
If, during the warranty period, any component part of the equipment becomes defective by reason
of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect, RAD shall
have the option to choose the appropriate corrective action: a) supply a replacement part, or b)
request return of equipment to its plant for repair, or c) perform necessary repair at the
equipment's location. In the event that RAD requests the return of equipment, each party shall
pay one-way shipping costs.
RAD shall be released from all obligations under its warranty in the event that the equipment has
been subjected to misuse, neglect, accident or improper installation, or if repairs or modifications
were made by persons other than RAD's own authorized service personnel, unless such repairs by
others were made with the written consent of RAD.
The above warranty is in lieu of all other warranties, expressed or implied. There are no warranties
which extend beyond the face hereof, including, but not limited to, warranties of merchantability
and fitness for a particular purpose, and in no event shall RAD be liable for consequential damages.
RAD shall not be liable to any person for any special or indirect damages, including, but not limited
to, lost profits from any cause whatsoever arising from or in any way connected with the
manufacture, sale, handling, repair, maintenance or use of the Megaplex-4, and in no event shall
RAD's liability exceed the purchase price of the Megaplex-4.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to Megaplex-4 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the Megaplex-4 are provided "as is" and without warranty of any kind.
RAD disclaims all warranties including the implied warranties of merchantability and fitness for a
particular purpose. RAD shall not be liable for any loss of use, interruption of business or indirect,
special, incidental or consequential damages of any kind. In spite of the above RAD shall do its
best to provide error-free software products and shall offer free Software updates during the
warranty period under this Agreement.
RAD's cumulative liability to you or any other party for any loss or damages resulting from any
claims, demands, or actions arising out of or relating to this Agreement and the Megaplex-4 shall
not exceed the sum paid to RAD for the purchase of the Megaplex-4. In no event shall RAD be
liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even
if RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste equipment
in protecting the environment, the owner of this RAD product is required to refrain
from disposing of this product as unsorted municipal waste at the end of its life
cycle. Upon termination of the unit’s use, customers should provide for its
collection for reuse, recycling or other form of environmentally conscientious
disposal.
ii
Megaplex-4
Installation and Operation Manual
Front Matter
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the manual.
Safety Symbols
Warning
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or
service personnel.
Danger of electric shock! Avoid any contact with the marked surface while
the product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the
building protective ground bus.
Warning
Some products may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may be also attached.
Please observe the following precautions:
•
Before turning on the equipment, make sure that the fiber optic cable is
intact and is connected to the transmitter.
•
Do not attempt to adjust the laser drive current.
•
Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
•
The use of optical devices with the equipment will increase eye hazard.
•
Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of this
product. Only qualified and authorized service personnel should carry out adjustment, maintenance
or repairs to this product. No installation, adjustment, maintenance or repairs should be performed
by either the operator or the user.
Megaplex-4
iii
Front Matter
Installation and Operation Manual
Handling Energized Products
General Safety Practices
Do not touch or tamper with the power supply when the power cord is connected. Line voltages
may be present inside certain products even when the power switch (if installed) is in the OFF
position or a fuse is blown. For DC-powered products, although the voltages levels are usually not
hazardous, energy hazards may still exist.
Before working on equipment connected to power lines or telecommunication lines, remove
jewelry or any other metallic object that may come into contact with energized parts.
Unless otherwise specified, all products are intended to be grounded during normal use. Grounding
is provided by connecting the mains plug to a wall socket with a protective ground terminal. If a
ground lug is provided on the product, it should be connected to the protective ground at all times,
by a wire with a diameter of 18 AWG or wider. Rack-mounted equipment should be mounted only
in grounded racks and cabinets.
Always make the ground connection first and disconnect it last. Do not connect telecommunication
cables to ungrounded equipment. Make sure that all other cables are disconnected before
disconnecting the ground.
Some products may have panels secured by thumbscrews with a slotted head. These panels may
cover hazardous circuits or parts, such as power supplies. These thumbscrews should therefore
always be tightened securely with a screwdriver after both initial installation and subsequent
access to the panels.
Connecting AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be readily
disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
iv
Megaplex-4
Installation and Operation Manual
Front Matter
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF position.
When connecting the DC supply wires, first connect the ground wire to the corresponding terminal,
then the positive pole and last the negative pole. Switch the circuit breaker back to the ON
position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Connecting Data and Telecommunications Cables
Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port
differs from the standard one, a notice will be given in the manual.
Ports
Safety Status
V.11, V.28, V.35, V.36, RS-530, X.21,
10BaseT, 100BaseT, 1000BaseT,
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, POE
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:
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.
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.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
Megaplex-4
v
Front Matter
Installation and Operation Manual
When using shielded or coaxial cables, verify that there is a good ground connection at both ends.
The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk, there
are restrictions on the diameter of wires in the telecom cables, between the equipment and the
mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention
Pour réduire les risques s’incendie, utiliser seulement des conducteurs de
télécommunications 26 AWG ou de section supérieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In
such cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Electromagnetic Compatibility (EMC)
The equipment is designed and approved to comply with the electromagnetic regulations of major
regulatory bodies. The following instructions may enhance the performance of the equipment and
will provide better protection against excessive emission and better immunity against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables with the exception of 1000BaseT ports that must always use shielded
twisted pair cables of good quality (CAT 5E or higher). However, the use of shielded wires is always
recommended, especially for high-rate data. In some cases, when unshielded wires are used,
ferrite cores should be installed on certain cables. In such cases, special instructions are provided
in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines is
dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal conversion
loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with plastic
connectors (without a grounded metal hood, such as flat cables) to sensitive data lines. Before
connecting such cables, discharge yourself by touching ground or wear an ESD preventive wrist
strap.
vi
Megaplex-4
Installation and Operation Manual
Front Matter
FCC-15 User Information
This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own expense.
Canadian Emission Requirements
This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulation.
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel
brouilleur du Canada.
Warning per EN 55022 (CISPR-22)
Warning
This is a class A product. In a domestic environment, this product may cause
radio interference, in which case the user will be required to take adequate
measures.
Avertissement
Cet appareil est un appareil de Classe A. Dans un environnement résidentiel,
cet appareil peut provoquer des brouillages radioélectriques. Dans ces cas, il
peut être demandé à l’utilisateur de prendre les mesures appropriées.
Achtung
Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In
Wohngebieten können beim Betrieb dieses Gerätes Rundfunkströrungen
auftreten, für deren Behebung der Benutzer verantwortlich ist.
Megaplex-4
vii
Front Matter
Installation and Operation Manual
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.
viii
Megaplex-4
Installation and Operation Manual
Avertissement
Front Matter
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.
Veuillez observer les précautions suivantes :
•
Avant la mise en marche de l'équipement, assurez-vous que le câble de
fibre optique est intact et qu'il est connecté au transmetteur.
•
Ne tentez pas d'ajuster le courant de la commande laser.
•
N'utilisez pas des câbles ou connecteurs de fibre optique cassés ou sans
terminaison et n'observez pas directement un rayon laser.
•
L'usage de périphériques optiques avec l'équipement augmentera le
risque pour les yeux.
•
L'usage de contrôles, ajustages ou procédures autres que celles spécifiées
ici pourrait résulter en une dangereuse exposition aux radiations.
ATTENTION : Le rayon laser peut être invisible !
Les utilisateurs pourront, dans certains cas, insérer leurs propres émetteurs-récepteurs Laser SFP
dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas être tenue responsable de
tout dommage pouvant résulter de l'utilisation d'émetteurs-récepteurs non conformes. Plus
particulièrement, les utilisateurs sont avertis de n'utiliser que des produits approuvés par l'agence
et conformes à la réglementation locale de sécurité laser pour les produits laser de classe 1.
Respectez toujours les précautions standards de sécurité durant l'installation, l'opération et la
maintenance de ce produit. Seul le personnel de service qualifié et autorisé devrait effectuer
l'ajustage, la maintenance ou les réparations de ce produit. Aucune opération d'installation,
d'ajustage, de maintenance ou de réparation ne devrait être effectuée par l'opérateur ou
l'utilisateur.
Manipuler des produits sous tension
Règles générales de sécurité
Ne pas toucher ou altérer l'alimentation en courant lorsque le câble d'alimentation est branché.
Des tensions de lignes peuvent être présentes dans certains produits, même lorsque le
commutateur (s'il est installé) est en position OFF ou si le fusible est rompu. Pour les produits
alimentés par CC, les niveaux de tension ne sont généralement pas dangereux mais des risques de
courant peuvent toujours exister.
Avant de travailler sur un équipement connecté aux lignes de tension ou de télécommunications,
retirez vos bijoux ou tout autre objet métallique pouvant venir en contact avec les pièces sous
tension.
Sauf s'il en est autrement indiqué, tous les produits sont destinés à être mis à la terre durant
l'usage normal. La mise à la terre est fournie par la connexion de la fiche principale à une prise
murale équipée d'une borne protectrice de mise à la terre. Si une cosse de mise à la terre est
fournie avec le produit, elle devrait être connectée à tout moment à une mise à la terre de
protection par un conducteur de diamètre 18 AWG ou plus. L'équipement monté en châssis ne
devrait être monté que sur des châssis et dans des armoires mises à la terre.
Branchez toujours la mise à la terre en premier et débranchez-la en dernier. Ne branchez pas des
câbles de télécommunications à un équipement qui n'est pas mis à la terre. Assurez-vous que tous
les autres câbles sont débranchés avant de déconnecter la mise à la terre.
Megaplex-4
ix
Front Matter
Installation and Operation Manual
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 (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de courtcircuit dépassant 35A (40A aux Etats-Unis et Canada).
Branchez toujours le câble d'alimentation en premier à l'équipement puis à la prise murale. Si un
commutateur est fourni avec l'équipement, fixez-le en position OFF. Si le câble d'alimentation ne
peut pas être facilement débranché en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est installé dans l'installation du bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si le système de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par
rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.
A cause de la capacité de courant des systèmes à alimentation CC, des précautions devraient être
prises lors de la connexion de l'alimentation CC pour éviter des courts-circuits et des risques
d'incendie.
Assurez-vous que l'alimentation CC est isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation locale.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de courtcircuit dépassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des câbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'équipement et fixez-le en
position OFF. Lors de la connexion de câbles d'alimentation CC, connectez d'abord le conducteur
de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le pôle négatif.
Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
x
Megaplex-4
Installation and Operation Manual
Front Matter
Your Network’s Edge
EU Declaration of Conformity
Manufacturer's Name:
RAD Data Communications Ltd.
Manufacturer's Address:
24 Raoul Wallenberg St., Tel Aviv 6971920, Israel
declares under its sole responsibility that the product:
Product Name:
MP-4100 including its plug-in modules MP-2100M and MP-4100M
Product Options:
All options (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative document(s) in
accordance with the relevant European Union harmonization legislation:
EMC
EN 55032: 2012+
Electromagnetic Compatibility of multimedia equipment – Emissions
AC/2013
requirements.
EN 55024:2010
(in accordance with
EN 61000-42/3/4/5/6/11)
Information technology equipment; Immunity characteristics;
EN 61000-3-2:2014
Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic
Limits and methods of measurement.
current emissions (equipment input current ≤ 16A per phase)
EN 61000-3-3:2013
Electromagnetic compatibility (EMC); Section 3-3: Limits Limitation of voltage changes, voltage fluctuations and flicker in public lowvoltage supply systems, for equipment with rated current ≤ 16A per phase
and not subject to conditional connection.
Safety
EN 60950-1:2006 +
Information technology equipment; Safety – Part 1:
A11:2009, A1:2010
General requirements.
A12:2011, A2:2013
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive
2014/30/EU, the Low Voltage Directive 2014/35/EU and the ROHS Directive
2011/65/EU.
The product was tested in typical configurations.
Signed for and on behalf of
RAD Data Communications Ltd.
Tel Aviv, 13 March 2017
Zohar Zosmanovich
Compliance Team Leader
European Contact:
RAD Data Communications GmbH
Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
Megaplex-4
xi
Front Matter
Installation and Operation Manual
Your Network’s Edge
EU Declaration of Conformity
Manufacturer's Name:
RAD Data Communications Ltd.
Manufacturer's Address:
24 Raoul Wallenberg St., Tel Aviv 6971920, Israel
declares under its sole responsibility that the product:
Product Name:
MP-4104 including its plug-in modules MP-2100M and MP-4100M
Product Options:
All options (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative document(s)
in accordance with the relevant European Union harmonization
legislation:
EMC
Safety
EN 55032: 2012+
AC/2013
Electromagnetic Compatibility of multimedia equipment – Emissions
requirements.
EN 55024:2010
(in accordance with
EN 61000-42/3/4/5/6/11)
Information technology equipment; Immunity characteristics;
Limits and methods of measurement.
EN 61000-3-2:2014
Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic
current emissions (equipment input current ≤ 16A per phase)
EN 61000-3-3:2013
Electromagnetic compatibility (EMC); Section 3-3: Limits Limitation of voltage changes, voltage fluctuations and flicker in public
low-voltage supply systems, for equipment with rated current ≤ 16A per
phase and not subject to conditional connection.
EN 60950-1:2006 +
A11:2009, A1:2010
A12:2011, A2:2013
Information technology equipment; Safety – Part 1:
General requirements.
Supplementary Information:
The product herewith complies with the requirements of the EMC
Directive 2014/30/EU, the Low Voltage Directive 2014/35/EU and the
ROHS Directive 2011/65/EU.
The product was tested in typical configurations.
Signed for and on behalf of
RAD Data Communications Ltd.
Tel Aviv, 13 March 2017
Zohar Zosmanovich
Compliance Team Leader
European Contact:
xii
RAD Data Communications GmbH
Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
Megaplex-4
Installation and Operation Manual
Front Matter
Your Network’s Edge
EU Declaration of Conformity
Manufacturer's Name:
RAD Data Communications Ltd.
Manufacturer's Address:
24 Raoul Wallenberg St., Tel Aviv 6971920, Israel
declares under its sole responsibility that the product:
Product Name:
MPF
Product Options:
MPF/48/120VDC (may be followed by several suffixes separated by
slashes)
conforms to the following standard(s) or other normative document(s)
in accordance with the relevant European Union harmonization
legislation:
EMC
EN 55032: 2012+
Electromagnetic Compatibility of multimedia equipment – Emissions
AC/2013
requirements.
EN 55024:2010
(in accordance with
EN 61000-42/3/4/5/6/11)
Information technology equipment; Immunity characteristics;
EN 61000-3-2:2014
Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic
Limits and methods of measurement.
current emissions (equipment input current ≤ 16A per phase)
EN 61000-3-3:2013
Electromagnetic compatibility (EMC); Section 3-3: Limits Limitation of voltage changes, voltage fluctuations and flicker in public
low-voltage supply systems, for equipment with rated current ≤ 16A per
phase and not subject to conditional connection.
Safety
EN 60950-1:2006 +
Information technology equipment; Safety – Part 1:
A11:2009, A1:2010
General requirements.
A12:2011, A2:2013
Supplementary Information:
The product herewith complies with the requirements of the EMC
Directive 2014/30/EU, the Low Voltage Directive 2014/35/EU and the
ROHS Directive 2011/65/EU.
The product was tested in typical configurations.
Signed for and on behalf of
RAD Data Communications Ltd.
Tel Aviv, 13 March 2017
Zohar Zosmanovich
Compliance Team Leader
European Contact:
RAD Data Communications GmbH
Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
Megaplex-4
xiii
Front Matter
xiv
Installation and Operation Manual
Megaplex-4
Quick Start Guide
This section describes the minimum configuration needed to prepare
Megaplex-4 for operation.
1.
Installing the Unit
Perform the following steps to install the unit:
1. Determine the required configuration of Megaplex-4, according to your
application.
2. Install the Megaplex-4 enclosure.
3. Install the modules in accordance with the site installation plan.
4. Connect the ASCII terminal to the RS-232 control port.
5. Connect power to the unit.
Connecting the Interfaces
To connect the interfaces:
1. Insert the SFP modules (if applicable) into the relevant SFP-based Ethernet
ports.
2. Refer to the site installation plan, and connect the prescribed cables to the
Megaplex-4 modules.
Connecting to a Terminal
To connect to an ASCII terminal:
1. Connect one side of the cable supplied by RAD (CBL-DB9F-DB9M-STR for
Megaplex-4100, CBL-MUSB-DB9F for Megaplex-4104) to the Megaplex
connector, designated CONTROL DCE.
2. Connect the other side of the cable to the ASCII terminal equipment.
Connecting the Power
Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Megaplex-4
Installing the Unit
1
Quick Start Guide
Installation and Operation Manual
2.
Configuring the Unit for Management
Configure Megaplex-4 for management, using a local ASCII-based terminal.
Starting a Terminal Session for the First Time
To start the terminal session:
1. Connect an ASCII terminal to the CONTROL DCE connector of the active CL
module (use a straight cable).
2. Configure the ASCII terminal to the settings listed below and then set the
terminal emulator to VT100 emulation for optimal view of system menus.
Data Rate:
9,600 bps
Data bits:
8
Parity:
None
Stop bits:
1
Flow control:
None.
3. If you are using HyperTerminal, set the terminal mode to 132-column mode
for optimal view of system menus (Properties> Settings> Terminal Setup>
132 column mode).
4. Turn the power on.
Note
The Megaplex-4 PS modules do not include a power switch. Use an external
power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
5. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
After a few seconds, Megaplex-4 starts decompressing its software.
After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4 performs
its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4.
6. When the startup process is completed, you are prompted to press <Enter>
to receive the login prompt.
7. Press <Enter> until you receive the login prompt.
8. If the Megaplex-4 default user name and password have not yet been
changed, log in as administrator using su as the user name (su for full
configuration and monitoring access) and 1234 for password.
9. The device prompt appears:
mp4100#
You can now type the necessary CLI commands.
2
Configuring the Unit for Management
Megaplex-4
Installation and Operation Manual
Quick Start Guide
Configuring the Router
The router must be configured with a router interface that is bound to the SVI
used for the management flows, and assigned an IP address. Also, a static route
must be set up for the default gateway.
This section illustrates the following configuration:
•
•
Router interface 1:
Bound to SVI 1
IP address 172.17.154.96 with mask 255.255.255.0
Router: Static route associated with IP address 172.17.154.1 (default
gateway).
To define the router:
•
Enter the following commands:
configure router 1
interface 1
bind svi 1
# IP address 172.17.154.96 with mask 255.255.255.0
address 172.17.154.96/24
no shutdown
exit
# Default gateway 172.17.154.1
static-route 0.0.0.0/0 address 172.17.154.1
exit all
3.
Saving Management Configuration
Saving Configuration
Type save in any level to save your configuration in startup-config.
Copying User Configuration to Default Configuration
In addition to saving your configuration in startup-config, you may also wish to
save your configuration as a user default configuration.
Megaplex-4
Saving Management Configuration
3
Quick Start Guide
Installation and Operation Manual
To save user default configuration:
•
Enter the following commands:
exit all
file copy startup-config user-default-config
y
4.
Verifying Connectivity
At the ASCII terminal, ping the IP address assigned to Megaplex-4 and verify that
replies are received. If there is no reply to the ping, check your configuration and
make the necessary corrections.
4
Verifying Connectivity
Megaplex-4
Contents
Chapter 1. Introduction
1.1
1.2
1.3
Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-1
Chassis .......................................................................................................................... 1-1
IEEE-1613 Compliance ................................................................................................... 1-2
CL Modules.................................................................................................................... 1-2
PS Modules ................................................................................................................... 1-4
Applications ....................................................................................................................... 1-5
Central Solution for RAD CPE Devices ............................................................................ 1-5
TDM and Ethernet Multiservice Access .......................................................................... 1-5
Smooth Migration from TDM to PSN.............................................................................. 1-6
Carrier Ethernet Services ............................................................................................... 1-7
Features .......................................................................................................................... 1-10
Forwarding Schemes ................................................................................................... 1-10
Service Types .............................................................................................................. 1-11
Flow Classification ....................................................................................................... 1-11
Tagging and Marking ................................................................................................... 1-12
L2CP Handling ............................................................................................................. 1-12
Fault Propagation ........................................................................................................ 1-13
Traffic Management and Service Level Agreement (SLA) Monitoring, Troubleshooting and
Measurement .............................................................................................................. 1-13
Flexible Ethernet Transport over TDM .......................................................................... 1-16
Flexible TDM Transport over Ethernet .......................................................................... 1-16
Fiber Multiplexing ........................................................................................................ 1-16
DS0 Cross-Connect ..................................................................................................... 1-16
Protection ................................................................................................................... 1-17
Diversity of Rings ........................................................................................................ 1-18
Modularity and Flexibility ............................................................................................. 1-18
Next-Generation ADM/Terminal ................................................................................... 1-18
Timing ......................................................................................................................... 1-18
Simple Network Time Protocol .................................................................................... 1-19
Management ............................................................................................................... 1-19
Syslog ......................................................................................................................... 1-20
Diagnostics ................................................................................................................. 1-21
Alarm Collection and Reporting ................................................................................... 1-21
Performance Monitoring.............................................................................................. 1-21
RADview Performance Management ............................................................................ 1-22
Security ....................................................................................................................... 1-22
New in this Version ............................................................................................................ 1-22
Physical Description ........................................................................................................... 1-23
System Structure ............................................................................................................. 1-23
Description of Megaplex-4100 Chassis ............................................................................. 1-23
Rear View .................................................................................................................... 1-24
Front Panel ................................................................................................................. 1-25
Description of IEEE-1613 compliant Megaplex-4100 Chassis ............................................ 1-25
Rear View .................................................................................................................... 1-26
Front Panel ................................................................................................................. 1-27
Description of Megaplex-4104 Chassis ............................................................................. 1-28
I/O Modules ..................................................................................................................... 1-29
Common Logic (CL.2) Modules ......................................................................................... 1-34
Megaplex-4
i
Table of Contents
1.4
1.5
Installation and Operation Manual
Power Supply (PS) Modules .............................................................................................. 1-35
PS Modules ................................................................................................................. 1-35
Feed and Ring Voltage Sources ................................................................................... 1-35
Functional Description ........................................................................................................ 1-36
Megaplex-4 Architecture .................................................................................................. 1-36
TDM Engine ...................................................................................................................... 1-38
DS0 Cross-Connect Matrix ........................................................................................... 1-38
DS1 Cross-Connect Matrix ........................................................................................... 1-40
E1/T1 Framers and Mappers ........................................................................................ 1-40
SDH/SONET Engine .......................................................................................................... 1-41
SDH/SONET Network Port Interfaces ........................................................................... 1-41
SDH/SONET Framer and LO/HO Cross-Connect Matrix ................................................. 1-41
Packet Engine .................................................................................................................. 1-41
Packet Processor ......................................................................................................... 1-42
Carrier Ethernet (CL.2/A Assembly) ............................................................................. 1-43
VCAT Engine ................................................................................................................ 1-46
HO/LO Mapper ............................................................................................................ 1-46
Ethernet over SDH/SONET, Full/Channelized T3, E1/T1 - General Concept ................... 1-46
Ethernet over E1/T1 .................................................................................................... 1-47
Ethernet over SDH/SONET ........................................................................................... 1-48
Ethernet over Full/Channelized T3 ............................................................................... 1-49
Megaplex-4 Architecture Entities ..................................................................................... 1-50
Technical Specifications...................................................................................................... 1-56
Chapter 2. Installation
2.1
2.2
2.3
2.4
2.5
2.6
ii
Safety .................................................................................................................................. 2-1
Safety Precautions ............................................................................................................. 2-1
Grounding .......................................................................................................................... 2-2
Laser Safety ....................................................................................................................... 2-3
Protection against ESD ...................................................................................................... 2-3
Site Requirements and Prerequisites .................................................................................... 2-4
AC Power Requirements ..................................................................................................... 2-4
DC Power Requirements .................................................................................................... 2-4
Front and Rear Panel Clearance ......................................................................................... 2-5
Ambient Requirements ...................................................................................................... 2-5
Megaplex-4100 – Regular Chassis ................................................................................. 2-5
Megaplex-4100 – IEEE-1613 Compliant Chassis ............................................................. 2-5
Megaplex-4104 ............................................................................................................. 2-6
Electromagnetic Compatibility Considerations .................................................................... 2-7
Optical Cable Requirements ............................................................................................... 2-7
Package Contents................................................................................................................. 2-7
Megaplex-4100 Package Contents ..................................................................................... 2-7
Megaplex-4104 Package Contents ..................................................................................... 2-8
Required Equipment ............................................................................................................. 2-8
Mounting the Products ......................................................................................................... 2-9
Installing the Regular Megaplex-4100 Chassis .................................................................... 2-9
Installing in a 19” Rack .................................................................................................. 2-9
Installing in 23” Rack................................................................................................... 2-10
Installing the IEEE-1613 Compliant Megaplex-4100 Chassis in a 19” Rack ........................ 2-10
Installing the Megaplex-4104 Chassis............................................................................... 2-12
Installing Modules .............................................................................................................. 2-12
Installing PS Modules ....................................................................................................... 2-12
Megaplex-4100 Module Panels .................................................................................... 2-13
Megaplex-4
Installation and Operation Manual
Table of Contents
Megaplex-4104 Module Panels .................................................................................... 2-14
Megaplex-4100 Internal Jumpers ................................................................................. 2-15
Megaplex-4104 Internal Jumpers ................................................................................. 2-16
Installing a PS Module ................................................................................................. 2-18
Removing a PS Module ................................................................................................ 2-18
Installing CL Modules........................................................................................................ 2-18
Megaplex-4100 Module Panels .................................................................................... 2-18
Megaplex-4104 Module Panels .................................................................................... 2-24
Installing and Replacing SFPs ....................................................................................... 2-27
Installing a CL Module.................................................................................................. 2-29
Removing a CL Module ................................................................................................ 2-30
Replacing a CL Module during Equipment Operation –Megaplex-4 Chassis with two CL
Modules ...................................................................................................................... 2-30
Replacing a CL Module during Equipment Operation –Megaplex-4 Chassis with Single CL
Module ........................................................................................................................ 2-31
Adding a Protection CL Module to a Working Module Configured as SONET ................. 2-31
Installing System Modules in Megaplex-4104 Chassis ....................................................... 2-32
Installing I/O Modules ...................................................................................................... 2-32
Installing Blank Panels ...................................................................................................... 2-32
2.7 Connecting to Power .......................................................................................................... 2-32
Grounding Megaplex-4 ..................................................................................................... 2-32
Connecting to Power ....................................................................................................... 2-33
Connecting to External Feed Voltages .............................................................................. 2-33
2.8 Connecting Megaplex-4 to a Terminal................................................................................. 2-33
Megaplex-4100 CL.2 Module ............................................................................................ 2-34
Megaplex-4104 CL.2 Module ............................................................................................ 2-34
2.9 Connecting to a Management Station or Telnet Host ......................................................... 2-35
2.10 Connecting to a Station Clock ............................................................................................ 2-35
2.11 Connecting to Alarm Equipment ......................................................................................... 2-36
2.12 Connecting to SDH/SONET Equipment ................................................................................ 2-37
Connecting Optical Cables to the SDH/SONET Links ......................................................... 2-37
Connecting Coaxial Cables to SDH/SONET Links................................................................ 2-38
2.13 Connecting to E1 and T1 Equipment .................................................................................. 2-39
2.14 Connecting to Ethernet Equipment..................................................................................... 2-39
Chapter 3. Operation and Maintenance
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
Turning On the Unit ............................................................................................................. 3-1
Indicators ............................................................................................................................. 3-2
CL.2 Front Panel Indicators ................................................................................................ 3-2
Front Panel Indicators ........................................................................................................ 3-5
Startup ................................................................................................................................. 3-6
Configuration Files ............................................................................................................. 3-6
Loading Sequence .............................................................................................................. 3-7
Working with Custom Configuration File ............................................................................... 3-7
Configuration and Management ........................................................................................... 3-8
Management Access Methods .............................................................................................. 3-9
Layer-3 Management Access ......................................................................................... 3-9
Layer-2 Management Access ....................................................................................... 3-10
Services for Management Traffic ........................................................................................ 3-11
CLI-Based Configuration ..................................................................................................... 3-11
Working with Terminal ..................................................................................................... 3-11
Working with Telnet and SSH ........................................................................................... 3-14
Working with Telnet .................................................................................................... 3-14
Megaplex-4
iii
Table of Contents
Installation and Operation Manual
Using SSH ................................................................................................................... 3-14
Login ............................................................................................................................... 3-15
Using the CLI .................................................................................................................... 3-16
CLI Prompt .................................................................................................................. 3-17
Navigating ................................................................................................................... 3-17
Command Tree ............................................................................................................ 3-18
Command Structure .................................................................................................... 3-19
Special Keys ................................................................................................................ 3-19
Getting Help ................................................................................................................ 3-20
Using Scripts .................................................................................................................... 3-24
3.9 SNMP-Based Network Management ................................................................................... 3-24
Preconfiguring Megaplex-4 for SNMP Management .......................................................... 3-24
Working with RADview ..................................................................................................... 3-26
Working with Shelf View .................................................................................................. 3-26
Working with Other SNMP-Based NMS ............................................................................. 3-26
3.10 Turning Off the Unit ........................................................................................................... 3-27
Chapter 4. Service Provisioning
4.1
Service Elements .................................................................................................................. 4-1
Profiles .............................................................................................................................. 4-1
Scheduling and Shaping Entities......................................................................................... 4-2
Physical Ports .................................................................................................................... 4-2
Logical Ports ...................................................................................................................... 4-3
Forwarding Entities ............................................................................................................ 4-4
29BFlows ............................................................................................................................ 4-4
30BBridge ........................................................................................................................... 4-5
31BRouter........................................................................................................................... 4-5
4.2 Services Provided by Megaplex-4 .......................................................................................... 4-5
4.3 E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a) ...................................... 4-14
4.4 E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b) ................................................... 4-16
4.5 E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a) ...................................... 4-18
4.6 Fast Ethernet Traffic to PSN over Fiber (2b) ....................................................................... 4-20
4.7 Fast Ethernet Traffic to SDH/SONET (3) ............................................................................. 4-21
4.8 Shared E-LAN Service with Multiple Drops per Node over SDH/SONET ................................ 4-23
4.9 E1 to SDH Traffic over Copper via DS0 Mapping (3a) .......................................................... 4-26
4.10 Fast Ethernet Traffic to PSN over Copper (3b).................................................................... 4-28
4.11 High-Speed Traffic to SDH/SONET (4) ................................................................................ 4-29
4.12 High-Speed Traffic to PSN (4a, 4b) .................................................................................... 4-31
4.13 Low-Latency High-Speed Traffic to PSN (4c, 4d) ................................................................ 4-34
4.14 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection ..................... 4-37
4.15 Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a) ........................................................... 4-41
4.16 Fast Ethernet Traffic to Multiple E1 (MLPPP Protocol) (5b) ................................................. 4-44
4.17 Voice Traffic to SDH/SONET (6) .......................................................................................... 4-45
4.18 Voice Traffic to PSN (6a) .................................................................................................... 4-47
4.19 Teleprotection Traffic to SDH/SONET (7) ............................................................................ 4-50
4.20 T3 Traffic to SONET (8) ...................................................................................................... 4-52
4.21 Voice to T3 via DS0 Cross-Connect (9) ............................................................................... 4-54
4.22 Ethernet Traffic over PDH to SDH/SONET (10a) .................................................................. 4-55
4.23 Ethernet Traffic over PDH to E1/T1 (10b) ........................................................................... 4-57
Chapter 5. Cards and Ports
5.1
iv
Cards.................................................................................................................................... 5-1
Megaplex-4
Installation and Operation Manual
5.2
5.3
5.4
5.5
5.6
Table of Contents
Configuring Modules in the Chassis .................................................................................... 5-1
Example ............................................................................................................................. 5-3
Displaying Modules in the Chassis ...................................................................................... 5-3
Displaying Ports in the Chassis ......................................................................................... 5-15
Example 1: Displaying all Ports in the Modules Installed in the System ........................ 5-15
Example 2: Displaying Ethernet Ports in the Modules Installed in the System .............. 5-16
Example 3: Displaying All Ports in the Modules Installed in the System including Tx/Rx
Statistics for Ethernet-type Ports ................................................................................ 5-17
Example 4: Displaying Ethernet Ports in the Modules Installed in the System including
Tx/Rx Statistics ............................................................................................................ 5-17
Resetting I/O Modules ..................................................................................................... 5-18
Configuration Errors ......................................................................................................... 5-18
Port-Related Profiles .......................................................................................................... 5-19
Signaling Profiles ............................................................................................................. 5-19
Functional Description................................................................................................. 5-19
Factory Defaults .......................................................................................................... 5-19
Configuring CAS Signaling Profiles ............................................................................... 5-20
Example ...................................................................................................................... 5-22
Analog Signaling Profiles .................................................................................................. 5-22
Functional Description................................................................................................. 5-22
Factory Defaults .......................................................................................................... 5-25
Configuring Analog Signaling Profiles .......................................................................... 5-25
Example ...................................................................................................................... 5-26
VC Profiles ....................................................................................................................... 5-27
Factory Defaults .......................................................................................................... 5-28
Configuring VC Profiles ................................................................................................ 5-28
L2CP Profiles .................................................................................................................... 5-30
Factory Defalts............................................................................................................ 5-30
Configuring L2CP Profiles ............................................................................................ 5-30
Binary Command Ports ....................................................................................................... 5-32
Applicable Modules .......................................................................................................... 5-32
Functional Description ..................................................................................................... 5-32
Factory Defaults .............................................................................................................. 5-32
Configuring Binary Command Ports .................................................................................. 5-32
Configuring CMD-IN Ports ............................................................................................ 5-32
Configuring CMD-OUT Ports ........................................................................................ 5-33
Configuring CMD-CHANNEL Ports................................................................................. 5-33
Viewing Status Information .............................................................................................. 5-34
Displaying Binary Command Statistics .............................................................................. 5-35
BRI Ports ............................................................................................................................ 5-36
Applicable Modules .......................................................................................................... 5-36
Standards Compliance...................................................................................................... 5-36
Functional Description ..................................................................................................... 5-36
Factory Defaults .............................................................................................................. 5-36
Configuring a BRI (ISDN) Port ........................................................................................... 5-36
Example ........................................................................................................................... 5-37
Control Port ....................................................................................................................... 5-38
Standards Compliance...................................................................................................... 5-38
Functional Description ..................................................................................................... 5-38
Factory Defaults .............................................................................................................. 5-38
Configuring the Control Port ............................................................................................ 5-38
DS0-Bundle Ports ............................................................................................................... 5-39
Applicable Modules .......................................................................................................... 5-39
Standards Compliance...................................................................................................... 5-39
Megaplex-4
v
Table of Contents
Installation and Operation Manual
Benefits ........................................................................................................................... 5-39
Functional Description ..................................................................................................... 5-39
Factory Defaults .............................................................................................................. 5-40
Configuring DS0 Bundle Ports .......................................................................................... 5-40
Viewing DS0-Bundle Status Information ........................................................................... 5-40
Configuration Errors ......................................................................................................... 5-41
Displaying DS0-Bundle Statistics ...................................................................................... 5-42
5.7 DS1 Ports ........................................................................................................................... 5-43
Applicable Modules .......................................................................................................... 5-43
Functional Description ..................................................................................................... 5-43
Factory Defaults .............................................................................................................. 5-44
Configuring Internal DS1 Port Parameters ........................................................................ 5-44
Example ........................................................................................................................... 5-45
Viewing DS1 Port Status .................................................................................................. 5-45
Testing DS1 Ports ............................................................................................................ 5-46
Local Loopback on DS1 Port of I/O Module ................................................................. 5-47
Remote Loopback on DS1 Port of I/O Module ............................................................. 5-47
Local Loopback on Timeslots of DS1 I/O Module Port .................................................. 5-48
Remote Loopback on Timeslots of DS1 I/O Module Port.............................................. 5-48
Loopback Duration ...................................................................................................... 5-48
Activating Loopbacks .................................................................................................. 5-49
Configuration Errors ......................................................................................................... 5-49
5.8 DS1 Optical Ports ............................................................................................................... 5-50
Applicable Modules .......................................................................................................... 5-50
Standards Compliance...................................................................................................... 5-50
Functional Description ..................................................................................................... 5-50
Factory Defaults .............................................................................................................. 5-50
Configuring DS1 Optical Port Parameters ......................................................................... 5-50
Viewing a DS1-Opt Port Status ........................................................................................ 5-51
Testing DS1 Optical Links ................................................................................................. 5-51
Local Digital Loopback (Local Loop) ............................................................................ 5-51
Remote Digital Loopback (Remote Loop) .................................................................... 5-52
Loopback Duration ...................................................................................................... 5-52
Activating the Loopbacks ............................................................................................ 5-53
5.9 Ethernet Ports .................................................................................................................... 5-53
Applicable Modules .......................................................................................................... 5-53
Standards Compliance...................................................................................................... 5-53
Functional Description ..................................................................................................... 5-53
GbE Port Interfaces ..................................................................................................... 5-53
Fast Ethernet Port Interfaces ...................................................................................... 5-54
Hierarchy and Values ................................................................................................... 5-54
Flow Control ................................................................................................................ 5-55
L2CP Handling ............................................................................................................. 5-56
Autonegotiation .......................................................................................................... 5-57
Queue Group Profile .................................................................................................... 5-57
Factory Defaults .............................................................................................................. 5-57
Configuring User Ethernet Ports ....................................................................................... 5-58
Example ........................................................................................................................... 5-61
Displaying Ethernet Port Status ....................................................................................... 5-61
Testing Ethernet Ports ..................................................................................................... 5-62
Configuration Errors ......................................................................................................... 5-62
Displaying Ethernet Port Statistics ................................................................................... 5-62
5.10 E1 Ports ............................................................................................................................. 5-65
Applicable Modules .......................................................................................................... 5-65
vi
Megaplex-4
Installation and Operation Manual
Table of Contents
Standards Compliance...................................................................................................... 5-67
Functional Description ..................................................................................................... 5-67
Framing ....................................................................................................................... 5-67
Interface Type ............................................................................................................. 5-68
Receive Signal Attenuation (M8E1, VS-6/E1T1, VS-16E1T1-PW and VS-16E1T1-EoP
Modules) ..................................................................................................................... 5-68
E1 Payload Processing ................................................................................................. 5-68
Handling E1 Alarm Conditions ..................................................................................... 5-69
OOS Signaling ............................................................................................................. 5-69
Inband Management ................................................................................................... 5-70
Interoperability with Nokia clock distribution (PDH Sync) ............................................ 5-70
Factory Defaults .............................................................................................................. 5-70
Configuring E1 Ports ........................................................................................................ 5-71
Examples ......................................................................................................................... 5-76
Example 1 ................................................................................................................... 5-76
Example 2 ................................................................................................................... 5-77
Example 3 ................................................................................................................... 5-77
Configuration Errors ......................................................................................................... 5-78
Viewing an E1 Port Status ................................................................................................ 5-78
Testing E1 Ports ............................................................................................................... 5-79
CL Modules.................................................................................................................. 5-80
I/O Modules ................................................................................................................ 5-83
Loopback Duration ...................................................................................................... 5-89
Activating Loopbacks and BER Tests............................................................................ 5-89
Displaying E1 Port Statistics ............................................................................................. 5-91
5.11 E1-i, T1-i Ports ................................................................................................................... 5-95
5.12 G.703 Ports ........................................................................................................................ 5-95
Applicable Modules .......................................................................................................... 5-95
Standards Compliance...................................................................................................... 5-95
Functional Description ..................................................................................................... 5-95
Factory Defaults .............................................................................................................. 5-97
Configuring DS0-G703 Port Parameters ........................................................................... 5-97
Viewing a DS0-G703 Port Status ...................................................................................... 5-98
Testing DS0-G703 Links ................................................................................................... 5-98
Local Digital Loopback (Local Loop) ............................................................................ 5-98
Remote Digital Loopback (Remote Loop) .................................................................... 5-98
Loopback Duration ...................................................................................................... 5-99
Activating Loopbacks and BER Tests............................................................................ 5-99
5.13 GFP Ports ......................................................................................................................... 5-100
Applicable Modules ........................................................................................................ 5-100
Standards Compliance.................................................................................................... 5-100
Factory Defaults ............................................................................................................ 5-100
Configuring GFP Ports .................................................................................................... 5-100
Displaying GFP Statistics ................................................................................................ 5-101
5.14 HDLC Ports (CL.2 Modules) ............................................................................................... 5-104
Applicable Modules ........................................................................................................ 5-104
Standards Compliance.................................................................................................... 5-104
Factory Defaults ............................................................................................................ 5-104
Configuring HDLC Ports .................................................................................................. 5-104
Displaying HDLC Statistics .............................................................................................. 5-105
5.15 HDLC Ports (I/O Modules) ................................................................................................. 5-107
Applicable Modules ........................................................................................................ 5-107
Standards Compliance.................................................................................................... 5-107
Factory Defaults ............................................................................................................ 5-107
Megaplex-4
vii
Table of Contents
Installation and Operation Manual
Configuring HDLC Ports .................................................................................................. 5-107
Configuration Errors ....................................................................................................... 5-108
5.16 Internal Ethernet (D-NFV) Ports ....................................................................................... 5-109
Applicable Modules ........................................................................................................ 5-109
Standards Compliance.................................................................................................... 5-109
Factory Defaults ............................................................................................................ 5-109
Configuring Internal Ethernet Ports ................................................................................ 5-110
Displaying D-NFV Internal Ethernet Port Status .............................................................. 5-111
Testing D-NFV Ports ....................................................................................................... 5-111
Displaying Ethernet Port Statistics ................................................................................. 5-111
5.17 Logical MAC Ports ............................................................................................................. 5-113
Applicable Modules ........................................................................................................ 5-113
Factory Defaults ............................................................................................................ 5-113
Configuring Logical MAC Ports ........................................................................................ 5-114
Viewing MAC Address ..................................................................................................... 5-115
Displaying Logical MAC Statistics .................................................................................... 5-115
5.18 Management Ethernet Port .............................................................................................. 5-116
Benefits ......................................................................................................................... 5-117
Configuring the Out-Of-Band Management Port ............................................................ 5-117
5.19 Management Ethernet Port – Controlled Forwarding ........................................................ 5-117
Benefits ......................................................................................................................... 5-117
Functional Description ................................................................................................... 5-118
Configuring the Out-Of-Band Management Port Controlled Forwarding ......................... 5-118
5.20 MLPPP Ports ..................................................................................................................... 5-119
Applicable Modules ........................................................................................................ 5-119
Standards Compliance.................................................................................................... 5-119
Factory Defaults ............................................................................................................ 5-120
Configuring MLPPP Ports ................................................................................................ 5-120
Example ......................................................................................................................... 5-120
Configuration Errors ....................................................................................................... 5-121
5.21 Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules) ............................................. 5-121
Applicable Modules ........................................................................................................ 5-121
Standards Compliance.................................................................................................... 5-122
Functional Description ................................................................................................... 5-122
Factory Defaults ............................................................................................................ 5-124
Configuring Optical Link Parameters and Accessing the Remote Unit ............................. 5-124
Configuring the Local Optical Link ............................................................................. 5-124
Configuring the Remote Optimux .............................................................................. 5-126
Example ......................................................................................................................... 5-128
Configuration Errors ....................................................................................................... 5-128
Viewing Optical Link SFP Status Information .................................................................. 5-129
Testing Optical Links ...................................................................................................... 5-130
Local Loopback on Local Optical Link......................................................................... 5-130
Remote Loopback on Local Optical Link .................................................................... 5-131
Link Local Loopback on Remote Optimux .................................................................. 5-132
Link Remote Loopback on Remote Optimux .............................................................. 5-132
Loopback Duration .................................................................................................... 5-133
Activating the Loopbacks .......................................................................................... 5-133
5.22 PCS Ports ......................................................................................................................... 5-134
Applicable Modules ........................................................................................................ 5-134
Standards Compliance.................................................................................................... 5-135
Functional Description ................................................................................................... 5-135
Factory Defaults ............................................................................................................ 5-136
Configuring a PCS Port ................................................................................................... 5-137
viii
Megaplex-4
Installation and Operation Manual
Table of Contents
Displaying PCS Port Status ............................................................................................. 5-138
Testing PCS Ports ........................................................................................................... 5-138
Displaying PCS Statistics ................................................................................................ 5-139
5.23 PPP Ports ......................................................................................................................... 5-140
Applicable Modules ........................................................................................................ 5-140
Standards Compliance.................................................................................................... 5-140
Factory Defaults ............................................................................................................ 5-140
Configuring PPP Ports .................................................................................................... 5-140
Example ......................................................................................................................... 5-141
Configuration Errors ....................................................................................................... 5-142
5.24 Serial Ports ....................................................................................................................... 5-142
Applicable Modules ........................................................................................................ 5-142
Standards Compliance.................................................................................................... 5-144
Functional Description ................................................................................................... 5-145
Factory Defaults ............................................................................................................ 5-145
Configuring Serial Port Parameters................................................................................. 5-146
Example ......................................................................................................................... 5-151
Viewing Status Information ............................................................................................ 5-151
Displaying VS Serial Port Statistics ................................................................................. 5-153
Configuration Errors ....................................................................................................... 5-153
Testing Serial Ports ........................................................................................................ 5-155
Local Digital Loopback (Local Loop) .......................................................................... 5-155
Remote Digital Loopback (Remote Loop) .................................................................. 5-156
Loopback Duration .................................................................................................... 5-157
Activating the Loopbacks .......................................................................................... 5-157
5.25 Serial Bundle Ports ........................................................................................................... 5-158
Applicable Modules ........................................................................................................ 5-158
Functional Description ................................................................................................... 5-158
Factory Defaults ............................................................................................................ 5-158
Configuring Serial Bundle Port Parameters ..................................................................... 5-158
Example ......................................................................................................................... 5-159
Configuration Errors ....................................................................................................... 5-159
Testing Serial-Bundle Ports ............................................................................................ 5-160
Composite Data Stream Local Digital Loopback ......................................................... 5-160
Composite Data Stream Remote Digital Loopback ..................................................... 5-160
Loopback Duration .................................................................................................... 5-162
Activating the Loopbacks .......................................................................................... 5-162
5.26 SDH/SONET Ports ............................................................................................................. 5-163
Applicable Modules ........................................................................................................ 5-163
Standards Compliance.................................................................................................... 5-163
Functional Description ................................................................................................... 5-163
SDH Implementation Principles .................................................................................. 5-163
Direct Multiplexing Approach ..................................................................................... 5-164
General Structure of SDH Signals .............................................................................. 5-164
SDH Frame Organization ........................................................................................... 5-165
VC Assembly/Disassembly Process ............................................................................. 5-166
STM-1 Frame Structure ............................................................................................. 5-167
Pointers .................................................................................................................... 5-168
SDH Overhead Data .................................................................................................. 5-168
SDH Tributary Units ................................................................................................... 5-173
SDH Maintenance Signals and Response to Abnormal Conditions .............................. 5-176
SONET Environment .................................................................................................. 5-179
SDH/SONET Interfaces............................................................................................... 5-180
Automatic Laser Shutdown ....................................................................................... 5-180
Megaplex-4
ix
Table of Contents
Installation and Operation Manual
Inband Management Access through SDH/SONET Networks ...................................... 5-180
SDH/SONET Hierarchy and Allowed Activities............................................................. 5-182
Factory Defaults (SDH/SONET Parameters) .................................................................... 5-182
Configuring an SDH/SONET Link ..................................................................................... 5-183
Assigning VC Profiles to AUG/OC-3 ................................................................................. 5-185
Configuration Errors ....................................................................................................... 5-186
Viewing SDH/SONET Status Information ......................................................................... 5-189
Testing SDH/SONET Ports .............................................................................................. 5-192
Remote Loopback on SDH/SONET Link ...................................................................... 5-193
Local Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5 ....................................... 5-193
Remote Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5 ................................... 5-194
Loopback Duration .................................................................................................... 5-194
Activating Loopbacks ................................................................................................ 5-194
Displaying SDH/SONET Statistics .................................................................................... 5-195
5.27 SHDSL Ports ..................................................................................................................... 5-199
Applicable Modules ........................................................................................................ 5-199
Standards Compliance.................................................................................................... 5-202
Benefits ......................................................................................................................... 5-202
Functional Description ................................................................................................... 5-202
SHDSL Transmission Subsystem Structure ................................................................. 5-202
SHDSL Modulation Method ........................................................................................ 5-202
Handling of Timeslot 0 .............................................................................................. 5-203
Management via Embedded Operational Channel (EOC) ............................................ 5-203
Single IP Management ............................................................................................... 5-203
Factory Defaults ............................................................................................................ 5-204
Configuring an SHDSL Port ............................................................................................. 5-204
Displaying the Status of SHDSL Port and Repeaters ....................................................... 5-208
Testing SHDSL Ports ...................................................................................................... 5-209
Local Port Loopback (M8SL only)............................................................................... 5-209
Remote Port Loopback (M8SL only) .......................................................................... 5-210
Remote Loopback on Remote Unit ............................................................................ 5-211
Activating SHDSL Loopbacks ..................................................................................... 5-211
Configuration Errors ....................................................................................................... 5-212
Displaying SHDSL Port Statistics..................................................................................... 5-214
Displaying SHDSL Repeater Statistics ............................................................................. 5-217
5.28 SVI (Switched Virtual Interface) Ports ............................................................................... 5-219
5.29 T1 Ports ........................................................................................................................... 5-220
Applicable Modules ........................................................................................................ 5-220
Standards Compliance.................................................................................................... 5-221
Functional Description ................................................................................................... 5-221
Framing ..................................................................................................................... 5-221
Line Interface (M8T1, VS-16E1T1-EoP, VS-16E1T1-PW, VS-6/E1T1 Only) ................... 5-221
Line Length ............................................................................................................... 5-222
Zero Suppression ...................................................................................................... 5-222
Interface Type ........................................................................................................... 5-222
Handling of T1 Alarm Conditions ............................................................................... 5-222
T1 Payload Processing ............................................................................................... 5-223
OOS Signaling ........................................................................................................... 5-223
Inband Management ................................................................................................. 5-224
Factory Defaults ............................................................................................................ 5-224
Configuring a T1 Port ..................................................................................................... 5-225
Configuring an Internal T1 Port ...................................................................................... 5-227
Examples ....................................................................................................................... 5-228
Example 1 ................................................................................................................. 5-228
x
Megaplex-4
Installation and Operation Manual
Table of Contents
Example 2 ................................................................................................................. 5-229
Example 3 ................................................................................................................. 5-229
Configuration Errors ....................................................................................................... 5-230
Viewing a T1 Port Status ................................................................................................ 5-230
Testing T1 Ports ............................................................................................................. 5-231
CL Modules................................................................................................................ 5-231
I/O Modules .............................................................................................................. 5-234
Loopback Duration .................................................................................................... 5-236
Activating Loopbacks and BER Tests.......................................................................... 5-236
Displaying T1 Port Statistics ........................................................................................... 5-237
5.30 T3 Ports ........................................................................................................................... 5-241
Applicable Modules ........................................................................................................ 5-241
Standards Compliance.................................................................................................... 5-241
Functional Description ................................................................................................... 5-241
Framing ..................................................................................................................... 5-241
Line Length ............................................................................................................... 5-242
Interface Type ........................................................................................................... 5-242
Factory Defaults ............................................................................................................ 5-242
Configuring a T3 Port ..................................................................................................... 5-242
Configuration Errors ....................................................................................................... 5-243
Viewing a T3 Port Status ................................................................................................ 5-244
Testing T3 Ports ............................................................................................................. 5-244
Local Loopback on T3 Port ........................................................................................ 5-244
Remote Loopback on T3 Port .................................................................................... 5-245
Loopback Duration .................................................................................................... 5-245
Activating Loopbacks ................................................................................................ 5-245
Displaying T3 Port Statistics ........................................................................................... 5-246
5.31 TDM Bridge Ports ............................................................................................................. 5-250
Applicable Modules ........................................................................................................ 5-250
Standards Compliance.................................................................................................... 5-250
Factory Defaults ............................................................................................................ 5-250
Configuring TDM Bridge Ports ........................................................................................ 5-250
Example ......................................................................................................................... 5-251
5.32 Teleprotection Ports (Physical) ......................................................................................... 5-251
Applicable Modules ........................................................................................................ 5-251
Functional Description ................................................................................................... 5-251
Factory Defaults ............................................................................................................ 5-251
Configuring CMD-IN Ports .............................................................................................. 5-252
Configuring CMD-OUT Ports ........................................................................................... 5-253
Configuring CMD-CHANNEL Ports ................................................................................... 5-255
Clear-Cmd-Led Command per System ............................................................................ 5-256
Configuration Errors ....................................................................................................... 5-256
Viewing Status Information ............................................................................................ 5-257
Displaying Teleprotection Statistics................................................................................ 5-259
5.33 Teleprotection Ports (Logical) .......................................................................................... 5-260
Applicable Modules ........................................................................................................ 5-260
Functional Description ................................................................................................... 5-261
Factory Defaults ............................................................................................................ 5-261
Configuring CMD-IN-I Ports ............................................................................................ 5-261
Configuring CMD-OUT-I Ports ......................................................................................... 5-262
Viewing Status Information of Logical Teleprotection Ports ........................................... 5-262
Testing Teleprotection Ports .......................................................................................... 5-263
Loopback Duration .................................................................................................... 5-264
Activating the Loopback ............................................................................................ 5-264
Megaplex-4
xi
Table of Contents
Installation and Operation Manual
5.34 VCG Ports ......................................................................................................................... 5-264
Applicable Modules ........................................................................................................ 5-264
Standards Compliance.................................................................................................... 5-264
Benefits ......................................................................................................................... 5-265
Functional Description ................................................................................................... 5-265
Ethernet over SDH/SONET ......................................................................................... 5-265
Encapsulation Modes ................................................................................................ 5-266
Support for LCAS ....................................................................................................... 5-266
Ethernet over Full/Channelized T3 ............................................................................. 5-266
Ethernet over E1/T1 .................................................................................................. 5-267
Factory Defaults ............................................................................................................ 5-268
Configuring VCG Ports .................................................................................................... 5-268
Configuration Errors ....................................................................................................... 5-270
Viewing LCAS Status Information ................................................................................... 5-270
Displaying LCAS Statistics .............................................................................................. 5-272
5.35 Voice Ports ....................................................................................................................... 5-274
Applicable Modules ........................................................................................................ 5-274
Standards Compliance.................................................................................................... 5-276
Functional Description ................................................................................................... 5-276
Factory Defaults ............................................................................................................ 5-277
Configuring External Voice Port Parameters ................................................................... 5-278
Example ......................................................................................................................... 5-283
Configuring Internal Voice Port Parameters .................................................................... 5-283
Configuration Errors ....................................................................................................... 5-284
Viewing a Voice Port Status ........................................................................................... 5-285
Testing Voice Ports ........................................................................................................ 5-286
Local Digital Loopback (Local Loop) .......................................................................... 5-286
Remote Digital Loopback (Remote Loop) .................................................................. 5-287
Forward Tone Injection ............................................................................................. 5-288
Backward Tone Injection ........................................................................................... 5-289
Loopback Duration .................................................................................................... 5-290
Activating Loopbacks and Tone-Inject Tests .............................................................. 5-290
Chapter 6. Management and Security
6.1
6.2
6.3
xii
Access Control List (ACL) ...................................................................................................... 6-1
Standards and MIBs ........................................................................................................... 6-1
Benefits ............................................................................................................................. 6-1
Functional Description ....................................................................................................... 6-1
Binding Access Control Lists .......................................................................................... 6-1
Filtering ......................................................................................................................... 6-1
Statistics ....................................................................................................................... 6-2
Factory Defaults ................................................................................................................ 6-2
Configuring ACL ................................................................................................................. 6-2
Access-Control-Level Tasks ........................................................................................... 6-2
Management-Level Tasks .............................................................................................. 6-3
Example ........................................................................................................................ 6-4
Displaying Status ............................................................................................................... 6-4
Displaying Statistics ........................................................................................................... 6-5
Access Policy ........................................................................................................................ 6-5
Factory Defaults ................................................................................................................ 6-5
Configuring Access Policy ................................................................................................... 6-5
Authentication via RADIUS Server ......................................................................................... 6-6
Standards .......................................................................................................................... 6-6
Megaplex-4
Installation and Operation Manual
6.4
6.5
6.6
Table of Contents
Benefits ............................................................................................................................. 6-7
Functional Description ....................................................................................................... 6-7
Factory Defaults ................................................................................................................ 6-7
Configuring the RADIUS Server ........................................................................................... 6-7
Viewing the RADIUS Server Profile Status ........................................................................... 6-8
Viewing RADIUS Statistics .................................................................................................. 6-8
Authentication via TACACS+ Server....................................................................................... 6-9
Standards .......................................................................................................................... 6-9
Benefits ............................................................................................................................. 6-9
Factory Defaults ................................................................................................................ 6-9
Functional Description ..................................................................................................... 6-10
Components................................................................................................................ 6-10
Accounting .................................................................................................................. 6-10
Defining TACACS+ Server ................................................................................................. 6-11
Configuring Accounting Groups ........................................................................................ 6-12
Examples ......................................................................................................................... 6-12
Defining Server ........................................................................................................... 6-12
Defining Accounting Group.......................................................................................... 6-13
Displaying Statistics ......................................................................................................... 6-13
IEEE 802.1X - Port-based and MAC-based Network Access Control .................................... 6-14
Standards ........................................................................................................................ 6-15
Benefits ........................................................................................................................... 6-15
Factory Defaults .............................................................................................................. 6-15
Functional Description ..................................................................................................... 6-15
Components................................................................................................................ 6-15
Typical Authentication Progression.............................................................................. 6-16
Virtual Ports for MACsec Support ................................................................................ 6-17
Configuring 802.1X Access Control .................................................................................. 6-18
Example ........................................................................................................................... 6-20
Displaying Statistics ......................................................................................................... 6-25
Viewing the 802.1X Status ............................................................................................... 6-27
MACsec .............................................................................................................................. 6-28
Standards ........................................................................................................................ 6-28
Benefits ........................................................................................................................... 6-29
Factory Defaults .............................................................................................................. 6-29
Functional Description ..................................................................................................... 6-29
MACsec Key Agreement (MKA) .................................................................................... 6-31
MACsec Frames ........................................................................................................... 6-31
Confidentiality and Integrity ........................................................................................ 6-32
Enabling and Disabling ................................................................................................ 6-32
Pre-Shared Keys .......................................................................................................... 6-32
Hashing ....................................................................................................................... 6-33
MACsec Protection ...................................................................................................... 6-33
Outer VLAN Policy ....................................................................................................... 6-33
Key Server Priority....................................................................................................... 6-34
Replay Protection ........................................................................................................ 6-34
Standard MACsec ........................................................................................................ 6-34
Network with Non-MACsec Devices ............................................................................. 6-35
Multiple ERP Rings ....................................................................................................... 6-36
Using 802.1X to Authorize End Stations on Non-MACsec Ports ................................... 6-37
Configuring MACsec ......................................................................................................... 6-37
Example ........................................................................................................................... 6-39
Displaying Statistics ......................................................................................................... 6-40
Viewing the Macsec Status............................................................................................... 6-42
Megaplex-4
xiii
Table of Contents
Installation and Operation Manual
Configuration Errors ......................................................................................................... 6-43
Managers ........................................................................................................................... 6-44
Management Access........................................................................................................... 6-44
Factory Defaults .............................................................................................................. 6-45
Configuring Access ........................................................................................................... 6-45
6.9 SNMP Management ............................................................................................................ 6-46
Standards ........................................................................................................................ 6-46
Benefits ........................................................................................................................... 6-47
Functional Description ..................................................................................................... 6-47
SNMP Message Formats .............................................................................................. 6-48
The SNMPv3 Mechanism .............................................................................................. 6-52
Factory Defaults .............................................................................................................. 6-53
Configuring SNMPv3 ......................................................................................................... 6-53
Mapping SNMPv1 to SNMPv3 ........................................................................................... 6-61
Configuring SNMP Communities for SNMPv1 .................................................................... 6-62
Example ........................................................................................................................... 6-63
6.10 User Access ........................................................................................................................ 6-65
Factory Defaults .............................................................................................................. 6-65
Defining Users and Passwords ......................................................................................... 6-65
Example ........................................................................................................................... 6-66
Viewing Connected Users ................................................................................................. 6-67
6.7
6.8
Chapter 7. Resiliency and Optimization
7.1
7.2
7.3
xiv
Fault Propagation ................................................................................................................. 7-2
Functional Description ....................................................................................................... 7-2
Factory Defaults ................................................................................................................ 7-5
Configuring Fault Propagation ............................................................................................ 7-5
Configuration Errors ........................................................................................................... 7-7
APS Protection ..................................................................................................................... 7-7
Standards .......................................................................................................................... 7-8
Benefits ............................................................................................................................. 7-8
Functional Description ....................................................................................................... 7-8
Factory Defaults ................................................................................................................ 7-9
Configuring Automatic Protection Switching ...................................................................... 7-9
Adding and Removing an APS Group ............................................................................. 7-9
Binding Ports to an APS Group .................................................................................... 7-10
Viewing the Status of an APS Group ................................................................................ 7-12
Example ........................................................................................................................... 7-13
DS0 SNCP (DS0-Bundle) Protection .................................................................................... 7-13
Applicable Modules .......................................................................................................... 7-13
Benefits ........................................................................................................................... 7-14
Standards ........................................................................................................................ 7-14
Factory Defaults .............................................................................................................. 7-14
Functional Description ..................................................................................................... 7-14
DS0 Bundle Ports ........................................................................................................ 7-15
Signaling Method ........................................................................................................ 7-15
Local and External Service Protection .......................................................................... 7-15
Control Bit ................................................................................................................... 7-15
Configuration Procedure ............................................................................................. 7-16
Configuring DS0 SNCP Protection ..................................................................................... 7-16
Viewing the DS0 SNCP Protection Status.......................................................................... 7-17
Example 1. DS0 SNCP protects timeslots of serial and voice ports over CL E1-i link.......... 7-18
Configuration Errors ......................................................................................................... 7-20
Megaplex-4
Installation and Operation Manual
7.4
7.5
7.6
7.7
7.8
Table of Contents
Ethernet Group Protection ................................................................................................. 7-20
Applicable Modules .......................................................................................................... 7-20
Standards ........................................................................................................................ 7-20
Functional Description ..................................................................................................... 7-21
Configuring Ethernet Protection Group ............................................................................ 7-24
Adding and Removing an Ethernet Protection Group ................................................... 7-24
Binding Ports to an Ethernet Protection Group ........................................................... 7-25
Example ........................................................................................................................... 7-25
Viewing the Status of an Ethernet Protection Group ........................................................ 7-27
Configuration Errors ......................................................................................................... 7-28
Ethernet Ring Protection (ERP) ........................................................................................... 7-28
Applicable Modules .......................................................................................................... 7-28
Standards ........................................................................................................................ 7-29
Benefits ........................................................................................................................... 7-29
Factory Defaults .............................................................................................................. 7-29
Functional Description ..................................................................................................... 7-30
Ring Topology ............................................................................................................. 7-30
R-APS Messaging ......................................................................................................... 7-30
Mechanism of Operation ............................................................................................. 7-31
Administrative Commands ........................................................................................... 7-31
Multiple Rings.............................................................................................................. 7-32
Timers ......................................................................................................................... 7-33
ERP Configuration ............................................................................................................ 7-33
Configuring ERP ........................................................................................................... 7-33
Displaying ERP Status .................................................................................................. 7-37
Displaying ERP Statistics.............................................................................................. 7-38
Example ...................................................................................................................... 7-39
Configuration Errors ......................................................................................................... 7-42
HSR Protection ................................................................................................................... 7-43
Benefits ........................................................................................................................... 7-43
Standards ........................................................................................................................ 7-44
Functional Description ..................................................................................................... 7-44
Node Functionalities ................................................................................................... 7-44
Duplicate Discard ........................................................................................................ 7-45
Supervision Packet Analysis ......................................................................................... 7-45
Configuring the HSR ......................................................................................................... 7-45
Example ........................................................................................................................... 7-47
Configuration Errors ......................................................................................................... 7-49
Viewing the LRE Status .................................................................................................... 7-50
Displaying a Node Table .............................................................................................. 7-50
Displaying a Proxy Table .............................................................................................. 7-51
Displaying LRE Statistics................................................................................................... 7-51
I/O Group Protection .......................................................................................................... 7-52
Benefits ........................................................................................................................... 7-52
Standards ........................................................................................................................ 7-53
Factory Defaults .............................................................................................................. 7-53
Functional Description ..................................................................................................... 7-53
Protection Mode ......................................................................................................... 7-53
Configuring I/O Group Protection ..................................................................................... 7-53
Example ........................................................................................................................... 7-55
Configuration Errors ......................................................................................................... 7-55
LAG Protection ................................................................................................................... 7-55
Benefits ........................................................................................................................... 7-56
Configuring the LAG ......................................................................................................... 7-56
Megaplex-4
xv
Table of Contents
Installation and Operation Manual
Displaying LAG Status ...................................................................................................... 7-59
Displaying LACP Status ..................................................................................................... 7-59
Displaying LAG Statistics .................................................................................................. 7-60
Displaying LACP Statistics ................................................................................................ 7-61
Configuration Errors ......................................................................................................... 7-61
7.9 Path Protection for SDH/SONET Payload ............................................................................ 7-62
Factory Defaults .............................................................................................................. 7-62
Functional Description ..................................................................................................... 7-62
Configuring VC Path Protection ........................................................................................ 7-63
Adding and Removing a VC Path Protection Group ...................................................... 7-63
Binding Ports to a VC path Protection Group ............................................................... 7-63
Viewing the Status of a VC Path Protection Group ........................................................... 7-64
Example ........................................................................................................................... 7-64
Configuration Errors ......................................................................................................... 7-65
7.10 PW Protection .................................................................................................................... 7-65
Benefits ........................................................................................................................... 7-65
Standards ........................................................................................................................ 7-65
Factory Defaults .............................................................................................................. 7-66
Functional Description ..................................................................................................... 7-66
Working and Protection Port Parameters..................................................................... 7-66
Configuring PW Protection ............................................................................................... 7-66
Example ........................................................................................................................... 7-67
Viewing the PW Protection Status .................................................................................... 7-67
Configuration Errors ......................................................................................................... 7-68
7.11 TDM Group Protection ........................................................................................................ 7-68
Benefits ........................................................................................................................... 7-69
Standards ........................................................................................................................ 7-69
Factory Defaults .............................................................................................................. 7-69
Functional Description ..................................................................................................... 7-70
Working and Protection Port Parameters..................................................................... 7-70
Protection Mode ......................................................................................................... 7-71
Traffic Duplication ....................................................................................................... 7-71
Configuring TDM Group Protection ................................................................................... 7-72
Example 1 ........................................................................................................................ 7-75
Example 2 ........................................................................................................................ 7-75
Example 3 ........................................................................................................................ 7-76
Example 4 ........................................................................................................................ 7-77
Example 5. ....................................................................................................................... 7-77
Example 6 ........................................................................................................................ 7-79
Configuration Errors ......................................................................................................... 7-80
7.12 TDM Ring Protection .......................................................................................................... 7-81
Benefits ........................................................................................................................... 7-82
Standards ........................................................................................................................ 7-82
Factory Defaults .............................................................................................................. 7-82
Functional Description ..................................................................................................... 7-82
Configuring TDM Ring Protection ..................................................................................... 7-85
Example ........................................................................................................................... 7-86
7.13 Accelerated Ethernet Hardware Switchover Protection ....................................................... 7-86
Applicable Modules .......................................................................................................... 7-87
Benefits ........................................................................................................................... 7-87
Standards ........................................................................................................................ 7-87
Factory Defaults .............................................................................................................. 7-87
Configuring 50m HW protection between CL.2 modules .................................................. 7-87
xvi
Megaplex-4
Installation and Operation Manual
Table of Contents
Chapter 8. Traffic Processing
8.1
8.2
Bridge .................................................................................................................................. 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-1
Factory Defaults ................................................................................................................ 8-1
Functional Description ....................................................................................................... 8-1
Bridge Model ................................................................................................................. 8-2
Deleting Bridge Elements .............................................................................................. 8-2
Using the Bridge for Management ................................................................................. 8-2
Admission to Bridge ...................................................................................................... 8-3
Packet Editing on Reverse Flows ................................................................................... 8-3
Spanning Tree Protocol ................................................................................................. 8-5
Configuring the Bridge ....................................................................................................... 8-6
Configuring for Traffic ................................................................................................... 8-6
Configuring for Management ......................................................................................... 8-6
Configuring the Bridge .................................................................................................. 8-7
Examples ......................................................................................................................... 8-10
Layer-2 Management Access ....................................................................................... 8-10
Layer-2 VLAN-aware Bridging between CL and M-ETH Ports ........................................ 8-12
Cascading Bridges on Different M-ETH Modules via CL Bridge ...................................... 8-15
RSTP Basic Application ................................................................................................ 8-18
Configuration Errors ......................................................................................................... 8-23
Displaying MAC Address Table .......................................................................................... 8-24
Cross-Connections ............................................................................................................. 8-26
Factory Defaults .............................................................................................................. 8-29
Benefits ........................................................................................................................... 8-29
Functional Description ..................................................................................................... 8-29
Timeslot Types ............................................................................................................ 8-29
Full Timeslot versus Split Timeslot Assignment (Split Timeslot Cross-Connect) ............ 8-30
Bidirectional Transfer Mode ........................................................................................ 8-30
Unidirectional Broadcast Function ............................................................................... 8-31
Bidirectional Broadcast Applications ............................................................................ 8-32
V.24 Conference Applications ...................................................................................... 8-35
Configuring a DS0 Cross-Connection ................................................................................ 8-36
Example 1. Bidirectional DS0 Cross-Connect: CL <-> I/O Modules, Single Timeslot ....... 8-39
Example 2. Consecutive Timeslot Assignment: E1/T1/E1-i/T1-i Port <-> Serial Module Port
................................................................................................................................... 8-40
Example 3. Consecutive Timeslot Assignment: Two E1/T1/E1-i/T1-i I/0 Module Ports .. 8-40
Example 4. Unidirectional Broadcast: M8E1 Port is Sending Data to three M8E1
ports using UniRx ........................................................................................................ 8-40
Example 5. Unidirectional Broadcast – Voice ............................................................... 8-40
Example 6. Unidirectional Broadcast – Serial ............................................................. 8-41
Examples 7a and 7b. Bidirectional Voice-Grade Data Broadcast 1:n ............................ 8-41
Example 8. Bidirectional Broadcast: Serial Port is Sending Data to Remote RTUs over
Various E1 Ports .......................................................................................................... 8-43
Example 9. Bidirectional Broadcast with Monitoring over E1 ........................................ 8-43
Configuring a TDM Cross-Connection ............................................................................... 8-44
Example 1. Cross-connecting the Full E1 Payload ........................................................ 8-45
Example 2. Indirect Mapping........................................................................................ 8-45
Configuring a Split Timeslot Cross-Connection ................................................................. 8-46
Example ...................................................................................................................... 8-47
Configuring an SDH/SONET Cross-Connection .................................................................. 8-48
Example 1. Direct Transparent Mapping of E1 Links over SDH ..................................... 8-49
Example 2. Mapping Framed E1 Link Payload to VC-12 Container ................................ 8-50
Megaplex-4
xvii
Table of Contents
8.3
8.4
8.5
8.6
xviii
Installation and Operation Manual
Configuring a PW-TDM Cross-Connection ......................................................................... 8-50
Example 1. PW-TDM Cross-connection between PW 1 and Serial HS-12N Port ............ 8-51
Example 2. PW-TDM Cross-connection between PW 1 and Serial Port located on the same
VS Module ................................................................................................................... 8-52
Configuration Errors ......................................................................................................... 8-52
Viewing the Cross-Connect Summary ............................................................................... 8-55
Example 1. Viewing all DS0 Connections in the System ............................................... 8-56
Example 2. Viewing all DS0 Connections in the System for T1-i Ports .......................... 8-56
Example 3. Viewing all TDM Connections in the System ............................................... 8-56
Example 4. Viewing all SDH/SONET Connections in the System for VC11 ..................... 8-56
Example 5. Viewing all PW Connections in the System ................................................. 8-57
Flows ................................................................................................................................. 8-57
Standards ........................................................................................................................ 8-57
Benefits ........................................................................................................................... 8-58
Factory Defaults .............................................................................................................. 8-58
Functional Description ..................................................................................................... 8-58
Ethernet Entities ......................................................................................................... 8-58
Aware and Unaware Traffic ......................................................................................... 8-59
Tagging and Marking ................................................................................................... 8-60
Defining Classifier Profiles ........................................................................................... 8-61
Configuring Flows ............................................................................................................ 8-62
Example ........................................................................................................................... 8-67
Configuration Errors ......................................................................................................... 8-68
Viewing the Flow Summary .............................................................................................. 8-71
Testing the Flows............................................................................................................. 8-73
Displaying Flow Statistics ................................................................................................. 8-75
Peer ................................................................................................................................... 8-76
Factory Defaults .............................................................................................................. 8-76
Benefits ........................................................................................................................... 8-76
Functional Description ..................................................................................................... 8-76
Adding and Configuring Remote Peers ............................................................................. 8-77
Viewing the Remote Peer Summary ................................................................................. 8-78
Examples ......................................................................................................................... 8-78
Configuration Errors ......................................................................................................... 8-79
Pseudowires ....................................................................................................................... 8-79
Standards ........................................................................................................................ 8-79
Benefits ........................................................................................................................... 8-80
Functional Description ..................................................................................................... 8-80
Pseudowire Packet Processing Subsystem ................................................................... 8-81
PSN Configuration Parameters .................................................................................... 8-87
Pseudowire QoS/CoS ................................................................................................... 8-87
ToS ............................................................................................................................. 8-88
Jitter Buffer ................................................................................................................. 8-88
Adaptive Timing .......................................................................................................... 8-89
OAM Protocol .............................................................................................................. 8-90
Factory Defaults .............................................................................................................. 8-91
Configuring Pseudowires .................................................................................................. 8-92
Examples ......................................................................................................................... 8-98
Displaying PW Statistics ................................................................................................. 8-100
Viewing the Pseudowire Status and Summary ................................................................ 8-106
Configuration Errors ....................................................................................................... 8-108
Quality of Service (QoS) ................................................................................................... 8-113
Factory Defaults ............................................................................................................ 8-113
Bandwidth Profiles ......................................................................................................... 8-113
Megaplex-4
Installation and Operation Manual
8.7
8.8
Table of Contents
Factory Defaults ........................................................................................................ 8-113
Configuring Shaper Profiles ....................................................................................... 8-114
Configuring Policer Profiles........................................................................................ 8-115
Queue Mapping Profiles ................................................................................................. 8-118
Factory Defaults ........................................................................................................ 8-118
Adding Queue Mapping Profiles................................................................................. 8-119
Configuring Queue Mappings .................................................................................... 8-120
Examples ................................................................................................................... 8-120
Marking Profiles ............................................................................................................. 8-121
Factory Defaults ........................................................................................................ 8-121
Configuring Marking Profiles ...................................................................................... 8-122
Queue Block Profiles ...................................................................................................... 8-122
Factory Defaults ........................................................................................................ 8-123
Adding Queue Block Profiles...................................................................................... 8-123
Configuring Queue Block Profile ................................................................................ 8-123
Example .................................................................................................................... 8-124
Queue Group Profiles ..................................................................................................... 8-125
Factory Defaults ........................................................................................................ 8-125
Adding Queue Group Profiles .................................................................................... 8-126
Configuring Queue Group Parameters ....................................................................... 8-126
Example .................................................................................................................... 8-127
WRED Profiles ................................................................................................................ 8-128
Factory Defaults ........................................................................................................ 8-128
Configuring WRED Profiles ......................................................................................... 8-129
Example .................................................................................................................... 8-129
Router (Management) ...................................................................................................... 8-129
Benefits ......................................................................................................................... 8-130
Factory Defaults ............................................................................................................ 8-130
Configuring Inband Management ................................................................................... 8-130
Loopback Router Interface ............................................................................................. 8-130
Configuring the Management Router ............................................................................. 8-130
Displaying the Routing Table .......................................................................................... 8-133
Configuration Errors ....................................................................................................... 8-134
Example ......................................................................................................................... 8-134
Router (Pseudowire) ........................................................................................................ 8-137
Functional Description ................................................................................................... 8-138
Adding and Configuring Router Interfaces ...................................................................... 8-139
Adding a Router Interface ......................................................................................... 8-139
Configuring the Router Interface ............................................................................... 8-140
Displaying the Routing Table .......................................................................................... 8-141
Configuring Static Routes and Default Gateway ............................................................. 8-142
Example 1. Establishing PW Connectivity between HS-12N Module and MPW-1 Fast Ethernet
Port ............................................................................................................................... 8-143
Example 2. Establishing PW Connectivity between HS-12N Module and VCG .................. 8-144
Chapter 9. Timing and Synchronization
9.1
Clock Selection ..................................................................................................................... 9-1
Standards .......................................................................................................................... 9-1
Functional Description ....................................................................................................... 9-1
Clock Synchronization ................................................................................................... 9-1
System Timing Modes ................................................................................................... 9-3
Clock Domain ................................................................................................................ 9-6
Factory Defaults ................................................................................................................ 9-6
Megaplex-4
xix
Table of Contents
9.2
9.3
Installation and Operation Manual
Configuring the Clock Domain ............................................................................................ 9-7
Displaying the Clock Domain Status ................................................................................... 9-8
Configuring the Clock Sources ............................................................................................ 9-9
Displaying the Clock Source Status .................................................................................. 9-11
Displaying Clock Source Statistics .................................................................................... 9-12
Configuring the Station Clock ........................................................................................... 9-12
Displaying the Station Clock Status .................................................................................. 9-14
Configuring the Recovered Clock ...................................................................................... 9-14
Displaying the Recovered Clock Status ............................................................................. 9-14
Configuration Errors ......................................................................................................... 9-15
Date and Time (Manual) ..................................................................................................... 9-16
Setting the Date and Time ............................................................................................... 9-16
Example ........................................................................................................................... 9-17
Displaying the Date and Time .......................................................................................... 9-17
Date and Time (from NTP Server) ....................................................................................... 9-17
Factory Defaults .......................................................................................................... 9-18
Configuring SNTP Parameters ...................................................................................... 9-18
Defining SNTP Servers ................................................................................................. 9-18
Configuring SNTP Server Parameters ........................................................................... 9-18
Example ...................................................................................................................... 9-19
Chapter 10. Administration
10.1 Administrative Information ................................................................................................. 10-1
10.2 MAC Address Allocation ...................................................................................................... 10-2
10.3 Managing the SONET/SDH Link Rate Selection License ....................................................... 10-3
Checking the License Availability ...................................................................................... 10-3
Ordering the License ........................................................................................................ 10-4
Downloading the License File Using TFTP ......................................................................... 10-5
Downloading the License File Using XModem .............................................................. 10-5
Installing the License for Redundant CL Modules ......................................................... 10-6
10.4 Inventory............................................................................................................................ 10-6
Standards and MIBs ......................................................................................................... 10-6
Benefits ........................................................................................................................... 10-6
Displaying Inventory Information ..................................................................................... 10-6
Displaying Inventory Component Information .................................................................. 10-7
Setting Administrative Inventory Information ................................................................... 10-7
Example ...................................................................................................................... 10-8
10.5 File Operations ................................................................................................................... 10-9
File Names in the Unit...................................................................................................... 10-9
Copying Files within Megaplex-4 .................................................................................... 10-10
Displaying Files within Megaplex-4 ................................................................................. 10-12
Deleting Files ................................................................................................................. 10-13
Saving the Configuration ................................................................................................ 10-13
Downloading/Uploading Files ......................................................................................... 10-13
Example – Download via SFTP ................................................................................... 10-14
Example – Upload via SFTP ........................................................................................ 10-14
10.6 Resetting Megaplex-4....................................................................................................... 10-15
Resetting to Factory Defaults ........................................................................................ 10-15
Resetting to User Defaults ............................................................................................. 10-15
Rebooting the Megaplex-4 Chassis ................................................................................ 10-16
Rebooting the Module ................................................................................................... 10-16
Chapter 11. Monitoring and Diagnostics
xx
Megaplex-4
Installation and Operation Manual
Table of Contents
11.1 Alarms, Events and Traps ................................................................................................... 11-2
Masking ........................................................................................................................... 11-3
Alarm Buffer .................................................................................................................... 11-3
Alarm Relays .................................................................................................................... 11-4
Configuring Alarm Reporting ............................................................................................ 11-4
Factory Defaults .......................................................................................................... 11-4
Examples ..................................................................................................................... 11-7
Working with the Alarm and Event Logs ........................................................................... 11-8
Example 1: Displaying Active Alarms ............................................................................ 11-9
Example 2. Displaying Active Alarms Details ................................................................ 11-9
Example 3. Displaying Information of LOF alarm on SDH/SONET port .......................... 11-9
Example 4. Alarm Log ................................................................................................ 11-10
Example 5. Alarm List ................................................................................................ 11-10
Alarm and Event Lists..................................................................................................... 11-11
Configuration Error Messages ........................................................................................ 11-11
11.2 Configuration Error Messages........................................................................................... 11-12
11.3 Diagnostic Loopbacks ....................................................................................................... 11-12
11.4 Ethernet BERT (RFC-2544 Testing) ................................................................................... 11-17
Standards ...................................................................................................................... 11-17
Benefits ......................................................................................................................... 11-17
Functional Description ................................................................................................... 11-18
Factory Defaults ............................................................................................................ 11-18
Performing the Test ....................................................................................................... 11-18
Configuration Error Messages ........................................................................................ 11-20
Example ......................................................................................................................... 11-21
11.5 Ethernet OAM (CFM) ........................................................................................................ 11-22
Standards ...................................................................................................................... 11-22
Benefits ......................................................................................................................... 11-22
Factory Defaults ............................................................................................................ 11-22
Functional Description ................................................................................................... 11-24
OAM Elements........................................................................................................... 11-24
OAM Functions .......................................................................................................... 11-25
MEPs and Services ..................................................................................................... 11-25
Messaging System ..................................................................................................... 11-27
Performance Monitoring............................................................................................ 11-29
Configuring OAM ............................................................................................................ 11-30
Configuring OAM CFM General Parameters ................................................................ 11-30
Configuring Maintenance Domains ............................................................................ 11-34
Configuring Maintenance Associations ...................................................................... 11-35
Configuring Maintenance Endpoints .......................................................................... 11-36
Configuring Maintenance Intermediate Points ........................................................... 11-38
Examples ................................................................................................................... 11-38
Configuring Maintenance Endpoint Services .............................................................. 11-40
Configuring Destination NEs ...................................................................................... 11-41
Configuring OAM CFM Service Event Reporting .......................................................... 11-43
Displaying OAM CFM Statistics ....................................................................................... 11-46
Performing OAM Loopback ............................................................................................. 11-51
Performing OAM Link Trace ............................................................................................ 11-51
11.6 Ethernet OAM (EFM)......................................................................................................... 11-52
Standards ...................................................................................................................... 11-52
Benefits ......................................................................................................................... 11-53
Functional Description ................................................................................................... 11-53
Factory Defaults ............................................................................................................ 11-53
Configuring OAM EFM .................................................................................................... 11-53
Megaplex-4
xxi
Table of Contents
Installation and Operation Manual
Example ......................................................................................................................... 11-54
11.7 In-Service Ping.................................................................................................................. 11-55
Benefits ......................................................................................................................... 11-55
Functional Description ................................................................................................... 11-55
Factory Defaults ............................................................................................................ 11-56
Performing the Ping ....................................................................................................... 11-56
Examples ....................................................................................................................... 11-60
Terminating the Ping ...................................................................................................... 11-60
11.8 LEDs ................................................................................................................................. 11-61
11.9 Performance Management ............................................................................................... 11-61
Standards ...................................................................................................................... 11-61
Benefits ......................................................................................................................... 11-61
Functional Description ................................................................................................... 11-61
Factory Defaults ............................................................................................................ 11-62
Configuring Performance Management .......................................................................... 11-62
Viewing Performance Management Configuration .......................................................... 11-64
Examples ....................................................................................................................... 11-64
11.10
Ping Test ................................................................................................................... 11-66
11.11
Statistic Counters ...................................................................................................... 11-66
11.12
Syslog ....................................................................................................................... 11-67
Standards and MIBs ....................................................................................................... 11-67
Benefits ......................................................................................................................... 11-67
Factory Defaults ............................................................................................................ 11-67
Functional Description ................................................................................................... 11-68
Elements ................................................................................................................... 11-68
Transport Protocol .................................................................................................... 11-68
Message Format........................................................................................................ 11-68
Facilities and Severities ............................................................................................. 11-69
Syslog Configuration ...................................................................................................... 11-69
11.13
Troubleshooting ........................................................................................................ 11-71
Preliminary Checks ......................................................................................................... 11-71
Troubleshooting Procedure ............................................................................................ 11-72
11.14
Technical Support...................................................................................................... 11-73
Chapter 12. Software Upgrade
12.1 Compatibility Requirements................................................................................................ 12-1
12.2 Impact ................................................................................................................................ 12-2
12.3 Prerequisites ...................................................................................................................... 12-2
Software Files .................................................................................................................. 12-2
System Requirements ...................................................................................................... 12-2
12.4 Upgrading Software using the CLI (TFTP) ............................................................................ 12-3
Verifying the IP Settings ................................................................................................... 12-4
Pinging the PC .................................................................................................................. 12-4
Activating the TFTP Server ............................................................................................... 12-4
Downloading the New Software Release File to Megaplex-4 Flash Disk............................ 12-4
Installing the New Software Release File from the Flash Disk........................................... 12-6
12.5 Upgrading Software using the CLI (SFTP) ............................................................................ 12-8
Pinging the PC .................................................................................................................. 12-8
Activating the SFTP Server ............................................................................................... 12-8
Downloading the New Software Release File to Megaplex-4 Flash Disk............................ 12-9
Installing the New Software Release File from the Flash Disk......................................... 12-11
12.6 Upgrading Megaplex-4 Software via the Boot Menu ......................................................... 12-12
Starting Boot Manager ................................................................................................... 12-13
xxii
Megaplex-4
Installation and Operation Manual
Table of Contents
Using the TFTP/FTP Protocol .......................................................................................... 12-15
Using the XMODEM Protocol .......................................................................................... 12-17
12.7 Verifying the Upgrade Results .......................................................................................... 12-19
12.8 Restoring the Previous Software Version.......................................................................... 12-20
Appendix A. Connection Data
Appendix B. I/O Modules
Appendix C. Test Plan
Megaplex-4
xxiii
Table of Contents
xxiv
Installation and Operation Manual
Megaplex-4
Chapter 1
Introduction
1.1
Overview
RAD’s Megaplex-4 multiservice next generation access nodes are high-capacity,
carrier-class multiservice concentrators, which transport traffic over fiber or
copper and provide multiple Legacy and next-generation services on
PDH/SDH/SONET or packet-switched networks (PSN). The Megaplex-4 family
includes two devices: a powerful 10-slot Megaplex-4100 and a compact 4-slot
Megaplex-4104.
Megaplex-4 is an ideal solution for carriers and private network operators in
migrating their networks and services to next-generation communications.
Featuring dual star connection architecture with hybrid TDM-Ethernet modules
allows native TDM and native Ethernet traffic handling with minimal encapsulation
delays and zero bandwidth overhead. In networks with SDH/SONET backbone,
Ethernet can be carried over VCG. In addition, it is equipped with a full standardsbased pseudowire emulation suite, ensuring TDM service quality is maintained
when migrating the services from TDM network to packet switched network.
Carrier class service reliability is ensured with system redundancy options, link
and path protection schemes and enhanced support for diverse ring topologies.
Handling a broad range of SDH/SONET, E1/T1, Ethernet, data and voice services,
various network topologies and versatile access media in a single compact
managed node, makes Megaplex-4 a versatile and cost-effective next-generation
multiservice access node solution for large enterprises, including utilities,
transportation and campuses, as well as for carriers and service providers.
Product Options
Chassis
Megaplex-4 systems are available in two chassis sizes:
Megaplex-4
•
Megaplex-4100 – 4U-high chassis can accommodate up to 10 I/O modules.
•
Megaplex-4104 – compact 2U-high chassis can accommodate up to 4 I/O
modules. It is a cost-effective alternative for power utility substations, service
providers, and small POP or branch office applications or for sites with limited
space.
Overview
1-1
Chapter 1 Introduction
Installation and Operation Manual
IEEE-1613 Compliance
Special Megaplex-4100 and Megaplex-4104 chassis ordering options are available
complying with IEEE-1613 environmental requirements (for
teleprotection/communications devices in the power utilities substations as well
as other markets, see Chapter 2 for details).
CL Modules
The CL.2 modules are provided in several flavors, to cater for specific needs of
each customer. Table 1-1 lists the functionalities supported by each CL.2 option.
A short description of CL.2/A, CL.2/DS0 and /AP options is given in this section
below.
Note
Starting from Megaplex release 4.81, CL.2 Non-A versions are moved to mature
operation and the CL types provided by RAD will be available are CL.2/A(P) and
CL.2/DS0. Customers who purchased the “non-A” CL version will be able to order
it with Megaplex SW versions 4.71 and lower. RAD will continue to support all
systems and CL types according to RAD’s standard support policies.
Table 1-1. Features Supported by CL.2 Options
CL.2/622GBEA
CL.2/622GBEAP
CL.2/GBEA CL.2/622GBE CL.2/DS0
CL.2/GBEAP
SDH/SONET
+
-
+
-
DS0 Cross-Connect
+
+
+
+
E-line
+
+
+
Inside
modules
only
E-LAN
+
+
M-ETH only
M-ETH only
E-Tree
+
+
-
-
Management VLAN via VCG
+
-
-
-
Flow between modules (CL and I/O)
+
+
+
-
+
+
-
-
Maximum number of VS-6/E1, VS-6/T1, M16E1T1
or T3 modules per chassis (see the
corresponding module manual)
10
9
10
9
Maximum number of SH-16 or other VS modules
per chassis (see the corresponding module
manual)
9
9
9
9
Traffic Management
(Scheduling/Shaping)
1-2
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
CL.2/622GBEA
CL.2/622GBEAP
CL.2/GBEA
CL.2/GBEAP
CL.2/622GBE CL.2/DS0
ERPS
+
+
-
-
LAG + LACP
+
+
-
-
LAG
+
+
+
-
HSR
+
+
-
-
RSTP
+
+
-
-
Ethernet group protection
-
-
+
-
802.1x
+
+
-
-
MACsec
CL.2/622GBEAP only
CL.2/GBEAP only
CIR, CBS, EIR and EBS per flow
+
+
-
-
CIR, CBS per port
+
+
-
-
Classification per P-Bit/DSCP
+
+
-
-
Classification per single or double VLAN
+
+
+
-
Ethernet OAM
+
+
-
-
VLAN editing
Inner + Outer
Inner + Outer
Outer
Outer
Ethernet PM
+
+
-
-
Internal Clock Quality
ST-3E
ST-3E
ST-3E
ST-4
Clock Quality Status (SSM)
+
+
-
-
SyncE
+
+
-
Ethernet BERT
+
+
+
-
TDM BERT
+
+
+
+
In-Service Ping
+
+
-
-
Ethernet Protection
Security
Service Assured Access
Timing
Diagnostics
Carrier Ethernet (CL.2/A Assembly)
The CL.2/A assembly provides carrier Ethernet capabilities, such as Ethernet
traffic management (TM), standards-based Ethernet Operations, Administration
and Maintenance and Performance Monitoring (OAM&P), as well as carrier grade
Ethernet functionality.
These functionalities are available on any MAC entity, such as the CL module GbE
ports, VCG, Ethernet module (M-ETH)_ports, etc.
Megaplex-4
Overview
1-3
Chapter 1 Introduction
Installation and Operation Manual
This assembly can be ordered with or without SDH/SONET interface.
MACsec (CL.2/AP Assembly)
The CL.2/A modules can be ordered in a special CL.2/AP version, hardware-ready
for the activation of 2 GbE MACsec engines based on MACsec per IEEE 802.1AE2006 and 802.1AEbn-2011 (128/256-bit) standards. The engines are activated
by a separately ordered license.
SDH/SONET Interface
Two SDH/SONET ports located on the CL.2 modules can be ordered in two
versions:
•
STM-1/OC-3 only, with software key license upgrade to STM-4/OC-12 if
required
•
Software-configurable to STM-4/OC-12 or STM-1/OC-3, with software key
license built-in.
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical.
GbE Interface
The GbE ports can be ordered with one of the following interfaces:
•
10/100/1000BASE-T (UTP) copper ports. This type of ports support autonegotiation, with user-specified advertised data rate (10, 100 or 1000 Mbps)
and operating mode (half- or full-duplex).
•
SFP sockets, for installing SFP plug-in modules.
DS0 Cross-Connect
A basic low-cost version of CL.2 modules is supplied without SDH/SONET and GbE
ports.
CL Module for “No Fans” Operation
There are special CL.2 options complying with IEEE-1613 to support “No Fans
operation” requirement. For Megaplex-4100, these CL options have to be ordered
together with a special IEEE-1613-compliant chassis.
PS Modules
PS modules for Megaplex-4100 and Megaplex-4104 have different shape and
technical characteristics (see Table 1-8). AC or DC power supplies are available for
both chassis. The DC modules can be ordered with selectable ground reference or
floating ground.
Megaplex-4 can be ordered with one power supply module, or with two power
supply modules, for redundancy.
The Megaplex-4100 chassis also has a selection of PS options complying with
IEEE-1613 to support “No Fans operation” requirement. These options have to be
ordered together with a special IEEE-1613-compliant chassis.
1-4
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Megaplex-4104 has one special IEEE-1613-compliant option.
Applications
Central Solution for RAD CPE Devices
Megaplex-4 offers a complete, end-to-end solution as a central aggregation
platform for diverse CPE devices managed together under RADview. Megaplex-4 is
interoperable with DXC, MP-2100/2104, FCD, ASMi, Optimux, as well as ETX, RICi
and IPMUX family devices.
Figure 1-1 illustrates Megaplex-4 as a central site solution, Ethernet and TDM
aggregator for SDH/SONET and PSN networks.
Wireless
FE
Airmux
Video
Airmux
E3 Chanellized
FE
FCD-IP
Router
STM-1
DXC-8R
FE/GbE
PSN
DXC-4
RICi-8
POP
FE
E1
IPmux
SHDSL
SHDSL.bis
ASMi
SDH/SONET
FCD-E1E
E1
ETH
n x E1
STM-4/
OC-12
FO
Megaplex-4
ETH
E1/V.35
ETH
n x E1
Optimux
STM-1/
OC-3
SHDSL
SHDSL.bis
T3
ETH
ASMi-53
FE
ETH
ETX
RV Station
E1/V.35
STM-1/OC-3
ETH
E1/T1
FCD-155E
Voice
Data
ETH
E1/T1
MP-2100/2104
T3
Radio
Megaplex-4104
Radio
Figure 1-1. Megaplex-4 as a Central Site Aggregator for different RAD CPEs,
Ethernet and TDM Aggregator for SDH/SONET and PSN
TDM and Ethernet Multiservice Access
Enterprises, campuses and utility companies can deploy Megaplex-4 as a core or
an edge device to create a diversity of STM-1/STM-4/OC-3/OC-12 or Ethernet
rings, multiplexing voice, fax, data, and other low speed traffic. Megaplex-4 can
also groom and cross-connect between channels and terminate Ethernet traffic.
Megaplex-4 can work with industry-specific devices, such as Teleprotection and
Omnibus units (see Figure 1-2).
Megaplex-4
Overview
1-5
Chapter 1 Introduction
Installation and Operation Manual
Control Center
GbE
PSN
Megaplex-4100
SDH/SONET/ETH
FO
Megaplex-4104
Megaplex-4104
E1/T1
Airmux-400
Megaplex-4100
SHDSL.bis
FXS
E&M
PA
FXS
E&M
PA
FO
E1/T1
Airmux-400
TAC
PBX
Megaplex-2100
PBX
ASMi
SCADA
LAN
Optimux
LAN
TAC
LAN
LAN
Figure 1-2. Megaplex-4 as Multiservice Platform for Transportation and Power Utilities
Smooth Migration from TDM to PSN
Megaplex-4 equipped with the MPW-1 module provides legacy services over
packet-switched networks (PSN). The MPW-1 module converts the data stream
from other modules in the Megaplex-4 chassis (E1/T1, SHDSL, data or voice
ports) delivered by the internal Megaplex backplane via MPW-1’s internal DS1
ports into IP or MPLS packets for transmission over Ethernet, IP or MPLS
networks. The ASIC-based architecture provides a robust and high performance
pseudowire solution with minimal processing delay. MPW-1 supports various
legacy services over packet transport types, including TDMoIP, CESoPSN, SAToP,
HDLCoPSN (see Figure 1-3).
1-6
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
E1
Remote Sites
SHDSL.bis
E1
POP
FO
PBX
PBX
ASMi-54
FE
Megaplex-4100
LAN
FE
Optimux-108
GbE
ERP
E1
Video
FO
E1
SHDSL.bis
PBX
FE
PBX
Optimux-108
FE
Central Office
VoIP
ASMi-54
Megaplex-4100
E1
Video
PBX
E1
FO
SHDSL.bis
ASMi-54
FE
PBX
FE
LAN
NMS
Optimux-108
POP
E1
LAN
STM-1/
OC-3
FXS
FO
SDH/SONET
PBX
Optimux-108
Megaplex-4104
FE
E1
Video
X.21
FCD-E1L
FXS
E1/T1
Megaplex-2104
V.35
Figure 1-3. Migrating TDM and Ethernet Services from SDH/SONET to PSN
Carrier Ethernet Services
Megaplex-4 delivers Ethernet services as defined by the MEF standards. MEF
identifies three types of standardized Carrier Ethernet services, each of
which corresponds with a set of UNI attributes and EVC attributes:
•
Megaplex-4
E-Line: A point-to-point connection, where each EVC links two UNIs. E-Line
services can be of either of two variants:
Ethernet Private Line (EPL): An E-Line-type service (see Figure 1-4) in
which only one point-to-point EVC is supported by the same physical
interface at both UNIs, i.e. no service multiplexing is allowed. EPL may
be delivered as a guaranteed bandwidth service, whereby the carrier
provides SLA-based rate and performance commitments and allocates
network resources accordingly, similar to a leased line service.
Ethernet Virtual Private Line (EVPL): An E-Line service (see Figure 1-5)
allowing service multiplexing so that a single UNI supports multiple
EVCs. As data frames may be mapped to different EVCs, an EVPL
service is not required to provide full frame transparency, unlike an EPL
service. User traffic is distinguished by different VLAN IDs and
Overview
1-7
Chapter 1 Introduction
Installation and Operation Manual
transported over common network resources, thereby necessitating
traffic policing/shaping functionalities at the provider network ingress.
•
•
E-LAN (Ethernet Local Area Network): A multipoint-to-multipoint topology,
where each EVC links more than two UNIs. The following are designated as ELAN services:
Ethernet Private LAN (EPLAN): A multipoint service (see Figure 1-6),
requiring a dedicated UNI per EVC, in which service multiplexing is
prohibited. Other service attributes are similar to those of a point-topoint EPL service.
Ethernet Virtual Private LAN (EVPLAN): An E-LAN-type service (see
Figure 1-7) allowing EVC multiplexing at the UNI, similar in attributes to
an EVPL. A flow based EVPLAN service enables service multiplexing for
applications such as departmental LAN differentiation – by service,
location or user function – at the UNI level.
E-Tree: A service using a multipoint rooted EVC, whereby one or more of the
UNIs are classified as “Roots”, while all other UNIs are designated as
“Leaves”. Traffic delivery is permitted between a Root and a Leaf, in both
directions, but prohibited between Leaves. Specific Root/Leaf subsets and
the corresponding traffic delivery rules depend on particular service
definitions.
Figure 1-4. EPL (Ethernet Private Line) Service
1-8
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Figure 1-5. EVPL (Ethernet Virtual Private Line) Service
Figure 1-6. EP-LAN (Ethernet Private LAN) Service
Figure 1-7. EVP-LAN (Ethernet Virtual Private LAN) Service
Megaplex-4
Overview
1-9
Chapter 1 Introduction
Installation and Operation Manual
Features
PDH Access
Megaplex-4 delivers PDH Access at E1/T1 and fractional E1/T1 level with up to
160 E1/T1 ports per chassis over copper or fiber, including access over
2-wire/4-wire/8-wire SHDSL, with up to 80 SHDSL ports per chassis.
Data Services
Megaplex-4 provides up to 120 multichannel sub-DS0 low speed data, 64-kbps
codirectional G.703 channels, teleprotection channels, multichannel ISDN access
(up to 120 ISDN “U” and/or “S” type ports per chassis), and n×64 kbps high
speed data (up to 2.048 Mbps for E1 environments, or up to 1.544 Mbps for T1
environments).
Voice Services
Voice services are provided by analog and digital voice modules (up to 4800 voice
channels per chassis for E1 ports, up to 3840 voice channels for T1 ports), with
support for special services such as omnibus and party lines. Voice channel
processing can include user-defined signaling translations.
SDH/SONET Services
SDH/SONET services are provided by up to 4 separately configurable STM-1/STM4 or OC-3/OC-12 links per node, with support for APS (Automatic Protection
Switching) for line redundancy.
Ethernet Layer 2 Services
Ethernet Layer 2 services are supported by various I/O modules with Ethernet
ports, and 4 GbE ports on CL modules. Up to eight separately configurable
Ethernet ports are available per I/O module; each CL module has two GbE ports,
for up to four separately configurable GbE ports per chassis. Megaplex-4 can
provide Ethernet traffic termination for transport over E1, T1, SHDSL uplinks,
virtually concatenated group uplinks and high and low-order SDH/SONET
VC-12/VC1.5 virtual containers. It can also serve as Ethernet access concentrator
with GbE uplinks.
Incoming Ethernet traffic is classified and mapped according to port-based
(all-in-one) bundling or by user port and CE VLAN-ID, VLAN priority, DSCP, IP
precedence, and Ethertype. This offers operators the flexibility to differentiate
services using traffic management TM tools, such as traffic policing, queuing and
shaping, and enforce SLA per service.
Megaplex-4 supports powerful bandwidth profiles such as CIR/CBS and EIR/EBS for
differentiated Ethernet services and includes comprehensive Ethernet OAM
(Operation, Administration, and Maintenance) and Ethernet Performance
Monitoring functionality together with SLA monitoring.
Forwarding Schemes
Traffic forwarding is performed using point-to-point (E-Line) or bridge (E-LAN,
E-TREE) mechanisms.
1-10
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Service Types
Megaplex-4 provides port- and flow-based services.
Port-Based Service
In a typical port-based (all-to-one bundling) application Megaplex-4 receives
different services via different user ports (Figure 1-8). This method achieves
clearer service separation, it does not require any customer marking for CoS.
Customer Premises
Service Provider Node
GbE
Packet Switched
Network
(Ethernet, IP or MPLS)
PE
Megaplex-4
VoIP
GbE
Premium
Data
GbE
Best Effort
Data
Figure 1-8. Port-Based Service
Flow-Based Service
In a typical flow-based application different services are assigned to different
Ethernet flows received by the same user port (Figure 1-9). This provides a
cheaper, more scalable solution, with a possibility of mixing different service
types.
Service Provider Node
Customer Premises
GbE
Packet Switched
Network
(Ethernet, IP or MPLS)
PE
VoIP
Premium
Data
Best Effort
Data
Megaplex-4
Figure 1-9. Flow-Based Service
Flow Classification
The ingress user traffic is mapped to the Ethernet flows using the following list of
per-port classification criteria. In the classifications, VLAN refers to the service
provider (outer) VLAN, previously referred to as SP-VLAN, while inner VLAN refers
to the Customer Entity VLAN, previously referred to as CE-VLAN.
Megaplex-4
•
Port-based (All to one bundling)
•
VLAN
•
VLAN + VLAN priority
•
VLAN + IP precedence
•
VLAN + DSCP
•
VLAN + inner VLAN
•
VLAN + VLAN priority + inner VLAN
•
VLAN + Ethertype
Overview
1-11
Chapter 1 Introduction
Installation and Operation Manual
•
VLAN priority
•
IP precedence
•
DSCP
•
Ether Type
•
Untagged
Megaplex-4 supports up to 512 Ethernet flows. Flows between external Ethernet
ports and the CL.2/A bridge are bidirectional. All other flows are unidirectional.
Tagging and Marking
Megaplex-4 supports several options for marking and tagging.
You can perform the following marking and tagging actions:
•
Overwrite inner or outer VLAN with a new value
•
Overwrite inner or outer VLAN p-bit with a new value.
You can perform the following tagging actions:
•
Add (push) outer VLAN, with p-bit value that can be copied from the original
value or set to a new value. When you add a new VLAN, the original outer
VLAN becomes the inner VLAN.
•
Remove (pop) outer VLAN and p-bit. When you remove a VLAN, the inner
VLAN becomes the outer VLAN.
•
Add (push) inner VLAN, with p-bit value that can be copied from the original
value or set to a new value
•
Remove (pop) inner VLAN and p-bit.
Only certain combinations of actions on the outer and inner VLAN are allowed.
Refer to Chapter 8 for details on the permitted combinations of actions.
L2CP Handling
Megaplex-4 can be configured to pass through (“tunnel”) Layer-2 control frames
(including other vendors’ L2CP frames) across the network, to peer supported
protocols, or to discard L2CP frames.
1-12
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Fault Propagation
The user can configure fault propagation between any two ports in Megaplex-4,
as shown in the figure below.The fault propagation behavior is according to the
port type (refer to Chapter 7 for details).
Megaplex-4
Packet Switched
Network
(Ethernet, IP or MPLS)
CPE
Network Termination
Unit
Figure 1-10. Fault Propagation
Traffic Management and Service Level Agreement (SLA)
Monitoring, Troubleshooting and Measurement
Powerful tools assure Megaplex-4’s ability to analyze the current traffic load and
dynamically make necessary adjustments to accommodate the different types of
traffic or changing conditions. RAD also provides effective service-level
agreement (SLA) monitoring tools such as Ethernet service OAM (CFM), Ethernet
link OAM (EFM) etc.
Quality of Service (QoS)
Megaplex-4 efficiently handles multi-priority traffic on a per-flow basis, that
enables simultaneous processing of hundreds of service flows. The device
enables multi-criteria traffic classification as well as metering, policing and
shaping to help carriers rate-limit user traffic according to predefined CIR
(committed information rate) and EIR (excess information rate) profiles.
Enhanced quality of service is further supported by up to 2-level hierarchical
scheduling mechanism that combines Strict Priority (SP) and weighted fair queue
(WFQ) scheduling, to efficiently handle real-time, premium and best-effort traffic.
Scheduling and shaping are supported at the EVC, and port levels.
Megaplex-4 also uses weighted random early detection (WRED) policy for
intelligent queue management and congestion avoidance. Packet editing
capabilities include 802.1ad Q-in-Q tagging and color-sensitive P-bit re-marking,
which ensures metering continuity across color-aware and color-blind Metro
networks and WANs.
Different service types require different levels of QoS to be provided end-to-end.
QoS can be defined per subscriber as well as per flow. QoS has three aspects:
policing (rate limitation), traffic prioritization and traffic shaping.
Traffic Policing
A policer is per flow. The policers meter, mark and rate-limit the traffic according
to the dual token bucket mechanism (CIR+CBS, EIR+EBS). A special mechanism
Megaplex-4
Overview
1-13
Chapter 1 Introduction
Installation and Operation Manual
compensates for Layer 1 headers. Traffic can be limited to the line rate or the
data rate.
In addition, Megaplex-4 features unique p-bit re-marking capabilities that assign
color-specific p-bit values to Ethernet frames at network ingress to ensure
metering continuity across the Metro Ethernet network. User traffic that was
marked “yellow” according to the CIR/EIR parameters by the device QoS engine is
assigned a new p-bit value to signal its status and priority, so that it is dropped
first by 802.1Q and 802.1ad (a.k.a IEEE 802.1QinQ ) network elements in the
event of congestion. This is especially useful in color-blind as well as color-aware
networks with no “discard eligible” (“yellow”) marking.
Traffic Prioritization (Queuing)
Once traffic is classified to a flow, it can be mapped to Strict (Strict Priority)
queues or WFQ (Weighted Fair Queues):
•
Strict. The data flow set to the highest priority is transmitted first. If this data
flow stops, all tasks at lower priorities move up by one priority level. For
example, the data flow set to the second-highest priority is then transmitted
at the highest priority.
•
WFQ. Allows different scheduling priorities to statistically multiplex data flows
with different shares on the service. Each data flow has a separate FIFO
queue. A link transmitting at a data rate R, all non-empty data flows N are
served simultaneously according to the assigned share w, each at an average
rate of R/(w1 + w2 + w3 + … +wN). If one data flow stops, the remaining data
flows each receive a larger share w.
The WRED mechanism ensures that queues are not congested and high-priority
traffic is maintained. Each queue is assigned a WRED profile for which you can
configure the thresholds and probability to suit your needs.
Queue Group
Level 0
Level 1
1
2
Flow1
Queue
Block 0
3
4
1
UNI
Flow2
1
Queue
Block 1
2
2
3
3
4
Flow3
1
2
Figure 1-11. Queue Structure – Towards CL.2/A GbE Port
1-14
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Level 0 contains up to 8 queue blocks per CL.2/A GbE port. Each block has up to
eight queues and its own scheduling (Strict and WFQ). For each queue block in
level 0, there is a queue in level 1 that represents the scheduling between the
queue blocks in level 0. Flows can be bound to each queue block in level 0.
Queue Group
Level 0
Flow1
1
UNI
Flow2
2
3
Flow3
Figure 1-12. Queue Structure – Towards User Ethernet or VCG Ports
Level 0 contains a single queue block per Ethernet port. Each block has up to
eight queues and its own scheduling (Strict and WFQ). Flows can be bound to
each queue block in level 0.
Queue Mapping
For the network ports (CL.2/A GbE), Megaplex-4 supports up to 8 queue blocks
per queue group. Towards the user ports, a single queue block with up to eight
queues is supported. Flows that are in the direction user port to network port
can be bound to one of up to 8 queue blocks, and flows that are in the direction
network port to user port can be bound to one of eight queues.
The queue mapping functionality associates the user priorities with queue
numbers (CoS).
The queue mapping functionality is bound to each flow.
Hardware-Based SLA Monitoring and Troubleshooting (Ethernet
OAM) and Measurement (Performance Monitoring)
Featuring ultra-fast, hardware-based processing capabilities, Megaplex-4
performs OAM and PM measurements in under1 ms with maximum precision.
Megaplex-4 provides OAM to monitor and troubleshoot an Ethernet network and
quickly detect failures:
•
Megaplex-4
CFM OAM (End-to-end OAM) based on IEEE 802.1ag and Y.1731 for continuity
check, non-intrusive loopback and link-trace, and performance monitoring
Overview
1-15
Chapter 1 Introduction
•
Installation and Operation Manual
EFM OAM (Link OAM) according to IEEE 802.3-2005 (formerly IEEE 802.3ah)
for remote management and fault indication, including discovery, link
monitoring, remote fault detection (dying gasp) and remote loopback.
Megaplex-4 offers advanced Ethernet service assurance tools, including userdefined KPI (key performance indicators) threshold configuration for delay
(latency), delay variation (jitter), packet loss and availability. Other tools include
real-time SLA violation alerts and per-flow statistics reporting.
Flexible Ethernet Transport over TDM
Flexible Ethernet transport options over TDM links provide full support for
Ethernet services over existing TDM infrastructures with efficient bandwidth
utilization for each type of application, and also enable cost-effective migration
to packet switched transport. The available Ethernet transport options include:
•
HDLC bundles with selectable number of timeslots over individual external E1
and T1 links, and internal PDH ports of the SDH/SONET subsystem
•
Wideband, multilink MLPPP bundles over E1 links, with a bandwidth of up to
16.384 Mbps (the equivalent of eight E1 links)
•
Virtually concatenated groups over SDH/SONET links, with selectable
granularity down to VC-12/VT1.5/VC-3/VC-4/STS-1/STS-3C, Megaplex-4
performs low-order and high-order virtual concatenation, including GFP
encapsulation per ITU-T Rec. G.7041 or LAPS per ITU-T Rec. X.85/X.86. For
reliable transmission, Megaplex-4 also supports LCAS per ITU-T Rec. G.7042.
Flexible TDM Transport over Ethernet
Megaplex-4 supports TDM pseudowire (PW) circuit emulation for E1 and T1 over
IP and MPLS packet-switched networks. It complies with the pseudowire edge-to
edge emulation (PWE3) standards, including TDMoPSN, HDLCoPSN, CESoPSN and
SAToP, and therefore it is compatible with other pseudowire equipment offered
by RAD, such as Gmux-2000 Pseudowire Gateways, the IPmux family of TDM
Pseudowire Access Gateways, as well as with previous generations of Megaplex
equipment with IP main link modules.
Fiber Multiplexing
Megaplex-4 also features multiport fiber multiplexing modules, for transporting 4
or 16 E1 streams, together with Ethernet traffic of up to 100 Mbps, over
proprietary fiber optic links to compatible standalone units offered by RAD for
use at customers’ premises.
DS0 Cross-Connect
Megaplex-4 features an internal DS0 cross connect matrix of up to 8384/6080
channels. Traffic from any channel can be cross-connected directly to any other
channel.
These capabilities enable Megaplex-4 to function as a service differentiation point
at the headquarters, handing off traditional voice and data services to the
transport network.
1-16
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
At the remote offices or customer premises, Megaplex-4 may also be deployed to
effectively fan out multiple voice and data services.
A special low-cost version of CL.2 modules is supplied without SDH/SONET and
GbE ports. This version provides an improved price/performance solution for DS0
cross-connect and channel-bank applications (see Table 1-4 for maximum
capacity) and LRS-102 replacement. It also creates a platform that allows
upgrade from a transparent rack to an aggregation with GbE &
STM-4/OC-12/STM-4/OC-3 solutions by simple replacement of a CL module.
Protection
The modular, distributed architecture of Megaplex-4 enables redundancy at
different levels of the network and provides a resilient system with no single
point of failure. Hardware redundancy is provided through an optional redundant
power supply and CL modules, with switchover to the backup CL links within
50 msec.
Each combined common logic, cross-connect matrix and broadband link module
(CL) provide automatic switchover between each two STM-1/STM-4/OC-3/OC-12
links within 50 msec, for 1+1 protection against hardware, network or cable
failure. The SDH/SONET employs APS 1+1 protection against link or hardware
failure as well as subnetwork connection protection according to ITU-T Rec G.841
(SNCP for SDH and UPSR for SONET) for path protection and ring topology. This
provides end-to-end service protection.
The CL Ethernet GbE ports employ LAG protection against link or hardware failure.
With the CL.2/A capabilities, Megaplex-4 supports Ethernet Ring Protection
Switching (ERPS) per ITU-T G.8032v1.
Selected I/O modules can also be configured for redundancy and can be
hot-swapped, allowing for continuous service.
For more detailed information about different redundancy types, refer to the
following:
Megaplex-4
•
CL redundancy –Common Logic (CL.2) Modules in this chapter
•
PS redundancy – Power Supply (PS) Modules in this chapter
•
APS – Automatic Protection Switching section in Chapter 7
•
Path protection – Path Protection for SDH/SONET Payload section in
Chapter 7
•
I/O module redundancy – TDM Ring Protection, and TDM Group Protection
and I/O Group Protection sections in Chapter 7
•
Ethernet protection – Configuring the LAG section in Chapter 7
•
Ethernet group (Logical MAC-based) protection – Ethernet Group Protection
section in Chapter 7
•
Hitless Switching Redundancy in Ring topology –HSR Protection section in
Chapter 7
•
Ethernet Ring Protection - Ethernet Ring Protection (ERP) section in Chapter 7
•
DS0 SNCP Protection – DS0 SNCP (DS0-Bundle) Protection section in
Chapter 7.
Overview
1-17
Chapter 1 Introduction
Installation and Operation Manual
Diversity of Rings
In addition to supporting standard SDH/SONET and Ethernet rings, Megaplex-4
can be used to create E1, T1, TDM over SHDSL, TDM over fiber, or a mix of ring
topologies. For more detailed information, refer to TDM Ring Protection section
in Chapter 7.
Megaplex-4 provides a perfect solution in combining low-rate service provisioning
and ring protection.
Modularity and Flexibility
Megaplex-4 is available in two basic chassis:
•
Megaplex-4100 is a 4U-high chassis providing slots for up to 2 AC or DC
power supplies, 2 common logic and 10 I/O modules.
•
Megaplex-4104 is a compact low-cost 2U-high chassis providing slots for up
to 2 AC or DC power supplies, 2 common logic and 4 I/O modules.
Both chassis allow for a “pay as you grow” approach and enable CapEx
optimization.
Next-Generation ADM/Terminal
STM-1/STM-4/OC-3/OC-12 network owners can extend the use of existing ADM
equipment or terminal multiplexers, saving replacement or expansion costs, by
implementing VCAT protocols to carry the Ethernet traffic in a more efficient way
and minimize wasted bandwidth.
Megaplex-4 performs STM-1/STM-4/OC-3/OC-12 add/drop multiplexing for
grooming LAN and TDM traffic over SDH/SONET networks. Ethernet traffic can be
mapped into n x VC-12/VC-3/VC-4 or n x VT1.5/STS-1/STS-3C virtual containers.
Megaplex-4 brings Ethernet economics and packet-switching efficiency to existing
SDH/ SONET/TDM infrastructures. It thereby enables utilities and other private
fiber network owners to reduce both Opex and Capex as they use their optical
bandwidth for reselling revenue generating Ethernet services. New business
opportunities can be created by leveraging existing equipment to support clear
channel data streams and the latest high bandwidth services.
Megaplex-4 eliminates the need for two separate units (ADM and multiplexer) for
private networks where voice, Ethernet and data services are required.
Timing
Flexible timing options enable reliable distribution of timing together with flexible
selection of timing sources, including external station clock for daisy-chaining the
clock signals to other equipment. Megaplex-4 also provides traceable timing
quality and supports automatic selection of best-quality timing reference.
Megaplex-4 timing is fully redundant, i.e., each CL module has its own timing
subsystem, and can supply all the clock signals required by the system via the
chassis timing bus. However, at each time, only one CL module (the active
module) actually drives the timing bus, while the other (standby) module is
disconnected from the bus, but continuously monitors the state of the main
1-18
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
module timing subsystem. If a problem is detected in the active timing
subsystem, the standby subsystem hitlessly takes over.
The user can define the following clock sources:
•
Recovered from the STM-1/STM-4/OC-3/OC-12 interface, including automatic
selection, based on SSM (Synchronization Status Messaging)
•
Recovered from the GbE interface (CL modules only), including automatic
selection based on ESMC (Ethernet Synchronization Messaging Channel)
•
Internal crystal free-running oscillator-based clock
•
Derived from the receive clock of a specified module user port
•
ACR Adaptive clock recovered from a pseudowire circuit (MPW-1 modules
only)
•
External station clock.
Multiple clock sources can be set and assigned corresponding quality and priority.
Megaplex-4 uses the highest quality stratum available, determined by monitoring
the synchronization status messages (SSM) of the configured SDH/SONET clock
sources.
For detailed information about the different system timing modes, refer to the
following sources:
•
Clock Selection in Chapter 9
•
Relevant I/O module section in the Megaplex-4 I/O Modules Installation and
Operation Manual.
Simple Network Time Protocol
The Simple Network Time Protocol (SNTP) provides the means of synchronizing all
managed elements across the network to a clock source provided by NTP servers.
Megaplex-4 supports the client side of a simple network time protocol (SNTP) v.3
(RFC 1769).
Management
Megaplex-4 offers carrier-class service provisioning features, including end-to-end
path management, to ensure continuous service availability. Advanced SNMP
management capabilities provide control and monitoring of all network elements:
SDH/SONET access and ring units as well as remote POP and Last Mile broadband
access feeders and CPEs.
Complete control over the Megaplex-4 functions can be attained via the following
applications:
Megaplex-4
•
CLI-driven terminal utility for management via a local ASCII-based terminal
connection (see Working with Terminal and Terminal Control Port in Chapter
4). Telnet access is supported via IP-based connection.
•
RADview – RAD’s SNMP-based element management system, providing a
dedicated PC/Unix-based GUI for controlling and monitoring the unit from a
network management station. It also includes northbound CORBA interface
Overview
1-19
Chapter 1 Introduction
Installation and Operation Manual
for integration into any third-party NMS (network management system). For
more information, refer to the RADview User's Manual.
•
Shelf View – RAD’s SNMP-based standalone application with fully FCAPScompliant element management. It displays a dynamic graphic representation
of the device panel(s), providing an intuitive, user-friendly GUI.
For more information about configuration alternatives, refer to Management
Alternatives in Chapter 4.
The unit can be managed by and report to up to 10 different users
simultaneously. Accounts of existing and new users can be defined/changed
remotely, using a dedicated RADIUS server as explained under Authentication via
RADIUS Server in Chapter 4.
A wide range of inband and out-of-band management options provide
organizations with the means needed to integrate the equipment within the
organizational management network, as well as transfer their management traffic
seamlessly through the Megaplex-4-based network.
Remote units can be managed in the following ways:
•
Out-of-band, using the 10/100 Ethernet management port (for more
information, see Out-Of-Band Ethernet Control in Chapter 6)
•
Inband, using IP/PPP or IP/HDLC over DCC, via the STM-1/STM-4/OC-3/OC-12
links (for more information, see SDH/SONET Ports in Chapter 6)
•
Inband, using the IP/PPP or IP/FR over a dedicated timeslot in any E1/T1 or
SHDSL link (for more information, see the description of a relevant port in
Chapter 6, for example, Configuring E1 Ports).
•
Inband, via any of the user Ethernet ports, including the CL module GbE ports
(see Configuring Flows in Chapter 8)
•
Via a network management station running RADview, RAD’s SNMP element
management application.
Databases and scripts of commonly used commands can be easily created and
applied to multiple units using command line interface.
Software upgrades can be downloaded to CL and selected I/O modules. Preset
configuration files can be downloaded/uploaded to/from Megaplex-4 via TFTP or
SFTP. For more information and instructions, refer to Chapter 12.
Syslog
The syslog protocol is a client/server-type protocol, featuring a standard for
forwarding log messages in an IP network and supports up to four syslog servers
at present. A syslog sender sends a small text message of less than 1024 bytes
to the syslog receiver. Syslog messages are sent via UDP in cleartext. The Syslog
server acts as a centralized repository for all elements in the network, providing
for a unified logging infrastructure, easier troubleshooting and forensics, lower
operational risks and costs and higher availability and SLA through faster
response time.
1-20
Overview
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Diagnostics
When a problem occurs, Megaplex-4 offers a set of diagnostic functions that
efficiently locate the problem (in the Megaplex-4 chassis, one of I/O modules, a
connecting cable, or external equipment) and rapidly restore full service.
The diagnostic functions are based on the activation of loopbacks at various
ports. These loopbacks enable identifying whether a malfunction is caused by
Megaplex-4 or by an external system component (for example, equipment, cable,
or transmission path connected to the Megaplex-4). A detailed description of the
test and loopback functions is given in Chapter 6, under the corresponding
section (for example, E1 Ports, SHDSL Ports).
Comprehensive diagnostic capabilities include:
•
Local and remote loopbacks
•
Real-time alarms to alert the user on fault conditions
•
SDH/SONET link monitoring
•
Ethernet traffic counters
•
Ethernet, E1/T1, SHDSL and Optical interface status monitoring.
Alarm Collection and Reporting
Megaplex-4 continuously monitors critical signals and signal processing functions.
If a problem is detected, the Megaplex-4 generates time-stamped alarm
messages. The time stamp is provided by an internal real-time clock.
For continuous system monitoring, the user can monitor alarm messages through
the supervisory port. Alarm messages can also be automatically sent as traps to
user-specified network management stations.
The alarms can be read on-line by the network administrator using a Telnet host, an
SNMP-based network management station, or a supervision terminal.
Note
Megaplex-4 can also monitor one external sense input, and will report its
activation as any other internally-detected alarm.
In addition to the alarm collection and reporting facility, the Megaplex-4 has two
alarm relays with floating change-over contacts: one relay for indicating the
presence of major alarms and the other for minor alarms. Each relay changes
state whenever the first alarm is detected, and returns to its normal state when
all the alarms of the corresponding severity disappear. The relay contacts can be
used to report internal system alarms to outside indicators, e.g., lights, buzzers,
bells, etc., located on an alarm bay or remote monitoring panel.
Performance Monitoring
Megaplex-4 collects statistics per physical port and per connection for 15-minute
intervals, which enables the network operator to monitor the transmission
performance and thus the quality of service provided to users, as well as identify
transmission problems. Performance parameters for all the active entities are
continuously collected during equipment operation.
Megaplex-4
Overview
1-21
Chapter 1 Introduction
Installation and Operation Manual
Statistics for the last 24 hours are stored in the device and can be retrieved by
the network management station. For additional information, refer to the
Statistics section for the relevant port (for example Viewing Ethernet Port
Statistics under Ethernet Ports in Chapter 6).
Megaplex-4 maintains a cyclic event log file that stores up to 256 time-stamped
events. In addition, an internal system log agent can send all reported events to a
centralized repository or remote server. For additional information, refer to
Handling Events in Chapter 11.
RADview Performance Management
Megaplex-4 maintains performance management (PM) statistics for selected
entities in the device. The PM statistics are collected into a file periodically, for
display in the RADview PM portal (refer to the RADview System User’s Manual for
further details on the PM portal). The PM collection process can be globally
enabled or disabled for the entire device. In addition, the statistics collection can
be enabled for all entities of a specific type, or for specific entities.
Security
User access to Megaplex-4 is restricted via user name and password. For more
information, refer to Management Access Methods in Chapter 4.
Telnet-like management can be secured using a Secure Shell (SSH) client/server
program. Instead of sending plain-text ASCII-based commands and login requests
over the network, SSH provides a secure communication channel.
SFTP (Secure File Transfer Protocol, also known as SSH File Transfer Protocol) is
supported, to provide secure (encrypted) file transfer using SSHv2.
In addition, Megaplex-4 supports SNMP version 3, providing secure access to the
device by authenticating and encrypting packets transmitted over the network.
For more information, refer to The SNMPv3 Mechanism in Chapter 4.
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network. For more information, refer to Authentication via RADIUS Server
Mechanism in Chapter 4.
1.2
New in this Version
The following new functionalities have been added in version 5.0:
1-22
•
New VS-8/E&M module – New option for the VS voice module with 8 E&M
voice ports
•
New MS-JNPR module – IP/MPLS edge router module based on Juniper vMX
•
New MS-CESP module – Data/voice cross-connect processing engine
•
New MS-UB module – Multiservice virtualization platform
New in this Version
Megaplex-4
Installation and Operation Manual
•
Chapter 1 Introduction
Configurable MTU for management data channel – Management router MTU
configuration is no longer hard-coded to 200 bytes. It can be now configured
in the range of 1260 to 1500 bytes or set to 200 bytes
1.3
Physical Description
System Structure
Megaplex-4 units use modular chassis. The chassis has physical slots in which
modules are installed by the user to obtain the desired equipment configuration.
Megaplex-4 configuration includes the following main subsystems:
•
I/O subsystem, provides interfaces to the user’s equipment. The number of
user interfacing modules that can be installed in a chassis is up to 10 for
Megaplex-4100 and 4 for Megaplex-4104
•
Multiplexing, timing and control subsystem, located on the common logic and
cross-connect (CL.2) modules.
•
Power supply subsystem, located on the power supply (PS) modules
•
Chassis. The main function of the chassis is to provide interconnections
between the various modules, and in particular to connect between the user
interfacing (I/O) modules, and the CL modules that provide the multiplexing
function and the optional connections to SDH/SONET and/or Ethernet
networks.
CL and PS modules are always installed in their dedicated chassis slots, whereas
the user interfacing modules can be installed in any of the other chassis slots
(called I/O slots).
Any operational Megaplex-4 system must include at least one CL module and one
PS module. These modules are thus referred to as system modules. User
interfacing modules, called I/O modules, are added to this basic configuration.
Megaplex-4 system modules are critical components, because a failure in any one
of these modules could disable the whole system, whereas a failure in an I/O
module affects only a small part of the system, and can be generally overcome by
using alternate routes, putting unused capacity into service, etc. Therefore, in
most applications Megaplex-4 units should be equipped with an additional
redundant system module of each type. Redundancy is also available for the
network interfacing subsystems.
The Megaplex-4 system is designed to automatically put a redundant module or
subsystem in service in case the corresponding system component fails, thereby
ensuring continuous system operation in the event of any single module failure.
Moreover, redundant modules may be inserted or removed even while the system
operates.
Description of Megaplex-4100 Chassis
Figure 1-13 shows a general view of a regular Megaplex-4100 chassis.
Megaplex-4
Physical Description
1-23
Chapter 1 Introduction
Installation and Operation Manual
Megaplex-4100 is built in a 4U-high chassis that is intended for installation in 19”
and 23” racks, using brackets attached to the sides of the chassis, near the front or
rear panel. Thus, a Megaplex-4100 can be installed in accordance with the specific
requirements of each site, either with the Megaplex-4100 front panel toward the
front of the rack (per ANSI practice), or with the module panels toward the front
(per ETSI practice).
System status indicators are located on both the front panels and on the CL
module panels. Additional indicators are located on the module panels. The cable
connections are made directly to the module panels.
Figure 1-13. Typical Megaplex-4100 Chassis, General View
Rear View
Figure 1-14 shows a typical rear panel of the Megaplex-4100 chassis and
identifies the slots and their use. The chassis has 14 slots:
•
Two slots are reserved for power supply (PS) modules
•
Two slots are reserved for CL modules
•
The other 10 slots, arranged in two groups of 5 each, are intended for I/O
modules. Each I/O slot can accept any type of I/O module.
Note the labels which designate the type of module that can be installed in each
slot:
•
Slots labeled PS-A and PS-B (identified as ps-a and ps-b on supervision
terminal screens): power supply modules
•
Slots labeled I/O-1 to I/O-10 (identified as slot 1 to slot 10 on supervision
terminal screens): I/O modules
•
Slots labeled CLX-A and CLX-B (identified as cl-a and cl-b on supervision
terminal screens): CL modules.
In addition, each slot is keyed, therefore it is not possible to install a wrong
module type.
1-24
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
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
PS-B
PS-A
PS-B
IO-1 IO-2
I/O 1
PP S/A
S/D C
C
P S/D C
P S/D C
I/O 2
IO-3
I/O 3
IO-4 IO-5
I/O 4
I/O 5
CL-A
CL-B
CL -A
IO-6
CL -B
I/O 6
C L-2
M 8E1
IO-7
I/O 7
C L-2
1
2
3
4
5
6
7
8
L ASER
L ASER
CL ASS
LOC
E
CL ASS
1
ON LI NE
M
E
S
D
H 1
/
S
O
N
E 2
T
M
E
CH-3 CH-3
REM
LOC
LI NK
1-8
M
E
CH-4 CH-4
REM
VD C-I N
M
CL ASS
RT N
+72V
ON
-48V
100-120VA C
200-240VA C
1
AC T
Rx
48V
REM
LOC
L ASER
72V
-
LI NK
Tx
+
E
T
H
1
CH-6
REM
LOC
ON
S
D
H 1
/
S
O
N
E 2
T
ON
LI NE
AC T
G
b
E
2
CH-5
C
O
N D
T C
R E
O
L
LI NK
E
T
H
C
O
N D
T C
R E
O
L
Rx
Rx
Tx
AC T
LI NK
Tx
LI NK
E
T
H
2
E
T
H
3
PS Slots
REM
LOC
CH-8
REM
I/O Slots
A
L
A
R
M
C
L
O
C
K
ON /LOS
A
L
A
R
M
A CT
ET H2
ON
LI NE
AC T
I/O 9
I/O 1 0
1
2
3
4
5
6
7
8
S
H
D
S
L
.
b
I
s
E
T
H O
LI NK /
A CT
E
T
H
LI NK
1-8
LI NK /
A CT
O
P
A
P
B
100
100
A CT
1
1
L ASER
L ASER
CL ASS
CL ASS
1
1
O
P
A
L ASER
CL ASS
LI NK
AC T
LI NK
E
T
H
CH-7
AC T
LI NK
ET H1
2
AC T
LI NK
ALM
LOS
1
G
b
E
LOC
+
ON LI NE
ALM
LOS
CH-2 CH-2
L
I
N
K
1
CH-1 CH-1
REM
LOC
REM
LOC
VD C-I N
I/O 8
M 8E1
STAT US
STAT US
L
I
N
K
IO-8 IO-9 IO-10
C
L
O
C
K
ON /LOS
2
1
E
T
H
1
E
T
H
2
E
T
H
3
LO SS
E
T
H
1
E
T
H
2
E
T
H
3
CL Slots
L
A IS
I
N
LO SS
LI NK K
LASER
CLASS
1
A CT
A
AC T
1
B
AC T
E
T
H
L
I
N
3 K
O
P
B
4
2
A IS
LO SS
LI NK
LI NK
AC T
LI NK
I/O Slots
Figure 1-14. Megaplex-4100 Chassis, Typical Rear View
Front Panel
The front panel of the Megaplex-4100 chassis is shown in Figure 1-15. For
description of LED indicators, see Chapter 3.
POWER SUPPLY
A
B
SYSTEM
ALARM
TEST
MEGAPLEX-4100
Figure 1-15. Megaplex-4100 Chassis, Front Panel
Description of IEEE-1613 compliant Megaplex-4100 Chassis
A special IEEE-1613 compliant chassis includes a heat sink on the front panel and
two special fixtures replacing the vertical walls of the CL module slots, to allow
more airflow into the CL modules. These fixtures use I/O 5 and I/O 6 slots, on
both sides of CL modules.
Megaplex-4
Physical Description
1-25
Chapter 1 Introduction
Installation and Operation Manual
The figures below show a general view of an IEEE-1613 compliant Megaplex-4100
chassis. The chassis is intended for installation in 19” rack, using brackets
attached to the sides of the chassis, near the front or rear panel.
Figure 1-16. IEEE-1613 Compliant Megaplex-4100 Chassis, Rear View
Figure 1-17. IEEE-1613 Compliant Megaplex-4100 Chassis, Front View
Rear View
The figure below shows a typical rear panel of the Megaplex-4100 IEEE-1613
compliant chassis and identifies the slots and their use. The chassis has 14 slots:
1-26
•
Two slots are reserved for power supply (PS) modules (special ordering
options)
•
Two slots are reserved for CL modules (special ordering options)
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
•
8 slots, arranged in two groups of 4 each (I/O 1,2,3,4 and I/O 7,8,9,10), are
intended for I/O modules. Each I/O slot can accept any type of I/O module
•
I/O slots 5 and 6 are reserved for accommodation of CL module cooling
fixtures.
Each slot is keyed, therefore it is not possible to install a wrong module type.
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.
Figure 1-18. IEEE-1613 Compliant Megaplex-4100 Chassis, Rear View
Front Panel
The front panel of the IEEE-1613 Compliant Megaplex-4100 chassis is shown in
Figure 1-15. For description of LED indicators, see Chapter 3.
Megaplex-4
Physical Description
1-27
Chapter 1 Introduction
Installation and Operation Manual
Figure 1-19. IEEE-1613 Compliant Megaplex-4100 Chassis, Front Panel
Description of Megaplex-4104 Chassis
Figure 1-20 shows a general view of the Megaplex-4104 chassis.
Figure 1-20. Megaplex-4104 Chassis
The chassis has 8 slots:
•
Two slots are reserved for power supply (PS) modules
•
Two slots are reserved for CL modules
•
The other 4 slots are intended for I/O modules. Each I/O slot can accept any
type of I/O module.
The Megaplex-4104 chassis is supplied with brackets for installation in racks. The
brackets are attached to the sides of the chassis, as explained in Chapter 2.
Figure 1-21 shows a typical front view of the Megaplex-4104 chassis equipped
with two CL.2/4104 modules, and identifies the slots and their use.
1-28
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Figure 1-21. Megaplex-4104 Chassis, Front View
The rear panel of the Megaplex-4104 chassis is shown below. For description of
LED indicators, see Chapter 3.
Figure 1-22. Megaplex-4104 Chassis, Rear Panel
I/O Modules
Table 1-2 lists the I/O modules currently offered for the Megaplex-4 in the
alphabetical order of their names. Contact RAD Marketing for information on
additional modules that may be available for your specific application
requirements.
Table 1-2. Megaplex-4 I/O Modules
Megaplex2100/2104
Compatible
Module
Description
ACM
Alarm and diagnostics module with four outbound relays for reporting
internal alarms to outside indicators such as bells, buzzers, etc. Eight
inbound sensors enable external alarms or conditions to be reported to
the Megaplex system.
Yes
ASMi-54C
Eight-port SHDSL.bis module with two Ethernet ports, for transporting
digital data to customer premises over the existing copper infrastructure
of the distribution network while eliminating the need for repeaters. It
multiplexes Ethernet over 1, 2, and 4 pairs of SHDSL.bis copper lines.
Each SHDSL port can operate in a link with an ASMi-54/ASMi-54L
standalone unit offered by RAD.
No
Has eight independently configurable SHDSL.bis external ports for SHDSL
services, and two 10/100 Mbps Ethernet ports, for packet-based
services.
Can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R) SHDSL.bis
Terminal Unit for up to 8 ASMi-54 standalone devices or another ASMi54C module.
Megaplex-4
Physical Description
1-29
Chapter 1 Introduction
Installation and Operation Manual
Megaplex2100/2104
Compatible
Module
Description
ASMi-54C/N
No
Eight-port SHDSL.bis modules with eight E1 and two optional Ethernet
ports, for transporting digital data to customer premises over the
existing copper infrastructure of the distribution network, while
eliminating the need for repeaters. Transparently forward E1 data and
optionally Ethernet, over 1 or 2 pairs of SHDSL.bis/SHDSL copper lines to
ASMi-54/ASMi-54L (SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone
modems on the remote site.
Have eight independently configurable SHDSL.bis external ports for
SHDSL services, eight E1 ports for E1 services and two optional 10/100
Mbps Ethernet ports, for packet-based services.
D-NFV
Virtualization module, adding to Megaplex-4 a built-in standard Intel x86 No
core that hosts virtual machines providing virtual network functions (VFs)
or value-added service capabilities. The module had one GbE and four
Fast Ethernet user ports.
HS-6N,
HS-12N
High-speed data module, providing 6, respectively 12, high-speed V.35
or RS-530/V.11 data channels. Channel data rates are user-selectable in
the range of 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).
Yes
Supports enhanced clock modes. Any channel can be directed to any E1
or T1 link or internal PDH port.
HS-703
High-speed data sub-channel module, providing four 64-kbps
codirectional ITU-T Rec. G.703 data channels.
Yes
HS-RN
Low-speed data module, providing 4 synchronous or asynchronous data
channels with ITU-T Rec. V.24/EIA RS-232 interfaces, each operating at
an independently selectable data rate in the range of 0.6 kbps up to
38.4 kbps in the asynchronous mode, and up to 64 kbps in the
synchronous mode. End-to-end control signals are also supported.
Available in two models:
Yes
•
HS-RN/HDLC: employing proprietary, HDLC-based, rate adaptation for
performance optimization with respect to either bandwidth or
latency, in accordance with user configuration
•
HS-RN/V.110: employing V.110 rate adaptation, fully compatible with
the old HS-R module. Enables optimum rate utilization of uplink
bandwidth and minimum end-to-end data latency
Supports unidirectional broadcast applications.
HS-S
ISDN basic rate access module with four type “S” interfaces. Performs
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-4 links,
and can provide phantom feed to user equipment
1-30
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Megaplex2100/2104
Compatible
Module
Description
HS-U-6,
HS-U-12
ISDN basic rate access module with 6, respectively 12, type “U” interfaces.
Performs submultiplexing and data rate adaptation on B channels per ITU-T
Rec. I.460. The module supports two operation modes:
•
/I: intended for extension of ISDN lines, can provide phantom feed to
user equipment. Supports 2B + D channels, and the channel data rates
are user-selectable (16, 32, and 64 kbps for each B channel, and
16 kbps for the D channel).
•
/1: intended for use over leased lines, and can be used as dedicated
line termination units for the ASM-31 and ASMi-31 short-range
modems offered by RAD. Supports user channel data rates of 4.8,
9.6, 19.2, 48, 56, and 64 kbps over each B channel, and 128 kbps by
combining the two B channels. The D channel is ignored.
Yes
HSF-2
Interface module for teleprotection equipment, complying with IEEE C37.94
requirements. Provides two ports with 850 nm multimode fiber interfaces,
with a capacity of up to 10 × 64 kbps per port.
LS-6N,
LS-12
Data sub-multiplexer modules, providing 6, respectively 12, synchronous Yes
or asynchronous data channels with ITU-T Rec. V.24/EIA RS-232
interfaces, each operating at independently selectable data rate in the
range of 2.4 to 64 kbps. Support end-to-end transmission of control line
per channel. LS-12 channels can be bundled into two groups, each
independently routed to a different destination.
M-ETH
Module with 8 GbE interfaces supporting optical or electrical media and
providing 9 Gbps switching capacity (up to 1 Gbps capacity to the CL.2
module and 8 Gbps shared among its 8 external ports). The capacity can
be allocated among the 8 interfaces with a granularity of 100 Kbps.
No
M16E1
Module with 16 E1 DSU interfaces, providing up to 160 E1 ports per
chassis and transparent E1 transfer to SDH.
No
M16T1
Module with 16 T1 DSU interfaces providing up to 160 T1 ports per
chassis and transparent T1 transfer to SONET.
No
M8E1
No
Module with eight E1 interfaces and user-selectable DSU or LTU mode,
and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
M8T1
No
Module with eight T1 interfaces and user-selectable DSU or CSU mode,
and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
Megaplex-4
Yes
Physical Description
1-31
Chapter 1 Introduction
Installation and Operation Manual
Module
Description
M8SL
Module with eight SHDSL interfaces, for transporting E1 and fractional
E1 payloads, and three 10/100 Mbps Ethernet ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The
three Ethernet ports are connected to an internal Ethernet switch, and
share a 100 Mbps Fast Ethernet connection to the CL module.
Megaplex2100/2104
Compatible
No
Each port features an independent multi-rate SHDSL modem,
transmitting at user-selectable data rates in the range of 192 kbps to
2048 kbps. Has internal non-blocking full cross-connect matrix similar to
M8E1 and M8T1 modules.
SHDSL interface type (STU-C or STU-R) is user-selectable.
Compatible with other RAD equipment having STU-R SHDSL interfaces,
such as the ASMi-52 SHDSL Modems. M8SL modules will also operate in
a link with 991.2-compatible STU-R units from other vendors.
MPW-1
No
Pseudowire server I/O module that provides TDM pseudowire access
gateway services over packet-switched networks (Ethernet, IP, and
MPLS) for TDM traffic (E1, T1, SHDSL, ISDN, high-speed and low-speed
data, voice) received via the Megaplex-4 TDM buses from other modules.
Has eight independently-configurable internal DS1 ports, each capable of
handling 32 timeslots, for a total processing capacity of 256 timeslots
(the equivalent of 8 E1, or 2.048 Mbps streams).
MS-JNPR
No
Carrier-class IP/MPLS router, based on Juniper’s virtualized MX router
series (vMX). Provides Megaplex-4 TDM and Voice/Ethernet and IP service
transport over IP/MPLS network using Layer 2 VPN, VPLS, IPVPN.
MS-CESP
Multiservice CESprocessor module. Provides voice compression &
conferencing, low-speed rate adaptation, sub-TS/DS0 cross-connect for
compressed voice and low-speed data.
No
MS-UB
Multiservice virtualization platform with Ubuntu Linux distribution. Adds
virtualization capabilities to Megaplex-4, enabling users to install various
VNFs running on an x.86 server card. Users may develop and release
their own customized functions embedded in the Megaplex-4 system.
No
OP-108C
No
Dual E1 and Ethernet multiplexer, where each multiplexer operates
independently and can operate in a link with the Optimux-108 and
Optimux-108L, 4 E1 and Ethernet Multiplexer standalone units offered by
RAD.
Each multiplexer transparently transports four independent E1 data
streams and one 100BASE-TX Ethernet channel over one optical link.
Each link has two optical ports, with user-configurable redundancy
between the two ports.
The optical ports can be equipped with field-replaceable SFPs. Support
for standard SFP optical transceivers link interfaces enables selecting the
optimal interface for each application. High-performance SFPs available
from RAD can achieve ranges of up to 120 km (75 miles).
1-32
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Megaplex2100/2104
Compatible
Module
Description
OP-34C
16-channel E1 and Ethernet multiplexer, transporting 16 independent E1 No
data streams and optionally Ethernet data from a 100BASE-TX Ethernet
channel over one link operating at the E3 (34.386 Mbps) rate. Is
primarily intended to operate in a link with the Optimux-34 standalone
fiber-optic multiplexer offered by RAD. However, it can also operate in a
link with another OP-34C module.
The link has two ports, with user-configurable redundancy between the
two ports. The ports can be equipped with field-replaceable SFPs with
optical or copper (ITU-T Rec. G.703) interfaces. Using SFP optical
transceivers enables selecting the optimal interface for each application.
High-performance SFPs available from RAD can achieve ranges of up to
110 km (68.3 miles).
Ringer-2100R
Ringer-4104R
DC power supply module for DC feed and up to 32 voice channel ring
voltages for Megaplex-4100/Megaplex-4104
Yes
SH-16
16-port SHDSL.bis EFM module, delivering Ethernet digital data to
customer premises via High speed Digital Subscriber Line
(SHDSL/SHDSL.bis) technology, as standardized by ITU-T Rec. G.991.2.
No
Each SHDSL.bis port is a multirate SHDSL/SHDSL.bis modem transmitting
user-selectable data rates up to 5.7 Mbps on each pair. Extended rates
of up to 15 Mbps per 2W/30 Mbps for 4W are available for ASMi-54L
modem at the far end (EFM mode).
SH-16 transports Ethernet over 1 (2-wire), 2 (4-wire), and 4 (8-wire)
pairs of SHDSL.bis copper lines.
T3
Single-port multiplexer module, providing access to standard T3
equipment over unbalanced copper lines with full duplex data rates of
44.7 Mbps.
No
TP
Command In/Out teleprotection module with four selectable voltage
(Teleprotection) inputs and eight outputs, secured and reliable end-to-end commands
transmission.
No
VC-16,
VC-8,
VC-4,
VC-8A,
VC-4A
Yes
Analog voice modules VC-16, VC-8 and VC-4 provide 16, 8 or 4
PCM-encoded toll-quality voice channels.
The modules are available in three models:
•
E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464
Types I, II, III and V, and BT SSDC5
•
FXS: 2-wire interfaces for direct connection to telephone sets
•
FXO: 2-wire interfaces for direct connection to PBX extension lines.
VC-8A and VC-4A are similar to VC-8 and VC-4 modules, except that they
also support ADPCM.
VC-6/LB
Megaplex-4
Yes
6-port PCM voice module for local battery telephones. It is a
user-programmable voice interface module for Megaplex-4 used for
connection of local battery-powered (LB) telephones. The voice channels
use toll-quality 64 kbps PCM voice encoding in compliance with ITU-T
Rec. G.711 and AT&T Pub. 43801.
Physical Description
1-33
Chapter 1 Introduction
Installation and Operation Manual
Megaplex2100/2104
Compatible
Module
Description
VC-4/ OMNI
“Omnibus” E&M voice module providing four toll-quality voice channels.
Intended for broadcast applications, in which a master site needs to
communicate with multiple remote stations simultaneously (such as to
broadcast an important message). Also provides party-line service.
Yes
VS Modules
Multiservice versatile module with broad variety of services available in a
single module:
No
Note
•
VS-12: 12 serial data ports and 2 Ethernet ports
•
VS-6/BIN: 6 serial data ports, 8 in/out binary command ports and 1
Ethernet port.
•
VS-6/C37: 6-port serial module with 2 fiber optic C37.94 ports and 1
Ethernet port
•
VS-6/703: 6-port serial module with 2 64-kbps G.703 codirectional
interfaces
•
FXS/E&M: Voice module with 4 E&M ports and 8 FXS ports
•
VS-8/E&M: Voice module with 8 E&M ports
•
VS-6/E&M: 6-port serial module with 4 E&M voice ports and 1
Ethernet port
•
VS-6/FXO: 6-port serial module with 8 FXO voice ports and 1 Ethernet
port
•
VS-6/FXS: 6-port serial module with 8 FXS voice ports and 1 Ethernet
port
•
VS-16E1T1-EoP 16-port E1/T1 module with EOP support
•
VS-16E1T1-PW: 16-port E1/T1 module with pseudowire support
•
VS-6/E1T1: 6 serial data ports, 8 E1/T1 ports and 1 Ethernet port
Some of the modules behave differently in the Megaplex-4100 /4104 and
Megaplex-2100/2104 chassis.
Common Logic (CL.2) Modules
The Common Logic (CL.2) module controls the Megaplex operation and is the
interface for its configuration and management.
CL.2 houses the TDM and Packet processing engines, as well as the GbE and
SDH/SONET uplinks.
For direct connection to the SDH/SONET network, CL.2 features two standard
network ports with a software-configurable STM-1/STM-4 or OC-3/OC-12
interface. The dual ports on the CL.2 module can be used either for operation in
parallel or for redundancy.
For direct connection to packet-based networks, CL.2 has two UTP or SFP-based
GbE ports. The UTP interface features autonegotiaton speed detection
capabilities.
1-34
Physical Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Megaplex-4 allows the installation of two CL.2 modules of the same type, to
ensure continuous operation when one module is reset, restarted, or stops
operating for any reason. In such a case, the redundant main module immediately
takes over the unit, using its own pre-configured settings. The switch-over to the
protecting module occurs automatically upon detection of failure in the active
module, or upon removing the active module from the chassis. The SDH/SONET
and/or Ethernet traffic subsystems located on the CL modules operate
independently of the management subsystems. For instructions on extracting and
inserting a CL module, refer to Removing/Installing the CL Module in Chapter 2.
Power Supply (PS) Modules
PS Modules
Two PS modules can be installed in the chassis. Only one PS module is required to
provide power to a fully equipped Megaplex-4; installing a second module
provides redundancy. While both modules operate normally, they share the load;
in case one fails or does not receive power, the other module continues to
provide power alone. Switch-over is automatic and does not disturb normal
operation. For instructions on extracting and inserting a power supply, refer to
Removing/Installing the PS Module in Chapter 2.
PS modules for Megaplex-4100 and Megaplex-4104 have different shape and
technical characteristics. -48 VDC nominal DC power supplies are available for
both chassis. In addition, Megaplex-4100 can be ordered with AC (115 or 230
VAC nominal) power supply modules. For the full list of module options for the
Megaplex-4100 and Megaplex-4104 chassis, see Table 1-8.
Feed and Ring Voltage Sources
External feed voltages are required by the following modules:
•
Voice modules installed in AC-fed chassis
•
ISDN modules
•
SHDSL modules.
The recommended source for external voltages in the case of voice and ISDN
modules is Ringer-2200N offered by RAD. Ringer-2200N is a standalone unit
intended for rack mounting, capable of providing power for up to 120 voice
channels. Refer to the Ringer-2200N Installation and Operation Manual for
connection instructions.
The recommended source for external phantom feed voltages in the case of
SHDSL modules is MPF (Megaplex Power Feed) offered by RAD. standalone unit
intended for rack mounting, MPF provides power for Megaplex SHDSL modules
that require DC voltage to remote DSL repeaters or modems (up to 40 active
SHDSL modems or repeaters operating in 4-wire mode). Refer to the MPF
Installation and Operation Manual for connection instructions.
For additional details, refer to the Ringer-2200N Installation and Operation Manual
and MPF Standalone Power Supply for ASMi-54C/N modules section in the
Megaplex-4 I/O Modules Installation and Operation Manual.
Megaplex-4
Physical Description
1-35
Chapter 1 Introduction
Installation and Operation Manual
1.4
Functional Description
Megaplex-4 Architecture
STM-n/OC-n
STM-n/OC-n
GbE
GbE
Megaplex-4 unique dual star topology architecture (see Figure 1-23) connects the
common logic processing engines to any of the 10 I/O slots independently. In
addition each of the I/O slots is connected by a TDM path, as well as an Ethernet
path, allowing true native TDM and Ethernet traffic handling with minimal
encapsulation delays, no overhead and dual TDM-Ethernet mode modules.
Common Logic
Packet
Engine
Dual Star
Topology Connection
TDM
Engine
Each I/O Module has an
Independent “Traffic Highway”
Ethernet
Interface
TDM
Interface
Ethernet
Interface
Ethernet
Interface
TDM
Interface
I/O
TDM
Interface
Ethernet
Interface
I/O
Ethernet
Interface
I/O
TDM
Interface
TDM
Interface
TDM
Interface
Ethernet
Interface
TDM
Interface
Ethernet
Interface
TDM
Interface
TDM
Interface
Ethernet
Interface
Ethernet
Interface
10/4 x I/O
Figure 1-23. Megaplex-4 Internal Architecture
The Megaplex-4 architecture includes the following main subsystems:
•
I/O subsystem: provides interfaces to the user’s equipment. For description,
see I/O Modules section below.
•
TDM engine:
•
1-36
DS0 cross-connect matrix: handles the TDM traffic. The matrix also
handles the signaling information associated with TDM traffic.
DS1 cross-connect matrix: provides direct timing-independent crossconnect of E1/T1 streams directly to any selected VC-12/VT1.5.
PDH mapper and framer: handle the TDM traffic directed to the network,
and enable mapping any E1/T1 port to any VC-12/VT1.5, respectively.
SDH/SONET engine: includes the circuits needed to interface to an
SDH/SONET network:
Functional Description
Megaplex-4
Installation and Operation Manual
•
Chapter 1 Introduction
Low-order/high-order (LO/HO) cross-connect matrix: controls the routing
of VCs/VTs at all the levels among the PDH mapper, and the SDH/SONET
links. Also provides automatic protection switching (APS) for the network
links, and path protection.
SDH/SONET interfaces: provide the physical interfaces for the SDH/SONET
links.
Ethernet (packet) engine: includes the circuits needed to interface to a
packet-switched network. The Ethernet traffic handling subsystem includes:
Packet processor: controls the forwarding of Ethernet traffic within the
Megaplex-4 (including forwarding from internal ports, Ethernet-over-TDM
and virtually concatenated groups) to external Ethernet ports as well as
carrier Ethernet functionality (traffic-management, OAM&P) and carrier
grade capabilities (G.8032v1 ERPS) when using the CL.2/A assembly
HO/LO mapper and VCAT engine: handle the Ethernet traffic directed for
transport over the SDH/SONET network by means of virtually
concatenated groups, with optional LCAS support (per ITU-T Rec.
G.7042).
GbE interfaces: provide the physical interfaces for the packet switched
network links.
•
Timing subsystem: provides timing signals to all the Megaplex-4 circuits, and
external (station) clock interfaces. For redundancy, two independent
subsystems, each located in a CL module, are used. For more information,
see Clock Selection in Chapter 9.
•
Management subsystem: controls Megaplex-4 operation, stores its software
and configuration, and provides interfaces for local and remote management,
and for alarm reporting. The management subsystem is also redundant: two
independent subsystems, each located in a CL module, are used. For more
information, see Management Access Methods in Chapter 4, Management
Bridge and Management Router in Chapter 8, as well as Chapter 12, Software
Upgrade.
•
Power supply subsystem: includes power supply modules that provide power
to the internal circuits, and an interface for external line feed. For
redundancy, two power supply modules can be installed in the chassis. For
more information, see Power Supply (PS) Modules in this chapter and
Installing PS Modules in Chapter 2.
Figure 1-24 illustrates the position and the contents of the TDM, SDH/SONET and
Packet engines in the Megaplex-4 Data Flow Block Diagram.
Megaplex-4
Functional Description
1-37
Chapter 1 Introduction
Installation and Operation Manual
SDH/SONET
Framers and
HO/LO VC/VT
Cross-Connect
Matrix
VCAT
Engine
E1/T1
Mapper
TDM Engine
Packet Engine
Packet
Processor
HO/LO
and VCAT
Mapper
SDH/SONET
Engine
SDH/SONET Ports
GbE Ports
DS1
Cross-Connect
Matrix
E1/T1
Framer
DS0
Cross-Connect
Matrix
ETH
DS1
DS0
Figure 1-24. Data Flow Block Diagram
TDM Engine
TDM traffic can be switched between any of the following entities on the specific
level:
•
DS0 (analog and digital interfaces: voice, serial, framed E1/T1, E1 over DSL,
E1/T1 over PW or multiplexed fiber, E1/T1 coming from VC-12/VT1.5)
•
DS1 (unframed E1/T1 coming from M16E1/M16T1, Optimux modules or
ASMi-54C/N): transparent and clock independent DS1 processing towards
SONET/SDH or other I/O ports
•
SDH/SONET (high and low level cross connect between SDH/SONET ports).
The cross-connect level can be selected to DS1 or DS0 operation mode per port.
DS0 Cross-Connect Matrix
The DS0 cross-connect matrix located on CL modules provides fully non-blocking
1/0 cross-connect among I/O modules and PDH ports of the CL.2 modules. This
matrix operates in coordination with the cross-connect matrices located on most
types of I/O modules.
The DS0 cross-connect matrix provides full control over the routing of individual
timeslots. This is needed for handling the payload of E1 ports with G.704
framing, T1 ports with SF or ESF framing, and for the inband management
timeslot. The traffic associated with sub-E1 ports (such as ISDN, voice or serial
1-38
Functional Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
interfaces} is always handled in the DS0 mode. Accordingly, Megaplex-4
distinguishes among three main types of payload per timeslot:
•
Voice: timeslots carrying PCM-encoded payload.
Channel-associated signaling (CAS) information is always associated with
voice timeslots, and therefore it must also be converted when
cross-connecting timeslots from ports using different standards.
•
Data: data timeslots are transparently transferred from port to port. In
general, it is assumed that no CAS is associated with data timeslots.
•
Management: one timeslot can be assigned in any E1 or T1 port to carry
inband management traffic to the end user’s equipment. Such timeslots are
always directed to the CL management subsystem, for processing.
The flow of payload carried by data and voice timeslots is normally bidirectional
(full duplex connection). However, for individual timeslots, it is also possible to
define unidirectional flows, called unidirectional broadcasts, from one source (a
timeslot of a source port) to multiple destinations (each destination being a
selected timeslot of another port). For more information, see the Unidirectional
Broadcast Function section under Cross-Connections in Chapter 8.
The following diagram and table illustrate the DS0 matrix capacity.
For the regular CL.2 modules (with SDH/SONET and GbE ports), the maximum
capacity on the I/O side is achieved with the following module combination:
•
Megaplex-4100: 8 M16E1/M16T1 modules + 2 M8E1/M8T1 modules
•
Megaplex-4104: 4 M16E1/M16T1 modules.
For the CL.2 modules without SDH/SONET and GbE ports (DS0 only option), the
maximum capacity on the I/O side is achieved with 10 M16E1/M16T1 modules for
Megaplex-4100 and 4 M16E1/M16T1 modules for Megaplex-4104.
Table 1-3. Maximum DS0 Matrix Capacity
Modules
SDH
SONET
SDH/SONET
(Network) side
2 CL.2 modules
4032 (2 x 63 × 32) DS0
4032 (2 x 84 × 24) DS0
I/O (Tributary) side
MP-4100
8 M16E1/M16T1 modules
3840 (120* × 32) DS0
2880 (120* × 24) DS0
2 M8E1/M8T1 modules
512 (2 x 8 × 32) DS0
384 (2 x 8 × 24) DS0
I/O (Tributary) side
MP-4104
4 M16E1/M16T1 modules
2048 (64 × 32) DS0
1536 (64 × 24) DS0
Total MP-4100
8384 DS0
7296 DS0
Total MP-4104
6080 DS0
5568 DS0
*8 x 16 =128 – the closest number to the 120 E1/T1 restriction.
The resulting I/O + CL.2 capacity is up to 8384 DS0 for SDH and 7296 DS0 for
SONET.
Megaplex-4
Functional Description
1-39
Chapter 1 Introduction
Installation and Operation Manual
Table 1-4. Maximum DS0 Matrix Capacity (DS0 only option)
Modules
E1
T1
SDH/SONET
(Network) side
2 CL.2 modules
-
-
I/O (Tributary) side
MP-4100
10 M16E1/M16T1 modules
5120 (160 × 32) DS0
3840 (160 × 24) DS0
I/O (Tributary) side
MP-4104
4 M16E1/M16T1 modules
2048 (64 × 32) DS0
1536 (64 × 24) DS0
Total MP-4100
5120 DS0
3840 DS0
Total MP-4104
2048 DS0
1536 DS0
DS1 Cross-Connect Matrix
The DS1 cross-connect matrix provides direct timing-independent cross-connect
of E1/T1 streams directly to any selected VC-12/VT1.5. The E1/T1 traffic from
selected modules (M16E1/M16T1, ASMi-54C/N, Optimux) can be mapped directly
to SONET/SDH without passing the DS0 matrix, thus maintaining independent
timing of the E1/T1 links.
When using the DS1 cross-connect for Megaplex-4100, up to 160 E1/T1 links can
be added and dropped at each node when connected over STM-4/OC-12. The
DS1 cross-connect matrix has a capacity of 160 × DS1 for the I/O side. On the
CL.2 side, the matrix capacity is 252 × VC-12/VT1.5 per Megaplex-4 node. The
252 x VC/VT is the total budget of cross-connected LO (VC-12/VC-3/VT1.5) and
HO (VC-4/STS-1) containers.
E1/T1 Framers and Mappers
The TDM payload directed to the network is structured by the DS0 cross-connect
matrix and applied to the E1/T1 framers. Each framer behaves as a logical E1/T1
port, with user-selectable framing: each CL.2 module can have up to 63 E1 ports,
or up to 84 T1 ports, in accordance with the SDH/SONET framing mode.
The operation mode of each framer can be configured by the user:
•
For SDH network interfaces, E1 ports are supported
•
For SONET network interfaces, T1 ports are supported.
The frame type is also selectable, separately for each port:
•
For E1 ports, either basic G.704 framing (identified as G732N) or G.704
multiframe (G.732S) can be selected.
•
For T1 ports, the selections are SF (D4) and ESF.
Each framer adds the appropriate overhead and creates the frame structure. The
data stream provided by each framer is applied to the E1/T1 mappers:
•
1-40
For E1 ports, the mapper enables mapping the port data stream to any of the
63/252 VC-12 in the STM-1/STM-4 signal.
Functional Description
Megaplex-4
Installation and Operation Manual
•
Chapter 1 Introduction
For T1 ports, the mapper enables mapping the port data stream to any of the
84/336 VT1.5 in the OC-3/OC-12 signal.
SDH/SONET Engine
The SDH/SONET engine includes the following parts:
•
Network port interfaces
•
SDH/SONET framers and high-order (HO – STS-1/VC-4) cross-connect matrix.
The SDH/SONET subsystem is integrated with the Ethernet over SDH/SONET
engine.
SDH/SONET Network Port Interfaces
Each CL.2 module has two STM-1/OC-3/STM-4/OC-12 ports. The ports can be
ordered either with the following interfaces:
•
STM-1/OC-3:155.52 Mbps ±4.6 ppm
•
STM-4/OC-12: 622.08 Mbps ±4.6 ppm.
Each port has an SFP socket that provides the physical interface. For more
information, see SDH/SONET Ports in Chapter 6.
SDH/SONET Framer and LO/HO Cross-Connect Matrix
The SDH/SONET framer subsystem provides the frame assembly/disassembly
services and SDH/SONET overhead processing for the link to the network. The
framer operating modes (SDH or SONET, STM-1/OC-3 or STM-4/OC-12) are
selected by software configuration.
The low-order/high-order (LO/HO) cross-connect matrix controls the routing of
VCs/VTs at all the levels between the E1/T1 mapper, VCAT mapper, and the
SDH/SONET links. It also provides automatic protection switching (APS) for the
network links, and path protection.
The LO part supports low-order cross-connections (VC-12 and VC-3 for SDH links,
VT1.5 for SONET links), while the HO part enables the routing of the high-order
payload (VC-4 for SDH links and STS-1 for SONET links) in the SDH/SONET mode.
Packet Engine
The Packet (Ethernet) Engine is a state-of-the-art, multi-port GbE switching and
aggregating block, which enables hardware-based Ethernet capabilities, such as
traffic management and performance monitoring, between any of the Ethernet
entities.
This Ethernet flow-based traffic can be terminated by any of the following
entities:
Megaplex-4
•
Fast Ethernet and GbE ports located on I/O modules
•
Internal Ethernet ports of I/O modules carrying traffic generated by CPE
devices and transferred over E1, T1, voice, multiplexed fiber or SHDSL circuits
Functional Description
1-41
Chapter 1 Introduction
Installation and Operation Manual
•
Two Gigabit Ethernet ports located on CL.2 modules
•
SDH/SONET ports by using Virtual or Contiguous concatenation (up to 32 VCG
per CL.2) with GFP or LAPS and optional LCAS support.
The Ethernet engine flow classification mechanism is based on port (unaware
mode) or VLAN (aware mode with pop/push or preserve capabilities).
Packet Processor
The GbE packet processor is a high-capacity Ethernet processor with classifier,
capable of handling a wide range of VLAN and port-based flows.
The processor includes GbE and Fast Ethernet ports, which are used as follows:
Note
•
Two external GbE ports, one connected to the GbE 1 interface and the other
to the GbE 2 interface. The two ports can be configured to operate as a
redundancy pair, using hardware-based path and link failure for rapid
switching to the backup link.
•
Fast Ethernet ports are used for Ethernet traffic from I/O modules, one from
each I/O slot.
•
Two GbE ports are internally connected to the Ethernet processor of the
other CL module installed in the Megaplex-4.
•
8 GbE ports on the dedicated M-ETH module, with 1 GbE uplink to the CL.2
modules, supporting VLAN-aware bridging inside the module between all its
ports
•
Each Ethernet port is supported by an independent MAC controller that
performs all the functions required by the IEEE 802.3 protocol. The maximum
frame size supported by the basic Ethernet switch is 9600 bytes. For
maximum frame sizes supported by different I/O modules, see Configuring
User Ethernet Ports in Chapter 6.
•
The frames passed by the MAC controllers are analyzed by the ingress rate
policy controller of the corresponding port before being transferred, through
the switch fabric, to an internal port controller, which controls the frame
egress priorities and inserts them in separate queues. The switch supports up
to four transmission classes (queues) for the Fast Ethernet ports, and up to 8
transmission classes for the GbE ports. The queues are connected to the
ports through port egress policy controllers. This approach provides full
control over traffic flow, and ensures that congestion at one port does not
affect other ports.
In the Megaplex equipped with CL.2/A assembly, the queue mapping functionality
associates the user priorities with queue numbers (CoS) and the marking
functionality maps the user priority to the SP priority, according to
p-bit/DSCP/IP precedence. In the Megaplex with regular CL.2 module, queue
mapping is fixed and based on p-bit.
The available number of queues depends on flow classification and flow editing
(for details, see Chapter 8).
1-42
Functional Description
Megaplex-4
Installation and Operation Manual
•
Chapter 1 Introduction
The processor includes a flow classification engine categorizing packets into
flows in accordance with user-defined classification rules. Classification takes
place at full wire speed. The processor recognizes standard frame types.
In addition to the Ethernet traffic handling subsystem components located on
the CL.2 modules, I/O modules with Ethernet ports (M-ETH, M8E1, M8T1,
M8SL, OP-34C, OP-108C, ASMi-54C, ASMi-54C/N, MPW-1, VS) also include a
local Ethernet handling subsystem. This subsystem includes:
Ethernet port interfaces: provide 10/100/1000 Mbps physical interfaces
for external Ethernet links.
Layer 2 Ethernet switch: provides the local Ethernet VLAN classification.
GbE (M-ETH) or Fast Ethernet data ports
Ethernet termination and processing: provides the interface between the
Layer 2 Ethernet switch and the I/O module specific technology interface.
Note
For M8E1, M8T1, and M8SL modules, this function terminates
Ethernet frames in the direction from the switch to the local
cross-connect matrix and processes them for transmission through
the appropriate bundles, that is, over TDM media. In the inverse
direction, the payload received from TDM media is packetized and
inserted in Ethernet frames for transmission to the appropriate
Ethernet port
For MPW-1 and VS modules, this function provides the interfaces for
pseudowire packet traffic
For the Optimux modules, this function terminates Ethernet frames
over the fiber-optic TDM interface
For the ASMi-54C/N and ASMi-54C modules, this function terminates
the Ethernet frames over SHDSL.
The Ethernet termination and processing function can also serve Ethernet traffic
carried through E1-i/T1-i ports of CL.2 modules.
For a detailed description of I/O module Ethernet traffic handling subsystem,
refer to the Megaplex-4 I/O Modules Installation and Operation Manual.
Carrier Ethernet (CL.2/A Assembly)
In addition to the basic functionality described above, the CL.2/A assembly
provides carrier Ethernet capabilities, such as Ethernet traffic management (TM),
standards-based Ethernet Operations, Administration and Maintenance and
Performance Monitoring (OAM&P), as well as carrier grade Ethernet functionality.
These functionalities are available on any MAC entity, such as the CL module GbE
ports, VCG, Ethernet module (M-ETH)_ports, etc.
Figure 1-25 and Figure 1-26 show the data flow in the device equipped with
CL.2/A for the CL.2 GbE ports and other ports supporting hierarchical scheduling,
respectively. Table 1-5 provides an overview of the traffic handling stages.
Megaplex-4
Functional Description
1-43
Chapter 1 Introduction
Installation and Operation Manual
Figure 1-25. Data Flow in the Megaplex equipped with CL.2/A – CL.2 GbE ports
Figure 1-26. Data Flow in the Megaplex equipped with CL.2/A – other MAC Ports
Table 1-5. Traffic Handling Stages
Processing Stage
Relevant Profiles
Applied to
Description
L2CP processing
L2CP
Port, flow
Defines actions for L2CP processing (discard, peer,
tunnel)
Classification
Classifier
Flow
Classifying traffic such as email traffic, content
streaming, large document transmission, etc.
1-44
Functional Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Processing Stage
Relevant Profiles
Applied to
Description
Policing
Policer
Flow
Policing the traffic within the flow (CIR, CBS, EIR and
EBS parameters)
Mapping of flow
to queue
CoS mapping
Flow
Dividing the services using a 3-bit field, specifying a
priority value between 0 (signifying best-effort) and
7 (signifying highest priority)
Defines method and values for mapping packet
attributes (P-bit, DSCP, IP-Precedence) to internal
CoS Values
Scheduling
(between CoS)
‘Storing’ data that is transmitted according to the
CoS level specified
Scheduling and ‘regulating’ traffic
WRED
Queue
Defines green and yellow packet thresholds and
drop probabilities
Queue
Queue block
Defines queue type with shaper and WRED profile
Queue block
Queue block
within
Defines queue block parameters (queues, scheduling
scheme, weights)
queue group
Shaping
Queue group
Port
Defines level-1, -2 and -3 scheduling elements and
structures within queue group
Shaper
Queue,
queue block
Ensuring that traffic is shaped to the desired rate
(CIR, CBS Parameter)
Scheduling
(between EvC)
(GbE ports only)
‘Storing’ data that is transmitted according to the
CoS level specified
Scheduling and ‘regulating’ traffic
WRED
Queue
Defines green and yellow packet thresholds and
drop probabilities
Queue
Queue block
Defines queue type with shaper and WRED profile
Queue block
Queue block
within
Defines queue block parameters (queues, scheduling
scheme, weights)
queue group
Queue group
Editing and
Marking
Megaplex-4
Marking
Port
Defines level-1, -2 and -3 scheduling elements and
structures within queue group
VLAN Editing
Performing VLAN manipulations, such as push s-tag,
pop, mark, and more, as well as marking the p-bit on
the outer VLAN header (per packet attribute or
internal CoS).
Flow
Adding or removing VLAN IDs, as well as marking the
priority on the outer VLAN header (defines method
of mapping CoS and packet color values into P-bit)
Functional Description
1-45
Chapter 1 Introduction
Installation and Operation Manual
VCAT Engine
The VCAT Engine handles all the functions related to the use of virtual
concatenation, and the preparation of Ethernet traffic for efficient transport over
the SDH/SONET network.
The Ethernet mapper subsystem includes the following functions:
•
LAPS encapsulation
•
GFP encapsulation
•
Virtually concatenated group mapper.
To increase the available number of virtually concatenated groups as Ethernet
transport links, you can configure redundancy for pairs of selected VCGs.
HO/LO Mapper
The HO/LO mapper maps the Ethernet traffic for transmission over the
SDH/SONET network, and creates the virtually concatenated groups (VCGs) that
enable the user to control the utilization of the bandwidth available on the link to
the SDH/SONET network.
The routing of the VCG payload is defined by means of cross-connections, which
means selection of specific VCs/VTs to be used to carry each VCG, in the number
needed to provide the required bandwidth. This operation creates the trails that
are needed to connect the local users to remote locations through the
SDH/SONET network.
Ethernet over SDH/SONET, Full/Channelized T3, E1/T1 General Concept
To describe and map the Ethernet traffic passing over different media (E1/T1,
SDH/SONET, T3 etc), the Megaplex-4 architecture uses a concept of Logical MAC
ports. Logical MAC represents the Ethernet part of the entity. It should be bound
to a gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical
layer.
The meaning of the gfp, hdlc or mlppp ports and their further mapping depends
on the Ethernet traffic media:
•
GFP ports exist on CL.2, VS-16E1T1-EoP and T3 modules and represent VCGs
(Virtual Concatenation Groups) with GFP encapsulation. They can be mapped
either directly to the physical layer or to VCG. In the latter case the binding is
done in two stages and this VCG should be further bound to the physical
layer.
•
HDLC ports exist in two flavors:
1-46
HDLC ports defined on CL.2 modules represent VCGs (Virtual
Concatenation Groups) with LAPS encapsulation. They can be mapped
either directly to the physical layer or to another VCG. In the latter case
the binding is done in two stages and this VCG should be further bound
to the physical layer
Functional Description
Megaplex-4
Installation and Operation Manual
•
Chapter 1 Introduction
HDLC ports defined on M8E1, M8T1 and M8SL modules represent HDLC
bundles which can be bound to the physical layer representing E1/T1
ports or specific timeslots.
MLPPP ports exist only on M8E1 and M8SL modules and are mapped to the
PPP port. The binding is done in two stages and this PPP port should be
further bound to the physical layer.
Ethernet over E1/T1
The Ethernet services supported by M8E1, M8T1 and M8SL modules are
configured by defining flows within the Megaplex-4. The flows are defined by
means of Ethernet virtual connection that interconnects two or more ports
(called Logical MAC ports).
Megaplex-4 uses a special protocol to support the flow of Ethernet traffic. In
M8T1 it is HDLC protocol, in M8E1 and M8SL two types of protocols can be used:
HDLC and MLPPP.
Figure 1-27 shows the relationship between the entities involved in the Ethernet
over E1/T1 functionality.
Logical MAC
1..32
MLPPP
1
HDLC
1..32
XC
Unframed
E1
1
1:
1:n
Bind
1:1
PPP
1..8
Framed
E1/T 1
Figure 1-27. Logical Entities Representing Ethernet Traffic over E1/T1 Media
The maximum number of HDLC ports that can be defined on an M8E1/M8T1/M8SL
module is 32, and together with the three Ethernet ports, an M8E1/M8T1/M8SL
module supports up to 35 ports. Each of these ports can be connected to any
other Ethernet port within the Megaplex-4, for example, to another HDLC or
external Ethernet port on any module (including GbE ports on CL modules), to a
Logical MAC port, etc.
Note
Megaplex-4
It is possible to open only 8 E1-i/T1-i links per module and assign up to 4 HDLC
ports to each of them so that the total capacity is 32 HDLC ports per module.
Moreover, each used E1-i/T1-i link reduces the number of external E1/T1 links
that can be connected to E1/T1 equipment.
Functional Description
1-47
Chapter 1 Introduction
Installation and Operation Manual
In the HDLC Mode, two or more timeslots are cross-connected to the HDLC
entity. The bound HDLC port can be defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1/T1 port. As seen from the diagram, the
timeslot mapping between the framed E1/T1 and HDLC ports should be done via
cross-connect.
The MLPPP protocol is an extension of the PPP protocol that uses the PPP Link
Control Protocol (LCP) and Bridge Control Protocol (BCP) to bind two or more PPP
links to provide increased bandwidth. Each PPP port binds an E1 port. The MLPPP
bundle can be defined only on unframed ports, and its maximum bandwidth is a
multiple of 2048kbps.
The binding of HDLC/MLPPP to flow is done by the intermediate Logical MAC
entity.
Ethernet over SDH/SONET
To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
1. At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
2. The resulting streams are mapped to the desired VCs/SPEs, also configured by
management. The Path Overhead (POH) byte carried by all the group
members is used to transfer to the far endpoint the information needed to
identify:
The relative time difference between arriving members of the virtual
group.
The sequence number of each arriving member.
3. Each member of the virtual group is independently transmitted through the
network. The network need not be aware of the type of payload carried by
the virtual members of the group.
4. At the receiving end, the phase of the incoming VCs/SPEs is aligned and then
the original payload data stream is rebuilt. This requires using a memory of
appropriate size for buffering all the arriving members of the group at the
receiving end. The memory size depends on the maximum expected delay,
therefore to minimize latency the maximum delay to be compensated can be
defined by management.
Figure 1-28 shows the relationship between the entities involved in the Ethernet
over SDH/SONET functionality. Ethernet is mapped to SDH/SONET in the following
steps.
1-48
Functional Description
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
1. Bind VC/VT/STS containers to GFP or HDLC ports. This can be done in two
ways:
Directly 1:1 without using virtual concatenation ( no VCAT)
Using virtual concatenation (VCAT). In this case VC/VT/STS should be first
bound n:1 to a VCG port and then this VCG should be bound to a GFP/
HDLC port.
2. Bind a GFP/HDLC port to a Logical MAC port (1 to 32).
3. Create ingress/egress flows.
Note
The maximum total number of GFP and HDLC ports per CL.2 is 32.
Flow
Egress/Ingress Port
ETH Group
Logical MAC
1
Logical MAC
32
OR
Bind 1:1
HDLC 1..32
GFP 1..32
OR
Bind 1:1
VCG
1..32
Bind 1:1
Bind 1:n
VCAT No
VC4-4C/
STS-12C
VC4/STS-3C
VC3/STS-1
VC12/VT1.5
Figure 1-28. Logical Entities Representing Ethernet Traffic over SDH/SONET Media
Ethernet over Full/Channelized T3
T3 modules allow encapsulating Ethernet traffic with the GFP protocol and
transferring it over full or channelized T3 media. In both cases Ethernet ports are
connected to Logical MAC ports via flows, and these Logical MAC ports are bound
to GFP ports. Starting from the GFP ports, two ways are available:
Megaplex-4
Functional Description
1-49
Chapter 1 Introduction
Installation and Operation Manual
•
To transfer Ethernet over full T3, only one GFP/Logical MAC port is created
and T3 port is bound directly to it.
•
To transfer Ethernet over channelized T3, up to 16 Logical MAC, GFP and VCG
ports are created, so that the VCG ports are bound to GFP ports and VCG
ports are bound to Logical MAC ports. Up to 16 T1 ports can be bound to
each VCG port, but the total T1 number is limited by 28 T1 ports per T3
module. On the remaining T1s, regular TDM traffic can be mapped.
Figure 1-29 shows the relationship between the entities involved in the Ethernet
over T3/T1 functionality.
Flow
Egress/Ingress Port
Logical MAC
1
ETH Group
Logical MAC
16
Bind 1:1
Bind 1:1
GFP 1
GFP 16
OR
Bind 1:1
VCG 1..16
Bind 1:1
Bind 1:n
T1
T3
Figure 1-29. Logical Entities Representing Ethernet Traffic over Full/Channelized T3 Media
Megaplex-4 Architecture Entities
Table 1-6 lists the possible values and hierarchy of different Megaplex-4
architecture entities involved in the Megaplex-4 I/O modules. Each entity is
described in detail in Chapter 6 under the section for corresponding type of
ports: E1, T1, Ethernet, Serial, Logical Mac, Teleprotection etc.
Table 1-6. Megaplex-4 Architecture Entities and their Hierarchy
1-50
Modules
Port Type
Hierarchy
Possible Values
CL.2
sdh-sonet
slot: port
slot/1..2
Functional Description
Megaplex-4
Installation and Operation Manual
Modules
Chapter 1 Introduction
Port Type
Hierarchy
Possible Values
aug
slot: au4
speed 155: slot/1
speed 622: slot/1..4
vc-12
slot:port:au4:tug3:tug2:
tributary
slot/port/au4/tug3/tug2/
1..63
(port = sdh-sonet)
(tributary = vc12)
vc3-sts1
slot:port:au4:tug3
slot/port/au4/tug3/1..3
vt1.5
slot:port:au4:tug3:tug2:
tributary
slot/port/au4/tug3/tug2/
1..84
(port = sdh-sonet)
(tributary = vt1.5)
oc-3
slot: oc-3
speed 155: slot/1
speed 622: slot/1..4
e1-i
slot:port:tributary
slot/port/1..63
(tributary = e1-i)
t1-i
slot:port:tributary
slot/port/1..84
(tributary = t1-i)
ASMi-54C
ASMi-54C/N
D-NFV
hdlc
slot:hdlc
slot/1..32
gfp
slot:gfp
slot/1..32
vcg
slot:vcg
slot/1..32
logical-mac
slot: logical-mac
slot/1..32
ethernet
slot:port
slot/1..2
mngethernet
slot:port
slot/1
station
id
cl-a; cl-b
shdsl
slot:port
slot/1..8
pcs
slot:pcs
slot/1..8
ethernet
slot:port
slot/1..2
shdsl
slot: port
slot/1..8
e1
slot: port
slot/1..8
e1-i
slot: port
slot/1..8
pcs
slot: pcs
slot/1..8
ethernet
slot:port
slot/1..2
int-eth
ethernet
Megaplex-4
slot/1
slot:port
slot/1
Functional Description
1-51
Chapter 1 Introduction
Modules
Port Type
D-NFV/L
int-eth
HSU-6, HSU-12, HS-S
serial
slot:port
slot/1..6, slot/1..12,
slot/1..4
bri
slot: port
(port=d-channel)
slot/1..6, slot/1..12,
slot/1..4
bri
slot:port:tributary
(port=serial,
tributary = b1,b2)
slot/port/1..2
HS-6N, HS-12,
HS-703
serial
slot:port
slot/1..6, slot/1..12,
slot/1..4
HSF-2
serial
slot: port
slot/1..2
LS-6N, LS-12N
serial
slot:port
slot/1..6, slot/1..12
serial-bundle
slot:port
slot/1..2
M-ETH
ethernet
slot:port
slot/1..8
M8E1, M8T1
e1/t1
slot: port
slot/1..8
hdlc
slot: hdlc
slot/1..32
ppp
slot: ppp
slot/1..8
mlppp
slot: mlppp
slot/1
logical-mac
slot: logical-mac
slot/1..32
ethernet
slot: port
slot/1..3
shdsl
slot: port
slot/1..8
e1-i
slot: port
slot/1..8
hdlc
slot: hdlc
slot/1..32
ppp
slot: ppp
slot/1..8
mlppp
slot: mlppp
slot/1
logical-mac
slot: logical-mac
slot/1..32
ethernet
slot:port
slot/1..3
M16E1/M16T1
e1/t1
slot: port
slot/1..16
MPW-1
ds1
slot: port
8
pw
slot: port
128
ethernet
slot: port
3
M8SL
MS-JNPR
OP-108C
1-52
Installation and Operation Manual
Functional Description
Hierarchy
Possible Values
slot/1
int-eth
slot/1
ethernet
slot:port
slot/1
e1
slot:mux eth tdm:port
slot/1/1..1/4, slot/3/1..3/4
Megaplex-4
Installation and Operation Manual
Modules
OP-108C/E1
Chapter 1 Introduction
Port Type
Hierarchy
Possible Values
mux-eth-tdm
slot: port
slot/1..2
ethernet
slot: port
slot/1..2
ethernet
slot: mux_eth_tdm: ethernet
slot/1/1, slot/3/1
e1
slot: port
slot/1..8
mux-eth-tdm
slot: port
slot/1..2
ethernet
slot:port
slot/1..2
int-eth
slot:port:tributary
slot/1/1, slot/3/1
(port = mux_eth_tdm)
(tributary = int-eth)
OP-34C
e1
slot:port:tributary
slot/1/1..16
(port = mux_eth_tdm)
(tributary = e1)
mux-eth-tdm
slot: port
slot/1
ethernet
slot:port
slot/1
int-eth
slot:port:tributary
slot/1/1
(port = mux_eth_tdm)
(tributary = int-eth)
SH-16
shdsl
slot:port
slot /1..slot/16
pcs
slot:port
slot /1..slot/16
shdsl
slot:port
slot /1..slot/16
pcs
slot:port
slot /1..slot/16
e1-i
slot: port
slot /1..slot/16
ds1
slot:port
slot/1.. slot/16
pw
slot:port
slot/1.. slot/128
t3
slot:port
slot/1
t1
slot:port
slot/1/1 .. slot/1/28
logical-mac
slot:port
slot/1 .. slot/16
gfp
slot:port
slot/1 .. slot/16
vcg
slot:port
slot/1 .. slot/16
VC-4/4A/8/8A/16
voice
slot:port
slot/1..4, slot/1..8,
slot/1..16
VC-6/LB
voice
slot:port
1..6
VC-4/OMNI
voice
slot:port
1..4
SH-16/E1
T3
Megaplex-4
Functional Description
1-53
Chapter 1 Introduction
Modules
Installation and Operation Manual
Port Type
Hierarchy
Possible Values
voice
slot:port:tributary
slot/1/1..4/4
(port = voice) (tributary =
internal)
TP (Teleprotection)
VS-12
VS-6/BIN
cmd-in
slot:port
slot/1..4
cmd-in-i
slot:port:tributary
(port = cmd-channel)
(tributary = internal)
slot/1/1..1/4
slot/3/1..3/4
cmd-out
slot:port
slot/1..4, 5..8
cmd-out-i
slot:port:tributary
(port = cmd-channel)
(tributary = internal)
slot/1/1..1/4
slot/3/1..3/4
cmd-channel
slot:port
slot/1..4
ds1
slot:port
slot/1.. slot/8
pw
slot:port
slot/1.. slot/8
serial
slot:port
slot/1… slot/12
tdm-bridge
slot:port
slot/1… slot/4
ethernet
slot:port
slot/1, slot/2
ds1
slot:port
slot/1.. 12
pw
slot:port
slot/1.. 24
serial
slot:port
slot/1… slot/6
tdm-bridge
slot:port
slot/1… slot/6
ethernet
slot:port
slot/1
cmd-in
slot:port:tributary
(port = cmd-channel)
(tributary = internal)
slot /1/1 …… slot /1/4
slot:port:tributary
(port = cmd-channel)
(tributary = internal)
slot /1/1 …… slot /1/4
cmd-channel
slot:port
slot /1, slot /2
ds1
slot:port
slot/1.. 12
pw
slot:port
slot/1.. 24
serial
slot:port
slot/1… slot/6
ethernet
slot:port
slot/1
ds1-opt
slot:port
slot /1, slot/2
ds1
slot:port
slot/1.. 12
pw
slot:port
slot/1.. 24
cmd-out
VS-6/C37
1-54
Functional Description
slot /2/1 …… slot /2/4
slot /2/1 …… slot /2/4
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Modules
Port Type
Hierarchy
Possible Values
VS-6/FXS
serial
slot:port
slot/1… slot/6
tdm-bridge
slot:port
slot/1… slot/6
ethernet
slot:port
slot/1
voice
slot:port
slot/1.. 8
ds1
slot:port
slot/1.. 12
pw
slot:port
slot/1.. 24
serial
slot:port
slot/1… slot/6
tdm-bridge
slot:port
slot/1… slot/6
ethernet
slot:port
slot/1
voice
slot:port
slot/1.. 8
ds1
slot:port
slot/1.. 12
pw
slot:port
slot/1.. 24
serial
slot:port
slot/1..6
tdm-bridge
slot:port
slot/1..6
ethernet
slot:port
slot/1
voice
slot:port
slot/1..4
ds1
slot:port
slot/1..12
pw
slot:port
slot/1..24
voice
slot:port
slot/1..8
ds1
slot:port
slot/1.. 8
pw
slot:port
slot/1..16
voice (FXS)
slot:port
slot/1..8
voice (E&M)
slot:port
slot/9..12
ds1
slot:port
slot/1..8
pw
slot:port
slot/1..16
e1-i/t1-i
slot:port
slot/1..16
e1/t1
slot:port
slot/1..16
vcg
slot:port
slot/1..16
gfp
slot:port
slot/1..16
logical mac
slot:port
slot/1..16
e1/t1
slot:port
slot/1..16
ds1
slot:port
slot/1..16
pw
slot:port
slot/1..128
VS-6/FXO
VS-6/E&M
VS-8/E&M
FXS/E&M
VS-16E1T1-EoP
VS-16E1T1-PW
Megaplex-4
Functional Description
1-55
Chapter 1 Introduction
Installation and Operation Manual
Modules
Port Type
Hierarchy
Possible Values
VS-6/E1T1
serial
slot:port
slot/1..6
ethernet
slot:port
slot/1
e1/t1
slot:port
slot/1..8
ds1
slot:port
slot/1..16
pw
slot:port
slot/1..128
serial
slot:port
slot/1..6
ethernet
slot:port
slot/1
ds0-g703
slot:port
slot/1..8
ds1
slot:port
slot/1..12
pw
slot:port
slot/1..24
VS-6/703
1.5
Note
Technical Specifications
For I/O module technical specifications, refer to the corresponding section in the
Megaplex-4 I/O Modules Installation and Operation Manual.
STM-1/STM-4/
OC-3/OC-12 Ports
Number of Ports
• 2 per CL module
• 4 per chassis
Bit Rate
• STM-1/OC-3:155.52 Mbps ± 4.6 ppm
• STM-4/OC-12: 622.08 Mbps ± 4.6 ppm
Compliance
• SDH: ITU-T G.957, G.783, G.798
• SONET: GR-253-CORE
Line Code
NRZ
Framing
• SDH: ITU-T Rec. G.707, G.708, G.709, G.783
• SONET: ANSI T1.105-1995, GR-253-CORE
Ethernet over SDH/SONET • GFP (Generic Framing Procedure): ITU-T
G.7041, ANSI T1-105.02, framed mode
• LAPS (Links Access Procedure); X.86
• LCAS (Link Capacity Adjustment Scheme):
ITU-T G.7042
1-56
Technical Specifications
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
• 1+1 unidirectional APS (G.842)
Protection
• 1+1 bidirectional APS (G.841, Clause 7.1).
• 1+1 bidirectional optimized APS (G.841 Annex
B. Linear Multiplex Section (MSP); compatible
with 1:1 bidirectional switching)
• Path Protection (Telecordia UPSR standard
and ITU-T SNCP recommendation)
Connectors
SFP-based in accordance with RAD’s SFP/XFP
Transceivers data sheet.
GbE Ports
• 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
Maximum Frame Size
9600 bytes (for max. frame sizes supported by
different I/O modules, see Configuring User
Ethernet Ports in Chapter 6)
Protection
On the same CL module (link protection) or
between CL modules (link and equipment
protection):
• LAG with or without LACP
• ERPS (G.8032v1)
Copper GbE Ports
Optical GbE Ports
Interface Type
10/100/1000BASE-T port, full-duplex, with
autonegotiation
Connectors (per port)
RJ-45, shielded
Interface Type
1000 Mbps full-duplex port
Link Connectors
SFP-based in accordance with Table 1-7
Note: For detailed specifications of SFP transceivers,
see the RAD SFP Transceivers data sheet.
Table 1-7. SFP Connector Modules for GbE Interfaces
Transceiver Wavelength Fiber Type
SFP-5
850 nm
50/125 µm,
Transmitter Connector
Type
VCSEL
Input power
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
LC
(min)
(max)
(min)
(max)
(km)
(miles)
-17
0
-9.5
0
0.55
0.3
multi-mode
Megaplex-4
Technical Specifications
1-57
Chapter 1 Introduction
SFP-6
1310 nm
Installation and Operation Manual
9/125 µm,
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
single mode
SFP-7
1550 nm
9/125 µm,
single mode
SFP-8d
1310 nm
9/125 µm,
single mode
Serial Control Port
(CONTROL DCE)
Interface
RS-232/V.24 (DCE)
Data Rate
9.6, 19.2, 38.4, 57.6, 115.2 kbps asynchronous
Connector
• CL.2: DB-9
• CL.2/4104: MINI-USB
Ethernet
Management Port
(CONTROL ETH)
Interface
10/100BaseT with autonegotiation
Connector
RJ-45
Timing
Clock Sources
• Recovered from the STM-4/STM-1/OC-12/OC3 interface, including automatic selection
based on SSM (Synchronization Status
Messaging)
• Internal crystal free-running oscillator-based
clock
• Derived from the receive clock of a specified
user port
• Adaptive clock recovered (ACR) from a
pseudowire circuit
•
Internal Clock Quality
External station clock
CL.2/622GBEA: ST-3E
CL.2/GBEA: ST-3E
CL.2 ST-3E:
CL.2/DS0: ST-4
Station Clock Interface
Rate:
• 2.048 MHz
• 2.048 Mbps
• 1.544 Mbps
Interface (software-selectable):
• RS-422 squarewave
• ITU-T Rec. G.703, HDB3 coding for 2.048 MHz
and 2.048 Mbps
• ITU-T Rec. G.703, B8ZS coding for 1.544 Mbps
1-58
Technical Specifications
Megaplex-4
Installation and Operation Manual
Diagnostics
Indicators
Chapter 1 Introduction
Connector
RJ-45
Tests
Local and remote loopbacks per link
Alarms
Time and date stamped
Performance Statistics
Ethernet, SDH/SONET, E1/T1, SHDSL, VCG, PCS,
GFP, HDLC and PW ports
Front Panel
POWER SUPPLY A, B
(green)
• On: the corresponding PS module is on (and
one of the CL modules is active)
• Off: Power supply is off
SYSTEM TEST (yellow)
• On: a test (or loopback) is being performed in
the Megaplex-4
• Off: No active tests
SYSTEM ALARM (red)
• Blinking: a major and/or critical alarm has
been detected in Megaplex-4
• On: a minor alarm has been detected in
Megaplex-4
• Off: No active alarms
CL.2 Module
ON LINE (green/yellow)
• On (green): CL module is active or software
decompression
• Blinking slowly (green): CL module is on
standby
• On (yellow): a test is being performed (active
module only)
ALM (red)
• On: alarms have been detected in the
Megaplex-4, but the highest alarm severity is
minor or warning.
• Blinking: a major and/or critical alarm has
been detected in Megaplex-4
• Off: No active alarms
SDH/SONET Ports
Megaplex-4
Technical Specifications
1-59
Chapter 1 Introduction
Installation and Operation Manual
ON LINE (green/yellow)
On (green): the corresponding port is active
(carries SDH/SONET traffic, and there is no major
alarm condition, nor any test on this port)
Blinking (green) – the port is in protection mode
On (yellow): a test is active on the port
Off: no traffic or test on the port
LOS (red)
On: loss-of-signal at the corresponding port
Off: no loss-of-signal
GbE Ports
LINK (green)
On: the port is connected to an active Ethernet
hub or switch
Off: Ethernet link is not detected
ACT (yellow)
On or Blinking (in accordance with the traffic):
ETH frames are received or transmitted
Off: ETH frames are not received and
transmitted
Management Ethernet
Ports
LINK (green)
On: the port is connected to an active Ethernet
hub or switch
Off: Ethernet link is not detected
ACT (yellow)
On or Blinking (in accordance with the traffic):
ETH frames are received or transmitted
Off: ETH frames are not received and
transmitted
Station CLOCK Port
ON (green)
On: the station clock port is configured as no
shutdown
Off: no traffic or test on the port
LOS (red)
On: loss-of-signal (when station clock port
configured as connected)
Off: no loss-of-signal
Alarm Relay Port
Port Functions
• 1 inbound RS-232 alarm input
• 2 outbound (dry contact) relays triggered by
major/minor alarms
1-60
Technical Specifications
Megaplex-4
Installation and Operation Manual
Chapter 1 Introduction
Operation
Normally open, normally closed, using different
pins
Connector
• CL.2: DB-9, female
• CL.2/4104: 9-pin, flat
Power Consumption
Power Supplies
Caution
27.75 W (per CL, max)
See Table 1-8
The DC input is primarily designed for negative input voltage (grounded positive
pole). However, the DC input voltage can be floated with respect to Megaplex-4
ground by means of field-selectable jumpers. Internal jumpers can also be set to
match operational requirements that need either the + (positive) or – (negative)
terminal of the power source to be grounded. Contact your nearest RAD Partner
for detailed information.
Table 1-8. Power Supplies
MP-4100
MP-4104
PS/AC
PS/DC
PS/AC
PS/DC
Operating
Range
115 VAC/230 VAC
(85 to 264 VAC)
-48 VDC
(-36 to -56 VDC)
90 VAC to 260 VAC
-48 VDC (-36 to 56 VDC)
Frequency
50/60Hz
-
50/60Hz
-
HVDC support
100 to 360 VDC
-
110 to 300 VDC
-
Maximum AC
input power
315W + power supplied for ring and feed
voltage purposes
200W + power supplied for ring and feed
voltage purposes
Total output
250W* + power supplied for ring and
feed voltage purposes (drawn directly
from external source)
160W + power supplied for ring and feed
voltage purposes (drawn directly from external
source)
Selectable
ground reference
or floating
ground
-
-
Yes
Yes
* IEEE-1613 “no-fan” compliant system and modules: 175W
Maximum Power Supply Output Currents
Regulated Output Voltage
+3.3V
+5V
-5V
+12V
-12V
PS/4100
30A
40A
6.5A
2A
2A
PS/4104
25A
15A
2.4A
2A
0.8A
Number of Module Slots 14-slot chassis
Megaplex-4
Technical Specifications
1-61
Chapter 1 Introduction
Megaplex-4100
Chassis
Installation and Operation Manual
Slot Usage
• 2 power supply slots
• 2 common logic slots
• 10 identical slots for I/O modules
Megaplex-4104
Chassis
Number of Module Slots 8-slot chassis
Slot Usage
• 2 power supply slots (of different shape)
• 2 common logic slots (can also accommodate a
single dual-slot CL.2 module)
• 4 identical slots for I/O modules
Chassis
Dimensions
Megaplex-4100
Megaplex-4104
Height
18 cm/7 in (4U)
9 cm/3.5 in (2U)
Width
44 cm/17 in
44 cm/17 in
Depth (without handles) 33 cm/13 in (regular
33 cm/13 in
chassis)
37 cm/14.6 in (IEEE-1613compliant chassis)
cm
(1.8
iWeight:
Weight (fully loaded
chassis)
15.3 kg/33.8 lb max.
7.54 kg/16.6 lb max.
CL.2/4100
CL.2/4104
Height
17.3 cm (6.8 in)
17.3 cm (6.8 in)
Width
4.5 cm (1.8 in)
2.5 cm (1 in)
Depth – Regular
32.5 cm (12.8 in)
32.5 cm (12.8 in)
Depth – IEEE-1613compliant
35 cm (13.8 in)
Weight – Regular
630 g (1.3 lb)
Weight – IEEE-1613compliant
2030 g (2.27 lb)
Megaplex-4100
RM-MP-MX-23/19: hardware kit for installing one
Megaplex-4100 in either a 19-inch or 23-inch rack
CL.2 Dimensions
Rack Installation
Kits
540 g (1.2 lb)
MP-2100-RM-ETSI/19: hardware kit for installing one
Megaplex-4100 in a 23-inch ETSI rack (can also be
used for installation in 19-inch rack)
1-62
Technical Specifications
Megaplex-4
Installation and Operation Manual
Megaplex-4104
Chapter 1 Introduction
RM-42: hardware kit for installing one Megaplex-4104
in a 19-inch rack
RM-42-CM: hardware kit for installing one Megaplex4104 in a 19-inch rack with cable management
WM-42: wall-mounting kit for installing Megaplex-4104
WM-42-CM: wall-mounting kit for installing Megaplex4104 with cable management
Note
Environment
Chassis handles installed on the rack mount brackets add 4 cm (1.6 in) to the
total depth.
Operating Temperature
-10°C to 55°C (14°F to 131°F)
Note: For extended operating temperature ranges, and
for “no-fans” Megaplex-4104 chassis temperature
ranges, refer to Ambient Requirements section in
Chapter 2. For additional questions, contact your local
RAD Business Partner.
Note
Megaplex-4
Storage Temperature
-20°C to +70°C (-4°F to +160°F)
Humidity
Up to 95%, non-condensing
Actual operating temperature range is determined by the specific modules
installed in the chassis.
Technical Specifications
1-63
Chapter 1 Introduction
1-64
Technical Specifications
Installation and Operation Manual
Megaplex-4
Chapter 2
Installation
This chapter provides installation instructions for Megaplex-4 devices.
The chapter presents the following information:
•
General description of equipment enclosure and its panels.
•
Mechanical and electrical installation instructions for the enclosure itself and
for system modules, that is, PS and CL modules.
After installing the system, it is necessary to configure it in accordance with the
specific user's requirements:
•
The preliminary system configuration is always performed by means of a
supervision terminal (procedures for using the terminal are given in
Chapter 4). The software necessary for using the terminal is stored in the CL
module: if the CL module is not yet loaded with the required software, refer
to Chapter 12 for detailed software installation instructions.
•
After the preliminary configuration, the system can also be managed by
means of Telnet hosts and/or SNMP-based network management stations,
e.g., RADview. Refer to the User's Manual of the network management
station for operating instructions.
2.1
Safety
Safety Precautions
Warning
Megaplex-4
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.
Safety
2-1
Chapter 2 Installation
Installation and Operation Manual
Megaplex-4 modules contain components sensitive to electrostatic discharge
(ESD). To prevent ESD damage, always hold the module by its sides, and do not
touch the module components or connectors.
Cautions
Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the Megaplex-4 modules. To prevent physical damage:
• Always keep modules in their protective packaging until installed in the
Megaplex-4 chassis, and return them to the packaging as soon as they are
removed from the enclosure.
• Do not stack modules one above the other, and do not lay any objects on
PCBs.
When inserting a module into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the module PCB does not touch
the adjacent module, nor any part of the chassis. If resistance is felt before the
module fully engages the mating backplane connector, retract the module, realign
it with the slot guides and then insert again.
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
Warning
Grounding
Grounding
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the lines connected to the equipment, the Megaplex-4 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-4 and its modules.
Warning
• Never connect cables to Megaplex-4 if not properly installed and grounded.
• Disconnect all the cables connected to the electrical connectors of the
Megaplex-4 before disconnecting its grounding connection.
Before connecting any other cable and before applying power to this equipment,
the protective ground (earth) terminal of the equipment must be connected to
protective ground. Megaplex-4 grounding terminals are located on the Megaplex4 PS module panels.
Whenever Megaplex-4 units are installed in a rack, make sure that the rack is
properly grounded and connected to a reliable, low-resistance grounding system,
because the rack can also provide a connection to ground.
2-2
Safety
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
In addition, the grounding connection is also made through each one of the AC
power cables. Therefore, the AC power cable plug must always be inserted in a
socket outlet provided with a protective ground.
Laser Safety
Warning
Megaplex-4 modules may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near the
optical transmitter. The laser warning symbol may also be attached.
For your safety:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the optical transmitter.
• Do not use broken or unterminated fiber-optic cables/connectors.
• Do not look straight at the laser beam and into the optical connectors while
the unit is operating.
• Do not attempt to adjust the laser drive current.
• The use of optical instruments with this product will increase eye hazard.
Laser power up to 1 mW at 1300 nm and 1550 nm could be collected by an
optical instrument.
• Use of controls or adjustment or performing procedures other than those
specified herein may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
Megaplex-4 modules equipped with laser devices provided by RAD comply with
laser product performance standards set by governmental agencies for Class 1 laser
products. The modules do not emit hazardous light, and the beam is totally enclosed
during all operating modes of customer operation and maintenance.
In some cases, the users may insert their own SFP laser transceivers into
Megaplex-4 modules. Users are alerted that RAD cannot be held responsible for
any damage that may result if non-compliant transceivers are used. In particular,
users are warned to use only agency approved products that comply with the
local laser safety regulations for Class 1 laser products.
Wherever applicable, Megaplex-4 modules are shipped with protective covers
installed on all the optical connectors. Do not remove these covers until you are
ready to connect optical cables to the connectors. Keep the covers for reuse, to
reinstall the cover over the optical connector as soon as the optical cable is
disconnected.
Protection against ESD
Electrostatic discharge occurs between two objects when an object carrying static
electrical charges touches, or is brought near enough, the other object.
Static electrical charges appear as result of friction between surfaces of insulating
materials, separation of two such surfaces, and may also be induced by electrical
fields. Routine activities such as walking across an insulating floor, friction
between garment parts, friction between objects, etc. can easily build charges up
to levels that may cause damage, especially when humidity is low.
Megaplex-4
Safety
2-3
Chapter 2 Installation
Installation and Operation Manual
Caution Megaplex-4 modules contain components sensitive to electrostatic discharge
(ESD). To prevent ESD damage, always hold a module by its sides, and do not
touch the module components or connectors. If you are not using a wrist strap,
before touching a module, it is recommended to discharge the electrostatic
charge of your body by touching the frame of a grounded equipment unit.
Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistance,
yet are not insulators.
2.2
Site Requirements and Prerequisites
AC Power Requirements
AC-powered Megaplex-4 units should be installed within 1.5m (5 feet) of an
easily-accessible grounded AC outlet capable of furnishing 150/230 VAC (nominal),
50/60 Hz.
DC Power Requirements
DC-powered Megaplex-4 units require a -48 VDC (-36 to -57 VDC) power source
(in accordance with the nominal mains voltage of the ordered PS module).
Cautions
• Megaplex-4 PS modules have no power switch and start operating as soon as
power is applied. Therefore, an external power ON/OFF switch is required (for
example, the circuit breaker that protects the power line can also serve as an
ON/OFF switch).
• Internal jumpers on the DC PS modules can be set to match operational
requirements that need either the + (positive) or – (negative) terminal of the
power source to be grounded. The normal factory setting is for a power
source with the +(positive) terminal grounded (the power supply module
jumpers are installed in the BGND=FGND and GND=FGND positions). When it is
necessary to use a power source with the – (negative) terminal grounded, or a
floating power source, the jumpers must be disconnected (set to NO).
Check the position of jumpers in the Megaplex-4 power supply module (see
Figure 2-8 and Figure 2-9) before connecting the DC supply voltage.
Certain I/O modules may still cause BGND to be connected to FGND or GND,
even after setting the jumpers to NO. Refer to the Installation and Operation
Manuals of the modules installed in the chassis for proper setting of their
ground-control jumpers.
2-4
Site Requirements and Prerequisites
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
• If the Megaplex-4 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on the power supply
modules, and check the ground and shield wiring on the cables connected to
the chassis. This may require replacing the cables with cables suitable to your
specific application.
• Megaplex-4 chassis must always be connected to FGND (protective ground).
Special ordering options with preconfigured floating ground settings are available.
Contact your local RAD Partner for more information. When working with FXS
voice modules, see also the VC-4/4A/8/8A/16 section in Appendix B.
Front and Rear Panel Clearance
Allow at least 90 cm (36 inches) of frontal clearance for operator access. Allow
the same clearance at the rear of the unit for interface cable connections and
module replacement.
Ambient Requirements
Megaplex-4100 – Regular Chassis
The Megaplex-4100 I/O modules are cooled by free air convection.
The ambient operating temperature range of Megaplex-4100 is -10 to +55°C (14
to 131°F), at a relative humidity of up to 95%, non-condensing. The storage
temperature is -20°C to +70°C (-4°F to +160°F). Actual operating temperature
range is determined by the specific modules installed in the chassis.
The Megaplex-4100 chassis has no fans and is cooled mainly by free air
convection. Cooling vents are located in the bottom and upper covers. Do not
obstruct these vents. When the chassis is installed in a 19" rack, allow at least 1U
of space below and above the unit.
The PS power supply modules have a miniature cooling fan installed on their front
panels: this fan operates only when the temperature is high.
CL.2 modules also have internal fans.
Megaplex-4100 – IEEE-1613 Compliant Chassis
RAD offers a special Megaplex-4100 IEEE-1613 Compliant chassis. This chassis
includes a heat sink on the front panel and two special fixtures replacing the
vertical walls of the CL module slots to allow more airflow into the CL modules.
These fixtures use I/O 5 and I/O 6 slots, on both sides of CL modules.
To fully comply with IEEE-1613 standard including “No Fans operation”, this
chassis must be ordered with special options of CL and PS system modules.
The I/O modules supported in this chassis are as follows:
Megaplex-4
•
M16E1/M16T1, HSF-2, VS, T3 modules (all flavors)
•
M8E1/M8T1, MPW-1, M-ETH, HS-RN, TP, HS-6N/HS-12N (specific flavors).
Site Requirements and Prerequisites
2-5
Chapter 2 Installation
Installation and Operation Manual
The following modules do not require a special ordering option:
•
VS
•
T3
•
TP/CV/SSR.
The rest of the supported modules require a special ordering option (if needed,
please contact your local RAD Business Partner).
Megaplex-4104
The Megaplex-4104 chassis has 2 cooling fans on its right side. Do not obstruct
these vents. When the chassis is installed in a 19" rack, allow at least 10 cm of
spacing at the sides of the device.
The Megaplex-4104 PS power supply and CL.2 modules do not include fans.
The ambient operating temperature range of Megaplex-4104 is -10 to +55°C (14
to 131°F), at a relative humidity of up to 95%, non-condensing. The storage
temperature is -20°C to +70°C (-4°F to +160°F). Actual operating temperature
range is determined by the specific modules installed in the chassis.
There is a Megaplex-4104 chassis that complies with IEEE-1613 standard
including “No Fans operation”. This chassis option supports a pre-defined
configuration, including card slot assignment (see Table 2-1). If a different
configuration is required, please contact your local RAD Business Partner.
Table 2-1. Operating Temperature Ranges for Megaplex-4104 IEEE-1613
Compliant Configurations
1
Configuration
Operating Temperature
Range
CL.A: MP-4104M-CL.2/DS0
-20°C – 55°C
CL.B: MP-4104M-CL.2/DS0
IO-1: HSF-2
IO-2: M16E1
IO-3: HS-RN
IO-4: HS-12
PS-A: MP-4104M-PS/48
PS-B: MP-4104M-PS/48
Make sure to insert a right module to the right slot; double-check the slot labels
in accordance with the diagram below.
2-6
Site Requirements and Prerequisites
CL-B
CL-A
I/O 1
I/O 2
I/O 3
I/O 4
PS-B
I/O 2
RAD
I/O 3
PS-B
PS-A
I/O 4
PS-A
MEGAPLEX-4104
CL-B
CL-A
I/O 1
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Electromagnetic Compatibility Considerations
The Megaplex-4 is designed to comply with the electromagnetic compatibility
(EMC) requirements of Sub-Part J of FCC Rules, Part 15, for Class A electronic
equipment, and additional applicable standards such as EN55022 and EN55024.
Megaplex-4 also complies with all the requirements of the CE mark.
To meet these standards, it is necessary to perform the following actions:
Note
•
Connect the Megaplex-4 case to a low-resistance grounding system.
•
Install blank panels to cover all empty slots. Appropriate blank panels can be
ordered from RAD.
•
Whenever possible, use shielded telecommunication cables. In particular, it is
recommended to use a shielded RS-232 to connect to the CL module serial
control port.
The serial control port is normally used only during preliminary configuration, and
for maintenance purposes. If you cannot obtain a shielded control cable, connect
the cable only for the minimum time required for performing the task.
•
In certain cases, the use of shielded cables or twisted pairs, or use of ferrite
cores, is recommended. Refer to the individual module Installation and
Operation Manual for details.
Covering all empty slots is also required for reasons of personal safety.
Warning
Optical Cable Requirements
The cables connected to Megaplex-4 optical ports should use 2-mm optical fibers
terminated in the corresponding type of connectors. When routing fibers, make
sure to observe the minimum bending radius (35 mm). RAD recommends
installing plastic supports on each cable connector: these supports determine the
fiber bending radius at the connector entry point and also prevent stress at this
point.
2.3
Package Contents
Megaplex-4100 Package Contents
The Megaplex-4100 package (P/N beginning with MP-4100-2) includes the
following items:
Megaplex-4
•
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)
Package Contents
2-7
Chapter 2 Installation
Installation and Operation Manual
•
Supervision terminal cable, CBL-DB9F-DB9M-STR
•
Open-ended alarm cable, CBL-MP-4100/AR/OPEN/2M
•
Rack installation kit in accordance with order:
RM-MP-MX-23/19: hardware kit for installing one Megaplex-4100 in either
a 19-inch or 23-inch rack
MP-2100-RM-ETSI/19: hardware kit for installing one Megaplex-4100 in a
23-inch ETSI rack (can also be used for installation in 19-inch rack)
•
Air buffer for installation of the Megaplex-4100 IEEE-1613 chassis (if
ordered)
•
Manual download form.
I/O modules are shipped either separately, or preinstalled in the chassis, in
accordance with your order.
Megaplex-4104 Package Contents
The Megaplex-4104 package (P/N beginning with MP-4104-2) includes the
following items:
•
Megaplex-4104 chassis, including CL and PS modules in accordance with order
•
Power cables in accordance with order, and a DC plug for the DC power cable
•
Supervision terminal cable, CBL-MUSB-DB9F
•
Open-ended alarm cable, CBL-MP-4104/AR/OPEN/2M
•
Rack installation kit in accordance with order:
•
RM-42: hardware kit for installing one Megaplex-4104 in a 19-inch rack
(supplied with the device)
RM-42-CM: hardware kit for installing one Megaplex-4104 in a 19-inch
rack with cable management
WM-42: wall-mounting kit for installing Megaplex-4104
WM-42-CM: wall-mounting kit for installing Megaplex-4104 with cable
management
Manual download form.
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-4 device depend
on the Megaplex-4 application.
You can use standard cables or prepare the appropriate cables yourself in
accordance with the information given in Appendix A, and in the Installation and
Operation Manuals of the installed modules.
2-8
Required Equipment
Megaplex-4
Installation and Operation Manual
2.5
Chapter 2 Installation
Mounting the Products
This section presents instructions for installing Megaplex-4 units. To help you
familiarize with the equipment, it also presents a physical description of the
Megaplex-4 versions.
Do not connect any cables to the Megaplex-4 before it is installed in the
designated position.
Warning
Installing the Regular Megaplex-4100 Chassis
Megaplex-4100 is intended for installation on shelves and racks. Do not connect
power to the enclosure before it is installed in the designated position.
Installing in a 19” Rack
For rack installation, it is necessary to install two brackets to the sides of the
unit. As illustrated in Figure 2-1, you may install the brackets in two ways, to
orient the unit in accordance with your requirements (either with the
Megaplex-4100 front panel toward the front of the rack, or the module panels
toward the front).
Install Brackets Here if
You Want the Front Panel
toward the Front of the Rack
Figure 2-1. Attachment of Brackets to Megaplex-4100 Case for Installing in 19” Rack
Megaplex-4
Mounting the Products
2-9
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-2 shows how to attach the brackets for installation in 23”
racks (only front installation is shown in this figure).
Figure 2-2. Attachment of Brackets for Installation of Megaplex-4100 Unit in 23” Rack
After attaching the brackets, fasten the enclosure to the rack by four screws
(two on each side).
After installing the enclosure, check and install the required modules, in
accordance with the installation plan.
Installing the IEEE-1613 Compliant Megaplex-4100 Chassis in a 19”
Rack
For installation of a single IEEE-1613 Compliant Megaplex-4100 Chassis in a 19”
rack, see the previous section.
If you need to install two chassis one above the other, you need a special
separating tray (thermal isolation panel) RM-51. You may install the brackets in
two ways, to orient the units 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). These cases are shown in the figure below. Pay
attention to the position of the tray in both cases:
2-10
•
When the front panel is accessed from the front of the rack, the tray is
installed with the bottom up
•
When the module panels are accessed from the front of the rack, the tray is
installed with the bottom up.
Mounting the Products
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Figure 2-3. Installing Two Megaplex-4100 IEEE-1613 Compliant Chassis in 19” Rack:
Accessing Megaplex Front Panel from the Front of the Rack
Megaplex-4
Mounting the Products
2-11
Chapter 2 Installation
Installation and Operation Manual
Figure 2-4. Installing Two Megaplex-4100 IEEE-1613 Compliant Chassis in 19” Rack:
Accessing Module Panels from the Front of the Rack
Installing the Megaplex-4104 Chassis
Megaplex-4104 can be installed on shelves, racks and mounted on the wall. Do
not connect power to the enclosure before it is installed in the designated
position.
For rack and wall-mount installation, refer to the leaflets supplied with RM-42,
RM-42-CM, WM-42 and WM-42-CM rack-mount and wall-mount kits.
2.6
Installing Modules
Installing PS Modules
Warning
High
Voltage
2-12
Dangerous voltages are present inside the PS module when it is connected to
power. Do not connect the PS module to power before it is properly installed
within the Megaplex-4 enclosure. Always disconnect the input power from the PS
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.
Installing Modules
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Megaplex-4100 Module Panels
The following PS versions are offered for Megaplex-4100:
•
DC-powered modules, PS/48: 250W modules, operating on -48 VDC (nominal)
•
AC-powered module, PS/AC: 250W module, operates on 115 VAC or 230 VAC,
50/60Hz (nominal voltage is marked on the module panel) and includes HVDC
support of 100 to 360 VDC.
•
IEEE-1613 compliant DC-powered modules, PS/48/H1: 175W modules,
operating on -48 VDC (nominal)
•
IEEE-1613 compliant AC-powered module, PS/AC/H1: 175W module, operates
on 115 VAC or 230 VAC, 50/60Hz (nominal voltage is marked on the module
panel) and includes HVDC support of 100 to 360 VDC.
Typical PS panels are shown in Figure 2-5. PS modules do not include a power
on/off switch and start operating as soon as power is applied. It is recommended
to use an external power on/off switch, for example, the circuit breaker used to
protect the supply line to the Megaplex-4100 may also serve as the on/off
switch.
AC-Powered Module
-48 VDC-Powered Module
Figure 2-5. Typical Megaplex-4100 PS Module Panels
Megaplex-4
Installing Modules
2-13
Chapter 2 Installation
Installation and Operation Manual
AC-Powered Module, IEEE-1613
Compliant
DC-Powered Module, IEEE-1613
Compliant
Figure 2-6. Typical Megaplex-4100 PS Module Panels
The PS modules connect to an external feed and ring voltage source, e.g., a
Ringer-2200N standalone unit offered by RAD:
•
The AC-powered PS versions have a separate connector, designated VDC-IN,
for the external -48 VDC and +72 VDC voltages.
•
The connection of the +72 VDC voltage to the DC-powered PS versions is
made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
The regular PS modules have a miniature cooling fan on the front panel. Make
sure to keep the fan opening free of obstructions.
Megaplex-4104 Module Panels
The following PS versions are offered for Megaplex-4104:
•
DC-powered modules, PS/48: 160W modules, operating on -48 VDC (-36 to
-56 VDC)
•
AC-powered module, PS/AC: 160W module, operates on 100 VAC to 260 VAC,
50/60Hz (including HVDC support of 110 to 300 VDC)
Typical PS panels are shown in Figure 2-7. PS modules do not include a power
on/off switch and start operating as soon as power is applied. It is recommended
to use an external power on/off switch, for example, the circuit breaker used to
protect the supply line to the Megaplex-4104 may also serve as the on/off
switch.
2-14
Installing Modules
Megaplex-4
Installation and Operation Manual
AC-Powered Module
Chapter 2 Installation
DC-Powered Module
Figure 2-7. Typical Megaplex-4104 PS Module Panels
The PS modules connect to an external feed and ring voltage source, e.g., a
Ringer-2200N standalone unit offered by RAD:
•
The AC-powered PS versions have a separate connector, designated VDC-IN,
for the external -48 VDC and +72 VDC voltages.
•
The connection of the +72 VDC voltage to the DC-powered PS versions is
made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
The PS modules connect to an external feed and ring voltage source, e.g., a
Ringer-2200N standalone unit offered by RAD. The connection of the +72 VDC
voltage to the DC-powered PS is made through the VDC-IN input connector. The
DC feed voltage is derived from the DC input voltage, and therefore has the same
voltage and polarity.
Megaplex-4100 Internal Jumpers
The PS modules include two internal jumpers that control the connection of
frame ground to the internal ground lines.
Caution
If the Megaplex-4100 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local RAD Partner for more information.
The jumpers of a typical PS module (PS/DC or PS/AC) are identified in Figure 2-8.
Megaplex-4
Installing Modules
2-15
Chapter 2 Installation
Installation and Operation Manual
Front Panel
BGND = FGND
YES
NO
48 VDC Positive Line
Connected to Frame
Ground
48 VDC Positive Line
not Connected
to Fram e Ground
GND = FGND
YES
NO
NO YES NO YES
Signal Ground
Connected to
Frame Ground
Signal Ground
not Connected to
Frame Ground
Figure 2-8. Typical Megaplex-4100 PS Module (Lateral View), Location of Internal Jumpers
Note
•
The jumper designated GND=FGND controls the connection between the
internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
•
The jumper designated BGND=FGND controls the connection between the
positive (+) line of the external 48 VDC voltage and the frame (enclosure)
ground. The module is normally delivered with the jumper set to YES. If
necessary, you can set the jumper to NO to float the external 48 VDC positive
line with respect to the frame ground. This is usually necessary when the DC
voltage is used to feed or ring voltages.
PS/DC and PS/AC modules can also use a positive supply voltage. In this case,
always disconnect BGND from FGND (set the jumper to NO).
If two power supply modules are installed, make sure that the internal
jumpers are set to the same position on both modules.
Caution Certain I/O modules may still cause BGND to be connected to FGND or GND, even
after setting the jumpers to NO. Refer to the appropriate sections of Appendix B
describing the modules installed in the chassis for proper setting of their groundcontrol jumpers.
Megaplex-4104 Internal Jumpers
Megaplex-4104 PS modules include two sets of internal jumpers that control the
connection of frame ground to the internal ground lines.
2-16
Installing Modules
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Caution If the Megaplex-4104 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local RAD Partner for more information.
The jumpers of a typical PS module (PS/DC) are identified in Figure 2-9.
Front Panel
YES
NO
YES NO
YES
NO
GND = FGND
BGND = FGND
Signal Ground
Connected to
Frame Ground
48 VDC Positive Line
Connected to Frame
Ground
Signal Ground
not Connected to
Frame Ground
YES
NO
48 VDC Positive Line
not Connected
to Frame Ground
Figure 2-9. Typical Megaplex-4104 PS Module (Top View), Location of Internal Jumpers
Note
•
The jumper designated GND=FGND controls the connection between the
internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
•
The jumper designated BGND=FGND controls the connection between the
positive (+) line of the external 48 VDC voltage and the frame (enclosure)
ground. The module is normally delivered with the jumper set to YES. If
necessary, you can set the jumper to NO to float the external 48 VDC positive
line with respect to the frame ground. This is usually necessary when the DC
voltage is used to feed or ring voltages.
PS/DC and PS/AC modules can also use a positive supply voltage. In this case,
always disconnect BGND from FGND (set the jumper to NO).
If two power supply modules are installed, make sure that the internal
jumpers are set to the same position on both modules.
Caution Certain I/O modules may still cause BGND to be connected to FGND or GND, even
after setting the jumpers to NO. Refer to the appropriate sections of Appendix B
describing the modules installed in the chassis for proper setting of their
ground-control jumpers.
Megaplex-4
Installing Modules
2-17
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-4 chassis. Disconnect the cable(s) from the
module before it is removed from the chassis.
1. Insert the PS module in the PS-A slot, and fasten it with the two screws.
2. Connect the power cable according to the voltages indicated on the panel.
3. If an additional redundant module is used, install it in the PS-B slot.
Note
You can install a redundant module in an operating enclosure without turning the
Megaplex-4 power off. In this case:
• First insert the module in its slot
• Connect its power cable.
Removing a PS Module
1. Disconnect the power cable(s) connected to the module.
2. Release the two module screws
3. Pull the PS module out.
Installing CL Modules
Megaplex-4100 accommodates two dual-slot CL.2 modules. A special compact
single-slot CL.2 module version is available, allowing the use of two CL.2 modules
in the Megaplex-4104 chassis. Megaplex-4104 can also use the regular dual-slot
module (one per chassis).
The modules include the chassis management and timing subsystem, and a
cross-connect matrix for TDM traffic, two SDH/SONET ports (with STM-1/OC-3 or
STM-4/OC-12 interfaces, in accordance with order) and two GbE ports (with SFPs
or with copper interfaces, in accordance with order). The panels for the
STM-1/OC-3 or STM-4/OC-12 versions are identical. A special version without
SDH/SONET and GbE ports can be used for DS0 cross-connect services only.
Megaplex-4100 Module Panels
The Megaplex-4100 chassis can be equipped with two CL modules. At any time,
only one module is active, and the other serves as hot standby.
The figures below show the following versions of CL.2 module panels:
2-18
•
CL.2
•
CL.2/A, regular
•
CL.2/AP, regular
•
CL.2/A, IEEE-1613-compliant
•
CL.2/AP, IEEE-1613-compliant
Installing Modules
Megaplex-4
Installation and Operation Manual
•
Chapter 2 Installation
CL.2/DS0 only, IEEE-1613-compliant.
Table 2-2 describes the functions of the panel switches. For description of LED
indicators, see Chapter 3.
CL.2
CL.2
LASER
CLASS
1
CL.2
LASER
CLASS
1
ON LINE
ON LINE
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
1
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
G
b
E
G
b
E
LINK
ALM
ON
LINE
ACT
1
2
C
O
N D
T C
R E
O
L
LINK
ACT
ON LINE
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
E
T
H
C
L
O
C
K
A
L
A
R
M
ON/LOS
CL.2 with Copper
GbE Interfaces
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2 with Optical
GbE Interfaces
C
O
N D
T C
R E
O
L
ACT
LINK
A
L
A
R
M
E
T
H
C
L
O
C
K
ON/LOS
CL.2 for DS0 Crossconnect only
Figure 2-10. CL.2 Module Panels
Megaplex-4
Installing Modules
2-19
Chapter 2 Installation
Installation and Operation Manual
CL.2
A
CL.2
A
LASER
CLASS
1
LASER
CLASS
1
ON LINE
ON LINE
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
1
2
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
A
L
A
R
M
G
b
E
G
b
E
LINK
E
T
H
C
L
O
C
K
A
L
A
R
M
ON/LOS
CL.2/A with Copper
GbE Interfaces
ON
LINE
ACT
ON LINE
ALM
ALM
1
2
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2/A with Optical
GbE Interfaces
ACT
ACT
1
2
C
O
N D
T C
R E
O
L
LINK
ACT
ON LINE
ALM
LOS
ACT
C
O
N D
T C
R E
O
L
CL.2
A
CL.2
A
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
G
b
E
G
b
E
E
T
H
C
L
O
C
K
ON/LOS
CL.2/A (GbE only) with
Copper GbE Interfaces
1
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2/A (GbE only) with
Optical GbE Interfaces
Figure 2-11. CL.2/A Module Panels
2-20
Installing Modules
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
CL.2
AP
CL.2
AP
LASER
CLASS
1
CL.2
AP
LASER
CLASS
1
ON LINE
ALM
ON LINE
LOS
S
D
H 1
/
S
O
N
E 2
T
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
1
A
L
A
R
M
G
b
E
G
b
E
2
ON LINE
ALM
ON
LINE
ACT
ACT
E
T
H
LINK
C
L
O
C
K
ON/LOS
CL.2/AP with
Copper GbE
Interfaces
ON LINE
ALM
C
O
N D
T C
R E
O
L
1
A
L
A
R
M
2
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2/AP with Optical
GbE Interfaces
ACT
ACT
1
2
LINK
ALM
LOS
ACT
C
O
N D
T C
R E
O
L
CL.2
AP
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
G
b
E
G
b
E
E
T
H
C
L
O
C
K
ON/LOS
CL.2/AP (GbE only) with
Copper GbE Interfaces
1
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2/AP (GbE only)
with Optical GbE
Interfaces
Figure 2-12. CL.2/AP Module Panels
Megaplex-4
Installing Modules
2-21
Chapter 2 Installation
CL.2/A with Copper
GbE Interfaces
Installation and Operation Manual
CL.2/A with Optical
GbE Interfaces
CL.2/A (GbE only) with
Copper GbE Interfaces
CL.2/A (GbE only) with
Optical GbE Interfaces
Figure 2-13. CL.2/A/1613 Module Panels
2-22
Installing Modules
Megaplex-4
Installation and Operation Manual
CL.2/AP with Copper
GbE Interfaces
CL.2/AP with Optical
GbE Interfaces
Chapter 2 Installation
CL.2/AP (GbE only) with
Copper GbE Interfaces
CL.2/AP (GbE only) with
Optical GbE Interfaces
Figure 2-14. CL.2/AP/1613 Module Panels
Megaplex-4
Installing Modules
2-23
Chapter 2 Installation
Installation and Operation Manual
Figure 2-15. CL.2/DS0/1613 Module Panel
Table 2-2. Module CL.2 for Megaplex-4100, Panel Components
Item
Function
CLOCK Connector
RJ-45 connector for the station clock input and output signals
CONTROL ETH Connector
RJ-45 connector for the 10/100BaseT Ethernet management port
CONTROL DCE Connector
9-pin D-type female connector with RS-232 DCE interface, for connection to
system management. Connector pin allocation is given in Appendix A
ALARM Connector
9-pin D-type female connector, for connection to the Megaplex-4100 alarm
relay outputs, and an external alarm input. Connector pin allocation is given in
Appendix A
SDH/SONET 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding SDH/SONET ports
GbE 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors
Megaplex-4104 Module Panels
A special compact single-slot CL.2 module allows the use of two CL.2 modules in
the Megaplex-4104 chassis. At any time, only one module is active, and the other
serves as hot standby.
Megaplex-4104 can also use the regular dual-slot module (one per chassis).
The figures below show the following versions of CL.2 module panels:
2-24
•
CL.2
•
CL.2/A
Installing Modules
Megaplex-4
Installation and Operation Manual
•
Chapter 2 Installation
CL.2/AP.
Table 2-3 describes the functions of the panel switches. For description of LED
indicators, see Chapter 3.
CL.2
CL.2
LASER
CLASS
1
LASER
CLASS
1
ON LINE
ALM
ON LINE
LOS
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
G
b
E
G
b
E
2
ON LINE
ALM
ON
LINE
ACT
1
2
LINK
C
O
N
T
R
O
L
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
ACT
1
CL.2
ACT
C
O
N
T
R
O
L
E
T
H
LINK
D
C
E
A
L
A
R
M
C
L
O
C
K
ACT
E
T
H
LINK
D
C
E
A
L
A
R
M
ON/LOS
CL.2 with Copper
GbE Interfaces
LINK
C
L
O
C
K
ON/LOS
CL.2 with Optical
GbE Interfaces
C
O
N
T
R
O
L
ACT
E
T
H
LINK
D
C
E
A
L
A
R
M
C
L
O
C
K
ON/LOS
CL.2 for DS0 Crossconnect only
Figure 2-16. CL.2/4104 Module Panels
Megaplex-4
Installing Modules
2-25
Chapter 2 Installation
Installation and Operation Manual
CL.2
A
CL.2
A
LASER
CLASS
1
LASER
CLASS
1
ALM
ON LINE
ON LINE
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
1
ON
LINE
ACT
ACT
C
O
N
T
R
O
L
E
T
H
LINK
A
L
A
R
M
C
L
O
C
K
ACT
2
LINK
E
T
H
LINK
D
C
E
A
L
A
R
M
ON/LOS
CL.2/A with Copper
GbE Interfaces
ALM
ACT
1
2
D
C
E
ON LINE
ACT
1
LINK
C
O
N
T
R
O
L
ALM
ON LINE
CL.2
A
G
b
E
G
b
E
2
ALM
LOS
LOS
S
D
H 1
/
S
O
N
E 2
T
CL.2
A
CL.2
A
C
L
O
C
K
ON/LOS
CL.2/A with Optical
GbE Interfaces
G
b
E
G
b
E
1
2
LINK
C
O
N
T
R
O
L
ACT
E
T
H
LINK
D
C
E
A
L
A
R
M
C
L
O
C
K
ON/LOS
CL.2/A (GbE only) with
Copper GbE Interfaces
C
O
N
T
R
O
L
ACT
LINK
E
T
H
LINK
D
C
E
A
L
A
R
M
C
L
O
C
K
ON/LOS
CL.2/A (GbE only) with
Optical GbE Interfaces
Figure 2-17. CL.2/A/4104 Module Panels
2-26
Installing Modules
Megaplex-4
Installation and Operation Manual
LASER
CLASS
1
LASER
CLASS
1
ACT
1
2
Chapter 2 Installation
ACT
1
G
b
E
2
LINK
G
b
E
LINK
CL.2/AP with
Copper GbE
Interfaces
CL.2/AP with Optical
GbE Interfaces
CL.2/AP (GbE only) with
Copper GbE Interfaces
CL.2/AP (GbE only)
with Optical GbE
Interfaces
Figure 2-18. CL.2/AP/4104 Module Panels
Table 2-3. Module CL.2 for Megaplex-4104, Panel Components
Item
Function
CLOCK Connector
RJ-45 connector for the station clock input and output signals
CONTROL ETH Connector
RJ-45 connector for the 10/100BaseT Ethernet management port
CONTROL DCE Connector
MINI-USB connector, for connection to system management. Connector pin
allocation is given in Appendix A
ALARM Connector
9-pin flat connector, for connection to the Megaplex-4104 alarm relay outputs,
and an external alarm input. Connector pin allocation is given in Appendix A
SDH/SONET 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding SDH/SONET ports
GbE 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors
Installing and Replacing SFPs
Before installing a CLmodule, you may have to install the prescribed types of SFPs .
Megaplex-4
Installing Modules
2-27
Chapter 2 Installation
Installation and Operation Manual
Installing an SFP
When installing an optical SFP in an operating module, be aware that it may
immediately start generating laser radiation.
Warning
Caution
During the installation of an SFP with optical interfaces, make sure that all optical
connectors are closed by protective caps.
Do not remove the covers until you are ready to connect optical fibers to the
connectors. Be aware that when inserting an SFP into a working module, the SFP
transmitter may start transmitting as soon as it is inserted.
Note
All the following procedures are illustrated for typical SFPs with optical interfaces.
However, the same procedures apply for SFPs with electrical (copper) interfaces.
Third-party SFP optical transceivers must be agency-approved, complying with the
local laser safety regulations for Class 1 laser equipment.
Warning
To install the SFP module:
1. Lock the wire latch of the SFP module by lifting it up until it clicks into place,
as illustrated in Figure 2-19.
Note
Some SFP models have a plastic door instead of a wire latch.
Figure 2-19. Locking the Wire latch of a Typical SFP
2. Carefully remove the dust covers from the corresponding SFP socket of the CL
module, and from the SFP electrical connector.
3. Orient the SFP as shown in Figure 2-19, and then insert the rear end of the
SFP into the module socket.
4. Push SFP slowly backwards to mate the connectors, until the SFP clicks into
place. If you feel resistance before the connectors are fully mated, retract the
SFP using the wire latch as a pulling handle, and then repeat the procedure.
5. If necessary, repeat the procedure for the other SFP.
2-28
Installing Modules
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Caution Insert the SFP gently. Using force can damage the connecting pins.
6. Remove the protective rubber caps from the SFP modules.
To remove the SFP module:
Disconnect the fiber optic cables from the SFP module.
1. Unlock the wire latch by lowering it downwards (as opposed to locking).
2. Hold the wire latch and pull the SFP module out of the port.
Caution Do not remove the SFP while the fiber optic cables are still connected. This may
result in physical damage (such as a chipped SFP module clip or socket) or cause
malfunction (e.g., the network port redundancy switching may be interrupted).
Replacing an SFP
SFPs can be hot-swapped. It is always recommended to coordinate SFP
replacement with the system administrator. During the replacement of SFPs with
optical interfaces, only the traffic on the affected link is disrupted (the other link
can continue to carry traffic).
To replace an SFP:
1. If necessary, disconnect any cables connected to the SFP connectors.
2. Push down the SFP locking wire, and then pull the SFP out.
3. Reinstall protective covers on the SFP electrical and optical connectors.
4. Install the replacement SFP in accordance with the Installing an SFP section.
Installing a CL Module
CL modules are installed in the CLX-A and/or CLX-B slots. When two CL modules
are installed, redundancy is available. In this case, the module installed in slot
CLX-A will be automatically selected as the master module, provided that it
operates normally and stores all the required configuration parameters.
To install a CL module:
1. Check that the two fastening screws of the module are free to move.
2. Insert the CL module in its chassis slot and slide it backward as far as it goes.
3. Simultaneously press the extractor handles toward the center of the module
to fully insert its rear connector into the mating connector on the backplane.
4. Secure the CL module by tightening its two screws.
To interconnect the expansion ports of CL modules:
•
Megaplex-4
Connect the expansion cable between the EX LINK connectors of the two
modules.
Installing Modules
2-29
Chapter 2 Installation
Installation and Operation Manual
Removing a CL Module
To remove a CL module:
1. Fully release the two screws fastening the module to the chassis.
2. Simultaneously push the extractor handles outward, to disengage the rear
connector.
3. Pull the module out.
Replacing a CL Module during Equipment Operation –
Megaplex-4 Chassis with two CL Modules
In a Megaplex-4 equipped with two functional CL modules, the standby module
can be removed/replaced with minimal disruption of Megaplex-4 services: when
you replace the on-line CL module, Megaplex-4 will automatically switch to the
standby module, provided that module is operational.
The expected disruptions can be minimized in the following ways:
•
An active CL module also provides routing services and clock signals to other
Megaplex-4 subsystems, as well as an out-of-band connection to
management. Simply removing the active CL module will therefore cause a
disruption, however short, in all the services provided by the Megaplex-4
chassis. It is therefore important to prevent this type of disruption, and this
can be achieved by first switching (flipping) to the standby CL module before
replacing the on-line CL module.
•
Removing a module always disconnects the traffic carried by the active
payload interfaces (GbE and/or SDH/SONET) located on the replaced module.
Note that these traffic interfaces can be active even on the standby CL
module, and therefore the only way to avoid traffic disconnections is to use
automatic protection for these interfaces: for example, APS can be used to
protect SDH/SONET traffic, and LAG protection can be used to protect
Ethernet traffic.
You can identify the active and standby modules by their ON LINE indicators.
Caution
To prevent service disruption, check that the ON LINE indicator of the CL module
you want to remove is flashing. If not, use the supervisory terminal (or any other
management facility) to reset the module to be replaced, and wait for execution
of this command before continuing: this will cause the Megaplex-4 to flip to the
other CL module within 50 msec.
To flip to the other CL module using the supervision terminal:
1. Identify the on-line CL module: this is the module with the lit ON LINE
indicator.
2. Whenever possible, connect the supervision terminal directly to the CONTROL
DCE connector of the on-line CL module, and log in as administrator.
3. At the mp4100>admin# prompt, type reboot active to send a reset command
to the module to be replaced.
2-30
Installing Modules
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
4. Wait for the flipping to be executed. After it is executed, the ON LINE
indicator of the CL module the supervision terminal is connected to starts
flashing, while that of the other module stops flashing and lights steadily.
5. You can now disconnect the supervision terminal, and remove the module.
6. When installing a CL module in the slot of the removed module, you may
cause flipping to the original module by resetting the current on-line CL
module.
Replacing a CL Module during Equipment Operation –
Megaplex-4 Chassis with Single CL Module
In a Megaplex-4 equipped with a single CL module, before replacing the CL
module it is recommended that a functional CL module of the same type be
installed in the free CL slot. The replacement can be temporary.
After inserting the additional CL module, it is necessary to let it update its
database from the information provided by the existing CL module:
1. If necessary, program the additional module in the Megaplex-4 database.
2. Enter commit to update the databases, and then wait until the CL DB
CHECKSUM IS DIFFERENT alarm is off.
3. At this stage, continue in accordance with the steps listed above for a
Megaplex-4 with two CL modules.
If the only CL module in the chassis is replaced, Megaplex-4 services will always
be disrupted to some extent while no CL module is present. Therefore, be
prepared and perform the replacement as rapidly as possible.
Among other steps, make sure to upload the existing configuration database to a
host, using TFTP. After replacement is completed, download the database to the
new CL module, to continue normal operation in accordance with the previous
configuration.
Adding a Protection CL Module to a Working Module
Configured as SONET
When the working CL module is configured as SONET, inserting a new CL module
for protection requires the following configuration steps:
1. Retrieve the “startup-config” file.
2. Add the protection CL to the retrieved “startup-config” script (if the working
module is CL-A, add the following string: “configure slot cl-b card-type
cl2-622gbe…” etc.)
3. Copy the new script to the database.
4. Save the changes.
5. Insert the module into the chassis.
6. Reboot the device.
Megaplex-4
Installing Modules
2-31
Chapter 2 Installation
Installation and Operation Manual
Installing System Modules in Megaplex-4104 Chassis
Refer to the above sections for MP-4100. The only difference is that the power
supply has a different shape.
Caution
To prevent physical damage to the electronic components assembled on the two
sides of the module printed circuit boards (PCB) while it is inserted into its
chassis slot, support the module while sliding it into position and make sure that
its components do not touch the chassis structure, nor other modules.
This precaution is particularly important when installing modules into the two
lower I/O slots (1 and 4) of the Megaplex-4104 chassis: take special care to
support the module from below, while pushing it in gently.
Installing I/O Modules
Install each I/O module in the prescribed I/O slot, in accordance with the
installation plan.
For installation instructions, refer to the corresponding section of Appendix B.
Installing Blank Panels
Install blank panels in all the chassis slots that are not occupied by modules.
2.7
Connecting to Power
Grounding Megaplex-4
Warning
Before connecting any cables and before switching on this instrument, the
protective ground terminals of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Make sure that only fuses of the required rating are used for replacement. Use of
repaired fuses and the short-circuiting of fuse holders is forbidden.
Whenever it is likely that the protection offered by fuses has been impaired, the
instrument must be made inoperative and be secured against any unintended
operation.
Connect a short, thick copper braid between the grounding screw on each PS
module panel and a nearby grounding point.
2-32
Connecting to Power
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
Connecting to Power
Caution Megaplex-4 does not have a power on/off switch and will start operating as soon
as power is applied to at least one of its PS modules. It is recommended to use
an external power on/off switch to control the connection of power to Megaplex4. For example, the circuit breaker used to protect the supply line to Megaplex-4
may also serve as the on/off switch.
Power should be connected only after completing cable connections.
Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Note
When redundant power supply modules are used, it is recommended to connect
the power cables to outlets powered by different circuits.
Connecting to External Feed Voltages
External feed voltages are required by the following modules:
•
Voice modules installed in AC-fed chassis
•
ISDN modules
•
SHDSL modules.
The recommended source for external voltages in the case of voice and ISDN
modules is Ringer-2200N offered by RAD. Ringer-2200N is a standalone unit
intended for rack mounting, capable of providing power for up to 120 voice
channels. Refer to the Ringer-2200N Installation and Operation Manual for
connection instructions.
The recommended source for external phantom feed voltages in the case of
SHDSL modules is MPF (Megaplex Power Feed) offered by RAD. standalone unit
intended for rack mounting, MPF provides power for Megaplex SHDSL modules
that require DC voltage to remote DSL repeaters or modems (up to 40 active
SHDSL modems or repeaters operating in 4-wire mode). Refer to the MPF
Installation and Operation Manual for connection instructions.
Caution
Turn on the Ringer-2200N/MPF external voltage source, or connect the external
voltages, only after Megaplex-4 is turned on.
Turn off the Ringer-2200N/MPF external voltage source, or disconnect the
external voltages, only before Megaplex-4 is turned off.
2.8
Connecting Megaplex-4 to a Terminal
Two of the four connectors available on CL.2 modules (CONTROL DCE and ALARM)
are different for Megaplex-4100 and Megaplex-4104 CL.2 modules. Be sure to
refer to the correct section below.
Megaplex-4
Connecting Megaplex-4 to a Terminal
2-33
Chapter 2 Installation
Installation and Operation Manual
Megaplex-4100 CL.2 Module
The CL supervisory port has a serial RS-232 asynchronous DCE interface
terminated in a 9-pin D-type female connector, designated CONTROL DCE.
This port can be directly connected to terminals using a cable wired
point-to-point. A cross cable is required to use the DTE mode, for example, for
connection through modems or digital multiplexer channels.
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.
To connect to the CONTROL DCE port:
The connections to the CONTROL DCE connector are made as follows:
•
Connection to a supervision terminal with 9-pin connector: by means of a
straight cable (a cable wired point-to-point).
•
Connection to modem with 9-pin connector (for communication with remote
supervision terminal): by means of a crossed cable.
Additional connection options are presented in Appendix A.
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.
Megaplex-4104 CL.2 Module
The CL.2/4104 supervisory port has a serial RS-232 asynchronous DCE interface
terminated in a mini-USB connector, designated CONTROL DCE.
This port can be directly connected to terminals using a cable wired
point-to-point. A cross cable is required to use the DTE mode, for example, for
connection through modems or digital multiplexer channels.
Note
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.
To connect to the CONTROL DCE port:
The connections to the CONTROL DCE connector are made as follows:
•
2-34
Connection to a supervision terminal with 9-pin connector: by means of the
CBL-MUSB-DB9F cable supplied by RAD.
Connecting Megaplex-4 to a Terminal
Megaplex-4
Installation and Operation Manual
•
Chapter 2 Installation
Connection to modem with 9-pin connector (for communication with remote
supervision terminal): by means of an additional crossed cable connected to
the CBL-MUSB-DB9F cable.
Additional connection options are presented in Appendix A.
To connect to an ASCII terminal:
1. Connect the mini-USB connector of the CBL-MUSB-DB9F cable available from
RAD to the CONTROL DCE connector.
2. Connect the other connector of the CBL-MUSB-DB9F cable to an ASCII
terminal.
Caution
Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to supervisory
terminal port.
2.9
Connecting to a Management Station or Telnet
Host
The CL modules have 10BASE-T/100BASE-TX Ethernet interfaces terminated in
RJ-45 connectors, designated CONTROL ETH.
These interfaces support MDI/MDIX crossover and therefore the ports can always
be connected through a “straight” (point-to-point) cable to any other type of
10/100BASE-T Ethernet port (hub or station).
To connect to a management station or Telnet host:
•
The link to network management stations using SNMP, and/or Telnet hosts is
made to the RJ-45 connector designated CONTROL ETH.
•
You can use any standard cable (straight or crossed) to connect to any type
of Ethernet port (hub or station).
2.10 Connecting to a Station Clock
The station clock ports located on the CL modules can accept 2.048 MHz or
1.544 MHz signals (framed 2.048 Mbps or 1.544 Mbps signals are also accepted).
The port can also output the clock signal: this output provides a convenient
means for distributing clock signals, including the Megaplex-4 nodal clock signal,
to other equipment.
Megaplex-4
Connecting to a Station Clock
2-35
Chapter 2 Installation
Installation and Operation Manual
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:
•
Note
One of the contacts in the station clock connector is used to sense the
connection of the unbalanced adapter cable (see Appendix A). Do not connect
cables with more than two pairs when you want to use the balanced interface.
•
Note
The cable used for connecting to equipment with balanced interface should
include only two twisted pairs, one for the clock output and the other for the
clock input.
To connect to equipment with unbalanced interface, it is necessary to
convert the CL RJ-45 connector to the standard pair of BNC female
connectors used for unbalanced ITU-T Rec. G.703 interfaces. For this
purpose, RAD offers a 15-cm long adapter cable, CBL-RJ45/2BNC/E1/X. This
cable has one RJ-45 plug for connection to CL station clock connector, and
two BNC female connectors at the other end.
When using redundant CL modules, one of the two station clock ports must be
connected to a station clock source. For best protection, it is recommended to
connect the two station ports to two separate station clock sources.
2.11 Connecting to Alarm Equipment
The alarm port is terminated in a 9-pin D-type female (Megaplex-4100 CL
module) or 9-pin flat (Megaplex-4104 CL module) connector located on the CL
module, designated ALARM. This port includes:
•
Caution
2-36
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.
Connecting to Alarm Equipment
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
•
+5V auxiliary voltage output (through a 330 Ω series resistor).
•
External alarm sense input. The input accepts an RS-232 input signal; it can
also be connected by means of a dry-contact relay to the auxiliary voltage
output.
To connect to the ALARM connector:
The alarm cables for Megaplex-4100 and Megaplex-4104 are supplied by RAD. Refer
to Appendix A for connector pin functions.
Caution
To prevent damage to the internal alarm relay contacts, it is necessary to limit, by
external means, the maximum current that may flow through the contacts
(maximum allowed current through closed contacts is 1A). The maximum voltage
across the open contacts must not exceed 60 VDC.
2.12 Connecting to SDH/SONET Equipment
Note
SFP transceivers can also be installed in the field by the customer, however RAD
strongly recommends to order modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Connecting Optical Cables to the SDH/SONET Links
The optical fibers intended for connection to equipment installed in a rack should
pass through fiber spoolers, located at the top or bottom of the rack, in
accordance with the site routing arrangements (overhead or under-the-floor
routing). The spoolers must contain enough fiber for routing within the rack up to
the CL optical connectors, and for fiber replacement in case of damage (splicing
repairs).
From the spoolers, the optical fibers should be routed through cable guides
running along the sides of the rack frame to the level of the equipment to which
they connect.
When connecting optical cables, make sure to prevent cable twisting and avoid
sharp bends (unless otherwise specified by the optical cable manufacturer, the
minimum fiber bending radius is 35 mm). Always leave some slack, to prevent
stress. RAD recommends installing plastic supports on each cable connector:
these supports determine the fiber bending radius at the connector entry point
and also prevent stress at this point.
Megaplex-4
Connecting to SDH/SONET Equipment
2-37
Chapter 2 Installation
Installation and Operation Manual
Caution When calculating optical link budget, always take into account adverse effects of
temperature changes, optical power degradation and so on. To compensate for
the signal loss, leave a 3 dB margin. For example, instead of the maximum
receiver sensitivity of -28 dBm, consider the sensitivity measured at the Rx side
to be -25 dBm. Information about Rx sensitivity of fiber optic interfaces is
available in SFP/XFP Transceivers data sheet .
Caution Make sure all the optical connectors are closed at all times by the appropriate
protective caps, or by the mating cable connector.
Do not remove the protective cap until an optical fiber is connected to the
corresponding connector, and immediately install a protective cap after a cable is
disconnected.
Before installing optical cables, it is recommended to clean thoroughly their
connectors using an approved cleaning kit.
To connect optical cables to the SDH/SONET links:
1. For each optical interface, refer to the site installation plan and identify the
cables intended for connection to the SFP serving the corresponding
interface.
2. Where two fibers are used, pay attention to TX and RX connections, and
leave enough slack to prevent strain:
Connect the prescribed transmit fiber (connected to the receive input of
the remote equipment) to the TX connector of the SFP.
Connect the prescribed receive fiber (connected to the transmit output of
the remote equipment) to the RX connector of the SFP serving the same
interface.
Connecting Coaxial Cables to SDH/SONET Links
The SFPs offered by RAD for the electrical SDH/SONET links are equipped with
two mini-BNC connectors, one identified as TX (transmit output) and the other as
RX (receive input).
To convert to BNC connectors, RAD offers the CBL-MINIBNC-BNC adapter cable,
terminated in two BNC connectors.
To connect coaxial cables to the SDH/SONET links:
1. For each electrical interface, identify the cables intended for connection to
this interface in accordance with the site installation plan.
Note
If you are using the CBL-MINIBNC-BNC adapter cable, first connect its mini-BNC
connectors to the corresponding connectors of the SDH links (note TX and RX
designations), and then proceed with the connection of the external cables.
2. Connect the prescribed coaxial transmit cable (connected to the receive input
of the remote equipment) to the TX connector of the interface.
2-38
Connecting to SDH/SONET Equipment
Megaplex-4
Installation and Operation Manual
Chapter 2 Installation
3. Connect the prescribed coaxial receive cable (connected to the transmit
output of the remote equipment) to the RX connector of the same interface.
2.13 Connecting to E1 and T1 Equipment
The maximum allowable line attenuation between a Megaplex-4 E1/T1 external
port and the network interface depends on the type of port interface, and
therefore it is given in the Installation and Operation Manual of each specific
module.
The electrical E1 and T1 interfaces of Megaplex-4 systems must not be connected
directly to unprotected public telecommunication networks. Use primary
protectors in the MDF or IDF for additional protection.
2.14 Connecting to Ethernet Equipment
SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends ordering modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Caution When calculating optical link budget, always take into account adverse effects of
temperature changes, optical power degradation and so on. To compensate for
the signal loss, leave a 3 dB margin. For example, instead of the maximum
receiver sensitivity of -28 dBm, consider the sensitivity measured at the Rx side
to be -25 dBm. Information about Rx sensitivity of fiber optic interfaces is
available in SFP/XFP Transceivers data sheet.
Megaplex-4
Connecting to Ethernet Equipment
2-39
Chapter 2 Installation
2-40
Connecting to Ethernet Equipment
Installation and Operation Manual
Megaplex-4
Chapter 3
Operation and
Maintenance
This chapter:
•
Explains power-on and power-off procedures.
•
Describes the Megaplex-4 LED indicators and their function.
3.1
Turning On the Unit
When turning Megaplex-4 on, it is useful to monitor the power-up sequence.
You can monitor the power-up sequence using any standard ASCII terminal (dumb
terminal or personal computer emulating an ASCII terminal) equipped with an
RS-232 communication interface (same terminal that can be used to control the
Megaplex-4 operation).
To monitor Megaplex-4:
1. Configure the terminal for 115.2 kbps, one start bit, eight data bits, no
parity, and one stop bit.
2. Select the full-duplex mode, echo off, and disable any type of flow control.
Make sure to use VT-100 terminal emulation: using a different terminal type
will cause display problems, for example, the cursor will not be located at the
proper location, text may appear jumbled, etc.
To prepare Megaplex-4 for first-time turn-on:
1. Before first-time turn-on, inspect Megaplex-4 installation and check that the
required cable connections have been correctly performed in accordance with
Chapter 2.
2. To monitor the Megaplex-4 during power up and to perform preliminary
configuration procedures, connect a terminal to the CONTROL DCE connector
of the CL module installed in Megaplex-4 slot CLX-A (this module will be, by
default, the active CL module).
Note
Megaplex-4
On the supervision terminal screens, the slots assigned to CL modules are
identified as CL-A, and CL-B.
Turning On the Unit
3-1
Chapter 3 Operation and Maintenance
Caution
Installation and Operation Manual
To turn the Megaplex-4 on:
When an external feed and ring voltage source is connected to the PS modules
installed in Megaplex-4, always turn that source on only after the PS module(s)
have been turned on.
1. Turn the power on.
Note
The Megaplex-4 PS modules do not include a power switch. Use an external
power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
2. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
After a few seconds, Megaplex-4 starts decompressing its software.
After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4 performs
its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4.
3. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active CL module lights in green and that of the
other CL module flashes slowly in green. At this stage, the indicators display
the actual Megaplex-4 status.
3.2
Indicators
The following tables summarize the function of all LED indicators in
Megaplex-4. The normal indications on power-up (provided the corresponding
port is connected) are marked in bold.
CL.2 Front Panel Indicators
Figure 3-1 shows typical dual-slot CL.2 module panels with SDH/SONET and GbE
interfaces (all possible CL.2 panels are described in Chapter 2). Indicators for
single-slot CL.2 modules of Megaplex-4104 are identical. Table 3-1 to Table 3-6
describe the functions of the panel components.
3-2
Indicators
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
CL-2
CL-2
LASER
CLASS
1
LASER
CLASS
1
ON LINE
ON LINE
ALM
S
D
H 1
/
S
O
N
E 2
T
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
1
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
G
b
E
G
b
E
LINK
E
T
H
C
L
O
C
K
A
L
A
R
M
ON/LOS
Copper GbE Interfaces
ON
LINE
ACT
1
2
C
O
N D
T C
R E
O
L
LINK
ACT
ALM
LOS
LOS
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
Optical GbE Interfaces
Figure 3-1. CL.2 Module Panels
Table 3-1. CL.2 System LED Indicators
Megaplex-4
Name
LED Color
Function
ON LINE
Yellow/green
•
On (green): CL module is active or software
decompression
•
Blinking slowly (green): CL module is on
standby
•
On (yellow): a test is being performed
(active module only)
Indicators
3-3
Chapter 3 Operation and Maintenance
Installation and Operation Manual
Name
LED Color
Function
ALM
Red
•
On: alarms have been detected in the
Megaplex-4, but the highest alarm severity
is minor or warning.
•
Blinking: a major and/or critical alarm has
been detected in Megaplex-4
•
Off: No active alarms
Note 1: On the standby CL module, this
indicator is always off, even while an alarm
condition is present
Note 2: The LED still remains on even when
active alarms are already cleared. It only turns
off once active alarms have been cleared via
clear-alarm-log all-logs command.
Table 3-2. SDH/SONET Link LED Indicators
Name
LED Color
Function
ON LINE
Green/Yellow
On (green): the corresponding port is active
(carries SDH/SONET traffic, and there is no
major alarm condition, nor any test on this
port)
Blinking (green) – the port is in protection
mode
On (yellow): a test is active on the port
Off: no traffic or test on the port
Red
LOS
On: loss-of-signal at the corresponding port
Off: no loss-of-signal
Note: Any other alarm condition related to
SDH/SONET traffic handled by the port is
indicated only by the CL general alarm (ALM)
indicator
Note
Status indicators for SDH/SONET ports are active only when the corresponding
port is equipped with an SFP and configured as no shutdown.
Table 3-3. Gigabit Ethernet Port LED Indicators
Name
LED Color
Function
LINK (per port)
Green
On: the port is connected to an active Ethernet
hub or switch
Off: Ethernet link is not detected
ACT (per port)
Yellow
On or Blinking (in accordance with the traffic):
ETH frames are received or transmitted
Off: ETH frames are not received and
transmitted
3-4
Indicators
Megaplex-4
Installation and Operation Manual
Note
Chapter 3 Operation and Maintenance
GbE Status indicators are active only when the corresponding port is configured
as no shutdown, and for optical ports – when the port is equipped with an SFP
Table 3-4. Management Ethernet Port LED Indicators
Name
LED Color
Function
LINK (per port)
Green
On: the port is connected to an active Ethernet hub or
switch
Off: Ethernet link is not detected
ACT (per port)
Yellow
On or Blinking (in accordance with the traffic): ETH
frames are received or transmitted
Off: ETH frames are not received and transmitted
Table 3-5. Clock LED Indicators
Name
LED Color
Function
ON
Green
On: the station clock port is configured as no shutdown
Off: no traffic or test on the port
LOS
Red
On: loss-of-signal (when station clock port configured as
connected)
Off: no loss-of-signal
Front Panel Indicators
The front panels of the Megaplex-4100 and Megaplex-4104 chassis include
additional system status indicators. The figures below identify the front panel
indicators, and Table 3-6 describes indicator functions.
POWER SUPPLY
A
B
SYSTEM
ALARM
TEST
MEGAPLEX-4100
Figure 3-2. Megaplex-4100 Chassis, Front Panel
Megaplex-4
Indicators
3-5
Chapter 3 Operation and Maintenance
Installation and Operation Manual
Figure 3-3. Megaplex-4104 Chassis, Front Panel
Table 3-6. System LED Indicators
Name
Color
Function
POWER SUPPLY
A, B
Green
•
On: the corresponding PS module is on (and one of
the CL modules is active)
•
Off: Power supply is off
•
On: a test (or loopback) is being performed in the
Megaplex-4100
•
Off: No active tests
•
Blinking: a major and/or critical alarm has been
detected in Megaplex-4100
•
On: a minor alarm has been detected in Megaplex4100
•
Off: No active alarms
SYSTEM TEST
SYSTEM ALARM
3.3
Yellow
Red
Startup
Configuration Files
The following files contain configuration settings:
3-6
Startup
•
factory-default contains the manufacturer default settings
•
running-config contains the current configuration that is different from the
default configuration
•
startup-config contains the saved non-default user configuration. This file is
not automatically created. You can use the save or copy command to create
it.
•
user-default-config contains default user configuration. This file is not
automatically created. You can use the copy command to create it.
•
candidate stores any configuration before it is copied to running-config via
commit command.
•
main-sw contains the active software image.
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
Loading Sequence
At startup, the device boots from the startup-config file, the user-default file, or
the factory-default file, in the sequence shown in Figure 3-4 . If none of these
files exist, the device boots using hard-coded defaults.
Start
Pass
Boot from
Startup-config
Sanity
Check
Yes
Startup-config exist?
Fail
Boot from
User-default-config
Pass
Sanity
Check
No
Yes
User-default-config
exist?
Fail
No
Boot from
Factory-default-config
End
Figure 3-4. Loading Sequence
If the loading of startup-config or the user-default file fails, the loading failure
event is registered in the event log.
To display the parameter values after startup, use the info [detail] command.
3.4
Working with Custom Configuration File
In large deployments, often a central network administrator sends configuration
scripts to the remote locations and all that remains for the local technician to do
is to replace the IP address in the script or other similar minor changes (using any
text editor), and then download the file to the device.
To download the configuration file, use the copy command. It is recommended to
copy the file to both startup-config and the user-default file and check that the
device passes the sanity test (no configuration errors are displayed).
After downloading the configuration file to startup-config, you have to execute
the file. This can be done in two ways:
Megaplex-4
Working with Custom Configuration File
3-7
Chapter 3 Operation and Maintenance
Installation and Operation Manual
•
Reset the unit. After the unit completes its startup, the custom configuration
is complete.
•
Instead of resetting the unit, you can simply copy the configuration file to the
running-config file (see File Operations in Chapter 10).
•
Figure 3-5 shows the commands that can copy configuration files in a visual
diagram. For details on file operations, refer to File Operations in Chapter 10.
•
Admin user-default
Sanity
check
Commit
Copy
Copy
User-Default Config
Save
Factory-Default
TFTP
Startup-Config
Running-config
TFTP
Configuration
Session
(Candidate DB)
Copy
Admin factory-default
Figure 3-5. Commands that Copy Configuration Files
3.5
Configuration and Management
Table 4-1 summarizes management alternatives for Megaplex-4.
Table 4-7. Management Alternatives
Port
Manager
Location
Transport
Method
Management
Protocol
Application
CONTROL DCE
Local
Out-of-band
RS-232
Terminal emulation programs
(HyperTerminal, Procomm, Putty).
See Management Access Methods
below.
CONTROL ETH, any
user ETH port on CL
or I/O modules
Local,
remote
Out-of-band
(via CONTROL
ETH only),
Inband
Telnet, SSH over
Ethernet
Procomm, Putty (see Working with
Telnet and SSH below)
STM-1/STM-4/
OC-3/OC-12 links
Remote
Inband
Telnet, SSH over
DCC (IP/PPP or
IP/HDLC)
Procomm, Putty (see Working with
Telnet and SSH below)
3-8
Configuration and Management
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
Port
Manager
Location
Transport
Method
Management
Protocol
Application
Any E1/T1 or SHDSL
link
Remote
Inband
Telnet, SSH over
a dedicated
timeslot (IP/PPP
or IP/FR)
Procomm, Putty (see Working with
Telnet and SSH below)
SNMP over a
dedicated
timeslot (IP/PPP
or IP/FR)
RADview (see Working with
RADview below)
3rd-party NMS (see Working with
Shelf View below)
Optical (mux-ethtdm) link of OP
modules
Local,
remote
Inband
RAD proprietary
HyperTerminal, Procomm, Putty,
any NMS
SHDSL ports of
ASMi-54C/E1/ETH/N
and ASMi-54/ETH
modules
Local,
remote
Inband
EOC
HyperTerminal, Procomm, Putty,
any NMS
Note
By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled.
The following functions are supported by the Megaplex-4 management software:
•
Viewing system information
•
Modifying configuration and mode of operation, including setting system
default values and resetting the unit
•
Monitoring performance
•
Initiating connectivity tests
•
Uploading and downloading software and configuration files.
3.6
Management Access Methods
Two methods used to access the Megaplex-4 management host are via Layer 2 or
Layer 3 networks. By default, Megaplex-4 is managed by Router 1, via Layer-3. If
you want to manage the device via a management VLAN (Layer-2 management),
the bridge must be configured.
Layer-3 Management Access
Figure 4-1 illustrates a typical Layer-3 management scheme.
Megaplex-4 and remote CPE devices are managed using:
•
Megaplex-4
Out-of-band traffic via a dedicated Ethernet management port, or
Management Access Methods
3-9
Chapter 3 Operation and Maintenance
Inband traffic via E1/T1 and SDH/SONET ports.
mng-eth
cl-a
RI#2
mng-eth
cl-b
PPP
DTS
RI#3
•
Installation and Operation Manual
PPP
DCC
Router
RI#1
Host
SVI#1
Figure 4-6. Layer-3 Management Access
The Megaplex-4 host can be accessed by defining IP address and enabling
management on any of the internal router interfaces.
By default, Megaplex-4 has router interface 1 connected to out-of-band Ethernet
management port internally (when no flows are configured between the bridge
and the out-of-band Ethernet management port).
For description of Layer-3 management access, see Management Router section
in Chapter 3.
Layer-2 Management Access
Figure 4-2 illustrates a typical Layer-2 management scheme. Megaplex-4 and
remote CPE devices share the same Layer-2 broadcast domain (VLAN X) and
Layer-2 forwarding entity (bridge) is used for access.
In this scheme, Megaplex-4 and remote CPE devices can be managed using:
•
Out-of-band traffic via a dedicated Ethernet management port, or
•
Inband traffic via any Ethernet port.
The Megaplex-4 host is an IP address of a router interface, connected to a bridge
port.
3-10
Management Access Methods
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
RI#2
PPP
DTS
PPP
DCC
BP#3
mng-eth
cl-b
RI#3
mng-eth
cl-a
Router
BP#2
1
RI#1
Bridge#1 Aware
BP#1
Host
SVI#1
Figure 4-7. Layer-2 Management Access
For description of Layer-2 management access, see Bridge section in Chapter 3.
3.7
Services for Management Traffic
To gain access to the devices, as explained in Management Access Methods, you
must provision an E-LAN (Layer-2) or routing (Layer-3) service. Services are
explained in Chapter 5.
3.8
CLI-Based Configuration
Working with Terminal
Megaplex-4 has a V.24/RS-232 asynchronous DCE port, designated CONTROL DCE
and terminated in a 9-pin D-type female connector. The control port continuously
monitors the incoming data stream and immediately responds to any input string
received through this port.
To set up terminal control:
1. Verify that all the cables are properly connected. For more information, refer
to Chapter 2.
2. Connect Megaplex-4 to a PC equipped with HyperTerminal. Refer to
Connecting to a Terminal in Chapter 2 for additional information on
connecting to the control port.
3. Turn on the control terminal or start the PC terminal emulation. To do so, go
to Start> All Programs> Accessories> Communications>HyperTerminal to
create a new terminal connection.
The HyperTerminal application opens, and the Connection Description
dialog box is displayed.
Megaplex-4
CLI-Based Configuration
3-11
Chapter 3 Operation and Maintenance
Installation and Operation Manual
Figure 4-8. HyperTerminal, Connection Description Dialog Box
4. Enter a name for the terminal connection.
5. Select an icon to represent the terminal connection, or leave the default icon
selected.
6. Click <OK>.
The Connect To dialog appears.
Figure 4-9. Connect To Dialog Box
7. Select a PC COM port to be used to communicate with Megaplex-4 and click
<OK>.
The COM Properties dialog appears.
3-12
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
Figure 4-10. Properties Dialog Box
8. Configure the communication port parameters as follows:
Bits per second: 9,600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
9. Click <OK>.
HyperTerminal is now ready for communication with the unit.
10. Power-up the unit by connecting the power cable(s).
Megaplex-4 boots up and self-test results appear on the terminal screen.
Once the test has been completed successfully, the ON LINE LED
becomes green and a login prompt appears.
Figure 4-11. HyperTerminal Window
11. Refer to the next section for details on logging on.
Megaplex-4
CLI-Based Configuration
3-13
Chapter 3 Operation and Maintenance
Installation and Operation Manual
Working with Telnet and SSH
Typically, the Telnet host is a PC or a Unix station with the appropriate suite of
TCP/IP protocols.
To enable a Telnet host to communicate, it is necessary to assign its IP address
to the management router (1) interface 1. This interface is configured by default
and connected to the out-of-band Ethernet management port (CONTROL ETH).
After this preliminary configuration, you can use a Telnet host connected to it
directly or via a local area network.
Working with Telnet
Telnet uses the terminal utility screens for configuration. The only difference is
that Telnet management access is possible only after performing a preliminary
configuration of the Megaplex-4.
To configure router interface #1 for management:
1. Define IP address of the management interface (#1).
Note
The IP address must be configured to a value different from 1.1.1.x.
2. Define the default gateway (static-route 0.0.0.0/0).
# configure
config# router 1
config>router(1)# interface 1
config>router(1)>interface(1)# address 172.18.170.77/24
config>router(1)>interface(1)#exit
config>router(1)# static-route 0.0.0.0/0 address 172.18.170.1
config>router(1)#commit
3. Enable Telnet access if it is disabled. By default, Megaplex-4 has Telnet access
enabled.
To enable or disable access via Telnet:
1. At the config>mngmnt# prompt, enter access.
The config>mngmnt>access# prompt appears.
2. Type telnet to enable or no telnet to disable Telnet access. The access is
enabled by default.
Using SSH
To prepare for using SSH:
1. If your Megaplex-4 is not yet configured for management, configure router
interface #1 as shown above for Telnet (if you already have Telnet
configured, no need to do this).
2. Enable SSH access if it is disabled. By default, Megaplex-4 has SSH access
enabled.
3-14
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
To enable or disable access via SSH:
1. At the config>mngmnt# prompt, enter access.
The config>mngmnt>access# prompt appears.
2. Type ssh to enable or no ssh to disable Telnet access. The access is enabled
by default.
3. Connect the Ethernet port of the PC to the CONTROL ETH port of the active
CL module, or to the same LAN the CONTROL ETH port is attached to.
4. Start the SSH client program, and select the following parameters:
Connection type: SSH
IP address: use the preconfigured host IP address
Port: 22 (the default SSH port)
5. Click Open to open the SSH session with the Megaplex-4.
6. You will see the log-in prompt: type the prescribed user name, for example,
su, and then press <Enter>.
7. You will see a request for password: enter the prescribed password, for
example, 1234, and then press <Enter>.
8. If login is successful, you will see the main menu.
Login
To access the unit's management/configuration/monitoring options, you must
log in.
Megaplex-4 supports the following access levels:
Megaplex-4
CLI-Based Configuration
3-15
Chapter 3 Operation and Maintenance
Installation and Operation Manual
•
Superuser (su) can perform all the activities supported by the Megaplex-4
management facility, including defining new users of any level and changing
their passwords.
•
Operator (oper) can perform all the activities except defining new users and
changing passwords.
•
User (user) can only monitor the device or change his/her own password
•
Technician (tech) can monitor the device, perform diagnostics and clear
alarms)
To enter the Megaplex-4100 CLI:
1. At the User prompt (user>), enter the access level (su | oper | tech | user) and
press <Enter>.
2. The Password prompt (password>) appears.
3. Enter 1234 as password and press <Enter>.
The base prompt # appears.
Note
It is recommended to change default passwords to prevent unauthorized access
to the unit.
A special option (chngpass) is provided for the case when the user has forgotten
his/her password.
To change/restore the password:
1. At the User prompt (config>mngmnt# user>), enter chngpass and press
<Enter>.
2. Enter user as user name and press <Enter> to receive a temporary password.
With this password you can enter as user and change the password to your
own.
A key code is displayed.
3. Send the key code to RAD Technical Support department.
RAD technical support department will generate a temporary password
which is valid for a single login.
4. Use this temporary password to login and set new permanent user name and
password.
Using the CLI
The CLI consists of commands organized in a tree structure of levels, starting at
the base level. Each level (also referred to as context) can contain levels and
commands (refer to the Navigating section for more information on the levels
and commands available in Megaplex-4). The level is indicated by the CLI prompt.
Note
3-16
Most commands are available only in their specific context. Global commands are
available in any context. You can type ? at any level to display the available
commands.
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
CLI Prompt
The base level prompt contains the device name, which is mp4100 by default (the
device name can be configured in the system level; refer to the Device
Information section in this manual). The prompt ends with $, #, or >, depending
on the type of entity being configured and the user level.
Commands that are not global are available only at their specific tree location,
while global commands can be typed at any level. To find out what commands are
available at the current location, type ?.
If a new dynamic entity is being configured, the last character of the prompt is $.
Examples of dynamic entities include flows, QoS profiles, and OAM CFM entities.
If a new dynamic entity is not being configured, the last character of the prompt
is > (for tech or user access levels) or # (for other access levels).
In addition to being the default prompt, the # symbol also indicates a static or
already configured entity. The $ symbol indicates a new dynamic entity that takes
several commands to configure. The dynamic entity is created as inactive. After
the configuration is completed, it is activated by using the no shutdown
command, as shown in the following example.
# configure port logical-mac 5/1
config>port>log-mac(5/1)$ bind mlppp 5/1
config>port>log-mac(5/1)$ no shutdown
config>port>log-mac(5/1)$ commit
Figure 3-12. Creating and Activating Dynamic Entity
The shutdown command disables a hardware element (such as a port), while no
shutdown enables/activates it.
Note
The examples in this manual use # as the last character of the prompt, unless the
creation of a new dynamic entity is being illustrated.
After you type a command at the CLI prompt and press <Enter>, responds
according to the command entered.
Navigating
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location, followed by #. To navigate up, use the global command
exit. To navigate all the way up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed (or not) by a command. If only level names are typed, navigation is
performed and the prompt changes to reflect the current location in the tree. If
the level names are followed by a command, the command is executed, but no
navigation is performed and the prompt remains unchanged.
Note
To use show commands without navigating, type show followed by the level
name(s) followed by the rest of the show command.
In the example below the levels and command were typed together and therefore
no navigation was performed, so the prompt has not changed.
Megaplex-4
CLI-Based Configuration
3-17
Chapter 3 Operation and Maintenance
Installation and Operation Manual
# configure port ppp 5/1 bind e1 5/1
# configure port ppp 5/2 bind e1 5/2
# configure port ppp 5/3 bind e1 5/3
# configure port ppp 5/4 bind e1 5/4
# configure port ppp 5/5 bind e1 5/5
# configure port ppp 5/6 bind e1 5/6
# configure port ppp 5/7 bind e1 5/7
# configure port ppp 5/8 bind e1 5/8
Figure 4-13. Commands without Level Navigation
In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
#
# configure
config# port
config>port# ppp 5/1
config>port# ppp(5/1)# bind e1 5/1
config>port# ppp(5/1)#
Figure 3-14. Commands with Level Navigation
Note
Level names are abbreviated in the prompt.
Command Tree
The tree command displays a hierarchical list of all the commands in the CLI tree,
starting from the current context.
To view the entire CLI tree (commands only):
1. At the root level, type tree.
# tree
|
+---admin
|
|
|
+---factory-default
|
|
|
+---reboot
|
|
|
+---software
|
|
|
|
|
+---install
|
|
|
|
|
+---show status
more..
2. Press <Enter> to see more or <CTRL-C> to return to the prompt.
When adding the detail parameter, the output also includes the parameters and
values for each command.
3-18
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
To view the CLI tree including all parameters and values:
1. Navigate to the required context by typing level names separated by a space
and press <Enter>.
2. Type tree detail and press <Enter>.
config# tree detail
configure
|
+---access-control
|
|
|
+---access-list [ipv4] <acl-name>
|
|
no access-list <acl-name>
|
|
|
|
|
+---delete <sequence-number>
|
|
|
|
|
+---deny udp <src-address> [<src-port-range>] <dst-address>
[<dst-port>] [log] [sequence
<sequence>]
|
|
|
deny tcp <src-address> [<src-port-range>] <dst-address>
[<dst-port >] [log] [sequence
<sequence>]
3. Press <Enter>to see more or <CTRL-C> to return to the prompt.
Command Structure
CLI commands have the following basic format:
command [parameter]{value1 | value2 | … | valuen} [optional parameter <value>]
where:
{}
Indicates that one of the values must be selected
[]
Indicates an optional parameter
<>
Indicates a value to be replaced by user text
You can type only as many letters of the level, command, or parameter as
required by the system to identify it. For example, you can enter config manag
to navigate to the management level.
To finish configuration changes, type commit. If this command is performed
successfully, OK is displayed. Otherwise, Megaplex-1 displays the relevant error
message.
To verify whether the applied configuration changes are valid (before applying
commit), use the sanity-check command.
You can remove all configuration activity after the last commit command using
the discard-changes command.
Special Keys
The following keys are available at any time:
Megaplex-4
?
List all commands and levels available at the current level
<Tab>
Command autocomplete
↑
Display the previous command (history forward)
CLI-Based Configuration
3-19
Chapter 3 Operation and Maintenance
Installation and Operation Manual
↓
Display the next command (history backward)
<Backspace>
Delete character before cursor
<Delete>
Delete character before cursor
<-
Move cursor one character left
->
Move cursor one character right
<Ctrl-E>
Log out
<Ctrl>+Z
Navigate to base level
The following commands are available at any time and at any level:
echo [<text-to-echo>]
Echoes the specified text
exec <file-name> [echo]
Executes a file, optionally echoing the commands
help [hotkeys] [globals]
Displays general help, or optionally just the
hotkeys and/or global commands
history
Displays the command history for the current
session (by default the history contains the last
10 commands)
info [detail]
Displays information on the current configuration
tree [detail]
Displays all lower command levels and commands
accessible from the current context level
Getting Help
You can get help in the following ways:
•
Type help to display general help (see General Help)
•
Type help <command> to display information on a command and its
parameters
•
Type ? to display the commands available in the level (see Level Help)
•
Use <Tab> while typing commands and parameters, for string completion
•
Use ? after typing a command or parameter, for interactive help (see
Interactive Help).
General Help
Enter help at any level to display general CLI help, including:
•
Short description of CLI interactive help
•
Commands and levels available at the current level
•
Globally available commands
•
CLI special keys (hotkeys)
•
Output modifiers for filtering output.
Example of help command output from the root level:
1. Full help - 'help <cmd>'.
2. To complete level name, command, keyword, argument - <tab> ('conf<tab>' =>
3-20
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
'configuration').
3. To display all currently valid levels, commands, keywords or arguments '?' ('name ?' => '<name-of-device>').
Commands and levels:
admin
+ Administrative commands
configure
+ Configure device
file
+ File commands
Global commands:
commit
- Update the candidate database to the running
database
discard-changes
- Resets to last-saved parameter profile
echo
- Displays a line of text (command) on the screen
exec
- Executes a file
exit
- Returns to the next higher command level (context)
help
- Displays information regarding commands in the
current level
history
- Displays the history of commands issued since the
last restart
info
- Displays the current device configuration
level-info
- Displays the current device configuration commands from the current level only
logout
- Logs the device off
ping
- Ping request to verify reachability of remote host
sanity-check
- Initiates a self test of the device
save
- Saves current settings
startup-config-confi* - Confirm configuration
tree
- Displays the command levels from the current
context downwards
virtual-terminal
- Enter the virtual terminal
Hotkeys:
DEL
-delete character
<-move cursor right
->
-move cursor left
TAB
-complete token
?
-help
Arrow up
-history forward
Arrow down
-history backward
BACKSPACE
-delete character
^Z
-return to configuration root
^E
-exit cli
Command Help
Enter help <command> to display command and parameter information.
config>system# help name
- name <name-of-device>
- no name
<name-of-device> : Adds free text to specify the device name [0..255 chars]
Level Help
Enter ? at the command prompt to display the commands available in the current
level.
Megaplex-4
CLI-Based Configuration
3-21
Chapter 3 Operation and Maintenance
Installation and Operation Manual
file# ?
copy
delete
dir
- Copies a file
- Deletes a file from the device
- Lists all files in the device
show copy
show sw-pack
- Displays copy status
- Displays the existing sw-packs and their content
String Completion
Megaplex-4 automatically completes levels, commands, and parameters when you
press <Tab> immediately after a string.
If the string can be completed in more than one way, Megaplex-4 appends the
characters that are common to all the possibilities.
If the string can be completed in only one way, Megaplex-4 completes it and
appends a space.
If the string is already a complete level/command/parameter or cannot be
completed to a level/command/parameter, no completion is done.
Pressing <Tab> a second time displays any available command parameters.
Some user-defined strings such as flow names or profile names can be completed
as well. If the user enters an entity name (flow, profile or similar) that does not
exist in the database, Megaplex-4 creates this entity with the selected name.
The following table shows examples of string completion.
Table 4-8. String Completion
Level
String
Possibilities for Completion
Result After Pressing <Tab>
file
show c
show configuration-files
show copy
show co
file
show con
show configuration-files
show configuration-files<space>
config>flows
class
classifier-profile
classifier-profile<space>
config>sys
name
name
name
config
mgm
No possibilities
mgm
config>flows
flows# flow my-f
my-flow-1
my-flow-
my-flow-2
config>flows
flows# flow my-flow-1
my-flow-1
my-flow-1<space>
config>flows
flows# flow my-flow-3
No possibilities
my-flow-3
This is a new flow, as my-flow-3
did not exist before.
Interactive Help
To get interactive help, type ?.
In general, typing a ? directly after a string performs string completion, while
typing <space> and then a ? executes the command.
3-22
CLI-Based Configuration
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
When a <CR> appears in a ? list, the string you entered is itself a valid command
needing no further additions. Pressing <Enter> executes the command or
navigates to the indicated level.
Typing ? immediately after a command or partial command with no space before
the ?, tells Megaplex-4 to display all possibilities for completing the string. Help
output is always followed by the string you typed with the cursor at the end of
the string waiting for input.
config>flows# classifier-profile myclass m?
match-any
config>flows# classifier-profile myclass m
admin# fact?
factory-default-all
- Resets all configuration and counter
factory-default
- Loads factory default configuration
admin# fact
admin# factory-default?
factory-default-all
- Resets all configuration and counters
<CR>
admin# factory-default
When a string cannot be completed, Megaplex-4 displays “cli error: Invalid
Command”.
admin# stac?
# cli error: Invalid Command
admin# stac
file# da ?
# cli error: Invalid Command
file# da
Typing <?> after a space between a command or level name and the ? tells
Megaplex-4 to try to execute the command. The space tells the CLI that you are
finished typing and to try to match the string to an appropriate command. The
string does not have to be a complete command.
If there is only one possible command starting with that string, pressing <Enter>
will execute the command. If there is more than one command that starts with
the string, the CLI displays a message that it can’t clarify which command you
want.
172_17_155_24>admin# factory?
factory-default-all
factory-default
- Resets all configuration and counters
- Loads factory default configuration
A command followed by a ? without a space, shown above, returns a list of
possible completions. The same command followed by a space and then the ?
returns an ambiguous command message. This means the string entered could be
completed to more than one command is therefore ambiguous, as shown below.
172_17_155_24>admin# factory ?
# cli error: Ambiguous Command
172_17_155_24>admin# factory
A string that is a complete command name followed by a space ? displays all
possible command parameters.
Megaplex-4
CLI-Based Configuration
3-23
Chapter 3 Operation and Maintenance
Installation and Operation Manual
config>flows# show ?
summary
- Displays list of flows
config>flows# show
config>flows# classifier-profile ?
<classification-n*> : [1..32 chars]
config>flows# classifier-profile
The next example shows a complete command to which a parameter could be
appended. It also shows how a string that is a complete command is executed by
pressing <CR>, or <Enter>.
config>access-control# resequence access-list acl_1 ?
<CR>
<number>
: [0..100000]
The next example shows a complete command that has no parameters.
config>flows# classifier-profile myclass match-any ?
<CR>
config>flows# classifier-profile myclass match-any
Using Scripts
CLI commands can be gathered into text files. They may be created using a text
editor, by recording the user commands or by saving the current configuration.
These files can be configuration files or scripts. Configuration files have specific
names and contain CLI commands that Megaplex-4 can use to replace the current
configuration, while scripts contain CLI commands that add to the current
configuration. Configuration files can be imported from and exported to RAD
devices via file transfer protocols.
Note
Although scripts can be created using a text editor, it is recommended to save
the configuration file and then edit it rather than write a script from scratch. The
sequence of the commands is very important and if a script fails during startup at
a certain command, the entire configuration file is discarded.
For more information on configuration files, refer to the description in the
Operation chapter.
In order to execute a CLI script, you have to copy/paste it to the CLI terminal, or
send it to Megaplex-4 via the RADview Jobs mechanism, CLI script option.
To execute a script, perform the commit command.
3.9
SNMP-Based Network Management
Preconfiguring Megaplex-4 for SNMP Management
Megaplex-4 can be managed by any SNMP-based network management station,
such as the RADview family of network management stations, provided IP
communication is possible with the management station, as well as with the
standalone RADview stations.
3-24
SNMP-Based Network Management
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
To manage the Megaplex-4 from a remote NMS, it is necessary to preconfigure
the basic parameters using a supervision terminal connected to the Megaplex-4
CONTROL DCE port. RAD recommends Layer-3 management access via
out-of-band Ethernet management port.
To preconfigure Megaplex-4 for Layer-3 management access:
1. Add a router interface, bind it to the SVI and add a static route to the next
hop.
Note
The IP address must be configured to a value different from 1.1.1.x.
2. Configure SNMPv3 parameters:
OID tree visibility, mask and type
Access group
Trap report policy.
Script below provides all necessary configuration steps. Replace IP addresses and
entity names with values relevant for your network environment.
### Defining the Router Interface####
configure
router 1 interface 1 address 172.18.171.121/24
router 1 interface 1 bind svi 1
router 1 static-route 0.0.0.0/0 address 172.18.171.1
exit all
#*********************Configuring_SNMP_View/Mask/Type************************
configure management snmp
view internet 1
mask 1
type included
no shutdown
exit all
#**********************************End***************************************
#*********************Enabling_SNMP_V3***************************************
configure management snmp
snmpv3
no shutdown
exit all
#**********************************End***************************************
#*********************Configuring_SNMP_Access_Group************************
configure management snmp
access-group initial usm no-auth-no-priv
context-match prefix
exit all
#**********************************End***************************************
#**************************Configring_SNMP_Traps*****************************
configure management snmp
target-params p
message-processing-model snmpv3
version usm
Megaplex-4
SNMP-Based Network Management
3-25
Chapter 3 Operation and Maintenance
Installation and Operation Manual
security name initial level no-auth-no-priv
no shutdown
exit
target a
target-params p
tag-list unmasked
address udp-domain 172.17.176.35
no shutdown
exit
notify unmasked
tag unmasked
no shutdown
trap-sync-group 1
exit all
#**********************************End************************************
Working with RADview
RADview-EMS is a user-friendly and powerful SNMP-based element management
system (EMS), used for planning, provisioning and managing heterogeneous
networks. RADview-EMS provides a dedicated graphical user interface (GUI) for
monitoring RAD products via their SNMP agents. RADview-EMS for Megaplex-4 is
bundled in the RADview-EMS package for PC (Windows-based) or Unix.
For more details about this network management software, and for detailed
instructions on how to install, set up, and use RADview, contact your local RAD
partner or refer to the RADview-EMS User's Manual at the RAD website.
Megaplex-4100 can be also managed by the RV-SC/TDM service management
application.
Working with Shelf View
Shelf View is an SNMP-based application with fully FCAPS-compliant element
management. It displays a dynamic graphic representation of the device panel(s),
providing an intuitive, user-friendly GUI. Shelf View includes port and/or card
interfaces and their operational and communication statuses.
Shelf View is distributed as an executable (*.exe) file. It can be run under
Windows 7 and Windows 8 with Java Runtime Environment 1.7.0 and above. The
application (and its manual) are available via RAD partners.
Working with Other SNMP-Based NMS
Megaplex-4 can be integrated into 3rd-party management systems at different
levels:
3-26
•
Viewing device inventory and receiving traps (see Chapter 11 for trap list)
•
Managing device, including configuration, statistics collection, diagnostics,
using standard and private MIBs:
IANAifType-MIB
IETF Syslog Device MIB
SNMP-Based Network Management
Megaplex-4
Installation and Operation Manual
Chapter 3 Operation and Maintenance
IEEE8023-LAG-MIB
MEF-R MIB
RAD private MIB
RFC 2819 (RMON-MIB)
RFC 2863 (IF-MIB)
RFC 3273 (Remote Network Monitoring MIB)
RFC 3411 (SNMP-FRAMEWORK-MIB)
RFC 3413 (SNMP-TARGET-MIB)
RFC 3414 (SNMP-USER-BASED-SM-MIB)
RFC 3415 (SNMP-VIEW-BASED-ACM-MIB)
RFC 3418 (SNMPv2-MIB)
RFC 3636 (MAU-MIB)
RFC 4668 (RADIUS-AUTH-CLIENT-MIB)
RFC 4836.MIB (MAU-MIB)
RFC 3592 SONET MIB
RFC 4319 SHDSL2-SHDSL-LINE-MIB
RFC 4805 DS1-MIB.
3.10 Turning Off the Unit
To turn the Megaplex-4 unit off:
•
Megaplex-4
Disconnect the power cord from the power source.
Turning Off the Unit
3-27
Chapter 3 Operation and Maintenance
3-28
Turning Off the Unit
Installation and Operation Manual
Megaplex-4
Chapter 4
Service Provisioning
This chapter presents information on the service elements and services provided
by Megaplex-4.
4.1
Service Elements
This section details the managed elements that need to be configured during
service provisioning.
Service provisioning elements are as follows:
•
Profiles
•
Physical ports (User Ethernet, SHDSL, E1, T1, T3, Voice, Serial, Mux-Eth-Tdm
(fiber optic links of Optimux modules), DS1-opt (fiber optic links of VS-6/C37
modules), SDH/SONET, Teleprotection and VS-6/BIN CMD CHANNEL, CMD-IN,
CMD-OUT ports)
•
Logical ports (PCS, HDLC, MLPPP, PPP, BRI, Serial Bundle, Logical MAC, VCG,
GFP, SVI, Internal DS1, PW, LAG, LRE, Teleprotection CMD-IN-I and CMD-OUT-I)
•
Forwarding entities (flow, bridge, router).
Profiles
Most traffic processing features are defined by creating and applying various
profiles. Profiles comprise sets of attributes related to a specific service entity.
Profiles must be defined prior to other managed objects.
Table 5-1. Profile Types
Profile Type
Applied to
Description
Scale per Chassis
Classifier
Flow
Defines criteria for flow classification
128
Shaper
Queue, queue block
Defines CIR, CBS, EIR and EBS
parameter
30
WRED
Queue
Defines green and yellow packet
thresholds and drop probabilities
8
Queue block
Queue block within
queue group
Defines queue block parameters
(queues, scheduling scheme,
weights)
128
Megaplex-4
Service Elements
4-1
Chapter 4 Service Provisioning
Installation and Operation Manual
Profile Type
Applied to
Description
Scale per Chassis
Queue group
Port
Defines level-0 and -1 scheduling
elements and structures within
queue group
15
L2CP
Port, flow
Defines actions for L2CP processing
(drop, peer, tunnel)
6
Policer
Flow
Define CIR, CBS, EIR and EBS
parameters
60
Marking
Flow
Defines method of mapping CoS
values into P-bit
12
Signaling
E1/T1 ports
Specifies translation rules for
signaling information
5
VC
GFP, HDLC, E1, E1-I,
AUG, T1, T1-I, OC3
ports
Defines the handling of SDH/SONET
(VC/VT/STS) traffic
64
Analog Signaling
Voice ports
Specifies translation rules for
signaling information
8
Scheduling and Shaping Entities
Megaplex-4 schedules traffic using the following hierarchical scheduling entities:
•
Queue – a lowest-level scheduling element. Its priority can be strict or weight
fair. Queues have shaper and WRED profiles assigned to them.
•
Queue block (also referred to as scheduling element, or SE) – a mid-level
scheduling element that consists of several queues. Queue blocks are created
by associating queues with queue block profiles. There are two levels of
queue blocks for CL GbE ports and one level for other Ethernet ports. Queue
blocks have shaper profiles assigned to them.
•
Queue group – a top-level scheduling element that consists of several queue
blocks. Queue groups are created by associating queue group profile to ports.
Megaplex-4 provides the following shaping tools:
•
Dual leaky bucket shaper (CIR/EIR)
•
Single leaky bucket shaper (CIR).
Congestion is avoided by using the WRED mechanism.
Physical Ports
Services provided by Megaplex-4100/4104 are based on its physical ports. These
ports are located on the following modules (which can sometimes be
interchangeable in providing specific services):
4-2
•
SDH/SONET –CL.2
•
GbE – CL.2, M-ETH
Service Elements
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
•
Fast Ethernet – OP-108C, OP-34C, ASMi-54C/N, ASMi-54C, MPW-1, M8E1,
M8T1, M8SL, VS
•
SHDSL – ASMi-54C/N, ASMi-54C, M8SL
•
E1 – OP-108C, OP-34C, ASMi-54C/N, M8E1, M16E1, VS-16E1T1-EoP
•
T1 – M8T1, M16T1, VS-16E1T1-EoP
•
T3 – T3
•
Voice – VC-4/VC-8/VC-4A/VC-8A/VC-16, VC-4/OMNI, VC-6/LB, VS Voice family
•
Serial – HS-6N/12N, HS-U-6/12, HS-S, HS-RN, HSF-2, LS-6N/12, VS family
•
Mux-Eth-Tdm (Optimux fiber optic links) – OP-108C, OP-34C
•
DS1-Opt (VS fiber optic links) – VS-6/C37
•
CMD CHANNEL, CMD-IN, CMD-OUT – TP (Teleprotection), VS-6/BIN
Logical Ports
Logical ports maintained by Megaplex-4 do not have physical port attributes and
serve different purposes, depending on the module and on the service provided
by the module/system physical ports. The following logical ports exist:
Megaplex-4
•
Switched Virtual Interface (SVI) located on CL.2 modules and used for binding
flows to bridge ports, router interfaces or Layer-2 TDM pseudowires. SVIs
serve as intermediaries for bridges and routers, which must comply with
standards of their own (VLAN domains for bridge ports or IP address for
router interfaces) and. They also serve as aggregation points for TDM PWs
•
VCG, GFP and HDLC ports located on CL.2 modules and used for efficient
transport of Ethernet traffic over the SDH/SONET network. GFP and HDLC
ports are mapped either directly to the physical layer or to VCG. In the latter
case, the binding is done in two stages and the VCG is further bound to the
physical layer.
•
VCG and GFP ports located on T3 modules and used for efficient transport of
Ethernet traffic over the T1/T3 networks. GFP ports are mapped either
directly to the physical layer or to VCG. In the latter case, the binding is done
in two stages and the VCG is further bound to the physical layer.
•
VCG and GFP ports located on VS-16E1T1-EoP modules and used for efficient
transport of Ethernet traffic over the E1/T1 networks. VCG ports are bound
directly to GFP.
•
HDLC, MLPPP and PPP ports used for efficient transport of Ethernet traffic
over E1/T1. HDLC ports defined on located on M8E1, M8T1 and M8SL
modules and are bound to the physical layer. MLPPP and PPP ports exist only
on M8E1 and M8SL modules; PPP ports are bound to the physical layer,
serving an intermediary to MLPPP ports. MLPPP and HDLC ports are connected
to Ethernet media via Logical MAC ports.
•
Logical MAC ports located on CL.2, T3, VS-16E1T1-EoP and M8E1/M8T1/M8SL
modules used to describe and map the Ethernet traffic passing over different
media (E1/T1, T3, SDH/SONET, etc) and representing the MAC layer of the
entity. Logical MAC ports are bound to a GFP, HDLC or MLPPP ports, which, in
its turn, are bound to the physical layer.
Service Elements
4-3
Chapter 4 Service Provisioning
Installation and Operation Manual
•
PCS (Physical Coding Sublayer) ports located on the ASMi-54C/N, ASMI-54C
and SH-16 modules, which determine the Ethernet (packet) physical layer
transmission capabilities over SHDSL lines
•
BRI ports located on HSU-6, HSU-12 and HS-S I/O modules and used to
provide ISDN services.
•
The serial bundle ports located on LS-6N, LS-12 modules and used to form
single/dual composite data stream, serving as intermediaries to bind serial
ports to either of the Megaplex uplink ports
•
Internal DS1 Ports located on MPW-1 and VS modules and used to connect
between pseudowires and serial ports.
•
CMD-IN-I and CMD-OUT-I ports located on Teleprotection module and used to
manipulate the logical Rx/Tx information over the corresponding CMD
CHANNEL
•
PW ports located on MPW-1 and VS modules.
Forwarding Entities
Several internal entities carry traffic and make forwarding and switching
decisions. These are:
•
Flows – the main traffic-carrying elements
•
Bridge – traffic-forwarding element for Layer-2 E-LAN services
•
Router – traffic-forwarding element for Layer-3 services.
Flows
Flows interconnect two physical or logical ports and are the main traffic-carrying
elements in Megaplex-4 architecture. You can use classifier profiles to specify the
criteria for flows. The classification is per port and is applied to the ingress port
of the flow.
Flows defined in Megaplex-4100/4104 can be unidirectional (between
physical/logical ports) or bidirectional (between physical/logic ports and brigde
ports of CL modules).
Note
Bridge ports in M-ETH modules are bound directly (without using flows).
Flow processing is performed as follows:
4-4
•
Ingress traffic is mapped in flows using classification match criteria defined
via classification profile.
•
L2CP frames are handled per flow according to L2CP profile settings.
•
User priority (P-bit, IP Precedence, DSCP) is mapped into internal Class of
Service (CoS) according to assignment per flow.
•
User priority (P-bit, IP Precedence, DSCP) can be mapped into packet color
(yellow or green) according to assignment per flow.
•
VLANs can be edited per flow by stacking (pushing), removing (popping), or
swapping (marking) tags on single-, or double-tagged packets. P-bit values
are either copied or set according to CoS marking profile.
Service Elements
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
•
A single policer can be applied to a flow, using policer profile.
•
A flow is mapped to a specific queue block within a queue group associated
with egress port.
Bridge
The bridge is a forwarding entity used by Megaplex-4 for delivering E-LAN services
in multipoint-to-multipoint topology and G.8032 ring protection. With up to 11
bridge instances, Megaplex-4 provides up to 170 bridge ports, subdivided as
follows:
•
80 ports on the CL.2 bridge
•
9 ports per M-ETH module bridge (8 external + 1 internal) – maximum 90
ports per chassis.
The bridge uses bridge ports for connecting to logical and physical ports.
The bridge is defined by a bridge number, bridge ports and a VLAN membership
table that specifies which bridge ports are members in a certain broadcast
domain (VLAN). The bridge supports one level of VLAN editing on ingress and one
level on egress. The editing is performed at the flow level.
Router
The Megaplex-4 router is an internal Layer-3 interworking device that forwards
traffic between its interfaces. Each router interface is assigned an IP address and
can be bound to one of the following:
•
Physical/logical E1/T1/DS1-opt (via DTS) or SDH/SONET (via DCC) port
•
SVI port connected via flow to a bridge port (which provides access to any
Ethernet-type physical/logical port)
The router uses switched virtual interfaces (SVIs) for connecting to logical and
physical ports. The connection is always made by directing flows from a port to
an SVI, and then binding the SVI to a router interface.
4.2
Services Provided by Megaplex-4
Both carriers and transportation and utility services providers can benefit from
Megaplex-4 capabilities. The services for carriers and service providers (TDM
and/or ETH grooming) are as follows.
Carrier and utility services provided by Megaplex-4 include:
•
Megaplex-4
Aggregation Services:
TDM (E1/T1) service aggregation over copper/fiber lines into SDH/SONET
backbone
TDM (E1/T1) service aggregation over copper/fiber lines into PSN
backbone
TDM (E1/T1) and Ethernet service aggregation over copper/fiber lines into
SDH/SONET backbone
Services Provided by Megaplex-4
4-5
Chapter 4 Service Provisioning
•
Installation and Operation Manual
TDM (E1/T1) and Ethernet service aggregation over copper/fiber lines into
SDH/SONET and PSN backbone (TDM to TDM, Ethernet to PSN)
TDM (E1/T1) and Ethernet service aggregation over copper/fiber lines into
PSN backbone
Ethernet service aggregation over copper/fiber lines into PSN.
Voice aggregation to T3 backbones.
Cross-connect services:
Legacy (Voice, serial, ISDN) services cross-connect for interbranch
connectivity
Multiplexing any traffic (Legacy/TDM/Ethernet) for cross-connect services.
T3 traffic to SONET (via T1 x-connect).
Transportation and utility services provided by Megaplex-4 include:
•
TDM- and Ethernet service aggregation to SDH/SONET backbones
•
Legacy and new Ethernet-based service aggregation to SDH/SONET and PSN
backbones (keeping mission-critical services towards the TDM backbone)
•
Legacy and new Ethernet-based service aggregation to PSN backbones
•
Resilient ring topology for legacy and Ethernet services with minimal
downtime
•
Teleprotection over SDH/SONET.
Selected services from the above list are summarized in Table 5-2 and schematic
diagrams in Figure 5-1 to Figure 5-7. Modules shown in diagrams as examples are
listed in Table 5-2 in bold. If you want to draw a diagram for a specific service
provided by another module, you can use the relevant elements of sample
services to draw a service of your own.
Table 5-2. Selected Services Provided by Megaplex-4
No
Description
I/O Modules Providing
the Service
Schematic
Diagram
Configuration
Procedure
1a
TDM (E1) service aggregation over
copper lines into SDH/SONET backbone
(via direct transparent mapping)
OP-108C, OP-34C,
ASMi-54C/N, M16E1,
M16T1, VS-16E1T1-EoP
Figure 5-1
Figure 5-13
Table 5-3
1b
TDM (E1/T1) service aggregation over
copper lines into SDH/SONET backbone
(via DS0 mapping)
OP-108C, OP-34C,
ASMi-54C/N, M8E1,
M8T1, M16E1, M16T1, VS16E1T1-EoP
Figure 5-1
Figure 5-14
Table 5-4
2a
TDM (E1/T1) service aggregation over
fiber lines into PSN backbone
OP-108C, OP-34C
Figure 5-1
Figure 5-15
Table 5-5
2b
Ethernet service aggregation over fiber
lines into PSN backbone
OP-108C, OP-34C,
ASMi-54C/N, ASMi-54C,
MPW-1, M8E1, M8T1,
M8SL
Figure 5-1
Figure 5-16
Table 5-6
4-6
Services Provided by Megaplex-4
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
No
Description
I/O Modules Providing
the Service
Schematic
Diagram
Configuration
Procedure
3
Fast Ethernet service aggregation to
SDH/SONET backbones
OP-108C, OP-34C,
ASMi-54C/N, ASMi-54C,
MPW-1, M8E1, M8T1,
M16E1, M16T1
Figure 5-2
Figure 5-17
Table 5-7
3a
TDM (E1) service aggregation over
copper lines into PSN backbone
ASMi-54C/N
Figure 5-2
Figure 5-19
Table 5-9
3b
Ethernet service aggregation over copper
lines into PSN backbone
ASMi-54C/N, ASMi-54C
Figure 5-2
Figure 5-20
Table 5-10
3c
Shared E-LAN service with multiple drops
per node over SDH/SONET
M-ETH
Figure 5-3
Figure 5-18
4
High-Speed service aggregation to
SDH/SONET backbones
HS-6N/12N
Figure 5-4
Figure 5-21
Table 5-11
4a
High-Speed service aggregation to Fast
Ethernet
HS-6N/12N + MPW-1
Figure 5-4
Figure 5-22
High-Speed service aggregation into PSN
backbone
HS-6N/12N + MPW-1
High-Speed service aggregation into PSN
backbone with G.8032 protection
HS-6N/12N, MPW-1
High-Speed service aggregation to Fast
Ethernet (low-latency)
VS
High-Speed service aggregation into PSN
backbone (low-latency)
VS
Fast Ethernet service aggregation to
E1/T1 links
M8E1, M8T1, M8SL
Fast Ethernet service aggregation to
multiple E1 links
M8E1, M8SL
6
Voice aggregation to SDH/SONET
backbones
VC-4/VC-8/ VC-4A/
VC-8A/VC-16, VC-4/OMNI,
Figure 5-7
Figure 5-27
Table 5-17
6a
Voice service aggregation into PSN
backbone
VS Voice
Figure 5-8
Figure 5-28
7
Teleprotection over SDH/SONET
TP
Figure 5-9
Figure 5-29
Table 5-19
8
Voice aggregation to T3 backbones
T3
Figure 5-10
Figure 5-30
4b
4c
4d
4e
5a
5b
Table 5-8
Table 5-12
Figure 5-22
Table 5-12
Figure 5-5
Figure 5-24
Table 5-14
Figure 5-6
Figure 5-22
Table 5-12
Figure 5-6
Figure 5-24
Table 5-14
Figure 5-7
Figure 5-25
Table 5-15
Figure 5-7
Figure 5-26
Table 5-16
Table 5-18
VC-4/VC-8/ VC-4A/
VC-8A/VC-16, VC-4/OMNI,
VS Voice
Megaplex-4
Figure 5-4
Table 5-20
Services Provided by Megaplex-4
4-7
Chapter 4 Service Provisioning
Installation and Operation Manual
No
Description
I/O Modules Providing
the Service
Schematic
Diagram
Configuration
Procedure
9
T3 traffic to SONET
T3
Figure 5-11
Figure 5-31
Table 5-21
10a
Ethernet traffic over PDH to SDH/SONET
Figure 5-12
VS-16E1T1-EoP
Figure 5-32
Table 5-22
10b
Ethernet traffic over PDH to TDM (E1/T1)
Figure 5-12
VS-16E1T1-EoP
Figure 5-33
Table 5-23
The following figures schematically describe selected services provided by
Megaplex-4.
M8E1/T1
M16E1/T1, VS-16E1T1-EoP
E1
OR
1a
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
TP
1b
E1-i/T1-i
DS0
X-Connect
Voice
HS-12N
VCAT
GFP
L.MAC
ETH
Engine
OP-108C
2a
E1i
GbE
PSN
IntETH
E1
Mux-ETHTDM
2b
ETH
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via
direct transparent mapping)
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via DS0
mapping)
Ethernet service aggregation over fiber lines into PSN backbone
ASMi-54C/N
MPW-1
TDM (E1/T1) service aggregation over fiber lines into PSN backbone
Figure 5-1. Services 1, 1a, 2a, 2b
4-8
Services Provided by Megaplex-4
Megaplex-4
ETH
Installation and Operation Manual
Chapter 4 Service Provisioning
M8E1/T1
M16E1/T1
Voice
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
3a
DS0
X-Connect
HS-12N
TP
VCAT
GFP
ETH
Engine
L.MAC
3
ASMi-54C/N
E1i
E1
SHDSL
ETH
PCS
GbE
PSN
3b
ETH
OP-108C
Fast Ethernet service aggregation to SDH/SONET backbones
TDM (E1) service aggregation over copper lines into PSN backbone
Ethernet service aggregation over copper lines into PSN backbone
MPW-1
Figure 5-2. Services 3, 3a, 3b
M8E1/T1
M16E1/T1
VC-4/4A/8/8A/16
VC-4/OMNI
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
DS0
X-Connect
HS-12N
L.MAC
M-ETH
VCAT
GFP
L.MAC
3c
PSN
ETH
Engine
ETH
Engine
GbE
ASMi-54C/N
OP-108C
Shared E-LAN service with multiple drops per node over SDH/SONET
MPW-1
Figure 5-3. Service 3c
Megaplex-4
Services Provided by Megaplex-4
4-9
Chapter 4 Service Provisioning
Installation and Operation Manual
M8E1/T1
M16E1/T1
Voice
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
TP
DS0
X-Connect
4
Serial
VCAT
GFP
L.MAC
HS-12N
ETH
Engine
4b
GbE
PSN
ASMi-54C/N
4a
OP-108C
PW
Router
SVI
MPW-1
DS1
PW
X-Connect
High-Speed service aggregation to SDH/SONET backbones
PW
High-Speed service aggregation to Fast Ethernet
High-Speed service aggregation into PSN backbone
ETH
Figure 5-4. Services 4, 4a, 4b
M8E1/T1
M16E1/T1
Voice
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
TP
DS0
X-Connect
Serial
VCAT
GFP
East
PSN
West
L.MAC
HS-12N
ETH
Engine
4c
ASMi-54C/N
GbE
GbE
OP-108C
PW
Router
SVI
MPW-1
DS1
PW
X-Connect
PW
High-Speed service aggregation into PSN backbone
with G.8032 protection
ETH
Figure 5-5. Service 4c
4-10
Services Provided by Megaplex-4
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
E1/T1
Voice
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
TP
DS0
X-Connect
E1-i/T1-i
Serial
VCAT
GFP
4f
ETH
Engine
L.MAC
ASMi-54C/N
OP-108C
GbE
PSN
VS
PW
Router
Serial
SVI
4d
DS1
PW
X-Connect
4e
High-Speed service aggregation to SDH/SONET backbones
PW
High-Speed service aggregation to Fast Ethernet
High-Speed service aggregation into PSN backbone
ETH
Figure 5-6. Services 4d, 4e, 4f
M8E1/T1
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
HDLC
E1/T1
ETH
L.MAC
5a
VC-4/4A/8/8A/16, VC-4/OMNI
VS voice
E1-i/T1-i
DS0
X-Connect
Voice
6
M8E1
5b
PPP
VCAT
GFP
ETH
Engine
L.MAC
E1
MLPPP
L.MAC
ETH
GbE
PSN
TP
M16E1/T1
Fast Ethernet service aggregation to E1/T1 links
Fast Ethernet service aggregation to multiple E1 links
HS-12N
Voice aggregation to SDH/SONET backbones
ASMi-54C/N
MPW-1
Figure 5-7. Services 5a, 5b, 6
Megaplex-4
Services Provided by Megaplex-4
4-11
Chapter 4 Service Provisioning
Installation and Operation Manual
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
DS0
X-Connect
VCAT
GFP
L.MAC
ETH
Engine
6a
VS Voice
GbE
PSN
Voice
PW
Router
SVI
DS1
1/1
PW
X-Connect
PW
1/1
DS1/PW 1:1
Voice service aggregation into PSN backbone
Figure 5-8. Service 6a
M8E1/T1
Voice
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1-i/T1-i
DS0
X-Connect
7
CMD
Channel
CMD-IN-I
CMD-IN
CMD-OUT-I
CMD-OUT
TP
VCAT
GFP
L.MAC
ETH
Engine
M16E1/T1
HS-12N
GbE
PSN
ASMi-54C/N
MPW-1
Teleprotection Traffic over SDH/SONET
Figure 5-9. Service 7
4-12
Services Provided by Megaplex-4
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
M8E1/T1
T3
8
T1
CL.2
SDH/SONET
X-Connect
SONET Link
SONET
T3
TP
M16E1/T1
VCAT
GFP
ETH
Engine
L.MAC
HS-12N
ASMi-54C/N
GbE
PSN
MPW-1
T3 Module
CL.2
VC-4/4A/8/8A/16, VC-4/OMNI,
VS voice
T3
Link
T3
DS0
X-Connect
T1
Voice
9
T3 to SONET
Voice aggregation to T3 backbones
Figure 5-10. Services 8,9
M8E1/T1
M16E1/T1, VS-16E1T1-EoP
E1
OR
1a
CL.2
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
TP
1b
E1-i/T1-i
DS0
X-Connect
Voice
HS-12N
VCAT
GFP
L.MAC
ETH
Engine
OP-108C
2a
E1i
PSN
GbE
IntETH
E1
Mux-ETHTDM
2b
ETH
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via
direct transparent mapping)
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via DS0
mapping)
Ethernet service aggregation over fiber lines into PSN backbone
ASMi-54C/N
MPW-1
TDM (E1/T1) service aggregation over fiber lines into PSN backbone
Megaplex-4
Services Provided by Megaplex-4
4-13
ETH
Chapter 4 Service Provisioning
Installation and Operation Manual
Figure 5-11. Services 8,9
VS-16E1T1-EoP
CL.2
10b
10a
SDH/
SONET
SDH/SONET
Link
SDH/SONET
X-Connect
E1i
E1
GFP
VCG
L.MAC
VCAT
GFP
L.MAC
ETH
Engine
M-ETH
GbE
PSN
ETH
Engine
Ethernet Traffic over PDH to SDH/SONET
Ethernet Traffic over PDH to TDM(E1/T1)
Figure 5-12. Services 10a,10b
Sections 5.3 to 5.21 summarize the steps required to configure selected services
shown in the above diagrams. For further details on a configuration step, refer to
the corresponding section indicated in the service provisioning table.
Note
• Applications in the following diagrams may be implemented in a different way;
Sections 5.3 to 5.21 just show typical service elements.
• The diagrams below display all possible protection alternatives. In most cases
there is no need to configure all of them and it is recommended to select the
one most suitable for your application.
4.3
E1/T1 Traffic to SDH/SONET via Direct
Transparent Mapping (1a)
Figure 5-13 illustrates an E1/T1 to SDH/SONET service via direct transparent
mapping. This service is used for unframed E1/T1 ports of all I/O modules except
M8E1/M8T1. Table 5-3 details configuration steps needed for service
provisioning.
4-14
E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a)
Megaplex-4
Installation and Operation Manual
1. Define profiles
Chapter 4 Service Provisioning
vc profile
SDH/SONET Link
VC-12/VT1.5
E1/T1
I/O Module,
E1/T1 Port
Configure I/O
card e1/t1 port
Configure link
Set sdh-sonet link
parameters
2. Configure ports
Assign vc profile
for each aug/oc-3
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
4. Configure
protection
Configure aps
protection
Configure vc-path
protection
Legend:
Mandatory
Optional
Figure 5-13. E1/T1 to SDH/SONET Service via Direct Transparent Mapping
Megaplex-4
E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a)
4-15
Chapter 4 Service Provisioning
Installation and Operation Manual
Table 5-3. E1/T1 to SDH/SONET Service Provisioning – Direct Transparent Mapping
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to
E1-i/T1-i and AUG/OC-3 ports)
E1 Ports
port {e1 | t1}
Configuring physical E1/T1 ports of I/O module
port sdh-sonet
Configuring physical SDH/SONET ports
T1 Ports
ports
2. Configure
physical
1. Define
profiles
Sequence
SDH/SONET Ports
Selecting aug/oc3 group
3. Configure
crossconnections
SDH/SONET
Cross-Connect
cross-connect sdh-sonet
Cross-connecting between E1-i/T1-i ports and
VC-12/VT1.5 containers (CL.2 module)
3. Configure
protection
Assigning vc profile to aug/oc3
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.4
E1/T1 Traffic to SDH/SONET via DS0
Cross-Connect (1b)
Figure 5-14 illustrates an E1/T1 to SDH/SONET service via DS0 cross-connect. This
service is used for framed E1/T1 ports of all I/O modules and for unframed ports
of M8E1/M8T1 modules (M8E1/M8T1 do not support direct transparent mapping).
Table 5-4 details configuration steps needed for service provisioning.
4-16
E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b)
Megaplex-4
Installation and Operation Manual
1. Define profiles
Chapter 4 Service Provisioning
signaling
profile
vc profile
VC-12/VT1.5
SDH/SONET Link
E1/T1
CL.2 Module,
E1-i/T1-i Ports
E1/T1
Configure
e1-i/t1-i
parameters
Configure link
Set sdh-sonet
link parameters
Set e1-i/t1-i port
parameters
Assign vc profile
2. Configure ports for each aug/oc-3
Assign vc profile
I/O Module,
E1/T1 Port
Configure I/O
card serial port
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
Configure aps
protection
4. Configure
protection
Configure DS0
cross-connect
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-14. E1/T1 to SDH/SONET Service via DS0 Mapping
Table 5-4. E1/T1 to SDH/SONET Service Provisioning
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to
E1-i/T1-i and AUG/OC-3 ports)
Signaling Profiles
port signaling-profile
Configuring signaling profiles (to be assigned
to E1/T1 ports – M8E1/M8T1 modules only)
E1 Ports
port {e1 | t1}
Configuring physical E1/T1 ports of I/O module
port { e1-i | t1-i}
Configuring physical parameters of E1-i/T1-i
ports (CL.2 module)
T1 Ports
and logical ports
2. Configure physical
1. Define profiles
Sequence
E1 Ports
T1 Ports
Assigning vc profile
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
Selecting aug/oc3 group
Assigning vc profile to aug/oc3
Megaplex-4
E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b)
4-17
Chapter 4 Service Provisioning
4. Configure
protection
3. Configure crossconnections
Sequence
Installation and Operation Manual
Step
Commands
Comments
DS0 CrossConnect
cross-connect ds0
Cross-connecting between E1/T1 port of
M16E1/M16T1 module and e1-i/t1-i port of
CL.2 module
SDH/SONET
Cross-Connect
cross-connect sdh-sonet
Cross-connecting between E1-i/T1-i ports and
VC-12/VT1.5 containers (CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting E1/T1 service
APS Protection
protection aps
Protecting SDH/SONET links
4.5
E1 Traffic to SDH over Fiber via Direct
Transparent Mapping (2a)
Figure 5-15 illustrates an E1 to SDH over fiber service. This example is done via
direct transparent mapping since E1 links are framed. For unframed links you
must use DS0 cross-connect (as shown in Figure 5-1 and Figure 5-14 for M16E1).
Table 5-5 details configuration steps needed for service provisioning.
4-18
E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a)
Megaplex-4
Installation and Operation Manual
1. Define profiles
Chapter 4 Service Provisioning
vc profile
SDH Link
VC-12
E1
OP-108C
Module,
E1-i Port
Configure E1-i
port
Configure link
OP-108C
Module,
MUX-ETH-TDM
Port
Configure
mux-eth-tdm
port
Optimux-108
Configure E1 and
Fiber Optic ports
Set sdh link
parameters
2. Configure
ports
Assign vc profile
for each aug
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
Configure aps
protection
4. Configure
protection
Configure vc-path
protection
Legend:
Mandatory
Optional
Figure 5-15. E1 to SDH over Fiber Service via Direct Transparent Mapping
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to E1-i
and AUG ports)
E1 Ports
port e1 (<slot>/<port>/
<tributary>)
Configuring E1-i ports of I/O module
Mux-Eth-Tdm
Ports (Fiber Optic
Links of Optimux
Modules)
port mux-eth-tdm
Configuring Mux-Eth-Tdm ports of I/O module
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH ports
and logical ports
Step
2. Configure physical
Sequence
1. Define
profiles
Table 5-5. E1 to SDH over Fiber Service Provisioning
Selecting aug group
Assigning vc profile to aug
Megaplex-4
E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a)
4-19
Chapter 4 Service Provisioning
4. Configure
protection
Sequence
Installation and Operation Manual
Step
Commands
Comments
SDH/SONET
Cross-Connect
cross-connect sdh-sonet
Cross-connecting between E1 ports
(<slot>/<port>/<tributary>) and VC-12
containers (CL.2 module)
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH payload units
APS Protection
protection aps
Protecting SDH links
4.6
Fast Ethernet Traffic to PSN over Fiber (2b)
Figure 5-16 illustrates a Fast Ethernet to PSN over fiber service. Table 5-6 details
configuration steps needed for service provisioning.
1. Define profiles
classifier
profile
policer
profile
Flow 1a
Flow 1b
CL.2 Module,
GbE Port
Configure GbE
port
OP-108C
Module,
Int-Eth Port
OP-108C Module,
MUX-ETH-TDM
Port
Optimux-108
Configure int-eth
port
Configure
mux-eth-tdm
port
Configure
Ethernet and
Fiber Optic ports
Set Ethernet
port parameters
Set Mux-Eth-Tdm
port parameters
2. Configure ports
Assign policer
profile for remote
Optimux-108
3. Configure flows
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
Legend:
Mandatory
Optional
Figure 5-16. Fast Ethernet to PSN over Fiber Service
4-20
Fast Ethernet Traffic to PSN over Fiber (2b)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-6. Fast Ethernet to PSN over Fiber Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
remote Optimux Ethernet ports)
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from I/O port
Mux-Eth-Tdm
Ports (Fiber Optic
Links of Optimux
Modules)
port mux-eth-tdm
Configuring fiber optic ports of I/O module
and some remote device parameters (for
example, assigning policer profile)
User Ethernet
Ports
port ethernet
<slot>/<port>/<tributary>
Defining internal Ethernet ports of I/O module
User Ethernet
Ports
port ethernet
<slot>/<port>
Configuring physical GbE ports on the CL.2
module
Assigning policer profile
Flows
flows>flow
Define flow 1a:
•
egress port – GbE port of CL.2 module
•
ingress port – internal Ethernet port of
OP-108C module
Assign classifier profile
4. Configure flows
Define required VLAN editing actions:
•
match-all
•
push vlan <x>
•
p-bit fixed
Define flow 1b:
•
ingress port – GbE port of CL.2 module
•
egress port – internal Ethernet port of OP108C module
Assign classifier profile
Define required VLAN editing actions:
4.7
•
match vlan <x>
•
pop
Fast Ethernet Traffic to SDH/SONET (3)
Figure 5-17 illustrates a Fast Ethernet to SDH/SONET service. This service is
shown in Figure 5-2 on the example of ASMi-54C/N module. Table 5-7 details
configuration steps needed for service provisioning.
Megaplex-4
Fast Ethernet Traffic to SDH/SONET (3)
4-21
Chapter 4 Service Provisioning
1. Define profiles
Installation and Operation Manual
Classifier
profile
VC profile
SDH/SONET Link
VC-12/VT1.5
Policer profile
VCG Port
Flow 1a
Flow 1b
Logical
MAC
GFP Port
I/O Module,
Fast Ethernet
Port
Configure link
Configure VCG
port
Configure GFP
port
Set sdh-sonet
link parameters
Set vcg port
parameters
Set gfp port
parameters
Set Ethernet
port parameters
Assign vc
profile for each
aug/oc-3
Assign vc
profile
Bind vcg port
Assign policer
profile
Bind vc/vt
Assign vc
profile
2. Configure ports
Configure
Ethernet port
Define logical
mac port and
bind gfp port
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
3. Configure flows
4. Configure protection
Configure aps
protection
Configure vcpath protection
Configure
ethernet-group
protection
Legend:
Mandatory
Optional
Figure 5-17. Fast Ethernet to SDH/SONET Service
Table 5-7. Fast Ethernet to SDH/SONET Service Provisioning
1. Define profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC profiles (to be assigned to gfp,
vcg and aug/oc3 ports)
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Ethernet ports)
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from I/O port.
Fast Ethernet Ports
port ethernet
Configuring physical Ethernet ports of I/O
module
and logical ports
2. Configure physical
Assigning policer profile
Logical MAC Ports
port logical-mac
Defining logical MAC port to establish
connectivity between gfp and fast ethernet
ports.
GFP Ports
port gfp
Configuring physical parameters of GFP port
Assigning vc profile
Binding the corresponding VCG to the GFP port
When Ethernet service contains a single
VC-3/STS-1 or VC-12/VT1.5 container, the GFP
port can be bound to it directly
4-22
Fast Ethernet Traffic to SDH/SONET (3)
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
VCG Ports
port vcg
Configuring physical parameters of VCG port
Assigning vc profile
Binding the corresponding VC-4/STS-3c,
VC-3/STS-1 or VC-12/VT1.5 to the VCG
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
Selecting aug/oc3 group
Assigning vc profile to aug/oc3
Flows
flows>flow
Define unaware flows over EoS with n x
VC-12/VT1.5 and SP VLAN:
Define flow 1:
•
ingress port – I/O card ethernet port
•
egress port – logical-mac
Bind classifier profile
3. Configure flows
Define required VLAN editing actions:
•
match-all
•
push vlan <x>
•
p-bit fixed
Define flow 2:
•
ingress port –logical-mac,
•
egress port – I/O card port ethernet
Bind classifier profile
4. Configure
protection
Define required VLAN editing actions:
•
match vlan <x>
•
pop
Ethernet Group
Protection
protection ethernetgroup
Protecting Ethernet and packet traffic against
transmission failures on the SDH/SONET links
Path Protection for
SDH/SONET Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.8
Shared E-LAN Service with Multiple Drops per
Node over SDH/SONET
Figure 5-18 illustrates a shared E-LAN service with multiple drops per node over
SDH/SONET, schematically shown in Figure 5-3. Table 5-8 details configuration
steps needed for service provisioning.
Megaplex-4
Shared E-LAN Service with Multiple Drops per Node over SDH/SONET
4-23
Chapter 4 Service Provisioning
Installation and Operation Manual
WRED
Shaper
Queue
VC profile
Queue block
1. Define profiles
Classifier
Queue group
Marking
CL Bridge (1)
Flows
1a, 1b
Flow 3
SDH/SONET Link
SDH/SONET Link
VCG Port
VCG Port
VC-12/VT1.5
GFP Port
GFP Port
Logical
Logical
MAC
MAC
BP
Flow 2
2. Configure ports
Configure link
Configure VCG
port
Configure GFP
port
Set sdh-sonet
link parameters
Set vcg port
parameters
Set gfp port
parameters
Assign vc
profile for each
aug/oc-3
Assign vc
profile
Bind vcg port
Bind vc/vt
Assign vc
profile
M-ETH
Bridge BP
BP
BP
ERP
Bind
Bind
BP
M-ETH Module,
GbE Ports
BP
Define logical
mac port and
bind gfp port
Configure
Ethernet port
Bind queue
group profile
Set Ethernet
port parameters
Define a bridge
Define a bridge
Define bridge
ports
Define bridge
ports
3. Configure bridge and ERP
Bind to M-ETH
Ethernet port
Configure ERP
Configure flows
2,3
4. Configure flows
Legend:
Mandatory
Configure VLAN
membership
Define ERP
Define VLANs
Configure East
and West ports
Configure bridge
ports as VLAN
members
Configure RPL
owner
Configure MAC
table size
Configure flows
1a, 1b
Bind ingress and
egress ports
Assign ingress
and egress ports
Bind classifier
profile
Assign classifier
profile
Bind queue
mapping profile
Define vlan
editing actions
Bind queue
block instance
Optional
Figure 5-18. Shared E-LAN Service with Multiple Drops per Node over
SDH/SONET
Table 5-8. Shared E-LAN over SDH/SONET Service Provisioning
1. Define profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC profiles (to be assigned to gfp,
vcg and aug/oc3 ports)
Classifier Profiles
classifier-profile
Define classification profiles for Flows 1a, 1b
and bidirectional Flows 2 and 3.
Flows 1a, 1b:
•
Use “match all” setting
•
Push/pop Data VLAN of the ERP.
Flows 2 and 3: use “match all” setting.
Data VLAN is part of ERP definition.
4-24
Shared E-LAN Service with Multiple Drops per Node over SDH/SONET
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
Priority Queue
Mapping
queue-map-profile
Define profile for mapping CoS values to
queues.
Congestion
Avoidance (WRED)
wred-profile
Define WRED profiles to be attached to queue
profiles
Shaper
shaper-profile
Define shaper profiles to be attached to a
queue and queue group profiles
Queue Block
queue-block-profile
Define queue block profiles to be attached to
queue group profiles
Queue Group
queue-group-profile
Define queue group profile for GbE CL ports
Marking
marking-profile
Define profile for conversion of CoS and packet
color values into P-bit when push or mark tag
editing is used
Ethernet Ports
port ethernet
Configure physical parameters of GbE port
(M-ETH module)
Logical MAC Ports
port logical-mac
Define logical MAC ports to establish
connectivity between gfp ports of CL module
and bp ports of CL Bridge (1).
GFP Ports
port gfp
Configure physical parameters of GFP port
Assign vc profile
and logical ports
2. Configure physical
Bind the queue group profile intended for
Flows 2, 3 to Logical Mac port
Bind the corresponding VCG to the GFP port
When Ethernet service contains a single
VC-3/STS-1 or VC-12/VT1.5 container, the GFP
port can be bound to it directly
VCG Ports
port vcg
Configure physical parameters of VCG port
Assign vc profile
Bind the corresponding VC-4/STS-3c, VC-3/STS1 or VC-12/VT1.5 to the VCG
SDH/SONET Ports
port sdh-sonet
Configure physical SDH/SONET ports
Select aug/oc3 group
Assign vc profile to aug/oc3
bridge
3. Define
Bridge
Megaplex-4
bridge
Define, assign a number and configure bridge
entities:
•
M-ETH bridge (aware or unaware)
•
CL bridge (always aware) with VLAN table
where the Data VLAN of ERP is configured
with proper bridge ports
Shared E-LAN Service with Multiple Drops per Node over SDH/SONET
4-25
Chapter 4 Service Provisioning
Installation and Operation Manual
Comments
bridge
Define bridge ports
4. Define
bridge
ports
Commands
Bridge
5. Configure
VLAN
membership
Step
Bridge
bridge
Add VLANs, define bridge ports as VLAN
members and specify MAC table size for each
VLAN
6. Configure
ERP
Sequence
Bridge
protection
Define ERP, configure RPL owner, configure
East and West ports
Flows
flows>flow
Define the following flows:
7. Configure flows
M-ETH Bridge: Bind to M-ETH GbE ports
•
Flow 1a: ingress – BP (CL), egress –
BP (M-ETH)
•
Flow 1b: ingress – BP (M-ETH), egress –
BP (CL)
•
Flows 2,3: ingress – Logical Mac, egress –
BP
Define VLAN editing actions
Bind classifier profiles to all flows
Bind queue mapping profile to flows 2,3
Bind queue block instance to flows 2,3
Bind marking profile to flows 2, 3
4.9
E1 to SDH Traffic over Copper via DS0
Mapping (3a)
Figure 5-19 illustrates an E1 to SDH over copper service. This example is done via
DS0 mapping since E1 links are framed. Note that for unframed links you can use
direct transparent mapping as shown in Figure 5-4 and Figure 5-14 for M16E1.
Table 5-9 details configuration steps needed for service provisioning.
4-26
E1 to SDH Traffic over Copper via DS0 Mapping (3a)
Megaplex-4
Installation and Operation Manual
vc profile
1. Define profiles
VC-12
SDH Link
2. Configure
ports
Chapter 4 Service Provisioning
E1
E1
CL.2 Module,
E1-i Ports
Configure link
Configure
e1-i parameters
Set sdh link
parameters
Set e1-i port
parameters
Assign vc profile
for each aug
Assign vc profile
I/O Module,
E1-i Port
I/O Module,
SHDSL Port
ASMi Modem
Configure E1-i
port
Configure SHDSL
port
Configure E1 and
SHDSL ports
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
4. Configure
protection
Configure aps
protection
Configure vc-path
protection
Configure DS0
cross-connect
Configure
tdm-group
protection
Legend:
Mandatory
Optional
Figure 5-19. E1 to SDH over Copper Service via DS0 Mapping
Table 5-9. E1 to SDH over Copper Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to E1-i
and AUG ports)
E1 Ports
port e1-i
Configuring E1-i ports of I/O module
SHDSL Ports
port shdsl
Configuring SHDSL ports of I/O module
E1 Ports
port e1-i
Configuring E1-i ports (CL.2 module)
Assigning vc profile
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH ports
Selecting aug group
3.
Configu
re
cross-
Assigning vc profile to aug
Megaplex-4
DS0 CrossConnect
cross-connect ds0
Cross-connecting between E1-i port of
ASMi-54C/N module and E1-i port of CL.2
module
E1 to SDH Traffic over Copper via DS0 Mapping (3a)
4-27
Chapter 4 Service Provisioning
4. Configure
protection
Sequence
Installation and Operation Manual
Step
Commands
Comments
SDH/SONET
Cross-Connect
cross-connect sdh-sonet
Cross-connecting between E1-i ports and
VC-12 containers (CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting E1 service
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH payload units
APS Protection
protection aps
Protecting SDH links
4.10
Fast Ethernet Traffic to PSN over Copper (3b)
Figure 5-20 illustrates a Fast Ethernet to PSN over copper service. Table 5-10
details configuration steps needed for service provisioning.
1. Define profiles
classifier
profile
policer
profile
Flow 1a
Flow 1b
CL.2 Module,
GbE Port
Configure GbE
port
I/O Module,
PCS Port
I/O Module,
SHDSL Port
ASMi Modem
Define PCS port
and bind it to
SHDSL port
Configure
SHDSL port
Configure
Ethernet and
SHDSL ports
Set Ethernet
port parameters
2. Configure ports
3. Configure flows
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
Legend:
Mandatory
Optional
Figure 5-20. Fast Ethernet to PSN over Copper Service
4-28
Fast Ethernet Traffic to PSN over Copper (3b)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-10. Fast Ethernet to PSN over Copper Service Provisioning
and logical ports
2. Configure
physical
1. Define
profiles
Sequence
Step
Commands
Comments
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from I/O port
SHDSL Ports
port shdsl
Configuring SHDSL ports of I/O module
PCS Ports
port pcs
Configuring PCS ports of I/O module and
binding an SHDSL port to it
User Ethernet
Ports
port ethernet
Configuring physical GbE ports on the CL.2
module
Flows
flows>flow
Define flow 1a:
•
egress port – GbE port of CL.2 module
•
ingress port – PCS port of ASMi module
Assign classifier profile
4. Configure flows
Define required VLAN editing actions:
•
match-all
•
push vlan <x>
•
p-bit fixed
Define flow 1b:
•
ingress port – GbE port of CL.2 module
•
egress port – PCS port of ASMi module
Assign classifier profile
Define required VLAN editing actions:
4.11
•
match vlan <x>
•
pop
High-Speed Traffic to SDH/SONET (4)
Figure 5-21 illustrates a high-speed to SDH/SONET service. Table 5-11 details
configuration steps needed for service provisioning.
Megaplex-4
High-Speed Traffic to SDH/SONET (4)
4-29
Chapter 4 Service Provisioning
1. Define profiles
vc profile
SDH/SONET Link
2. Configure ports
Installation and Operation Manual
VC-12/VT1.5
E1/T1
CL.2 Module,
E1-i/T1-i Ports
Configure link
Configure
e1-i/t1-i parameters
Set sdh-sonet
link parameters
Set e1-i/t1-i
port parameters
Assign vc profile
for each aug/oc-3
Assign vc profile
Timeslots n*64
I/O Module,
Serial Port
Configure I/O
card serial port
3. Configure cross
connect
Configure
sdh-sonet cross
connect
4. Configure
protection
Configure aps
protection
Configure vc-path
protection
Configure ds0
cross connect
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-21. High-Speed to SDH/SONET Service
4-30
High-Speed Traffic to SDH/SONET (4)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-11. High-Speed to SDH/SONET Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to E1i/T1-i and AUG/OC-3 ports)
Serial Ports
port serial
Configuring physical serial ports of I/O module
E1 Ports
port { e1-i | t1-i}
Configuring physical parameters of E1-i/T1-i
ports (CL.2 module)
T1 Ports
Assigning vc profile
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
Selecting aug/oc3 group
3. Configure
protection
3. Configure timeslot
cross-connections
Assigning vc profile to aug/oc3
DS0 cross-connect
cross-connect ds0
Cross-connecting between serial ports of highspeed module and timeslots of e1-i/t1-i ports
of CL.2 module
SDH/SONET
cross-connect
cross-connect sdh-sonet
Cross-connecting between timeslots of
E1-i/T1-i ports and VC-12/VT1.5 containers
(CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting E1/T1 service
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.12
High-Speed Traffic to PSN (4a, 4b)
Figure 5-22 illustrates in detail high-speed to PSN (Ethernet) services
schematically shown in Figure 5-4:
•
Service 4a: The traffic from serial port is forwarded to Ethernet port, which
serves as a pseudowire exit port toward the PSN.
•
Service 4b: The traffic from serial port is forwarded to GbE port, which serves
as a pseudowire exit port toward the PSN.
These services use the pseudowire engine of the MPW-1 module. Table 5-12
details configuration steps needed for service provisioning.
Megaplex-4
High-Speed Traffic to PSN (4a, 4b)
4-31
Chapter 4 Service Provisioning
1. Define profiles
classifier
profile
Installation and Operation Manual
policer
profile
MPW-1/FE Port or
CL.2/GbE port
Flow 1a
Flow 1b
SVI
RIF
PW
Router
PW
MPW-1 Module, TS x 64 kbps
DS1 Ports
Configure I/O
card serial port
Configure ds1
port
Configure
ethernet port
I/O Module,
Serial Port
Set Ethernet
port parameters
2. Configure ports
Assign policer
profile
Define SVI port
3. Define SVI
Define RIFs
Define router
interfaces
4. Define and bind
router interfaces
Bind router
interfaces to
SVIs
Add static
routing table
5. Define PW peer
Add and configure
a pseudowire
6. Add a pseudowire
Configure ds0
cross-connect
Configure pw-tdm
cross-connect
7. Configure
cross-connections
8. Configure flows
Define remote
PW peer
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
ingress and
egress ports
Define vlan
editing
actions
Define vlan
editing
actions
Assign
classifier
profile
9. Configure
protection
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-22. High-Speed to Ethernet Service
4-32
High-Speed Traffic to PSN (4a, 4b)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-12. High-Speed to Fast Ethernet Service Provisioning
and logical ports
Step
Commands
Comments
Defining Classifier
Profiles
flows flow classifierprofile
Create classifier profile “match-all”
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Fast Ethernet ports)
Serial Ports
port serial
Configuring physical parameters of serial ports
of I/O module
DS1 Ports
port ds1
Configuring physical parameters of DS1 ports
(MPW-1 module)
Ethernet Ports
port ethernet
Configuring physical parameters of Fast
Ethernet port (MPW-1 module, Service 4a) or
GbE port (CL.2 module, Service 4b)
Switched Virtual
Interface
port svi
Define an SVI port.
Keep in mind that PW SVI represents untagged
traffic termination point. This means that VLAN
tags must be pushed on exiting it and popped
on the flows terminating at SVI.
Pseudowire Router
router (2)
Add interfaces to the router
Define static routing table
Bind the RIFs to the SVIs
Peer
peer
Configure remote pseudowire peer
Pseudowires
pwe
Add and configure pseudowires
6. Define
pseudowire
5. Define PW peer
4. Add RIFs and
bind them to
SVIs
3. Define SVIs
2. Configure physical
1. Define profiles
Sequence
Megaplex-4
High-Speed Traffic to PSN (4a, 4b)
4-33
Chapter 4 Service Provisioning
Step
Commands
Comments
DS0 Cross-connect
cross-connect ds0
Cross-connecting between serial ports of
high-speed module and timeslots of DS1 ports
of MPW-1 module
PW-TDM
Cross-connect
cross-connect pw-tdm
Cross-connecting between timeslots of DS1
ports and PW (MPW-1 module)
Flows
flows>flow
Define two flows:
8. Configure flows
7. Configure cross-connections
Sequence
Installation and Operation Manual
•
Flow 1a: ingress – SVI, egress – Ethernet
port of MPW-1 module
•
Flow 1b: ingress – Ethernet port of MPW-1
module, egress –SVI
Assign classifier profile to flows 1a and 1b
9. Configure
protection
Define VLAN editing actions
TDM Group
Protection
4.13
protection tdm-group
Protecting E1/T1 service
Low-Latency High-Speed Traffic to PSN (4c,
4d)
Figure 5-23 illustrates in detail low-latency high-speed to PSN (Ethernet) services
using the pseudowire engine of RAD’s versatile VS modules, schematically shown
in Figure 5-6:
•
Service 4d: The traffic from serial port is forwarded to Ethernet port, which
serves as a pseudowire exit port toward the PSN.
•
Service 4e: The traffic from serial port is forwarded to GbE port, which serves
as a pseudowire exit port toward the PSN.
The VS modules providing these services have two advantages over the legacy
modules:
4-34
•
No additional MPW-1 module is needed to perform cross-connect
•
The cross-connect is latency-optimized due to the absence of additional ds0
cross-connect in the middle.
Low-Latency High-Speed Traffic to PSN (4c, 4d)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
However, cross-connection of multiple ports has to be done via ds0 ports.
Service 4f shown in Figure 5-6 is the same as Service 4 in Figure 5-4.
Table 5-13 details configuration steps needed for service provisioning.
1. Define profiles
classifier
profile
policer
profile
CL.2/GbE or
any FE
port
Flow 1a
Flow 1b
SVI
RIF
TS x 64 kbps
VS Module,
PW
PW
Router
VS Module,
Serial Port
Configure I/O
card serial port
Configure
ethernet port
Set Ethernet
port parameters
2. Configure ports
Assign policer
profile
Define SVI port
3. Define SVI
Define RIFs
Define router
interfaces
4. Define and bind
router interfaces
Bind router
interfaces to
SVIs
Add static
routing table
5. Define PW peer
Add and configure
a pseudowire
6. Add a pseudowire
Configure pw-tdm
cross-connect
7. Configure
cross-connections
8. Configure flows
9. Configure
protection
Define remote
PW peer
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
ingress and
egress ports
Define vlan
editing
actions
Define vlan
editing
actions
Assign
classifier
profile
Configure pwtdm protection
Legend:
Mandatory
Optional
Figure 5-23. Low-Latency High-Speed to Ethernet Service
Megaplex-4
Low-Latency High-Speed Traffic to PSN (4c, 4d)
4-35
Chapter 4 Service Provisioning
Installation and Operation Manual
Table 5-13. Low-Latency High-Speed to Fast Ethernet Service Provisioning
and logical ports
Step
Commands
Comments
Defining Classifier
Profiles
flows flow classifierprofile
Create classifier profile “match-all”
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Fast Ethernet ports)
Serial Ports
port serial
Configuring physical parameters of serial ports
of I/O module
Ethernet Ports
port ethernet
Configuring physical parameters of Fast
Ethernet port (Service 4d) or GbE port (CL.2
module, Service 4e)
Switched Virtual
Interface
port svi
Define an SVI port.
Pseudowire Router
router (2)
Keep in mind that PW SVI represents untagged
traffic termination point. This means that VLAN
tags must be pushed on exiting it and popped
on the flows terminating at SVI.
Add interfaces to the router
Define static routing table
Bind the RIFs to the SVIs
Peer
peer
Configure remote pseudowire peer
Pseudowires
pwe
Add and configure pseudowires
PW-TDM
Cross-connect
cross-connect pw-tdm
Cross-connecting between serial ports of
high-speed module and PW
7. Configure
cross-connections
6. Define
pseudowire
5. Define PW peer
4. Add RIFs and
bind them to
SVIs
3. Define SVIs
2. Configure
physical
1. Define profiles
Sequence
4-36
Low-Latency High-Speed Traffic to PSN (4c, 4d)
Megaplex-4
Installation and Operation Manual
Step
Commands
Comments
Flows
flows>flow
Define two flows:
8. Configure flows
Sequence
Chapter 4 Service Provisioning
•
Flow 1a: ingress – SVI, egress – Fast
Ethernet port of I/O module
•
Flow 1b: ingress – Ethernet port of I/0
module, egress –SVI
Assign classifier profile to flows 1a and 1b
9. Configure
protection
Define VLAN editing actions
PW Protection
4.14
protection pw
Protecting PW service
High-Speed Service Aggregation into PSN
Backbone with G.8032 Protection
Figure 5-24 illustrates in detail high-speed service aggregation into PSN backbone
with G.8032 protection (schematically shown in Figure 5-5). In this application,
the traffic from serial port is forwarded to GbE port, which serves as a
pseudowire exit port toward the PSN.
These services use the pseudowire engine of the MPW-1 module. Table 5-14
details configuration steps needed for service provisioning.
Megaplex-4
High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
4-37
Chapter 4 Service Provisioning
Installation and Operation Manual
WRED
Shaper
Queue
Shaper
Queue block
L2CP
1. Define profiles
CL.2/GbE port
Classifier
Queue group
Policer
Marking
Flows
1a, 1b
Flow 3
BP
Bridge
SVI
RIF
BP
CL.2/GbE port
PW
Router
PW
MPW-1 Module,
DS1 Ports
TS x 64 kbps
I/O Module,
Serial Port
Flow 2
ERP
BP
Configure
ethernet port
2. Configure ports
Configure I/O
card serial port
Configure ds1
port
Configure
physical layer
Define
classifier
(“match-all”)
Bind L2CP
profile
Bind queue
group profile
Define SVI port
3. Define SVI
Define RIFs
4. Define and bind router interfaces
Define router
interfaces
Bind router
interfaces to
SVIs
Add static
routing table
Define remote
PW peer
5. Define PW peer
Add and configure
a pseudowire
6. Add a pseudowire
Configure pw-tdm
cross-connect
7. Configure cross-connections
8. Define a bridge
Configure ds0
cross-connect
Define a bridge
Define bridge ports
9. Define bridge ports
Configure ERP
Configure VLAN
membership
10. Configure VLAN membership and ERP
12. Configure flows
Define ERP
Define VLANs
Configure East
and West ports
Configure bridge
ports as VLAN
members
Configure RPL
owner
Configure MAC
table size
Configure flows 2,3
Configure flow 1
Bind ingress and
egress ports
Bind ingress and
egress ports
Bind L2CP
profile
Bind classifier
profile
Bind classifier
profile
Define VLAN
editing actions
Bind policer
profile
Legend:
Mandatory
Optional
Bind queue
mapping profile
Bind queue
block instance
Figure 5-24. High-Speed Service Aggregation into PSN Backbone with G.8032
Protection
4-38
High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-14. High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
and logical ports
2. Configure physical
1. Define profiles
Sequence
Step
Commands
Comments
Classifier Profiles
classifier-profile
Define classification profiles for Flows 1a, 1b
and Flows 2 and 3). Use “match all” setting for
Flows 1a, 2 and 3. For Flow 1b, define classifier
for the VLAN pushed in Flow 1a.
Policing
policer-profile
Create a policer bandwidth profile with
required CIR, CBS, EIR, EBS values. Not relevant
for flow 1.
Layer 2 Control
Protocol (L2CP)
l2cp-profile
Define policy for L2CP traffic handling by port
and/or flow (peer, tunnel or drop)
Priority Queue
Mapping
queue-map-profile
Define profile for mapping CoS values to
queues.
Congestion
Avoidance (WRED)
wred-profile
Define WRED profiles to be attached to queue
profiles
Shaper
shaper-profile
Define shaper profiles to be attached to a
queue and queue group profiles
Queue Block
queue-block-profile
Define queue block profiles to be attached to
queue group profiles
Queue Group
queue-group-profile
Define queue group profile for Gbe CL ports
Marking
marking-profile
Define profile for conversion of CoS and packet
color values into P-bit when push or mark tag
editing is used. Not relevant for flow 1.
Serial Ports
port serial
Configure physical parameters of serial ports of
I/O module
DS1 Ports
port ds1
Configure physical parameters of DS1 ports
(MPW-1 module)
Ethernet Ports
port ethernet
Configure physical parameters of GbE port
(CL.2 module)
Bind previously created L2CP profile
3. Define SVIs
Bind the queue group profile intended for
flows 2. 3 to GbE port
Megaplex-4
Switched Virtual
Interface
port svi
Define an SVI port.
Keep in mind that PW SVI represents untagged
traffic termination point. This means that VLAN
tags must be pushed on exiting it and popped
on the flows terminating at SVI.
High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
4-39
Installation and Operation Manual
Sequence
Step
Commands
Comments
4. Add RIFs and
bind them to
SVIs
Chapter 4 Service Provisioning
Pseudowire Router
router (2)
Add interfaces to the router
Define static routing table
peer
Configure remote pseudowire peer
Pseudowires
pwe
Add and configure pseudowires
DS0 Cross-connect
cross-connect ds0
Cross-connecting between serial ports of
high-speed module and timeslots of DS1 ports
of MPW-1 module
PW-TDM
Cross-connect
cross-connect pw-tdm
Cross-connecting between timeslots of DS1
ports and PW (MPW-1 module)
Bridge
bridge
Define, assign a number and configure a bridge
entity
9. Define
bridge ports
Bridge
bridge
Define bridge ports
10. Configure
VLAN
membership
Bridge
bridge
Add VLANs, define bridge ports as VLAN
members and specify MAC table size for each
VLAN
Protection
protection
Define ERP, configure RPL owner, configure
East and West ports
4-40
bridge
8. Define
7. Configure
cross-connections
6. Define
pseudowire
5. Define PW
peer
Peer
11. Configure
ERP
Bind the RIFs to the SVIs
High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
Megaplex-4
Installation and Operation Manual
Step
Commands
Comments
Flows
flows>flow
Define the following flows:
12. Configure flows
Sequence
Chapter 4 Service Provisioning
•
Flow 1a: ingress – SVI, egress – BP
•
Flow 1b: ingress – BP, egress – SVI
•
Flows 2,3: ingress – GBE, egress – BP
Define VLAN editing actions
Bind L2CP profile to flows 2,3
Bind classifier profiles to all flows
Bind policer profile to flows 2,3
Bind queue mapping profile to flows 2,3
Bind queue block instance to flows 2,3
Define required VLAN editing actions for flow 1
Bind marking profile to flows 2, 3
4.15
Fast Ethernet Traffic to E1/T1 (HDLC Protocol)
(5a)
Figure 5-25 illustrates a Fast Ethernet to E1/T1 service. This service is shown in
Figure 5-4 on the example of M8E1 module. Table 5-15 details configuration
steps needed for service provisioning.
Megaplex-4
Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a)
4-41
Chapter 4 Service Provisioning
1. Define profiles
Installation and Operation Manual
Policer profile
Classifier
profile
E1/T1 Port
HDLC Port
Configure HDLC
port
Configure E1/T1
Port
Logical
MAC
Flow 1a
Flow 1b
I/O Module,
Fast Ethernet
Port
Configure
Ethernet port
Define logical
mac port and
bind hdlc port
Set Ethernet
port parameters
Assign policer
profile
2. Configure ports
3. Configure
cross-connections
Configure ds0
cross-connect
4. Configure flows
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
Configure tdmgroup protection
5. Configure protection
Legend:
Mandatory
Optional
Figure 5-25. Fast Ethernet to E1/T1 Service (HDLC Protocol)
As per the figure 5-25, 3rd point is to configure DS0 cross-connect, however in
service provisioning table 3rd point is mentioned as configure flows instead of
DS0 cross-connect. DS0 configuration table is not mentioned.
Table 5-15. Fast Ethernet to E1/T1 Service Provisioning (HDLC Protocol)
1. Define
profiles
Sequence
4-42
Step
Commands
Comments
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Ethernet ports)
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from I/O port.
Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a)
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
Fast Ethernet Ports
port ethernet
Configuring physical Ethernet ports of I/O
module
and logical ports
3. Configure
cross-connections
2. Configure physical
Assigning policer profile
Logical MAC Ports
port logical-mac
Defining logical MAC port to establish
connectivity between hdlc and fast ethernet
ports.
Binding HDLC port to Logical MAC
HDLC Ports
port hdlc
Configuring parameters of HDLC port
E1/T1 Ports
port {e1 | t1}
Configuring physical E1/T1 ports
DS0 Cross-connect
cross-connect ds0
Cross-connecting between HDLC ports and
timeslots of E1/T1 ports
Flows
flows>flow
Define unaware flows over EoS with n x
VC-12/VT1.5 and SP VLAN:
Define flow 1:
•
ingress port – I/O card ethernet port
•
egress port – logical-mac
Assign classifier profile
4. Configure flows
Define required VLAN editing actions:
•
match-all
•
push vlan <x>
•
p-bit fixed
Define flow 2:
•
ingress port –logical-mac,
•
egress port – I/O card port ethernet
Assign classifier profile
5.
Configure
protection
Define required VLAN editing actions:
Megaplex-4
TDM Group
Protection
protection tdm-group
•
match vlan <x>
•
pop
Protecting E1/T1 links
Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a)
4-43
Chapter 4 Service Provisioning
4.16
Installation and Operation Manual
Fast Ethernet Traffic to Multiple E1 (MLPPP
Protocol) (5b)
Figure 5-26 illustrates a Fast Ethernet to multiple E1 service. This service is shown
in Figure 5-4 on the example of M8E1 module. Table 5-16 details configuration
steps needed for service provisioning.
Classifier
profile
1. Define profiles
Policer profile
E1 Port
PPP Port
Configure E1
Port
Configure PPP
port
Set E1
parameters
Define ppp
port
Up to 8 PPP
Ports
Flow 1a
Flow 1b
Logical
MAC
MLPPP Port
Configure
MLPPP port
I/O Module,
Fast Ethernet
Port
Configure
Ethernet port
Define logical
mac port and
bind mlppp port
Set mlppp port
parameters
Set Ethernet
port parameters
Bind ppp port
Assign policer
profile
Bind e1 port
2. Configure ports
3. Configure flows
4. Configure protection
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-26. Fast Ethernet to Multiple E1 Service (MLPPP Protocol)
Table 5-16. Fast Ethernet to E1/T1 Service Provisioning (MLPPP Protocol)
4-44
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Ethernet ports)
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from I/O port.
Fast Ethernet Ports
port ethernet
Configuring physical Ethernet ports of I/O
module
Assigning policer profile
Logical MAC Ports
port logical-mac
Defining logical MAC port to establish
connectivity between mlppp and fast ethernet
ports.
Binding MLPPP port to Logical MAC
Fast Ethernet Traffic to Multiple E1 (MLPPP Protocol) (5b)
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
MLPPP Ports
port mlppp
Configuring physical parameters of the MLPPP
port
Binding the PPP port to the MLPPP port
PPP Ports
port ppp
Defining and binding the PPP port to the E1
physical port of a M8E1 module
E1 Ports
port e1
Configuring physical E1 ports
Flows
flows>flow
Define unaware flows over EoS with n x
VC-12/VT1.5 and SP VLAN:
Define flow 1:
•
ingress port – I/O card ethernet port
•
egress port – logical-mac
Bind classifier profile
3. Configure flows
Define required VLAN editing actions:
•
match-all
•
push vlan <x>
•
p-bit fixed
Define flow 2:
•
ingress port –logical-mac,
•
egress port – I/O card port ethernet
Bind classifier profile
4. Configure
protection
Define required VLAN editing actions:
TDM Group
Protection
4.17
protection tdm-group
•
match vlan <x>
•
pop
Protecting E1/T1 links
Voice Traffic to SDH/SONET (6)
Figure 5-27 illustrates voice to SDH/SONET service. Table 5-17 details
configuration steps needed for service provisioning.
Megaplex-4
Voice Traffic to SDH/SONET (6)
4-45
Chapter 4 Service Provisioning
vc profile
1. Define profiles
SDH/SONET Link
2. Configure ports
Installation and Operation Manual
E1/T1
VC-12/VT1.5
Voice
CL.2 Module,
E1-i/T1-i Ports
Configure link
Configure
e1-i/t1-i parameters
Set sdh-sonet
link parameters
Set e1-i/t1-i
port parameters
Assign vc profile
for each aug/oc-3
Assign vc profile
I/O Module,
Voice Port
Configure I/O
card voice port
3. Configure cross
connect
Configure
sdh-sonet cross
connect
4. Configure
protection
Configure aps
protection
Configure vc-path
protection
Configure ds0
cross connect
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-27. Voice to SDH/SONET Service
Table 5-17. Voice to SDH/SONET Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to
E1-i/T1-i and AUG/OC-3 ports)
Voice Ports
port voice
Configuring physical voice ports of I/O module
E1 Ports
port { e1-i | t1-i}
Configuring physical parameters of E1-i/T1-i
ports (CL.2 module)
T1 Ports
Assigning vc profile
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
Selecting aug/oc3 group
Assigning vc profile to aug/oc3
4-46
Voice Traffic to SDH/SONET (6)
Megaplex-4
Installation and Operation Manual
3. Configure
protection
3. Configure timeslot
cross-connections
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
DS0 cross-connect
cross-connect ds0
Cross-connecting between serial ports of highspeed module and timeslots of e1-i/t1-i ports
of CL.2 module
SDH/SONET
cross-connect
cross-connect sdh-sonet
Cross-connecting between timeslots of
E1-i/T1-i ports and VC-12/VT1.5 containers
(CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting E1/T1 service
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.18
Voice Traffic to PSN (6a)
Figure 5-22 illustrates in detail high-speed to PSN (Ethernet) services
schematically shown in Figure 5-4:
•
Service 6a: The traffic from voice port is forwarded to GbE port, which serves
as a pseudowire exit port toward the PSN.
These services use the pseudowire engine of the VS voice module. Table 5-12
details configuration steps needed for service provisioning.
Megaplex-4
Voice Traffic to PSN (6a)
4-47
Chapter 4 Service Provisioning
1. Define profiles
classifier
profile
Installation and Operation Manual
policer
profile
CL.2/GbE
port
Flow 1a
Flow 1b
SVI
RIF
PW
Router
PW
Configure
ethernet port
VS Voice
Module,
DS1 Ports
Configure ds1
port
64 kbps
VS Voice Module,
Voicel Port
Configure I/O card
voice port
Set Ethernet
port parameters
2. Configure ports
Assign policer
profile
Define SVI port
3. Define SVI
Define RIFs
Define router
interfaces
4. Define and bind
router interfaces
Bind router
interfaces to
SVIs
Add static
routing table
5. Define PW peer
Add and configure
a pseudowire
6. Add a pseudowire
Configure pw-tdm
cross-connect
DS1/PW 1:1
7. Configure
cross-connections
8. Configure flows
Define remote
PW peer
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
ingress and
egress ports
Define vlan
editing
actions
Define vlan
editing
actions
Configure ds0
cross-connect
Assign
classifier
profile
Legend:
Mandatory
Optional
Figure 5-28. Voice to Ethernet Service
4-48
Voice Traffic to PSN (6a)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Table 5-18. Voice to Ethernet Service Provisioning
and logical ports
6. Define
pseudowire
5. Define PW peer
4. Add RIFs and
bind them to
SVIs
3. Define SVIs
2. Configure physical
1. Define profiles
Sequence
Megaplex-4
Step
Commands
Comments
Defining Classifier
Profiles
flows flow classifierprofile
Create classifier profile “match-all”
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Fast Ethernet ports)
Voice Ports
port voice
Configuring physical parameters of voice ports
of I/O module
DS1 Ports
port ds1
Configuring physical parameters of DS1 ports
(I/O module)
Ethernet Ports
port ethernet
Configuring physical parameters of GbE port
(CL.2 module, Service 6a)
Switched Virtual
Interface
port svi
Define an SVI port.
Keep in mind that PW SVI represents untagged
traffic termination point. This means that VLAN
tags must be pushed on exiting it and popped
on the flows terminating at SVI.
Pseudowire Router
router (2)
Add interfaces to the router
Define static routing table
Bind the RIFs to the SVIs
Peer
peer
Configure remote pseudowire peer
Pseudowires
pwe
Add and configure pseudowires.
Voice channels are sharing same PW.
Voice Traffic to PSN (6a)
4-49
Chapter 4 Service Provisioning
Step
Commands
Comments
DS0 Cross-connect
cross-connect ds0
Cross-connecting between voice ports and
timeslots of DS1 ports of VS voice module
PW-TDM
Cross-connect
cross-connect pw-tdm
Cross-connecting between timeslots of DS1
ports and PW
Flows
flows>flow
Define two flows:
8. Configure flows
7. Configure cross-connections
Sequence
Installation and Operation Manual
•
Flow 1a: ingress – SVI, egress – Fast
Ethernet port of I/O module
•
Flow 1b: ingress – Ethernet port of I/0
module, egress –SVI
Assign classifier profile to flows 1a and 1b
Define VLAN editing actions
4.19
Teleprotection Traffic to SDH/SONET (7)
Figure 5-29 illustrates teleprotection over SDH/SONET service. Table 5-19 details
configuration steps needed for service provisioning.
4-50
Teleprotection Traffic to SDH/SONET (7)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
vc profile
I/O Module,
CMD-IN-I Ports
1. Define profiles
2. Configure ports
E1/T1
VC-12/VT1.5
SDH/SONET Link
64/128 kbps
CL.2 Module,
E1-i/T1-i Ports
Configure link
Configure
e1-i/t1-i parameters
Set sdh-sonet
link parameters
Set e1-i/t1-i
port parameters
Assign vc profile
for each aug/oc-3
Assign vc profile
I/O Module,
CMD Channel
Ports
Configure cmdchannel port
Configure
cmd-in-i port
I/O Module,
CMD-IN Ports
Configure cmd-in
port
Set cmd-in-i
port parameters
Bind cmd-in
port
I/O Module,
CMD-OUT-I
Ports
I/O Module,
CMD-OUT Ports
Configure
cmd-out-i port
Configure cmdout port
Set cmd-out
port parameters
Bind cmd-out-i
port
3. Configure cross
connect
Configure
sdh-sonet cross
connect
4. Configure
protection
Configure aps
protection
Configure vc-path
protection
Configure TP
cross connect
Configure ds0
cross connect
Configure tdmgroup protection
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-29. Teleprotection Service
Table 5-19. TP to SDH/SONET Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Megaplex-4
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to
E1-i/T1-i and AUG/OC-3 ports)
CMD-IN Ports
port cmd-in
Configuring cmd-in ports
CMD-IN-I Ports
port cmd-in-i
Configuring cmd-in-i ports
Binding the cmd-in port to the cmd-in-i port
CMD-OUT Ports
port cmd-out
Configuring cmd-out ports
Binding the cmd-out-i port to the cmd-out
port
CMD-OUT-I Ports
port cmd-out-i
Configuring cmd-out-i ports
CMD-CHANNEL
Ports
port cmd-channel
Configuring cmd channels
Teleprotection Traffic to SDH/SONET (7)
4-51
Chapter 4 Service Provisioning
Sequence
Installation and Operation Manual
Step
Commands
Comments
E1 Ports
port {e1-i | t1-i}
Configuring physical parameters of E1-i/T1-i
ports (CL.2 module)
T1 Ports
Assigning vc profile
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
Selecting aug/oc3 group
3. Configure
protection
3. Configure
timeslot crossconnections
Assigning vc profile to aug/oc3
DS0 cross-connect
cross-connect ds0
Cross-connecting between the cmd-channel
and timeslots on the E1/T1 ports of the uplink
module
SDH/SONET
cross-connect
cross-connect sdh-sonet
Cross-connecting between timeslots of
E1-i/T1-i ports and VC-12/VT1.5 containers
(CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting E1/T1 service
Path Protection
for SDH/SONET
Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.20
Protecting CMD channels
T3 Traffic to SONET (8)
Figure 5-30 illustrates a T3 to SONET service using T3 module. Table 5-20 details
configuration steps needed for service provisioning.
4-52
T3 Traffic to SONET (8)
Megaplex-4
Installation and Operation Manual
1. Define profiles
Chapter 4 Service Provisioning
vc profile
SONET Link
VT1.5
T1
T3 Module,
T1 Ports
Configure link
Configure
t1 parameters
Set sdh-sonet
link parameters
Set t1 port
parameters
Fixed
connection
T3 I/O Module,
T3 Port
Configure I/O
card T3 port
Assign vc profile
2. Configure ports for each aug/oc-3
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
Configure aps
protection
4. Configure
protection
Configure tdmgroup protection
Legend:
Mandatory
Optional
Figure 5-30. T3 to SDH/SONET Service
Table 5-20. T3 to SDH/SONET Service Provisioning
and logical ports
2. Configure physical
1. Define
profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC Profiles (to be assigned to OC-3
ports)
T1 Ports
configure port e1-t1 t1
Configuring parameters of T1 ports (T3
module)
T3 Ports
configure port e3-t3 t3
Configuring physical T3 ports
SONET Ports
port sdh-sonet
Configuring physical SONET ports
Selecting oc3 group
Assigning vc profile to oc3
Megaplex-4
T3 Traffic to SONET (8)
4-53
Installation and Operation Manual
Step
Commands
Comments
SDH/SONET
Cross-Connect
cross-connect sdh-sonet
Cross-connecting between T1 ports (T3
module) and VT1.5 containers (CL.2 module)
TDM Group
Protection
protection tdm-group
Protecting T3 and T1 services
APS Protection
protection aps
Protecting SDH/SONET links
4. Configure
protection
Sequence
3. Configure
crossconnections
Chapter 4 Service Provisioning
4.21
Voice to T3 via DS0 Cross-Connect (9)
Figure 5-31 illustrates a voice to T3 service via DS0 cross-connect. Table 5-21
details configuration steps needed for service provisioning.
T3 Module,
T3 Port
Fixed
connection
T3 Module,
T1 Ports
Configure t3 port
Configure
t1 parameters
Set t3 link
parameters
Set t1 port
parameters
I/O Module,
Voice Port
Configure I/O
card voice port
1. Configure ports
2. Configure
cross-connect
Configure DS0
cross-connect
Configure
tdm-group
protection
Configure
tdm-group
protection
3. Configure
protection
Legend:
Mandatory
Optional
Figure 5-31. Voice Aggregation to T3 Link
4-54
Voice to T3 via DS0 Cross-Connect (9)
Megaplex-4
Installation and Operation Manual
Chapter 4 Service Provisioning
Step
Commands
Comments
1. Configure physical
Voice Ports
configure port voice
Configuring physical voice ports of I/O module
T1 Ports
configure port e1-t1 t1
Configuring parameters of internal T1 ports
(T3 module)
T3 Ports
configure port e3-t3 t3
Configuring physical T3 ports
2.
Configure
crossconnection
DS0 CrossConnect
cross-connect ds0
Cross-connecting between the voice port of VC
module and internal T1 port of T3 module
TDM Group
Protection
protection tdm-group
Protecting T3 ports
TDM Group
Protection
protection tdm-group
Protecting T1 ports
And logical ports
Sequence
3. Configure protection
Table 5-21. Voice Aggregation to T3 Link Provisioning
4.22
Ethernet Traffic over PDH to SDH/SONET (10a)
Figure 5-32 illustrates an Ethernet traffic over PDH to SDH/SONET service. This
service is shown in Figure 5-12 on the example of VS-16E1T1-EoP module.
Table 5-22 details configuration steps needed for service provisioning.
Megaplex-4
Ethernet Traffic over PDH to SDH/SONET (10a)
4-55
Chapter 4 Service Provisioning
1. Define profiles
Installation and Operation Manual
VC profile
SDH/SONET Link
Classifier
profile
VC-12/VT1.5 E1/T1
Configure link
Set sdh-sonet
link parameters
Policer profile
CL.2/GbE
port
VCG Port
GFP Port
Configure
e1-i/t1-i
parameters
Configure VCG
port
Configure GFP
port
Set vcg port
parameters
Set gfp port
parameters
Set Ethernet
port parameters
Assign vc
profile
Bind vcg port
Assign policer
profile
Bind vc/vt
Assign vc
profile
Set e1-i/t1-i port
parameters
Assign vc
profile for each
aug/oc-3
Flow 1a
Flow 1b
Logical
MAC
E1-i/T1-i Port
Assign vc profile
2. Configure ports
Configure
Ethernet port
Define logical
mac port and
bind gfp port
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
Configure flow
1a
Configure flow
1b
Assign
ingress and
egress ports
Assign
ingress and
egress ports
Assign
classifier
profile
Assign
classifier
profile
Define vlan
editing
actions
Define vlan
editing
actions
4. Configure flows
5. Configure protection
Configure aps
protection
Configure vcpath protection
Legend:
Mandatory
Optional
Figure 5-32. Ethernet traffic over PDH to SDH/SONET Service
Table 5-22. Ethernet traffic over PDH to SDH/SONET Service Provisioning
and logical ports
2. Configure physical
1. Define profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC profiles (to be assigned to gfp,
vcg and aug/oc3 ports)
Policer Profiles
qos policer-profile
Configuring policer profiles (to be assigned to
Ethernet ports)
Classifier Profiles
flows classifier-profile
Define classification profile for traffic
originating from the port.
Ethernet Ports
port ethernet
Configuring physical Ethernet ports CL.2 module
Logical MAC Ports
port logical-mac
Defining logical MAC port to establish
connectivity between gfp and ethernet ports.
GFP Ports
port gfp
Configuring physical parameters of GFP port
Binding the corresponding VCG to the GFP port
VCG Ports
4-56
port vcg
Ethernet Traffic over PDH to SDH/SONET (10a)
Configuring physical parameters of VCG port
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 4 Service Provisioning
Step
Commands
Comments
E1 Ports
port { e1-i | t1-i}
Configuring physical parameters of E1-i/T1-i
ports (VS-16E1T1-EoP module)
SDH/SONET Ports
port sdh-sonet
Configuring physical SDH/SONET ports
SDH/SONET
Cross-Connect
cross-connect sdhsonet
Cross-connecting between E1-i/T1-i ports (VS16E1T1-EoP module) and VC-12/VT1.5
containers
Flows
flows>flow
Define two flows:
5.
Configure
protectio
n
4. Configure flows
3. Configure
crossconnections
T1 Ports
•
Flow 1a: ingress – logical mac, egress –GbE
port of CL.2 modules
•
Flow 1b: ingress –GbE port of CL.2 modules,
egress –logical mac
Assign classifier profile to flows 1a and 1b
Define VLAN editing actions
Path Protection for
SDH/SONET Payload
protection vc-path
Protecting SDH/SONET payload units
APS Protection
protection aps
Protecting SDH/SONET links
4.23
Ethernet Traffic over PDH to E1/T1 (10b)
Figure 5-33 illustrates an Ethernet traffic over PDH to E1/T1 service. This service
is shown in Figure 5-12 on the example of VS-16E1T1-EoP module. Table 5-23
details configuration steps needed for service provisioning.
Megaplex-4
Ethernet Traffic over PDH to E1/T1 (10b)
4-57
Chapter 4 Service Provisioning
1. Define profiles
VC profile
Installation and Operation Manual
Classifier
profile
Flows
1a, 1b
VCG Port
E1/T1 Port
GFP Port
Logical
MAC
M-ETH
Bridge BP
BP
Bind
M-ETH Module,
GbE Ports
Bind
BP
Configure
e1/t1 port
2. Configure ports
Configure VCG
port
Configure GFP
port
Set vcg port
parameters
Set gfp port
parameters
Assign vc
profile
Bind vcg port
Bind e1/t1
port
Assign vc
profile
Define logical
mac port and
bind gfp port
Configure
Ethernet port
Set Ethernet
port parameters
Define a bridge
Define bridge
ports
Bind to M-ETH
Ethernet port
3. Configure bridge
Configure VLAN
membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
table size
Configure flows
1a, 1b
4. Configure flows
Assign ingress
and egress ports
Assign classifier
profile
Define vlan
editing actions
Legend:
Mandatory
Optional
Figure 5-33. Ethernet traffic over PDH to E1/T1 Service
Table 5-23. Ethernet traffic over PDH to E1/T1 Service Provisioning
4-58
and logical ports
2. Configure
physical
1. Define
profiles
Sequence
Step
Commands
Comments
VC Profiles
port vc-profile
Configuring VC profiles (to be assigned to gfp,
vcg and aug/oc3 ports)
Classifier Profiles
classifier-profile
Define classification profile for traffic
originating from the port.
Ethernet Ports
port ethernet
Configure physical parameters of GbE port
(M-ETH module)
Logical MAC Ports
port logical-mac
Define logical MAC ports to establish
connectivity between gfp ports of VS-16E1T1EoP module and bp ports of M-ETH Bridge.
Ethernet Traffic over PDH to E1/T1 (10b)
Megaplex-4
Installation and Operation Manual
Sequence
Chapter 5 Service Provisioning
Step
Commands
Comments
GFP Ports
port gfp
Configure physical parameters of GFP port
Assign vc profile
Bind the corresponding VCG to the GFP port
VCG Ports
port vcg
Configure physical parameters of VCG port
Assign vc profile
Bind the corresponding E1/T1 port to the VCG
E1 Ports
port { e1 | t1}
Configuring physical parameters of E1/T1 ports
(VS-16E1T1-EoP module)
bridge
Define, assign a number and configure bridge
entities:
T1 Ports
Bridge
•
bridge port
Define bridge ports
M-ETH Bridge: Bind to M-ETH GbE ports
bridge
4. Configure flows
3. Define
Bridge
M-ETH bridge
Bridge
bridge vlan
Add VLANs, define bridge ports as VLAN
members and specify MAC table size for each
VLAN
Flows
flows>flow
Define the following flows:
•
Flow 1a: ingress – Logical Mac (VS-16E1T1EoP), egress – BP (M-ETH)
•
Flow 1b: ingress – BP (M-ETH), egress –
Logical Mac (VS-16E1T1-EoP)
Define VLAN editing actions
Bind classifier profiles to all flows
Megaplex-4
Ethernet Traffic over PDH to E1/T1 (10b)
5-59
Chapter 5 Service Provisioning
5-60
Ethernet Traffic over PDH to E1/T1 (10b)
Installation and Operation Manual
Megaplex-4
Chapter 5
Cards and Ports
5.1
Cards
Cards (I/O modules) currently offered for Megaplex-4 are listed in Chapter 1,
Table 1-2.
Configuring Modules in the Chassis
Use the following procedure to program modules in the Megaplex-4 chassis. After
physical installation in the chassis, each module must be defined manually. The
system identifies module types, but powers the modules up and downloads
operation software only after modules are defined by the user. You can program
modules even if they are not installed in the chassis.
To program modules in the Megaplex-4 chassis:
1. Navigate to configure slot <slot>.
The config>slot<slot># prompt is displayed.
2. Use the card-type command to perform the tasks listed below.
3. Use the no card-type command to delete a module from the Megaplex-4
database.
Task
Command
Comments
Defining power supply
modules
card-type power-supply ps
Slots: ps-a, ps-b
Defining common logic
modules
card-type cl {cl2-622gbe | cl2622gbea | cl2 }
Using no card-type removes the selection
Slots: cl-a, cl-b
cl2-622gbe – CL.2 module with 2 GbE ports
and 2 STM-1/OC-3 or STM-4/OC-12 links
cl2-622gbe/a – CL.2 module with 2 GbE ports
(possibility of upgrade to advances Ethernet
capabilities) and 2 STM-1/OC-3 or STM-4/OC-12
links
cl2 – CL.2 module without GbE and SDH/SONET
ports for DS0 cross-connect
Using no card-type removes the selection
Defining M8E1/M8T1,
M16E1/M16T1 modules
Megaplex-4
card-type e1-t1 {m8e1 | m8t1
| m16e1 | m16t1 }
Slots: 1 to 10
Using no card-type removes the selection
Cards
5-1
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Defining high speed
modules
card-type high-speed {hs12n |
hs6n | hsf2 | hs703}
Slots: 1 to 10
Using no card-type removes the selection
Note: When TDM group protection with
inband management over E1 is needed in
the chassis, do not install HSF-2 and
HS-703 modules in I/O slot 6.
Defining SHDSL modules
Defining ISDN modules
card-type=dsl {asmi54c |
asmi54c-e1eth | asmi54c-e1 |
m8sl | sh16 | sh16-e1|
sh16-e1-pw}
Slots: 1 to 10
card-type isdn {hsu12 | hsu6 |
hss}
Slots: 1 to 10
Using no card-type removes the selection
Using no card-type removes the selection
Note: When TDM group protection with
inband management over E1 is needed in
the chassis, do not install these modules
in I/O slot 6.
Defining low speed
modules
card-type low-speed {ls6n |
ls12 | hsr-n}
Slots: 1 to 10
Using no card-type removes the selection
Note: When TDM group protection with
inband management over E1 is needed in
the chassis, do not install these modules
in I/O slot 6.
Defining T3 modules
card-type e3-t3 mt3
Slots: 1 to 10
Using no card-type removes the selection
Defining versatile modules
Defining voice modules
Defining multiservice
modules
card-type versatile {vs-12 |
vs-6-bin | vs-6-c37 | vs-6-fxs |
vs-6-fxo | vs-6-em | vs-fxs-em |
vs-6-fxs-pw-acr | vs-6-fxo-pwacr | vs-6-em-pw-acr | vs-8em |
vs-e1-eop | vs-t1-eop | vs-e1-pw
| vs-t1-pw | vs-6-e1 | vs-6-t1 |
vs-g703}
Slots: 1 to 10
card-type voice {vc4fxs | vc4fxo |
vc4e-m | vc8fxs | vc8fxo |
vc8e-m | vc16fxs | vc16fxo |
vc16e-m | vc4-omni | vc6lb }
Slots: 1 to 10
card-type multi-service {ms-rtr-l
| ms-jnpr | ms-ub | ms-cesp | mssgw}
Slots: 2, 3, 4, 5, 7, 8, 9, 10
Using no card-type removes the selection
Note: When TDM group protection with
inband management over E1 is needed in
the chassis, do not install these modules
in I/O slot 6
Using no card-type removes the selection
Note: Out of two slots taken by each MS
module, it is the right one that is
identified in the terminal.
Defining alarm relay
modules
5-2
Cards
card-type alarm-relay {acm | tp}
Slots: 1 to 10
Using no card-type removes the selection
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Defining Optimux modules
card-type optimux {op108c |
op108c-e1 | op34c | op34c-e1}
Slots: 1 to 10
Defining pseudowire
modules
card-type pw mpw1
Slots: 1 to 10
Defining D-NFV modules
card-type virtual-engine {ve |
ve-l}
Using no card-type removes the selection
Using no card-type removes the selection
Slots: 2, 3, 4, 5, 7, 8, 9, 10
Using no card-type removes the selection
Note: Out of two slots taken by each
D-NFV module, it is the right one that is
identified in the terminal.
Note
The Megaplex-4100 chassis is supplied with a power supply in slot PS-A and a
CL.2 module in slot CL-A configured as factory defaults:
(slot ps-a card-type power-supply ps
slot cl-a card-type cl cl2-622gbe).
Example
To configure a chassis with:
•
Two power supply modules
•
Two CL.2 modules
•
One ASMi-54C/N module in slot 6
•
Five M8E1 modules in slots 1–5.
# config slot ps-a card-type ps-a power-supply ps
# config slot ps-b card-type ps-b power-supply ps
# config slot cl-a card-type cl cl2-622gbe
# config slot cl-b card-type cl cl2-622gbe
# config slot 1 card-type e1-t1 m8e1
# config slot 2 card-type e1-t1 m8e1
# config slot 3 card-type e1-t1 m8e1
# config slot 4 card-type e1-t1 m8e1
# config slot 5 card-type e1-t1 m8e1
# config slot 6 card-type dsl asmi54c-e1eth
To delete the ASMi-54C/N module in slot 6 from the database:
config# slot 6 no card-type
Displaying Modules in the Chassis
You can display information on the following:
Megaplex-4
•
Modules installed in the chassis: show cards-summary command
•
Module programmed in the specific slot: info or show card-type command
•
All the parameters configured in the database (per chassis): info detail
command.
Cards
5-3
Chapter 5 Cards and Ports
Installation and Operation Manual
To d is p la y t h e m o d u le s in s t a lle d in t h e ch a s s is :
•
At the config# prompt, enter the show cards-summary command.
•
config# show cards-summary
Slot Family
Type
HW Ver
SW Ver
---------------------------------------------------------------------------PS-A Power Supply ps
Undefined Undefined
PS-B Not Installed-Undefined Undefined
CL-A CL
CL2 622GbE
0.0/ 0.0 3.00P14/ 0
CL-B Not Installed-Undefined Undefined
1
Optimux
OP-34C
1
1.50A0
2
Optimux
OP-34C
1
1.50A0
3
Optimux
OP-34C Eth E1
1
1.50A0
4
E1-T1
M8 E1
1
1.69
5
E1-T1
M16 E1
1
1.50
6
E1-T1
M8 T1
1
1.69
7
Optimux
OP-108C
2
2.UNDEF
8
Optimux
OP-108C
2
2.UNDEF
9
E1-T1
M16 T1
1
1.50
10
High Speed
HS6N
2
6.00
To display information on the module programmed in the slot:
•
At the slot# prompt, enter the info command.
config>slot(1)# info
card-type e1-t1
m8t1
OR
•
At the slot# prompt, enter the show card-type command.
config>slot(1)# show card-type
Family : E1-T1
Type
: M8 E1
HW Ver : 1
SW Ver : 1.73
To display information on all the parameters configured in the database (per
chassis):
•
At the config# prompt, enter the info detail command.
# configure info detail
echo "Management configuration"
#
Management configuration
management
echo "SNMP Configuration"
#
SNMP Configuration
snmp
snmp-engine-id mac 00-00-00-00-00-00
no snmpv3
exit
more..
echo "RADIUS"
#
RADIUS
radius
server 1
exit
5-4
Cards
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
server
exit
server
exit
server
exit
2
3
4
exit
exit
echo "Slot Configuration"
#
Slot Configuration
slot ps-a
card-type power-supply ps
exit
#
Slot Configuration
more..
slot ps-b
exit
#
Slot Configuration
slot cl-a
card-type cl cl2-622gbe
exit
#
Slot Configuration
slot cl-b
exit
#
Slot Configuration
slot 1
card-type voice vc4e-m
exit
#
Slot Configuration
slot 2
card-type voice vc4e-m
exit
#
Slot Configuration
slot 3
card-type voice vc4e-m
more..
exit
#
Slot Configuration
slot 4
card-type voice vc4e-m
exit
#
Slot Configuration
slot 5
card-type voice vc4e-m
exit
#
Slot Configuration
slot 6
card-type voice vc4e-m
exit
#
Slot Configuration
slot 7
card-type voice vc4e-m
exit
#
Slot Configuration
slot 8
card-type voice vc4e-m
exit
more..
#
Slot Configuration
slot 9
Megaplex-4
Cards
5-5
Chapter 5 Cards and Ports
Installation and Operation Manual
card-type voice vc4e-m
exit
#
Slot Configuration
slot 10
card-type voice vc4e-m
exit
echo "System Configuration"
#
System Configuration
system
echo "Clock Configuration"
#
Clock Configuration
clock
echo "Station Clock Configuration"
#
Station Clock Configuration
station 1
exit
exit
exit
more..
echo "QoS - Configuration"
#
QoS - Configuration
qos
echo "Policer Profile configuration"
#
Policer Profile configuration
policer-profile "Policer1"
exit
exit
echo "Port Configuration"
#
Port Configuration
port
echo "Signaling Profile Configuration"
#
Signaling Profile Configuration
signaling-profile ""
exit
#
Signaling Profile Configuration
signaling-profile ""
exit
#
Signaling Profile Configuration
signaling-profile ""
exit
#
Signaling Profile Configuration
signaling-profile ""
exit
#
Signaling Profile Configuration
signaling-profile ""
exit
echo "Ethernet - Port Configuration"
#
Ethernet - Port Configuration
ethernet cl-a/1
no policer
exit
#
Ethernet - Port Configuration
ethernet cl-a/2
no policer
exit
echo "Managment Ethernet - Port Configuration"
#
Managment Ethernet - Port Configuration
mng-ethernet cl-a/1
exit
echo "E1 Internal - Port Configuration"
5-6
Cards
Megaplex-4
Installation and Operation Manual
#
Chapter 5 Cards and Ports
E1 Internal - Port Configuration
e1-i cl-a/1
exit
E1 Internal - Port Configuration
e1-i cl-a/2
exit
E1 Internal - Port Configuration
e1-i cl-a/3
#
#
exit
#
#
#
E1 Internal - Port Configuration
e1-i cl-a/4
exit
E1 Internal - Port Configuration
e1-i cl-a/5
exit
E1 Internal - Port Configuration
e1-i cl-a/6
no shutdown
more..
#
#
#
#
#
#
more..
#
#
#
#
#
#
#
Megaplex-4
exit
E1 Internal - Port Configuration
e1-i cl-a/7
no shutdown
exit
E1 Internal - Port Configuration
e1-i cl-a/8
exit
E1 Internal - Port Configuration
e1-i cl-a/9
exit
E1 Internal - Port Configuration
e1-i cl-a/10
exit
E1 Internal - Port Configuration
e1-i cl-a/11
exit
E1 Internal - Port Configuration
e1-i cl-a/12
exit
E1 Internal - Port Configuration
e1-i cl-a/13
exit
E1 Internal - Port Configuration
e1-i cl-a/14
exit
E1 Internal - Port Configuration
e1-i cl-a/15
exit
E1 Internal - Port Configuration
e1-i cl-a/16
exit
E1 Internal - Port Configuration
e1-i cl-a/17
exit
E1 Internal - Port Configuration
e1-i cl-a/18
exit
E1 Internal - Port Configuration
e1-i cl-a/19
Cards
5-7
Chapter 5 Cards and Ports
Installation and Operation Manual
exit
more..
#
#
#
#
#
#
#
more..
#
#
#
#
#
#
more..
#
#
#
#
#
#
5-8
Cards
E1 Internal - Port Configuration
e1-i cl-a/20
exit
E1 Internal - Port Configuration
e1-i cl-a/21
exit
E1 Internal - Port Configuration
e1-i cl-a/22
exit
E1 Internal - Port Configuration
e1-i cl-a/23
exit
E1 Internal - Port Configuration
e1-i cl-a/24
exit
E1 Internal - Port Configuration
e1-i cl-a/25
exit
E1 Internal - Port Configuration
e1-i cl-a/26
exit
E1 Internal - Port Configuration
e1-i cl-a/27
exit
E1 Internal - Port Configuration
e1-i cl-a/28
exit
E1 Internal - Port Configuration
e1-i cl-a/29
exit
E1 Internal - Port Configuration
e1-i cl-a/30
exit
E1 Internal - Port Configuration
e1-i cl-a/31
exit
E1 Internal - Port Configuration
e1-i cl-a/32
exit
E1 Internal - Port Configuration
e1-i cl-a/33
exit
E1 Internal - Port Configuration
e1-i cl-a/34
exit
E1 Internal - Port Configuration
e1-i cl-a/35
exit
E1 Internal - Port Configuration
e1-i cl-a/36
exit
E1 Internal - Port Configuration
e1-i cl-a/37
exit
E1 Internal - Port Configuration
e1-i cl-a/38
Megaplex-4
Installation and Operation Manual
#
more..
#
#
#
#
#
#
#
Chapter 5 Cards and Ports
exit
E1 Internal - Port Configuration
e1-i cl-a/39
exit
E1 Internal - Port Configuration
e1-i cl-a/40
exit
E1 Internal - Port Configuration
e1-i cl-a/41
exit
E1 Internal - Port Configuration
e1-i cl-a/42
exit
E1 Internal - Port Configuration
e1-i cl-a/43
exit
E1 Internal - Port Configuration
e1-i cl-a/44
exit
E1 Internal - Port Configuration
e1-i cl-a/45
exit
E1 Internal - Port Configuration
e1-i cl-a/46
more..
#
#
#
#
#
#
more..
#
#
#
#
Megaplex-4
no shutdown
exit
E1 Internal - Port Configuration
e1-i cl-a/47
no shutdown
exit
E1 Internal - Port Configuration
e1-i cl-a/48
exit
E1 Internal - Port Configuration
e1-i cl-a/49
exit
E1 Internal - Port Configuration
e1-i cl-a/50
exit
E1 Internal - Port Configuration
e1-i cl-a/51
exit
E1 Internal - Port Configuration
e1-i cl-a/52
exit
E1 Internal - Port Configuration
e1-i cl-a/53
exit
E1 Internal - Port Configuration
e1-i cl-a/54
exit
E1 Internal - Port Configuration
e1-i cl-a/55
exit
E1 Internal - Port Configuration
e1-i cl-a/56
exit
Cards
5-9
Chapter 5 Cards and Ports
#
#
#
#
#
#
#
#
#
#
#
#
Installation and Operation Manual
E1 Internal - Port Configuration
e1-i cl-a/57
exit
E1 Internal - Port Configuration
e1-i cl-a/58
exit
E1 Internal - Port Configuration
e1-i cl-a/59
exit
E1 Internal - Port Configuration
e1-i cl-a/60
exit
E1 Internal - Port Configuration
e1-i cl-a/61
exit
E1 Internal - Port Configuration
e1-i cl-a/62
exit
E1 Internal - Port Configuration
e1-i cl-a/63
exit
echo "Voice - Port Configuration"
Voice - Port Configuration
voice 1/1
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 1/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 1/3
no shutdown
signaling cas
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 1/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 2/1
no shutdown
signaling cas
more..
#
#
5-10
Cards
exit
Voice - Port Configuration
voice 2/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 2/3
no shutdown
signaling cas
exit
Megaplex-4
Installation and Operation Manual
#
#
Chapter 5 Cards and Ports
Voice - Port Configuration
voice 2/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 3/1
no shutdown
signaling cas
more..
#
#
#
#
exit
Voice - Port Configuration
voice 3/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 3/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 3/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 4/1
no shutdown
signaling cas
more..
#
#
#
#
exit
Voice - Port Configuration
voice 4/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 4/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 4/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 5/1
no shutdown
signaling cas
more..
#
#
Megaplex-4
exit
Voice - Port Configuration
voice 5/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 5/3
Cards
5-11
Chapter 5 Cards and Ports
Installation and Operation Manual
no shutdown
signaling cas
#
#
exit
Voice - Port Configuration
voice 5/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 6/1
no shutdown
signaling cas
more..
#
#
#
#
exit
Voice - Port Configuration
voice 6/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 6/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 6/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 7/1
no shutdown
signaling cas
more..
#
#
#
#
exit
Voice - Port Configuration
voice 7/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 7/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 7/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 8/1
no shutdown
signaling cas
more..
#
5-12
Cards
exit
Voice - Port Configuration
voice 8/2
no shutdown
signaling cas
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
exit
Voice - Port Configuration
voice 8/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 8/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 9/1
no shutdown
signaling cas
#
#
#
more..
exit
Voice - Port Configuration
voice 9/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 9/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 9/4
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 10/1
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 10/2
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 10/3
no shutdown
signaling cas
exit
Voice - Port Configuration
voice 10/4
no shutdown
signaling cas
exit
echo "SDH/Sonet - Port Configuration"
SDH/Sonet - Port Configuration
sdh-sonet cl-a/1
exit
SDH/Sonet - Port Configuration
sdh-sonet cl-a/2
exit
#
#
#
#
#
#
#
#
#
exit
Megaplex-4
Cards
5-13
Chapter 5 Cards and Ports
Installation and Operation Manual
echo "Cross Connect"
Cross Connect
cross-connect
ds0 e1-i cl-a/6 ts 3 voice 9/2
ds0 e1-i cl-a/6 ts 4 voice 9/4
ds0 e1-i cl-a/6 ts 7 voice 10/2
ds0 e1-i cl-a/6 ts 8 voice 10/4
ds0 e1-i cl-a/7 ts 1 voice 1/2
ds0 e1-i cl-a/7 ts 2 voice 1/4
ds0 e1-i cl-a/7 ts 5 voice 2/2
ds0 e1-i cl-a/7 ts 6 voice 2/4
ds0 e1-i cl-a/7 ts 9 voice 3/2
ds0 e1-i cl-a/7 ts 10 voice 3/4
ds0 e1-i cl-a/7 ts 13 voice 4/2
ds0 e1-i cl-a/7 ts 14 voice 4/4
ds0 e1-i cl-a/7 ts 18 voice 5/2
more..
ds0 e1-i cl-a/7 ts 19 voice 5/4
ds0 e1-i cl-a/7 ts 22 voice 6/2
ds0 e1-i cl-a/7 ts 23 voice 6/4
ds0 e1-i cl-a/7 ts 26 voice 7/2
ds0 e1-i cl-a/7 ts 27 voice 7/4
ds0 e1-i cl-a/7 ts 30 voice 8/2
ds0 e1-i cl-a/7 ts 31 voice 8/4
ds0 e1-i cl-a/46 ts 3 voice 9/1
ds0 e1-i cl-a/46 ts 4 voice 9/3
ds0 e1-i cl-a/46 ts 7 voice 10/1
ds0 e1-i cl-a/46 ts 8 voice 10/3
ds0 e1-i cl-a/47 ts 1 voice 1/1
ds0 e1-i cl-a/47 ts 2 voice 1/3
ds0 e1-i cl-a/47 ts 5 voice 2/1
ds0 e1-i cl-a/47 ts 6 voice 2/3
ds0 e1-i cl-a/47 ts 9 voice 3/1
ds0 e1-i cl-a/47 ts 10 voice 3/3
ds0 e1-i cl-a/47 ts 13 voice 4/1
ds0 e1-i cl-a/47 ts 14 voice 4/3
ds0 e1-i cl-a/47 ts 18 voice 5/1
more..
ds0 e1-i cl-a/47 ts 19 voice 5/3
ds0 e1-i cl-a/47 ts 22 voice 6/1
ds0 e1-i cl-a/47 ts 23 voice 6/3
ds0 e1-i cl-a/47 ts 26 voice 7/1
ds0 e1-i cl-a/47 ts 27 voice 7/3
ds0 e1-i cl-a/47 ts 30 voice 8/1
ds0 e1-i cl-a/47 ts 31 voice 8/3
sdh-sonet vc12-vt2 cl-a/1/1/2/1/1 e1-i
sdh-sonet vc12-vt2 cl-a/1/1/1/7/2 e1-i
sdh-sonet vc12-vt2 cl-a/2/1/2/1/1 e1-i
sdh-sonet vc12-vt2 cl-a/2/1/1/7/2 e1-i
exit
router 1
exit
router 2
exit
echo "Port Configuration"
#
Port Configuration
port
echo "SDH/Sonet VC Profile Configuration"
#
SDH/Sonet VC Profile Configuration
vc-profile "tug-structure"
#
5-14
Cards
cl-a/46
cl-a/47
cl-a/6
cl-a/7
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
exit
SDH/Sonet VC Profile Configuration
vc-profile "hvc-laps"
payload-label 0x18
exit
SDH/Sonet VC Profile Configuration
vc-profile "hvc-gfp"
payload-label 0x1b
exit
SDH/Sonet VC Profile Configuration
vc-profile "lvc-eos"
payload-label 0x05
exit
#
#
#
exit
Displaying Ports in the Chassis
You can display the following information on all the ports in the Megaplex-4
chassis, whether they are enabled or disabled:
•
All or selected ports in the chassis without Rx/Tx statistics: show summary
detail command
•
All or selected ports in the chassis with Rx/Tx statistics for Ethernet-type
ports (ethernet | lag | logical-mac | pcs | ethernet-mng | int-ethernet) : show
summary counters command
This command does not show all the port parameters but is more concise than
info detail.
You can also choose to dispay only ports that are enabled or disabled.
To d is p la y t h e p o rt s o f t h e m o d u le s in s t a lle d in t h e ch a s s is :
•
At the config>port# prompt, enter the following command.
show summary {detail | counters} [{ethernet | lag | logical-mac | e1 | t1 |
e3 | t3 | sdh-sonet | shdsl | pcs | voice | serial | hdlc | ppp | mlppp | gfp | vcg | svi |
bridge | ethernet-mng | hvc-sts1 | mux-eth-tdm | station-clock | ds1 | e1-i | t1i | vc-vt | cmd-in | cmd-in-i | cmd-out | cmd-out-i | cmd-channel | bri | tdmbridge | int-ethernet | ds0-bundle | ds0-g703 | ds1-opt }] [{all | admin-up | admindown }]
Example 1: Displaying all Ports in the Modules Installed in the
System
•
config>port# show summary detail
Port
Index
Admin
Oper
Speed Loopback
Name
----------------------------------------------------------------------------Ethernet Mng
cl-a/1
Enabled
Up
100M
--CL-A mng ethernet
01
Station Clk
cl-a/1
Enabled
Up
---CL-A station 01
Ethernet
cl-a/1
Disabled Down
1G
--CL-A ethernet 01
Megaplex-4
Cards
5-15
Chapter 5 Cards and Ports
Ethernet
SDH/SONET
SDH/SONET
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
T1-I
more..
cl-a/2
cl-a/1
cl-a/2
cl-a/1
cl-a/2
cl-a/3
cl-a/4
cl-a/5
cl-a/6
cl-a/7
cl-a/8
cl-a/9
cl-a/10
cl-a/11
cl-a/12
cl-a/13
cl-a/14
cl-a/15
cl-a/16
cl-a/17
cl-a/18
cl-a/19
cl-a/20
cl-a/21
cl-a/22
cl-a/23
cl-a/24
cl-a/25
cl-a/26
cl-a/27
cl-a/28
cl-a/29
cl-a/30
cl-a/31
cl-a/32
Installation and Operation Manual
Disabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Down
Up
Up
Up
Up
Up
Up
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
Down
1G
622M
622M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
1M
-----------------------------------------------------------------------
CL-A ethernet 02
CL-A sdh-sonet 01
CL-A sdh-sonet 02
CL-A t1-i 01
CL-A t1-i 02
CL-A t1-i 03
CL-A t1-i 04
CL-A t1-i 05
CL-A t1-i 06
CL-A t1-i 07
CL-A t1-i 08
CL-A t1-i 09
CL-A t1-i 10
CL-A t1-i 11
CL-A t1-i 12
CL-A t1-i 13
CL-A t1-i 14
CL-A t1-i 15
CL-A t1-i 16
CL-A t1-i 17
CL-A t1-i 18
CL-A t1-i 19
CL-A t1-i 20
CL-A t1-i 21
CL-A t1-i 22
CL-A t1-i 23
CL-A t1-i 24
CL-A t1-i 25
CL-A t1-i 26
CL-A t1-i 27
CL-A t1-i 28
CL-A t1-i 29
CL-A t1-i 30
CL-A t1-i 31
CL-A t1-i 32
Example 2: Displaying Ethernet Ports in the Modules Installed
in the System
config>port# show summary detail ethernet
Port
Index
Admin
Oper
Speed Loopback
Name
----------------------------------------------------------------------------Ethernet
cl-a/1
Disabled Down
1G
--CL-A ethernet 01
Ethernet
cl-a/2
Disabled Down
1G
--CL-A ethernet 02
Ethernet
cl-b/1
Disabled Down
1G
--CL-B ethernet 01
Ethernet
cl-b/2
Disabled Down
1G
--CL-B ethernet 02
Ethernet
1/1
Enabled
Down
100M
--M8 ETH 1
Ethernet
1/2
Enabled
Down
100M
--M8 ETH 2
Ethernet
1/3
Disabled Down
100M
--M8 ETH 3
Ethernet
3/1
Disabled Down
100M
--IO-3 ethernet 01
5-16
Cards
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Example 3: Displaying All Ports in the Modules Installed in the
System including Tx/Rx Statistics for Ethernet-type Ports
config>port# show summary counters
Port
Ethernet Mng
cl-a/1
Station Clk
cl-a/1
Ethernet
cl-a/1
Ethernet
cl-a/2
SDH/SONET
cl-a/1
SDH/SONET
cl-a/2
T1-I
cl-a/1
T1-I
more..
cl-a/2
Admin
Oper
Speed
Tx Packets
Rx Packets
Error Packets
Enabled
Up
Enabled
Up
Disabled
Down
Disabled
Down
Enabled
Up
Enabled
Up
Enabled
Up
Enabled
100M
N/A
--
N/A
1G
0
1G
0
622M
N/A
622M
N/A
1M
N/A
1M
N/A
N/A
N/A
N/A
N/A
0
0
0
0
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Example 4: Displaying Ethernet Ports in the Modules Installed
in the System including Tx/Rx Statistics
config>port# show summary counters ethernet
Port
Ethernet
cl-a/1
Ethernet
cl-a/2
Ethernet
cl-b/1
Ethernet
cl-b/2
Ethernet
1/1
Ethernet
1/2
Ethernet
1/3
Ethernet
more..
3/1
Megaplex-4
Admin
Oper
Speed
Tx Packets
Rx Packets
Error Packets
Disabled
Down
Disabled
Down
Disabled
Down
Disabled
Down
Enabled
Down
Enabled
Down
Disabled
Down
Disabled
1G
0
1G
0
1G
0
1G
0
100M
0
100M
0
100M
0
100M
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Cards
5-17
Chapter 5 Cards and Ports
Installation and Operation Manual
Resetting I/O Modules
To reset an I/O module:
1. Navigate to configure slot(slot number)#.
The config>slot(slot number)# prompt is displayed.
2. Enter reset to reset the module installed in the selected slot.
Note
Resetting a module will temporarily disrupt services supported by that module.
Configuration Errors
Table 5-1 lists messages generated by Megaplex-4 when a configuration error is
detected.
Table 5-1. Configuration Error Messages
Code
Type
Syntax
Meaning
100
Error
AT LEAST ONE PS CARD MUST
BE DEFINED
At least one power supply module must be defined in the
system configuration
101
Error
AT LEAST ONE CL CARD MUST
BE DEFINED
At least one CL module must be defined in the system
configuration
102
Warning
MODULE TYPE MISMATCH
The modules actually installed in the equipment and the
modules programmed in the database are not the same
103
Warning
INTERFACE HW/SW MISMATCH
The interface type configured by the management system
is different from the interface selected by means of
jumpers
104
Error
MODULE DATABASE MISMATCH The CL module type configured in the database {cl2622gbe | cl2-622gbea |cl2-gbea | cl2-ds0 } does not match
the installed module type (can be displayed by
“show config cards-summary” command ("CL2 622GbE",
"CL2 622GbEa", "CL2 GbEa" or "CL2 DS0").
400
Error
DIFFERENT CL CARDS FOR
REDUNDANCY
Different CL module types are installed in slots CL-A and
CL-B; CL redundancy is not available
404
Error
PORT ASSIGNED IS IN
SHUTDOWN STATE
One of the two ports connected via flow, cross-connect or
bind command is in shutdown state. Set this port to “no
shutdown”.
766
Error
ILLEGAL CARD TYPE
DEFINITION
Since out of two slots taken by each D-NFV module, it is
the right one that is identified in the terminal, the D-NFV
module cannot be configured in the following I/O slots.
•
MP-4100: slots 1 & 6.
•
MP-4104 slots 1 & 2.
Similarly, it cannot be configured in a slot, following a slot
occupied with any other module.
5-18
Cards
Megaplex-4
Installation and Operation Manual
5.2
Chapter 5 Cards and Ports
Port-Related Profiles
Signaling Profiles
This feature is available for the E1/T1 ports on the M8E1/M8T1 modules.
Functional Description
When CAS is used (always in an M8T1 module, and in an M8E1 module when the
E1 port uses G.732S framing, with or without CRC-4 support), the signaling
information of each voice channel is carried by means of up to four bits (signaling
bits), designated by the applicable standards as bits A, B, C, and D.
The number of bits actually available for carrying signaling information and the
data rate at which signaling information can be transferred, depend on the port
(E1 or T1) and the framing mode being used, which are determined by the
applicable international standards.
The information appearing in the signaling bits can be provided either by voice
interface modules installed in the Megaplex-4, or by digital PBXs or local exchange
trunks connected to one of the E1 or T1 Megaplex-4 ports.
Digital PBXs and local exchanges often use dedicated signaling protocols to
exchange the signaling information through the E1 or T1 trunk bits assigned to
CAS, and therefore may interpret the state of CAS bits in proprietary ways. The
CL module can perform signaling protocol conversions, for example – to enable
the termination of PBX timeslots by a voice module installed in an I/O slot, to
connect a PBX to PSTN lines, etc.
The format of the signaling information is defined by specifying a profile. A profile
enables the user to specify translation rules for each individual signaling bit. The
available selections are A, B, C, D (value copied from the corresponding incoming
bit), ~A, ~B, ~C, ~D (inverted value of corresponding incoming bit), 0 (always 0),
and 1 (always 1).
In addition to the translation of individual bits, the receive path conversion
section also defines the signaling bit patterns that indicate the busy and idle
states.
The user can assign a separate profile to each TDM (E1 or T1) port. Each port,
and even individual timeslots of a port, can therefore use different receive and
transmit translation rules. Up to 5 different profiles, each covering a different set
of interoperability requirements, can be defined and stored in the Megaplex-4
configuration databases.
See also VC-4, VC-4A, VC-8, VC-8A, VC-16 section in Megaplex-4 I/O Modules
Installation and Operation Manual, Voice Modules Chapter, for specific
considerations regarding voice ports.
Factory Defaults
The default signaling profiles (profile1 to profile5) are provided with no signaling
translation.
Megaplex-4
Port-Related Profiles
5-19
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Default Value
idle-code
0x00
busy-code
0x0f
Each default signaling profile looks as follows.
busy-code 0x0f
idle-code 0x00
a-bit-code tx a rx
b-bit-code tx b rx
c-bit-code tx c rx
d-bit-code tx d rx
a
b
c
d
You can change the contents but not the names of each of the 5 profiles.
Configuring CAS Signaling Profiles
Use the following procedure to modify the signaling translation rules contained in
the five signaling profiles supported by Megaplex-4, in accordance with your
specific application requirements. You can specify different rules for the receive
and transmit directions.
•
Receive direction: defines the interpretation of the incoming signaling
information, that is, the signaling information received from the external
port. This section enables the user to select the translation of each incoming
bit to the corresponding internal signaling bit (the signaling bit actually sent
to each module which needs the signaling information received by a main
link).
•
Transmit direction: defines the translation of the internal signaling bits to the
signaling bits transmitted through the external port.
To add a signaling profile:
1. Navigate to configure port.
The config>port# prompt is displayed.
2. Type signaling-profile <signaling-profile-name>. Signaling profile name has
the fixed format: profile1 to profile5.
A signaling profile with the specified name is created and the following
prompt is displayed, for example:
config>port>signaling-profile(<profile2>)#.
3. Configure the signaling profile as described below.
To configure a signaling profile:
4. Navigate to configure port signaling-profile < signaling-profile-name> to
select the signaling profile to configure.
The config>port>signaling-profile(<signaling-profile-name>)# prompt is
displayed.
5. Enter all necessary commands according to the tasks listed below.
5-20
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Specifying translation rules
for signaling bit A (receive
and transmit directions)
a-bit-code tx {0 | 1 | a | b
| c | d | inverse-a | inverse-b
| inverse-c | inverse-d}
rx {0 | 1 | a | b | c | d | inverse-a
| inverse-b | inverse-c | inverse-d}
0 – bit value is always 0
b-bit-code tx {0 | 1 | a | b
| c | d | inverse-a | inverse-b
| inverse-c | inverse-d}
rx {0 | 1 | a | b | c | d | inverse-a
| inverse-b | inverse-c | inverse-d}
0 – bit value is always 0
c-bit-code tx {0 | 1 | a | b
| c | d | inverse-a | inverse-b
| inverse-c | inverse-d}
rx {0 | 1 | a | b | c | d | inverse-a
| inverse-b | inverse-c | inverse-d}
0 – bit value is always 0
d-bit-code tx {0 | 1 | a | b
| c | d | inverse-a | inverse-b
| inverse-c | inverse-d}
rx {0 | 1 | a | b | c | d | inverse-a
| inverse-b | inverse-c | inverse-d}
0 – bit value is always 0
busy-code {00 to 0F (hexa)}
Hexadecimal number in the range of 0 to
0F (two digits)
Specifying translation rules
for signaling bit B (receive
and transmit directions)
Specifying translation rules
for signaling bit C (receive
and transmit directions)
Specifying translation rules
for signaling bit D (receive
and transmit directions)
Specifying the signaling bit
pattern indicating the busy
state
1 – bit value is always 1
a, b, c, d – bit value copied from the
corresponding incoming bit
inverse-a, inverse-b, inverse-c, inverse-d
– inverted bit value, related to the
corresponding incoming bit
1 – bit value is always 1
a, b, c, d – bit value copied from the
corresponding incoming bit
inverse-a, inverse-b, inverse-c, inverse-d
– inverted bit value, related to the
corresponding incoming bit
1 – bit value is always 1
a, b, c, d – bit value copied from the
corresponding incoming bit
inverse-a, inverse-b, inverse-c, inverse-d
– inverted bit value, related to the
corresponding incoming bit
1 – bit value is always 1
a, b, c, d – bit value copied from the
corresponding incoming bit
inverse-a, inverse-b, inverse-c, inverse-d
– inverted bit value, related to the
corresponding incoming bit
The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which, when
converted to binary format, yields the
desired ABCD sequence.
Example: if the busy state is indicated by
the incoming sequence 1000, select 8.
Specifying the signaling bit
pattern indicating the idle
state
Megaplex-4
idle-code {00 to 0F (hexa)}
Hexadecimal number in the range of 0 to
0F (two digits)
The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which when
converted to binary format yields the
desired ABCD sequence.
Port-Related Profiles
5-21
Chapter 5 Cards and Ports
Installation and Operation Manual
Example
To create and configure signaling profile “1”:
•
a-bit-code rx and tx – translated to inverse-a
•
b-bit-code rx and tx – b
•
c-bit-code rx and tx – translated to 1
•
d-bit-code rx and tx – d
config# port signaling-profile profile1 a-bit-code tx inverse-a
rx inverse-a
config# port signaling-profile profile1 b-bit-code tx b rx b
config# port signaling-profile profile1 c-bit-code tx 1 rx 1
config# port signaling-profile profile1 d-bit-code tx d rx d
To display the resulting signaling profile:
config>port>signaling-profile(profile1)# info detail
busy-code 0x0f
idle-code 0x00
a-bit-code tx inverse-a rx inverse-a
b-bit-code tx b rx b
c-bit-code tx 1 rx 1
d-bit-code tx d rx d
The screen lists the four signaling bits, A to D, together with their current
translations. In this case, the busy and idle codes are left at their
defaults.
To assign profile 1 to an E1 port:
config>port>e1(9/1)# signaling-profile 1
Note
Pay attention to the syntax:
• When configuring the profile n (n=1,2,3,4,5), use “profile<n>” number
• When assigning the configured profile to an E1/T1 port, use simply “<n>”, not
“profile<n>”)
Analog Signaling Profiles
This feature is available for the voice ports of the VS modules.
Functional Description
Analog voice signals are digitized using PCM (Pulse-code modulation), in
compliance with ITU-T G.711 and AT&T Pub. 43801 standards. The signaling
information of each voice channel is carried by means of up to four bits (signaling
bits), designated by the applicable standards as bits A, B, C and D. Analog
signaling profile is configured per channel and per direction.
Table 5-2 and Table 5-3 show the analog signaling profile actions for FXS and
FXO modules, respectively.
5-22
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Table 5-2. Analog Signaling Profile Actions for FXS Modules
Signaling
Mode
Direction
Tx
Loop
Start
Signaling Bits
A
B
C
D
signaling/inverse-sig
1/0
1/0
1
1/0
signaling/inverse-sig
1/0
1
signaling/inverse-sig
not-used
not-used
not-used
not-used
signaling/inverse-sig
not-used
not-used
signaling/inverse-sig
forward-disconnect/
not-used
not-used
signaling/inverse-sig
not-used
not-used
signaling/inverse-sig
1/0
1/0
1
signaling/inverse-sig
wink
not-used
not-used
signaling/inverse-sig
wink
forwarddisconnet
not-used
signaling/inverse-sig
forward-disconnect/
wink
not-used
Rx
inverse-forward-disconnect
forward-disconnect/
inverse-forwarddisconnect
Tx
Wink
Start
Rx
inverse-forward-disconnect
Table 5-3. Analog Signaling Profile Actions for FXO Modules
Signaling
Mode
Direction
Tx
Signaling Bits
A
B
C
D
signaling/inversesig
1/0
1/0
1
1/0
signaling/inverse-sig
1/0
1
signaling/inversesig
loop-disconnect/
1/0
1
loop-disconnet
signaling/inverse-sig
1/0
1
signaling/inversesig
not-used
not-used
notused
1/0
signaling/inverse-sig
not-used
notused
signaling/inversesig
wink
1/0
1
signaling/inversesig
wink
loop-disconnet
1
Loop Start
Rx
Wink Start
Megaplex-4
Tx
inverse-loopdisconnect
Port-Related Profiles
5-23
Chapter 5 Cards and Ports
Installation and Operation Manual
Rx
signaling/inversesig
loop-disconnect/
signaling/inversesig
not-used
wink
1
not-used
notused
inverse-loopdisconnect
For E&M modules, the A/B bits are selected based on tx-a-bit/tx-b-bit sent by the
remote unit and the received signaling.
In the tables above, the corresponding bit states are shown as follows:
•
not-used indicates that the corresponding bit is not relevant;
•
signaling states:
•
•
•
•
•
•
5-24
For FXS module, 0 indicates on-hook and 1 indicates off-hook.
For FXO module, 0 indicates no ring and 1 indicates ring.
inverse-sig has two states:
For FXS module, 0 indicates off-hook and 1 indicates on-hook.
For FXO module, 0 indicate ring and 1 indicates no ring.
loop-disconnect has two states:
0 indicates the far-end party is not disconnected (CO is feeding the
line);
1 indicates the far-end party has disconnected (CO has disconnected
the line feeding);
inverse-loop-disconnect has two states:
0 indicates loop current feed open state (CO has disconnected the line
feeding);
1 indicates no loop current feed open state (CO is feeding the line) ;
forward-disconnect has two states:
0 indicates the far-end party is not disconnected (FXS port is feeding
the line) ;
1 indicates the far-end party has disconnected (FXS port has
disconnected the line feeding);
inverse-forward-disconnect has two states:
0 indicates the far-end party has disconnected (FXS port has
disconnected the line feeding);
1 indicates the far-end party is not disconnected (FXS port is feeding
the line) ;
wink indicates reverse battery polarity:
0 indicates reversion battery polarity,
1 indicates normal battery polarity.
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Factory Defaults
The following default analog signaling profiles are provided:
mp-4100>config>port# inf detail
analog-signaling-profile "sig_over_a_bit"
a-bit-tx signaling
a-bit-rx signaling
b-bit-tx 1
b-bit-rx not-used
c-bit-tx 0
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
exit
analog-signaling-profile "sig_tx_a_rx_b"
a-bit-tx signaling
a-bit-rx not-used
b-bit-tx 1
b-bit-rx inverse-sig
c-bit-tx signaling
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
exit
analog-signaling-profile "sig_tx_b_rx_a"
a-bit-tx 0
a-bit-rx signaling
b-bit-tx inverse-sig
b-bit-rx not-used
c-bit-tx 0
c-bit-rx not-used
d-bit-tx inverse-sig
d-bit-rx not-used
exit
The default analog signaling profiles cannot be modified or deleted.
Configuring Analog Signaling Profiles
To configure an analog signaling profile:
1. Navigate to configure port analog-signaling-profile <analogsignaling-profile-name> to configure.
The config>port>analog-signaling-profile(<analogsignaling-profile-name>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Specifying translation rules
for signaling bit A (receive
and transmit directions)
a-bit-tx {1 | 0 | signaling | inversesig | loop-disconnect}
Comments
a-bit-rx {not-used | signaling |
inverse-sig | forward-disconnect |
inverse-forward-disconnect}
Megaplex-4
Port-Related Profiles
5-25
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Specifying translation rules
for signaling bit B (receive
and transmit directions)
b-bit-tx {1 | 0 | signaling | inversesig | loop-disconnect | inverse-loopdisconnect | wink}
Comments
b-bit-rx {not-used | signaling |
inverse-sig | forward-disconnect |
inverse-forward-disconnect | wink}
Specifying translation rules
for signaling bit C (receive
and transmit directions)
c-bit-tx {1 | 0 | signaling | loopdisconnect | wink}
Specifying translation rules
for signaling bit D (receive
and transmit directions)
d-bit-tx {1 | 0 | signaling | inversesig}
c-bit-rx {not-used | forwarddisconnect | wink}
d-bit-rx {not-used | signaling |
inverse-sig}
Example
To create and configure analog signaling profile “profile1”:
•
a-bit-tx– translated to 1
•
a-bit-rx– translated to not-used
•
b-bit-tx– signaling
•
b-bit-rx– signaling
•
c-bit-tx and rx, d-bit-tx and rx use the default value
config>port>analog-signaling-pro(profile1)# a-bit-tx 1
config>port>analog-signaling-pro(profile1)# a-bit-rx not-used
config>port>analog-signaling-pro(profile1)# b-bit-tx signaling
config>port>analog-signaling-pro(profile1)# b-bit-rx signaling
To display the resulting signaling profile:
config>port>signaling-profile(profile1)# info detail
a-bit-tx 1
a-bit-rx not-used
b-bit-tx signaling
b-bit-rx signaling
c-bit-tx 0
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
To assign profile 1 to a voice port:
config>port>voice(10/3)# analog-signaling-profile profile1
5-26
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
VC Profiles
In the Megaplex-4 architecture, any SDH/SONET unit of order lower than
SDH/SONET port is configured by creating VC profiles and binding it to the
corresponding unit. You can create up to 64 profiles to define the handling of
SDH/SONET (VC/VT/STS) traffic. You can then assign the required profile to a gfp,
hdlc, e1, e1-i, aug, t1, t1-i or oc-3 port.
Four pre-defined default VC profiles are available in the system. They are bound
automatically to VC-12/VT-1.5/ VC-3/VC-4/STS-1/STS-3C or E1/T1 ports when
certain configurations take place in the system. Table 5-4 lists these profiles
together with their names and corresponding configurations.
Table 5-4. Default VC Profiles
Name
VC Profile
Matches Configuration
lvc-eos
payload-label 0x05
VC-12/VT-1.5 bound to VCG
pathtrace direction tx length 15plus-crc string
"www.rad.com" padding nulls
Note: When this profile is
no plm-response
no tim-response
rate-threshold eed e-3 sd e-6
assigned to GFP ports (which
is done automatically), the
pathtrace parameters define
the J2 pathtrace
interval-threshold cv 25 es 20 ses 3 uas 10
day-threshold cv 250 es 200 ses 7 uas 10
tug-structure
payload-label 0x02
pathtrace direction tx length 15plus-crc string
"www.rad.com" padding nulls
no plm-response
no tim-response
rate-threshold eed e-3 sd e-6
interval-threshold cv 25 es 20 ses 3 uas 10
day-threshold cv 250 es 200 ses 7 uas 10
VC-12/VT1.5 bound to VCG on
the overhead (POH) level or
E1/T1 is cross-connected to
SDH/SONET ports directly
Note: When this profile is
assigned to AUG/OC-3 ports
(which is done automatically),
the pathtrace parameters
define the J1 pathtrace
When this profile is assigned
to E1/T1 ports (which is done
automatically), the pathtrace
parameters define the J2
pathtrace
hvc-laps
payload-label 0x18
pathtrace direction tx length 15plus-crc string
"www.rad.com" padding nulls
VC-3/VC-4/STS-1/STS-3C
bound to VCG with LAPS
encapsulation (hdlc)
no plm-response
Note: When this profile is
no tim-response
rate-threshold eed e-3 sd e-6
interval-threshold cv 25 es 20 ses 3 uas 10
assigned to HDLC ports (which
is done automatically), the
pathtrace parameters define
the J1 pathtrace
day-threshold cv 250 es 200 ses 7 uas 10
Megaplex-4
Port-Related Profiles
5-27
Chapter 5 Cards and Ports
Installation and Operation Manual
Name
VC Profile
Matches Configuration
hvc-gfp
payload-label 0x1b
pathtrace direction tx length 15plus-crc string
"www.rad.com" padding nulls
VC-3/VC-4/STS-1/STS-3C
bound to VCG with GFP
encapsulation (gfp)
no plm-response
Note: When this profile is
no tim-response
rate-threshold eed e-3 sd e-6
interval-threshold cv 25 es 20 ses 3 uas 10
assigned to GFP ports (which
is done automatically), the
pathtrace parameters define
the J1 pathtrace
day-threshold cv 250 es 200 ses 7 uas 10
Factory Defaults
The VC profile parameter defaults are listed in the table below.
Parameter
Default Value
payload-label
0x02 (default values for pre-defined profiles are listed in
Table 5-4)
pathtrace direction
tx
pathtrace padding
nulls
pathtrace length
15plus-crc
plm-response
disable
tim-response
disable
rate-threshold eed
e-3
rate-threshold sd
e-6
interval-threshold cv
25
interval-threshold es
20
interval-threshold ses
3
interval-threshold uas
10
day-threshold cv
250
day-threshold es
200
day-threshold ses
7
day-threshold uas
10
Configuring VC Profiles
Usually the four predefined VC profiles assigned to the corresponding units by
default should satify the user needs. However, if it is necessary to add and
configure a new user-defined profile, you must first disconnect the respective
predefined profile and only then configure and assign the new one.
5-28
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To add a user-defined VC profile:
6. Navigate to configure port.
The config>port# prompt is displayed.
7. Type vc profile <vc-profile-name>.
A VC profile with the specified name is created and the following prompt
is displayed: config>port>vc-profile(<vc-profile-name>)$.
8. Configure the VC profile as described below.
To configure a VC profile:
9. Navigate to configure port vc-profile <vc-profile-name> to select the VC
profile to configure.
The config>port>vc-profile(<vc-profile-name>)# prompt is displayed.
10. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Specifying the expected payload
label (one byte)
payload-label { 00 to FF
(hexa) }
Hexadecimal number in the range of 0 to
FF (two digits)
Using no pathtrace disables the checking
Enabling the checking of the
receive/transmit path trace label
by the port and configuring the
optional path trace direction and
padding
pathtrace [direction { tx | rxtx}] [length {64 | 15pluscrc}] [string <path-tracestring>] [padding {spaces |
nulls}]
When the VC profile is assigned to
au4/oc3 ports, this string defines the J1
pathtrace.
Enables the sending of RDI
indications by the port, in case
the received signal label (SDH
overhead byte C2 or V5) is
different from the expected
signal label
plm-response rdi
Using no plm-response disables RDI
indications
Enables the sending of RDI
indications by the port, in case
the received path trace label
(carried in SDH overhead byte J1
or J2) is different from the
expected path trace label
tim-response rdi
Using no tim-response disables RDI
indications
Selecting EED (error rate
degradation) and SD (signal
degrade) thresholds
rate-threshold [eed {e-3 | e4 | e-5} ] [ sd {e-6 | e-7 | e-8
| e-9}]
If the selected BER value is exceeded,
Megaplex-4 generates the relevant (EED
or SD) alarm
Setting CV, ES, SES and/or UAS
counter value during a 15-min
interval starting from which a
trap will be sent
interval-threshold [cv
<cv-value 0-900>] [es <esvalue 0-900>] [ses <sesvalue 0-900>] [uas
<uas-value 0-900>]
Megaplex-4
When the VC profile is assigned to
gfp/hdlc/e1/t1 ports, this string defines
the J2 pathtrace.
Port-Related Profiles
5-29
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Setting CV, ES, SES and/or UAS
counter value during 24-hours
interval starting from which a
trap will be sent
day-threshold [cv <cv-value
0-86400>] [es <es-value 086400>] [ses <ses-value 086400>] [uas <uas-value 086400>]
Comments
L2CP Profiles
Megaplex-4 handles Layer-2 control protocol traffic on a per-port basis. The L2CP
traffic is processed using a two-stage mechanism comprising per-port L2CP
profiles (set of rules for traffic handling). The L2CP profile affects untagged L2CP
frames. In total, Megaplex-4 supports up to 16 L2CP profiles:
•
Up to 4 (including default) port-level profiles can be defined on directlyattached ports
•
Up to 32 different addresses/protocols can be selected per L2CP profile.
If no default action is configured for an unspecified address or protocol, this
traffic is tunneled.
Note
If an L2CP profile has been attached to a port, the profile cannot be deleted or
modified.
Factory Defalts
By default, a “tunnel all” profile is attached to every port.
Configuring L2CP Profiles
Megaplex-4 can tunnel, discard or peer (trap to host for protocol processing)
L2CP packets. These actions are defined by L2CP profiles, which also provide
different L2CP addresses. The following MAC addresses are supported by L2CP
profiles: 01-80-C2-00-00-00, 01-80-C2-00-00-02 – 10 and 01-80-C2-00-00-20 –
2F.
Note
PAUSE frames (01-80-C2-00-00-01) are not part of L2CP profiles. They are either
peered or discarded according to flow control setting of a port.
According to L2CP profiles, Megaplex-4 performs the following:
Note
5-30
•
Discards L2CP traffic.
•
Tunnels L2CP traffic. Megaplex-4 forwards the traffic according to its
configuration (flows etc).
•
Peers L2CP traffic. Megaplex-4 forwards the traffic to the CPU.
Megaplex-4 supports peer action only for the following MAC addresses/protocols:
•
01-80-C2-00-00-00 (RSTP)
•
01-80-C2-00-00-02 (LACP, OAM (EFM))
•
01-80-C2-00-00-03 (802.1x).
Port-Related Profiles
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To add an L2CP profile:
11. Navigate to configure port.
The config>port# prompt is displayed.
12. Type l2cp profile <l2cp-profile-name>.
An L2CP profile with the specified name is created and the following
prompt is displayed: config>port>l2cp-profile(<l2cp-profile-name>)$.
13. Configure the L2CP profile as described below.
To configure an L2CP profile:
14. Navigate to configure port l2cp-profile <vc-profile-name> to select the L2CP
profile to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
15. Type info detail to view the existing parameters, for example:
config>port>l2cp-profile(ella)$ info d
mac 01-80-C2-00-00-00 tunnel
mac 01-80-C2-00-00-01 tunnel
mac 01-80-C2-00-00-02 tunnel
mac 01-80-C2-00-00-03 tunnel
mac 01-80-C2-00-00-04 tunnel
mac 01-80-C2-00-00-05 tunnel
mac 01-80-C2-00-00-06 tunnel
mac 01-80-C2-00-00-07 tunnel
mac 01-80-C2-00-00-08 tunnel
mac 01-80-C2-00-00-09 tunnel
mac 01-80-C2-00-00-0A tunnel
mac 01-80-C2-00-00-0B tunnel
mac 01-80-C2-00-00-0C tunnel
mac 01-80-C2-00-00-0D tunnel
mac 01-80-C2-00-00-0E tunnel
mac 01-80-C2-00-00-0F tunnel
mac 01-80-C2-00-00-10 tunnel
mac 01-80-C2-00-00-20 tunnel
mac 01-80-C2-00-00-21 tunnel
mac 01-80-C2-00-00-22 tunnel
mac 01-80-C2-00-00-23 tunnel
mac 01-80-C2-00-00-24 tunnel
mac 01-80-C2-00-00-25 tunnel
mac 01-80-C2-00-00-26 tunnel
mac 01-80-C2-00-00-27 tunnel
mac 01-80-C2-00-00-28 tunnel
mac 01-80-C2-00-00-29 tunnel
mac 01-80-C2-00-00-2A tunnel
mac 01-80-C2-00-00-2B tunnel
mac 01-80-C2-00-00-2C tunnel
16. Select the mac address you want to change and type it with modified
functionality (discard or peer), for example:
mac 01-80-C2-00-00-2A discard
Megaplex-4
Port-Related Profiles
5-31
Chapter 5 Cards and Ports
5.3
Installation and Operation Manual
Binary Command Ports
Applicable Modules
The Binary command module VS-6/BIN has 8 command inputs and 8 outputs,
enabling binary equipment to utilize the advanced transport capabilities offered
by Megaplex.
The binary commands can be locally output or be carried to a peer card/Megaplex
over a TDM/SDH network or over a packet-switched network using two
cmd-channel ports. Up to 4 commands can be carried over a single DS0.
Functional Description
See Versatile Modules chapter in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all binary command ports disabled. Other parameter
defaults are listed in the table below.
Parameter
Description
Default Value
Association between the cmd-in active state and the
supplied voltage
high
cmd-out alarm state indication
yes
cmd-in
input-active
cmd-out
alarm-state-energized
Configuring Binary Command Ports
Configuring CMD-IN Ports
To configure a cmd-in port:
1. Navigate to configure port cmd-in <slot>/<port>/<trib> to select the cmd-in
port to configure.
The config>port>cmd-in>(<slot>/<port>/<trib>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
5-32
Binary Command Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Defining the association
between the cmd-in active
state and the supplied
voltage
input-active {high | low}
•
low – command input is activated by low
voltage (0 to 18 VDC)
•
high – command input is activated by high
voltage (24 to 48 VDC)
Forcing the cmd-in port into
active state, disregarding
the actual input state
force-active
Using no force-active cancels the command
Configuring CMD-OUT Ports
To configure the cmd-out port parameters:
1. Navigate to configure port cmd-out <slot>/<port>/<trib> to select the port
to configure.
The config>port>cmd-out>(<slot>/<port>/<trib>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Defining cmd-out alarm
state indication
alarm-state-energized {yes |
no}
Energizing:
•
energized yes – The corresponding relay is
normally unenergized and switches to the
energized state when the alarm is active.
•
energized no – The corresponding relay is
normally energized and switches to the
unenergized state when the alarm is
active.
The relay contacts are normally open.
Configuring CMD-CHANNEL Ports
To configure the cmd-channel port parameters:
1. Navigate to configure port cmd-channel <slot>/<port> to select the port to
configure.
The config>port>cmd-channel>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Administratively enabling port
no shutdown
Using shutdown disables the port
Assigning short description to port
name <string>
Using no name removes the name
Megaplex-4
Binary Command Ports
5-33
Chapter 5 Cards and Ports
Installation and Operation Manual
Viewing Status Information
For viewing the status of the binary command ports, follow the instructions
below.
To view the status of a cmd-in port:
1. Navigate to config>port> cmd-in> (<slot>/<port>/<tributary>)#
2. Type show status.
The status is displayed, for example as follows:
config>port>cmd-in(10/1/1)# show status
Name
: VS-6/BIN CMD In 1
Administrative Status : Up
Operation Status
: Up
Value
: 0
Forced
: No
The status display provides information about:
Administrative and operational status
Value – Command value (0, 1),
Forced – Whether the port is in force-active state (Yes/No).
To view the status of a cmd-out port:
1. Navigate to config>port> cmd-out> (<slot>/<port>/<tributary>)#
2. Type show status.
The status is displayed, for example as follows:
config>port>cmd-out(10/1/1)# show status
Name
: VS-6/BIN CMD Out 1
Administrative Status : Up
Operation Status
: Up
Value
: 0
The status display provides information about:
Administrative and operational status
Value – Command value (0, 1).
To view the status of a cmd-channel port:
1. Navigate to config>port> cmd-channel> (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
config>port>cmd-channel(10/1)# show status
Name
: VS-6/BIN CMD CH 1
Administrative Status : Up
Operation Status
: Up
5-34
Binary Command Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Displaying Binary Command Statistics
Binary command ports cmd-in, cmd-out and cmd-channel feature RAD proprietary
statistical diagnostics.
To display the statistics of a cmd-in port:
1. Navigate to config>port> cmd-in> (<slot>/<port>/<tributary>)#
2. Type show statistics.
The statistics is displayed, for example as follows:
config>port>cmd-in(2/1/1)# show statistics
Trip : 1
The statistics shows the number of trips occurred since the port has been open.
To display the statistics of a cmd-out port:
1. Navigate to config>port> cmd-out> (<slot>/<port>/<tributary>)#
2. Type show statistics.
The statistics (number of trips) is displayed, for example as follows:
config>port>cmd-out(2/1/1)# show statistics
Trip Counter : 1
To display the statistics of a cmd-channel port:
1. Navigate to config>port> cmd-channel> (<slot>/<port>)#
2. Type show statistics.
The statistics is displayed, for example as follows:
config>port>cmd-channel(2/1)# show statistics
Frame Error : 0
CRC Error
: 0
Table 5-5. Binary Command Statistics Parameters
Parameter
Description
Frame Error
Number of frame errors received on the cmd channel since last reset or power-up
CRC Error
Number of CRC errors received on the cmd channel since last reset or power-up
A CRC error is declared when the CRC bits generated locally on the data in the received
frame (protecting critical teleprotection bits) do not match the CRC bits (crc1 – crc4)
received from the transmitter.
To clear the statistics on a binary command port:
1. Navigate to the corresponding port.
2. Enter clear-statistics.
The statistics for the specified port are cleared.
Megaplex-4
Binary Command Ports
5-35
Chapter 5 Cards and Ports
5.4
Installation and Operation Manual
BRI Ports
Applicable Modules
The following table shows the number of BRI ports on the HSU-6, HSU-12 and
HS-S I/O modules.
Table 5-6. BRI Ports
Module
Type of Module
Number of Ports
HSU-6, HSU12
ISDN “U”
6/12
HSS
ISDN “S”
4
The following parameters can be configured for the BRI ports:
•
Port name
•
Administrative status
•
Number of bits that must be allocated to each internal port (B-channel)
Standards Compliance
The BRI ports comply with the ANSI T1.601 and ITU-T Rec. G.961 standards.
Functional Description
See the corresponding module section in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all BRI ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
rate-bits
2
Configuring a BRI (ISDN) Port
To configure the BRI port parameters:
17. Navigate to configure port bri <slot>/<port>[tributary] to select the BRI port
to configure:
5-36
BRI Ports
To configure Channel B1, use configure port bri <slot>/<port>/1
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To configure Channel B2, use configure port bri <slot>/<port>/2
To configure Channel D, use configure port bri <slot>/<port>
The config>port>bri>(<slot>/<port>/[tributary>]# prompt is displayed.
18. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying the number of
bits that must be allocated
to each internal port
(B-channel), in accordance
with the payload data rate
rate-bits {2 | 4 | 8}
The data rates supported by each
B-channel are as follows:
2
Used for payload data rates up to 16
kbps.
4
Used for payload data rates up to 32
kbps.
8
Used for payload data rates up to 64
kbps.
For the D-Channel rate-bits is constantly
set to 2 (16 kbps).
Example
The following section illustrates how to configure the bri ports 3 and 4 (B1, B2
and D-channels) on the HS-U-6 module installed in slot 5:
•
Data rate 8 kbps on each B-channel (total 32 kbps).
•
Data rate 2 kbps on each D-channel (total 4 kbps).
•
Administratively enable the ports.
•
Leave all other parameters disabled or at their defaults.
------------hs-U6---------------config# port bri 5/3/1 no shutdown
config# port bri 5/3/1 rate-bits 8
config# port bri 5/3/2 no shutdown
config# port bri 5/3/2 rate-bits 8
config#
config# port bri 5/4/1 no shutdown
config# port bri 5/4/1 rate-bits 8
config# port bri 5/4/2 no shutdown
config# port bri 5/4/2 rate-bits 8
config# #------------d-channel-----config# port bri 5/3 no shutdown
config# port bri 5/3 rate-bits 2
config#
config# port bri 5/4 no shutdown
config# port bri 5/4 rate-bits 2
Megaplex-4
BRI Ports
5-37
Chapter 5 Cards and Ports
5.5
Installation and Operation Manual
Control Port
All the Megaplex-4 supervision and configuration functions, and in particular the
preliminary configuration activities, can be performed using a “dumb” ASCII
terminal (or a PC running a terminal emulation program) directly connected to the
Megaplex-4 serial RS-232 asynchronous supervisory port, located on its front
panel. The terminal is controlled by the program stored in the Megaplex-4. No
information has to be stored in the terminal.
Standards Compliance
The control port complies with the EIA RS-232/ITU-T V.24 standards.
Functional Description
The supervisory port enables the preliminary configuration of the Megaplex-4.
After the preliminary configuration is completed, Megaplex-4 can also be
managed by the other means, for example, Telnet hosts and SNMP network
management stations.
The supervisory port has a DCE interface, and supports data rates in the range of
9.6 to 115.2 kbps.
The terminal control parameters determine the control port's baud rate,
password used for each control session, and availability of the fixed security
timeout.
The following parameters can be configured for the control ports:
Note
•
Data rate
•
Security timeout
•
Length of the screen from which you are accessing the device.
Terminal parameters can only be configured when using a terminal connection.
Factory Defaults
Megaplex-4 is supplied with the control port enabled. Other parameter defaults
are listed in the table below.
Parameter
Default Value
baud-rate
9600 bps
timeout
10
Configuring the Control Port
To configure the terminal parameters:
•
5-38
Control Port
At the config>terminal# prompt, enter the necessary parameters according to
the table below.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Setting the baud rate (bps)
baud-rate {9600bps | 19200bps |
38400bps | 57800bps | 115200bps}
Enabling and defining a security
timeout (in minutes)
timeout limited <timeout in minutes>
Possible values are 0 to 60.
To specify the number of rows to
display
length <number-of-rows>
The number of rows can be 0,
to indicate no limit on the
number of lines displayed, or
20.
Disabling the security timeout
timeout forever
For example:
To set up a terminal connection at 19200 kbps with timeout after 10 minutes:
•
Set up the baud rate to 19200 kbps and make sure that the same rate is
selected in HyperTerminal for any future HyperTerminal connections.
•
Set the security timeout to 10 minutes.
config>terminal# baud-rate 19200bps
config>terminal# timeout-limited 10
5.6
DS0-Bundle Ports
To protect individual timeslots of E1/T1/E1-i/T1-i/DS1 ports of the relevant uplink
modules, special entities called DS0 bundles can be created in Megaplex-4. These
DS0 bundle ports are protected by the DS0 SNCP group redundancy, ensuring
end-to-end protection of n x ds0 services (ds0 bundles) over any TDM network
infrastructure. For description and instructions, refer to DS0 SNCP in Chapter 7.
Applicable Modules
This feature is available for the all VS and VS voice modules, except for E1/T1
modules.
Standards Compliance
DS0 bundle is RAD proprietary technology.
Benefits
DS0 bundle ports serve for establishing DS0 SNCP protection on the individual
timeslot level.
Functional Description
See DS0 SNCP (DS0-Bundle) Protection in Chapter 7.
Megaplex-4
DS0-Bundle Ports
5-39
Chapter 5 Cards and Ports
Installation and Operation Manual
Factory Defaults
Megaplex-4 is supplied with all DS0 bundle ports disabled. Other parameter
defaults are listed in the table below.
Parameter
Default Value
signaling-method
signaling-bit
control-bit
ts 1 bit D
Configuring DS0 Bundle Ports
To configure a DS0 bundle port:
1. Navigate to configure port ds0-bundle <slot>/<port> to select the ds0bundle port to configure.
The config>port> ds0-bundle >(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below:
Task
Command
Comments
Assigning short description
to the port
name <string>
Using no name removes the name
Administratively enabling
the port
no shutdown
Using shutdown disables the port
Set the signaling used for
path detection
signaling-method signaling-bit
signaling-bit is not supported over T1 links.
Binding the ds0-bundle
port to the protected/
protecting timeslots of the
service
bind {e1 | t1 | e1-i| t1-i | ds1 | ds1-opt }
<slot>/<port> [</tributary>] time-slot <ts
list>
It is supported only on E1 links using G.732S
or G.732S-CRC framing
Timeslots from any ports supporting
timeslot cross connect can be bound to a
ds0-bundle.
Using no before the corresponding
command removes the binding
19.
<ts list> can be in the format x,y,… for nonconsequent timeslots or in the format x..y
for non-consequent timeslots
[/tributary]> is relevant for T1-i ports of T3
modules and E1-i ports of OP modules
Binding a detection
timeslot bit to a ds0bundle port
control-bit ts <1..15, 17..31> bit {a | b |
c | d}
Viewing DS0-Bundle Status Information
For viewing the DS0-Bundle status information, follow the instructions below.
To view the DS0-Bundle status information:
1. Navigate to config>port> ds0-bundle (<slot>/<port>)#
5-40
DS0-Bundle Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
2. Type show status.
The status is displayed.
configure port ds0-bundle 4/1
config>port>ds0-bundle(4/1)# show status
Name
: IO-4 Ds0 Bundle 01
Administrative Status : Up
Operational Status
: Up
Rx Status
: In Sync
Tx Status
: In Sync
mp4100# configure port ds0-bundle 4/2
mp4100>config>port>ds0-bundle(4/2)# show status
Name
: IO-4 Ds0 Bundle 02
Administrative Status : Up
Operational Status
: Down
Rx Status
: OOS
Tx Status
: In Sync
Administrative
Status
Displays the administrative status of the corresponding DS0 bundle: Up or
Down
Operational Status
Displays the operation status of the corresponding DS0 bundle: Up or
Down
Rx/Tx Status
Displays the RX/TX status of the ds0-bundle port:
•
In Sync – the DS0 bundle is syncronized
•
OOS – Loss or LOF of the uplink frame or signaling-bit fail indication
Configuration Errors
The following tables list messages generated by Megaplex-4 when a configuration
error on DS0-bundle ports is detected.
Table 5-7. DS0 Bundle Configuration Error Messages
Code
Type
Syntax
Meaning
812
Error
PORT CAN BE BOUND TO LINK
WITH E1 MF ONLY
Signaling control ds0-bundle can be bound only to an E1
link with g732s or g732s-crc line-type
813
Error
PORT CAN'T BE BOUND TO
LINK WITH TDM GROUP
Ds0-bundle cannot be bound to a link which is a member
in tdm-group protection
814
Warning
PORT IS NOT MEMBER OF
ACTIVE DS0-GROUP
When ds0-bundle port is enabled (no shutdown), it has to
be a member of an active protection ds0-group
Megaplex-4
DS0-Bundle Ports
5-41
Chapter 5 Cards and Ports
Installation and Operation Manual
Displaying DS0-Bundle Statistics
DS0 bundle ports feature the collection of statistical diagnostics.
To display the DS0 bundle statistics:
•
At the prompt config>slot>port>ds0-bundle (<slot><port>)#, enter show
statistics followed by parameters listed below.
DS0 bundle statistics are displayed. The counters are described in the
table below. For example:
config>port>ds0-bundle(4/1)# show statistics
Time Elapsed (Sec) : 54
Frame Errors:
0
SES
:109
Table 5-8. DS0 Bundle Statistics Parameters
Parameter
Description
Time elapsed
The number of seconds that have elapsed since the latest of one of the
following events:
SES
•
Creation of the DS0 bundle.
•
Ds0BundleStatsClearTimeCmd was set to on (3).
•
Re-initialization of the agent.
Displays the total number of severely errored seconds since statistics is
available
To clear the statistics on a DS0 bundle port:
1. Navigate to the corresponding port.
2. Enter clear-statistics.
The statistics for the specified port are cleared.
5-42
DS0-Bundle Ports
Megaplex-4
Installation and Operation Manual
5.7
Chapter 5 Cards and Ports
DS1 Ports
Applicable Modules
The following table shows the number of ds1 ports and the features supported
by each Megaplex-4 module.
mpw-1
vs-fxs-em
tp
vs-6-e1t1
vs-12
vs-6-fxs
vs-6-bin
vs-6-fxo
vs-e1-t1-pw
vs-6-c37
vs-6-em
sh16-e1-pw
vs-6-fxs-pwacr
Feature/
Command
vs-6-fxo-pwacr
vs-6-em-pwacr
vs-g703
Number of
ports
8
12
12
8
4
16
name
√
√
√
√
√
√
shutdown
√
√
√
√
√
√
signaling
√
-
√
√
-
-
line-type
√
-
-
-
-
√
Idle-code
-
-
-
-
-
√
vc-profile
-
-
-
-
-
√
Functional Description
The internal DS1 ports are logical ports that provide the linkage between the
packet processing subsystem and the TDM subsystem:
Megaplex-4
•
On the TDM side, a DS1 port serves as an endpoint for traffic from the TDM
and signaling buses. Each I/O or E1-i/T1-i port in the Megaplex-4 that will use
pseudowires on a PW module must be assigned bandwidth (timeslots) on the
internal DS1 port, using the standard Megaplex-4 timeslot assignment
procedures.
•
On the pseudowire side, a DS1 port serves as the collection point for
timeslots to be carried by each pseudowire. Thus, to carry traffic from a
specific TDM port by means of a pseudowire, it is necessary to assign the
same timeslots on the TDM side and on the pseudowire side. The pseudowire
timeslot assignment is made as part of the pseudowire configuration
procedure, and it determines the cross-connect operations performed by the
DS1 Ports
5-43
Chapter 5 Cards and Ports
Installation and Operation Manual
pseudowire cross-connect matrix (see Configuring a PW-TDM Cross
Connection in Chapter 8).
When using the PW-equipped modules, the user can independently configure
each internal DS1 port in accordance with the table above.
Factory Defaults
Megaplex-4 is supplied with all DS1 ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
line-type
SH-16/E1/PW, VS-16E1T1-PW, VS-6/E1T1: g732s
Other modules: framed
signaling
disabled
tx-clock-source
domain 1
idle-code
0x7f
vc profile
tug-structure
Configuring Internal DS1 Port Parameters
To configure the internal DS1 port parameters:
20. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to configure.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
21. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no before name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying the code
transmitted to fill unused
timeslots
idle-code <00 to FF (hexa)>
Specifying the code transmitted to fill
unused timeslots
Specifying the framing
mode of the internal DS1
port (MPW-1 module)
5-44
DS1 Ports
This field is valid for SH-16/E1/PW,
VS-6/E1T1 and VS-E1T1/PW modules only.
This field is valid for MPW-1 only.
line-type {unframed | framed}
Make sure to select the same value at both
end points.
Megaplex-4
Installation and Operation Manual
Task
Command
Specifying the framing
mode of the internal DS1
port for SH-16/E1/PW,
VS-6/E1T1 and VSE1T1/PW modules
Chapter 5 Cards and Ports
Comments
These options are valid for the following
card types:
line-type {unframed | g732n | g732n-crc |
g732s | g732s-crc}
•
vs-e1-pw
•
vs-6-e1.
•
sh16-e1-pw.
Make sure to select the same value at both
end points.
These options are valid for the following
card types:
Specifying the framing
mode of the internal DS1
port for VS-6/E1T1 and
VS-E1T1/PW modules
line-type {unframed | esf | sf}
•
vs-t1-pw
•
vs-6-t1.
Make sure to select the same value at both
end points.
DS1 ports configured as framed (ESF) T1 do
not work with PW configured as SATOP.
Enabling transmitting an
out-of-service signal
(OOS) on PW failure
Assigning VC profile to
the port
signaling
vc profile <profile name>
This field is valid for MPW-1 and VS voice
only.
no signaling disables transmitting an OOS
signal
Relevant for SH-16/E1/PW, VS-16E1T1-PW
and VS-6/E1T1 modules.
For creating VC profiles, see VC Profiles.
Using no vc removes the profile.
Example
The following section illustrates how to configure the internal DS1 port 1 on the
MPW-1 module installed in slot 9:
•
Set the line type to unframed.
•
Administratively enable the port.
•
Leave all other parameters disabled or at their defaults.
config>port>ds1(9/1)# line-type unframed
config>port>ds1(9/1)# no shutdown
Viewing DS1 Port Status
Follow the instructions below for viewing the status of an internal DS1 port.
To view the DS1 port status:
•
At the config>port>ds1(<slot>/<port>)# prompt, enter show status.
The status information appears as illustrated below.
config>port>ds1(4/2)# show status
Name
: IO-4 Ds1 02
Megaplex-4
DS1 Ports
5-45
Chapter 5 Cards and Ports
Installation and Operation Manual
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
Testing DS1 Ports
The DS1 ports of all the PW-supporting I/O modules feature test and loopback
functions at the timeslot level. Some of them also feature test and loopback
functions per port (see the table below).
Table 5-9. Local and Remote Loopbacks on DS1 Ports
Modules
Per TS
Per Port
VS-6/BIN
v
v
v
-
VS-6/C37
VS-6/FXS, VS-6/FXO,
VS-6/E&M, VS-FXS/E&M
VS-6/E1T1
VS-E1T1/PW
SH-16/E1/PW
VS-6/703
TP
MPW-1
The following sections briefly describe each type of loopback on DS1 ports of I/O
modules. The table below shows the paths of the signals when each or loopback
is activated.
Table 5-10. Loopbacks on DS1 Ports of I/O Modules
I/O
Local loopback on DS1 port
CL
Port
Interface
DS1
Cross-Connect
Matrix
Port
Interface
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on DS1 port
5-46
DS1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
I/O
CL
I/O Interface
1
Local loopback on DS1 timeslots
2
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
1
Remote loopback on DS1 timeslots
2
..
..
.
DS1
Cross-Connect
Matrix
Local Loopback on DS1 Port of I/O Module
The local port loopback is used to test the path of the signals intended for
transmission through a selected DS1 port: this path starts at the other
Megaplex-4 port(s) connected to the selected port, passes through the
cross-connect matrix in the CL module, and continues up to the port line
interface. Within the tested module, the path includes most of the line interface
circuits serving the selected port, and the operation of the routing circuits that
handle the port signals within the module.
As shown in the table above, when a local loopback is activated, the port
transmit signal is returned to the input of the same port receive path at a point
just before the line interface. The local port must receive its own signal, and thus
it must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed “all-ones” signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on DS1 Port of I/O Module
The remote port loopback is used to test the line interface circuits of a selected
DS1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in the table above, when a remote loopback is activated on a DS1 port,
that port returns the received signal to the remote unit, via the transmit path.
The received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
Megaplex-4
DS1 Ports
5-47
Chapter 5 Cards and Ports
Installation and Operation Manual
The remote loopback should be activated only after checking that the remote unit
operates normally with the local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
If the local Megaplex-4 unit also operated normally when the local port loopback
was activated, then while the remote loopback is connected the local unit should
receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of DS1 I/O Module Port
The local loopback on selected timeslots of a DS1 port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the DS1 port.
As shown in the table above, the loopback is activated within the I/O module
routing matrix, and only on the timeslots specified by the user during the
activation of the loopback. As a result, there is no disturbance to services
provided by means of the other timeslots of the same port: only the flow of
payload carried by the specified timeslots is disrupted.
The user can activate the loopback on any individual timeslot, or on several
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
assigned to HDLC ports.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
Remote Loopback on Timeslots of DS1 I/O Module Port
The remote loopback on selected timeslots of a DS1 port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. This test is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the T1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
As shown in the table above, the loopback is activated within the I/O module
routing matrix, and only on the timeslots specified by the user. As a result, there
is no disturbance to services provided by means of the other timeslots of the
same port: only the flow of payload carried by the specified timeslots is
disrupted.
The other features related to loopback activation/deactivation described above
for the local loopback on timeslots are also applicable to the remote loopback.
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the PW modules. Therefore, when you initiate a loopback, you have the option
to limit its duration to a selectable interval in the range of 1 through 30 minutes.
5-48
DS1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks
To perform a loopback on the internal DS1 port:
1. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to be tested.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring
the direction of the
loopback and the duration
of it (in minutes)
loopback {local | remote} [timeslot <1..31>] [duration <duration
in minutes 1..30> ]
local – local loopback
Stopping the loopback
no loopback
remote – remote loopback
Configuration Errors
The following tables list messages generated by Megaplex-4 when a configuration
error on DS1 ports is detected.
Table 5-11. DS1 port Configuration Error Messages
Code
Type
Syntax
Meaning
434
Error
PORT LINE TYPE MISMATCH
When the CL module has no SDH/SONET ports, line-type
must not be configured as g732s or g732s-crc for the
following modules/ports:
•
SH16-E1-PW: ports DS1 1..16
•
VS-E1-PW: ports E1 9..16 or DS1 9..16
•
VS-6-E1: ports DS1 9..16.
Error 434 may also appear for other port types – refer to
the corresponding manual section.
769
Error
Megaplex-4
PORT SIGNALING MUST BE
DISABLED
The following modules/ports require signaling disabled:
•
VS-6/703: ports DS1 9..12
•
VS-6-FXS-PW-ACR: ports DS1 9..12
•
VS-6-FXO-PW-ACR: ports DS1 9..12
•
VS-6-EM-PW-ACR: ports DS1 9..12
DS1 Ports
5-49
Chapter 5 Cards and Ports
Installation and Operation Manual
DS1 Optical Ports
5.8
Applicable Modules
DS1 optical ports denote fiber optic links of VS-6/C37 modules.
Standards Compliance
IEEE C37.94
Functional Description
The IEEE C37.94 standard defines a programmable nx64 kbps (n = 1…12)
multimode optical fiber interface between teleprotection and digital multiplexer
equipment, for distances of up to 2 km.
The VS-6/C37 module features a dual-port fiber optic interface, operating at a
nominal wavelength of 830 nm and nominal line rate of 2.048 Mbps. Each port is
terminated in a pair of ST connectors for connection to standard multimode fiber.
The fiber optic interface has a wide dynamic range, which ensures that the
receiver will not saturate even when using short fiber optic cables (saturation is
caused when the optical power applied to the receiver exceeds its maximum
allowed input power, and results in very high bit error rates).
The interface can be used for both user and network ports – either for intersubstation communication or for transmitting distance Teleprotection
information.
Factory Defaults
Megaplex-4 is supplied with all ds1-opt ports disabled. Other parameter defaults
are listed in the table below.
Parameter
Default Value
inband-management
no inband-management (disabled)
inband-management – routing-protocol
none
Configuring DS1 Optical Port Parameters
To configure the DS1 optical link parameters:
1. Navigate to configure port ds1-opt <slot>/<port> to select the port to
configure.
The config>port>ds1-opt>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
5-50
DS1 Optical Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol
{ppp | fr} [routing-protocol {none | proprip | rip2} ]
VS modules only.
ppp – synchronous PPP over HDLC
encapsulation
fr –Frame Relay encapsulation (under
DLCI 100) in accordance with RFC
2427
See also Configuring Inband
Management in Chapter 8 for
important considerations on
selecting routing protocol.
Using no inband management
<timeslot> disables inband
management through this timeslot
Viewing a DS1-Opt Port Status
Follow the instructions below for viewing the status of the DS1-opt port 5/1 as
an example.
To view the DS1-opt port status:
•
At the config>port>ds1-opt (<slot>/<port>)# prompt, enter show status.
The status information appears as illustrated below.
config>port>ds1-opt(5/1)# show status
Name
: IO-5 Ds1 Opt01
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
Testing DS1 Optical Links
The test and diagnostics functions available on each optical link are:
•
Local loopback on local optical link
•
Remote loopback on local optical link
Local Digital Loopback (Local Loop)
The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
Megaplex-4
DS1 Optical Ports
5-51
Chapter 5 Cards and Ports
Installation and Operation Manual
While the loopback is connected, the local serial port should receive its own
signal.
The loopback signal path is shown below.
Figure 5-1. Local Loopback, Signal Path
Remote Digital Loopback (Remote Loop)
The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote serial port should receive its own
signal.
The loopback signal path is shown below.
Figure 5-2. Remote Loopback, Signal Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the VS-6/C37 module. Therefore, when you initiate a loopback, you have the
option to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local module before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
5-52
DS1 Optical Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
The default is infinite duration (without timeout).
Activating the Loopbacks
To perform a loopback on the DS1 optical link:
3. Navigate to configure port ds1-opt <slot>/<port> to select the optical link to
be tested.
The config>port>ds1-opt>(<slot>/<port>)# prompt is displayed.
4. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}
[duration <duration in minutes
1..30> ]
local – local loopback
Stopping the loopback
no loopback
5.9
remote – remote loopback
Ethernet Ports
Applicable Modules
Megaplex-4 features the following user Ethernet ports:
•
Two fiber optic or copper Gigabit Ethernet network ports on each CL.2
module
•
Eight fiber optic or copper Gigabit Ethernet network ports on each M-ETH I/O
module
•
Various fiber-optic/copper external Fast Ethernet user ports on the following
I/O modules: M8E1, M8T1, M8SL, OP-108C, OP-34C, ASMi-54C, ASMi-54C/N,
MPW-1, VS, D-NFV.
Optimux modules, in addition to external Ethernet ports, also have internal
Ethernet ports, serving to increase the total payload and management bandwidth
transferred to the optical link.
Standards Compliance
IEEE 802.3, RFC 4836, RFC 3635.
Functional Description
GbE Port Interfaces
The GbE ports on CL modules provide the physical connection to the packet
switched network. The GbE ports on M-ETH modules provide Megaplex-4 with a
multirate FE/GE interface, for optical or electrical media. This module can be used
to provide LAN connectivity among Ethernet ports on the same module, as well
Megaplex-4
Ethernet Ports
5-53
Chapter 5 Cards and Ports
Installation and Operation Manual
as Ethernet services, thus eliminating the need for an external switch while
providing a dependable Ethernet connectivity solution.
These ports can be ordered with one of the following interfaces:
•
10/100/1000BASE-T copper ports. This type of ports support
autonegotiation, with user-specified advertised data rate (10, 100 or
1000 Mbps) and operating mode (half- or full-duplex).
The ports also support automatic polarity and crossover detection, and
polarity correction, for connection through any type of cable to any type of
Ethernet port (hub or station).
Alternatively, auto-negotiation can be disabled and the rate and operating
mode be directly specified.
•
SFP sockets, for installing 100/1000BASE-X SFP plug-in modules. Support for
standard SFP optical transceivers for the GbE link interfaces enables selecting
the optimal interface for each application. This type of ports does not
support autonegotiation.
The interfaces support Synchronous Ethernet (Sync-E) master and slave modes
according to ITU-T G.8261–G.8266 requirements. This allows each port to:
•
Extract the port clock. The derived clock will be used by the clock selection
mechanism as a source clock
•
Set the port Tx clock according to the domain clock available from the CL
module
•
Act as a source of ESMC messages for SSM-based clock modes.
Fast Ethernet Port Interfaces
The external Ethernet ports have 10/100 Mbps interfaces capable of
auto-negotiation. The user can configure the advertised data rate (10 or
100 Mbps) and operating mode (half-duplex or full-duplex). Alternatively,
auto-negotiation can be disabled, and the rate and operating mode be directly
specified.
The Ethernet ports can be ordered with one of the following types of interfaces:
•
Sockets for SFP Fast Ethernet transceivers. RAD offers several types of SFPs
with optical interfaces, for meeting a wide range of operational requirements
(SFPs with copper interfaces are also available). The SFPs are hot-swappable.
•
10/100BASE-TX interfaces terminated in RJ-45 connectors. In addition to
auto-negotiation, MDI/MDIX polarity and cross-over detection and automatic
cross-over correction are also supported. Therefore, these ports can always
be connected through a “straight” (point-to-point) cable to any other type of
10/100BASE-T Ethernet port (hub or station).
The ordering options depend on the specific I/O module.
Hierarchy and Values
The following table shows the number of Ethernet ports on each Megaplex-4
module, their CLI denomination, hierarchy and possible values. The hierarchical
position of external Ethernet ports is slot:port for all the modules. The internal
5-54
Ethernet Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Ethernet ports of the Optimux modules are designed as slot:port:tributary (in
these modules port=mux_eth_tdm).
Table 5-12. Ethernet Ports on I/O Modules
Modules
CLI Name
Hierarchy
Possible Values
M-ETH
ethernet
slot: port
1..8
M8E1, M8T1, M8SL
ethernet
slot: port
1..3
OP-108C
ethernet
slot:port
1..2
int-eth
slot:port:tributary
1/1, 3/1
(port = mux_eth_tdm)
(tributary = int-eth)
OP-34C
ethernet
slot:port
1
int-eth
slot:port:tributary
1/1
(port = mux_eth_tdm)
(tributary = int-eth)
ASMi-54C,
ASMi-54C/N
ethernet
slot:port
1..2
MPW-1
ethernet
slot:port
1..3
VS
ethernet
slot:port
1 per submodule
D-NFV
ethernet
slot:port
1..4
int-eth
slot:port
1
For more information, see the respective module section in Megaplex-4 I/O
Modules Installation and Operation Manual, Voice Modules Chapter.
Flow Control
A flow control is a mechanism that allows an Ethernet receiving end that is
unable to process all the traffic sent to it, to hold the transmitted traffic until it is
able to process packets again.
The mechanism uses a PAUSE frame, which is a packet that instructs the far-end
device to stop transmission of packets until the receiver is able to handle traffic
again. The PAUSE frame has a timer value included (set by the originating
receiver), which tells the far-end device how long to suspend transmission. If that
timer expires or is cleared by getting a PAUSE frame with timer value set to 0, the
far-end device can then send packets again. Flow control is an optional port-level
parameter.
Flow control is supported on both directly- and indirectly-attached ports:
•
Directly-attached ports support symmetrical flow control (both Rx and Tx)
•
Indirectly-attached ports support Rx flow control only, without issuing Tx
PAUSE frames (asymmetric flow control).
When autonegotiation is enabled, flow control mode is negotiated and a port
advertises its user-selected flow control capabilities to the peer. The actual flow
Megaplex-4
Ethernet Ports
5-55
Chapter 5 Cards and Ports
Installation and Operation Manual
control mode, as well as duplex mode and transmission speed are set after the
negotiation is completed.
When autonegotiation is disabled, the flow control mode is manually selected by
the user.
All Megaplex-4 Ethernet interfaces, except the OOB management port, support
flow control.
L2CP Handling
Megaplex-4 handles Layer-2 control protocol traffic on a per-port basis. The L2CP
traffic is processed using a two-stage mechanism comprising per-port L2CP
profiles (set of rules for traffic handling). The L2CP profile affects untagged L2CP
frames. In total, Megaplex-4 supports up to 16 L2CP profiles:
•
Up to 4 (including default) port-level profiles can be defined on directlyattached ports
•
Up to 32 different addresses/protocols can be selected per L2CP profile.
If no default action is configured for an unspecified address or protocol, this
traffic is tunneled.
Note
If an L2CP profile has been attached to a port, the profile cannot be deleted or
modified.
L2CP Profile Settings
Megaplex-4 can tunnel, discard or peer (trap to host for protocol processing)
L2CP packets. These actions are defined by L2CP profiles, which also provide
different L2CP addresses. The following MAC addresses are supported by L2CP
profiles: 01-80-C2-00-00-00, 01-80-C2-00-00-02 – 10 and 01-80-C2-00-00-20 –
2F.
Note
PAUSE frames (01-80-C2-00-00-01) are not part of L2CP profiles. They are either
peered or discarded according to flow control setting of a port.
According to L2CP profiles, Megaplex-4 performs the following:
Note
•
Discards L2CP traffic.
•
Tunnels L2CP traffic. Megaplex-4 forwards the traffic according to its
configuration (flows etc).
•
Peers L2CP traffic. Megaplex-4 forwards the traffic to the CPU.
Megaplex-4 supports peer action only for the following MAC addresses/protocols:
•
01-80-C2-00-00-00 (RSTP)
•
01-80-C2-00-00-02 (LACP, OAM (EFM))
•
01-80-C2-00-00-03 (802.1x).
Default L2CP Profile
By default, a “tunnel all” profile is attached to every port.
5-56
Ethernet Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Autonegotiation
The speed and duplex mode of an Ethernet interface is set either manually by the
operator or negotiated with the peer interface. The autonegotiation procedure
enables automatic selection of the operating mode on a LAN. It enables
equipment connecting to an operating LAN to automatically adopt the LAN
operating mode (if it is capable of supporting that mode).
Queue Group Profile
Queue group profiles are the largest entities used in pre- and post-forwarding
traffic management. They are attached to physical ports and consist of queue
block and shaper profiles. See Queue Group Profiles section in Chapter 8 for
details.
Factory Defaults
By default, the Ethernet non-management ports have the following configuration.
Fast Ethernet ports:
config>port>eth(4/1)# info detail
name "IO-4 ethernet 01"
shutdown
auto-negotiation
max-capability 100-full-duplex
no flow-control
no policer
egress-mtu 1790
queue-group profile "FeDefaultQueueGroup"
no l2cp
tag-ethernet-type 0x8100
GbE ports of CL modules:
config>port>eth(cl-b/1)# info detail
name "CL-B ethernet 01"
shutdown
auto-negotiation*
max-capability 1000-full-duplex**
min-tagged-frame-length 68
no efm
no shaper
egress-mtu 1790
queue-group profile "GbeDefaultQueueGroup"
l2cp profile "L2cpDefaultProfile"
tag-ethernet-type 0x8100
GbE ports of M-ETH modules:
config>port>eth(7/4)# info detail
name "IO-7 ethernet 04"
shutdown
auto-negotiation*
max-capability 1000-full-duplex**
no flow-control
no efm
no policer
Megaplex-4
Ethernet Ports
5-57
Chapter 5 Cards and Ports
Installation and Operation Manual
egress-mtu 1790
queue-group profile "MeDefaultQueueGroup"
no l2cp
tag-ethernet-type 0x8100
*copper ports only
**for fiber ports: 1000-x-full-duplex
For description of default queue group profiles, see Queue Group Profiles section
in Chapter 8.
Configuring User Ethernet Ports
To configure the user Ethernet port parameters (any module with Ethernet ports):
1. Navigate to configure port ethernet <slot>/<port> to select the Ethernet port
to configure.
The config>port>eth>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed in the table
below.
Task
Command
Comments
Assigning short description to the
port
name <string>
Using no name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Enabling autonegotiation
auto-negotiation
For copper ports only
Using no auto-negotiation disables
autonegotiation
Enabling OAM (EFM) on the
Ethernet port
efm
See Ethernet OAM (EFM) in Chapter 8.
GbE ports of CL.2 and M-ETH modules only
no efm disables OAM (EFM) on the Ethernet
port
Setting maximum frame size (in
bytes) to transmit (frames above
the specified size are discarded)
5-58
Ethernet Ports
egress-mtu <64–9600>
The maximum frame size for GBE Ethernet
ports of CL and M-ETH modules is 9600.
The maximum frame size for Fast Ethernet
ports of different I/O modules is as follows:
•
ASMi-54C/N – 9600
•
VS/SH/D-NFV – 9140
•
M8E1, M8T1, M8SL, OP-34C, OP-108C,
ASMi-54C/N, MPW-1,
•
ASMi-54C – 1522.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Setting maximum advertised
capability (highest traffic handling
capability to be advertised during
the autonegotiation process)
max-capability {10-half-duplex |
10-full-duplex | 100-half-duplex |
100-full-duplex | 1000-full-duplex
| 1000-x-full-duplex}
10-full-duplex –10baseT full duplex (copper
ports only)
10-half-duplex – 10baseT half duplex (copper
ports only)
100-full-duplex – 100baseT full duplex
100-half-duplex – 100baseT half duplex (in
the case of M-ETH – copper ports only)
1000-full-duplex – 1000base T full duplex
(copper GbE ports only)
1000-x-full-duplex – 1000base T full duplex
(fiber GbE ports only)
This parameter applies only if
autonegotiation is enabled.
Setting data rate and duplex
mode of the Ethernet port, when
autonegotiation is disabled
speed-duplex 10-half-duplex | 10full-duplex | 100-half-duplex |
100-full-duplex | 1000-full-duplex
| 1000-x-full-duplex}
10-full-duplex –10baseT full duplex (copper
ports only)
10-half-duplex – 10baseT half duplex (copper
ports only)
100-full-duplex – 100baseT full duplex
100-half-duplex – 100baseT half duplex (in
the case of M-ETH – copper ports only)
1000-full-duplex – 1000base T full duplex
(copper GbE ports only)
1000-x-full-duplex – 1000base T full duplex
(fiber GbE ports only)
Setting flow control for the
selected port (when operating in
the full duplex mode), or back
pressure (when operating in the
half-duplex mode)
flow-control
Using no flow-control disables flow control
Assigning queue group profile to
Ethernet port
queue-group profile <queuegroup-profile-name>
Megaplex-4 with CL.2/A modules only
The queue group profile is defined under
Quality of Service (QoS) in Chapter 8.
no queue-group removes queue group
association
The default queue group profile for Fast
Ethernet ports is defined with 10 Mbps
shaper. Define a new queue group profile if
you need more bandwidth.
The queue group profile cannot be edited.
Thus to use bridge connectivity you need to
remove the existing queue group profile from
this Ethernet port, configure a new queue
group profile and assign it to this port.
Megaplex-4
Ethernet Ports
5-59
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Associating a Layer-2 control
processing profile with the port
l2cp <l2cp-profile-name>
Megaplex-4 with CL.2/A modules only
no l2cp
GbE ports of CL.2 and M-ETH modules only
Defines discarding or tunneling policy for
Layer-2 protocols.
no l2cp removes association with L2CP profile
The associated L2CP profile specifies peer
action for the following MAC addresses
depending on the protocol in use:
•
01-80-C2-00-00-00 (RSTP)
•
01-80-C2-00-00-02 (LACP, OAM (EFM))
•
01-80-C2-00-00-03 (802.1x).
Configuring collection of
performance management
statistics for this port, which are
presented via the RADview
Performance Management portal
pm-collection interval <seconds>
You can enable PM statistics collection for all
Ethernet ports rather than enabling it for
individual ports. In addition to enabling PM
statistics collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Activating/deactivating a policer
profile
policer-profile <name>
The policer profile is defined under Quality of
Service (QoS) in Chapter 8.
Using no policer <name> deactivates this
policer profile
The total sum of bandwidths defined in
policer profiles for all 8 ports of the M-ETH
module must not exceed 1 GbE.
Setting the minimum VLAN-tagged
frame length (in bytes) that will
be accepted
min-tagged-frame-length {64 | 68
| 72}
CL GbE and internal D-NFV ports only
Specifying the Ethertype expected
in Ethernet packet
tag-ethernet-type
<0x0000-0xFFFF>
Megaplex-4 with CL.2/A modules only
Enabling transmitting of Sync-E
clock availability and quality via
ESMC messages
tx-ssm
CL GbE ports only
no tx-ssm disables ESMC messages
transmission
To configure the internal Ethernet port parameters (Optimux cards only):
1. Navigate to configure port ethernet <slot>/<port>/<tributary> to select the
internal Ethernet port to configure.
The config>port>eth>(<slot>/<port>/<tributary>)# prompt is displayed.
2.
Enter all necessary commands according to the tasks listed in the below.
Task
Command
Comments
Assigning short description to the port
name <string>
Using no name removes the name
5-60
Ethernet Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Administratively enabling the port
no shutdown
Using shutdown disables the port
Setting maximum frame size (in bytes) to
transmit (frames above the specified size
are discarded)
egress-mtu <64–1600>
Assigning queue group profile to Ethernet
port
queue-group <queuegroup-profile-name>
no queue-group removes queue group
association
The default queue group profile for Fast
Ethernet ports is defined with 10 Mbps shaper.
Define a new queue group profile if you need
more bandwidth.
Specifying the Ethertype expected in
Ethernet packet
tag-ethernet-type
<0x0000-0xFFFF>
Example
To configure the Ethernet interface:
•
Port – port 1 on CL-A module
•
Autonegotiation – enabled
•
L2CP profile – l2cp_prof1
•
Maximum frame size to transmit – 9600 bytes
•
Queue group profile –_group1
•
Administratively enabled.
# config port eth cl-a/1 no shutdown
# configure port ethernet cl-a/1 queue-group profile group1
# configure port ethernet cl-a/1 l2cp prof1
# configure port ethernet cl-a/1 egress-mtu 9600
Displaying Ethernet Port Status
You can display the status and configuration of an individual external Ethernet
port. Status of internal Ethernet ports of Optimux modules cannot be displayed.
To display status of an Ethernet port:
•
At the prompt config>port>eth(<slot>/<port>)#, enter show status.
The Ethernet port status parameters are displayed.
For example: Module – M8E1, Slot – 6, Ethernet port – 1, copper SFP-9F
connector.
config>port>eth(6/1)# show status
Name
:
Administrative Status : Up
Operation Status
: Up
Connector Type
: SFP In
Megaplex-4
Ethernet Ports
5-61
Chapter 5 Cards and Ports
Installation and Operation Manual
Auto Negotiation
: Enabled
Speed And Duplex
: 100 Half Duplex
SFP
--------------------------------------------------------Connector Type
: Copper
Manufacturer Name
: RAD data comm.
Manufacturer Part Number
: SFP-9F
Typical Maximum Range (Meter) : 100
Wave Length (nm)
: Not Applicable
Fiber Type
: Not Applicable
Note
For GbE ports, assigned MAC addresses are also displayed. For MAC address
allocation mechanism, see Chapter 10.
Testing Ethernet Ports
No testing is available.
Configuration Errors
The following tables list messages generated by Megaplex-4 when a configuration
error on Ethernet ports is detected.
Table 5-13. Ethernet Configuration Error Messages
Code
Type
Syntax
Meaning
407
Error
SUM POWER EXCEEDED
The total allocated power per Megaplex-4 system must
not exceed 250W.
There is limitation of 250W, per Megaplex-4 chassis, due
to PS limitation. These 250W are shared between the
following modules:
•
Voice FXS (VC) modules – consuming 1.5W per port.
•
ASMi-54C with power feeding – consuming 3.5W per
port.
This sanity appears if you open too many ports, with
overall consumption of more than 250W. To correct,
close some ports.
587
Warning
SUM OF POLICERS RATE
EXCEED SUPPORTED BW
The total sum of bandwidths defined in policer profiles for
all 8 ports of the M-ETH module must not exceed 1 GbE.
Displaying Ethernet Port Statistics
The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819. The statistics are available both on external Ethernet ports and
internal Ethernet ports of Optimux modules.
To display the internal Ethernet port statistics on Optimux modules:
•
5-62
At the prompt config>slot>port>eth(<slot>/<port>/<tributary>)#, enter show
statistics:
Ethernet Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
OP-108C section OP A, OP-34C: <port>/<tributary> = 1/1
OP-108C section OP B: <port>/<tributary> = 3/1
To display the external Ethernet port statistics:
•
At the prompt config>slot>port>eth(<slot>/<port>)#, enter show statistics.
Ethernet port statistics are displayed. The counters are described in the
table below.
Screens and counters are different for Fast Ethernet ports of I/O modules
and GbE ports of CL.2 modules.
M8E1 Module:
config>port>eth(8/1)# show statistics
Running
--------------------------------------------------------------Counter
Rx
Tx
Total Frames
0
0
Total Octets
0
0
Unicast Frames
0
0
Multicast Frames 0
0
Broadcast Frames 0
0
Paused Frames
0
FCS Errors
0
Filtered Frames 0
Jabber Errors
0
Undersize Frames 0
Oversize Frames 0
0
------
64 Octets
0
65-127 Octets
0
128-255 Octets
0
256-511 Octets
0
512-1023 Octets 0
1024-1528 Octets 0
-------
M-ETH Module:
config>port>eth(7/3)# show statistics
Running
----------------------------------------------------------------Counter
Rx
Tx
Total Frames
0
9
Total Octets
0
2002
Unicast Frames
0
0
Multicast Frames 0
0
Broadcast Frames 0
9
Paused Frames
0
FCS Errors
0
Filtered Frames 0
Jabber Errors
0
Undersize Frames 0
Oversize Frames 0
Discard Frames
-Megaplex-4
0
-----0
Ethernet Ports
5-63
Chapter 5 Cards and Ports
Installation and Operation Manual
64 Octets
0
0
65-127 Octets
0
128-255 Octets
0
256-511 Octets
0
512-1023 Octets 0
1024-1518 Octets 0
1519-Max Octets 0
4
0
5
0
0
0
CL.2 Module:
config>port>eth(cl-a/1)# show statistics
Running
--------------------------------------------------------------Counter
Rx
Tx
Total Frames
0
0
Total Octets
0
0
Unicast Frames
0
0
Multicast Frames
0
0
Broadcast Frames
0
0
Single Collision
Paused Frames
FCS Errors
-0
0
0
0
--
Table 5-14. Ethernet Statistics Parameters
Parameter
Description
Total Frames
Total number of frames received/transmitted
Total Octets
Total number of bytes received/transmitted
Unicast Frames
Total number of unicast frames received/transmitted
Multicast Frames
Total number of multicast frames received/transmitted
Broadcast Frames
Total number of broadcast frames received/transmitted
Single Collision
The number of successfully transmitted frames on this
interface for which transmission is inhibited by exactly one
collision.
Paused Frames
Total number of pause frames (used for flow control)
received/transmitted through the corresponding Ethernet port
FCS Errors
The number of frames received on this interface that are an
integral number of octets in length but do not pass the FCS
check
Filtered Frames
Total number of filtered frames received/transmitted
I/O Ethernet ports only
Jabber Errors
Total number of frames received with jabber errors
I/O Ethernet ports only
Oversize Frames
Total number of oversized frames received/transmitted
I/O Ethernet ports only
Undersize Frames
Total number of undersized frames received/transmitted
I/O Ethernet ports only
Discard Frames
Total number of discarded frames received/transmitted
M-ETH ports only
5-64
Ethernet Ports
Note
CL.2 GbE ports only
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Description
Note
64 Octets
Total number of received/transmitted 64-byte packets
I/O Ethernet ports only
65–127 Octets
Total number of received/transmitted 65–127-byte packets
I/O Ethernet ports only
128–255 Octets
Total number of received/transmitted 128–255-byte packets
I/O Ethernet ports only
256–511 Octets
Total number of received/transmitted 256–511-byte packets
I/O Ethernet ports only
512–1023 Octets
Total number of received/transmitted 512–1023-byte packets
I/O Ethernet ports only
1024–1518 Octets
Total number of received/transmitted 1024–1518-byte
packets
I/O Ethernet ports only
1519 - Max Octets
Total number of received/transmitted packets with 1519
bytes and up to maximum
M-ETH ports only
To clear the statistics for an Ethernet port:
•
At the prompt config>port>eth<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.10 E1 Ports
Applicable Modules
The following table shows the number of E1 and E1-i ports and their features
supported by each Megaplex-4 module. The hierarchical position of e1 and e1-i
ports is slot:port for all the modules, with the exception of Megaplex cards
OP-108C and OP-34C, where it is slot:port:tributary (in these modules
slot:port=mux_eth_tdm). The digits in brackets (1 to 4) denote restrictions or
other special remarks regarding implementation of this feature in specific
modules.
Table 5-15. Features Supported by Megaplex-4 External E1 Ports
Feature/
M8E1
M16E1
OP-108C
OP-108C/
OP-34C
ASMi-54C/N
E1
Command
VS-
VS-
16E1T1-
16E1T1-PW
VS-6/E1T1
EoP
Number of ports
8
16
8
8
16
8
16
16
8
name
√
√
√
√
√
√
√
√
√
shutdown
√
√
√
√
√
√
√
√
√
inband-
√(1)
√(1)
√(1)
–
√(1)
√(1)
√(8)
√(1)
√(1)
√
√
–
√
–
√
√
√
√
management
interface-type
Megaplex-4
E1 Ports
5-65
Chapter 5 Cards and Ports
M8E1
Feature/
Installation and Operation Manual
M16E1
OP-108C
OP-108C/
OP-34C
ASMi-54C/N
E1
Command
VS-
VS-
16E1T1-
16E1T1-PW
VS-6/E1T1
EoP
line-type
√
√
√
–
√
out-of-service
√
√
√
–
(voice, data)
(2)(1)
(2)(1)
(2)(1)
restoration-time
√
–
–
rx-sensitivity
√
–
√
signaling- profile
(1)(4)
timeslots-signaling-
√
profile
(1)(4)
idle-code
√ (1)
√
√(9)
√
√
√
(2)(1)
(2)(1)
–
–
–
–
–
–
–
–
–
–
–
√ (1)
√ (1)
√
√
√
√
(2)(1)
(2)(1)
–
–
–
–
√
√
√
–
–
–
–
–
–
–
–
–
–
–
–
√ (1)
√ (1)
√
√ (1)
√ (1)
–
–
–
√
–
–
–
ts0-over-dsl
remote-crc
vc-profile
–
√ (7)
√ (7)
–
√ (7)
√ (7)
√ (7)
√ (7)
√ (7)
tx-clock-source
–
–
–
–
–
–
–
√ (10)
√ (10)
Table 5-16. Features Supported by Megaplex-4 Internal E1 Ports
CL.2
Feature/
M8SL
Command
ASMi-54C/N,
VS-16E1T1-EoP
SH-16/E1
ASMi-54C/N: 8
Number of ports
63
8
SH-16/E1: 16
16
name
√
√
√
√
shutdown
√
√
√
√
inband-management
√(1)
√(1)
√(1)
–
interface-type
–
–
–
–
line-type
√
√(6)
√
√(9)
out-of-service (voice,
√ (2)(1)
–
data)
√
√
(2)(1)
(2)(1)
restoration-time
–
–
–
–
rx-sensitivity
–
–
–
–
signaling- profile
–
√ (1)(4)
–
–
timeslots-signaling-
–
√ (1)(4)
–
–
√ (1)
√(1)
√(1)
–
profile
idle-code
5-66
E1 Ports
Megaplex-4
Installation and Operation Manual
CL.2
Feature/
M8SL
Command
Chapter 5 Cards and Ports
ASMi-54C/N,
VS-16E1T1-EoP
SH-16/E1
ts0-over-dsl
√
√
–
remote-crc
√(5)
–
–
√ (7)
√
√
vc-profile
1 - N/A for Unframed
2 - OOS voice and signaling N/A for line-type=g732n/g732n-crc
3 – Unframed not supported
4 - N/A for line-type=g732n/g732n-crc
5 – Applicable if ts0-over-dsl is looped and line-type is g732n
6 - N/A for line-type=g732n-crc/g732n-crc
7 - Applicable if line type is Unframed and the link is directly mapped to SDH-SONET vc12-vt2
8 –N/A for E1 bound to VCG
9 –When E1 is bound to VCG, line-type=g732n-crc only
10 – Applicable when E1 is cross connected directly to PW
Note
OP-108C/E1 are LRS-102 modules with E1 physical ports, which can also be
installed and operate in Megaplex-4.
Standards Compliance
The E1 link interfaces meet the applicable requirements of ITU-T Rec. G.703,
G.704, G.706, G.732, and G.823.
Functional Description
External E1 Link Interfaces are available in M8E1, M16E1, OP-108C/E1, VS-6/E1T1,
VS-16E1T1-PW, VS-16E1T1-EoP and ASMi-54C/N I/O modules. Internal E1 ports
are available in CL.2, M8SL, VS-16E1T1-EoP and ASMi-54C/N I/O modules.
The Megaplex-4 Optimux modules (OP-108C and OP-34C) also have internal ports
but of other type than E1-i. These ports are designed and configured as “E1” but
hierarchically they hold tributary positions, such as <slot>/<port>/<tributary>.
The parameters configurable for each module can be chosen from Table 5-16 . E1
port parameters are described in the following sections.
Framing
The external and internal E1 ports can be independently configured in accordance
with the desired ITU-T framing mode and signaling formats:
•
Megaplex-4
Basic G.704 framing (identified as G.732N) for applications that require CCS.
E1 Ports
5-67
Chapter 5 Cards and Ports
Installation and Operation Manual
•
G.704 framing with timeslot 16 multiframe (identified as G.732S and referred
to as G.704 multiframe mode) for applications that require CAS.
•
Unframed mode for transparent transfer of 2.048 Mbps streams, including
streams with proprietary framing. Also enables transferring framed E1
streams without terminating timeslot 0, and timeslot 16.
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode can be independently selected for each external or internal E1
port of the I/O module. It is configured by means of the line-type parameter.
Interface Type
The external ports support two line interfaces:
•
120Ω balanced line interface. The nominal balanced interface transmit level is
±3V.
•
75Ω unbalanced interface. The nominal unbalanced interface transmit level is
±2.37V.
Only one of these interfaces can be active at any time. The active interface can
be selected by the user, separately for each port.
Receive Signal Attenuation (M8E1, VS-6/E1T1, VS-16E1T1-PW
and VS-16E1T1-EoP Modules)
The E1 line interfaces have integral LTUs, which enable long-haul operation with
line attenuation of up to 43 dB. The line interface can also emulate a DSU
interface, for short-haul applications: in this case, the maximum line attenuation
is 12 dB. The receive signal attenuation level is configured by means of the
rx-sensitivity parameter. In addition, this parameter can be also configured to
monitor E1 services, with line attenuation of up to12 dB.
Note
To assure effective monitoring for M8E1, connect two 510 Ω resistors between
the monitored line and the monitoring port. The resistors should be connected in
series between the monitored line and the monitoring port, one resistor for the
TIP wire and the second one for the RING wire.
E1 Payload Processing
Megaplex-4 E1 modules support three main types of payload per timeslot:
•
Data timeslots: timeslots which are transparently transferred from port to
port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
•
Voice timeslots: timeslots carrying PCM-encoded payload, with A-law
companding for M8E1 ports and µ-law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
5-68
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
standards. The user can specify translation rules for the signaling information
by defining signaling profiles – see details in the Signaling Profiles section.
•
Management timeslots: with framed signals, one timeslot per port can be
assigned to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). However, it is also possible to define unidirectional flows, called
unidirectional broadcasts, from one source (a timeslot of a source port) to
multiple destinations (each destination being a selected timeslot of another
port).
In case of data timeslots, the flow of payload is normally unidirectional. If the
application requires bidirectional flows, cross-coneect must be configured
symmetrically for both directions.
Handling E1 Alarm Conditions
External and internal E1 ports using framed mode support two types of indications
in the individual timeslots:
•
Idle Timeslot Indication. A special code can be transmitted in empty timeslots
(timeslots which do not carry payload).
•
OOS Indications. The OOS code is inserted in individual timeslots to signal the
equipment routed to one of the E1 ports of the module that the link
connected to the external port is out-of-service (e.g., because of loss of
frame synchronization).
For ports using a G.704 timeslot 16 multiframe mode, the CAS information
can also be replaced by a selectable OOS indication.
The idle code and OOS indications can be independently configured for each port.
Moreover, separate OOS codes can be transmitted in the timeslots, in accordance
with the type of payload carried by each timeslot (voice or data).
OOS Signaling
If the communication between modules located in different Megaplex units fails,
e.g., because loss of main link synchronization, etc., it is necessary to control the
state of the signaling information at the two ends of the link. This activity, called
out-of-service (OOS) signaling, is performed by the E1 interfaces and can be
selected in accordance with the specific application requirements, on a per-link
basis.
The OOS signaling options supported by the E1 module ports are as follows:
Megaplex-4
•
Signaling forced to idle state for the duration of the out-of-service condition
(force-idle). This option is suitable for use with all the VC module types.
•
Signaling forced to busy state for the duration of the out-of-service condition
(force-busy). This option is suitable for use with E&M and FXO modules, but
not with FXS modules.
•
Signaling forced to idle state for 2.5 seconds, and then changed to busy
state for the remaining duration of the out-of-service condition (idle-busy).
This option is suitable for use with E&M and FXO modules, but not with FXS
modules.
E1 Ports
5-69
Chapter 5 Cards and Ports
•
Installation and Operation Manual
Signaling forced to busy state for 2.5 seconds, and then changed to idle
state for the remaining duration of the out-of-service condition (busy-idle).
This option is suitable for use with all the VC module types.
Inband Management
E1 and internal E1 ports of Megaplex-4 using a framed mode feature inband
management access to the end user’s equipment provided by configuring a
dedicated management timeslot.
The transfer of inband management traffic is controlled by using synchronous
PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
RIP2 routing tables are transmitted as follows:
•
Proprietary RIP – Management traffic is routed using RAD proprietary routing
protocol
•
RIP2 – In addition to the RAD proprietary routing protocol, RIP2 routing is
also supported.
Interoperability with Nokia clock distribution (PDH Sync)
Megaplex-4 features an ability to lock the system to a single master in order to
avoid timing loops. This can be done using a Nokia-compatible DS0-based
protocol running over two user configurable bits in TS0 (selected out of TS0
spare bits). The master can be connected to Megaplex or Nokia device.
In loop network branching equipment, two loop network TS0 control bits are used
for monitoring of the network state and for controlling the synchronization.
These bits are MCB (Master Clock Bit) and LCB (Loopback Clock Bit). These control
bits are transmitted from the station with clock source of the network in 0-state
and, as they proceed through the network, they indicate to the slave stations
whether the clock of the RX direction in question comes from the Network
Master clock source (MCB=0) and whether there are clock loopbacks in the RX
direction concerned (LCB=1).
This feature is available for E1 ports of the M8E1 modules.
Factory Defaults
Megaplex-4 is supplied with all e1/e1-i ports disabled. Other parameter defaults
are listed in the table below.
5-70
E1 Ports
Parameter
Default Value
line-type
g732s
restoration-time
immediate
rx-sensitivity
short-haul
interface-type
balanced
idle-code
0x7f
inband-management
no inband-management (disabled)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Default Value
inband-management – routing-protocol
none
out-of-service - voice
0x00
out-of-service - data
0x00
out-of-service - signaling
force-idle
signaling-profile
no signaling-profile
ts0-over-dsl
enabled
vc profile
tug-structure
clock-source-bit
master: SA7
loopback: SA8
Configuring E1 Ports
To configure the E1 port parameters of OP-108C, OP-34C modules:
1. Navigate to configure port e1 <slot>/< mux-eth-tdm port>/<tributary> to
select the E1 port to configure.
The config>port>e1>(<slot>/<mux-eth-tdm port>/<tributary>)# prompt is
displayed.
Note
Tributary e1 ports of Megaplex Optimux modules are actually internal ports but of
type other than e1-i.
• For OP-108C, <port>/<tributary> is 1/1 to 1/4 and 3/1 to 3/4. Tributaries 2/x
and 4/x do not exist.
•
For OP-34C, <port>/<tributary> is 1/1 to 1/16. Tributaries 2/x do not exist.
To configure the E1 port parameters of other modules:
1. Navigate to configure port e1 <slot>/<port> to select the E1 port to
configure.
The config>port>e1>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below (see
Table 4-5 for parameters supported in each module).
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Setting TS0 bits as
master and loopback
clock source bits (M8E1
only)
clock-source-bit [master
{ SA4 | SA5 | SA6 | SA7 | SA8 }]
Using no clock-source-bit disables the
settings.
[loopback { SA4 | SA5 | SA6 | SA7 | SA8 }]
Non-used SA are set to “1”.
Megaplex-4
E1 Ports
5-71
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Specifying E1 framing
mode
line-type {unframed | g732n
| g732n-crc | g732s | g732s-crc}
When the E1 port is bound to a VCG port,
VS-16E1T1-EoP supports g732n-crc option
only.
Setting attenuation level
of the receive signal
rx-sensitivity {short-haul | long-haul |
monitor }
M8E1 and VS E1T1 modules only:
short-haul – low sensitivity (-12 dB)
long-haul – high sensitivity (-43 dB)
monitor – monitor sensitivity (-12 dB)
Specifying port
impedance
interface-type {balanced | unbalanced}
Specifying the code
transmitted to fill unused
timeslots in E1 frames
idle-code { 00 to FF (hexa) }
The available selections are [0x01 to 0xFF]
with the following values that are illegal:
0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol
{ppp | fr} [routing-protocol {none | proprip | rip2} ]
ppp – synchronous PPP over HDLC
encapsulation
fr –Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
See also Configuring Inband Management in
Chapter 8 for important considerations on
selecting routing protocol.
Not available for VS-16E1T1-EoP modules
when this E1 port is bound to a VCG port
Using no inband management <timeslot>
disables inband management through this
timeslot
Transmitting an
out-of-service signal
(OOS)
out-of-service [voice <00 to FF (hexa)>] [
data <00 to FF (hexa)>] [signaling
{force-idle | force-busy | idle-busy |
busy-idle}]
The hexadecimal number is in the range of 0
to FF (two digits)
The selected out-of-service data code is
also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
Configuring collection of
performance
management statistics
for this port, which are
presented via the
RADview Performance
Management portal
5-72
E1 Ports
pm-collection interval <seconds>
You can enable PM statistics collection for
all E1 ports rather than enabling it for
individual ports. In addition to enabling PM
statistics collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Specifying the signaling
profile (M8E1 only)
signaling-profile {1 | 2 | 3 | 4 | 5 | per-ts}
1 to 5 –All the voice timeslots of the port
being configured use the same signaling
profile, and the number specifies the signaling
profile to be used, in the range of 1 to 5.
per-ts – The signaling profile can be
individually selected for each voice timeslot of
the port being configured.
This parameter is relevant only when using a
framing mode that supports CAS (line-type
= g732s)
Using no signaling-profile cancels signaling
profile setting (signaling information is
transparently transferred)
For creating and configuring signaling
profiles, see Signaling Profiles.
Specifying the signaling
profile per a single
timeslot or per timeslot
range
timeslots-signaling-profile [tsx] {1 | 2 | 3 |
4 | 5}
timeslots-signaling-profile [tsx..tsy] {1 | 2 |
3 | 4 | 5}
This command is available for voice
timeslots only, if you selected per-ts under
signaling-profile
This command is not available for TS #16.
This command is possible for multiple
timeslots only if they are consecutive
Setting the time required
for a port to resume
normal operation after
loss of frame
restoration-time {1-sec | immediate |
10-sec}
Used to change the frame synchronization
algorithm, to reduce the time required for
the port to return to normal operation after
local loss of synchronization.
1-sec – After 1 second.
10-sec – Similar to the requirements of
AT&T TR-62411 (after 10 seconds).
Immediate – Immediate, complies with ITU-T
Rec. G.732.
This parameter cannot be changed when
using the Unframed mode.
Selecting the timing
reference source used by
the port for the
transmit-to-network
direction
tx-clock-source loopback
tx-clock-source domain <number>
tx-clock-source through-timing
loopback – Clock received from the E1/T1
port
domain – Clock provided by system clock
domain
through-timing – Clock received from
VC12/VT1.5 or PW (according to the
transport network)
This field is valid for VS-16E1T1-PW and
VS-6/E1T1 modules only.
Megaplex-4
E1 Ports
5-73
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Assigning VC profile to
the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.
Relevant for M16E1, Optimux modules (in
Megaplex chassis only), VS-6/E1T1,
VS-16E1T1-PW, VS-16E1T1-EoP and
ASMi-54C/N. M8E1 does not support this
feature.
Using no vc removes the profile
To configure the internal E1 port parameters:
1. Navigate to configure port e1-i <slot>/<port> to select the internal E1 port to
configure.
The config>port>e1-i>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to the port
name <string>
Using no name removes the name
Administratively enabling
the port
no shutdown
Using shutdown disables the port
Specifying E1 framing
mode
line-type { unframed | g732n | g732n-crc |
g732s | g732s-crc }
g732n-crc and g732s-crc options are not
relevant for the M8SL module.
For even e1-i ports representing the serial
ASMi-52 interface (far-end-type=highspeed-mux-serial-e1), the only possible
selection is g732n.
When the internal E1 port is bound to a VCG
port, VS-16E1T1-EoP supports g732n-crc
option only.
Specifying the code
transmitted to fill unused
timeslots in E1 frames
5-74
E1 Ports
idle-code <00 to FF (hexa)>
The available selections are [0x01 to 0xFF]
with the following values that are illegal:
0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol
{ppp | fr} [routing-protocol {none | proprip | rip2} ]
ppp – synchronous PPP over HDLC
encapsulation
fr –Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
See also Configuring Inband Management in
Chapter 8 for important considerations on
selecting the routing protocol.
Using no inband management <timeslot>
disables inband management through this
timeslot
Inband management is not available for
even e1-i ports representing the serial
ASMi-52 interface (far-end-type=highspeed-mux-serial-e1).
Transmitting an
out-of-service signal
(OOS)
out-of-service [voice <00 to FF (hexa)>] [
data <00 to FF (hexa)>] [signaling
{force-idle | force-busy | idle-busy |
busy-idle}]
The hexadecimal number is in the range of 0
to FF (two digits)
The selected out-of-service data code is
also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
For even e1-i ports representing the serial
ASMi-52/53 interface (far-end-type=highspeed-mux-serial-e1), the only possible
selection is data.
Configuring collection of
performance
management statistics
for this port, which are
presented via the
RADview Performance
Management portal
Megaplex-4
pm-collection interval <seconds>
You can enable PM statistics collection for
all E1 ports rather than enabling it for
individual ports. In addition to enabling PM
statistics collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
E1 Ports
5-75
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Selecting the handling of
timeslot 0 for M8SL,
ASMi-54C/N, SH-16/E1
and CL.2 internal E1 ports
ts0-over-dsl
Timeslot 0 is transparently transferred
through the SHDSL link and terminated by
the remote equipment). When selecting the
port bandwidth, make sure to assign an
additional timeslot for transferring timeslot
0. This is the only option when using the
G.732S mode.
This option is not available for even e1-i
ports representing the serial ASMi-52/53
interface (far-end-type=high-speed-muxserial-e1).
Using no ts0-over-dsl means local
termination of timeslot 0. This option is
relevant when the framing mode (line-type)
of the internal (virtual) port is G.732N.
In addition, when ASMi-54C/N is working vs.
ASMi-52/ASMi-53 with V.35 interface, this
parameter must be also set to ‘no’.
Enabling CRC-4 error
detection at the remote
ASMi-52/52L unit (M8SL
only)
remote-crc
Assigning VC profile to
the port
vc profile <profile name>
Used for performance monitoring, and is
available only when the ASMi-52/52L
includes an E1 user port
Using no remote-crc disables the remote
CRC-4 error detection
For creating VC profiles, see VC Profiles.
Using no vc removes the profile
Examples
Example 1
The following section illustrates how to configure the E1 port labeled 1 on the
M8E1 module installed in slot 9:
•
Set the E1 framing mode to G.732N with CRC.
•
Set the line interface to unbalanced.
•
Set the attenuation level of the receive signal to long-haul.
•
Set the idle code to 8E.
•
Administratively enable the port.
•
Leave all other parameters disabled or at their defaults.
config>port>e1(9/1)# interface-type unbalanced
config>port>e1(9/1)# line-type g732n-crc
config>port>e1(9/1)# rx-sensitivity long-haul
config>port>e1(9/1)# idle-code 0x8E
config>port>e1(9/1)# no shutdown
5-76
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Example 2
This section illustrates how to configure inband management via a dedicated
timeslot on M8E1 Module.
1. Define an M8E1 module in Slot 1 and configure inband management via E1
port 1 with the following parameters:
Dedicated timeslot - #31
Inband management protocol: synchronous PPP over HDLC encapsulation
Routing protocol: RAD proprietary RIP.
config>slot# 4 card-type e1-t1 m8e1
config>port# e1 1/1 no shutdown
config>port# e1 1/1 line-type g732n
config>port# e1 1/1 inband-management 31 protocol ppp routingprotocol prop-rip
2. Configure router interface 5.
config>router# 1 interface 5 address 17.17.17.17/24
3. Bind E1 port 1/1 to router interface 5.
config>router# 1 interface 5 bind e1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate E1 port 2 of M8E1 module in Slot 9.
2. Configure signaling profile per ts:
TS-10 to profile 2
TS-1 to 9 to profile 3
Routing protocol: RAD proprietary RIP.
config>port>e1(9/2)# no shutdown
config>port>e1(9/2)# signaling-profile per-ts
config>port>e1(9/2)# timeslots-signaling-profile 10 2
config>port>e1(9/2)# timeslots-signaling-profile [1..9] 3
config>port>e1(9/2)# commit
Result : OK
3. Displaying signaling profile per ts:
config>port>e1(9/2)# info detail
name "IO-9 e1 02"
no shutdown
line-type g732s
line-code hdb3
interface-type balanced
idle-code 0x7f
restoration-time immediate
out-of-service voice 0x00 data 0x00 signaling
signaling-profile per-ts
timeslots-signaling-profile 1 3
timeslots-signaling-profile 2 3
timeslots-signaling-profile 3 3
Megaplex-4
force-idle
E1 Ports
5-77
Chapter 5 Cards and Ports
Installation and Operation Manual
timeslots-signaling-profile
timeslots-signaling-profile
timeslots-signaling-profile
timeslots-signaling-profile
timeslots-signaling-profile
timeslots-signaling-profile
timeslots-signaling-profile
rx-sensitivity short-haul
4 3
5 3
6 3
7 3
8 3
9 3
10 2
Configuration Errors
The following table lists messages generated by Megaplex-4 when a configuration
error on E1 modules is detected.
Table 5-17. E1 Configuration Error Messages
Code
Type
Syntax
Meaning
131
Warning
RESTORATION TIME DOES NOT For E1 links, the restoration time must be in accordance
MATCH THE STD
with ITU-T recommendations
132
Error
FRAME TYPE / PROFILE
MISMATCH
One of the following:
•
The selected framing mode does not support
signaling profiles
•
When the station clock is configured to interfacetype= e1 with tx-ssm enabled, line-type must
be g732n-crc
141
Error
ROUTING PROTOCOL/
MNG TYPE MISMATCH
The rip2 protocol on an I/O module port can be enabled
only when the inband management method is configured
to ppp or fr
144
Error
ILLEGAL IDLE CODE SELECTION
Code transmitted in idle timeslots is illegal. The available
selections for E1/E1-i ports are [0x01 to 0xFF] with the
following values that are illegal: 0x00, 0x08, 0x10, 0x12,
0x21, 0x24, 0x42, 0x49, 0x84, 0x92
146
Error
NUM OF E1/T1 PORTS
EXCEEDS 120
The maximum number of framed E1 ports opened on the
M16E1, ASMi-54C/N or OP modules must not exceed 120.
434
Error
PORT LINE TYPE MISMATCH
When the CL module has no SDH/SONET ports, line-type
must not be configured as g732s or g732s-crc for the
following modules/ports:
•
SH16-E1-PW: ports DS1 1..16
•
VS-E1-PW: ports E1 9..16 or DS1 9..16
•
VS-6-E1: ports DS1 9..16.
Error 434 may also appear for other port types – refer to
the corresponding manual section.
Viewing an E1 Port Status
Follow the instructions below for viewing the status of the E1 port 5/1 as an
example.
5-78
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To view the E1 port status:
•
At the config>port>e1(<slot>/<port>/<tributary>)# prompt, enter show
status.
The status information appears as illustrated below.
Note
<tributary> relates to OP modules only:
• For OP-108C, <port>/<tributary> is 1/1 to 1/4, 3/1 to 3/4.
• For OP-34C, <port>/<tributary> is 1/1 to 1/16.
Note
The M8E1 module in PDH sync Mode displays two additional fields:
• MCB bit state: Locked to Master/Unlocked to Master
• LCB bit state: In Loopback Timing/Not In Loopback Timing.
M8E1:
config>port>e1(5/1)# show status
Name
:
Administrative Status : Down
Operation Status
: Up
Connector Type
: DB44
SH-16/E1:
config>port>e1-i(10/2)# show status
Name
: IO-10 e1-i 02
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
M8E1 in PDH sync mode:
config>port>e1(2/1)# show status
Name
: IO-2 e1 01
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
Connector Type
: DB44
MCB (SA5)
LCB (SA6)
Rx
Locked to Master
Not In Loopback Timing
Tx
Locked to Master
In Loopback Timing
Testing E1 Ports
Megaplex-4 E1 ports feature test and loopback functions at the port and timeslot
levels. The available loopbacks depend on the port type (E1, E1-i) and specific
module. The following table shows the loopbacks supported by E1 and E1-i ports
on each Megaplex-4 module. The hierarchical position of e1 and e1-i ports is
slot:port for all the modules, with the exception of Megaplex cards OP-108C and
OP-34C, where the e1 port is found at slot:port:tributary (in these modules
slot:port=mux_eth_tdm). The digits in brackets (1 to 3) denote restrictions or
other special remarks regarding implementation of this loopback in specific
modules.
Megaplex-4
E1 Ports
5-79
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 5-18. Loopbacks Supported by Megaplex-4 E1 and E1-i Ports
E1 Ports (e1)
M8E1
M16E1
Internal E1 Ports (e1-i)
OP-108C
OP-34C
Lopback Type
ASMi-54C/N
CL.2
VS-16E1T1-
VS-16E1T1-EoP
M8SL
ASMi-54C/N,
SH-16/E1
EoP
VS-16E1T1-PW
VS-6/E1T1
Local Loop
√
√
√(1)
√(1)
√
√
–
√
Remote Loop
√
√
√
√
√
√
–
√
√
√
√(2)
√(2)
√
√
√
√
√
√
√(2)
√(2)
√
√
√
√
–
–
√
√
–
–
–
√
remote
–
–
√
√
–
–
–
√
Ber Test
√
√
√
–
√
√
–
√
Loop per TS
Local
Loop per TS
Remote
Local on
remote
Remote on
1 - Loopback on local and remote devices
2 - Only for local internal e1 ports.
CL Modules
The following sections briefly describe each type of loopback on E1-i ports of CL
modules. Table 5-20 shows the paths of the signals when each loopback is
activated.
5-80
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Table 5-19. Loopbacks on E1-i ports of CL.2 Modules
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
I/O Port
..
.
..
..
.
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
E1-i port
2
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on E1-i port
2
..
..
..
E1-i/T1-i Framers
1
Local loopback on
timeslots of
E1-i port
2
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on timeslots of
E1-i port
Megaplex-4
2
..
..
.
.
E1 Ports
5-81
Chapter 5 Cards and Ports
Installation and Operation Manual
Local Loopback on E1-i Port
The local E1-i port loopback is used to test the intra-Megaplex-4 paths of the
signals intended for transmission through a selected E1-i port: these paths start
at the other Megaplex-4 port(s) connected to the tested E1-i port, pass through
the DS1 cross-connect matrix in the CL module, and continue up to the framer of
the E1-i port within the SDH/SONET link interface. Therefore, these paths include
all of the Megaplex-4 local ports connected to the tested E1-i port, and in the
particular the operation of the DS1 cross-connect matrix circuits that handle the
signals directed to the tested E1-i port within the CL module.
As shown in Table 5-20, the local E1-i port loopback is activated within the E1-i
framer of a selected CL E1-i port.
Remote Loopback on E1-i Port
As shown in Table 5-20, the E1-i port remote loopback is activated on the framer
serving the port within the SDH/SONET link interface.
Local Loopback on E1-i Port Timeslots
The local loopback on selected timeslots of an E1-i port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.
This test is recommended for testing the signal paths between the E1-i port and
an I/O port of another module that uses only a fraction of the available E1-i port
bandwidth.
As shown in Table 5-20, the loopback is activated only on the timeslots specified
by the user during the activation of the loopback. As a result, there is no
disturbance to services provided by means of the other timeslots of the same
E1-i port, only the flow of payload carried by the specified timeslots is disrupted.
The user can activate the loopback on any individual timeslot, or on several
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
cross-connected with HDLC ports.
Remote Loopback on E1-i Port Timeslots
The remote loopback on selected timeslots of an E1-i port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. The corresponding timeslots received from the local equipment
are disconnected.
This test is recommended for testing signal paths from a remote equipment unit,
through the selected timeslots of the E1-i port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
As shown in Table 5-20, the loopback is activated only on the timeslots specified
by the user during the activation of the loopback. As a result, there is no
disturbance to services provided by means of the other timeslots of the same
E1-i port: only the flow of payload carried by the specified timeslots is disrupted.
It is not allowed to activate loopbacks on timeslots assigned to HDLC ports.
5-82
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
I/O Modules
The following sections briefly describe each type of loopback on E1 and E1-i ports
of I/O modules. Table 5-21 shows the paths of the signals when each loopback is
activated.
Table 5-20. Loopbacks on E1 and E1-i Ports of I/O Modules
I/O
Local loopback on E1/E1-i port
(M8E1, M16E1, ASMi-54C/N,
OP-108C/E1, SH-16/E1, VS16E1T1-EoP, OP-108C, OP-34C
modules)
Remote loopback on E1/E1-i
timeslots (M8E1, M16E1, ASMi54C/N, SH-16/E1, VS-16E1T1EoP, OP-108C, OP-34C
modules)
Port
Interface
DS1
Cross-Connect
Matrix
Port
Interface
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on E1/E1-i
port (M8E1, M16E1, ASMi54C/N, OP-108C/E1, SH-16/E1,
VS-16E1T1-EoP, OP-108C,
OP-34C modules)
Local loopback on E1/E1-i
timeslots (M8E1, M16E1, ASMi54C/N, SH-16/E1, VS-16E1T1EoP, OP-108C, OP-34C
modules)
CL
I/O Interface
1
2
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
1
2
..
..
.
DS1
Cross-Connect
Matrix
Local Loopback on E1 Port of I/O Module
The local port loopback is used to test the path of the signals intended for
transmission through a selected E1 port: this path starts at the other Megaplex-4
port(s) connected to the selected port, passes through the cross-connect matrix
in the CL module, and continues up to the port line interface. Within the tested
module, the path includes most of the line interface circuits serving the selected
port, and the operation of the routing circuits that handle the port signals within
the module.
As shown in Table 5-21, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
Megaplex-4
E1 Ports
5-83
Chapter 5 Cards and Ports
Installation and Operation Manual
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed “all-ones” signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on E1 Port of I/O Module
The remote port loopback is used to test the line interface circuits of a selected
E1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in Table 5-21, when a remote loopback is activated on an E1 port, that
port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
The remote loopback should be activated only after checking that the remote unit
operates normally with the local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
If the local Megaplex-4 unit also operated normally when the local port loopback
was activated, then while the remote loopback is connected the local unit should
receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of E1 I/O Module Port
The local loopback on selected timeslots of an E1 port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the E1 port.
As shown in Table 5-21, the loopback is activated within the I/O module routing
matrix, and only on the timeslots specified by the user during the activation of
the loopback. As a result, there is no disturbance to services provided by means
of the other timeslots of the same port: only the flow of payload carried by the
specified timeslots is disrupted.
You can activate the loopback on any individual timeslot, or on several arbitrarily
selected timeslots. You cannot activate loopbacks on timeslots assigned to HDLC
ports.
This convenience feature is also available for loopback deactivation. The
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
5-84
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Remote Loopback on Timeslots of E1 I/O Module Port
The remote loopback on selected timeslots of an E1 port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. This loopback is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the E1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
As shown in Table 5-21, the loopback is activated within the I/O module routing
matrix, and only on the timeslots specified by the user during the activation of
the loopback. As a result, there is no disturbance to services provided by means
of the other timeslots of the same port. Only the flow of payload carried by the
specified timeslots is disrupted.
You cannot activate loopbacks on timeslots assigned to HDLC ports.
The other features related to loopback activation/deactivation described above
for the local loopback on timeslots are also applicable to the remote loopback.
E1 Port Loopbacks on Remote Optimux Devices
Megaplex-4 features local and remote E1 loopbacks on the remote Optimux
devices connected to optical links of its OP-108C and OP-34C modules.
A typical signal flow for a local loopback on an E1 port of a remote Optimux is
shown in Figure 5-3. The remote Optimux device can be one of the following:
•
Optimux-108/108L connected to OP-108C module (Section A or B)
•
Optimux-34 connected to OP-34C module.
•
The number of E1 ports is 4 for Optimux-108/108L and 16 for Optimux-34.
Remote Optimux
Megaplex-4100
"1"
CL
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
E1 Payload
Mux/Demux
..
.
LIU 4
E1
Port 1
..
.
.
.
E1
Port
4(16)
Figure 5-3. Typical Signal Flow for E1 Port Local Loopback on Remote Optimux Device
When a local loopback on an E1 port of the connected Optimux is activated by an
OP module command, the E1 port transmit signal is returned to the input of the
port receive path (the E1 port signal is disconnected from the transmit path and
is replaced by an AIS signal).
While the loopback is activated, the tested Optimux port will receive its own
signal, and therefore must operate normally. In addition, the user equipment
connected to the tested E1 port must also receive its own signal and thus it must
be synchronized.
This test checks the operation of the far end Optimux E1 port interface, and the
connections to the E1 equipment attached to the far end E1 port.
Megaplex-4
E1 Ports
5-85
Chapter 5 Cards and Ports
Installation and Operation Manual
A typical signal flow for a remote loopback on an E1 port of a remote Optimux is
shown in Figure 5-4.
Local OP-34C or
OP-108C Section
Megaplex-4100
Remote Optimux
"1"
CL
E1
Port 1
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
..
.
..
..
.
E1 Payload
Mux/Demux
E1
Port 4
(16)
LIU 4
(16)
Figure 5-4. Typical Signal Flow for E1 Port Remote Loopback on Remote Optimux
When a remote loopback on an E1 port of the connected Optimux is activated by
an OP module command, the received E1 signal is returned to the input of the
port transmit path after being processed by the internal E1 port, and is
transmitted back to the OP module (the E1 port signal is disconnected from the
receive path and is replaced by an AIS signal).
Therefore, the corresponding internal E1 port of the OP module receives its own
signal, and it must operate normally. In addition, the OP module user equipment
connected via the tested E1 port must also receive its own signal and thus it
must be synchronized.
This test checks the connections between the user’s E1 equipment connected via
the tested internal E1 port of the local OP module, the operation of the OP
module link (section) and of the remote Optimux, and the network connections
between the local OP module and the remote Optimux.
Note
The same loopback can be activated/deactivated by a supervision terminal
connected to the far end Optimux.
Local and Remote Loopbacks on Remote ASMi Modems from E1-i
Ports of ASMi-54C/N and SH-16/E1 Modules
E1-i ports of ASMi-54C/N module feature additional local and remote loopbacks
on remote ASMi modems. Availability of loopbacks and their activation command
depend on the remote modem flavor (far-end-type). The following table lists the
loopbacks available on e1-i ports of ASMi-54C/N module for each far end type.
Table 5-21. Local and Remote Loopbacks on Remote ASMi Modems from E1-i Ports of ASMi-54C/N
and SH-16/E1 Modules
Far-end-type
Loopback
Far-end Device Ports
Tested
Figure
asmi52* (ASMi-52 or
ASMi-52L standalone)
remote-on-remote
E1
Figure 5-5
5-86
E1 Ports
local-on-remote
Figure 5-6
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Far-end-type
Loopback
Far-end Device Ports
Tested
Figure
asmi52-e1-eth* (ASMi52 standalone with E1
and LAN ports (Mux
type))
remote-on-remote
E1
Figure 5-5
asmi52-e1-dte* (ASMi-52
standalone with E1 and
serial ports (Mux type))
remote-on-remote serial
Serial
Figure 5-5
local-on-remote serial
Serial
Figure 5-6
remote-on-remote e1
E1
Figure 5-5
local-on-remote e1
E1
Figure 5-6
high-speed-mux-serial-e1
(ASMi-52/53 standalone
with E1 and serial ports
(Mux type), 4M/4W
functionality)
remote-on-remote
Odd e1-i ports of the I/O
module = loopback on E1
ports of remote modem
Figure 5-5
asmi54 (ASMi-54 or
ASMi-54L standalone)
remote-on-remote
E1 ports
Figure 5-5
local-on-remote
E1 ports
Figure 5-6
managed (ASMi-54L
standalone configurable
via EOC or ASMi-53)
remote-on-remote
E1 ports
Figure 5-5
local-on-remote
E1 ports
Figure 5-6
Figure 5-6
local-on-remote
local-on-remote
Figure 5-6
Even e1-i ports =
loopback on Serial ports
of remote modem
*ASMi-54C/N only
Note
Only one loopback at a time can be activated from Megaplex-4. At any moment
the last loopback command is valid and overrides the previous loopback
command.
Figure 5-5 shows the signal paths of a typical remote loopback on the remote
ASMi modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
The loopback is activated within the user interface of the remote modem, which
returns the received data through the transmit path.
Megaplex-4
E1 Ports
5-87
Chapter 5 Cards and Ports
Installation and Operation Manual
Megaplex-4100/4104
CL
Remote
Loopback
ASMi-54C/N
ASMi-52/54
E1 or DTE
Routing
Matrix
Port e1-i 1
..
..
.
..
E1 or Serial
..
Port*
.. *When far-end-type=high-speed.. mux-serial-e1, loops on ASMi E1
ports are activated from odd e1-i
Port e1-i 8
ports and loops on ASMi serial
ports - from even e1-i ports
Bus
Interface
Other Port
Interface
Figure 5-5. Remote Loopback on Remote Unit, Signal Paths
Local Loopback on Remote Unit
Figure 5-6 shows the signal paths of a typical local loopback on the remote ASMi
modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a local loopback request
to the remote modem connected to that channel. The command is sent through
the inband eoc channel configured on the remote modem.
The loopback is activated within the user interface of the remote modem, which
returns the received data through the transmit path.
Megaplex-4100/4104
CL
Local
Loopback
ASMi-54C/N
ASMi-52/54
E1 or DTE
Routing
Matrix
Port e1-i 1
Bus
Interface
Other Port
Interface
.
..
..
.
E1 or Serial
..
Port*
..
*When far-end-type=high-speed.. mux-serial-e1, loops on ASMi E1
. ports are activated from odd e1-i
Port e1-i 8
ports and loops on ASMi serial
ports - from even e1-i ports
Figure 5-6. Local Loopback on Remote Unit, Signal Paths
BER Test
The BER test, activated by the command bert, is used to evaluate data
transmission through selected timeslots of the link connected to a selected E1 or
E1-i port without using external test equipment.
Data transmission is checked by applying a test sequence generated by an
internal test sequence generator towards the remote equipment. The timeslots in
which the sequence is transmitted, are defined by means of the bert command.
The test sequence is 2E-15.
To check that the line is alive or verify the BER detection calibration, the user can
also inject single errors into the transmitted pattern.
5-88
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
The BER Test on unframed ports is performed per port, while on framed ports it
is performed also per individual timeslot.
The timeslot on which BERT is performed must be cross-connected.
The transmitted data is returned by means of a loop, somewhere along the data
path, to the test sequence evaluator. The evaluator compares the received data,
bit by bit, to the original data and detects any difference (bit error). The output
of the evaluator is sampled during module polling, to check whether errors were
detected in the interval between consecutive pollings.
The number of errors is accumulated from the activation of the BER test.
The test results are displayed on a supervision terminal as a number in the range
of 0 (no errors detected during the current measurement interval) through
63535. The meaning of the displayed parameters is given in the table below.
The BER test duration is infinite (to stop the test manually, use no bert
command).
Table 5-22. Bert Performance Parameters
Parameter
Description
Status
Displays the BERT status: Not Active, In Sync or Out of Sync
Run Time (Sec)
Displays the total time the test is running in seconds
Sync Loss (Sec)
Displays the number of times Sync Loss was detected since BERT
started to run
Bert Error Count
Displays the total number of bit errors detected
Pattern
Displays the BERT pattern (always 2e-15)
ES (Sec)
Displays the total number of seconds in which errors have been
detected
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks and BER Tests
To perform a loopback or BER test on the E1 port:
1. Navigate to configure port e1 <slot>/<port>/<tributary> to select the E1 port
to be tested.
The config>port>e1>(<slot>/<port>/<tributary>)# prompt is displayed.
Megaplex-4
E1 Ports
5-89
Chapter 5 Cards and Ports
Installation and Operation Manual
<tributary> relates to OP modules only:
Note
• For OP-108C, <port>/<tributary> is 1/1 to 1/4, 3/1 to 3/4.
• For OP-34C, <port>/<tributary> is 1/1 to 1/16.
2. Enter all necessary commands according to the tasks listed below.
To perform a loopback or BER test on the internal E1 port:
1. Navigate to configure port e1-i <slot>/<port> to select the internal E1 port to
be tested.
The config>port>e1-i>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring
the direction of the loopback
(all modules)
loopback {local | remote} [time-slot
<1..31>] [duration <duration in
minutes 1..30> ]
local – local loopback (per port and per
timeslot)
remote – remote loopback (per port and
per timeslot)
For additional loopbacks on e1-i ports of
ASMi-54C/N modules, see two table rows
below.
Activating and configuring
the direction of the loopback
(additional loopbacks on e1-i
ports of SH-16/E1 and
ASMi-54C/N modules, any
far-end-type except
asmi52-e1-dte)
loopback { remote-on-remote |
local-on-remote } [duration
<duration in minutes 1..30> ]
remote-on-remote – remote loopback on
remote ASMi modem
Activating and configuring
the direction of the loopback
(additional loopbacks on e1-i
ports of ASMi-54C/N, farend-type = asmi52-e1-dte,
and SH-16/E1 modules, farend-type = non-manage )
loopback { remote-on-remote serial
<port-number> | local-on-remote
serial <port-number> | remote-onremote e1 <port-number> | localon-remote e1 <port-number> }
[duration <duration in minutes
1..30> ]
remote-on-remote serial – remote
loopback on serial port of remote
ASMi-52/53 (E1+DTE) modem
local-on-remote – local loopback on
remote ASMi modem
local-on-remote serial – local loopback on
serial port of remote ASMi-52/53 (E1+DTE)
modem
remote-on-remote e1 – remote loopback
on E1 port of remote ASMi-52/53
(E1+DTE) modem
local-on-remote e1 – local loopback on E1
port of remote ASMi-52/53 (E1+DTE)
modem
Stopping the loopback
no loopback
Activating the BER test and
configuring its parameters
bert [ts <ts number 1..31>] [injecterror single]
The [ts <ts number in the range from 1 to
31>] command is used only for framed
ports and is mandatory for these ports.
The timeslot on which BERT is performed
must be cross-connected.
CL flip stops the BERT session.
5-90
E1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Stopping the BER test
no bert
Displaying the BER test
results
show bert
Clearing the BER test
counters
clear-bert-counters
Comments
A typical display:
Status
: Not Active
Bit Error Count: 1
Pattern
: 2e-15
Run Time (Sec) : 1
ES (Sec)
: 1
Sync Loss (Sec): 1
To perform a loopback on the E1 port of the remote Optimux:
1. Navigate to configure port mux-eth-tdm <slot>/<port> to select the optical
link connected to the device being tested.
Note
The number of <port> is:
• 1 or 3 for OP-108C
• 1 for OP-34C
Remote devices connected to protection ports 2 and 4 cannot be configured.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
2. Type remote.
3. Type configure port e1 <port> to select the E1 port of the remote device to
be tested.
Note
The number of <port> is:
• 1 to 4 for Optimux-108/108L
• 1 to 16 for Optimux-34.
4. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}
[duration <duration in minutes
1..30> ]
local – local loopback:
Stopping the loopback
no loopback
remote – remote loopback
Displaying E1 Port Statistics
E1 and E1-i ports of Megaplex-4 feature the collection of statistical diagnostics
per relevant parts of ITU-T G.826, thereby allowing the carrier to monitor the
transmission performance of the links.
Megaplex-4
E1 Ports
5-91
Chapter 5 Cards and Ports
Installation and Operation Manual
To display the E1 port statistics:
•
Note
At the prompt config>slot>port>e1(<slot><port>[<tributary>])#, enter show
statistics followed by the parameters listed below.
<tributary> relates to OP modules only:
• For OP-108C, <port>/<tributary> is 1/1 to 1/4, 3/1 to 3/4.
• For OP-34C, <port>/<tributary> is 1/1 to 1/16.
To display the E1-i port statistics:
•
At the prompt config>slot>port>e1-i(<slot><port>)#, enter show statistics
followed by the parameters listed below.
Task
Command
Comments
Displaying statistics
show statistics {total | all | current}
•
total –total statistics of last
96 intervals
•
current –current statistics
•
all –all statistics: first current
statistics, then statistics for all
valid intervals, and finally total
statistics
Displaying statistics
for a specific
interval
show statistics interval <interval-num 1..96>
E1 port statistics are displayed.
Note
BES, LOFC and Rx Frames Slip are displayed for framed formats only.
For example:
Current statistics:
config>port>e1(1/2)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 191
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Statistics for interval 67:
config>port>e1(3/1)# show statistics interval 67
Interval Number : 67
Interval
--------------------------------------------------------------ES
: 16
SES
: 1
UAS
: 589
5-92
E1 Ports
Megaplex-4
Installation and Operation Manual
BES
Rx Frames Slip : 0
LOFC
: 0
Chapter 5 Cards and Ports
: 0
Total statistics:
config>port>e1(1/2)# show statistics total
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
All statistics:
config>port>e1(1/2)# show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 171
Valid Intervals
: 2
config>port>e1(1/2)#
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 1
Interval
--------------------------------------------------------------ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 2
Interval
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
The counters are described in Table 5-24, Table 5-25 and Table 5-26.
Megaplex-4
E1 Ports
5-93
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 5-23. E1 Port Statistics Parameters – Current 15-Minute Interval
Parameter
Description
ES
Displays the number of errored seconds in the current 15-minute interval.
An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
UAS
Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
SES
•
Any second following 10 consecutive SES seconds
•
A second for which any of the previous 10 consecutive seconds was also a UAS
and any of the previous 10 consecutive seconds was a SES.
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES
Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
LOFC
Displays the number of LOFC in the current interval.
The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip
Displays the number of Rx Frames Slips in the current 15-minute interval.
A CSS is a second with one or more controlled slip events.
Time elapsed
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96).
Table 5-24. E1 Port Statistics Parameters – Selected 15-Minute Interval
Parameter
Description
ES
Displays the total number of errored seconds (ES) in the selected interval
UAS
Displays the total number of unavailable seconds (UAS) in the selected interval
SES
Displays the total number of severely errored seconds (SES) in the selected interval
BES
Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC
Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number
The number of interval for which statistics is displayed.
Note: The sequence of intervals is different for the E1 ports of different module
families:
5-94
E1 Ports
•
For the M8E1 modules, Interval #1 is the latest in time
•
For the M16E1, ASMi-54C/N, SH-16/E1, OP-108C and OP-34C modules, Interval #1
is the earliest in time.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Table 5-25. E1 Port Statistics Parameters – Total Statistics
Parameter
Description
ES
Displays the total number of errored seconds (ES) since statistics are available
UAS
Displays the total number of unavailable seconds (UAS) since statistics are available
SES
Displays the total number of severely errored seconds since statistics are available
BES
Displays the total number of bursty errored seconds (BES) since statistics are available
LOFC
Displays the total number of loss of frame alignment events since statistics are available
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events since statistics are
available
To clear the statistics for an E1 port:
•
At the prompt config>port>e1<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
To clear the statistics for an E1-i port:
•
At the prompt config>port>e1-i<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.11 E1-i, T1-i Ports
See E1 Ports and T1 Ports sections, respectively.
5.12 G.703 Ports
Applicable Modules
G.703 ports denote G.703 codirectional links of VS-6/703 modules.
Standards Compliance
ITU-T Rec. G.703, Section 1.1.4.1
Functional Description
The 64 kbps codirectional interface is defined by ITU-T Rec. G.703, Section
1.1.4.1 and has the following functions:
Megaplex-4
•
Bidirectional transfer of data signals
•
Transfer of 64 kHz bit clock signals associated with the data signals
•
Transfer of 8 kHz byte clock signals associated with the data signals.
G.703 Ports
5-95
Chapter 5 Cards and Ports
Installation and Operation Manual
ITU-T Rec. G.703, Section 1 describes three different versions for 64 kbps
interfaces, which differ mainly in the type and direction of the clock signals, and
the number of wires used.
The term codirectional describes an interface that transmits the information and
the associated timing signals in the same direction. The interface uses four wires
(two twisted pairs), one pair for the transmit direction and the other pair for the
receive direction). Each pair carries both the data and the associated clock
signals.
Figure 5-7 illustrates the flow of signals across the interface.
Transmit Data and
Associated Timing
TRANSMITTER
RECEIVER
RECEIVER
TRANSMITTER
Receive Data and
Associated Timing
Figure 5-7. G.703 Codirectional Interface
The 64 kbps co-directional interface transfers data at a nominal rate of 64 kbps,
and a maximum rate tolerance of 100 ppm. The interface uses two balanced
twisted pairs having a nominal impedance of 120Ω. The transmit pulse shape,
measured across a 120Ω resistive load impedance, is nominally rectangular. A
mark is represented by a peak voltage of 1.0V, and a space is represented by a
voltage of 0 ±0.10V. The nominal pulse width is 3.9 μsec. The maximum line
attenuation that should be compensated for by the receiver is 3 dB at up to
128_kHz.
The interface supports the delineation of byte intervals. The signal waveform
uses coding to carry both clock and timing information, and to obtain a signal
with essentially zero DC component. The coding is performed in the following
steps, illustrated in the figure below:
5-96
•
Step 1: The basic 64 kbps bit period is divided into four unit intervals.
•
Step 2: A binary “one” is encoded as a block of the following four symbols:
1100. A binary “zero” is encoded as a block of the following four symbols:
1010.
•
Step 3: The binary signal is converted into a three-level signal by alternating
the polarity of consecutive blocks (to ensure DC balance).
•
Step 4: To mark the start and end of a byte, the alternation in polarity of the
blocks is violated every eighth block. The violation block marks the last bit in a
byte.
G.703 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
One Byte
Byte Timing
Bit Number
7
8
1
2
3
4
5
6
7
8
1
64 kbps Data
1
0
0
1
0
0
1
1
1
0
1
Step 1 + 2
Binary Data
Step 3
Three-Level
Encoded Data
Step 4
Three-Level
Signal
with Polarity
Violations
Violation
Violation
Figure 5-8. G.703 Codirectional Signal Coding
Factory Defaults
Megaplex-4 is supplied with all ds0-g703 ports disabled.
Configuring DS0-G703 Port Parameters
To configure the DS0-G703 link parameters:
1. Navigate to configure port ds0-g703 <slot>/<port> to select the port to
configure.
The config>port> ds0-g703>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Megaplex-4
G.703 Ports
5-97
Chapter 5 Cards and Ports
Installation and Operation Manual
Viewing a DS0-G703 Port Status
Follow the instructions below for viewing the status of the DS0-G703 port 10/1
as an example.
To view the DS0-G703 port status:
•
At the config>port> ds0-g703 (<slot>/<port>)# prompt, enter show status.
The status information appears as illustrated below.
config>port>ds0-g703(10/1)# show status
Name
: VS-6/703 Link 1
Administrative Status : Down
Operation Status
: Down
Loopback Type
: None
Testing DS0-G703 Links
The test and diagnostics functions available on each optical link are:
•
Local loopback on local link
•
Remote loopback on local link
•
BER test on the link
Local Digital Loopback (Local Loop)
The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
While the loopback is connected, the local serial port should receive its own
signal.
The loopback signal path is shown below.
Figure 5-9. Local Loopback, Signal Path
Remote Digital Loopback (Remote Loop)
The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
5-98
G.703 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote serial port should receive its own
signal.
The loopback signal path is shown below.
Figure 5-10. Remote Loopback, Signal Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the VS-6/G703 module. Therefore, when you initiate a loopback, you have the
option to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local module before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks and BER Tests
To perform a loopback or BER Test on the G703 link:
3. Navigate to configure port ds0-g703 <slot>/<port> to select the optical link
to be tested.
The config>port> ds0-g703>(<slot>/<port>)# prompt is displayed.
4. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}
[duration <duration in minutes
1..30> ]
local – local loopback
Stopping the loopback
no loopback
Activating the BER test and
configuring its parameters
bert
Megaplex-4
remote – remote loopback
G.703 Ports
5-99
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Stopping the BER test
no bert
Displaying the BER test results
show bert
Comments
A typical display:
Status
: Not Active
Bit Error Count: 1
Pattern
: 2e-15
Run Time (Sec) : 1
ES (Sec)
: 1
Sync Loss (Sec): 1
5.13 GFP Ports
Applicable Modules
GFP ports represent VCGs (Virtual Concatenation Groups) with GFP encapsulation
and can be configured for the following ports:
•
SDH/SONET (CL.2 modules)
•
E1/T1 (VS-16E1T1-EoP modules)
•
T3 (T3 modules).
They can be mapped either directly to the physical layer or to VCG. In the latter
case, the binding is done in two stages and the VCG is further bound to the
physical layer.
Standards Compliance
GFP Ports comply with ITU-T Rec. G.7041, using the framed mode.
Factory Defaults
Megaplex-4 is supplied with all GFP ports disabled.
Configuring GFP Ports
To configure a GFP port:
1. Navigate to configure port gfp <slot>/<port> to select the gfp port to
configure.
The config>port>gfp>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
`
Assigning short description to
port
name <string>
Using no name removes the name
5-100
GFP Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
`
Administratively enabling port
no shutdown
Using shutdown disables the port
Binding the corresponding
VC/VT/STS-1/VCG to the GFP port
(CL modules)
bind vc4-sts3c
<slot>/<port>/<tributary>
bind vc3-sts1
<slot>/<port>/<au4>/
<tributary>
bind vc-vt <slot>/<port>/
<au4>/<tug_3>/<tug_2>
[/<tributary>]
For the allowed ranges, seeTable 5-31.
bind vcg <slot>/<port>
The connection to a VC or VT/STS
depends on the frame selection
(frame=sdh or frame=sonet)
You cannot bind both a VCG and a
VC/VT/STS-1 to a GFP port
Using no before the corresponding
command removes the binding
Binding the corresponding
T3/VCG to the GFP port (T3
modules)
bind t3 <slot>/<1>
bind vcg <slot>/<port>
The allowed ranges of VCG ports is 1 to
16 per slot.
Binding the corresponding VCG
to the GFP port (VS-16E1T1-EoP
modules)
bind vcg <slot>/<port>
Enabling payload error detection:
in this case, a frame checksum is
calculated, using the 32-bit
polynomial recommended by
ITU-T, and added to the GFP
frame structure
fcs-payload
Using no fcs-payload disables payload
error detection
Enabling the use of payload data
scrambling in the transmit and
receive directions, before
insertion in frames
scrambler-payload { rx | tx |
rx-tx }
Using no scrambler-payload disables
payload scrambling for both the transmit
and receive directions
Assigning user-defined VC profile
to the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.
Using no before the corresponding
command removes the binding
The allowed ranges of VCG ports is 1 to
16 per slot.
Using no before the corresponding
command removes the binding
Using no vc removes the profile
Before you assign the user-defined
profile, you must use the no vc command
to remove the automatical lvc-eos or
hvc-gfp profile assignement
Displaying GFP Statistics
GFP ports feature the collection of statistical diagnostics.
To display the GFP port statistics:
•
Megaplex-4
At the prompt config>slot>port>gfp (<slot><port>)#, enter show statistics
followed by parameters listed below.
GFP Ports
5-101
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Displaying statistics
show statistics {all | current}
•
current –Displays the current
statistics
•
all –Displays all statistics: first
current interval statistics, then
statistics for all valid intervals
Displaying statistics
for a specific interval
show statistics interval <interval-num 1..96>
GFP statistics are displayed. The counters are described in Table 5-27.
For example:
Current Statistics:
config>port>gfp(cl-b/6)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 299
Valid Intervals
: 96
Total RX Frames
: 475682
Total RX Frames
: 475681
Idle Frames Error : 237726
cHEC Errors
: 0
tHEC Errros
: 0
eHEC Errors
: 0
FCS Errors
: 0
PTI Mismatch
: 0
EXI Mismatch
: 0
Statistics for interval 67:
config>port>gfp(cl-a/1)# show statistics interval 67
Interval
--------------------------------------------------------------Interval Number
: 67
Total RX Frames
: 1192393
Total RX Frames
: 1192403
Idle Frames Error : 0
cHEC Errors
: 0
tHEC Errros
: 0
eHEC Errors
: 0
FCS Errors
: 0
PTI Mismatch
: 0
EXI Mismatch
: 0
Table 5-26. GFP Statistics Parameters
Parameter
Description
Time elapsed (Current
statistics only)
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds
5-102
GFP Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Description
Valid Intervals (Current
statistics only)
The number of elapsed finished 15-min intervals for which statistics data can
be displayed, in addition to the current (not finished) interval (up to 96)
Interval number (Selected
interval statistics only)
Number of interval for which statistics is displayed
Total Rx Frames
Total number of frames received
Total Tx Frames
Total number of frames transmitted
Idle Frames Error
Number of idle frames errors.
Idle frame is a special four-octet GFP control frame consisting of only a GFP
Core Header with the PLI and cHEC fields (see 6.1.1 in G.7041) set to 0, and
no Payload Area. The Idle frame is intended for use as a filler frame for the
GFP transmitter to facilitate the adaptation of the GFP octet stream to any
given transport medium where the transport medium channel has a higher
capacity than required by the client signal
cHEC Errors
Number of cHEC errors.
GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Core Header Error Check (cHEC).
tHEC Errors
Number of tHEC errors.
GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Type Header Error Check (tHEC).
FCS Errors
The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
PTI Mismatch
Number of payload Headers with incorrect PTI values
EXI Mismatch
Number of payload Headers with incorrect EXI values
There are two options for clearing GFP statistics data:
•
Clearing current interval statistics
•
Clearing all statistics.
To clear the current interval statistics:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
To clear all statistics data:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-all.
The statistics are cleared.
Megaplex-4
GFP Ports
5-103
Chapter 5 Cards and Ports
Installation and Operation Manual
5.14 HDLC Ports (CL.2 Modules)
Applicable Modules
HDLC ports defined on CL.2 modules represent VCGs (Virtual Concatenation
Groups) with LAPS encapsulation. They can be mapped either directly to the
physical layer or to a VCG. In the latter case, the binding is done in two stages
and the VCG is further bound to the physical layer. The maximum total number of
GFP and HDLC ports that can be configured per slot is 32.
For HDLC ports defined on M8E1, M8T1 and M8SL modules, see HDLC Ports (I/O
Modules).
Standards Compliance
HDLC ports in CL.2 modules comply with ITU-T Rec. X.86.
Factory Defaults
Megaplex-4 is supplied with all HDLC ports disabled.
Configuring HDLC Ports
To configure an HDLC port:
1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to the port
name <string>
Using no before name removes the name
Administratively enabling
the port
no shutdown
Using shutdown disables the port
Binding the
corresponding
VC/VT/STS-1/VCG to the
HDLC port
bind vc4-sts3c <slot>/<port>/<tributary>
bind vc3-sts1 <slot>/<port>/<au4>/
<tributary>
bind vc-vt <slot>/<port>/
<au4>/<tug_3>/<tug_2>/
[<tributary>]
For the allowed ranges, seeTable 5-31.
bind vcg <slot>/<port>
5-104
HDLC Ports (CL.2 Modules)
The connection to a VC or VT/STS depends
on the frame selection (frame=sdh or
frame=sonet)
You cannot bind both a VCG and a
VC/VT/STS-1 to a GFP port
Using no before the corresponding
command removes the binding
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Assigning user-defined VC
profile to the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.
Using no vc removes the profile
Before you assign the user-defined profile,
you must use the no vc command to
remove the automatical hvc-laps or lvc-eos
profile assignement
Displaying HDLC Statistics
HDLC ports of CL.2 modules feature the collection of statistical diagnostics.
To display the HDLC port statistics:
•
At the prompt config>slot>port>hdlc (<slot><port>)#, enter show statistics
followed by parameters listed below.
Task
Command
Comments
Displaying statistics
show statistics {all | current}
•
current –Displays the current
statistics
•
all –Displays all statistics: first
current interval statistics, then
statistics for all valid intervals
Displaying statistics
for a specific interval
show statistics interval <interval-num 1..96>
HDLC statistics are displayed. The counters are described in Table 5-28.
For example:
Current Statistics:
config>port>hdlc(cl-b/6)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec)
: 430
Valid Intervals
: 96
Total RX Frames
: 569704
Total TX Frames
: 569703
Address Mismatch
: 0
Control Mismatch
: 0
LAPS Sapi Mismatch
: 0
FCS Errors
: 0
Abort Frames
: 0
Minimum Length Violation : 0
Maximum Length Violation : 0
Statistics for interval 67:
config>port>sdh-sonet(cl-a/1)# show statistics interval 67
Interval
--------------------------------------------------------------Interval Number
: 67
Megaplex-4
HDLC Ports (CL.2 Modules)
5-105
Chapter 5 Cards and Ports
Installation and Operation Manual
Total RX Frames
: 1192393
Total RX Frames
: 1192403
Address Mismatch
: 0
Control Mismatch
: 0
LAPS Sapi Mismatch
: 0
FCS Errors
: 0
Abort Frames
: 0
Minimum Length Violation : 0
Maximum Length Violation : 0
Table 5-27. HDLC Statistics Parameters
Parameter
Description
Time elapsed (Current
statistics only)
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds
Valid Intervals (Current
statistics only)
The number of elapsed finished 15-min intervals for which statistics data can
be displayed, in addition to the current (not finished) interval (up to 96)
Interval number (Selected
interval statistics only)
Number of interval for which statistics is displayed
Total Rx Frames
Total number of frames received
Total Tx Frames
Total number of frames transmitted
Address Mismatch
The number of frames with wrong address value (the correct value of
Address byte in LAPS Overhead is 0x4)
Control Mismatch
The number of frames with wrong control value (the correct value of Control
byte in LAPS Overhead is 0x3)
LAPS Sapi Mismatch
The number of frames with wrong SAPI value (the correct value of SAPI byte
in LAPS Overhead is 0xF0E1)
FCS Errors
The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
Abort Frames
The number of abort frames received (a packet can be aborted by inserting
the abort sequence, 0x7d7e. Reception of this code at the far end will cause
the receiver to discard this frame)
Minimum Length Violation
Total number of undersized frames received/transmitted
Maximum Length Violation
Total number of oversized frames received/transmitted
There are two options for clearing HDLC statistics data:
•
Clearing current interval statistics
•
Clearing all statistics, except for the current interval.
To clear the current interval statistics:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
5-106
HDLC Ports (CL.2 Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To clear all statistics data except for from the current interval:
3. Navigate to the corresponding entity as described above.
4. Enter clear-statistics current-all.
The statistics for the specified entity are cleared.
5.15 HDLC Ports (I/O Modules)
Applicable Modules
This section describes HDLC ports defined on M8E1, M8T1 and M8SL modules.
These ports can be bound to the physical layer representing E1/T1 ports or
specific timeslots. For HDLC ports defined on CL.2 modules, see HDLC Ports (CL.2
Modules).
Standards Compliance
HDLC ports in E1/T1 I/O modules comply with IETF RFC 1990.
Factory Defaults
Megaplex-4 is supplied with all HDLC ports disabled.
Configuring HDLC Ports
To configure an HDLC port:
1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to the
port
name <string>
Using no name removes the name
Administratively
enabling the port
no shutdown
Using shutdown disables the port
Megaplex-4
HDLC Ports (I/O Modules)
5-107
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Binding the
corresponding
E1/T1 port to the
HDLC port
bind e1
<slot>/<port>/[<tributary>]
For the allowed ranges, seeTable 5-31.
bind t1
<slot>/<port>/[<tributary>]
bind e1-i <slot>/<port>
bind t1-i <slot>/<port>
When binding e1 ports, optional <tributary> index
relates to Megaplex Optimux cards (OP-34C, OP-108C)
only and denotes their internal E1 ports.
Binding the HDLC port to specific timeslots of E1/T1
physical port is done via the xc command.
Using no before the corresponding command removes
the binding
HDLC ports of the M8E1, M8T1 and M8SL modules
cannot be bound to E1-i/T1-i ports of CL-B.
Selecting
encapsulation
method of the
HDLC port
encapsulation {raw-hdlc |
c-hdlc}
raw-hdlc – HDLC encapsulation protocol
Assigning VC
profile to the port
vc profile <profile name>
Using no vc removes the profile
Note
c-hdlc – CISCO HDLC encapsulation protocol
It is possible to open only 8 E1/E1-i/T1 links per M8E1/M8SL/M8T1 module and
assign up to 4 HDLC ports to each of them so that the total capacity is 32 HDLC
ports per module. Moreover, every E1/E1-i/T1 used reduces the number of
external E1/T1 links that can be connected to E1/T1 equipment.
Configuration Errors
Table 5-29 lists messages generated by Megaplex-4 when a configuration error
on HDLC/PPP/MLPP ports is detected.
Table 5-28. HDLC/PPP/MLPPP Port Configuration Error Messages
Code
Type
Syntax
Meaning
420
Error
MLPPP PORT CAN'T BE BOUND E1 port bound to MLPPP port cannot be a member of
TO TDM GROUP
protection group
422
Error
MLPPP PORT SHOULD BE
BOUND TO UNFRAMED E1
MLPPP port cannot be bound to a framed port
423
Error
HDLC/PPP PORT OR
ASSOCIATED E1/T1 PORT
DOWN
Whenever the HDLC/PPP port is connected, the associated
ports should be at ‘no shutdown’, and vice-versa.
424
Error
HDLC/PPP ILLEGAL SLOT
ASSOCIATION
The I/O slot specified for an HDLC port and the slot of its
associated E1/E1-i/T1/T1-i port cannot be another I/O
slot. It must be either the same I/O slot or CL-A/CL-B.
The I/O slot specified for a PPP port and the slot of its
associated E1 port must be the same I/O slot.
426
5-108
Error
MORE THAN ONE MLPPP PORT Only one MLPPP port can be active on any given I/O
PER SLOT
module
HDLC Ports (I/O Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
427
Error
ONLY ONE E1/T1 PORT CAN BE Only one E1/T1 port can be bound to a single HDLC port
BOUND TO HDLC PORT
429
Error
EVEN TS NUM MUST BE
DEFINED PER HDLC PORT
HDLC rate must be a multiple of 128 kbps (even number
of timeslots).
430
Error
LINKS ASSIGNED FOR MLPPP
PORT EXCEEDED
The maximum number of E1 ports that can be bound to
MLPPP port is 8.
431
Error
ILLEGAL NUMBER OF
TIMESLOTS
Illegal number of timeslots has been selected
432
Error
ILLEGAL HDLC SLOT
ASSIGNMENT
All 4 HDLC ports bound to a specific E1-i/T1-i port must be
assigned (for processing) to the same I/O module.
433
Error
MAX 4 HDLC PORTS MAY BE
DEFINED PER LINK
The maximum number of HDLC ports defined per
E1/E1-i/T1/T1-i port is 4
434
Error
PORT LINE TYPE MISMATCH
TDM cross connect can be done only for unframed E1/T1
ports
Error 434 may also appear for other port types – refer to
the corresponding manual section.
437
Error
SAME E1 BOUND TO
DIFFERENT PPP PORTS
E1 port can’t be bound to more than one PPP port
5.16 Internal Ethernet (D-NFV) Ports
Applicable Modules
These ports are available in D-NFV modules.
Standards Compliance
IEEE 802.3, RFC 4836, RFC 3635.
Factory Defaults
By default, the D-NFV Ethernet ports have the following configuration.
config>port>int-eth(2/1)# info detail
name "IO-2 ethernet 01"
tag-ethernet-type 0x8100
min-tagged-frame-length 68
egress-mtu 1790
queue-group profile "MaxDefaultQueueGroup"
no policer
For description of default queue group profiles, see Queue Group Profiles section
in Chapter 8.
Megaplex-4
Internal Ethernet (D-NFV) Ports
5-109
Chapter 5 Cards and Ports
Installation and Operation Manual
Configuring Internal Ethernet Ports
To configure the internal Ethernet port parameters of the D-NFV module:
1. Navigate to configure port int-ethernet <slot>/<1> to select the Ethernet
port to configure.
The config>port>eth>(<slot>/<1>)# prompt is displayed.
Note
Port 2 will be activated in the future versions.
2. Enter all necessary commands according to the tasks listed in the table
below.
Note
There is no need in opening the internal Ethernet port, since it always up.
Task
Command
Comments
Assigning short description to the
port
name <string>
Using no name removes the name
Setting maximum frame size (in
bytes) to transmit (frames above
the specified size are discarded)
egress-mtu <64–9600>
Assigning queue group profile to
Ethernet port
queue-group profile <queuegroup-profile-name>
Megaplex-4 with CL.2/A modules only
The queue group profile is defined under
Quality of Service (QoS) in Chapter 8.
no queue-group removes queue group
association
The default queue group profile for Fast
Ethernet ports is defined with 10 Mbps
shaper. Define a new queue group profile if
you need more bandwidth.
The queue group profile cannot be edited.
Thus to use bridge connectivity you need to
remove the existing queue group profile from
this Ethernet port, configure a new queue
group profile and assign it to this port.
Activating/deactivating a policer
profile
policer-profile <name>
The policer profile is defined under Quality of
Service (QoS) in Chapter 8.
Using no policer <name> deactivates this
policer profile
Setting the minimum VLAN-tagged
frame length (in bytes) that will
be accepted
min-tagged-frame-length {64 | 68
| 72}
Specifying the Ethertype expected
in Ethernet packet
tag-ethernet-type
<0x0000-0xFFFF>
5-110
Internal Ethernet (D-NFV) Ports
Megaplex-4 with CL.2/A modules only
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Displaying D-NFV Internal Ethernet Port Status
You can display the status and configuration of an individual internal Ethernet
port.
To display status of a D-NFV internal Ethernet port:
•
At the prompt config>port>int-eth(<slot>/<1>)#, enter show status.
The Ethernet port status parameters are displayed.
For example:
config>port>int-eth(2/1)# show status
Name IO-2 ethernet 01
Administrative Status : Up
Operational Status
: Up
Auto Negotiation
: Complete
Speed And Duplex
: 1000 Full Duplex
Testing D-NFV Ports
No testing is available.
Displaying Ethernet Port Statistics
The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819.
To display the D-NFV Ethernet port statistics:
•
At the prompt config>slot>port>int-eth(<slot>/<port>)#, enter show
statistics.
Ethernet port statistics are displayed. The counters are described in the
table below.
config>port>int-eth(2/1)# show statistics
Running
----------------------------------------------------------------------------Counter
Rx
Tx
Total Frames
918141957
Total Octets
878307843
2624907620
Unicast Frames
917997904
18446744073418874042
Multicast Frames 1644
1644
Broadcast Frames 242476
98423
FCS Errors -Jabber Errors
0
Undersize Frames 0
Oversize Frames 0
Discard Frames
-Paused Frames
Filtered Frames 65111933
64 Octets
Megaplex-4
--1519-Max Octets
0
--
142072
Internal Ethernet (D-NFV) Ports
5-111
Chapter 5 Cards and Ports
Installation and Operation Manual
65-127 Octets
518879389
128-255 Octets
539
256-511 Octets
134
512-1023 Octets 167213425
1024-1518 Octets 231906387
1519-Max Octets 0
Table 5-29. Ethernet Statistics Parameters
Parameter
Description
Total Frames
Total number of frames received/transmitted
Total Octets
Total number of bytes received/transmitted
Unicast Frames
Total number of unicast frames received/transmitted
Multicast Frames
Total number of multicast frames received/transmitted
Broadcast Frames
Total number of broadcast frames received/transmitted
Paused Frames
Total number of pause frames (used for flow control)
received/transmitted through the corresponding Ethernet port
FCS Errors
The number of frames received on this interface that are an
integral number of octets in length but do not pass the FCS
check
Filtered Frames
Total number of filtered frames received/transmitted
Jabber Errors
Total number of frames received with jabber errors
Oversize Frames
Total number of oversized frames received/transmitted
Undersize Frames
Total number of undersized frames received/transmitted
I/O Ethernet ports only
Discard Frames
Total number of discarded frames received/transmitted
Not relevant for D-NFV
64 Octets
Total number of received/transmitted 64-byte packets
65–127 Octets
Total number of received/transmitted 65–127-byte packets
128–255 Octets
Total number of received/transmitted 128–255-byte packets
256–511 Octets
Total number of received/transmitted 256–511-byte packets
512–1023 Octets
Total number of received/transmitted 512–1023-byte packets
1024–1518 Octets
Total number of received/transmitted 1024–1518-byte
packets
1519 - Max Octets
Total number of received/transmitted packets with
1519 bytes and up to maximum
Note
To clear the statistics for an Ethernet port:
•
At the prompt config>port>int-eth<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5-112
Internal Ethernet (D-NFV) Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
5.17 Logical MAC Ports
Applicable Modules
To describe and map the Ethernet traffic passing over different media (E1/T1, T3,
SDH/SONET, etc), the Megaplex-4 architecture uses a concept of Logical MAC
ports. Logical MAC represents the MAC layer of the entity. It should be bound to a
gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical layer.
Table 5-31 lists the possible entities that can be bound to the Logical MAC, with
their corresponding media, protocols and possible values.
Table 5-30. Entities Bound to Logical MAC
Entities
Media
Protocol
Module
Possible
Values
gfp
Ethernet over
SDH/SONET
GFP encapsulation
protocol
CL.2
1 to 32
gfp
Ethernet over T3
GFP encapsulation
protocol
T3
1 to 16
gfp
Ethernet over
E1/T1
GFP encapsulation
protocol
VS-16E1T1-EoP
1 to 16
hdlc
Ethernet over
SDH/SONET
LAPS encapsulation
protocol
CL.2
1 to 32
hdlc
Ethernet over
E1/T1
HDLC Layer 2 protocol
M8E1/M8T1, M8SL
1 to 32
mlppp
Ethernet over E1
MLPPP, PPP Layer 2
protocols
M8E1, M8SL
1
Factory Defaults
By default, the Logical MAC ports have the following configuration.
For CL module:
config>port>log-mac(cl-a/5)$ info detail
name "CL-A Logical mac 05"
shutdown
egress-mtu 1790
queue-group profile "LMDefaultQueueGroup"
tag-ethernet-type 0x8100
For T3 module:
config>port>log-mac(cl-a/5)$ info detail
name "IO-3 Logical mac 05"
shutdown
For VS-16E1T1-EoP module:
config>port>log-mac(cl-a/5)$ info detail
Megaplex-4
Logical MAC Ports
5-113
Chapter 5 Cards and Ports
Installation and Operation Manual
name "IO-10 Logical mac 05"
shutdown
tag-ethernet-type 0x8100
egress-mtu 1790
queue-group profile "LMDefaultQueueGroup"
For description of the Logical Mac default queue group profile, see Queue Group
Profiles section in Chapter 8.
Configuring Logical MAC Ports
To configure the Logical MAC port:
1. Navigate to configure port logical-mac <slot>/<port> to select the Logical Mac
entity to configure.
The config>port>logical-mac>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to
Logical MAC
name <string>*
Using no name removes the name
Administratively enabling Logical
MAC
no shutdown*
Using shutdown disables the Logical MAC
Binding HDLC port to Logical MAC
bind hdlc <slot>/<port>
Ethernet over E1/T1: port=HDLC bundle
Ethernet over SDH/SONET: port=VCG using
LAPS encapsulation protocol
Binding GFP port to Logical MAC
bind gfp <slot>/<port>*
GFP port=VCG using GFP encapsulation
protocol
Binding MLPPP port to Logical
MAC
bind mlppp <slot>/<port>
Enabling OAM (EFM) on the
Logical MAC port
efm
Setting maximum frame size (in
bytes) to transmit (frames above
the specified size are discarded)
egress-mtu <64–9600>
Assigning queue group profile to
Ethernet port
queue-group <queuegroup-profile-name>
Specifying the Ethertype
expected in Ethernet packet
tag-ethernet-type
<0x0000-0xFFFF>
Note
See Ethernet OAM (EFM) in Chapter 8.
no efm disables OAM (EFM)
no queue-group removes queue group
association
The only parameters used for configuration of logical-mac ports of T3 modules
are marked with an asterisk (*).
To bind a flow to a Logical MAC port, see ingress-port logical-mac command
under config>flows>flow.
5-114
Logical MAC Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Viewing MAC Address
For viewing the MAC address used by the Logical MAC port, follow the
instructions below.
To view the MAC address used by the Logical MAC port:
3. Navigate to config>port> log-mac (<slot>/<port>)#
4. Type show status.
The status is displayed, for example as follows:
config>port>log-mac(cl-a/1)$ show status
MAC Address : 00-20-D2-F3-BC-D5
Note
For MAC address allocation mechanism, see Chapter 10.
Displaying Logical MAC Statistics
You can display statistics for the Logical MAC ports of T3 modules.
To display the Logical MAC statistics:
At the prompt config>slot>port>log-mac (<slot>/<port>)#, enter show
statistics. Logical MAC statistics are displayed. The counters are described in the
table below. For example:
config>port>log-mac(9/1)# show statistics
Running
---------------------------------------------------------------Counter
Rx
Tx
Total Frames
23785
23789
Total Octets
2473744
2473952
Total Frames/Sec 914
914
Total Bits/Sec
761152
761216
Minimum Bits/Sec 0
0
Maximum Bits/Sec 761152
0
Unicast Frames
23786
23788
Multicast Frames 0
0
Broadcast Frames 0
0
Error Frames
0
64 Octets
0
0
65-127 Octets
23784
23784
128-255 Octets
0
0
256-511 Octets
0
0
512-1023 Octets 0
0
1024-1518 Octets 0
0
1519-2047 Octets 0
0
2048-Max Octets 0
0
Table 5-31. Logical MAC Statistics Parameters
Parameter
Description
Total Frames Rx/Tx
Total number of frames received/transmitted
Megaplex-4
Logical MAC Ports
5-115
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
Total Octets Rx/Tx
Total number of bytes received/transmitted
Unicast Frames Rx/Tx
Total number of unicast frames received/transmitted
Multicast Frames Rx
Total number of multicast frames received/transmitted
Broadcast Frames Rx
Total number of broadcast frames received/transmitted
Total Frames/Sec Rx/Tx
Number of frames received/transmitted per second
Total Bits/Sec Rx/Tx
Number of bits received/transmitted per second
Minimum Bits/Sec Rx/Tx
Minimum number of bits received/transmitted per second
Maximum Bits/Sec Rx/Tx
Maximum number of bits received/transmitted per second
64 Octets
Total number of received/transmitted 64-byte packets
65–127 Octets
Total number of received/transmitted 65–127-byte packets
128–255 Octets
Total number of received/transmitted 128–255-byte packets
256–511 Octets
Total number of received/transmitted 256–511-byte packets
512–1023 Octets
Total number of received/transmitted 512–1023-byte packets
1024–1518 Octets
Total number of received/transmitted 1024–1518-byte packets
1019–2047 Octets
Total number of received/transmitted 1024–1518-byte packets
2048-Max Octets
Total number of received/transmitted packets with 2048 bytes and up to
maximum
To clear the statistics for a Logical MAC port:
•
At the prompt config>port>log-mac<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.18 Management Ethernet Port
Megaplex-4 has one out-of-band management Ethernet port (CONTROL ETH)
located on each CL.2 module panel dedicated to management traffic. The port
has a 10BASE-T/100BASE-TX Ethernet interface. This interface supports MDI/MDIX
crossover, and therefore the port can always be connected through a “straight”
(point-to-point) cable to any other type of 10/100BASE-T Ethernet port (hub or
station).
The CONTROL ETH ports of both CL modules can be simultaneously connected to
the same LAN, through standard Ethernet hubs or switches.
To support out-of-band management, management stations, Telnet hosts, etc
can be attached to the same LAN, or to any LAN from which IP communication
with the CL.2 module Ethernet ports is possible.
5-116
Management Ethernet Port
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Benefits
Configuring a dedicated management port eliminates the possibility of
management traffic reducing bandwidth and/or causing interruptions in the
traffic flow caused by the management.
Configuring the Out-Of-Band Management Port
The following parameters can be configured for the management Ethernet port:
•
Port name
•
Administrative status.
To configure the Management Ethernet port parameters:
1. Navigate to configure port mng-ethernet <slot>/<port> to select the
Ethernet port to configure.
The config>port>mng-ethernet>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to port
name <string>
Using no before name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Configuring collection of
performance management statistics
for the port, that are presented via
the RADview Performance
Management portal
pm-collection interval <seconds>
Note: You can enable PM statistics
collection for all Ethernet ports rather than
enabling it for individual ports. In addition
to enabling PM statistics collection for the
ports, it must be enabled for the device.
Refer to the Performance Management
section in the Monitoring and Diagnostics
chapter for details.
5.19 Management Ethernet Port – Controlled
Forwarding
A set of special parameters allows the network manager (NoC operator) to
control the usage of the ETH OOB MNG by the personnel of a remote substation.
These parameters lock the management port from the remote users and allow its
opening only for a specific time interval. During this management timeout, data
forwarding is allowed and the personnel will be able to manage the port.
Benefits
Configuring a management activity timeout assures more security due to
controlled use of the Megaplex-4 host management port.
Megaplex-4
Management Ethernet Port – Controlled Forwarding
5-117
Chapter 5 Cards and Ports
Installation and Operation Manual
Functional Description
By default the management port at the remote site is disabled. Via remote access
from the NoC, the network manager sets the port to be active for a configurable
duration.
Since the command is on the system level, OOB ports of both CL modules are
configured identically.
Unless configured and saved otherwise, after power up the port returns to
“enable”.
In case the timeout is activated and OOB cable is not connected the timer will
start only after the OOB cable is reconnected. This function is needed to simplify
the synchronization between the substation personnel and the network manager.
CL Activity change or reconnecting mng-ethernet cable stops the timer and a new
command is needed to start the session again.
The flow chart below describes in a single diagram all events involved in
management timeout activation.
Figure 6-11. Management Forwarding Flow Chart
Configuring the Out-Of-Band Management Port Controlled Forwarding
To configure the Management Ethernet port parameters:
1. Navigate to config>mngmnt#.
2. Enter all necessary commands according to the tasks listed below.
5-118
Management Ethernet Port – Controlled Forwarding
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Enable traffic forwarding between
the mng-ethernet port and the
remote sub-station user
enable-mng-ethernet-traffic
no enable-mng-ethernet-traffic command
disables traffic forwarding (default state)
Set and activate the management
timeout
temp-enable-mng-ethernettraffic <0..120>
This activation/deactivation command does
not require commit command.
The command values are set in minutes.
Entering a new value while previous timer is
still active restarts the timer to the new
value.
0 stops the timer, management access via
mng-ethernet is not allowed
Changing of the mng-ethernet to
“shutdown” while timer is active stops
forwarding traffic.
Default: 30
To display the timeout remaining time, use the following command:
mp4100>config>mngmnt#show mng-ethernet-timeout
Traffic Forwarding Configured Timeout [Min]
Traffic Forwarding Remaining Time [Min]: 9
: 60
5.20 MLPPP Ports
Applicable Modules
MLPPP ports exist only on M8E1 and M8SL modules and are mapped to a PPP
port. The binding is done in two stages and the PPP port should be further bound
to the physical layer (see Figure 1-8 in Chapter 1).
M8E1 and M8SL modules have one MLPPP port per module.
The MLPPP bundle can use any number of the links supported by the module, that
is, from 1 to 8. All the links (ports) used by the MLPPP bundle must have identical
physical layer parameters and their line-type parameter must be configured as
unframed. Therefore, each bonded link adds 2048 kbps to the available
bandwidth.
Management traffic is carried inband, as part of the Ethernet traffic, using the
dedicated management VLAN configured for the Megaplex-4 host.
Note that ports bound to MLPPP ports cannot be part of a protection group.
However, some redundancy is inherent in the MLPPP protocol, because if one of
the bonded links is out-of-service, the result is only a reduction in the available
transmission bandwidth.
Standards Compliance
The MLPPP ports conform to the IETF RFC 1990 standard.
Megaplex-4
MLPPP Ports
5-119
Chapter 5 Cards and Ports
Installation and Operation Manual
Factory Defaults
Megaplex-4 is supplied with all MLPPP ports disabled. The MTU default value is
250.
Configuring MLPPP Ports
To configure an MLPPP port (bundle):
5. Navigate to configure port mlppp <slot>/<port> to select the MLPPP port
(bundle) to configure.
The config>port>mlppp>(<slot>/<port>)# prompt is displayed.
6. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to the
port
name <string>
Using no name removes the name
Administratively enabling the port
no shutdown
Using shutdown disables the bundle
Binding the PPP port to the MLPPP
port
bind ppp <slot>/<port>
Selecting the MTU (maximum
transmission unit) for fragmented
packet
mtu <value in bytes>
Slot: 1 to 10, Port: 1 to 8
Using no bind ppp<slot>/<port>
removes the binding
The supported range is 80 to 1600
bytes.
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
To map E1 port 1 to Ethernet Port 2:
•
Bind corresponding E1 streams to each PPP port
•
Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
•
Configure Logical Mac port 5/1 and bind to it the MLPPP port
•
Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.
# configure port ppp 5/1 bind e1 5/1
# configure port ppp 5/2 bind e1 5/2
# configure port ppp 5/3 bind e1 5/3
# configure port ppp 5/4 bind e1 5/4
# configure port ppp 5/5 bind e1 5/5
# configure port ppp 5/6 bind e1 5/6
# configure port ppp 5/7 bind e1 5/7
# configure port ppp 5/8 bind e1 5/8
#
# exit all
# configure port mlppp 5/1 no shutdown
5-120
MLPPP Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
# configure port mlppp 5/1 bind ppp 5/1
# configure port mlppp 5/1 bind ppp 5/2
# configure port mlppp 5/1 bind ppp 5/3
# configure port mlppp 5/1 bind ppp 5/4
# configure port mlppp 5/1 bind ppp 5/5
# configure port mlppp 5/1 bind ppp 5/6
# configure port mlppp 5/1 bind ppp 5/7
# configure port mlppp 5/1 bind ppp 5/8
# configure port logical-mac 5/1
config>port>log-mac(5/1)$ bind mlppp 5/1
config>port>log-mac(5/1)$ no shutdown
config>port>log-mac(5/1)$ commit
# configure flows classifier-profile unw match-any match all
config>flows>flow(01)$ classifier unw
config>flows>flow(01)$ egress-port eth 5/2
config>flows>flow(01)$ ingress-port logical-mac 5/1
config>flows>flow(01)$ commit
config>flows>flow(01)$ no shutdown
config>flows>flow(02)$ classifier unw
config>flows>flow(02)$ egress-port logical-mac 5/1
config>flows>flow(02)$ ingress-port eth 5/2
config>flows>flow(02)$ commit
config>flows>flow(02)$ no shutdown
Configuration Errors
See Table 5-29.
5.21 Mux-Eth-Tdm Ports (Fiber Optic Links of
Optimux Modules)
Applicable Modules
Mux-eth-tdm ports denote fiber optic links of Optimux modules.
Each Optimux module link has two optical ports, which can be operated as a
protection group, to enhance service availability to critical users. The service
provider can control each standalone unit through the link connecting the unit to
the Optimux module, and therefore can manage a large number of standalone
units from a central location.
OP-108C comprises two identical independently-operating sections, identified as
OP A and OP B, each of which is capable of multiplexing four independent internal
E1 data streams and up to 100 Mbps of Ethernet payload for transport over a
fiber-optic link. OP-34C has a single section capable of multiplexing 16
independent internal E1 data streams and up to 32 Mbps of Ethernet payload for
transport over a fiber-optic link.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-121
Chapter 5 Cards and Ports
Installation and Operation Manual
In addition to its own OP modules, Megaplex-4 can also operate with similar
modules initially designed for operation in the LRS-102 chassis. The difference
between the Megaplex and LRS modules is in the type of E1 ports:
•
Megaplex modules have internal E1 ports, and can be connected to other
ports within Megaplex-4 via the chassis TDM buses
•
LRS modules have external E1 ports which can be connected only to external
users, but cannot be connected to other ports within Megaplex-4 via the
chassis TDM buses.
In the CLI, LRS-102 modules are identified by “-e1” at the end of the module
name: for example, the LRS-102 OP-108C (OP-108C/E1) module is identified as
op108c-e1.
The following table shows the number of mux-eth-tdm ports on Megaplex-4 and
LRS-102 I/O modules.
Table 5-32. Mux-Eth-Tdm Ports
Module
Number of Ports
OP-108C, OP108C/E1
4:
OP34C
•
2 for Section OP A (mux-eth-tdm 1 main,
mux-eth-tdm 2 redundant)
•
2 for Section OP B (mux-eth-tdm 3 main,
mux-eth-tdm 4 redundant)
2 (mux-eth-tdm 1 main, mux-eth-tdm 2 redundant)
Standards Compliance
Fiber optic links of Optimux modules are RAD proprietary technology.
Functional Description
The link interface subsystem of each Optimux module section includes a link
redundancy switch, and two independent link interfaces (one for each link port)
with SFP sockets.
The link redundancy switch operates as follows:
•
When only one SFP is installed, only one link port is active. The link
redundancy switch then connects the link mux/demux to this port.
•
When both SFP are installed, but redundancy is disabled, the link redundancy
switch connects the link mux/demux to the first port (LINK 1 or LINK 3 in
OP-108C, OP-108C/E1, LINK 1 in OP-34C).
•
When both SFP are installed, and redundancy is enabled, the link redundancy
switch connects the link mux/demux to the port selected as the primary port
of the corresponding link. When signal loss is detected by the primary port,
the switch transfers the traffic to the other (secondary) port.
Each link interface performs the following functions:
5-122
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
•
The transmit path converts the link data and the associated clock signal
provided by the link mux/demux to the signals needed to drive the SFP that
provides the physical interface of each port, for transmission to the far end
equipment.
•
The receive path recovers the link data stream received from the far end
equipment, and the associated clock, and provides the data and clock to the
link mux/demux.
The link interfaces accept a wide range of SFPs, and therefore the performance
depends on the installed SFP model. RAD offers a wide range of SFPs to meet a
wide range of system requirements. The fiber-optic interfaces can operate over
62.5/125 micron multi-mode, or 9/125 micron single-mode fibers (typical
attenuation of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm). The offered SFPs include models that need a single fiber instead of the
customary two fibers; for example, WDM models SF1 and SF2 operating at two
different wavelengths, or the SF3 model with SC/APC (angled polished connector)
that operates at a single wavelength.
Note
It is strongly recommended to order OP modules with RAD SFPs installed: this will
ensure that prior to shipping RAD has performed comprehensive functional
testing on the assembled module, including SFPs. Although users can install their
own SFPs into OP modules, RAD cannot guarantee full compliance to product
specifications when using non-RAD SFPs, and cannot be held responsible for any
damage that may result if non-compliant transceivers are used. In particular,
users are warned to use only agency approved SFPs that comply with the local
laser safety regulations for Class 1 laser products.
Table 5-34 provides information on the characteristics of the SFPs offered by
RAD, together with typical maximum ranges (calculated assuming typical fiber
attenuations of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm, and a 3-dB margin).
All the fiber-optic interface options offer high performance and have a wide
dynamic range, which ensures that the receiver will not saturate even when using
short fiber-optic cables. (Saturation is caused when the optical power applied to
the receiver exceeds its maximum allowed input power, and results in very high
bit error rates.)
Table 5-33. Link Port Interface Characteristics
Module
Name
Transmitter
Type and
Wavelength
[nm]
Connector Fiber Type
Type
Typical
Output
Power
Receiver
Sensitivity
Typical Range
[dBm]
[km]
[miles]
[dBm]
SFP-1
LED, 1310
LC
62.5/125 Multimode
-18
-31
6.5
4.0
SFP-2
Laser, 1310
LC
9/125 Single mode
-12
-31
38
23.6
SFP-3
Long haul
laser, 1310
LC
9/125 Single mode
-2
-34
70
43.4
SFP-4
Long haul
laser, 1550
LC
9/125 Single mode
-2
-34
120
74.5
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-123
Chapter 5 Cards and Ports
Module
Name
Transmitter
Type and
Wavelength
[nm]
Installation and Operation Manual
Connector Fiber Type
Type
Typical
Output
Power
Receiver
Sensitivity
Typical Range
[dBm]
[km]
[miles]
[dBm]
SFP-10a Laser WDM,
LC
Tx –1310, Rx –
1550
9/125 Single mode
(single fiber)
-12
-30
40
24.8
SFP-10b Laser WDM,
LC
Tx –1550, Rx –
1310
9/125 Single mode
(single fiber)
-12
-30
40
24.8
SFP-18A Tx – 1310, Rx LC
– 1550
9/125 single mode
(single fiber)
-2
-30
60
37.3
SFP-18B Tx – 1550, Rx LC
– 1310
9/125 single mode
(single fiber)
-2
-30
60
37.3
SFP-19A Laser WDM,
LC
Tx –1490, Rx –
1570
9/125 single mode
(single fiber)
-8
-30
80
49.7
SFP-19B Laser WDM,
LC
Tx –1570/Rx –
1490
9/125 single mode
(single fiber)
-8
-30
80
49.7
SFP-24
62.5/125 Multimode
-7
-31
6.5
4.0
VCSEL
LC
The OP-34C, OP-108C modules (Megaplex-4) and the OP-108C/E1 modules
(LRS-102) can be connected to remote standalone Optimux units, or to other
modules installed in the Megaplex-4 or LRS-102 chassis via fiber optic links.
Factory Defaults
Megaplex-4 is supplied with all mux-eth-tdm ports disabled. The default far-endtype value is no far-end-type.
Configuring Optical Link Parameters and Accessing the Remote Unit
Configuring the Local Optical Link
To configure the optical link parameters:
1. Navigate to configure port mux-eth-tdm <slot>/<port> to select the port to
configure.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
5-124
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Note
Chapter 5 Cards and Ports
The number of <port> is:
• 1 or 3 for OP-108C
• 1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively. To use links 2
and 4 as protection links they must be set manually to “no shutdown”.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specify the type of far
end equipment
connected to this port
far-end-type {op-108 | op-108-eth | mplrs-card | op-34 | op-34-v35 | op-xle1 | op-xl-t1 | op-xl-e1-16 | other | op108l | op-108l-eth}
Assigning short
description to the remote
port connected to this
link
far-end-name <string>
Accessing
the remote device
connected to the uplink
See Table 5-35 for device
definitions and possible
interconnections.
Using no far-end-type removes the
name
Using no far-end-name removes the
name
Once the remote device has been
accessed by this command, you can
activates loopbacks and configure
parameters of the remote device
remote
Table 5-34. Far End Devices
Local Device
Remote Device
Description
OP-108C, OP-108C/E1
no far-end-type
No far end equipment is connected
op-108
Optimux-108 or Optimux-108L standalone unit without
Ethernet ports
op-108-eth
Optimux-108 or Optimux-108L standalone unit with
Ethernet ports
op-108l
Optimux-108L/BM standalone unit without Ethernet
ports
op-108l-eth
Optimux-108L/BM standalone unit with Ethernet ports
mp-lrs-card
OP-108C card installed in another Megaplex-4 or
OP-108C/E1 card installed in an LRS-102 or in another
Megaplex-4
other
Other type of equipment compatible with OP-108C.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-125
Chapter 5 Cards and Ports
Installation and Operation Manual
Local Device
Remote Device
Description
For OP-34C
no far-end-type
No far end equipment is connected
op-34
Optimux-34 standalone unit with 16 E1 ports and one
user Ethernet port with configurable throughput rate
op-xl-e1
Optimux-XLE1 standalone unit with 12 E1 ports and one
user Ethernet port providing a fixed throughput rate of
8 Mbps
op-xl-e1-16
Optimux-XLE1/16 standalone unit
op-34-v35
Optimux-34 standalone unit with 16 E1 ports, one V.35
port, and one user Ethernet port with configurable
Ethernet throughput rate
mp-lrs-card
OP-34C card installed in another Megaplex-4
other
Other type of equipment compatible with OP-34C.
Configuring the Remote Optimux
To configure the remote Optimux ports, you must first access the remote unit.
To access the remote unit:
3. Navigate to configure port mux-eth-tdm <slot>/<port> to select the optical
link connected to the device being tested.
Note
The number of <port> is:
• 1 or 3 for OP-108C
• 1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively, and cannot be
configured.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
4. Type remote.
Now you are at the remote Optimux context and can configure the
followings ports:
Management Ethernet port
User Ethernet port
Optical link
E1 ports.
To configure the remote Optimux management Ethernet port parameters:
5. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type
configure port mng-eth 1. (There is only one management Ethernet port on
any Optimux standalone device.)
6. Enter all necessary commands according to the tasks listed below.
5-126
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To configure the remote Optimux user Ethernet port parameters:
7. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type
configure port eth 1. (There is only one management Ethernet port on any
Optimux standalone device.)
8. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to
port
name <string>
Using no name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Enabling autonegotiation
auto-negotiation
Using no auto-negotiation disables
autonegotiation
Setting maximum advertised
capability (highest traffic
handling capability to be
advertised during the
autonegotiation process)
max-capability {100-full-duplex }
100-full-duplex – 100baseT full duplex
This parameter applies only if
autonegotiation is enabled and is
always 100-full-duplex. When
autonegotiation is disabled, this
parameter is replaced by speed-duplex.
This parameter is not relevant for the
Ethernet management port.
Setting data rate and duplex
mode of the Ethernet port,
when autonegotiation is
disabled
speed-duplex {10-full-duplex |
100-full-duplex |10-half-duplex
|100-half-duplex }
10-full-duplex –10baseT full duplex
100-full-duplex – 100baseT full duplex
10-half-duplex – 10baseT half duplex
100-half-duplex – 100baseT half
duplex.
When autonegotiation is enabled, this
parameter is replaced by max-capability.
Setting flow control for the
selected port (when operating
in the full duplex mode), or
back pressure (when operating
in the half-duplex mode)
flow-control
Using no flow-control disables flow
control
Activating/deactivating a
policer profile to set ingress
rate limitation (user port only)
policer-profile <name>
The policer profile for ingress rate
limitation is defined under qos (see
Configuring Policer Profiles in
Chapter 8).
Using no policer <name> deactivates
this policer profile
To configure the remote Optimux optical link parameters:
9. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type
configure port mux-eth-tdm <port 1..2> to select the optical link of the
remote device to be tested.
10. Enter all necessary commands according to the tasks listed below.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-127
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
To configure the remote Optimux E1 parameters:
11. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type:
Note
configure port e1 <port>.
The number of <port> is:
• 1 to 4 for each section for Optimux-108/108L
• 1 to 16 for Optimux-34.
12. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying port
impedance used by the
E1 port
interface-type {balanced | unbalanced}
Example
The following section illustrates how to configure the remote Optimux-108
connected to port 3 of local OP-108C module installed in slot 1:
•
Administratively enable the optical links, Ethernet port and all E1 ports.
•
Leave their parameters at their defaults.
configure port mux-eth-tdm 1/3 remote
configure port mux-eth-tdm 1 no shutdown
configure port mux-eth-tdm 2 no shutdown
configure port ethernet 1 no shutdown
configure port e1 1 no shutdown
configure port e1 2 no shutdown
configure port e1 3 no shutdown
configure port e1 4 no shutdown
exit-remote
exit all
Configuration Errors
The table below lists messages generated by Megaplex-4 when a configuration
error on modules with mux-eth-tdm ports (OP-108C/OP-34C) is detected.
5-128
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Table 5-35. OP-108C/OP-34C Configuration Error Messages
Code
Type
Syntax
Meaning
500
Warning
FAR-END CHANGED, DEVICE
WILL RESTART
The type of far-end device connected to the OP-108C
module is different from the one configured. The module
will perform a reset.
501
Error
NOT IDENTICAL FAR-END
DEVICE TYPE
When two far end devices are connected to the OP-108C
module, they must be identical.
502
Error
PORT ASSIGNED TO
DISCONNECTED LINK
The optical link (mux-eth-tdm port) status is set to
shutdown, while the corresponding E1 or Ethernet ports
are configured as “no shutdown”.
503
Error
ETH RATE & E1/T1/TRIBUTARY
RATE MISMATCH
The far-end user Ethernet port rate exceeds the available
link bandwidth. Increase the bandwidth by reducing the
number of active E1 ports
Viewing Optical Link SFP Status Information
For viewing the status of the optical link SFP, follow the instructions below.
To view the status of a local optical link SFP:
13. Navigate to mux-eth-tdm (<slot>/<port>)#
14. Type show sfp-status.
The status is displayed, for example as follows:
config>port>mux-eth-tdm(11/3)# show sfp-status
SFP
--------------------------------------------------------------Connector Type
: LC
Manufacturer Name
: WTD
Manufacturer Part Number
: RTXM139-BG-RAD
Typical Maximum Range (Meter) : 15000
Wave Length (nm)
: 1310
Fiber Type
: SM
SFP
--------------------------------------------------------------Current
Minimum
Maximum
RX Power (dBm)
: 0.0 dBm
TX Power (dBm)
: 0.0 dBm
Laser Bias (mA)
: 0.0 mA
Laser Temperature (Celsius) : 0.0 C
Power Supply (V)
: 3.3 V
The performance monitoring data for the OP module link physical layer includes
status data for each link port, and SFP data for the installed SFPs. Table 4-4
explains the parameters of the SFP installed for selected link port.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-129
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 4-4. Link SFP Parameters
Parameter
Description
Connector Type
Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name
Displays the original manufacturer’s name
Vendor PN
Displays the original vendor’s part number
Typical Max. Range
(Meter)
Displays the maximum range expected to be achieved over typical optical fibers, in
meters
Wave Length (nm)
Displays the nominal operating wavelength of the SFP, in nm
Fiber Type
Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm)
Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm)
Displays the current optical power, in dBm, received by the SFP
Laser Bias (mA)
Displays the measured laser bias current, in mA
Laser Temperature
(Celcius)
Displays the measured laser temperature, in °C
Power Supply (V)
Displays the SFP power supply voltage
For displaying protection status, see Example 2 in TDM Group Protection section
in Chapter 7.
Testing Optical Links
The test and diagnostics functions available on each optical link are:
•
Local loopback on local OP module link
•
Remote loopback on local OP module link
•
Local loopback on remote Optimux unit (OP module only, with limited
duration)
•
Remote loopback on remote Optimux unit
Local Loopback on Local Optical Link
A typical signal flow for a local loopback on the local OP module link is shown in
Figure 5-11. Note that AIS is sent to the link as shown in Figure 5-11 only when
the far end device configured for the tested section is a basic Optimux unit (with
E1 ports only); when the far end device includes an Ethernet port, a special
pattern is sent, and the Ethernet ports (both on the tested section of the local
OP module, and on the remote Optimux) are shut down for the duration of the
test.
5-130
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Megaplex-4100
OP-108C Section
or OP-34C
CL
1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Link
Mux/Demux
Uplink
Interface
Figure 5-12. Signal Flow for Link Local Loopback on Local OP Module
When a link local loopback is activated on an OP module, the link transmit signal
is returned to the input of the link receive path at a point just before the uplink
interface. The local link receive path will receive its own signal, and therefore
must operate normally.
In addition, user equipment connected via each E1 internal port served by the
corresponding link must also receive its own signal and thus it must be
synchronized.
This test checks the operation of the local OP link (section), and the connections
to the E1 equipment attached via local internal E1 ports.
Remote Loopback on Local Optical Link
A typical signal flow for a remote loopback on the local OP-108C link is shown in
the figure below.
Megaplex-4100
OP-108C - OP-A Section
CL
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Link
Mux/Demux
Uplink
Interface
Figure 5-13. Signal Flow for Link Remote Loopback on Local
OP Link
When a link remote loopback is activated on an OP module, the received link
signal is processed by the uplink interface, returned to the input of the link
transmit path at a point just before the uplink interface, and transmitted back to
the far end device. Therefore, the far end device receives its own TDM signal, and
its TDM paths must operate normally.
During the test, the local link receive path supplies AIS signals to each local
internal E1 port.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-131
Chapter 5 Cards and Ports
Installation and Operation Manual
This test checks the connections between the user E1 equipment attached to the
E1 ports of the far end device, the operation of the far end device, the uplink
interface of the local OP module (module section), and the network connections
between the local OP module and the far end device.
Link Local Loopback on Remote Optimux
A typical signal flow for a local link loopback on the remote Optimux-108/108L is
shown in Figure 5-13. Note that AIS is sent to the link as shown in Figure 5-13
only when the far end device connected to the tested section is a basic Optimux
(with E1 ports only).
The link local loopback signal path on the remote Optimux is shown in
Figure 5-13.
Megaplex-4100
Local OP-108C Section
Remote Optimux
CL
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
..
.
E1/ Payload
Mux/Demux
"1"
E1
Port 1
LIU 4
(16)
..
.
.
.
E1
Port 4
(16)
Figure 5-14. Typical Signal Flow for Link Local Loopback on Remote Optimux
When a link local loopback is activated by an OP module command on the
connected Optimux, the Optimux link transmit signal is returned to the input of
its link receive path within the uplink interface. The Optimux link receive path will
receive its own signal, and therefore must operate normally.
In addition, user equipment connected to each OP module E1 port served by the
link must receive an AIS signal.
Ethernet traffic will not be disrupted while the loopback is activated.
This test checks the operation of the far end Optimux, and the connections to
the E1 equipment attached to the far end E1 ports.
This test is possible for OP-108C only with limited (not infinite) duration and not
available for OP-34C.
Link Remote Loopback on Remote Optimux
A typical signal flow for a link remote loopback is shown in Figure 5-14. Note that
AIS is applied only when the far end device connected to the tested section is a
basic Optimux (with E1 ports only). Ethernet traffic will not be disrupted while the
loopback is activated.
5-132
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Remote Optimux
Megaplex-4100
CL
E1
Port 1
LIU 1
"1"
Routing
Matrix
Other Port
Interface
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
E1 Payload
Mux/Demux
..
.
..
..
.
E1
Port 4
(16)
LIU 4
(16)
Figure 5-15. Typical Signal Flow for Link Remote Loopback on Remote Optimux
When a link remote loopback is activated on an Optimux, the received link signal
is processed by the uplink interface, returned to the input of the link transmit
path, and transmitted back to the local OP module. Therefore, the local OP
module receives its own TDM signal, and its TDM paths must operate normally.
In addition, user equipment connected via each local OP module internal E1 port
served by the corresponding link must also receive its own signal and thus it must
be synchronized.
This test checks the connections between the user E1 equipment attached to the
internal E1 ports of the local OP module, the operation of the local OP module,
the uplink interface of the far end device, and the network connections between
the local OP module and the far end device.
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the OP module. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local module before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating the Loopbacks
To perform a loopback on the local optical link:
1. Navigate to configure port mux-eth-tdm <slot>/<port> to select the optical
link to be tested.
Note
The number of <port> is:
• 1 or 3 for OP-108C
• 1 for OP-34C
Loopbacks on protection ports 2 and 4 (of the same kind as on links 1 and 3) are
activated automatically, provided the protection links are at “no shutdown”.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
Megaplex-4
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-133
Chapter 5 Cards and Ports
Installation and Operation Manual
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}
[duration <duration in minutes
1..30> ]
local – local loopback
Stopping the loopback
no loopback
remote – remote loopback
To perform a loopback on the remote optical link:
15. Navigate to configure port mux-eth-tdm <slot>/<port> to select the optical
link connected to the device being tested.
Note
The number of <port> is:
• 1 or 3 for OP-108C
• 1 for OP-34C
Remote devices connected to protection ports 2 and 4 cannot be configured.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
16. Type remote.
17. Navigate to configure port mux-eth-tdm <port 1..2> to select the optical link
of the remote device to be tested.
18. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}
[duration <duration in minutes
1..30> ]
local – local loopback:
•
not available for OP-34C
•
for OP-108C available only when
the duration is not infinite
remote – remote loopback
Stopping the loopback
no loopback
5.22 PCS Ports
Applicable Modules
PCS (Physical Coding Sublayer) ports available on the ASMi-54C and SH-16
modules determine the Ethernet (packet) physical layer transmission capabilities
over SHDSL lines. The number of PCS ports on each module is 8 for ASMi-54C
modules and 16 for SH-16 modules.
The following can be configured for the PCS ports:
5-134
•
Assigning PCS port name
•
Setting port administrative status
PCS Ports
Megaplex-4
Installation and Operation Manual
•
Chapter 5 Cards and Ports
Binding an SHDSL port to a PCS port
Standards Compliance
PCS ports comply with IEEE 802.3-2005.
Functional Description
In Megaplex-4, PCS ports are used to transport Ethernet traffic over SHDSL.
The internal SHDSL processing subsystem of ASMi-54C and SH-16 modules
enables configuring the desired Physical Coding Sublayer parameters for each
SHDSL line (actually – for each SHDSL port).
PCS ports are processed in groups of four:
•
ASMi-54C modules include two groups of PCS ports: 1 to 4, and 5 to 8.
•
SH-16 modules include four groups of PCS ports: 1 to 4, 5 to 8, 9 to 12 and
13 to 16.
PCS ports are independently configurable.
In ASMi-54C/ETH and SH-16 modules, the available bandwidth is the payload rate
of the associated line. In ASMi-54C/N, the available PCS bandwidth is the payload
rate of the associated line, less any bandwidth assigned to the associated E1
port of the same line.
Even when all SHDSL lines of the ASMi-54C/SH-16 modules operate in 2-wire
mode, the PCS transport bandwidth can be increased using PAF (PME Aggregation
Function), also defined in IEEE 802.3-2005. PAF creates PCS groups. The PCS
groups that can be configured on the ASMi-54C/N, ASMi-54C/ETH and SH-16
modules are listed in Table 5-38, Table 5-39 and Table 5-40, respectively.
The main functions performed for each PCS port include:
•
Ethernet payload data rate matching: the average payload rate accepted by
each PCS port is matched to the physical rate supported by the
corresponding PME.
•
As for M-pair bonding, one of the PCS ports (the PCS with the lowest index in
the group) is automatically selected as the master PCS port, from which all
the other PCS ports copy their parameters.
Each active PCS port can serve as a bridge port that can terminate Ethernet flows
configured within the Megaplex-4.
Table 5-37. Supported PCS Groups versus Lines Parameter, ASMi-54C/N module
Maximum Number of
PCS Groups
Number of SHDSL
Ports in PCS Group
2 (4 wires)
4
2 (4 wires)
Megaplex-4
SHDSL Ports in
PCS Group
Master PCS in the
Group
1, 2
1
3, 4
3
5, 6
5
7, 8
7
PCS Ports
5-135
Chapter 5 Cards and Ports
Installation and Operation Manual
Maximum Number of
PCS Groups
Number of SHDSL
Ports in PCS Group
8
1 (2 wires)
SHDSL Ports in
PCS Group
Master PCS in the
Group
1 to 8
N/A
Table 5-38. Supported PCS Groups versus Lines Parameter for ASMi-54C/ETH
Maximum
Number of PCS
Groups
Number of SHDSL
Ports (Lines) in PCS
Group
2
SHDSL Lines in
PCS Group
Master PCS in the
Group
4
1, 2, 3, 4
1
4
5, 6, 7, 8
5
1, 2
1
3, 4
3
5, 6
5
7, 8
7
2
4
2
Table 5-39. Supported PCS Groups versus Lines Parameter for SH-16
Maximum
Number of PCS
Groups
4
8
16
Number of SHDSL
Ports (Lines) in PCS
Group
4(8 wires)
2(4 wires)
1(2 wires)
SHDSL Lines in
PCS Group
Master PCS in the
Group
1, 2, 3, 4
1
5, 6, 7, 8
5
9,10, 11,12
9
13,14, 15,16
13
1, 2
1
3, 4
3
5, 6
5
7, 8
7
9,10
9
11,12
11
13,14
13
15,16
15
1,2…, 16
-
Factory Defaults
By default, the PCS ports have the following configuration.
config>port>pcs(3/3)# info detail
name "IO-3 Pcs 03"
shutdown
5-136
PCS Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
tag-ethernet-type 0x8100
no efm
egress-mtu 1790
queue-group profile "PcsDefaultQueueGroup"
no l2cp
For description of the PCS default queue group profile, see Queue Group Profiles
section in Chapter 8.
Configuring a PCS Port
To configure a PCS port:
1. Navigate to configure port pcs <slot>/<port> to select the port to configure.
The config>port>pcs>(<slot>/<port># prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to a name <string>
PCS port
Using no name removes the name
Administratively enabling the
port
Using shutdown disables the PCS
no shutdown
Enabling OAM (EFM) on the PCS efm
port (Carrier Ethernet class CL
only)
See Ethernet OAM (EFM) in Chapter 8.
ASMi-54C/ETH modules (without E1 links)
and SH-16 modules
no efm disables OAM (EFM) on the PCS
port
Setting maximum frame size (in egress-mtu <64–9600>
bytes) to transmit (frames
above the specified size are
discarded)
Associating a Layer-2 control
l2cp <l2cp-profile-name>
processing profile with the port no l2cp
(Carrier Ethernet class CL only)
ASMi-54C/ETH modules (without E1 links)
and SH-16 modules
Defines discarding or tunneling policy for
Layer-2 protocols.
no l2cp removes association with L2CP
profile
The associated L2CP profile specifies peer
action for the following MAC addresses
depending on the protocol in use:
Assigning queue group profile
to the PCS port (Carrier
Ethernet class CL only)
Megaplex-4
queue-group profile <queuegroup-profile-name>
•
01-80-C2-00-00-00 (RSTP)
•
01-80-C2-00-00-02 (OAM (EFM))
no queue-group removes queue group
association
PCS Ports
5-137
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Specifying the Ethertype
expected in Ethernet packet
(Carrier Ethernet class CL only)
tag-ethernet-type
<0x0000-0xFFFF>
Binding a SHDSL port to a PCS
port
bind shdsl <slot><port>
Comments
Using no before bind removes the binding
Displaying PCS Port Status
You can display the status and configuration of an individual PCS port.
To display the status of a PCS port:
•
At the prompt config>port>pcs(<slot/port)#, enter show status.
The PCS port status parameters are displayed.
For example:
To display the status of PCS port 15 of an SH-16 module installed in slot 3:
config>port>pcs(3/15)# show status
Name
: IO-3 Pcs 15
Administrative Status : Up
Operation Status
: Testing
Loopback
: Remote On Remote
Testing PCS Ports
You can perform a remote-on-remote loopback of the PCS port of the
ASMi-54C/N and SH-16 modules. In ASMi-54C/N, this loopback is mainly used in
the Ethernet BERT test but can be also used to check Ethernet connectivity using
external test equipment.
•
The ASMi-54C/ETH module does not support loopbacks on its PCS ports.
To perform a loopback on a PCS port of the ASMi-54C/N or SH-16 module:
1. Navigate to configure port pcs <slot>/<port> to select the PCS port to
configure.
The config>port>pcs>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Warning
Before activating the remote-on-remote loopback on a PCS port, be aware that if
Ethernet services are being provided by the system, the traffic passing through
the PCS port will be looped. Take appropriate care to prevent this scenario. Do
not activate this loop when the system is connected to the live network.
19.
5-138
PCS Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Setting loopback duration
and activating the loopback
on the PCS port
loopback remote-on-remote duration Using no loopback disables the loopback
<duration in minutes 1..30> ]
Displaying PCS Statistics
You can display statistics for the PCS ports of SH-16 modules and all kinds of
ASMi-54C modules.
To display the PCS statistics:
At the prompt config>slot>port>pcs (<slot>/<port>)#, enter show statistics
followed by parameters listed below.
PCS statistics are displayed. The counters are described in the table
below. For example:
config>port>pcs(3/1)# show statistics
Running
----------------------------------------------------------------Total Frames Rx
: 36911
Total Frames Tx
: 23851
Total Octets Rx
: 2511512
Total Octets Tx
: 1620916
Unicast Frames Tx
: 0
Multicast Frames Rx : 0
Broadcast Frames Rx : 0
FCS Errors
: 0
Jabber Errors
: 0
Undersize Frames
: 0
Oversize Frames
: 0
Paused Frames
: 0
64 Octets
: 0
65-127 Octets
: 36706
128-255 Octets
: 0
256-511 Octets
: 0
512-1023 Octets
: 0
1024-1528 Octets
: 0
Table 5-40. PCS Statistics Parameters
Parameter
Description
Total Frames Rx/Tx
Total number of frames received/transmitted
Total Octets Rx/Tx
Total number of bytes received/transmitted
Unicast Frames Tx
Total number of unicast frames transmitted
Multicast Frames Rx
Total number of multicast frames received
Broadcast Frames Rx
Total number of broadcast frames received
FCS Errors
Total number of frames received on this PCS that are an integral number of
octets in length but do not pass the FCS check
Megaplex-4
PCS Ports
5-139
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
Jabber Errors
Total number of frames received with jabber errors
Undersize Frames
Total number of undersized frames received/transmitted
Oversize Frames
Total number of oversized frames received/transmitted
Paused Frames
Total number of pause frames (used for flow control) received/transmitted
through the corresponding PCS
64 Octets
Total number of received/transmitted 64-byte packets
65–127 Octets
Total number of received/transmitted 65–127-byte packets
128–255 Octets
Total number of received/transmitted 128–255-byte packets
256–511 Octets
Total number of received/transmitted 256–511-byte packets
512–1023 Octets
Total number of received/transmitted 512–1023-byte packets
1024–1528 Octets
Total number of received/transmitted 1024–1528-byte packets
To clear the statistics for a PCS:
•
At the prompt config>port>pcs<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.23 PPP Ports
Applicable Modules
PPP is the intermediate layer between the MLPPP and the physical (E1) layer.
Dividing the Ethernet traffic between several PPP ports grouped by a single
MLPPP entity provides increased bandwidth over several physical connections.
PPP ports exist only on M8E1 and M8SL modules.
Standards Compliance
The PPP ports conform to the IETF RFC 1990 standard.
Factory Defaults
Megaplex-4 is supplied with all PPP ports disabled.
Configuring PPP Ports
To configure a PPP port:
1. Navigate to configure port ppp <slot>/<port> to select the PPP port to
configure.
The config>port>ppp>(<slot>/<port>)# prompt is displayed.
5-140
PPP Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to port
name <string>
Using no name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Binding the PPP port (logical entity) to
the E1 physical port of a M8E1/M8SL
module
bind e1 <slot>/<port>
Slot: 1 to 10; Port: 1 to 8
Using no bind e1 <slot>/<port>
removes the binding
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
Note
To map E1 port 1 to Ethernet Port 2:
•
Bind corresponding E1 streams to each PPP port
•
Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
•
Configure Logical Mac port 5/1 and bind to it the MLPPP port
•
Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.
The PPP ports are administratively enabled by default so there is no need for the
no shutdown command.
•
# configure port ppp 5/1 bind e1 5/1
# configure port ppp 5/2 bind e1 5/2
# configure port ppp 5/3 bind e1 5/3
# configure port ppp 5/4 bind e1 5/4
# configure port ppp 5/5 bind e1 5/5
# configure port ppp 5/6 bind e1 5/6
# configure port ppp 5/7 bind e1 5/7
# configure port ppp 5/8 bind e1 5/8
#
# exit all
# configure port mlppp 5/1 no shutdown
# configure port mlppp 5/1 bind ppp 5/1
# configure port mlppp 5/1 bind ppp 5/2
# configure port mlppp 5/1 bind ppp 5/3
# configure port mlppp 5/1 bind ppp 5/4
# configure port mlppp 5/1 bind ppp 5/5
# configure port mlppp 5/1 bind ppp 5/6
# configure port mlppp 5/1 bind ppp 5/7
# configure port mlppp 5/1 bind ppp 5/8
# configure port logical-mac 5/1
config>port>log-mac(5/1)$ bind mlppp 5/1
config>port>log-mac(5/1)$ no shutdown
config>port>log-mac(5/1)$ commit
Megaplex-4
PPP Ports
5-141
Chapter 5 Cards and Ports
Installation and Operation Manual
# configure flows classifier-profile unw match-any match all
config>flows>flow(01)$ classifier unw
config>flows>flow(01)$ egress-port eth 5/2
config>flows>flow(01)$ ingress-port logical-mac 5/1
config>flows>flow(01)$ commit
config>flows>flow(01)$ no shutdown
config>flows>flow(02)$ classifier unw
config>flows>flow(02)$ egress-port logical-mac 5/1
config>flows>flow(02)$ ingress-port eth 5/2
config>flows>flow(02)$ commit
config>flows>flow(02)$ no shutdown
Configuration Errors
See Table 5-29.
5.24 Serial Ports
Applicable Modules
The following table shows the type and number of serial ports available on each
Megaplex-4 serial I/O module.
Table 5-41. Megaplex-4 Serial Ports
5-142
Module
Type of Module
Number of Ports
HS-6N, HS12N
n x 64 kbps high speed
6/12
HSU-6, HSU12
ISDN “U”
6/12
HSS
ISDN “S”
4
HS703
Codirectional data
4
HS-RN
sub-DSO low speed
4
HSF-2
fiber optic teleprotection
2
LS-6N, LS-12
low speed
6/12
Serial Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Module
Type of Module
Number of Ports
VS-6/BIN, VS-6/C37
versatile
6
versatile
12
VS-6/FXS, VS-6/FXO,
VS-6/E&M, VS-6/E1T1
VS-12
The following parameters can be configured for the serial ports:
•
Port name
•
Administrative status
•
Clock mode
•
Port data rate
•
Size of the FIFO buffer used by the channel
•
Port transmission mode
•
Setting CTS line to track the state of the local RTS line
•
Selecting the number of data bits/ stop bits and controlling the
end-to-end transfer of the parity bit in the asynchronous word format
•
Selecting other parameters for specific kind of modules.
Table 5-43 summarizes the features available for serial ports of different I/O
modules. To configure a specific module, select its supported parameters in
Table 5-43 and then refer to Configuring Serial Port Parameters for configuration
instructions. In addition, consult the corresponding module section in Megaplex-4
I/O Modules Installation and Operation Manual for specific configuration
considerations.
Table 5-42. Features Supported by Megaplex-4 Serial Ports
Feature/Command
HS-
HS-6N/12N
VS
HS-S
RN
Number of ports
4
6/12
HS-U-6/12
HS-U-6/12
“I” Mode
“1” Mode
6/12
6/12
4
6/12
cmd-in*
bri
bri
LS-6N, LS-12
HSF-2
6/12
2
serial-bundle
cmd-out*
–
–
cmd-ch*
ports)
√
–
√
√
√
√
–
–
name
√
√
√
√
√
√
√
√
shutdown
√
√
√
√
√
√
√
√
clock-mode
√
√
–
–
–
√
√
–
cts-rts
√
√
√
–
–
–
√
–
rate
√
√
√
–
–
√
–
√
fifo-size
–
√
–
–
–
–
–
–
Additional ports
–
–
Split TS crossconnect (for serial
Megaplex-4
Serial Ports
5-143
Chapter 5 Cards and Ports
Feature/Command
Installation and Operation Manual
HS-
HS-6N/12N
VS
HS-S
RN
HS-U-6/12
HS-U-6/12
“I” Mode
“1” Mode
LS-6N, LS-12
HSF-2
mode
√
–
√
–
–
√
√
–
encapsulation-mode
√
–
√
–
–
–
–
–
end-to-end-control
√
–
√
–
–
√
√
–
data-bits
√
–
√
–
–
√
√
–
parity
√
–
√
–
–
√
–
–
stop-bits
√
–
√
–
–
√
–
–
rate-adaptive
–
–
–
–
–
√
–
–
interface
–
–
√
√
√
–
–
–
activation-type
–
–
–
–
√
–
–
–
s-bit-signaling
–
–
√
–
–
–
–
–
data-position
–
–
√
–
–
–
–
–
*for VS-6/BIN modules
Support of some features related to serial ports differs for different VS modules.
These features are listed in the following table.
Table 5-43. Additional Features Related to Serial Ports of I/O Modules
I/O Module
R.111
Conference
DS0-SNCP Bundles/
Encapsulation
Mode
DS0 Groups
Yes
No
28/14
VS-6/C37
Yes
No
16/8
VS E&M Voice with serial ports
Yes
No
24/12
VS-6/BIN
Yes
Yes
12/6
VS-FXS/E&M
No
N/A
20/10
VS FXS/FXO Voice
No
No
28/14
VS E&M Voice (PW-enhanced)
No
No
20/10
VS-6/8E1T1/PW
No
No
N/A
VS-12, VS FXS/FXO Voice with
serial ports (basic)
(basic)
(PW-enhanced), VS-6/703
Standards Compliance
The Megaplex-4 serial ports comply with following standards:
5-144
•
HS-703: ITU-T G.703, Codirectional interface
•
LS-6N/LS-12 channel interface: ITU-T Rec. V.24/EIA RS-232, user-selectable
DCE or DTE
Serial Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
•
LS-6N/LS-12 async-to-sync conversion method compatible with ITU-T Rec.
V.14
•
HS-RN channel interface: ITU-T Rec. V.24/EIA RS-232, ITU-T Rec. V.110
•
HSF-2: IEEE PC37.94 standard draft
•
VS: Serial channels interface: V.35, V.11/RS-422, V.24/ EIA RS-232, ITU-T Rec.
V.110.
Functional Description
See corresponding section in Megaplex-4 I/O Modules Installation and Operation
Manual for each module.
Factory Defaults
Megaplex-4 is supplied with all serial ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
clock-mode
dce
HSF-2: 1x64
HSU-6/12: 1.2
rate
HS-RN: 0.6
LS-6N/LS-12: 9.6
VS, HS-6N/12N: 1 x 64kbps
fifo-size
auto
mode
sync
encapsulation-mode
VS modules: none
HS-RN: bandwidth
cts-rts
no cts-rts (disabled)
end-to-end-control
no end-to-end-control (disabled)
data-bits
8 (HSU-6/12 modules:7)
parity
no parity (disabled)
stop-bits
1
rate-adaptive
proprietary
interface
Megaplex-4
VS modules: v35
HSU modules: nt
activation-type
1
s-bit-signaling
off
data-position
F:0 B:1
Serial Ports
5-145
Chapter 5 Cards and Ports
Installation and Operation Manual
Configuring Serial Port Parameters
To configure the serial port parameters:
1. Navigate to configure port serial <slot>/<port> to select the serial port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Configuring the clock mode
in synchronous mode
HS-RN, HSU-6/12 (lt1 mode
only): clock-mode
{dce|external-dce}
•
dce – The port provides transmit and
receive clocks to the DTE
•
external-dce – The port provides the
receive clock to the DTE, and accepts the
transmit clock from the DTE
•
dte – The channel interface requires
transmit and receive clock signals from
the user’s equipment
HS-6N/12N, LS-6N/LS-12:
clock-mode {dce | externaldce | dte }
In modules with sync/async operation this
selection is relevant only for synchronous
mode
Setting the data rate of this
port in kbps. The selection
depends on the module and
encapsulation type
HS-6N/12N: rate {1 | 2 | 3 | 4 |
5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 14 | 15 | 16 | 17 | 18 | 19
| 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31} x
{56kbps | 64kbps}
The allowed range is n×56 kbps or n×64 kbps,
where n is 1 through 24 for a T1 link, and 1
through 31 for an E1 link.
In HS-6N/12N modules with V.24/RS-232
interface, the data rate for all channels is
64 kbps only.
HSF-2: rate {1x64 | 2x64 |
3x64 | 4x64 | 5x64 | 6x64 |
7x64 | 8x64 | 9x64 | 10x64}
HSU-6/12 (lt1 mode only):
rate {1.2 | 2.4 | 4.8 | 9.6 | 16 |
19.2 | 32 | 38.4 | 48 | 56 |
57.6 | 64 | 115.2 | 128}
5-146
Serial Ports
The available data rates depend on the port
transmission mode:
•
Synchronous mode: 1.2, 2.4, 4.8, 9.6, 16,
19.2, 32, 38.4, 48, 56 (supported only
when connected to an ASMi-31 using
V.110 rate adaptation), 64 or 128 kbps.
•
Asynchronous mode: 1.2, 2.4, 4.8, 9.6,
19.2, 38.4, 48, 57.6 or 115.2 kbps.
Megaplex-4
Installation and Operation Manual
Task
Chapter 5 Cards and Ports
Command
Comments
HS-RN: rate {0.6 | 1.2 | 2.4 |
4.8 | 7.2 | 9.6 | 14.4 | 19.2 |
28.8 | 38.4 | 48 | 56 | 64}
The supported range is as follows:
ASYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
14.4*, 19.2, 28.8*, or 38.4 kbps.
SYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
14.4*, 19.2, 28.8*, 38.4, 56, or 64 kbps.
The rates marked by an asterisk (*) are
supported only by the HDLC-based model
When encapsulation-mode=latency, only
rates up to 19.2 kbps are supported, and the
required uplink bandwidth is always one full
timeslot. In sync mode, also 56 kbps and
64 kbps are supported.
When encapsulation-mode=3bit-transitional,
only 64 kbps is supported (rate is not
configurable).
LS-6N/LS-12: rate {2.4 | 4.8 |
7.2 | 8 | 9.6 | 14.4 | 16 | 19.2 |
24 | 28.8 | 32 | 38.4 | 48 | 56 |
57.6 | 64}
Determines the channel data rate, in kbps.
Group 1: 2.4, 4.8, 9.6, 19.2, 38.4
Group 2: 7.2, 14.4, 28.8, 57.6
Group 3: 8.0, 16.0, 24.0, 32.0, 48.0, 56.0,
64.0
Note: Both channels of a given pair must
operate at rates belonging to the same group.
Group 3 rates can be selected only on
channels using the synchronous protocol.
VS (encapsulationmode=none) : rate {1 | 2 | 3 |
4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18
| 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 |
31} x {56kbps | 64kbps}
The data rate of the serial port of VS-6/703
and PW-enhanced VS voice modules
protected by DS0-SNCP is limited to 1792K
(28*64 kbps).
VS (encapsulationmode=v110) : rate {2.4 | 4.8 |
9.6 | 19.2 | 38.4 }
VS (encapsulationmode=hcm): rate {2.4 | 4.8 |
9.6 | 19.2 | 38.4 }
With this encapsulation mode, each channel
always occupies one timeslot (64 kbps)
VS (encapsulationmode=r111): rate {2.4 | 4.8 |
9.6 | 19.2 }
For more information, see Configuring the
Rates with R.111 Encapsulation in Chapter 8
of the Megaplex-4 I/O Modules Installation
and Operation Manual.
VS (encapsulationmode=3bit-transitional) : rate
{1 | 2 } x 64kbps
Megaplex-4
Serial Ports
5-147
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Activating E2E S-Bit
transport
s-bit-signaling {on | off}
Applicable only when encapsulation-mode is
HCM
Define location of the data
channel inside HCM frame
data-position F {0..9} B {0..7}
Applicable only when encapsulation-mode is
hcm.
Selecting the size of the
FIFO buffer used by the
channel (HS-6N/12N only)
fifo-size {auto | 16bit | 30bit |
52bit | 72bit}
In general, you should select auto. The
automatically selected value depends on the
channel data rate:
•
±16 bits for 64 kbps
•
±30 bits for 128 and 192 kbps
•
±52 bits for 256 through 320 kbps
•
±72 bits for 384 through 1536 kbps
•
±52 bits for 1600 through 1792 kbps
•
±30 bits for 1856 and 1920 kbps
•
±16 bits for 1984 kbps.
For special applications that require longer
buffers, you may want to manually select one
of the supported FIFO sizes (±16 bits, ±30
bits, ±52 bits, or ±72 bits)
Selecting the port
transmission mode (HS-RN,
HSU-6/12, LS-6N/LS-12, VS)
mode {sync | async}
HS-RN: this command is irrelevant for
encapsulation-mode=3bit-transitional
Selecting the encapsulation
mode for the VS modules
encapsulation-mode {v110 |
3bit-transitional | none | hcm |
r111}
This parameter defines the serial port
behaviour of VS modules (see diagram in
Megaplex-4 I/O Modules Installation and
Operation Manual, Versatile Modules chapter,
Encapsulation Modes).
Enabling conference
functionality (VS-6/BIN only)
conference
Using no conference disables the conference
functionality.
Setting CTS line to track the
state of the local RTS line
cts-rts
HS-RN, HS-6N/12N, LS-6N/LS-12, VS modules
only
VS: this command is relevant only for v110
and hcm encapsulation modes.
Using no cts-rts sets the CTS line continously
to on.
5-148
Serial Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Configuring end-to-end
control (VS, HS-RN,
HSU-6/12: lt1 mode)
end-to-end-control
When configured, the state of the local RTS
and DTR lines are reflected by the remote
DCD and DSR line, respectively. For HS-RN, do
not use this selection for data rates
exceeding 38.4 kbps.
Using no end-to-end-control disables end-toend control. For HS-RN, always use this
selection for data rates exceeding 38.4 kbps.
When encapsulation-mode=3bit-transitional,
only the state of the local RTS line can be
transmitted end-to-end to the remote DCD
line, but not local DTR to the remote DSR.
The RTS line is functioning as follows:
•
RTS on: traffic flow is established to the
remote equipment, remote DCD on
•
RTS off - 0xC0 code is sent to remote
equipment, remote DCD off
In VS modules, DTR and DSR lines are relevant
only for the following encapsulation modes:
•
v110
•
hcm when s-bit-signaling is on.
In VS modules, for encapsulation-mode=none
this selection is available only for n x 56 kbps
data rates. For n x 64 kbps data rates, see
the next table row.
Configuring end-to-end
control (VS, encapsulationmode=none, n x 64 kbps
data rates, serial port is
cross-connected to E1
uplink with G.732S or
G.732S-CRC framing)
end-to-end-control [rts |
inverse-rts]
This selection is unavailable for VS E1/T1
modules.
When configured, the state of the local RTS
line is reflected by the remote DCD line.
For end user devices using negative logic
interpretation, use inverse-rts setting.
For end user devices using positive logic
interpretation (this is a normal usage case),
use end-to-end-control rts setting or simply
end-to-end-control (rts is set by default).
Using no end-to-end-control disables end-toend control.
Megaplex-4
Serial Ports
5-149
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Configuring end-to-end
control (LS-6N/LS-12)
end-to-end-control {rts | rtsdtr}
rts – the state of the local RTS line is
reflected by the remote DCD line
rts-dtr – the state of the local RTS and DTR
lines are reflected by the remote DCD and
DSR line, respectively
Using no end-to-end-control disables end-toend control (only local support is enabled)
Both channels of a given pair must be
assigned to support the matching control
signals.
Selecting the number of
data bits in the
asynchronous word format
HS-RN, HSU-6/12, HS-S, VS:
data-bits {5 | 6 | 7 | 8}
LS-6N/LS-12: data-bits {6 | 7 |
8 | 9}
HSU-6/12: 5 or 6 data bits are supported only
when the remote equipment is an ASMi-31
using V.110 rate adaptation.
LS-6N/12: The number is equal to the total
number of data and parity bits
HS-RN: this command is irrelevant for
encapsulation-mode=3bit-transitional
VS: this command is relevant only for v110
and hcm encapsulation modes
Controlling the
end-to-end transfer of the
parity bit in the
asynchronous word format
VS, HS-RN: parity
HSU-6/12 (lt1 mode only),
HS-S: parity {odd | even}
Using no parity means that the parity bit is
not transferred
LS-6N/12: Parity is transparently transferred
HS-RN: this command is irrelevant for
encapsulation-mode=3bit-transitional
VS: this command is relevant only for
encapsulation mode=v110
Selecting the number of
stop bits in the
asynchronous word format
(VS, HS-RN, HSU-6/12, lt1
mode only)
stop-bits {1 | 2}
Selecting the multiplexing
and rate adaptation method
supported by the
corresponding HS-U-6/12
port (lt1 mode only)
rate-adaptive {proprietary |
v110}
5-150
Serial Ports
•
proprietary – RAD proprietary method
based on ITU-T Rec. I.460
•
v110 – Multiplexing and rate adaptation in
accordance with ITU-T Rec. V.110
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Selecting the function and
mode of the HS-U-6/12/
HS-S external port
interface {lt | nt | te | lt1}
Selections for HS-U-6/12 are:
•
nt –port operates as a network
termination unit in the “I” mode.
•
lt – port operates as a line termination
unit in the “I” mode.
•
lt1– port operates as a line termination
unit in the “1” mode (used for connection
to NT equipment, such as ASMi-31).
Selections for HS-S are:
Setting the physical
interface type for VS
modules
interface {rs-232 | v35 |
rs-422}
Selects the ISDN activation
mode of an HS-U-6/12 port
configured for operation in
the nt mode
activation-type {1 | 2 | 3}
•
te – terminal mode.
•
nt – network termination mode.
Example
The following section illustrates how to configure serial port 1 on the HS-6N
module installed in slot 5:
•
Data rate 128 kbps.
•
Set CTS line to track the state of the local RTS line
•
Administratively enable the port.
•
Leave all other parameters disabled or at their defaults.
config>port>serial(5/1)# rate 2 x 64kbps
config>port>serial(5/1)# cts-rts
config>port>serial(5/1)# no shutdown
Viewing Status Information
The displayed information is different for different I/O modules. The examples
below relate to VS modules (card type=versatile) and HS-RN modules. For serial
ports of all the other modules only Administrative and operational status and
Loopback Type are displayed.
To view the status of a VS serial port:
1. Navigate to config>port> serial (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
config>port>serial(3/7)# show status
Megaplex-4
Serial Ports
5-151
Chapter 5 Cards and Ports
Installation and Operation Manual
Name
: IO-3 serial 07
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
RTS : High
CTS : High
DCD : High
DTR : Low
DSR : High
The status display provides information about:
Administrative and operational status
Loopback Type – Status of loopback activated on the port (None, Local,
Remote)
State of control signals (High/Low)
When using the HCM encapsulation, the following additional parameters are
displayed in the status screen:
Frame synchronization, local and remote (LOS/In Sync)
SSF – State of local S-bit synchronization (Disabled/LOS/In Sync)
State of remote RTS and DTR control signals (High/Low)
config>port>serial(3/7)# show status
Name
: IO-3 serial 07
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
RTS: High
F Sync
CTS: High
DCD: High
DTR: Low
DSR: High
SSF
: In Sync
Rem F Sync : In Sync
Rem RTS
: In Sync
: High
Rem DTR
: High
To view the status of an HS-RN serial port:
1. Navigate to config>port> serial (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
Name
: IO-1 serial 01
Administrative Status : Up
Operation Status
: Up
HW Type
: HDLC
Loopback Type
: None
The status display provides information about:
5-152
Serial Ports
Administrative and operational status
Loopback Type – Status of loopback activated on the port (None, Local,
Remote)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Module hardware type: HDLC or V.110/3-Bit.
Displaying VS Serial Port Statistics
Serial ports feature RAD proprietary statistical diagnostics. This feature is
available only for VS modules (card type=versatile) and for the following
encapsulation modes:
•
3bit-transitional
•
HCM
•
R.111.
To display the statistics of a serial port:
1. Navigate to config>port> serial> (<slot>/<port>)#
2. Type show statistics.
The statistics is displayed, for example as follows:
# config port serial 3/3
config>port>serial(3/3)# show statistics
DTE Rx Counter
: 609087
DTE Tx Counter
: 0
WAN Rx Violation : 0
Table 5-44. VS Module Serial Port Statistics Parameters
Parameter
Description
DTE Rx Counter
Number of data transitions on the input data wires since last reset or power-up (Rx
from DTE)
DTE Tx Counter
Number of data transitions on the output data wires since last reset or power-up (Tx
to DTE)
WAN Rx Violation
(3-bit transitional
only)
Number of 3-bit transitional protocol code violation since last reset or power-up
HCM F bit errors
(hcm only)
Number of errors in the Framing bit since last reset or power-up
To clear the statistics on a serial port:
1. Navigate to the corresponding port.
2. Enter clear-statistics.
The statistics for the specified port are cleared.
Configuration Errors
The tables below list messages generated by Megaplex-4 when a configuration
error on modules with serial ports is detected.
Megaplex-4
Serial Ports
5-153
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 5-45. HS-12N/HS-6N Configuration Error Messages
Code
Type
Syntax
Meaning
150
Error
FIFO SIZE TOO SMALL
The manually-selected FIFO size must be equal or larger
than the minimum FIFO size required for the selected rate
and link type (E1 or T1)
151
Error
ILLEGAL CHANNELS RATE
COMBINATION
All channels are configured for operation in multiples of
64 kbps or 56 kbps. This error may be caused by:
152
Error
•
Selection of 64K in an odd-numbered channel (e.g.,
channel 1) and 56K in an adjacent channel (e.g.,
channel 2) is not allowed.
•
The total rate of 2 adjacent channels must not
require more than 31 timeslots
CTS SHOULD BE SAME FOR ALL All the channels of the specified module must be
CHANNELS
configured with the same CTS mode
Table 5-46. HS-U-6/12 Configuration Error Messages
Code
Type
Syntax
Meaning
130
Error
CLOCK MODE/CLOCK SOURCE
MISMATCH
The EXT-DCE clock mode cannot be selected when the
port interface is configured as LT-1 (applicable only for
HS-U-6 and HS-U-12 modules)
Table 5-47. VS Configuration Error Messages
Code
Type
Syntax
Meaning
768
Error
PORT ENCAPSULATION MODE
NOT SUPPORTED ON CARD
HCM and R.111 encapsulation modes for serial interface
are not supported in the following modules:
•
VS-6/E1T1 modules
•
VS-G703
•
VS-6-FXS-PW-ACR
•
VS-6-FXO-PW-ACR
•
VS-6-EM-PW-ACR
810
Error
E2E CONTROL /
ENCAPSULATION-MODE
MISMATCH
When serial port encapsulation mode is v110, 3-bittransitional or hcm, end-to-end-control inverse-rts is
illegal (use end-to-end-control rts).
811
Error
E2E CONTROL / XC LINK LINETYPE MISMATCH
When serial port encapsulation mode is none, port rate is
Nx64Kbps and end-to-end-control is enabled, the only
possibility of serial port cross-connect is E1 link with
either g732s or g732s-crc line-type)
Error
PORT RATE / CONFERENCE
MODE MISMATCH
For VS-6/BIN module with encapsulation-mode = 3-bittransitional and conference mode activated, port rate can
be 1x64Kbps only.
817
5-154
Serial Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
818
Error
ILLEGAL PORT RATE FOR
DS0-GROUP SUPPORT
The data rate of the serial port of VS-6/703 and
PW-enhanced VS voice modules protected by DS0-SNCP is
limited to 1792K (28*64 kbps).
819
Error
ILLEGAL CONFERENCE MODE
FOR BOUND PORT
A serial port cannot be bound to a tdm-bridge when it is
set to conference mode.
Testing Serial Ports
The following test and diagnostics functions available on each serial port:
•
Local digital loopback
•
Remote digital loopback
Some additional tests and loopbacks are available for HS-U-6/12 modules working
in “1” Mode in conjunction with remote ASMi-31 modems. For their description,
see HS-U-6 and HS-U-12 Modules section in Megaplex-4 I/O Modules Installation
and Operation Manual.
Local Digital Loopback (Local Loop)
The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
While the loopback is connected, the local serial port should receive its own
signal.
The loopback signal path is shown below.
Megaplex-4
Serial Ports
5-155
Chapter 5 Cards and Ports
Installation and Operation Manual
Channel 1
User or
Test
Equipment
..
...
.
..
..
.
..
..
.
..
..
.
HS-703
HS-703
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-16. Local Loopback, Signal Path
Remote Digital Loopback (Remote Loop)
The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote serial port should receive its own
signal.
The loopback signal path is shown below.
5-156
Serial Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
HS-703
HS-703
C
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-17. Remote Loopback, Signal Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating the Loopbacks
To perform a loopback on the serial port:
3. Navigate to configure port serial <slot>/<port> to select the serial port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.
4. Enter all necessary commands according to the tasks listed below.
Megaplex-4
Serial Ports
5-157
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Activating and configuring the
direction of the loopback
loopback {local | remote}
•
local. Returns the transmitted data
at the physical layer to the
receiving path. The local physical
loopback includes a configurable
timeout mechanism that ends the
loopback operation after a userdefined duration.
•
remote. Returns the received data
at the physical layer to the
transmitting path.
Using no loopback stops the loopback.
5.25 Serial Bundle Ports
Applicable Modules
The serial bundle ports are available only on LS-6N, LS-12 modules. The following
parameters can be configured for the serial bundle ports:
•
Port name
•
Administrative status
•
Setting the port data rate.
Functional Description
See the LS-6N, LS-12 Modules section in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all serial bundle ports disabled. Other parameter
defaults are listed in the table below.
Parameter
Default Value
rate
64kbps
Configuring Serial Bundle Port Parameters
To configure the serial bundle port parameters:
1. Navigate to configure port serial-bundle <slot>/<port> to select the port to
configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
5-158
Serial Bundle Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying the bandwidth
allocated to the
corresponding composite
channel on the Megaplex
uplink
rate {14.4kbps | 32kbps | 56kbps |
64kbps | 128kbps | 192kbps | 256kbps |
384kbps | 512kbps | 768kbps}
Binding external serial ports
that will be carried over this
serial bundle port
(composite channel)
bind serial <slot>
To remove the binding, you must bind this
serial-bundle port to another serial port
Example
The following section illustrates how to configure the serial bundle (internal) port
1 on the LS-12 module installed in slot 6:
•
Data rate 32 kbps.
•
Administratively enable the port.
•
Bind external serial ports 1 and 2 to be carried over this serial bundle port
•
Leave all other parameters disabled or at their defaults.
config# port serial-bundle 6/1
config>port>serial-bundle(6/1)# no shutdown
config>port>serial-bundle(6/1)# bind serial 1
config>port>serial-bundle(6/1)# bind serial 2
config>port>serial-bundle(6/1)# rate 32
config>port>serial-bundle(6/1)# exit
config>port# exit
Configuration Errors
The table below lists messages generated by Megaplex-4 when a configuration
error on modules with serial-bundle ports (LS-6N/LS-12) is detected.
Megaplex-4
Serial Bundle Ports
5-159
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 5-48. LS-6N/LS-12 Configuration Error Messages
Code
Type
Syntax
Meaning
210
Error
BANDWIDTH OVERFLOW
The bandwidth allocated to the internal port of the
LS-6N/LS-12 module must be greater than, or equal to the
sum of the following:
•
The bandwidths allocated to the external ports
•
Management channel, if the remote unit is a KM
working in slave mode
•
Frame synchronization
•
Channel end-to-end control signals (one per pair)
211
Error
SERIAL PORTS NOT IN SAME
RATE GROUP
The two adjacent serial ports (1/2, … 11/12) of an LS-12
module must operate in the same rate group.
212
Error
SERIAL PORTS NOT BOUND TO The two adjacent serial ports (1/2, … 11/12) of an LS-12
SAME SERIAL BUNDLE PORT
module must be bound to same serial bundle port.
213
Error
SERIAL PORT/SERIAL-BUNDLE
PORT RATE MISMATCH
The external port rate is not compatible with the data rate
allocated on the link to the corresponding internal port
214
Error
NO EXTERNAL CHANNEL IS
CONNECTED
The internal port is connected to the link, but no external
port is connected to the internal port
Testing Serial-Bundle Ports
The LS-6N and LS-12 modules feature the test loopbacks on each composite data
stream (serial-bundle port). The test and diagnostics functions available on each
serial-bundle port are:
•
Local digital loopback
•
Remote digital loopback
Composite Data Stream Local Digital Loopback
When a local loop is activated on the Megaplex-4 composite data stream, the
module composite transmit signal is returned to its receive path. As a result, each
individual channel receives its own signal.
The composite transmit signal is still connected to the transmit path and reaches
the LS-6N/12 module installed in the remote Megaplex unit, therefore the remote
equipment does not lose synchronization.
While the loop is connected, all the local users connected to the module must
receive their own signals, and the S.LOSS indicators of the local module must be
off. This loopback provides a quick operational check of the local module. The
loopback signal path is shown in Figure 5-17.
Composite Data Stream Remote Digital Loopback
When a remote composite data stream loopback is activated, the LS-6N/12
module loops back the receive signal toward the remote equipment. The received
signal remains connected as usual to the receive path of the local module, and
5-160
Serial Bundle Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
therefore the local S.LOSS indicates must be off. The loopback signal path is
shown in Figure 5-18.
While the loop is connected, and the link to the remote equipment operates
normally, all the users connected to the remote module must receive their own
signals, and the S.LOSS indicators of the modules must be off.
This loop allows the user to perform a quick operational check of the end-to-end
transmission via this module.
Channel 1
Channel 2
.
.
.
User or
Test
Equipment
.
.
.
Channel 12
.
.
.
.
LS-12
Local Unit
Remote Unit
I/O MODULES
I/O MODULES
LS-12
User or
Test
Equipment
System
Management
Figure 5-18. Composite Local Loopback, Signal Path
Megaplex-4
Serial Bundle Ports
5-161
Chapter 5 Cards and Ports
Installation and Operation Manual
Channel 1
Channel 2
User or
Test
Equipment
.
.
.
.
.
.
Channel 12
.
.
.
.
LS-12
Local Unit
Remote Unit
I/O MODULES
I/O MODULES
LS-12
User or
Test
Equipment
System
Management
Figure 5-19. Composite Remote Loopback, Signal Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to a selectable interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating the Loopbacks
To perform a loopback on the serial-bundle port:
3. Navigate to configure port serial-bundle <slot>/<port> to select the serial
port to configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.
4. Enter all necessary commands according to the tasks listed below.
5.
5-162
Serial Bundle Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Activating and
configuring the
direction of the
loopback
loopback {local | remote}
•
local. Returns the transmitted data
at the physical layer to the
receiving path. The local physical
loopback includes a configurable
timeout mechanism that ends the
loopback operation after a userdefined duration.
•
remote. Returns the received data
at the physical layer to the
transmitting path.
Stopping the loopback
no loopback
5.26 SDH/SONET Ports
Applicable Modules
Megaplex-4 features four SDH/SONET ports (two ports located on each of the
two CL.2 modules). The ports can be ordered either with STM-1/OC-3 or
STM-4/OC-12 interfaces. The panels and terminal identification for the STM-1/OC3 and STM-4/OC-12 versions are identical.
Standards Compliance
The SDH/SONET ports comply with the following standards:
•
SDH: ITU-T G.957, G.783, G.798
•
SONET: GR-253-core.
In particular, framing complies with the following:
•
SDH: ITU-T G.707, G.708, G.709
•
SONET: GR-253-core.
Functional Description
SDH Implementation Principles
This section describes the implementation principles for the Synchronous Digital
Hierarchy (SDH), as a background for the detailed presentation of the SDH signal
structures. In the following explanations, the following terms are used to describe
SDH networks:
•
Megaplex-4
Network node. The SDH network node is a facility at which signals built in
accordance with the SDH frame structure are generated and/or terminated.
Therefore, a network node provides a convenient access point to add or drop
payload signals, e.g., PDH tributary signals, for transmission over the SDH
network.
SDH/SONET Ports
5-163
Chapter 5 Cards and Ports
Installation and Operation Manual
•
SDH transport system. An SDH transport system provides the technical means
to transfer SDH signals between two network nodes.
•
SDH network. An SDH network is formed by interconnecting the required
number of network nodes by means of SDH transport systems.
The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two
principles:
6. Direct synchronous multiplexing of individual tributary signals within the
structure of the higher-rate multiplexed signal.
7. Transparent transporting of each individual tributary signal through the
network, without any disassembly except at the two network nodes that
exchange information through that particular signal.
To enable synchronous multiplexing, SDH equipment is designed to permit
efficient and reliable synchronization of the whole network to a single timing
reference.
Direct Multiplexing Approach
Direct multiplexing means that individual tributary signals can be inserted and
removed into the SDH multiplexed signal without intermediate multiplexing and
demultiplexing steps. This capability results in the following characteristics:
•
Efficient signal transport, as the same SDH transport system can carry various
types of payloads (tributary signals).
•
Flexible routing, because any tributary can be inserted and removed into the
SDH signal as a single unit, without affecting in any way the other tributary
signals carried by the same SDH signal. This permits the user to build
cost-effective add/drop multiplexers, the key component of flexible networks,
instead of implementing digital cross-connect systems as entities separated
from multiplexing equipment.
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore provides the network operator full
control over all the operational aspects of SDH networks and equipment units.
This overhead permits the integration of the network management and
maintenance functions within the transport network itself.
General Structure of SDH Signals
The SDH signal is a serial signal stream with a frame structure. Figure 5-19 shows
the general structure of SDH signals.
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure. Each SDH frame starts with framing bytes, which enable
equipment receiving the SDH data stream to identify the beginning of each
frame. The location of the other bytes within this frame structure is determined
by its position relative to the framing byte.
The organization of the frame can be easily understood by representing the
frame structure as a rectangle comprising boxes arranged in N rows and M
columns, where each box carries one byte. In accordance with this
representation, the framing byte appears in the top left-hand box (the byte
located in row 1, column 1), which by convention is referred to as byte 1 of the
SDH frame.
5-164
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
N x M Bytes
Order of
Transmission
F
F
F
F
F B
B B
B
B
N x M Bytes
1
N Rows
2
Order of
Transmission
B B
B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure 5-20. General Structure of SDH Signals
The frame bytes are transmitted bit by bit, sequentially, starting with those in the
first row (see arrow in Figure 5-19). After the transmission of a row is completed,
the bits in the next lower row are transmitted. The order of transmission within
each row is from left to right. After transmission of the last byte in the frame
(the byte located in row N, column M), the whole sequence repeats - starting
with the framing byte of the following frame.
SDH Frame Organization
As shown in Figure 5-20, an SDH frame comprises two distinct parts:
•
Section Overhead (SOH)
•
Virtual Container (VC).
N Rows
F
Section
Overhead
Path Overhead (One Column)
F
F
F
Virtual Container
(VC)
M Columns
Figure 5-21. SDH Frame Organization
Megaplex-4
SDH/SONET Ports
5-165
Chapter 5 Cards and Ports
Installation and Operation Manual
Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type.
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
Virtual Container (VC)
The VC is an envelope (i.e., a special type of signal structure, or frame) that is
used to transport a tributary signal across the SDH network.
The path followed by a VC within the network may include any number of nodes,
therefore the VC may be transferred from one SDH transport system to another,
many times on its path through the network. Nevertheless, in most cases the VC
is assembled at the point of entry to the SDH network and disassembled only at
the point of exit.
Since the VC is handled as an envelope that is opened only at the path end
points, some of its signal carrying capacity is dedicated to path overhead. The
path overhead provides the facilities (e.g., alarm and performance monitoring),
required to support and maintain the transportation of the VC between the end
points.
VC Assembly/Disassembly Process
The concept of a tributary signal being inserted into a virtual container, to be
transported end-to-end across a SDH network, is fundamental to the operation
of SDH networks. This process of inserting the tributary signal into the proper
locations of a VC is referred to as “mapping”.
In all the SDH signal structures, the carrying capacity provided for each individual
tributary signal is always slightly greater than that required by the tributary rate.
Thus, the mapping process must compensate for this difference. This is achieved
by adding stuffing bytes, e.g., path overhead bytes, to the signal stream as part
of the mapping process. This increases the bit rate of the composite signal to the
rate provided for tributary transport in the SDH structure.
At the point of exit from the SDH network, the tributary signal must be recovered
from the virtual container, by removing the path overhead and stuffing bits. This
process is referred to as “demapping”. After demapping, it is necessary to
restore the original data rate of the recovered tributary data stream.
5-166
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
STM-1 Frame Structure
Figure 5-21 shows the STM-1 frame structure.
2430 Bytes/Frame
155.52 Mbps
9 Rows
F
F
Section
Overhead
Path Overhead (9 Bytes)
Serial Signal
Stream
F
F
STM-1 Virtual Container (VC-4)
Container Capacity = 150.34 Mbps
Payload Capacity = 149.76 Mbps
9 Columns
260 Columns
1 Column
2430 Bytes/Frame x 8 Bits/Byte x 8000 Frames/sec = 155.52 Mbps
Figure 5-22. STM-1 Frame Structure
STM-1 frames are transmitted at a fixed rate of 8000 frames per second.
Note
At a transmission rate of 8000 frames per second, each byte supports a data rate
of 64 kbps.
The STM-1 signal frame comprises 9 rows by 270 columns, resulting in a total
signal capacity of 2430 bytes (19440 bits per frame). Considering the STM-1
frame repetition rate, 8000 frames per second, this yields a bit rate of
155.520 Mbps.
The STM-1 frame comprises the following parts:
•
Section Overhead. The STM-1 section overhead occupies the first nine
columns of the STM-1 frame, for total of 81 bytes.
•
Virtual Container. The remaining 261 columns of the STM-1 frame, which
contain a total of 2349 bytes, are allocated to the virtual container. The
virtual container itself comprises a container for the payload signal (260
columns), preceded by one column of path overhead. The virtual container
carried in an STM-1 frame is referred to as a Virtual Container Level 4, or
VC-4. VC-4, which is transported unchanged across the SDH network,
provides a channel capacity of 150.34 Mbps.
The VC-4 structure includes one column (9 bytes) for the VC-4 path overhead,
leaving 260 columns of signal carrying capacity (149.76 Mbps). This carrying
capacity is sufficient for transporting a 139.264 Mbps tributary signal (the
fourth level in the PDH signal hierarchy). The VC-4 signal carrying capacity can
also be subdivided, to permit the transport of multiple lower-level PDH
signals.
Megaplex-4
SDH/SONET Ports
5-167
Chapter 5 Cards and Ports
Installation and Operation Manual
Pointers
In Figure 5-21, the VC-4 appears to start immediately after the section overhead
part of the STM-1 frame.
Actually, to facilitate efficient multiplexing and cross-connection of signals in the
SDH network, VC-4 structures are allowed to float within the payload part of
STM-1 frames. This means that the VC-4 may begin anywhere within the STM-1
payload part. The result is that in most cases, a given VC-4 begins in one STM-1
frame and ends in the next.
Were the VC-4 not allowed to float, buffers would be required to store the VC-4
data up to the instant it can be inserted in the STM-1 frame. These buffers
(called slip buffers), which are often used in PDH multiplex equipment, introduce
long delays. Moreover, they also cause disruptions in case a slip occurs.
Identifying VC-4 Beginning in the STM-1 Frame
When a VC-4 is assembled into the STM-1 frame, a pointer (byte) located in the
section overhead of the STM-1 frame indicates the location of the first byte (J1)
of the VC-4 that starts in that STM-1 frame.
Using Pointers to Correct Timing Differences
SDH network are intended to operate as synchronous networks. Ideally, this
means that all SDH network nodes should derive their timing signals from a single
master network clock. However, in practical applications, network implementation
must accommodate timing differences (clock offsets). These may be the result of
an SDH node losing network timing reference and operating on its standby clock,
or it may be caused by timing differences at the boundary between two separate
SDH networks.
The VC-4 is allowed to float freely within the space made available for it in the
STM-1 frame, therefore phase adjustments can be made as required between the
VC-4 and the STM-1 frame.
To accommodate timing differences, the VC-4 can be moved (justified), positively
or negatively three bytes at time, with respect to the STM-1 frame. This is
achieved by simply recalculating and updating the pointer value at each SDH
network node. In addition to clock offsets, updating the pointer will also
accommodate any other adjustment required between the input SDH signal rate
and the timing reference of the SDH mode.
Pointer adjustments introduce jitter. Excessive jitter on a tributary signal degrades
signal quality and may cause errors. Therefore, SDH networks must be designed
to permit reliable distribution of timing to minimize the number of pointer
adjustments.
SDH Overhead Data
SDH Overhead Data Types
In SDH networks, a transmission path can include three equipment functions:
•
5-168
SDH terminal multiplexer – which performs the insertion/removal of tributary
signals into SDH frames
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
•
SDH cross-connect switch – permits to change the routing of tributary signals
carried in SDH frames
•
Regenerator – used to increase the physical range of the transmission path.
The resulting structure of an SDH transmission path is shown in Figure 5-22.
Multiplexer
Section
Multiplexer Section
Regenerator
Section
Regenerator
Section
Regenerator
Section
Tributary
Signals
..
.
SDH
Terminal
Multiplexer
Tributary
Signals
..
.
SDH
Terminal
Multiplexer
SDH Cross-Connect
VC
Assembly
VC
Disassembly
Path
Figure 5-23. Structure of Transmission Path in SDH Network
As shown in Figure 5-22, a transmission path can comprise three types of
segments:
•
Multiplexer section – a part of a transmission path located between a
terminal multiplexer and an adjacent SDH cross-connect equipment, or
between two adjacent SDH terminal multiplexers.
•
Regenerator section – a part of a transmission path located between a
terminal multiplexer or SDH cross-connect equipment and the adjacent
regenerator, or between two adjacent regenerators. A multiplexer section can
include up to three regenerator sections.
•
Path – the logical connection between the point at which a tributary signal is
assembled into its virtual container, and the point at which it is disassembled
from the virtual container.
To provide the support and maintenance signals associated with transmission
across each segment, each of these segments is provided with its own overhead
data, hence three types of overhead data:
•
•
Section overhead, carried in the first nine columns of the STM-1 frame:
Multiplexer section (MS) overhead – carried in overhead rows 5 to 9
Regenerator section (RS) overhead – carried in overhead rows 1 to 3
AU pointers– carried in overhead row 4.
Path overhead, carried in the first column of a VC-4. The path overhead
carried in the VC-4 is called high-order path overhead; see the SDH Tributary
Units section for a description of the low-order path overhead.
Figure 5-23 shows the detailed structure of the overhead data in STM-1 frames.
Megaplex-4
SDH/SONET Ports
5-169
Chapter 5 Cards and Ports
Installation and Operation Manual
Path
Overhead
Section Overhead
Framing
A1
Regenerator
Section
Overhead
(Rows 1 - 3)
AU Pointers
(Row 4)
Framing
A1
Framing
A1
Framing
A2
Framing
A2
ID
C1
Path Trace
J1
BIP-8
B1
Orderwire
E1
User
F1
BIP-8
B3
DCC
D1
DCC
D2
DCC
D3
Signal Label
C2
Pointer
H1
Pointer
H2
Pointer
H3
APS
APS
K1
K2
User Channel
F2
DCC
D4
DCC
D5
DCC
D6
Multiframe
H4
DCC
D7
DCC
D8
DCC
D9
Z3
DCC
D10
DCC
D11
DCC
D12
Z4
Orderwire
E2
Z5
BIP-24
B2
Multiplex
Section
Overhead
(Rows 5 - 9)
Framing
A2
B2
Z1
Z1
B2
Z1
Z2
Z2
Z2
Pointer
H3
Pointer
H3
Path Status
G1
Bytes reserved for future use
Figure 5-24. Organization of STM-1 Overhead Data
Regenerator Section Overhead (RSOH)
A regenerator section of an SDH network comprises the transmission medium
and associated equipment between a network element and the adjacent
regenerator, or between two adjacent regenerators. The associated equipment
includes the aggregate interfaces and SDH processing equipment which either
originates or terminates the regenerator section overhead.
The functions of the various bytes carried in the STM-1 regenerator section
overhead are described below.
Framing (A1, A2 Bytes)
The six framing bytes carry the framing pattern, and are used to indicate the start
of an STM-1 frame.
Channel Identifier (C1 Byte)
The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
Parity Check (B1 Byte)
A 8-bit wide bit-interleaved parity (BIP-8) checksum is calculated over all the bits
in the STM-1 frame, to permit error monitoring over the regenerator section. The
computed even-parity checksum is placed in the RSOH of the following STM-1
frame.
5-170
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Data Communication Channel (D1, D2, D3 Bytes)
The 192 kbps Data Communication Channel (DCC) provides the capability to
transfer network management and maintenance information between
regenerator section terminating equipment.
Orderwire Channel (E1 Byte)
The E1 byte is used to provide a local orderwire channel for voice
communications between regenerators and remote terminal locations.
User Communication Channel (F1 byte)
The F1 byte is intended to provide the network operator with a channel that is
terminated at each regenerator location, and can carry proprietary
communications.
The information transmitted on this channel can be passed unmodified through a
regenerator, or can be overwritten by data generated by the regenerator.
AU Pointers (H1, H2, H3 bytes)
The AU (Administration Unit) pointer bytes are used to enable the transfer of
STM-1 frames within STM-N frames, and therefore are processed by multiplexer
section terminating equipment. Separate pointers are provided for each STM-1
frame in an STM-N frame.
AU pointer function is to link between the section overhead and the associated
virtual container(s).
Multiplexer Section Overhead (MSOH)
A multiplexer section of an SDH network comprises the transmission medium,
together with the associated equipment (including regenerators) that provide the
means of transporting information between two consecutive network nodes
(e.g., SDH multiplexers). One of the network nodes originates the multiplexer
section overhead (MSOH) and the other terminates this overhead.
The functions of the various bytes carried in the STM-1 multiplexer section
overhead are described below.
Parity Check (B2 Bytes)
A 24-bit wide bit-interleaved parity (BIP) checksum is calculated over all the bits
in the STM-1 frame (except those in the regenerator section overhead). The
computed checksum is placed in the MSOH of the following STM-1 frame.
Protection Switching (K1, K2 Bytes)
The K1 and K2 bytes carry the information needed to activate/deactivate the
switching between the main and protection paths on a multiplexer section.
Data Communication Channel (D4 to D12 Bytes)
Bytes D4 to D12 provide a 576 kbps data communication channel (DCC) between
multiplexer section termination equipment. This channel is used to carry network
administration and maintenance information.
Megaplex-4
SDH/SONET Ports
5-171
Chapter 5 Cards and Ports
Installation and Operation Manual
Orderwire Channel (E2 Byte)
The E2 byte is used to provide a local orderwire channel for voice
communications between multiplexer section terminating equipment.
Alarm Signals
Alarm information is included as part of the MSOH. These functions are explained
in the SDH Maintenance Signals and Response to Abnormal Conditions section
below.
VC-4 Path Overhead Functions
The path overhead (POH) is contained within the virtual container portion of the
STM-1 frame. The POH data of the VC-4 occupies all the 9 bytes of the first
column. The functions of the various bytes carried in the VC-4 path overhead are
described below.
Path Trace Message (J1 Byte)
The J1 byte is used to repetitively transmit a 64-byte string (message). The
message is transmitted one byte per VC-4 frame.
A unique message is assigned to each path in an SDH network. Therefore, the
path trace message can be used to check continuity between any location on a
transmission path and the path source.
Parity Check (B3 Byte)
An 8-bit wide bit-interleaved parity even checksum, used for error performance
monitoring on the path, is calculated over all the bits of the previous VC-4. The
computed value is placed in the B3 byte.
Signal Label (C2 Byte)
The signal label byte, C2, indicates the structure of the VC-4 container. The signal
label can assume 256 values, however two of these values are of particular
importance:
•
The all “0”s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)
•
The code “00000001” represents the VC-4 equipped state.
Path Status (G1 Byte)
The G1 byte is used to send status and performance monitoring information from
the receive side of the path terminating equipment to the path originating
equipment. This allows the status and performance of a path to be monitored
from either end, or at any point along the path.
Multiframe Indication (H4 byte)
The H4 byte is used as a payload multiframe indicator, to provide support for
complex payload structures, for example payload structures carrying multiple
tributary units (TUs – see the SDH Tributary Units section). If, for example, the TU
overhead is distributed over four TU frames, these four frames form a TU
5-172
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
multiframe structure. The H4 byte then indicates which frame of the TU
multiframe is present in the current VC-4.
User Communication Channel (F2 Byte)
The F2 byte supports a user channel that enables proprietary network operator
communications between path terminating equipment.
Alarm Signals
Alarm and performance information is included as part of the path overhead.
These functions are explained in SDH Maintenance Signals and Response to
Abnormal Conditions section below.
SDH Tributary Units
The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the
transport of a fourth level (139.264 Mbps) PDH multiplex signal.
To enable the transport and switching of lower-rate tributary signals within the
VC-4, several special structures, called Tributary Units (TUs), have been defined.
The characteristics of each TU type have been specifically selected to carry one of
the standardized PDH signal rates. In addition, a fixed number of whole TUs may
be mapped within the container area of a VC-4.
Tributary Unit Frame Structure
The structure of the tributary unit frame is rather similar to the SDH frame
structure. With reference to Figure 5-20, the tributary unit frame also includes a
section overhead part and a virtual container part, which comprises a container
and path overhead.
In general, the tributary unit frame is generated in three steps:
•
A low rate tributary signal is mapped into the TU “container”
•
Low-path path overhead is added before the container, to form the
corresponding virtual container (VC-11, VC-12, VC-2 or VC-3, depending on
the TU type)
•
A TU pointer is added to indicate the beginning of the VC within the TU
frame. This is the only element of TU section overhead.
The TU frame is then multiplexed into a fixed location within the VC-4.
Because of the byte interleaving method, a TU frame structure is distributed over
four consecutive VC-4 frames. It is therefore more accurate to refer to the
structure as a TU multiframe. The phase of the multiframe structure is indicated
by the H4 byte contained in the VC-4 path overhead.
Tributary Unit Types
As mentioned above, specific containers (C), virtual containers (VC) and
associated TU structures have been defined for each standard PDH multiplex
signal level. These structures are explained below:
•
Megaplex-4
TU-11: Each TU-11 frame consists of 27 bytes, structured as 3 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
SDH/SONET Ports
5-173
Chapter 5 Cards and Ports
Installation and Operation Manual
of 1.728 Mbps and will accommodate the mapping of a North American DS1
signal (1.544 Mbps). 84 TU-11s may be multiplexed into the STM-1 VC-4.
•
TU-12: Each TU-12 frame consists of 36 bytes, structured as 4 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 2.304 Mbps and will accommodate the mapping of a CEPT 2.048 Mbps
signal. 63 TU-12s may be multiplexed into the STM-1 VC-4.
•
TU-2: Each TU-2 frame consists of 108 bytes, structured as 12 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 6.912 Mbps and will accommodate the mapping of a North American DS2
signal. 21 TU-2s may be multiplexed into the STM-1 VC-4.
•
TU-3: Each TU-3 frame consists of 774 bytes, structured as 86 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 49.54 Mbps and will accommodate the mapping of a CEPT 34.368 Mbps
signal or a North American 44.768 DS3 signal. Three TU-3s may be
multiplexed into the STM-1 VC-4.
Figure 5-24 illustrates the assembly (multiplexing) of TUs in the VC-4 structure,
for the specific case of the TU-12. For other multiplexing options, see
Figure 5-25.
2430 Bytes/Frame
155.52 Mbps
9 Rows
F
F
Section
Overhead
VC-4 Path Overhead
Serial Signal
Stream
9 Columns
TU-12
No. 1
F
TU-12 No.2
to
TU-12 No.62
F
TU-12
No. 63
260 Columns
1 Column
Figure 5-25. VC-4 Carrying TU-12 Payload
As shown in Figure 5-24, 63 TU-12s can be packed into the 260 columns of
payload capacity (i.e., the C-4 container) provided by a VC-4. This leaves 8
columns in the C-4 container unused. These unused columns result from
intermediate stages in the TU-12 to VC-4 multiplexing process, and are filled by
fixed stuffing bytes.
SDH Multiplexing Hierarchy
Figure 5-25 shows a general view of the SDH multiplexing hierarchy. The
hierarchy illustrates both the European and North American PDH multiplex levels.
Figure 5-25 also shows the utilization of additional SDH signal structures:
•
5-174
TUG: tributary unit group, is the structure generated by combining several
lower level tributaries into the next higher level tributary. For example, TUG-2
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
is generated by combining 3 TU-12 or 4 TU-11, and TUG-3 is generated by
combining 7 TUG-2.
Note
STM-1
(155.520 Mbps)
•
AU: administrative unit, is a structure that includes a VC and a pointer to the
beginning of the VC. For example, AU-3 contains one VC-3 and includes a
pointer to the beginning of the VC.
•
AUG: administrative unit group, is the structure generated by combining
several lower level administrative units into the next higher level
administrative unit. For example, AUG for the STM-1 level is generated by
combining 3 AU-3 (several AUG can be combined for generating STM-N (N =
4, 16, etc.) structures).
For simplicity, reference is made only to VCs (the actual structure needed to
transport a VC can be found from the SDH or SONET multiplexing hierarchy).
×1
×1
AU-4
VC-4
AU-3
VC-3
AUG
C-4
139.264 Mbps
(E4)
×1
×3
44.736 Mbps
(DS3)
×3
VC-3
TU-3
C-3
×7
34.368 Mbps
(E3)
×1
TUG3
TU-2
×1
×7
×2
TUG2
Legend
×4
VC-2
C-2
3.152 Mbps
(DS1C)
VT3
TU-11
VC-11
C-11
1.544 Mbps
(DS1)
TU-12
VC-12
C-12
2.048 Mbps
(E1)
Pointer Processing
×3
Mapping
6.312 Mbps
(DS2)
Figure 5-26. SDH Multiplexing Hierarchy
The flexibility of the SDH multiplexing approach is illustrated by the many paths
that can be used to build the various signal structures. For example, Figure 5-25
shows that the STM-1 signal can be generated by the following multiplexing
paths:
Megaplex-4
•
Each E1 signal is mapped into a VC-12, which is then encapsulated in a TU-12.
•
Each group of 3 TU-12 is combined to obtain a TUG-2 (3 E1 signals per TUG-2.)
•
Seven TUG-2 are combined to obtain one TUG-3 (21 E1 signals per TUG-3).
TUG-3 is carried in a VC-3.
•
Three VC-3 are combined to generate one VC-4 (63 E1 signals per VC-4). The
STM-1 signal carries one VC-4.
SDH/SONET Ports
5-175
Chapter 5 Cards and Ports
Installation and Operation Manual
SDH Maintenance Signals and Response to Abnormal
Conditions
The maintenance signals transmitted within the SDH signal structure are
explained in Table 5-50.
Table 5-49. SDH Maintenance Signal Definitions
Signal
Description
Loss of Signal (LOS)
LOS state entered when received signal level drops below the value at which an
error ratio of 10 is predicted.
-3
LOS state exited when 2 consecutive valid framing patterns are received,
provided that during this time no new LOS condition has been detected
Out of Frame (OOF)
OOF state entered when 4 or 5 consecutive SDH frames are received with invalid
(errored) framing patterns. Maximum OOF detection time is therefore 625 µs.
OOF state exited when 2 consecutive SDH frames are received with valid framing
patterns
Loss of Frame (LOF)
LOF state entered when OOF state exists for up to 3 ms. If OOFs are
intermittent, the timer is not reset to zero until an in-frame state persists
continuously for 0.25 ms.
LOF state exited when an in-frame state exists continuously for 1 to 3 ms
Loss of Pointer (LOP)
LOP state entered when N consecutive invalid pointers are received where N = 8,
9 or 10.
LOP state exited when 3 equal valid pointers or 3 consecutive AIS indications are
received.
Note
Multiplexer Section AIS
The AIS indication is an “all 1’s” pattern in pointer bytes.
Sent by regenerator section terminating equipment (RSTE) to alert downstream
MSTE of detected LOS or LOF state. Indicated by STM signal containing valid
RSOH and a scrambled “all 1’s” pattern in the rest of the frame.
Detected by MSTE when bits 6 to 8 of the received K2 byte are set to “111” for
3 consecutive frames. Removal is detected by MSTE when 3 consecutive frames
are received with a pattern other than “111” in bits 6 to 8 of K2.
Far End Receive Failure
(FERF or MS-FERF)
Sent upstream by multiplexer section terminating equipment (MSTE) within
250 µs of detecting LOS, LOF or MS-AIS on incoming signal. Optionally
transmitted upon detection of excessive BER defect (equivalent BER, based on B2
bytes, exceeds 10 ). Indicated by setting bits 6 to 8 of transmitted K2 byte to
“110”.
-3
Detected by MSTE when bits 6 to 8 of received K2 byte are set to “110” for 3
consecutive frames. Removal is detected by MSTE when 3 consecutive frames are
received with a pattern other than “110” in bits 6 to 8 of K2.
Transmission of MS-AIS overrides MS-FERF
5-176
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Signal
Description
AU Path AIS
Sent by MSTE to alert downstream high order path terminating equipment (HO
PTE) of detected LOP state or received AU Path AIS. Indicated by transmitting “all
1’s” pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when “all 1’s” pattern is received in bytes H1 and H2 for 3
consecutive frames. Removal is detected when 3 consecutive valid AU pointers
are received
High Order Path Remote
Alarm Indication
(HO Path RAI, also known
as HO Path FERF)
Generated by high order path terminating equipment (HO PTE) in response to
received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
POH G1 byte to “1”.
TU Path AIS
Sent downstream to alert low order path terminating equipment (LO PTE) of
detected TU LOP state or received TU path AIS. Indicated by transmitting “all 1’s”
pattern in entire TU-1, TU-2 and TU-3 (i.e., pointer bytes V1-V3, V4 byte, plus all
bytes of associated VC-1, VC-2 and VC-3 loaded by “all 1’s” pattern).
Detected by peer HO PTE when bit 5 of received G1 byte is set to “1” for 10
consecutive frames. Removal detected when peer HO PTE receives 10
consecutive frames with bit 5 of G1 byte set to “0”
Detected by LO PTE when “all 1’s” pattern received in bytes V1 and V2 for 3
consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Note
Low Order Path Remote
Alarm Indication
(LO Path RAI, also known
as LO Path FERF)
TU Path AIS is only available when generating and/or receiving “floating
mode” tributary unit payload structures.
Generated by low order path terminating equipment (LO FTE) in response to
received TU Path AIS. Sent upstream to peer LO PTE.
Indicated by setting bit 8 of LO POH V5 byte to “1”.
Detected by peer LO PTE when bit 8 of received V5 byte is set to “1” or 10
consecutive multiframes. Removal detected when peer LO PTE receives 10
consecutive multiframes with bit 8 of V5 byte set to “0”.
Note
LO Path RAI is only available when generating and/or receiving “floating
mode” tributary unit payload structures.
This section describes the response to the wide range of conditions that can be
detected by the maintenance means built into the SDH frames, and the flow of
alarm and indication signals.
Figure 5-26 provides a graphical representation of the flow of alarm and
indication signals through an SDH transmission path.
Megaplex-4
SDH/SONET Ports
5-177
Chapter 5 Cards and Ports
Installation and Operation Manual
Low Order Path
High Order Path
Multiplexer Section
Regenerator
Section
Regenerator
Section
LO PTE
HO PTE
MS TE
RS TE
MS TE
LOP
HO PTE
LO PTE
LOP
LOP
AIS
(H1H2)
AIS
(V1V2)
LOS
LOF
LOS
LOF
AIS (X2)
Tributary
AIS
FERF
(X2)
RAI
(G1)
RAI (G1)
RAI
(VS)
RAI (VS)
B1(BIP-8)
B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE
(G1)
FEBE
(G1)
BIP-2
(VS)
FEBE
(VS)
FEBE
(VS)
Legend
Collection
Transmission
Generation
LO
HO
Low Order
High Low Order
PTE
RS TE
MS TE
Path Terminating Equipment
Regenerator Section Terminating Equipment
Multiplexer Section Terminating Equipment
Figure 5-27. Flow of Alarm and Indication Signals through an SDH Transmission Path
Flow of Alarm and Response Signals
The major alarm conditions such as Loss of Signal (LOS), Loss of Frame (LOF),
and Loss of Pointer (LOP) cause various types of Alarm Indication Signals (AIS) to
be transmitted downstream.
In response to the detection of an AIS signals, and detection of major receiver
alarm conditions, other alarm signals are sent upstream to warn of trouble
downstream:
5-178
•
Far End Receive Failure (FERF) is sent upstream in the multiplexer overhead
after multiplexer section AIS, or LOS, or LOF has been detected by equipment
terminating in a multiplexer section span;
•
A Remote Alarm Indication (RAI) for a high order path is sent upstream after
a path AIS or LOP condition has been detected by equipment terminating a
path
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
•
Chapter 5 Cards and Ports
A Remote Alarm Indication (RAI) for a low order path is sent upstream after
low order path AIS or LOP condition has been detected by equipment
terminating a low order path.
Performance Monitoring
Performance monitoring at each level in the maintenance hierarchy is based on
the use of the byte interleaved parity (BIP) checksums calculated on a frame by
frame basis. These BIP checksums are sent downstream in the overhead
associated with the regenerator section, multiplexer section and path
maintenance spans.
In response to the detection of errors using the BIP checksums, the equipment
terminating the corresponding path sends upstream Far End Block Error (FEBE)
signals.
SONET Environment
SONET (Synchronous Optical Network) is an alternative standard to SDH, widely
used in North America and other parts of the world. SONET uses similar
implementation principles, and even the frame structures are quite similar to
those used by SDH. Therefore, the following description is based on the
information already presented for SDH.
Figure 5-27 shows the SONET multiplexing hierarchy.
STS-3
(155.520 Mbps)
×1
STS-3
STS-3c
139.264 Mbps
(E4)
×1 STS-3c
SPE
×3
×3
44.736 Mbps
(DS3)
VT6
VT6
SPE
6.312 Mbps
(DS2)
VT3
VT3
SPE
3.152 Mbps
(DS1C)
VT1.5
VT1.5
SPE
1.544 Mbps
(DS1)
VT2
VT2
SPE
2.048 Mbps
(E1)
×1
×2
STS-1
Legend
STS-1
SPE
×7
VT
Group
×4
Pointer Processing
×3
Mapping
Figure 5-28. SONET Multiplexing Hierarchy
The designations of the main signal structures in the SONET hierarchy are as
follows:
Megaplex-4
•
Containers are replaced by Synchronous Payload Envelopes (SPE) for the
various virtual tributaries (VTs)
•
Virtual containers (VCs) are replaced by virtual tributaries (VTs), however the
rates are similar to those used in the SDH hierarchy
SDH/SONET Ports
5-179
Chapter 5 Cards and Ports
Installation and Operation Manual
•
Tributary unit groups (TUGs) are replaced by virtual tributary groups
•
The VC-3 level is replaced by the Synchronous Transport Signal level 1
(STS-1), and has the same rate (51.840 Mbps).
•
3 STS-1 can be combined to obtain one Synchronous Transport Signal level 3
(STS-3) at the same rate as STM-1 (155.520 Mbps). The corresponding
optical line signal is designated OC-3.
SDH/SONET Interfaces
Each CL.2 module has two STM-1/OC-3/STM-4/OC-12 ports. The ports can be
ordered with the following interfaces:
•
STM-1/OC-3:155.52 Mbps ±20 ppm
•
STM-4/OC-12: 622.08 Mbps ±20 ppm
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical. The bit rate for the STM-4/OC-12 version is set by means
of the speed parameter.
The framer operating mode, SDH or SONET, is selected by software configuration.
The two modules must always use the same mode, and therefore selecting the
mode for one module automatically switches the other to the same mode.
Each port has an SFP socket that provides the physical interface. RAD offers a
wide range of SFPs covering requirements from short-range low-cost optical
interfaces to long-range, high-performance interfaces. Optical SFPs are
terminated in LC connectors. RAD also offers SFPs with electrical interfaces for
intra-office applications.
The port interfaces support the enhanced digital diagnostic monitoring interface
per SFF-8472, which enables collecting status and performance data from the
SFPs, as well as alerting if abnormal conditions might cause damage or
performance degradation.
SFPs are hot-swappable, and can be replaced in the field. This enables upgrading
the network port interface characteristics as network topology changes.
Automatic Laser Shutdown
For safety, Megaplex-4 uses automatic laser shutdown (ALS), which protects
against accidental exposure to laser radiation in case of fiber breaks or
disconnections. This is achieved by automatically switching off the transmitter of
an SDH/SONET interface when the receiver of the same interface reports loss of
the optical signal. To enable automatic recovery, the transmitter is periodically
turned back on, for a short time. If the receive signal does not reappear, the
transmitter is turned back off; if the receive signal reappears, the transmitter
remains on (normal operation).
Inband Management Access through SDH/SONET Networks
Figure 5-28 illustrates the inband management access through SDH/SONET
networks. The inband management is done via the Data Communication Channel
(DCC) carried in the SDH/SONET overhead. Each SDH/SONET link can have its DCC
used for management. DCC ports use the host IP address of the Megaplex-4
management subsystem.
5-180
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Note
Chapter 5 Cards and Ports
Inband management can also support more complex topologies, such as rings.
However, this is possible only if the carrier’s SDH/SONET network provides access
to the DCC and enables transparent transfer of user data through the DCC. In this
case, a Telnet host or an SNMP-based network management station connected to
one of the Megaplex-4 units in the network can manage all the other units,
inband.
Typically, the Telnet host or management station is connected to a CL Ethernet
port of the local Megaplex-4 unit. To enable remote management, the
management traffic not addressed to the internal management subsystem of the
Megaplex-4 is also connected by this subsystem to the DCCs carried by the other
SDH/SONET links connected to the Megaplex-4.
At the remote Megaplex-4 units, the management traffic is extracted from the
DCC and connected to the local unit management subsystem. This arrangement
enables the management station to manage each remote
Megaplex-4 unit.
CL
Megaplex-4100
CL
Megaplex-4100
SDH/
SONET
CL
Megaplex-4100
Network
Management
Station
Figure 5-29. Inband Management Access through SDH/SONET Networks
As mentioned above, the inband management traffic is carried in the DCC bytes,
as part of the SDH/SONET overhead. The user can select the DCC bytes to carry
the traffic, which are named differently for SDH and SONET environments.
SDH:
Megaplex-4
•
Regenerator DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
•
Multiplex DCC bytes (D4 to D12), which provide a 576 kbps channel
terminated at SDH multiplex section terminating equipment.
SDH/SONET Ports
5-181
Chapter 5 Cards and Ports
Installation and Operation Manual
SONET:
•
Section DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
•
Line DCC bytes (D4 to D12), which provide a 576 kbps channel terminated at
SDH multiplex section terminating equipment.
You can also select the encapsulation and routing protocols used for inband
management parameters:
•
Two encapsulation options are available: HDLC, or PPP over HDLC in
accordance with RFC1661 and RFC1662.
For compatibility with particular implementations of the HDLC encapsulation
protocol for management purposes, you can select the Type 1 flavor (for this
flavor, the LCP (Link Control Protocol) packets do not include address and
control fields in their overhead).
•
Two options are also available for the management traffic routing protocol:
RAD proprietary protocol. This protocol is sufficient for managing any
RAD equipment and should always be used with HDLC encapsulation.
RIP2: the Megaplex-4 transmits RIP2 routing tables. This permits
standard RIP routers to reach the Megaplex-4 SNMP agent through the
inband (DCC) channel. The RIP2 network is limited to 14 nodes.
SDH/SONET Hierarchy and Allowed Activities
The Megaplex-4 CLI architecture follows the SDH/SONET hierarchy. The kinds of
activities available on each SDH/SONET hierarchical level are listed below:
Activities
SDH/SONET
AUG/OC-3
TUG-3/STS-1
VC-12/VT-1.5
Configuring Port Parameters
v
-
-
-
Assigning VC Profile
-
v
-
-
Activating Loopbacks
v
v
v
v
Displaying Status
v
v
v
v
Displaying Statistics
v
v
v
v
The following sections explain how these activities are performed.
Factory Defaults (SDH/SONET Parameters)
Megaplex-4 is supplied with all SDH/SONET ports enabled. Other parameter
defaults are listed in the table below.
5-182
Parameter
Default Value
frame-type
sdh
speed
155mbps
dcc
disabled
dcc mode
d1-to-d3
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Default Value
dcc routing-protocol
none
dcc deviation
standard
threshold eed
1e-3
threshold sd
1e-6
j0-pathtrace direction
tx
j0-pathtrace padding
nulls
j0-pathtrace string
www.rad.com
rdi-on-failure
enabled
tim-response
enabled
automatic-laser-shutdown
disabled
loopback
disabled
Tx-ssm
enabled
Configuring an SDH/SONET Link
To configure external SDH/SONET parameters:
1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to
port
name <string>
Using no name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Setting the type of operation in
accordance with the SDH or
SONET standards
frame-type {sdh | sonet}
Selecting the SDH/SONET port
speed and operating mode
speed {155mbps | 622mbps}
Enabling DCC inband
management and configuring
DCC parameters: encapsulation
protocol and the DCC bytes used
to carry inband management
traffic
dcc [encapsulation {hdlc |
ppp-o-hdlc | type1}] [mode
{d1-to-d3 | d4-to-d12}]
[routing-protocol
{ none | prop-rip | rip2}]
[deviation {standard | type1}
See Functional Description above for
parameter explanation. Using no dcc
disables inband management
Selecting EED (error rate
degradation) and SD (signal
degrade) thresholds
threshold [eed {1e-3 | 1e-4 |
1e-5}] [sd {1e-6 | 1e-7 | 1e8 | 1e-9}]
If the selected BER value is exceeded,
Megaplex-4 generates the relevant (EED
or SD) alarm
Megaplex-4
155mbps: STM-1 (SDH)/OC-3 (SONET)
622mbps: STM-4 (SDH)/OC-12 (SONET)
See also Configuring Inband Management
in Chapter 8 for important considerations
on selecting the routing protocol.
SDH/SONET Ports
5-183
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Enabling the checking of the
receive/transmit path trace label
by the port and configuring the
optional path trace direction and
padding (when the path label is
shorter than the required length
of 15 characters)
j0-pathtrace [direction { tx |
rx-tx }] [string <path-tracestring> ] [padding {spaces |
nulls }]
Using no j0-pathtrace disables the
checking
Enabling RDI (remote defect
indication) sending in case of
failure
rdi-on-failure
The SDH fault conditions are:
•
LOS (loss of SDH signal)
•
LOF (loss of SDH frame)
•
AIS (alarm indication signal)
Using no rdi-on-failure disables RDI
sending
Enabling the sending of RDI
indications by the port, in case
the received path trace label
(carried in SDH overhead byte
J0) is different from the
expected path trace label
tim-response
Using no tim-response disables sending
of RDI indications
Enabling automatic laser
shutdown of optical laser link on
sync loss
automatic-laser-shutdown
Using no automatic-laser-shutdown
disables automatic shutdown
Defines the administrative unit
group (AUG)
aug <aug number>
This option is valid only when
frame-type=sdh.
Possible values:
•
for speed=155mbps: 1
•
for speed=622mbps: 1 to 4
See also Assigning VC Profiles to
AUG/OC-3 below
Enabling SSM transmission
tx-ssm
Defines an OC-3 connection
oc3 <oc3 number>
This option is valid only when
frame-type=sonet.
Possible values:
•
for speed=155mbps: 1
•
for speed=622mbps: 1 to 4
See also Assigning VC Profiles to
AUG/OC-3 below
5-184
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Configuring collection of
performance management
statistics for this port, which are
presented via the RADview
Performance Management portal
pm-collection interval
<seconds>
You can enable PM statistics collection
for all sdh-sonet ports rather than
enabling it for individual ports. In
addition to enabling PM statistics
collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Example
This example illustrates how to configure an SDH Port with management via DCC
(Dedicated Communication Channel).
1. Program SDH Port 1 in Slot CL-A and configure DCC management with the
following parameters:
Speed: 155 Mbps
DCC encapsulation protocol: HDLC
DCC bytes used to carry inband management traffic: D1 – D3
config>slot# cl-a card-type cl cl2-622gbe
config>port# sdh-sonet cl-a/1 no shutdown
config>port# sdh-sonet cl-a/1 frame-type sdh
config>port# sdh-sonet cl-a/1 speed 155mbps
config>port# sdh-sonet cl-a/1 dcc encapsulation hdlc mode d1to-d3
2. Configure router interface 3, address 10.10.10.9, subnet mask 24
config>router 1 interface 3 address 10.10.10.9/24
3. Bind SDH port 1 on CL-A to router interface 2
config>router# 1 interface 3 bind sdh-sonet cl-a/1
The inband management connectivity via DCC is established.
Assigning VC Profiles to AUG/OC-3
To assign a VC profile to AUG:
1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH port
to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
2. Set frame-type to sdh.
3. Enter the aug command followed by the desired aug number (1 for 155
Mbps, 1 to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> aug(number)# prompt is
displayed.
Megaplex-4
SDH/SONET Ports
5-185
Chapter 5 Cards and Ports
Installation and Operation Manual
4. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning user-defined VC profile
to the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.
Using no vc removes the profile
Before you assign the user-defined
profile, you must use the no vc command
to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement
To assign a VC Profile to OC-3:
5. Navigate to configure port sdh-sonet <slot>/<port> to select the SONET port
to configure.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.
6. Set frame-type to sonet.
7. Enter the oc3 command followed by the desired OC-3 number (1 for
155 Mbps, 1 to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> oc3(number)# prompt is
displayed.
8. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning user-defined VC profile
to the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.
Using no vc removes the profile
Before you assign the user-defined
profile, you must use the no vc command
to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement
Configuration Errors
Table 5-51 lists messages generated by Megaplex-4 when a configuration error is
detected.
Table 5-50. SDH/SONET Configuration Error Messages
Code
Type
Syntax
Meaning
300
Error
TOO MUCH VCS/VTS
The maximum number of virtual containers that can be
used by one virtually concatenated group cannot exceed
63 for VC-12, or 64 for VT1.5
301
Error
MINIMUM NUMBER OF VCs/VTs The minimum number of virtual containers (VC-12 or
IS 2
VT-1.5) in a group is 2
302
Error
VC GROUP IS NOT CONNECTED The virtually concatenated group is not bound to any
other entity. Check and correct
5-186
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
303
Error
DIFFERENT CLS FRAME
STRUCTURE
The two CL modules installed in the Megaplex-4 must use
the same link standards (either SDH or SONET)
305
Error
MISSING E1-I/T1-I SDH-SONET
CROSS CONNECT
An E1-i/T1-i port is opened on CL.2 but not crossconnected to VC/VT on SDH/SONET.
307
Error
ILLEGAL VCG MAPPING
The virtually concatenated group mapping is not correct
309
Error
E1-I/T1-I PORT IS AT
SHUTDOWN
e1-i/t1-i port cannot be cross-connected when it is in
shutdown state. Set the port to no shutdown
311
Error
ILLEGAL BINDING
Pay attention to the following:
312
313
Error
Error
Megaplex-4
ILLEGAL SDH/SONET CROSS
CONNECT
NUMBER OF LIMITED VC-VT XCONNECTS EXCEEDED
•
A VCG and a VC-VT container bound to it must belong
to the same CL module (A or B).
•
A Logical MAC and a GFP/HDLC port bound to it must
belong to the same CL module (A or B).
•
A GFP/HDLC port and a VCG bound to it must belong to
the same CL module (A or B).
•
A GFP/HDLC port defined as “no shutdown” must be
bound to a Logical MAC
•
A VCG port defined as “no shutdown” must be bound
to a GFP/HDLC port.
Pay attention to the following:
•
An E1-i/T1-i port and a VC-VT container crossconnected with it must belong to the same CL module
(A or B).
•
A VCG over N*VC-3 and a VC-12 cannot be mixed on
the same AU-4. If a mix on the same AU-4 is needed,
map the VC-12 on the 1st TUG-3 in this AU-4.
Pay attention to the following:
•
Number of vc-vt containers per CL module is limited
to 252.
•
Number of vc-vt containers for EoS per CL module is
limited to 128.
SDH/SONET Ports
5-187
Chapter 5 Cards and Ports
Installation and Operation Manual
Code
Type
Syntax
Meaning
314
Error
ASSIGNMENT/NUMBER OF VC
MISMATCH
One of the following:
•
Mismatch between the link speed
(155mbps/622mbps) and the number of virtual
containers defined. The numbers should not exceed
the following ranges:
SDH:
<port 1..2>
aug <aug number 1..4> (1 for STM-1)
tug3 <tug3 number 1..3>
vc12 <tug2 number 1..7>
<tributary number 1..3>
SONET:
<port 1..2>
oc3 (<oc3 number 1..4> (1 for OC-3)
sts1 (<sts1 number 1..3>
vt1-5 (<tug2 number 1..7>
<tributary number 1..4>).
•
A VC cannot be bound/cross-connected
simultaneously to multiple sources (VCG port,
E1-i/T1-i port, etc).
315
Error
VCAT NUMBER OF VCs LIMITED The maximum number of virtual containers (VC-12 or VTTO 64
1.5) that can be bound to one VCG cannot exceed 64
316
Error
GFP/HDLC PORT CAN BE
BOUND TO SINGLE VC-VT
ONLY
A GFP or HDLC port of the CL module can be bound only
to a single vc-vt container.
317
Error
VC-PROFILE DOES NOT MATCH
PORT TYPE
The VC profile content does not match the port type.
318
Error
WRONG LCAS PARAMETER
One of the LCAS parameters does not match one of the
VCG parameters.
320
Warning
WTR VALUE WILL BE SET TO
ALL VC-PATH GROUPS
Changing Wait-To-Restore time in VC-PATH groups affects
all other configured VC-PATH groups.
5-188
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
776
Error
INSUFFICIENT BUS BANDWIDTH When SDH/SONET services are activated, the maximum
number of activated TUG-2 ports is 60 for all the I/O
modules. Due to this restriction on PDH bus occupancy,
the maximum number of ports supported on all I/O
modules in the chassis is as follows:
When CL is assembled with SDH/SONET ports, the
communication between CL and I/O modules is over
proprietary PDH links, terminated by SDH/SONET framer
with maximum 60 activated TUG-2 ports. Due to this
restriction on PDH bus occupancy, the maximum number
of ports supported on all I/O modules in the chassis is as
follows:
•
180 E1 ports
•
240 T1 ports
•
180 or 240 DS1 ports depending on the respective
service (E1 or T1).
Viewing SDH/SONET Status Information
For viewing the status of the SDH/SONET hierarchical entities, follow the
instructions below.
To view the status of an SDH/SONET port:
9. Navigate to config>port>sdh-sonet> (<slot>/<port>)#
10. Type show status.
The status is displayed, for example as follows:
config>port>sdh-sonet(cl-a/1)# show status
Name
: CL-A sdh-sonet 01
Administrative Status : Up
Operational Status
: Down
Rx Quality
Tx Quality
Connector Type
: DNU
: SEC
: SFP Out
Trace Message (J0)
---------------------------------------------------------------Received
:
To view the SFP status:
11. Navigate to config>port>sdh-sonet> (<slot>/<port>)#
12. Type show sfp-status.
The SFP status is displayed, for example as follows:
Megaplex-4
SDH/SONET Ports
5-189
Chapter 5 Cards and Ports
Installation and Operation Manual
SFP
--------------------------------------------------------------Connector Type
: LC
Vendor Name
:
Vendor Part Number
: CT-0155TSP-MB5L
Typical Maximum Range (Meter) : 15000
Wave Length (nm)
: 1310
Fiber Type
: SM
RX Power (dBm)
: -50.0 dBm
TX Power (dBm)
: -12.0 dBm
Laser Bias (mA)
: 14.0 mA
Laser Temperature (Celsius) : 47.0 C
Power Supply (V)
: 3.3 V
Note
The last 5 rows are displayed only for SFPs with built-in DDM functionality.
The table below explains the parameters of the SFP installed for selected port.
Table 5-51. Link SFP Parameters
Parameter
Description
Connector Type
Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name
Displays the original manufacturer’s name
Vendor PN
Displays the original vendor’s part number
Typical Max. Range
(Meter)
Displays the maximum range expected to be achieved over typical optical fibers, in
meters
Wave Length (nm)
Displays the nominal operating wavelength of the SFP, in nm
Fiber Type
Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm)
Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm)
Displays the current optical power, in dBm, received by the SFP
Laser Bias (mA)
Displays the measured laser bias current, in mA
Laser Temperature
(Celcius)
Displays the measured laser temperature, in °C
Power Supply (V)
Displays the SFP power supply voltage
To view the status of an AUG-3/OC-3:
13. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4> )#
5-190
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>#
14. Type show status.
The status is displayed, for example as follows:
config>port>sdh-sonet(cl-a/1)>aug(1)# show status
General
-----------------------------------------------------------Expected Trace Message (J1) : www.rad.com
Received Trace Message (J1) : www.rad.com
Expected Signal Label
: 0x1B
Received Signal Label
: 0x1B
Loopback Type
: None
To view the status of a TUG-3/STS-1:
15. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4> )
tug3 (<tug3 number 1..3>)#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>
sts1 (<sts1 number 1..3>) #
16. Type show status.
The status is displayed, for example as follows:
config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)# show status
General
--------------------------------------------------------------Expected Trace Message (J1) : www.rad.com
Received Trace Message (J1) : www.rad.com
Expected Signal Label
: 0x02
Received Signal Label
: 0x02
Loopback Type
: None
To view the status of a VC-12/VT-1.5:
17. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4> )
tug3 (<tug3 number 1..3>)
vc12 (<tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
Megaplex-4
SDH/SONET Ports
5-191
Chapter 5 Cards and Ports
Installation and Operation Manual
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 <oc3 number 1..4>)
sts1 <sts1 number 1..3>)
vt1-5 <tug2 number 1..7>)/ <tributary number 1..4>)#.
18. Type show status.
The status is displayed, for example as follows:
config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)# show
status
General
--------------------------------------------------------------Expected Trace Message (J2) : www.rad.com
Received Trace Message (J2) : www.rad.com
Expected Signal Label
: 0x05
Received Signal Label
: 0x05
Loopback Type
: None
Testing SDH/SONET Ports
Megaplex-4 features remote loopbacks on the SDH/SONET ports of the CL.2
modules, local loopbacks on AUG/OC-3 and TUG-3/STS-1 and remote loopbacks
on AUG/OC-3, TUG-3/STS-1 and VC-12/VT-1.5. The following sections briefly
describe each type of loopback. Table 5-53 shows the paths of the signals when
each loopback is activated.
Table 5-52. SDH/SONET Loopbacks
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
Diagnostic
Function
2
I/O Port
DS1
Cross-Connect
Matrix
..
..
.
..
.
E1/T1
Mapper
VC/VT
Matrix
Framer
Remote
loopback on
SDH/SONET link
Local loopbacks
on AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
5-192
SDH/SONET Ports
SDH/
SONET
Framer
VC/VT
Matrix
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
Diagnostic
Function
2
I/O Port
DS1
Cross-Connect
Matrix
..
..
..
.
.
E1/T1
Mapper
Remote
loopbacks on
AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
VC/VT
Matrix
SDH/
SONET
Framer
VC/VT
Matrix
Remote Loopback on SDH/SONET Link
As shown in Table 5-53, the remote loopback is activated within the network side
circuits of the SDH/SONET framer, and therefore the loopback signal paths
includes all the circuits of the local Megaplex-4 SDH/SONET interface but very few
of the framer circuits.
When the remote loopback is activated, the received SDH/SONET signal is
processed by the receive path of the local Megaplex-4 SDH/SONET interface and
then returned to the input of the transmit path through the framer. Therefore,
when the remote loopback is activated on the external port, the receive signal is
returned to the remote unit. To correct transmission distortions, the returned
signal is regenerated by the SDH/SONET interface circuits.
The remote loopback should be activated at only one of the two units
interconnected by the SDH/SONET link, otherwise an unstable situation occurs.
Local Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5
As shown in Table 5-53, the local loopback is activated within the SDH/SONET VC
cross-connect matrix. When the local loopback is activated, the transmit signal is
returned to the receive path before the output to the SDH/SONET framer, at
different points for each entity.
While the loopback is activated, the equipment mapped to the corresponding
E1-i/T1-i port of the local Megaplex-4 must receive its own signal, and thus it
must be frame-synchronized.
Note
Megaplex-4
The local loopback on VC-12/VT-1.5 is supported for unframed E1/T1 or VC12/VT-1.5 ports mapped to VCG ports. It is not supported for VC-12/VT-1.5 ports
mapped to E1-i/T1-I ports of CL modules.
SDH/SONET Ports
5-193
Chapter 5 Cards and Ports
Installation and Operation Manual
Remote Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5
As shown in Table 5-53, the remote loopback on AUG/OC-3, TUG-3/STS-1, or
VC-12/VT-1.5 is activated within the network side circuits of the VC/VT
cross-connect matrix. Therefore, the loopback signal path includes all the circuits
of the local Megaplex-4 SDH/SONET interface and framer, but very few of the
other circuits.
When the remote loopback is activated, the received SDH/SONET signal is
processed by the receive path of the local Megaplex-4 SDH/SONET interface and
then returned to the input of the transmit path through the framer. Therefore,
when the remote loopback is activated on the external port, the receive signal is
returned to the remote unit.
The remote loopback should be activated only after checking that the equipment
connected at the remote side to the tested unit operates normally during a local
loopback. In this case, the remote unit must receive its own signal, and thus it
must be frame-synchronized. The effect on the ports of the remote unit is mixed,
as explained above for the local loopback.
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to a selectable interval in the range of 1 through 60 minutes.
After the selected interval expires, the loopback is automatically deactivated
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks
To perform a loopback on the SDH/SONET port:
19. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to be tested.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.
20. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating the remote
loopback and setting its
duration (in minutes)
loopback {remote} [duration
<duration in minutes 1..60> ]
Using no loopback remote disables the
loopback
To perform a loopback on the AUG/OC-3 port:
•
5-194
Default (without duration parameter)
is infinite loopback
From the config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4>) or config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>) # context, activate the loopback as follows:
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Activating the local or
remote loopback on this
aug/oc3 port
loopback { remote | local}
Using no loopback followed by the
corresponding command disables the
loopback
To perform a loopback on the TUG-3/STS-1 port:
21. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4>)
tug3 (<tug3 number 1..3>)#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>)
sts1 (<sts1 number 1..3>) #
22. Activate the loopback as follows:
Task
Command
Comments
Activating the local or
remote loopback on this
tug3/sts1
loopback {remote | local}
Using no loopback followed by the
corresponding command disables the
loopback
To perform a loopback on the VC-12/VT-1.5:
23. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>)
sts1 (<sts1 number 1..3>)
vt1-5 (<tug2 number 1..7>)/ <tributary number 1..4>)#.
24. Activate the loopback as follows:
Task
Command
Comments
Activating the remote
loopback on this vc12/vc1-5
loopback remote
Using no loopback remote disables the
loopback
Displaying SDH/SONET Statistics
SDH/SONET ports of Megaplex-4 feature the collection of statistical diagnostics at
different hierarchical levels, per ANSI T1.403.
Megaplex-4
SDH/SONET Ports
5-195
Chapter 5 Cards and Ports
Note
Only locally-terminated entities (AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5) are
monitored by Megaplex-4.
To display the SDH/SONET port statistics:
•
Installation and Operation Manual
At the prompt config>slot>port>sdh-sonet (<slot><port>)#, enter show
statistics followed by parameters listed below.
To display the AUG/OC-3 statistics:
25. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4> )#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4> )#
26. Enter show statistics followed by parameters listed in the table below.
To display the TUG-3/STS-1 statistics:
27. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4>)
tug3 (<tug3 number 1..3>)#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>)
sts1 (<sts1 number 1..3>) #
28. Enter show statistics followed by parameters listed in the table below.
To display the VC-12/VT-1.5 statistics:
29. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>)
sts1 (<sts1 number 1..3>)
vt1-5 (<tug2 number 1..7>)/ (<tributary number 1..4>)#.
30. Enter show statistics followed by parameters listed in the table below.
5-196
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
•
Task
Command
Comments
Displaying statistics
show statistics {all | current}
•
current –Displays the current
statistics
•
all –Displays all statistics: first
current interval statistics, then
statistics for all valid intervals
Displaying statistics
for a specific interval
show statistics interval <interval-num 1..96>
SDH/SONET statistics are displayed. The counters are described in
Table 5-54 and Table 5-55. For example:
Current statistics:
config>port>sdh-sonet(cl-a/1)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 222
Valid Intervals
: 2
ES
: 0
SES
: 0
SEFS
: 0
CV
: 0
Statistics for interval 67:
config>port>sdh-sonet(cl-a/1)# show statistics interval 67
Interval
--------------------------------------------------------------Interval Number : 67
Section ES
: 0
Section SES
: 0
Section SEFS
: 31
Section CV
: 0
All statistics:
config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)# show
statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 712
Valid Intervals
: 1
ES
: 0
SES
: 0
UAS
: 0
CV
: 0
Interval
-------------------------------------------------------------Interval Number : 1
ES
: 3
SES
: 2
UAS
: 57
Megaplex-4
SDH/SONET Ports
5-197
Chapter 5 Cards and Ports
Installation and Operation Manual
CV
: 0
Table 5-53. SDH/SONET Port Statistics Parameters – Current 15-Minute Interval
Parameter
Description
ES
Displays the number of errored seconds in the current 15-minute interval.
An errored second is any second containing one or more of the following types of
errors:
•
•
•
SEFS (UAS)
Severely Errored Frame (SEF) defect (also called Out-of-Frame (OOF) event):
A SEF defect is declared after detection of four contiguous errored frame
alignment words.
The SEF defect is terminated when two contiguous error-free frame words are
detected.
Loss of Signal (LOS) defect:
A LOS defect is declared after no transitions are detected in the incoming line
signal (before descrambling) in an interval of 2.3 to 100 microseconds.
The LOS defect is terminated after a 125-microsecond interval (one frame) in
which no LOS defect is detected.
Loss of Pointer (LOP) defect:
A LOP defect is declared after no valid pointer is detected in eight consecutive
frames. The LOP defect will not be reported while an AIS signal is present.
The LOP defect is terminated after a valid pointer is detected.
•
Alarm Indication Signal (AIS) received in the SDH overhead.
•
Coding Violation (CV): a coding violation is declared when a Bit Interleaved Parity
(BIP) error is detected in the incoming signal. The BIP information is collected using
the B1 byte in the Section Overhead.
Displays the number of unavailable seconds (UAS (SEFS)) in the current interval.
An unavailable second is any second in which one or more SEF defects have been
detected.
SES
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second in which multiple error events of the types taken into
consideration for an ES have occurred.
CV
Displays the number of coding violations (CV) in the current interval.
Time elapsed
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96)
Table 5-54. SDH/SONET Port Statistics Parameters – Selected 15-Minute Interval
Parameter
Description
Section ES
Displays the total number of errored seconds (ES) in the selected interval
Section SES
Displays the total number of severely errored seconds (SES) in the selected interval
Section SEFS
Displays the total number of unavailable seconds (SEFS/UAS) in the selected interval
5-198
SDH/SONET Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Description
Section CV
Displays the total number of code violations (CV) in the selected interval
Interval number
Number of interval for which statistics is displayed
There are two options for clearing SDH/SONET statistics data:
•
Clearing current interval statistics
•
Clearing all statistics, except for the current interval.
To clear the current interval statistics:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
To clear all statistics data except for from the current interval:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-all.
The statistics for the specified entity are cleared.
5.27 SHDSL Ports
Applicable Modules
The SHDSL ports are available on the M8SL, ASMi-54C family and SH-16 I/O
modules.
The ASMi-54C includes three main modules:
•
ASMi-54C/ETH –Ethernet over SHDSL.bis 8-port module with EFM support
•
ASMi-54C/E1/N - E1 over SHDSL 8-Port module
•
ASMi-54C/E1/ETH/N –E1 and Ethernet over SHDSL/SHDSL.bis 8-port module.
•
Note
ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules have the same features for their
SHDSL ports; in this section they are denoted as ASMi-54C/N, to distinguish from
the older ASMi-54C/ETH version. The generic term ASMi-54C is used when the
information is applicable to all of the ASMi-54C models.
•
The SH-16 module includes two main modules:
•
SH-16 –Ethernet over SHDSL/SHDSL.bis 16-port module
•
SH-16/E1 - E1/Ethernet over SHDSL/SHDSL.bis 16-port module
•
Note
In this chapter, the generic term SH-16 is used when the information is applicable
to both SH-16 and SH-16/E1 models. The designation SH-16/E1 is used when
information is applicable only to this model.
•
Megaplex-4
SHDSL Ports
5-199
Chapter 5 Cards and Ports
Installation and Operation Manual
The following table shows the number of SHDSL/SHDSL.bis ports and the features
supported by each Megaplex-4 module. The digits in brackets (1 to 5) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Note
ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules have the same features for their
SHDSL ports; in this section they are denoted as ASMi-54C/N, to distinguish from
the older ASMi-54C/ETH version. The generic term ASMi-54C is used when the
information is applicable to all of the ASMi-54C models.
Table 5-55. Features Supported by Megaplex-4 SHDSL/SHDSL.bis Ports
Feature/
ASMi-
ASMi-54C/E1/N,
Command
54C/ETH
ASMi-54C/E1/ETH/N
STU-C
SH-16
STU-R
Number of
M8SL
STU-C
STU-R
16
16
ports
8
8
8
name
√
√
√
√
√
√
shutdown
√
√
√
√
√
√
far-end-
non-managed
(4)
non-
non-managed or
non-
asmi52 (ASMi-52 or
type
or asmi54
asmi52 (ASMi-52 or
managed or
asmi54 (ASMi-52
managed or
ASMi-52L
(ASMi-54,
ASMi-52L standalone)
asmi54
(E1 or V.35),
asmi54
standalone)
(ASMi-54,
ASMi-54,
(ASMi-54,
asmi52-e1-dte
ASMi-53 or
ASMi-53,
ASMi-53 or
(ASMi-52 standalone
ASMi-54L
ASMi-54L,
ASMi-54L
with E1 and serial
standalone)
ETX-203AM,
standalone)
ports (Mux type))
(R/O)
ETX-2i
(R/O)
standalone)
high-speed-
(ASMi-52 standalone
managed or
mux-serial-
with E1 and LAN
asmi54-eoc
e1 (ASMi-
ports (Mux type))
(ASMi-54L
53
standalone
standalone
configurable via
with E1 and
EOC or ASMi-53
serial ports
standalone)
(Mux type),
high-speed-mux-
4M/4W
ASMi-54L,
ETX-203AM,
ETX-2i
standalone)
managed or
asmi54-eoc
(ASMi-54L
standalone
configurable
via EOC or
ASMi-53)
asmi52-e1-eth (ASMi-52
standalone with E1 and
LAN ports (Mux type))
non-managed or asmi54
(ASMi-54 or ASMi-54L
standalone)
managed or asmi54-eoc
(ASMi-54L standalone
configurable via EOC or
ASMi-53) ,
ASMi-54C/E1/ETH/N
module only)
asmi52-e1-dte (ASMi-52
standalone with E1 and
8
asmi52-e1-eth
asmi52-eth-dte
(ASMi-52 standalone
with serial and LAN
ports (Mux type))
mp-card (M8SL
module installed in
serial-e1 (ASMi-
functionalit
serial ports (Mux type))
53 standalone
y)
high-speed-mux-serial-e1
with E1 and serial
(ASMi-52 or ASMi-53
ports (Mux type),
dxc (equipment from
standalone with E1 and
4M/4W
the
serial ports (Mux type),
functionality)
DXC-8R/10A/30
Megaplex-4 unit)
fcd-ip (FCD-IP device)
family of multiservice
4M/4W functionality)
access nodes
stu
√
√
√
√
√
√
line-prob
√
√
–
√
–
–
5-200
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Feature/
ASMi-
ASMi-54C/E1/N,
Command
54C/ETH
ASMi-54C/E1/ETH/N
Chapter 5 Cards and Ports
SH-16
M8SL
STU-C
STU-R
STU-C
STU-R
√
√
–
√
–
√
tc
√
–(1)
√
√
√
–(1)
wires
√
√
√
√
√
–(2)
power-
√
–
√
√
√
√
√
–
√
√
√
–
√
–
–
√
–
–
√
√
–
√
–
√
√
√
√
√
√
√
clock-mode
–
√
–
–
–
–
remote-
–
√
–
–
–
–
√
√
–
√
–
–
–
–
–
–
–
√
–
√
√
–
√
√
–
–
–
–
–
√
data-ratemaximum
backoff
default
currentmargin
worstmargin
loopattenuation
-threshold
snr-marginthreshold
ch1-ts-num
powerfeeding
tscompaction
-mode
ts0-over-dsl
(3)
remote-crc
(3)
•
1 – HDLC only
2 – 2 wire only
3 – these parameters are configured under e1-i ports
4 – ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules cannot work with a mix of ASMi-54/53 and ASMi-52 modems at the
far end. At every moment, all the remote modems should be either ASMi-54/ ASMi-54L/ASMi-53 or ASMi-52/ ASMi-52L.
Megaplex-4
SHDSL Ports
5-201
Chapter 5 Cards and Ports
Installation and Operation Manual
Standards Compliance
SHDSL and SHDSL.bis ports comply with ITU-T Rec. G.991.2 and ETSI TS 101 524.
Benefits
The SHDSL/SHDSL.bis technology is an efficient method for transmitting
full-duplex data at high rates over a single unloaded and unconditioned twisted
copper pair, of the type used in the local telephone distribution plant. Therefore,
SHDSL provides a cost-effective solution for short-range data transmission and
last-mile applications.
Functional Description
SHDSL has been standardized in ITU-T Rec. G.991.2, and has been extended
beyond the original specifications, which called only for support of rates up to
2.312 Mbps per pair. The current SHDSL.bis version, as standardized in ITU-T Rec.
G.991.2, supports variable payload data rates up to 5.696 Mbps (5.7 Mbps line
rate) on a single unloaded and unconditioned twisted copper pair, of the type
used in the local telephone distribution plant. SHDSL.bis includes an extension,
referred to as M-pair, that enables to bond multiple pairs (up to four) to achieve
variable payload rates up to 22.784 Mbps (22.8 Mbps equivalent line rate).
SHDSL Transmission Subsystem Structure
The basic SHDSL transmission subsystem includes two units interconnected by a
single pair of wires, usually a regular unloaded twisted pair. The pair is used for
duplex transmission.
Two different types of SHDSL units are defined by ITU-T Rec. G.991.2:
•
SHDSL central unit (STU-C), usually located at the network side, at the central
office (CO), which controls the operation of the whole subsystem, supervises
the link setup process and provides the timing reference.
•
SHDSL remote unit (STU-R), which terminates the line at the user side, on the
customer premises (CPE).
This feature is supported by all SHDSL modules.
Note
When the ASMi-54C/ETH module is operating in the STU-R mode, the maximum
number of remote units is two. These units are served by PCS 1 and PCS 5.
When the SH-16 module is operating in the STU-R mode, the maximum number
of remote units is four. These units are served by PCS 1, PCS 5, PCS 9 and PCS 13.
SHDSL Modulation Method
SHDSL uses multi-level pulse-amplitude modulation (PAM) together with trellis
coding. Advanced digital signal processing (DSP) techniques enable symmetric
data transmission at rates of 192 to 2304 kbps (3 to 36 x 64 kbps timeslots), or
5.696 Mbps (up to 89 timeslots) for SHDSL.bis, which corresponds to lines rates
of 200 to 2312 kbps, respectively 5.7 Mbps. The modulation method is spectrally
compatible with other transmission technologies deployed in the access network,
including other DSL technologies.
5-202
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Handling of Timeslot 0
To meet various systems requirements, the user can select the handling method
of timeslot 0 of an E1 stream by each SHDSL port of M8SL and ASMi-54C/N
modules. Two options are available:
•
Terminate (loop back) timeslot 0. This option is available in the basic G.704
mode only.
•
Transfer timeslot 0 transparently through the SHDSL link, down to the E1
port of the unit connected to the remote ASMi-52/ASMi-52L unit. This option
is available in both G.704 framing modes.
The handling method of TS0 is configured by means of ts0-over-dsl parameter.
See also ASMi-54C Modules and M8SL Modules in Megaplex-4 I/O Modules
Installation and Operation Manual, SHDSL Modules Chapter for additional
configuration considerations.
Management via Embedded Operational Channel (EOC)
SH-16, ASMi-54C/ETH and ASMi-54C/E1/ETH/N modules provide an inband
management channel (EOC) for end-to-end system management and supervision
of ASMi-54 and ASMi-53 family of SHDSL/SHDSL.bis modems. SH-16 and
ASMi-54C/E1/ETH/N can also manage ASMi-52 standalone modems with E1 or
V.35 interface. This management channel uses SHDSL overhead bits and operates
without interfering with data transmission.
EOC management can be used to configure unaware flows between the GbE
ports of CL modules and PCS ports of ASMi-54C modules without configuring the
module itself.
Note
Configuring aware flows requires dedicated VLAN management.
To activate EOC management, the far-end equipment (ASMi-54L or ASMi-53
modem) must be defined as managed.
Single IP Management
The ASMi-54L modems (starting from version 2.6 and higher) can be fully
managed via SH-16, ASMi-54C/ETH or ASMi-54C/E1/ETH/N modules installed in
the Megaplex-4 chassis, using RADview with the Single IP solution.
The Single IP solution uses one legal IP address (the Megaplex-4 CL module IP
address) to manage up to 96 standalone units via the chassis. The remote
standalone ASMi-54L/ASMi-53 is assigned a private IP address derived from the
CL.2 IP by an internal algorithm. This solution saves IP addresses on the
Megaplex-4 working with a remote standalone ASMi-54L/ASMi-53 modem.
This IP address is assigned to all the system which includes the Megaplex-4 with
all its CL.2 and ASMi-54C/SH-16 modules and the remote standalone ASMi-54L
units.
If dedicated VLAN management is not configured on an ASMi-54C/SH-16 PCS
port, single IP management is automatically established.
When working in Single IP mode, RADview sends packets to the ASMi-54L using
the Megaplex-4 IP address. The Megaplex-4 CL.2 module works as NAPT router
and routes the management packets to the appropriate entity.
Megaplex-4
SHDSL Ports
5-203
Chapter 5 Cards and Ports
Installation and Operation Manual
Factory Defaults
Megaplex-4 is supplied with all SHDSL ports disabled. Other parameter defaults
are listed in the table below.
Parameter
Default Value
wires
2
tc
64-65-octets
stu
central
far-end-type
none
power-backoff default
0
line-prob
line-prob (enabled)
ts-compaction-mode
no-mapping
data-rate [kbps]
192
loop-attenuation-threshold
0
clock-mode {plesiochronous1 |
plesiochronous2 | synchronous3a }
plesiochronous1
snr-margin-threshold
0
current-margin
0
worst-margin
no worst-margin (disabled)
remote-ch1-ts-num
0
power-feeding
no power-feeding (disabled)
Configuring an SHDSL Port
To configure the SHDSL port parameters:
1. Navigate to configure port shdsl <slot>/<port> to select the SHDSL port to
configure.
The config>port>shdsl>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
3.
Task
Command
Comments
Assigning short description name < name>
to port
Using no name removes the name
Administratively enabling
port
Using shutdown disables the port
5-204
SHDSL Ports
no shutdown
Megaplex-4
Installation and Operation Manual
Task
Command
Specifying number of wires wires {2 | 4 | 8}
for an M-pair group
Chapter 5 Cards and Ports
Comments
In ASMi-54C/ETH and SH-16, the available selections
depend on the tc parameter:
•
tc=64-65-octets: 2/4/8 wires are supported, no
TDM payload
•
tc=hdlc: 2/4 wires and TDM payload are
supported
ASMi-54C/N supports only 2- or 4-wire operation
M8SL supports only 2-wire operation
When SH-16 is working in HDLC mode, only one type
of service (4x2W, 2x4W or 8W) is allowed per each
group of 4 ports (1-4 ,5-8, 9-12, 13-16).
Specifying TC layer and
functional mode
(ASMi-54C/ETH and SH-16
modules)
tc {64-65-octets | hdlc}
Setting the port operation
mode: CO or CPE
stu {central | remote}
All the module ports use the same Transmission
Convergence layer (the last selection is automatically
applied to all the ports)
The selection is done per four lines.
This option is available for M8SL, SH-16 and
ASMi-54C modules when the equipment connected
to the far end of the line is another M8SL, SH-16 or
ASMi-54C module installed in a Megaplex-4.
When a SH-16 modules is operating 2W or 4W as a
CO, it is not recommended to connect the entire
group of 4 ports (1-4, 5-8, 9-12, 13-16) on the CO
module to the entire group of 4 ports on the CPE
module, since short interruption of data may occur
when connecting/disconnecting one of the links.
Specifying the far end
equipment connected to
this SHDSL port
far-end-type {none | asmi52 | To specify far-end equipment for specific SHDSL
asmi52-e1-dte |
modules, consult Table 5-56. Note that nonhigh-speed-mux-serial-e1 |
managed and asmi54 options denote the same
asmi52-e1-eth | asmi52-eth- functionality and are interchangeable. The same
dte | non-managed | asmi54
holds for managed and asmi54-eoc options.
|managed | asmi54-eoc |fcd-ip |For working with far-end-type=high-speed-muxdxc | mp-card}
serial-e1, see the relevant module (ASMi-54C/N or
SH-16/E1) in Megaplex-4 I/O Modules Installation
and Operation Manual, SHDSL Modules Chapter.
Enabling the transmit
power backoff and setting
its value (for SH-16,
ASMi-54C/ETH and M8SL
modules)
power-backoff default <value Possible values are 0 to 31 dbm.
in dbm>
Power backoff is used to reduce the transmit power
below the nominal value specified in the standards:
this reduces interference caused by your signal to
other equipment using pairs in the same cable,
without degrading the link transmission quality.
Values set for STU-C are copied automatically to
STU-R.
Using no power-backoff disables the power backoff
Megaplex-4
SHDSL Ports
5-205
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Controlling the use of line
probing per ITU-T Rec.
G.991.2 for the
corresponding line (to
automatically select the
maximum data rate
supported by the line)
line-prob
This parameter is relevant for ASMi-54C/ETH and
SH-16, only when tc = 64-65-octets.
Using no line-prob disables line probing
When line probing is enabled, either the currentmargin or worst-margin parameter must be enabled
and set
Controlling the mapping of ts-compaction-mode {nothe connected E1 port
mapping | low-ts-mapping}
timeslots into the SHDSL
frames
This parameter is relevant only for M8SL when far
end device is MP card, FCD-IP, or DXC.
no-mapping – The connected timeslots of the E1
frame are placed in the SHDSL frame in consecutive
timeslots, in ascending order.
when a new E1 timeslot, lower than the timeslots
already connected, is added, the timeslots with
higher numbers must be moved (reassigned): this
results in a brief interruption of data transfer for the
moved timeslots.
low-ts-mapping – The first two timeslots of the
SHDSL frame are reserved for the signaling timeslot
(timeslot 16) and the dedicated management
timeslot. The payload starts from the third timeslot,
and is inserted in consecutive timeslots according to
the E1 frame order.
This ensures that the signaling and dedicated
timeslots will continue to function even when new
timeslots are connected in the E1 frame. Service
interruption might still occur when timeslots are
moved, but in this case only data timeslots are
moved.
When the far end device is an ASMi-52/ASMi-52L,
no-mapping is automatically used.
Setting the SHDSL port
data rate (line payload
rate)
data-rate maximum [rate in
kbps]
In ASMi-54C/ETH and SH-16, this parameter is
relevant only when line probing is disabled (no lineprob).
For available selections, see the respective SHDSL
Data Rate tables in Chapter 7 of the Megaplex-4 I/O
Modules Installation and Operation Manual.
Selecting the loop
attenuation threshold in
db
loop-attenuation-threshold
<value in dbm>
The range is 0 to 127 (the number specifies the
maximum value, in dB).
If the attenuation measured on the SHDSL link
exceeds the threshold value, an alarm is generated.
Selecting clock
clock-mode {plesiochronous1 | Not for ASMi-54C/ETH
synchronization mode in
plesiochronous2 |
In plesyncronous1 clock mode, short interruption of
accordance with the SHDSL synchronous3a}
data may occur when connecting/disconnecting one
bit rates available in
of the links. This limitation is relevant for 2W/4W
remote devices
operation only.
5-206
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Selecting the SNR margin
threshold in db
snr-margin-threshold <value in The range is 0 to 15 (the number specifies the
db>
maximum value, in dB).
If the attenuation measured on the SHDSL link
exceeds the specified value, an alarm is generated.
Specifying the target
margin for the measured
signal-to-noise ratio
relative to the current
noise level
current-margin <value in db>
This parameter is relevant for SH-16 and
ASMi-54C/ETH modules only, when line probing is
enabled.
The range is -10 db to +21 dB).
Values set for STU-C are copied automatically to
STU-R.
Using no current-margin disables the use of the
signal-to-noise ratio measured relative to the
current noise level.
Alternatively, line activation may be performed in
accordance with the Worst Margin value.
Specifying the target
worst-margin <value in db>
margin for the measured
signal-to-noise ratio
relative to the reference
worst-case near-end
crosstalk noise specified in
ITU-T Rec. G.991.2
This parameter is relevant for ASMi-54C/ETH and
SH-16 only, when line probing is enabled.
The range is -10 db to +21 dB.
Values set for STU-C are copied automatically to
STU-R.
Using no worst-margin disables the use of the
signal-to-noise ratio measured measured relative to
crosstalk.
Alternatively, line activation may be performed in
accordance with the Current Margin value.
The available selections are 0 to 31.
Setting the number of
timeslots connected to
CH1 (E1) on the remote
modem
remote-ch1-ts-num <value>
Activating power feeding
to this SHDSL line
power-feeding {local |forward} local – provides power feeding only to the nearest
repeater
This parameter is relevant only for ASMi-54C/N
when the remote modem is ASMi-52/ASMi-52L MUX
type
forward – provides power feeding to the nearest
repeater and forwards it also to the next one (this
feature is available only for RAD’s S-RPT/EFM
repeaters)
Using no power-feeding disables the power feeding
of this line.
This command is not available for a module working
in STU-R mode.
See also Megaplex-4 I/O Modules Installation and
Operation Manual, SHDSL Modules Chapter, Working
with Power Feeding, in ASMi-54C Modules and SH-16
Modules sections.
Megaplex-4
SHDSL Ports
5-207
Chapter 5 Cards and Ports
Installation and Operation Manual
To verify the SHDSL port parameters:
•
At the config>port>shdsl>(<slot>/<port>)# prompt, type info detail.
The configured SHDSL port parameters are displayed.
For example:
config>port>shdsl(2/1)# info detail
name "IO-2 shdsl 01"
far-end-type managed
wires 4
stu central
power-backoff default 0
power-feeding local
data-rate maximum 5632
loop-attenuation-threshold 0
snr-margin-threshold 0
clock-mode plesiochronous1
no shutdown
Displaying the Status of SHDSL Port and Repeaters
You can display the status and configuration of an individual SHDSL port. If
relevant, the display also shows the number and parameters of SHDSL repeaters
installed in the line. For each repeater and wire, the values of SNR Margin (db)
and Loop Attenuation (db) are displayed on the Network and Customer sides.
To display status of an SHDSL port:
•
At the prompt config>port>shdsl(<slot/port)#, enter show status.
The SHDSL port status parameters are displayed.
Note
The possible status values are interpreted as follows:
•
ON – Power feeding is connected
•
OFF – Power feeding is disconnected
•
Failure – Current overload or failure on the line
•
N/A – Power feeding is not relevant for this module
config>port>shdsl(8/1)# show status
Administrative Status : Up
Operation Status
: Up
Interface Type
: STU-C
Far-End-Device-Type : MP-card
Loopback Type
: None
Wires
: 4
Transmission Mode
: B-G
Line Rate (Kbps)
: 1552
HW Type
: shdsl
Number Of repeaters
: 1
Wires
---------------------------------------------------------------------5-208
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
State
SNR
Loop
Power
Power
Margin
Attenuation
Backoff
Feeding
(db)
(db)
---------------------------------------------------------------------Data
23
0
6
ON
Repeater Number
: 1
Repeater Side
: Customer
Wire Num
: 1
SNR Margin (db)
: 23
Loop Attenuation (db) : 0
Loopback Type
: Remote
2
23
0
Network
1
24
0
2
24
0
Testing SHDSL Ports
The SHDSL ports of the M8SL modules feature the following loopbacks, which can
be independently activated for each port:
•
Local loopback
•
Remote loopback.
• In addition, the M8SL module features a remote loopback on remote ASMi-52
or ASMi-52L unit.
• The SHDSL ports of the ASMi-54C/N and SH-16 modules feature the remote
loopback on remote unit, which can be independently activated for each port.
•
The ASMi-54C/ETH module does not support loopbacks on its SHDSL ports.
Local Port Loopback (M8SL only)
The local port loopback is used to test the path of the signals intended for
transmission through a selected SHDSL port: this path starts at the other port(s)
within the same Megaplex-4 chassis that are connected to the selected port,
passes through the CL module, and continues up to the SHDSL modem serving
the port. Within the tested I/O module, the path includes most of the SHDSL
modem circuits serving the selected port, and the operation of the routing
circuits that handle the port signals within the module.
A typical local port loopback signal path is shown in Figure 5-29.
As shown in Figure 5-29, when a local loopback is activated on one of the module
ports, the transmit signal is returned to the input of the same port receive path,
at a point just before the line interface. The local port must receive its own
signal, and thus it must be frame-synchronized.
Note
During local port loopback, the remote equipment does not receive a valid SHDSL
signal, and therefore it loses synchronization. This is normal, and does not
indicate a problem.
After the local loopback is deactivated, the SHDSL subsystem must synchronize
again, and therefore you will see the sequence of port synchronization
indications at both the local and the remote ports.
Megaplex-4
SHDSL Ports
5-209
Chapter 5 Cards and Ports
Installation and Operation Manual
In addition, each I/O module connected to the corresponding port must also
receive its own signal: in general, the result is that these modules are
synchronized and do not generate alarm indications. However modules that
cannot receive their own signal (for example modules with Ethernet interfaces)
enter an alarm state while a local loopback is activated.
Megaplex-4100
CL
M8SL
Port 1
Other Port
Interface
Routing
Matrix
.
..
.
.
Bus
Interface
.
..
.
..
.
Port 8
Figure 5-30. Local Port Loopback Signal Path
Remote Port Loopback (M8SL only)
The remote port loopback is used to test the SHDSL modem circuits of a selected
SHDSL external port. This test also checks the transmission plant connecting the
remote equipment to the corresponding port of the I/O module.
A typical remote port loopback signal path is shown in Figure 5-30.
Megaplex-4100
CL
M8SL
Port 1
Other Port
Interface
Routing
Matrix
Bus
Interface
..
..
.
..
..
..
.
Port 8
Figure 5-31. Remote Port Loopback Signal Path
When a remote loopback is activated on one of the SHDSL ports, the SHDSL
modem serving that port returns the received signal toward the remote unit, via
the transmit path. The received signal remains connected as usual to the receive
path of the corresponding port. To correct transmission distortions, the returned
signal is fully regenerated by the SHDSL modem circuits.
The remote loopback should be activated only after checking that the remote unit
operates normally with local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
5-210
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
If the local Megaplex-4 unit operates normally with the local port loopback, then
while the remote loopback is connected the local unit should receive a valid
signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the two Megaplex-4
connected in a link, otherwise an unstable situation occurs.
Remote Loopback on Remote Unit
The remote loopback on remote unit is relevant for M8SL, SH-16 and ASMi-54C/N
SHDSL ports connected to remote modems. This loopback is used to test all the
circuits of the corresponding module port, the line to the remote unit, and the
operation of the remote unit.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
The loopback is activated within the user interface of the remote modem, which
returns the received data through the transmit path.
Figure 5-31 shows the signal paths of a typical remote loopback on the remote
ASMi-52/ASMi-52L.
Megaplex-4100
CL
M8SL
Routing
Matrix
Other Port
Interface
ASMi-52
Port 1
..
..
.
Bus
Interface
..
.
..
.
..
Remote
Loopback
Port 8
Figure 5-32. Remote Loopback on Remote Unit, Signal Paths
Activating SHDSL Loopbacks
You can activate a loopback on an SHDSL port or on one of the repeaters
operating on its line. Repeaters feature only remote loopbacks with infinite
duration. For the PCS loopback, see Testing PCS Ports.
To perform a loopback on the SHDSL port:
4. Navigate to configure port shdsl <slot>/<port> to select the SHDSL port to
configure.
The config>port>shdsl>(<slot>/<port>)# prompt is displayed.
5. Enter all necessary commands according to the tasks listed below.
Megaplex-4
SHDSL Ports
5-211
Chapter 5 Cards and Ports
Warning
Installation and Operation Manual
Before activating the remote-on-remote loopback on an SHDSL port, be aware
that if Ethernet services are being provided by the system, the traffic passing
through the SHDSL port will be looped. Take appropriate care to prevent this
scenario. Do not activate this loop when the system is connected to the live
network.
Task
Command
Setting loopback duration
and activating the
corresponding loopback on
this port
loopback {local | remote | remote-on- Local and remote loopbacks are available
remote } [ duration <duration in
for M8SL modules only.
minutes 1..30> ]
Using no loopback disables the loopback
Comments
To perform a loopback on an SHDSL repeater:
6. Navigate to configure port shdsl <slot>/<port>)repeater (repeater ID)#, to
select the repeater.
The config>port>shdsl (<slot>/<port>)repeater (repeater ID)# prompt is
displayed.
7. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating the remote
loopback on the repeater
loopback remote
Using no loopback remote disables the
loopback
Configuration Errors
The following tables list messages generated by Megaplex-4 when a configuration
error on SHDSL modules is detected.
Table 5-56. ASMi-54C and SH-16 Configuration Error Messages
Code
Type
Syntax
Meaning
510
Error
INCORRECT SHDSL LINES IN
PCS
When the configured TC Layer is 64/65-Octets, the wrong
combination of SHDSL lines is used in a PCS
511
Error
SHDSL ADMIN IS NOT
CONNECTED
One of the SHDSL lines is in “shutdown” state
512
Error
ILLEGAL SHDSL RATE
The selected SHDSL rate is not compatible with the
selected operating mode
513
Error
NOT IDENTICAL SHDSL
DEFINITION
When the Wire parameter of an SHDSL line is configured
to 4W or 8W, all the parameters of the corresponding
SHDSL wire pairs must be identical
514
Error
ILLEGAL PCS DEFINITION FOR
STU-R
When the STU side is configured as the Remote, and the
TC Layer is 64/65 Octets, the only PCS and SHDSL line
combinations allowed are as follows:
5-212
SHDSL Ports
•
PCS 1 can bound to SHDSL lines 1, or 1,2, or 1,2,3,4
•
PCS 5 can bound to SHDSL lines 5, or 5,6, or 5,6,7,8
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
515
Error
NOT IDENTICAL LINE PROBE
DEFINITION
When the STU side is configured as the Remote, Line
Probe (line-prob) must be enabled
516
Error
NOT IDENTICAL WIRE NUMBER
DEFINITION
When the TC Layer is 64/65-Octets, the wires parameter
must be set to 2W
517
Error
AT LEAST ONE MARGIN MUST
BE SET
When line probing is enabled, either the current-margin or
worst-margin parameter must be enabled and set
518
Error
ILLEGAL SHDSL DEFINITION
FOR STU-R
When the STU side is configured as the Remote, and the
TC Layer is HDLC, only SHDSL lines 1 and 5 can be set to
4W or 8W.
519
Error
ILLEGAL NUMBER OF WIRE
COMBINATION
When the TC Layer is HDLC, the wires parameter of the
SHDSL lines must be configured according to Supported
Lines versus Wires Parameter table in ASMi-54C module
section of Megaplex-4 I/O Modules Installation and
Operation Manual, SHDSL Modules Chapter.
520
Error
ILLEGAL E1-i DEFINITION
When the TC Layer is HDLC, the E1-i port is configured to
“no shutdown” and the corresponding SHDSL line to
“shutdown” (make sure that only the allowed e1-i ports
are set to “no shutdown”).
When the TC Layer is 64/65 Octets, one of the e1-i ports
is set to “no shutdown”
521
Error
STU-MODE MUST BE THE SAME The STU parameter of all the SHDSL lines in a module
IN ALL LINES
must be set to same value
522
Error
TC-LAYER MUST BE THE SAME
IN ALL LINES
The TC Layer parameter of all the SHDSL lines in a module
must be set to same value
524
Error
TS0 MODE DOESN'T FIT TO
LINE TYPE
Contradiction between TS0 mode and line type
525
Error
FE TYPE MUST BE THE SAME IN Far-end-type parameter must be set to the same value for
ALL LINES
all SHDSL ports (not for SH-16).
526
Error
ILLEGAL PCS BINDING
When working in 4W/8W mode, some PCS ports cannot be
bound to some SHDSL ports. For allowed binding, see
Supported Ports versus Wires Parameter table in
Megaplex-4 I/O Modules Installation and Operation
Manual, SHDSL Modules Chapter.
527
Error
ILLEGAL PARAM VALUE FOR
E1-I PORT
When far-end-type=high-speed-mux-serial-e1, the
following combinations (either of them) at the
corresponding e1-i port are illegal:
•
inband-management is activated
•
wires=4 + line-type=g732n + ts0-over-dsl = yes
•
wires=4 + line-type=unframed + ts0-over-dsl = no.
If one of these statements is true, modify the
corresponding settings.
528
Error
Megaplex-4
UNUSED E1-I PORT IS
CONNECTED
Even E1-i ports cannot be connected when working in 4W
mode.
SHDSL Ports
5-213
Chapter 5 Cards and Ports
Installation and Operation Manual
Code
Type
Syntax
Meaning
529
Warning
FAR-END CHANGED, DEVICE
WILL RESTART
When far-end-type=high-speed-mux-serial-e1 is selected
instead of another far-end-type setting, both the
ASMi-54C module and the remote modem will be
automatically restarted (SH-16 module will not restart).
530
Error
DATA RATE EXCEEDS MAXIMAL The data rate configured for SHDSL port exceeds the
RATE
maximum rate (see SH-16 SHDSL Data Rates and
ASMi-54C SHDSL Data Rates tables in Chapter 7 of the
Megaplex-4 Modules Installation and Operation Manual).
531
Error
DATA RATE NOT SUPPORTED
For 4W/HDLC operation, rates 17024 to 18432 kbps are
unavailable.
532
Error
ILLEGAL REMOTE CH1 TS
NUM
The number of timeslots connected to CH1 (E1) on the
remote modem (remote-ch1-ts-num) exceeds the number
of open timeslots (not for SH-16).
533
Error
CL-DS0/HIGH-SPEED-MUXSERIAL-E1 NOT SUPPORTED"
Far-end-type=high-speed-mux-serial-e1 is not supported
when CL.2 type is DS0 only.
534
Error
POWER FEEDING MUST BE THE When 2 lines are bonded together, power feeding must be
SAME IN SHDSL LINES
either On or Off for both lines.
536
Error
STU-C MODE CAN'T BE
SELECTED AS CLOCK SOURCE
A port configured in STU-C mode cannot be selected as a
clock source
537
Error
ILLEGAL_FAR_END_TYPE_FOR
STU-R MODE
For a port working in STU-R mode, far-end-type can be
only “non-managed”.
538
Error
ILLEGAL_PARAMETER_FOR
TC_LAYER_64-65 OCTET
When working with tc=64-65-octets, the following
parameters cannot be configured (SH-16 only):
•
far-end-type= high-speed-mux-serial-e1
•
clock-mode=plesiochronous1
Table 5-57. M8SL Configuration Error Messages
Code
Type
Syntax
Meaning
220
Error
RATE/TS ASSIGNMENT
MISMATCH
The line rate configured for the M8SL port must match the
number of timeslots assigned
221
Error
CLOCK REFERENCE PORT
SHOULD BE SET STU-R
The M8SL port configured as clock reference must be
configured as STU-R
222
Error
MAX BANDWIDTH MISMATCH
Maximum bandwidth configured on the SHDSL line must
match the number of timeslots assigned
Displaying SHDSL Port Statistics
You can display statistics for the SHDSL ports of all kinds of ASMi-54C, SH-16 and
M8SL modules.
5-214
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To display the SHDSL port statistics:
At the prompt config>slot>port>shdsl (<slot>/<port>)#, enter show statistics
followed by parameters listed below. <wire-num> specifies the number of the
SHDSL interface wire for which the statistics is displayed.
Note
Day statistics (all types) are supported only for ASMi-54C/ETH and SH-16, other
statistic types are supported by all SHDSL modules.
Task
Command
Comments
Displaying
statistics
show statistics <wire-num> {all | all-intervals | alldays-interval | current | current-day}
All SHDSL modules:
•
current - current statistics (up to
15 min)
•
all-intervals - all intervals during
the last 24 hours
Additional statistics (ASM-54C/ETH
and SH-16 modules only):
•
current-day - current today's
statistics
•
all-days-interval - all intervals
during the last 7 days
•
all - current, all-intervals,
current-day, all-days-interval
Displaying
statistics for a
specific 15-min
interval
show statistics <wire-num> interval <interval-num
1..96>
All SHDSL modules
Displaying
statistics for a
selected day
show statistics <wire-num> day <day-num 1..7>
ASMi-54C/ETH only
SHDSL port statistics are displayed. For example:
Current Statistics for Wire 1 (all modules):
config>port>shdsl(4/2)# show statistics 1 current
Wire Num : 1
Current
--------------------------------------------------------------Time Elapsed (Sec) : 388
Valid Intervals
: 0
ES
: 0
LOSWS
: 0
SES
: 0
CRC Anomalies : 0
UAS
: 0
Statistics for Interval 1, Wire 1 (all modules):
config>port>shdsl(4/2)# show statistics 1 interval 1
Wire Num : 1
Interval
--------------------------------------------------------------Interval Number : 1
Megaplex-4
SHDSL Ports
5-215
Chapter 5 Cards and Ports
Installation and Operation Manual
ES
: 0
SES
UAS
: 395
: 395
LOSWS
CRC Anomalies
: 1
: 0
Current Day Statistics for Wire 1 (ASMi-54C/ETH):
config>port>shdsl(4/2)# show statistics 1 current-day
Wire Num : 1
Current Day
--------------------------------------------------------------Time Elapsed (Sec) : 3115
Valid Days
: 0
ES
: 0
LOSWS
: 11
SES
: 1163
CRC Anomalies : 0
UAS
: 1163
Statistics for Day 1, Wire 1 (ASMi-54C/ETH):
config>port>shdsl(4/2)# show statistics 1 day 1
Wire Num : 1
Day Interval
--------------------------------------------------------------Day Number : 1
ES
: 0
LOSWS
: 1
SES
: 395
CRC Anomalies
: 0
UAS
: 395
The counters are described in the table below.
Table 5-58. SHDSL Statistics Parameters
Parameter
Description
Time elapsed (for current
interval)
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds
Time elapsed (for current
day, ASMi-54C/ETH only)
The elapsed time (in seconds) since the beginning of the current day, in
seconds. The range is 1 to 8640 seconds
Interval number
Number of interval for which statistics are displayed
Note: The sequence of intervals is different for the SHDSL ports of different
modules:
•
For the M8SL and ASMi-54C/N modules, Interval #1 is the latest in time
•
For the ASMi-54C/ETH modules, Interval #1 is the earliest in time.
Day number
Number of day for which statistics are displayed (ASMi-54C/ETH only)
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics can be
displayed, in addition to the current (not finished) interval (up to 96)
Valid days
The number of elapsed finished days (24 hours) for which statistics can be
displayed, in addition to the current (not finished) day (up to 7)
(ASMi-54C/ETH only)
5-216
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Description
ES
The number of errored SHDSL seconds (ES) in the current/selected
interval/day/week.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared
UAS
The number of unavailable SHDSL seconds (UAS) in the current/selected
interval/day/week.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The
SHDSL line becomes unavailable at the onset of 10 contiguous SESs (the 10
SESs are included in the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10
contiguous seconds with no SESs (the 10 seconds with no SESs are excluded
from the unavailable time)
SES
The number of severely errored SHDSL seconds (SES) in the current/selected
interval/day/week.
The SHDSL SES is any second which is not declared a UAS, during which at
least 50 CRC anomalies are declared, or one or more LOSW defects are
declared
CRC Anomalies
The number of CRC anomalies in the current/selected interval/day/week.
A CRC anomaly is declared when the CRC bits generated locally on the data in
the received SHDSL frame do not match the CRC bits (crc1 - crc6) received
from the transmitter. A CRC anomaly only pertains to the frame over which it
was declared.
LOSWS
Displays the number of SHDSL LOSW seconds (LOSWS) in the
current/selected interval/day/week.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW
defects are declared
Displaying SHDSL Repeater Statistics
You can display statistics for the SHDSL repeaters working in line with
ASMi-54C/N modules.
To display the SHDSL repeater statistics:
At the prompt config>port>shdsl (<slot>/<port>) repeater (repeater ID)#, enter
show statistics running.
SHDSL statistics are displayed separately for each repeater and each wire
on the customer and the network side. The number of columns depends
on number of wire-pairs configured in the line menu. The statistics are
accumulated since the corresponding SHDSL port of the ASMi-54C/N
module is on.
For example:
config>port>shdsl(2/5)# repeater 1
config>port>shdsl(2/5)>repeater(1)# show statistics running
Repeater Side : Customer
Network
Wire Num
: 1
2
1
2
Megaplex-4
SHDSL Ports
5-217
Chapter 5 Cards and Ports
Installation and Operation Manual
ES
: 4
SES
: 0
UAS
: 248
LOSWS
: 248
CRC Anomalies : 19
4
0
248
248
19
0
0
47
47
0
0
0
47
47
0
The counters are described in the table below.
Table 5-59. SHDSL Repeater Statistics Parameters
Parameter
Description
ES
The number of errored SHDSL seconds (ES) accumulated since the module is
on.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared
UAS
The number of unavailable SHDSL seconds (UAS) accumulated since the
module is on.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The
SHDSL line becomes unavailable at the onset of 10 contiguous SESs (the 10
SESs are included in the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10
contiguous seconds with no SESs (the 10 seconds with no SESs are excluded
from the unavailable time)
SES
The number of severely errored SHDSL seconds (SES) accumulated since the
module is on.
The SHDSL SES is any second which is not declared a UAS, during which at
least 50 CRC anomalies are declared, or one or more LOSW defects are
declared
CRC Anomalies
The number of CRC anomalies accumulated since the module is on.
A CRC anomaly is declared when the CRC bits generated locally on the data in
the received SHDSL frame do not match the CRC bits (crc1 - crc6) received
from the transmitter. A CRC anomaly only pertains to the frame over which it
was declared.
LOSWS
Displays the number of SHDSL LOSW seconds (LOSWS) accumulated since
the module is on.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW
defects are declared
To clear the statistics for an SHDSL port:
•
At the prompt config>port>shdsl<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
You cannot clear repeater statistics.
Note
5-218
If the SHDSL cable is removed, the repeater statistics is cleared. However, do not
use this as a method to clear repeater statistics.
SHDSL Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
5.28 SVI (Switched Virtual Interface) Ports
A switched virtual interface (SVI) is a VLAN of switch ports represented by one
interface to a routing or bridging system. There is no physical interface for the
VLAN, and the SVI provides this interface for VLANs participating in management
and PW traffic.
In Megaplex-4 management, an SVI port is an intermediate Ethernet entity
between the Bridge/Router and another Ethernet port (bound one-to-one)
providing the Layer 3 processing for packets from all switch ports associated with
the VLAN. It also serves as an ingress or egress port for terminating management
flows. The flow is configured between the physical port, which is the
management source, and the corresponding SVI port bound to the bridge port.
This flow will classify the management traffic to be forwarded to the bridge port.
For illustration, see Example under Management Bridge in Chapter 8. There is
one-to-one mapping between a VLAN and SVI, thus only a single SVI can be
mapped to a VLAN.
PW traffic created in the Megaplex-4 is switched to the external network via flows
with SVI as one of the flow endpoints. Same SVI can share multiple PW’s with a
VLAN-based classifier, defined in the PW menu.
You can enable and operate a switched virtual interface (SVI port) as explained
below.
To define an SVI port:
•
At the config>port# prompt, enter svi <port number>.
The config>port>svi <port number># prompt appears and the relevant SVI
port is defined.
To administratively enable an SVI port:
•
At the config>port>svi<port number># prompt, enter no shutdown.
The SVI port is administratively enabled.
To administratively disable an SVI port:
•
At the config>port>svi<port number># prompt, enter shutdown.
The SVI port is administratively disabled.
To display all SVI ports configured in the system:
•
At the config>port prompt, enter show svi-summary.
config>port# show svi-summary
SVI Number Admin
Bound to
----------------------------------------------------------------------------1
Enabled
Router 1 1
2
Enabled
PW 1
All SVI ports configured in the system are displayed together with the
entities the SVI port is bound to.
Megaplex-4
SVI (Switched Virtual Interface) Ports
5-219
Chapter 5 Cards and Ports
Installation and Operation Manual
5.29 T1 Ports
Applicable Modules
The following table shows the number of t1 and t1-i ports and the features
supported by each Megaplex-4 module. The digits in brackets (1 to 3) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Table 5-60. Megaplex-4 T1 and Internal T1 Ports
T1 Ports (t1)
Internal T1 Ports
(t1-i)
Feature/
M8T1
Command
M16T1
T3
VS-
VS-
16E1T1-
16E1T1-
VS-6/E1T1
CL.2
VS16E1T1-
EoP
PW
EoP
Number of ports
8
16
28
16
16
8
84
16
name
√
√
√
√
√
√
√
√
shutdown
√
√
√
√
√
√
√
√
slot:
slot:
slot:1
slot:
slot:
slot:
slot:
slot:
port
port
:trib
port
port
port
port
port
√ (1)
√(1)(4)
√(1)
√(1)
management
√(1)
√(1)
line-interface
√
–
–
√
√
√
–
–
line-type
√(2)
√
√
√ (5)
√
√
√
√
√
√
√
only)
√
√
–
line-code
√
√
–
√
√
√
–
√
–
–
√
√
√
–
√ (1)
√ (1)
√ (1)
√ (1)
hierarchy
inband-
–
√(1)
line-length (DSU
–
–
–
line-buildout (CSU
only)
–
out-of-service
–
(voice, data,
signaling)
√ (1)
√ (1)
√ (1)
restoration-time
√
–
√
–
–
–
–
–
signaling- profile
√ (1)
–
–
–
–
–
–
–
–
–
–
profile
√ (1)
–
–
idle-code
√ (1)
√ (1)
√ (1)
√ (1)
√ (1)
√ (1)
√ (1)
–
vc-profile
–
√ (3)
√
√ (3)
√ (3)
√ (3)
√
√
tx-clock-source
–
–
–
–
√(6)
√(6)
–
–
timeslots-signaling-
5-220
T1 Ports
–
–
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
1 - N/A for Unframed
2 – Unframed is not supported when working with CL.2 module without SDH/SONET
ports
3 – Applicable if line type is unframed and the link is directly mapped to SDH-SONET
vc12-vt2
4 –N/A for T1 bound to VCG
5 –When T1 is bound to VCG, line-type=esf only
6 - Applicable when T1 is cross connected directly to PW
Standards Compliance
The T1 interface complies with ANSI T1.403-1989, AT&T Pub. 54016, AT&T
TR-62411 and ANSI T1.107.4 standards.
Functional Description
External T1 Link Interfaces are available in M8T1, VS-16E1T1-PW, VS-6/E1T1,
VS-16E1T1-EoP and M16T1 I/O modules. Internal T1 ports are available in CL.2
and VS-16E1T1-EoP modules (denoted in CLI as t1-i) and T3 modules (denoted in
CLI as t1). The parameters configurable for each module can be chosen from
Table 5-16 . General description of T1 port parameters is given in the following
sections.
Framing
The external and internal T1 ports can be independently configured in accordance
with the desired ITU-T framing mode and signaling formats:
•
D4 (SF) framing (12 frames per multiframe)
•
ESF framing (24 frames per multiframe)
•
Unframed mode: enables transparent transfer of 1.544 Mbps streams,
including streams with proprietary framing.
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode can be independently selected for each external or internal T1
port of the I/O module. It is configured by means of line-type parameter.
Line Interface (M8T1, VS-16E1T1-EoP, VS-16E1T1-PW, VS6/E1T1 Only)
Each T1 line interface has an integral CSU, which enables operation with line
attenuations up to 34 dB. The nominal transmit level is ±3V.
The CSU transmit level must be adjusted to ensure reliable operation of the
network. It can be attenuated by 7.5, 15, or 22.5 dB, for compliance with FCC
Rules Part 68A. This adjustment minimizes the interference your transmit signal
causes to other users that transmit their signals on other pairs of the same cable.
Megaplex-4
T1 Ports
5-221
Chapter 5 Cards and Ports
Installation and Operation Manual
The required setting depends mainly on the length of the cable that connects the
T1 port and the first repeater down the line.
Repeaters are usually spaced a mile apart. They are therefore designed to
optimally handle signals attenuated by one mile length of cable. If the T1 port
were closer, the repeater would receive your signal at a higher level. This will not
significantly improve the handling of your signal, but will certainly increase the
interference coupled from your pair to repeaters that serve other pairs in the
cable. To prevent this, you can select an attenuation value that will bring your
signal level closer to the expected repeater signal level. This is achieved by
connecting, as required, one, two, or three artificial line sections in series with
your T1 transmit signal. Each line section introduces a nominal attenuation of
7.5 dB (equivalent to the attenuation of approximately 1000 feet of cable). Your
system administrator or data carrier will give you the proper setting for each
port.
The line interface can also emulate a DSU interface. The selection CSU/DSU is
defined by the line-interface parameter. The relative output transmit level of the
port is selected by means of the line-buildout parameter.
Line Length
When configured for DSU emulation, the line transmit signal is user-adjustable for
line lengths of 0 to 655 feet in accordance with AT&T CB-119. The transmit signal
mask is selected in accordance with the transmit line length, to meet DSX-1
requirements, as specified by AT&T CB-119. The following selections are
available:
•
0 – 133 Ft
•
133 – 266 Ft
•
266 – 399 Ft
•
399 – 533 Ft
•
533 – 655 Ft.
These values define the length of the cable (in feet) connected between the port
connector and the network access point.
Zero Suppression
Zero suppression is user-selectable, separately for each port: transparent (AMI)
coding, B7ZS, or B8ZS. It is configured by means of line-code parameter.
Interface Type
The external T1 links have 100 Ω balanced interfaces.
Handling of T1 Alarm Conditions
The external and internal T1 ports support two types of indications in the individual
timeslots: idle timeslots and out-of-service (OOS) indications.
•
5-222
T1 Ports
Idle Timeslot Indication. A special code can be transmitted in empty timeslots
(timeslots which do not carry payload).
Megaplex-4
Installation and Operation Manual
•
Chapter 5 Cards and Ports
OOS Indications. The OOS code is inserted in individual timeslots to signal the
equipment routed to one of the module ports that the link connected to the
external port is out-of-service (e.g., because of a loss of frame
synchronization).
The idle code and OOS indications can be independently configured for each
module port. Moreover, separate OOS codes can be transmitted in the timeslots,
in accordance with the type of payload carried by each timeslot (voice or data).
T1 Payload Processing
The Megaplex-4 T1 modules support three main types of payload per timeslot:
•
Data timeslots: timeslots which are transparently transferred from port to
port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
•
Voice timeslots: timeslots carrying PCM-encoded payload, with A-law
companding for M8E1 ports and µ-law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
standards. The user can specify translation rules for the signaling
information, called signaling profiles – see details in the Signaling Profiles
section.
•
Management timeslots: with framed signals, one timeslot can be assigned in
any port to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). It is also possible to define unidirectional flows, called unidirectional
broadcasts, from one source (a timeslot of a source port) to multiple destinations
(each destination being a selected timeslot of another port).
In case of data timeslots, the flow of payload is normally unidirectional. If the
application requires bidirectional flows, cross-connect must be configured
symmetrically for both directions.
OOS Signaling
If communication between modules located in different Megaplex units fails, e.g.,
because loss of main link synchronization, it is necessary to control the state of
the signaling information at each end of the link. This activity, called
out-of-service (OOS) signaling, is performed by the M8T1 modules and can be
selected in accordance with the specific application requirements, on a per-link
basis.
The OOS signaling options supported by the M8T1 modules are as follows:
•
Megaplex-4
Signaling forced to the idle state for the duration of the out-of-service
condition (force-idle). This option is suitable for use with all the VC module
types.
T1 Ports
5-223
Chapter 5 Cards and Ports
Installation and Operation Manual
•
Signaling forced to the busy state for the duration of the out-of-service
condition (force-busy). This option is suitable for use with E&M and FXO
modules, but not with FXS modules.
•
Signaling forced to the idle state for 2.5 seconds, and then changed to the
busy state for the remaining duration of the out-of-service condition
(idle-busy). This option is suitable for use with E&M and FXO modules, but
not with FXS modules.
•
Signaling forced to the busy state for 2.5 seconds, and then changed to the
idle state for the remaining duration of the out-of-service condition
(busy-idle). This option is suitable for use with all the VC module types.
Inband Management
T1 and internal T1 ports of Megaplex-4 using a framed mode feature inband
management access to the end user’s equipment provided by configuring a
dedicated management timeslot.
The transfer of inband management traffic is controlled by using synchronous
PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
Transmission of RIP2 routing tables is done via the following options:
•
Proprietary RIP – Management traffic is routed using RAD proprietary routing
protocol
•
RIP2 – In addition to the RAD proprietary routing protocol, RIP2 routing is
also supported.
Factory Defaults
Megaplex-4 is supplied with all t1/t1-i ports disabled. Other parameter defaults
are listed in the table below.
5-224
T1 Ports
Parameter
Default Value
line-type
esf
restoration-time
10sec
line-interface
csu
idle-code
0x7f
inband-management
no inband-management (disabled)
inband-management – routing-protocol
none
out-of-service - voice
00
out-of-service - data
00
out-of-service - signaling
force-idle
signaling-profile
1
line-code
b8zs
line-length
0-133
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Default Value
line-buildout
0db
duration
infinite
Configuring a T1 Port
To configure the T1 port parameters of I/O modules:
1. Navigate to configure port t1 <slot>/<port>/<tributary> to select the T1 port
to configure.
The config>port>t1>(<slot>/<port>/<tributary>)# prompt is displayed.
Note
<tributary> refers to T1 ports of T3 modules.
2. Enter all necessary commands according to the tasks listed below (see
Table 5-61 for parameters supported in each module).
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying T1 framing
mode
line-type {unframed | esf | sf}
When the T1 port is bound to a VCG port,
VS-16E1T1-EoP supports esf option only.
Setting the line code
used by the port, and the
zero suppression method
line-code {ami | b8zs}
For guaranteed clear channel capability, use
B8ZS; do not use B7ZS for ports carrying
inband management
Specifying T1 operation
mode
line-interface {dsu | csu}
Specifying the length of
the T1 line in DSU mode
line-length {0-133 | 134-266 | 267-399 |
400-533 | 534-655}
Specifying the code
transmitted to fill unused
timeslots in T1 frames
idle-code <00 to FF (hexa)>
Megaplex-4
The available selections are [0x40 to 0x7F]
and [0xC0 to 0xFF]
T1 Ports
5-225
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol
{ppp | fr} [routing-protocol {none |
prop-rip | rip2} ]
ppp – synchronous PPP over HDLC
encapsulation
fr –Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
See also Configuring Inband Management in
Chapter 8 for important considerations on
selecting the routing protocol.
Using no inband management <timeslot>
disables inband management through this
timeslot
Not available for VS-16E1T1-EoP when this
T1 port is bound to a VCG port
Transmitting an
out-of-service signal
(OOS)
out-of-service [ voice <00 to FF (hexa)>]
[data <00 to FF (hexa)>] [signaling
{force-idle | force-busy | idle-busy |
busy-idle} ]
Specifying the signaling
profile
signaling-profile { 1 | 2 | 3 | 4 | 5 | per-ts}
Using no signaling-profile cancels signaling
profile setting
For creating and configuring signaling
profiles, see Signaling Profiles.
Specifying the signaling
profile per a single
timeslot or per timeslot
range
timeslots-signaling-profile [tsx] {1 | 2 | 3 |
4 | 5}
Setting the time required
for a port to resume
normal operation after
loss of frame
restoration-time {1sec | 10sec}
timeslots-signaling-profile [tsx..tsy] {1 | 2 |
3 | 4 | 5}
This command is available for voice
timeslots only, if you selected per-ts under
signaling-profile
This command is possible for multiple
timeslots only if they are consecutive
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.
1sec – After 1 second.
10sec – Similar to the requirements of AT&T
TR-62411 (after 10 seconds).
This parameter cannot be changed when
using the Unframed mode.
Specifying the line buildout (relative output
transmit level of the port)
5-226
T1 Ports
line-buildout {0db | -7dot5db | -15db |
-22dot5db}
M8T1, VS-16E1T1-EoP, VS-16E1T1-PW and
VS-6/E1T1 modules only
CSU mode only
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Selecting the timing
reference source used by
the port for the
transmit-to-network
direction
tx-clock-source loopback
loopback – Clock received from the E1/T1
port
tx-clock-source domain <number>
tx-clock-source through-timing
domain – Clock provided by system clock
domain
through-timing – Clock received from
VC12/VT1.5 or PW (according to the
transport network)
This field is valid for VS-16E1T1-PW and
VS-6/E1T1 modules only.
Assigning VC profile to
the port
vc profile <profile name>
Relevant for M16T1, VS-16E1T1-EoP and T3
modules, VS-16E1T1-PW, VS-6/E1T1. M8T1
does not support this feature.
For creating VC profiles, see VC Profiles.
Using no vc removes the profile.
Configuring collection of
performance
management statistics
for this port, which are
presented via the
RADview Performance
Management portal
pm-collection interval <seconds>
You can enable PM statistics collection for
all T1 ports rather than enabling it for
individual ports. In addition to enabling PM
statistics collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Configuring an Internal T1 Port
To configure the internal T1 port parameters:
8. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
configure.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.
9. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying T1 framing
mode
line-type {unframed | esf | sf}
When the internal T1 port is bound to a VCG
port, VS-16E1T1-EoP supports esf option
only.
Specifying the code
transmitted to fill unused
timeslots in T1 frames
idle-code <00 to FF (hexa)>
The available selections are [0x40 to 0x7F]
and [0xC0 to 0xFF]
Megaplex-4
T1 Ports
5-227
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol
{ppp | fr} [routing-protocol {none |
prop-rip | rip2} ]
ppp – synchronous PPP over HDLC
encapsulation
fr –Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
See also Configuring Inband Management in
Chapter 8 for important considerations on
selecting the routing protocol.
Not available for VS-16E1T1-EoP when this
T1 port is bound to a VCG port
Using no inband management <timeslot>
disables inband management through this
timeslot
Setting the time required
for a port to resume
normal operation after
loss of frame
restoration-time {1sec | 10sec}
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.
1sec – After 1 second.
10sec – Similar to the requirements of AT&T
TR-62411 (after 10 seconds).
This parameter cannot be changed when
using the Unframed mode.
Configuring collection of
performance
management statistics
for this port, which are
presented via the
RADview Performance
Management portal
pm-collection interval <seconds>
You can enable PM statistics collection for
all T1 ports rather than enabling it for
individual ports. In addition to enabling PM
statistics collection for the ports, it must be
enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Assigning VC profile to
the port
vc profile <profile name>
Using no vc removes the profile
Examples
Example 1
The following example illustrates how to configure the T1 port labeled 1 on the
M8T1 module installed in slot 9 as follows:
5-228
T1 Ports
•
Set the T1 framing mode to SF.
•
Set the restoration time to 10 sec.
•
Set the line code to AMI.
•
Set the idle code to 8E.
•
Administratively enable the port.
•
Leave all other parameters disabled or at their defaults.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
config>port>t1(9/1)# line-type sf
config>port>t1(9/1)# line-code ami
config>port>t1(9/1)# restoration-time 10sec
config>port>t1(9/1)# idle-code 0x8E
config>port>t1(9/1)# no shutdown
Example 2
This section illustrates how to configure inband management via a dedicated
timeslot on M8T1 Module.
1. Program an M8T1 module in Slot 1 and configure inband management via T1
port 1 with the following parameters:
Dedicated timeslot - #24
Inband management protocol: synchronous PPP over HDLC encapsulation
Routing protocol: RAD proprietary RIP.
config>slot# 4 card-type e1-t1 m8t1
config>port# t1 1/1 no shutdown
config>port# t1 1/1 line-type sf
config>port# e1 1/1 inband-management 24 protocol ppp routingprotocol prop-rip
2. Configure router interface 5.
config>router# 1 interface 5 address 17.17.17.17/24
3. Bind T1 port 1/1 to router interface 5.
config>router# 1 interface 5 bind t1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate T1 port 2 of M8T1 module in Slot 9.
2. Configure signaling profile per ts:
TS-10 to profile 2
TS-1 to 9 to profile 3
Routing protocol: RAD proprietary RIP.
config>port>e1(9/2)# no shutdown
config>port>e1(9/2)# signaling-profile per-ts
config>port>e1(9/2)# timeslots-signaling-profile 10 2
config>port>e1(9/2)# timeslots-signaling-profile [1..9] 3
config>port>e1(9/2)# commit
Result : OK
3. Displaying signaling profile per ts:
config>port>t1(9/2)# info detail
name "IO-9 e1 02"
no shutdown
line-type sf
line-code ami
interface-type balanced
idle-code 0x7f
Megaplex-4
T1 Ports
5-229
Chapter 5 Cards and Ports
Installation and Operation Manual
restoration-time 10sec
out-of-service voice 0x00 data 0x00 signaling
signaling-profile per-ts
timeslots-signaling-profile 1 3
timeslots-signaling-profile 2 3
timeslots-signaling-profile 3 3
timeslots-signaling-profile 4 3
timeslots-signaling-profile 5 3
timeslots-signaling-profile 6 3
timeslots-signaling-profile 7 3
timeslots-signaling-profile 8 3
timeslots-signaling-profile 9 3
timeslots-signaling-profile 10 2
rx-sensitivity short-haul
force-idle
Configuration Errors
The following table lists messages generated by Megaplex-4 when a configuration
error on T1 modules is detected.
Table 5-61. T1 Configuration Error Messages
Code
Type
Syntax
Meaning
131
Warning
RESTORATION TIME DOES NOT For T1 links, the restoration time must be 10 seconds,
MATCH THE STD
according to the standard.
132
Error
FRAME TYPE / PROFILE
MISMATCH
The selected framing mode does not support signaling
profiles.
141
Error
ROUTING PROTOCOL/
MNG TYPE MISMATCH
The rip2 protocol on an I/O module port can be enabled
only when the inband management method is configured
to ppp or fr
144
Error
ILLEGAL IDLE CODE SELECTION
Code transmitted in idle timeslots is illegal. The available
selections for T1/T1-i ports are [0x40 to 0x7F] and [0xC0
to 0xFF]
146
Error
NUM OF E1/T1 PORTS
EXCEEDS 120
The maximum number of framed T1 ports opened on the
M16T1 modules must not exceed 120.
Viewing a T1 Port Status
Follow the instructions below for viewing the status of a T1 port.
To view the T1 port status:
•
Note
At the config>port>t1(<slot>/<port>/<tributary>)# prompt, enter show
status.
The index <tributary> is applicable to internal T1 ports of T3 modules.
The status information appears as illustrated below.
For T1 ports of M8T1, M16T1 modules:
config>port>t1(5/1)# show status
5-230
T1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Name
: IO-5 t1 01
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
Connector Type
: DB44
For T1-i ports of CL.2 modules:
config>port>t1-i(cl-a/1)# show status
Name
: CL-A t1-i 01
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
For T1 ports of T3 modules:
config>port>t1(3/1/1)# show status
Name
: IO-1 t1 01/01
Administrative Status : Up
Operation Status
: Up
Loopback Type
: None
Testing T1 Ports
The Megaplex-4 T1 ports feature test and loopback functions at the port and
timeslot levels. The following loops are supported on all t1/t1-i ports:
•
Local loopback on t1/t1-i module port
•
Remote loopback on t1/t1-i module port
•
Local loopback on timeslots of t1/t1-i module port
•
Remote loopback on timeslots of t1/t1-i module port
•
BER test on M16T1 ports and T1 ports of VS modules.
In addition, M8T1 modules support network line loopback (LLB) and network
payload loopback (PLB). T1 ports of other I/O modules do not support
network-controlled loopbacks.
The hierarchical position of t1 ports is as follows:
•
For t1 ports of T3 modules: slot:1:tributary
•
For t1 and t1-i ports of other modules: slot:port.
CL Modules
The following sections briefly describe each type of loopback on T1-i ports of CL
modules. Table 5-63 shows the paths of the signals when each or loopback is
activated.
Megaplex-4
T1 Ports
5-231
Chapter 5 Cards and Ports
Installation and Operation Manual
Table 5-62. Loopbacks on T1-i ports of CL.2 Modules
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
I/O Port
.
..
..
..
.
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
T1-i port
2
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on T1-i port
2
..
..
..
E1-i/T1-i Framers
1
Local loopback on
timeslots of
T1-i port
2
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on timeslots of
T1-i port
5-232
T1 Ports
2
.
..
..
.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Local Loopback on T1-i Port
The local T1-i port loopback is used to test the intra-Megaplex-4 paths of the
signals intended for transmission through a selected T1-i port. These paths start
at the other Megaplex-4 port(s) connected to the tested T1-i port, pass through
the DS1 cross-connect matrix in the CL module, and continues up to the framer
of the T1-i port within the SDH/SONET link interface. These paths include all of
the Megaplex-4 local ports connected to the tested T1-i port, and in the
particular the operation of the DS1 cross-connect matrix circuits that handle the
signals directed to the tested T1-i port within the CL module.
The local T1-i port loopback is activated within the T1-i framer of a selected CL
T1-i port, as shown in Table 5-63.
Remote Loopback on T1-i Port
The T1-i port remote loopback is activated on the framer serving the port within
the SDH/SONET link interface, as shown in Table 5-63.
Local Loopback on T1-i Port Timeslots
The local loopback on selected timeslots of a T1-i port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.
This test is recommended for testing the signal paths between the T1-i port and
an I/O port of another module that uses only a fraction of the available T1-i port
bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 5-63. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
specified timeslots is disrupted.
You can activate the loopback on any individual timeslot, or on several arbitrarily
selected timeslots. You cannot activate loopbacks on timeslots cross-connected
with HDLC ports.
Remote Loopback on T1-i Port Timeslots
The remote loopback on selected timeslots of a T1-i port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. The corresponding timeslots received from the local equipment
are disconnected.
This test is recommended for testing signal paths from a remote equipment unit,
through the selected timeslots of the T1-i port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 5-63. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
specified timeslots is disrupted. You cannot to activate loopbacks on timeslots
assigned to HDLC ports.
Megaplex-4
T1 Ports
5-233
Chapter 5 Cards and Ports
Installation and Operation Manual
I/O Modules
The following sections briefly describe each type of loopback on T1 ports of I/O
modules. Table 5-21 shows the paths of the signals when each or loopback is
activated.
Table 5-63. Loopbacks on T1 Ports of I/O Modules
I/O
Local loopback on T1 port (M8T1,
M16T1, VS-16E1T1-EoP, VS-16E1T1PW, VS-6/E1T1, T3 modules)
CL
Port
Interface
DS1
Cross-Connect
Matrix
Port
Interface
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on T1 port (M8T1,
M16T1, VS-16E1T1-EoP, VS-16E1T1PW, VS-6/E1T1 modules)
I/O Interface
Local loopback on T1 timeslots
(M8T1, M16T1, VS-16E1T1-PW, VS6/E1T1, VS-16E1T1-EoP modules)
1
2
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
Remote loopback on T1 timeslots
(M8T1, M16T1, VS-16E1T1-EoP,
VS-16E1T1-PW, VS-6/E1T1 modules)
1
2
..
..
.
DS1
Cross-Connect
Matrix
Local Loopback on T1 Port of I/O Module
The local port loopback is used to test the path of the signals intended for
transmission through a selected T1 port: this path starts at the other
Megaplex-4 port(s) connected to the selected port, passes through the
cross-connect matrix in the CL module, and continues up to the port line
interface. Within the tested module, the path includes most of the line interface
circuits serving the selected port, and the operation of the routing circuits that
handle the port signals within the module.
As shown in Table 5-21, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
5-234
T1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed “all-ones” signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on T1 Port of I/O Module
The remote port loopback is used to test the line interface circuits of a selected
T1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in Table 5-21, when a remote loopback is activated on a T1 port, that
port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
The remote loopback should be activated only after checking that the remote unit
operates normally with the local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
If the local Megaplex-4 unit also operated normally when the local port loopback
was activated, then while the remote loopback is connected the local unit should
receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of T1 I/O Module Port
The local loopback on selected timeslots of a T1 port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the T1 port.
As shown in Table 5-21, the loopback is activated within the I/O module routing
matrix, and only on the timeslots specified by the user during the activation of
the loopback. As a result, there is no disturbance to services provided by means
of the other timeslots of the same port: only the flow of payload carried by the
specified timeslots is disrupted.
The user can activate the loopback on any individual timeslot, or on several
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
assigned to HDLC ports.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
Megaplex-4
T1 Ports
5-235
Chapter 5 Cards and Ports
Installation and Operation Manual
Remote Loopback on Timeslots of T1 I/O Module Port
The remote loopback on selected timeslots of a T1 port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. This test is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the T1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
As shown in Table 5-21, the loopback is activated within the I/O module routing
matrix, and only on the timeslots specified by the user. As a result, there is no
disturbance to services provided by means of the other timeslots of the same
port: only the flow of payload carried by the specified timeslots is disrupted.
It is not allowed to activate loopbacks on timeslots assigned to HDLC ports.
The other features related to loopback activation/deactivation described above
for the local loopback on timeslots are also applicable to the remote loopback.
BER Test
The BER test, activated by the command bert, is used to evaluate data
transmission through selected timeslots of the link connected to a selected T1
without using external test equipment. It is available on the M16T1 module ports
and T1 ports of VS modules.
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks and BER Tests
To perform a loopback or BER test on the T1 port:
1. Navigate to configure port t1 <slot>/<port>/[<tributary>] to select the T1
port to be tested.
Note
The index <tributary> is applicable to internal T1 ports of T3 modules.
The config>port>t1>(<slot>/<port>[<tributary>])# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
To perform a loopback on the internal T1 port:
1. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
be tested.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.
5-236
T1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring
the direction of the
loopback and the duration
of it (in minutes)
loopback {local | remote} [timeslot <1..24>] [duration <duration
in minutes 1..30> ]
local – local loopback
Stopping the loopback
no loopback
Activating the BER test and
configuring its parameters
bert [ts <ts number 1..24>]
[inject-error single]
remote – remote loopback
The [ts <ts number in the range from 1
to 24>] command is used only for
framed ports and is mandatory for these
ports.
The timeslot on which BERT is performed
must be cross-connected.
CL flip stops the BERT session.
Stopping the BER test
no bert
Displaying the BER test
results
show bert
Clearing the BER test
counters
clear-bert-counters
A typical display:
Status
: Not Active
Bit Error Count: 1
Pattern
: 2e-15
Run Time (Sec) : 1
ES (Sec)
: 1
Sync Loss (Sec): 1
Displaying T1 Port Statistics
T1 and T1-i ports of Megaplex-4 feature the collection of statistical diagnostics
per ANSI T1.403, thereby allowing the carrier to monitor the transmission
performance of the links.
To display the T1 port statistics:
•
Note
The index <tributary> is applicable to internal T1 ports of T3 modules.
To display the T1-i port statistics:
•
Megaplex-4
At the prompt config>slot>port>t1(<slot>/<port>/[tributary])#, enter show
statistics followed by the parameters listed below.
At the prompt config>slot>port>t1-i(<slot>/<port>)#, enter show statistics
followed by the parameters listed below.
T1 Ports
5-237
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Displaying statistics
show statistics {total | all | all-intervals |
current}
•
total - Total statistics of last
96 intervals
•
all-intervals – Statistics for all
valid intervals
•
current - Current statistics
•
all – All statistics: first current
statistics, then statistics for all
valid intervals, and finally total
statistics
Displaying statistics
for a specific
interval
show statistics interval <interval-num 1..96>
T1 port statistics are displayed. The counters are described in
Table 5-64, Table 5-65 and Table 5-66.
Note
BES, LOFC and Rx Frames Slip are displayed for framed formats only and are not
displayed for T1 ports of T3 modules.
For example:
Current statistics:
config>port>t1(1/2)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 191
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Statistics for interval 67:
config>port>t1(3/1)# show statistics interval 67
Interval Number : 67
Interval
--------------------------------------------------------------ES
: 16
SES
: 1
UAS
: 589
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total statistics:
config>port>t1(1/2)# show statistics total
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
5-238
T1 Ports
Megaplex-4
Installation and Operation Manual
BES
Rx Frames Slip : 0
LOFC
: 0
Chapter 5 Cards and Ports
: 0
All statistics:
config>port>t1(1/2)# show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 171
Valid Intervals
: 2
config>port>e1(1/2)#
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 1
Interval
--------------------------------------------------------------ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 2
Interval
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Table 5-67. T1 Port Statistics Parameters – Current 15-Minute Interval
Parameter
Description
ES
Displays the number of errored seconds in the current 15-minute interval.
An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
Megaplex-4
T1 Ports
5-239
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
UAS
Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
SES
•
Any second following 10 consecutive SES seconds
•
A second for which any of the previous 10 consecutive seconds was also a UAS
and any of the previous 10 consecutive seconds was a SES.
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES
Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
LOFC
Displays the number of LOFC in the current interval.
The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip
Displays the number of Rx Frames Slips in the current 15-minute interval.
A CSS is a second with one or more controlled slip events.
Time elapsed
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96).
Table 5-68. T1 Port Statistics Parameters – Selected 15-Minute Interval
Parameter
Description
ES
Displays the total number of errored seconds (ES) in the selected interval
UAS
Displays the total number of unavailable seconds (UAS) in the selected interval
SES
Displays the total number of severely errored seconds (SES) in the selected interval
BES
Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC
Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number
Displays the number of interval for which statistics is displayed
Note: The sequence of intervals is different for the T1 ports of different module
families:
•
For the M8T1 modules, Interval #1 is the latest in time
•
For the M16T1 and T3 modules, Interval #1 is the earliest in time.
Table 5-69. T1 Port Statistics Parameters – Total Statistics
Parameter
Description
ES
Displays the total number of errored seconds (ES) since statistics is available
UAS
Displays the total number of unavailable seconds (UAS) since statistics is available
5-240
T1 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Parameter
Description
SES
Displays the total number of severely errored seconds since statistics is available
BES
Displays the total number of bursty errored seconds (BES) since statistics is available
LOFC
Displays the total number of loss of frame alignment events since statistics is available
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events since statistics is available
To clear the statistics for a T1 port:
•
At the prompt config>port>t1<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.30 T3 Ports
Applicable Modules
T3
Standards Compliance
The T3 interface complies with ANSI T1.107 and ANSI T1.102 standards.
Functional Description
T3 ports of Megaplex-4 provide access to standard T3 equipment over
unbalanced copper lines with full duplex data rates of 44.7 Mbps, enabling easy
connectivity to a T3/SONET network.
General description of T3 port parameters is given in the following sections.
Framing
The T3 ports can be independently configured in accordance with the desired
framing mode:
•
Synchronous M13 (SYNTRAN) in accordance with ANSI T1.107a.
•
Asynchronous C-bit parity multiplex applications in accordance with ANSI
T1.107-1995
•
Unframed.
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode is configured by means of line-type parameter.
Megaplex-4
T3 Ports
5-241
Chapter 5 Cards and Ports
Installation and Operation Manual
Line Length
The maximum allowed signal attenuation is in accordance with ITU-T Rec. G.703
requirements. For optimal performance, the receive side includes an equalizer
which must be preset in accordance with cable length: up to 225 ft, or more than
225 ft.
This is configured by means of line-length parameter.
Interface Type
The T3 links have 75 Ω unbalanced interfaces.
Factory Defaults
Megaplex-4 is supplied with all T3 ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
line-type
m13
line-length
up-to-225ft
vc profile
"tug-structure"
Configuring a T3 Port
To configure the T3 port parameters of I/O modules:
1. Navigate to configure port t3 <slot>/<port> to select the T3 port to
configure.
The config>port>t3>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no name removes the name
Defining the port as
channelized
channelized
Using no channelized cancels channelization
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying T3 framing
mode
line-type {c-bit-parity | m13 | unframed}
m13 – synchronous M13 multiplex framing
mode
c-bit-parity – asynchronous C-bit parity
framing mode
unframed – unframed mode. This mode is
used for transferring Ethernet over T3 and
is not relevant for Ethernet transport over
T1.
5-242
T3 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Specifying the length of
the T3 line
line-length {up-to-225ft | over-225ft}
The following example illustrates how to configure the T3 port labeled 1 on the
T3 module installed in slot 9 as follows:
•
Set the T3 framing mode to c-bit-parity.
•
Administratively enable the port.
•
Leave all other parameters disabled or at their defaults.
config>port>t3(9/1)# line-type c-bit-parity
config>port>t3(9/1)# no shutdown
Configuration Errors
The following table lists messages generated by Megaplex-4 when a configuration
error on T3 modules is detected.
Table 5-70. T3 Configuration Error Messages
Code
Type
Syntax
Meaning
434
Error
PORT LINE TYPE MISMATCH
One of the following:
•
T3 port can be bound to a VCG only when working in
unchannelized mode with C-BIT parity line-type.
•
T1 unframed cannot be bound to a VCG.
•
T3 can be bound to a GFP only when working in
unchannelized mode with C-BIT parity line-type or in
unframed mode
Error 434 may also appear for other port types – refer to
the corresponding manual section.
770
Error
VCAT NUMBER OF PORTS
LIMITED TO 16
771
Error
GFP CAN BE BOUND TO SINGLE
A GFP can be bound only to a single T1/T3 port.
PORT ONLY
772
Warning
MISSING ASSOCIATED T1 IN
CHANNELIZED PORT
When T3 is configured as channelized (framed) it must
contain at least one T1 port
773
Warning
UNCHANNELIZED PORT CANT
CONTAIN ASSOCIATED T1
When T3 is configured as unchannelized, it cannot contain
associated T1 ports
774
Warning
SHUTDOWN PORT CONTAINS
ASSOCIATED T1 CHANNELS
When a T3 port contains associated open T1 ports, it
must be open as well.
775
Error
ILLEGAL X-CONNECT FOR T1
PORTS 17-28
If one of the timeslots is defined as voice and the CL
module has no SDH/SONET ports, this cross-connect is
impossible for internal T1 ports 17 to 28 of the T3
module.
Megaplex-4
According to ITU-T Rec. G.7043/Y.1343, you cannot bind
more than 16 T1 ports to a single VCG.
T3 Ports
5-243
Chapter 5 Cards and Ports
Installation and Operation Manual
Code
Type
Syntax
Meaning
776
Error
INSUFFICIENT BUS BANDWIDTH Relevant only in a CL with SDH, while being connected to
CL via PDH bus. 28 ports can be opened only on 3 slots.
All other slots can open only up to 24 ports.
778
Error
UNFRAMED PORT CONTAINS
ASSOCIATED T1 CHANNELS
When T3 is configured as unframed, it cannot contain
associated T1 ports
Viewing a T3 Port Status
Follow the instructions below for viewing the status of a T3 port.
To view the T3 port status:
•
At the config>port>t3(<slot>/<port>)# prompt, enter show status.
The status information appears as illustrated below.
config>port>t3(1/1)# show status
Name
: IO-1 t3 01
Administrative Status : Up
Operation Status
: Up
Testing T3 Ports
The Megaplex-4 T3 ports feature local and remote loopbacks at the port level.
Table 5-21 shows the paths of the signals when each or loopback is activated.
Table 5-71. Loopbacks on T3 Ports
I/O
Local loopback on T3 port
CL
Port
Interface
DS1
Cross-Connect
Matrix
Port
Interface
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on T3 port
Local Loopback on T3 Port
The local port loopback is used to test the path of the signals intended for
transmission through a selected T3 port: this path starts at the other
Megaplex-4 port(s) connected to the selected port, passes through the
5-244
T3 Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
cross-connect matrix in the CL module, and continues up to the port line
interface. Within the tested module, the path includes most of the line interface
circuits serving the selected port, and the operation of the routing circuits that
handle the port signals within the module.
As shown in Table 5-21, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
Remote Loopback on T3 Port
The remote port loopback is used to test the line interface circuits of a selected
T3 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in Table 5-21, when a remote loopback is activated on a T3 port, that
port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
The remote loopback should be activated only after checking that the remote unit
operates normally with the local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
If the local Megaplex-4 unit also operated normally when the local port loopback
was activated, then while the remote loopback is connected the local unit should
receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks
To perform a loopback on the T3 port:
1. Navigate to configure port t3 <slot>/<port> to select the T3 port to be
tested.
The config>port>t3>(<slot>/<port>)# prompt is displayed.
Megaplex-4
T3 Ports
5-245
Chapter 5 Cards and Ports
Installation and Operation Manual
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring
the direction of the
loopback and the duration
of it (in minutes)
loopback {local | remote} [duration
<duration in minutes 1..30> ]
local – local loopback
Stopping the loopback
no loopback
Displaying the loopback
status
show loopback
remote – remote loopback
Displaying T3 Port Statistics
T3 ports of Megaplex-4 feature the collection of statistical diagnostics per
RFC-3896, allowing the carrier to monitor the transmission performance of the
links.
To display the T3 port statistics:
•
At the prompt config>slot>port>t3(<slot><port>)#, enter show statistics
followed by the parameters listed below.
Task
Command
Comments
Displaying statistics
show statistics {total | all | all-intervals |
current}
•
total - Total statistics of last
96 intervals
•
all-intervals – Statistics for all
valid intervals
•
current - Current statistics
•
all – All statistics: first current
statistics, then statistics for all
valid intervals, and finally total
statistics
Displaying statistics
for a specific
interval
show statistics interval <interval-num 1..96>
T3 port statistics are displayed. The counters are described in Table 5-73.
For example:
Current statistics:
config>port>e1(1/2)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 751
Valid Intervals
: 3
PES
PSES
SEFS
UAS
5-246
T3 Ports
: 0
: 0
: 0
: 20
LES
CES
CSES
: 0
: 0
: 0
Megaplex-4
Installation and Operation Manual
PCV
Chapter 5 Cards and Ports
: 0
Statistics for interval 4:
config>port>t3(2/1)# show statistics interval 4
Interval
--------------------------------------------------------------------Interval Number : 4
PES
PSES
SEFS
UAS
PCV
: 0
: 0
: 0
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
All intervals:
config>port>t3(2/1)# show statistics all-intervals
Interval
--------------------------------------------------------------------Interval Number : 1
PES
PSES
SEFS
UAS
PCV
: 0
: 0
: 0
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
: 0
: 0
: 0
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
: 0
: 0
: 0
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
Interval
Interval Number : 2
PES
PSES
SEFS
UAS
PCV
Interval
Interval Number : 3
PES
PSES
SEFS
UAS
PCV
Total statistics:
Megaplex-4
T3 Ports
5-247
Chapter 5 Cards and Ports
Installation and Operation Manual
config>port>t3(2/1)# show statistics total
Total
----------------------------------------------------------------PES
: 5
LES
: 0
PSES
: 5
CES
: 5
SEFS
: 5
CSES
: 5
UAS
: 1159
PCV
: 0
All statistics:
PES
PSES
SEFS
UAS
PCV
config>port>t3(2/1)# show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 287
Valid Intervals
: 3
: 0
LES
: 0
: 0
CES
: 0
: 0
CSES
: 0
: 0
: 0
Interval
----------------------------------------------------------------Interval Number : 1
PES
PSES
SEFS
UAS
PCV
: 0
: 0
: 10
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
Interval
----------------------------------------------------------------Interval Number : 2
PES
PSES
SEFS
UAS
PCV
: 0
: 0
: 21
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
Interval
----------------------------------------------------------------Interval Number : 3
5-248
T3 Ports
Megaplex-4
Installation and Operation Manual
PES
PSES
SEFS
UAS
PCV
Chapter 5 Cards and Ports
: 0
: 0
: 0
: 0
: 0
LES
CES
CSES
: 0
: 0
: 0
Total
--------------------------------------------------------------PES
: 0
LES
PSES
: 0
CES
SEFS
: 31
CSES
UAS
: 0
PCV
: 0
: 0
: 0
: 0
Table 5-72. T3 Port Statistics Parameters
Parameter
Description
Time elapsed
(Current statistics
only)
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds
Valid Intervals
(Current statistics
only)
The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96)
Interval number
(Selected interval
and “all-intervals”
statistics only)
Number of interval for which statistics is displayed. Interval #1 is the earliest in time.
LES
A Line Errored Second is a second in which one or more CV OR one or more LOS
defects occurred.
UAS
Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
•
Any second following 10 consecutive SES seconds
•
A second for which any of the previous 10 consecutive seconds was also a UAS
and any of the previous 10 consecutive seconds was a SES.
PES
Displays the number of P-bit Error Seconds (PES) in the current interval. A Line error
Second is a second in which one or more PCV occurred OR one or more LOS defects.
PCV
Displays the number of P-bit Coding Violations (PCV).
A P-bit Coding Violation or a P-bit Parity Error event is the occurrence of a received Pbit code on the DS3 M-frame that is not identical to the corresponding locallycalculated code.
Displays the namber of C-bit Errored Seconds (CES).
A CES is a second with one or more CCVs OR one or more Out of Frame defects OR
detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3
applications. This gauge is not incremented when UASs are counted.
Megaplex-4
T3 Ports
5-249
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
PSES
Displays the namber of P-bit Severely Errored Seconds (PSES)
A PSES is a second with 44 or more PCVs OR one or more Out of Frame defects OR
detected incoming AIS. This gauge is not incremented when UASs are counted.
CSES
Displays the number of C-bit severely errored seconds (CSES) in the current interval.
A CSES is a second with 44 or more CCVs OR one or more Out of Frame defects OR
detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3
applications. This gauge is not incremented when UASs are counted.
CSES
Displays the number of C-bit severely errored seconds (CSES) in the current interval.
A CSES is a second with 44 or more CCVs OR one or more Out of Frame defects OR
detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3
applications. This gauge is not incremented when UASs are counted.
SEFS
Displays the number of Severely Errored Framing Seconds (SEFS)
A SEFS is a second with one or more Out of Frame defects OR detected incoming AIS.
This item is not incremented during unavailable seconds.
To clear the statistics for a T3 port:
•
At the prompt config>port>t3<slot>/<port>)#, enter clear-statistics.
The statistics for the specified port are cleared.
5.31 TDM Bridge Ports
Applicable Modules
To implement specific bidirectional broadcast applications over serial ports of VS
modules, Megaplex-4 architecture uses an entity named TDM bridge port. TDM
bridge ports exist only on VS modules and are mapped to serial ports. The
maximum number of TDM bridge ports is 4 per VS-12 module and 6 per VS-6/C37,
VS-6/BIN, VS-6/FXS, VS-6/FXO, VS-6/E&M modules.
Standards Compliance
TDM bridge ports are RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with all TDM bridge ports disabled.
Configuring TDM Bridge Ports
To configure a TDM Bridge port:
1. Navigate to configure port tdm-bridge <slot>/<port> to select the TDM
bridge port to configure.
5-250
TDM Bridge Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
The config>port>tdm-bridge>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to
port
name <string>
Using no name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Binding the serial port to the
tdm-bridge port
bind serial <slot>/<port>
Serial slot number must be the same as
tdm-bridge slot number.
Using no before the corresponding
command removes the binding
Example
See DS0 Cross-Connect section in Chapter 8, Example 9.
5.32 Teleprotection Ports (Physical)
Applicable Modules
The TP module supports up to 4 command inputs and 8 outputs, enabling
teleprotection equipment to utilize the advanced transport capabilities offered by
Megaplex.
It also includes two independent groups of CMD channels:
•
East – CMD channels 1 (working) and 2 (protection)
•
West – CMD channels 3 (working) and 4 (protection).
The teleprotection commands can be locally output or be carried to a peer
card/Megaplex over a TDM/SDH network or over a packet-switched network. Up
to 4 commands can be carried over a single DS0.
Functional Description
See Alarm Relay Modules chapter in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
The Megaplex-4 is supplied with all teleprotection ports disabled. Other
parameter defaults are listed in the table below.
Parameter
Description
Default Value
cmd-in
Megaplex-4
Teleprotection Ports (Physical)
5-251
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
Default Value
input-active
Association between the cmd-in active state and the
supplied voltage
high
preset-duration
Extended cmd-in duration period (msec)
0
bounce-override
Debounce filter window time (time during which the cmd- 1000
in signal is sampled, µsec)
switching-voltage
Switching voltage
110
prolongation
Minimum duration of pulse period (msec)
0
alarm-state-energized
cmd-out alarm state indication
yes
led-latched
LED behavior when the related command turns inactive
no led-latched
pulse-duration
Maximum duration of pulse period (msec)
0
rate
Setting cmd-channel rate
(in kbps)
64
tx-address
Tx address for recognizing and preventing wrong crossconnect of teleprotection data in the network
1
rx-address
Rx address for recognizing and preventing wrong crossconnect of teleprotection data in the network
2
trigger-mode
Teleprotection triggering mode
speed-optimized
oos-recovery
Mode of recovery from sending oos code and switching
back from the protection state
auto
cmd-out
cmd-channel
Configuring CMD-IN Ports
To configure a cmd-in port:
1. Navigate to configure port cmd-in <slot>/<port> to select the cmd-in port to
configure.
The config>port>cmd-in>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
5-252
Teleprotection Ports (Physical)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Setting the debounce filter
window time (time during
which the cmd-in signal is
sampled)
bounce-override <µsec >
0 to 32000 µsec, in 250-µsec steps
Setting the extended cmd-in
duration period
preset-duration <msec>
Defining the association
between the cmd-in active
state and the supplied
voltage
input-active {high | low}
Defining LED behavior when
the related command turns
inactive
led-latched
For more information on bounce-override
command, see Teleprotection section in
Megaplex-4 I/O Modules Installation and
Operation Manual, Alarm Relay Modules
Chapter.
0 to 2000 msec, in 1-msec steps
For more information on preset-duration
command, see Teleprotection section in
Megaplex-4 I/O Modules Installation and
Operation Manual, Alarm Relay Modules
Chapter.
Clearing the led-latched
state
clear-cmd-led
Forcing the cmd-in port into
active state, disregarding
the actual input state
force-active
Selection of the switching
voltage
switching-voltage
•
low – low voltage means that command
input is in active state
•
high – high voltage means that
command input is in active state
•
led-latched – the LED lights once the
related command becomes active, and
stays on even when the command is not
active, until explicit clear-cmd-led
command is issued by the user
•
no led-latched – the LED follows the
related command activity
See also Clear-Cmd-Led Command per
System
Using no force-active cancels the command
{24 |48 |110 | 125 | 220 | 250}
Configuring CMD-OUT Ports
Cmd out ports 1 to 4 always serve as primary ports.
Cmd out ports 5 to 8 can either serve as secondary cmd-out ports or used to
report internal system alarms to outside indicators. In the first case they are
bound to the primary ports and automatically copy their configuration. In the
second case you have to bind them to the corresponding alarms under reporting
context by using bind-alarm-to-relay and bind-alarm-source-to-relay commands,
as described in Chapter 11.
To configure the cmd-out port parameters:
1. Navigate to configure port cmd-out <slot>/<port> to select the port to
configure.
Megaplex-4
Teleprotection Ports (Physical)
5-253
Chapter 5 Cards and Ports
Installation and Operation Manual
The config>port>cmd-out>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
4.
Task
Command
Comments
Assigning short description
to port
name <string>
Using no name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Setting minimum cmd-out
signal duration (for very
short pulses)
prolongation <msec>
If the received pulse period of cmd-out-i
signal (received via cmd-channel) is shorter
than this specific value, the cmd-out pulse
duration will be extended to this value.
Allowed values: 0 to 15000, with steps of
1 msec
If prolongation =0, the command is not
activated and the received pulse period is not
extended
When cmd-out is functioning as a binary
output port, this parameter does not appear.
Setting maximum cmd-out
signal duration (for very
long pulses)
pulse-duration <msec>
If the received pulse period of cmd-out-i
signal (received via cmd-channel) is longer
than this specific value, the cmd-out pulse
duration will be shortened to this value.
Allowed values: 0 to 15000, with steps of
1 msec
If pulse-duration=0, the command is not
activated and the received pulse period is not
shortened
When cmd-out is functioning as a binary
output port, this parameter does not appear.
Defining cmd-out alarm
state indication
alarm-state-energized {yes |
no}
yes – alarm state is indicated by closed cicruit
Defines LED behavior when
the related command turns
inactive
led-latched
•
led-latched – the LED lights once the
related command becomes active, and
stays on even when the command is not
active, until explicit clear-cmd-led
command is issued by the user.
•
no led-latched – the LED follows the
related command activity.
5-254
Teleprotection Ports (Physical)
no – alarm state is indicated by open cicruit
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Creating a set of ports that
will be trigger sources for
the current port
trigger-bind < number> cmdout-i <slot/port/tributary
[none | or | and]
See Command Cross-Connect in Megaplex-4
I/O Modules Installation and Operation
Manual, Alarm Relay Modules Chapter.
trigger-bind < number> cmdin <slot/port> [none | or |
and]
Using no trigger-bind < number> removes the
set.
“none” is default operator and can be
omitted when only one trigger source is
defined.
When more than one trigger sources are
defined, the operator must be either “or” or
“and” for all trigger sources.
Binding a secondary cmdout port to a primary cmdout port
secondary-bind <slot>/<port>
Primary cmd-out ports: 1 to 4.
Secondary cmd-out ports: 5 to 8.
One or more secondary ports can be bound
to one primary port.
A cmd-out port cannot be simultaneously
bound as Alarm Relay (see Chapter 11) and
bound as secondary cmd-out port to a
primary cmd-out port (the current command).
To view the command result, use “info detail”
command.
Clearing the led-latched
state
clear-cmd-led
See also Clear-Cmd-Led Command per System
Configuring CMD-CHANNEL Ports
To configure the cmd-channel port parameters:
1. Navigate to configure port cmd-channel <slot>/<port> to select the port to
configure.
The config>port>cmd-channel>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Administratively enabling port
no shutdown
Using shutdown disables the port
Assigning short description to port
name <string>
Using no name removes the name
Setting cmd-channel rate
(in kbps)
rate {64 | 128}
Configuring Tx address for
recognizing and preventing wrong
cross-connect of teleprotection
data in the network
tx-address
Megaplex-4
The allowed values are 1 to 254.
Teleprotection Ports (Physical)
5-255
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Configuring Rx address for
recognizing and preventing wrong
cross-connect of teleprotection
data in the network
rx-address
The allowed values are 1 to 254.
Stopping transmitting the oos code
reactivate
For oos-recovery=manual only
Controlling the mode of recovery
from sending oos code and
switching back from the protection
state
oos-recovery {auto |
manual}
•
auto – when the OOS condition is over,
the cmd-in-i port automatically stops
sending the oos code and switches back
from the protection state
•
manual – when the OOS condition is over,
the oos code continues to be sent and
the system remains in the protection
state until the user sends “reactivate”
command
•
speed-optimized – one frame is enough
to trigger command change
•
security-optimized – in order to trigger
the command change, the value must be
stable for at least two frames (this adds
1.5 msec delay)
Defining teleprotection triggering
mode
trigger-mode {speedoptimized | securityoptimized}
Clear-Cmd-Led Command per System
The clear-cmd-led command can be performed not only for a specific port, but
system-wide.
To clear the Latched Led state system-wide:
1. Navigate to configure port.
The config>port># prompt is displayed.
2. Enter clear-cmd-led {all | cmd-in | cmd-out} for the required ports:
cmd-in – all cmd-in ports
cmd-out – all cmd-out ports
all – all cmd-in and cmd-out ports.
The state is cleared for all the ports indicated in the command.
Configuration Errors
The tables below list messages generated by Megaplex-4 when a configuration
error on the Teleprotection module is detected.
5-256
Teleprotection Ports (Physical)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Table 5-73. TP Configuration Error Messages
Code
Type
Syntax
Meaning
680
Error
IDENTICAL TX/RX ADDRESSES
ARE ILLEGAL
The Tx&Rx addresses on a cmd channel cannot be
configured to the same value (with the exception of 254)
681
Error
BOUND PORT IS IN
SHUTDOWN STATE
One of the following ports is in shutdown state:
•
cmd-out-i or cmd-in port participating in trigger-bind
command
•
cmd-out port participating in secondary-bind command
682
Error
SECONDARY PORT IS BOUND
MORE THAN ONCE
A secondary cmd-out port can be bound to a primary cmdout port only once
684
Error
ASSOCIATED CMD CHANNEL IS
IN SHUTDOWN STATE
When a cmd-in-i and/or cmd-out-i port is in “no
shutdown” state, its associated cmd-channel ports must
be also at “no shutdown”.
685
Error
ILLEGAL LOGIC OPERATOR IN
TRIGGER-BIND
When more than one trigger sources are defined, the
operator must be either “or” or “and” for all trigger
sources.
686
Error
ILLEGAL PORT TYPE USED IN
TRIGGER BIND
For cmd-out and cmd-in-i ports, the associate
trigger port can be either cmd-out-i or cmd-in.
687
Error
ILLEGAL SECONDARY
SLOT/PORT BOUND
Primary and secondary cmd-out ports bound to each other
must reside in the same slot.
688
Error
PULSE DURATION IS SHORTER
THAN PROLONGATION
Command prolongation must be shorter than pulse
duration.
Viewing Status Information
For viewing the status of the physical Teleprotection ports, follow the
instructions below.
To view the status of a cmd-in port:
1. Navigate to config>port> cmd-in> (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
config port cmd-in 4/1 show status
Name
: IO-4 Cmd in 01
Administrative Status : Up
Operation Status
: Up
Value
: 1
Led
: Latched
Force
: Yes
Input Control Voltage : 220 VDC
The status display provides information about:
Megaplex-4
Administrative and operational status
Value - Command value (0, 1, or N/A)
Teleprotection Ports (Physical)
5-257
Chapter 5 Cards and Ports
Installation and Operation Manual
Led – LED behavior when the related command turns inactive
(Latched/No Latched)
Force – Whether the port is in force-active state (Yes/No)
Input Control Voltage (24, 48, 110, 125, 220 or 250 VDC)
To view the status of a cmd-out port:
1. Navigate to config>port> cmd-out> (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
config port cmd-out 4/1 show status
Name
: IO-4 Cmd out 01
Administrative Status : Up
Operation Status
: Down
Value
: 1
Led
: Not Latched
Relay Type
: Electro Mechanical
The status display provides information about:
Administrative and operational status
Value – Command value (0, 1, or N/A)
Led – LED behavior when the related command turns inactive
(Latched/No Latched)
Relay Type (Electro Mechanical or Solid State). The value is identical for all
cmd-out ports and based on the card type.
To view the status of a cmd-channel port:
1. Navigate to config>port> cmd-channel> (<slot>/<port>)#
2. Type show status.
The status is displayed, for example as follows:
config port cmd-channel 4/1 show status
Name
: IO-4 CMD Channel 01
Administrative Status : Up
Operation Status
: Down
Detail Status
: No Sync
Rx Address
: 0
Latency (millisec)
: 2
Protection State
: Active
CMD IN I
Name
Admin
Oper
Tx Val
4/1/1
4/1/2
4/1/3
4/1/4
IO-4 Cmd in-i 01
IO-4 Cmd in-i 01
IO-4 Cmd in-i 01
IO-4 Cmd in-i 01
Up
Up
Up
Up
Up
Up
Up
Up
0
0
0
0
CMD OUT I
Name
Admin
Oper
Loopback
Rx Val
4/1/1
IO-4 Cmd out-i 01
Up
Up
No Loop
0
5-258
Teleprotection Ports (Physical)
Megaplex-4
Installation and Operation Manual
4/1/2
4/1/3
4/1/4
IO-4 Cmd out-i 01
IO-4 Cmd out-i 01
IO-4 Cmd out-i 01
Chapter 5 Cards and Ports
Up
Up
Up
Up
Up
Up
No Loop
No Loop
No Loop
0
0
0
The status display provides information about:
Administrative and operational status
Detail Status:
o
Sync – port is synchronized
o
No Sync –port is not synchronized
o
Address mismatch – there is a mismatch between the Rx address and
the expected Tx address
o
N/A – not relevant
Rx Address –recieved Rx address
Latency –cmd-channel data end-to-end latency
Protection state for cmd-channels 1/2 and 3/4 (Active/Standby or N/A if
protection not defined)
Cmd-in and cmd-out-i status (see Viewing Status Information of Logical
Teleprotection Ports for details)
Displaying Teleprotection Statistics
Teleprotection ports cmd-in, cmd-out and cmd-channel feature RAD proprietary
statistical diagnostics.
To display the statistics of a cmd-in port:
1. Navigate to config>port> cmd-in> (<slot>/<port>)#
2. Type show statistics.
The statistics is displayed, for example as follows:
config port cmd-in 4/1 show statistics
Raw
Debounced
Trip : 1
1
The statistics shows the number of trips occurred before (raw) and after
(debounced) debounce filtering.
To display the statistics of a cmd-out port:
1. Navigate to config>port> cmd-out> (<slot>/<port>)#
2. Type show statistics.
The statistics (number of trips) is displayed, for example as follows:
config port cmd-out 4/1 show statistics
Trip Counter : 4
To display the statistics of a cmd-channel port:
1. Navigate to config>port> cmd-channel> (<slot>/<port>)#
2. Type show statistics.
Megaplex-4
Teleprotection Ports (Physical)
5-259
Chapter 5 Cards and Ports
Installation and Operation Manual
The statistics is displayed, for example as follows:
config port cmd-channel 4/1 show statistics
Frame Error : 2
CRC Error
: 3
CMD IN I
Trip Counter
4/1/1
4/1/2
4/1/3
4/1/4
0
0
0
0
CMD OUT I
Trip Counter
4/1/1
4/1/2
4/1/3
4/1/4
0
0
0
0
Table 5-74. TP Statistics Parameters
Parameter
Description
Frame Error
Number of frame errors received on the cmd channel since last reset or power-up
CRC Error
Number of CRC errors received on the cmd channel since last reset or power-up
A CRC error is declared when the CRC bits generated locally on the data in the received
frame (protecting critical teleprotection bits) do not match the CRC bits (crc1 – crc4)
received from the transmitter.
To clear the statistics on a TP port:
1. Navigate to the corresponding port.
2. Enter clear-statistics.
The statistics for the specified port are cleared.
5.33 Teleprotection Ports (Logical)
Applicable Modules
Teleprotection ports are available on TP modules. Four cmd-in-i and four cmdout-i ports for each of cmd channels 1 and 3 house the logic to manipulate the
logical Rx/Tx information over the corresponding cmd channel. This logic is
capable to perform either basic transparent command cross-connect or logical
(and/or) operation between the external/logical inputs/outputs and
teleprotection information transported over cmd channels.
Automation cmd channels 5 and 6 can be connected to four cmd-out-i ports
each.
5-260
Teleprotection Ports (Logical)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Functional Description
See the Teleprotection Modules section in Megaplex-4 I/O Modules Installation
and Operation Manual, Alarm Relay Modules Chapter.
Factory Defaults
The Megaplex-4 is supplied with all teleprotection ports disabled. Cmd in-i ports
have no factory defaults. Cmd-out-i parameter defaults are listed in the table
below.
Parameter
Description
Default Value
oos-code
The value that will be inserted to the related cmd-out
output when the cmd-channel is in the out-of-service
state
last-valid-state
Configuring CMD-IN-I Ports
To configure the cmd-in internal port parameters:
1. Navigate to configure port cmd-in-i <slot>/<port>/<tributary> to select the
port to configure.
The config>port>cmd-in-i>(<slot>/<port>/<tributary>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Administratively enabling
port
no shutdown
Using shutdown disables the port
Assigning short description
to port
name <string>
Using no name removes the name
Creating a set of ports that
will be trigger sources for
the current port
trigger-bind < number> cmd-out-i
<slot/port/tributary> [none | or |
and]
See Command Cross-Connect in
Megaplex-4 I/O Modules Installation and
Operation Manual, Alarm Relay Modules
Chapter, Teleprotection section.
trigger-bind < number> cmd-in
<slot/port> [none | or | and]
Using no trigger-bind < number>
removes the set.
“none” is default operator and can be
omitted when only one trigger source is
defined.
When more than one trigger sources are
defined, the operator must be either
“or” or “and” for all trigger sources.
Megaplex-4
Teleprotection Ports (Logical)
5-261
Chapter 5 Cards and Ports
Installation and Operation Manual
Configuring CMD-OUT-I Ports
To configure the cmd-out internal port parameters:
1. Navigate to configure port cmd-out-i <slot>/<port>/<tributary> to select the
port to configure.
The config>port>cmd-out-i>(<slot>/<port>/<tributary>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Administratively enabling
port
no shutdown
Using shutdown disables the port
Assigning short description
to port
name <string>
Using no name removes the name
Selecting the value that will
be inserted to the related
cmd-out output when the
cmd-channel is in the outof-service state
oos-code {on | off |
last-valid-state}
off – Cmd-out is forced to off
Activating remote loopback
loopback remote [duration
<minutes>]
on – Cmd-out is forced to on
last-valid-state – Cmd-out takes the last valid
state value (on or off)
See Testing Teleprotection Ports below
Viewing Status Information of Logical Teleprotection Ports
For viewing the status of the logical Teleprotection ports, follow the instructions
below.
To view the status of a cmd-out-i port:
1. Navigate to config>port> cmd-out-i> (<slot>/<port>/<trib>)#
2. Type show status.
The status is displayed, for example as follows:
config port cmd-out-i(4/1/1)# show status
Name
: IO-4 Cmd out-i 01
Administrative Status : Up
Operation Status
: Up
Value
: 1
Loopback
: No Loop
The status display provides information about:
Administrative and operational status
Value - Command value (0, 1, N/A)
Whether a remote loopback is active on the port.
To view the status of a cmd-in-i port:
1. Navigate to config>port> cmd-in-i> (<slot>/<port>/<trib>)#
2. Type show status.
5-262
Teleprotection Ports (Logical)
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
The status is displayed, for example as follows:
config port cmd-in-i(4/1/1)# show status
Name
: IO-4 Cmd-in-i 01
Administrative Status : Up
Operation Status
: Up
Value
: 1
The status display provides information about:
Administrative and operational status
Value - Command value (0, 1, N/A).
Testing Teleprotection Ports
The remote digital loopback in the TP module are activated from cmd-out-i ports.
The loopback can be performed independently per each entity.
The remote loopback is a digital loopback performed at the cmd-out-i port, by
returning the received teleprotection signal from the communication network
(cmd-channel) back to the remote RTU. This loopback checks network
connectivity of the remote RTU.
The diagram below shows where the loopback is implemented.
CMD-CH 3/4
CMD-CH 1/2
CMD In #1
CMD In #2
CMD In #3
CMD In #4
CMD-OUT-I#1
CMD-OUT-I #2
CMD-OUT-I #3
CMD-OUT-I #4
CMD-OUT-I #1
CMD-OUT-I #2
CMD-OUT-I #3
CMD-OUT-I #4
or
or
or
or
te
mo
Re
loo
CMD slot:port
CMD Out #5
CMD Out #6
CMD Out #7
CMD Out #8
CMD-IN-I #1
CMD-IN-I #2
CMD-IN-I #3
CMD-IN-I #4
CMD slot:port:tributary
CMD-IN-I #1
CMD-IN-I #2
Selected cross connect
CMD-IN-I #3
CMD-IN-I #4
CMD-CH 3/4
Logical AND/OR
CMD-CH 1/2
CMD OUT 5..8 - Secondary
k
ac
pb
CMD OUT 1..4 – Primary
CMD Out #1
CMD Out #2
CMD Out #3
CMD Out #4
Primary CMD selection
Figure 5-33. Remote Loopback Functionality inside TP Cross-Connect
Megaplex-4
Teleprotection Ports (Logical)
5-263
Chapter 5 Cards and Ports
Installation and Operation Manual
Loopback Duration
The activation of a loopback disconnects the remote equipment served by the
Megaplex-4. Therefore, when you initiate a loopback, you have the option to limit
its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires.
The default is infinite duration (without timeout).
Activating the Loopback
To perform a loopback on the cmd-out-i port:
1. Navigate to configure port cmd-out-i <slot>/<port>/<trib>.
The config>port> cmd-out-i>(<slot>/<port>/<trib>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Activating and configuring the
direction of the loopback
loopback remote [duration
<minutes>]
Returns the received data at the
physical layer to the transmitting path.
Using no loopback stops the loopback.
Duration –1 to 30 minutes or infinite
5.34 VCG Ports
Applicable Modules
Virtually concatenated groups (VCGs) can be configured on the following ports:
•
SDH/SONET (CL.2 modules)
•
E1/T1 (VS-16E1T1-EoP modules)
•
T3 (T3 modules).
To prepare Ethernet traffic for efficient transport over the SDH/SONET network,
the traffic is encapsulated using LAPS or GFP encapsulation, before being
transmitted over a virtually concatenated group. Ethernet transport over T3 and
Ethernet transport over E1/T1 is done using GFP encapsulation. Megaplex-4 also
supports the Link Capacity Adjustment Scheme (LCAS), covered by ITU-T Rec.
G.7042.
In Megaplex-4, VCGs are protected by the Ethernet group redundancy. For
description and instructions, refer to Ethernet Group Protection in Chapter 7.
Standards Compliance
Two types of supported encapsulation comply with the following standards:
5-264
VCG Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
•
LAPS (Link Access Protocol – SDH) encapsulation in accordance with ITU-T
Rec. X.86
•
GFP (Generic Framing Procedure) encapsulation in accordance with ITU-T Rec.
G.7041, using the framed mode.
Benefits
Virtual concatenation has the following main advantages:
•
Scalability: allows bandwidth to be selected in relatively small increments, as
required to match the desired payload data rate.
•
Efficiency: the resulting signals are easily routed through a SDH/SONET
network, without wasting bandwidth, and therefore allows for more efficient
utilization of the bandwidth available on existing networks.
•
Compatibility: virtual concatenation requires only the end nodes to be aware
of the containers being virtually concatenated, and therefore is transparent
to the core network elements.
•
Resiliency: individual members of a virtually concatenated group can be freely
routed across the network.
Functional Description
Ethernet over SDH/SONET
To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
The processing is as follows:
5. At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
6. The resulting streams are mapped to the desired VCs/SPEs, also configured by
management. The Path Overhead (POH) byte carried by all the group
members is used to transfer to the far endpoint the information needed to
identify:
Megaplex-4
The relative time difference between arriving members of the virtual
group
The sequence number of each arriving member.
VCG Ports
5-265
Chapter 5 Cards and Ports
Installation and Operation Manual
7. Each member of the virtual group is independently transmitted through the
network. The network need not be aware of the type of payload carried by
the virtual members of the group.
8. At the receiving end, the phase of the incoming VCs/SPEs is aligned and then
the original payload data stream is rebuilt. This requires using a memory of
appropriate size for buffering all the arriving members of the group at the
receiving end. The memory size depends on the maximum expected delay,
therefore to minimize latency the maximum delay to be compensated can be
defined by management.
Encapsulation Modes
Ethernet frames must be encapsulated before transport over the SDH/SONET
network. You can select the desired encapsulation mode, independently, for each
virtually concatenated group. This can be done by binding VCG ports to the
corresponding entity:
•
For LAPS encapsulation, see Configuring HDLC Ports.
•
For GFP encapsulation, see Configuring GFP Ports.
Support for LCAS
Each virtually concatenated group with two or more VCs/VTs can be configured to
support LCAS.
With LCAS, the capacity of a virtually concatenated group can be hitlessly
decreased when one of the VCs/VTs fails; when the failure is no longer present,
the group will automatically and hitlessly recover to return to the normal capacity.
Another LCAS advantage is that it allows setting up a link even when the number
of VCs/VTs at the two endpoints, or anywhere along the trail followed by the VCG,
is not equal.
The user can specify a minimum number of VCs/VTs for the group capacity: if the
number of VCs/VTs decreases below this minimum, an alarm will be generated.
Ethernet over Full/Channelized T3
9. T3 modules allow encapsulating Ethernet traffic with the GFP protocol and
transferring it over full or channelized T3 media. In both cases Ethernet ports are
connected to Logical MAC ports via flows, and these Logical MAC ports are bound
to GFP ports. Starting from the GFP ports, two ways are available:
•
To transfer Ethernet over full T3, only one GFP/Logical MAC port is created
and T3 port is bound directly to it.
•
To transfer Ethernet over channelized T3, up to 16 Logical MAC, GFP and VCG
ports are created, so that the VCG ports are bound to GFP ports and VCG
ports are bound to Logical MAC ports. Up to 16 T1 ports can be bound to
each VCG port, but the total T1 number is limited by 28 T1 ports per T3
module. On the remaining T1s, regular TDM traffic can be mapped.
Figure 5-33 shows the relationship between the entities involved in the Ethernet
over T3/T1 functionality.
5-266
VCG Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Flow
Egress/Ingress Port
ETH Group
Logical MAC
16
Logical MAC
1
Bind 1:1
Bind 1:1
GFP 1
GFP 16
OR
Bind 1:1
VCG 1..16
Bind 1:1
Bind 1:n
T1
T3
Figure 5-34. Logical Entities Representing Ethernet Traffic over Full/Channelized T3 Media
Ethernet over E1/T1
10. VS-16E1T1-EoP modules allow encapsulating Ethernet traffic with the GFP
protocol and transferring it over E1/T1 media. Ethernet ports are connected to
Logical MAC ports via flows, these Logical MAC ports are bound to GFP ports and
GFP ports are bound to VCG ports. Up to 16 E1/T1 or E1-i/T1-i ports can be
bound to each VCG port.
Figure 5-34 shows the relationship between the entities involved in the Ethernet
over E1/T1 functionality.
Megaplex-4
VCG Ports
5-267
Chapter 5 Cards and Ports
Installation and Operation Manual
Flow
Egress/Ingress Port
Logical MAC
16
Logical MAC
1
ETH Group
Bind 1:1
Bind 1:1
GFP 1
GFP 16
Bind 1:1
Bind 1:1
VCG 1
VCG 16
OR
Bind 1:n
E1/T1
Bind 1:n
E1-i/T1-i
Figure 5-35. Logical Entities Representing Ethernet Traffic over E1/T1 Media
Factory Defaults
Megaplex-4 is supplied with all VCG ports disabled.
Configuring VCG Ports
To configure a VCG:
•
At the config>port>vcg (slot/port)# prompt, enter all necessary commands
according to the tasks listed below:
Task
Command
Comments
Assigning short description to a
VCG port
name <string>
Using no name removes the name
5-268
VCG Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Administratively enabling a VCG
port
no shutdown
Using shutdown disables the VCG port
Binding the corresponding
VC/VT/STS-1 to the VCG port
bind vc4-sts3c
<slot>/<port>/<tributary>
bind vc3-sts1
<slot>/<port>/<au4>/
<tributary>
bind vc-vt <slot>/<port>/
<au4>/<tug_3>/<tug_2>
[/<tributary>]
For the allowed ranges, seeTable 5-31.
The connection to a VC or VT/STS
depends on the frame selection
(frame=sdh or frame=sonet)
Using no before the corresponding
command removes the binding
The maximum number of VC-4/STS-3C
containers per system is limited to the
full STM-4/OC-3 capacity of a single CL.2
module.
The maximum number of vc-vt containers
for EoS per CL module is limited to 128.
Binding the T1 internal port of
the T3 module to the VCG port
bind t1
<slot>/1/<tributary t1>
The maximum number of T1 ports bound
to one VCG port is 16.
Binding the E1/T1 external and
internal ports of the VS-16E1T1EoP module to the VCG port
bind t1 <slot>/<port>
The maximum number of E1/T1 or
E1-i/T1-i ports bound to one VCG port is
16.
bind t1-i <slot>/<port>
bind e1 <slot>/<port>
bind e1-i <slot>/<port>
Ports bound to VCG must be defined on
same slot as this VCG port.
The ports bound to a specific VCG must
belong to the same type (no mix is
allowed between e1 and e1-i ports or t1
and t1-I ports).
Enabling the use of the Link
Capacity Adjustment Scheme
(LCAS) on the corresponding
group
lcas
LCAS is relevant only when the group
includes 2 or more VCs/T1s. Therefore for
VC-4 (STS-3c) binding it is relevant only
when STM-4/OC-12 ports are configured
Using no lcas disables the use of LCAS
Selecting the minimum allowed
number of operational
VC/VT/STS/T1s that must remain
in operation. If the number
decreases below the selected
value, an alarm is generated.
minimum-number-of-links
<value>
This parameter is relevant only when
LCAS is enabled.
Selecting the maximum
differential delay (delay
compensation needed for
alignment of low- and
high-order virtually concatenated
payloads in the SONET/SDH
network)
max-differentialdelay <value>
The range is 1 to 256 (in msec)
Megaplex-4
Default: 64 msec
For optimal latency performance of the
ETHoSDH services, it is recommended to
set low values of max-differential-delay
(the minimum value needed for your
application).
VCG Ports
5-269
Chapter 5 Cards and Ports
Installation and Operation Manual
Configuration Errors
The tables below list messages generated by Megaplex-4 when a configuration
error on the VCG ports is detected.
Table 5-75. VCG Configuration Error Messages
Code
Type
Syntax
Meaning
767
Error
CAN'T BIND THE SAME E1/T1
TO DIFFERENT VCGS
The same E1/T1 port cannot be bound to 2 different
VCGs. This error is relevant for VS-16E1T1EOP and T3
modules.
Viewing LCAS Status Information
For viewing the LCAS status information, follow the instructions below.
To view the LCAS status information:
1. Navigate to config>port>vcg> (<slot>/<port>)#
2. Type show status.
The status is displayed.
Example for SDH/SONET:
config>port>vcg(cl-a/2)# show status
Name
: CL-A vcg 02
Administrative Status : Up
Operation Status
: Up
LCAS Status
: All Normal
Members
--------------------------------------------------------------Link
: cl-a/2/1/1/1/2
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/1/1/3
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/2/2/3
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/3/5/1
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/1/2/1
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/2/3/1
Source Status : Norm
5-270
VCG Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/2/5/1
Source Status : EOS
Sink Status
: EOS
Status
: OK
Example for T3:
config>port>vcg(3/1)# show status
Name
: IO-3 vcg 01
Administrative Status : Up
Operation Status
: Up
LCAS Status
: All Normal
Members
----------------------------------------------------------------Link
: 3/1/3
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: 3/1/4
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: 3/1/5
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: 3/1/6
Source Status : EOS
Sink Status
: EOS
Status
: OK
The parameters displayed in the screen are as follows:
Megaplex-4
Administrative
Status
Displays the administrative status of the corresponding VC/VT or T1 link:
Up or Down
Operation Status
Displays the operation status of the corresponding VC/VT or T1 link: Up or
Down
LCAS Status
Displays the LCAS status of the corresponding VC/VT or T1 link:
•
All Normal –all T1/VC/VT ports bound to the selected VCG are active
•
Within Range –number of active T1/VC/VT ports bound to the selected
VCG is not below the value set by the “minimum-number-of-links”
parameter
•
Below Min No of VC –number of active T1/VC/VT ports bound to
the selected VCG and active is below the value set by the “minimumnumber-of-links” parameter
VCG Ports
5-271
Chapter 5 Cards and Ports
Installation and Operation Manual
Link
SDH/SONET: Identifies the position of the corresponding VC or VT within
the STM-1/STM-4 or OC-3/OC-12 frame, using the vc4-sts3c/
tug-3/tug-2/tu format. The Link number also includes the identification of
the link, cl-a/1, cl-a/2, cl-b/1 or cl-b/2.
T3: Identifies the position of the corresponding T1 within the T3 frame,
using the <slot>/1/<t1 tributary> format.
Source Status
Displays the state of the corresponding VC/VT (SDH/SONET) or T1 (T3
module) on the local end of the path serving the selected VCG (that is, the
end located on the Megaplex-4 to which the supervisory terminal is
connected):
•
Fixed – the end uses the fixed bandwidth (not LCAS)
•
Add – the corresponding VC/VT or T1 is about to be added to the VCG
•
Norm – normal transmission state
•
EOS – end-of-sequence indication
•
Idle – the corresponding VC/VT or T1 is not part of the VCG, or is about
to be removed from the group
•
DNU – do not use the corresponding VC/VT or T1, for example,
because the sink side reported a failure.
The state is correct at the time the command to display this screen has
been received by the Megaplex-4.
Sink Status
Same as above for the sink side (remote end of the path).
Status
Displays the member status of the corresponding VC/VT or T1 link: OK or
Failed
Displaying LCAS Statistics
VCG ports feature the collection of LCAS statistical diagnostics.
To display the LCAS statistics:
•
At the prompt config>slot>port>vcg (<slot><port>)#, enter show statistics
followed by parameters listed below.
Task
Command
Comments
Displaying statistics
show statistics {all | current}
•
current –Displays the current
statistics
•
all –Displays all statistics: first
current interval statistics, then
statistics for all valid intervals
Displaying statistics
for a specific interval
show statistics interval <interval-num 1..96>
LCAS statistics are displayed. The counters are described in the table
below. For example:
Current Statistics (SDH/SONET):
config>port>vcg(cl-a/2)# show statistics current
Current
5-272
VCG Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
----------------------------------------------------------------Time Elapsed (Sec)
: 644
Valid Intervals
: 3
Number of Active VCs/VTs
: 4
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0
Current Statistics (T3):
config>port>vcg(3/1)# show statistics current
Current
---------------------------------------------------------------Time Elapsed (Sec)
: 444
Valid Intervals
: 96
Number of Active Links
: 4
Maximum Number of Active Links : 4
Minimum Number of Active Links : 0
Statistics for interval 2 (SDH/SONET):
config>port>vcg(cl-a/2)# show statistics interval 2
Interval
---------------------------------------------------------------Interval Number
: 2
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0
Under Minimum Limit Time
: 0
Statistics for interval 2 (T3):
config>port>vcg(3/1)# show statistics interval 2
Interval
---------------------------------------------------------------Interval Number
: 2
Maximum Number of Active Links : 4
Minimum Number of Active Links : 0
Under Minimum Limit Time
: 0
Table 5-76. LCAS Statistics Parameters
Parameter
Description
Time elapsed (Current
statistics only)
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds
Valid Intervals (Current
statistics only)
The number of elapsed finished 15-min intervals for which statistics data can
be displayed, in addition to the current (not finished) interval (up to 96)
Interval number (Selected
interval statistics only)
Number of interval for which statistics is displayed
Number of Active
VCs/VTs/Links (Current
statistics only)
Displays the current number of active VCs/VTs (for SDH/SONET) or T1 links
(for T3 modules) reported for the corresponding VCG
Maximum Number of Active
VCs/VTs/Links
Displays the maximum number of active VCs/VTs(for SDH/SONET) or T1 links
(for T3 modules) reported for the corresponding VCG during the selected
interval
Megaplex-4
VCG Ports
5-273
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Description
Minimum Number of Active
VCs/VTs/Links
Displays the minimum number of active VCs/VTs(for SDH/SONET) or T1 links
(for T3 modules) reported for the corresponding VCG during the selected
interval
Under Minimum Limit Time
(Selected interval statistics
only)
Displays the accumulated time, in seconds, during which the number of
active VCs/VTs (for SDH/SONET) or T1 links (for T3 modules) for the
corresponding VCG has been less than the configured minimum allowed
number
There are two options for clearing LCAS statistics data:
•
Clearing current interval statistics
•
Clearing all statistics, except for the current interval.
To clear the current interval statistics:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
To clear all statistics data except for from the current interval:
1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-all.
The statistics for the specified entity are cleared.
5.35 Voice Ports
Applicable Modules
Voice ports are available on the following modules:
Note
•
VC-4, VC-8 and VC-16
•
VC-4A, VC-8A
•
VC-4/OMNI
•
VC-6/LB
•
VS voice modules (VS-6/FXS, VS-6/FXO, VS-6/E&M, VS-8/E&M and FXS/E&M)
•
PW-enhanced VS voice modules (VS-6/FXS/PW, VS-6/FXO/PW and
VS-6/E&M/PW
•
When the information is applicable to both basic and advanced version of the
module, the basic name (such as VS-6/FXS) is used in this manual. The complete
designation is used only for information applicable to a specific PW-enhanced
version.
•
5-274
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
The following table shows the number of voice ports on each Megaplex-4 I/O
module.
Table 5-77. Megaplex-4 Voice Ports
Module
Number of Ports
VC-4/OMNI
4
VC-4A/8A
4/8
VC-4/8/16
4/8/16
VC-6/LB
6
VS-6/FXS, VS-6/FXS/PW
8
VS-6/FXO, VS-6/FXO/PW
8
VS-6/E&M, VS-6/E&M/PW
4
VS-8/E&M
8
FXS/E&M
8(FXS)+4(E&M)
Analog voice interface modules, VC-4, VC-8 and VC-16, provide 4, 8 or 16
PCM-encoded toll-quality voice channels (ports). The modules are available in
three models:
•
E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464 Types I, II, III
and V, and BT SSDC5.
•
FXS: 2-wire interfaces for direct connection to telephone sets.
•
FXO: 2-wire interfaces for direct connection to PBX extension lines
VC-4A and VC-8A modules are analog voice interface module similar to VC-4 and
VC-8, except that they also support ADPCM.
The VC-6/LB module is used for connection of local battery-powered (LB)
telephones. It provides 6 voice channels using toll-quality 64 kbps PCM voice
encoding in compliance with ITU-T Rec. G.711 and AT&T Pub. 43801.
A special ”omnibus“ VC-4/OMNI module provides four toll-quality voice channels
for applications where a master site needs to communicate with multiple remote
stations simultaneously (such as to broadcast an important message).
The VS voice modules (VS-6/FXS, VS-6/FXO, VS-6/E&M, VS-8/E&M and FXS/E&M)
provide 8 FXS, 8 FXO, 8 E&M or 4 E&M toll-quality analog voice channels.
The following parameters can be configured for the voice ports:
Megaplex-4
•
Port name
•
Administrative status
•
End-to-end signaling transfer method
•
Pulse metering frequency for FXO/FXS channels (VC modules only)
•
Number of wires for E&M channels
•
Specifying the compression method used in the ADPCM encoding.
•
Analog signaling method for FXO/FXS channels
Voice Ports
5-275
Chapter 5 Cards and Ports
Installation and Operation Manual
•
Analog signaling profile (VS voice modules only)
•
E&M signaling standard
•
Impedance for FXS and FXO modules (VS voice modules only)
•
Cadence for FXS and FXO modules (VS voice modules only)
Standards Compliance
The Megaplex-4 voice ports comply with following standards:
Modulation Technique
PCM: per ITU-T Rec. G.711 and AT&T Pub. 43801
ADPCM: per ITU-T G.726 and G.727
Echo Cancellation
ITU-T G.168
Analog Interface
ITU-T Rec. G.712
E&M Signaling Method
• EIA RS-464 Type I
• EIA RS-464 Type II, III and V (British Telecom
SSDC5) using internal -12 VDC in place of -48 VDC
FXS/FXO Signaling Modes • EIA RS-464 loop-start and wink-start
End-to-End Signaling for
E1 Uplinks
User-selectable as per ITU-T Rec. G.704, para. 3.3.32
Functional Description
All the VC/VS voice modules provide high-quality voice channels. The functional
difference between the various modules is in the signaling interface and mode.
The analog interface depends on the module type:
•
VC-4/4A/8/8A/16 E&M modules: user-selectable for 2-wire or 4-wire
•
VC-4/4A/8/8A/16 FXS/FXO and VC-6/LB modules: always 2-wire
•
VC-4/OMNI modules: always 4-wire
•
E&M submodules of VS voice modules: user-selectable for 2-wire or 4-wire
•
FXS/FXO submodules of VS voice modules: always 2-wire
Voice encoding method for all VC-4A and VC-8A module versions is
user-selectable for either toll-quality 64 kbps PCM or 32/24 kbps ADPCM. The
VC-4, VC-8, VC-16, VS-6/E&M, FXS/E&M, VS-6/FXS, and VS-6/FXO modules
feature only PCM encoding.
The user can select the companding law, µ-law or A-law, in accordance with
system requirements. In accordance with ITU-T Rec. G.711, the A-law should be
used on E1 trunks and the µ-law should be used on T1 trunks. However, the user
can select the desired companding law, µ-law or A-law, in accordance with the
specific system requirements.
5-276
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
To increase application flexibility, the nominal audio transmit and receive levels of
all the module versions can be adjusted over a wide range (see Table 5-79).
Table 5-78. Transmit and Receive Levels for Various Interfaces
Module Interface
Transmit
[dbm]
Receive
[dbm]
min
max
min
max
E&M regular
-10
+5
-17
+3.5
E&M 4W enhanced
-17
+5
-17
+9
FXS
-5
+5
-17
+1
LB
-17
+8
-23
+2
FXO
-3.5
+5
-17
+1
E&M 2/4 wire mixed
-8
+5
-17
+2
E&M 4 wire only
-17
+5
-17
+9
FXS/FXO
-5
+5
-17
+1
VC modules
VS voice modules
Due to the high quality audio reproduction, DTMF signaling is transparently
transferred, inband. Therefore, the user can use DTMF signaling as usual, e.g.,
can operate the telephone set keypad to access voice mail systems, interactive
systems, etc.
The VC-4A and VC-8A modules use G.168 standard for echo cancellation (up to
4 ms per channel).
For VS voice modules, pulse metering frequency is not supported.
For more information, see also the following sections in the Megaplex-4 I/O
Modules Installation and Operation Manual:
•
VC-4/VC-4A/VC-8/VC-8A/VC-16, VC-6/LB and VC-4/OMNI sections in Voice
Modules chapter
•
VS Voice section in Versatile Modules chapter.
Factory Defaults
Megaplex-4 is supplied with all voice ports disabled. Other parameter defaults are
listed in the table below.
Megaplex-4
Parameter
Default Value
coding
a-law
Voice Ports
5-277
Chapter 5 Cards and Ports
Installation and Operation Manual
Parameter
Default Value
no signaling (disabled)
Note: this default value is not used in the
signaling
VC-6/LB module and must be changed to one of
the other options, as explained in the
configuration section.
analog-signaling-profile
sig_over_a_bit
meter-rate
12khz
wires
2
compression
no compression (disabled)
analog-signaling
loop-start
e-m-type
ssdc5
echo-canceler
no echo-canceler (disabled)
operation-mode
ptp
signaling-feedback
no signaling-feedback (disabled)
tx-gain
0 dbm
rx-sensitivity
0 dbm
impedance
600
cadence
local
loop-disconnect-time
250msec
forward-disconnect
250msec
duration
infinite
omni-signaling
legacy
disconnect-tone
no disconnect-tone (disabled)
ring-voltage
normal
Configuring External Voice Port Parameters
The sets of configurable parameters are different for voice ports of VC modules
and VS voice modules.
To configure the external voice port parameters for VC modules:
3. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
4. Enter all necessary commands according to the tasks listed below.
5. For VC modules:
5-278
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Assigning short
description to port
name <string>
Using no before name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying the
companding law to be
used by the voice
channels
coding {a-law | u-law}
a-law - A-law coding, intended for use on
E1 links
Specifying the
end-to-end signaling
transfer method for voice
modules
signaling {rbmf | cas | rbf}
u-law -µ-law coding, intended for use on T1
links
This command is relevant for
VC-4/4A/8/8A/16 and VC-6/LB modules. For
VC-4/OMNI modules, see omni-signaling
command.
The signaling transfer options depend on
the type of link module installed in the
Megaplex chassis:
•
with T1 link modules, RBMF and RBF is
used
•
with E1 link modules, CAS and RBF is
used
rbf – proprietary “robbed bit” signaling
method that does not require multiframe
synchronization, used as follows:
•
7-bit PCM with channel signaling carried
by the 8th bit of each channel
•
3-bit ADPCM with channel signaling
carried by the 4th bit of each channel
when using G.727
For VC family modules, the RBF option is
used for VC-4A/VC-8A and VC-6/LB only.
rbmf – robbed bit signaling in accordance
with AT&T Pub 43801.
cas – Channel-associated signaling in
accordance with ITU-T Rec. G.704.
Using no signaling means that channel
signaling is not transferred (not used in the
VC-6/LB module)
Specifying the
end-to-end signaling
transfer method for
VC-4/OMNI modules
omni-signaling {legacy | abcd}
legacy
The channel uses legacy signaling
(used by the uplink port connected
to this channel)
abcd
The channel uses RAD proprietary
signaling for VC-4/OMNI modules
Using no omni-signaling means that channel
signaling is not transferred
Specifying the pulse
metering frequency
Megaplex-4
meter-rate { 16khz | 12khz }
This feature is supported only on FXS and
FXO modules in PCM mode
Voice Ports
5-279
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Specifying the interface
to be used by the voice
channels
wires {2 | 4}
Selection between 2-wire and 4-wire
interface is available only for the
VC-4/4A/8/8A/16 E&M modules. Can be
independently selected for each pair of
channels (1, 2; 3, 4; etc.).
Specifying the
compression method
used in the ADPCM
encoding
compression {g726 | g727}
Always use G.727 when working with RBF or
RBMF signaling.
If PCM encoding is used, a sanity error is
sent.
Using no compression disables compression
Specifying the analog
signaling method used
for all FXO/FXS channels
analog-signaling {loop-start | wink-start}
Specifying the E&M
signaling standard
e-m-type {1 | 2 | 3 | ssdc5}
Can be selected only for FXO and FXS
modules operated in PCM mode.
For VC-4, VC-4A, VC-8 and VC-8A modules,
the selection is made for the entire group
of all the module channels. For VC-16
modules, the selection can be separately
made for each group of eight channels: 1 to
8 and 9 to 16.
This selection is available only for E&M
modules. The E&M signaling type can be
independently selected for each group of
four channels 1, 2, 3, 4; 5, 6, 7, 8; etc.).
Note: For the E&M/POS module, select 2
only.
Enabling the built-in
adaptive echo canceller,
supporting up to a 4
msec delay
echo-canceler
Setting the operating
mode of the channel for
VC-4/OMNI modules
operation-mode {ptp | omni-bus |
p2mp-dst | p2mp-src}
5-280
Voice Ports
This option is relevant only for VC-4A and
VC-8A modules.
Using no before echo-canceler disables
echo canceling
This parameter is valid only for
VC-4/OMNI modules:
•
omni-bus – The channel is operated in
an “omnibus” (conference call)
application.
•
ptp – The channel is operated as a
regular E&M voice channel.
•
p2mp-dst –The channel is operated as a
destination (remote station) in a pointto-multipoint application
•
p2mp-src –The channel is operated as a
source (master) in a point-to-multipoint
application.
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Controlling the use of
signaling feedback for
FXO modules
signaling-feedback
Available only for FXO modules.
For VC-4, VC-4A, VC-8 and VC-8A, the
selection should be the same for all the
module channels. For VC-16 modules, the
selection can be separately made for each
group of eight channels: 1 to 8 and 9 to 16.
This is done by forcing the last choice
(signaling-feedback/no signaling-feedback)
to all the module/group ports.
Using no before signaling-feedback disables
the signaling feedback.
Selecting the nominal
input level of the
transmit path
tx-gain <value in dbm>
The input level can be set in 0.5 dB steps in
the range of +8 dBm to -17 dBm, depending
on the module type (see Table 5-79).
Selects the nominal
output level of the
receive path
rx-sensitivity <value in dbm>
The output level can be set in 0.5 dB steps
in the range of +9 dBm to -23 dBm,
depending on the module type (see
Table 5-79).
Enabling the “end of
speech” signal (short
tones) on hanging up on
the partner side
disconnect-tone
FXS modules only
Using “no disconnect-tone” disables the
tone
To configure the external voice port parameters for VS voice module:
1. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short
description to port
name <string>
Using no before name removes the name
Administratively enabling
port
no shutdown
Using shutdown disables the port
Specifying the
companding law to be
used by the voice
channels
coding {a-law | u-law}
a-law - A-law coding, intended for use on
E1 links
Megaplex-4
u-law -µ-law coding, intended for use on T1
links
Voice Ports
5-281
Chapter 5 Cards and Ports
Installation and Operation Manual
Task
Command
Comments
Specifying the
end-to-end signaling
transfer method for voice
modules
signaling {rbmf | cas | rbf}
The signaling transfer options depend on
the type of link module installed in the
Megaplex chassis:
•
with T1 link modules, RBMF and RBF is
used
•
with E1 link modules, CAS and RBF is
used
RBF is a proprietary “robbed bit” signaling
method that does not require multiframe
synchronization, it is supported by E&M
module only.
Using no signaling means that channel
signaling is not transferred
Specifying the interface
to be used by the voice
channels
wires {2 | 4}
Selection between 2-wire and 4-wire
interface is available only for the E&M
modules.
Can be independently selected for each
channel.
Specifying the analog
signaling method used
for all FXO/FXS channels
analog-signaling {loop-start | wink-start}
Can be selected only for FXO and FXS
modules.
Specifying the E&M
signaling standard
e-m-type {1 | 2 | 3 | ssdc5 | positive}
This selection is available only for E&M
modules.
The E&M signaling type can be
independently selected for each group of
four channels 1, 2, 3, 4; 5, 6, 7, 8; etc.)
Controlling the use of
signaling feedback for
FXO modules
signaling-feedback
This parameter is available only for FXO
modules and is needed when FXO is working
opposite E&M interface.
Using no before signaling-feedback disables
the signaling feedback.
Selecting the nominal
input level of the
transmit path
tx-gain <value in dbm>
The input level can be set in 0.5 dB steps in
the range of +5 dBm to -17 dBm, depending
on the module type (see Table 5-79).
Selects the nominal
output level of the
receive path
rx-sensitivity <value in dbm>
The input level can be set in 0.5 dB steps in
the range of +9 dBm to -17 dBm, depending
on the module type (see Table 5-79).
Specifying the analog
signaling profile
analog-signaling-profile <profile-name>
By default the analog signaling profile shall
be sig_over_a_bit
Specifying the line
impedance
impedance {600 | 900}
Available only for FXS/FXO modules
5-282
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Specifying if the cadence
of the ring is generated
locally or translated
directly from the received
signaling bit
cadence {local | transparent}
Available only for FXS/FXO modules
Specifying the amount of
time during which the
battery voltage is
disconnected by the FXS
port after a far-end
notification has been
received
forward-disconnect {250msec | 500msec |
750msec | 1sec | 2sec}
Available only for FXS modules
Specifying the amount of
time of momentary
battery voltage removal
that will be detected by
the FXO port
loop-disconnect-time {250msec | 500msec
| 750msec | 1sec | 2sec}
Avaliable only for FXO modules
Specifying the ring
voltage value
ring-voltage {normal | high}
Available only for FXS ports:
•
normal – 54 Vrms
•
high – 85 Vrms
For each pair of FXS ports (1..2, 3..4, 5..6,
7..8) - once one of the ports is configured
with a Ring Voltage value of 'high', the
second port shall be set to shutdown.
Example
The following section illustrates how to configure the voice FXS port 1 on the
VC-8 module installed in slot 9:
•
Set -µ-law coding
•
Set CAS signaling
•
Administratively enable the port
•
Leave all other parameters disabled or at their defaults.
config# #----------vc8fxs----------------config# port voice 9/1 no shutdown
config# port voice 9/1 coding a-law
config# port voice 9/1 signaling cas
Configuring Internal Voice Port Parameters
To configure the internal voice port parameters (VC-4/OMNI only):
6. Navigate to configure port voice <slot>/<port>/<tributary> to select the
internal voice port to configure.
The config>port>voice>(<slot>/<port>/<tributary>)# prompt is displayed.
Megaplex-4
Voice Ports
5-283
Chapter 5 Cards and Ports
Installation and Operation Manual
7. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to port
name <string>
Using no before name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Specifying the end-to-end signaling
transfer method for VC-4/OMNI
modules
omni-signaling {legacy | abcd}
Using no before omni-signaling means that
channel signaling is not transferred
Configuration Errors
Table 5-80 and Table 5-81 list messages generated by Megaplex-4 when a
configuration error on voice modules is detected.
Table 5-79. VC and VS Voice Modules Configuration Error Messages
Code
170
Type
Error
Syntax
Meaning
ILLEGAL SIGNALING METHOD
You can select the channel associated signaling method
only when an E1 module port with G.732S framing is used.
You can select the robbed bit multiframe signaling transfer
method only for E1 links with G.732S framing, or on T1
links.
171
Warning VOICE CODING LAW (E1/T1)
MISMATCH
The selected voice companding law differs from the
companding law specified by the standards: the A-law is
generally used for E1 links, and the µ-law is generally used
on T1 links
172
Error
TX GAIN VALUE OUT OF RANGE The transmit gain selected for the specified channel is not
within the supported range
173
Error
RX SENSITIVITY VALUE OUT OF
RANGE
The receive sensitivity (gain) selected for the specified
channel is not within the supported range
174
Error
OOS/INTERFACE MISMATCH
The selected OOS mode cannot be used on this type of
interface
175
Error
SIGNALING PROFILE/INTERFACE The selected profile cannot be used on this type of
MISMATCH
interface
176
Error
ILLEGAL NUMBER OF WIRES
Voice modules with /FXO and /FXS interfaces support only
the two-wire interface.
For voice modules with /E&M interface only, it is possible
to select two-wire or four-wire interfaces. In addition, for
VC-4/4A/8A/16 modules with /E&M interface, the same
interface type must be selected for consecutive pairs of
channels (for example, 1, 2 or 15, 16)
177
5-284
Error
NO SIGNALING IS ILLEGAL FOR
THIS INTERFACE
Voice Ports
The selected interface cannot be used with no signaling –
the signaling option must be specified
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Code
Type
Syntax
Meaning
179
Error
ILLEGAL ANALOG SIG
COMBINATION
For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of
analog-signaling parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
180
Error
ILLEGAL FXO SIG FEEDBACK
COMBINATION
For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of
signaling-feedback parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
181
Error
ILLEGAL TS SPLIT CONFIG FOR
ADPCM MODE
Split timeslot cross-connect must be peformed on a pair
of ports (1,2 or 3,4..)
182
Error
TX/RX GAIN LEVEL MUST BE
SET IN 0.5 dB STEPS
Step value is not legal for VS voice modules.
750
Error
NUM OF BI-DIRECTION-RX TS
EXCEEDS 30
The number of bidirection-rx timeslots cross-connected to
the voice port in VS voice modules cannot exceed 30.
763
Error
SERIAL PORT/PW BANDWIDTH
MISMATCH
In VS modules, the serial port rate must match the number
of timeslots on this serial port listed in the cross-connect
pw-tdm command.
764
Error
ILLEGAL RING VOLTAGE/PORTS For each pair of channels (1-2, 3-4, 5-6 or 7-8) only one
ADMIN COMBINATION
channel can be set to 'high' ring voltage.
Table 5-80. VC-4/OMNI Configuration Error Messages
Code
Type
Syntax
Meaning
241
Error
ONLY FIRST TRIBUTARY CAN
BE CONNECTED
If operation-mode is ptp, only the first tributary channel
of this voice port can be connected. All the other tributary
channels must be set to shutdown.
242
Error
FIRST TRIBITURY MUST BE
CONNECTED
If the operation-mode is p2mp-dst, and the first internal
channel is not connected, the other internals cannot be
connected and cannot carry traffic.
Viewing a Voice Port Status
Follow the instructions below for viewing the status of a voice port.
To view the voice port status:
•
At the config>port>voice(<slot>/<port>/<tributary>)# prompt, enter show
status.
The status information appears as illustrated below.
Note
<tributary> relates to VC-4/OMNI modules only.
config>port>voice(3/1)# show status
Megaplex-4
Voice Ports
5-285
Chapter 5 Cards and Ports
Installation and Operation Manual
Name
Administrative Status
Operation Status
HW Type
Loopback Type
: IO-3 voice 01
: Up
: Up
: EM 4W EXT GAIN
: None
The status display provides information about:
Administrative and operational status
Loopback Type – Status of loopback activated on the port (None, Local,
Remote, Tone Inject Forward, Tone Inject Backward)
Module hardware type according to the following table:
Table 5-81. VC Module Hardware Types
Displayed String
Module Description
Ordering Option
"FXS RP MP"
Reverse polarity & Metering
FXS/MET,
FXS/RJ/MET
"FXS RP NO MP"
Reverse polarity & No Metering
FXS, FXS/RJ
“FXO RP MP"
Reverse polarity & Metering
FXO/MET,
FXO/RJ/MET
"FXO RP NO MP"
Reverse polarity & No Metering
FXO, FXO/RJ
"EM 4W EXT GAIN”
4W only, with enhanced gain
levels
E&M/4WIRE
"EM 2W/4W"
Regular 2w & 4w
E&M, E&M/EXT
"EM 2W/4W DS"
Double Signaling
E&M/DS
"EM 2W/4W POS 5/12 V"
Positive signaling voltage, 5/12V
E&M/POS
"EM 2W/4W POS 24V"
Positive signaling voltage, 24V
E&M/RJ/POS/24
Testing Voice Ports
The test and diagnostics functions available on each voice channel are:
Note
•
Local digital loopback
•
Remote digital loopback
•
Forward tone injection
•
Backward tone injection.
VC-6/LB modules support only forward tone injection.
Local Digital Loopback (Local Loop)
The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
5-286
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
While the loopback is connected, the local voice channel should receive its own
signal, e.g., a strong sidetone should be heard in the earpiece if the channel is
connected to a telephone set.
The loopback signal path is shown in Figure 5-35.
Channel 1
User or
Test
Equipment
..
...
.
..
..
.
..
..
.
..
..
.
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-36. Local Loopback, Signal Path
Note
When working in the ADPCM mode, the local digital loopback towards the local
user equipment is performed for each pair of consecutive channels (1-2, 3-4,
etc.)
Remote Digital Loopback (Remote Loop)
The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote voice channel should receive its own
signal, e.g., a strong sidetone should be heard in the earpiece if the channel is
connected to a telephone set.
The loopback signal path is shown in Figure 5-36.
Megaplex-4
Voice Ports
5-287
Chapter 5 Cards and Ports
Installation and Operation Manual
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-37. Remote Loopback, Signal Path
Forward Tone Injection
The test tone is a data sequence repeating at a rate of 1 kHz. This data sequence
is identical to the data sequence that would have been generated if a 1-kHz
signal having a nominal level of 1 mW (0 dBm0) were applied to the input of the
channel codec.
The tone is injected to the local transmit path multiplexer, instead of the transmit
signal of the channel. The signal received from the other end remains connected
to the local subscriber.
While the forward tone injection is activated, the remote user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 5-37 shows the signal path.
5-288
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
Test
~ Tone
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-38. Forward Test Tone Injection Path
Backward Tone Injection
When the backward test tone injection is enabled, the test tone (a data sequence
repeating at a rate of 1 kHz) is injected to the local receive input of the channel
decoder, instead of the received signal of the channel, and the resulting analog
signal is supplied to the local subscriber. The signal received from the other end is
disconnected from the local subscriber.
While the backward tone injection is activated, the local user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 5-38 shows the signal path.
Megaplex-4
Voice Ports
5-289
Chapter 5 Cards and Ports
Installation and Operation Manual
..
..
.
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
Test
Tone
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-39. Backward Test Tone Injection Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4 before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks and Tone-Inject Tests
To perform a loopback on the voice port:
8. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
9. Enter all necessary commands according to the tasks listed below.
5-290
Voice Ports
Megaplex-4
Installation and Operation Manual
Chapter 5 Cards and Ports
Task
Command
Comments
Activating and
configuring the
direction of the
loopback and the
duration of it (in
seconds)
loopback {local | remote} [tone-inject]
[duration <duration in minutes 1..30> ]
local – local loopback
Megaplex-4
remote – remote loopback
local tone-inject – backward tone
injection (not for VC-6/LB modules)
remote tone-inject – forward tone
injection
Voice Ports
5-291
Chapter 5 Cards and Ports
5-292
Voice Ports
Installation and Operation Manual
Megaplex-4
Chapter 6
Management and Security
6.1
Access Control List (ACL)
Access control lists are used to flexibly filter and mark incoming network traffic.
Standards and MIBs
Relevant sections of RFC 1812
Benefits
The service providers use the ACLs to maintain the network security by
preventing the malicious traffic from entering the device.
Functional Description
Devices featuring ACLs can flexibly filter management traffic, by denying or
permitting IP packets to enter entities in the device, according to the packet’s
source address, protocol type or other criteria.
ACL entries are sequentially numbered rules, or ACEs (Access Control Elements)
containing statements (Deny, Permit) and conditions. You can create up to 3 ACL
and up to 128 ACEs per system.
Packets are permitted or denied access, based on the following conditions:
•
IP source address
•
TCP and UDP port.
The ACL structure is illustrated in the Example section.
If there is a need to add a rule between already existing rules with consecutive
numbers, the rules can be interspaced to accommodate additional rules between
them.
Binding Access Control Lists
Once created, ACLs are applied (bound) to the virtual management entity for
filtering management traffic (only inbound direction is supported).
Filtering
Packets attempting to enter an entity to which the ACL is bound are checked
against the access list rules, one by one. Access of matching packets is denied
(packets are dropped) or permitted, as directed by the ACL statement.
Megaplex-4
Access Control List (ACL)
6-1
Chapter 6 Management and Security
Installation and Operation Manual
Packets matching a Deny statement (rule) are dropped unless permitted by a
previous rule.
Packets matching a Permit statement (rule) are permitted to access an entity
unless denied by a previous statement.
After a match, the rest of the rules are ignored. Packets not matching any rule
are dropped. Empty ACLs deny access of all packets matched to them.
Statistics
The device collects ACL statistics per management entity. The statistic counters
include the number of rule matches that occurred since the counters were last
cleared. The statistic counters are cleared upon device reboot. The user may also
clear ACL statistics of any entity and direction pair.
Factory Defaults
By default there are no ACL lists configured.
Configuring ACL
The ACL configuration tasks are performed at the access control and
management levels.
To configure an ACL:
1. Create an access control list.
2. Add deny and permit rules to the ACL.
3. Bind the ACL to a management entity
Access-Control-Level Tasks
The following commands are available in the CLI access-control context:
config>access-control#. The exception to this are the deny and permit
commands, which are performed in the access-list(acl_name) context:
configure>access-control>access-list(acl_name)#.
Table 6-1. Access-Control-Level Commands
Task
Command
Comments
Creating and
deleting an ACL
access-list <acl_name>
You can create up to 3 ACLs per system.
Creating an ACL is performed by assigning
a name. The ACL names must be unique
and contain up to 252 alphanumeric
characters.
6-2
no access-list <acl_name>
Access Control List (ACL)
Megaplex-4
Installation and Operation Manual
Chapter 6 Management and Security
Task
Command
Comments
Adding deny
rules to an ACL
deny {tcp | udp} <src-address>[<src-portrange>] <dst-address>[<dst-port>] [log]
[sequence <sequence-number>]
Management-bound ACLs have the
following configuration limitations:
•
<src-port-range> must be any port –
do not indicate specific ports
•
The destination IP address (<dstaddress>) must be any
•
The destination port must be tcp/23
(Telnet), tcp/22 (SSH) or udp/161
(SNMP)
Sequence number range is 1–
2147483648.
log – not in use in the current version
Adding permit
rules to an ACL
permit {tcp | udp} <src-address>[<src-portrange>] <dst-address> [<dst-port-range>]
[log] [sequence <sequence-number>]
Management-bound ACLs have the
following configuration limitations:
•
<src-port-range> must be any port –
do not indicate specific ports
•
The destination IP address (<dstaddress>) must be any
•
The destination port must be tcp/23
(Telnet), tcp/22 (SSH) or udp/161
(SNMP)
Sequence number range is 1–
2147483648.
log – not in use in the current version
Removing rules
from an ACL
delete <sequence-number>
The value range is 1–2147483647
seconds
Setting the
logging interval
of all ACLs
logging access-list <value>
Enable logging at the maximum rate of the
value set at Access Control level.
no logging access-list
no logging access-list disables event
logging for all rules in the ACL.
Management-Level Tasks
The following commands are available in the CLI management context:
configure>management>access#.
Table 6-2. Management-Level Commands
Task
Command
Comments
Binding the ACL to a
management entity
access-group <acl-name> in
no access-group
The management entity supports the ACLs
only in the in direction.
Displaying ACL statistics
show access-list statistics
See Displaying Statistics below.
Clearing ACL statistics
clear-statistics access-list
Megaplex-4
Access Control List (ACL)
6-3
Chapter 6 Management and Security
Displaying the summary
of ACLs bound to a
management entity
Installation and Operation Manual
show access-list summary
Displays ACL status at the current level
See Displaying Status below
Example
To create an ACL:
The example below illustrates a typical ACL applied to the incoming management
traffic:
•
Allows SNMP (UDP port 161) traffic from source 172.17.170.81/32
•
Allows SSH (TCP port 22) traffic from source 172.17.170.81/32
•
Allows Telnet (TCP port 23) traffic from source 172.17.170.81/32
configure
access-control
access-list mng1
permit udp 172.17.170.81/32 any 161 sequence 1
permit tcp 172.17.170.81/32 any 22 sequence 2
permit tcp 172.17.170.81/32 any 23 sequence 3
Note
You cannot edit a rule with the same sequence number. To edit a rule, delete the
existing one and create a new rule with a new sequence number.
The table below summarizes the rules configured for the ACL. Items in red are
either implied or unavailable for the current parameter or serve as system
settings that cannot be changed.
Sequence
Action
Protocol
Source IP
TCP/UDP
Number
Dest. IP
TCP/UDP Dest. Port
Source Port
1
Permit
UDP
172.17.170.81/32
Any
Any
161
2
Permit
TCP
172.17.170.81/32
Any
Any
22
3
Permit
TCP
172.17.170.81/32
Any
Any
23
Displaying Status
The ACL status displays information on the ACL name, type (IPv4), the entity that
the ACL is bound to and its direction. The status information is available for the
ACLs at the management access levels.
To display the ACL status:
•
In the config>mngmnt>access# prompt, enter the show access-list summary
command.
The following status information is displayed:
ACL
6-4
Name
Access Control List (ACL)
Type
Bound to
Direction
Megaplex-4
Installation and Operation Manual
Chapter 6 Management and Security
--------------------------------------------------------------mng1
IPv4
management inbound
Displaying Statistics
The ACL statistic counters gather information on the number of rule matches
registered on the ACL since the last reboot or counter clearing.
Note
All ACLs have an implied last rule that denies all packets. The device does not
provide statistic counters for this rule. If you intend to collect statistics on the
number of the packets discarded by the default ACL mechanism, you must add
the deny ip any any rule at the end of the ACL.
To display the ACL statistics:
•
In the config>mngmnt>access# prompt, enter the show access-list statistics
command.
The following statistic information is displayed:
IPv4 access list: mng1
(in)
Bound to: Management
Matches counted for: 0 days 0 hours 2 minutes 33 seconds
--------------------------------------------------------------10
permit tcp 172.17.154.154/24 any 22 (0 matches)
20
permit tcp 172.17.154.154/24 any 23 (0 matches)
30
permit udp 172.17.154.154/24 any 161 (0 matches)
6.2
Access Policy
The access policy allows specifying up to three user authentication methods
(local, RADIUS, TACACS+). If an authentication method is not available or the user
is not found, the next method is used if applicable.
Factory Defaults
By default, authentication is via the locally stored database (1st-level local).
Configuring Access Policy
To define the access policy:
•
Megaplex-4
In the config>mngmnt>access# prompt, enter the necessary commands
according to the tasks listed below.
Access Policy
6-5
Chapter 6 Management and Security
Installation and Operation Manual
Task
Command
Comments
Specifying authentication method
preferably via RADIUS/TACACS+, then
optionally TACACS+/RADIUS, then
optionally local
auth-policy 1st-level radius [2nd-level
tacacs+ [3rd-level {local | none}]]
Megaplex-4 first attempts authentication via
the server specified by 1st-level. If the
server does not answer the authentication
request, then Megaplex-4 attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then Megaplex-4
attempts to authenticate according to
3rd-level:
auth-policy 1st-level tacacs+ [2nd-level
radius [3rd-level {local | none}]]
•
local – Megaplex-4 authenticates via the
local database
•
none –No further authentication is
done, and the authentication request is
rejected.
Note: If at any time in this process, an
authentication server rejects an
authentication request, Megaplex-4 ends
the authentication process and does not
attempt authentication at the next level.
Specifying authentication method
preferably via TACACS+, then
optionally local
auth-policy 1st-level tacacs+ [2nd-level {
local | none } ]
If 2nd-level is set to local, authentication is
performed via the TACACS server. If the
TACACS server does not answer the
authentication request, then Megaplex-4
authenticates via the local database. .If the
TACACS server rejects the authentication
request, Megaplex-4 ends the
authentication process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
6.3
Authentication via RADIUS Server
Megaplex-4 provides connectivity to up to four Radius authentication servers. You
have to specify access parameters such as assigning Radius server IDs, specifying
the associated server IP addresses and the number of retries.
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS).
RFC 2618, RADIUS Authentication Client MIB.
6-6
Authentication via RADIUS Server
Megaplex-4
Installation and Operation Manual
Chapter 6 Management and Security
Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network.
Because of its generic nature, the RADIUS protocol can easily be used by service
providers and enterprises to manage access to the Internet, internal networks,
wireless networks, and integrated e-mail services. These networks may
incorporate DSL, access points, VPNs, network ports etc.
Functional Description
A work station attempts to log on to a Megaplex unit, which in turn submits an
authentication request to the RADIUS server.
The password is not transmitted over the network. A hash code is generated over
it instead and a previously defined shared secret (string of free text) between the
RADIUS server and the Megaplex unit is transmitted.
Verifying credentials and privileges via RADIUS data base
Logon request to Megaplex-4
Network
Logging on to Megaplex-4 or
returning authentication error
Megaplex-4
Management Work Station
Access accepted or denied
RADIUS Server
Shared Secret
Figure 6-1. RADIUS Server Operation Scheme
The RADIUS server verifies the user information against a database stored at the
RADIUS server. The RADIUS server replies in one of the following ways:
•
Access Rejected. Access to all resources denied.
•
Access Accepted. Access to the requested network resources granted.
Factory Defaults
Description
Default Value
The max number of authentication attempts.
2
Time interval between two authentication attempts.
2 seconds
UDP port used for the authentication channel
1812
Configuring the RADIUS Server
Megaplex-4 provides connectivity to up to four Radius authentication servers. You
have to specify access parameters such as assigning Radius server IDs, specifying
the associated server IP addresses and the number of retries.
Megaplex-4
Authentication via RADIUS Server
6-7
Chapter 6 Management and Security
Installation and Operation Manual
This section explains how to define and configure a RADIUS server, activate and
de-activate it.
To define a Radius server:
1. At the config>mngmnt# prompt, enter radius.
The config>mngmnt>radius# prompt appears.
2. Enter server <1..4>.
The config>mngmnt>radius>server <1..4># prompt appears.
3. Define the parameters for the relevant Radius server as illustrated and
explained in the table below.
Task
Command
Assigning an IP address to the server
address <1.1.1.1..255.255.255.255>
Defining a non-disclosed string (shared
secret) used to encrypt the user password.
key <string of free text>
Defining the number of authentication
request attempts
retry <0..10>
Defining the period of time during which
Megaplex-4 waits for a response from the
RADIUS server.
timeout <1..5>
Specifying the UDP port used for the
authentication channel
auth-port <1..65535>
Viewing the RADIUS Server Profile Status
This section explains how to display the status of the RADIUS servers.
To display the RADIUS server profile status:
•
At the config>mngmnt>radius# prompt, enter show status.
The status of the four RADIUS server entries appears regardless if they
are configured and enabled or not.
config>mngmnt>radius# show status
Server
IP Address
Access Status
----------------------------------------------------------------------------1.
172.17.143.3
Enable Connected
2.
0.0.0.0
Disable
Not connected
3.
0.0.0.0
Disable
Not connected
4.
0.0.0.0
Disable
Not connected
config>mngmnt>radius#
Viewing RADIUS Statistics
This section explains how to display RADIUS sever statistics.
6-8
Authentication via RADIUS Server
Megaplex-4
Installation and Operation Manual
Chapter 6 Management and Security
To display RADIUS statistics:
•
At the config>mngmnt>radius# prompt, enter show statistics.
RADIUS statistics appear as illustrated below.
config>mngmnt>radius# show statistics
Server1
Server2 Server3 Server4
--------------------------------------------------------------Access Requests
: 0
0 0
0
Access Retransmits : 0
0 0
0
Access Accepts
: 0
0 0
0
Access Rejects
: 0
0 0
0
Access Challenges : 0
0 0
0
Malformed Response : 0
0 0
0
Bad Authenticators : 0
0 0
0
Pending Requests
: 0
0 0
0
Timeouts
: 0
0
0 0
Unknown Types
: 0
0 0
0
Packets Dropped
: 0
0 0
0
6.4
Authentication via TACACS+ Server
TACACS+ (Terminal Access Controller Access Control System Plus) is a security
application that provides access control for routers, network access servers, and
other networked computing devices via one or more centralized servers. TACACS+
provides separate authentication, authorization, and accounting services. It is
used to communicate between the switch and an authentication database.
Because TACACS+ is based on TCP, implementations are typically resilient against
packet loss.
Standards
RFC 1492, An Access Control Protocol, sometimes called TACACS.
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet but leaves a
standard TACACS+ header.
Factory Defaults
By default, no TACACS+ servers are defined. When the TACACS+ server is first
defined, it is configured as shown below.
Parameter
Default Value
retry
1
timeout
5 seconds
Megaplex-4
Authentication via TACACS+ Server
6-9
Chapter 6 Management and Security
Installation and Operation Manual
Parameter
Default Value
authentication-port
49
accounting-port
49
Functional Description
TACACS+ is a protocol that provides access control for routers, network access
servers and other networked computing devices via one or more centralized
servers. TACACS+ is based on AAA model:
•
Authentication – The action of determining who a user is.
•
Authorization – The action of determining what a user is allowed to do. It can
be used to customize the service for the particular user.
•
Accounting – The action of recording what a user is doing, and/or has done.
The TACACS+ client can be configured to use authentication/authorization with or
without accounting functionality.
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
•
The access client is an entity which seeks the services offered by the
network.
•
TACACS+ client running on Megaplex-4, processes the requests from the
access client and pass this data to TACACS+ server for authentication.
•
The TACACS+ server authenticates the request, and authorizes services over
the connection. The TACACS+ server does this by matching data from the
TACACS+ client`s request with entries in a trusted database.
TACACS+ server decides whether to accept or reject the user's authentication or
authorization. Based on this response from the TACACS+ server, the TACACS+
client decides whether to establish the user's connection or terminate the user's
connection attempt. The TACACS+ client also sends accounting data to the
TACACS+ server to record in a trusted database.
TACACS+ uses TCP for its transport and encrypts the body of each packet.
TACACS+ client and server can agree to use any port for authentication and
accounting. TACACS+ supports authentication by using a user name and a fixed
password.
Accounting
Megaplex-4 supports up to five accounting groups, with up to five TACACS+
servers per group. However, each TACACS+ server can be bound to a single
accounting group only.
A group can be defined with its own accounting level:
•
Shell accounting, which logs the following events:
6-10
Successful logon
Authentication via TACACS+ Server
Megaplex-4
Installation and Operation Manual
Chapter 6 Management and Security
Logon failure
Successful logoff
Megaplex-4-terminated management session.
•
System accounting, which records system events/alarms registered in local
log file
•
Command accounting, which logs the following events:
Any shell command that was successfully executed by Megaplex-4
Any level that was successfully changed in a shell.
Defining TACACS+ Server
Megaplex-4 provides connectivity to up to five TACACS+ authentication servers.
You must specify the associated server IP address, key, number of retries, etc.
To define TACACS+ server:
1. If you intend to use TACACS+ for authentication, verify that TACACS+ is
selected as level-1 authentication method (see Access Policy).
2. At the config>mngmnt>tacacsplus# prompt, type server <ip-address> to
specify the server IP address.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
3. Enter the necessary commands according to the tasks listed below.
Task
Command
Comments
Defining a new TACACS+ server
server <ip-address>
no server deletes a TACACS+
server
Defining a non-disclosed string (shared
secret) used to encrypt the user
password
key <string> [hash]
The shared secret is a secret
key consisting of free text
known to the client and the
server for encryption. It is
hashed if specified.
Defining the TCP port to be used for
accounting
accounting-port
<tcp-port-number>
Range 1–65535
Defining the T
