Gmux-2000 - Manual (Version Menu) PDF

INSTALLATION AND
OPERATION MANUAL
Gmux-2000
Hub-Site Pseudowire and Voice Trunking
Gateway (SDH Version)
Version 3.2
The Access Company
Gmux-2000
Hub-Site Pseudowire and Voice Trunking Gateway
(SDH Version)
Version 3.2
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 Gmux-2000
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 Gmux-2000 product name is owned by RAD. No right, license, or interest to such trademark
is granted hereunder, and you agree that no such right, license, or interest shall be asserted by
you with respect to such trademark. The RAD name, logo, logotype, and the terms EtherAccess,
TDMoIP and TDMoIP Driven, and the product names Optimux and IPmux, are registered
trademarks of RAD Data Communications Ltd. All other trademarks are the property of their
respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
Gmux-2000. 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
Gmux-2000, based on or derived in any way from the Gmux-2000. Your undertaking in this
paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the Gmux-2000 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 Gmux-2000 and all copies and
portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters
RAD Data Communications Ltd.
North America Headquarters

RAD Data Communications Inc.
24 Raoul Wallenberg Street

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

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

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

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

specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
Handling Energized Products

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

Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port
differs from the standard one, a notice will be given in the manual.
Ports
Safety Status
V.11, V.28, V.35, V.36, RS-530, X.21,

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

Balanced E1, T1, Sub E1/T1
TNV-1 Telecommunication Network Voltage-1:

Ports whose normal operating voltage is within the
limits of SELV, on which overvoltages from
telecommunications networks are possible.
FXS (Foreign Exchange Subscriber)

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

(with feeding voltage), U-Interface
ISDN

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

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

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

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

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

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

Warning
Avertissement
Achtung
This is a class A product. In a domestic environment, this product may cause radio
interference, in which case the user will be required to take adequate measures.
Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel, cet
appareil peut provoquer des brouillages radiolectriques. Dans ces cas, il peut tre
demand lutilisateur de prendre les mesures appropries.
Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In Wohngebieten
knnen beim Betrieb dieses Gertes Rundfunkstrrungen auftreten, fr deren
Behebung der Benutzer verantwortlich ist.
Franais
Mise au rebut du produit

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

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

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

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

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

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

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

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

Assurez-vous que l'installation lectrique est conforme la rglementation locale.
Branchez toujours la fiche de secteur une prise murale quipe d'une borne protectrice de mise
la terre.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du btiment devrait avoir une capacit
leve de rupture et devrait fonctionner sur courant de court-circuit dpassant 35A.
Branchez toujours le cble d'alimentation en premier l'quipement puis la prise murale. Si un
commutateur est fourni avec l'quipement, fixez-le en position OFF. Si le cble d'alimentation ne
peut pas tre facilement dbranch en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est install dans l'installation du btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si le systme de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par
rapport la mise la terre. Tout ple doit tre mis la terre en externe.
A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient
tre prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques
d'incendie.
Les units CC devraient tre installes dans une zone accs restreint, une zone o l'accs n'est
autoris qu'au personnel qualifi de service et de maintenance.
Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que
l'installation est conforme la rglementation locale.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du btiment devrait avoir une capacit
leve de rupture et devrait fonctionner sur courant de court-circuit dpassant 35A.
Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le
en position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le
conducteur de mise la terre la borne correspondante, puis le ple positif et en dernier, le
ple ngatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du
btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC
est flottante.
Preface
Foreword
This manual describes the Gmux-2000 Pseudowire Gateway. The manual covers the general
system characteristics, presents typical systems applications, and provides installation,
operating procedures, and configuration information for the modules which are part of the
basic Gmux-2000 system configuration.
This release of the manual covers the characteristics of Gmux-2000 equipment running
software version 3.2, when used in networks using the SDH standards.
A separate version of this manual covers the Gmux-2000 characteristics, when used in
networks using the SONET standards.
Manual Organization
This manual is organized as follows:
Chapter 1. Introduction
presents the main features and typical applications of the Gmux-2000 family, describes the
various equipment versions, and lists the technical characteristics of the Gmux-2000
systems.
Chapter 2. Functional Description

presents a functional description of the Gmux-2000 equipment, and system application
guidelines.
Chapter 3. System Installation

provides detailed installation and operation instructions for Gmux-2000 systems.
Chapter 4. Operation and Preliminary Configuration

provides general operating instructions and preliminary configuration procedures for
the Gmux-2000. It also provides navigation maps for the supervision utility.
Chapter 5. Configuration
provides detailed configuration procedures for Gmux-2000 systems.
Chapter 6. Configuring Typical Applications

describes configuration procedures for typical Gmux-2000 applications.
Chapter 6. Troubleshooting and Diagnostics

describes the diagnostic and performance monitoring functions supported by
Gmux-2000 systems. It also explains the alarm and configuration error (sanity)
messages generated by Gmux-2000 systems.
Appendix A. Connection Data

provides connection data for the basic modules used in the Gmux-2000 systems.
Appendix B. Installing New Software Releases

provides instructions for the installation of new software releases.
Appendix C. Operating Environment

describes the Gmux-2000 operating environment.
Index
helps you find information within the Gmux-2000 manual.
Conventions
Note
A note draws attention to a general rule for a procedure, or to exceptions to a
rule.
Caution
A caution warns of possible damage to the equipment if a procedure is not

followed correctly.
A warning alerts to the presence of important operating and maintenance

(servicing) instructions in the literature accompanying the equipment. If these
instructions are not followed exactly, bodily injury may occur.
Warning
Related Documentation
In addition to this System manual, RAD offers separate Installation and Operation Manuals
for each of the modules available for the Gmux-2000 system.
Each module Installation and Operation Manual presents the technical characteristics,
applications and specific configuration information for the corresponding module.
Quick Start Guide

If you are familiar with the Gmux-2000, use this guide to prepare it for operation,
starting from its factory-default configuration.
Caution
Before performing the procedures described below, review the safety precautions
given in Chapter 3.
1.
Installing Gmux-2000
1. Refer to the site installation plan and install the Gmux-2000 enclosure in the
prescribed position.
2. Install modules in accordance with the required service. Slot utilizations for
the main types of service are identified below.
Alternate Slot for SDH Interface Module
or
Pseudowire Emulation Server
or
Pseudowire Emulation Module with External Interfaces
Slot for SDH Interface Module

or
or
Power Inlet
(PI) Module
INLET
P.S . 3
P.S . 2
P.S . 1
CT RL. 2
CRTL. 1
Gmux-2000
I/O-9
I/O-8
I/O-7
I/O-6
I/O-5
I/O-4
I/O-3
I/O-2
I/O-1
ALA RM S
PW R
M AJ . ALARM
T ST
M IN . ALA RM
FAN-TRAY
Slot:
PW R
FLT
L ASER
CL ASS
LOC
REM
AC-IN
TX
STM1
ACT
GE 1
POWER
POWER
GbE
LOC
RDY
REM
ALM
I/O-9
RX
I/O 9
LINK
L ASER
CL ASS
1
TX
RX
GE 2
LINK
PAUSE
LINK
PAUSE
ACT
TX
RX
TX
RX
FLT
I/O-8
MONITOR
Slot for PSN

I/O 8 Interface Module
PS-AC
I/O-7
I/O 7
I/O-6
I/O 6 Alternate Slot for

PSN Interface Module
I/O-5
I/O 5
I/O-4
I/O 4
I/O-3
I/O 3
I/O-2
I/O 2
I/O-1
I/O 1
POWER
POWER
2
PS-AC
PS-AC
1
9 10 11 12 13 14 15 16
17 18 19 20 21
ACT
FLT
POWER
E1.PW.SRV / 21
POWER
1
1
10 11 12 13 14 15 16
17 18
19 20 21
ACT
FLT
PS-AC
E1.PW.SRV / 21
OUT
IN
SD
1
ACT
LINK
10 11 12 13 14 15 16 17 18 19 20 21
S TAT ION CLOCK
ACT
FLT
E1.PW.SRV / 21
ACT
CONTROL
ETH
CONTROL
FLT
DPW
OUT
IN
SD
ACT
CONTROL
LINK
S TAT ION CLOCK
ACT
ETH
CONTROL
Slots for
Pseudowire Emulation
Servers
and/or
Modules with External
E1 Interfaces
FLT
DPW
Fan Tray
System Slots
I/O Slots
2 Slots for CONTROL Modules

3 Slots for PS Modules
Slot Utilization for TDM Traffic Transport Services
Gmux-2000 Ver. 3.2
Quick Start Guide

or
Voice Compression Module
Power Inlet
(PI) Module
INLET
P.S . 3
P.S . 2
P.S . 1
CT RL. 2
CRTL. 1
Gmux-2000
I/O-9
I/O-8
I/O-7
I/O-6
I/O-5
I/O-4
I/O-3
I/O-2
I/O-1

or
ALA RM S
PW R
M AJ . ALARM
T ST
M IN . ALA RM
FAN-TRAY
Slot:
PW R
FLT
L ASER
CL ASS
1
LOC
REM
AC-IN
RX
TX
STM1
ACT
LOC
RDY
REM
ALM
I/O-9
I/O 9
I/O-8
Slot for PSN

I/O-7
I/O 7
I/O-6

I/O-5
I/O 5
I/O-4
I/O 4
I/O-3
I/O 3
I/O-2
I/O 2
I/O-1
I/O 1
RX
LINK
GE 1
L ASER
CL ASS
1
POWER
POWER
TX
GE 2
LINK
PAUSE
LINK
PAUSE
ACT
TX
RX
TX
RX
FLT
MONITOR
GbE
PS-AC
POWER
POWER
2
PS-AC
PS-AC
LOC
1
11
13
REM
15
ACT
LOC
FLT
REM
2
POWER
POWER
10
12
14
16
1-16 E1
VC-E1/16
LINK
LOC
1
11
13
REM
15
ACT
LOC
FLT
REM
PS-AC
2
10
12
16
14
11
13
S TAT ION CLOCK
ACT
DCE
FLT
REM
2
CONTROL
ACT
LOC
LINK
ETH
REM
15
10
12
14
16
1-16 E1
VC-E1/16
CONTROL
LOC
1
ACT
LINK
IN
SD
1-16 E1
VC-E1/16
OUT
LINK
LOC
FLT
1
11
13
REM
15
ACT
LOC
OUT
IN
4
10
12
14
16
LINK
1-16 E1
VC-E1/16
ACT
FLT
REM
2
SD
LINK
LOC
S TAT ION CLOCK

1
11
13
REM
15
ACT
LOC
CONTROL
ACT
ETH
CONTROL
FLT
REM
FLT
DCE
10
VC-E1/16
12
14
16
Slots for
Voice Compression
Modules
1-16 E1
LINK
Fan Tray
System Slots
I/O Slots

Slot Utilization for Compressed Voice Transport Services

3. Refer to the site installation plan, and connect the prescribed cables to the
Gmux-2000 modules.
4. When ready, apply power.
Gmux-2000 Ver. 3.2
2.
Quick Start Guide
Configuration Sequence
Preliminary Preparations
1. Connect a terminal to the CONTROL DCE connector of the active CONTROL
module (use a straight cable).
Note
You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CONTROL modules installed in the Gmux-2000, using a Y-cable.
You may use any standard ASCII terminal (dumb terminal or personal
computer emulating an ASCII terminal) equipped with an RS-232
communication interface. Make sure to use VT-100 terminal emulation.
2. Configure the terminal for 115.2 kbps, one start bit, eight data bits, no
parity, and one stop bit. Select the full-duplex mode, echo off, and disable
any type of flow control.
3. Connect the Gmux-2000 to power.
4. Wait until all the PWR and the CONTROL ACT indicators stop flashing and the
ACT indicator of one CONTROL module remains ON, and then press <Enter>
once to obtain the log-in screen.
5. If the Gmux-2000 default user name and password have not yet been
changed, log in as administrator using su as the user name and 1234 for
password.
If your password is accepted, you will see the Gmux-2000 main menu.
Note
If you cannot establish communication with the Gmux-2000 or the display is

jumbled, reset the Gmux-2000 to the factory default parameters using section 2
of the internal switch SW1 located on the CONTROL modules. After configuring
the desired CONTROL DCE port parameters, return section 2 of SW1 to the User
Selected setting.
The following table provides an outline of the Gmux-2000 system configuration
procedure. For module configuration procedures, use the Quick Start sections in
the Installation and Operation Manuals of the modules installed in the
Gmux-2000 chassis.
For your convenience, a navigation map of the Gmux-2000 supervision terminal
menus is also provided below.
Gmux-2000 Ver. 3.2
Quick Start Guide

Step
Action
Using
Select the default database number, 1 to 5
Configuration>Database Tools>Choose DB Number
Reload the factory-default parameters
Configuration>Database Tools>Factory Default
If the Gmux-2000 is equipped with all the

modules, load the hardware configuration.
Configuration>Database Tools>Load Hardware
Alternatively, configure the modules installed in Configuration>System>Card Type

the Gmux-2000
4
Configure CONTROL DCE port parameters
Configuration>System>Serial Port
Configure CONTROL ETH port parameters
Configuration>System>Ethernet Port
Configure the IP communication parameters of

the Gmux-2000 management agent
Configuration>System>Host IP
Configure Gmux-2000 management access
Configuration>System>Management>Management
Access
Configure specific managers and any required

static routes
Configuration>System>Management>Manager List
Configure the Gmux-2000 logistic parameters
Configuration>System>Management>Device Info
10
11
If necessary, configure syslog functionality:
1. Configure syslog system IP address.
Configuration>System>Syslog System Address
2. Configure syslog parameters
Configuration>System>Syslog>Syslog Configuration
Set Gmux-2000 real-time clock:
1. Select the date source, and the date format Configuration>System>Date & Time>Date Source,
Date Format
2. When the internal real time clock is used,

set the time of day
3. When NTP synchronization is used,

configure NTP parameters
12
Configuration>System>Date & Time>Time and Date

parameters
Configuration>System>Date & Time>NTP Server,
GMT, Update Interval
Prepare the Gmux-2000 for SNMP

management:
1. Select the SNMP support mode
Configuration>System>Management>SNMPv3
(enable/disable SNMPv3).
If SNMP support mode is changed, save to
activate the change before continuing
2. When SNMPv3 is disabled, configure SNMP

management parameters
Configuration>System>Management>Authentication/
Community
3. When SNMPv3 is enabled, configure

parameters in the following order:
SNMP Engine ID
SNMPv3 users
SNMPv3 targets and notifications
Configure SNMPv1/SNMPv3 mapping
Configuration>System>Management>SNMP Engine ID
Setting>Users
Setting>Targets & Notify
Setting> SNMPv1/v3 Mapping
Gmux-2000 Ver. 3.2

Step
Quick Start Guide
Action
Using
13
Configure physical layer parameters for each

module, and each module port
Configuration>Physical Layer
14
Configure timing flow
Configuration>System>Clock Source
15
Configure redundancy
Configuration>System>Redundancy
16
Configure connection parameters for each

bundle
Configuration>Connection
17
Configure Gmux-2000 internal routing
Configuration>TS Assignment
18
Configure Gmux-2000 alarm handling
Configuration>System>Alarms
19
Save the final configuration in the selected

database
Configuration>Database Tools>Update Database
20
If necessary, prepare additional databases (up

to 5)
To start from an existing database, use

Configuration>Database Tools>Load Database.
Repeat the relevant steps as needed to create a new
database
Gmux-2000 Ver. 3.2
Quick Start Guide
Main Menu
Inventory
Monitoring
Configuration
System
Diagnostics
Self Test Results
Security Key
System Information
SW/HW Revision
Utilities
Statistics
File Utilities
Download/Upload by TFTP
Internal Download
Internal Upload
Ping
PS
Status
CL
Event Log
I/O
Read Log
Clear Log
Bundle
Destination IP Address
VLAN Tagging
VLAN ID
VLAN Priority
Ping Repetitions
Trace Route
Send Ping
Reset CL
Reset I/O
Reboot System
Loopback
File System
Reset
Alarm
APS Commands
Fan
Display System Alarm
Display PS Alarms
Display CL Alarms
Display I/O Alarms
Display Bundle Alarm
DSP All Alarms
Clock
Redundancy
System
Physical Layer
Host IP
I/O
Syslog System
Address
..
.
.
SNMPv3 Enabled
Device Info
Authentification/Community
Manager List
Management Access
Username&Password
SNMP Engine ID
SNMPv3
Date & Time
..
.
.
TS Assignment
Bundle ID
Card SS/PP
Connection Mode
TS Assignment
PSN Type
Assign TS Range
to Bundle
Connection
Configuration
Assign Entire
Port to Bundle
Database Tools
Choose dB Number
Factory Default
Load Database
Load Hardware
Check Sanity
Update Database
I/O 9
Management
SNMPv3 Disabled
I/O 1
I/O 2
Connection
or
Device Info
Manager List
Management Access
Username&Password
SNMP Engine ID
SNMPv3
SNMPv3 Setting
Assign Entire
TSs To Port
NVRAM
NTP
Clock Source
Alarms
Redundancy
CL
I/O
Serial Port
Ethernet Port
Card Type
Syslog
Gmux-2000 Ver. 3.2
Contents
Chapter 1. Introduction
1.1 Overview.................................................................................................................... 1-1
Purpose and Use..................................................................................................... 1-1
Main Features ......................................................................................................... 1-2
PSN Interfaces ................................................................................................... 1-3
SDH Interfaces ................................................................................................... 1-4
Pseudowire (PW) Emulation Services .................................................................. 1-5
Voice Trunking Services ...................................................................................... 1-6
Control Functions ............................................................................................... 1-8
Timing................................................................................................................ 1-9
External Alarm Monitoring and Reporting ............................................................ 1-9
Power Supply Subsystem .................................................................................... 1-9
1.2 Typical Applications .................................................................................................. 1-10
Pseudowire Emulation Services for TDM Transport................................................. 1-10
Voice Compression Applications ............................................................................ 1-11
High Capacity Toll Bypass over SDH Networks ................................................... 1-11
High Capacity Toll Bypass over Packet Switched Networks ................................ 1-12
Connecting Multiple Remote Call Centers .......................................................... 1-12
Voice Trunking over Multiple E1 Streams ........................................................... 1-13
Voice Trunking over STM-1 Link ........................................................................ 1-14
Interoperability with Vmux Family Products ....................................................... 1-14
1.3 Equipment Description ............................................................................................. 1-16
System Structure .................................................................................................. 1-16
TDM Pseudowire Emulation Services ................................................................. 1-16
Voice Compression Services .............................................................................. 1-17
Physical Description .............................................................................................. 1-18
Front Side ........................................................................................................ 1-18
Rear Side ......................................................................................................... 1-19
Modules................................................................................................................ 1-21
Description of Gmux-2000 Modules ...................................................................... 1-22
Power Supply Modules ..................................................................................... 1-22
CONTROL Module ............................................................................................. 1-23
Description of I/O Modules.................................................................................... 1-24
STM1 SDH Interface Module ............................................................................. 1-24
E1-PW-SRV/21 Pseudowire Emulation Server Module ........................................ 1-25
E1-PW/28 Pseudowire Emulation Module with External E1 Interfaces ................ 1-27
GbE PSN Interface Module ................................................................................ 1-29
VC-E1/16, VC-E1/12 Voice Compression Modules .............................................. 1-30
1.4 Technical Specifications............................................................................................ 1-34
System Characteristics .......................................................................................... 1-34
STM1 Module Characteristics ................................................................................. 1-35
GbE Module Characteristics ................................................................................... 1-37
E1-PW/28 PW Module with External Interfaces Characteristics ............................... 1-38
E1-PW-SRV/21 PW Emulation Server Module Characteristics ................................... 1-40
VC-E1/16, VC-E1/12 Voice Compression Modules Characteristics ............................ 1-42
User-Side Voice Ports............................................................................................ 1-42
Network-Side Data Ports ...................................................................................... 1-43
Voice Transmission Parameters ............................................................................. 1-44
Timing .................................................................................................................. 1-46
Gmux-2000 Ver. 3.2
Table of Contents
General................................................................................................................. 1-46
Station Clock Interface .......................................................................................... 1-47
System Management ............................................................................................ 1-47
Power Requirements ............................................................................................. 1-49
Environment ......................................................................................................... 1-49
Physical ................................................................................................................ 1-50
Chapter 2. Functional Description
2.1 Scope ........................................................................................................................ 2-1
2.2 Gmux-2000 Functional Description ............................................................................. 2-1
Description of Gmux-2000 System Used for TDM Transport Services ....................... 2-1
TDM Traffic Flow within the Gmux-2000 ............................................................. 2-2
TDMoPSN Packet Processing ............................................................................... 2-4
HDLCoPSN Processing ........................................................................................ 2-5
SAToPSN Packet Processing ................................................................................ 2-6
CESoPSN Packet Processing ................................................................................ 2-6
Jitter Buffer Functions ........................................................................................ 2-6
Adaptive Timing ................................................................................................. 2-8
OAM Protocol ..................................................................................................... 2-8
Alarm Indications ............................................................................................... 2-9
Description of Gmux-2000 System Used for Voice Trunking Services ...................... 2-10
Voice Compression Operating Modes ................................................................ 2-13
Handling of Voice Signals ................................................................................. 2-15
Processing of Inband Signaling ......................................................................... 2-17
Automatic Fax Processing ................................................................................. 2-18
Handling of Voiceband Modem Signals .............................................................. 2-19
Handling of Voice Trunk Signaling ..................................................................... 2-19
Voice Packet Processing ................................................................................... 2-20
Estimating Bandwidth Requirements................................................................. 2-21
Preventing Excessive Bandwidth Consumption .................................................. 2-22
Processing of Transparent Timeslots ................................................................ 2-23
2.3 Connection (Bundle) Handling .................................................................................. 2-24
Overview .............................................................................................................. 2-24
Bundle Configurations Storage ......................................................................... 2-24
Number of Active Connections (Bundles) .......................................................... 2-24
Bundle Configuration Parameters .......................................................................... 2-26
TDMoIP Bundle Parameters ............................................................................... 2-26
TDMoIP CV (Compressed Voice) Bundle Parameters ........................................... 2-28
2.4 Redundancy (APS) Functions .................................................................................... 2-29
Redundancy for SDH Network Interfaces ............................................................... 2-29
Overview of SDH Network Interface Capabilities ............................................... 2-29
Operation of 1+1 Unidirectional Protection Function ........................................ 2-30
Redundancy for PSN Interface ............................................................................... 2-33
Overview of PSN Interface Redundancy Modes ................................................. 2-33
Using Link Aggregation ..................................................................................... 2-34
Using 1:1 Bidirectional APS for Port Redundancy............................................... 2-35
Module Redundancy Using 1:1 Bidirectional APS ............................................... 2-36
1:N Protection Mode ............................................................................................. 2-37
ii
Gmux-2000 Ver. 3.2
Table of Contents
2.5 Timing Subsystem .................................................................................................... 2-39

Output Timing Signals ........................................................................................... 2-40
Timing Reference Sources ..................................................................................... 2-41
Internal Reference Signals ................................................................................ 2-41
External Reference Signals................................................................................ 2-41
Internal Oscillator ............................................................................................. 2-41
External Clock Interface ......................................................................................... 2-42
Timing Subsystem Redundancy ............................................................................. 2-42
2.6 Management Subsystem .......................................................................................... 2-44
Functional Block Diagram ...................................................................................... 2-44
CONTROL Module Management Subsystem ....................................................... 2-44
Ethernet Connections to CONTROL Modules...................................................... 2-45
Serial Port Connections .................................................................................... 2-46
CONTROL Module Redundancy .............................................................................. 2-46
External Alarm Interfaces ...................................................................................... 2-46
Dry-Contact Alarm Interface ............................................................................. 2-47
External Sense Input......................................................................................... 2-47
2.7 Power Supply Subsystem.......................................................................................... 2-47
Chapter 3. System Installation
3.1 Safety ........................................................................................................................ 3-1
General Safety Precautions ..................................................................................... 3-1
Grounding .............................................................................................................. 3-2
Laser Safety Classification ....................................................................................... 3-3
Laser Safety Statutory Warning and Operating Precautions ..................................... 3-3
Protection against ESD ....................................................................................... 3-3
Proper Handling of Modules .................................................................................... 3-4
3.2 Site Requirements ...................................................................................................... 3-4
Power ..................................................................................................................... 3-4
AC Power ........................................................................................................... 3-5
DC Power ........................................................................................................... 3-5
Payload Connections ............................................................................................... 3-6
E1 Port Connections ........................................................................................... 3-6
SDH Port Connections ........................................................................................ 3-7
PSN Connections ................................................................................................ 3-7
Optical Cable Requirements ................................................................................ 3-8
Station Clock Connections ....................................................................................... 3-8
Management Connections ....................................................................................... 3-8
Ethernet Connections to CONTROL Modules........................................................ 3-8
Serial Port Connections ...................................................................................... 3-8
Alarm Port Connections .......................................................................................... 3-9
Front and Rear Panel Clearance ............................................................................... 3-9
Ambient Requirements ........................................................................................... 3-9
Electromagnetic Compatibility Considerations ........................................................ 3-10
3.3 Package Contents .................................................................................................... 3-10
3.4 Equipment Needed................................................................................................... 3-10
3.5 Gmux-2000 Enclosure .............................................................................................. 3-11
General Description .............................................................................................. 3-11
Front Panel ........................................................................................................... 3-12
Rear View ............................................................................................................. 3-13
3.6 Installing the Fan Tray .............................................................................................. 3-14
Fan Tray Description ............................................................................................. 3-14
Installation Procedure ........................................................................................... 3-15
Gmux-2000 Ver. 3.2
iii
Table of Contents
3.7 Installing the Power Inlet (PI) Module ....................................................................... 3-16

PI Description ....................................................................................................... 3-16
Installing PI Modules ............................................................................................. 3-17
3.8 Installing the Gmux-2000 PS Modules ....................................................................... 3-17
PS Module Description .......................................................................................... 3-17
Installation Procedure ........................................................................................... 3-18
Removing a PS Module .......................................................................................... 3-20
3.9 Installation of CONTROL Modules ............................................................................. 3-21
CONTROL Module Description ............................................................................... 3-21
Preparing the CONTROL Module for Installation ..................................................... 3-22
Clock Interface Selection .................................................................................. 3-22
Switch SW1 (Restore Factory-Default Parameters) ............................................ 3-23
Installing the CONTROL Module ............................................................................. 3-24
Removing the CONTROL Module ............................................................................ 3-24
Replacing a CONTROL Module During Equipment Operation ................................... 3-24
Gmux-2000 Chassis with two CONTROL Modules .............................................. 3-24
Gmux-2000 Chassis with Single CONTROL Module ............................................. 3-25
3.10 Installing I/O Modules ............................................................................................... 3-25
3.11 Installing Blank Panels .............................................................................................. 3-25
3.12 Installation of Gmux-2000 Enclosure ........................................................................ 3-26
Preparing for Installation in Rack ........................................................................... 3-26
Installation in Rack ................................................................................................ 3-28
3.13 Connecting Cables .................................................................................................... 3-28
Grounding ............................................................................................................ 3-28
Connecting Power ................................................................................................. 3-29
Connecting AC Power ....................................................................................... 3-29
Connecting DC Power ....................................................................................... 3-29
Connecting CONTROL Module ................................................................................ 3-30
Connection Data for CONTROL DCE Connector .................................................. 3-30
Connection Data for CONTROL ETH Connectors ................................................ 3-30
Connection Data for CLOCK Connectors ............................................................ 3-30
Connecting I/O Modules ........................................................................................ 3-30
Chapter 4. Operation and Preliminary Configuration
4.1 Overview.................................................................................................................... 4-1
4.2 Operating Instructions ............................................................................................... 4-1
Preparations for Monitoring Power-Up Sequence..................................................... 4-1
Turning the Gmux-2000 On ..................................................................................... 4-2
Normal Indications .................................................................................................. 4-3
General Indications............................................................................................. 4-3
CONTROL ETH Interface Status Indications .......................................................... 4-3
PSN Interface Modules (GbE) Status Indications .................................................. 4-3
SDH Interface Modules (STM1) Module Status Indications ................................... 4-4
Pseudowire Emulation Server Modules (E1-PW-SRV/21) Module Status Indications 44
Pseudowire Emulation Modules with External E1 Interfaces (E1-PW/28) Status
Indications ......................................................................................................... 4-4
Voice Compression Modules (VC-E1/16 and VC-E1/12) Status Indications ............ 4-4
Turning the Gmux-2000 Off .................................................................................... 4-4
4.3 Configuration Options ................................................................................................ 4-5
iv
Gmux-2000 Ver. 3.2
Table of Contents
4.4 Preliminary Configuration Sequence ........................................................................... 4-5

Requirements ......................................................................................................... 4-5
Terminal Characteristics ..................................................................................... 4-5
Software ............................................................................................................ 4-6
Preparation for Preliminary Configuration ................................................................ 4-6
Log-in for Supervision and Configuration ............................................................ 4-6
Preliminary Configuration Session ........................................................................... 4-8
4.5 Configuring Gmux-2000 via Supervision Terminal ...................................................... 4-13
Introduction.......................................................................................................... 4-13
Preparation of New Configuration Parameters .................................................. 4-14
Validity Checks ................................................................................................. 4-14
Power-up Process ............................................................................................ 4-15
General Terminal Operating Procedures ................................................................. 4-15
Organization of Terminal Screens ..................................................................... 4-15
General Procedures .......................................................................................... 4-17
Saving Changes to Configuration Database ....................................................... 4-19
Ending a Terminal Configuration Session........................................................... 4-19
4.6 Menu Structure of Supervision Utility........................................................................ 4-20
Main Menu Structure............................................................................................. 4-20
Detailed Menu Structures ...................................................................................... 4-21
4.7 Configuring Gmux-2000 via Telnet ............................................................................ 4-35
Telnet (IP) Host Characteristics ............................................................................. 4-35
General Telnet Operating Procedures .................................................................... 4-35
4.8 Using SSH ................................................................................................................ 4-35
4.9 Configuring Gmux-2000 via SNMP............................................................................. 4-36
Chapter 5. Configuration
5.1 Overview.................................................................................................................... 5-1
Navigation Maps ..................................................................................................... 5-1
Overview of Configuration Menu Structure .............................................................. 5-2
5.2 Managing Gmux-2000 Configuration Databases .......................................................... 5-3
Overview ................................................................................................................ 5-3
Using the Database Tools ....................................................................................... 5-4
5.3 Configuration Sequence ............................................................................................. 5-6
5.4 Configuring System Parameters .................................................................................. 5-8
System Parameters Configuration Sequence ............................................................ 5-8
Overview of System Configuration Submenu ........................................................... 5-8
Programming Modules .......................................................................................... 5-13
Module Programming Procedure ....................................................................... 5-13
Programming Procedure for VC-E1/16, VC-E1/12 Modules ................................. 5-13
Configuring Serial Port Parameters ........................................................................ 5-14
Configuring Ethernet Control Port Parameters ....................................................... 5-16
Configuring System-Level IP Communication Parameters........................................ 5-16
Configuring Management Access and Users ........................................................... 5-18
Configuring Global Management Access Rights ................................................. 5-19
Configuring User Access Rights ......................................................................... 5-20
Managing Existing Users ................................................................................... 5-23
Configuring the User Authentication Method .................................................... 5-24
Configuring Manager List Parameters .................................................................... 5-26
Configuring Logistic Parameters ............................................................................ 5-30
Gmux-2000 Ver. 3.2
Table of Contents
5.5
5.6
5.7
5.8
5.9
vi
Configuring Syslog Functionality ............................................................................ 5-31

Configuring Syslog System Address .................................................................. 5-31
Configuring Syslog Server Parameters ............................................................... 5-32
Displaying Syslog Statistics ............................................................................... 5-34
Configuring Date & Time ....................................................................................... 5-35
Configuring Gmux-2000 for SNMP Management........................................................ 5-39
Enabling/Disabling SNMPv3 Security Features ........................................................ 5-39
Configuring for SNMP Management without SNMPv3 Security ................................ 5-40
Configuring Authentication and Communities.................................................... 5-40
Configuring SNMP Engine ID .................................................................................. 5-42
Configuring SNMP Management with SNMPv3 Security........................................... 5-43
Configuration Authorized SNMPv3 Users ........................................................... 5-44
Configuring SNMPv3 Targets and Notifications .................................................. 5-46
SNMPv1/v3 Mapping ......................................................................................... 5-51
Summary User Table......................................................................................... 5-52
Summary Target Table ...................................................................................... 5-52
Configuring Physical Layer Parameters ...................................................................... 5-54
Configuring System Timing Flow ............................................................................... 5-55
Configuring Nodal Timing References................................................................ 5-55
Configuring the External (Station) Clock Interfaces............................................ 5-59
Configuring Redundancy........................................................................................... 5-61
Redundancy Configuration Options ....................................................................... 5-61
Configuring Gmux-2000 Control Subsystem Redundancy ....................................... 5-62
Configuring Gmux-2000 I/O Redundancy SDH Interface Subsystem ..................... 5-63
Configuring Gmux-2000 I/O Redundancy PSN Interface Subsystem ..................... 5-69
Configuring Link Aggregation for the PSN Interface ........................................... 5-70
Configuring 1:1 Bidirectional Port Protection Mode for the PSN Interface .......... 5-73
Configuring 1:1 Bidirectional Module Protection for the PSN Interface............... 5-74
Configuring Gmux-2000 I/O Redundancy 1:N Protection Mode ............................ 5-76
Configuring Connections .......................................................................................... 5-79
Overview of Connection Submenu ......................................................................... 5-80
General Bundle Configuration Procedure ............................................................... 5-85
Selecting the Bundle Structure .............................................................................. 5-86
Configuring TDMoIP (CE) Bundle Parameters .......................................................... 5-87
Configuring TDMoIP (CE) Bundles for UDP/IP Networks ...................................... 5-87
Configuring TDMoIP (CE) Bundle Parameters for MPLS/ETH Networks ................ 5-94
Selection Guidelines for TDM Payload Bytes per Frame ..................................... 5-96
Selecting an Optimal Jitter Buffer Size .............................................................. 5-97
Configuring HDLC Bundle Parameters .................................................................... 5-97
Configuring HDLC Bundle Parameters for UDP/IP Networks................................ 5-97
Configuring HDLC Bundle Parameters for MPLS/ETH Networks ........................... 5-98
Configuring SAToPSN Bundle Parameters ............................................................... 5-99
Configuring SAToPSN Bundle Parameters for UDP/IP Networks .......................... 5-99
Configuring SAToPSN Bundle Parameters for MPLS/ETH Networks ................... 5-100
Configuring CES Bundle Parameters ..................................................................... 5-101
Configuring CES Bundle Parameters for UDP/IP Networks ................................ 5-101
Configuring CES Bundle Parameters for MPLS/ETH Networks ........................... 5-102
Configuring TDMoIP (CV) Bundle Parameters ........................................................ 5-103
TDMoIP (CV) Bundle Configuration Sequence .................................................. 5-103
Preliminary TDMoIP (CV) Bundle Configuration Steps ....................................... 5-103
Configuring TDMoIP (CV) Bundle Routing Parameters ...................................... 5-105
Configuring TDMoIP (CV) General Bundle Parameters ...................................... 5-108
Configuring TDMoIP (CV) Bundle Voice Parameters .......................................... 5-110
Gmux-2000 Ver. 3.2
Table of Contents
5.10 Configuring TS Assignment ..................................................................................... 5-119

Overview of TS Assignment Submenu .................................................................. 5-119
Timeslot Assignment Procedure for TDMoPSN, HDLCoPSN, and CESoPSN Bundles 5-120
Assigning Individual Timeslots......................................................................... 5-120
Selecting a Range of Timeslots ....................................................................... 5-122
Assigning an Entire Port to a Bundle ............................................................... 5-123
Configuring Timeslot Assignment for Voice Compression Modules ........................ 5-124
Configuring Timeslot Assignment for Compressed Voice Ports ......................... 5-125
Configuring Timeslot Assignment for Data Ports ............................................. 5-127
5.11 Viewing Logistic (Inventory) Information ................................................................. 5-130
Displaying the System Inventory ......................................................................... 5-130
Displaying System Information ....................................................................... 5-131
Interpreting the I/O Inventory Screens ............................................................ 5-132
Interpreting the SW/HW Revision Screens ....................................................... 5-134
Displaying PS Inventory Information ............................................................... 5-134
Displaying CL Inventory Information................................................................ 5-135
Displaying I/O Inventory Information............................................................... 5-136
Interpreting the Port Information Screen ........................................................ 5-138
Displaying Bundle Inventory Information ......................................................... 5-140
Displaying Fan Inventory Information .............................................................. 5-142
Displaying Timing Subsystem (Clock) Inventory Information ............................ 5-144
Displaying Redundancy Information .................................................................... 5-145
Displaying Information on APS Interfaces........................................................ 5-145
Displaying APS Group Status ........................................................................... 5-146
5.12 Utilities .................................................................................................................. 5-148
Overview of Utilities Menu .................................................................................. 5-148
Using the File Utilities ......................................................................................... 5-149
Selecting a Task ............................................................................................. 5-149
Downloading/Uploading by TFTP ..................................................................... 5-149
Internal Software Downloading ...................................................................... 5-151
Uploading Files from other Modules to CONTROL Module ................................ 5-153
Using the Reset Functions................................................................................... 5-154
Using the File System Utilities ............................................................................. 5-155
Using the Dir Function .................................................................................... 5-156
Copying Files .................................................................................................. 5-157
Renaming Files ............................................................................................... 5-158
Deleting Files ................................................................................................. 5-159
Formatting Disk.............................................................................................. 5-159
Chapter 6. Configuring Typical Applications
6.1 Overview.................................................................................................................... 6-1
Outline of Preliminary Configuration Sequence ........................................................ 6-1
General Configuration Sequence ............................................................................. 6-3
6.2 Application 1 Transport of Unframed Bundle from E1 Trunk .................................... 6-3
Application Overview .............................................................................................. 6-3
Gmux-2000 Configuration Procedure ....................................................................... 6-4
Preliminary Configuration ................................................................................... 6-4
Configuring Management ................................................................................... 6-4
Configuring System Clock ................................................................................... 6-6
Configuring I/O Module Physical Layer Parameters .............................................. 6-6
Configuring the Bundle ....................................................................................... 6-7
Connecting the E1 Port to the Bundle ................................................................. 6-8
IPmux-11 Configuration .......................................................................................... 6-9
Gmux-2000 Ver. 3.2
vii
Table of Contents
6.3
6.4
6.5
6.6
Host IP and NMS Settings ................................................................................... 6-9

E1 Physical Settings............................................................................................ 6-9
Bundle Connection Settings ................................................................................ 6-9
Monitoring the Bundle Traffic ................................................................................ 6-10
Application 2 Transport of Framed Bundle from E1 Trunk ...................................... 6-11
Application Overview ............................................................................................ 6-11
Gmux-2000 Configuration ..................................................................................... 6-11
Configuring I/O Module Physical Layer Parameters ............................................ 6-11
Configuring the Bundle Connection Parameters and its Timeslot Assignment ..... 6-11
IPmux-11 Configuration .................................................................................... 6-13
Monitoring the Bundle Traffic ................................................................................ 6-14
Application 4 Transport of Unframed Bundle from SDH Network ........................... 6-15
Gmux-2000 Configuration ..................................................................................... 6-15
Configuring I/O Modules Physical Layer Parameters ........................................... 6-15
Configuring the Bundle ..................................................................................... 6-16
Connecting the Internal E1 Port to the Bundle .................................................. 6-17
Map the Internal E1 Port to the SDH Interface .................................................. 6-18
IPmux-14 Configuration ........................................................................................ 6-18
Application 5 Voice Trunking Application ............................................................... 6-19
Configuring the West Gmux-2000 ......................................................................... 6-19
Preliminary Configuration ................................................................................. 6-19
Configuring Management and IP Communication Parameters ............................ 6-20
Configuring Physical Parameters of Voice Compression Module ......................... 6-22
Configuring Physical Parameters of GBE Module ................................................ 6-23
Configuring Physical Parameters of STM-1 Module ............................................ 6-23
Configuring System Clock ................................................................................. 6-24
Creating Bundles .............................................................................................. 6-24
Assigning Timeslots to Voice Ports.................................................................... 6-25
Map Voice Ports to the STM-1 Link ................................................................... 6-26
Connecting Bundles .......................................................................................... 6-27
Configuring Voice Ports 2 to 6 .......................................................................... 6-27
Assigning Data Port Timeslots .......................................................................... 6-27
Configuring the East Gmux-2000 ........................................................................... 6-28
Inband Management of Gmux-2000 via Voice Compression TDM Links ...................... 6-29
Configuration Procedure ....................................................................................... 6-30
Chapter 7. Troubleshooting and Diagnostics

7.1 Monitoring Performance ............................................................................................. 7-1
Overview of Monitoring Menu ................................................................................. 7-2
Selecting a Monitoring Task .................................................................................... 7-3
Displaying Performance Monitoring Statistics .......................................................... 7-3
Displaying Physical Layer Statistics Parameters ........................................................ 7-4
Displaying Connection Statistics for TDMoIP (CE) Bundles ...................................... 7-10
Displaying Status Information ............................................................................... 7-12
Displaying Physical Layer Status Parameters (GbE Modules) ................................... 7-12
Displaying Connection Status Parameters .............................................................. 7-17
Displaying Connection Performance Monitoring Data for TDMoIP (CV) Bundles ....... 7-18
viii
Gmux-2000 Ver. 3.2
Table of Contents
7.2 Troubleshooting ....................................................................................................... 7-21

Preliminary Checks ................................................................................................ 7-21
Troubleshooting Hardware Problems ..................................................................... 7-22
Handling Service Problems .................................................................................... 7-25
7.3 Detecting Configuration (Sanity) Errors ................................................................. 7-26
Displaying Sanity Errors......................................................................................... 7-26
Interpreting the Sanity Errors ................................................................................ 7-27
7.4 Handling Alarms and Traps ....................................................................................... 7-37
Overview of Alarm Collection and Reporting .......................................................... 7-37
Alarm Buffer .................................................................................................... 7-37
Alarm Relays .................................................................................................... 7-37
Configuring Alarm Handling ................................................................................... 7-38
Selecting Alarm Attributes ................................................................................ 7-39
Selecting Alarm Priorities .................................................................................. 7-43
Selecting Alarm Thresholds ............................................................................... 7-44
Selecting Alarms Threshold Window.................................................................. 7-46
Selecting Alarm Reporting Method .................................................................... 7-47
Configuring Alarm Input Functions .................................................................... 7-48
Using the Event Log .............................................................................................. 7-49
Reading the Event Log ..................................................................................... 7-50
Clearing the Log ............................................................................................... 7-51
Displaying Alarms.................................................................................................. 7-53
Interpreting Alarms ............................................................................................... 7-55
System and CONTROL Module Alarms ............................................................... 7-55
GbE Module Alarms .......................................................................................... 7-59
STM1 Module External SDH Port Alarms ......................................................... 7-60
STM1 Module Internal VC-4 Port Alarms ......................................................... 7-61
STM1 Module Internal VC-12 Port Alarms ....................................................... 7-63
Pseudowire Emulation Server Module Alarms .................................................... 7-64
Bundle Alarms .................................................................................................. 7-66
VC-E1/16, VC-E1/12 Alarms .............................................................................. 7-67
Traps Generated by Gmux-2000 ............................................................................ 7-68
7.5 Testing Gmux-2000 Operation.................................................................................. 7-71
Overview .............................................................................................................. 7-71
Diagnostic Tests for SDH (STM-1) Ports ................................................................ 7-72
Remote STM-1 Port Loopback .......................................................................... 7-72
Local STM-1 Port Loopback............................................................................... 7-73
E1 Port Diagnostic Functions for E1-PW-SRV/21 Modules ...................................... 7-73
Remote Loopback on E1 Port (E1-PW-SRV/21 Module) ...................................... 7-73
Local Loopback on E1 Port (E1-PW-SRV/21 Module) .......................................... 7-74
E1 Port Diagnostic Functions for E1-PW/28 Modules ............................................. 7-75
Remote Loopback on External E1 Port (E1-PW/28 Module)................................ 7-75
Local Loopback on External E1 Port (E1-PW/28 Module) .................................... 7-75
VC-E1/16, VC-E1/12 Voice Port Diagnostic Functions ............................................. 7-76
Remote Loopback on Voice Port ....................................................................... 7-76
Local Loopback on Voice Port ........................................................................... 7-77
Test Tone Injection........................................................................................... 7-79
VC-E1/16, VC-E1/12 Data Port Diagnostic Functions .............................................. 7-79
Remote Loopback on Data Port ........................................................................ 7-79
Ping Function ........................................................................................................ 7-81
Gmux-2000 Ver. 3.2
ix
Table of Contents
Activating Diagnostic Functions ............................................................................. 7-81

Overview of Diagnostics Menu Structure ........................................................... 7-81
Selecting a Diagnostics Task ............................................................................. 7-82
Performing Ping (IP Connectivity) Checks .......................................................... 7-82
Performing Loopback Tests .............................................................................. 7-85
7.6 Frequently Asked Questions ..................................................................................... 7-87
7.7 Technical Support .................................................................................................... 7-91
Appendix A. Connection Data
Appendix B. Installing New Software Releases
Appendix C. Operating Environment
Gmux-2000 Ver. 3.2
Chapter 1
Introduction
1.1
Overview
Purpose and Use

Gmux-2000 is a high-capacity carrier-class pseudowire gateway. Gmux-2000 is
designed to facilitate smooth and cost-effective migration to packet-switched
networks for users of the existing TDM-based platforms and infrastructure, by
enabling transport of legacy circuit-switched TDM traffic, (including voice traffic),
over Ethernet, IP, and MPLS packet-switched networks (PSNs). Two main types of
services are supported:
TDM pseudowire circuit emulation (PW) for E1 and channelized STM-1. Using
pseudowire emulation methods means that Gmux-2000 can support all the
signaling methods and payload types.
Voice trunking, using advanced, bandwidth-efficient voice compression

techniques, enables transporting compressed E1 voice traffic (including
inband signaling, modems, and fax) over TDM links (E1 and STM-1) and
Gigabit Ethernet packet-switched networks using IP and/or MPLS transport.
Gmux-2000 is compatible with other pseudowire equipment offered by RAD, for

example, the IPmux family of TDM Pseudowire Access Gateways, the Vmux family
of Voice Trunking Gateways, the ACE-3XXX family of Multiservice Pseudowire
Access products, as well as with Megaplex equipment with IP main link modules,
and is compliant with the emerging pseudowire edge-to-edge emulation (PWE3)
standards, including TDMoPSN, HDLCoPSN, CESoPSN and SAToPSN. Advanced
systems design confers the flexibility needed to meet the requirements of
practically every TDM transport application. Full redundancy for all the critical
subsystems ensures high availability for continuous, reliable service. Extensive
management capabilities, starting with supervision terminals and Telnet/SSH
hosts and up to SNMP-based network management, confer complete control over
all aspects of equipment operation, and support efficient provisioning and rapid
response to changing requirements. Automatic event notification in accordance
with the syslog protocol and NTP-based automatic time-of-day synchronization
of managed nodes enable effective management of large networks and easier
isolation of the source of transmission problems.
To protect network operations against unauthorized access, Gmux-2000 supports
a wide range of security features for every management facility: RADIUS
authentication for supervision terminal and Telnet access, SSH for secure Telnet
access, and SNMP management with authentication and privacy per SNMPv3
(using both user-based and view-based security models), with continued support
for SNMPv1 and SNMPv2.
Gmux-2000 Ver. 3.2
Overview
1-1
Chapter 1 Introduction
Main Features
Gmux-2000 is a flexible, modular system that can be provisioned in accordance
with the current application requirements, while providing significant room for
future growth. Its function is to transparently bridge between legacy
circuit-switched TDM networks and packet-switched networks, by converting TDM
data streams coming from the TDM ports into packets that are transported over
the PSN.
The current Gmux-2000 version offers the following maximum capacities:
TDM ports: for SDH ports, the Gmux-2000 capacity is two full channelized
SDH ports at the STM-1 level (155.52 Mbps) for a total of 126 E1 streams.
For redundancy, the Gmux-2000 can be equipped with four STM-1 ports (two
of them serving as backup ports).
When using PDH ports at the E1 (2.048 Mbps) level, the maximum
pseudowire emulation capacity is up to 196 E1 streams.
The voice compression capacity is up to 112 E1 streams, with compressed
voice transport over STM-1 and E1 links, as well as over PSN (though the PSN
GbE links).
PSN ports: up to two Gigabit Ethernet (GbE) ports. For redundancy, the
Gmux-2000 can be equipped with four GbE ports (two of them serving as
backup ports).
Advanced packet-handling capabilities, and VLAN and ToS support enable the
operator to provision the highest quality of service (QoS) that modern
packet-switched networks can provide.
The Gmux-2000 system is built in a 6U high modular chassis that can be installed
in standard 19 inch (ANSI) and ETSI racks. The chassis has a total of 9 I/O slots
that can be used as follows:
PSN interface modules: 2 slots
SDH interface modules: 2 slots
I/O modules: up to 7 slots (including the 2 slots that can be used for SDH
interface modules). The I/O slots support pseudowire emulation server
modules, and voice compression modules.
The current Gmux-2000 version supports 1:N protection for pseudowire
emulation server modules, and for voice compression modules using only
internal ports. 1:N protection is one of the Gmux-2000 automatic protection
switching (APS) functions that uses an additional, spare, module to serve as
standby (protection) module for a group of N modules of the same type (the
protected modules) that carry the traffic.
Note
On the supervision terminal screens, the 1:N protection mode is identified as

N+1 protection.
Additional slots are dedicated to control logic, timing, and power supply. To
enhance availability, redundancy is provided for all the critical subsystems (power
supply, control and timing). Either AC or DC power can be used, in accordance
with order. Built-in cooling fans enable dense mounting in racks.
1-2
Overview
Gmux-2000 Ver. 3.2
Internally, the Gmux-2000 uses redundant buses (one set of telecom buses for
the TDM side, and high-speed dual-StarLAN buses for the packet side). The
internal timing and management buses are also redundant.
Gmux-2000 supports a wide range of management capabilities:
SNMP: the Gmux-2000 includes an internal SNMP agent that enables full
SNMP management via SNMP-based network management, for example, by
means of RADview network management stations, in particular the
RADview/TDMoIP Service Center. The internal agent supports SNMPv3,
including the authentication and privacy features, with continued support for
SNMPv1 and SNMPv2.
Supervision terminal: ASCII terminal or a PC running a terminal emulation

program, connected either directly to the Gmux-2000, or through a modem
or any other type of full-duplex data link. This terminal can perform all the
Gmux-2000 supervision and configuration functions, and in particular the
preliminary system configuration. To enable reliable authentication of users,
Gmux-2000 supports the RADIUS (Remote Authentication Dial In User Service)
protocol.
Telnet: by means of any host capable of IP communication with Gmux-2000.

The functions available under the Telnet protocol are similar to those
available from a supervisory terminal, including RADIUS authentication.
SSH: secure access using the SSH (Secure Shell) protocol, using any standard
SSH client utility running on a PC or laptop capable of IP communication with
Gmux-2000.
Gmux-2000 also supports the syslog protocol per RFC3164. This protocol enables
automatic reporting of traps and alarms, with user-configurable severity level
filter, to a specified remote collector (syslog server).
PSN Interfaces
Gmux-2000 uses Gigabit Ethernet links for connection to packet-switched
networks.
The links use Gigabit Ethernet field-replaceable SFP transceivers with optical and
copper GbE interfaces, for meeting a wide range of operational requirements. A
separate, non-traffic carrying, Fast Ethernet copper port enables on-site
monitoring by technical personnel.
Only one dual-port PSN interface module is required in the chassis, however
Gmux-2000 supports two PSN interface modules.
Each external GbE port is assigned its own IP address, and can be independently
provisioned, to enable load balancing. The two ports of a PSN interface module
can also be configured to use link aggregation per IEEE 802.3ad without LACP
(Link Aggregation Control Protocol), thereby providing a single logical link to the
network. Alternatively, redundancy can be used by configuring 1:1 bidirectional
APS (Automatic Protection Switching) at the port level, or at the module level:
Gmux-2000 Ver. 3.2
When redundancy is enabled at the port level (that is, between the two ports
of the same PSN interface module), at any time one port is active and the
other serves as a backup, and therefore each port can be routed along a
different path over the network (dual-homing support).
Overview
1-3
When redundancy is enabled at the module level (that is, between the two
PSN interface modules installed in the chassis), at any time the two ports of
one module are active, and the ports of the other module serve as backup. In
addition, each active port can be routed along a different path, as for
port-level redundancy.
The internal ports of each PSN interface module connect by pairs of Fast Ethernet
ports, through the StarLAN packet bus of the chassis, to each I/O module and to
each control module.
All the external and internal ports of the module are handled by an internal
high-performance Ethernet switch with MPLS support. The switch provides
user-configurable VLAN support for the payload and management traffic. Class of
service is ensured by supporting per-bundle configuration of IEEE 802.1p priority
at Layer 2 and Type of Service (ToS/DiffServ) at Layer 3. For MPLS networks, the
switch also enables specifying a requested Class-of-Service using the EXP bits.
SDH Interfaces
The SDH interfaces are provided by SDH interface modules. Each SDH interface
module has two channelized STM-1 ports. SDH interface modules provide physical
STM-1 interfaces for direct access to the Synchronous Digital Hierarchy (SDH)
transmission cores at the STM-1 level (155.520 Mbps), and also handle the TDM
traffic flow between Gmux-2000 internal E1 ports, and the SDH network.
The physical STM-1 ports can be ordered with fixed intra-office electrical (75
coax) interfaces, fixed optical interfaces with various characteristics (850 and
1310 nm with laser and LED transmitters, for operation over multi-mode or
single-mode fibers) that comply with the applicable requirements of ITU-T Rec.
G.957, G.958 and I.432, or with field-replaceable SFP transceivers with optical
interfaces, for meeting a wide range of operational requirements.
The SDH interface module operates as a dual-port SDH terminal multiplexer (TM)
for the Gmux-2000 chassis that terminates the external STM-1 links and their
overhead. The two module ports support free mapping of any internal E1 port of
any I/O module to any TU-12 tributary unit. Each port is capable of multiplexing
up to 63 E1 streams, for a total module capacity of 126 E1 data streams.
The SDH interface module ports can be configured to provide two independent
STM-1 links, or one STM-1 link with line redundancy. Line redundancy is activated
by configuring 1+1 unidirectional APS (Automatic Protection Switching) per ITU-T
Rec. G.783. This means that the traffic is automatically switched to the other
STM-1 port in case the active STM-1 port or its link fails.
Only one SDH interface module is required in the chassis, however Gmux-2000
supports two modules, for a total of four STM-1 ports per chassis. Therefore, the
Gmux-2000 SDH interface can be used in the following application modes:
1-4
TM with single STM-1 link (single module, second port not connected)
TM with dual STM-1 links (single module, both STM-1 ports connected)
TM with single STM-1 link, and with line redundancy (single module, both
STM-1 ports connected).
TM with dual STM-1 links, with both line and hardware redundancy (two
modules, with all the STM-1 ports connected).
Overview
Gmux-2000 Ver. 3.2
Pseudowire (PW) Emulation Services

Pseudowire emulation services are provided by means of advanced
RAD-developed ASIC packet processors, that handle the TDM-to-packet
conversion. The packet streams generated by packet processors (commonly
referred to as bundles) can be independently routed through the packet-switched
network to the desired destination (each bundle provides a pseudowire
connection).
Packet formats can be selected on a per-bundle basis for optimal transmission
over IP- or MPLS-based networks (UDP/IP and MPLS/ETH, respectively), and each
bundle/pseudowire can be independently routed to any destination.
The following user-configurable protocols are supported, independently for each
pseudowire:
TDMoIP (TDM over IP) in accordance with RFC5087, and TDMoMPLS in

accordance with RFC5087 and ITU-T Rec. Y.1413
HDLCoPSN (HDLC over PSN) in accordance with RFC5087 and RFC4618

(except Clause 5.3 PPP)
CESoPSN (structure-aware TDM circuit emulation over PSN) in accordance

with RFC5086
SAToPSN (structure-agnostic TDM over PSN) in accordance with RFC4553
Gmux-2000 meets the requirements for edge-to-edge simulation of TDM circuits

over PSN in accordance with RFC4197, including high-performance adaptive
timing capabilities.
Each packet processor has a capacity of one E1 stream, supports up to 16
pseudowires, operates independently, and its conversion parameters are
user-configurable to meet a wide range of applications. The total number of
pseudowire connections per module is 112, the total per Gmux-2000 can be up
to 560, and the maximum number of remote devices connected to one
Gmux-2000 can be up to 256.
Within the Gmux-2000, TDM conversion to packet traffic is provided in two ways:
By means of E1 pseudowire emulation server modules. RAD offers server

modules capable of handling 21 E1 independent streams.
Server modules are needed to process the payload received through an SDH
interface module. Three such modules are needed to handle one full STM-1
payload (63 E1 streams). Gmux-2000 supports six E1 pseudowire emulation
server modules and one SDH interface module in the chassis, for a maximum
capacity of 126 E1 streams; with two SDH interface modules, the maximum is
five modules, the corresponding capacity is 105 E1 streams.
For critical applications, 1:N protection can be used: in this case, one server
module serves as protection for the other modules (5 or 4, respectively).
Gmux-2000 Ver. 3.2
By means of E1 pseudowire emulation modules with external E1 interfaces.

RAD offers pseudowire emulation server modules with 28 external E1
interfaces. The E1 interfaces of these modules provide an alternative to SDH
interfaces. In a Gmux-2000 without SDH interfaces, up to seven pseudowire
emulation modules can be installed in the chassis, resulting in a maximum
capacity of 196 E1 streams.
Overview
1-5
A pseudowire emulation server module with external E1 interfaces has 28

independent E1 ports with ITU-T Rec. G.703 balanced (120 ) and (75 )
unbalanced interfaces.
For both types of pseudowire emulation modules, the framing method is userselectable per port, in accordance with the specific application requirements:
Unframed for transparent E1 transport. This permits only one pseudowire per
port.
G.704 framing. The framing mode can be either basic G.704 framing, suitable
for applications that require CCS, or G.704 framing with timeslot 16
multiframe (G.704 multiframe mode) for applications that require CAS.
With G.704 framing, up to four independent pseudowires per port are
supported. In addition, CRC-4 support per ITU-T Rec. G.706 can also be
enabled, for full E1 performance monitoring.
Note
For compatibility, Gmux-2000 also supports the previous generation of

pseudowire circuit emulation (CE) module, which do not support the full range of
pseudowire emulation protocols, and have a capacity of only 16 bundles per E1
port.
Voice Trunking Services

Voice trunking services are provided by means of voice compression modules,
containing complete voice compression subsystems with a compression capacity
of 16 E1, respectively 12 E1, voice trunks. The voice trunks can be connected
either via the external E1 (PDH) user-side links located on the voice compression
module itself, or via the internal ports, which can be mapped to the desired TUs
of the STM-1 (SDH) ports located on the SDH interface modules.
These modules enable Gmux-2000 systems to deliver voice traffic, including
inband signaling (DTMF, MFR2, and MFC), voiceband modems and Group III fax up
to 14.4 kbps, over the following types of links:
TDM links: E1 (PDH) links located on the voice compression module itself, or
STM-1 (SDH) ports located on the SDH interface modules
GbE links, located on the PSN interface modules.
In addition to voice traffic, voice compression modules can also transparently

transfer selected timeslots of the voice trunks.
The modules support the ITU-T Rec. G.723.1 and G.729 Annex A voice
compression algorithms, as well as ITU-T Rec. G.711 (A-law and -law PCM), and
use TDMoIP multiplexing for efficiently transporting the payload of E1 trunks over
TDM (E1 or SDH) networks. Packet structure is selectable (TDMoIP for UDP/IP
networks, and AAL2oMPLS for MPLS networks). In addition to standard packet
structures, RAD proprietary versions of these protocols are also offered to
achieve significantly higher bandwidth efficiency.
Advanced digital signal processing techniques ensure highly-reliable service,
unaffected by the use of voice compression. These techniques include:
1-6
Per-channel voice activity detection (VAD) and silence suppression
Built-in echo cancellation for delays up to 32 msec per ITU-T Rec. G.168
Overview
Gmux-2000 Ver. 3.2
Relaying of Group III fax, modems at commonly used rates and standards,
inband signaling and custom tones.
Where compression cannot be used, for example, for non-standard inband

signaling and modem protocols, voiceband signals can be faithfully
transmitted using selectable PCM or ADPCM coders.
To prevent voice degradation when traffic passes multiple modules, a RAD

proprietary super-tandem mode ensures that voice signals pass compression only
once, irrespective of the number of hops on the transmission path.
At the highest compression ratio, the 16-port modules enable compressing up to
16 E1 voice trunks for transport over a single E1 network link (up to 16:1
compression ratio); for 12-port modules, the maximum compression ratio cannot
exceed 12:1. Compressed voice traffic can be routed over up to 32
independently-configurable bundles, where a bundle can carry any number of
timeslots, up to a full E1 voice port (30 channels). Each compressed voice bundle
can be independently connected to any desired network-side port (either TDM
port or GbE port).
Moreover, the voice compression modules support both point-to-point and
point-to-multipoint (channelized) applications over their E1 network-side links,
with user-configurable link bandwidth assignment per destination (the timeslots
available on each E1 network-side link can be assigned to up to 10 independent
subchannels).
To guarantee high service quality together with highly efficient utilization of
transport links, voice compression modules support the ITU-T Rec. Q.50 (Annex A
and B) bandwidth control protocol, as well as a proprietary bandwidth limiting
algorithm that ensures quality degrades gradually during intervals of excessive
traffic load. To preserve service quality, a separate mechanism makes it possible
to block the setup of new modem calls when bandwidth utilization exceeds
user-configurable, application-specific thresholds.
The modules provide full support for a wide range of signaling protocols. This
includes CAS and R2 signaling (transferred end-to-end either transparently, or
after translation in accordance with user-specified profiles) as well as optimized
HDLC-based transfer of CCS protocols such as ISDN, QSIG, Signaling Scheme 7
(SS7), etc. The CCS timeslots are user-selectable, independently for each voice
port, with a maximum of two timeslots per port.
The voice compression modules have both TDM and packet ports:
The TDM ports comprise a set of 16, respectively 12, voice (user-side) E1
ports and a separate set of 2 data (network-side) E1 ports
The packet ports comprise 2 network-side ports, to connection to

Gmux-2000 internal packet buses.
To provide maximum application flexibility and avoid the need for additional
equipment, each set of TDM ports has both external ports with ITU-T Rec. G.703
interfaces located on the module panel, and internal ports that can be connected
via the Gmux-2000 telecom buses to the SDH ports located on the SDH interface
modules that may be installed in the chassis (each internal module port can be
independently mapped to any desired VC-12).
Gmux-2000 Ver. 3.2
Overview
1-7
The maximum number of voice compression modules that may be installed in a

Gmux-2000 chassis is 7. Note however that 2 out of the 7 Gmux-2000 I/O slots
that support these modules also support SDH interface modules, and therefore
the maximum voice compression capacity (7 modules) can be reached only when
using the external module ports. The maximum number of modules decreases by
one for each installed SDH interface module:
For 16-port modules, the maximum chassis capacities are as follows:
Without SDH interface modules in the chassis, 7 voice compression

modules yield 112 E1 voice trunks per chassis (3360 voice channels).
One SDH interface module and 6 voice compression modules yield a

maximum capacity of 96 E1 trunks per chassis (2880 voice channels)
Two SDH interface modules and 5 voice compression modules yield a

maximum capacity of 80 E1 trunks per chassis (2400 voice channels).
With 12-port modules, the respective maximum capacities are 84, 72, and 60
E1 voice trunks (up to 2520, 2160, and 1800 voice channels, respectively).
To improve availability, the data ports of the voice compression modules can be
configured to provide backup for the connection to the network. In this case, the
data ports operate in pairs: in each pair, one port serves as the main (primary)
port, and the other as backup (secondary) port. At any time, only one port of
each pair carries traffic. As long as the primary port can carry the traffic, it is
automatically selected as the active port; in case of a problem on the link or in
the port hardware, the traffic is automatically switched to the backup port.
Switching is revertive.
When using only their internal ports, 1:N protection is also available for the voice
compression modules.
Control Functions
The Gmux-2000 management subsystem is located on a dedicated control
module. Only one control module is necessary, however the Gmux-2000 chassis
system is designed to use two control modules, thereby providing a hot-standby
capability for the Gmux-2000 system control functions.
The main functions of the control module are as follows:
1-8
Overview
Interfacing with the external management functions (SNMP-based network

management stations, supervision terminals, or Telnet/SSH hosts), syslog
servers, and authentication servers (RADIUS). Each control module has
several interfaces:
Two out-of-band interfaces: a serial RS-232 asynchronous port and a

10/100BASE-TX Ethernet interface
Ethernet inband interfaces toward the PSN, via a Layer 2 switch.
Control of Gmux-2000 system operation. The modules installed in the chassis

are controlled via redundant management buses. The control modules store
the application software, which determines the system capabilities and
characteristics. This software can be remotely updated through the
management link.
Gmux-2000 Ver. 3.2
Storage of configuration databases. The configuration databases can be

uploaded and downloaded through the management link.
Collection of operational history (alarms, configuration error messages,

performance statistics, etc). This information can be read by local
management, as well as from remote locations through the management link.
A real-time clock in the Gmux-2000 control module enables to time stamp
each individual operational history item. The real-time clock can be set either
manually, or be automatically synchronized to an external time reference,
using the NTP (Network Time Protocol).
Timing
Gmux-2000 timing subsystem includes a central timing subsystem, located on the
control module, and local timing subsystems located on the individual I/O
modules. Since Gmux-2000 is normally equipped with two control modules,
redundancy is also available for the central timing subsystem.
The various clock signals needed by the Gmux-2000 are derived as follows:
Receive clocks: the receive clock of each interface is extracted from the
corresponding received data stream. For the TDM side, this is the received
signal; for the PSN side ports, the clock is derived from the average rate of
received data, by means of a special adaptive timing recovery circuit.
Transmit clock: the transmit clock of the each TDM interface can be locked to
one of the following sources:
System (nodal) clock provided by the central timing subsystem
TDM receive clock, or, when applicable, adaptive clock of the same
interface.
The Gmux-2000 system clock can be locked to any of the sources listed above for
the transmit clocks. In addition, the system clock can also be locked to external
station clocks (1.544/2.048 MHz or 1.544/2.048 Mbps), connected via interfaces
located on the CONTROL module, or to an internal clock oscillator. A system clock
output is also available in the same interface.
External Alarm Monitoring and Reporting

The Gmux-2000 chassis includes a connector for reporting chassis alarms, by
means of dry-contacts, to external equipment (buzzers, dialers, etc.).
The connector also has an external alarm input for monitoring external sensors, a
useful capability in unmanned locations.
Power Supply Subsystem

The Gmux-2000 chassis can use AC (115 or 230 VAC, 50/60 Hz) or DC (24 or
48 VDC) sources. The chassis can be equipped with up to three power supply
modules, thereby enabling redundancy for the power supply subsystem.
Gmux-2000 Ver. 3.2
Overview
1-9
1.2
Typical Applications
Pseudowire Emulation Services for TDM Transport

Figure 1-1 shows a basic TDM transport application, in which the Gmux-2000
provides the connection between the PSTN and an SDH network over a
packet-switched network:
The E1 trunks of the PSTN V5 switches are connected to the E1 interfaces of

an Gmux-2000. The Gmux-2000 converts these trunks to data streams, which
are sent via the GbE PSN interface to the packet-switched network.
The individual packet streams reach the other Gmux-2000, which multiplexes
them into an STM-1 signal. This signal is connected to an STM-1 ADM port,
and thus reaches the SDH network.
Figure 1-1. Basic Transport Application

Figure 1-2 shows another typical Gmux-2000 application in which it provides the
equivalent of leased line services over the packet-switched network.
In the application of Figure 1-2, the Gmux-2000 receives individual packet
streams from several TDMoIP or TDM pseudowire access gateways and/or legacy
multiplexers with TDMoIP interfaces (for example, modular Megaplex-2100 E1/T1
Integrated Access Devices equipped with ML-IP IP main link modules).
These packet streams reach the PSN interface of the Gmux-2000 via the
packet-switched network. The Gmux-2000 retrieves the original E1 streams and
multiplexes them into an STM-1 signal, which is connected via an ADM to the SDH
network.
In both applications, Gmux-2000 provides flexible, robust connections because it
works over a packet-switched network, yet enables the users to design
hierarchical, reliable timing distribution in accordance with the specific application
requirements, despite the intervening packet-switched network.
1-10
Gmux-2000 Ver. 3.2
Figure 1-2. Gmux-2000 as Access Multiplexer
Voice Compression Applications

High Capacity Toll Bypass over SDH Networks
Figure 1-3 shows a Gmux-2000 equipped with voice compression modules used
to provide a high-capacity toll bypass link over the SDH network.
Up to 5 or 6 VC-E1/16
2 E1
16 E1
16 E1
2 E1
VC-E1/16
STM1
Up to 80 or 96
E1
PSTN Switch
STM-1
Gmux-2000
with VC-E1/16 and
STM1 Modules
SDH
Network
Up to 80 or 96
E1
STM-1
Gmux-2000
with VC-E1/16 and
STM1 Modules
PBX
Backup
Figure 1-3. High Capacity Toll Bypass over SDH Network

In this application, a high-capacity PBX, located on customers premises, may be
directly connected to a PSTN switch via a large number of E1 trunks. The
maximum number of E1 trunks depends on the desired protection level for the
STM-1 link:
Gmux-2000 Ver. 3.2
1-11
When only one SDH interface module is used (line redundancy only), the
maximum number of E1 trunks supported by one Gmux-2000 chassis is 96
(up to 2880 or 2976 compressed voice channels, depending on the number
of voice timeslots per trunk, 30 or 31)
When two SDH interface modules are used (line and hardware redundancy),
the maximum number of E1 trunks supported by one Gmux-2000 chassis is
80 (up to 2400, or 2480 compressed voice channels, depending on the
number of voice timeslots per trunk, 30 or 31).
High Capacity Toll Bypass over Packet Switched Networks

Figure 1-4 shows a Gmux-2000 equipped with voice compression modules used
to provide a high-capacity toll bypass link over a packet switched network.
Up to 112
E1
PBX
GbE
Packet
Switched
Network
GbE
Gmux-2000
with VC-E1/16 and
GbE Modules
Up to 112
E1
Gmux-2000
with VC-E1/16 and
GbE Modules
PBX
Figure 1-4. High Capacity Toll Bypass over Packet Switched Network
This application uses the packet ports of the voice compression modules to direct
the compressed voice traffic (or any part of this traffic, as configured by the
user) to the desired GbE port(s) installed in the Gmux-2000. The PSN connection
characteristics are configured by defining bundles.
Voice compression modules can operate over IP and/or MPLS packet switched
networks, in accordance with users configuration for each bundle.
PSN connections can be used in parallel with any type of TDM network
connections.
Connecting Multiple Remote Call Centers

Figure 1-5 shows a Gmux-2000 equipped with voice compression modules that
provides access links to from the corporate PBX or from a PSTN switch to several
remote call centers, each using one Vmux-2100 Voice Trunking Gateway.
When equipped with 16-port voice compression modules, the maximum capacity
of the Gmux-2000 is 112 E1 trunks, using only one E1 link to connect a group of
up to 16 E1 trunks to each call center.
The connection to the Vmux-2100 units is made over the external data ports. In
this application, a separate module is used for each remote location: in this way,
availability can be greatly enhanced by using the backup function: each E1 link
can be backed up by using the other data port.
Using the point-to-multipoint capability of the voice compression modules
enables connecting to an even larger number of remote locations, because each
data port can connect to up to 10 separate locations.
Voice compression modules also supports inband management of the Vmux-2100
units: in Figure 1-5, a network management station, for example,
RADview-SC/Vmux, connected to a GbE port of the Gmux-2000 unit can manage
inband the Vmux-2100 units connected via Gmux-2000 data ports.
1-12
Gmux-2000 Ver. 3.2
Up to 7 VC-E1/16
16 E1
2 E1
16 E1
2 E1
Up to
112 E1s
Gmux-2000
with VC-E1/16
Modules
PBX or
PSTN Switch
Figure 1-5. Remote Call Centers (Main Link Hot Standby Mode)
Voice Trunking over Multiple E1 Streams

provides voice trunks between two MSCs with STM-1 interfaces over E1
infrastructure, either as a replacement for access to SDH infrastructure, or when
no SDH infrastructure is available.
16 E1
2 E1
STM-1
16 E1
STM1
2 E1
VC-E1/16
STM-1
MSC
Up to 10 or 12 E1s
(Compressed)
Gmux-2000
with VC-E1/16 Modules
STM-1
Gmux-2000
with VC-E1/16 Modules
MSC
Backup
Figure 1-6. Voice Trunking over Multiple E1 Streams (Main Link Redundancy
Mode)
The maximum number of E1 trunks depends on the desired protection level for
the STM-1 link to each MSC:
Gmux-2000 Ver. 3.2
When only one SDH interface module is used (line redundancy only), the
maximum number of E1 trunks supported by one Gmux-2000 chassis is 96
1-13
When two SDH interface modules are used (line and hardware redundancy),
the maximum number of E1 trunks supported by one Gmux-2000 chassis is
80.
Voice compression modules also support inband management of the Gmux-2000

units: in Figure 1-6, a network management station, for example,
RADview-SC/Vmux, connected to a GbE port of one Gmux-2000 unit can manage
inband the other Gmux-2000 unit, via the voice compression module data ports.
Voice Trunking over STM-1 Link

provides voice trunks from a remote location over an STM-1 link.
Using voice compression reduces the number of VC-12s needed on the STM-1
link, thereby freeing bandwidth for other applications.
16 E1
2 E1
STM-1
16 E1
2 E1
STM1
VC-E1/16
STM-1
(Compressed)
STM-1
(Compressed)
STM-1
(Uncompressed)
Voice
Switch
Digital
Cross
Connect
STM-1
(Uncompressed)
Gmux-2000
with
VC-E1/16 Modules
Figure 1-7. Voice Trunking over STM-1 Link
Interoperability with Vmux Family Products

Voice compression modules are fully interoperable with the RAD Vmux family of
Voice Trunking Gateways. Figure 1-8 shows a Gmux-2000 equipped with voice
compression modules connecting a large number of E1 voice trunks to multiple
locations, using a much smaller number of E1 links to carry the compressed voice
traffic.
An important advantage of Gmux-2000 voice compression module is that it
provides for inband management of the individual Vmux units by means of the
same network management station, for example, RADview-SC/Vmux, that is used
to manage the Gmux-2000 in which the module is installed. The management
station can connect to the Gmux-2000 from a remote location, via the GbE
module.
1-14
Gmux-2000 Ver. 3.2
Gmux-2000
with
VC-E1/16 Modules
Figure 1-8. Interoperability with Vmux Equipment over TDM Networks

Figure 1-9 shows a similar application that uses an IP network for connecting to
the Vmux-2100 units.
Up to 112
E1
GbE
Packet
Switched
Network
E1
GbE
Gmux-2000
with VC-E1/16 and
GbE Modules
Gmux-2000
with VC-E1/16 and
GbE Modules
Vmux-2100
E1
Vmux-2100
E1
ETH
ETH
Figure 1-9. Interoperability with Vmux Equipment over PSN Networks
Gmux-2000 Ver. 3.2
1-15
1.3
Equipment Description
This section provides information on the physical construction and hardware

configuration options available for the Gmux-2000.
System Structure
Gmux-2000 can simultaneously support pseudowire emulation and voice trunking
services. The following sections describe each type of service.
TDM Pseudowire Emulation Services

The structure of a Gmux-2000 system equipped for TDM transport using
pseudowire emulation is shown in Figure 1-10.
Management Ports Station Clocks
(IN/OUT)
RS-232 Ethernet
Management
Subsystem
Timing
Subsystem
Power Input
Power Supply
Subsystem
Cooling Fans
STM-1 Ports
SDH
Interface
Subsystem
Pseudowire
Emulation
Server
Subsystem
PSN
Interface
Subsystem
External
E1 Ports
PSN
Interfaces
Pseudowire
Emulation
Subsystem
with External
E1 Interfaces
Gmux-2000
Figure 1-10. Gmux-2000 System Structure for TDM Pseudowire Emulation
Services
The Gmux-2000 configuration includes the following subsystems:
1-16
TDM interfacing subsystem: provides interfaces to the TDM users equipment

or network. Two types of interfaces are available:
SDH interfaces, located on separate modules
PDH E1 interfaces, collocated with the packet processors.
Gmux-2000 Ver. 3.2
Packet processing subsystem: performs the conversion between the circuit

switched (TDM) and packet switched networks, using edge-to-edge
pseudowire emulation techniques.
PSN interface subsystem: interfacing to the packet-switched network (PSN),

and handling of the packet-switched traffic (Layer 3/4 routing and Layer 2
switching functions).
Timing subsystem (collocated with the management subsystem): provides

timing signals to all the Gmux-2000 circuits, and external (station and nodal)
clock interfaces.
Management (control) subsystem: controls Gmux-2000 operation, stores its

software and configuration, and provides interfaces for local and remote
management.
Power supply subsystem: includes power inlet and power supply modules.
Cooling fans: for increased system reliability.
The intrasystem connections (traffic, timing, power distribution and

management) are located on the backplane. Two types of traffic buses are used:
TDM bus: carries the TDM traffic between the SDH interface modules and the
internal ports of other modules, in accordance with the required service:
either pseudowire emulation server modules, or internal TDM ports of voice
compression modules (see below). The TDM bus consists of multiple telecom
(19.44 MHz) buses.
Packet bus: carries the packet traffic between the PSN ports and I/O modules
(pseudowire emulation and voice compression modules). Consists of multiple
collision-free Fast Ethernet connections having a star (StarLAN) topology.
Voice Compression Services

The structure of a Gmux-2000 system equipped for voice compression services is
shown in Figure 1-11.
The Gmux-2000 configuration used for voice compression services is similar to
that used for TDM pseudowire emulation, except that for voice trunking
applications, a voice compression subsystem replaces the pseudowire emulation
subsystem. The voice compression subsystem has its own set of TDM interfaces.
These interfaces include (see description starting on page 1-6):
PDH E1 interfaces, located on the voice compression modules
Internal SDH interfaces, which connect to the SDH network via the SDH
interface subsystem.
The voice compression subsystem is used to compress voice and the associated
signaling for transmission over packet switched networks, and over E1 links
(either links connected to the external E1 ports or mapped to the desired TUs of
the STM-1 ports).
In addition to the TDM links, the compressed voice can also be inserted in voice
compression bundles, and connected via the Gmux-2000 packet buses to the PSN
interface modules, for transport over the PSN.
Gmux-2000 Ver. 3.2
1-17

Management Ports Station Clocks
(IN/OUT)
RS-232 Ethernet
Management
Subsystem
Timing
Subsystem
Power Input
Power Supply
Subsystem
Cooling Fans
STM-1 Ports
SDH
Interface
Subsystem
Internal
SDH Ports
External
E1 Voice
Ports
Voice
Compression
Subsystem
PSN
Interface
Subsystem
PSN
Interfaces
External
E1 Data
Ports
Gmux-2000
Figure 1-11. Gmux-2000 System Structure for Voice Compression Services
Physical Description
Front Side
Figure 1-12 shows a general front view of a Gmux-2000 chassis. The Gmux-2000
chassis is modular, and has a height of 6U.
The chassis is intended for installation in 19-inch (ANSI) and ETSI racks using rack
mounting kits available from RAD (not shown in Figure 1-12), however it can also
be installed on shelves.
Air intake and discharge vents are located on the side walls.
1-18
Gmux-2000 Ver. 3.2
Figure 1-12. Gmux-2000 Front View
Rear Side
The rear side of the chassis has physical slots in which plug-in modules are
installed to obtain the desired equipment configuration:
The management and power supply modules, and the fan tray, are always
installed in dedicated chassis slots, called system slots
PSN interfacing modules, SDH interfacing modules, pseudowire emulation

server modules (either with or without external interfaces), and voice
compression modules are installed in the other chassis slots (called I/O slots).
The I/O slots are identified as I/O-1 to I/O-9.
All the external connections are made to connectors located on the plug-in
modules; the rear panel has only one connector for external alarms.
Figure 1-13 and Figure 1-14 show typical Gmux-2000 rear views, and identify the
functions of the various slots. The unit shown in Figure 1-13 is equipped for TDM
traffic transport services, and that shown in Figure 1-14 is equipped for voice
trunking services.
Gmux-2000 Ver. 3.2
1-19

or
or

or
or
Power Inlet
(PI) Module
INLET
P.S. 3
P.S. 2
P.S. 1
CT RL. 2
CRTL. 1
Gmux-2000
I/O-9
I/O-8
I/O-7
I/O-6
I/O-5
I/O-4
I/O-3
I/O-2
I/O-1
ALA RM S
PWR
M AJ . ALARM
T ST
M IN . ALA RM
FAN-TRAY
Slot:
PW R
FLT
L ASER
CL ASS
1
LOC
REM
AC-IN
RX
TX
STM1
ACT
LINK
GE 1
L ASER
CL ASS
1
POWER
POWER
LOC
RDY
REM
ALM
I/O 9
I/O-9
RX
TX
GE 2
LINK
PAUSE
LINK
PAUSE
ACT
TX
RX
TX
RX
FLT
Slot for PSN

I/O-8
MONITOR
GbE
PS-AC
I/O-7
I/O 7
I/O-6

I/O-5
I/O 5
I/O-4
I/O 4
I/O-3
I/O 3
I/O-2
I/O 2
I/O-1
I/O 1
POWER
POWER
2
PS-AC
PS-AC
1
9 10 11 12 13 14 15 16
17 18 19 20 21
ACT
FLT
POWER
E1.PW.SRV / 21
POWER
1
1
10 11 12 13 14 15 16
17 18
19 20 21
ACT
FLT
PS-AC
E1.PW.SRV / 21
OUT
IN
SD
1
ACT
LINK
10 11 12 13 14 15 16 17 18 19 20 21
ACT
S TAT ION CLOCK
FLT
E1.PW.SRV / 21
ACT
CONTROL
ETH
CONTROL
FLT
DPW
OUT
IN
SD
ACT
LINK
S TAT ION CLOCK
ACT
CONTROL
ETH
CONTROL
Slots for
Servers
and/or
E1 Interfaces
FLT
DPW
Fan Tray
System Slots
I/O Slots

Figure 1-13. Typical Gmux-2000 Rear View (Unit Equipped for TDM Traffic Transport Services)
or
Power Inlet
(PI) Module
INLET
P.S. 3
P.S. 2
P.S. 1
CT RL. 2
CRTL. 1
Gmux-2000
I/O-9
I/O-8
I/O-7
I/O-6
I/O-5
I/O-4
I/O-3
I/O-2
I/O-1

or
ALARM S
PW R
M AJ. ALARM
T ST
M IN. ALARM
FAN -TRAY
Slot:
PW R
FLT
LASER
CLASS
1
LOC
REM
AC-IN
RX
TX
STM1
ACT
LINK
GE 1
LASER
CLASS
1
POWER
POWER
GbE
TX
LOC
RDY
REM
ALM
I/O-9
RX
GE 2
LINK
PAUSE
LINK
PAUSE
ACT
TX
RX
TX
RX
FLT
I/O-8
MONITOR
I/O 9
Slot for PSN
PS-AC
I/O-7
I/O 7
I/O-6

I/O-5
I/O 5
I/O-4
I/O 4
I/O-3
I/O 3
I/O-2
I/O 2
I/O-1
I/O 1
POWER
POWER
2
PS-AC
PS-AC
LOC
1
11
13
REM
15
ACT
LOC
FLT
REM
2
POWER
POWER
10
12
14
16
1-16 E1
VC-E1/16
LINK
LOC
1
11
13
REM
15
ACT
LOC
FLT
REM
PS-AC
10
12
16
14
11
13
15
ST ATION CLOCK
CON TROL
ACT
ACT
DCE
FLT
REM
2
ET H
REM
LOC
LINK
10
12
14
16
1-16 E1
VC-E1/16
CONTROL
LOC
1
ACT
LINK
IN
SD
1-16 E1
VC-E1/16
OUT
LINK
LOC
FLT
1
11
13
REM
15
ACT
LOC
OUT
IN
LINK
FLT
REM
2
SD
ACT
10
12
14
16
1-16 E1
VC-E1/16
LINK
LOC
ST ATION CLOCK
1
11
13
REM
15
ACT
LOC
CONTROL
ET H
CON TROL
DCE
ACT
FLT
FLT
REM
2
10
VC-E1/16
12
14
16
Slots for
Voice Compression
Modules
1-16 E1
LINK
Fan Tray
System Slots
I/O Slots

Figure 1-14. Typical Gmux-2000 Rear View (Unit Equipped for Voice Trunking Services)
1-20
Gmux-2000 Ver. 3.2
The module types that can be installed in Gmux-2000 chassis slots are listed in
Table 1-1. Note that slots I/O 6 and I/O 7 can also be used as alternative slots for
PSN interface and SDH interface modules, respectively (their recommended slots
appear in bold in Table 1-1). This alternative is also identified in Figure 1-13 and
Figure 1-14.
Table 1-1. Gmux-2000 Chassis Slot Assignments

Slot Type
Module Types
Supporting Slot Designations
Power inlet module (115/230 VAC, 48 VDC or INLET

24 VDC)
System Slot
I/O Slot
Power supply module (115/230 AC, 48 VDC

or 24 VDC)
PS.1, PS.2, PS.3
Control & clock module
CTRL.1, CTRL.2
Pseudowire emulation server module
I/O-1 to I/O-5, I/O-7, I/O-9
Pseudowire emulation module with external

E1 interfaces
I/O-1 to I/O-5, I/O-7, I/O-9
Voice compression module
I/O-1 to I/O-5, I/O-7, I/O-9
SDH interface module
I/O-7, I/O-9
PSN interface module
I/O-6, I/O-8
Modules
Table 1-2 lists the modules currently available for the Gmux-2000, their
functions, and the corresponding chassis slots:
System modules are described in Chapter 2.
For a concise description of I/O modules, see the Description of I/O Modules
section below; for additional details, refer to the corresponding module
Installation and Operation Manual.
Table 1-2 also presents the Gmux-2000 system capacity.

Table 1-2. Gmux-2000 Modules
Maximum Chassis
Capacity
Module
Function
Can be Installed in
PI/AC
3-port AC power input module

(115/230 VAC, 50/60 Hz)
INLET
PI/48
2-port DC power input module (48 VDC)
INLET
PI/24
DC power input module (24 VDC)
INLET
PS-AC
AC power supply module (115/230 VAC,

50/60 Hz)
PS.1, PS.2, PS.3
PS-DC
DC power supply module (48 VDC)
PS.1, PS.2, PS.3
PS-DC 24V
DC power supply module (24 VDC)
PS.1, PS.2, PS.3
Gmux-2000 Ver. 3.2
1-21

Maximum Chassis
Capacity
Module
Function
Can be Installed in
CONTROL
Control module, contains the Gmux-2000

control circuits and its timing subsystem
CTRL.1, CTRL.2
STM1
Dual-port SDH interface module
I/O-7, I/O-9
GbE
Dual-port GbE PSN interface module
I/O-6, I/O-8
E1-PW-SRV/21
21-port E1 pseudowire emulation server

module
I/O-1 to I/O-5, I/O-7,

I/O-9
E1-PW/28
28-port E1 pseudowire emulation module

with external E1 ports
I/O-1 to I/O-5, I/O-7,

I/O-9
VC-E1/16
16-port E1 voice compression module
I/O-1 to I/O-5, I/O-7,

I/O-9
VC-E1/12
12-port E1 voice compression module
I/O-1 to I/O-5, I/O-7,

I/O-9
Note
For compatibility with previous Gmux-2000 versions, pseudowire circuit emulation

(CE) modules, E1-CE/28 and E1-CE-SRV/21, are also supported. Starting with
Gmux-2000 version V3.2, pseudowire emulation modules, which have enhanced
capabilities, are used to provide the functions of circuit emulation modules.
Description of Gmux-2000 Modules

This section provides a concise description of the functions of the Gmux-2000
system modules. Refer to Chapter 2 for a functional description of these
modules.
Power Supply Modules

The Gmux-2000 requires power supply (PS) modules and separate power input
(PI) module.
The Gmux-2000 can use either AC or DC power sources. The PI and PS modules
must match the selected power source (see Table 1-2).
The Gmux-2000 chassis has three PS slots, thereby enabling the installation of
three PS modules.
The method used to connect power to the PS modules depends on the power
source, AC or DC:
1-22
AC power: the AC power inlet module, PI/AC, has three separate inputs, one
for each AC PS module: this enables connecting each PS module to an
independent power circuit. Note that all the AC power inputs must be
simultaneously connected/disconnected by means of an external ON/OFF
switch or circuit breaker.
DC power: the DC power inlet modules enable connecting simultaneously two

separate DC power sources with the same nominal voltage (either 48 VDC or
24 VDC), in parallel, to each DC PS module. This enables connecting one DC
Gmux-2000 Ver. 3.2
source to all the PS modules, or connecting in parallel two sources, for

redundancy. Two types of DC power inlet modules are offered:
DC power inlet module with two DC inputs. Currently, this version is

available for 48 VDC sources, and is designated PI/48
DC power inlet module with single DC input. Currently, this version is

available for 24 VDC sources, and is designated PI/24. Unlike PI/48, which
occupies the whole PI slot of the chassis, PI/24 is a half-width module,
and therefore two PI/24 modules can be installed in the PI slot. Together,
the two PI/24 modules provide two DC inputs, the same as the full-width
PI version, but the advantage of using half-width PI modules is that each
one can be removed and replaced, without disconnecting both power
sources from the DC PS modules.
RAD offers PS modules with two ratings: 200W and 300W, and therefore three PS
modules can supply a maximum of 600 W, respectively 900W, of power to the
modules installed in the chassis. The actually required power depends on the
modules installed in the chassis, but with the currently offered modules two
200W PS modules are sufficient to power a fully-equipped chassis.
Note
Contact RAD Technical Support Department if it is necessary to use both 200W

and 300W PS modules in the same chassis.
Installing more PS modules than is required to power the installed modules has
the advantage of redundancy. For example, when the chassis requires two PS
modules, it is still recommended to install the third PS module as well, for 2+1
redundancy:
Note
With a redundant PS module, all the three modules are connected to power,
and when operating normally all share the load.
In case any one PS module fails or loses its input power, the remaining PS
modules continue to supply power to the chassis, without any service
disruption. Therefore, a malfunctioning PS module can be replaced online;
after replacement, the module starts again sharing the load. Switch-over is
thus automatic and hitless.
In this example, should the total required power exceed the maximum that can be
provided by two PS modules (400W, respectively 600W), redundancy is no longer
available, because three PS modules must be operational to supply the power.
Load sharing is still active.
CONTROL Module
The CONTROL module performs two main functions:
Gmux-2000 Ver. 3.2
Control functions:
Interfacing with the network management stations, supervision terminals,

and Telnet hosts.
Control of Gmux-2000 system operation.
Storage of application software, which determines the capabilities and

features provided by the Gmux-2000.
1-23
Storage of configuration databases.
Collection of operational history (alarms, performance statistics, etc.).
Clock and timing generation functions: generates nodal clock signals for the
Gmux-2000 system, locked to user-selected internal or external sources.
Only one CONTROL module is necessary per Gmux-2000 chassis, however the
chassis has two slots dedicated to this type of module. The second slot is used to
install a redundant CONTROL module, thereby providing a hot-standby capability
for the Gmux-2000 system control and timing functions.
When a second CONTROL module is installed, the two modules operate as a
master/slave pair; one module is the active (master) module, and the other
serves as a hot standby (slave).
Only the master module communicates with the management station/terminal
and actively manages the Gmux-2000 system. The slave module is automatically
updated by the master module with all the configuration and status data, and
therefore the slave can take over at any time without disrupting system
operation. The slave module communicates only with the master module.
Moreover, the transmit line in the slave serial port connectors is disabled, to
enable physical connection in parallel (e.g., by means of a Y cable) to a
management facility.
Note
The station clock interfaces can also be configured to enable parallel connection
by means of a Y-cable.
Description of I/O Modules

This section provides a concise description of the I/O modules available for the
Gmux-2000 system. For complete functional descriptions of these modules, refer
to the module Installation and Operation Manuals.
STM1 SDH Interface Module

The STM1 module operates as a dual-port SDH terminal multiplexer (TM) for the
Gmux-2000 chassis that terminates STM-1 links and their overhead. The module
has two independent channelized STM-1 ports, where each port is capable of
multiplexing up to 63 E1 streams taken from any internal E1 ports of the I/O
modules installed in the Gmux-2000 chassis into one STM-1 data stream. The
total module capacity is 126 E1 data streams.
The STM1 module ports can be configured to provide two independent STM-1
links, or one STM-1 link with line redundancy. Line redundancy is activated by
configuring 1+1 unidirectional APS (Automatic Protection Switching). This means
that the traffic is automatically switched to the other STM-1 port in case the
active STM-1 port or its link fails. Installing two STM1 modules provides both line
and hardware redundancy.
The STM1 module supports free mapping of any internal E1 port of any I/O
module to any TU-12 tributary unit carried in a VC-4 virtual container.
The STM1 module can be used in conjunction with E1-PW-SRV/21 modules, which
include pseudowire emulation processors needed to process the STM-1 payload,
1-24
Gmux-2000 Ver. 3.2
to prepare it for being transported over the packet-switched network, and in

conjunction with VC-E1/16 and VC-E1/12 voice compression modules.
STM1 modules can be ordered in the following versions, which differ with respect
to the interface types of the external STM-1 ports:
Fixed electrical interfaces for intra-office applications that require direct,

short-range connection to higher-level SDH multiplexers. An electrical
interface has two BNC connectors and requires two 75 coaxial cables per
port.
Fixed optical interfaces for short-haul and long-haul applications, complying

with ITU-T Rec. G.957, terminated in SC connectors. These interfaces require
two fibers per port (a transmit fiber and a receive fiber). RAD offers a wide
range of fixed optical interfaces, which include LED and laser sources
operating at 850 or 1310 nm over multi-mode and single-mode fiber, and
therefore can optimally meet a wide range of system requirements. The
long-haul optical interface has a range of up to 40 km (26 miles), thereby
enabling remote access to regional and national SDH transmission networks.
SFP sockets for field-replaceable standard SFPs with optical interfaces

(typically, SFPs use LC connectors). This enables selecting the optimal
interface for each application and fiber type. RAD offers a wide range of
SFPs, including high-performance SFPs that are also offered in WDM versions
using a single fiber instead of the customary two fibers, and can achieve
ranges up to 80 km/50 miles.
The STM1 module supports flexible timing modes for its SDH ports:
Receive path: the receive path recovers the clock signal from the STM-1 line
signal. The recovered STM-1 receive clock can be provided as a timing
reference for the Gmux-2000.
Transmit path: the transmit timing of the STM-1 interface can be either
derived from the Gmux-2000 system timing, or locked to the locally recovered
STM-1 receive clock (loopback timing).
STM1 operating mode is determined by commands received from the Gmux-2000

CONTROL module. The CONTROL module can also download software updates to
the module.
E1-PW-SRV/21 Pseudowire Emulation Server Module

E1-PW-SRV/21 is a server module intended for use in Gmux-2000 equipped with
SDH interfaces that provides E1 circuit emulation services over packet-switched
networks using the TDMoIP protocol. The module has a capacity of 21 E1
(2.048 Mbps) trunks, each served by an independent E1 interface. Each E1
interface can be mapped to any desired VC-12 in any STM1 module. Therefore, a
Gmux-2000 equipped with one STM1 module and three E1-PW-SRV/21 modules
enables transporting a whole STM-1 stream over the packet-switched network,
with the added advantage that each E1 stream can be independently routed to
the desired endpoint through the network.
The number of pseudowires (bundles) supported by each port depends on the
framing mode:
Gmux-2000 Ver. 3.2
Each framed E1 port can be served by up to 16 pseudowires, where each

pseudowire can be separately routed to its desired destination, thus
1-25
providing the equivalent of fractional E1 services over packet-switched

networks, and a total of 112 destinations per module.
The actual number of active pseudowires depends on timeslot assignment
(any given timeslot can be included in a single pseudowire)
An unframed E1 port is served by a single pseudowire.
Each pseudowire terminated on the E1-PW-SRV/21 can be independently

configured to handle the desired type of traffic:
Transparent transfer of data (unframed E1 streams) using TDMoPSN, or

SAToPSN
Transfer of framed E1 streams in accordance with ITU-T Rec. G.704 and

G.706, using TDMoPSN, and CESoPSN.
For voice payload, the signaling protocol is also selectable: channelassociated signaling (CAS), or common-channel signaling (CCS) such as
Signaling Scheme 7 (SS7), ISDN PRI signaling, etc.
Note that when using CESoPSN, neither CCS, nor CAS signaling are interpreted
(but timeslots carrying signaling, for example, timeslot 16, can be
transparently transferred within the pseudowire, as a regular data timeslot)
Fractional E1 services, with or without CAS, are supported by means of

TDMoPSN. Without CAS, CESoPSN can also be used
HDLC traffic carried over framed and unframed E1 using HDLCoPSN. This
enables efficient and transparent transfer of Frame Relay traffic.
Packet structure is independently selectable for each pseudowire, for

compatibility with the various pseudowire protocols (TDMoPSN, CESoPSN,
HDLCoPSN, SAToPSN) and the UDP/IP and MPLS/ETH network standards.
The functions performed by the E1-PW-SRV/21 module for each processing path
include:
1-26
Interfacing to the internal telecom buses. The module has an SDH mapper
that can direct any VC-12 to any internal E1 port. The total mapping capacity
is 21 VC-12s, out of the 63 carried in the STM-1 payload.
E1 payload processing. Each internal E1 port can be independently configured

to handle the VC-12 payload in accordance with the desired ITU-T framing
mode and signaling formats:
Unframed (G.703) mode: in this case, the whole data stream is

transported over the packet-switched network by a single pseudowire,
using the TDMoPSN, or SAToPSN protocol. This mode can also be used to
transfer timeslot 0 of framed E1 streams end-to-end, or transparently
transfer an E1 data stream with proprietary framing. Note that the
HDLCoPSN protocol can also handle unframed E1 data streams.
Basic G.704 framing, with or without support for CRC-4 in accordance

with ITU-T Rec. G.706. This framing mode can be used for applications
that require CCS.
G.704 framing with timeslot 16 multiframe (G.704 multiframe mode),

with or without support for CRC-4. This framing mode is used for
applications that require CAS.
Gmux-2000 Ver. 3.2
The timing mode of each port can be independently selected, to support the
timing mode used by the users equipment connected to each port, in
accordance with the options listed in RFC4197.
Note
Conversion between TDM and packet formats. The conversion parameters are
controlled by defining pseudowires, and can be optimized for the specific
end-users equipment and the application requirements.
E1-PW-SRV/21 supports packet payload version V2, which includes a control

word. For compatibility with other equipment, E1-PW-SRV/21 also supports
payload version V1, which does not include a control word and thus has lesser
capabilities, for example, does not support the OAM protocol. The payload
version is user-selectable.
Forwarding the pseudowire packet streams. Each pseudowire can be

forwarded to the desired endpoint through the packet-switched network. The
user can specify forwarding and priority/quality of service parameters. For
forwarding, pseudowires are sent to the GbE module, which sends them
through the desired network interface. Both UDP/IP and MPLS/ETH networks
are supported.
The E1-PW-SRV/21 module operating parameters are determined by commands

received from the Gmux-2000 CONTROL module. The CONTROL module can also
download new software to the module, when the Gmux-2000 software is
updated.
The module supports comprehensive diagnostics, including power-up self-test,
and local and remote loopbacks for each port. Front-panel indicators indicate at a
glance the status of each module port.
E1-PW/28 Pseudowire Emulation Module with External E1

Interfaces
The E1-PW/28 module provides E1 circuit emulation services over packet-switched
networks using the TDMoIP protocol. The module has a capacity of 28 E1
(2.048 Mbps) trunks, each served by an independent external E1 interface, and
therefore a Gmux-2000 fully equipped with E1-PW/28 modules can handle up to
196 E1 data streams.
The E1-PW/28 modules are offered in two models:
E1-PW/28/BAL 28-port module with balanced E1 external interfaces.
E1-PW/28/UNBAL 28-port module with unbalanced E1 external interfaces.
The number of pseudowires supported by each port depends on the framing

mode:
Gmux-2000 Ver. 3.2
Each framed E1 port can be served by up to 16 pseudowires, where each

pseudowire can be separately routed to its desired destination, thus
providing the equivalent of fractional E1 services over packet-switched
networks, and a total of 112 destinations per module. The actual number of
active pseudowires depends on timeslot assignment (a timeslot can be
included in a single pseudowire)
An unframed E1 port is served by a single pseudowire.
1-27
Each pseudowire terminated on the E1-PW/28 can be independently configured

to handle the desired type of traffic:
Transparent transfer of data (unframed E1 streams) using TDMoPSN, or

SAToPSN
Transfer of framed E1 streams in accordance with ITU-T Rec. G.704 and

G.706, using TDMoPSN, and CESoPSN.
For voice payload, the signaling protocol is also selectable:
channel-associated signaling (CAS), or common-channel signaling (CCS) such
as Signaling Scheme 7 (SS7), ISDN PRI signaling, etc.
Note that when using CESoPSN, neither CCS, nor CAS signaling are interpreted
(but timeslots carrying signaling, for example, timeslot 16, can be
transparently transferred within the pseudowire, as a regular data timeslot)

HDLC traffic carried over framed and unframed E1 using HDLCoPSN. This
enables efficient and transparent transfer of Frame Relay traffic.
Packet structure is independently selectable for each pseudowire, for

compatibility with the various pseudowire protocols (TDMoPSN, CESoPSN,
HDLCoPSN, SAToPSN) and the UDP/IP and MPLS/ETH network standards.
The functions performed by the E1-PW/28 module for each port include:
Interfacing to the local users E1 equipment. Each module port can be

independently configured in accordance with the desired ITU-T framing mode
and signaling formats:
Unframed (G.703) mode: in this case, the whole data stream is

transported over the packet-switched network by a single pseudowire,
using the TDMoPSN, or SAToPSN protocol. This mode can also be used to
transfer timeslot 0 of framed E1 streams end-to-end, or transparently
transfer an E1 data stream with proprietary framing. Note that the
HDLCoPSN protocol can also handle unframed E1 data streams.

with ITU-T Rec. G.706. This framing mode can be used for applications
that require CCS.

with or without support for CRC-4. This framing mode is used for
The timing mode of each port can be independently selected, to support the
timing mode used by the users equipment connected to each port, in
accordance with the options listed in RFC4197.
1-28
Conversion between TDM and packet formats. The conversion parameters are
controlled by defining pseudowires, and can be optimized for the specific
end-users equipment and the application requirements.
Gmux-2000 Ver. 3.2
Note
E1-PW/28 supports packet payload version V2, which includes a control word. For
compatibility with other equipment, E1-PW/28 also supports payload version V1,
which does not include a control word and thus has lesser capabilities, for
example, does not support the OAM protocol. The payload version is
user-selectable.
Forwarding the pseudowire packet streams. Each pseudowire can be

forwarded to the desired endpoint through the packet-switched network. The
user can specify forwarding and priority/quality of service parameters. For
forwarding, pseudowires are sent to the GbE module, which sends them
through the desired network interface. Both UDP/IP and MPLS/ETH networks
are supported.
The E1-PW/28 module operating parameters are determined by commands

received from the Gmux-2000 CONTROL module. The CONTROL module can also
download new software to the module, when the Gmux-2000 software is
updated.
and local and remote loopbacks for each port. Front-panel indicators indicate at a
GbE PSN Interface Module

The GbE module provides two main functions:
Provides physical interfaces to the packet-switched network
Handles the packet-switched traffic flow between the Gmux-2000 internal

StarLAN packet bus, and the packet-switched network.
Only one GbE module is required in the chassis, however Gmux-2000 supports
two GbE modules.
The GbE module provides the interface to the packet-switched network for the
Gmux-2000 packet traffic. The module supports both IP and MPLS
packet-switched networks, and is capable of processing data at wire speed.
The GbE module has two external ports for connection to the packet-switched
network. The ports use Gigabit Ethernet SFP transceivers with optical and copper
GbE interfaces, for meeting a wide range of operational requirements.
Each external port of the module is assigned its own IP address, and can be
independently used, to enable load balancing. The module ports can also be
configured to use link aggregation per IEEE 802.3ad without LACP (Link
Aggregation Control Protocol), thereby providing a single logical link to the
network. Alternatively, redundancy can be used by configuring 1:1 bidirectional
APS (Automatic Protection Switching) at the port level, or at the module level:
Gmux-2000 Ver. 3.2
When redundancy is enabled at the port level (that is, between the two ports
of the same GbE module), at any time one port is active and the other serves
as a backup, and therefore each port can be routed along a different path
over the network.
When redundancy is enabled at the module level (that is, between the two
GbE modules installed in the chassis), at any time the two ports of one
module are active, and the ports of the other module serve as backup. In
1-29
addition, each active port can be routed along a different path, as for
port-level redundancy.
The internal ports of the module connect by pairs of Fast Ethernet ports, through
the StarLAN packet bus of the chassis, to each I/O module and to each CONTROL
module.
All the external and internal ports of the module are handled by an internal
high-performance Ethernet switch with MPLS support. The switch performs Layer
3/4 static routing for the internal packet traffic. No routing protocol is used: the
switch routes each pseudowire in accordance with the static routing information
configured by the user:
For UDP/IP pseudowires, the internal routing is made only on the basis of the
pseudowire IP address and UDP port (a maximum of 255 UDP ports per IP
address are allowed)
For MPLS pseudowires, the internal routing is made on the basis of the
pseudowire MPLS label. Two labels can be configured: an inbound label, which
is mandatory, and an optional outbound label.
Static routing is also used for external routing. The static routing information is
configured as entries in the manager list (up to 100 entries can be defined,
where up to 10 can be used for managers and the others serve as static routes).
The external GbE port used by each pseudowire can be independently selected,
except when using link aggregation or redundancy.
The management traffic is routed to the CONTROL module.
The switch generates ARP requests when the destination MAC address is
unknown, and answers ARP requests. The ARP refresh rate is user-configurable,
and can be disabled when necessary. The switch also supports pinging for IP
connectivity checks (the ping destination must also be included as a static entry
in the manager list).
The switch provides user-configurable VLAN support for the payload and
management traffic. Class of service is ensured by supporting per-pseudowire
configuration of IEEE 802.1p priority at Layer 2 and Type of Service (ToS/DiffServ)
at Layer 3. For MPLS networks, the switch also enables specifying the requested
Quality-of-Service by means of the EXP bits.
In addition to the external payload-carrying ports, the GbE module has a
10/100BASE-TX monitoring interface, for use by technical support personnel.
VC-E1/16, VC-E1/12 Voice Compression Modules

VC-E1/16 and VC-E1/12 are complete voice compression subsystems with a
compression capacity of 16 E1, respectively 12 E1, voice trunks.
The voice compression modules are available in two models, which differ only in
the number of voice ports:
VC-E1/16 module with 16 E1 voice ports
VC-E1/12 module with 12 E1 voice ports.
The modules enable Gmux-2000 systems to deliver voice traffic, including inband
signaling (DTMF, MFR2, and MFC), voiceband modems and Group III fax up to
14.4 kbps, over the following types of links:
1-30
Gmux-2000 Ver. 3.2
TDM links: E1 (PDH) links located on the module itself, or STM-1 (SDH) ports
located on STM1 modules
GbE links, located on GbE modules.
Gmux-2000 supports the ITU-T Rec. G.723.1 and G.729 Annex A voice
compression algorithms, as well as ITU-T Rec. G.711 (A-law and -law PCM), and
uses TDMoIP multiplexing for efficiently transporting the payload of E1 trunks
over TDM (E1 or SDH) networks. Packet structure is selectable (TDMoIP for UDP/IP
networks, and AAL2oMPLS for MPLS networks). In addition to standard packet
structures, Gmux-2000 also offers RAD proprietary versions of these protocols
that achieve significantly higher bandwidth efficiency.
Advanced digital signal processing techniques ensure highly-reliable service,
unaffected by the use of voice compression. These techniques include:
Per-channel voice activity detection (VAD) and silence suppression
Built-in echo cancellation for delays up to 32 msec per ITU-T Rec. G.168
Relaying of Group III fax, modems at commonly used rates and standards,
inband signaling and custom tones.
Where compression cannot be used, for example, for non-standard inband

signaling and modem protocols, voiceband signals can be faithfully
transmitted using selectable PCM or ADPCM coders.
To prevent voice degradation when traffic passes multiple VC-E1/16 or Vmux

units, a special super-tandem mode ensures that voice signals pass compression
only once, irrespective of the number of hops on the transmission path.
At the highest compression ratio, VC-E1/16 enables compressing up to 16 E1
voice trunks for transport over a single E1 network link (up to 16:1 compression
ratio); for VC-E1/12, the maximum compression ratio cannot exceed 12:1 because
it has only 12 voice ports. VC-E1/16 and VC-E1/12 traffic can be routed over up
to 32 independently-configurable bundles, where a bundle can carry any number
of timeslots, up to a full E1 voice port (30 or 31 channels). Each compressed
voice bundle can be independently connected to any desired network-side port
(either TDM port or GbE port).
Moreover, VC-E1/16 and VC-E1/12 support both point-to-point and
point-to-multipoint (channelized) applications over their E1 network-side links,
with user-configurable link bandwidth assignment per destination (the timeslots
available on each E1 network-side link can be assigned to up to 10 independent
subchannels).
To guarantee high service quality together with highly efficient utilization of
transport links, VC-E1/16 and VC-E1/12 support the ITU-T Rec. Q.50 (Annex A and
B) bandwidth control protocol, as well as a proprietary bandwidth limiting
algorithm that ensures quality degrades gradually during intervals of excessive
traffic load. To preserve service quality, a separate mechanism makes it possible
to block the setup of new modem calls when bandwidth utilization exceeds
user-configurable, application-specific thresholds.
VC-E1/16 and VC-E1/12 provide full support for a wide range of signaling
protocols. This includes CAS and R2 signaling (transferred end-to-end either
transparently, or after translation in accordance with user-specified profiles) as
well as optimized HDLC-based transfer of CCS protocols such as ISDN, QSIG,
Gmux-2000 Ver. 3.2
1-31
Signaling Scheme 7 (SS7), etc. The CCS timeslots are user-selectable,

independently for each voice port, with a maximum of two timeslots per port.
VC-E1/16 and VC-E1/12 have both TDM and packet ports:
The TDM ports comprise a set of 16, respectively 12, voice (user-side) E1
ports and a separate set of 2 data (network-side) E1 ports
The packet ports comprise 2 network-side ports, for connection to

Gmux-2000 internal packet buses.
To provide maximum application flexibility and avoid the need for additional
equipment, each set of TDM ports has both external ports with ITU-T Rec. G.703
interfaces located on the module panel, and internal ports that can be connected
via the Gmux-2000 telecom buses to the SDH ports located on the STM1 modules
that may be installed in the chassis (each internal module port can be
independently mapped to any desired VC-12).
The maximum number of VC-E1/16 and VC-E1/12 modules that may be installed in
a Gmux-2000 chassis is 7. Note however that 2 out of the 7 Gmux-2000 I/O slots
that support VC-E1/16 modules also support STM1 modules, and therefore the
maximum voice compression capacity (7 modules) can be reached only when
using the external VC-E1/16 or VC-E1/12 module ports (when using internal ports,
STM1 modules must be installed in the chassis, thereby reducing the number of
slots available for modules by one for each STM1 module installed). The maximum
number of VC-E1/16 or VC-E1/12 modules decreases by one for each installed
STM1 module:
With VC-E1/16 modules, the maximum capacities are as follows:
Without STM1 modules in the chassis, 7 VC-E1/16 modules yield 112 E1

voice trunks per chassis. Assuming that one timeslot is reserved for
signaling (for example, timeslot 16 for CAS, or any timeslot for CCS), the
number of voice timeslots per E1 trunk is 30, resulting in a maximum
capacity of 3360 voice channels per module.
When CCS protocols such as SS7 are used, the signaling information can
be separately carried, in accordance with customers signaling transfer
method: in this case, the number of voice timeslots per trunk can reach
31, for a maximum capacity of 3472 channels per module.
1-32
One STM1 module and 6 VC-E1/16 modules yield a maximum capacity of

96 E1 trunks per chassis (2880, respectively 2976, voice channels)
Two STM1 modules and 5 VC-E1/16 modules yield a maximum capacity of

80 E1 trunks per chassis (2400, respectively 2480, voice channels).
With VC-E1/12 modules, the respective maximum capacities are 84, 72, and
60 E1 voice trunks (up to 2520, 2160, and 1800 voice channels, or 2604,
2232, and 1860 for 31 timeslots per trunk).
Gmux-2000 Ver. 3.2
To improve availability, VC-E1/16 and VC-E1/12 data ports can be configured to

provide backup for the connection to the network. In this case, the data ports
operate in pairs: in each pair, one port serves as the main (primary) port, and the
other as backup (secondary) port. At any time, only one port of each pair carries
traffic. As long as the primary port can carry the traffic, it is automatically
selected as the active port; in case of a problem on the link or in the port
hardware, the traffic is automatically switched to the backup port. Switching is
revertive.
This means that when using backup over the external E1 data (network-side)
ports, only one E1 port is available; when using the internal (SDH) network ports
with backup enabled, an additional set of internal data ports becomes available,
and therefore the maximum number of E1 data ports is four (two primary and
two secondary). For maximum service availability, Gmux-2000 offers 1:N
protection for VC-E1/16 or VC-E1/12 modules configured to use only internal
ports for both voice and data. In the 1:N protection mode, one VC-E1/16 or VCE1/12 module is assigned to serve as a hot standby for the other VC-E1/16 or VCE1/12 modules installed in the chassis.
VC-E1/16 operating parameters are determined by commands received from the
Gmux-2000 CONTROL module. The CONTROL module can also download new
software to the module, when the Gmux-2000 software is updated. VC-E1/16
modules also support inband management of remote Gmux-2000 units: a
remotely located network management station, for example, RADview-SC/Vmux,
connected to a GbE port of one Gmux-2000 unit can manage the other
Gmux-2000 units interconnected to it via VC-E1/16 or VC-E1/12 data ports.
Vmux-2100 Voice Trunking Gateways connected to VC-E1/16 or VC-E1/12 ports
can also be managed in the same way.
local and remote loopbacks and test tone injection for the voice ports, and
remote loopbacks for the network ports. It also collects comprehensive
performance statistics that can be uploaded via TFTP to a management station
such as the RADview-SC/Vmux for analysis. Front-panel indicators indicate at a
Gmux-2000 Ver. 3.2
1-33
1.4
Technical Specifications
System Characteristics
General
Function
Pseudowire gateway
TDM Interfaces
Depends on installed modules:

SDH: STM-1 (155.52 Mbps), maximum
capacity of 126 E1 streams
PDH: E1 (2.048 Mbps), maximum capacity of
196 E1 streams
Packet Switched Network

Interface
Physical
GbE ports, maximum capacity of 2 GbE streams
Protocols
Ethernet
IP
MPLS
Main Types of Services
Depends on installed modules:

TDM transport over PSN using pseudowire
circuit emulation (PW)
Voice trunking over PSN, using voice
compression
Routing Capabilities
Any E1 stream from any TDM interface to any

IP or MPLS destination
Number of Stored Bundles
Up to 2000
Protection Modes
SDH Links
1+1 unidirectional APS per ITU-T Rec. G.783
GbE Links
Link aggregation per IEEE 802.3ad, without

LACP (Link Aggregation Control Protocol
1:1 bidirectional APS at the port level
1:1 bidirectional APS at the module level
I/O Modules
1-34
1:N protection for I/O modules with internal

ports (one protection group per chassis)
Gmux-2000 Ver. 3.2
STM1 Module Characteristics

General
Function
STM-1 interface module
External Ports
Two STM-1 ports, with interface in accordance

with order:
Fixed electrical interface
Fixed optical interface
SFP-based optical interface
Framing
ITU-T Rec. G.707, G.708, G.709
Port Payload Capacity
63 E1 streams
Number of Telecom Buses

Supported
Two telecom buses:

Port 1 serves telecom bus A
Port 2 serves telecom bus B
Operational Configurations
Single STM1 Module in
Chassis
TM with single STM-1 link (when second

port is not connected)
TM with dual STM-1 links (when both STM-1
ports are connected)
TM with single STM-1 link, and with line
redundancy (single Gmux-2000 module,
both STM-1 ports connected).
Two STM1 Modules in

Chassis
Fixed Electrical
STM-1 Port
Interface
Characteristics
Fixed Optical
STM-1 Port
Interface
Characteristics
Gmux-2000 Ver. 3.2
TM with dual STM-1 links, with both line and

hardware redundancy (all the STM-1 ports
connected)
Physical Layer
ITU-T Rec. G.703, Para. 12
Line Code
CMI
Nominal Bit Rate
155.520 Mbps
Connectors
Two BNC connectors
Physical Layer
ITU-T Rec. G.957
Nominal Bit Rate
155.520 Mbps
Standard
SDH
1-35
Table 1-3. STM1 Module, Fiber Optic Interface Characteristics

Wavelength
1310 nm
850 nm
Transmitter
Type
Power Coupled Receiver

into Fiber
Sensitivity
Typical
Optical
Budget
Typical Max.
Range
(km/miles)
9/125 m,
single mode
Laser
-15 to -8 dBm
-31 dBm
16 dB
20/13
9/125 m,
single mode
Laser, long
haul
-5 to 0 dBm
-34 dBm
29 dB
40/26
62.5/125 m,
multi-mode
LED
-20 to -14 dBm -30 dBm
10 dB
2/1.3
62.5/125 m,
multi-mode
VCSEL
-20 to -14 dBm -30 dBm
10 dB
2/1.3
Fiber Type
SFP-Based STM-1 Physical Layer

Port Interface
Nominal Bit Rate
Characteristics
ITU-T Rec. G.957

155.520 Mbps
Connectors
One or two LC connectors, depending of SFP

type
Recommended RAD SFP

Types
Dual Fibers: SFP-1, SFP-2, SFP-3, SFP-4

Single Fiber: SFP-10a, SFP-10b, SFP-13,
SFP-18a, SFP-19a, SFP-19b
Note
Module Timing
STM-1 Receive Port Timing
For detailed specifications of SFP

transceivers, see the RAD SFP
Transceivers data sheet.
Receive clock recovered from the received

STM-1 line signal
Gmux-2000 system clock can be locked to
the recovered receive clock signal of an STM1 port
STM-1 Transmit Port Timing Internal timing (locked to Gmux-2000 system

clock)
Loopback timing (transmit timing locked to

clock recovered from selected received STM-1
line signal)
Internal Port Receive Timing Receive clock recovered from the received
STM-1 line signal
1-36
Gmux-2000 Ver. 3.2
Port Indicators
Internal Port Transmit

Timing
Locked to the Gmux-2000 system clock
L LOS (red)
Local loss of STM-1 signal
R LOS (red)
Remote loss of STM-1 signal
Module Indicators ACT (green)
Diagnostics
Locked to one of the recovered internal E1

port clock signals (which may itself use
loopback timing or adaptive timing)
Module is active and carries traffic
FLT (red)
Fault detected in module
Loopbacks
User-activated local loopback on each

external STM-1 port
User-activated remote loopback on each
external STM-1 port
Self-Test
Automatically performed upon power-up or

reset
Physical
Occupies a single I/O module slot (slot 7 or 9)
Payload Routing
User-defined mapping, any E1 port to any TU-12

within the STM-1 payload
GbE Module Characteristics

General
Function
GbE PSN interface module
External Ports
Two GbE ports with SFP modules, with optical

or copper interfaces
One 10/100BASE-TX monitoring port
Internal Ports
Two Fast Ethernet internal ports toward the

packet (StarLAN) bus to each I/O slot
One Fast Ethernet internal port toward the
packet (StarLAN) bus to each CONTROL
module
Optical Port
Interface
Characteristics
Gmux-2000 Ver. 3.2
Payload Handling
Gigabit Ethernet switch
Interface Type
Optical 1000BASE-X port, full-duplex, with

autonegotiation user-selectable
Link Connectors
Dual LC
1-37
Copper Port
Interface
Characteristics
GbE Port
Indications
MONITOR Port
Characteristics
Interface Type
1000BASE-T port, full-duplex, with or without

autonegotiation user-selectable
Link Connector
RJ-45
LINK Indicator (green)
Lights when port is connected to an active

Ethernet port or LAN
PAUSE Indicator (green)
Lights when port receives PAUSE frames
RX Indicator (green)
Lights when port detects receive activity
TX Indicator (green)
Lights when port detects transmit activity
Function
Monitoring port for technical support personnel
Interface Type
10/100BASE-TX Ethernet
Interface Operating Modes
User-selectable rates and mode (10 or

100 Mbps, full-duplex or half-duplex), or
automatic selection by auto-negotiation
Automatic polarity detection and correction
Interface Connector
Diagnostics
8-pin RJ-45
Module is active
FLT (red)
Fault detected in module
Self-Test
Automatic, after power-up or reset
Physical
Occupies a single I/O slot (slot 6 or 8)
E1-PW/28 PW Module with External Interfaces Characteristics

General
Function
Pseudowire E1 emulation server with external E1

interfaces
External TDM Ports
28 external E1 ports
Internal Packet Ports
2+2 Fast Ethernet internal ports toward the

packet (StarLAN) bus
Number of Pseudowires
Up to 16 active pseudowires per E1 port

Up to 112 pseudowires per E1-PW/28
1-38
Gmux-2000 Ver. 3.2
Protocols
TDMoIP in accordance with RFC5087

TDMoMPLS in accordance with RFC5087 and
ITU-T Rec. Y.1413
HDLCoPSN in accordance with RFC5087 and
RFC4618 (except Clause 5.3 PPP)
CESoPSN in accordance with RFC5086
SAToPSN in accordance with RFC4553

Types
UDP over IP
Payload Routing
Packet Routing
User-defined internal routing (any packet

processor to any PSN port), and connection
parameters (each pseudowire to any
destination)
E1 Interface
Characteristics
Type and Bit Rate
E1, 2.048 Mbps
Line Interface
E1-PW/28/BAL: 120 balanced
MPLS over ETH
E1-PW/28/UNBAL: 75 unbalanced
Standards Compliance
ITU-T Rec. G.703, G704, G.706, G.732
Line Code
HDB3
Framing Modes
Unframed (G.703)
Basic G.704 framing, with or without CRC-4
G.704 timeslot 16 multiframe, with or without
CRC-4
Transmit Level
E1-PW/28/BAL: 3V 10%, balanced

E1-PW/28/UNBAL: 2.37V 10%, unbalanced
Module Timing
Receive Level
0 through -12 dB
Connectors (per module)
Two 62-pin D-type female connectors: one for

channels 1 to 14, and the other for channels 15
to 28
E1 Port Transmit Path

Timing

clock recovered from the E1 signal received
from the line)
Adaptive timing (transmit timing locked to
the average rate of packets received from
the packet-switched network)
Gmux-2000 system timing
Gmux-2000 Ver. 3.2
1-39
E1 Port Receive Path Timing Locked to clock recovered from the received E1
signal
Port Indicators
Diagnostics
L (red) Indicator per Port
Lights for loss of signal, local loss of

synchronization, or local loss of synchronization
+ AIS
R (red) Indicator per Port
Lights for remote loss of synchronization
Loopbacks
Local loopback on each E1 port

Remote loopback on each E1 port
Self-Test
Physical

reset
Occupies a single I/O slot (slot 1 to 5, 7, 9)
E1-PW-SRV/21 PW Emulation Server Module Characteristics

General
Function
E1 pseudowire emulation server with internal

TDM ports
Internal TDM Ports
21 internal E1 ports
Internal Packet Ports
Two Fast Ethernet internal ports toward the

packet (StarLAN) bus
Number of Pseudowires
Up to 16 active pseudowires per E1 port

Up to 112 pseudowires per E1-PW-SRV/21
Protocols
TDMoIP in accordance with RFC5087

TDMoMPLS in accordance with RFC5087 and
ITU-T Rec. Y.1413
HDLCoPSN in accordance with RFC5087 and
RFC4618 (except Clause 5.3 PPP)
CESoPSN in accordance with RFC5086
SAToPSN in accordance with RFC4553
Payload Routing
1-40

Types
UDP over IP
Packet Routing
User-defined internal routing (any packet

processor to any PSN port), and connection
parameters (each pseudowire to any
destination)
MPLS over ETH
Gmux-2000 Ver. 3.2
E1 Internal Port
Characteristics
Type and Bit Rate
E1, 2.048 Mbps
Standards Compliance
ITU-T Rec. G.703, G704, G.706, G.732
Framing Modes
Unframed (G.703)
Basic G.704 framing with or without CRC-4
G.704 timeslot 16 multiframe with or without
CRC-4
Module Timing

Timing

clock recovered from the E1 signal received
from the SDH mapper)
Adaptive timing (transmit timing locked to
the average rate of packets received from
the packet-switched network)
Gmux-2000 nodal timing
E1 Port Receive Path Timing Timing locked to clock received from the SDH
mapper
Port Indicators
Dual-Color Indicator
Off Port is disabled (not connected)

Red Port is enabled, but an alarm condition
is present (local loss of synchronization or
critical alarm in the STM1 module serving the
port)
Green Port is enabled and none of the
alarm conditions described above is present.
Flashes during module initialization and

during software downloading.
Lights steadily after initialization is
successfully completed, if no fault is
detected in the module.
Diagnostics
FLT (red)
Hardware fault detected in module
Loopbacks
Local loopback on each E1 port

Remote loopback on each E1 port
Self-Test
Physical
Gmux-2000 Ver. 3.2

reset
Occupies a single I/O slot (slot 1 to 5, 7, 9)
1-41
VC-E1/16, VC-E1/12 Voice Compression Modules Characteristics

General
Function
Voice compression module
Compression Capacity
VC-E1/16: 16 E1 trunks
VC-E1/12: 12 E1 trunks
User-Side Voice Ports
16, respectively 12, external E1 ports

or
16, respectively 12, internal E1 ports
connected to SDH ports
Network-Side Data Ports
2 external E1 ports
or
2 internal E1 ports and 2 backup ports, all
connected to SDH ports

Types
UDP over IP
MPLS over ETH
User-Side Voice Ports

Voice Port
Characteristics
Port Type
E1, 2.048 Mbps
Compliance
ITU-T Rec. G.703, G.704, G.706, G.732, G.823
Framing

G.704 multiframe, with or without CRC-4
Signaling
CAS for G.704 multiframe

CCS (transparent transport) for basic G.704
framing
External
Voice Port
Interface
Characteristics
Jitter Performance
ITU-T Rec. G.823
Line Interface
120 , balanced
75 , unbalanced
Line Code
HDB3
Transmit Level
Balanced: 3V 10%
Unbalanced: 2.37V 10%
Receive Level
DSU mode: 0 to -12 dB

LTU mode: 0 to -36 dB
1-42
Gmux-2000 Ver. 3.2
Internal
Voice Port
Interface
Characteristics
Connector (per module)
64-pin TELCO female connector
Interfacing
VC-12
Compliance
ITU-T Rec. G.783 and G.707
Network-Side Data Ports

Data Port
Characteristics
Port Type
E1, 2.048 Mbps
Compliance
ITU-T Rec. G.703, G.704, G.706, G.732, G.823
Framing

Unframed
Bandwidth Utilization
Basic G.704 framing: channelized mode with

up to 10 independently configurable
subchannels per port (1 to 31 timeslots per
subchannel)
Unframed: one subchannel, with a capacity of
32 timeslots
Jitter Performance
External Data Port Line Interface

Characteristics
ITU-T Rec. G.823

120 balanced
75 unbalanced
User-selected for each port
Line Code
HDB3
Transmit Level
Balanced: 3V 10%
Unbalanced: 2.37V 10%
Receive Level
DSU mode: 0 to -12 dB

LTU mode: 0 to -36 dB
Connector
RJ-45 per port
Internal Data Port Interfacing

Interface
Compliance
Characteristics
VC-12
Backup
Characteristics
External: 1 primary, 1 secondary
Number of Ports
Internal: 2 primary, 2 secondary
Backup Switching Mode
Gmux-2000 Ver. 3.2
ITU-T Rec. G.783 and G.707
Revertive
1-43
Packet Bus Interfaces
Two Fast Ethernet interfaces to Gmux-2000

internal packet buses
Voice Transmission Parameters

Internal Ports
Maximum Number
Up to 32 active bundles per module, each

independently configurable
Bundle Size
1 timeslot to full port (30 or 31 timeslots),

user-configurable
Routing Parameters
Selectable source and destination CBID for

UDP/IP, or MPLS label for MPLS/ETH
Destination IP address
Next hop IP address
Configurable VLAN support
Selectable exit port and subchannel
Connectivity Check
Transmission rate: 1 to 60 seconds between

packets
Alarm threshold: 2 to 5 cycles
Voice
Compression Algorithms
Compression (per
Bundle)
MP-MLQ per ITU-T Rec. G.723.1, at rates of

5.3 and 6.4 kbps
Conjugate structure-algebraic-code-excited
linear prediction (CS-ACELP) per Annex A of
ITU-T Rec. G.729A, at a rate of 8 kbps
Uncompressed Voice
Algorithms
ITU-T Rec. G.711 with A-law companding
Silence Suppression
Voice activity detection with silence

suppression
ITU-T Rec. G.711 with -law companding
Configurable comfort noise generation
1-44
Companding Law
User-selectable, A-law or -law
Echo Canceling
ITU-T Rec. G.168, maximum delay 32 msec
Receive Signal Level
Adjustable relative to nominal output level:

-6 to +6 dB, in 1-dB steps
Transmit Signal Level
Adjustable relative to nominal input level:

-12 dB, -6 to +6 dB in 1-dB steps, +12 dB
Gmux-2000 Ver. 3.2
Voice
Encapsulation Method
Compression (per
Bundle) (Cont.)
For UDP/IP networks:

Standard TDMoIP
RAD proprietary TDMoIP (TDMoIP+)
For MPLS networks:
Standard AAL2 over MPLS per ITU-T Y.1414
(AAL2oMPLS)
RAD proprietary AAL2 over MPLS
(AAL2oMPLS+)
Encapsulation Parameters
Configurable packet size (100 to 1461 bytes)

Configurable maximum inter-packet interval
(10 to 90 msec)
Trunk Signaling Support
CAS (timeslot 16): user-configurable signaling

translation (up to 5 signaling profiles), idle
code and OOS code
CCS with user-selectable timeslots: supports
ISDN, QSIG, SS7 protocols
CCS Signaling Support
Transparent transfer, using HDLC over AAL2

SSTED per ITU-T Rec. I.366.1
Selectable keep-alive message suppression
ratio for SS7
Inband Signaling
Relaying (detection and generation) of DTMF,

MFR2, MFC, complies with EIA/TIA-464B
Configurable MFR2/MFC relaying parameters
Fax Support
Group III fax relay at rates of 4.8 to 14.4 kbps

or
Transmission of voiceband fax signals
Modem Support
V.22/V.22bis, V.32/V.32bis, V.34 up to

21.6 kbps
or
Transmission of voiceband modem signals
Voiceband Fax/Modem
Coders
ITU-T Rec. G.711 with A-law companding

ITU-T Rec. G.711 with -law companding
ITU-T Rec. G.726 at 32 kbps
ITU-T Rec. G.726 at 24 kbps
Gmux-2000 Ver. 3.2
1-45
Voice
Bandwidth Utilization
Compression (per Controls
Bundle) (Cont.)
Support for ITU-T Rec. Q.50 (Annex A and

Annex B, user-selectable), with selectable call
rejection threshold. Enabled/disabled on a
per-port basis
Random discarding of packets when link
bandwidth utilization exceeds selectable
threshold. Available on all voice ports
Modem call rejection when link bandwidth
utilization exceeds selectable threshold.
Configurable on a per-port/per-connection
basis
Timing
Module Timing

Timing

clock recovered from the received E1 signal)
Gmux-2000 system timing
E1 Port Receive Path Timing Locked to clock recovered from the received E1
signal
General
Module Indicators ACT (green) Indicator
Flashes during module initialization and during

software downloading.
Lights steadily after initialization is successfully
completed, if no fault is detected in the
module.
FLT (red) Indicator
Port Indicators
Hardware fault detected in module
LOC (red) Indicator per Port Lights for loss of signal, local loss of
synchronization, or local loss of synchronization +
AIS
REM (red) Indicator per Port Lights for remote loss of synchronization
Diagnostics
Loopbacks
Local loopback on each E1 voice port

Remote loopback on each E1 voice port
Local tone injection in selectable voice port
timeslots
Remote loopback on each E1 data port
Self-Test
1-46
Automatically performed upon power-up or reset
Gmux-2000 Ver. 3.2
Physical
Occupies a single I/O slot (I/O-1 to I/O-5, I/O-7

and I/O-9)
Station Clock Interface

Interfaces
Signal Characteristics
2048 kbps, ITU-T Rec. G.703, 120 balanced

or 75 unbalanced interface (input and
output)
1544 kHz ITU-T Rec. G.703 100 balanced
(input and output)
2048 kHz or 1544 kHz squarewave input and
output (RS-485 levels)
Connectors
Port Indicators
Balanced Interface
8-pin RJ-45
Unbalanced Interface
BNC
SD (dual color)
OFF no station clock configured

Green station clock present
Red station clock not present
System Management
Management
Capabilities
Supervision terminal compatible with VT-100, connected either directly or

via modem
Telnet
SSH
SNMP (RADview and other SNMP-based network management stations)
User authentication based on RADIUS
SNMP
Management
Capabilities
SNMPv1
SNMPv2, with selectable security model: user-based (SNMPv2u) or
community-based (SNMPv2c)
SNMPv3, with selectable security model: user-based or view-based
Selectable compatibility (any SNMP version, or specific version)
Management
Interfaces
Serial ports on CONTROL modules, supports the supervision terminal

10/100BASE-TX ports on CONTROL modules, support Telnet, SSH, and SNMP
Inband via uplink ports, support for Telnet, SSH, and SNMP
Gmux-2000 Ver. 3.2
1-47
Serial Control Port Interface

Characteristics
Data Rate
Data Word Format
RS-232 asynchronous DCE port

0.3, 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 57.6 and 115.2
kbps
1 start bit
7 or 8 data bits
Parity: none/odd/even
1 or 2 stop bits
Ethernet
Control Port
Characteristics
Internal Time
Connector
9-pin D-type female
Interface Type
10/100BASE-TX
Interface Operating Modes
10 or 100 Mbps, full-duplex or half-duplex,

selection by autonegotiation
Interface Connector
8-pin RJ-45
Source
Real time clock, battery-backed
Time Display Format
Time and day with calendar support up to year

2099, with three user-selectable formats
Time Setting
Manual setting: using supervision terminal,

Telnet, SSH, or SNMP-based network
management
NTP-based: automatic setting, and
resynchronization at user-selectable intervals,
using a specified NTP server
Alarm Collection
and Monitoring
Alarms
Last 256 time-stamped alarms stored in buffer

Buffer reset upon power-up, or by users
command
Monitoring Options
By management: using supervision terminal,

Telnet, SSH, or SNMP
Remote reporting using the syslog protocol per
RFC3164
Syslog Capabilities
Device functionality per RFC3164

Reporting of all supported traps and alarms
Configurable severity level filter, and optional
configurable local message sources
Configurable target syslog server (collector)
1-48
Gmux-2000 Ver. 3.2
External Alarm
Interfaces
Alarm Outputs
Major alarm indication by floating change-over

dry-contact contacts
Minor alarm indication by floating change-over
contacts
Output Contact Ratings
Max. 60 VDC/30 VAC across open contacts

Max. 1 ADC through closed contacts
Max. load switching capacity: 60W
External Alarm Input
One active-low input, RS-232 levels
Power Requirements
Power Sources
AC Power
100 to 240 VAC (115/230 VAC nominal), 50/60 Hz
DC Power
In accordance with the PS model:

48 VDC: 36 to 72 VDC
24 VDC: 18 to 36 VDC
Number of Power Supply

Modules
AC
DC
3 modules, each one with a separate power input

circuit
3 modules, with 2 separate DC power inputs per
module
Power Supply Capacity
Per following table
Number of PS Modules and PS

Module Rating
One PS Module
Two PS Modules Three PS Modules
200W
300W
200W
300W
200W
300W
Max Power without

Redundancy
200 W
300 W
400 W
600 W
600 W
900 W
200 W
300 W
400 W
600 W
Max Power with Redundancy
Environment
Temperature
Operating
0 to 55C (32 to 131F)
Storage
-20 to +70C (0 to 150F)
Humidity
0 to 90%, non-condensing
Cooling
Internal fan tray
Gmux-2000 Ver. 3.2
1-49
Physical
Number of Slots
1 power inlet slot

3 power supply slots
2 control slots
9 I/O slots
1 slot for cooling fan tray
Dimensions
Width
440 mm (17.3 inch)
Height
265 mm (10.4 inch), 6U
Depth
210 mm (8.2 inch)
Weight
12 kg (26.4 lb), maximum
Mounting Method 19-inch (ANSI) rack, requires RM-2000 rack mounting kit
ETSI rack, requires RM-2000E rack mounting kit
1-50
Gmux-2000 Ver. 3.2
Chapter 2
Functional Description
2.1
Scope
This Chapter provides a functional description of the Gmux-2000 system that

supplements the information presented in Chapter 1, and describes the main
Gmux-2000 features.
For background information regarding the Gmux-2000 operating environment,
refer to Appendix C.
2.2
Gmux-2000 Functional Description
Gmux-2000 can simultaneously provide TDM transport services, using pseudowire

emulation, and voice trunking services. The following sections describe signal
processing for each type of service.
Description of Gmux-2000 System Used for TDM Transport Services

Figure 1-10 shows the functional block diagram of a typical Gmux-2000 system
used for TDM transport services, and identifies the modules and physical
interfaces that implement each function. The following description refers to
Figure 1-10.
The Gmux-2000 includes the following main subsystems:
I/O interface and pseudowire server subsystem: includes two main

subsystems:
TDM interfacing subsystem: provides interfaces to the TDM users

equipment or network. Two types of interfaces are available:
SDH interfaces, located on separate modules
PDH (E1) interfaces, collocated with the packet processors.
Pseudowire processing subsystem: performs the conversion between the

circuit-switched (TDM) and packet-switched networks, using pseudowire
emulation technology.
Refer to the Installation and Operation Manuals of the relevant interface

modules for a detailed functional description.
Gmux-2000 Ver. 3.2
PSN interface subsystem: provides the interface to the packet-switched

network (PSN), and handles the packet-switched traffic.
2-1
Chapter 2 Functional Description
Timing subsystem: (collocated with the management subsystem): provides

timing signals to all the Gmux-2000 circuits, and external (station and nodal)
clock interfaces.
Management subsystem: controls Gmux-2000 operation, stores its software

and configuration, and provides interfaces for local and remote management.
Alarm interfacing subsystem: provides dry-contact relay interfaces for

reporting chassis alarms, and an input interface for external sensors.
Power supply subsystem: includes power inlet and power supply modules.
Cooling fans: for increased system reliability.
Traffic buses. Gmux-2000 has two types of traffic buses:
TDM buses: carries the TDM traffic between the SDH interface modules
and the associated pseudowire emulation server modules. Consists of
multiple telecom (19.44 MHz) buses.
Packet bus: carries the packet traffic between PSN port and TDMoIP
modules. The traffic arrives either from the pseudowire emulation server
modules, or from the pseudowire emulation modules with external PDH
(E1) interfaces. Consists of multiple collision-free Fast Ethernet
connections having a star (StarLAN) topology.
Timing buses. Gmux-2000 has a dual timing bus system that has two
functions:
Carries reference signals from the I/O and pseudowire server modules to
the timing subsystem
Carries nodal clock signals from the timing subsystem to all the other
modules.
Control buses. The control buses carry control signals from the management
subsystem to each module installed in the chassis, and transfer status and
monitoring data from the modules to the management subsystem.
Power distribution bus: distributes supply voltages to the modules installed in

the chassis.
TDM Traffic Flow within the Gmux-2000

The flow of traffic within the Gmux-2000 chassis depends on the type of TDM
interfaces of the pseudowire emulation modules installed in the chassis: SDH or
PDH (E1).
Figure 2-1 shows the flow within a Gmux-2000 equipped with modules using SDH
interfaces:
2-2
The SDH interface subsystem provides the connection between the external
link and the internal telecom buses.
The payload appearing on the telecom buses is collected by means of an SDH

mapper. The collected payload is processed by an E1 framer, which enables
extracting signaling information and separating the timeslots assigned to
each bundle, in accordance with users assignment (the E1 framer creates an
internal E1 port, which is connected through the SDH mapper to the SDH
link).
Gmux-2000 Ver. 3.2
The resulting payload is provided to each packet processor. The packet

processor converts the payload into packets suitable for transmission over
the packet-switched network.
The resulting packets are encapsulated in Ethernet frames and then sent via
the Layer 2 Ethernet switch of the pseudowire emulation server module to
the PSN interface module through the internal StarLAN packet bus. The
Ethernet switch provides the flexibility needed to support multiple
connections (bundles or pseudowires). The bandwidth available to each
Ethernet switch for connecting to the PSN interface module is two Fast
Ethernet ports.
A Layer 2/3/4 Ethernet switch located on the PSN interface module analyzes
the traffic received from each pseudowire emulation server module and
directs it, via the configured PSN link, to the packet-switched network.
The switch also provides ARP services and answers/generates pings for the
bundles configured on the Gmux-2000, and for its management subsystem,
using the static routing information configured by the user.
STM-1
SDH
Interface
Subsystem
Pseudowire Emulation Servers

TDMoIP PW Servers
TDMoIP PW Servers
SDH
Mapper
E1
Framer
Packet
Processor
Telecom
Buses
PSN Interfacing Subsystem

Layer 2 Switch
Telecom
Buses
Packet Bus
(StarLAN)
Layer
2/3/4
Switch
GbE
Transceiver
PSN
Link 1
GbE
Transceiver
PSN
Link 2
Figure 2-1. Traffic Flow within Gmux-2000 with SDH Interfaces

Figure 2-2 shows the flow within a Gmux-2000 equipped with modules using E1
external interfaces:
The E1 interface subsystem provides the connection to the external E1 links

and the internal telecom buses. When necessary, the E1 framer extracts the
signaling information separates the payload of the timeslots assigned to each
bundle in accordance with users assignment, and provides the payload to the
corresponding packet processor.
The payload is processed by the corresponding packet processor in

accordance with users assignment and converted into packets for
transmission over the packet-switched network.
The resulting packets are then handled in the same way as explained above
for the Gmux-2000 equipped with SDH interfaces.
Pseudowire Emulation Modules with
External E1 Interfaces
E1
Framer
Packet
Processor
Layer 2 Switch
E1
E1
Interface
Subsystem
PSN Interfacing Subsystem

Packet Bus
(StarLAN)
Layer
2/3/4
Switch
GbE
Transceiver
PSN
Link 1
GbE
Transceiver
PSN
Link 2
Figure 2-2. Traffic Flow within Gmux-2000 with E1 Interfaces
Gmux-2000 Ver. 3.2
2-3
As is apparent from Figure 2-1 and Figure 2-2, the two alternative payload
processing methods converge, as they both generate packet traffic with identical
characteristics on the internal packet buses. This approach, which is based on
using flexible processing paths for various types of TDM payloads, enables future
growth in both capacity (more modules and more ports) and services (more types
of payload and enhanced software).
TDMoPSN Packet Processing

The packet processing subsystem consists of independent processors, one for
each E1 stream. The functions performed by each packet processor depend on
the user-configured pseudowire parameters, and the framing and signaling mode
of the associated E1 port. This section explains the processing of TDMoPSN
packets; see following sections for the processing of other types if packets.
Note
Appendix C presents an overview of the pseudowire emulation technology.

The main functions performed by the packet processor when using the TDMoPSN
mode are as follows:
In the transmit-to-network direction, the packet processor processes the

data stream received through the E1 framer to generate the bundles in
accordance with users specifications. When using a framed mode, the user
can specify the timeslots to be transported end-to-end.
To prepare a bundle, the packet processor extracts segments from the
continuous data stream for insertion into the bundle payload section. The
total size of the bundle payload section is specified by the user (n48 bytes,
where n is 1 to 30):
When operating in a framed (G.704) mode, the slices are formed by

collecting the appropriate timeslots from consecutive E1 frames until the
TDM payload section of the packet is filled. Timeslot 0 is never included.
When using channel-associated signaling (CAS) and the bundle is
configured as a voice bundle with CAS, the signaling information
associated with the timeslots transported by the bundle, taken from
timeslot 16 of the E1 stream, is also inserted in the packet.
When using common channel signaling (CCS), the signaling timeslot must
be included in the bundle, and be transparently transferred end-to-end to
the users equipment (for example, a PSTN switch or PBX) at the other
end of the link, which can then extract the desired information from the
CCS timeslot and process it in accordance with the users signaling
protocol. Alternatively, the signaling payload can be transported by
means of a separate HDLC bundle (see HDLCoPSN Processing section
below) to the users equipment (for example, a PSTN switch or PBX) at
the other end of the link, where the signaling information can be
processed.
2-4
When operating in the unframed (G.703) mode, the slices are formed by
collecting consecutive bytes from the received E1 stream until the TDM
payload section of the packet is filled.
Gmux-2000 Ver. 3.2
After building the payload section, the packet processor adds the overhead
necessary to transmit each slice to the desired destination over the packet
switched network (either UDP/IP or MPLS/ETH), and builds TDMoIP,
respectively TDMoMPLS, packets for transmission to the desired destination.
The resulting packets are encapsulated then sent via the packet bus
interfacing subsystem of the module to the PSN interface module.
In the receive-from-network direction, the TDMoPSN packets retrieved from

the received Ethernet frames are temporarily stored in a packet buffer. Each
bundle has its own buffer. The function of this buffer is to enable the packet
processor to read out the received packets at a constant rate, and thus
eliminate jitter in their arrival times. Therefore, this buffer is called jitter
buffer.
Note that the read-out rate must be equal to the average rate at which
frames are received from the PSN. Assuming that the packet loss in the PSN
is negligible, this rate is equal to the rate of the original data stream of each
bundle. The adjustment of the read-out rate to the arriving packet rate is
performed by the adaptive clock recovery mechanism of each packet
processor (the recovered clock signal can also be used as a timing reference
see the Adaptive Timing section on page 2-8).
The packet processor recovers the payload carried by the packets and
restores the original data stream of the bundle, in accordance with the
selected framing mode.
When the bundle carries only selected timeslots, the payload is reinserted in
the appropriate timeslots. Therefore, when several bundles carry payloads
destined to the same E1 port, all the useful payload is reinserted in the
original timeslots, and only the remaining empty timeslots in the internal port
E1 frame are filled with a user-selectable idle code.
In a similar way, when the port uses a framing mode that carries channelassociated signaling (CAS), the signaling information related to the timeslots
transported by each bundle is reinserted in the positions corresponding to
the bundle timeslots.
Since the TDMoPSN packet structure for framed ports does not depend on
the port frame structure, packets carrying traffic from an E1 port can be
directed to a T1 port at the far end, as long as the total number of timeslots
does not exceed 24, and the payload type is data (CAS cannot be transferred
between E1 and T1 ports).
HDLCoPSN Processing
HDLCoPSN packet processing is similar to the processing of TDMoPSN packets
described above, except that the HDLCoPSN protocol is intended to provide
port-to-port transport of HDLC-encapsulated traffic, in accordance with RFC4618,
for example, Frame Relay or CCS protocols.
For framed ports, the HDLC traffic is carried in specific timeslots of an E1 frame
(these timeslots are specified during the configuration of a HDLCoPSN bundle and
are always considered data timeslots).
Gmux-2000 Ver. 3.2
2-5
Note
For HDLCoPSN, it is not necessary to configure the same number of timeslots at

the bundle end points. The bundle bandwidth will be determined by the endpoint
with the smaller number of assigned timeslots.
The HDLCoPSN protocol can also handle whole (unframed) E1 streams.
When assembling packets for a HDLC bundle, HDLC idle flags are removed, and
only the contents of HDLC packets with useful payload are inserted in packets.
This results in better bandwidth utilization efficiency. At the receive end, HDLC
packet structure is restored and inserted in the port data stream. Therefore,
HDLC bundles can connect only ports with same framing mode.
SAToPSN Packet Processing

SAToPSN is different from the TDMoPSN and HDLCoPSN protocols, in that it is
used to transfer transparently a bit stream at the nominal port rate
(2.048 Mbps). Therefore, SAToPSN can be used only when the port uses the
unframed mode, and thus only one bundle can be configured per port.
SAToPSN packet payload consists of a user-specified number of raw TDM bytes
(32 to 1440 bytes), and is treated as data payload.
Note
The SAToPSN packet overhead is large, and therefore, for efficient bandwidth
utilization, the number of raw TDM bytes per packet should be as large as
possible.
The receiving end restores the original bit stream, and therefore a SAToPSN
bundle can only be directed to another unframed E1 port, or to an n 64 kbps
protocol (where n must be 32, that is, to a serial port operating at a rate of
2048 kbps).
CESoPSN Packet Processing

CESoPSN transports raw TDM data, that is, packets are formed by inserting a
user-specified number of complete TDM frames (1 to 45 frames) in the packet
payload area. Therefore, CESoPSN bundles can only be configured on framed
ports.
The TDM frames are considered serial data, even if they carry voice and CAS.
Since a CESoPSN bundle transports raw TDM frames, a CESoPSN bundle can only
be directed to another E1 framed port.
Jitter Buffer Functions

The packets of each bundle are transmitted by pseudowire emulation modules at
essentially fixed intervals towards the PSN. The packets are transported by the
PSN and arrive to the far end after some delay. Ideally, the PSN transport delay
should be constant: in this case, the packets arrive at regular intervals (these
intervals are equal to the intervals at which they had been transmitted).
However, in reality packets arrive at irregular intervals, because of variations in
the network transmission delay. The term Packet Delay Variation (PDV) is used to
designate the maximum expected deviation from the nominal arrival time of the
packets at the far end device.
2-6
Gmux-2000 Ver. 3.2
Note
The deviations from the nominal transmission delay experienced by packets are
referred to as jitter, and the PDV is equal to the expected peak value of the jitter.
Note however that nothing prevents the actual delay from exceeding the selected
PDV value.
To compensate for deviations from the expected packet arrival time, each
pseudowire emulation module uses jitter buffers that temporarily store the
packets arriving from the PSN (that is, from the far end equipment) before being
transmitted to the local TDM equipment, to ensure that the TDM traffic is sent to
the TDM side at a constant rate.
For each bundle, the jitter buffer must be configured to compensate for the jitter
level expected to be introduced by the PSN, that is, the jitter buffer size
determines the Packet Delay Variation Tolerance (PDVT).
Two conflicting requirements apply:
Since packets arriving from the PSN are first stored in the jitter buffer before
being transmitted to the TDM side, TDM traffic suffers an additional delay.
The added delay time is equal to the jitter buffer size configured by the user.
The jitter buffer is filled by the incoming packets and emptied out to fill the
TDM stream. If the PSN jitter exceeds the configured jitter buffer size,
underflow/overflow conditions occur, resulting in errors at the TDM side:
A jitter buffer overrun occurs when it receives a burst of packets that

exceeds the configured jitter buffer size + packetization delay. When an
overrun is detected, the pseudowire packet processing subsystem clears
the jitter buffer, causing an underrun.
A jitter buffer underrun occurs when no packets are received for more
than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is
automatically filled with a conditioning pattern up to the PDVT level in order to
compensate for the underrun. Then, the pseudowire packet processing
subsystem starts processing the packets and empty out the jitter buffer toward
the TDM side.
To minimize the possibility of buffer overflow/underflow events, two conditions
must be fulfilled:
The buffer must have sufficient capacity. For this purpose, the buffer size can
be selected by the user in accordance with the expected jitter characteristics,
separately for each bundle, in the range of 0 to 200 msec.
The read-out rate must be equal to the average rate at which frames are
received from the network. For this purpose, the read-out rate must be
continuously adapted to the packet rate, a function performed by the
adaptive clock recovery mechanism of each packet processor.
After the jitter buffer mechanism reaches a stable state, there may still be
temporary changes in network delay, which occur before the mechanism can
readjust. To provide the best possible user experience the user can specify how
to handle packets under such transient conditions:
Gmux-2000 Ver. 3.2
By specifying that the handling will be sensitive to voice, the user instructs
the receiving end to drop some packets (such packets are then replaced by
2-7
dummy packets). Under normal conditions, this results in negligible voice

degradation.
By specifying that the handling will be sensitive to data, the user instructs the
receiving end to do nothing until eventually an under- or overrun occurs, or
conditions return to normal. This achieves the best possible data integrity
(error correction, or higher protocols, may sometimes compensate for the
resulting problems).
Adaptive Timing
Each PDH port can use the adaptive timing mode to lock its transmit timing to the
clock signal associated with the payload carried by a user-specified bundle.
The adaptive clock recovery mechanism estimates the average rate of the
payload data received in the frames arriving from the packet-switched network.
Assuming that the packet-switched network does not lose data, the average rate
at which payload arrives will be equal to the rate at which payload is transmitted
by the source.
Note
Generally, lost packets, as well as packets that did not arrive in the correct order,
are replaced by special dummy packets. However, for CESoPSN and SAToPSN,
packets can be reordered.
The method used to recover the payload clock of a bundle is based on monitoring
the fill level of the selected bundle jitter buffer: the clock recovery mechanism
monitors the buffer fill level, and generates a read-out clock signal with
adjustable frequency. The frequency of this clock signal is adjusted so as to read
frames out of the buffer at a rate that keeps the jitter buffer as near as possible
to the half-full mark. This condition can be maintained only when the rate at
which frames are loaded into the buffer is equal to the rate at which frames are
removed. Therefore, the adaptive clock recovery mechanism actually recovers the
original payload transmit clock.
The performance of the clock recovery mechanism can be optimized for the
operating environment, by specifying the following parameters:
The accuracy of the original timing source, in accordance with the standard
SDH terminology (Stratum 1, 2, 3, 3E, or 4/unknown)
The type of PSN that transports the traffic: router-based network (for
example, UDP/IP) versus switch-based network (for example, MPLS/Ethernet).
OAM Protocol
The OAM protocol, supported only by packet payload version V2, is used by
pseudowire emulation modules to check for a valid bundle connection: this
includes checks for compatible configuration parameters at the packet processors
at the two endpoints of a bundle, and detection of inactive bundle status.
The information regarding bundle state is collected by the continuous, periodic
handshake between the two endpoints of a bundle, which generates little traffic,
but ensures that each endpoint recognizes the connection, and that it is enabled. In
case no response is received to OAM packets within a predefined interval (a few
tens of seconds), the bundle is declared inactive.
2-8
Gmux-2000 Ver. 3.2
When the use of the OAM protocol is enabled, little traffic flows until the connection
between the two bundle endpoints is established: only after the connection is
confirmed by the OAM exchange is transmission at the normal (full) rate started,
and the bundle starts carrying traffic. In case the connection is lost, the transmitted
traffic is again significantly decreased (several packets per second per connection).
The OAM connectivity check also prevents network flooding in case the
connection is lost.
The user can specify the method used to identify OAM packets:
In accordance with source port: in this case the OAM packets run over a UDP
port number that is assigned only for OAM traffic, but use the same VLAN ID
and ToS of the originating connection.
In accordance with the contents of the control word, which is included in

version V2 packets (Virtual Circuit Connection Verification VCCV): the first
four bits of an OAM control word are always set to 0001.
Alarm Indications
For TDM ports, the applicable standards specify the methods used to report loss
of signal, loss of frame alignment, AIS reception, reception of a remote defect
indication (RDI) from the equipment connected to the TDM port, etc.
However, to provide a complete picture of a packet transmission system, it is
necessary to generate additional alarms that cover transmission problems
through the packet-switched network, problems caused by incorrect or
incompatible configuration, equipment malfunctions, etc.
For example, the bundle payload cannot be reconstructed when one of the
following conditions occurs:
The far end cannot send packets because of a failure (loss of signal, loss of
frame alignment, or reception of AIS by the far end port)
Jitter buffer underflow or overflow at the local end.
Failure of the transmission path that prevents the reception of packets at the
local end.
In such cases, all the bundle timeslots in the recovered E1 stream are filled with
the user-selected out-of-service (OOS) code; with CAS, the signaling information
in timeslot 16 is also replaced by the user-selected signaling OOS code.
Note however that the conditions listed above are detected at the local end of a
trail (path through the network). When using a framed mode, an E1 port
terminates timeslot 0, and therefore, when the users application requires that
alarms be propagated to the far end of the trail, it is necessary to use a special
alarm generation mode, called the trail extension mode, in contrast to the trail
termination mode described above.
Note
The trail extension mode is supported only when bundles use the OAM protocol.
When the trail extension mode is selected, some alarm conditions are reported
over the transmission path, and reflected in the signal generated by the port at
the other end of the path (the far end port):
Gmux-2000 Ver. 3.2
2-9
AIS is transmitted by a far end E1 port toward the connected equipment

when all the bundles connected to that port failed.
RDI is transmitted by a far end E1 port toward the connected equipment

when all the bundles connected to that port receive packets with the R bit
(remote alarm flag) set.
Note that AIS can be transmitted even when using the unframed mode, whereas
RDI can be transmitted only when using a framed mode.
Description of Gmux-2000 System Used for Voice Trunking Services

When Gmux-2000 is used in voice trunking services, voice compression modules
are installed, instead of the pseudowire emulation modules shown in Figure 1-10.
A Gmux-2000 can include up to seven voice compression modules, each operating
independently. For a description of the voice compression subsystem integration
within the Gmux-2000, see the Voice Compression Operating Modes section on
page 2-13.
Figure 2-3 shows the structure of a voice compression module.
UE
External E1
Voice Ports
(1-16 or 1-12)
Voice Port
Line
Interfaces
Voice
Port
US
Mode
Selection
Internal
E1 Voice
Ports
Voice
Compression
and
Signaling
Processor
Payload
Processor
Packet
Bus
Interface
External E1
Data Ports
LINK 2
Data Port
Line
Interfaces
To SDH
Interface
Subsystem
NE
NS
Data
Port
Mode
Selection
Internal
E1 Data
Ports
Timeslot
Cross
Connect
Control and
Status Signals
Management
Clock Signals
Timing and
Clock
Generation
SDH Interface
(Mapper)
To CONTROL Module
LINK 1
To PSN Interface Subsystem
Figure 2-3. Voice Compression Subsystem Structure

The operation of the main voice compression module subsystems is described
below.
2-10
User Interfacing Subsystem. The user interfacing subsystem of each module

includes 16 or 12 voice ports (depending on the voice compression module
type), each comprising an E1 framer and a port interface.
Gmux-2000 Ver. 3.2
In the transmit path, each voice port synchronizes to the incoming E1

stream, terminates timeslot 0, collects the payload from the incoming E1
timeslots, and sends the audio signals to the voice compression
subsystem. The port signaling information is collected by the signaling
interface and sent to the payload processor for processing.
In the receive path, each port collects the decompressed audio signals
from the voice compression subsystem and the restored signaling
information from the signaling interface, adds the framing overhead, and
rebuilds the E1 frame in accordance with the selected framing mode.
The voice ports support the following framing modes:

with ITU-T Rec. G.704 and G.706. The CRC-4 option should be selected
whenever possible, because it allows to monitor the E1 link transmission
performance.
The basic G.704 framing mode is required for applications that require
CCS. The user can specify the timeslots that carry the CCS protocol (up to
two timeslots). These timeslots are then transferred to the payload
processor, for processing. The supported CCS protocols are ISDN, QSIG
and SS7.

with or without support for CRC-4. This framing mode is required for
The voice ports have two sets of interfaces:
External physical interfaces for directly connecting to the users PBX/voice

switch. Each voice port has a balanced ITU-T Rec. G.703 interface.
Internal interfaces (internal ports) that connect through the voice

compression module SDH mapper to the Gmux-2000 telecom buses.
These internal ports are mapped to VC-12s on the desired SDH ports, and
the path parameters can be configured as for any other VC-12 ports.
At any time, only one set of voice port interfaces (either the external or the
internal set) is active, that is, connected to the E1 voice framers, in
accordance with the selected operating mode (see VC-E1/16 Operating
Modes section in Chapter 1).
Network Interfacing Subsystem. The network interfacing subsystem consists

of data ports, each comprising an E1 framer and a port interface.
In the transmit path, each data port collects the compressed audio
signals from the payload processor and builds the data stream for
transmission to the network.
In the receive path, each data port synchronizes to the incoming data
stream, collects the payload and sends it to the payload processor, for
further processing (separation of signaling and compressed audio).
The payload processor provides the information to be sent to the network,

and it also handles the information received from the network. The
connection between the data ports and the payload processor is made by a
timeslot cross-connect matrix.
Gmux-2000 Ver. 3.2
2-11
The data ports support the following framing modes:
Basic G.704 framing mode, with or without support for CRC-4 in

accordance with ITU-T Rec. G.706, with timeslot 0 terminated at each
port.
This mode provides 31 payload timeslots per port (total bandwidth
available for payload 1984 kbps), and has the advantage that it
supports channelizing for point-to-multipoint applications. The number of
subchannels that may be defined on each port is up to 10 (the minimum
is 1). Each subchannel operates essentially as a transparent pipe for a
preconfigured fraction of the total payload.
Unframed mode. This mode provides 32 payload timeslots per port, and
therefore enables full utilization of link bandwidth (2048 kbps), but can
be used only for point-to-point applications (no channelizing the whole
port is handled as a single subchannel).
The data ports have two sets of interfaces:
External E1 physical interfaces, for directly connecting to E1 transmission

equipment. The number of external E1 data ports is 2.
Internal interfaces (internal ports) that connect through the SDH mapper
to the Gmux-2000 telecom buses. The number of internal data ports is
either 2 (without backup) or 4 (backup enabled). These internal ports are
mapped to VC-12s on the desired SDH ports, and the path parameters
can be configured as for any other VC-12 ports.
At any time, only one set of data port interfaces (either the internal or the
external ports) is active, that is, connected to the E1 data framers, in
accordance with the selected operating mode (see Voice Compression
Operating Modes section on page 2-13).
To improve service availability, the network interfacing subsystem can be
configured to provide backup for the connection to the network. In this case,
the data ports operate in pairs:
When using the external E1 data ports, the maximum bandwidth of the
network connection is the bandwidth available on a single port
(1984 kbps for framed modes, 2048 kbps for the unframed mode).
When connecting through the internal (SDH) ports, the maximum

bandwidth is the bandwidth available on two ports.
Packet Bus Interfacing Subsystem. The packet bus interfacing subsystem

includes an Ethernet switch that handles the traffic flow between the internal
packet ports of the payload processor and the Gmux-2000 packet buses, en
route to the GbE PSN interface module. This traffic flow is configured by
defining bundles terminated on GbE ports.
The internal packet ports are connected to the chassis packet buses via two
Fast Ethernet transceivers.
2-12
Voice Compression Subsystem. The transmit path of the voice compression

subsystem converts each payload timeslot to a stream of packets for
transmission through the network.
Gmux-2000 Ver. 3.2
The packets are sent to the payload processor, which transfers the packets
of each bundle of timeslots either to the appropriate internal or external
(network) data port and subchannel, or to GbE module, via the packet bus
interface.
The receive path receives from the payload processor streams of packets for
each payload timeslot, and sends the decompressed voice streams to the
corresponding voice port framer.
Signaling Processing Subsystem. In the transmit path, the signaling interface

retrieves the signaling information of each port from the appropriate
timeslots, in accordance with the port signaling transfer mode (CAS or CCS),
and transfers it to the payload processor for processing.
In the receive path, the signaling interface inserts the signaling information of
each port restored by the payload processor in the appropriate timeslots.
Voice compression modules do not use the signaling information: the
signaling information is only transmitted through the compressed voice
connections, for use by the users equipment at the local and remote
endpoints.
Timing and Clock Generation Subsystem. The timing of each E1 port is derived
as follows:
Transmit path: the transmit timing of each external port can be either:
Derived from the Gmux-2000 nodal timing. In this case, the

equipment connected to the corresponding port must use loopback
timing.
Locked to the clock signal recovered from the receive line signal of
the port. This locks the port transmit timing to the transmit timing of
the equipment connected to the port receive clock (loopback timing).
All the E1 ports, whether data or voice, must use the same clock source.
Note
Receive path: the receive path of each E1 port always receives the clock
signal from the external E1 port.
The receive clock frequency must always be equal to the transmit clock
frequency.
Voice Compression Operating Modes

Note
The following description uses the mode designations as they appear on

supervision terminal and Telnet screens.
Voice compression modules can be configured to operate in four modes, which
differ with respect to signal flow among the TDM ports: UE_NE, US_NE, UE_NS,
and US_NS.
The various operating modes are described below. For clarity, the voice
compression, signaling interface, and payload processor subsystems of Figure 2-3
have been shown as a single voice compression subsystem in the following
figures (Figure 2-4 to Figure 2-7).
Gmux-2000 Ver. 3.2
2-13
Note that in operating mode modes, traffic from the active user ports can also be
directed to the packet buses. This connection (from the payload processor, via
the packet bus interface see Figure 2-3), has been omitted in Figure 2-4 to
Figure 2-7, because it is always available, irrespective of the selected mode.
UE_NE Mode: In this mode, Gmux-2000 voice compression subsystem accepts

user traffic from the 16 or 12 external E1 ports (User External UE) and
sends the compressed traffic through the external E1 network ports of the
module (Network External NE) (see Figure 2-4).
UE_NE Mode
1
Voice
Compression
External
Voice Ports
1-16 E1
Timeslot
Cross
Connect
LINK 1
External
Data Ports
LINK 2
16
Figure 2-4. Signal Flow in UE_NE Mode
US_NE Mode: In this mode, Gmux-2000 voice compression subsystem accepts

user traffic from the SDH ports (User SDH US) located on the STM1 module,
and sends the compressed traffic through the external E1 network ports of
the module (Network External NE) (see Figure 2-5).
US_NE Mode
1
To STM1
Modules
SDH
Mapper
Internal
Voice Ports
Voice
Compression
Timeslot
Cross
Connect
LINK 1
External
Data Ports
LINK 2
16
Figure 2-5. Signal Flow in US_NE Mode
2-14
UE_NS Mode. In this mode, Gmux-2000 voice compression subsystem accepts

user traffic from the 16 or 12 external E1 ports (User External UE), and
sends the compressed traffic in VC-12s through SDH ports (Network SDH
NS) located on the STM1 module (see Figure 2-6).
Gmux-2000 Ver. 3.2
UE_NS Mode
1
External
Voice Ports
1-16 E1
Voice
Compression
Timeslot
Cross
Connect
Internal
Data Ports
SDH
Mapper
To STM1
Modules
16
Figure 2-6. Signal Flow in UE_NS Mode
US_NS Mode. In this mode, Gmux-2000 voice compression subsystem accepts

user traffic from the SDH ports (User SDH US) located on the STM1 module,
and sends the compressed traffic through the same, or other, SDH ports
(Network SDH NS) (see Figure 2-7).
US_NS Mode
1
Internal
Voice Ports
Timeslot
Cross
Connect
Voice
Compression
Internal
Data Ports
LINK 1
3
4
LINK 2
16
SDH Mapper
To STM1
Modules
Figure 2-7. Signal Flow in US_NS Mode
Handling of Voice Signals

The 64 kbps PCM-encoded voice signals received through the voice compression
module user (voice) ports can be compressed using one of the compression
algorithms supported by the voice compression. To support voice transmission
systems based on both E1 and T1 standards, the user can specify the
companding law used by the PCM sections (A-law or -law, in accordance with
ITU-T Rec. G.711).
The supported low bit rate voice compression options and data rates are as
follows:
Gmux-2000 Ver. 3.2
Voice compression using multiple-pulse, maximum likelihood code-excited

linear prediction (MP-MLQ) per ITU-T Rec. G.723.1, at a channel data rate of
5.3 or 6.4 kbps.
Voice compression using conjugate structure-algebraic-code-excited linear

prediction (CS-ACELP) per Annex A of ITU-T Rec. G.729A, at a channel data
rate of 8 kbps.
2-15
Note
When using the ITU-T Rec. G.729A coder, the user can configure the caller ID
signaling protocol (Bellcore Type 1 or V.23), and delay the sending of the caller ID
information by a selectable interval.
In addition, the user can also select uncompressed transmission, which requires a
channel rate of 64 kbps, by specifying a PCM coder (that is, an ITU-T Rec. G.711
coder with A-law or -law companding). This option is not available when using
the super-tandem mode.
Although voice is not compressed when using PCM (ITU-T Rec. G.711) coders, all
the other signal processing functions and services are active; moreover, the
selected companding law, which is used towards the network, can be different
from that used for the local traffic.
Note
When using ITU-T Rec. G.711 coders, the maximum number of active E1 ports per
voice compression module is maximum 8 (ports 1 to 8).
With regular voice encoding methods, much bandwidth is wasted during the
normal periods of silence in a call (it is often assumed that up to 60% of the call
duration consists of quiet intervals). Therefore, to further reduce the actual
bandwidth required for voice transmission, the voice compression subsystem
supports voice activity detection (VAD), with silence detection and suppression.
To improve silence detection in noisy environments, the user can select between
the internal VAD policy, which complies with the standard silence detection
methods, and the RAD-proprietary generic VAD policy, which allows the user to
select the detection threshold: one for high background noise, another for
normal background, or to cancel the VAD function altogether (this last option is
not supported for uncompressed (ITU-T Rec. G.711) voice, because in this case
the only way to improve bandwidth utilization efficiency is to use the VAD
function). At the receiving side, the far end fills the silence interval with noise
having characteristics similar to normal background noise (this capability is called
comfort noise generation CNG), to give the far end subscriber the impression of
a live line, and therefore the subjective quality of the call is not noticeably
affected. The use of comfort noise generation is also a user-selectable option.
To improve the perceived communication quality, the following additional
capabilities are offered:
Adaptive compensation for delay variations in voice packet transport over the
network. The compensation is performed by a special mechanism which
automatically adjusts the jitter buffer size to the actual delay variations, and
thus keeps the end-to-end delay in the voice path to the minimum possible
(see TDMoPSN Packet Processing section on page 2-4 for a description of
jitter buffer functions).
Adaptive echo canceling for near-end reflections (echo delay up to 32 msec).

The echo canceling performance complies with ITU-T Rec. G.168
requirements, and is user-selectable for each bundle.
Echoes are generated at the points the transmission path changes from
4-wire to 2-wire. Therefore, echo canceling is needed only when 2-wire
equipment (phones, fax, modems) are used at the end points served by this
bundle.
2-16
Gmux-2000 Ver. 3.2
Only one echo canceller should be used at each end point that connects to
2-wire equipment. Therefore, if another echo canceller is already inserted in
the signal path of a bundle, for example, at a PBX, the echo canceling
function of the module should be disabled for that bundle.
Control over the transmit and receive levels of the audio path (the receive
path transmits towards the local users equipment, for example, PBX, and the
transmit path receives the signal from the local equipment). This function can
be used to compensate for attenuation in the audio paths. For example,
when a local subscriber is connected by a long line to the PBX, the input and
output gains can be increased to compensate for the expected attenuation,
and thus improve the perceived voice quality.
Being able to select the correct nominal transmit input level (that is, a level
that matches the nominal signal level received from the voice equipment) has
an additional advantage: it ensures the best voice compression performance,
because the compression DSP then operates at its optimum point.
Support for super tandem links, that is, links which comprise several
segments connected in tandem, where each segment could perform voice
decompression and compression. Recompression would significantly degrade
voice quality. Therefore, when the super tandem mode enabled, the voice
compression module detects whether the arriving voice data has already been
compressed by another voice compression module or Vmux Voice Trunking
Gateway, and transfers such data unmodified. This is always required on the
intermediate segments of tandem links.
When the super tandem mode is enabled, the uncompressed voice option
(that is, the use of ITU-T Rec. G.711 coders) is not available.
Processing of Inband Signaling

Inband signaling by means of tones, for example, DTMF, MFR2 and MFC, is widely
used in modern telephony networks. Pure tones are also used for various
functions, for example, 2000 Hz tones are sometimes used for continuity checks
(COT).
The waveform of such signals is very different from speech waveforms, therefore
most compression algorithms distort them; for example, distortion of DTMF
signals transmitted as analog signals through a compressed voice channel may
cause errors to occur in the detection of the dialed digits by PBXs and other
equipment.
The method used to overcome this problem is referred to as relaying: when
relaying is enabled, the transmit path demodulates the signal to retrieve the
encoded data, and transmits the data through the link; the receiving end then
synthesizes a clean signal carrying the data, for transmission to the users
equipment. For example, to enable reliable transmission of DTMF signals, the DSP
detects incoming DTMF signals, independently for each timeslot, and identifies
the dialed digits. The detected digits are digitally transmitted through the link to
the far end, where clean digital representations of DTMF signals are synthesized
and inserted into the decompressed data stream sent in the corresponding
timeslot.
Gmux-2000 Ver. 3.2
2-17
While inband signaling is received, the voice path is disconnected, to prevent

interference by signals transmitted through the regular processing path.
The method used for DTMF relaying is also used to transfer transparently call
progress tones.
Voice compression always relay DTMF signals, using preconfigured parameters
that ensure optimal operation.
With respect to 1780 and 2000 Hz tones, and for MF-based signaling (for
example, MFR2/R2 and MFC), relaying can be enabled/disabled by the user.
For MF signaling, the user can specify detection parameters, for example, then
minimum level and duration a signal must exceed in order to be detected as a
signaling code, and can also enable MFC spoofing, which shortens the call setup
delay when using R2-MFC signaling by forcing an acknowledge after a
user-selectable interval.
Note
Uncompressed voice channels, using PCM (that is, ITU-T Rec. G.711 coders), can
transmit inband signaling without significant distortion, yet DTMF and tone
relaying are always preferable and should be enabled.
MF relaying is always disabled when using an ITU-T Rec. G.711 coder.
Automatic Fax Processing

The processing of audio signals by low bit rate voice compression methods does
not enable analog transmission of fax signals. Therefore, when it is expected that
a compressed voice bundle will carry signals generated by fax machines, it is
necessary to enable the automatic fax relaying function.
When automatic fax relaying is enabled, a voice compression module will
automatically recognize and transmit Group III fax messages at the standard rates
in the range of 4.8 to 14.4 kbps. The maximum fax rate can be selected by the
user. The module supports automatic fallback capability, that is, it will
automatically switch to the next lower data rate supported by both
communicating faxes.
The whole fax transmission process is therefore handled as a data transmission,
with the module DSP providing the fax signal modulation/demodulation functions
and the detection and generation of the fax connection set up tones (in digital
format), to enable the handshaking necessary to implement the standard fax
communication protocol. Fax relaying works as follows:
To set up a fax connection, the DSP processing the local timeslot (channel)
emulates the remote fax machine toward the local machine, and the remote
DSP emulates the local fax toward the remote machine.
After the fax connection is established, the fax data stream is transmitted as
a packetized data stream through the link. This means that the link must have
enough free bandwidth to enable sustained transmission of a data stream at
the fax data rate (and the additional connection supervision signals).
This process enables any standard Group III facsimile machine to transmit over
the link. The only limitation is that the round-trip transmission delay through the
link cannot exceed the time-out intervals specified by the fax communication
2-18
Gmux-2000 Ver. 3.2
protocol (about 700 msec); otherwise, the handshaking needed to establish a fax
connection will fail.
Note
When necessary, the minimum time a 1100 Hz or 2100 Hz must be present for
positive detection of a modem or fax signal can be fine-tuned.
For bundles expected to carry non-standard fax protocols, which are not
recognized by the module DSPs, the user can configure voiceband fax
transmission. In this case, a timeslot carrying a fax transmission is handled as an
analog voiceband signal with unknown characteristics, and it is therefore
transferred using one of the following types of coders, which are both capable of
transferring complex waveforms with little distortion:
ITU-T Rec. G.711 A-law or -law PCM coder (the same coders available for
uncompressed voice), which require a channel rate of 64 kbps. PCM requires
a bandwidth on the order of one timeslot on the network side
ITU-T Rec. G.726 ADPCM coders, which compress the signal to a channel rate
of 32 kbps (commonly used in Europe, and other countries using the
E1-based hierarchy), or 24 kbps (commonly used in North America, and in
countries using the T1-based hierarchy). ADPCM provides performance very
close to PCM, but requires significantly less bandwidth (40% to 50% of that
required by PCM) on the network side.
The selected voiceband coder is used for both fax and modem voiceband
transmissions.
Handling of Voiceband Modem Signals

Voice compression modules handle voiceband modem signals using either relaying
or voiceband signal transmission, as selected by the user:
Modem relaying is similar to fax relaying, except that the DSP emulates a
voiceband modem instead of a fax modem. The recognized modem protocols
include V.22/V.22bis, V.32/V.32bis, and V.34 up to 21.6 kbps
Voiceband transmission, using the selected voiceband coder, can be

configured by the user for all the modem calls. When modem relaying is
enabled, voiceband transmission is automatically used for any unrecognized
modem protocol.
Handling of Voice Trunk Signaling

Two voice trunk signaling methods are in use, CAS and CCS.
CAS Handling. Channel-associated signaling (CAS) can be used when an E1

voice port uses G.704 framing with timeslot 16 multiframe. Timeslot 16
carries the signaling information: four signaling bits (designated A, B, C, D)
are used for each channel, for a total of 30 signaling channels.
Each voice port needs to retrieve the CAS information needed by each
channel (timeslot), and transfer it within the voice packets to the far end.
To provide the flexibility needed to adapt to variations to the standard
signaling codes that are sometimes implemented by PBX equipment
manufacturers, the module supports the definition of specific interpretation,
Gmux-2000 Ver. 3.2
2-19
or translation, rules called signaling profile. The profile modifies the signaling
information in the direction from the network to the PBX (local user) side.
Each voice port can use a different signaling profile. The total number of
different signaling profiles that can be defined for each module is up to 5.
In addition to signaling translation, each profile also enables defining the
signaling code to be sent to the local user (PBX) to indicate idle timeslots,
and the code sent to indicate the out-of-service state (that is, a timeslot that
cannot carry traffic, for example, as a result of a test or maintenance
activity).
CCS Handling. Common-channel signaling (CCS) uses dedicated timeslots

within the E1 structure to carry serial data channels for exchanging signaling
information between the local and far end. CCS can be used when an E1 voice
port uses the basic G.704 framing mode.
With CCS, it is usually necessary to transfer the signaling information
transparently through the link, in parallel with the voice payload, and let the
end users equipment interpret the signaling. This transfer uses an optimized
HDLC protocol, which is transparent to the endpoints.
For one widely used protocol, Signaling Scheme 7 (SS7), it is possible to
increase bandwidth utilization efficiency, because SS7 uses two specific types
of protocol signal units (messages) that do not carry signaling information:
Link status signal units (LSSUs): used to exchange information regarding

the status of the SS7 signaling link between two endpoints. After a
signaling link is successfully set up between the SS7 link endpoints, the
LSSUs carry little new information.
Fill-in signal units (FISUs): used just to keep the HDLC signaling link alive.
These messages do not carry any information payload, and are
transmitted only when there no other types of SS7 signal units to
transmit. In the absence of other signaling traffic, the signaling links carry
a significant number of FISUs.
To reduce the bandwidth wasted to transmit LSSUs and FISUs, the voice
compression subsystem can be configured to suppress a certain fraction of
these messages (up to 90%). When the suppression ratio is 0%, the channel
performs the same as a HDLC channel.
Voice compression modules support one HDLC timeslot and one SS7 timeslot
per trunk.
Voice Packet Processing

The assembly and disassembly of voice packets for transport over the network is
handled by the payload processor. Two sets of parameters for this purpose are
needed:
2-20
Parameters used to define compressed voice (CV) bundles. A bundle consists

of selected timeslots from a common voice port that have the same
destination, and require identical processing (same voice coding method,
same voice processing parameters, etc.).
Parameters used to define the network connection parameters, that is, a

physical port and the assigned bandwidth (number of timeslots) on that port,
Gmux-2000 Ver. 3.2
for the compressed voice traffic. The bandwidth is determined by defining

subchannel characteristics.
Note
Multiple bundles may be carried over a single subchannel, provided the available
bandwidth is sufficient.
The voice packets transmitted to the network are inserted in a multiplexed frame
structure. The frame can include a total of 100 to 1461 bytes, where a smaller
number yields lower delays, and a larger size improves bandwidth utilization
efficiency.
A time-out interval (10 to 90 msec) is also defined, after which the current frame
is sent even if it is not filled up completely.
Estimating Bandwidth Requirements

Two basic methods of encapsulation and multiplexing of voice packets are
supported by voice compression modules: TDM for use over IP networks
(TDMoIP), and AAL2 for use over MPLS networks (AAL2oMPLS). Both methods
take the packets containing the compressed voice and add additional data for
enabling transport over the corresponding type of network:
Note
For TDMoIP, the data includes UDP encapsulation followed by encapsulation

in Ethernet frames, with or without VLAN information.
For AAL2oMPLS, the data includes MPLS encapsulation followed by

encapsulation in Ethernet frames, with or without VLAN information.
In addition to traffic packets, voice compression modules also send connectivity

check packets.
The size of the voice packets depends on the selected coding method, and on
the encapsulation method.
Since a significant fraction of the number of bytes in each packet is used to carry
headers data, the module supports two additional RAD-proprietary,
bandwidth-efficient encapsulation methods, identified as TDMoIP+ and
AAL2oMPLS+.
The actual number of packets generated depends on the voice activity, and may
vary widely over short intervals, although over the long term the average number
changes much less.
Despite the statistical variations, it is necessary to make preliminary evaluations
of the bandwidth needed to carry the expected traffic. RAD offers a dedicated
Bandwidth Calculator, which can be used to predict the required bandwidth,
taking into consideration the following main parameters:
Packet size
Selected coder
Silence percentage.
With time, the bandwidth utilization statistics can be analyzed, and the assigned
bandwidth be modified to better match actual traffic.
Gmux-2000 Ver. 3.2
2-21
For this purpose, Gmux-2000 automatically collects voice compression

performance statistics, and stores the data in a file, STAT.DAT, that can be sent
by TFTP to a RADview-SC/Vmux Service Center.
Preventing Excessive Bandwidth Consumption

The bandwidth needed to transport compressed voice is not constant, but varies
in accordance with the actual amount of intelligence transmitted in each timeslot
at each instant. For example, for voice calls the required bandwidth decreases
during silence intervals and increases while users talk; in modem or fax calls, the
bandwidth is relatively constant for long intervals.
To safely use as much bandwidth on the network connection as possible without
degrading the quality of service, the following procedures are used:
The voice compression module can signal the equipment connected to voice
ports, for example, a PBX, that new calls cannot be accepted when a certain
bandwidth utilization threshold is exceeded. For this purpose, the module
uses the relevant portions of the protocol specified in ITU-T Rec. Q.50. The
threshold at which new calls will be rejected is selectable, and the selection
applies to all the voice ports.
ITU-T Rec. Q.50 specifies a protocol that uses 3 bits in timeslot 16 of the
multiframes to establish a communication link between the module and the
equipment connected to each voice port.
Since this protocol is effective only when the connected equipment supports
it, the use of the ITU-T Rec. Q.50 is separately configurable for each voice
port. Moreover, for compatibility with different implementations, the user can
select for each voice port the particular implementation:
ITU-T Rec. Q.50 Annex A: in addition to the communication link in timeslot

16, this Annex enables the user to specify the signaling bits to be used
for call setup. Only two bits are used for this purpose: either A, B or C, D;
these bits are selectable separately for each port. The module will ignore
the other two bits.
ITU-T Rec. Q.50 Annex B: this Annex specifies that only signaling bits A, B
be used for call setup.
For ongoing calls, the voice compression module has an additional mechanism
that randomly discards a small portion of voice packets on each call when the
available bandwidth is not sufficient to transfer the offered traffic. This
mechanism does not depend on support by the connected equipment, and is
always active.
The user can configure the threshold at which voice packets start to be
discarded, which must always be higher than the threshold specified for call
rejection using ITU-T Rec. Q.50.
The algorithm used by the voice compression module for this purpose leads
to a temporary degradation of voice quality, that in many cases is quite
tolerable, and is always preferable to call disconnection as a result of
congestion. During congestion conditions, buffers may overflow and are
flushed. Therefore, overflow event are very disruptive, because they
2-22
Gmux-2000 Ver. 3.2
effectively disconnect the link, and any means for avoiding congestion has a
very positive effect on voice transmission.
The last bandwidth control mechanism at the module level is used to block
new modem calls when bandwidth utilization reaches a certain threshold.
Since modem calls can be transmitted either as analog (voiceband) signals or
using relaying, separate thresholds are used for each type of modem call.
A similar mechanism is supported at the connection (bundle) level.
Processing of Transparent Timeslots

To support a wider range of services, voice compression modules can also
transfer transparently selected voice port timeslots. Timeslots configured for
transparent transfer bypass the voice compression subsystem, and are converted
to packets without any compression.
At the receive side, the data contained in packets carrying the transparent
timeslots is directly converted to a data stream that is inserted in the
corresponding timeslots, without passing through the voice decompression
subsystem. This restores the original payload carried in the selected timeslots.
The user can specify the jitter buffer size used for the data carried by transparent
timeslots, in the range of 20 to 100 msec. Since usually such timeslots carry data,
this permits to select the most appropriate jitter buffer while restricting the
round-trip delay to acceptable values.
Transparent timeslots can be included in each compressed voice bundle. Note
that the payload data rate for such timeslots is always equal to the timeslot rate,
64 kbps. The required bandwidth on the links is slightly higher than 64 kbps,
because of the packet overhead.
Gmux-2000 Ver. 3.2
2-23
2.3
Connection (Bundle) Handling
Overview
The Gmux-2000 can provide large numbers of simultaneous pseudowire
connections through the packet-switched network. When using the TDMoIP
version V2 (the current standard version), the rated Gmux-2000 maximum is 556
pseudowire connections to up to 256 remote destinations.
In this manual, as well as on management screens, pseudowire connections are
also referred to as bundles.
Gmux-2000 supports two basic types of bundles:
Bundles for transport of TDM traffic, using pseudowire emulation, supported

by E1-PW-SRV/21 and E1-PW/28 modules. the protocol used by each bundle
can be selected in accordance with the type of traffic and application
requirements:
Transparent transfer of data (unframed E1 streams) can use TDMoPSN, or

SAToPSN, or HDLCoPSN
Transfer of framed E1 streams can use TDMoPSN or CESoPSN

HDLC traffic, in particular Frame Relay traffic, carried over framed and
unframed E1, can use HDLCoPSN.
Bundles for compressed voice traffic, supported by VC-E1/16 and VC-E1/12

modules.
Each bundle can be configured for operation over UDP/IP or MPLS/ETH networks.
Bundle Configurations Storage

Storing large numbers of bundle configurations has the advantage that a stored
inactive bundle configuration can be rapidly switched to the active state by
changing its administrative status. The maximum number of bundle (connection)
configurations that may be defined on the Gmux-2000 is 2000, where each
bundle is assigned a unique index number in the range of 1 to 2000.
However, the maximum number of bundle configurations the Gmux-2000 can
actually store depends on the type and number of modules installed in the
chassis:
E1-PW-SRV/21 and E1-PW/28: 16 bundle configurations for each E1 port, and

a maximum of 112 bundle configurations per module
VC-E1/16, VC-E1/12: 32 bundles per module.
Number of Active Connections (Bundles)

The maximum number of active connections depends on two factors:
2-24
The maximum number of active bundles at the source module level:
Gmux-2000 Ver. 3.2
E1-PW-SRV/21, E1-PW/28: maximum 16 active bundles per E1 port, and

up to 112 per module, where up to 99 bundles can have the same
destination
VC-E1/16, VC-E1/12: maximum 32 active bundles per module. The number

of bundles per voice port depends on users requirements (each bundle
can carry any number of timeslots, up to 30).
The maximum number of active connections at the Gmux-2000 level, which is

determined by the bandwidth and switching capacity of the GbE module.
With respect to bandwidth, a single GbE port is sufficient to carry the traffic
load generated by the maximum possible number of active bundles, whereas
Gmux-2000 supports a maximum of two active GbE links. Each PSN interface
module has two GbE ports, which can be configured either as independent
ports, or as a single aggregated link, or as redundant ports. Therefore, it is
possible to split the traffic among the two ports in accordance with the
specific application requirements and load balancing considerations (when
two GbE modules are installed, redundancy must always be enabled).
With respect to switching, it is necessary to consider the capabilities of the
Layer 2/3/4 Gigabit Ethernet switch of the module, versus the resources
consumed by each bundle: each UDP/IP bundle uses one pair of Layer 3 and 4
addresses (e.g., UDP socket and IP address) for each endpoint. An IP address
can be associated with a number of different Layer 4 sockets.
Note
TDMoIP bundles using TDMoIP Version V1 requires two UDP ports per bundle.
Therefore, to perform bundle routing operations, the internal GbE Ethernet
switch must store pairs of Layer 4 (UDP) sockets and IP addresses, which
require memory space for storage.
To enable efficient utilization of the memory space, the switch has a total of
four Layer 4 socket pools, where each pool has a different size. In each pool,
the user can specify the number of Layer 4 sockets per IP address, and the
total number of IP addresses. By design, pool 1 supports the smallest number
of UDP sockets per IP address, and pool 4 supports the largest number. The
maximum number of entries in all of the four pools is 4096.
When configuring the Layer 4 pools, take into consideration the following
factors:
Gmux-2000 Ver. 3.2
Each connection to a remote destination requires one IP address, and

therefore the total number of IP addresses determines the total number
of remote connections that can be simultaneously supported by the
Gmux-2000.
The number of UDP sockets per IP address determines the maximum

number of bundles to that destination. For TDMoIP packet version V2, the
number of bundles is equal to the number of UDP sockets, whereas for
TDMoIP V1 the number of bundles is half the number of UDP sockets.
2-25
Table 2-1. Default GbE Switch Layer 4 Pool Configuration, and Resulting Bundle Handling Capacity
Pool
Number of UDP Sockets per IP

Address in Pool
Number of Remote IP
Addresses in Pool
Total V2 Bundle
Capacity per Pool
300
600
138
1104
16
72
1152
200
1200
Total for all Pools
516
4056
For efficient utilization, it is recommended to apportion the total pool

capacity so that pool 1 handles the required number of remote connections
(IP addresses) with the smallest number of bundles per IP address, and so on,
up to pool 4, which handles the required number of remote connections with
many bundles per IP address.
When the total number of bundles and destinations is not too large, the
apportioning of the available capacity is not very critical, and the default
values are a good starting point. In more complex applications, the
apportioning should be made by trial-and-error, i.e., by starting each trial
from some arbitrary selection of the number of bundles per IP address and
improving the guess on each trial.
Bundle Configuration Parameters

The bundle (connection) parameters define the way payload will be transported
from a local Gmux-2000 TDM port, through the packet-switched network, and
down to a remote destination supporting the same capabilities.
The parameters depend on the bundle type, which determines the type of traffic
handled by the bundle (compressed voice, data and/or voice traffic, or HDLC
traffic), and on the PSN type (UDP/IP or MPLS/ETH).
TDMoIP Bundle Parameters

The user can configure the following bundle parameters:
2-26
Parameters needed by the packet processor to determine the bundle

structure and its handling, for example:
The type of protocol used to build the bundle: TDMoPSN, HDLCoPSN,

CESoPSN, or SAToPSN. This protocol must match the type of traffic to be
carried by the bundle (see page 2-24).
The packet structure required by the PSN: UDP/IP or MPLS/ETH.
The payload section size.
The framing mode (which determines the signaling method), and the
various out-of-service signaling codes. These parameters are implicitly
determined when the associated internal E1 port is configured.
Gmux-2000 Ver. 3.2
The transported payload: selected timeslots, versus all the timeslots or

the whole stream
Adaptive timing: when you enable adaptive timing for a bundle, you also
implicitly specify that the bundle will serve as the timing reference for the
E1 port at which the bundle is connected (a bundle can be connected to
only one port).
Jitter buffer size needed to compensate for the expected delay variation
of the PSN.
Timing parameters: enable/disable the adaptive clocking.
Out-of-service signaling, and response to bundle out-of-service

conditions.
Parameters that ensure compatibility with the remote end users equipment,
for example:
The packet payload format (version V1 versus V2).
The far end interface type.
The use of the OAM connectivity protocol, and the method used to
identify OAM packets.
Routing parameters:
Note
Layer 2 parameters: VLAN tagging according to IEEE 802.1Q
The same VLAN ID must be used for all the bundles addressed to a given IP
address.
Layer 3 parameters:
Note
Destination IP address of the bundle

Static routing information: next hop IP address and the PSN port (one
of the GbE module ports) through which the bundle will be sent.
Layer 4 parameters: the source and the destination circuit bundle

identifier (CBID) for UDP/IP, or the inbound and outbound MPLS labels for
MPLS/ETH.
Configuring an inbound label for each bundle is mandatory. When no outbound

label is configured, the inbound label is also used as the outbound label.
Quality of service parameters:
Gmux-2000 Ver. 3.2
Layer 2: VLAN priority labeling according to IEEE 802.1p

Layer 3: user-configurable ToS (Type of Service) for the outgoing IP
packets. For MPLS/ETH networks, you can also specify the EXP bits in
the MPLS overhead, which determine the requested quality of service
in the MPLS network.
2-27
TDMoIP CV (Compressed Voice) Bundle Parameters

The user can configure, for each TDMoIP CV bundle, the following specific types
of parameters:
The parameters needed by the voice compression processor to determine the

bundle structure and its handling, for example:
The packet structure and specific header format (regular or

RAD-proprietary): TDMoIP or TDMoIP+ for UDP/IP PSN, and AAL2oMPLS or
AAL2oMPLS+ for MPLS/ETH.
The maximum frame size and maximum packetizing interval.
The transported payload: selected timeslots versus all the timeslots, and
timeslots to be transparently transferred by the bundle, in addition to the
voice traffic.
Routing parameters:
Note
Layer 2 parameters: VLAN tagging according to IEEE 802.1Q.
The same VLAN ID must be used for all the bundles addressed to a given IP
address.
Layer 3 parameters:
Static routing information: next hop IP address and the PSN port (one
of the GbE ports) or the voice compression module port and subchannel through which the bundle will be sent.
Layer 4 parameters: the source and the destination circuit bundle

identifiers (CBID) for UDP/IP, or the inbound and outbound MPLS labels
for MPLS/ETH.
Quality of service parameters:
Layer 2: VLAN priority labeling according to IEEE 802.1p.

Layer 3: user-configurable ToS (Type of Service) for the outgoing IP
packets.
For MPLS/ETH networks: the EXP bits in the MPLS overhead, which
determine the requested quality of service in the MPLS network.
Connectivity checking packet rate and time-out parameters
Voice processing parameters:
2-28
Destination IP address of the bundle.
Coder type and rate
Caller ID parameters (optional)
Nominal audio input and output levels
Fax and modem signal processing parameters:
Fax and modem operation modes
Voiceband signal coding method and rate
Supported fax rates
Gmux-2000 Ver. 3.2
Maximum accepted number of modem calls
Time required to detect a 1100 or 2200 Hz tone before switching to fax

or modem mode
Multifrequency signaling mode and processing parameters
Custom tone detection parameters
Use of super-tandem mode
Use of echo cancelling
Bundle voice coding parameters
Voice activity detection parameters
Jitter buffer size for transparent timeslots.
2.4
Redundancy (APS) Functions
Gmux-2000 provides protection for the following subsystems:
SDH network interface subsystem
PSN interface subsystem
User interface subsystem (pseudowire emulation modules, and voice

compression modules).
The following sections present the redundancy options for each type of
connections.
Redundancy for SDH Network Interfaces

Gmux-2000 supports 1+1 unidirectional (line) protection with APS per ITU-T
Rec. G.783 for the links to the SDH network.
Overview of SDH Network Interface Capabilities

Redundancy can be used when installing additional ports with bandwidth
exceeding that required for carrying the maximum traffic.
The Gmux-2000 payload reaches the SDH interface module (STM1) via telecom
buses, where each telecom bus has a capacity of one STM-1 stream, and its
payload can be independently mapped. The current Gmux-2000 version supports
two telecom buses, designated A and B. Only one STM-1 port can be connected
to each telecom bus, in accordance with the following fixed assignment:
Port 1 of an SDH interface module (irrespective of the I/O slot, 7 or 9, in

which the module is installed) is always connected to telecom bus A
Port 2 of an SDH interface module is always connected to telecom bus B.
Considering the number of telecom buses, the maximum number of STM-1 ports
that can be active at any time in the Gmux-2000 chassis is two (one on each
telecom bus). This provides the following options:
Gmux-2000 Ver. 3.2
2-29
When one STM1 module is installed in the chassis, each port configured as
connected provides a bandwidth of one STM-1. Therefore, when both ports
are connected, the module provides a bandwidth of two STM-1 without
redundancy. When the required bandwidth is only one STM-1, redundancy
can be enabled when both ports can be connected to the SDH network via
independent links.
When two STM1 modules are installed in the chassis, redundancy must be
enabled, because the total bandwidth cannot exceed two STM-1.
Redundancy is activated by configuring APS groups using 1+1 unidirectional

protection. Considering the options described above, the supported APS
configurations are as follows:
When one STM1 module is installed in the chassis: one APS group including
the two ports of the STM1 module
When two STM1 modules are installed in the chassis: two APS groups, one for
each pair of similarly named ports. Therefore, one APS group includes the
LINK 1 ports of the STM1 modules, and the other APS group includes the
LINK 2 ports.
Note that when redundancy is used, only one mapping is required for each
telecom bus, because the ports connected to that bus must have identical
configurations for line redundancy to work. The mapping can be configured only
on the primary port of an APS group (actually, the secondary port cannot be
included in an APS group before its mapping is deleted).
Link capacity, mapping, and redundancy options are summarized in Table 2-2.
Table 2-2. Summary of Mapping, Link Capacity, and Redundancy Options for SDH Interfaces
Number
of STM1
Modules
1
1
Telecom Buses Served by Module Telecom Buses Served by Module

Link Capacity and
in Slot I/O 7
in Slot I/O 9
Redundancy Options
Port 1
Port 2
Port 1
Port 2
Telecom Bus A
Telecom Bus B
Telecom Bus A
Telecom Bus B
Telecom Bus A
Telecom Bus A
2 STM-1, no redundancy
Telecom Bus B
1 STM-1 with redundancy

(one APS group)
Telecom Bus B
2 STM-1, with redundancy

(two APS groups: one for
ports 1, one for ports 2)
Operation of 1+1 Unidirectional Protection Function

Figure 2-8 illustrates the operation of the 1+1 unidirectional protection function
on a Gmux-2000 using a single STM1 module.
1+1 unidirectional protection works as follows:
2-30
Both the working and protection ports of an APS group simultaneously

transmit the same data toward the remote end, via two different paths.
At each side, the signal received by each port of an APS group is evaluated in
accordance with the alarm weighting criteria specified in ITU-T Rec. G.707, to
Gmux-2000 Ver. 3.2
determine the best signal (the signal with the lowest total alarm weight). The
results of this evaluation are used to select the receive signal actually
connected to the corresponding telecom bus (these tasks are performed by a
processing function identified as an internal protection switch).
Figure 2-8.A shows the normal operating conditions, under which the signal
received through the working port is selected for processing.
When a fault occurs, protection switching takes place.

For example, Figure 2-8.B shows the change in case the working signal path
ending at the LINK 1 port of the West Gmux-2000 fails: the received signal is
now taken from LINK 2. Note that the same action would be taken in
response to any problem along this path (fault at location A, fault at location
B, transmit failure at the East LINK 1 port, or receive failure at the West
LINK 1 port).
The basic 1+1 unidirectional protection configuration shown in Figure 2-8

protects against failures on the transmission path through the SDH network, but
the protection against failures on the STM1 module is very limited (only failures in
the link interface are corrected). To enhance the protection to cover the whole
module, the configuration can be extended to a dual-link configuration, by
installing two STM1 modules at each side. In this case, protection switching
replaces a port on the working module with the corresponding port on the
protection module (in the example given above, a fault in the path ending at LINK
1 of one STM1 module would switch the traffic to LINK 1 of the second STM1
module). In the same way, a hardware failure in one STM1, or a break in the
optical cable connecting to an STM1, would switch the traffic to the other
module.
With 1+1 unidirectional protection, each side independently selects the best
signal (in Figure 2-8.B, no change occurred at the East Gmux-2000), and
therefore no protocol is needed to coordinate protection switching with the
remote side. For example, in Figure 2-8.B, the East side would also switch to the
protection port (LINK 2) if the West side problem is a break in both fibers
connected to the West LINK 1 port.
The alarm criteria taken into consideration for protection switching are as follows
(listed in decreasing weight order):
The module with the other port in the APS group is not installed.
Forced-flip command.
Critical alarm. A critical alarm is caused by the detection of one or more of

the following fault conditions: loss of SDH line signal, reception of AIS signal
on the line, loss of SDH frame, or clock failure.
Major alarm. A major alarm is caused by EED (excessive error degradation).

The EED threshold can be selected by the user.
Minor alarm. A minor alarm is caused by an SD (signal degraded) condition,

where the threshold can be selected by the user. However, the user can
configure APS parameters to ignore the SD criterion.
Revert request (only when the revertive recovery mode is selected).
The working port always carries the traffic, as long as its total alarm weight does
not exceed that of the protection. The user can however force switching (flipping)
Gmux-2000 Ver. 3.2
2-31
to the other port by a manual flip command: such command is always executed,
except when the other port in the APS group by a manual command, except when
it is located on a module not installed in the chassis.
Internal
Protection
Switch
Internal
Protection
Switch
Gmux-2000
Gmux-2000
SDH
Network
LINK 1
LINK 1
LINK 2
LINK 2
STM1
Module
STM1
Module
Legend
Working link
Protection link
A. Normal Operation
Internal
Protection
Switch
Internal
Protection
Switch
Gmux-2000
Gmux-2000
A
LINK 1
LINK 2
STM1
Module
SDH
Network
LINK 1
LINK 2
STM1
Module
Legend
Working link
Protection link
B. Operation after Protection Switching due to Fault in Path to one Port

Figure 2-8. Operation of 1+1 Unidirectional Protection Function
The two ports in an APS group can be assigned priorities: Gmux-2000 will generate
alarm messages to notify managers (supervision terminal, Telnet hosts,
management stations, etc.) that protection switching from the high priority port to
the low priority port, or vice versa, occurred.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
2-32
Gmux-2000 Ver. 3.2
Non-revertive mode the STM1 module will not automatically flip back after
the failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
However, as explained above, the user can always initiate flipping back by a
manual flip command.
Revertive mode the STM1 module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
To prevent switching under marginal conditions, the user can specify a

restoration time, which is the minimum interval before flipping back to the
original port. During the restoration time, alarms are ignored. As a result, the
module starts evaluating the criteria for protection switching (flipping) only after
the restoration time expires, thereby ensuring that another flip cannot occur
before the specified time expires.
Redundancy for PSN Interface

The maximum total bandwidth of the Gmux-2000 connections to the PSN is 2
Gbps (2 GbE links). In most applications, this bandwidth exceeds the bandwidth
needed for the traffic that can be generated by the chassis, and therefore
redundancy can be used to increase availability.
Overview of PSN Interface Redundancy Modes

When a single PSN interface (GbE) module is installed in the Gmux-2000, the two
external ports of a PSN interface (GbE) module can be configured to operate
either independently, as two separate PSN interfaces, or used as a single PSN
interface with line redundancy, using one of the following modes:
Link aggregation mode in accordance with IEEE 802.3ad (without LACP). This
mode inherently provides redundancy: if one of the GbE ports fails, the other
can continue transferring traffic, albeit at half the bandwidth available when
both ports are up. Link aggregation always provides revertive recovery,
because that as soon as the down port returns to normal, the full bandwidth
is again available.
1:1 bidirectional port protection (redundancy) mode with APS. In this mode,
at any time only one of the ports is actively carrying traffic. With 1:1
bidirectional redundancy, the recovery mode (revertive or non-revertive), and
the restoration time in the revertive mode, can be selected in accordance
with the application requirements.
Both link aggregation and redundancy are configured by defining an APS

(Automatic Protection Switching) group on the GbE ports. When two PSN
interface modules are installed in the Gmux-2000, the redundancy protection can
be extended to include module hardware, using 1:1 bidirectional module
protection (redundancy) with APS.
Note
Gmux-2000 Ver. 3.2
Redundancy partners use a common IP address, which can be configured only on

the primary port.
2-33
In most operating conditions, redundancy switching (flipping) is caused by the

detection of loss of GbE signal at a module port. However, Gmux-2000 modules
supports a wider range of flipping criteria, which are evaluated in accordance with
the following criteria, arranged below in decreasing order of severity before a flip
decision is taken:
1. GbE module removed from chassis.
2. GbE module or port hardware failure.
3. Users flip command (a diagnostic function for APS groups).
4. Priority flip. GbE ports included in an APS group can be assigned two
protection priority levels, low and high: in the event that the faults at two
ports have the same total fault weight, the high priority module will be used.
The same is true for GbE module redundancy.
5. Loss of GbE port signal.
Using Link Aggregation

The two ports of a PSN interface module (GbE module) can be operated as a
single interface, using link aggregation in accordance with IEEE 802.3ad without
LACP (Link Aggregation Control Protocol).
With link aggregation, the two GbE ports serve as a single logical interface with
twice the bandwidth of one port. The two ports must connect to the same
switch/router, as shown in Figure 2-9.
Gmux-2000
Gmux-2000
GE1
GE1
GE2
GE2
GbE
Module
GbE
Module
Figure 2-9. Link Aggregation Application

The aggregated interface is assigned a single MAC address, and a single IP
address. The rule used to distribute the Ethernet traffic between the two ports is
based on the internal MAC addresses of the I/O modules: frames from modules
with odd MAC addresses pass through one port, and the frames from modules
with even MAC addresses pass through the other port. The switch/router directly
connected to the GbE module ports must be configured for the same distribution
method.
Using link aggregation inherently provides redundancy, because that if one of the
GbE ports fails, the other can continue transferring traffic, albeit at half the
bandwidth available when both ports are up. Therefore, link aggregation per IEEE
802.3ad has inherent APS (Automatic Protection Switching) characteristics.
Failure of one the links is detected by sensing the loss of valid signals at a port,
in which case the whole traffic is sent through the remaining port.
2-34
Gmux-2000 Ver. 3.2
Link aggregation always provides revertive recovery, because that as soon as the
down port returns to normal, the full bandwidth is again available.
Note
Although under link aggregation the two module ports have identical properties,
it is necessary to arbitrarily select one port (the first port configured as part of
link aggregation) as the primary port: all the bundles using this GbE module as
their network port must point to the primary port.
The equipment connected to the GbE ports must use compatible switching
criteria for redundancy to be available:
For networks using Layer 2 switching: the criterion is signal loss
For networks using Layer 3 routing: the router must support IEEE 802.3ad or
other link aggregation protocol that views the aggregated link as a single
logical interface.
Using 1:1 Bidirectional APS for Port Redundancy

As an alternative to link aggregation, the two ports of the same GbE module can
be configured for 1:1 bidirectional APS. With this mode, two topologies can be
used:
Connection of both GbE module ports to the same switch/router, as shown in

Figure 2-9.
Connection of the GbE module ports to different switch/routers, as shown in

Figure 2-10. The main advantage of this topology is its higher availability,
because each port can be routed along a different path through the network.
Gmux-2000
Gmux-2000
GE1
GE1
GE2
GE2
GbE
Module
GbE
Module
Legend
On-line link
Off-line link
Figure 2-10. 1:1 Bidirectional APS Application (Dual Homing)

With the 1:1 bidirectional APS port redundancy mode, at any time only one of the
ports is actively carrying traffic, and the other port serves as the backup port.
The protection switching (flipping) time depends on the number of bundles per IP
address; typically, the switching times are 15 to 60 seconds.
with the application requirements:
Gmux-2000 Ver. 3.2
2-35
Non-revertive mode the GbE module will not automatically flip back after
the failed port returns to normal operation, but only when the currently used
port fails, or after a manual flip command.
Revertive mode the GbE module will flip back to the original port when it
returns to normal operation. Flipping back can be delayed by specifying a
restoration time, during which alarms are ignored. As a result, the module
starts evaluating the criteria for protection switching (flipping) only after the
restoration time expires, thereby ensuring that another flip cannot occur
before the specified time expires.
As for link aggregation, with port redundancy using 1:1 bidirectional APS the
aggregated interface is also assigned a single MAC address, and a single IP
address.
For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface (in the
topology of Figure 2-10, this will be an interface of a different router). After
learning again the MAC interface, connectivity is automatically restored.
For networks using Layer 3 routing: the router must support some form of
redundancy, and the network must be able to accept the same IP subnet
from different interfaces.
Module Redundancy Using 1:1 Bidirectional APS

Figure 2-11 shows an application using 1:1 bidirectional APS to provide module
redundancy.
When module redundancy is configured, it actually defines two APS groups: one
including port 1 of each GbE module, and the other including port 2 of each GbE
module. Each group is connected to the far end through a different path (shown
in Figure 1-5 as two different networks). The two ports in each APS group use
identical IP addresses, and the two GbE modules use the same MAC address.
Module redundancy is based on the port redundancy protection mode described
above, but extends protection to include:
2-36
Hardware redundancy: at any time, one GbE module is on-line, and the other
is off-line. Therefore, service is available even when one GbE module fails
Enhanced path redundancy: each pair of ports can connect to a different

network (in any case, the IP addresses of the two networks must be in
different subnets).
Gmux-2000 Ver. 3.2
Network 1
Gmux-2000
Gmux-2000
GE1
GE2
PW
PW
Packet Buses
Off-Line GbE
On-Line GbE
Off-Line GbE
On-Line GbE
Network 2
Legend
On-line link
Off-line link
Figure 2-11. Module Redundancy Application Using 1:1 Bidirectional APS

With 1:1 bidirectional APS module redundancy, at any time only one of the
modules (the on-line module) is actively carrying traffic, whereas the transmit
and receive ports of the off-line module are disabled (however, the link indicators
of the off-line ports still display the true state of the link connected to them).
The corresponding internal ports are also in the link down state.
The on-line GbE module carries all the traffic, and maintains the ARP table; the
off-line module is continuously updated by the on-line module. However, both
modules check the existence of the other module, to detect module removal or
hardware failure (including failure of a single port).
with the application requirements (revertive or non-revertive, as described
above).
For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface. After
learning again the MAC interface, connectivity is automatically restored.
For networks using Layer 3 routing: the router must support some form of
redundancy, and the network must be able to accept the same IP subnet
from different interfaces.
1:N Protection Mode

Gmux-2000 supports 1:N protection (an APS function) for I/O modules installed in
the chassis. The 1:N protection function is managed by the Gmux-2000 control
subsystem, and operates independently of the other Gmux-2000 APS capabilities.
Gmux-2000 Ver. 3.2
2-37
The current Gmux-2000 version supports 1:N protection only for pseudowire
emulation server modules and for voice compression modules (VC-E1/12, VCE1/16, VC-T1/12, VC-T1/16) operating in the internal port (US_NS) mode, and only
one 1:N protection group can be configured in the chassis.
An 1:N protection group is formed by adding a spare (standby, or protection)
module to a group of N modules that carry the traffic (the protected modules).
All the 1:N modules must be of the same type.
1:N protection operates as follows:
When all of the N traffic-carrying (protected) I/O modules operate normally,

the protection module is idle.
When any one of the N traffic carrying modules reports a malfunction, the
malfunctioning module is automatically replaced by the protection module,
thereby restoring the original traffic capacity.
The process used to replace a protected module by the protection module is
as follows:
The Gmux-2000 control subsystem automatically downloads the

configuration of the malfunctioning module to the protection module.
Therefore, no configuration data should be prepared by the user for the
protection module.
The Gmux-2000 control subsystem updates the internal traffic flow

configuration within the chassis:
At the telecom buses side: the malfunctioning module is disconnected

from the telecom buses, and the protection module is connected in
accordance with the downloaded configuration. Therefore, no change
in SDH link mapping takes place
At the packet buses side: the Fast Ethernet buses of the
malfunctioning module are disconnected from the GbE module(s), and
those of the protection module are connected in accordance with the
downloaded configuration. Therefore, only the internal packet routing
is affected: no change is visible from the outside
The whole process may require up to 30 seconds, after which service is

completely restored.
To provide differential quality of service, it is possible to define two protection
priority levels, low and high: in the event that protection is required for two
modules at the same time, only the high priority module will be protected.
The need for protection switching (flipping) is evaluated in accordance with the
following criteria, arranged below in decreasing order of severity:
1. Module removed from chassis.
2. Hardware failure.
3. Users flip command (a diagnostic function for APS groups).
4. Priority flip.
5. Link failure.
2-38
Gmux-2000 Ver. 3.2
Therefore, when more than one module need protection at the same time, the
protection will be activated only for the module with the more severe criteria,
while still observing the user-defined protection priorities. Therefore, separate
severity evaluations are made for each protection priority, to select the protected
module with the highest severity score, yet a low priority module will get
protected only when no protection is needed by a high priority module.
After the protected malfunctioning module is replaced, and is again ready for
service, there are two possibilities:
If the user selected the revertive recovery mode, when the replaced
protected module returns to normal operation after a protection flip, the
reverse process automatically takes place.
Therefore, the protected module is returned to service, and the protection
module is again idle and ready to protect any other malfunctioning module in
the group. To ensure a minimum interval before flipping back, the user can
specify the time to wait before restore.
If the user selected the non-revertive recovery mode, after a protection flip
the protection module continues carrying the traffic even if the protected
module replaced by it returns to normal operation.
The protection module will stop carrying the traffic only shen a manual forceflip command is received. This returns the protected module to service, and
the protection module is again idle and ready to protect any other
malfunctioning module in the group
Note that irrespective of the selected recovery mode, when a malfunction occurs
in a module with a higher priority, the protection module is switched to protect
the other module, even if the originally replaced module has not yet returned to
normal service.
2.5
Timing Subsystem
Gmux-2000 timing subsystem consists of up to three independent but

interconnected sections, identified in Figure 2-12:
PDH timing section: generates the transmit timing signals needed by the PDH
(E1) ports of each I/O module installed in the chassis. Actually, each I/O
module with PDH ports has its own timing subsystem.
SDH timing section: generates the transmit timing signals needed by the SDH
(STM-1) ports of each SDH interface module installed in the chassis.
System timing section: generates a common system-wide (nodal) timing

reference that can be used by all the modules installed in the chassis. This
nodal timing signal can be locked to a variety of sources, including external
(station) clocks.
Redundancy is used to ensure reliable timing. Therefore, each subsystem can

provide two timing references, one configured as the master (higher priority) and
the other as the fallback (lower priority) reference.
Gmux-2000 Ver. 3.2
Timing Subsystem
2-39
PDH Timing
Transmit Clocks
to SDH Ports
E1 Ports
Timing Generator
(PDH Subsystem)
SDH Subsystem
Timing Generator
Master
Fallback
Master
Adaptive Receive
Clocks from
Bundles
Transmit
Clocks to
E1 Ports
Receive (LBT)
Clocks from
SDH Ports
Fallback
Receive (LBT)
Clocks from
E1 Ports
SDH Timing
System Timing
System B
Master
Fallback
STATION
System A (Nodal)
Timing Generator
Input
Output
System
Clock
Internal Clock
Figure 2-12. Gmux-2000 Timing Subsystems

The implementation of the Gmux-2000 timing subsystem is shown in Figure 2-13.
This figure shows the functional block diagram of the Gmux-2000 timing
subsystem, located on the CLOCK card (part of the CONTROL module).
Receive Clocks
from I/O Modules
Receive Clocks
from SDH Timing
Master
Fallback
Fallback
Internal
Clock
STATION
Input
Output
Frame Sync
Master
Reference
Clock
Selector
Master
Fallback
Nodal
Clock
Generator
Transmit
Frame Sync
E1 Transmit
E1 Clock
(2.048 MHz) Clock
(Nodal Clock
Supplied to
all E1 Cards)
Station
Clock
Interface
Figure 2-13. Gmux-2000 Timing Subsystem, Functional Block Diagram
Output Timing Signals

The purpose of the timing subsystem is to generate stable timing signals needed
by the various Gmux-2000 subsystems, all locked to one of the reference signals
selected by the user.
The timing signals generated by the subsystem are as follows:
2-40
Nodal clock. The nodal clock is the source from which all the timing signals
needed by the Gmux-2000 circuits are derived. Its nominal frequency is
normally 2.048 MHz, however the user can also select 1.544 Mbps.
Timing Subsystem
Gmux-2000 Ver. 3.2
E1 transmit clock. This signal has a frequency of 2.048 MHz and is made
available to the transmit paths of the E1 ports (when the E1 ports are
configured to use the system clock as their timing reference).
Transmit frame sync signal. This signal has a frequency of 8 kHz and is made
available to the transmit paths of the E1 and SDH ports.
Timing Reference Sources

Internal Reference Signals
The Gmux-2000 timing subsystem can use as reference the following types of
internal signals, all derived from the receive paths of the various I/O modules
installed in the chassis (see descriptions in the installation and operation manuals
of the relevant interface modules):
2.048 MHz clock signal from a selected E1 port. The source of this signal may
be selected from the following options:
Clock signal recovered from an external E1 line signal of a pseudowire

emulation module or voice compression module
Clock signal recovered from an internal E1 port of a pseudowire emulation

server module
Clock signal recovered from a selected bundle by the adaptive timing

recovery mechanism of a packet processor on a pseudowire emulation
module
Timing reference signal from a selected SDH port.
The various reference signals are received via the Gmux-2000 timing bus. Each
type of signal is received on two different lines, one designated as master source
and the other as fallback.
To ensure that a Gmux-2000 always has the best possible timing accuracy at all
times, when all the configured sources (master and fallback) fail the timing
subsystem enters the holdover mode. In the holdover mode, the timing
subsystem maintains the internal reference frequency at the last value acquired
before the failure. This situation persists until at least one of the configured
reference source returns to normal, and thus is selected again.
Control signals from the CONTROL module ensure that at any time only one
module applies a signal on each timing bus line.
External Reference Signals

The Gmux-2000 timing subsystem can also use as reference a 2.048 Mbps or
2.048 MHz signal received from an external (station) source (1.544 MHz or
1.544 Mbps sources can also be used).
Internal Oscillator
The free-running internal Gmux-2000 oscillator can also be used as reference
source.
Gmux-2000 Ver. 3.2
Timing Subsystem
2-41
Note
When the Gmux-2000 is turned on and no other reference sources are yet
configured (factory defaults), or none of the configured sources is available, the
internal source is automatically selected.
Considering the accuracy of the internal source, it is recommended to use it only
when no other reference sources are available, for example, during maintenance
activities on a Gmux-2000 unit, and also in stand-alone networks that are not
connected to a backbone (connecting a Gmux-2000 to a backbone would enable
using the network timing as nodal timing reference).
In a stand-alone network, one Gmux-2000 unit, selected as the timing master of
the network, uses its internal oscillator as master source, and all the other
equipment units lock their timing to that Gmux-2000.
External Clock Interface

The external clock interface has two functions:
Input for external (station) clock signal
Output for the Gmux-2000 nodal clock. This output provides a convenient
means for distributing the Gmux-2000 nodal clock signal to other equipment.
The interface characteristics are selected by the user:
Nominal clock frequency: 2.048 MHz or 2.048 Mbps (however, a 1.544 MHz
or 1.544 Mbps source can also be used)
Signal characteristics: AMI signal at ITU-T Rec. G.703 levels, or squarewave at

RS-485 levels.
The interface has two sets of connectors:
RJ-45 connector, is always used when the interface uses RS-485 levels. This
connector is also used when the ITU-T Rec. G.703 balanced (120) interface
is selected.
Two BNC connectors, one serving an input and the other as output when the
ITU-T Rec. G.703 unbalanced (75) interface is selected.
The selection between the balanced and unbalanced ITU-T Rec. G.703 interfaces
is made by jumpers located on the CLOCK card.
Timing Subsystem Redundancy

When the Gmux-2000 is equipped with two CONTROL modules, two timing
subsystems are actually available in the Gmux-2000, one on each CONTROL
module.
In this case, only one timing subsystem is active: that located on the CONTROL
module serving as primary. The other timing subsystem, located on the slave
CONTROL module, serves as a hot standby and is synchronized to the primary
timing subsystem but does not supply any signals to the other Gmux-2000
circuits.
When the slave CONTROL module becomes master, its timing subsystem also
becomes primary.
2-42
Timing Subsystem
Gmux-2000 Ver. 3.2
Note however that CONTROL module flipping can occur as a result of one of
several causes:
Management command
Automatic switching in case a malfunction has been detected in the primary

CONTROL module
Automatic switching in case a malfunction has been detected in the timing

subsystem of the primary CLOCK card
Removal of the primary CONTROL module. This is the only cause that may
disrupt the supply of stable timing signals, as it takes a few tens of
milliseconds for the other timing subsystem to detect the event. Therefore,
before the primary CONTROL module is removed from its slot, it is highly
recommended to first force flipping to the slave module by management
commands.
When using redundant CONTROL modules, only one of the two station clock
interfaces must be connected to a station clock source. However, for best
protection, it is recommended to connect the two station clock interfaces to two
separate station clock sources.
When only one station clock source is available, you can have better hardware
protection by connecting the station clock inputs in parallel, by means of a simple
Y-cable. In this case, configure the CONTROL module to use a Y-cable: this
configuration ensures that at any time only one station clock interface (that of
the active module) is active.
The same arrangements are also effective with respect to the nodal clock
outputs.
Gmux-2000 Ver. 3.2
Timing Subsystem
2-43
2.6
Management Subsystem
Functional Block Diagram

Figure 2-14 shows the functional block diagram of the Gmux-2000 management
subsystem, located on the CONTROL module. The alarm interfacing circuits are
located on the ALARM card (part of the chassis).
Control
Buses to
All Cards
To
CLOCK
Card
To
Alarm
Card
CONTROL Card
Serial Port
Interface
CONTROL
DCE
Ethernet
Interface
CONTROL
ETH
Figure 2-14. Management Subsystem Functional Block Diagram
CONTROL Module Management Subsystem

The main functions of the management subsystem located on the CONTROL
module are as follows:
2-44
Interfacing with external management and monitoring functions. The

following options are available:
Supervision terminal: ASCII terminal or a PC running a terminal emulation

program, connected either directly to the Gmux-2000, or through a
modem or any other type of full-duplex data link. This terminal can
perform all the Gmux-2000 supervision and configuration functions, and
in particular the preliminary system configuration.
Telnet: by means of any host capable of IP communication with Gmux2000. The functions available under the Telnet protocol are similar to
those available from a supervisory terminal.
SSH: secure access using the SSH (Secure Shell) protocol, using any
standard SSH client utility running on a PC or laptop capable of IP
communication with Gmux-2000.
SNMP: the Gmux-2000 includes an internal SNMP agent that enables full
SNMP management by SNMP-based network management, for example,
the RADview family of management stations for element and network
management available from RAD, which are supplemented by dedicated
RADview-SC/TDMoIP and RADview-SC/Vmux Service Centers, which enable
efficient and effective management of TDMoIP and voice compression
services.
Gmux-2000 Ver. 3.2
syslog: Gmux-2000 supports automatic event notification to

user-specified syslog servers in accordance with the syslog protocol per
RFC3164. Gmux-2000 can report all the supported traps and alarms, but
also enables configuring the minimal severity level for reporting to each
syslog server.
To protect network operations against unauthorized access, Gmux-2000

supports a wide range of security features for every management facility:
RADIUS authentication for supervision terminal and Telnet access, SSH for
secure Telnet access, and SNMP management with authentication and privacy
per SNMPv3 using selectable security models, with support for SNMPv1 and
SNMPv2.
Control of Gmux-2000 system operation.
Storage of application software, which determines the capabilities and

features provided by the Gmux-2000. This software can be remotely
downloaded and updated through the management link without taking the
equipment off-line. The stored software includes both system software, run
by the CONTROL module, and software for the other modules installed in the
chassis.
Storage of configuration databases. The configuration databases can also be

uploaded and downloaded through the management link.
Collection of operational history (alarms, performance statistics, etc.), and of

internal chassis temperature, as read by an internal temperature sensor. The
collected information can be read by maintenance personnel through the
management link.
A real-time clock provides time stamps for all the collected information. The
real-time clock can be set either manually or automatically, using the NTP
(Network Time Protocol). A network operator can use NTP to periodically
synchronize the local equipment time within the managed network to the
accurate time provided by the worldwide network of NTP time servers, and
thus is able to reliably correlate alarm reports from different sources. To use
NTP, it is necessary to configure the IP address of the desired NTP server, and
select a time zone.
The performance statistics collected for the modules installed in the chassis
are also synchronized to the real-time clock.
The application software, as well as the configuration databases, are stored on a

flash disk. The Gmux-2000 software includes file utilities that enable access to
the flash disk file system: this provides powerful and efficient management
capabilities, as it allows copying, deleting, and renaming the files located on the
flash disk.
Ethernet Connections to CONTROL Modules

The CONTROL module has an internal Layer 2 Ethernet switch that serves
management communications. This switch has the following access ports:
Gmux-2000 Ver. 3.2
Two Fast Ethernet ports that connect through the management bus to the
GbE module. These ports provide management access to the Gmux-2000
management subsystem from the packet-switched network side.
2-45
An internal port for the local management subsystem.
External 10BASE-T/100BASE-TX Ethernet interface terminated in the

CONTROL ETH RJ-45 connector. 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).
A separate set of control buses carries the internal management traffic to the I/O
modules installed in the chassis.
Caution The Gmux-2000 internal management traffic uses VLANs for identification and
internal routing. The VLAN IDs used for internal management traffic are 101 and
102. Therefore, the VLAN IDs 101 and 102 must be reserved, and must not be
allocated to traffic reaching Gmux-2000 ports, as this may lead to unpredictable
results.
Serial Port Connections

The supervisory port of the Gmux-2000 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.
CONTROL Module Redundancy

When a second CONTROL module is installed, the two modules operate as a
master/slave pair; one module is the active (master) module, and the other
serves as a hot standby (slave).
Only the master module communicates with the management station/terminal
and actively manages the Gmux-2000 system. The slave module is automatically
updated by the master module with all the configuration and status data, and
therefore the slave can take over at any time without disrupting system
operation. The slave module communicates only with the master module.
Moreover, the transmit line in the slave serial port connectors is disabled, to
enable physical connection in parallel (e.g., by means of a Y cable) to the
supervision terminal or to a modem.
External Alarm Interfaces

The Gmux-2000 chassis includes a connector for reporting chassis alarms to
external equipment (buzzers, dialers, etc.) by means of dry-contacts, for
example, you can activate a bay alarm, dial out to report the alarm, etc.
The connector also has an external alarm input for monitoring external sensors:
when the alarm input is in its active state, Gmux-2000 generates an alarm with a
configurable text string.
2-46
Gmux-2000 Ver. 3.2
Dry-Contact Alarm Interface

The alarm port is terminated in a 9-pin D-type female connector located on the
Gmux-2000 rear panel, designated ALARMS.
This port includes floating change-over dry-contact outputs for the major and
minor alarm relays. The alarm relay contacts are rated at maximum 60 VDC or
30 VAC across open contacts, and maximum 1 ADC through closed contacts (total
load switching capacity of 60W).
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.
External Sense Input

The external sense input in the ALARMS connector is referenced to pin 3 of the
connector, and uses an auxiliary voltage output (derived from the +12V internal
supply voltage through a 340 series resistor and a protection diode).
A dry-contact relay must be connected between this auxiliary output and the
reference pin.
2.7
The Gmux-2000 power supply subsystem comprises up to three power supply

(PS) modules connected to the power sources via a separate power input (PI)
module.
The Gmux-2000 can use either 115/230 VAC, 50/60 Hz or 24/48 VDC power
sources. The PI and PS modules must match the selected power source:
The AC power inlet (PI/AC) module has three separate inputs, one for each PS
module: this enables connecting each PS module to an independent power
circuit.
The DC power inlet (PI/DC) module has two separate inputs, each distributed
to all the PS modules. This provides redundancy for the DC input power
source.
Two PS modules are sufficient to power a fully-equipped chassis. However, it is

recommended to install the third PS module as well, for 2+1 redundancy:
With a redundant PS module, all the three modules are connected to power,
and when operating normally share the load.
In case any one PS module fails or loses its input power, the remaining PS
modules continue to supply power to the chassis, without any service
disruption. Therefore, a malfunctioning PS module can be replaced online;
after replacement, the module starts again sharing the load. Switch-over is
thus automatic and hitless.
Redundancy is also available when the chassis requires a single PS module, and
two PS modules are installed.
Gmux-2000 Ver. 3.2
2-47
2-48
Gmux-2000 Ver. 3.2
Chapter 3
System Installation
This Chapter provides installation instructions for the Gmux-2000 systems,
including the installation of the modules that are part of the basic system
configuration.
The Chapter presents the following information:
General description of the equipment enclosure and its panels.
Mechanical and electrical installation instructions for the enclosure itself and
the fan tray, PI, PS and CONTROL 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 CONTROL modules: if the CONTROL modules are not yet loaded with the
required software, refer to Appendix B for detailed software installation
instructions.
After the preliminary configuration, the system can also be managed by means of
Telnet hosts or SNMP-based network management stations, e.g., RADview. Refer
to the User's Manual of the network management station for operating
instructions.
3.1
Safety
General Safety Precautions
Warning
Caution
Gmux-2000 Ver. 3.2
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.
Gmux-2000 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.
Safety
3-1
Chapter 3 System Installation
Caution Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the Gmux-2000 modules. To prevent physical damage:
Always keep modules in their protective packaging until installed in the
Gmux-2000 chassis, and return them to the packaging as soon as they are
removed from the enclosure.
Do not stack modules one above the other, and do not lay any objects on
PCBs.
When inserting a module into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the module PCB does not
touch the adjacent module, nor any part of the chassis. If resistance is felt
before the module fully engages the mating backplane connector, retract the
module, realign it with the slot guides and then insert again.
Grounding
Grounding
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the lines connected to the equipment, the Gmux-2000 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

Gmux-2000 and its modules.
Warning
Never connect cables to Gmux-2000 if not properly installed and grounded.

Disconnect all the cables connected to the electrical connectors of the
Gmux-2000 before disconnecting its grounding connection.
Before connecting any other cable and before applying power to this equipment,
the protective ground terminal of the equipment must be connected to protective
ground. The grounding connection is made to the grounding terminal located on
the Gmux-2000 rear panel.
Whenever Gmux-2000 units are installed in a rack, make sure that the rack is
properly grounded and connected to a reliable, low-resistance grounding system,
as the rack can also provide a connection to the ground.
In addition, the grounding connection is also made through each one of the
power cables. Therefore, the power cable plug must always be inserted in a
socket outlet provided with a protective ground.
3-2
Safety
Gmux-2000 Ver. 3.2
Laser Safety Classification

Gmux-2000 modules equipped with laser devices 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.
Gmux-2000 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.
Laser Safety Statutory Warning and Operating Precautions

All the personnel involved in equipment installation, operation, and maintenance
must be aware that the laser radiation is invisible. Therefore, the personnel must
strictly observe the applicable safety precautions and in particular must avoid
looking straight into optical connectors, neither directly nor using optical
instruments.
In addition to the general precautions described in this section, be sure to
observe the following warning when operating a product equipped with a laser
device. Failure to observe the warning could result in fire, bodily injury, and
damage to the equipment.
To reduce the risk of exposure to hazardous radiation:
Warning
Do not try to open the enclosure. There are no user-serviceable components

inside.
Do not operate controls, make adjustments, or perform procedures to the
laser device other than those specified herein.
Allow only authorized RAD service technicians to repair the unit.
Protection against ESD

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

Gmux-2000 modules include small components installed on both sides of the
printed circuit boards. These components are exposed as long as the modules are
not installed in the chassis, are therefore may be unintentionally damaged. To
prevent physical damage to modules:
1. Always keep the modules in their protective shipping containers until installed
in the chassis. These containers also protect against ESD.
2. Avoid piling up modules.
3. While inserting modules in their chassis slots, support the modules and make
sure their components do not touch the chassis structure, nor other modules
while sliding into position.
3.2
Site Requirements
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
Warning
Caution
Gmux-2000 does not have a power switch, and therefore it will start operating as
soon as power is applied to one of the power supply inlets. For proper equipment
operation, at least two power supply modules must be operative and receive
power simultaneously.
It is recommended that the external circuit breaker used to protect the input
power lines be also used as ON/OFF power switch.
Power
Gmux-2000 can be equipped with either AC or DC power supply modules.
It is not allowed to mix power supply modules operating on different supply
voltages in one chassis.
Warning
Each type is available in 200W and 300W models (see Description of PS Modules
in Section 1.3). Contact RAD Technical Support Department if it is necessary to
use both 200W and 300W PS modules in the same chassis.
3-4
Site Requirements
Gmux-2000 Ver. 3.2
AC Power
AC-powered Gmux-2000 units should be installed within 1.5m (5 feet) of
easily-accessible grounded AC outlets capable of furnishing 115 or 230 VAC,
50/60 Hz.
The connection of AC power is made through the AC power inlet module. This
module has a separate input connector for each AC power supply module
installed in the chassis. Therefore, the connection of AC power to each power
supply module installed in the chassis is made through a separate power cable:
for a Gmux-2000 equipped with the full complement of power supply modules
(three), three separate power cables are required.
Therefore, it is necessary to make appropriate arrangements for simultaneously
applying power to all the Gmux-2000 power inlets by means of a single ON/OFF
power switch. Powering AC power supply modules one at a time may cause
undesirable effects, for example, the GbE modules may be reset.
When PS redundancy is required, at least two of the three PS modules must be
able to supply power to modules installed in the chassis.
DC Power
DC-powered Gmux-2000 units require a 24 VDC or 48 VDC (nominal voltage)
power source. Three DC power supply modules can be installed in the chassis.
When PS redundancy is required, at least two of the three PS modules must be
able to supply power to modules installed in the chassis.
The connection of DC power is made through DC power inlet modules, which are
available in two models:
DC power inlet module with two DC inputs, occupies the full width of the PI
slot in the Gmux-2000 chassis
Half-width DC power inlet module with single DC input. Two half-width PI

modules can be installed in the PI slot, and together they provide two DC
inputs.
Irrespective of the DC power inlet model, each DC input voltage is distributed in

parallel to all the PS power supply modules through a protection fuse, and
therefore it is sufficient to connect power to one input for all of the DC power
supply modules to be simultaneously powered.
The second DC input enables connecting a separate DC input voltage, and thus
when power is connected to both DC input connectors, availability is increased by
having a redundant power source. The two DC inputs are isolated by diodes, and
therefore it is not possible for current to flow from one DC input to the other.
Caution The same nominal DC voltage must be supplied to both DC input connectors.
Within the Gmux-2000, the DC input supply lines are not referenced to the
chassis (frame) ground.
Gmux-2000 Ver. 3.2
Site Requirements
3-5
Caution Gmux-2000 is usually supplied with the internal digital ground (DGND) not
connected to the frame ground (FGND). However, you may order the Gmux-2000
with DGND connected to FGND. Contact your local distributor for more
information.
Payload Connections
E1 Port Connections
Gmux-2000 systems may be equipped with external E1 ports. External E1 ports
are located on E1-PW/28 pseudowire circuit emulation modules, and on VC-E1/12
and VC-E1/16 voice compression modules.
The maximum allowable line attenuation between a Gmux-2000 E1 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 interfaces of Gmux-2000 systems must not be connected
directly to unprotected public telecommunication networks. The connections
must be made through a network termination unit that provides separation
between the interface conductors and the telecommunication network
conductors in accordance with the applicable local regulations.
The E1 ports located on E1-PW/28 modules are terminated in 62-pin female

D-type connectors (each module has one pair of connectors for its 28 E1
ports). RAD offers special patch panels for installation in standard 19 in.
racks that have separate connectors for each port: standard cables can then
be used to connect the user's equipment to the patch panel connectors.
Two types of patch panels are offered:
Patch-28B: 1U-high patch panel for balanced interfaces, has 28 RJ-45

connectors, one for each port
Patch-28UB: 2U-high patch panel for unbalanced interfaces, has 28 pairs

of BNC connectors, one pair for each port.
The panels provide only transparent connections to the module E1 port lines:
they do not provide any impedance matching, and therefore it is necessary to
use the panel type corresponding to the selected E1-PW/28 port interface.
Both patch panels have two 64-pin TELCO connectors on their rear panels,
for connection via adapter cables to the E1-PW/28 connectors. RAD also
offers adapter cables, designated CBL-2DB62/2TELCO, having a length of
2 meter, for connecting the patch panel to the module.
Each panel serves one E1-PW/28 module, and requires one adapter cable.
VC-E1/12 and VC-E1/16 voice compression modules have two types of

external E1 ports:
3-6
External E1 voice ports: these ports have user-selectable balanced or

unbalanced ITU-T Rec. G.703 interfaces, terminated in one 64-pin D-type
female connector. RAD offers as optional accessories the following
dedicated adapter cables:
Site Requirements
Gmux-2000 Ver. 3.2
CBL-TELCO-RJ45/16E1, terminated in RJ-45 plugs, which is used to

connect equipment with standard RJ-45 connectors to the module
64-pin D-type connector. This cable is intended for connection to
equipment with balanced interfaces.
CBL-TELCO-OPEN/2M and CBL-TELCO-OPEN/10M. These cables are
terminated in free leads that can be connected to any terminal block,
or to any connector appropriate for your application. These cables
can be used for connection to both balanced and unbalanced
interfaces.
External E1 data ports: these ports have balanced or unbalanced ITU-T

Rec. G.703 interfaces (interface type is software-selectable). Each port
has one RJ-45 eight-pin connector, used for both the balanced and
unbalanced interface.
The connection to equipment with balanced interface is made by any
standard RJ-45-to-RJ-45 cable. For connection to equipment with
unbalanced interface, RAD offers as an optional accessory an adapter
cable, CBL-RJ45/2BNC/E1/X, with one RJ-45 plug at one end and two BNC
female connectors at the other end.
SDH Port Connections
Note
Optical Ports. SDH ports can be ordered with fixed STM-1 optical ports, or
with SFP-based ports.
Each optical fixed port has two SC optical connectors, one for the receive
input and the other for the transmit output. The optical ports can be
ordered with 850 nm short-haul interfaces for use over multimode fibers,
or with various 1310 nm interfaces, from LEDs for short haul to lasers for
long haul applications, for use over single-mode fibers.
Each SFP-based port accepts field-replaceable standard SFPs with optical

interfaces, and thus enables selecting the optimal SFP for each
application and fiber type. RAD offers a wide range of SFPs, including
high-performance SFPs that are also offered in WDM versions using a
single fiber instead of the customary two fibers, and can achieve ranges
up to 80 km/50 miles.
RAD strongly recommends ordering the Gmux-2000 modules with RAD SFPs, as
this permits full performance testing of the supplied equipment.
Electrical Ports. SDH ports can also be ordered with electrical STM-1 ports.
Each port has two 75 BNC connectors, one for the receive input and the
other for the transmit output. The electrical interface is intended for short
intra-office cable runs (typically up to 135 meter over RG-59B/U coax). This
interface must not be directly connected to unprotected public
telecommunication networks.
PSN Connections
The PSN interfaces are located on the GbE module. These modules have ports
with Gigabit Ethernet interfaces that support auto-negotiation.
Gmux-2000 Ver. 3.2
Site Requirements
3-7
The physical interfaces are located on hot-swappable SFP transceivers. RAD

offers SFPs with optical and copper GbE interfaces that meet a wide range of
operational requirements, for example, SFP-5, SFP-6, SFP-7 or SFP-8D for optical
interfaces, and SFP-9 for copper interfaces.
Optical Cable Requirements

The cables connected to Gmux-2000 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.
Station Clock Connections

The Gmux-2000 station clock ports can accept and generate 2.048 MHz or
1.544 MHz signals. Each port is terminated in one RJ-45 connector for the
balanced (100/120 ) interface, and two BNC connectors for the unbalanced
(75 ) interface.
Two types of signals can be accepted and generated: all-ones AMI-coded clock
signal, or a squarewave signal at RS-485 levels.
The station clock outputs provide a convenient means for distributing the
Gmux-2000 nodal clock signal to other equipment.
Note
When using redundant CONTROL modules, only one of the two station clock ports
must be connected to a station clock source. For best protection, it is
recommended to connect the two station ports to two separate station clock
sources.
When only one clock source is available, you can have better protection by
connecting the station clock inputs in parallel, by means of a simple Y-cable. In
this case, configure the CONTROL module to use a Y-cable: this ensures that at
any time only one station clock interface (that of the active module) is active.
Management Connections
Ethernet Connections to CONTROL Modules
The CONTROL modules have 10BASE-T/100BASE-TX Ethernet interfaces
terminated in RJ-45 connectors. 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).
Serial Port Connections

The out-of-band supervisory port of the Gmux-2000 has a serial RS-232
asynchronous DCE interface terminated in a 9-pin D-type female connector,
designated CONTROL DCE.
3-8
Site Requirements
Gmux-2000 Ver. 3.2
This port can be directly connected to terminals using a cable wired

point-to-point. A cross cable is required to use the DTE mode, for example, for
connection through modems or digital multiplexer channels.
Note
When using redundant CONTROL modules, you can connect the terminal,
respectively the modem, in parallel to the corresponding serial port connectors of
the two modules by means of a simple Y-cable, because at any time only one serial
port (that of the active module) is active.
Ethernet ports of redundant CONTROL modules do not require any special
connections: each one can be connected to a separate Ethernet hub port.
Alarm Port Connections

The alarm port is terminated in a 9-pin D-type female connector located on the
Gmux-2000 rear panel, designated ALARMS. This port includes:
Caution
Floating change-over dry-contact outputs for the major and minor alarm
relays. The alarm relay contacts are rated at maximum 60 VDC/30 VAC across
open contacts, and maximum 1 ADC through closed contacts (total load
switching capacity of 60 W).
Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
External alarm sense input. The input is intended for connection by means of
a dry-contact relay that provides open-circuit/short-circuit to an auxiliary
voltage output (derived from the +12V internal supply voltage through a
340 series resistor and a protection diode). Either the open- or
short-circuit state can be configured as the active state, that will be reported
as an alarm.
Front and Rear Panel Clearance

Gmux-2000 can be installed on shelves and in telecommunication racks. RAD
offers rack mount kits for installation in 19 inch (ANSI) racks or in ETSI racks.
Allow at least 90 cm (36 inches) of frontal clearance for operator access. Allow
the same clearance at the rear of the unit for cables and module replacement.
Ambient Requirements
The ambient operating temperature range of the Gmux-2000 is 32 to 131F
(0 to +55C), at a relative humidity of up to 90%, non-condensing. Gmux-2000
chassis has a cooling fan tray that exhausts air from the chassis. The chassis
cooling vents are located in the side covers. Do not obstruct these vents.
Gmux-2000 Ver. 3.2
Site Requirements
3-9
Caution Do not operate Gmux-2000 without the fan tray installed. Irreversible damage to
hardware will occur if the chassis is operated without the fan tray installed, even
for a few minutes (maximum allowed at room temperature is 5 minutes).
When the Gmux-2000 is installed in a rack, it is recommended to allow at least
1U of space below and above the unit.
Electromagnetic Compatibility Considerations

The Gmux-2000 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.
To meet these standards, it is necessary to perform the following actions:
Connect the Gmux-2000 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.
Covering all empty slots is also required for reasons of personal safety and for
efficient cooling of the chassis.
Warning
3.3
Package Contents
The Gmux-2000 package includes the following items:
Gmux-2000 chassis
Power cords
Hardware kit for rack installation (if ordered)
Technical documentation CD.
Modules are shipped either separately, or preinstalled in the chassis, in

accordance with your order.
3.4
Equipment Needed
The cables you need to connect to the Gmux-2000 depend on your specific
application. You can prepare the appropriate cables yourself in accordance with
the information given in Appendix A, or order cables from RAD.
For information regarding the cables needed to connect to Gmux-2000 I/O
modules, refer to the module Installation and Operation Manuals.
3-10
Equipment Needed
Gmux-2000 Ver. 3.2
3.5
Gmux-2000 Enclosure
General Description
Figure 3-1 shows a general view of the Gmux-2000 enclosure, as seen from its
front side. The front panel includes only status indicators: the various modules
and all the connectors are reached on the rear side.
Cooling vents are located on the side covers of the enclosure.
The Gmux-2000 enclosure can be ordered with brackets for installation in various
types of racks. The brackets are attached to the sides of the enclosure, near the
front or rear panel.
Figure 3-1. Gmux-2000 Enclosure, General View
Gmux-2000 Ver. 3.2
Gmux-2000 Enclosure
3-11
Front Panel
The front panel of the Gmux-2000 enclosure includes labels for the system status
indicators. Figure 3-2 identifies the status indicators, and Table 3-1 describes the
indicator functions.
Figure 3-2. Gmux-2000 Enclosure, Front Panel

Table 3-1. Gmux-2000 Status Indicators
Indicator
Description
PWR (green)
Lights when the Gmux-2000 is powered
TST (yellow)
Lights when a test (or test loopback) is active in the local or remote Gmux-2000
MAJ ALARM
(red)
Flashes when a major alarm condition is detected in the local Gmux-2000
MIN ALARM
(red)
Lights when a minor alarm condition is detected in the local Gmux-2000
3-12
Gmux-2000 Enclosure
Gmux-2000 Ver. 3.2
Rear View
Figure 3-3 shows a typical rear view of the Gmux-2000 enclosure (this figure
presents a Gmux-2000 equipped for circuit emulation applications). The rear side
includes the following main sections:
16 slots: 6 of them are slots for system modules, 9 slots (identified as I/O-1
to I/O-9), are used to install I/O modules, and the last slot is occupied by the
fan tray that provides air flow through the enclosure.
Top panel, includes the chassis grounding terminal, a group of status

indicators that replicate the status indications provided on the front panel,
and a connector for alarm outputs and inputs.
or
or
Pseudowire Emulation Module with External E1 Interfaces
or
or
Pseudowire Emulation Module with External E1 Interfaces
Power Inlet
(PI) Module
Grounding
Terminal
Slot
Map
INLET
P.S . 3
P.S . 2
P.S . 1
CT RL. 2
CRTL. 1
Gmux-2000
Rear Panel
I/O-9
I/O-8
I/O-7
I/O-6
I/O-5
I/O-4
I/O-3
I/O-2
I/O-1
ALA RM S
PW R
M AJ . ALARM
T ST
M IN . ALA RM
FAN-TRAY
Slot:
PW R
FLT
L ASER
CL ASS
1
LOC
REM
AC-IN
TX
STM1
ACT
GE 1
L ASER
CL ASS
1
POWER
POWER
GbE
TX
RX
LOC
RDY
REM
ALM
I/O-9
RX
I/O 9
LINK
GE 2
LINK
PAUSE
LINK
PAUSE
ACT
TX
RX
TX
RX
FLT
I/O-8
MONITOR
Slot for PSN

PS-AC
I/O-7
I/O 7
I/O-6

I/O-5
I/O 5
I/O-4
I/O 4
I/O-3
I/O 3
I/O-2
I/O 2
I/O-1
I/O 1
POWER
POWER
2
PS-AC
PS-AC
1
9 10 11 12 13 14 15 16
17 18 19 20 21
ACT
FLT
POWER
E1.PW.SRV / 21
POWER
1
1
10 11 12 13 14 15 16
17 18
19 20 21
ACT
FLT
PS-AC
E1.PW.SRV / 21
OUT
IN
SD
1
ACT
LINK
10 11 12 13 14 15 16 17 18 19 20 21
S TAT ION CLOCK
ACT
FLT
E1.PW.SRV / 21
ACT
CONTROL
ETH
CONTROL
FLT
DPW
OUT
IN
SD
ACT
CONTROL
LINK
S TAT ION CLOCK
ACT
ETH
CONTROL
Slots for
Servers
and/or
E1 Interfaces
FLT
DPW
Fan Tray
System Slots
I/O Slots

Figure 3-3. Gmux-2000 Enclosure, Typical Rear View
Gmux-2000 Ver. 3.2
Gmux-2000 Enclosure
3-13
3.6
Installing the Fan Tray
This section provides instructions for installing a fan tray in an empty chassis. The
same procedure may be used to replace the fan tray.
Fan Tray Description

The fan tray includes a total of 8 independently controlled fans that provide
cooling air. The rotation speed of the fans, and thus the airflow, can be varied to
adapt to the cooling requirements: for example, when the temperature inside the
enclosure is sufficiently low, the speed is decreased to reduce wear and noise.
The proper operation of the fans is monitored by the CONTROL modules.
Figure 3-4 shows a general view of the fan tray. The fan tray has two indicators:
PWR (green) lights when the fan tray receives power
FLT (red) lights when a malfunction is detected in the fan tray, for example,
a faulty fan, is detected in the tray.
Figure 3-4. Fan Tray, General View

Note
3-14
The I/O slots labels are located on the fan tray panel.
Gmux-2000 Ver. 3.2
Installation Procedure
To install the fan tray:

1. Carefully check the fan tray for foreign objects and dirt that may have been
trapped inside, and remove them.
2. Insert the fan tray in the chassis slot as shown in Figure 3-5, and slide it
backward until its rear connector engages the mating connector on the
backplane.
3. Secure the fan tray by tightening its two screws.
Figure 3-5. Installing the Fan Tray

Caution When replacing the Gmux-2000 fan tray in an operating chassis, do it quickly:
irreversible damage to hardware will occur if the chassis is operated without the
fan tray installed, even for a few minutes (maximum allowed at room
temperature is 5 minutes).
Gmux-2000 Ver. 3.2
3-15
3.7
Installing the Power Inlet (PI) Module
PI Description
The connection of power to the Gmux-2000 power supply modules is made
through a PI module. The following types of PI modules are offered (see
Figure 3-6):
Note
PI/AC for AC-powered power supply modules. The PI/AC module has 3 AC input
connectors, one for each PS-AC module that may be installed in the chassis.
Refer to the Connection of AC Mains section at the beginning of this manual for
instructions regarding the required circuit breaker.
PI/DC for DC-powered power supply modules. Two PI/DC models are currently
offered:
PI/DC full-width PI module for 48 VDC-powered power supply modules.

The PI/DC module enables connecting two DC power sources to the
Gmux-2000. Each DC power source is connected in parallel to the three
PS-DC modules that may be installed in the chassis. A PWR indicator lights
when power is present at the corresponding input.
Each source is protected by a separate fuse, located behind the
corresponding power connection terminals (see Figure 3-7). These fuses,
designated H1 and H2, are 20-A super-time-lag (TT) high-breaking
capacity ceramic fuses, type 172600 by Chess Schurter or equivalent.
PI/DC half-width PI module for 24 VDC-powered power supply modules.

The PI/DC module enables connecting one DC power sources to the
Gmux-2000; installing two PI/DC modules in the PI slot of the Gmux-2000
chassis enables connecting two DC power sources, the same as the fullwidth PI/DC module, where each power source is connected in parallel to
the three PS-DC modules that may be installed in the chassis. Each halfwidth PI can be separately removed, to enable replacing the internal fuse
without disconnecting the Gmux-2000 power.
A PWR indicator lights when power is present at the corresponding input.
+
48V
PWR
PWR
DC-IN
A. PI/DC Module for 48V DC Input Voltage

+
AC-IN
B. PI/DC Module for 24V DC Input Voltage
PI/AC Module
Figure 3-6. Typical PI Module Panels
3-16
Installing the Power Inlet (PI) Module
Gmux-2000 Ver. 3.2
Fuse H1
Fuse H2
Figure 3-7. Location of Fuses on Typical PI/DC Module

When replacing fuses, observe the following precautions:
Warning
For continued protection against risk of fire, replace only with same type and
rating of fuse.
Disconnect power before replacing a fuse.
Installing PI Modules
Caution Make sure to install PI/DC module matching the supply voltage required by the PS
modules.
For half-width PI modules, always install two modules side by side in the PI slot.
To install a PI module:
1. Insert the PI module in its chassis slot (see Figure 3-3), and slide it backward
until its rear connector engages the mating connector on the backplane.
2. Secure the PI module by tightening its two screws.
3. For half-width PI modules, repeat the process for the other module.
3.8
Installing the Gmux-2000 PS Modules
PS Module Description
The Gmux-2000 may be equipped with PS modules of the following types:
Gmux-2000 Ver. 3.2
PS-AC: operate on 115/230 VAC, 50/60 Hz; available in 200W and 300W
models
PS-DC: operates on 48 VDC; available in 200W and 300W models.
PS-DC 24: operates on 24 VDC, 300W model only.
3-17
Note
200W and 300W PS models look quite similar. To identify the module before
being installed in the chassis, look at its manufacturer label attached to the
internal shield. While Gmux-2000 operates, you can read the PS model using the
management station (for a supervision terminal, use the Inventory menu).
PS-DC modules have two indicators:
POWER lights when the module is powered
ALARM lights when a malfunction is detected in the module.
The PS-AC module has only a POWER indicator.

The chassis accepts three modules that share the load. The maximum power that
may be supplied by each module, 200W or 300W, and therefore three modules
can supply a maximum of 600W, respectively 900W.
In general, two PS modules are sufficient for powering a Gmux-2000 chassis, and
therefore, by installing three PS modules, 2:1 redundancy is achieved. In this
case, a PS module may be replaced without disrupting chassis operation (hot
hitless swapping).
POWER
ALARM
PS-DC
A. PS-DC Module for 48V DC Input Voltage
POWER
POWER
PS-AC
ALARM
PS-DC 24V
PS-AC Module
B. PS-DC 24V Module for 24V DC Input Voltage
Figure 3-8. Typical PS Module Panels
Installation Procedure
To install a PS module:
1. If necessary, disconnect the power cable connected to the corresponding PI
connector/terminal strip.
2. Check that its two fastening screws are free to move.
3. Insert the PS module in its chassis slot (see Figure 3-3) and slide it backward
as far as it goes (see Figure 3-9).
3-18
Gmux-2000 Ver. 3.2
Figure 3-9. Installing a PS Module

4. Refer to Figure 3-10 and press the extractor handle toward the center of the
module to fully insert its rear connector into the mating connector on the
backplane.
5. Secure the PS module by tightening its two screws.
1
2
Figure 3-10. Securing the PS Module to the Chassis
Gmux-2000 Ver. 3.2
3-19
Removing a PS Module
To remove a PS module:
1. If necessary, disconnect the power cable connected to the corresponding PI
connector/terminal strip.
2. Fully release the two screws fastening the module to the chassis.
3. Press the release button of the extractor (located on the side, and
4. push the extractor handle in the direction shown in Figure 3-11 to
disengage the rear connector.
5. Pull the module out.
4
2
3
1
Figure 3-11. Removing a PS Module
3-20
Gmux-2000 Ver. 3.2
3.9
Installation of CONTROL Modules
CONTROL Module Description

The Gmux-2000 chassis can be equipped with two CONTROL modules. At any
time, only one module is active, and the other serves as hot standby.
Figure 3-12 shows the front panel of the CONTROL module, and Table 3-2
explains the functions of the components located on the panel.
OUT
IN
SD
ACT
CONTROL
LINK
ETH
CONTROL
STATION CLOCK
ACT
DCE
FLT
Figure 3-12. CONTROL Module Panel

Table 3-2. CONTROL Module, Panel Components
Item
Function
ACT Indicator (green)
Lights steadily on the master (active) module.

Flashes when this module is in standby
FLT Indicator (red)
Lights in case of malfunction in this module.

When the module is in standby, this indicator is always off, even in case a problem
is present
CONTROL-DCE
Connector
9-pin D-type female connector with serial RS-232 DCE interface, for connection to a
supervision terminal or system management.
CONTROL-ETH
Connector
RJ-45 connector for the 10/100BASE-T interface, for connection to system

management through an Ethernet LAN
STATION CLOCK
Balanced Interface
Connector
RJ-45 connector for connection to the balanced station clock interface
STATION CLOCK IN
Connector
BNC connector for unbalanced connection of an external clock signal, for use as a
reference for the CONTROL module clock subsystem
STATION CLOCK OUT

Connector
BNC connector for the unbalanced output clock provided by the CONTROL module
clock subsystem
SD Indicator
Signal-detect indicator for the station clock input:

Off when the Gmux-2000 is not configured to use the station clock as a main or
fallback reference source.
Lights in green when the station clock has been configured as reference, and a good
signal is detected.
Lights in red when the station clock has been configured as reference, but no clock
signal is detected
Gmux-2000 Ver. 3.2
3-21
Preparing the CONTROL Module for Installation

The CONTROL module has two types of internal settings:
Jumpers located on the upper card (the CLOCK card), used to select the
station clock interface
Switch located on the CONTROL card. One of the sections of this switch can
be used to restore the configuration database to the factory-default values.
Figure 3-13 shows the location of the user settings located on the CONTROL
module.
OFF
Switch SW1
ON
SW1
ON
DIP1
DIP2
DIP3
DIP4
DIP5
DIP6
DIP7
DIP8
DB INIT
Section
CONTROL Card
Interface Selection - Clock Output

JP4
UBL
Unbalanced
Jumper JP2 FGND
Balanced
BAL
Pins 3,6 of RJ-45

Connector
not Connected to
Frame Ground
NO
YES
Pins 3,6 of RJ-45

Connector
Connected to
Frame Ground
CLOCK Card
Interface Selection - Clock Input

JP1
UBL
Unbalanced
Balanced
BAL
Figure 3-13. CONTROL Module, Internal Settings
Clock Interface Selection

Table 3-3 describes the jumper functions, and lists the factory (default) settings.
If the default settings meet your specific requirements, you may skip this section
and proceed with the installation of the module in the Gmux-2000 enclosure.
3-22
Gmux-2000 Ver. 3.2
In addition to these settings, the CONTROL module includes additional jumpers and
switches that are preset by the manufacturer and must not be moved.
Table 3-3. CONTROL Module, Panel Components

Jumper
Function
Jumper JP1
Selects the station clock input interface:

BAL 120 balanced interface. When using this interface, connect the station clock
input cable to the RJ-45 connector.
UNBAL 75 unbalanced interface. When using this interface, connect the station clock
input cable to the BNC female coaxial connector designated IN.
Default setting: BAL
Jumper JP4
Selects the station clock output interface:

BAL 120 balanced interface. When using this interface, connect the station clock
output cable to the RJ-45 connector.
UNBAL 75 unbalanced interface. When using this interface, connect the station clock
output cable to the BNC female coaxial connector designated OUT.
Default setting: BAL
Jumper FGND JP2
Controls the connection of the frame ground to pins 3, 6 in the RJ-45 station clock
connector.
YES Connected.
NO Not connected.
Default setting: YES
Switch SW1 (Restore Factory-Default Parameters)

During normal operation, all the sections of this switch must be set to OFF. When
you cannot establish communication with the CONTROL module, the only solution
is to restore the factory-default parameters and then configure the Gmux-2000
as required. This is performed by means of section 2 of the switch, which selects
the source of the configuration database parameters:
Note
Gmux-2000 Ver. 3.2
ON
The CONTROL module loads the factory-default parameters upon

power-up.
OFF
The CONTROL module loads the user-selected parameters from its

non-volatile memory on power-up.
User-selected parameter values are not erased by setting the switch section to
ON. Only after the CONTROL module is powered off and then on again, do the
default values replace the user values.
3-23
Installing the CONTROL Module

Use the procedure described on page 3-18 for the PS modules. The only
difference is that the CONTROL module has two extractors, which must be
simultaneously operated.
Removing the CONTROL Module

Use the procedure described on page 3-20 for the PS modules. The only
difference is that the CONTROL module has two extractors, which must be
simultaneously operated.
Replacing a CONTROL Module During Equipment Operation

Gmux-2000 Chassis with two CONTROL Modules
In a Gmux-2000 equipped with two good CONTROL modules, the standby module
can be removed/replaced without disrupting Gmux-2000 services.
If you replace the on-line CONTROL module, the Gmux-2000 will automatically
switch to the standby module, provided that module is OK. However, because the
active CONTROL module also provides clock signals to all the Gmux-2000
subsystems, there will be a short disruption in service. This disruption can be
avoided by first switching (flipping) to the standby module before replacing the
on-line module. You can identify the active and standby modules by their ACT
indicators.
Caution
To prevent service disruption, check that the ACT indicator of the CONTROL
module you want to remove is flashing. If not, use the supervisory terminal (or
any other management facility) to command the Gmux-2000 to flip to the other
CONTROL module, and wait for execution of this command before continuing.
To flip to the other CONTROL module using the supervision terminal:
1. Identify the on-line CONTROL module: this is the module with the lit ACT
indicator.
2. Connect the supervision terminal directly to the CONTROL DCE connector of
the on-line CONTROL module, and log in as administrator.
3. Use the Configuration>System>Redundancy>CL screen to change the CL
(CONTROL module) redundancy mode, which is normally AUTO, to the setting
corresponding to the standby CONTROL module (the module with the flashing
indicator):
Select CL-A to flip to the module installed in the CTRL.1 slot, or CL-B for
the module installed in the CTRL.2 slot.
Update the Gmux-2000 database to execute the change, using the

Configuration>Database Tools>Update Database screen.
4. Wait for the flipping to be executed. After it is executed, the ACT indicator of
the CONTROL module the supervision terminal is connected to starts flashing,
while that of the other module stops flashing and lights steadily.
3-24
Gmux-2000 Ver. 3.2
Note
The command will not be executed if a fault is detected in the module that is to
become the on-line module. In this case, the ACT indicators state will not change.
5. You can now disconnect the supervision terminal, and remove the module.
6. After installing again a CONTROL module in the slot of the removed module, it
is recommended to return the CL redundancy mode to AUTO. For this
purpose, the supervision terminal must again be connected to the on-line
CONTROL module.
Gmux-2000 Chassis with Single CONTROL Module

In a Gmux-2000 equipped with a single CONTROL module, it is recommended that
before replacing that CONTROL module, a good CONTROL module is installed in
the free CTRL slot. The replacement can be temporary.
In this case, after inserting the additional CONTROL module, first let it update its
database from the information provided by the existing CONTROL module: for
this purpose, change the CL redundancy mode to AUTO and wait about 10
minutes before starting the replacement procedure in accordance with the steps
listed above for a Gmux-2000 with two CONTROL module.
If the only CONTROL module in the chassis is replaced, Gmux-2000 services will
always be disrupted to some extent while no CONTROL 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 CONTROL module, to continue normal operation in accordance with the
previous configuration.
3.10 Installing I/O Modules

Install each I/O module in the prescribed I/O slot, in accordance with the
installation plan. For installation instructions, refer to the corresponding I/O
module Installation and Operation Manual.
3.11 Installing Blank Panels

Install blank panels in all the chassis slots that are not occupied by modules.
Gmux-2000 Ver. 3.2
Installing Blank Panels
3-25
3.12 Installation of Gmux-2000 Enclosure

Preparing for Installation in Rack
The Gmux-2000 is intended for installation on shelves and racks. Do not connect
power to the enclosure before it is installed in the designated position.
For rack installation, it is necessary to install two brackets to the sides of the
unit. RAD offers two rack mount kits:
RM-2000, for 19 inch (ANSI) racks
RM-2000E, for ETSI racks.
As illustrated in Figure 3-14 and Figure 3-15, you may install the brackets in two
ways, to orient the unit in accordance with your requirements (either with the
Gmux-2000 front panel toward the front of the rack, or the module panels
toward the front).
Figure 3-14 shows how to attach the brackets supplied in the RM-2000 kit for
installing the Gmux-2000 in 19 inch racks.
Install Bra
ckets Here
You Want
if
the Front
toward the
Pa
Front of th nel
e Rack
Figure 3-14. Attachment of Brackets for Installing the Gmux-2000 in 19 inch Racks
3-26
Installation of Gmux-2000 Enclosure
Gmux-2000 Ver. 3.2
Figure 3-15 shows how to attach the brackets supplied in the RM-2000E kit for
installing the Gmux-2000 in ETSI racks.
Install Brac
kets Here
You Want
if
the Front
toward th
Panel
e Front of
the Rack
Figure 3-15. Attachment of Brackets for Installing the Gmux-2000 in ETSI Racks
After attaching the brackets, you may attach handles on each side as shown in
Figure 3-16.
Figure 3-16. Attaching Handles to Brackets
Gmux-2000 Ver. 3.2
Installation of Gmux-2000 Enclosure
3-27
Installation in Rack
To install the Gmux-2000 in the rack:

1. Identify the prescribed position of each Gmux-2000 in the rack, in accordance
with the rack installation plan.
2. Obtain help from an additional person to place the Gmux-2000 in its
prescribed position, and then insert the guide posts located on each bracket
in the matching holes in the rack side rails. This will help keep the Gmux-2000
in position until it is fastened to the rack with the screws.
3. Have the other person hold the Gmux-2000 in place, and fasten the chassis
to the rack side rails with four screws, washers and nuts.
4. After installing the enclosure, check and install the required modules, in
accordance with the installation plan and the detailed instructions given in
each module Installation and Operation Manual.
3.13 Connecting Cables
Warning
Before connecting any cables and before switching on this instrument, the
protective ground terminal of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Make sure that only fuses of the required rating are used for replacement. The
use of repaired fuses and the short-circuiting of fuse holders is forbidden.
Whenever it is likely that the protection offered by fuses has been impaired, the
instrument must be made inoperative and be secured against any unintended
operation.
Note
The mounting brackets used for installing a Gmux-2000 in ETSI racks have special
openings for routing cables to one side of the chassis. You may also route optical
fibers through these openings, provided that the fibers are not stressed under
the other cables.
Grounding
Connect a short, thick copper braid between the grounding screw on the
Gmux-2000 rear panel and a nearby grounding point.
When the Gmux-2000 is powered by DC sources, connect additional grounding
leads from the grounding terminal of each PI/DC power connection terminal strip
to the nearest grounding point.
3-28
Connecting Cables
Gmux-2000 Ver. 3.2
Connecting Power
Caution
Gmux-2000 does not have a power switch, and therefore it will start operating as
soon as power is applied to one of the power supply inlets.
For proper equipment operation, at least two power supply modules must be
operative and receive power simultaneously. Therefore, for AC-powered PS
modules, it is necessary to simultaneously connect the power to all of the power
supply modules.
It is recommended that the external circuit breaker used to protect the input
power lines be also used as ON/OFF power switch.
Connecting AC Power
Connect each power cable first to the connector on the PI/AC module, and then
to the power outlet.
Note
When redundant power supplies are used, it is recommended to connect the

power cables to outlets powered by different circuits. However, it is necessary to
use one ON/OFF switch to simultaneously connect/disconnect all of them.
Connecting DC Power
Before starting, prepare the leads for connection to the PI/DC terminals as shown
in Figure 3-17.
Lead
itive
nd
Pos
Grou
ctive
e
t
o
Pr
Lead
ative
g
e
N
Strip 7mm
(1/4 in)
Figure 3-17. Connection to PI/DC Terminals
Gmux-2000 Ver. 3.2
Connecting Cables
3-29
Caution Pay attention to polarity. For each source, connect the protective ground lead,
then the positive lead, and the negative lead as the last one.
1. Refer to the Connection of DC Mains section at the beginning of this
manual.
2. Use a narrow blade screwdriver to release the terminal screw.
3. Push the lead into the terminal up to its insulating sleeve.
4. When the lead is in position, fasten the screw to secure the lead.
5. Verify that the lead is securely held by pulling on it lightly.
Connecting CONTROL Module

This section provides information on the connections required by the CONTROL
module.
Connection Data for CONTROL DCE Connector

The CONTROL DCE connector is an RS-232 asynchronous DCE port, terminated in
a 9-pin D-type female connector, intended for direct connection to terminals.
Since terminals usually have DTE interfaces, the connection to this port is made
by means of a straight-through cable. For connection to a modem, you need a
cross cable (also called null modem cable).
Connection Data for CONTROL ETH Connectors

The CONTROL ETH connector can be connected directly to an Ethernet hub port
using a straight cable.
Connection Data for CLOCK Connectors

To connect to the balanced clock interface, terminated in the CLOCK RJ-45
connector, use a cable prepared in accordance with your particular application
requirements, using the information presented in Appendix A.
The unbalanced (75) clock interface is relevant only when using 2.048 MHz or
2.048 Mbps clock sources. Use two 75 coaxial cables to connect to the two BNC
connectors for the interface. Pay attention to the function of each connector,
marked next to it: OUT output, IN input.
Connecting I/O Modules

Refer to the corresponding module Installation and Operation Manual.
3-30
Connecting Cables
Gmux-2000 Ver. 3.2
Chapter 4
Operation and Preliminary
Configuration
4.1
Overview
This Chapter provides general operating instructions and preliminary configuration

instructions for Gmux-2000 units.
The information presented in this Chapter is organized as follows:
Operating instructions: turn-on procedure, monitoring power-up sequence,

normal indications, and turn-off: Section 4.2
Configuration options for Gmux-2000: Section 4.3
Preliminary configuration instructions: Section 4.4
Configuring via supervision terminal: Section 4.5 and 4.6
Configuring via Telnet: Section 4.7
Using SSH: Section 4.8
Configuring via SNMP: Section 4.9
4.2
Operating Instructions
Preparations for Monitoring Power-Up Sequence

Any standard ASCII terminal (dumb terminal or personal computer emulating an
ASCII terminal) equipped with an RS-232 communication interface can be used to
control the Gmux-2000 operation.
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 monitor the Gmux-2000, configure the terminal for 115.2 kbps, one start bit,
eight data bits, no parity, and one stop bit. Select the full-duplex mode, echo off,
and disable any type of flow control.
Gmux-2000 Ver. 3.2
4-1
Chapter 4 Operation and Preliminary Configuration
To prepare the Gmux-2000 for first-time turn-on:

1. Before first-time turn-on, inspect Gmux-2000 installation and check that the
required cable connections have been correctly performed in accordance with
Chapter 3.
To monitor the Gmux-2000 during power up and preliminary configuration
procedures, connect a terminal to the CONTROL DCE connector of the active
CONTROL module in the Gmux-2000, using a straight (point-to-point) cable.
Note
You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CONTROL modules installed in the Gmux-2000, using a Y-cable.
Turning the Gmux-2000 On
Caution
To turn the Gmux-2000 on:

Gmux-2000 does not have a power on/off switch, and therefore it will start
operating as soon as power is applied.
For a Gmux-2000 equipped with AC-powered PS modules, make sure to
simultaneously connect the power to all the installed PS modules, for example, by
means of a common circuit breaker or ON/OFF switch.
For a fully equipped Gmux-2000, at least two of the three power supply (PS)
modules installed in the Gmux-2000 must be connected to power.
1. Connect the Gmux-2000 to power (see detailed instructions in Chapter 3).
The PWR indicators on all the PS modules that are powered light up, and
remain lit as long as the Gmux-2000 is powered.
You may also hear the fans in the Gmux-2000 fan tray start operating.
2. Wait for the completion of the power-up initialization process (this takes
about one minute). During this interval, monitor the power-up indications:
4-2
After power is applied, all the Gmux-2000 indicators turn on for a few
seconds. This enables you to check that the equipment indicators are OK.
After a few seconds, all the indicators turn off (except for the PS PWR
indicators).
The Gmux-2000 starts decompressing its software. During this process,

the ACT indicators of the CONTROL modules flash. The other indicators
(except for the PS PWR indicators) remain off while the ACT indicators
flash.
After software decompression is completed, all the indicators turn off for
a few seconds (except for the PS PWR indicators) as the Gmux-2000
performs its power-up initialization.
You can monitor the progress of the decompression and initialization

process on the terminal connected to the Gmux-2000. A typical display is
Gmux-2000 Ver. 3.2
Booting
Loading ...
Decompressing to RAM.
Processing archive: FLASH
Extracting GMUXCL.BIN
..........................................................
........ CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
Figure 4-1. Typical Power-Up Display

3. After the power-up initialization ends, all the PWR indicators must light
steadily, and the ACT indicator of the active CONTROL module lights. At this
stage, the indicators display the actual Gmux-2000 status.
4. At this stage, you may log in, using the supervision terminal.
Normal Indications
General Indications
Note
For a description of Gmux-2000 front panel indicator functions, refer to

Chapter 3.
1. As long as the Gmux-2000 is powered, all its PWR indicators lights steadily.
2. The ACT indicator of one of the CONTROL modules must light steadily.
3. The TST indicators must be off, unless a test has been activated on
Gmux-2000.
5. The MAJ ALARM and/or MIN ALARM indicators must be off. However, they may
flash, respectively light, as long as one or more of the Gmux-2000 ports is
not connected to operational equipment.
6. All the FLT indicators on the Gmux-2000 chassis and on the panels of the
modules installed in the chassis must be off.
CONTROL ETH Interface Status Indications

If a Gmux-2000 CONTROL ETH port is not yet connected to an active LAN, the
corresponding LINK and ACT indicators are off.
After connecting the CONTROL ETH port to an active LAN, the corresponding LINK
indicator must light. The ACT indicator of the port will flash, or appear to light
steadily, in accordance with the traffic.
PSN Interface Modules (GbE) Status Indications

The ACT indicators of GbE modules must light.
Gmux-2000 Ver. 3.2
4-3
When the equipment at the other end of the GbE links is operational, and the link
is physically connected:
The LINK indicators must light
The TX and RX indicators light in accordance with the transmit, respectively

receive, activity at the corresponding port.
The PAUSE indicator of a port may light from time to time, to indicate the
reception of PAUSE frames, used during temporary congestion conditions to
throttle traffic.
SDH Interface Modules (STM1) Module Status Indications

The ACT indicators of STM1 modules must light.
If an STM1 port is not yet connected to operational equipment, the
corresponding port LOSS LOC indicator lights. If the equipment at the other end
of the links is operational and the link is physically connected, the port LOSS LOC
and LOSS REM indicators must turn off.
Pseudowire Emulation Server Modules (E1-PW-SRV/21)

Module Status Indications
The ACT indicator of each pseudowire emulation server module must light.
Each E1 port indicator must light in green, provided the E1 equipment served by
the corresponding port is operational and the link is physically connected.
Pseudowire Emulation Modules with External E1 Interfaces

(E1-PW/28) Status Indications
The ACT indicator of each pseudowire emulation module must light.
For each external E1 port, if the port is not yet connected to operational
equipment, the corresponding L port indicator lights. If the equipment at the
other end of the link is operational and the link is physically connected, both the
L and R indicators of the external port must turn off.
Voice Compression Modules (VC-E1/16 and VC-E1/12) Status

Indications
The ACT indicator of each voice compression module must light.
For each external E1 port (either user or network port), if the port is not yet
connected to operational equipment, the corresponding LOC port indicator lights.
If the equipment at the other end of the link is operational and the link is
physically connected, both the LOC and REM indicators of the external port must
turn off.
Turning the Gmux-2000 Off
To turn the Gmux-2000 off:
4-4
Disconnect its power.
Gmux-2000 Ver. 3.2
4.3
Configuration Options
The Gmux-2000 configuration activities can be performed by means of the

following:
Supervision terminal
Telnet host
SSH client
SNMP-based network management system, e.g., the RADview-SC/Vmux

network management system (refer to the RADview User's Manual for
instructions).
The user can select whether to enable management by means of Telnet and/or
network management systems: only the supervision terminal is always able to
configure the Gmux-2000.
The capabilities of the four options listed above are similar, except that before
using Telnet, SSH, and/or network management systems, it is necessary to
perform a preliminary configuration using the supervision terminal.
The Gmux-2000 supports simultaneous management sessions: it is users
responsibility to prevent access conflicts and other errors that may occur when
multiple users simultaneously access the same equipment.
4.4
Preliminary Configuration Sequence
This section covers the preliminary configuration activities needed for a new
Gmux-2000. The activities presented below assume that Gmux-2000 uses its
factory-default configuration.
Note
If you cannot establish communication with Gmux-2000, reload the factory

defaults to each CL module installed in the chassis, using the switch located on
the CL module. Refer to the CL module installation section in Chapter 3.
Requirements
The preliminary activities are performed by means of an ASCII terminal (or a PC
running a terminal emulation program) directly connected to one of the
Gmux-2000 CONTROL DCE connectors, as described in Section 4.2 Preparations
for Monitoring Power-Up Sequence.
Terminal Characteristics
Any standard ASCII terminal (dumb terminal or personal computer emulating an
ASCII terminal) equipped with an RS-232 communication interface can be used to
configure and control the Gmux-2000 operation.
Gmux-2000 Ver. 3.2
4-5
Software
The software necessary to run the Gmux-2000 supervision program is contained
in the Gmux-2000 CONTROL modules. Moreover, the Gmux-2000 CONTROL
modules store all the configuration information generated or altered during the
communication with the terminal: no information is stored in the terminal.
Note
For proper display of screens on terminals, you must:

1. Select a fixed-pitch system font for the display. Use your operating system
documentation to find how to select a proper font.
2. Configure the terminal utility to use VT-100 terminal emulation.
Preparation for Preliminary Configuration

1. Connect a terminal to one of the Gmux-2000 CONTROL DCE connectors, as
described in Section 4.2 Preparations for Monitoring Power-Up Sequence.
2. Turn the Gmux-2000 on as described in Section 4.2 Turning the Gmux-2000
On.
Log-in for Supervision and Configuration

Gmux-2000 supports two access levels, which determine the functions the users
can perform using supervisory terminals, Telnet hosts, and SSH clients. The
access level is determined by the user name, and the protection against
unauthorized access is conferred by passwords.
The access levels supported by Gmux-2000 are described in Table 4-1.
Table 4-1. Gmux-2000 Access Levels

Access Level
Default User Name
Functions Accessible at this Level
Administrator
su
All the functions
Monitoring
user, tech
Only functions that do not affect equipment configuration and

service
The default passwords for both levels are identical, 1234. The passwords can be
changed at the administrator level, using Configuration>System>Management>
Management Access>User Access.
Notes
1. Pay attention to case: the password is case-sensitive.

2. If the administrator password has been changed and is not known, contact
RAD Technical Support Department for help.
To log in:
1. If the terminal is configured as explained in the Preparations for Monitoring
Power-Up Sequence section above, after the power-up initialization ends it
will display the cursor (a blinking underscore) at the home position of the
screen (top left-hand corner).
4-6
Gmux-2000 Ver. 3.2
2. Establish communication with the Gmux-2000 by pressing <Enter> once. You

may also see a few status messages, and then you will see the log-in screen.
A typical screen is shown below.
Pseudowire Gateway
USER NAME:
PASSWORD:
ESC - clear; & - exit; @-debug

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-2. Terminal Log-In Screen

Note
If the terminal is configured to different communication parameters (for example,

to another rate), you may see only random strings of characters, or there will be
no response to the pressing of the <Enter> key.
Refer to Chapter 3 for instructions on reloading the factory-default parameters
using the internal switch of the CONTROL module.
3. If the Gmux-2000 default user name and password have not yet been
changed, log in as follows:
Note
Type the default user name, su, and then press <Enter>.
Type the default password, 1234, and then press <Enter>.
If RADIUS authentication is enabled, you will see a Please wait prompt at the
bottom of the screen, followed by an alive indicator (a rotating line). Wait for
authentication to end. However, if the RADIUS server does not authenticate the
log in (or its response is not received before timeout), you will see Login Failed.
4. If your password is accepted, you will see the Gmux-2000 main menu. A
typical main menu screen is shown below.
If your log-in is not accepted, you will see Login Failed. After pressing <Enter>
the user name and password fields are cleared. In this case, try entering the
user name and password again, or reload the factory defaults.
Gmux-2000 Ver. 3.2
4-7
Pseudowire Gateway
Main Menu
1.
2.
3.
4.
5.
Inventory
Configuration
Monitoring
Diagnostics
Utilities
>
>
>
>
>
>
Please select item <1 to 5>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-3. Gmux-2000 Main Menu
Preliminary Configuration Session

The purpose of the preliminary configuration session is to prepare the minimal
set of parameters needed to manage the Gmux-2000.
In particular, after preliminary configuration you will enable management access
by Telnet hosts, SSH clients, and management stations, for example, RADview,
that are attached to a LAN directly connected to the CONTROL ETH Ethernet
ports of the Gmux-2000 CONTROL module, or at a remote location from which IP
communication to the CONTROL module Ethernet ports is possible.
Note
To enable management access to the Gmux-2000 from any relevant location, it is

necessary to fully configure the Gmux-2000: only full configuration can permit
management traffic to reach the Gmux-2000 via inband paths.
Full configuration is particularly important when using authentication by a remote
RADIUS server which is not located on the same LAN with the CONTROL ETH ports
of the Gmux-2000 .
The steps usually included in the preliminary configuration, when starting from
the factory defaults, are described in Table 4-2. For detailed operating
instructions, refer to the Chapter 5 section describing each activity.
Table 4-2. Gmux-2000, Outline of Preliminary Configuration Procedure

Step
1
4-8
Action
Using
Select the default database, 1
To update a new database, first load it

and then update the configuration
Configuration>Database Tools>Load Database

Gmux-2000 Ver. 3.2

Step
Action
Using


and then
Alternatively, configure the modules

installed in the Gmux-2000
Configuration>System>Card Type
Configure the IP communication parameters Configuration>System>Host IP

of the Gmux-2000 management agent
Configure specific managers and any

required static routes
Configuration>System>Management>Management Access

management:
If SNMP support mode is changed, save
to activate the change before
continuing
2. When SNMPv3 is disabled, configure

SNMP management parameters
Community

SNMP Engine ID
SNMPv3 users
9
1. Select the date source, and the date

format
2. When the internal real time clock is

used, set the time of day

10
Setting>Users
Configuration>System>Management>SNMPv3 Setting>
SNMPv1/v3 Mapping
Save the configured information in the

selected database
Note
Gmux-2000 Ver. 3.2
Configuration>System>Date & Time>Date Source, Date

Format
parameters
Configuration>System>Date & Time>NTP Server, GMT,
Update Interval
All the following menus are reached after opening the Configuration menu.
4-9
Select the default database:

1. Select Choose DB Number on the Database Tools menu.
2. Select the default database number, 1.
3. Select Update Database.
Reload the factory defaults:

1. Select Factory Default on the Database Tools menu.
2. Select Update Database to activate the default configuration as the online
database.
Initialize the Gmux-2000:

1. Select Load Hardware on the Database Tools menu.
2. Select Update Database to activate the default configuration for all the
hardware installed in the Gmux-2000.
To program modules not yet installed in the Gmux-2000 chassis:

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

1. Open Serial Port on the System menu.
2. Select the desired value for Speed (recommended value: 115200).
3. Select the desired word format parameters: Data Bits, Parity, and Stop Bit.
The recommended values are 8 data bits, no parity and 1 stop bit.
Configure the Gmux-2000 IP communication parameters:

1. Open Host IP on the System menu.
2. Move the cursor to the ONLINE CL field, and then select the prescribed value:
4-10
IP Address. Enter the IP address of the Gmux-2000 management agent,

using the dotted-quad format (four groups of digits in the range of 0
through 255, separated by periods).
IP Mask. Enter the IP subnet mask of the Gmux-2000 management agent.

Make sure to select a subnet mask compatible with the selected IP
address, and whose binary representation consists of consecutive
ones, followed by the desired number of consecutive zeroes.
Default Gateway. Specify the IP address (usually an IP router port) to

which the Gmux-2000 management agent will send packets when the
destination IP address is not within the subnet specified in the Mask field.
Gmux-2000 Ver. 3.2
Type the desired IP address, using the dotted-quad format. Make sure
that the IP address is within the subnet of the host IP address. The
default value, 0.0.0.0, means that no default gateway is defined.
3. To configure additional management interfaces, repeat the procedure for
each prescribed interface.
Note
Each IP address must be in a different IP subnet.

Configure specific managers, and the required static routes:

1. Open Management on the System menu.
2. Open Manager List on the Management submenu.
3. Type a and then press <Enter> to start configuring a new manager, or define
a static route to a new destination.
4. Select the prescribed values for each parameter:
IP Address. Enter the IP address of the new manager/static route

destination, using the dotted-quad format (four groups of digits in the
range of 0 through 255, separated by periods).
Next Hop. When the new IP address is not within the IP subnet of the
configured interface, enter an IP address to which the traffic will be sent,
to enable reaching this manager/destination. This is usually the address
of an IP router port.
Interface. Specify the interface through which traffic is sent to this

manager/destination: it can be the CONTROL ETH port of the CONTROL
module, or one of the GbE module ports.
When the Gmux-2000 includes a voice compression module (or such
modules are programmed in the database), you may also see in the list of
selectable interfaces the programmed voice compression modules: these
interfaces can be used only for managing inband equipment connected to
the external data ports of the voice compression modules. At this stage,
it is not recommended to configure such interfaces.
Gmux-2000 Ver. 3.2
Trap. Select whether traps will be sent to this manager/destination in

case an alarm report will result in the generation of a trap. For static
routes to destinations which are not management stations, do no enable
trap sending (you can enable trap sending to a maximum of 10 IP
addresses)
VLAN Valid. Select whether to use VLAN tagging for Gmux-2000 traffic
exchanged with this manager/destination. This is generally required for
management traffic
VLAN ID. When management VLAN tagging is enabled, enter here the
VLAN ID number to be used for traffic exchanged with this station.
VLAN Priority. When VLAN tagging is enabled, enter here the priority
assigned to the management VLAN traffic exchanged with this station.
4-11
5. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new station. To display the Manager List
again, press ESC.
6. Repeat the process until all the desired management stations have been
defined.
7. When done, save the changes and then confirm the action.
Configure management access options:

2. Open Management Access on the Management submenu.
3. Configure the Telnet/SSH Access mode:
For each access type, you can select one of the following options:
Disabled access by Telnet and SSH is blocked.
Enabled access is allowed to any logged Telnet user
Managers Only access, using either Telnet or SSH, is allowed only to the
authorized managers, configured by means of Management>Manager
List.
Enable Secure only secure access (SSH) is allowed, but access is not
restricted to managers configured by means of Management>Manager
List.
Managers Only Secure only secure (SSH) access is allowed, and access
is restricted to managers configured by means of Management>Manager
List.
4. Configure the SNMP Access parameters:

For each access type, you can select one of the following options:
Disabled access is blocked.
Enabled access is allowed to any logged user
Managers Only access is allowed only to the authorized management

stations, configured by means of Management>Manager List.
Configure the SNMP management parameters:

2. Select Device Info on the Management submenu.
3. Enter the prescribed description for each item.
5. Select Authentication/Community on the Management submenu.
6. Enter the prescribed community strings, and turn on or off the sending of an
authentication failure trap in case an SNMP request with invalid community is
received.
4-12
Gmux-2000 Ver. 3.2
Note
The community names are case-sensitive.

Set the Gmux-2000 real-time clock:

2. Select Date & Time on the Management submenu.
3. Select the Date Source: the recommended mode at this stage is NVRAM (the
internal real-time clock of the CL modules: after full configuration, you may
select NTP and configure the appropriate NTP parameters).
4. Open Date Format, and select the desired date format.
Note
dd stands for day, mm for month and yyyy for year.

5. When done, type % to save and then confirm the action.
6. Now set each component of the time of day and date. To change, select the
desired item and then type the desired value. Confirm each change by
pressing <Enter>.
Notes
Time must be entered in the 24-hour format.

It is recommended to set the time about one minute beyond the desired time,
and then press <Enter> at the correct instant.

7. When done, save and then confirm the action.
Save the changes to the default database:

1. On the Database Tools, select Update Database to save and activate the new
configuration.
4.5
Configuring Gmux-2000 via Supervision

Terminal
Introduction
Gmux-2000 operating mode, and all of its functions, are controlled by a set of
configuration parameters organized as a database. The parameters in the
database are selected by the user in accordance with the requirements of each
specific application.
To provide a starting point for the user, RAD provide a fixed set of
factory-default parameters. The factory defaults are not modified by user
configuration activities, and therefore these factory-defaults can be reloaded
whenever needed.
The preparation of the desired set of configuration parameters is made in
accordance with a set of rules, which together form the Gmux-2000 supervision
Gmux-2000 Ver. 3.2
Configuring Gmux-2000 via Supervision Terminal
4-13
language. The supervision language is used to communicate with the central

control subsystem of the Gmux-2000 located in the CONTROL modules, using a
supervision terminal connected to the control port of the CONTROL module. The
same language can also be used by Telnet hosts.
Preparation of New Configuration Parameters

The Gmux-2000 set can store several databases (up to 5). These databases are
stored on a flash disk, and the supervision utility includes the utilities needed to
manage the file system of this disk.
At any time, one of these databases serves as the active (online) database.
Gmux-2000 operation is controlled by the parameters contained in its active
database. The active database is stored in flash memory, and therefore the latest
configuration parameters are always available upon power-up.
During the preparation of configuration parameters, the central control
subsystem of the Gmux-2000 dedicates a section of its RAM, called editing
buffer, to this process. The editing buffer contains a copy of a user-selected
database (any of the five databases that can be stored by the Gmux-2000,
including the currently-active database), and only this copy is modified by the
commands entered by the user. Therefore, you can make configuration changes
and cancel them as required without affecting the traffic flow through the
Gmux-2000.
Any changes take effect (that is, are activated and thus become the active, or
online, database) only when they are saved: in this case, the contents of the
edited database are first copied to the flash disk, and then the Gmux-2000
control system reinitializes the modules in accordance with new database.
Validity Checks
The Gmux-2000 control subsystem automatically checks the validity of each new
subset of parameters selected by the user as soon as an attempt to save them is
made, alerts the user to potential conflicts, and rejects erroneous selections.
In addition, when the preparation of a new database is completed, the user can
initiate a preliminary check of its validity by means of a special command (Check
Sanity). The sanity check is performed on the configuration parameters stored
in the editing buffer. This function provides messages which help identify
conflicting parameters, inconsistent selection of related parameter values, etc.,
so that the parameters can be corrected before proceeding.
Only after all the validity and sanity checks are successfully passed, can the user
save the new (or modified) set of configuration parameters as a database (this is
made by means of the UPD DB or Update DataBase command). If the new set is
saved under the number of the active configuration database, the Gmux-2000
system will start operating in accordance with the new configuration.
Since the last validated sets of configuration parameters are stored in flash memory,
Gmux-2000 configuration is not affected when the power is turned off. However,
any changes not yet saved will be lost in case the Gmux-2000 is reset or powered
down.
4-14
Gmux-2000 Ver. 3.2
Power-up Process
Upon turn-on, the Gmux-2000 central control subsystem checks the validity of
the stored configuration data, and if everything is OK, it loads the data into the
working memory and reconfigures the system accordingly.
Therefore, the Gmux-2000 is ready for operation in accordance with the last
active database immediately after power is applied.
However, if the configuration data is not valid, the stored database will not be
activated; instead, the default database will be activated. To facilitate the
correction of the database, you may edit the original database that was not
activated and correct whatever was wrong.
After the operating parameters have been loaded, a process called configuration
set-up, the Gmux-2000 no longer requires operator attendance.
Note
Unless otherwise specified, all the parameter values appearing in the following
screens are given for illustration purposes only and do not reflect recommended
values.
General Terminal Operating Procedures

Organization of Terminal Screens
The Gmux-2000 is managed via a simple, menu-driven utility that uses a basic
terminal user interface. A typical screen that includes most is shown in
Figure 4-4.
Each screen includes the following main items (refer to Figure 4-4 for typical
appearance):
Header: identifies the device being configured (Gmux-2000).
Status indicator: status indicators may appear in the top right-hand corner to
indicate one or more of the following conditions:
TEST: displayed when a test is activated on the local Gmux-2000
ALRM: indicates that alarm conditions are present in the local Gmux-2000
ERROR: displayed after the user action is rejected, for example, because
of an invalid selection or out-of-range value. The indicator disappears
after a valid action is performed.
Work area: includes a description of the screen, followed by the items

available for the current screen. Each selectable item has its own number.
The screen description identifies the screen (in this example: E1 Port), and
also displays navigation data, that is, the path through the Gmux-2000 menu
structure that has been traversed to reach this screen
(Configuration>Physical Layer>E1 Port). If the full path is too long, its
beginning is truncated, in which case an ellipsis appears. When the same
screen is used to configure several items of the same type, for example,
several ports of the same I/O module, the header also identifies the specific
item (in this case, the F next and B prev options also appear in the lower
part of the work area).
Gmux-2000 Ver. 3.2
4-15
In addition, the work area includes the terminal prompt, >. The item number
you type appears to the right of the prompt.
The lower part of the work area is also used to display a concise explanation
of the available options and prompts regarding the actions available to you. It
may also display messages that request you to confirm operations such as
configuration changes, resetting, etc. or alerts that errors have been
detected during the evaluation of the parameters selected by you (in this
case, you will see a V View Sanity Log option).
Note
Save: after you make a configuration change, you must either save it in the
edit buffer, or undo (cancel). Changes that have been saved can take effect
only after the current database is updated.
The indication that changes have been made is provided by the

appearance of the S Save item just above the bottom line, and/or by
the addition of Save Parameters as the last item on the configuration
screen.
After saving, the S Save item disappears, however you will see the
message DB WAS CHANGED. PERFORM UPD.DB TO SAVE CHANGES IN
ONLINE FILE. This reminds you that in order to activate the changes, the
database must be updated. After pressing <Enter> to confirm the
message, it disappears and the % UPD DB item appears in the lower
part of the work area.
If you attempt to exit without saving the changes, you will see Do you want to
save changes? (Y/N/C) followed by the prompt >. You can confirm (Y) the
changes, exit without any change (N), or cancel (C) the request, and continue on
the current screen.
Bottom line: displays the keys used for navigation.
ESC
returns to the previous screen (not relevant for main menu)
returns directly to the main menu (not relevant for main menu)
&
ends the utility and displays the log-in screen again.
increases the area dedicated to the display of alarms.
displays additional help specific to the current screen.
In addition, the number of management connections (C) and the number

managers (M) currently connected to the Gmux-2000 is shown at the lower
right-hand corner (in Figure 4-4, this is 1 manager via one management
connection). The managers number indicates the total number of
management sessions active at the instant the screen was displayed,
irrespective of type (terminal, Telnet, SNMP, etc.). If no user is logged in, the
number of managers is 0.
4-16
The last two rows display the last two alarms. The alarms appear only when
Pop Alarm is enabled using Configuration>System>Serial Port.
Gmux-2000 Ver. 3.2
Note
If Pop Alarm is enabled, it is normal to see at least a RESET OCCURRED event after
power up. If not all of the Gmux-2000 ports are connected to operating
equipment, you may also see alarms reporting loss of signals, LAN not connected,
etc.
Pseudowire Gateway
Configuration>Physical layer>E1 port - (IO 3: EXT PORT 1 CARD TYPE-PWS_E1_PW)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Channel ID[1 - 28]

Admin Status
Idle code[0 - ff]
OOS Signaling
OOS code[0 - ff]
Transmit clk source
Rx Sensitivity
Assign entire port to bundle
Line type
Restoration Time
... (1)
(Connected)
... (7E)
>
(Space)
... (FF)
>
(System A)
(Short Haul)
>
>
(Framed G.704)
>
(CCITT)
>
F - next; B - prev; V - view sanity log
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-4. Typical Gmux-2000 Supervision Utility Screen
General Procedures
How to use the terminal to perform a desired activity:
To select a menu item, type the corresponding line number and then press
<Enter>. This will either
display a submenu or a parameter selection screen
or
let you type the (free text) parameter value in the same row
or
toggle the current value of the corresponding parameter (relevant to
ENABLE/DISABLE or ON/OFF selections).
Gmux-2000 Ver. 3.2
The type of response to be expected after selecting a menu item is indicated

as follows:
>
Selecting that item will display a submenu or a parameter

selection screen (see for example Transmit clk source in
Figure 4-4).
...
Selecting that item will let you type the desired value in the
same line (see for example Channel ID in Figure 4-4).
4-17
Nothing
When neither symbol is displayed, selecting that item will toggle

the current selection, now shown in brackets (for example, this
will change ENABLE to DISABLE or vice versa).
When a menu does not fit on one screen (because it includes many lines), it
is displayed on two consecutive pages. In this case, you will see (N) after
the last line on the first page and (P) before the first line on the second
page:
While on the first page, press N to display the second page
While on the second page, press P to return to the first page.
When a screen can display configuration fields, status or performance

monitoring information on several related entities, you can sequentially go
from entity to entity. In this case, you will see F (go to next entity) and B
(return to previous entity) in the last line of the screen.
For example, using the F and B keys you can sequentially select I/O slots or
multiple ports of the same module, display sequentially the attributes of the
various alarms, etc..
When a configuration screen is organized as a table, a special set of keys is

used for navigation within the table (such screens always have a ? (help)
option that displays these keys). The following keys may be used for
navigation within tables:
Left Arrow () move to the left
Right arrow () move to the right
Down Arrow () move down
Up Arrow () move up
^D scroll down
^U scroll up
F next
B previous
In addition, the following shortcuts are also available:
Tab select the next cell that may be changed
M switch to the menu mode
G followed by <row number>,<col number> select a specific cell. For

example, type G2,5 to select the fifth cell in the second row.
The current value of a parameter is listed within parentheses ( ). To change a

parameter value on a parameter selection screen:
Type the line number corresponding to the desired value, and then press
<Enter>
To enter a value which requires free text entry, type in the desired string
and then press <Enter>. Use backspace to erase the current string.
Note that whenever applicable, the allowed range of values of a
parameter is listed within square brackets [ ].
The entry is checked after pressing <Enter>, and it is accepted only if it is

valid:
4-18
If you make an error, for example, if you press a key not active on the
current screen or select an invalid parameter value, an ERROR indicator
Gmux-2000 Ver. 3.2
appears in the right-hand corner. This indicator disappears as soon as

you make a correct operation.
If you select a parameter value incompatible with the current operating

state or other parameters, you will see a message that explains the error.
For screens that may report multiple errors, you will see instead a
message that offers to display the list of errors detected.
After reporting the error, the Gmux-2000 is ready to accept your next entry.
When done with the current screen, press <ESC> to return to the previous
screen, or type ! to return directly to the main menu.
Saving Changes to Configuration Database

To save all the pending changes, type % - UPD DB. Gmux-2000 will automatically
perform a sanity check:
Note
If everything is correct, you will see DB UPDATING IN PROGRESS . . ., and the

database update is performed. Wait until the message disappears, and then
press any key to continue.
If only sanity warning are detected, you will see a SANITY WARNINGS, DB
UPDATING IN PROGRESS . . . message, but database updating is performed.
Wait until the message disappears, and then press any key to continue.
When warnings and/or errors are detected, you can see them using the option
V View Sanity Log, which appears in the bottom line.
If sanity errors are detected, you will see a SANITY ERRORS message, and the
changes are rejected.
The result of the update process is indicated in the prompt line: DB UPDATED
SUCCESSFULLY, or a failure message.
Ending a Terminal Configuration Session
To end the current terminal session:

Type & and then press <Enter>.
In addition, Gmux-2000 will automatically terminate the current session if no
activity is detected for 10 minutes.
After a session is ended, it is necessary to enter again a valid user name and
password to start a new session.
Gmux-2000 Ver. 3.2
4-19
4.6
Menu Structure of Supervision Utility
Main Menu Structure

Figure 4-5 shows the structure of the main menu.
Main Menu
1. Inventory
2. Configuration
3. Monitoring
4. Diagnostics
5. Utilities
Inventory
1.
2.
3.
4.
5.
6.
7.
8.
System
PS
CL
I/O
Bundle
Fan
Clock
Redundancy
Configuration
1.
2.
3.
4.
5.
System
Physical Layer
Connection
TS Assignment
Database Tools
1.
2.
3.
4.
Security Key
Statistics
Status
Event Log
Alarm
Monitoring
Diagnostics
Self Test Results
1. Ping
2. Loopback
3. APS Commands
Utilities
1. File Utilities
2. Reset
3. File System
Figure 4-5. Main Menu Structure

The functions of the various main menu items are as follows:
4-20
Inventory
Displays logistics information on the Gmux-2000, and its various

subsystems. See Chapter 5 for details.
Configuration
Configure Gmux-2000 operational parameters, and manage its

database files. See Chapter 5 for details.
Monitoring
Display Gmux-2000 alarms, events and status, and the

performance monitoring statistics. See Chapter 7 for details.
Gmux-2000 Ver. 3.2
Diagnostics
Activate test loopbacks on the various ports, and check IP

connectivity. See Chapter 7 for details.
Utilities
Use the file management and file transfer utilities.

See Chapter 5 for details.
Detailed Menu Structures

Figure 4-6 through Figure 4-19 show the detailed menu structure of the
supervision utility.
You may use these figures to find the screen used for any desired activity. For
additional details, refer to the Chapter listed above on the description of the
main menu, where you will find a detailed view and a description of the functions
and parameters available on each screen.
Inventory
1. System
2. PS
3. CL
4. I/O
5. Bundle
6. Fan
7. Clock
8. Redundancy
System
System Information
1. System Information
2. SW/HW Revision
I/O Inventory
SW/HW Revision
PS
CL
I/O
Slot
Components Details
Port Information
Bundle
Connection Number
Fan
Clock
Redundancy
CL
1. CL
2. I/O
I/O
APS Status
APS Interfaces
Figure 4-6. Inventory Menu Structure
Gmux-2000 Ver. 3.2
4-21
Configuration
1.
2.
3.
4.
5.
System
Physical Layer
Connection
TS Assignment
Database Tools
System
1. Host IP
2. Syslog System Address
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Physical Layer
Depends on Card Type
Connection
1.
2.
3.
4.
Bundle ID
Connection Mode
PSN Type
Connection Configuration
TS Assignment
1.
2.
3.
4.
Card SS/PP
TS Assignment
Assign TS Range to Bundle
Assign Entire Port to Bundle
TS Assignment
or
1. Card SS/PP
2. TS Assignment
3. Assign Entire TSs to Port
Only for Framed Modes
Database Tools
1.
2.
3.
4.
5.
6.
Choose dB Number
Factory Default
Load Database
Load Hardware
Check Sanity
Update Database
Figure 4-7. Configuration Menu Structure
4-22
Gmux-2000 Ver. 3.2
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Host IP
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
GbE 2/IF 1:
GbE 2/IF 2:
IP ADDRESS
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
IP MASK DEFAULT GATEWAY

0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Device Info
Syslog System Address
Sys Description
1. Sys Contact
2. Sys Name
3. Sys Location
SNMPv3 = Disabled
Management
Authentication/Community
1. Device Info
2. Authentication/Community
3. Manager List
4. Management Access
5. Username&Password
6. SNMP Engine ID
7. SNMPv3 - Disabled
1. Trap Community
2. Read Community
3. Write Community
4. Authentication Failure Trap
Manager List
IP ADDRESS NEXT HOP
INTERFACE TRAP (FOR MANAGER) VLAN VALID VLAN ID VLAN PRIORITY
172.171.75.32 255.255.255.255 CL Interface
Yes
Yes
67
6
See Part 4
NVRAM
Add
SNMP Engine ID
Date & Time
Engine ID
Engine ID Config Type
1. Rest Bytes
1. Date Source (NVRAM)

2. Date Format
Current Date & Time
3. Time Hour
4. Time Minutes
5. Time Seconds
6. Date Year
7. Date Month
8. Date Day
or
Date Format
Manager List
Manager List
1. IP Address
2. Next Hop
3. Interface
4. Trap (for Manager)
5. VLAN Valid
1. DD/MM/YYYY
2. MM/DD/YYYY
3. YYYY-MM-DD
NTP
VLAN Valid - Yes
VLAN Valid - No
or
1. IP Address
2. Next Hop
3. Interface
5. VLAN Valid
6. VLAN ID
7. VLAN Priority
INTERFACE
1. CL Interface
2. GIG A-IO 6/1
3. GIG A-IO 6/2
4. GIG B-IO 8/1
5. GIG B-IO 8/2
..
.
Date & Time

1. Date Source (NTP)
2. Date Format
Current Date & Time
3. NTP Server IP Address
4. GMT
5. Update Interval
GMT
Update Interval
Clock Source
1. System A
2. Ext Clock Interface
3. Ext In/Out Clk Mode
4. Ext Out Clock Source
5. Ext Out Clock State
Alarms
Management Access
See
Part 2
1. Attribute
2. Priority
3. Init Alarm Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
1. User Access
2. Telnet/SSH Access
3. SNMP Access
Web Access - Disabled
4. RADIUS Client
5. RADIUS Server
user, tech
su
User Access
User Access
1. Old Password
2. New Password
3. Confirmation
1. User Name
2. Permission
3. Access
4. Old Password
5. New Password
6. Confirmation
Permission
1. Full Control
2. Read Only
3. User Change
Access
Telnet/SSH Access
Username&Password
1. Display User List
2. Restore User List
Redundancy
1. Disabled
2. Enabled
3. Managers Only
4. Enable Secure
5. Managers Only Secure
1. Terminal
2. Telnet
3. All
SNMP Access
1. CL
2. I/O
1. Disabled
2. Enabled
3. Managers Only
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
RADIUS Client
1. Remote
2. Local
3. Remote&Local
See
Part 3
Ethernet Port
1. Speed
Card Type
RADIUS Server
1. Server IP Address
2. Shared Secret
3. Number of Retries
4. Timeout
5. Authentication Port
6. Accounting Port
Syslog
1. Syslog Configuration
2. Syslog Statistics
Figure 4-8. Configuration>System Submenu Structure (Part 1 of 4)
Gmux-2000 Ver. 3.2
4-23
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Master Clock Source
SNMPv3 = Disabled
Management
1. Device Info
3. Manager List
6. SNMP Engine ID
1. Internal
2. Rx Clk
3. Ext In-1
4. Ext In-2
Master Clock
1. Master Clock Source
2. Master Clock Source SS PP
See Part 1
Rx Clk only
System A
Fallback Clock Source
1. Master Clock
2. Fallback Clock
See Part 4
Ext Clock Interface
Fallback Clock
1. None
2. Rx Clk
3. Ext In-1
4. Ext In-2
1. Fallback Clock Source

2. Fallback Clock Source SS PP
Rx Clk only
1. G.703-T1
2. G.703-E1 Balanced
3. G.703-E1 Unbalanced
4. RS-422 T1
5. RS-422 E1
Date & Time

Depends on
Date Source
Ext Out Clock Source

1. System A
Attribute
Attribute
1. Alarm Level
2. Alarm Sub-Level
3. Alarm Attributes
Clock Source
1. System A
or
Alarm Level
1. Alarm Level
2. Bundle No.
3. Alarm Attributes
Normal
Y-Cable
Alarm Attributes
Priority
Define Alm Priority
1. Define Alm Priority

2. Alarm Number
3. Alarm Priority
Alarms
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
Alarm Level
Threshold
Threshold
1. Alarm Level
2. Bundle No.
3. Alarm Threshold
Alarm Priority
or
1. Alarm Level
2. Alarm Sub-Level
3. Alarm Threshold
Alarm Sub-Level
Alarm Threshold
Redundancy
Threshold Window
1. CL
2. I/O
1. Alarm Window
Report
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
Alarm
Report Relay-1 Relay-2 Log Minor Alarm LED Major Alarm LED
Critical on Yes
Yes
Yes
Yes
Yes
Yes
Critical off Yes
N/A
N/A
Yes
N/A
N/A
Major on
Yes
Yes
Yes
Yes
Yes
Yes
Major off
Yes
N/A
N/A
Yes
N/A
N/A
Minor on
Yes
Yes
Yes
Yes
Yes
Yes
Minor off
Yes
N/A
N/A
Yes
N/A
N/A
See
Part 3
Ethernet Port
1. Speed
Connect
Input Relay
1. Input Alarm Relay
2. Connect
3. Active
4. Alarm String
Active
Card Type
Syslog
4-24
Gmux-2000 Ver. 3.2
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
SNMPv3 = Disabled
Management
1. Device Info
3. Manager List
6. SNMP Engine ID
See
Part 1
Redundancy Mode
CL
1. Auto
2. CL-A
3. CL-B
1. Redundancy Mode
See Part 4
Date & Time
Depends on
Date Source
Config Mode
I/O
1. None
2. 1:1 (Bidirect)
STM1
3. 1+1 (Unidirect)
GbE
4. 802.3AD
5. N+1 - PW Server Modules only
1. APS ID
add
Clock Source
1. System A
3. Ext In/Out CLK Mode
Alarms
APS Configuration
I/O
Name
Config Mode
Recovery Mode
Time to Restore in sec
STM-1 SD Flip Criteria
1. APS ID
2. APS Configuration
3. APS Mapping
See
Part 2
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
APS Mapping
CH NUM INTERFACE PRIORITY
1
7/1
High
2
7/2
Low
Speed
Redundancy
1. 300
2. 1200
3. 2400
4. 4800
5. 9600
6. 19200
7. 38400
8. 57600
9. 115200
1. CL
2. I/O
Parity
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
Ethernet Port
1. No
2. Even
3. Odd
Speed
1. 10Mbps Half Duplex
2. 10Mbps Full Duplex
5. Auto Negotiation
1. Speed
Card Type
SLOT:
DB :
PS-1
PS-AC
PS-2
PS-AC
SLOT:
IO/1
DB :
VC-E1/16
Card Type
Syslog Configuration
Syslog
Recovery Mode
Revertive
Non-Revertive
1. Logging Status
3. Server UDP Port
4. Device UDP Port
5. Facility
6. Severity
SLOT:
DB :
IO/6
GbE
IO/2
Server-E1-PW
IO/7
STM_2
PS-3
PS-AC
CL-1
CL
IO/3
IO/4
CES-E1-PW Server-E1-PW
IO/8
GbE
CL-2
CL
IO/5
CES-E1-PW
IO/9
STM_2
Facility
Severity
Syslog Statistics
Total Tx Messages
Unqueued Dropped Messages
Gmux-2000 Ver. 3.2
4-25
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
See
Part 1
SNMPv3 = Enabled
Management
1. Device Info
2. Manager List
5. SNMP Engine ID
6. SNMPv3 - Enabled
7. SNMPv3 Setting
Authentication Protocol
1. usmNoAuthProtocol
2. usmHMACMD5AuthProtocol
3. usmHMACSHAAuthProtocol
Users
1.
2.
3.
4.
5.
Date & Time

Depends on
Date Source
Security Name
Privacy Protocol
Authentication Password
Privacy Password
Privacy Protocol
1 usmNoPrivProtocol
2. usmDESPrivProtocol
Targets Params
Targets & Notify
SNMPv3 Setting
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
SNMPv3 Factory Defaults
Summary User Table
Summary Target Table
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
1.
2.
3.
4.
5.
Name
Message Processing Model
Security Model
Security Name
Security Level
Message Processing
Model
Security Model
Target Address
1.
2.
3.
4.
Security Level
Name
IP Address
Params Name
Tag List
Notify
Clock Source
1. System A
Alarms
Trap
See
Part 2
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
Summary User Table

User
Initial
Security Model
USM
Security Level
noAuthNoPriv
Redundancy
1. CL
2. I/O

Address MPModel SecModel SecName SecLevel
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
See
Part 3
Ethernet Port
1. Speed
Card Type
Syslog
4-26
Gmux-2000 Ver. 3.2

Connection
1. Bundle ID
2. Connection Mode
3. PSN Type
4. Connection Configuration

Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
TDMoIP (CE), SAToP

UDP/IP
MPLS/ETH
Connection State
Source Bundle
Destination Bundle
TDM Byte in Frame
Jitter Buffer in Ms
Sensitivity
Payload Type
Connection State
Source CBID
Dest CBID
Payload Format
TDM Byte in Frame
Jitter Buffer in Ms
Sensitivity
OAM Connectivity
OAM Indication
Payload Type
Far End Type
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
IP TOS
Adaptive Clock
VLAN Tagging
VLAN ID
VLAN Priority
or
Far End Type

OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Adaptive Clock
Outbound Label Tagging
Outbound Tunnel Label
Outbound EXP Bits
Inbound Label Tagging
Inbound Tunnel Label
VLAN Tagging
VLAN ID
VLAN Priority
Figure 4-12. Configuration>Connection Submenu TDMoIP (CE) and SAToPSN

Bundles
Gmux-2000 Ver. 3.2
4-27
Connection
1. Bundle ID
2. Connection Mode
3. PSN Type
Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
UDP/IP
MPLS/ETH
Function
Function
1. AAL2oMPLS
2. AAL2oMPLS+
1. TDMoIP
2. TDMoIP+
TDMoIP (CV)
UDP/IP
Routing Parameters
1. Connection State
2. Function
3. Routing Parameters
4. Transparent Jitter Size
5. Max Bytes In Multiplexed Frame
6. Packetizing Interval
7. Connectivity Parameters
8. Voice Parameters
1. Destination IP
2. Exit Port
3. Next Hop
4. Source CBID
5. Dest CBID
6. Exit Channel
7. TOS Parameters
8. VLAN Parameters
MPLS/ETH
Routing Parameters
1. Destination IP
2. Exit Port
3. Next Hop
4. Source CBID
5. Dest CBID
6. Exit Channel
7. VLAN Parameters
TOS Parameters
TOS Byte Value (Hex)
1. Precedence
2. Delay
3. Throughput
4. Reliability
VLAN Parameters
1. VLAN Tagging
2. VLAN ID
3. VLAN Priority
Connectivity Parameters
Fax Modem
1. Connectivity Packet Rate (Sec)
2. Connectivity Timeout Cycles
Voice Parameters
1. Coder/Rate (Kbps)
2. Caller ID Type
3. Tx Delay for Caller ID
4. Volume to Line
5. Volume from Line
6. Fax/Modem
7. MF Parameters
8. Custom Tone Detection
9. Super Tandem
10. Echo Canceller
11. Coding
12. VAD
13. CNG Mode
14. Advanced Voice Parameters
1. Modem
2. Modem op mode
3. VBD Rate
4. Fax
5. Fax Rate (kbps)
6. Max VBD Modem Calls
7. Max Relay Modem Calls
MF Parameters
1. MFCR2 Relay
2. Minimum Pulse Width (msec)
3. Minimum Power Level (negative dBm)
4. MFC Spooling
5. Tone Ack Interval (N*20)
For
MFC Spooling
enabled
VAD
1. VAD Method
2. Noise Level for VAD
Generic VAD Policy

Internal VAD Policy
Advanced Voice Parameters

1. Cdis/CNG Detection Time (N*10msec)
Figure 4-13. Configuration>Connection Submenu TDMoIP (CV) Bundles
4-28
Gmux-2000 Ver. 3.2
Connection
1. Bundle ID
2. Connection Mode
3. PSN Type

Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
HDLC
UDP/IP
MPLS/ETH
Connection State
Source CBID
Dest CBID
OAM Connectivity
OAM Indication
OOS L Bit mode
Destination IP
Network Slot Port
Next Hop
IP TOS
VLAN Tagging
VLAN ID
VLAN Priority
or
Connection State
Source Bundle
Destination Bundle
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Outbund EXP Bits
VLAN Tagging
VLAN ID
VLAN Priority
Figure 4-14. Configuration>Connection Submenu HDLCoPSN Bundles
Gmux-2000 Ver. 3.2
4-29

Connection
1. Bundle ID
2. Connection Mode
3. PSN Type

Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
CES
UDP/IP
MPLS/ETH
Connection State
Source Bundle
Destination Bundle
TDM Frame in Packet
Jitter Buffer in Ms
Sensitivity
Payload Type
Connection State
Source CBID
Dest CBID
Payload Format
TDM Frame in Packet
Jitter Buffer in Ms
Sensitivity
OAM Connectivity
OAM Indication
Payload Type
Far End Type
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
IP TOS
Adaptive Clock
VLAN Tagging
VLAN ID
VLAN Priority
or
Far End Type

OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Adaptive Clock
Outbound EXP Bits
VLAN Tagging
VLAN ID
VLAN Priority
Figure 4-15. Configuration>Connection Submenu CESoPSN Bundles
4-30
Gmux-2000 Ver. 3.2

Voice Compression Modules - User (Voice) Ports
TS Assignment
1. Card ss/pp
2. TS Assignment
3. Assign TS Range to Bundle
4. Assign Entire Port to Bundle
or
Assign Entire TSs to Port
TS Assignment
TIME SLOT NUM : ts 1
Bundle Number: 0
TS Type
: Voice
Dest Port :
0
Dest TS
:
0
ts 2
0
HDLC-1
0
0
ts 3
0
NC
0
0
ts 4
0
Voice
0
0
ts 5
0
SS7-1
0
0
ts 6
0
Voice
0
0
ts 7 . . . ts31
0
0
NC . . . HDLC-1
0
0
0
0
Voice Compression Modules - Data Ports

TS Assignment
Channel Number: 1
TS Type
:
NC
ts 2
1
NC
ts 3
1
NC
ts 4
1
NC
ts 5
1
NC
ts 6
1
NC
ts 7
1
NC
. . . ts31
1
NC
ts 6
1
NC
ts 7
1
NC
. . . ts31
1
NC
Other Ports
TS Assignment
Bundle Number: 1
TS Type
:
NC
ts 2
1
NC
ts 3
1
NC
ts 4
1
NC
ts 5
1
NC

1. Bundle number
2. TS type
3. Dest port
4. From TS
5. Num of TS
6. Connect the TS range to bundle
7. Disconnect the TS range from bundle

Not Supported by Data Ports
of Voice Compression Modules

1. Bundle Number
2. Connect Entire Port to Bundle
3. Disconnect Entire Port from Bundle

or
1. Sub Channel Number
2. Connect Entire Time Slots to Port
3. Disconnect Entire Time Slots from Port
For Data Ports of

Voice Compression Modules
Figure 4-16. Configuration>TS Assignment Submenu
Gmux-2000 Ver. 3.2
4-31
Monitoring
Security Key
1. Statistics
2. Status
3. Event Log
4. Alarm
Physical Layer
Statistics
Depends on Selected I/O Slot
Connection
1. Physical Layer
2. Connection
1. Bundle Current PM
2. Bundle Intervals PM
Physical Layer
Status
Connection
1. Physical Layer
2. Connection
1. Bundle Counters
Alarm Buffer Type (History)

Event Log
Read Log
1. History
2. Status
3. Both
1. Read Log
2. Clear Log
Clear Log
1. Alarm Buffer Type
2. Alarm Priority
3. Alarm Level
4. Alarm Sub-Level
5. Clear Alarms
Alarm Priority
Alarm Level
Alarm
1. Display System Alarm
2. Display PS Alarms
3. Display CL Alarms
4. Display I/O Alarms
5. Display Bundle Alarm
6. DSP All Alarms
1. SYSTEM
2. PS_A
3. PS_B
4. PS_C
5. CL_A
6. CL_B
7. IO_1
8. IO_2
9. IO_3
10. IO_4

Display PS Alarms
11. IO_5
12. IO_6
13. IO_7
14. IO_8
15. IO_9
16. BUNDLE
17. SPECIFIC
18. ALL
Display CL Alarms
Display I/O Alarms
Depends on Selection on Alarm Level

Alarm Sub-Level

DSP All Alarms
1. Slot
2. "External Port"
3. "Internal Port"
Figure 4-17. Monitoring Menu Structure
4-32
Gmux-2000 Ver. 3.2
Diagnostics
Self Test Results
1. Ping
2. Loop Back
3. APS Commands
Ping
Ping
1. Destination IP Address
2. VLAN Tagging (No)
3. Ping Repetitions
4. Trace Route
5. Send Ping
STM1
or
E1-PW/28, E1-PW-SRV/21
STM-1 Port
1. STM-1 Port
2. Local Loopback
3. Remote Loopback
VC-E1/16, VC-E1/12
Loop Back
Loop Back
Loop Back
1. Slot Number
2. STM-1 Port
2. VLAN Tagging (Yes)
3. VLAN ID
4. VLAN Priority
5. Ping Repetitions
6. Trace Route
7. Send Ping
or
1. Slot Number
2. E1 Port
or
1. Slot Number
2. E1 Port Voice
3. E1 Port Data
E1 Port
1. E1 Port
2. Local Loopback
3. Remote Loopback
E1 Port Voice
1. E1 Port
2. Local Loopback
3. Remote Loopback
4. Inject Tone (select TS)
5. Inject Tone Test
E1 Port Data
APS Commands
1. APS ID
2. Interface
3. Command
4. Activate Command
Command
1. E1 Port
2. Remote Loopback
1. Normal Operation
2. Force Flip
Figure 4-18. Diagnostics Menu Structure
Gmux-2000 Ver. 3.2
4-33
Utilities
1. File Utilities
2. Reset
3. File System
1. Client File Name

2. Server File Name
3. TFTP Server IP
4. TFTP Retry Timeout
5. TFTP Total Timeout
6. Activate TFTP
File Utilities
1. Download/Upload by TFTP
2. Internal Download
3. Internal Upload
Activate TFTP
1. File Download
2. File Upload
Internal Download
1. CL
2. I/O [1 - 9]
Internal SW Download
Internal Upload
1. CL
2. Slot's File
3. Start SW Load
1. I/O [1 - 9]
2. File Name
3. Start Upload
Reset
1. Reset CL
2. Reset I/O
3. Reboot System
Reset I/O
1. I/O [1 - 9]
2. I/O Reset
File System
1. Dir
2. Copy File
3. Rename File
4. Delete File
5. Format Disk
Dir
1. Dir Online
2. Dir Offline
3. Dir I/O
4. Dir I/O View
For CONTROL modules only

For I/O modules only
Copy File
Rename File
Delete File
Figure 4-19. Utilities Menu Structure
4-34
Gmux-2000 Ver. 3.2
4.7
Configuring Gmux-2000 via Telnet
Telnet (IP) Host Characteristics

Typically, the Telnet host is a PC or a UNIX station with the appropriate suite of
TCP/IP protocols.
To enable a Telnet host to communicate, it is necessary to configure the IP
address of the Gmux-2000 management subsystem. After this preliminary
configuration, you can use a Telnet host directly connected to the CONTROL ETH
port of the active CONTROL module in the managed Gmux-2000 to perform
additional configuration tasks.
However, after configuring the communication parameters of the Gmux-2000
management subsystem, you may also use a Telnet host located at a remote site,
the only requirement being that IP communication be established between the
LAN serving that site and the LAN connected to the active Gmux-2000 CONTROL
ETH port.
General Telnet Operating Procedures

Telnet uses the terminal utility screens for configuration. See General Terminal
Operating Procedures on page 4-15.
The only difference is that Telnet management access is possible only after
performing a preliminary configuration of the Gmux-2000 (see Table 4-2).
To prepare for using Telnet:

1. Configure the Gmux-2000 host IP address.
Note
When the Telnet host is not on a LAN directly connected to the active Gmux-2000
CONTROL ETH port, it is necessary to configure all the IP communication
parameters appearing on the Configuration>System>Host IP screen.
2. Enable Telnet access using Configuration>System>Management>Management
Access>Telnet/SSH Access as explained in the Preliminary Configuration
Session section starting on page 4-8.
4.8
Using SSH
To secure the management communications, Gmux-2000 uses SSH.

Therefore, the PC used to manage the Gmux-2000 via SSH must run an SSH client
program, for example, PuTTY (a free, widely available SSH client, running under
Windows() and other operating systems).
To prepare for using SSH:

1. Configure the Gmux-2000 host IP address.
Gmux-2000 Ver. 3.2
Using SSH
4-35
Note
When the PC running the SSH client is not on a LAN directly connected to the
active Gmux-2000 CONTROL ETH port, it is necessary to configure all the IP
communication parameters appearing on the Configuration>System>Host IP
screen.
2. Enable SSH access using Configuration>System>Management>Management
Access>Telnet/SSH Access as explained in the Preliminary Configuration
Session section starting on page 4-8.
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: 54322 (the default SSH port)
5. Open the SSH session with the Gmux-2000.

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 log in is successful, you will see the main menu.
4.9
Configuring Gmux-2000 via SNMP
Gmux-2000 can be configured by any SNMP-based network management station,

for example, RADview, provided IP communication is possible with the
management station.
To enable SNMP management, it is necessary to enable SNMP access, and
configure the SNMP management parameters.
For SNMP management instructions, refer to the Users Guide of the desired
SNMP station.
To prepare for using SNMP access:

1. Configure the Gmux-2000 host IP address and all the other IP communication
parameters (use the Configuration>System>Host IP screen).
2. Configure specific management stations using the
Configuration>System>Management>Manager List.
3. Enable SNMP access using Configuration>System>Management>
Management Access>SNMP Access as explained in the Preliminary
Configuration Session section starting on page 4-8.
4-36
Configuring Gmux-2000 via SNMP
Gmux-2000 Ver. 3.2
Chapter 5
Configuration
5.1
Overview
This Chapter provides detailed configuration instructions for Gmux-2000 systems.

In addition to the procedures given in this Chapter, a complete system
configuration also requires configuring the individual modules in accordance with
the instructions given in the Installation and Operation Manuals of each module.
Note
Appendix C describes the Gmux-2000 operating environment, and provides

technical background information on the various Gmux-2000 configuration
parameters.
The configuration activities presented in this Chapter assume that Gmux-2000 is
configured using a standard ASCII terminal, as explained in Chapter 4. If you are
not familiar with the general supervision terminal operating instructions, review
Chapter 4, in particular Sections 4.2, 4.4, and 4.5.
However, after performing the preliminary configuration of the Gmux-2000 in
accordance with Section 4.4, the same configuration activities can also be
performed by means of a Telnet host or an SNMP network management station.
Note
screens are given for illustration purposes only. They do not reflect recommended
values.
Navigation Maps
You can find a complete collection of supervision utility navigation maps in
Chapter 4. For your convenience, the relevant navigation map also appears in the
beginning section of each main configuration activity.
Gmux-2000 Ver. 3.2
Overview
5-1
Chapter 5 Configuration
Overview of Configuration Menu Structure

For your convenience, Figure 5-1 shows the structure of the Configuration menu.
Configuration
1.
2.
3.
4.
5.
System
Physical Layer
Connection
TS Assignment
Database Tools
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Physical Layer
Depends on Card Type
Connection
1.
2.
3.
4.
Bundle ID
Connection Mode
PSN Type
1.
2.
3.
4.
Card SS/PP
TS Assignment
TS Assignment
TS Assignment
or
1. Card SS/PP
2. TS Assignment
3. Assign Entire TSs to Port
Database Tools
1.
2.
3.
4.
5.
6.
Choose dB Number
Factory Default
Load Database
Load Hardware
Check Sanity
Update Database
Figure 5-1. Configuration Menu Structure
5-2
Overview
Gmux-2000 Ver. 3.2
5.2
Managing Gmux-2000 Configuration Databases
Before starting configuration activities, it is important to understand the

Gmux-2000 database tools, used to manage Gmux-2000 databases.
Overview
The Gmux-2000 can store up to 5 different databases on the CONTROL module
flash disk. There are two types of database files:
Note
Online database file: one database file serves as the current online database.
This is the file from which parameters have been downloaded to the
Gmux-2000 modules, and therefore it determines the Gmux-2000
configuration.
All the other database files (up to 4) are simply stored on the flash disk.
These files may have been created by the user using the database tools or
the file system utilities, or received by TFTP from a remote host or
management station.
Database files are named DBxCONF.ext, where x stands for the database number,
1 to 5, and ext is OL for the online file and CFG for the other files. Backup copies
of the files are automatically stored with the extension BAK.
A copy of the online database is normally loaded into the CONTROL module edit
buffer. The contents of the edit buffer are preserved until the Gmux-2000 is
powered down: on the next power-up, the edit buffer is again loaded with a copy
of the online database and therefore any unsaved changes are lost.
Any authorized user (including operators of management stations, etc.) can work
on the edit buffer without affecting the online database, for example:
Make changes to the database copy located in the edit buffer
Replace the edit buffer contents with the factory defaults
Load into the edit buffer another database file, thus also replacing the
current contents with new contents.
The online database is updated by a dedicated Update Database command, which

performs the following actions:
1. Initiate a sanity check on the edit buffer contents, and reports errors.
2. If no errors are detected, saves the edit buffer contents to the flash disk as
the online database.
3. After successfully saving the contents buffer to the flash disk, configuration
messages are automatically sent to the Gmux-2000 subsystems to change
their operating mode in accordance with the new online database.
The shortcut % UPD DB can also be used to save configuration changes, update
the online database, and activate the changes.
To navigate to the required screen, use Configuration>Database Tools.
A typical Database Tools screen is shown in Figure 5-2.
Gmux-2000 Ver. 3.2
5-3
The functions performed by means of the various options available on Database

Tools screen are explained in Table 5-1.
Pseudowire Gateway
Configuration>Database tools
1.
2.
3.
4.
5.
6.
Choose db number[1 - 5]
Factory default
Load database
Load hardware
Check sanity
Update database
... (1)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-2. Typical Database Tools Screen

Table 5-1. Database Tools
Item
Description
Choose DB Number
Select the number of the target database.

The factory defaults are provided as database 1
Factory Default
Load the factory default values into the edit buffer
Load Database
Load the database selected by means of the Choose DB Number into the edit buffer.
This database is now the candidate for becoming the online database (this will occur
after a successful Update Database command)
Load Hardware
Read the hardware (modules) installed in the Gmux-2000 and load the factory
defaults for the installed hardware in the edit buffer.
This action will not replace user-configured parameters for some I/O slots, including
those made by means of the Configuration>Card Type screen (page 5-13): in this
case, the Load Hardware command operates only on empty or unconfigured slots
Check Sanity
Check configured parameters and report errors.

A sanity check is automatically performed whenever you try to update the database,
without explicitly entering the Check Sanity command
Update Database
Copy the contents of the edit buffer to flash disk as the online database, and
change the Gmux-2000 configuration and operating mode accordingly
Using the Database Tools
To create a new database from the factory default:

The Gmux-2000 can store up to 5 different databases. However, the
factory-default is that only database 1, loaded with factory-default parameter
values, is present in the Gmux-2000 (this is also true after the CONTROL module
internal flash disk has been formatted). You can create an additional database
5-4
Gmux-2000 Ver. 3.2
(up to the maximum (5) supported by the Gmux-2000) by means of the following
procedure:
1. Select the new database number with Configuration>Database Tools>Choose
DB Number.
2. Create the desired database with Configuration>Database Tools>Update
Database.
3. Now perform the desired configuration activities.
4. When done, save the configuration using Configuration>Database
Tools>Update Database.
The following sections explain how to use the commands available on the
Database Tools screen to perform typical activities.
To reload the factory defaults:

1. Select Factory Default.
2. You will be prompted to confirm: YOU ARE ABOUT TO SET DEFAULT VALUES
TO ACTIVE DATABASE, ARE YOU SURE?:
To confirm, type y
To abort, type n
3. Select Update Database to activate the default configuration as the online

database.
To initialize a new Gmux-2000:

1. Select Factory Default.
2. Select Load Hardware.
3. You will be prompted to confirm: CONFIGURATION MAY CHANGE AFTER LOAD
HW, ARE YOU SURE?:
To confirm, type y
To abort, type n
4. Select Update Database to activate the default configuration for all the
hardware installed in the Gmux-2000.
To create an additional database starting from the online database:

1. Select Choose dB Number and select the new database number (up to 5).
2. Prepare the desired configuration.
3. Select Update Database to create and activate the new database.
To modify the online database:

1. Make the required configuration changes.
2. Select Update Database or type % to activate the new configuration.
To modify the online database starting from another existing database:

1. Select Choose dB Number and select the source database number, 1 to 5.
Gmux-2000 Ver. 3.2
5-5
2. Select Load Database.
Note
If current Gmux-2000 configuration includes APS groups, your request is rejected

and you are prompted to delete the configured APS groups: DELETE APS
CONFIGURATION BEFORE LOAD DB OPERATION! ! !. In this case, first delete the
APS groups as explained in Section 5.8, and then repeat the command.
3. If necessary, make configuration changes.
4. Select Update Database to create and activate the new database.
5.3
Table 5-2 lists the steps needed to configure a new Gmux-2000.

Table 5-2. Gmux-2000 Configuration Sequence
Step
Action
Using
Select the default database number, 1 to 5

Alternatively, configure the modules installed in Configuration>System>Card Type

the Gmux-2000
4
Configure the IP communication parameters of

the Gmux-2000 management agent
Configuration>System>Management>Management
Access
Configure specific managers and any required

static routes
Configure the Gmux-2000 logistic parameters
10
11
If necessary, configure syslog functionality:
1. Configure syslog system IP address.
Configuration>System>Syslog System Address
2. Configure syslog parameters
Configuration>System>Syslog>Syslog Configuration
1. Select the date source, and the date format Configuration>System>Date & Time>Date Source,
Date Format
2. When the internal real time clock is used,

set the time of day

5-6

parameters
Configuration>System>Date & Time>NTP Server,
GMT, Update Interval
Gmux-2000 Ver. 3.2

Step
12
Action
Using

management:
If SNMP support mode is changed, save to
activate the change before continuing
2. When SNMPv3 is disabled, configure SNMP

management parameters
Community

SNMP Engine ID
SNMPv3 users
Setting>Users
Setting>SNMPv1/v3 Mapping
13

14
15
16
Configure connection parameters for each

bundle
17
18
19
Save the final configuration in the selected

database
20
If necessary, prepare additional databases (up

to 5)
To start from an existing database, use

Repeat the relevant steps as needed to create a new
database
Gmux-2000 Ver. 3.2
5-7
5.4
Configuring System Parameters
System Parameters Configuration Sequence

To configure the Gmux-2000 system parameters, perform the following steps:
1. Program the modules installed in the Gmux-2000.
2. Configure CONTROL DCE port parameters.
3. Configure CONTROL ETH port parameters.
4. Configure the IP communication parameters of the Gmux-2000 management
agent.
5. Configure Gmux-2000 management access.
6. Configure specific management stations.
7. Configure the Gmux-2000 logistic parameters.
8. Configure the parameters needed for syslog operations.
9. Configure the Gmux-2000 real-time clock.
To configure the Gmux-2000 for SNMP management, refer to Section 5.5.
Overview of System Configuration Submenu

For your convenience, Figure 5-3 shows the structure of the System submenu.
5-8
Gmux-2000 Ver. 3.2
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Host IP
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
GbE 2/IF 1:
GbE 2/IF 2:
IP ADDRESS
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
IP MASK DEFAULT GATEWAY

0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Device Info
Syslog System Address
Sys Description
1. Sys Contact
2. Sys Name
3. Sys Location
SNMPv3 = Disabled
Management
1. Device Info
3. Manager List
6. SNMP Engine ID
1. Trap Community
2. Read Community
3. Write Community
4. Authentication Failure Trap
Manager List
IP ADDRESS NEXT HOP
INTERFACE TRAP (FOR MANAGER) VLAN VALID VLAN ID VLAN PRIORITY
172.171.75.32 255.255.255.255 CL Interface
Yes
Yes
67
6
See Part 4
NVRAM
Add
SNMP Engine ID
Date & Time
Engine ID
Engine ID Config Type
1. Rest Bytes
1. Date Source (NVRAM)

2. Date Format
Current Date & Time
3. Time Hour
4. Time Minutes
5. Time Seconds
6. Date Year
7. Date Month
8. Date Day
or
Date Format
Manager List
Manager List
1. IP Address
2. Next Hop
3. Interface
5. VLAN Valid
1. DD/MM/YYYY
2. MM/DD/YYYY
3. YYYY-MM-DD
NTP
VLAN Valid - Yes
VLAN Valid - No
or
1. IP Address
2. Next Hop
3. Interface
5. VLAN Valid
6. VLAN ID
7. VLAN Priority
INTERFACE
1. CL Interface
2. GIG A-IO 6/1
3. GIG A-IO 6/2
4. GIG B-IO 8/1
5. GIG B-IO 8/2
..
.
Date & Time

1. Date Source (NTP)
2. Date Format
Current Date & Time
4. GMT
5. Update Interval
GMT
Update Interval
Clock Source
user, tech
1. System A
Alarms
Management Access
See
Part 2
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
1. User Access
2. Telnet/SSH Access
3. SNMP Access
Web Access - Disabled
4. RADIUS Client
5. RADIUS Server
User Access
1. Old Password
2. New Password
3. Confirmation
su
User Access
1. User Name
2. Permission
3. Access
4. Old Password
5. New Password
6. Confirmation
Permission
1. Full Control
2. Read Only
3. User Change
Access
Telnet/SSH Access
Username&Password
1. Display User List
2. Restore User List
Redundancy
1. Disabled
2. Enabled
3. Managers Only
4. Enable Secure
5. Managers Only Secure
1. Terminal
2. Telnet
3. All
SNMP Access
1. CL
2. I/O
1. Disabled
2. Enabled
3. Managers Only
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
Ethernet Port
1. Speed
Card Type
RADIUS Client
1. Remote
2. Local
3. Remote&Local
See
Part 3
RADIUS Server
2. Shared Secret
3. Number of Retries
4. Timeout
5. Authentication Port
6. Accounting Port
Syslog
Figure 5-3.A. Configuration>System Submenu Structure (Part 1 of 4)
Gmux-2000 Ver. 3.2
5-9
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
Master Clock Source
SNMPv3 = Disabled
Management
1. Device Info
3. Manager List
6. SNMP Engine ID
1. Internal
2. Rx Clk
3. Ext In-1
4. Ext In-2
Master Clock
1. Master Clock Source
2. Master Clock Source SS PP
See Part 1
Rx Clk only
System A
Fallback Clock Source
1. Master Clock
2. Fallback Clock
See Part 4
Ext Clock Interface
Fallback Clock
1. None
2. Rx Clk
3. Ext In-1
4. Ext In-2
1. Fallback Clock Source

2. Fallback Clock Source SS PP
Rx Clk only
1. G.703-T1
2. G.703-E1 Balanced
3. G.703-E1 Unbalanced
4. RS-422 T1
5. RS-422 E1
Date & Time

Depends on
Date Source
Ext Out Clock Source

1. System A
Attribute
Attribute
1. Alarm Level
2. Alarm Sub-Level
3. Alarm Attributes
Clock Source
1. System A
or
Alarm Level
1. Alarm Level
2. Bundle No.
3. Alarm Attributes
Normal
Y-Cable
Priority
Alarm Attributes
Define Alm Priority
1. Define Alm Priority

2. Alarm Number
3. Alarm Priority
Alarms
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
Alarm Level
Threshold
Threshold
1. Alarm Level
2. Bundle No.
3. Alarm Threshold
Alarm Priority
or
1. Alarm Level
2. Alarm Sub-Level
3. Alarm Threshold
Alarm Sub-Level
Alarm Threshold
Redundancy
Threshold Window
1. CL
2. I/O
1. Alarm Window
Report
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
Alarm
Report Relay-1 Relay-2 Log Minor Alarm LED Major Alarm LED
Critical on Yes
Yes
Yes
Yes
Yes
Yes
Critical off Yes
N/A
N/A
Yes
N/A
N/A
Major on
Yes
Yes
Yes
Yes
Yes
Yes
Major off
Yes
N/A
N/A
Yes
N/A
N/A
Minor on
Yes
Yes
Yes
Yes
Yes
Yes
Minor off
Yes
N/A
N/A
Yes
N/A
N/A
See
Part 3
Ethernet Port
1. Speed
Connect
Input Relay
1. Input Alarm Relay
2. Connect
3. Active
4. Alarm String
Active
Card Type
Syslog
Figure 5-3.B. Configuration>System Submenu Structure (Part 2 of 4)
5-10
Gmux-2000 Ver. 3.2
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
SNMPv3 = Disabled
Management
1. Device Info
3. Manager List
6. SNMP Engine ID
See
Part 1
Redundancy Mode
CL
1. Redundancy Mode
See Part 4
1. Auto
2. CL-A
3. CL-B
Date & Time

Depends on
Date Source
Config Mode
I/O
1. None
2. 1:1 (Bidirect)
STM1
3. 1+1 (Unidirect)
GbE
4. 802.3AD
5. N+1 - PW Server Modules only
1. APS ID
add
Clock Source
1. System A
3. Ext In/Out CLK Mode
Alarms
APS Configuration
I/O
1. APS ID
2. APS Configuration
3. APS Mapping
See
Part 2
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
Name
Config Mode
Recovery Mode
Time to Restore in sec
APS Mapping
CH NUM INTERFACE PRIORITY
1
7/1
High
2
7/2
Low
Speed
Redundancy
1. 300
2. 1200
3. 2400
4. 4800
5. 9600
6. 19200
7. 38400
8. 57600
9. 115200
1. CL
2. I/O
Parity
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
Ethernet Port
1. No
2. Even
3. Odd
Speed
5. Auto Negotiation
1. Speed
Card Type
SLOT:
DB :
PS-1
PS-AC
PS-2
PS-AC
SLOT:
IO/1
DB :
VC-E1/16
Card Type
Syslog Configuration
Syslog
Recovery Mode
Revertive
Non-Revertive
1. Logging Status
3. Server UDP Port
4. Device UDP Port
5. Facility
6. Severity
SLOT:
DB :
IO/6
GbE
IO/2
Server-E1-PW
IO/7
STM_2
PS-3
PS-AC
CL-1
CL
IO/3
IO/4
CES-E1-PW Server-E1-PW
IO/8
GbE
CL-2
CL
IO/5
CES-E1-PW
IO/9
STM_2
Facility
Severity
Syslog Statistics
Total Tx Messages
Unqueued Dropped Messages
Figure 5-3.C. Configuration>System Submenu Structure (Part 3 of 4)
Gmux-2000 Ver. 3.2
5-11
System
1. Host IP
3. Management
4. Date & Time
5. Clock Source
6. Alarms
7. Redundancy
8. Serial Port
9. Ethernet Port
10. Card Type
11. Syslog
See
Part 1
SNMPv3 = Enabled
Management
1. Device Info
2. Manager List
5. SNMP Engine ID
6. SNMPv3 - Enabled
7. SNMPv3 Setting
1. usmNoAuthProtocol
2. usmHMACMD5AuthProtocol
3. usmHMACSHAAuthProtocol
Users
1.
2.
3.
4.
5.
Date & Time

Depends on
Date Source
Security Name
Privacy Protocol
Privacy Password
Privacy Protocol
1 usmNoPrivProtocol
2. usmDESPrivProtocol
Targets Params
Targets & Notify
SNMPv3 Setting
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
Summary User Table
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
1.
2.
3.
4.
5.
Name
Security Model
Security Name
Security Level
Message Processing
Model
Security Model
Target Address
1.
2.
3.
4.
Security Level
Name
IP Address
Params Name
Tag List
Notify
Clock Source
1. System A
Alarms
Trap
See
Part 2
1. Attribute
2. Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay
SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
Summary User Table

User
Initial
Security Model
USM
Security Level
noAuthNoPriv
Redundancy
1. CL
2. I/O

Address MPModel SecModel SecName SecLevel
Serial Port
1. Timeout
2. Speed
3. Data bits
4. Parity
5. Stop Bit
6. Pop Alarm
See
Part 3
Ethernet Port
1. Speed
Card Type
Syslog
Figure 5-3.D. Configuration>System Submenu Structure (Part 4 of 4)
5-12
Gmux-2000 Ver. 3.2
Programming Modules
Use the following procedure to program modules in the Gmux-2000 chassis.
You can program modules even if they are not installed in the chassis.
To navigate to the required screen, use Configuration>System>Card Type.
A typical Card Type screen is shown in Figure 5-4.
To see the navigation keys available for this screen, type ? (help).
Note
Pseudowire Gateway
Configuration>System>Card type
SLOT:
DB :
PS-1
PS-AC
PS-2
PS-AC
SLOT:
DB :
IO/1
----------
IO/2
Server-E1-PW
SLOT:
DB :
IO/6
GbE
IO/7
STM-2
PS-3
PS-AC
IO/3
CES-E1-PW
IO/8
GbE
CL-1
CL
CL-2
CL
IO/4
-----------
IO/5
-----------
IO/9
STM-2
1. -----------2. PS-AC
3. PS-DC
>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-4. Typical Card Type Screen
Module Programming Procedure
To program modules in the Gmux-2000 chassis:

1. Move the cursor to the desired slot.
2. The selections supported for this slot are automatically displayed under the
slots table. Type the item number corresponding to the desired selection and
then press <Enter>.
3. When done, type % to update the current Gmux-2000 database.
Programming Procedure for VC-E1/16, VC-E1/12 Modules

VC-E1/16, VC-E1/12 have two groups of TDM ports:
Gmux-2000 Ver. 3.2
Voice (user-side) ports
5-13
Note
Data (network-side) ports that transfer the processed users payload to the
network.
In addition to the TDM ports, VC-E1/16 and VC-E1/12 have packet ports that
enable using GbE ports as exit ports for the processed users payload.
The user can connect each group of TDM ports either to the corresponding
external PDH (E1) ports of the module, or to SDH ports located on STM1
modules. When using SDH ports, the connection is made via the Gmux-2000
internal telecom buses; each module port can be mapped to any desired TU-12.
The TDM port connections depend on the module operating mode, which is
selected by means of an internal switch (see VC-E1/16, VC-E1/12 Installation and
Operation Manual).
When a new module is programmed in the chassis, it is necessary to manually
specify the selected operating mode. This selection must match the configuration
selected by means of the internal switch.
Table 5-3 specifies the available operating modes, and identifies the module
name to be selected for each mode.
Table 5-3. VC-E1/16, VC-E1/12 Operating Modes

Designation on Card
Type Screen
User-Side (Voice) Ports
Network-Side (Data) Ports
VC16E1_UE_NE
VC12E1_UE_NE
External E1 ports
External E1 data ports
VC16E1_UE_NS
VC12E1_UE_NS
External E1 ports
SDH ports
VC16E1_US_NE
VC12E1_US_NE
SDH ports
External E1 data ports
VC16E1_US_NS
VC12E1_US_NS
SDH ports
SDH ports
Configuring Serial Port Parameters

Use the following procedure to configure the communication parameters of the
serial RS-232 port, CONTROL DCE, located on the CONTROL module.
The same set of parameters are used by both CONTROL modules.
To navigate to the required screen, use Configuration>System> Serial Port.
A typical Serial Port screen is shown in Figure 5-5. The parameters that can be
configured are explained in Table 5-4.
5-14
Gmux-2000 Ver. 3.2
Pseudowire Gateway
1.
2.
3.
4.
5.
6.
Timeout (min)[3 - 10] ...

Speed
>
Data bits[7 - 8]
...
Parity
>
Stop bit[1 - 2]
...
Pop alarm
(10)
(115200)
(8)
(No)
(1)
(No)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-5. Typical Serial Port Screen

Table 5-4. Serial Port Parameters
Parameter
Function
Values
Timeout (sec)
Controls the idle disconnect time of the

CONTROL DCE port.
The allowed range is 3 to 10 minutes.

Default: 10
After the specified timeout interval, the

current supervision terminal session is
automatically disconnected
Speed
Selects the serial port data rate
The available selections are 300, 1200, 2400,

4800, 9600, 19200, 38400, 57600 and
115200 bps.
Default: 115200
Data Bits
Parity
Selects the number of data bits in the

word format
The available selections are 7 or 8 data bits.

Default: 8
Controls the use of parity
ODD Odd parity.

EVEN Even parity.
NO Parity disabled.
Default: NO
Stop Bits
Pop Alarm
Selects the number of stop bits in the

word format
Enable/disable the automatic display of
alarms on the supervisory terminal
The available selections are 1 or 2 stop bits.

Default: 1
YES The terminal automatically displays any
event or new alarm, or change in the state of
an alarm.
NO The automatic display feature is disabled.
Default: NO
Gmux-2000 Ver. 3.2
5-15
Configuring Ethernet Control Port Parameters

Use the following procedure to configure the physical layer parameters of the
CONTROL ETH Ethernet port.
To navigate to the required screen, use Configuration>System>Ethernet Port.
A typical Ethernet Port screen is shown in Figure 5-6.
PseudoWire Gateway
1. Speed
>
(Auto Negotiation)
>
% - UPD DB
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-6. Typical Ethernet Port Configuration Screen
To configure the Ethernet port parameters:

1. Select Speed to display the selection screen.
2. Select the desired operating mode of the port on the selection screen:
Auto Negotiation auto-negotiation is enabled. Auto-negotiation is used

to select automatically the mode providing the highest possible traffic
handling capability.
10Mbps half duplex auto-negotiation is disabled, and the port operates

in the half-duplex mode at 10 Mbps (lowest capability).
10Mbps full duplex auto-negotiation is disabled, and the port operates

in the full-duplex mode at 10 Mbps.
100Mbps half duplex auto-negotiation is disabled, and the port

operates in the half-duplex mode at 100 Mbps.
100Mbps full duplex auto-negotiation is disabled, and the port operates

in the full-duplex mode at 100 Mbps (highest capability).
Configuring System-Level IP Communication Parameters

Use the following procedure to define the IP communication parameters for the
Gmux-2000 management agent, and the other IP interfaces that are installed on
the Gmux-2000 (currently, additional IP interfaces are located only on the GbE
uplink ports).
5-16
Gmux-2000 Ver. 3.2
Note that only one IP address has to be assigned to the Gmux-2000 management
agent, because at any time only one of the CONTROL modules is online (this IP
address is automatically moved when the online CONTROL module is changed).
At any time, only a maximum of two GbE ports can be active, and be assigned IP
addresses.
In addition, remember that GbE ports configured as redundancy partners use a
common IP address, which can be configured only on the primary port. Do not
configure IP communication parameters for ports that will serve as secondary
ports in an APS group.
To navigate to the required screen, use Configuration>System>Host IP.
A typical Host IP screen is shown in Figure 5-7.
Pseudowire Gateway
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
GbE 2/IF 1:
GbE 2/IF 2:
IP ADDRESS
171.2.3.5
172.3.4.5
173.4.5.6
0.0.0.0
0.0.0.0
1. Change cell
IP MASK
255.0.0.0
255.0.0.0
255.0.0.0
0.0.0.0
0.0.0.0
DEFAULT GATEWAY
171.1.1.1
172.1.1.1
173.1.1.1
0.0.0.0
0.0.0.0
... (171.2.3.5)
>
V view sanity log
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-7. Typical Host IP Screen

The parameters that can be configured by means of the Host IP screen are
explained in Table 5-5.
To configure the host IP parameters:

1. Move the cursor to the location of an interface through which you will be
managing Gmux-2000.
2. Select Change Cell.
You can now enter the desired value on the same line.
3. Enter the prescribed host IP parameters, namely the IP address, IP subnet
mask and default gateway. See Table 5-5.
Note
Each IP address must be in a different IP subnet.

4. Repeat the procedure for each prescribed interface.
Gmux-2000 Ver. 3.2
5-17
Table 5-5. Host IP Parameters

Parameter
Function
Values
IP Address
Used to enter the IP address of the

corresponding IP interface
Type the desired IP address, using the

dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
periods).
Default: 0.0.0.0
IP Mask
Used to enter the IP subnet mask of the

corresponding IP interface
Type the desired IP subnet mask, using the

dotted-quad format. Make sure to select a
subnet mask compatible with the selected IP
address, and whose binary representation
consists of consecutive ones, followed by
the desired number of consecutive zeroes.
Default: 0.0.0.0
Default
Gateway
Specifies the IP address (usually an IP router

port) to which the corresponding IP interface
will send packets when the destination IP
address is not within the subnet specified in
the IP Mask field. The default value, 0.0.0.0,
means that no default gateway is defined

dotted-quad format. Make sure that the IP
address address is within the subnet of the
host IP address.
Default: 0.0.0.0
Configuring Management Access and Users

Use the following procedures to control access to the Gmux-2000 management
functions. The functions that can be performed are as follows:
Control globally the access to the Gmux-2000 management agent using SNMP
and Telnet. This is performed directly on the Management Access screen. This
capability enables to block the desired access options at the Gmux-2000
level, overriding the access rights of any user that may be logged on the
Gmux-2000. You can also enable remote access only from managers
configured on the Manager List.
Manage the Gmux-2000 users list, and their authorizations and access rights.
The required parameters are configured starting with the User Access screen
(reached from the Management Access screen). Existing users and their
passwords can be displayed, and reset when necessary to the factory default
list, using Configuration>System>Management>Username&Password.
Select the user authentication method, and configure the parameters needed
to access a remote RADIUS server.
The supervisory terminal can always be used to access the Gmux-2000

management agent, except for users specifically denied this capability.
Note
This Gmux-2000 version does not support Web access, and therefore this option
is set to Disabled and cannot be changed.
To navigate to the required screen, use Configuration>System>Management>
Management Access.
5-18
Gmux-2000 Ver. 3.2
Configuring Global Management Access Rights

A typical Management Access screen is shown in Figure 5-8.
Pseudowire Gateway
Configuration>System>Management>Management access
1. User Access
2. Telnet/SSH access
3. SNMP access
Web access
4. RADIUS Client
5. RADIUS server
>
>
>
>
>
>
(Enabled)
(Enabled)
(Disabled)
(Remote&Local)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-8. Typical Management Access Screen

Note
After activating changes to the global management access rights, your session
may be terminated. In this case, it is necessary to log in again using one of the
allowed access types.
To configure the global management access parameters:
1. Configure Telnet/SSH Access. You can select one of the following options:
Disabled access by Telnet and SSH is blocked
Enabled access is allowed to any logged Telnet user
Managers Only access, using either Telnet or SSH, is allowed only to the
authorized managers, configured by means of Management>Manager List
Enable Secure only secure access (SSH) is allowed, but access is not
restricted to managers configured by means of Management>Manager
List
Managers Only Secure only secure (SSH) access is allowed, and access
is restricted to managers configured by means of Management>Manager
List.
2. Configure SNMP Access:
Disabled access is blocked
Enabled access is allowed to any logged user
Managers Only access is allowed only to the authorized management

stations, configured by means of Management>Manager List.
3. When done, type % to update and then confirm the action.
Gmux-2000 Ver. 3.2
5-19
Note
You can type S to save the changes in the edited database. To update the active
database, type %.
Configuring User Access Rights

Users at the administrator level can manage the users list and their
authorizations and access rights as explained below.
To display the existing users, and restore the factory-default list of users and
authorizations, refer to the Managing Existing Users section on page 5-23).
To manage the users list and their authorizations and access rights:
1. Select User Access and then press <Enter> to display the User Access screen.
A typical User Access screen is shown in Figure 5-9.
Pseudowire Gateway
Configuration>System>Management>Management access>User Access
1.
2.
3.
4.
5.
6.
User Name
Permission
Access
Old Password
New Password
Confirmation
...
>
>
...
...
...
(su)
(Full Control )
(All )
()
()
()
>
F - next; B - prev; R - remove
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical User Access Screen for Administrators

Pseudowire Gateway
Configuration>System>Management>Management access>User Access
1.
2.
3.
4.
User Name
Old Password
New Password
Confirmation
...
...
...
...
(user)
()
()
()
>
F - next; B - prev; R - remove
1 M/ 1 C
-----------------------------------------------------------------------------
B. Typical User Access Screen for Other Levels

Figure 5-9. Typical User Access Screens
5-20
Gmux-2000 Ver. 3.2
Note
Any user can change his own password.

To change the password of an existing user:
1. Skip this step if you want to change your own password:
Select User Name, type the name of the desired user and then press <Enter>.
2. Select Old Password. Now enter the current password, to verify your
authorization, and then press <Enter>.
Note
Password characters are not displayed on the screen (only an asterisk * appears
for each character you type).
3. If your password is accepted, select New Password. Enter the new password
(4 to 8 characters), and then press <Enter>. Pay attention to case.
4. Select Confirmation and then type the new password a second time for
confirmation. Press <Enter> when done.
5. To save the new user definitions in the edited database, select Save All.
6. To update the active database, and thus activate the new user definitions,
type % to save and then confirm the action.
Note
To add a new user/change the current authorizations of an existing user:
Only the administrator can add new users, or change the current authorizations
of other users. For example, the factory-default user name su has this authority.
1. Skip this step if you want to change your own password:
Select User Name, type the name of the desired user and then press <Enter>.
If this is a new name, it will be added to the users list after the configuration
is completed and saved.
2. Select Permission to display the screen that controls what the user can do.
A typical screen is shown in Figure 5-10. The current level is displayed in
the screen header.
Pseudowire Gateway
...>Management>Management access>User Access>Permission
(Full Control )
1. Full Control
2. Read Only
3. User Change
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-10. Typical Permission Screen

Gmux-2000 Ver. 3.2
5-21
3. Select the desired authorization level and then press <Enter> to close the
screen. The various levels are as follows:
Full Control
Can perform all the activities (administrator level). For

example, this permission corresponds to the factory-default
user name su.
Read only
Can perform only activities that do not affect equipment

configuration and service, for example, can read the
equipment configuration parameters but cannot modify
them. This permission corresponds to the factory-default
user name user.
User Change
User with special authorizations, reserved for RAD technical

support personnel.
4. Select Access to display the screen that controls the individual access rights
of the user. A typical screen is shown in Figure 5-11. The current access level
is displayed in the screen header.
5. Select the desired access options and then press <Enter> to close the screen.
The default is All: any other selection restricts this user to one of the other
options on the screen. For example, selecting Telnet permits this user access
only by Telnet and SSH, but log in using a supervision terminal will fail.
Notes
The Gmux-2000 will block SNMP, SSH and/or Telnet access from any user,
irrespective of the users access rights, if such access has been globally
disabled by means of the Management Access screen.
Access by means of Web browsers is always disabled.
6. To assign a password/change the existing password, use the procedure on
the previous page.
Pseudowire Gateway
Configuration>System>Management>Management access>User Access>Access
(All )
1. Terminal
2. Telnet
3. All
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-11. Typical Access Screen
5-22
Gmux-2000 Ver. 3.2
Managing Existing Users

Users at the administrator level can display the existing users, and restore the
factory default list of users, thereby deleting any manually-configured users (for
example, this authority is available to the factory-default user name su).
Note
The restore function also deletes any changes to the factory default user
passwords.
Username&Password.
A typical task selection screen is shown in Figure 5-12.
PseudoWire Gateway
Configuration>System>Management>Username&Password
1. Display user list
2. Restore user list
[]
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-12. Typical Username&Password Screen
To display the list of currently configured users:

1. Select Display User List.
A typical screen is shown in Figure 5-13.
PseudoWire Gateway
Configuration>System>Management>Username&Password >Display user list
Username
SU
USER
user
tech
Password
1234
1234
debug
1234
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-13. Typical Display User List Screen
Gmux-2000 Ver. 3.2
5-23
To restore the list of currently configured users:

1. Select Restore User List.
Configuring the User Authentication Method

Gmux-2000 provides the following user authentication methods:
Local authentication: the user log in parameters (name and password) are
checked by the local Gmux-2000 management subsystem, using the list of
users configured by the administrator by means of Management Access>User
Access (see page 5-20).
Remote authentication: the local Gmux-2000 management subsystem sends

the user log in parameters to the RADIUS server configured by means of the
RADIUS Server screen. The user is allowed access to the management
functions only after its log in is authenticated by the RADIUS server.
If the RADIUS server IP address is not within the IP subnet of the local
CONTROL ETH port, make sure to prepare a static route to its IP address,
using Configuration>System>Manager List.
Note that in case network conditions do not permit IP address with the
RADIUS server, or congestion delays the response beyond the preset
time-out, log in will fail.
Remote and local authentication: the local Gmux-2000 management

subsystem first attempts to authenticate the user by means of the
configured RADIUS server. If the server does not answer within the preset
time-out (approx. 10 seconds), the management subsystem switches to local
authentication. This ensures that an authorized user can log in even if the
RADIUS server cannot be contacted.
To select the user authentication method:

1. On the Management Access screen (Figure 5-8), select RADIUS Client to
display the authentication method selection screen.
2. Select the prescribed authentication method.
3. If you select Remote or Remote&Local, you will see an additional option of
the Management Access screen, RADIUS Server, used configure the
parameters needed for secure communication with the prescribed RADIUS
server.
4. Select RADIUS Server to display the configuration screen.
A typical screen with the default parameter values is shown in Figure 5-14.
The parameters that can be configured by means of the RADIUS Server screen
are explained in Table 5-6.
Note
5-24
After changing the user authentication method, the database is automatically

updated, without requiring a manual UPD DB command. When the update is
completed, you will see a DB SUCCESSFULLY UPDATED message.
Gmux-2000 Ver. 3.2
PseudoWire Gateway
Configuration>System>Management>Management access>RADIUS server
1.
2.
3.
4.
5.
6.
Server IP Address
Shared Secret
Number of Retries[0 - 5]
Timeout (in seconds)[1 - 60]
Authentication Port[1 - 4094]
Accounting Port[1 - 4094]
...
...
...
...
...
...
(0.0.0.0)
()
(3)
(3)
(1812)
(1813)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-14. Typical RADIUS Server Configuration Screen
Table 5-6. RADIUS Server Configuration Parameters

Parameter
Function
Values
Server IP Address
Used to enter the IP address of the

prescribed RADIUS server

periods).
Default: 0.0.0.0
Shared Secret
Used to enter the key needed for

setting up a secure communication
session with the prescribed RADIUS
server
Alphanumeric string of up to 32 characters.

The string is case-sensitive.
Default: Empty string
Number of Retries Used to specify the number of times

Gmux-2000 should repeat the session
setup attempts, if the server does
respond within the specified timeout
The allowed range is 0 (no retry) to 5.
Timeout
Used to specify the time Gmux-2000

should wait for the server response
before aborting the current session
setup attempt
The allowed range is 1 to 60 seconds
Authentication
Port
Used to specify the number of the port

to be used for RADIUS authentication
sessions
The allowed range is 1 to 4094.
Accounting Port
Used to specify the number of the port

to be used for RADIUS accounting
sessions
Gmux-2000 Ver. 3.2
Default: 3
Default: 3
Default: 1812
Default: 1813
5-25
Configuring Manager List Parameters

The Manager List screen is used to configure:
Managers (for example, Telnet/SSH hosts or network management stations)

that may manage the Gmux-2000, and the parameters controlling their
access.
Static routes needed by traffic directed through the GbE ports
The total number of entries (managers and static entries) supported by the
Gmux-2000 is 100, where the maximum number of managers is 10.
Note
You must include in the manager list all the IP addresses to which you want to
send pings, and all the static routes that may be needed for GbE ports to reach
destination IP addresses which are not within the IP subnet of an exit port. in
particular, make sure to include routes for the RADIUS server. For static routes,
make sure to disable trap sending.
Manager List.
A Manager List screen, as seen when first opened, is shown in Figure 5-15.
Pseudowire Gateway
Configuration>System>Management>Manager list
IP ADDRESS
NEXT HOP
INTERFACE
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-15. Factory-Default Manager List Screen

Each screen page can include up to five entries. When more than five entries are
configured, type CTRL+D to continue to the next page.
Note
To add a new manager/define a static route to a new destination:
1. Type a and then press <Enter> to display the new manager configuration
screen. Typical screens are shown in Figure 5-16 and Figure 5-17.
2. Select each parameter in sequence, and configure the desired value using the
guidelines in Table 5-7.
3. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new manager/static route.
5-26
Gmux-2000 Ver. 3.2
4. To display the Manager List screen again, press <ESC>.

After managers/static routes are configured, the Manager List screen
comprises three sections, each displaying part of the configured information.
Use the left and right arrows to display the left, middle, or right section.
Figure 5-18 shows typical sections of the same page.
5. Repeat the process until all the desired managers/static routes have been
defined.
6. When done, type S to save.
PseudoWire Gateway
1.
2.
3.
4.
5.
IP ADDRESS
NEXT HOP
INTERFACE
TRAP
VLAN VALID
VLAN ID[1 - 4094]
VLAN PRIORITY[0 - 7]
... (172.35.56.32)
... (172.35.56.89)
>
(CL Interface)
(No)
(No)
... (0)
... (0)
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-16. Typical Add New Manager Screen (CL Interface with VLAN Tagging Disabled)
PseudoWire Gateway
1.
2.
3.
4.
5.
6.
7.
IP ADDRESS
NEXT HOP
INTERFACE
TRAP
VLAN VALID
VLAN ID[1 - 4094]
... (172.35.56.32)
... (172.35.56.89)
>
(CL Interface)
(No)
(Yes)
... (0)
... (0)
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-17. Typical Add New Manager Screen (CL Interface with VLAN Tagging Enabled)
Gmux-2000 Ver. 3.2
5-27
Table 5-7. Manager List Parameters

Parameter
Function
Values
IP Address
Used to enter the manager/destination IP

address of the entry

dotted-quad format (four groups of digits in the
Default: 0.0.0.0
Next Hop
Interface
Specifies an IP address to which the traffic

will be sent, to enable reaching this
manager/destination. This is usually the
address of an IP router port.
Type in the next hop IP address using the

dotted-quad format.
You need to specify a next-hop IP address

only when the destination address is not
within the IP subnet of the selected
interface
Default: 0.0.0.0
Selects the interface through which traffic

is sent to this manager/destination.
CL INTERFACE Traffic to this station will be sent

through the CONTROL ETH port of the CONTROL
module.
When the Gmux-2000 includes a voice

compression module (or such modules are
programmed in the database), you may also
see in the list of selectable interfaces the
programmed voice compression modules:
these interfaces can be used only to
manage inband RAD Vmux Voice Trunking
Gateway equipment connected to the
external data ports of the voice
compression modules. At this stage, it is
not recommended to configure such
interfaces
To use the default gateway, leave this field at

the default value, 0.0.0.0.
GIG
GIG
GIG
GIG
A-I/O 6/1
A-I/O 6/2
B-I/O 8/1
B-I/O 8/2
Traffic to this station will be

sent through the corresponding
module and port (identified by
GbE the I/O slot and port).
When GbE port redundancy is
used, make sure to select only
primary ports.
VMUX SLOT SL List of VC-E1/16 and VC-E1/12

programmed in the Gmux-2000 that can be used
to manage equipment from the RAD Vmux family
of Voice Trunking Gateways using inband
communication through VC-E1/16/VC-E1/12 data
ports.
Default: CL INTERFACE
Trap
VLAN Valid
5-28
Specifies whether traps will be sent to this

manager/destination in case an alarm
report will result in the generation of a
trap.
Do not enable trap sending to destinations
which are not management stations (you
can enable trap sending for a maximum of
10 IP addresses)
YES Gmux-2000 will send traps to this

manager.
Controls the use of VLAN tagging for

Gmux-2000 traffic exchanged with this
manager/destination.
YES Management VLAN tagging is enabled.

When you select YES, the screen changes to
include the VLAN configuration fields.
This is generally required for management

traffic
NO Management VLAN tagging is disabled.
NO Gmux-2000 will not send traps to this

destination.
Default: NO
Default: NO
Gmux-2000 Ver. 3.2
Parameter
Function
Values
VLAN ID
When VLAN tagging is enabled, specifies

the VLAN ID number used by the traffic
exchanged with this station.

Default: 1
When VLAN tagging is disabled, this

parameter cannot be changed. You can
however see the currently configured value,
which takes effect after you enable VLAN
tagging
VLAN Priority When management VLAN tagging is
enabled, specifies the priority assigned to
the management VLAN traffic exchanged
with this station.
The allowed range is 7 (highest priority) to 0

(lowest priority).
Default: 0
When VLAN tagging is disabled (VLAN Valid

is NO), this parameter cannot be changed.
You can however see the currently
configured value, which takes effect after
you enable VLAN tagging
Pseudowire Gateway
IP ADDRESS
172.171.75.32
->>
1. Change cell
NEXT HOP
172.35.56.89
INTERFACE
CL Interface
... (172.171.75.32)
>
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical Leftmost Section
Gmux-2000 Ver. 3.2
5-29
Pseudowire Gateway
IP ADDRESS
172.171.75.32
<<- ->>
1. CL Interface
2. GIG A-IO 8/1
3. GIG A-IO 8/2
4. GIG B-IO 9/1
5. GIG B-IO 9/2
6. VMUX SLOT 4
NEXT HOP
172.35.56.89
INTERFACE
CL Interface
TRAP(FOR MANAGER)
Yes
>
1 M/ 1 C
-----------------------------------------------------------------------------
B. Typical Middle Section

Pseudowire Gateway
TRAP(FOR MANAGER) VLAN VALID VLAN ID VLAN PRIORITY
Yes
Yes
67
6
<<1. Change cell [0 - 7]
... (6)
>
1 M/ 1 C
-----------------------------------------------------------------------------
C. Typical Rightmost Section

Figure 5-18. Typical Manager List Screen (after Adding First Manager)
To edit an existing manager/static route destination:

1. Use the left and right arrows to move the selection block to the desired cell
in the row of the entry to be edited.
2. Select Change Cell to open the corresponding field for editing. Use the
procedure described above to select a new value for the selected field.
3. When done, type S to save.
Configuring Logistic Parameters

Use the following procedure to specify logistic information that can be used to
identify the specific Gmux-2000 unit, provide contact information for operators
of management stations, etc.
Note
5-30
The details appearing on your screen may differ from those shown below.
Gmux-2000 Ver. 3.2

Device Info.
A typical Device Info screen is shown in Figure 5-19. The information that can be
defined using this screen is described in Table 5-8.
Pseudowire Gateway
Configuration>System>Management>Device info
Sys description...
1. Sys contact
...
2. Sys name
...
3. Sys location
...
(Gmux-2000: Hw Version: 1.00, Sw Version: 3.20)

()
()
()
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-19. Typical Device Info Screen

To configure an entry:
1. Select the desired entry.

2. Type the appropriate text (free text string, may include up to 32 characters).
3. When done, press <Enter>.
Table 5-8. Device Info Parameters

Parameter
Function
Values
Sys Description
Displays manufacturer-provided data on this Gmux-2000
Device type, hardware

version, and software version
Sys Contact
Specify contact information for the person/organization in

charge of this unit
Sys Name
Assign a logical name to this unit
Sys Location
Specify location information for this unit
Up to 32 alphanumeric
characters for each entry.
Configuring Syslog Functionality

Configuring Syslog System Address
The local (source) IP address used by the Gmux-2000 management subsystem for
communication with a remote syslog server, referred to as the syslog system
address, can be selected independently of the host IP address.
Gmux-2000 Ver. 3.2
5-31
Make sure to include the additional static routes for communication with the
syslog server (particular attention is required when the syslog system address is
not within the subnet of the host IP address).
Note
You can modify the syslog system address only when the syslog logging function
is disabled (see the Configuring Syslog Server Parameters section below).
To configure the syslog system address:
1. Navigate to Configuration>System.
2. Select Syslog System Address.
You can now enter the desired IP address on the same line.
Configuring Syslog Server Parameters

Use the following procedures to:
Enable/disable syslog logging (the reporting of events to the remote server)
Configure the syslog server address and its service ports. Make sure to add
the required static routes using Configuration>System>Management>
Manager List
Configure the logging parameters.
Note that the syslog server IP address and its service ports can be changed only
when syslog logging function is disabled
To configure syslog server parameters:

1. Navigate to the Configuration>System screen.
2. Select Syslog to display the syslog task selection screen.
A typical Syslog task selection screen is shown in Figure 5-20.
PseudoWire Gateway
Configuration>System>Syslog
1. Syslog configuration>
2. Syslog statistics
>
>
V - view sanity log
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-20. Typical Syslog Task Selection Screen

5-32
Gmux-2000 Ver. 3.2
3. Select Syslog Configuration.

You will see the Syslog Configuration screen. A typical screen is shown in
Figure 5-21.
Table 5-9 explains the parameters configured by means of this screen.

PseudoWire Gateway
Configuration>System>Syslog>Syslog configuration
1.
2.
3.
4.
5.
6.
Logging status
Server IP Address
Server UDP Port
Device UDP Port
Facility
Severity
>
...
...
...
>
>
(Enable)
(1.2.3.8)
(514)
(514)
(Local 1)
(Minor)
>
V - view sanity log; S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-21. Typical Syslog Configuration Screen

Table 5-9. Syslog Configuration Parameters
Parameter
Function
Values
Logging Status
Enables/disables logging on the remote

syslog server
ENABLE Logging is enabled, and the

DISABLE The logging service is disabled.
Make sure to select this state before
changing the syslog system IP address, the
server IP address, and/or the service UDP
ports.
Default: ENABLE
Server IP Address
Specifies the syslog server IP address.

Make sure to change the default IP
address to a valid single-node address:
do not select multicast or broadcast IP
addresses
Server UDP Port
Specifies the syslog server UDP port (the

port on which the syslog server expects
reports).
The allowed range is 0.0.0.0 to

255.255.255.255.
Default: 0.0.0.0

Default: 514
The default value, 514, matches the

RFC3164 default address.
Gmux-2000 Ver. 3.2
5-33
Device UDP Port
Specifies the local UDP port through

which syslog reports are sent.

Default: 514
The default value, 514, matches the

RFC3164 default address.
It is recommended to use the same value
as for the Server UDP Port
Facility
Specifies the specific internal Gmux-2000 The allowed range is Local 1 to Local 7.
management task or function from which Default: Local 1
syslog messages are sent to the remote
server.
RFC3164 specifies a standardized set of
facility codes. The facility code selected
by means of this parameter is a RAD
specific facility code, which is used in
addition to the RFC3164 facility codes
Severity
Defines the severity filtering function:

only events having a severity equal or
exceeding the configured level will be
sent to the syslog server.
See Table 5-10 for details
RFC3164 specifies a standardized set of

severity codes. RAD equipment uses a
slightly different severity scale, which is
compared in Table 5-10 with the
RFC3164 severity codes
Table 5-10. Syslog Configuration Severity Parameters

Severity
Description of Severity Condition
RAD Severity
Code
Emergency
System is unusable
Alert
Action must be taken immediately
Critical
Critical
Critical conditions
Major
Error
Error conditions
Minor
Warning
Warning conditions
Warning
Notice
Normal but significant condition
Event
Informational
Informational messages, no action required
Info
Debug
Debug
Debug-level messages
Displaying Syslog Statistics

Gmux-2000 enables to display the syslog reporting statistics. These statistics are
continuously collected while logging is enabled.
5-34
Gmux-2000 Ver. 3.2
The collected statistics are discarded when Gmux-2000 is turned off, and also
when it is reset. You can also manually reset the statistics by typing c (the reset
counters command).
To display syslog statistics:

1. Navigate to the Configuration>System screen.
2. Select Syslog to display the syslog task selection screen.
3. Select Syslog Statistics.
A typical Syslog Statistics screen is shown in Figure 5-22.
Table 5-11 explains the syslog statistic parameters.

PseudoWire Gateway
Configuration>System>Syslog>Syslog statistics
Total Tx Messages... (128)
Unqueued Dropped Messages... (7)
>
V - view sanity log; C - reset counters
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-22. Typical Syslog Statistics Screen

Table 5-11. Syslog Statistics Parameters
Parameter
Function
Total Tx Messages
Displays the number of messages transmitted by Gmux-2000 to

the syslog server
Unqueued Dropped
Messages
Displays the number of messages that could not be queued for

transmission to the syslog server by Gmux-2000
Configuring Date & Time

Use the following procedures to:
Select the date format displayed on the Gmux-2000 screens.
Select the method (source) used to synchronize the internal real-time clock
of the Gmux-2000. You have the following options:
Gmux-2000 Ver. 3.2
Manual setting of the initial date and time (identified as the NVRAM
method). After the initial setting, the internal clock is free running
5-35
Use the NTP (Network Time Protocol) to periodically synchronize the

internal clock to the accurate time provided by the worldwide network of
NTP time servers (identified as the NTP method). In the interval between
consecutive updates, the internal clock is free running
In accordance with the selected time synchronization method, perform the

following related tasks:
Manually update the time-of-day and date of the internal real-time clock
Configure the IP address of the desired NTP server, select a time zone,
and an update interval
Both screens display the current time and date provided by the Gmux-2000 clock.
Note
The internal real-time clock is used to time-stamp various messages, alarms, etc.
The previously attached time stamps are not changed when the time-of-day is
changed as a result of updates.
To navigate to the required screen, use Configuration>System>Date & Time:
A typical Date & Time screen for the manual method is shown in Figure 5-23.
A typical Date & Time screen for the NTP method is shown in Figure 5-24.
Pseudowire Gateway
Configuration>System>Date & Time
1. Date source
2. Date format
Current date & time
3. Time hour[0 - 23]
4. Time minutes[0 - 59]
5. Time seconds[0 - 59]
6. Date year[2002 - 2099]
7. Date month[1 - 12]
8. Date day[1 - 31]
9. Save date & time
>
>
...
...
...
...
...
...
...
(NVRAM [Internal])
(YYYY-MM-DD)
( 2000-07-11
18:47:41
(18)
(47)
(41)
(2000)
(7)
(11)
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-23. Typical Date & Time Screen (Internal Clock NVRAM Source)
5-36
Gmux-2000 Ver. 3.2
PseudoWire Gateway
Configuration>System>Date & Time
1. Date source
2. Date format
Current date & time
4. GMT (+/- XX)
5. Update interval[1 - 1440]
6. Save date & time
>
>
...
...
>
...
(NTP
[External])
(YYYY-MM-DD)
( 2000-07-11
18:47:41
(0.0.0.0)
( 0 [GMT])
(1440)
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-24. Typical Date & Time Screen (External NTP Source)
To select the Gmux-2000 date format:

1. Select Date Format.
2. On the Date Format screen, type the number corresponding to the desired
date format and then press <Enter>.
Note
dd stands for day, mm for month and yyyy for year.

3. When done, type % to save and then confirm the action.
To select the Gmux-2000 date source:

1. Select Date Source.
2. On the Date Source screen, type the number corresponding to the desired
source: NVRAM (Internal) or NTP (External), and then press <Enter>.
The screen is automatically changed in accordance with the selected
source (either Figure 5-23 or Figure 5-24).
To set the time and/or date (NVRAM (Internal) source only):

1. Each component of the time of day and date is separately set. To change,
select the desired item and then type the desired value:
Gmux-2000 Ver. 3.2
Time Hour
Time Minutes
Time Seconds
Date Year
Date Month
Date Day
5-37
Notes
Confirm each change by pressing <Enter>.
When done, select Save Date and Time.
Time must be entered in the 24-hour format.

It is recommended to set the time about one minute beyond the desired time,
and then save at the correct instant.
To specify the NTP parameters (NTP (External) source only):

1. Select NTP Server IP Address, type the IP address of the prescribed NTP
server, using the quad-dot format, and then press <Enter>.
2. Select your time zone, by specifying the difference between your local time
and Greenwich Mean Time (GMT):
1. Select GMT.
2. You will see the selection screen (a typical screen is shown in
Figure 5-25). The screen presents all the available options (-12 to +12
hours), where each option is illustrated by a well-known geographical
location, or time zone description, when available.
3. Select the appropriate option, and then press <Enter>.
4. Select Update Interval to change the interval between automatically
initiated time-of-day synchronization requests: you can select any interval
in the range of 1 to 1440 minutes.
5. Select Save Date and Time. The Current Date & Time field on the Date &
Time screen is updated.
PseudoWire Gateway
Configuration>System> Date & Time >GMT (+/- XX) ( 0
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
-12
-11
-10
-9
-8
-7
-6
-5
-4
-3
[Date Line West]

[Midway Island]
[Hawaii]
[Alaska]
[Pacific Time]
[Mountain Time]
[Central Time]
[Eastern Time]
[Atlantic Time]
[Brasilia]
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
-2
-1
0
+1
+2
+3
+4
+5
+6
+7
[GMT])
[Mid-Atlantic] 21. +8 [Beijing,Hong-Kong]

[Cape-Verde]
22. +9 [Tokyo,Seoul]
[GMT]
23. +10 [Melbourne,Sydney]
[Rome,Paris]
24. +11 [Magadan,Solomon Is]
[Jerusalem,Kyiv] 25. +12 [Auckland,Fiji]
[Moscow,Riyadh]
26. +13 [Nuku'alofa]
[Abu Dhabi,Tbilisi]
[Tashkent,Islamabad]
[Almaty,Astana]
[Bangkok,Jakarta]
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-25. Typical Time Zone (GMT) Selection Screen (NTP Source)
5-38
Gmux-2000 Ver. 3.2
5.5
Configuring Gmux-2000 for SNMP Management
Gmux-2000 can be configured for management with or without the security

features of SNMPv3 (refer to Appendix C for a description of the SNMP protocol
and its versions).
The following setions explain:
How to enable or disable the SNMP security features
How to configure Gmux-2000 for management without security features, for

compatibility with SNMP support in previous Gmux-2000 and management
station versions
How to configure Gmux-2000 for management with SNMPv3 security features
Enabling/Disabling SNMPv3 Security Features

When starting the SNMP configuration activities, the first action is to select
whether to enable or disable the SNMPv3 security features: this action effects all
the other SNMP parameters, and therefore, when changing the support mode, all
the SNMPv3 settings are erased, and the factory defaults are restored.
To enable the SNMPv3 security features:

1. Navigate to Configuration>System>Management.
A typical Management screen with SNMPv3 security features disabled (the
factory default state) is shown in Figure 5-26.
PseudoWire Gateway
Configuration>System>Management
1.
2.
3.
4.
5.
6.
7.
Device info
Manager list
Management access
Username&Password
SNMP Engine ID
SNMPv3
>
>
[]>
>
>
>
(Disabled)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-26. Typical Management Screen (SNMPv3 Disabled)

2. To change the state, select SNMPv3: the state is toggled to Enabled, and a
S Save item is added.
3. To activate the selection, type s. The screen is refreshed and the following
changes occur:
Gmux-2000 Ver. 3.2
The Authentication/Community item is removed, as it is no longer

relevant for SNMPv3.
5-39
The SNMPv3 Setting item, used to access the SNMPv3 configuration tasks
(see the Configuring SNMP Management with SNMPv3 Security section) is
added.
A typical Management screen with SNMPv3 security features enabled is
PseudoWire Gateway
Configuration>System>Management
1.
2.
3.
4.
5.
6.
7.
8.
Device info
Manager list
Management access
Username&Password
SNMP Engine ID
SNMPv3
SNMPv3 setting
>
>
[]>
>
>
>
(Enabled)
>
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-27. Typical Management Screen (SNMPv3 Enabled)
To disable the SNMPv3 security features:

2. To change the state, on the screen of Figure 5-27 select SNMPv3. You are
prompted to confirm by a message that explains the effects: ALL SV3
SETTINGS WILL BE ERASED, ARE YOU SURE?
3. You are prompted to confirm by a message that explains the effects: ALL SV3
SETTINGS WILL BE ERASED, ARE YOU SURE?
4. To abort, type n; to confirm, type y.
5. After typing y, the SNMPv3 state is toggled to Disabled, and a S Save item
is added.
6. To change the state, select SNMPv3: the state is toggled to Disabled, and a
S Save item is added.
7. To activate the selection, type s. The screen is refreshed and changes back to
Figure 5-26.
Configuring for SNMP Management without SNMPv3 Security

Configuring Authentication and Communities
Use the following procedure to specify the communities under which the
Gmux-2000 management agent will accept SNMP commands, and control the
generation of a security alert traps in case commands are received from an
unauthorized entity.
5-40
Gmux-2000 Ver. 3.2

Authentication/Community.
A typical Authentication/Community screen is shown in Figure 5-28. Table 5-12
explains the parameters configured by means of this screen.
Pseudowire Gateway
Configuration>System>Management>Authentication/Community
1.
2.
3.
4.
Trap community
Read community
Write community
Authentication failure trap
...
...
...
>
(public)
(public)
(private)
(Off)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-28. Typical Authentication/Community Screen

Note
The community names are case-sensitive.

Table 5-12. Authentication/Community Parameters
Parameter
Function
Values
Trap Community Type in the name of the SNMP community

under which the SNMP agent will send all
the traps
Up to eight alphanumeric characters.
Read Community Type in the name of the SNMP community

that has read-only authorization (the
SNMP agent will accept only getRequest
and getNextRequest commands from
management stations using that
community)
Write
Community
Type in the name of the SNMP community

that has read-write authorization (the
SNMP agent will accept setRequest
commands from management stations
using that community)
Authentication
Failure Trap
Select whether to send or not an

ON Send authentication failure trap.
authentication failure trap in case an SNMP OFF Do not send authentication failure trap.
request with invalid community is received
Default: OFF
Gmux-2000 Ver. 3.2
Default: public
Default: public
Default: private
5-41
Configuring SNMP Engine ID

The SNMP engine ID is a parameter defined in relation with SNMPv3, whose
primary function is to provide a unique and unambiguous identifier of the local
SNMP engine (processor), part of the Gmux-2000 management subsystem. Thus,
it thus also identifies the local Gmux-2000.
SNMPv3 bases the generation of its session keys on several parameters, one of
them being the SNMP engine ID. Therefore, the SNMP engine ID must always be
configured before configuring any other SNMPv3 parameters, and in particular
before configuring users (if you change the SNMP engine ID, you must also
reconfigure the users). Thus, you can configure the SNMP engine ID even when
SNMPv3 support is disabled.
The SNMP engine ID is a string that has an automatically-generated part, and a
user-defined part, which must be unique within the SNMP-managed network.
To specify the SNMPv3 Engine ID:

2. Select SNMPv3 Engine ID.
A typical SNMP Engine ID screen is shown in Figure 5-29. The SNMP
engine ID is a string that has an automatically-generated part, and a userdefined part. The Engine ID field displays the automatically-generated
part of the SNMP engine ID string. As indicated in the Engine ID Config
Type field, Gmux-2000 supports text entry for the user-defined part.
3. To modify the user-defined part, which must be unique within the SNMPmanaged network,1 select Rest Bytes, and.
4. Type the prescribed string, which must comprise 4 to 27 alphanumeric
characters, and then press <Enter> to confirm. Note that the string is added
to the Engine ID field (if the string is too long for the available display space,
it is truncated, in which case the last digits are replaced by an ellipsis )
5. Note that an S Save item is added: to activate the new engine ID, type s.
PseudoWire Gateway
Engine ID
... (800000a40400000000 )
Engine ID Config Type >
(Text)
1. Rest Bytes
... ()
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-29. Typical SNMP Engine ID Screen
5-42
Gmux-2000 Ver. 3.2
Configuring SNMP Management with SNMPv3 Security

The SNMPv3 parameters are configured by means of the SNMPv3 Setting
submenu.
A typical SNMPv3 Setting submenu is shown Figure 5-30. The parameters that can
be configured are explained in Table 5-13.
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting
1.
2.
3.
4.
5.
6.
Engine Boots
Engine Time
SNMP Message Size
Users
Targets & Notify
SNMPv1/v3 Mapping
Summary User Table
(4)
(370)
... (1500)
>
>
>
[]
[]
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-30. Typical SNMPv3 Setting Screen

Table 5-13. SNMPv3 Setting Parameters
Parameter
Function
Values
Engine Boots
Displays the number of times that the

SNMP engine has been initialized since the
SNMP Engine ID was last configured
The display range is 1 to 2147483647.

Default: 0
Engine Time
Displays the time, in seconds, that expired The display range is 0 to 2147483647.
since the value of the Engine Boots field
Default: 0
was last changed
SNMP Message
Size
The maximum length, in octets, of the

SNMP messages that the Gmux-2000 can
send or receive, and process.

Default: 1500
In addition to the maximum supported by

the Gmux-2000 SNMP engine, the selected
size must be supported by all the transport
links available to communicate with the
SNMP engine
Users
Opens the Users submenu, used to

configure the authorized SNMPv3 users
Gmux-2000 Ver. 3.2
See Table 5-14
5-43
Parameter
Function
Values
Targets & Notify
Opens the Targets & Notify submenu, used See Table 5-15 to Table 5-18
to configure the parameters of the targets
(management stations that can manage
the Gmux-2000, and/or receive
notifications of Gmux-2000 events)
SNMPv1/v3
Mapping
Opens the SNMPv1/v3 Mapping submenu,

used to configure the mapping of SNMPv1
security parameters to SNMPv3
parameters, to enable the Gmux-2000 to
support all the SNMP versions
See Table 5-19
SNMPv3 Factory
Defaults
Used to reload the SNMPv3 factory default

parameters.
To restore defaults, select SNMPv3 Factory

Defaults, and then confirm the action
This is useful for erasing the existing

configuration parameters and restoring the
SNMP engine to a known state.
In particular, this function is needed to
recover from configuration errors that
prevent management
Summary User
Table
Displays information on the existing users

and their main configuration data
See the Summary User Table section
Summary Target
Table
Displays information on the existing

targets, and their main configuration data
See the Summary Target Table section
Configuration Authorized SNMPv3 Users

Gmux-2000 has a single factory-default user, designated initial, which is
configured for non-secure operations (that is, no authentication and no privacy).
Non-secure operations are a good starting point for preliminary configuration,
but it must be changed as soon as possible to avoid defeating the very purpose
of SNMPv3.
A typical SNMPv3 Setting screen with the factory-default user parameters is
shown in Figure 5-31. The user configuration parameters are explained in
Table 5-14.
When several users are displayed, you can scroll the Security Name names by
typing f (forward) or b (backward). Always remove a user when you must change
one of its security parameters, and then define a new user with the desired
parameters.
To configure a new user:

1. Navigate to Configuration>System>Management>SNMPv3 Setting>Users.
2. To add a new user, select Security Name and then type the desired user
name, to replace the displayed user name.
3. Select Authentication Protocol, and then select one of the options listed in
Table 5-14.
5-44
Gmux-2000 Ver. 3.2
4. Additional fields, as explained in Table 5-14, are displayed automatically after

you make selections for the Authentication Protocol and Privacy Protocol.
5. When done, save the
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Users
1. Security Name
2. Authentication Protocol
... (initial)
>
(usmNoAuthProtocol)
>
F - Forward; B - Backward; R - Remove
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-31. Typical Factory-Default Users Screen

Table 5-14. SNMPv3 Users Security Parameters
Parameter
Function
Values
Security Name
Used to select the user name (the security

name and the user name are equivalent
under SNMPv3)
Selects the authentication protocol to be

used for this user.
usmNoAuthProtocol no authentication
protocol. This also prevents the use of
privacy (encryption) for this user.
Authentication
Protocol
Default: userName
SNMPv3 uses the key-Hashing Message

Authentication Code (HMAC) authentication usmHMACMD5AuthProtocol use of
method, described in RFC2104
authentication protocol enabled. The
authentication protocol is HMAC-MD5-96
(HMAC with MD5 (Message Digest algorithm
5) as the underlying hash function)
usmHMACSHAAuthProtocol use of
authentication protocol enabled. The
authentication protocol is HMAC-SHA-96
(HMAC with SHA-1 (Secure Hashing Algorithm
1 as the underlying hash function).
Default: usmNoAuthProtocol
Privacy Protocol
Selects the privacy (encryption) protocol to

be used for this user.
This parameter is not displayed when
Authentication Protocol is
usmNoAuthProtocol
usmNoPrivProtocol no privacy protocol.

usmDESPrivProtocol use of privacy protocol
enabled. SNMPv3 uses the cipher block
chaining (CBC) mode of the Data Encryption
Standard (DES) for encryption, with a key
length of 56 bits.
Default: usmNoPrivProtocol
Gmux-2000 Ver. 3.2
5-45
Parameter
Function
Values
Authentication
Password
Used to enter the password to be used by

the authentication protocol.

This parameter is not displayed when

Authentication Protocol is
usmNoAuthProtocol
Privacy
Password
The password required to use privacy.
This parameter is displayed only when

Privacy Protocol is uusmDESPrivProtoco
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Users
1.
2.
3.
4.
5.
Security Name
Privacy Protocol
Privacy Password
... (User1)
>
(usmHMACMD5AuthProtocol)
>
(usmDESPrivProtocol)
...
...
>
1 M/ 1 C
----------------------------------------------------------------------------
Figure 5-32. Typical Users Screen for New User
To remove an existing user:

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

The Targets & Notify screen is used to select targets that are authorized to
perform management and monitoring tasks.
A typical Targets & Notify screen is shown Figure 5-33. the tasks that can be
performed are listed below:
5-46
Select Target Params to target security parameters
Select Target Address to configure transport parameters for the selected

target
Select Notify to select the notification parameters
Select Trap to select the traps associated with the selected target
Gmux-2000 Ver. 3.2
Task parameters are explained in Table 5-15 to Table 5-18.
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Targets & Notify
1.
2.
3.
4.
Target Params
Target Address
Notify
Trap
>
>
>
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-33. Typical Targets & Notify Screen
To configure the Target Params:

1. Navigate to Configuration>System>Management>SNMPv3 setting>Targets &
Notify.
2. Select Target Params.
A typical Target Params screen is shown in Figure 5-34. The parameters
that can be configured are explained in Table 5-15.
PseudoWire Gateway
...ation>System>Management>SNMPv3 setting>Targets & Notify>Target Params
1.
2.
3.
4.
5.
Name
Security Model
Security Name
Security Level
...
>
>
...
>
()
()
()
()
()
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-34. Typical Targets Params Screen
Gmux-2000 Ver. 3.2
5-47
Table 5-15. Target Params Parameters

Parameter
Function
Values
Name
Selects the logistic name assigned to the

target
Message
Processing
Model
The message processing model to be used The available selections are: SNMPv1, SNMPv2c
when generating SNMP messages using this (SNMPv2 with community-based security
entry
model), SNMPv2u (SNMPv2 with user-based
security model (USM)), and SNMPv3.
Default: SNMPv3
Security Model The security model to be used when

generating SNMP messages for this target
The available selections are: Any, SNMPv1,

SNMPv2c, USM (User-Based Security Model),
and Not Defined.
Default: USM
Security Name
Security Level
Selects the security name which identifies

the principal (authority) for which SNMP
messages will be generated for this target
Selects the level of security to be used

when generating SNMP messages for this
target
The available selections are:
noAuthNoPriv No authentication, no privacy.

authNoPriv With authentication, no privacy.
authPriv With authentication and privacy.
Default: noAuthNoPriv
To configure the target transport parameters:

Notify.
2. Select Target Address.
A typical Target Address screen is shown in Figure 5-35. The parameters
PseudoWire Gateway
...tion>System>Management>SNMPv3 setting>Targets & Notify>Target Address
1.
2.
3.
4.
Name
IP Address
Params Name
Tag List
...
...
...
...
()
()
()
()
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-35. Typical Target Address Screen
5-48
Gmux-2000 Ver. 3.2
Table 5-16. Target Address Parameters

Parameter
Function
Values
Name
Selects the logistic name assigned to the

target (see Table 5-15)
Specifies the IP address of this target.
Any valid IP address.
Make sure to add a static route to the target,

if necessary
IP Address
Params
Name
Specifies the name used in the Target Params Alphanumeric string of up to 32 characters.
table (see Table 5-15) to identify the set of
SNMP parameters to be used when generating
messages to be sent to this transport address
Tag List
Used to specify a list of tag values which are

The allowed list can contain up to 255
used to select target addresses for a particular characters.
operation. See also Table 5-17
To configure the Notify parameters:

Notify.
2. Select Notify.
A typical Notify screen is shown in Figure 5-36. The parameters that can
be configured are explained in Table 5-17.
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Notify
Type
1. Name
2. Tag
>
(trap)
... (agnStatusChangeTrap)
... (unmasked)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-36. Typical Notify Screen
Gmux-2000 Ver. 3.2
5-49
Table 5-17. Notify Parameters

Parameter
Function
Values
Type
Displays the type of notifications to be

generated for the events associated with the
Tag List in Table 5-16
The only option is Trap.
Name
Tag
Unique identifier associated with this Notify

definition. May contain a trap description, etc.
Default: Trap
Default: agnStatusChangeTrap
This object contains a single tag value which is Alphanumeric string of up to 32 characters.
Default: Unmasked
used to select entries for the events
associated with the Tag List in Table 5-16
To configure the Trap and Notify Name associations:

Notify.
2. Select Trap.
A typical Trap screen is shown in Figure 5-37.
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Trap

1. Trap Name
2. Notify Name
>
>
(link Up)
(linkUp)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-37. Typical Trap Screen

Using the Trap screen, you can associate traps with the names appearing the
Notify screen (see Table 5-17).
Trap Name
Notify Name
Specifies a trap name

Specifies the corresponding Notify Name appearing in of
Table 5-17. See default associations in Table 5-18.
5-50
Gmux-2000 Ver. 3.2
Table 5-18. Default Trap and Notification Associations

No.
Trap Name
Notify Name
cold start
coldStart
warm start
warmStart
link Down
linkDown
link Up
linkUp
authentication Failure
authenticationFailure
TFTP Status
tftpStatusChangeTrap
agn status
agnStatusChangeTrap
Sanity check
sanityCheckTrap
DacsMux Alarm
dacsMuxAlarmsTrap
10
bundle Status
bundleConnectStatusTrap
11
Configuration Update
cnfgUpdateTrap
12
Data Uploaded
agnUploadDataTrap
SNMPv1/v3 Mapping
This screen is used to configure the mapping of SNMPv1 security parameters
(communities) to SNMPv3 security parameters, to enable the Gmux-2000 to
support all the SNMP versions.
A typical SNMPv1/v3 Mapping screen is shown in Figure 5-38. The parameters
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>SNMPv1/v3 Mapping
1.
2.
3.
4.
Community Index
Community Name
Security Name
Transport Tag
...
...
...
...
()
()
()
()
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-38. Typical SNMPv1/v3 Mapping Screen
Gmux-2000 Ver. 3.2
5-51
Table 5-19. SNMPv1/v3 Mapping Parameters

Parameter
Function
Values
Community
Index
The unique index for this
TBD
Community
Name
The community string (a SNMPv1 security

parameter) for which the following fields
represents a configuration
Security Name
Specifies the security name used in SNMPv3

for this community
Transport Tag
Specifies a set of IP addresses (transport

endpoints) from which management requests
will be accepted
Summary User Table

The Summary User Table screen displays information on the existing users and
their main configuration data. A typical Summary User Table screen is shown in
Figure 5-39. The user parameters are explained in Table 5-14.
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Summary User Table
User
initial
Security Model
USM
Security Level
noAuthNoPriv
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-39. Typical Summary User Table Screen

The Summary Target Table screen displays information on the existing targets,
and their main configuration data. A typical Summary Target Table screen is
shown in Figure 5-40. The target parameters are explained in Table 5-15 and
Table 5-16.
5-52
Gmux-2000 Ver. 3.2
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Summary Target Table
Address
MPModel SecModel SecName
SecLevel
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-40. Typical Summary Target Table Screen
Gmux-2000 Ver. 3.2
5-53
5.6
Configuring Physical Layer Parameters
Use the following procedure to configure the physical layer parameters for the
modules programmed in the various I/O slots of the Gmux-2000 chassis.
Refer to the Installation and Operation Manual of each module for detailed
configuration instructions.
To navigate to the required screen, use Configuration>Physical Layer.
A typical Physical Layer screen is shown in Figure 5-41. The screen shows the
configurable parameters for an E1-PW-SRV/21 module installed in slot I/O-2.
Pseudowire Gateway
Configuration>Physical layer
1.
2.
3.
4.
5.
6.
7.
I/O[1 - 9]
E1 port
VC12 channel
First GbE IF
Second GbE IF
Delete all slot's bundles
Disconnect all slot's bundles
... (2)
>
>
... (0/0)
... (0/0)
>
F - next; B - prev;
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-41. Typical Physical Layer Screen
To configure an I/O module or I/O module port:

1. Select I/O and then type the number of the desired I/O slot, 1 to 9, and then
press <Enter>.
or
Use the F or B key to sequentially display I/O slots in the I/O field.
2. The screen is updated to reflect the parameters supported by the module
programmed in the displayed slot.
3. When the module has several ports, select the corresponding Port item on
the module screen, and then select the specific port to be configured using
the procedure of Step 1 above.
4. Configure the desired parameters.
5. When done with the current port/module, type S to save, before continuing
with the next port.
6. To activate the new configuration, type % and then confirm the action.
5-54
Configuring Physical Layer Parameters
Gmux-2000 Ver. 3.2
5.7
Configuring System Timing Flow
The system timing flow is determined by selecting the timing reference of the
Gmux-2000 timing system.
The Gmux-2000 timing subsystem can use as reference the following types of
signals:
Timing reference signal from a selected SDH port. This option is preferable
for Gmux-2000 units connected to an SDH backbone, because usually large
SDH networks have highly accurate and stable master timing sources.
External (station) signal (2.048 MHz or 1.544 MHz) received from a station
clock port of the CONTROL module. This option also provides a convenient
way for using a high-quality master timing source available at the equipment
site.
Internal oscillator. This source is sufficient for use as reference in a

stand-alone network, not connected to a backbone (or during maintenance
activities). In this configuration, the Gmux-2000 unit selected as the timing
master of the network uses its internal oscillator as source, and all the other
equipment units lock their timing to that Gmux-2000. Note that only one
Gmux-2000 unit in the whole network may use this source.
Signal from a selected E1 port. The source of this signal may be selected from
the following options:
Clock signal recovered from an external E1 port
Clock signal recovered from an internal E1 port
This timing mode is suitable for tail-end Gmux-2000 units, which can extract a
good-quality clock from a directly connected E1 port.
You can configure both a master source and a fallback source for the Gmux-2000
timing system, using separate timing references for each one.
The internal oscillator is automatically selected as source in case all the other
sources (master and fallback) fail: therefore, it cannot be selected as fallback
source.
The Gmux-2000 timing subsystem is identified as System A on the various
screens.
To navigate to the required screen, use Configuration>System>Clock Source.
Configuring Nodal Timing References

A typical Clock Source screen is shown in Figure 5-42.
Gmux-2000 Ver. 3.2
5-55
Pseudowire Gateway
Configuration>System>Clock source
1.
2.
3.
4.
5.
System A
Ext clock interface
Ext in/out clk mode
Ext out clock source
Ext out clock state
>
>
>
(G.703-E1 balanced)
(Normal)
(System A)
(Not connect)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-42. Typical Clock Source Screen
To configure the system (nodal) timing:

1. Select System A to start configuring the nodal timing source.
You will see the clock source selection screen (see Figure 5-43).
Pseudowire Gateway
Configuration>System>Clock source>System A
1. Master clock
2. Fallback clock
>
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-43. Selection Screen for System A Clock Sources

2. Select the source to be configured: Master or Fallback.
3. After pressing <Enter>, you will see the configuration screen for the selected
source.
The screen displays the current selections. Figure 5-44 shows a typical Master
clock source configuration screen with the default selection, Internal; for the
Fallback clock screen, the default selection is None.
An additional field, Master clock source ss pp, appears after selecting as
source a recovered receive clock, Rx Clk (Figure 5-46). For any other source,
Master clock source ss pp is not displayed.
5-56
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>System>Clock source>System A>Master clock
1. Master clock source
>
(Internal)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-44. Master Clock Typical Source Selection Screen (Internal)
To select the clock source:

1. Select Master clock source. You will see the source selection screen. A typical
screen is shown in Figure 5-45.
The various selections are as follows:
Internal
Clock locked to the internal oscillator of the Gmux-2000.

This is the default selection for the master clock.
Rx Clk
Clock locked to the clock signal recovered from the

receive signal of a user-selectable interface.
Ext In-1
Clock locked to the external signal applied to the

STATION clock interface of the CONTROL module
installed in the CTRL.1 slot. Make sure to configure the
appropriate external clock interface.
Ext In-2
Same as above for the CTRL.2 slot.
None
No reference source. Appears only for the fallback clock,

where it is the default selection. However, even for this
selection, the internal Gmux-2000 oscillator is
automatically used when all the other sources (master
and fallback) fail.
2. After making your selection, the source selection screen closes and the new
source appears on the Master clock screen.
Gmux-2000 Ver. 3.2
5-57
Pseudowire Gateway
...ystem>Clock source>System A>Master clock>Master clock source (Rx clk)
1.
2.
3.
4.
Internal
Rx clk
Ext in-1
Ext in-2
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-45. Selection of Master Clock Source Screen

3. If in Step 1 you selected Rx Clk, the screen changes to enable the selection of
the source port.
Figure 5-46 shows a typical master source configuration screen, as seen

after selecting as source a recovered receive clock.
Pseudowire Gateway
2. Master clock source ss pp
3. Save parameters
>
(Rx clk)
... (9/1)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-46. Master Clock Typical Source Selection Screen (Rx Clk)
4. Select Master clock source ss pp and then enter the I/O slot and port that will
supply the reference signal. Use a slash / to separate the two entries.
5. When done, select the last item on the screen, Save Parameters, to save the
new user definitions in the edited database.
7. Repeat the same actions to select a fallback source. Make sure to select a
different source (Internal may be selected only for the master source,
5-58
Gmux-2000 Ver. 3.2
because it is always selected as a last recourse source when all the other
sources, master and fallback, failed).
Configuring the External (Station) Clock Interfaces

You need to configure the external (station) clock interfaces in two cases:
When using an external clock port, Ext In-1 or Ext In-2, as timing reference.
When it is necessary to output the system (nodal) clock through one, or

both, of these ports.
The current selections appear on the Master Clock screen shown in Figure 5-42.
The parameters that can be changed and their range of values are explained in
Table 5-20.
To configure the external clock interfaces:

1. On the Master Clock screen shown in Figure 5-42, select Ext Clock Interface.
After pressing <Enter>, you will see the Ext Clock Interface selection
screen. The Values column in Table 5-20 lists the options displayed on
the selection screen.
2. On the selection screen, type the number of the desired option and then
press <Enter>.
The selection screen closes and the new value appears in the Master
Clock screen.
3. To change the Ext In/Out Clk Mode displayed on the Master Clock screen,
press <Enter>.
Each pressing toggles the selection.
4. To change the Ext Out Clock State displayed on the Master Clock screen,
press <Enter>.
Each pressing toggles the selection.
5. When done, select the last item on the screen, Save Parameters to save the
new user definitions in the edited database.
Gmux-2000 Ver. 3.2
5-59
Table 5-20. Clock Source Parameters

Parameter
Function
Values
Ext Clock
Interface
Selects the physical interface

standard for the STATION CLOCK
interfaces located on the CONTROL
modules.
G.703-E1 balanced 2.048 MHz clock frequency,

using the ITU-T Rec. G.703 120 balanced interface in
the RJ-45 STATION CLOCK connector.
Note that you can also select clock

signals at the ANSI T1 rate,
1.544 MHz. In this case, you can
use only the ITU-T Rec. G.703 or
RS-485 balanced interface
G.703-E1 unbalanced 2.048 MHz clock frequency,

using the ITU-T Rec. G.703 75 unbalanced interface
in the BNC IN and OUT STATION CLOCK connectors.
RS-485 E1 2.048 MHz clock frequency, at RS-485
levels using the balanced interface in the RJ-45
STATION CLOCK connector.
G.703-T1 1.544 MHz clock frequency, using the
ITU-T Rec. G.703 100 balanced interface in the RJ-45
RS-485 T1 1.544 MHz clock frequency, at RS-485
levels using the balanced interface in the RJ-45
Default: G.703-T1
Ext In/Out Clk

Mode
When two CONTROL modules are

installed, enables using a single
external clock source for both
modules
Normal each external clock interface is permanently

connected to the module STATION CLOCK connector.
Therefore, each STATION CLOCK connector must be
connected to a separate external (station) clock
source, and separate clock output cables must be
used.
Y-Cable at any time, only the external clock
interface of the online CONTROL module is connected
to the corresponding STATION CLOCK connector.
Therefore, a Y-cable can be used to connect in
parallel the STATION CLOCK connectors of the two
modules to the same external (station) clock source.
Default: Normal
Ext Out Clock

Source
Displays the internal Gmux-2000

timing subsystem that provides an
output clock to the external clock
interface
The only available selection is SYSTEM A.
Ext Out Clock

State
Enables/disables the external clock

output in the STATION connectors
Connect the external clock output is enabled,

thereby allowing to output the nodal clock to other
equipment. The connection mode depends on the Ext
In/Out Clk Mode selection.
Default: SYSTEM A
Not Connect the external clock output is disabled.

Default: Not Connect
5-60
Gmux-2000 Ver. 3.2
5.8
Configuring Redundancy
Redundancy Configuration Options

Two types of redundancy are supported:
Gmux-2000 control subsystem redundancy.
Redundancy at the I/O module level. Currently, Gmux-2000 supports the

following redundancy capabilities:
APS for the SDH and PSN interface modules.
1:N protection. The current Gmux-2000 version supports 1:N protection

for the following types of modules:
Pseudowire emulation server modules
Voice compression modules using only internal ports (US_NS mode).
Refer to Chapter 2 for a description of the I/O redundancy options.

This section explains how to configure redundancy for Gmux-2000.
To navigate to the required screen, use Configuration>System>Redundancy.
A typical system-level Redundancy task selection screen is shown in Figure 5-47.
Pseudowire Gateway
1. CL
2. I/O
>
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-47. Typical System>Redundancy Task Selection Screen
To select a redundancy configuration task:

1. Select Redundancy on the Configuration menu.
2. Select the appropriate task and then press <Enter>:
Gmux-2000 Ver. 3.2
CL to configure Gmux-2000 control subsystem redundancy.
I/O to configure redundancy for the I/O subsystem.
5-61
Configuring Gmux-2000 Control Subsystem Redundancy

Redundancy for the Gmux-2000 control subsystem is supported only when the
Gmux-2000 chassis includes two operational CONTROL modules: if only one is
installed, it is automatically selected and redundancy cannot be activated.
You can also use the redundancy control function to force the Gmux-2000 to use
a specific CONTROL module, for example, in preparation for CONTROL module
replacement.
To navigate to the required screen, use Configuration>System>Redundancy>CL.
To select the desired CONTROL redundancy mode:

1. Select CL to display the CONTROL module redundancy selection screen.
A typical screen is shown in Figure 5-48. The screen shows the current
redundancy mode.
Pseudowire Gateway
Configuration>System>Redundancy>CL
1. Redundancy mode
>
(Auto)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-48. Typical CL Redundancy Mode Selection Screen

2. To change the current mode, select Redundancy mode.
A typical Redundancy Mode screen for a Gmux-2000 unit with two
CONTROL modules is shown in Figure 5-49.
The available selections are as follows:
AUTO
The online CONTROL module is automatically selected. In

case a fault occurs in the online CONTROL module, the
Gmux-2000 automatically switches to the other module.
This also changes the active out-of-band interfaces, and
the active external clock interface.
This is the recommended (and the default) selection.
5-62
CL-A
Forces the CONTROL module installed in slot CTRL.1 as the

online module.
CL-B
Forces the CONTROL module installed in slot CTRL.2 as the

online module
Gmux-2000 Ver. 3.2
If only one CONTROL module is installed, you will see only one selection,
that corresponding to the installed module.
Pseudowire Gateway
Configuration>System>Redundancy>CL>Redundancy mode (Auto)
1. Auto
2. CL-A
3. CL-B
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-49. Typical CL>Redundancy Mode Control Screen

3. Type the number of the item corresponding to the desired redundancy mode,
and then press <Enter>.
Configuring Gmux-2000 I/O Redundancy SDH Interface Subsystem

Use the following procedure to configure redundancy for the Gmux-2000 SDH
interface subsystem. Refer to Chapter 2 for a description of the redundancy
options available for the SDH interface subsystem when using the dual-port STM1
modules.
The APS (Automatic Protection Switching) configurations supported for STM1
modules are as follows:
When one STM1 module is installed in the Gmux-2000 chassis: one APS group
including the two ports of the STM1 module
When two STM1 modules are installed in the Gmux-2000 chassis: two APS
groups, one for each pair of similarly named ports. Therefore, one APS group
includes the LINK 1 ports of the STM1 modules, and the other APS group
includes the LINK 2 ports.
Redundancy is activated by configuring APS (Automatic Protection Switching)

groups using 1+1 unidirectional protection on the appropriate STM1 ports.
After configuring an APS group on STM1 modules, you have the following options:
Display its current status using Inventory>Redundancy>I/O
Change the active port using Diagnostics>APS Commands.
You can stop using redundancy by selecting None for the Config Mode instead of
the current APS mode.
To navigate to the required screen, use Configuration>System>Redundancy>I/O.
Gmux-2000 Ver. 3.2
5-63
To configure redundancy for the SDH interface subsystem:

1. Select I/O to display the APS group selection screen.
A typical screen with the default values is shown in Figure 5-50.
Pseudowire Gateway
Configuration>System>Redundancy>I/O - (APS 0)
1. APS ID[1 - 16]
... (0)
>
F - next; B - prev; X - add aps
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-50. Typical I/O>APS Group Selection Screen

2. Type X and then press <Enter> to add a new APS group.
The new APS group is automatically assigned the next free index (ID)
number, in the range of 1 to 16, and you see the APS configuration task
selection screen. A typical screen is shown in Figure 5-51.
Alternatively, use the APS ID field on Configuration>System>Redundancy>I/O
to select an existing APS group that can be reconfigured in accordance with
the prescribed parameters.
Pseudowire Gateway
Configuration>System>Redundancy>I/O - (APS 1)
1. APS ID[1 - 16]
2. APS configuration
3. APS mapping
... (1)
[]>
[]>
>
F - next; B - prev; X - add aps
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-51. Typical I/O>APS Configuration Task Selection Screen

3.
Select APS Configuration to configure the APS group parameters.

The screen changes to show the APS group configuration options. A
typical screen, as seen after all the parameters have been configured, is
5-64
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
Recovery mode
Time to restore in sec
1. Change cell
(APS 1)
STM1 Cards
1+1 (Unidirect)
Revertive
300
Enable
... (STM1 Cards)
>
% - UPD DB; F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-52. Typical I/O>APS Configuration Screen (STM1 Modules)

4. Sequentially select each parameter, and configure the prescribed values. The
screen is automatically adjusted after selecting each parameter value. Refer
to Table 5-21 for a description of the APS configuration parameters and the
allowed range of values.
Table 5-21. APS Configuration Parameters (STM1 Modules)

Parameter
Function
Values
Name
Used to assign a logical name to the APS

group
Selects the APS group configuration
NONE Cancels the protection function.
Config Mode
1:1 (BIDIRECT) 1+1 bidirectional protection

mode. This mode is supported only by GbE
modules see Configuring Gmux-2000 I/O
Redundancy PSN Interface Subsystem.
1+1 (UNIDIRECT) 1+1 unidirectional
protection mode. This is the only protection
mode supported by STM1 modules.
802.3AD Link aggregation per IEEE 802.3ad
without LACP. This mode is supported only by
GbE modules see Configuring Gmux-2000
I/O Redundancy PSN Interface Subsystem.
1:N 1:N protection for I/O modules see
configuration details in the Configuring Gmux-
2000 I/O Redundancy 1:N Protection Mode

section.
Default: NONE
Gmux-2000 Ver. 3.2
5-65
Parameter
Function
Values
Recovery Mode
Selects the recovery (service restoration)

mode
NON-REVERTIVE After redundancy flipping,

the STM1 module will not automatically flip
back to the original port when it returns to
normal operation. Flipping will occur again
only in case the currently active port fails, or
its weighted alarm index is higher (worse)
than that of the original STM-1 port.
REVERTIVE After redundancy flipping, the
STM1 module will automatically flip back to
the original STM-1 port when it returns to
normal operation (that is, when its weighted
alarm index is at most equal to that of the
currently active port).
Default: NON-REVERTIVE
Time to Restore
in sec
When the recovery mode is REVERTIVE, this

parameter specifies the time following the
last protection switching (flipping) during
which alarms are ignored.
The supported range is 120 to 720 seconds.

Default: 120
Therefore, the module starts evaluating the

criteria for protection switching (flipping)
only after this interval expires. This ensures
that another flipping cannot occur before
the specified interval expires.
This field can be changed only when the
recovery mode is REVERTIVE; in the
NON-REVERTIVE mode, the field always
displays 0
STM-1 SD Flip
Criteria
Used to select whether to take the SD

condition into consideration when
calculating the weighted alarm index.
The SD threshold is configured as part of
the VC-4 channel parameters of the STM1
modules
ENABLE The SD condition is used.

DISABLE The SD condition is ignored.
Default: ENABLE
5. Select APS Mapping to start configuring the APS group mapping.

You will see the APS group map, which contains a table that lists each
configured channel. Initially, the table is empty, as shown in Figure 5-53.
5-66
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS mapping CH NUM
INTERFACE
(APS 1)
PRIORITY
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-53. Typical New I/O>APS Mapping Screen (STM1 Modules)

6. Type a and then press <Enter> to add a new channel.
You will see the APS group channel selection data form. A typical screen
is shown in Figure 5-54.
Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS mapping CH NUM[1 - 7]
1. INTERFACE
2. PRIORITY
(APS 1)
... (1)
... (0/0)
(Low)
>
% - UPD DB; S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-54. Typical I/O>APS Mapping Channel Selection Screen (STM1 Modules)
7. Select Interface and then specify one of the external ports of the desired
STM1 module as channel 1, by typing the STM1 I/O slot number and port,
separated by a slash /.
Refer to Table 5-22 for a description of APS mapping parameters.
Note
The first port configured in the APS group serves as the primary port. All the
payload ports using this STM1 module port must be mapped only to the
primary port.
Make sure to configure exactly two channels in the group (the maximum
possible number of entries in an APS group is 7, but this maximum is not

applicable to STM1 modules).
Gmux-2000 Ver. 3.2
5-67
8. After configuring the first channel, type a again and then press <Enter>: the
second channel is automatically assigned the next number, 2.
The additional channel that can be configured as channel 2 depends on the
number of STM1 modules installed in the Gmux-2000 chassis:
One STM1 module: you must specify the other external port of the same
STM1 module.
Two STM1 modules: you must specify the same external port of the other
STM1 module.
9. Configure the additional channel, and then press <Enter>.

A typical I/O>APS Mapping screen that displays the two channels of the
group is shown in Figure 5-55.
Pseudowire Gateway
1
2
INTERFACE
7/1
7/2
(APS 1)
PRIORITY
High
Low
1. Change cell
... (7/1)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-55. Typical I/O>APS Mapping Screen after Configuration is Completed (STM1 Modules)
Note
If you include more than two channels in an APS group, it is not possible to
delete undesired channels. The only way to correct the error is to delete the
whole APS group, and then reconfigure it.
Table 5-22. APS Mapping Parameters (STM1 Modules)
Parameter
Function
Values
CH Num
Indicates the index number of the

channel in this APS group
The maximum range is 1 to 7.

Only 1 and 2 are valid selections.
Interface
Selects the STM1 external port that is

to serve the corresponding channel
Enter the STM1 I/O slot number, and the

prescribed external STM1 port. Use a slash to
separate the two numbers.
Default: 0/0
5-68
Gmux-2000 Ver. 3.2
Parameter
Function
Values
Priority
Specifies the channel priority within

this APS group
HIGH High priority. Gmux-2000 will generate an

alarm when protection switching occurs, to
indicate the priority of the selected active port.
LOW Low priority.
Default: LOW
10. After configuring two channels, the configuration of the APS group is
complete, and redundancy is activated as soon as the Gmux-2000 database is
updated.
Configuring Gmux-2000 I/O Redundancy PSN Interface Subsystem

GbE modules can be configured to provide redundancy in one of the following
modes:
Link aggregation mode in accordance with IEEE 802.3ad (without LACP). This
mode inherently provides redundancy: if one of the GbE ports fails, the other
can continue transferring traffic, albeit at half the bandwidth available when
both ports are up.
Link aggregation always provides revertive recovery, because that as soon as
the down port returns to normal, the full bandwidth is again available. Since
Gmux-2000 supports two GbE modules, two link aggregation groups can be
configured in each Gmux-2000 chassis
1:1 bidirectional port protection (redundancy) mode. In this mode, at any

time only one of the ports is actively carrying traffic.
With 1:1 bidirectional port redundancy, the recovery mode (revertive or nonrevertive), and the restoration time in the revertive mode, can be selected in
accordance with the application requirements. Since Gmux-2000 supports
two GbE modules, two link APS groups with GbE ports can be configured in
each Gmux-2000 chassis
1:1 bidirectional module protection (redundancy) mode. In this mode, at any

time only one of the modules (the on-line module) is actively carrying traffic,
whereas the external transmit and receive ports of the off-line module are
disabled (the corresponding internal ports are also in the link down state).
With 1:1 bidirectional module redundancy, the recovery mode (revertive or
non-revertive), and the restoration time in the revertive mode, can be
selected in accordance with the application requirements.
Notes
Only GbE ports configured as Connected can be used for link aggregation and
1:1 bidirectional protection.

Link aggregation and 1:1 bidirectional port protection can only be configured
between the two ports of the same GbE module.

All the PSN redundancy modes are configured by defining APS (Automatic
Protection Switching) groups on the GbE modules or ports. Since Gmux-2000
supports two GbE modules, two APS groups with GbE ports can be configured in
each Gmux-2000 chassis.
Gmux-2000 Ver. 3.2
5-69
After configuring an APS group, you have the following options:
Display its current status using Inventory>Redundancy>I/O
For 1:1 bidirectional port or module protection: you can change the active
port, respectively module, using Diagnostics>I/O>APS Commands.
You can stop using redundancy by selecting None for the Config Mode instead of
the current APS mode.
To navigate to the required screen, use Configuration>System>Redundancy>I/O.
Configuring Link Aggregation for the PSN Interface
To configure link aggregation for the PSN interface subsystem:

1. Select I/O to display the APS group selection screen.
A typical screen with the default values is shown in Figure 5-50.
2. Type a and then press <Enter> to add a new APS group.
The new APS group is automatically assigned the next free index (ID)
number, in the range of 1 to 16, and you see the APS configuration task
selection screen. A typical screen is shown in Figure 5-51.
Alternatively, use the APS ID field on Configuration>System>Redundancy>I/O
to select an existing APS group that can be reconfigured in accordance with
the prescribed parameters.
3. Select APS Configuration to configure the APS group parameters. Refer to
Table 5-23 for a description of APS configuration parameters.
Pseudowire Gateway
Config mode
1. Change cell
(APS 1)
GBE cards
802.3AD
... (GBE cards)
>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-56. Typical I/O>APS Configuration Screen Link Aggregation Mode (GbE Modules)
5-70
Gmux-2000 Ver. 3.2
Table 5-23. APS Configuration Parameters Link Aggregation Mode (GbE Modules)
Parameter
Function
Values
Name
Used to assign a logical name to the APS Alphanumeric string of up to 16 characters.

group
Config Mode
Selects the APS configuration

1:1 (BIDIRECT) 1:1 bidirectional protection mode.
See configuration details in the Configuring 1:1
Bidirectional Port Protection Mode for the PSN

Interface or Configuring 1:1 Bidirectional Module
Protection for the PSN Interface section below.
1+1 (UNIDIRECT) 1+1 unidirectional protection
mode. This mode is supported only by STM1
modules see configuration details in the
Configuring Gmux-2000 I/O Redundancy SDH

Interface Subsystem section.
without LACP. This is the mode to be selected.
configuration details in the Configuring Gmux-2000
I/O Redundancy 1:N Protection Mode section.
Default: NONE
4. Select APS Mapping to start configuring the APS group mapping.

You will see the APS group map, which contains a table that lists each
configured channel. Initially, the table is empty, as shown in Figure 5-53.
5. Type a and then press <Enter> to add a new channel.
You will see the APS group channel selection data form. A typical screen
6. Select Interface and then specify one of the external ports of the desired GbE
module as channel 1, by typing the GbE I/O slot number and port, separated
by a slash /.
Note
bundles using this GbE module as their network port must point to the primary
port. This is because the two GbE ports in an APS group operate as a single PSN
interface, and therefore it is not allowed to configure bundles on the secondary
port of the APS group.
7. After configuring the first channel, type a again and then press <Enter>: the
second channel is automatically assigned the next number, 2.
The additional channel that can be configured as channel 2 is always the
other external port of the same GbE module.
8. Configure the additional channel, and then press <Enter>.
Gmux-2000 Ver. 3.2
5-71
A typical I/O>APS Mapping screen that displays the two channels of an

APS group is shown in Figure 5-57.
Make sure to configure exactly two channels in the group (the maximum
possible number of entries in an APS group is 7, but this maximum is not
applicable to GbE modules).
Table 5-24. APS Mapping Parameters Link Aggregation (GbE Modules)

Parameter
Function
Values
CH Num
Indicates the index number of the channel in

this APS group
The maximum range is 1 to 7. Only 1 and 2

are valid selections.
Interface
Selects the GbE external port that is to serve

each channel.
Enter the GbE I/O slot number, and the

prescribed external GbE port. Use a slash to
Make sure to select the same I/O slot number separate the two numbers.
Default: 0/0
Priority
Specifies the channel priority within this APS

group.
HIGH High priority.
Since with link aggregation the two external

ports share the traffic and therefore have
equal priorities, the selection made in this
field is ignored
Default: LOW
LOW Low priority.
Pseudowire Gateway
1
2
INTERFACE
6/1
6/2
(APS 1)
PRIORITY
High
Low
1. Change cell
... (6/2)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-57. Typical I/O>APS Mapping Screen after Link Aggregation Configuration is Completed
(GbE Modules)
complete, and link aggregation is activated as soon as the Gmux-2000
database is updated.
5-72
Gmux-2000 Ver. 3.2
Note
If you include more than two channels in an APS group, it is not possible to
delete undesired channels. The only way to correct the error is to delete the
whole APS group, and then reconfigure it.
Configuring 1:1 Bidirectional Port Protection Mode for the

PSN Interface
To configure 1:1 bidirectional APS for GbE ports:

1. Add a new APS group as explained in the Configuring Link Aggregation for the
PSN Interface section above.
2. Configure the APS group parameters, using the APS Configuration field on
Configuration>System>Redundancy>I/O. Refer to Table 5-25 for a description
of the APS configuration parameters.
Pseudowire Gateway
Config mode
Recovery mode
1. Change cell
(APS 1)
GbE Ports
1:1 (Bidirect)
Revertive
300
... (GbE Ports)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-58. Typical I/O>APS Configuration Screen 1:1 Bidirectional Port Protection Mode (GbE
Modules)
3. Configure the APS group mapping, as explained in the Configuring Link
Aggregation for the PSN Interface section above. Refer to Table 5-24 for a
description of APS mapping parameters, but note that for 1:1 bidirectional
port protection the Priority parameter is effective.
Note
bundles using this Gmux-2000 module as their network exit port must point to
the primary port.
complete, and 1:1 bidirectional port protection is activated as soon as the
Gmux-2000 database is updated.
Gmux-2000 Ver. 3.2
5-73
Table 5-25. APS Configuration Parameters 1:1 Bidirectional Port Protection Mode (GbE Modules)
Parameter
Function
Values
Name
See Table 5-23
Config Mode

1:1 (BIDIRECT) 1:1 bidirectional protection
mode. This is the mode to be selected.

Interface Subsystem section.
without LACP. See configuration details in the

section above.
configuration details in Configuring Gmux-2000 I/O
Redundancy 1:N Protection Mode section.
Default: NONE
Recovery Mode
See Table 5-23
Time to Restore
in sec
See Table 5-23
Configuring 1:1 Bidirectional Module Protection for the PSN

Interface
To configure 1:1 bidirectional module protection for GbE modules:

1. Add a new APS group as explained in the Configuring Link Aggregation for the
PSN Interface section above.
2. Configure the APS group parameters, using the APS Configuration field on
Configuration>System>Redundancy>I/O. Refer to Table 5-25 for a description
of the APS configuration parameters.
5-74
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Config mode
Recovery mode
1. Change cell
(APS 1)
GbE Cards
1:1 (Bidirect)
Revertive
300
... (GbE Cards)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-59. Typical I/O>APS Configuration Screen 1:1 Bidirectional Module Protection Mode (GbE
Modules)
3. Configure the APS group mapping, as explained in the Configuring Link
Aggregation for the PSN Interface section above. For Gmux-2000 module
redundancy, select the primary Gmux-2000 module as channel 1, and the
secondary module as channel 2 of the group. For both slots, select 0 for the
port field.
Refer to Table 5-24 for a description of the other APS mapping parameters;
note that for 1:1 bidirectional port protection the Priority parameter is
effective. A typical screen, as seen after all the parameters have been
configured, is shown in Figure 5-60.
Note
The first module configured in the APS group serves as the primary module. All
the bundles using Gmux-2000 ports as their network exit ports must point to the
desired port on the primary module.
4. After configuring the two channels, the configuration of the APS group is
complete, and 1:1 bidirectional module protection is activated as soon as the
Gmux-2000 Ver. 3.2
5-75
Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS mapping - (APS 1)
CH NUM
1
2
INTERFACE
6/0
8/0
PRIORITY
High
Low
1. Change cell
... (6/0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-60. Typical I/O>APS Mapping Screen after 1:1 Bidirectional Module Protection
Configuration is Completed (GbE Modules)
Configuring Gmux-2000 I/O Redundancy 1:N Protection Mode

Gmux-2000 modules support 1:N protection for I/O modules installed in the
chassis. The current Gmux-2000 version has the following capabilities:
Support of 1:N protection mode only for the pseudowire server modules, and
for voice compression modules operating in the internal port (US_NS) mode
Only one 1:N protection group can be configured in the chassis.
An 1:N protection group for I/O modules is formed by adding a spare (standby, or
protection) module to a group of N modules that carry the traffic (the protected
modules). All the modules in an 1:N protection group must be of the same type.
To provide differential quality of service, it is possible to define two protection
priority levels, low and high: in the event that protection is required for two
modules in the 1:N protection group at the same time, only the high priority
module will be protected.
To configure 1:N protection for I/O modules:

1. Open the Configuration>System>Redundancy>I/O screen and type a to add a
new APS group.
Note
Gmux-2000 supports a single 1:N protection group per chassis. Therefore, if

another 1:N protection group is already configured, first delete it.
2. Open the APS Configuration screen for the new APS group, and select 1:N for
the Config Mode. You may also add a name for the group, in the Name field.
3. Select the Recovery Mode and Time to Restore (see Table 5-26 for details).
A typical screen, as seen after all the parameters have been configured, is
5-76
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Config mode
Recovery mode
1. Change cell
(APS 1)
PW Cards
N+1
Revertive
300
... (PW Cards)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-61. Typical I/O>APS Configuration Screen 1:N Protection Mode

Table 5-26. APS Configuration Parameters 1:N Protection Mode
Parameter
Function
Name
See Table 5-21
Config Mode
Values

1:1 (BIDIRECT) 1:1 bidirectional protection
mode. This mode is supported only by GbE
Configuring Gmux-2000 I/O Redundancy PSN

Interface Subsystem section above.

Interface Subsystem section above.
without LACP. See configuration details in the

section above.
1:N 1:N protection for I/O modules. This is the
mode to be selected.
Default: NONE
Recovery Mode
See Table 5-21
Time to Restore
in sec
See Table 5-21
Gmux-2000 Ver. 3.2
5-77
4. Open the APS Mapping screen, and add the protection members in the
following order (the order is indicated by the automatically assigned numbers
in the CH NUM column):
1. The first module to be specified is the I/O module serving as the
protection module, in the format {Slot]/{Port], where the port number
must be 0.
Note
After a protection module is selected, it cannot be changed. To select another
module, first delete the 1:N protection group, and then reconfigure another
group with the required protection module.
It is not necessary to define configuration parameters for the protection
module: the appropriate configuration parameters will be automatically

downloaded by the CONTROL module when flipping is necessary.
2. After the protection module is specified, you can specify the protected
modules in any order. For each module, use the format {Slot]/{Port],
where the port number must be 0.
For a Gmux-2000 equipped with a single STM1 module, the maximum

number of I/O modules that can be protected is 5
For a Gmux-2000 equipped with two STM1 modules, the maximum
number of I/O modules that can be protected is 4.
3. To provide differential quality of service, select for each module its

protection Priority: Low or High.
A typical screen, as seen after the required number of channels have been
configured, is shown in Figure 5-62.
Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS mapping - (APS 1)
CH NUM
1
2
3
4
5
INTERFACE
1/0
2/0
4/0
5/0
7/0
PRIORITY
Low
Low
Low
Low
High
1. Change cell
... (6/0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-62. Typical I/O>APS Mapping Screen after 1:N Protection Configuration is Completed
5. After configuring the required number of channels, the configuration of the
APS group is complete, and 1:N protection is activated as soon as the
5-78
Gmux-2000 Ver. 3.2
5.9
Configuring Connections
A bundle is a collection of parameters that define the way payload will be

transported from a local Gmux-2000 port, through the transport network, and
down to a remote destination supporting the same capabilities.
Packet formats can be selected on a per-bundle basis for optimal transmission
over IP- or MPLS-based networks (UDP/IP and MPLS/ETH, respectively), and each
bundle can be independently routed to any destination.
The following user-configurable protocols are supported, independently for each
bundle:
Note

accordance with RFC5087 and ITU-T Rec. Y.1413 (the term TDMoPSN is used
when information is applicable to both protocols)


with RFC5086
TDMoIP compressed voice (CV) bundles
TDMoPSN, HDLCoPSN, CESoPSN and SAToPSN bundles are supported by
pseudowire modules.
TDMoIP (CV) bundles are supported by voice compression modules.
The maximum number of bundle (connection) configurations that may be stored
in the Gmux-2000 is 2000, where each bundle is assigned a unique index number
in the range of 1 to 2000.
However, the actual maximum number the Gmux-2000 can store depends on the
number and type of that are installed in the chassis. Chapter 2 provides
information regarding the number of modules of each type that are supported by
the current Gmux-2000 version.
No bundles are included in the Gmux-2000 factory defaults: you must define your
own in accordance with the application requirements.
To be able to create a bundle, first make sure that all the TDM external and
internal ports, as well as the network ports that will carry the bundle and
participate in its processing, have already been configured and defined as
Connected.
The configuration of a bundle includes the following main activities:
1. Select the bundle structure: the structure is determined by the connection
mode and PSN type.
2. Configure the bundle parameters corresponding to the selected structure.
During bundle configuration, you can also choose whether to activate the bundle
configuration data, or just save it in the database without the bundle being used
by any module (as long as its Connection state is set to Disable).
Gmux-2000 Ver. 3.2
5-79
When you try to save the bundle configuration, the Gmux-2000 automatically
checks its parameters to verify that the bundle appears to be correctly defined,
without configuration conflicts nor obvious errors such as incorrect IP addresses,
etc. Any errors are reported: they must be corrected for the bundle to be saved.
Note
After a bundle is active, it is not recommended to change bundle parameters,
nor parameters of the ports and subsystems handling the bundle. You should
first delete the bundle defined on a module when that module is removed
from the Gmux-2000.
It is not recommended to delete a bundle while its Connection state is Enable:
first change its state to Disable.
Overview of Connection Submenu

The Connection submenu is used to manage the Gmux-2000 bundles.
The activities that may be performed include:
Add new bundles
Change the parameters of existing bundles
Delete existing bundles.
Figure 5-63 to Figure 5-66 show the full structure of the Connection submenu for
each type of bundle.
5-80
Gmux-2000 Ver. 3.2

Connection
1. Bundle ID
2. Connection Mode
3. PSN Type
Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
TDMoIP (CE), SAToP

UDP/IP
MPLS/ETH
Connection State
Source Bundle
Destination Bundle
TDM Byte in Frame
Jitter Buffer in Ms
Sensitivity
Payload Type
Connection State
Source CBID
Dest CBID
Payload Format
TDM Byte in Frame
Jitter Buffer in Ms
Sensitivity
OAM Connectivity
OAM Indication
Payload Type
Far End Type
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
IP TOS
Adaptive Clock
VLAN Tagging
VLAN ID
VLAN Priority
or
Far End Type

OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Adaptive Clock
Outbound EXP Bits
VLAN Tagging
VLAN ID
VLAN Priority
Figure 5-63. Configuration>Connection Submenu TDMoIP (CE) and SAToPSN

Bundles
Gmux-2000 Ver. 3.2
5-81

Connection
1. Bundle ID
2. Connection Mode
3. PSN Type
Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
HDLC
UDP/IP
MPLS/ETH
Connection State
Source CBID
Dest CBID
OAM Connectivity
OAM Indication
OOS L Bit mode
Destination IP
Network Slot Port
Next Hop
IP TOS
VLAN Tagging
VLAN ID
VLAN Priority
or
Connection State
Source Bundle
Destination Bundle
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Outbund EXP Bits
VLAN Tagging
VLAN ID
VLAN Priority
Figure 5-64. Configuration>Connection Submenu HDLC Bundles
5-82
Gmux-2000 Ver. 3.2
Connection
1. Bundle ID
2. Connection Mode
3. PSN Type
Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
CES
UDP/IP
MPLS/ETH
Connection State
Source Bundle
Destination Bundle
TDM Frame in Packet
Jitter Buffer in Ms
Sensitivity
Payload Type
Connection State
Source CBID
Dest CBID
Payload Format
TDM Frame in Packet
Jitter Buffer in Ms
Sensitivity
OAM Connectivity
OAM Indication
Payload Type
Far End Type
OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
IP TOS
Adaptive Clock
VLAN Tagging
VLAN ID
VLAN Priority
or
Far End Type

OOS L Bit Mode
Destination IP
Network Slot Port
Next Hop
Adaptive Clock
Outbound EXP Bits
VLAN Tagging
VLAN ID
VLAN Priority
Figure 5-65. Connection Submenu CESoPSN Bundles
Gmux-2000 Ver. 3.2
5-83
Connection
1. Bundle ID
2. Connection Mode
3. PSN Type

Connection Mode
1. HDLC
2. TDMoIP (CE)
3. TDMoIP (CV)
4. SAToP
5. CES
PSN Type
1. MPLS/ETH
2. UDP/IP
UDP/IP
MPLS/ETH
Function
Function
1. AAL2oMPLS
2. AAL2oMPLS+
1. TDMoIP
2. TDMoIP+
TDMoIP (CV)
UDP/IP
Routing Parameters
1. Connection State
2. Function
4. Transparent Jitter Size
5. Max Bytes In Multiplexed Frame
6. Packetizing Interval
8. Voice Parameters
1. Destination IP
2. Exit Port
3. Next Hop
4. Source CBID
5. Dest CBID
6. Exit Channel
7. TOS Parameters
8. VLAN Parameters
MPLS/ETH
Routing Parameters
1. Destination IP
2. Exit Port
3. Next Hop
4. Source CBID
5. Dest CBID
6. Exit Channel
7. VLAN Parameters
TOS Parameters
TOS Byte Value (Hex)
1. Precedence
2. Delay
3. Throughput
4. Reliability
VLAN Parameters
1. VLAN Tagging
2. VLAN ID
3. VLAN Priority
Fax Modem
1. Connectivity Packet Rate (Sec)
2. Connectivity Timeout Cycles
Voice Parameters
1. Coder/Rate (Kbps)
2. Caller ID Type
3. Tx Delay for Caller ID
4. Volume to Line
5. Volume from Line
6. Fax/Modem
7. MF Parameters
8. Custom Tone Detection
9. Super Tandem
10. Echo Canceller
11. Coding
12. VAD
13. CNG Mode
14. Advanced Voice Parameters
1. Modem
2. Modem op mode
3. VBD Rate
4. Fax
5. Fax Rate (kbps)
6. Max VBD Modem Calls
7. Max Relay Modem Calls
MF Parameters
1. MFCR2 Relay
2. Minimum Pulse Width (msec)
3. Minimum Power Level (negative dBm)
4. MFC Spooling
5. Tone Ack Interval (N*20)
For
MFC Spooling
enabled
VAD
1. VAD Method
2. Noise Level for VAD
Generic VAD Policy

Internal VAD Policy

1. Cdis/CNG Detection Time (N*10msec)
Figure 5-66. Configuration>Connection Submenu TDMoIP (CV) Bundles
5-84
Gmux-2000 Ver. 3.2
General Bundle Configuration Procedure
To start bundle configuration activities:

1. Select Connection on the Configuration menu.
2. You will see the bundle selection screen of the Connection submenu. The
screen contents depends on the number of already-defined bundles:
If no bundles have been configured, you will see the factory default
screen. A typical screen is shown in Figure 5-67.A: the header of this
screen indicates bundle 0 (no bundle).
In this case, first you must add a bundle: start by typing X. The F and B
keys are not active at this stage. The new bundle is automatically
assigned the next free index number. The bundle index number appears
at the top of each configuration screen.
Note
If bundles have already been configured, you will see the screen for the
bundle with the highest index number. A typical screen of this type is
shown in Figure 5-67.B.
Note the list of available commands displayed at the bottom of the screen.
Configuration>Connection 1. Bundle ID[1 - 2000]
Pseudowire Gateway
(BUNDLE 0)
... (0)
>
% - UPD DB; F - next; B - prev; X - add bundle
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical Screen with no Bundles

Pseudowire Gateway
Configuration>Connection - (BUNDLE 12)
1. Bundle ID[1 - 2000]
... (12)
2. Connection mode
>
(TDMoIP(CE))
3. PSN type
(UDP/IP)
4. Connection configuration
[]>
>
F - next; B - prev; X - add bundle; D - del bundle
1 M/ 1 C
-----------------------------------------------------------------------------
B. Typical Bundle Screen

Figure 5-67. Typical Configuration>Connection Bundle Selection Screens
Gmux-2000 Ver. 3.2
5-85
To select an existing bundle:

1. Select Bundle ID, type the number of the desired bundle, and then press
<Enter>.
or
2. Use the F or B key to sequentially display existing bundle numbers in the
Bundle ID field.
Note
You can modify an existing bundle only if it is not used by any other module. If a
bundle is in use, first disconnect it.
The screen is updated to reflect the parameters supported by the
displayed bundle.
3. To configure or edit the bundle parameters, select Connection Configuration.
4. When done with the current bundle, type S to save before continuing with
the next one.
Note
The S Save option, together with Save All, appear only after changes have been
made. After saving, you are prompted to update the online database.
5. If configuration errors are detected, you will be notified by an alert. Type V to
view the sanity errors and use that information to correct the bundle
parameters.
6. Repeat the procedure for all the additional bundles.
7. To update the online database and activate the new configuration, type %
and then confirm the action.
To delete an existing bundle:

1. Select the desired bundle as explained above.
2. Type D: you will be asked to confirm.
3. After confirming, the screen is updated to reflect the parameters supported
by the bundle with the current highest index. If no bundles exist, you will see
the screen of Figure 5-67.A.
Selecting the Bundle Structure

To navigate to the required screen, use Configuration>Connection>Connection
Configuration.
To select the bundle structure:

1. Select Connection Mode, and then select the desired bundle type. The bundle
types supported by Gmux-2000 are:
5-86
HDLC: bundle for carrying HDLC traffic using the HDLCoPSN protocol
Gmux-2000 Ver. 3.2
TDMoIP (CE): bundle for TDMoPSN circuit emulation, can carry data and
voice timeslots, as well as unframed data
SAToPSN: bundle using the SAToPSN protocol, for carrying an unframed

data stream
CES: bundle using the CESoPSN protocol, for carrying framed data
streams.
TDMoIP (CV): bundle carrying compressed voice (CV) using the TDMoPSN
protocol.
2. Select PSN Type, and then select the type of packet-switched network that
will be used to transport the bundle payload:
Note
UDP/IP UDP over IP with standard packet structure.
If you need to know the number of the source UDP port of a bundle, you can find
it as follows (unless noted otherwise, all numbers are in hexadecimal notation):
For TDMoIP (CE) bundles using packet payload Version V1:
During normal operation, the source UDP port is given by:
UDP Source Port = 1 + Destination Bundle Number
This means that during normal operation, the UDP ports numbers are in the
range of 0 to 8191 decimal.
While the bundle is in the local fail state, the source UDP port changes to:
This means that in the local fail state, the UDP ports numbers are higher than
8000 hexa (32768 decimal).
For TDMoIP (CE) bundles using packet payload Version V2:
This means that all the UDP ports numbers are higher than 2000 hexa (8192
decimal).
For CESoPSN and SAToPSN bundles using packet payload Version V2:
UDP Source Port = C000 + Destination Bundle Number
This means that all the UDP ports numbers are higher than C000 hexa (49152
decimal).
MPLS/ETH MPLS over Ethernet with standard packet structure. In this

case, only TDMoIP Version V2 is used.
Configuring TDMoIP (CE) Bundle Parameters

Configuring TDMoIP (CE) Bundles for UDP/IP Networks
To configure the bundle parameters:

1. Select Connection Configuration.
You will see the first page of the selected bundle connection
configuration screen. A typical screen is shown in Figure 5-68.
Gmux-2000 Ver. 3.2
5-87
2. Obtain the prescribed parameters, and then use Table 5-27 for parameter
descriptions and configuration guidelines.
3. Use the arrow keys to move the selection block to the desired parameter,
and then type Change cell to change the value. After pressing <Enter> to
confirm the new value, the selected value appears on the screen, and the
selection block automatically advances to the next parameter.
The range of values that can be selected is automatically updated, in
accordance with the position of the selection block. No range is shown
when the parameter has only two values: pressing <Enter> toggles the
value.
Note
As explained in Table 5-27, some of the parameters that appear in the

table/menu depend on values assigned to previous parameters. Figure 5-68
shows all the parameters that may appear.
Pseudowire Gateway
Configuration>Connection>Connection configuration Connection state
Source CBID
Dest CBID
| Payload format
v TDM byte in frame(x48)
Jitter buffer in Ms[0-200]
Sensitivity
1. Change cell
(BUNDLE 3)
Disable
0
0
V2
1
3.00
Sensitive to data
... (Disable)
>
% - UPD DB
1 M/ 1 C
-----------------------------------------------------------------------------
A. Page 1 of Typical Screen
5-88
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>Connection>Connection configuration ^ OAM connectivity
| OAM indication
Payload type
| Far end type
v OOS L bit mode
Destination IP
Network slot port
1. Change cell
(BUNDLE 3)
Enable
Source port number
Data
E1
Stop TX
0.0.0.0
0/0
... (0/0)
>
% - UPD DB
1 M/ 1 C
-----------------------------------------------------------------------------
B. Page 2 of Typical Screen

PseudoWire Gateway
Configuration>Connection>Connection configuration ^ Next hop
| IP TOS
Adaptive clock
VLAN tagging
VLAN ID
VLAN priority
1. Change cell
(BUNDLE 3)
0.0.0.0
0
Enable
Enable
0
0
... (Disable)
>
% - UPD DB
1 M/ 1 C
-----------------------------------------------------------------------------
C. Page 3 of Typical Screen

Figure 5-68. Typical Connection Configuration Screen
4. When done with the current bundle, type S to save before continuing with
the next one.
Note
The S Save prompt, together with the Save All option, appear only after
changes have been made. After saving, you are prompted to update the online
database.
5. If configuration errors are detected, you will be notified by an alert. Type V to
view the sanity errors and use the information presented in Chapter 7 to
identify the problem and correct the bundle parameters.
Gmux-2000 Ver. 3.2
5-89
Table 5-27. TDMoIP (CE) Bundle Parameters UDP/IP Networks

Parameter
Function
Connection
State
Selects the state of the connection defined

by means of this bundle.
Values
DISABLE The bundle is not active. You can

still configure and save the desired
The maximum number of bundles that may be parameters, to prepare the bundle for
activation when needed.
simultaneously active for an E1 port is 16,
and the total per module is 112
ENABLE The bundle is active.
Default: DISABLE
Source CBID
Selects the local endpoint source circuit

bundle identifier (CBID) at the local endpoint
(source) of the connection defined by means
of this bundle
The supported range is 1 to 8063.

0 means that no source CBID has been
defined.
Default: 0
Each bundle must have a unique source CBID

Dest CBID
Payload Format
Selects the circuit bundle identifier at the

destination endpoint of the connection
defined by means of this bundle.

0 means that no source CBID has been
defined.
Do not reuse the same Dest CBID value on

bundles terminating at the same destination
IP address, and/or using the same VLAN ID
(when VLAN tagging is enabled)
Default: 0
Selects the TDMoIP payload format.
V1 Old TDMoIP format, defined as

experimental in the relevant IETF drafts. Not
recommended for use.
The selection must be compatible with the

equipment at the far end of the connection.
Contact RAD Technical Support Department if TDMoIP version V1 requires two UDP
sockets per bundle and does not support
you need additional information
the OAM protocol, whereas TDMoIP V2
requires a single UDP socket per bundle. The
larger number of UDP sockets per bundle
needed by TDMoIP V1 reduces the maximum
number of bundles to a given destination
supported by Gmux-2000.
V2 Current TDMoIP format. Requires one
UDP socket per bundle and supports the
OAM protocol.
Default: V2
5-90
Gmux-2000 Ver. 3.2
Parameter
Function
Values
TDM Byte in
Frame
Specifies the number of TDM payload bytes

to be inserted in each packet.
The number is specified as a multiple of 48

bytes, for example, 1 means 48 bytes, and
30 means 1440 bytes.
A larger value increases the bandwidth

utilization efficiency, but also increases the
connection intrinsic latency, in particular
when the bundle is configured to carry a
small number of timeslots.
The available selections are 1 to 30 (48 to

1440 bytes, respectively).
Default: 1
Refer to the Selection Guidelines for TDM

Payload Bytes per Frame section below for
selection consideration
Jitter Buffer in
Ms
Specifies the value of the jitter buffer to be

used on this bundle.
The allowed range is 0 to 200 msec, in

0.01-msec steps.
You should use the shortest feasible buffer,

to minimize connection latency.
Default: 1.00 msec
Refer to the Selecting an Optimal Jitter Buffer

Size section below for selection consideration
Sensitivity
Specifies the handling of packets received

SENSITIVE TO DATA no action taken, until
after a delay exceeding that compensable for underrun or overrun occurs.
by means of the jitter buffer
SENSITIVE TO DELAY when the jitter-buffer
remains at its high value for a long time
(long delay), the jitter buffer is
automatically reset. As a result, some
packets are discarded.
Default: SENSITIVE TO DATA
OAM
Connectivity
Controls the use of the OAM connectivity

protocol for this bundle.
ENABLE The use of the OAM connectivity

protocol is enabled. This is the
recommended selection. Make sure to
select V2 for Payload Format.
The OAM connectivity protocol enables

detecting loss of communication with the
destination of TDMoIP traffic and taking steps DISABLE The use of the OAM connectivity
that prevent the resulting flooding. The
protocol is disabled.
protocol also enables checking that the
Default: ENABLE
destination uses a compatible configuration.
The selection must be compatible with the
equipment at the far end of the connection.
Contact RAD Technical Support Department if
you need additional information
OAM Indication
Specifies the method used to identify OAM

packets
SOURCE PORT NUMBER in accordance with

with the source port number: the OAM
packets run over a UDP port number
assigned only for OAM traffic.
CONTROL WORD in accordance with the
first four bits of the control word: these bits
are always set to 0001 in the control word
of an OAM packet.
Default: SOURCE PORT NUMBER
Gmux-2000 Ver. 3.2
5-91
Parameter
Function
Values
Payload Type
Selects the processing of the TDM payload

transported by this bundle.
DATA No processing. This is the selection

needed when transporting unframed E1
streams, E1 streams without timeslot 16
multiframe structure (FRAMED G.704 or
FRAME-CRC), and whenever the Far End
Type parameter is UNFRAMED, T1 D4, or T1
ESF.
VOICE/CAS Voice with CAS. This is the
selection needed when transporting E1
streams with timeslot 16 multiframe
structure (FRAME-MF or FRAME-MF-CRC),
provided the Far End Type parameter is E1.
Default: DATA
Far End Type
Specifies the type of framing used by the

equipment at the destination endpoint. The
selected value also determines the encoding
law used on PCM voice channels.
Make sure to select the same value at both
end points. The selected value must also
match the Line Type configured for the
physical port of the bundle local endpoint.
The only allowed selections are those
supported by the TDM interfaces installed in
the Gmux-2000. Therefore, you can select
only E1 and UNFRAMED.
E1 E1 stream with G.704 framing. The

PCM signals are processed assuming that
they are encoded in accordance with the
A-law. You can use this selection when the
port Line Type is a FRAMED version.
T1 ESF T1 stream with ESF framing. The
PCM signals are processed assuming that
they are encoded in accordance with the
-law. Do not select for Gmux-2000 with
SDH network interfaces.
T1 D4 T1 stream with SF (D4) framing.

The PCM signals are processed assuming
If necessary, you can also select T1 D4 or T1 that they are encoded in accordance with
ESF, but only when the Payload Type is DATA, the -law. Do not select for Gmux-2000
with SDH network interfaces.
and the total number of timeslots does not
exceed 24
UNFRAMED unframed E1 data stream,
transparently transferred. You can use this
selection when the port Line Type is
UNFRAMED.
Default: E1
OOS L Bit Mode
Selects the response to out-of-service

conditions detected at the local E1 physical
port. Such conditions are reported by setting
the L bit within the TDMoIP packet overhead
STOP TX transmit minimal packets with

the L bit set. This approach reduces
bandwidth consumption on the packet
switched network side.
TX OOS AND L BIT set the L bit in the
TDMoIP packets, and fill the packets with
the OOS Code configured for the
corresponding physical port. This setting,
which does not reduce bandwidth
consumption while the problem persists,
has the advantage that the average data
rate remains unchanged and therefore
enables reliable adaptive timing recovery.
Default: STOP TX
5-92
Gmux-2000 Ver. 3.2
Parameter
Function
Values
Destination IP
Specifies the IP address of the destination

bundle.
Type in the desired IP address, using the

periods).
Make sure to select a valid address that can

be reached through the uplink port
configured in the Network Slot Port field,
considering the value selected for the Next
Hop parameter
Network Slot
Port
Select the PSN port through which the traffic

generated by this bundle will be sent.
Make sure to specify a slot in which a GbE
module is installed
Next Hop
IP TOS
Default: 0.0.0.0
Enter the I/O slot (6 or 8) and the physical

port number (1 or 2) of the desired GbE
port. Separate the two digits by a slash /.
Default: 0/0
Specifies an IP address to which the bundle

packets will be sent, to enable reaching the
destination IP address. This is usually the

dotted-quad format.

only when the destination address is not
within the IP subnet of the uplink port
configured in the Network Slot Port field
Default: 0.0.0.0
Specifies the Layer 3 priority assigned to the

traffic generated by this bundle.
Type in the prescribed number, in the range

of 0 to 255.
For IP networks, this priority is indicated by

the IP type-of-service parameter for this
bundle. The specified value is inserted in the
IP TOS field of the bundle IP packets.
In accordance with RFC 2474, it is

recommended to use only values which are
multiples of 4.
To use the default gateway, leave this field

at the default value, 0.0.0.0.
Default: 0
When supported by an IP network, the

type-of-service parameter is interpreted, in
accordance with RFC 791 or RFC 2474, as a
set of qualitative parameters for the
precedence, delay, throughput and delivery
reliability to be provided to the IP traffic
generated by this bundle.
These qualitative parameters may be used by
each network that transfers the bundle IP
traffic to select specific values for the actual
service parameters of the network, to
achieve the desired quality of service
You can also specify a Layer 2 priority by
means of the VLAN Priority field, provided
VLAN Tagging for this bundle is Enable.
Gmux-2000 Ver. 3.2
5-93
Parameter
Function
Values
Adaptive Clock
Enables the adaptive timing recovery

mechanism for this bundle
ENABLE Adaptive timing is enabled. In this

case, the bundle will be automatically
selected as timing reference for the E1 port
to which it will be connected when the port
timing mode is Adaptive.
DISABLE Adaptive timing is disabled.
Default: DISABLE
VLAN Tagging
Controls the use of VLAN tagging for the

traffic generated by this bundle
ENABLE VLAN tagging is enabled.

DISABLE VLAN tagging is disabled.
Default: DISABLE
VLAN ID
When VLAN tagging is enabled, specifies the

VLAN ID number used by the bundle traffic
sent through this port.
Do not assign VLAN IDs 101 and 102: this will
interfere with the Gmux-2000 internal
management traffic, and may disrupt normal
operations.
Use the same VLAN ID for all the bundles
addressed to a given IP address.
The allowed range is 1 to 100, and 103 to

4094.
Do not use VLAN IDs 101 and 102: these
VLAN IDs are used for internal management
purposes within the Gmux-2000.
0 means that no VLAN ID has been
specified.
Default: 0

parameter is not displayed
VLAN Priority
When VLAN tagging is enabled, specifies the

priority assigned to the bundle traffic using
the selected VLAN.
The allowed range in accordance with IEEE

802.3p is 7 (highest priority) to 0 (lowest
priority).

Default: 0
Configuring TDMoIP (CE) Bundle Parameters for MPLS/ETH

Networks

Table 5-28. TDMoIP (CE) Bundle Parameters MPLS/ETH Networks

Parameter
Function
Connection
State
See Table 5-27
5-94
Values
Gmux-2000 Ver. 3.2
Parameter
Function
Values
Source Bundle
Selects the number of the source bundle at the

local endpoint of this connection.

0 means that no source bundle has been
defined.
Each bundle must have a unique source bundle

number
Destination
Bundle
Selects the number of the destination bundle at

the far endpoint of this connection.
Default: 0
0 means that no destination bundle has
been defined.
Do not reuse the same Destination Bundle value

on bundles terminating at the same destination
Default: 0
IP address, and/or using the same VLAN ID (when
VLAN tagging is enabled)
TDM Byte in
Frame
See Table 5-27
Jitter Buffer in
Ms
See Table 5-27
Sensitivity
See Table 5-27
Payload Type
See Table 5-27
Far End Type
See Table 5-27
OOS L Bit Mode
See Table 5-27
Destination IP
See Table 5-27
Network Slot
Port
See Table 5-27
Next Hop
See Table 5-27
Adaptive Clock
See Table 5-27
Outbound Label
Tagging
Controls the use of an interworking MPLS label

for the transmit (outbound) direction of the
bundle
Outbound
Tunnel Label
Outbound EXP
Bits
ENABLE Outbound tagging is enabled.

DISABLE Outbound tagging is disabled.
Default: DISABLE
Specifies the outbound MPLS label used for the

bundle.
The supported range is 16 to 8191. 0

means that no label has been defined.
This parameter is displayed only when Outbound

Label Tagging is ENABLE
Default: 0
Specifies the value of the outbound EXP bits in

the packet header used for the bundle.

Default: 0
This parameter is displayed only when Outbound

Inbound Label
Tagging
Controls the use of an interworking MPLS label

ENABLE Inbound tagging is enabled.
for the receive (inbound) direction of the bundle. DISABLE Inbound tagging is disabled.
Configuring an inbound label for each bundle is
Default: DISABLE
mandatory. When no outbound label is
configured, the inbound label is also used as the
outbound label
Gmux-2000 Ver. 3.2
5-95
Parameter
Function
Values
Inbound Tunnel
Label
Specifies the inbound MPLS label used for the

bundle.
The supported range is 16 to 8191. Each

bundle must have a unique inbound
MPLS label. 0 means that no label has
been defined.
This parameter is displayed only when Inbound

Default: 0
VLAN Tagging
See Table 5-27
VLAN ID
See Table 5-27
VLAN Priority
See Table 5-27
Selection Guidelines for TDM Payload Bytes per Frame

The TDMoIP technology enables transmitting the continuous data stream
generated by TDM equipment as a stream of discrete packets, having a structure
suitable for transmission over packet-switched networks. This process is called
packetizing (see Appendix C for a concise description of this process, and of the
reverse process used to reconstruct the TDM data stream).
As part of this process, the continuous TDM data stream is sliced in accordance
with the TDM Byte per Frame parameter, and 44 bytes of overhead are added to
create a TDMoIP packet (additional overhead is latter added to form frames for
transmission over Ethernet).
The number of TDM bytes inserted in each packet affects two important
performance parameters:
Bandwidth utilization efficiency: the smaller the number of TDM bytes per
packet, the lower the efficiency. The overhead can be a significant fraction of
the total packet when the TDM Byte per Frame parameter is small. The worst
efficiency occurs at the minimum packet size, 48 bytes of payload versus 44
bytes of overhead.
Packetizing delay and the associated delay variance. Considering that any
given TDM byte is received only once in every TDM frame, the rate at which
TDM bytes are received for filling packets is 8000 bytes per timeslot per
second. Since a packet will be sent only after its payload field has been filled,
the maximum possible filling rate occurs for bundles carrying 32 timeslots
(unframed mode) and a payload of 48 bytes per frame: in this case, the filling
of the 48 bytes takes 1.5 internal TDM frames (with CAS signaling, the
maximum number of timeslots decreases to 30).
However, the filling time increases significantly for bundles with few
timeslots; for example, a voice channel could be carried by a single-timeslot
bundle. Considering the nominal filling rate (approximately one byte every
0.125 msec), the filling time can easily become very significant. As a worstcase example, consider the time needed to fill a single-timeslot bundle:
5-96
At 48 TDM bytes per frame: approx. 5.5 msec with CAS support and
5.9 msec without CAS support
At 1440 TDM bytes per frame: approx. 165 msec with CAS support and
177 msec without CAS support.
Gmux-2000 Ver. 3.2
The round-trip (or echo) delay for voice channels is at least twice the
packetizing delay; any other delays encountered along the end-to-end
transmission path only add to this minimum. Another problem introduced by
packetizing is intrinsic jitter: because the instant a packet is filled up is usually
not synchronized with its transmission to network, but occurs after an
essentially random delay, some jitter is inherently introduced.
Selecting an Optimal Jitter Buffer Size

For reliable operation, the jitter buffer must be large enough to ensure that it is
not emptied when the transmission delay increases temporarily (an effect called
underflow, or underrun), nor fills up to the point that it can no longer accept new
frames when the transmission delay decreases temporarily (an effect called
overflow).
The minimum size of the jitter buffer depends on the intrinsic jitter, and the
maximum size is 200 msec.
The theoretically correct value for the size of the jitter buffer of any given bundle
is slightly more than the maximum variation in the transmission delay through the
network, as observed on the particular link between the bundle source and the
destination. For practical reasons, it is sufficient to select a value that is not
exceeded for any desired percentage of time: for example, a value of 99.93%
means that the jitter buffer will overflow or underflow for an accumulated total
of only one minute per day.
Jitter buffers are located at both ends of a link, therefore the delay added by the
buffers is twice the selected value. The resultant increase in the round-trip delay
of a connection may cause problems ranging from inconvenience because of long
echo delays on audio circuits (similar to those encountered on satellite links) to
time-out of data transmission protocols (especially polling protocols).
Therefore, the size of each jitter buffer must be minimized, to reduce the
round-trip delay of each connection in as far as possible, while still maintaining
the link availability at a level consistent with the application requirements.
Configuring HDLC Bundle Parameters

Configuring HDLC Bundle Parameters for UDP/IP Networks

Table 5-29. HDLC Bundle Parameters UDP/IP Networks

Parameter
Function
Connection State
See Table 5-27
Source CBID
See Table 5-27
Gmux-2000 Ver. 3.2
Values
5-97
Parameter
Function
Dest CBID
See Table 5-27
OAM Connectivity
See Table 5-27
OAM Indication
See Table 5-27
Destination IP
See Table 5-27
Network Slot Port
See Table 5-27
OOS L Bit Mode
See Table 5-27
Next Hop
See Table 5-27
IP TOS
See Table 5-27
VLAN Tagging
See Table 5-27
VLAN ID
See Table 5-27
VLAN Priority
See Table 5-27
Values
Configuring HDLC Bundle Parameters for MPLS/ETH Networks

Table 5-30. HDLC Bundle Parameters MPLS/ETH Networks

Parameter
Function
Connection State
See Table 5-27
Source Bundle
See Table 5-28
Destination Bundle
See Table 5-28
OOS L Bit Mode
See Table 5-28
Destination IP
See Table 5-27
Network Slot Port
See Table 5-27
Next Hop
See Table 5-27
See Table 5-28
See Table 5-28
Outbound EXP Bits
See Table 5-28
See Table 5-28
See Table 5-28
VLAN Tagging
See Table 5-27
VLAN ID
See Table 5-27
5-98
Values
Gmux-2000 Ver. 3.2

Parameter
Function
VLAN Priority
See Table 5-27
Values
Configuring SAToPSN Bundle Parameters

Configuring SAToPSN Bundle Parameters for UDP/IP Networks

Table 5-31. SAToPSN Bundle Parameters UDP/IP Networks

Parameter
Function
Values
Connection State
See Table 5-27
Source CBID
See Table 5-27
Dest CBID
See Table 5-27
Payload Format
See Table 5-27
Only V2 is available
TDM Byte in Frame
Specifies the number of TDM payload

bytes to be inserted in each packet
The available range is 32 to 1440 bytes per

packet.
Default: 32
Jitter Buffer in MS
See Table 5-27
Sensitivity
See Table 5-27
OAM Connectivity
See Table 5-27
OAM Indication
See Table 5-27
Payload Type
See Table 5-27
Only DATA is available
Far End Type
See Table 5-27
Only UNFRAMED is available
OOS L Bit Mode
See Table 5-27
Destination IP
See Table 5-27
Network Slot Port
See Table 5-27
Next Hop
See Table 5-27
IP TOS
See Table 5-27
Adaptive Clock
See Table 5-27
VLAN Tagging
See Table 5-27
VLAN ID
See Table 5-27
VLAN Priority
See Table 5-27
Gmux-2000 Ver. 3.2
5-99
Configuring SAToPSN Bundle Parameters for MPLS/ETH

Networks

Table 5-32. SAToPSN Bundle Parameters MPLS/ETH Networks

Parameter
Function
Connection State
See Table 5-28
Source Bundle
See Table 5-28
Destination Bundle
See Table 5-28
TDM Byte in Frame
Specifies the number of TDM payload

bytes to be inserted in each packet
Values
The available range is 4 to 1440 bytes per

packet.
Default: 4
Jitter Buffer in MS
See Table 5-28
Sensitivity
See Table 5-28
Payload Type
See Table 5-28
Far End Type
See Table 5-28
Only UNFRAMED is available
OOS L Bit Mode
See Table 5-28
Destination IP
See Table 5-28
Network Slot Port
See Table 5-28
Next Hop
See Table 5-28
Adaptive Clock
See Table 5-28
Outbound Label
Tagging
See Table 5-28
Outbound Tunnel
Label
See Table 5-28
Outbound EXP Bits
See Table 5-28
Inbound Label
Tagging
See Table 5-28
See Table 5-28
VLAN Tagging
See Table 5-28
VLAN ID
See Table 5-28
VLAN Priority
See Table 5-28
5-100
Gmux-2000 Ver. 3.2
Configuring CES Bundle Parameters

Configuring CES Bundle Parameters for UDP/IP Networks

Table 5-33. CES Bundle Parameters UDP/IP Networks

Parameter
Function
Values
Connection State
See Table 5-27
Source CBID
See Table 5-27
Dest CBID
See Table 5-27
Payload Format
See Table 5-27
Only V2 is available
TDM Frame in Packet
Specifies the number of TDM frames to

be inserted as payload in each packet
The available range is 1 to 45 frames per

packet (equivalent to 32 to 1440 bytes of
payload per packet).
Default: 4
Jitter Buffer in MS
See Table 5-27
Sensitivity
See Table 5-27
OAM Connectivity
See Table 5-27
OAM Indication
See Table 5-27
Payload Type
See Table 5-27
Far End Type
See Table 5-27
Always select E1, unless the the Payload

Type is DATA, and the total number of
timeslots does not exceed 24
OOS L Bit Mode
See Table 5-27
Destination IP
See Table 5-27
Network Slot Port
See Table 5-27
Next Hop
See Table 5-27
IP TOS
See Table 5-27
Adaptive Clock
See Table 5-27
VLAN Tagging
See Table 5-27
VLAN ID
See Table 5-27
VLAN Priority
See Table 5-27
Gmux-2000 Ver. 3.2
5-101
Configuring CES Bundle Parameters for MPLS/ETH Networks

Table 5-34. CES Bundle Parameters MPLS/ETH Networks

Parameter
Function
Connection State
See Table 5-28
Source Bundle
See Table 5-28
Destination Bundle
See Table 5-28
TDM Frame in Packet
Specifies the number of TDM frames to

be inserted as payload in each packet
Values
The available range is 1 to 45 frames per

packet (equivalent to 32 to 1440 bytes of
payload per packet).
Default: 4
Jitter Buffer in MS
See Table 5-28
Sensitivity
See Table 5-28
Payload Type
See Table 5-28
Far End Type
See Table 5-28
Always select E1, unless the the Payload

Type is DATA, and the total number of
timeslots does not exceed 24
OOS L Bit Mode
See Table 5-28
Destination IP
See Table 5-28
Network Slot Port
See Table 5-28
Next Hop
See Table 5-28
Adaptive Clock
See Table 5-28
Outbound Label
Tagging
See Table 5-28
Outbound Tunnel
Label
See Table 5-28
Outbound EXP Bits
See Table 5-28
Inbound Label
Tagging
See Table 5-28
See Table 5-28
VLAN Tagging
See Table 5-28
VLAN ID
See Table 5-28
VLAN Priority
See Table 5-28
5-102
Gmux-2000 Ver. 3.2
Configuring TDMoIP (CV) Bundle Parameters

TDMoIP (CV) bundles are supported only by voice compression modules, VC-E1/16
and VC-E1/12. In the following sections, the generic term VC-E1/16 is used for
both voice compression module versions.
TDMoIP (CV) Bundle Configuration Sequence

The tasks needed to configure TDMoIP (CV) connections and their parameters are
started from the Configuration>Connection menu, as explained on page 5-83.
The configuration of a bundle for VC-E1/16 includes the following main activities:
1. Select the bundle structure: the structure is determined by the connection
mode and PSN type.
2. Configure the bundle parameters corresponding to the selected structure.
These parameters include routing parameters, and general parameters.
3. Configure the voice processing parameters, and the additional parameters
needed to support voiceband modems and fax.
Preliminary TDMoIP (CV) Bundle Configuration Steps
To select the bundle structure:

1. Select Connection Mode, and then select TDMoIP (CV). This means that you
are configuring a TDMoIP bundle for compressed voice. This is the only type
of bundle that can be connected to VC-E1/16 ports.
2. Select PSN Type, and then select the type of packet-switched network that
will be used to transport the bundle payload:
Note
UDP/IP UDP over IP.
If you need to know the number of the source UDP port of a bundle, you can find
it as follows (all numbers are in hexadecimal notation):
This means that all the UDP ports numbers are higher than 2000 hexa, that is,
8192 decimal.
MPLS/ETH MPLS over Ethernet.

A typical TDMoIP (CV) Connection Configuration screen is shown in
Figure 5-69.
Gmux-2000 Ver. 3.2
5-103
Pseudowire Gateway
Configuration>Connection>Connection configuration 1.
2.
3.
4.
5.
6.
7.
8.
(BUNDLE 2)
Connection State
(Enable)
Function
>
(TDMoIP+)
Routing Parameters
>
Transparent Jitter Size (N*10mSec) - N [2 - 10]... (2)
Max Bytes In Multiplexed Frame[100 - 1461]
... (1400)
Packetizing Interval (Msec)[10 - 90]
... (30)
>
Voice Parameters
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-69. Typical TDMoIP (CV) Bundle Connection Configuration Screen

4. Select Function to select the packet structure version. The available options
depend on the selected PSN type.
The options available for UDP/IP networks are as follows:
TDMoIP TDM over IP with standard packet structure. Always select

this type for compatibility with other vendors UDP/IP equipment.
TDMoIP+ TDM over IP with RAD proprietary packet structure. This
proprietary structure, which increases the connection bandwidth
utilization efficiency by reducing the number of overhead bytes
carried in each packet, can be used only when the equipment at the
other end of the link is another VC-E1/16, or a Vmux Voice Trunking
Gateway with compatible software version.
The default for UDP/IP networks is TDMoIP+.
The options available for MPLS/ETH networks are as follows:
AAL2oMPLS AAL2 over MPLS with standard packet structure. Always

select this type for compatibility with other vendors equipment using
AAL2 over MPLS.
AAL2oMPLS+ AAL2 over MPLS with RAD proprietary packet
structure. This proprietary structure, which increases the connection
bandwidth utilization efficiency by reducing the number of overhead
bytes carried in each packet, can be used only when the equipment at
the other end of the link is another VC-E1/16, or a Vmux Voice
Trunking Gateway with compatible software version.
The default for MPLS/ETH networks is AAL2oMPLS+.
5-104
Gmux-2000 Ver. 3.2
Configuring TDMoIP (CV) Bundle Routing Parameters
To configure the TDMoIP (CV) bundle routing parameters:

1. Select Connection Configuration, and then select Routing Parameters.
A typical TDMoIP (CV) Routing Parameters screen is shown in Figure 5-70.
Pseudowire Gateway
...>Connection>Connection configuration>Routing Parameters 1.
2.
3.
4.
5.
6.
7.
8.
Destination IP
Next Hop
Source CBID[1 - 8063]
Dest CBID[1 - 8063]
Exit Port
Exit Channel[1 - 10]
TOS Parameters
VLAN Parameters
...
...
...
...
...
...
>
>
(BUNDLE 2)
(123.45.67.8)
(34.56.78.90)
(16)
(22)
(6/1)
(1)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-70. Typical TDMoIP (CV) Routing Parameters Screen

Table 5-35. TDMoIP (CV) Bundle Routing Parameters

Parameter
Function
Connection
State
Selects the state of the connection defined

Destination
IP
Specifies the destination IP address of the

bundle.
Values
DISABLE The bundle is not active. You can still

configure and save the desired parameters, to
The maximum number of bundles that may be prepare the bundle for activation when needed.
simultaneously active for a voice compression ENABLE The bundle is active.
module is 32
Default: DISABLE
Make sure to select a valid address that can

be reached through the port configured in
the Exit Port field, considering the value
selected for the Next Hop parameter.

dotted-quad format (four groups of digits in the
Default: 0.0.0.0
The voice compression module source IP

address is the CONTROL module host IP
address, configured by means of the
Configuration>System>Host IP screen
Gmux-2000 Ver. 3.2
5-105
Parameter
Function
Values
Next Hop
Specifies an IP address to which the bundle

packets will be sent, to enable reaching the
destination IP address. This is usually the

dotted-quad format.

only when the destination IP address is not
within the IP subnet that can be reached
through the port configured in the Exit Port
field
Default: 0.0.0.0
Source CBID
To use the default gateway, leave this field at

the default value, 0.0.0.0.
The function depends on the PSN Type:

UDP/IP: Selects the local endpoint source
circuit bundle identifier (CBID) at the local
endpoint (source) of the connection defined
The supported range is 1 to 8063. Each bundle

must have a unique source CBID.
0 means that no source CBID has been defined.
MPLS/ETH: Selects the inbound MPLS label

accepted for this bundle
The supported range is 16 to 8063. Each bundle

must have a unique inbound MPLS label. 0
means that no label has been defined.
Default: 0
Dest CBID
The function depends on the PSN Type:

UDP/IP: Selects the circuit bundle identifier at The supported range is 1 to 8063.
the destination endpoint of the connection
0 means that no source CBID has been defined.
defined by means of this bundle.
Exit Port
MPLS/ETH: Selects the outbound MPLS label

accepted for this bundle.
The supported range is 16 to 8063. 0 means

that no label has been defined.
Do not reuse the same Dest CBID value on

bundles terminating at the same destination
IP address, and/or using the same VLAN ID
(when VLAN tagging is enabled)
Default: 0
Select the port through which the traffic

To specify a VC-E1/16 data port:
Enter the I/O slot of the VC-E1/16 module that

You can select either a VC-E1/16 data port, or will use this bundle, and the data port number,
17 to 21 (when using backup, enter only the
one of the GbE module ports
number of the primary port). Separate the two
digits by a slash /.
To specify a GbE module port:
Enter the I/O slot (6 or 8) and the physical port
number (1 or 2) of the desired GbE port.
Separate the two digits by a slash /.
Default: 0/0
Exit Channel
When using as exit port a VC-E1/16 data port, Enter the number of the prescribed subchannel,
this parameter is used to select the data port 1 to 10.
subchannel through which the traffic
Default: 0
This parameter is not relevant for GbE ports
5-106
Gmux-2000 Ver. 3.2
Parameter
Function
Values
TOS
Parameters
Specifies the Layer 3 priority assigned to the

traffic generated by this bundle.
The ToS parameters are selected on a screen

that opens after selecting the TOS parameter.
This priority is indicated by the IP

type-of-service (ToS) parameter for this
bundle. The specified value is inserted in the
IP TOS field of the bundle IP packets.
The current value of the TOS parameter (00 to

FF hexa, equivalent to 0 to 255 decimal) is
displayed at the top of the screen in
hexadecimal notation. The displayed TOS value
is the sum of the parameter values selected for
each ToS component, and it is dynamically
updated after selecting a value for each
component.
When supported by an IP network, the

type-of-service parameter is interpreted in
accordance with RFC 791 or RFC 2474, as a
set of qualitative parameters for the
precedence, delay, throughput and delivery
reliability to be provided to the IP traffic
generated by this bundle. These qualitative
parameters may be used by each network
that transfers the bundle IP traffic to select
specific values for the actual service
parameters of the network, to achieve the
desired quality of service
You can also specify a Layer 2 priority by
means of the VLAN Priority field, provided
VLAN Tagging for this bundle is Enable
The available selections for each ToS

component are as follows (each is listed from
the lowest to the best value):
Precedence:
Routine (lowest)
Priority
Immediate
Flash
Flash Override
Critical/ECP
Internetwork Control
Network Control (highest)
Delay:
Normal
Low
Throughput:
Normal
High
Reliability:
Normal Reliability
High Reliability
Default: 00
VLAN
Parameters
Used to configure the use of VLANs for voice

packets. VLANs are relevant only when the
traffic traverses Ethernet-based networks.
Selecting VLAN Parameters displays a
submenu that includes the following
selections:
VLAN Tagging: controls the use of VLAN

tagging for the traffic generated by this
bundle
Gmux-2000 Ver. 3.2
ENABLE VLAN tagging is enabled.

DISABLE VLAN tagging is disabled.
Default: DISABLE
5-107
Parameter
Function
Values
VLAN
Parameters
(cont.)
The allowed range, in accordance with IEEE

802.3Q, is 1 to 4094.
VLAN ID: when VLAN tagging is enabled,

specifies the VLAN ID number used by the
bundle traffic sent through this port.
parameter is not displayed.
0 means that no VLAN ID has been specified.

Default: 0
When you select the VLAN ID for bundles

that exit via a GbE module port, make sure
that the same VLAN ID is used for all the
bundles having the same destination IP
address (the GbE module supports only
one VLAN per IP address)
VLAN Priority: when VLAN tagging is

The allowed range in accordance with IEEE
enabled, specifies the priority assigned to 802.3p is 7 (highest priority) to 0 (lowest
the bundle traffic using the selected
priority).
VLAN.
Default: 0

Configuring TDMoIP (CV) General Bundle Parameters
To configure the TDMoIP (CV) bundle packetizing parameters:

1. On the Connection Configuration screen, select each of the parameters listed
in Table 5-36 and select the prescribed values.
Table 5-36. TDMoIP (CV) General Bundle Parameters Packetizing Parameters

Parameter
Function
Values
Max Bytes in
Multiplexed
Frame
Specifies the total number of bytes (including The available selections are 100 to 1461.
all the header information) to be inserted in
Default: 1400
each packet sent to the network.
A larger value increases the bandwidth
utilization efficiency, but also increases the
connection intrinsic latency, in particular
when the bundle is configured, by means of
of the TS Assignment submenu, to carry a
small number of timeslots.
Transparent
Jitter Size
Specifies the jitter buffer size used for data

carried in transparent timeslots
The jitter buffer size is specified as a

multiple of 10 msec.
The allowed multiplier range is 2 to 10
(equivalent to 20 to 100 msec, in 10-msec
steps).
Default: 2 (20 msec)
5-108
Gmux-2000 Ver. 3.2
Parameter
Function
Values
Packetizing
Interval
Specifies the maximum time interval before a

TDMoIP packet is transmitted on this bundle.
The allowed range is 10 to 90 msec, in

1-msec steps.
If the packetizing interval expires, the

currently processed packet is transmitted
even if not yet filled with the number of
bytes specified by Max Bytes in Multiplexed
Frame.
Default: 30 msec
Make sure to select an interval compatible

with the specified maximum number of bytes.
To configure the bundle connectivity check parameters:

1. On the Connection Configuration screen, select Connectivity Parameters to
display the corresponding submenu.
2. Select each of the parameters listed in Table 5-37 and enter the prescribed
values.
Table 5-37. TDMoIP (CV) General Bundle Parameters Connectivity Check Parameters
Parameter
Function
Values
Connectivity
Packet Rate
(Sec)
Controls the rate at which keep-alive packets are

transmitted for this bundle.
The range is one packet every

second (1), to one packet every
60 seconds.
The keep-alive packets are used to check connectivity

with the destination. When loss of communication is
Default: 60
detected, VC-E1/16 generates a BUNDLE OOS alarm,
and notifies the equipment connected to the voice port
by sending the appropriate OOS indication.
Keep-alive packets are relatively small, and therefore
require a negligible bandwidth. Therefore, the rate can
be selected so as to minimize false alarms while
reducing the time needed to reliably detect loss of
connectivity:
In a network with low transmission delay (for

example, when using TDM links), you can configure
a higher rate (shorter interval) to ensure earlier
detection of a failure
In packet networks, where delays are more

common, it is recommended to set the connectivity
parameters to their maximum values
Connectivity
Specifies the number of keep-alive transmission cycles
Timeout Cycles within which VC-E1/16 expects to receive at least one
reply from the far end.
The available selections are 2 to

5 cycles.
Default: 3
For example, when the Connectivity Packet Rate is 60

seconds and the Connectivity Timeout Cycles is 3, a
bundle is declared out-of-service if no reply has been
received within 180 seconds of the last reply
Gmux-2000 Ver. 3.2
5-109
Configuring TDMoIP (CV) Bundle Voice Parameters
To configure the TDMoIP (CV) bundle voice processing parameters:

1. On the Connection Configuration screen, select Voice Parameters to display
the corresponding submenu.
A typical TDMoIP (CV) Voice Parameters screen is shown in Figure 5-71.
The screen includes two pages. The parameters displayed on the screen
are dynamically changed in accordance with your selections.
Pseudowire Gateway
...ig>Connection>Connection configuration>Voice Parameters -
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
...
>
Coder/Rate (Kbps)
Caller ID Type
Tx Delay For Caller ID[0 - 3000]
Volume To Line
Volume From Line
Fax/Modem
MF Parameters
Custom Tone Detection
Super Tandem
Echo Canceller
Coding
(N)
(BUNDLE 1)
>
(G.729A/8)
(Bellcore type 1)
... (400)
>
(0 dB)
>
(0 dB)
>
>
>
(Enable)
(Enable)
(A-Law)

S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
Pseudowire Gateway
...ig>Connection>Connection configuration>Voice Parameters ...
12.
13.
14.
15.
(P)
VAD
CNG Mode
Save parameters
(BUNDLE 1)
>
(Enable)
>
>
S - Save
1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 5-71. Typical TDMoIP (CV) Voice Parameters Screen
5-110
Gmux-2000 Ver. 3.2
Table 5-38. TDMoIP (CV) Bundle Voice Parameters

Parameter
Function
Values
Coder/Rate
(kbps)
Selects the coder used for this bundle, and the

resulting digitized voice data rate.
G.723.1/6.4 Coder complying with ITU-T

Rec. G.723.1, operating at 6.4 kbps.
Note the following limitations related to the

use of ITU-T Rec. G.711 coders:
G.723.1/5.3 Coder complying with ITU-T

Rec. G.723.1, operating at 5.3 kbps.
G.711 coders cannot be selected when the

Super Tandem mode is ENABLE.
G.729A/8 Coder complying with ITU-T Rec.

G.729A, operating at 8 kbps.
The maximum number of active E1 voice

ports when G.711 coders are used is 8.
Unlike the other options, no real

compression occurs with G.711 coders, and
the bandwidth needed to transfer a G.711
coded signal is on the order of one timeslot
on the exit port.
G.711 (A-Law) PCM coder complying with

ITU-T Rec. G.711, operates at a data rate of
64 kbps and uses the A companding law (this
companding law is commonly used in Europe,
and other countries using the E1 hierarchy).
The only bandwidth reduction is due to the

use of voice activity detection (VAD), and
therefore when using a G.711 coder you
cannot select OFF for the Noise Level for
VAD parameter.
G.711 (u-Law) PCM coder complying with

ITU-T Rec. G.711, operates at a data rate of
64 kbps, and uses the companding law
(this companding law is commonly used in
North America, and other countries using the
T1 hierarchy.)
Default: G.723.1/6.4
When using a G.711 coder, the MF

Parameters options are not displayed.
Caller ID Type Selects the caller ID signaling protocol.

This parameter is displayed only when the
Coder/Rate parameter is G.729A/8
Bellcore Type 1 The caller ID is signalled

using the Bellcore Type 1 protocol.
V.23 The caller ID is signalled using the
V.23 protocol.
Default: Bellcore Type 1
Tx Delay for
Caller ID
Specifies the time to wait from the start of the

set up process for a new call, before sending
the caller ID information for that call.
The available range is 0 to 3000 msec.

Default: 400 msec
This parameter is displayed only when the

Coder/Rate parameter is G.729A/8
Gmux-2000 Ver. 3.2
5-111
Parameter
Function
Values
Volume to
Line
Controls the gain of the receive audio path (the The available selections are -6 to +6 dB, in
path transmitting towards the local users
1-dB steps.
equipment, for example, a PBX or switch) for
Default: 0 dB
this bundle.
This function can be used to compensate for
attenuation in the local audio path. For
example, when a subscriber of the local PBX
served by the bundle being configured is
connected by a long line, you can increase the
gain to compensate for the expected audio line
attenuation, and thus improve the perceived
voice quality. For example:
If the expected line attenuation is 2 dB, and

the PBX nominal input level is 0 dBm,
increase the gain by selecting +2dB for
Volume to Line
When singing occurs, decrease the gain.
You can also adjust the receive gain to

compensate for level differences in the path
from the far-end equipment to the local
equipment: for example, if the far-end signal is
too weak, you can add gain at the output.
However, the recommended approach to
correct such problems is to adjust the far end
Volume from Line parameter (see below)s.
See Figure 5-72 below for a description of the
way VC-E1/16 interprets the Volume to Line
and Volume from Line parameters.
VC-E1/16 Processing Channel

Input Level
-6dB
Transmit
Input Circuit
Nominal Input Level

0dB
Digital
Signal
Processor
Adjust Volume from Line

to -6dB
User's
Equipment
Output Level
+2dB
Receive
Output Circuit
Nominal Output Level

0dB
Adjust Volume to Line

to +2dB
Figure 5-72. Selection of Volume to Line and Volume from Line Parameters
5-112
Gmux-2000 Ver. 3.2
Parameter
Function
Volume from
Line
Controls the nominal input level of the transmit The available selections are -12 dB, -6 to
path (the path receiving signals from the local
+6 dB in 1-dB steps, and +12 dB.
equipment, for example, a PBX) for this bundle. Default: 0dB
This function is used to compensate for
attenuation in the local audio path, or for
differences in the nominal levels of the
equipment. The purpose is to ensure that the
VC-E1/16 DSP processing the signal of this
bundle handles a signal at its optimum
(nominal) level, and thus can provide the best
perceived voice quality. For example:
Fax/Modem
When the audio signal received from the

local PBX in a timeslot served by the bundle
being configured is too low, for example,
-6B below the nominal level, select -6B for
the Volume from Line parameter to increase
the input gain and thus compensate for the
lower input signal.
When the nominal level of the audio signal

received from the local PBX is +3 dBm,
increase the Volume from Line parameter to
+3 dB
Values
Used to control the fax and modem processing

parameters for this bundle.
These parameters are selected on a separate
screen that opens when you select Fax/Modem.
Modem
Enables/disables modem signal identification
for this bundle
ENABLE Modem signal identification is

enabled.
DISABLE Modem signal identification is
disabled.
Default: DISABLE
Gmux-2000 Ver. 3.2
5-113
Parameter
Function
Values
Fax/Modem
(cont.)
Modem Op Mode
VOICEBAND DATA The modem signal is

handled as an analog signal. This mode
transparently transfers the modem signal
waveform, and therefore supports many
standards. Note that the bandwidth needed
to transfer a voiceband signal requires a
relatively large bandwidth on the exit port:
the exact bandwidth depends on the
selected VBD Rate coder, however it is on
the order of one timeslot.
Determines the modem signal processing

method.
This parameter is displayed only when Modem
is ENABLE
RELAY The modem signal is demodulated

by the receiving side, the resulting data is
transmitted through the link as a digital
signal, and reconverted to a clean modem
signal at the other side. This selection is
relevant only for modem signals conforming
to one of the standards recognized by the
VC-E1/16 (V.22/V.22bis, V.32/V.32bis, and
V.34 up to 21.6 kbps): any unrecognized
protocol is sent as a voiceband signal. The
required bandwidth in this mode is smaller
than that required for voiceband signals.
Default: VOICEBAND DATA
VBD Rate
Determines the coding method and rate used
to transmit voiceband modem signals.
Two basic types of coders, which are both
capable of transferring complex waveforms with
little distortion are used: PCM per ITU-T Rec.
G.711, and ADPCM (ITU-T Rec. G.726). ADPCM
provides performance very close to PCM, but
requires significantly less bandwidth (40 to
50%, depending on version)
G.711 64k 5 msec PCM coder complying

with ITU-T Rec. G.711, operating at a data
rate of 64 kbps, and sending frames every
5 msec.
G.711 64k 10 msec PCM coder complying
with ITU-T Rec. G.711, operating at a data
rate of 64 kbps, and sending frames every
10 msec.
G.726 32k ADPCM coder complying with
ITU-T Rec. G.726, operating at a data rate of
32 kbps (this rate is commonly used in
Europe, and other countries using the
E1-based hierarchy.)
G.726 24k ADPCM coder complying with
ITU-T Rec. G.726, operating at a data rate of
24 kbps (this rate is commonly used in North
America, and other countries using the
T1-based hierarchy.)
Default: G.711 64k 5 msec
5-114
Gmux-2000 Ver. 3.2

Fax/Modem
(cont.)
Fax
Enables/disables fax signal relaying for this
bundle
ENABLE Fax signal relaying is enabled. The
fax signal is identified and demodulated by
the receiving side; the resulting data is
transmitted through the link as a digital
signal, and reconverted to a clean fax signal
at the other side. Each end is also capable of
interpreting the Group III fax handshaking
protocol, to enable setting-up fax calls in
accordance with the fax standards.
DISABLE Fax signal identification is
disabled.
Default: ENABLE
Fax Rate (kbps)
4.8 kbps Maximum fax rate of 4.8 kbps.
Determines the maximum fax transmission rate. 9.6 kbps Maximum fax rate of 9.6 kbps.
When selecting a specific fax rate, you instruct
the VC-E1/16 to operate in the fax relay mode:
the fax signal is demodulated as a Group III fax
signal by the receiving side; the resulting data is
transmitted through the link as a digital signal,
and reconverted to a clean fax signal at the
other side.
Each end is also capable of interpreting the
Group III fax handshaking protocol, to enable
setting-up fax calls in accordance with the fax
standards, including support for rate fallback.
As a result, all the other standard rates lower
than the selected maximum rate are also
supported.
Max. VBD Modem Calls
14.4 kbps Maximum fax rate of 14.4 kbps.

VBD The fax signal is handled as an analog
signal. This mode transparently transfers the
fax modem signal waveform, and therefore
supports many standards. Note however that
the bandwidth needed to transfer a
voiceband signal requires a relatively large
bandwidth (on the order of one timeslot) on
the exit port.
Default: 14.4 kbps
The available range is 1 to 62% of the bundle

bandwidth.
Determines the bundle bandwidth utilization

threshold at which the set up of new voiceband Default: 62
modem calls is blocked.
is ENABLE
Max. Relay Modem Calls
Determines the bundle bandwidth utilization
threshold at which the set up of new modem
calls using the relay mode is blocked.
The available range is 1 to 62% of the bundle

bandwidth.
Default: 62

is ENABLE
Gmux-2000 Ver. 3.2
5-115
MF
Parameters
Used to control the MF processing parameters

for this bundle.
DTMF relaying is always active, irrespective of
the selection made for MF signals (relaying
means that the DTMF signals are decoded, the
corresponding digits and codes are transmitted
as data to the other end, where the original
DTMF signal is regenerated.

MFCR2 RELAY ENABLE MFR2/R2-MFC tone
identification is enabled, and thus tone relay
is enabled.
MFCR2 RELAY DISABLE MF signals
identification is disabled.
Default: DISABLE
The MF signal processing parameters are

selected on a separate screen that opens when
MFCR2 RELAY is ENABLE.
The MF Parameters option is not displayed
when the Coder/Rate parameter is G.711
(A-Law) or G.711 (u-Law), because relaying of
tones is not necessary for these coders, which
transfer complex signals without waveform
distortion
Minimum Pulse Width (msec)
Selects the minimum pulse width of the MF
tone that will be accepted for relaying
Minimum Power Level (dBm)
The supported range is 45 to 300

milliseconds.
Default: 50
The supported range is -1 to -35 dBm.
Selects the minimum power of the MF tone that Default: -20

will be accepted for relaying
MFC Spoofing
Controls the use of MFC tone spoofing
ENABLE MFC tone spoofing is enabled. This

shortens the call setup delay when using
R2-MFC signaling, by forcing an MF Forward
Tone acknowledge after the interval selected
by means of the Tone Ack Interval
parameter.
DISABLE MFC tone spoofing is disabled.
Default: DISABLE
Tone Ack Interval

Determines the tone acknowledge delay.
This parameter is displayed only when MFC
Spoofing is ENABLE
Custom Tone
Detection
The available range is a multiple (N) of

20 msec, where N is 3 to 20 (equivalent to
60 to 400 msec).
Default: 3 (60 msec)
Enable/disable detection and relaying of tones

used by specific types of equipment for this
bundle.
The selection is made on a separate screen
with the following options.
Custom Tone
Detection
(cont.)
Tone Detection
Enable/disable detection and relaying of tones
used by specific types of equipment for this
bundle
ENABLE Custom tone detection and

relaying is enabled.
DISABLE Custom tone detection and
relaying is disabled.
Default: ENABLE
5-116
Gmux-2000 Ver. 3.2

Tone Frequency
Selects the detected tones.
2000 Hz Detection and relaying of 2000 Hz

tones.
This parameter is displayed only when Tone

Detection is ENABLE
1780 Hz Detection and relaying of 1780 Hz

tones.
2000 Hz + 1780 Hz Detection and relaying
of both 2000 Hz and 1780 Hz tones.
Default: 2000 Hz
Super
Tandem
Enable/disable detecting whether voice data

arriving on this bundle has already been
compressed by another VC-E1/16 or Vmux Voice
Trunking Gateway
ENABLE Detection enabled. In this case,

the data is not processed (that is, it is not
decompressed and recompressed), in order
to preserve voice quality.
This function is needed at intermediate
stations along the bundle transmission path.
When ENABLE is selected, it is not possible
to select G.711 (A-Law) or G.711 (u-Law) for
the Coder/Rate parameter.
DISABLE Detection disabled. You can safely
use this selection when the voice port
associated with this bundle cannot receive
compressed voice.
Default: DISABLE
Echo
Canceller
Enable/disable the echo canceller function for

this bundle.
ENABLE The echo canceller function is

enabled.
Echo cancelling is needed only when 2-wire

equipment (phones, fax, modems) are used at
the end points served by this bundle.
DISABLE The echo canceller function is

disabled.
Default: DISABLE
Only one echo canceller should be used at each

end point that connects to 2-wire equipment.
Therefore, if another echo canceller is already
inserted in the signal path, for example, at a
PBX, disable the echo canceller
Coding
Selects the voice companding law for this

bundle (A-law or -law, in accordance with
ITU-T Rec. G.711)
A-Law A-law, the standard companding law

for E1 trunks.
U-Law -law, the standard companding law
for T1 trunks. You may want to use this
setting if the bundle connects to remote
equipment, for example, a Vmux Voice
Trunking Gateway, with T1 interfaces.
Default: A-Law
VAD
Controls the Voice Activity Detection (VAD)

mode for this bundle, and selects the noise
threshold level.
Gmux-2000 Ver. 3.2
5-117
VAD Method
Controls the use of Voice Activity Detection
(VAD) for this bundle

Generic VAD Policy RAD proprietary VAD
method, enables selection of noise threshold
level.
Internal VAD Policy VAD method compatible
with the applicable standards.
Default: Generic VAD Policy
Noise Level for VAD

Selects the noise threshold for the VAD
mechanism.
This parameter is displayed only when VAD
Method is Generic VAD Policy
OFF VAD disabled. This option is not

available when selecting G.711 (A-Law) or
G.711 (u-Law) for the Coder/Rate parameter.
HIGH VAD enabled, and the higher noise
threshold is selected. This selection is
recommended for applications with higher
background noise level.
LOW VAD enabled, and the lower noise
threshold is selected. This is the
recommended setting.
Default: LOW
CNG Mode
Controls the use of the comfort noise

generation (CNG) for for this bundle.
DISABLE Comfort noise generation is

disabled.
The insertion of comfort noise is made at the

ENABLE Comfort noise generation is
receiving end, and thus it is effective only when enabled.
VAD is enabled
Default: DISABLE
Advanced
Voice
Parameters
Provides access to additional parameters

effecting audio signal processing.
The available selections are multiples of

10 msec, in the range of 10 to 100 msec.

Default: 40
Cdis/CONNECTING Detection Time

Select the time needed to detect the presence
of 1100 Hz and 2100 Hz tones, before
switching to the fax or modem mode
5-118
Gmux-2000 Ver. 3.2
5.10 Configuring TS Assignment

Overview of TS Assignment Submenu
The TS Assignment submenu functions depend on the I/O module type:
With pseudowire emulation modules, timeslot assignment can be used to perform
two functions:
To specify the port timeslots served by bundle(s) configured for pseudowire

emulation modules, when the bundle(s) serve only part of the port timeslots.
The port timeslots to be served by a bundle can be selected in two ways:
Select individual timeslots, or a range of timeslots, on the corresponding

port. For the supervision terminal, use Config>TS Assignment.
When a bundle will carry the traffic of a whole E1 port, the connection of
the whole port to the bundle can be initiated either from
Config>TS Assignment, or from the E1 port physical parameters
configuration screen.
To specify the bundle that serves as timing reference when the port uses
adaptive timing. This is performed by connecting a single bundle with
Adaptive Clock = ENABLE to the port.
For voice compression modules, timeslot assignment is needed for the following
purposes:
To specify which voice port timeslots are served by the bundles

configured for voice compression modules
When necessary, to select timeslots for transparent transfer and attach

them to the desired bundle.
To specify the timeslots (that is, the bandwidth) assigned to each

subchannel (and thus, to the bundles connected to that subchannel) on
each voice compression data port. The number of timeslots determines
the transmission bandwidth assigned to each bundle.
You can connect/disconnect a bundle in one step.
Figure 5-73 shows the structure of the TS Assignment submenu.
Gmux-2000 Ver. 3.2
Configuring TS Assignment
5-119

Voice Compression Modules - User (Voice) Ports
TS Assignment
1. Card ss/pp
2. TS Assignment
3. Assign TS Range to Bundle
4. Assign Entire Port to Bundle
or
TS Assignment
Bundle Number: 0
TS Type
: Voice
Dest Port :
0
Dest TS
:
0
ts 2
0
HDLC-1
0
0
ts 3
0
NC
0
0
ts 4
0
Voice
0
0
ts 5
0
SS7-1
0
0
ts 6
0
Voice
0
0
ts 7 . . . ts31
0
0
NC . . . HDLC-1
0
0
0
0
Voice Compression Modules - Data Ports

TS Assignment
Channel Number: 1
TS Type
:
NC
ts 2
1
NC
ts 3
1
NC
ts 4
1
NC
ts 5
1
NC
ts 6
1
NC
ts 7
1
NC
. . . ts31
1
NC
ts 6
1
NC
ts 7
1
NC
. . . ts31
1
NC
Other Ports
TS Assignment
Bundle Number: 1
TS Type
:
NC
ts 2
1
NC
ts 3
1
NC
ts 4
1
NC
ts 5
1
NC

1. Bundle number
2. TS type
3. Dest port
4. From TS
5. Num of TS
6. Connect the TS range to bundle
7. Disconnect the TS range from bundle


1. Bundle Number
2. Connect Entire Port to Bundle
3. Disconnect Entire Port from Bundle

or
1. Sub Channel Number
2. Connect Entire Time Slots to Port
3. Disconnect Entire Time Slots from Port
For Data Ports of

Voice Compression Modules
Figure 5-73. Configuration>TS Assignment Submenu Structure
Timeslot Assignment Procedure for TDMoPSN, HDLCoPSN, and

CESoPSN Bundles
Assigning Individual Timeslots
When you select a specific port, you are provided with a timeslot map that
includes timeslots 1 to 31.
To assign individual timeslots to a Bundle:

1. Select TS Assignment on the Configuration menu.
2. You will see the TS Assignment submenu.
A typical TS Assignment screen is shown in Figure 5-74.
5-120
Gmux-2000 Ver. 3.2
Pseudowire Gateway
1.
2.
3.
4.
Card ss/pp
Ts assignment
Assign TS range to bundle
... (1/1)
[]>
>
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-74. Typical TS Assignment Screen

3. Select the E1 port on which the bundle is terminated to be configured: select
Card ss/pp and enter the number of the I/O slot (1 to 5, 7, 9) and port (1 to
21 for E1-PW-SRV/21 modules, or 1 to 28 for E1-PW/28 modules). Use a
slash / as separator.
4. Select Ts Assignment to display the individual timeslot assignment screen.
A typical screen is shown in Figure 5-75. The figure shows only the
leftmost screen section: to see the other sections, scroll to the right.
Pseudowire Gateway
Configuration>TS Assignment>Ts assignment
TIME SLOT NUM : ts 1 ts 2
Bundle number:
0
0
Ts type:
NC
NC
->>
1. Change cell [1 - 2000]
ts 3
0
NC
ts 4
0
NC
ts 5
0
NC
ts 6
0
NC
ts 7
0
NC
ts 8
0
NC
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-75. Typical Individual Timeslot Assignment Screen (Left-Hand Side)

5. For each timeslot (ts1 to ts31), you need to select the serving bundle:
1. Move the cursor under the desired timeslot in the Bundle row.
2. Select Change Cell and type the prescribed bundle number, in the range
of 1 to 2000. 0 means that the timeslot is not yet connected to a bundle.
Note
The required bundles must be defined before starting timeslot assignment.

6. For each timeslot, you need to select its type. The type determines the
processing of the traffic carried in the timeslot. The selection is made on a
Gmux-2000 Ver. 3.2
5-121
list that appears when the cursor is within the TS Type row. Move the cursor
under the timeslot, and then select Change Cell to make a selection:
Note
NC
Timeslot is not connected to the selected bundle.
FULL DUPLEX
Timeslot is connected to the selected bundle.
As an alternative, you can first use the Assign Entire Port to Bundle to
preconfigure the timeslots and their types, and then modify only the different
timeslots.
7. Use the arrow keys to move the selection block to the desired parameter,
and then type Change cell to change the value. After pressing <Enter> to
confirm the new value, the selected value appears in the table, and the
selection block automatically advances to the next field.
The range of values that can be selected is automatically updated, in
accordance with the position of the selection block.
Notes
When the bundle Payload Type is VOICE/CAS, make sure to connect timeslot 16,
because it carries the CAS information.
8. When done, type S to save before continuing with another server port.
Note
database.
Selecting a Range of Timeslots

You can assign/deassign a contiguous range of timeslots of an E1 port to one
bundle in one step, using Assign TS Range to Bundle on the Configuration>
Connection>TS Assignment screen.
After this step, you can modify the configuration of any desired timeslots,
including timeslots within the assigned range, as explained above.
To assign a range of timeslots:

1. Select Assign TS Range to Bundle to display the configuration screen.
5-122
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>TS Assignment>Assign TS range to bundle
1. Bundle number[1 - 2000]
2. From TS[1 - 31]
3. Num of TS[1 - 31]
... (0)
... (1)
... (31)
>
% - UPD DB
1 M/ 1 C
----------------------------------------------------------------------------
Figure 5-76. Typical Assign TS Range to Bundle Screen

2. Select Bundle Number and enter the prescribed bundle number.
Note
The required bundle must be defined before starting timeslot assignment.

3. Select From TS and enter the starting timeslot number, in the range of 1 to 31.
4. Select Num of TS and enter the total number of timeslots to be assigned
(maximum 31). Make sure that the number of timeslots you specify does not
exceed the following value: 32 - starting timeslot number.
5. Confirm the connection by selecting Connect the TS Range to Bundle.
To disconnect a range of timeslots:

1. Use the same procedure as above, but in Step 5 select Disconnect the TS
Range from Bundle.
Assigning an Entire Port to a Bundle

Note
This procedure is also applicable for SAToPSN bundles.

To assign the entire port to a bundle:
1. Select the bundle to be connected to the currently selected port: select
Assign Entire Port to Bundle to display the bundle selection screen.
2. Initially, the Bundle number field shows 0 (no bundle selected). Select Bundle
number and enter the number of a configured bundle.
3. The screen changes to display the options you have.
A typical Assign Entire Port to Bundle screen, as seen after a bundle has
been selected, is shown in Figure 5-77.
Gmux-2000 Ver. 3.2
5-123
Pseudowire Gateway
Configuration>TS Assignment>Assign entire port to bundle
... (1)
2. Connect entire port to bundle
3. Disconnect entire port from bundle
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-77. Typical Assign Entire Port to Bundle Screen

4. To connect the selected bundle to the port, select Connect entire port to
bundle.
5. When done, type S to save before continuing with another port.
Note
database.
6. Repeat the procedure for all the desired ports.
To disconnect entire port from bundle:

1. To disconnect the selected bundle from the port, select Disconnect entire
port from bundle.
Configuring Timeslot Assignment for Voice Compression Modules

For voice compression modules timeslot assignment is needed for the following
purposes:
5-124
To specify which voice port timeslots are served by the bundles configured
for voice compression modules.
When necessary, to select timeslots for transparent transfer and attach them
to the desired bundle.
To specify the timeslots (that is, the bandwidth) assigned to each subchannel
(and thus, to the bundles connected to that subchannel) on each voice
compression data port. The number of timeslots determines the transmission
bandwidth assigned to each bundle.
Gmux-2000 Ver. 3.2
Configuring Timeslot Assignment for Compressed Voice Ports

The voice port timeslots to be served by a compressed voice (TDMoIP (CV))
bundle can be selected in the following ways:
Select individual timeslots on the corresponding VC-E1/16 voice port. For the
supervision terminal, use Configuration>Connection>TS Assignment.
Select a range of consecutive timeslots on the corresponding Gmux-2000

voice port. For the supervision terminal, use Configuration>Connection>
Assign TS Range to Bundle.
When a bundle will carry the traffic of a whole E1 voice port, the connection
of the whole port to the bundle can be initiated either from Configuration>
Connection>TS Assignment, or from the E1 voice port physical parameters
configuration screen.
To configure individual timeslot assignment to TDMoIP (CV) bundles:

1. Select the voice port on which the bundle is terminated to be configured:
select Card ss/pp and enter the number of the I/O slot (1 to 5, 7, 9) and port
(1 to 16 for VC-E1/16 modules, or 1 to 12 for VC-E1/12 modules). Use a
slash / as separator.
When you select a specific voice port, you are provided with a timeslot
map that includes the available timeslots: for example, if the port uses
FRAMED MF or FRAMED MF - CRC framing, you will see only timeslots 1 to
15, and 17 to 31 (timeslot 16 is reserved for CAS). For FRAMED G.704 or
FRAMED G.704 - CRC framing, all the 31 timeslots are included in the
map. A typical screen is shown in Figure 5-78. The figure shows only the
Pseudowire Gateway
Configuration>TS Assignment>TS assignment
Bundle number:
0
Ts type :
Voice
Dest Port:
0
Dest TS :
0
->>
1. NC
2. Voice
3. HDLC-1
4. SS7-1
ts 2
ts 3
0
0
HDLC-1
NC
0
0
0
0
ts 4
0
Voice
0
0
ts 5
0
SS7-1
0
0
ts 6
0
SS7-1
0
0
ts 7
0
NC
0
0
ts 8
0
HDLC-1
0
0
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-78. Typical Individual Timeslot Assignment Screen for Voice Ports (Left-Hand Side)
Gmux-2000 Ver. 3.2
5-125
3. For each timeslot, you need to select the serving bundle. Move the cursor
under the timeslot in the Bundle row, and then select Change Cell and type
the prescribed bundle number, in the range of 1 to 2000. 0 means that the
timeslot is not yet connected to a bundle.
Note
The required TDMoIP (CV) bundles must be defined before starting timeslot
assignment.
4. For each timeslot, you need to select its type. The type determines the
processing of the traffic carried in the timeslot. The selection is made on a
list that appears when the cursor is within the TS Type row. Move the cursor
under the timeslot, and then select Change Cell to make a selection:
Note
NC
Timeslot is not connected to the selected bundle.
VOICE
Voice timeslot, that is, a timeslot with channel-associated

signaling information.
HDLC-1
Timeslot whose payload is interpreted as HDLC data, for

example, a timeslot that carries CCS data.
SS7-1
Timeslot whose payload is interpreted as being signaling data

per Signaling Scheme 7.
Trans
Transparent timeslot, that is, a timeslot whose payload is

transferred without any processing to the far end (for
example, a timeslot that carries encrypted voice or data).
As an alternative, you can first use the Assign Entire Port to Bundle or Assign TS
Range to Bundle to preconfigure the timeslots and their types, and then modify
only the different timeslots.
5. When operating in a link with the Vmux Voice Trunking Gateway, you need to
specify the destination port and the port timeslot at the Vmux. This is made
by moving the cursor to the Dest Port, respectively Dest TS, rows, and using
the procedure described in Step 1 above to make a selection.
To assign a range of timeslots to a bundle:

1. Select Assign TS Range to Bundle to display the configuration screen.
2. Select Bundle Number and enter the prescribed bundle number, in the range
of 1 to 2000. 0 means that the timeslot is not yet connected to a bundle.
Note
The required bundles must be defined before starting timeslot assignment.

3. Select TS Type and specify the type assigned to all the port timeslots, as
explained in the To configure individual timeslot assignment to TDMoIP (CV)
bundles section above.
4. When operating in a link with the Vmux Voice Trunking Gateway, you need to
specify the destination port and the port timeslot at the Vmux. This is made
by selecting Dest Port row, and entering the prescribed Vmux port number.
5-126
Gmux-2000 Ver. 3.2
Note
Each local timeslot assigned to the selected bundle s automatically connected to

the far-end timeslot with the same number.
5. Select From Ts and specify the first timeslot in the group to be assigned.
Make sure to select a number that allows to include in the bundle the
required number of timeslots, as defined by means of Num of TS: for
example, if the port uses FRAMED MF or FRAMED MF - CRC framing and you
want to connect to the bundle 20 timeslots, the highest timeslot number that
can be selected is 10 (considering that timeslot 16 is assigned to CAS
signaling).
6. Select Num of TS and enter the number of timeslots to be connected to the
selected bundle.
7. Confirm the connection by selecting Connect the TS Range to Bundle.
To disconnect a range of timeslots from the bundle:

1. To disconnect a range of timeslots of a VC-E1/16 voice port that are
connected to a specific bundle in one step, use the procedure described
above but with one difference: in Step 8, instead of selecting Assign TS
Range to Bundle, select Disconnect TS Range from Bundle.
To assign all the port timeslots to a TDMoIP (CV) bundle:

1. Select Assign Entire Port to Bundle to display the configuration screen.
2. Select Bundle Number and enter the prescribed bundle number.
3. Select TS Type and specify the type assigned to all the port timeslots.
4. Select Dest Port and enter the prescribed far end port number.
Note
Each local timeslot is automatically connected to the far-end timeslot with the
same number.
5. Confirm the connection by selecting Connect Entire Port to Bundle.
To disconnect a bundle from a port:

1. To disconnect all the timeslots of a VC-E1/16 voice port that are connected to
a specific bundle in one step, use the procedure described above but with
one difference: in Step 5, instead of selecting Connect Entire Port to Bundle,
select Disconnect Entire Port from Bundle.
Configuring Timeslot Assignment for Data Ports

The utilization of data port bandwidth is controlled by assigning timeslots, that is,
bandwidth, to each subchannel:
Gmux-2000 Ver. 3.2
For an unframed data port, there is only one subchannel. The subchannel is
configured as part of data port physical layer parameters configuration
procedure.
For a framed data port, up to 10 subchannels can be defined (this capability

is required in point-to-multipoint applications). Since each bundle serving a
voice port of the corresponding voice compression module is configured to
5-127
connect to a specific subchannel (see Configuring TDMoIP (CV) Bundle

Parameters section), this also assigns transmission bandwidth on the
connection to the network for each bundle.
The data port timeslots used by a subchannel can be selected in two ways:
Select individual timeslots on the corresponding data port. For the

supervision terminal, use Configuration>Connection>TS Assignment.
When a subchannel will use the full bandwidth of a whole data port, the
connection of the whole port to the subchannel can be initiated either from
Configuration>Connection>TS Assignment or from the E1 data port physical
parameters configuration screen.
To assign individual timeslots to a data port:

1. Select TS Assignment on the Configuration menu.
2. You will see the TS Assignment submenu for data ports.
A typical TS Assignment screen is shown in Figure 5-79.
Pseudowire Gateway
Configuration>TS Assignment>Assign entire TSs to port
1. Sub channel number[1 - 10]
2. Connect entire Time Slots to port
3. Disconnect entire Time Slots from port
... (1)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-79. Typical TS Assignment Screen for Data Ports of Voice Compression Modules
3. Select the data port on which the bundle is terminated to be configured:
select Card ss/pp and enter the number of the I/O slot (1 to 5, 7, 9) and port
(17 to 21). Use a slash / as separator.
When you select a specific data port, you are provided with a timeslot
map that includes timeslots 1 to 31.
A typical screen is shown in Figure 5-80. The figure shows only the
5-128
Gmux-2000 Ver. 3.2
Pseudowire Gateway
TIME SLOT NUM :
Channel number:
Ts mode:
->>
1. NC
2. Connected
ts 1
1
NC
ts 2
1
NC
ts 3
1
NC
ts 4
1
NC
ts 5
1
NC
ts 6
1
NC
ts 7
1
NC
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-80. Typical Individual Timeslot Assignment Screen for Data Port of Voice Compression
Module (Left-Hand Side)
5. For each timeslot, you need to select the subchannel. Move the cursor under
the timeslot in the Sub Channel row, and then select Change Cell and type
the prescribed subchannel number, in the range of 1 to 10. 0 means that no
subchannel is connected to the timeslot.
6. For each timeslot, you need to select its type: CONNECTED or NC (not
connected to the selected subchannel). The selection is made on a list that
appears under the table when the cursor is within the TS Type row. Move the
cursor under the timeslot, and then select Change Cell to make the selection.
Note
As an alternative, you can first use the Assign Entire TSs to Port to preconfigure
the timeslots and their mode, and then modify only the different timeslots.
To assign all the port timeslots to a subchannel:
1. Select Connect Entire Time Slots to Port to display the configuration screen.
2. Select Sub Channel Number and enter the prescribed subchannel number.
3. Confirm the connection by selecting Connect Entire Time Slots to Port.
To disconnect a subchannel from a port:
Gmux-2000 Ver. 3.2
To disconnect all the timeslots of a data port that are connected to a specific
subchannel, use the procedure described above but with one difference: in
Step 5, instead of selecting Connect Entire Time Slots to Port, select
Disconnect Entire Time Slots from Port.
5-129
5.11 Viewing Logistic (Inventory) Information

Use the following procedure to display logistics information on the Gmux-2000
system, and its subsystems.
The information displayed by means of the Inventory menu is automatically
retrieved from the various system components and from the Gmux-2000
configuration and software files. Therefore, it cannot be directly modified.
To display the Inventory menu:

Type 1 on the main menu and then press <Enter>.
A typical Inventory menu is shown in Figure 5-81.
Pseudowire Gateway
Inventory
1.
2.
3.
4.
5.
6.
7.
8.
System
PS
CL
I/O
Bundle
Fan
Clock
Redundancy
>
[]
>
>
>
[]
[]
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-81. Typical Inventory Menu

The menu includes a list of the main components installed in the Gmux-2000
unit. For details on a specific component, type its number and then press
<Enter>.
The information presented for each option is described below.
Displaying the System Inventory

The System submenu is displayed by selecting System on the Inventory menu. A
typical System submenu is shown in Figure 5-82.
The submenu provides two functions:
5-130
System information
Display general logistics information for the Gmux-2000

system.
SW/HW revision
Display the software and hardware versions for the

Gmux-2000 system and each of its main components.
Viewing Logistic (Inventory) Information
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>System
1. System information>
2. SW/HW revision
[]
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-82. Inventory>System Submenu Screen
Displaying System Information

A typical System Information screen is shown in Figure 5-83. Use the N and P
keys to scroll between screen pages.
The parameters appearing on the screen are explained in Table 5-39.
Table 5-39. System Information Parameters
Gmux-2000 Ver. 3.2
Parameter
Description
Product Name
Displays the product name, Gmux-2000
Sys Name
Displays the logical name assigned to this unit by means of the

Configuration>System>Device Info screen
Sys Location
Displays the location information entered by means of the

Configuration>System>Device Info screen
Sys Up Time
Displays the time (in seconds) this Gmux-2000 unit operates

since the last power-up or resetting
Nodal Clock
Displays the synchronization state of the nodal clock generation

system
Online Database
Displays the number of the online database
Major Alarm State
Indicates whether a major alarm is present in the system
Minor Alarm State
Indicates whether a minor alarm is present in the system
Backplane Type
Displays technical information for RAD support personnel
PS Inlet Type
Displays the type of PI module installed in the unit. This unit

determines the type of power source (AC or DC) that may be
connected to the Gmux-2000
5-131
Parameter
Description
I/O Inventory
Provides access to the logistics information available for the

Gmux-2000 system modules
Pseudowire Gateway
Inventory>System>System information
Product name
:
Sys name
:
Sys location
:
Sys Up time
:
Nodal clock
:
Online database :
Major alarm state:
Minor alarm state:
Backplane type
:
PS inlet type
:
1. I/O Inventory
Pseudowire Gateway
643 (Sec)
OK
3
On
Off
GMUX
AC
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-83. Typical System Information Screens
Interpreting the I/O Inventory Screens

Typical I/O Inventory screens are shown in Figure 5-84. The screen has three
pages: the additional page, with I/O 7 to I/O 9, is not shown below because it is
similar to page 2.
Use the N and P keys to scroll between screen pages.
5-132
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>System>System information>I/O Inventory
SLOT
====
PS.1
PS.2
PS.3
CL.1
CL.2
CLK-1
CLK-2
... (N)
>
HW
====
----------------PS-AC
CL
CL
CLK
CLK
SW
====
PS-AC
PS-AC
PS-AC
CL
CL
CLK
CLK
STATUS
======
------------OK
ONLINE
OFFLINE
ONLINE
OFFLINE

1 M/ 1 C
-----------------------------------------------------------------------------

Pseudowire Gateway
Inventory>System>System information>I/O Inventory
... (P)
SLOT
====
FAN
I0-1
I0-2
I0-3
I0-4
I0-5
I0-6
... (N)
>
HW
====
--------Server E1
Server E1
Server E1
----------------GbE
SW
====
--------Server E1
Server E1
Server E1
----------------GbE
STATUS
======
OK
-------------------------------------

1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-84. Typical I/O Inventory Screens
For each chassis slot, the I/O Inventory screen presents three types of
information:
HW
Lists the module installed in the corresponding chassis slot.

----- in this column indicates that the slot is empty.
SW
Lists the module programmed in the corresponding chassis slot.

----- in this column indicates that no module is programmed in
the corresponding slot.
STATUS
Displays the operational status of the module.

----- in the STATUS column indicates that the status information
could not be retrieved, for example, because a module is
programmed but not installed in the corresponding slot.
Gmux-2000 Ver. 3.2
5-133
Interpreting the SW/HW Revision Screens

Typical SW/HW Revision screens are shown in Figure 5-85. Use the N and P keys
to scroll between screen pages.
Pseudowire Gateway
Inventory>System>SW/HW revision
SLOT
CL-A
IO-1
|
v
IO-4
IO-6
CARD
CL
CES E1 PW
CES E1 PW
CES E1 PW
VC16E1-US-NS
VC16E1-US-NS
VC16E1-US-NS
GbE
SW VERSION
3.20B2
0.00U
SC Firmware 0.0
0.0
1.00All
VMX Firmware 1.0
0.0
1.10B2
HW VERSION
1.0
SC Main Board Balan 0.1
RAD TDMoIP ASIC 1.0
VMX Main Board 0.1
DSP 1.0
>
1 M/ 1 C
-----------------------------------------------------------------------------

Pseudowire Gateway
Inventory>System>SW/HW revision
^ SLOT
|
IO-6
IO-9
CARD
VC16E1-US-NS
VC16E1-US-NS
GbE
GbE
GbE
GbE
STM-2
STM-2
SW VERSION
VMX Firmware 1.0
0.0
1.10B2
GE Firmware 1.1
0.0
0.0
2.00D3
SDH Firmware 2.0
HW VERSION
VMX Main Board 0.1
DSP 1.0
GE Main Board 1.0
Switch IXE2424 0.177
PCI Bridge PLX9056 0.186
SDH Main Board 0.0
>
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-85. Typical SW/HW Revision Screen
The information presented in Figure 5-85 displays logistics data that may be
needed by RAD technical support personnel when servicing the unit. The
information is retrieved from the modules installed in chassis.
Displaying PS Inventory Information

The PS screen is displayed by selecting PS on the Inventory menu. It presents the
information read from each of the three PS slots of the chassis.
A typical PS screen is shown in Figure 5-86.
5-134
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>PS
PS-1 :
PS-2 :
PS-3 :
Exist
Yes
Yes
Yes
Type
AC
AC
AC
Input power
220
220
220
Manufacturer
Telkoor
Telkoor
Telkoor
Operational status
O.K
O.K
O.K
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-86. Typical PS Inventory Screen

For each PS module slot, the screen displays the following parameters:
Parameter
Description
Exist
Indicates whether a PS module is installed in the corresponding slot
Type
The type of power supply module, AC or DC, installed in the

corresponding slot
Input Voltage
The actual input voltage, in volts, as measured by the PS module

installed in the corresponding slot
Manufacturer
PS module manufacturer
Operational
Status
Indicates the operational status reported by the module installed in

the corresponding slot
Displaying CL Inventory Information

The CL screen is displayed by selecting CL on the Inventory menu. It presents
information on the CONTROL module installed in the Gmux-2000, as read from
each of the two CTRL slots of the chassis. A typical CL screen is shown in
Figure 5-87. To select a CTRL slot, select 1 on the screen: the information
displayed on the screen is then updated to reflect your selection.
For each CL module slot, the screen displays the following parameters:
Parameter
Description
Module Name
Displays CL, the generic name of the CONTROL module
Admin Status
When two CONTROL modules are installed in the chassis and

CONTROL module redundancy is enabled (AUTO), this field displays
whether the module serves as master (online) or slave (offline) at the
instant the screen display command has been executed by the
Gmux-2000. If CONTROL module redundancy is disabled, only one
module is active (that indicated on the screen).
When only one module is installed, it only indicates that no faults
(O.k) have been detected in the module.
Gmux-2000 Ver. 3.2
5-135
Parameter
Description
Exist
Indicates whether a CONTROL module is installed in the slot
Operation
Status
Indicates the operational status reported by the module installed in

the slot
HW Version
Displays the hardware version of the CONTROL module installed in the

slot
SW Version
Displays the software version of the CONTROL module installed in the

slot
MAC Address
Displays the MAC address of the CONTROL ETH interface of the

CONTROL module
Pseudowire Gateway
Inventory>CL
1. CL[1 - 2]
Module name
Admin status
Exist
HW version
SW version
MAC address
... (1)
>
(CL)
(O.K)
(Yes)
... (1.0)
... ( 3.20B2)
... (0020D220059A)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-87. Typical CL Inventory Screen
Displaying I/O Inventory Information

The I/O screen is displayed by selecting I/O on the Inventory menu. It presents
information on the module installed in a Gmux-2000 slot, as read from the
selected chassis slot.
A typical I/O screen for a module with external ports (in this example, an
E1-PW/28 module installed in slot I/O 1) is shown in Figure 5-88.
The displayed parameters are explained in Table 5-40. The information appearing
on the screen pertains to the module type displayed in the Module Name field;
for I/O modules, check also the I/O slot selected in the I/O slot field.
For modules without external ports, for example, E1-PW-SRV/21 modules, Port
Information is not displayed.
5-136
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>I/O
Module name
Admin status
Exist
HW revision
HW description
SW revision
SW description
1. I/O slot
2. Components details
3. Port information
>
...
...
...
...
>
[]>
[]>
(CES-E1)
(O.K)
(Yes)
(0.1)
(SC Main Board Balan)
( 0.00U )
(SC Firmware)
(IO-1)
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-88. Typical I/O Inventory Screen
To select a specific chassis slot:

1. Select 1 on the screen.
2. You will see the screen of Figure 5-89.
3. Select the number corresponding to the desired slot. After pressing <Enter>,
the information displayed on the screen is updated to reflect your selection.
If in Step 3 you selected an I/O slot, you can also use the F and B keys to
sequentially display information for the I/O slots.
Pseudowire Gateway
Inventory>I/O>I/O slot (IO-1)

1.
2.
3.
4.
5.
6.
7.
8.
9.
IO-1
IO-2
IO-3
IO-4
IO-5
IO-6
IO-7
IO-8
IO-9
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-89. Typical Inventory I/O Slot Selection Screen
Gmux-2000 Ver. 3.2
5-137
Table 5-40. I/O Inventory Parameters

Parameter
Description
Module Name
Displays the generic name of the module in the slot identified in the I/O slot field
Admin Status
When the chassis includes only one module of the type selected in the I/O slot field,
it only indicates that no faults (O.k) have been detected in the module
Exist
Indicates whether a module is installed in the corresponding slot
Operation Status
Indicates the operational status reported by the module installed in the

corresponding slot
HW Revision
Displays the hardware version of the installed in the corresponding slot
HW Description
Displays a description for the hardware of the module installed in the corresponding
slot
SW Revision
Displays the software version of the installed in the corresponding slot
SW Description
Displays a description for the software of the module installed in the corresponding
slot
I/O Slot
Displays the screen (shown in Figure 5-89) used to select a slot
Components Details
For modules including several subsystem: opens an additional screen for RAD
technical support personnel. A typical Components Details screen is shown in
Figure 5-90
Port Information
For modules with external ports, opens an additional screen with information on the
module ports
Pseudowire Gateway
Inventory>I/O>Components details
COMPONENT
SC Main Board
SC Firmware
RAD TDMoIP ASIC
VERSION
0.1
0.0
1.0
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-90. Typical Components Details Screen (GbE Module)
Interpreting the Port Information Screen

Typical Port Information screens are shown in Figure 5-91. For modules with
many ports (see for example, Figure 5-91.B), the screen may comprise several
pages.
5-138
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>I/O>Port information
PORT
1
2
<<-
PORT MODE
Single
Multi
DESCRIPTION
MAC ADDRESS
0020D22124AF
0020D22124AF
STATUS
PORT IS CONNECTED
PORT IS CONNECTED
>
1 M/ 1 C
-----------------------------------------------------------------------------
A. Typical Screen for GbE Ports

Pseudowire Gateway
Inventory>I/O>Port information
PORT
1
2
| 3
v 4
5
6
7
PHY INTERFACE WAVE LENGTH

rj45
N/A
rj45
N/A
rj45
N/A
rj45
N/A
rj45
N/A
rj45
N/A
rj45
N/A
PORT MODE
N/A
N/A
N/A
N/A
N/A
N/A
N/A
DESCRIPTION
E1 RJ45
E1 RJ45
E1 RJ45
E1 RJ45
E1 RJ45
E1 RJ45
E1 RJ45
>
1 M/ 1 C
-----------------------------------------------------------------------------
B. Typical Screen for E1 Ports

Figure 5-91. Typical Port Information Screens
The meaning of the fields appearing in Port Information screens are described
below. The fields actually displayed depend on the specific module.
Parameter
Description
Port
Port index number within the selected module
Phy Interface
The physical interface of the port
Port Mode
For optical ports, indicates whether the type of optical fiber (single or
multi-mode) of the port.
For copper ports, displays N/A (not applicable)
Wave Length
For optical ports, indicates the nominal working wavelength

(850/1310/1550 nm) and transmitter type (LED or laser) of the port.
For copper ports, displays N/A (not applicable)
Description
Gmux-2000 Ver. 3.2
A concise description of the port characteristics
5-139
Displaying Bundle Inventory Information

Information on the bundles (connections) contained in the Gmux-2000 database
can be displayed by selecting Bundle on the Inventory menu.
The screen presents information on the bundle (connection) selected in the
Bundle ID field. You cannot directly select a specific bundle: scroll to the desired
bundle using the F and B keys.
For each bundle you will see a screen comprising, three pages. Use the N and P
keys to scroll between screen pages.
The displayed information is retrieved from the Gmux-2000 database, and cannot
be directly modified: to modify bundle parameters, use the functions available
under the Configuration>Connection submenu (see description starting on page
5-74).
The displayed parameters depend on the bundle type: TDMoIP (CE), HDLCoPSN,
SAToPSN, CESoPSN, or TDMoIP (CV). Refer to the General Bundle Configuration
Procedure section starting on page 5-85 for a description of the parameters
displayed for each type of bundle.
To select a specific connection (bundle):

1. Select Bundle on the Inventory menu.
2. You will see the first bundle (the bundle with the lowest index number)
configured in the Gmux-2000 database. To select another bundle, press F or
B as required until the desired bundle index appears in the Bundle ID field.
Inventory>Bundle -
PseudoWire Gateway
(BUNDLE 1)
Bundle ID[1 - 2000]

Connection mode
PSN type
... (1)
>
(TDMoIP(CE))
>
(UDP/IP)
[]
>
F - next; B - prev;
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-92. Typical Inventory>Bundle Bundle Selection Screen

3. The bundle selection screen presents information on the bundle connection
mode and PSN type. To display the additional bundle information, select
Connection Configuration:
5-140
Typical Bundle connection configuration screens for a TDMoIP (CE) bundle

are shown in Figure 5-93. For a description of the parameters displayed
Gmux-2000 Ver. 3.2
on the screens, refer to Table 5-27 through Table 5-34, in accordance

with the bundle type.
A typical Bundle connection configuration screen for a TDMoIP (CV)

bundle is shown in Figure 5-94. For a description of the parameters
displayed on TDMoIP (CV) screens, refer to Table 5-35 through
Table 5-38.
Pseudowire Gateway
Inventory>Bundle>Connection configuration - (BUNDLE 1)
Connection state
Source CBID
Dest CBID
| Payload format
v TDM byte in frame(x48)
Sensitivity
Enable
22
23
V2
1
3.00
Sensitive to data
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
A. Page 1 of Typical Bundle Inventory Screen

Pseudowire Gateway
^ OAM connectivity
| OAM indication
Payload type
| Far end type
v OOS L bit mode
Destination IP
Network slot port
Enable
Source port number
Data
Framed G.704
Stop TX
2.3.4.9
6/1
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
B. Page 2 of Typical Bundle Inventory Screen
Gmux-2000 Ver. 3.2
5-141
Pseudowire Gateway
^ Network slot port
| Next hop
IP TOS
Adaptive clock
VLAN tagging
VLAN ID
VLAN priority
6/1
0.0.0.0
0
Enable
Enable
15
4
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
C. Page 3 of Typical Bundle Inventory Screen

Figure 5-93. Typical Bundle Inventory Screens (TDMoIP (CE) Bundle)
PseudoWire Gateway
Connection State
Function
3. Voice Parameters
(Disable)
>
(TDMoIP+)
>
... (1400)
... (30)
>
>
>
F - next; B - prev;
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-94. Typical Inventory>Bundle First Parameters Screen for TDMoIP (CV) Bundle
Displaying Fan Inventory Information

The Fan screen is displayed by selecting Fan Device on the Inventory menu. It
presents information on the fan tray module installed in the Gmux-2000. A
typical Fan screen is shown in Figure 5-95.
5-142
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Inventory>Fan
FAN 1-4:
FAN 5-8:
STATUS
Low
Low
EXIST
Yes
Yes
OPERATION STATUS
O.k
O.k
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-95. Typical Fan Inventory Screen

The meaning of the fields appearing on the Fan screen are described below.
Table 5-41. Fan Inventory Parameters

Parameter
Description
Status
Displays the rotation speed of the corresponding fans group:

Low for normal operation, High when more cooling air is
needed
Exist
Indicates whether a fan group is installed
Operation Status
Indicates the operational status reported of the corresponding

fans group
As seen in Figure 5-95, the fan tray includes eight fans, operating as two groups.
Figure 5-96 identifies the fans in each group.
Figure 5-96. Fan Groups Identification
Gmux-2000 Ver. 3.2
5-143
Displaying Timing Subsystem (Clock) Inventory Information

The Clock screen is displayed by selecting Clock on the Inventory menu.
This screen presents information on the timing subsystem of the Gmux-2000, as
read at the time the command is executed by the Gmux-2000. To refresh the
display, open the screen again.
The display includes two rows:
The CLK-1 row is for the timing subsystem located on the CONTROL module
installed in slot CTRL.1
The CLK-2 row is for the timing subsystem located on the CONTROL module
installed in slot CTRL.2.
A typical Clock screen is shown in Figure 5-97.

Pseudowire Gateway
Inventory>Clock
CLK-1
CLK-2
:
:
EXIST
Yes
Yes
STATUS WAITING FOR SYNC

Online
No
Offline
N/A
PLL LOCK
No
N/A
CLOCK STATE
Master
--------
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-97. Typical Clock Inventory Screen

The meaning of the fields appearing on the Clock screen are described below.
Table 5-42. Clock Inventory Parameters

Parameter
Description
Exist
Indicates whether the corresponding timing subsystem is installed
Status
Displays Online for the currently active timing subsystem (this is always on the active
CONTROL module)
Displays Offline for the other timing subsystem (this is always on the offline CONTROL
module)
Waiting for Sync
Displays No when the corresponding timing subsystem is synchronized (normal state).

Yes means that the system is essentially free running, because it did not received a
valid timing synchronization signal.
Displays N/A when the Gmux-2000 has only one timing subsystem (for example, when
only one CONTROL module is installed in the chassis)
PLL Lock
Displays the state of the PLL used to generate the timing signals. Yes means that the
corresponding timing subsystem is synchronized (normal state). No means that the
subsystem is not synchronized, although it may receive receive a valid timing
synchronization signal (see the Waiting for Sync field).
Displays N/A when the Gmux-2000 has only one timing subsystem (for example, when
only one CONTROL module is installed in the chassis)
5-144
Gmux-2000 Ver. 3.2
Parameter
Description
Clock State
Displays Master when the corresponding timing subsystem is configured to supply the
master timing clock, and Fallback when configured as fallback subsystem.
Displays when the Gmux-2000 has only one timing subsystem (for example,
when only one CONTROL module is installed in the chassis)
Displaying Redundancy Information

The redundancy information that can be displayed includes:
Information on APS interfaces
The status of each defined APS group, including the last flip events.
Displaying Information on APS Interfaces
To display information on APS interfaces:

1. Select Inventory>Redundancy>I/O>APS Interfaces.
Pseudowire Gateway
Inventory>Redundancy>I/O>APS Interfaces
|
v
INTERFACE
6:1
6:2
7:1
7:2
8:1
8:2
9:1
APS ID
1
1
0
0
0
0
0
ONLINE
Yes
Yes
N/A
N/A
N/A
N/A
N/A
CHANNEL STATUS
N/A
N/A
N/A
N/A
N/A
N/A
N/A
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-98. Typical Inventory>Redundancy>I/O>APS Interfaces Screen

2. The information is presented as a table that lists all the programmed
interfaces that can be included in APS groups. For the current version, this
includes the STM1 module ports, GbE module ports, pseudowire emulation
server modules, and voice compression modules.
Each interface is identified by the I/O slot number followed by the port
number within the I/O slot (the two numbers are separated by a slash). For
each interface, the following parameters are displayed:
Gmux-2000 Ver. 3.2
5-145
Displays whether the corresponding interface is online, that is, carries traffic:
Online
YES The interface is included in an APS group, and

carries traffic.
NO The interface is included in an APS group, but
does not carry traffic.
N/A The interface is not included in an APS group.
The index number of the APS group in which the
corresponding interface is mapped.
APS ID
The range is 1 to 16; 0 means that the interface is not

yet mapped as part of an APS group.
Port Status
Displays the port state:

Up The port is enabled, and operating OK.
Down The port is down or is not configured as
Connected.
N/A The port is not installed.
The information displayed in the table is correct at the time the table is retrieved
from the Gmux-2000: to refresh, you must read again the table.
Displaying APS Group Status
To display information on the APS group status:

1. Select Inventory>Redundancy>I/O>APS Status.
Pseudowire Gateway
Inventory>Redundancy>I/O>APS Status
APS ID
1
APS NAME
GBE Cards
FLIP CAUSE
No Flip
SWITCHED CH
-:-
FLIP TIME
--:--:--
FLIP DATE
--:--:--
>

1 M/ 1 C
----------------------------------------------------------------------------
Figure 5-99. Typical Inventory>Redundancy>I/O>APS Status Screen
5-146
Gmux-2000 Ver. 3.2
2. The information is presented as a table that lists all the programmed APS
groups. For each group, the following parameters are displayed:
APS ID
The index number of the APS group.
APS Name
The assigned APS group name.
Flip Cause
Displays the cause of the last protection switching

(flipping). The following causes may appear for an APS
group defined on the STM1 module:
No Flip No protection switching took place.
RDN Card not Exist When two modules are
programmed, but the other module has been
removed.
Revert The original port has returned to normal
operation, and traffic has been switched back. No
Flip No protection switching took place.
Link Down Loss of signal.
Revert The original port has returned to normal
operation, and traffic has been switched back to it.
This cause may appear only when using 1:1
bidirectional redundancy.
High Priority Flip The port configured as the High
priority port of the group has returned to normal
operation, and traffic has been switched back to it.
This cause may appear only when the Revertive
mode is used.
Forced Flip Switching initiated by a users
command (this command is sent by means of
Diagnostics>I/O>APS Commands>Force Flip).
Switched Channel
Displays the channel to which the protection switched

the traffic, in the format Slot/Port.
For GbE modules, a specific channel can appear only
when using 1:1 bidirectional redundancy.
Flip Time
The Gmux-2000 system time at which flipping

occurred.
For GbE modules, the time can appear only when using
1:1 bidirectional redundancy.
Flip Date
The Gmux-2000 system date at which flipping

occurred.
For GbE modules, the date can appear only when using
1:1 bidirectional redundancy.
The status information displayed in the table is correct at the time the table is
retrieved from the Gmux-2000: to refresh, you must read again the table.
Gmux-2000 Ver. 3.2
5-147
5.12 Utilities
Overview of Utilities Menu
Figure 5-100 shows the structure of the Utilities menu.
Utilities
1. File Utilities
2. Reset
3. File System
1. Client File Name

2. Server File Name
3. TFTP Server IP
4. TFTP Retry Timeout
5. TFTP Total Timeout
6. Activate TFTP
File Utilities
1. Download/Upload by TFTP
2. Internal Download
3. Internal Upload
Activate TFTP
1. File Download
2. File Upload
Internal Download
1. CL
2. I/O [1 - 9]
Internal Download
Internal Upload
1. CL
2. Slot's File
3. Start SW Load
1. I/O [1 - 9]
2. File Name
3. Start Upload
Reset
1. Reset CL
2. Reset I/O
3. Reboot System
Reset I/O
1. I/O [1 - 9]
2. I/O Reset
File System
1. Dir
2. Copy File
3. Rename File
4. Delete File
5. Format Disk
Dir
1. Dir Online
2. Dir Offline
3. Dir I/O
4. Dir I/O View
For CONTROL modules only

For I/O modules only
Copy File
Rename File
Delete File
Figure 5-100. Utilities Menu Structure
5-148
Utilities
Gmux-2000 Ver. 3.2
Using the File Utilities

Use the following procedure to the File Utilities are used to perform the following
tasks:
Transfer files by TFTP
Download software from files stored on the CONTROL module flash disk to
I/O Gmux-2000 modules that support this capability
Upload files from an I/O module to the CONTROL module flash disk.
To navigate to the required screen, use Utilities>File Utilities.
Selecting a Task
A typical File Utilities screen is shown in Figure 5-101.
Pseudowire Gateway
Utilities>File utilities
1. Download/upload by TFTP
2. Internal download
3. Internal upload
>
>
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-101. Typical File Utilities Screen
To select a specific task:

1. Type its number and then press <Enter>.
Downloading/Uploading by TFTP
TFTP always transfers files to/from the online CONTROL module. In general, you
must repeat the transfer for the other module, after flipping (interchanging)
between the online and offline modules.
Among other purposes, TFTP is used to update the Gmux-2000 software. See
detailed instructions in Appendix B.
To download/upload by TFTP:
1. Type Download/Upload by TFTP and then press <Enter>.
2. You will see the Download/Upload by TFTP screen.
A typical Download/Upload by TFTP screen is shown in Figure 5-102.
Gmux-2000 Ver. 3.2
Utilities
5-149
Pseudowire Gateway
Utilities>File utilities>Download/upload by TFTP
1.
2.
3.
4.
5.
6.
Client file name

Server file name
TFTP server IP
TFTP retry timeout
TFTP total timeout
Activate TFTP
...
...
...
...
...
>
()
()
(0.0.0.0)
(0)
(0)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-102. Typical Download/Upload by TFTP Screen

3. Define the parameters needed for the TFTP transfer:
Note
Type 1 and then press <Enter>. Enter the name of the desired file (for
software, it is usually GMUXCL.IMG) as used for the Gmux-2000 CONTROL
module. When done, press <Enter> to continue.
Type 2 and then press <Enter>. Enter the name of the desired
distribution file as used on the TFTP server (make sure to include the
path, when necessary). When done, press <Enter> to continue.
Type 3 and then press <Enter>. Enter the IP address of the server that
will download the software distribution file (use the dotted quad format),
and then <Enter> to continue.
Type 4 and then press <Enter>. Enter the desired retry time-out interval,
in seconds, for example, 30, and then press <Enter>.
Type 5 and then press <Enter>. Enter the desired total time-out interval,
in seconds, for example, 300, and then press <Enter>.
The retry time-out internal specifies the time to wait for connecting to the
server. After this interval expires, the CONTROL module will try again, and so on,
until the transfer can be started, or the total time-out interval expires: in this
case, the downloading fails.
4. When ready, type % to update the configuration database, and then type 6
and press <Enter> to display the Activate TFTP screen. A typical Activate TFTP
screen is shown in Figure 5-103.
5-150
Utilities
Gmux-2000 Ver. 3.2
Pseudowire Gateway
...>File utilities>Download/upload by TFTP>Activate TFTP
1. File download
2. File upload
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-103. Typical Activate TFTP Screen

5. Select the desired operation by typing its number. The available selections are
as follows:
File Download
Download the specified file from the TFTP server to the

flash disk of the Gmux-2000 CONTROL module. This is
the selection needed to update or install new software
on the Gmux-2000.
File Upload
Upload a file located on the CONTROL module flash disk

from the Gmux-2000 to the specified TFTP server.
6. When ready to start the transfer, press <Enter>.

7. If no errors are detected, the downloading process starts, and the screen
displays its relative progress.
Note
If downloading failed, repeat the whole procedure.

8. After the transfer is successfully completed, the online Gmux-2000 CONTROL
module stores the file on its flash disk.
Internal Software Downloading

The Internal Download screen is used to download software from the flash disk
of the online CONTROL module to a selected module that supports this option,
for example, VC-E1/16 or VC-E1/12.
A typical Internal Download screen is shown in Figure 5-104.
To perform an internal download:

1. Select Internal Download on the File Utilities screen to open the
corresponding screen. A typical Internal Download screen is shown in
Figure 5-104.
Gmux-2000 Ver. 3.2
Utilities
5-151
Pseudowire Gateway
Utilities>File utilities>Internal download
1. CL
2. I/O[1 - 9]
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-104. Typical Internal Download Screen

2. Select the item corresponding to the type of target module (the module you
want to download to). For example, select CL to download software to the
CONTROL module.
Pseudowire Gateway
1. CL
2. Slot's files
3. Start sw load
>
(N/A)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-105. Typical Internal Download Screen CL Selected

3. Now select Slot's files, and then select the file with the proper version. N/A
means that no file suitable for download to the selected target module is
currently stored on the CONTROL module flash disk.
5-152
Utilities
Gmux-2000 Ver. 3.2
Pseudowire Gateway
1. CL
2. Slot's files
3. Start sw load
>
(GMUXCL.IMG)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-106. Typical Internal Download Screen after Selecting a File

4. Press <Enter> to confirm, and return to the Internal Download screen.
5. Wait for downloading to complete. When successfully completed, you will see
Flash programming succeeded. Perform RESET to run new application.
6. To activate the new software, reset the module as follows:
1. Return to the Utilities menu
2. Select Reset.
3. Use the Reset screen to reset the module.
7. After the resetting is successfully completed, you will see the Gmux-2000
log-in screen.
Uploading Files from other Modules to CONTROL Module

The Internal Upload screen is used to upload a selected file from a module that
supports this option, for example, a voice compression module, to the flash disk
of the online CONTROL module.
After the file is stored on the flash disk of the CONTROL module, it can be sent
(uploaded) by TFTP to a management station. For example, this procedure
enables sending the STAT.DAT file of a voice compression module to a
RADview-SC/Vmux Service Center, for analysis.
To perform an internal upload:

1. Select Internal Upload on the File Utilities screen to open the corresponding
screen. A typical Internal Upload screen is shown in Figure 5-107.
2. Select the desired I/O source module (the module you want to upload from).
Note
Gmux-2000 Ver. 3.2
If you select an I/O module which does not support file uploading, you will see
Illegal Slot for this Command.
Utilities
5-153
Pseudowire Gateway
Utilities>File utilities>Internal upload
1. I/O[1 - 9]
... (0)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-107. Typical Internal Upload Screen

3. Now select File Name, and then enter the desired file name.
Pseudowire Gateway
Utilities>File utilities>Internal upload
1. I/O[1 - 9]
2. File name
3. Start upload
... (4)
... (stat.dat)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-108. Typical Internal Upload Screen after Selecting a File

4. Press <Enter> to confirm.
5. At this stage, you may start uploading the file by selecting Start Upload.
6. The uploading is started, and you will File upload. Please wait
7. Wait for the uploading to complete, before starting another activity.
Using the Reset Functions

Use the following procedure to reset a module installed in a specified slot.
Note
Resetting a module will temporarily disrupt services supported by that module.

To navigate to the required screen, use Utilities>Reset.
A typical Reset submenu is shown in Figure 5-109.
5-154
Utilities
Gmux-2000 Ver. 3.2
To reset a module:
1. Select the type of module to be reset:
Reset CL reset a CONTROL module
Reset card reset an I/O module.
2. Select the specific module on the module selection screen, and then select
Reset again.
3. You are requested to confirm the operation.
Pseudowire Gateway
Utilities>Reset
1. Reset CL
2. Reset card
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-109. Typical Reset Submenu
Using the File System Utilities

Use the following procedure to provide management utilities for the disk file
system, located on the CONTROL modules of the Gmux-2000. These functions
are similar to those available under Windows and other PC operating systems.
The files utilities should be used by knowledgeable personnel, familiar with PCs.
Note
The file names are not case-sensitive.

To navigate to the required screen, use Utilities>File System.
A typical File System submenu is shown in Figure 5-110.
Pseudowire Gateway
Utilities>File system
1.
2.
3.
4.
5.
Dir
Copy file
Rename file
Delete file
Format disk
>
>
>
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-110. Typical File System Submenu
Gmux-2000 Ver. 3.2
Utilities
5-155
To select a specific activity:

1. Type the desired number, and then press <Enter>.
Using the Dir Function

A typical Dir task selection screen is shown in Figure 5-111. This screen is used to
select the flash disk whose contents (directory) will be displayed:
Dir online the directory of the flash disk contained in the online CONTROL
module.
Dir offline the directory of the flash disk contained in the offline CONTROL
module. If only one CONTROL module is installed, you cannot use this option.
Dir I/O the directory of the flash disk contained in a selected I/O module,
for example, a voice compression module.
Pseudowire Gateway
Utilities>File system>Dir
1. Dir online
2. Dir offline
3. Dir I/O
[]>
[]>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-111. Typical Dir Task Selection Screen
To select a specific CONTROL module flash disk:

1. Select the desired module (the online or the offline CONTROL module), and
then press <Enter> to display the desired directory.
2. A typical Dir Online screen is shown in Figure 5-112. The display includes the
file names, their size, and the time they were last updated.
Note
5-156
Utilities
Gmux-2000 Ver. 3.2
Pseudowire Gateway
...>File system>Dir>Dir online
NAME
SYSTEM.INI
DB1CONF.BAK
ALARM.CFG
PASSCONF
DB1CONF.OL
ALARM.BAK
SIZE
2
128605
31344
560
128605
31344
DATE
2000-01-01
2000-01-01
2000-01-02
2045-05-15
2000-01-01
2000-01-02
bytes
bytes
bytes
bytes
bytes
bytes
TIME
00:00:00
16:49:00
22:26:18
02:09:40
16:53:04
21:20:50
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-112. Typical Dir Online Screen
To select a specific I/O module flash disk:

1. Select the desired I/O module, and then press <Enter>.
Note
If you select an I/O module which does not support this function, you will see
Illegal Slot for this Command.
2. At this stage, a Dir I/O View item appears, as shown in Figure 5-112.
Pseudowire Gateway
Utilities>File system>Dir
1.
2.
3.
4.
Dir
Dir
Dir
Dir
online
offline
I/O [1 - 9]
I/O view
[]>
[]>
... (4)
[]>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-113. Typical Dir Task Selection Screen After Selecting an I/O Module
3. To display the selected flash disk contents, select Dir I/O View.
Copying Files
Note
You can use the Copy File option to create a new database file by copying an
existing database file.
A typical Copy File screen is shown in Figure 5-114.
Gmux-2000 Ver. 3.2
Utilities
5-157
Pseudowire Gateway
Utilities>File system>Copy file
1. Enter file name you wish to copy ... ()
2. Enter destination file name
... ()
3. Copy file
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-114. Typical Copy File Screen
To copy a file:
1. Select Enter file name you wish to copy and then enter the name of the file,
as displayed on the directory.
2. Select Enter destination file name and then enter the name of the
destination file.
3. Select Copy file to actually perform the action.
Renaming Files
A typical Rename File screen is shown in Figure 5-115.
Pseudowire Gateway
Utilities>File system>Rename file
1. Enter current file name... ()
2. Enter new file name
... ()
3. Rename file
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-115. Typical Rename File Screen
To rename a file:
1. Select Enter current file name and then enter the name of the file, as
displayed on the directory. Make sure the file is not in use, for example, it is
not an online database file.
2. Select Enter new file name and then enter the new file name. Make sure the
new name is not already assigned.
5-158
Utilities
Gmux-2000 Ver. 3.2
3. Select Rename file to actually perform the action.
Deleting Files
A typical Delete File screen is shown in Figure 5-116.
Pseudowire Gateway
Utilities>File system>Delete file
1. Enter file name you wish to delete... ()
2. Delete file
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 5-116. Typical Delete File Screen
To delete a file:
1. Select Enter file name you wish to delete and then enter the name of the file,
as displayed on the directory. Make sure the file is not in use, for example, it
is not an online database file.
2. Select Delete file to delete the file. You must confirm the action.
Formatting Disk
Note
It is not recommended to format the flash disks of the two CONTROL modules at
the same time, unless the Gmux-2000 is not in service. Always take the CONTROL
module on which you wish to format the flash disk offline.
To format the flash disk of a selected CONTROL module:
1. Select Format disk.
2. You will be requested to confirm.
3. After confirming, the formatting begins.
4. After formatting is successfully completed, copy the required file system to
the disk.
Gmux-2000 Ver. 3.2
Utilities
5-159
5-160
Utilities
Gmux-2000 Ver. 3.2
Chapter 6
Configuring Typical
Applications
6.1
Overview
This Chapter provides configuration guidelines for Gmux-2000 systems for several
typical applications.
The configuration activities presented in this Chapter assume that Gmux-2000 is
configured using a standard ASCII terminal, and that you are familiar with the
Gmux-2000 management, as described in Chapter 4. Detailed descriptions and
instructions for using each screen identified below appear in Chapter 5.
Note
In Appendix C, you can find concise descriptions of the Gmux-2000 operating
environment, and technical background information on many Gmux-2000
configuration parameters.
For your convenience, you can find below outlines of the preliminary
configuration sequence, and of the general configuration sequence.
Outline of Preliminary Configuration Sequence

The purpose of the preliminary configuration is to prepare the minimal set of
parameters needed to manage the Gmux-2000. In particular, after preliminary
configuration you will enable management access by Telnet hosts and
management stations, for example, RADview-SC/TDMoIP Service Center, that are
attached to a LAN directly connected to the Ethernet port of the Gmux-2000
CONTROL module, or at a remote location from which IP communication with the
CONTROL module is possible.
After completing the preliminary configuration, you may also use Telnet hosts
and SNMP-based management stations to manage the Gmux-2000.
Note
To enable management access to the Gmux-2000 from any relevant location, it is

necessary to fully configure the Gmux-2000: only full configuration can permit
management traffic to reach the Gmux-2000 via inband paths.
The steps usually included in the preliminary configuration, when starting from
the factory defaults, are described in Table 6-1. For detailed operating
instructions, refer to the Chapter 5 section describing each activity.
Gmux-2000 Ver. 3.2
Overview
6-1
Chapter 6 Configuring Typical Applications
Table 6-1. Gmux-2000, Outline of Preliminary Configuration Procedure

Step
Action
Using
Select the default database, 1 to 5

Alternatively, configure the modules installed Configuration>System>Card Type

in the Gmux-2000
4
Configure the IP communication parameters

of the Gmux-2000 management agent
Configuration>System>Management>Management Access
Configure specific managers and any

required static routes
Configure the Gmux-2000 logistic

parameters
10

management:
If SNMP support mode is changed, save
to activate the change before continuing
2. When SNMPv3 is disabled, configure

SNMP management parameters
Community

SNMP Engine ID
SNMPv3 users
11
Setting>Users
Configuration>System>Management>SNMPv3 Setting>
SNMPv1/v3 Mapping
1. Select the date source, and the date

format
Configuration>System>Date & Time>Date Source, Date

Format
2. When the internal real time clock is used, Configuration>System>Date & Time>Time and Date
set the time of day

12
6-2
Save the configured information in the

selected database
Overview
parameters
Configuration>System>Date & Time>NTP Server, GMT,
Update Interval
Gmux-2000 Ver. 3.2
General Configuration Sequence

Table 6-2 lists the additional steps needed to configure a Gmux-2000 for typical
applications.
Table 6-2. Gmux-2000, Outline of Configuration Sequence for Typical Applications
Step
Action
Using

Configure connection parameters for each bundle
Save the final configuration in the selected database Configuration>Database Tools>Update Database
If necessary, prepare additional databases (up to 5) To start from an existing database, use
Repeat the relevant steps as needed to create a
new database
6.2
Application 1 Transport of Unframed Bundle

from E1 Trunk
Application Overview
The following procedure explains the main configuration actions for transparently
connecting an E1 trunk from an external port of an E1-PW/28 pseudowire
emulation module installed in a Gmux-2000 to the E1 users port of an IPmux-11,
by configuring an unframed bundle.
The application is shown in Figure 6-1.
Note
Gmux-2000 Ver. 3.2
The configuration procedures illustrated below are based on the use of SNMPv1.
Application 1 Transport of Unframed Bundle from E1 Trunk
6-3
Packet
Switched
Network
GbE
E1
ETH
E1
IPmux-11
Gmux-2000
with E1-PW/28
Modules
Network
Management
Station
Figure 6-1. Connecting E1 Trunk to IPmux-11
Gmux-2000 Configuration Procedure

Preliminary Configuration
When powering on the Gmux-2000 for the first time, the first step is to load the
hardware configuration, which means to configure the Gmux-2000 to recognize
the modules installed into the chassis
1. Select Configuration>Database tools>Load hardware.
2. Save and update the database.
3. Open Configuration>System>Card type and then verify proper the correct
hardware configuration: manually update to include any missing modules.
Pseudowire Gateway
SLOT:
DB :
PS-1
PS-AC
PS-2
PS-AC
SLOT:
DB :
IO/1
----------
IO/2
Server-E1-PW
SLOT:
DB :
IO/6
GbE
IO/7
STM-2
PS-3
PS-AC
IO/3
CES-E1-PW
IO/8
GbE
CL-1
CL
CL-2
CL
IO/4
-----------
IO/5
-----------
IO/9
STM-2
1. -----------2. PS-AC
3. PS-DC
Configuring Management
1. Configure the Gmux-2000 IP addresses which will be used for the bundle
connectivity and management. Open Configuration>System>Host IP and enter
the following parameters:
6-4
Gmux-2000 Ver. 3.2
Pseudowire Gateway
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
IP ADDRESS
0.0.0.0
<Gmux Host IP>
0.0.0.0
IP MASK
0.0.0.0
<Gmux Host Mask>
0.0.0.0
DEFAULT GATEWAY
0.0.0.0
<Default GW IP>
0.0.0.0
2. Save the parameters.

3. To allow the Gmux-2000 to be managed by a remote management station
(for example, the RADview-SC/TDMoIP Service Center), the management
station IP address should be added to the manager list.
1. Open Configuration>System>Management>Manager list.
2. Press A to add a manager to the Manager List.
Pseudowire Gateway
1.
2.
3.
4.
5.
MNG NUM[1 - 100]

IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[0 - 4095]
...
...
...
>
(1)
(<NMG Station IP>)
(0.0.0.0)
(GIG A-IO 6/1)
(No)
(No)
... (0)
... (0)

3. Set the SNMP Write community to public to later allow parameters change
using SNMP.
Use Configuration>System>Management>Authentication/Community.
Pseudowire Gateway
1.
2.
3.
4.
5.
Trap community
Read community
Write community
Save parameters
...
...
...
>
(public)
(public)
(public)
(Off)
5. Enable Telnet/SSH and SNMP access, to allow remote management. Use

Configuration>System>Management>Management Access.
Gmux-2000 Ver. 3.2
6-5
Pseudowire Gateway
1. User Access
3. SNMP access
Web access
4. Radius Client
>
>
>
>
>
(Enabled)
(Enabled)
(Disabled)
(Local)
6. Save the parameters and update the database.
Configuring System Clock

1. Verify that the default system clock mode, Internal, is indeed used. Open
Configuration>System>Clock source>System A>Master clock.
Pseudowire Gateway
2. Save parameters
>
(Internal)
Configuring I/O Module Physical Layer Parameters

1. Select a connected GbE interface as the exit interface of the bundles
associated with a specific pseudowire emulation module will be transmitted.
Open Configuration>Physical layer.
Pseudowire Gateway
1.
2.
3.
4.
5.
6.
I/O[1 - 9]
E1 port
First GbE IF
Second GbE IF
Disconnect all slots bundles
... (1)
>
... (6/1)
... (0/0)
2. Save.
3. Configure the Gmux-2000 E1 port characteristics, such as Line Type and Clock
settings. Select Configuration>Physical layer>E1 port.
6-6
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>Physical layer>E1 port - (IO 3: EXT PORT 1 CARD TYPE-CES-E1-PW)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Channel ID[1 - 28]

Admin Status
Idle code[0 - ff]
OOS Signaling
OOS code[0 - ff]
Transmit clk source
Rx Sensitivity
Line type
Restoration Time
... (1)
(Connected)
... (7E)
>
(Space)
... (FF)
>
(System A)
>
(Short Haul)
>
>
(Unframed)
>
(CCITT)
4. Save.
Configuring the Bundle

1. Open Configuration>Connection.
2. Select X to add a new TDMoIP (CE) bundle and select the UDP/IP PSN.
Pseudowire Gateway
1.
2.
3.
4.
5.
Bundle ID[1 - 2000]

Connection mode
PSN type
Connection configuration
Save parameters
>
... (1)
(TDMoIP(CE))
(UDP/IP)
[]>
3. Save.
4. Select Connection configuration.
Gmux-2000 Ver. 3.2
6-7
Pseudowire Gateway
Configuration>Connection>Connection configuration -
|
v
^
|
|
v
^
|
Connection state
Source CBID
Dest CBID
Payload format
TDM byte in frame(x48)
Sensitivity
OAM connectivity
OAM indication
Payload type
Far end type
OOS L bit mode
Destination IP
Network slot port
Next hop
IP TOS
Adaptive clock
VLAN tagging
(BUNDLE 3)
Disable
0
0
V2
1
3.00
Sensitive to data
Enable
Source port number
Data
UNFRAMED
TX OOS and L bit
<Ipmux-11(1) Host IP>
6/1
<Next Hop IP Add>
0
Disable
Disable
5. Save.
Connecting the E1 Port to the Bundle

1. Now associate the bundle with the E1 port 1 of the E1-PW/28 installed in I/O
slot 1 (configured for Unframed mode) by specifying the just-configured
bundle index number. Open Configuration>TS Assignment>Assign entire port
to bundle.
Pseudowire Gateway
... (1)
2. Select Connect entire port to bundle.

3. Wait for the Operation Performed message.
Pseudowire Gateway
1.
2.
3.
4.
Bundle number[1 - 2000]

... (1)
Connect entire port to bundle
Disconnect entire port from bundle
Save port assignment
6-8
Gmux-2000 Ver. 3.2
IPmux-11 Configuration
For the following configuration steps, use the latest IPmux-11 Installation and
Operation Manual.
Host IP and NMS Settings

1. Open Configuration>System>Host IP.
Note
1.
2.
3.
4.
Disable DHCP and save before setting the Host IP parameters.
IP address
IP mask
Default gateway
DHCP
...(<IPmux-11(1) Host IP>)

...(<IPmux-11(1) Host Mask>)
...(-)
(Disable)

1.
2.
3.
4.
5.
Manager IP address
Manager location
Link up/down trap
Alarm trap
VLAN tagging
... (<NMG Station IP>)

>
(All)
(Disable)
(Disable)
(Disable)
3. Open Configuration>System>Management>Authentication/Community.
1.
2.
3.
4.

Trap
Read
Write
(Disable)
... (SNMP_trap)
... (public)
... (public)
E1 Physical Settings
1. Configure the E1 Line Type and verify the correct clock settings. Use
Configuration>Physical layer>TDM configuration (E1).
1.
2.
3.
4.
5.
Channel ID
Admin status
Transmit clock source
Trail mode
Line type
Line interface
>
>
(1)
(Enable)
(Adaptive)
(Termination)
(Unframed G.703)
(DSU)
Bundle Connection Settings

Gmux-2000 Ver. 3.2
6-9
1.
2.
3.
4.
Bundle ID[1]
Connection mode
PSN type
Bundle connection
... (1)
>
(TDMoIP CE)
(UDP/IP)
>
2. Configure the bundle connection parameters to connect it to the bundle

configured on the Gmux-2000:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Next hop
IP TOS[0 - 255]
Connection status
Destination bundle[1 - 8063]
TDM bytes in frame(x48 bytes)[1 - 30]
Payload format
OAM connectivity
Jitter buffer [msec][3 - 300]
VLAN tagging
... (<Gmux Host IP>)

... <Next Hop IP Add>
... (0)
(Enable)
... (1)
... (5)
(V2)
(Enable)
... (15.0)
(Disable
Monitoring the Bundle Traffic

At this stage, the bundle already carries traffic.
On the Gmux-2000, open Monitoring>Status>Connection>Bundle counters to
monitor the bundle traffic, and check that the Connectivity Status is OK.
Pseudowire Gateway
Monitoring>Status>Connection>Bundle counters
1. Bundle ID[1 - 2000]
Connectivity Status
Sequence Errors
Jitter buffer Underflows
Jitter buffer Overflows
Min Jitter buffer Level [Msec]
Max Jitter buffer Level [Msec]
Frames Tx to PSN
Frames Rx from PSN
Min Round Trip Delay [Msec]
Max Round Trip Delay [Msec]
Average Round Trip Delay [Msec]
6-10
...
...
...
...
...
...
...
...
...
...
...
...
...
(1)
(<IPmux-11(1) Host IP>)
(OK)
(0)
(0)
(0)
(3)
(5)
(62419)
(62419)
(0)
(2)
(0)
Gmux-2000 Ver. 3.2
6.3
Application 2 Transport of Framed Bundle

from E1 Trunk
The following procedure explains the main configuration actions for connecting
selected timeslots of an E1 trunk from an external port of an E1-PW/28
pseudowire emulation module installed in a Gmux-2000 to the E1 users port of
an IPmux-11, by configuring a framed TDMoIP (CE) bundle.
The application is as shown in Figure 6-1.
For efficiency, this section presents only the differences between the
configuration steps explained in Section 6.2 and those needed to configure a
framed TDMoIP (CE) bundle.
Gmux-2000 Configuration
Configuring I/O Module Physical Layer Parameters
1. Configure the Gmux-2000 E1 port 2 physical layer parameters for framed
operation.
Pseudowire Gateway
Configuration>Physical layer>E1 port - (IO 3: EXT PORT 1 CARD TYPE-CES-E1-PW)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Channel ID[1 - 28]

Admin Status
Idle code[0 - ff]
OOS Signaling
OOS code[0 - ff]
Transmit clk source
Rx Sensitivity
Line type
Restoration Time
Save parameters
... (1)
(Connected)
... (7E)
>
(Space)
... (FF)
>
(System A)
>
(Short Haul)
>
>
(Framed G.704)
>
(CCITT)
Configuring the Bundle Connection Parameters and its

Timeslot Assignment
2. Select X to add a new TDMoIP (CE) bundle over the UDP/IP PSN. The new
bundle will be automatically assigned index number 2.
Gmux-2000 Ver. 3.2
Application 2 Transport of Framed Bundle from E1 Trunk
6-11
Pseudowire Gateway
1.
2.
3.
4.
5.
Bundle ID[1 - 2000]

Connection mode
PSN type
Save parameters
... (2)
>
(TDMoIP(CE))
(UDP/IP)
[]>
3. Save.
4. Select Connection configuration
Pseudowire Gateway
|
v
^
|
|
v
^
|
Connection state
Source CBID
Dest CBID
Payload format
Sensitivity
OAM connectivity
OAM indication
Payload type
Far end type
OOS L bit mode
Destination IP
Network slot port
Next hop
IP TOS
Adaptive clock
VLAN tagging
(BUNDLE 3)
Disable
0
0
V2
1
3.00
Sensitive to data
Enable
Source port number
Data
E1
TX OOS and L bit
<Ipmux-11(2) Host IP>
6/1
<Next Hop IP Add>
0
Disable
Disable
5. Save.
6. Open Configuration>TS Assignment.
7. Select E1 port 2 of the E1-PW/28 module installed in I/O slot.
Pseudowire Gateway
1. Card ss/pp
2. Ts assignment
3. Assign entire port to bundle
... (1/2)
[]>
>
8. Select TS assignment for assigning individual timeslots of the selected to the

new bundle.
9. Assign timeslots 1 to 5 to the bundle with index number 2.
6-12
Gmux-2000 Ver. 3.2
Pseudowire Gateway
TIME SLOT NUM : ts 1 ts 2 ts 3 ts 4 ts 5 ts 6
Bundle number:
2
2
2
2
2
0
Ts type:
Full Full Full Full Full NC
->>
ts 7
0
NC
ts 8
0
NC
10. Save.
11. Update the Gmux-2000 database.
Operation Manual.
The differences between the configuration steps explained in Section 6.2 and
those needed to configure the IPmux-11 for the framed TDMoIP (CE) bundle are
as follows:
1. Configure as follows:
Host IP address:
<IPmux-11 Host IP>
Host IP Mask:
<IPmux-11 Host Mask>
Manager IP Address:
<NMG Station IP>
E1 Port Line Type:
Framed G.704
E1 Port 2 Tx CLK source:
Adaptive
Bundle ID:
2. Configure TS Assignment as follows:

1. Open TS Assignment.
Connection mode
PSN type
(TDMoIP CE)
(UDP/IP)
1. Bundle ID[1 - 1]
2. DS0 bundle
3. Bundle connection
DS0 bundle
TDM channel ID: 1
... (1)
[]>
>
Bundle ID: 1
+1
+2
TS 0 1
1
TS 10 0
0
TS 20 0
0
TS 30 0
1. Change cell [0
+3
1
0
0
- 1]
+4
1
0
0
+5
1
0
0
+6
0
0
0
+7
0
0
0
+8
0
0
0
+9
0
0
0
+10
0
0
0
... (1)
2. Open Bundle connection.

Gmux-2000 Ver. 3.2
6-13
3. Configure bundle parameters as follows:
Destination IP:
<Gmux-2000 Host IP>
Destination ID:
TDM bytes:
Jitter buffer:
15
OAM
Enable
TDMoIP
V2
Monitoring the Bundle Traffic

At this stage, the bundle already carries traffic.
On the Gmux-2000, open Monitoring>Status>Connection>Bundle counters to
monitor the bundle traffic, and check that the Connectivity Status is OK.
Pseudowire Gateway
1. Bundle ID[1 - 2000]
Connectivity Status
Sequence Errors
Frames Tx to PSN
Frames Rx from PSN
Min Round Trip Delay [Msec]
Max Round Trip Delay [Msec]
Average Round Trip Delay [Msec]
6-14
...
...
...
...
...
...
...
...
...
...
...
...
...
(2)
(192.168.100.12)
(OK)
(0)
(0)
(0)
(3)
(5)
(62419)
(62419)
(0)
(2)
(0)
Gmux-2000 Ver. 3.2
6.4
Application 4 Transport of Unframed Bundle

from SDH Network
The following procedure explains the main configuration actions for transparently
connecting an E1 stream, received from an external port of an STM1 SDH
interface module, through an E1-PW-SRV/21 pseudowire emulation server module
installed in a Gmux-2000, to the E1 users port of an IPmux-14, by configuring an
unframed bundle.
Note
GbE
STM1
SDH
Network
Packet
Switched
Network
ETH
E1
IPmux-14
Gmux-2000
with STM1 and
E1-PW-SRV/21
Modules
Network
Management
Station
Figure 6-2. Connecting E1 Stream from SDH Network to IPmux-14

See preliminary configuration steps in Section 6.2.
Gmux-2000 Configuration
Configuring I/O Modules Physical Layer Parameters
1. Open Configuration>Physical layer and select STM-1 port.
Pseudowire Gateway
1.
2.
3.
4.
I/O[1 - 9]
Operation mode
STM-1 port
VC4 channel
Gmux-2000 Ver. 3.2
... (9)
>
(Terminal mode)
>
>
Application 4 Transport of Unframed Bundle from SDH Network
6-15
2. Configure the STM-1 port parameters.

Configuration>Physical layer>STM-1 port - (IO 9: EXT PORT 1 CARD TYPE- STM-2)
1.
2.
3.
4.
5.
6.
7.
8.
Port STM[1 - 2]
Connect state
AIS on fail
EED threshold
SD threshold
Clock mode
Protection type
Save parameters
... (1)
(Connected)
(Enable)
>
(3)
>
(6)
(LBT)
>
(No protection)
3. Open Configuration>Physical layer and select the internal E1 port 1 in I/O

slot 2.
Configuration>Physical layer>E1 port - (IO 2: E1 PORT 1 CARD TYPE- Server E1)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Channel ID[1 - 21]

Admin Status
Idle code[0 - ff]
OOS Signaling
OOS code[0 - ff]
Transmit clk source
TS type
Line type
Restoration Time
... (1)
(Connected)
... (7E)
>
(Space)
... (FF)
>
(LBT)
... (0)
(Full Duplex)
>
(Unframed G.703)
>
(CCITT)
Configuring the Bundle

1. Open Configuration>Physical layer and select GbE interface 6/1 as the exit
port.
3. Open Configuration>Connection. Select X to add a new TDMoIP (CE) bundle,
and select UDP/IP PSN. The bundle will be automatically assigned index
number 3.
4. Save.
5. Select Connection configuration.
6-16
Gmux-2000 Ver. 3.2
Pseudowire Gateway
|
v
^
|
|
v
^
|
Connection state
Source CBID
Dest CBID
Payload format
Sensitivity
OAM connectivity
OAM indication
Payload type
Far end type
OOS L bit mode
Destination IP
Network slot port
Next hop
IP TOS
Adaptive clock
VLAN tagging
(BUNDLE 3)
Enable
3
1
V2
5
15
Sensitive to data
Enable
Source port number
Data
UNFRAMED
TX OOS and L bit
<IPmux-14(3) Host IP>
6/1
<Next Hop IP Add>
0
Disable
Disable
Connecting the Internal E1 Port to the Bundle

1. Now associate the bundle with the E1 port 1 of the E1-PW-SRV/21 installed in
I/O slot 2 (configured for Unframed mode) by specifying the just-configured
bundle index number. Open Configuration>TS Assignment.
2. Change the Card ss/pp to 2/1.
3. Open Configuration>TS Assignment>Assign entire port to bundle.
Pseudowire Gateway
... (3)
4. Select Connect entire port to bundle.

5. Wait for the Operation Performed message.
Pseudowire Gateway
1.
2.
3.
4.

... (3)
Connect entire port to bundle
Disconnect entire port from bundle
6. Save.
Gmux-2000 Ver. 3.2
6-17
Map the Internal E1 Port to the SDH Interface

1. Open Configuration>Physical layer and configure the following parameters:
Pseudowire Gateway
Configuration>Physical layer>
1.
2.
3.
4.
I/O[1 - 9]
Operation mode
STM-1 port
VC4 channel
.. (9)
>
>
>
(Dual mode)
2. Select the VC4 Channel and configure its parameters (you may leave the
defaults, except for selecting Connected).
3. Select Telecom assignment.
4. Map the E1-PW-SRV/21 port 2/1 to a VC-12, for example:
Pseudowire Gateway
...VC4 Channel>Telecom assignment (IO 9: VC4 Port 1 CARD TYPE STM-2)
| TUG2-1
v add :
drop:
TUG3- 1
TU1 TU2
2/1 0/0
A
NC
A
NC
TUG3TU1 TU2
0/0 0/0
NC NC
NC NC
TU3
0/0
NC
NC
2
TU3
0/0
NC
NC
TUG3TU1 TU2
0/0 0/0
NC NC
NC NC
3
TU3
0/0
NC
NC
Operation Manual.
1. Configure as follows:
6-18
Host IP address:
<IPmux-14 Host IP>
Nest Hop
<Next Hop IP Add>
Host IP Mask:
<IPmux-14 Host Mask>
Manager IP Address:
<NMG Station IP>
T1 Line Type:
Unframed
Tx CLK source:
Adaptive
Bundle ID:
Destination IP:
<Gmux-2000 Host IP>
Destination ID:
TDM bytes:
Jitter buffer:
15
OAM
Enable
TDMoIP
V2
Gmux-2000 Ver. 3.2
6.5
Application 5 Voice Trunking Application
The following procedure explains the main configuration actions for transporting
compressed voice between two MSCs (referred to as West and East) using a pair
of Gmux-2000 units equipped with VC-E1/16 voice compression modules. A
network management station (not shown) is connected to the West Gmux-2000.
Note
MSC
Gmux-2000
MSC
Gmux-2000
5 E1
STM-1
(60 E1)
STM-1
(60 E1)
Figure 6-3. Voice Trunking Application

In the following examples, the following IP parameters are used:
The IP addresses used at the West Gmux-2000 are as follows:

IP Address
Mask
Default Gateway
CL Interface
172.17.92.70
255.255.255.0
172.17.92.1
GbE Module Port
192.168.5.70
255.255.255.0
192.168.5.1
Management Station
192.168.5.100
255.255.255.0
192.168.5.70
The IP addresses used at the East Gmux-2000 are as follows:

IP Address
Mask
Default Gateway
CL Interface
172.17.92.71
255.255.255.0
172.17.92.70
GbE Module Port
192.168.5.71
255.255.255.0
192.168.5.1
Configuring the West Gmux-2000

Preliminary Configuration
When powering on the Gmux-2000 for the first time, the first step is to load the
hardware configuration, which means to configure the Gmux-2000 to recognize
the modules installed into the chassis
1. Select Configuration>Database tools>Load hardware.
3. Open Configuration>System>Card type and then verify proper the correct
hardware configuration: manually update to include any missing modules.
Gmux-2000 Ver. 3.2
6-19
Pseudowire Gateway
SLOT:
DB :
PS-1
PS-AC
SLOT:
DB :
IO/1
VC16E1-US-NE
SLOT:
DB :
PS-2
PS-AC
IO/6
GbE
PS-3
------------
CL-1
CL
CL-2
CL
IO/2
IO/3
IO/4
IO/5
------------ ------------ ------------ -------IO/7
IO/8
------------ ------------
IO/9
STM-2
Configuring Management and IP Communication Parameters

1. Configure the Gmux-2000 IP addresses which will be used for the bundle
connectivity and management. Open Configuration>System>Host IP and enter
the following parameters.
Pseudowire Gateway
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
IP ADDRESS
172.17.92.70
192.168.5.70
0.0.0.0
1. Change cell
IP MASK
255.255.255.0
255.255.255.0
0.0.0.0
DEFAULT GATEWAY
172.17.92.1
192.168.5.1
0.0.0.0
... (255.255.255.0)
2. Press S to Save, then % to update the database.

3. To allow the West Gmux-2000 to be managed via Telnet from the network
management station, the management station IP address should be added to
West Gmux-2000 manager list.
2. Press A to add a manager to the Manager List.
Pseudowire Gateway
1.
2.
3.
4.
5.
MNG NUM[1 - 100]

IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[1 - 4094]
...
...
...
>
(1)
(192.168.5.100)
(0.0.0.0)
(GIG A-IO 6/1)
(Yes)
(No)
... (0)
... (0)
4. Save.
5. To allow the East Gmux-2000 to be managed via Telnet from the West
management station, the East CL IP address should be added to the West
Gmux-2000 Manager List. Press <ESC> and then press A to add a second
manager.
6-20
Gmux-2000 Ver. 3.2
Pseudowire Gateway
1.
2.
3.
4.
5.
MNG NUM[1 - 100]

IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[1 - 4094]
...
...
...
>
(2)
(172.17.92.71)
(0.0.0.0)
(VMUX SLOT 1)
(Yes)
(No)
... (0)
... (0)
6. Save.
7. Set the SNMP communities to later allow parameters change using SNMP. Use
Configuration>System>Management>Authentication/Community.
Pseudowire Gateway
1.
2.
3.
4.
5.
Trap community
Read community
Write community
Save parameters
...
...
...
>
(public)
(public)
(public)
(Off)
8. Enable Telnet/SSH and SNMP access, to allow remote management. Use

Configuration>System>Management>Management Access.
Pseudowire Gateway
1. User Access
3. SNMP access
Web access
4. Radius Client
>
>
>
>
>
(Enabled)
(Enabled)
(Disabled)
(Local)
9. Save the parameters and update the database.
Gmux-2000 Ver. 3.2
6-21
Configuring Physical Parameters of Voice Compression Module

1. Open Configuration>Physical layer and select I/O 1 to configure the VC-E1/16
module in slot 1.
Pseudowire Gateway
1.
2.
3.
4.
5.
6.
7.
8.
9.
I/O[1 - 9]
E1 port voice
E1 port data
VC12 channel
Signaling Profile Config
Bandwidth Control
SS7 Keep-Alive Suppression rate
Disconnect all slot's bundles
... (1)
>
>
>
>
>
>
(0%-No Suppression/Not SS7)
2. Configure voice port 1 physical parameters, using Configuration>Physical

layer>E1 port voice.
... >E1 port voice 1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Pseudowire Gateway
(IO 1: INT E1 VOICE PORT 1 CARD TYPE- VC12E1-US-NE)
Channel ID[1 - 12]

Admin Status
Idle code[0 - ff]
Restoration Time
Transmit clk source
Interface type
Profile [1 5]
Line Type
Q50 protocol
... (1)
(Connected)
... (FF)
>
(Fast)
(System A)
(DSU)
... (1)
>
>
(Framed MF)
>
(Disable)
3. Configure the same parameters for the other voice ports, 2 to 16.
4. Configure the data (uplink) port 1 physical parameters using
Configuration>Physical layer>E1 port data.
6-22
Gmux-2000 Ver. 3.2
...r>E1 port data 1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Pseudowire Gateway
(IO 1: EXT E1 DATA PORT 17 CARD TYPE- VC12E1-US-NE)
Channel ID[1 - 2]
Admin Status
Backup Status
Idle code[0 - ff]
Restoration Time
Transmit clk source
Interface type
LIU impedance
Sub channel configuration
Assign entire Time Slots to port
Line type
... (1)
(Connected)
(Disable)
... (7F)
>
(Fast)
(System A)
(DSU)
(Balance)
[]
>
>
(Framed G.704)
Configuring Physical Parameters of GBE Module

1. Open Configuration>Physical layer and select I/O 6 to configure the GbE
module.
Pseudowire Gateway
1.
2.
3.
4.
5.
I/O[1 - 9]
Arp refresh
L4 pools configuration
GbE port
Monitor Port
... (6)
>
(No Arp Refresh)
>
>
(Auto Negotiation)
2. Leave the GbE port parameters default values.

Pseudowire Gateway
Configuration>Physical layer>GbE port - (IO 6: EXT PORT 1 CARD TYPE- GbE)
1.
2.
3.
4.
GbE port[1 - 2]
Connect state
VLAN valid
Auto Negotiation
... (1)
(Connected)
(No)
(Enable)
Configuring Physical Parameters of STM-1 Module

1. Open Configuration>Physical layer and select I/O 9 to configure the STM-1
module.
Pseudowire Gateway
1.
2.
3.
4.
I/O[1 - 9]
Operation mode
STM-1 port
VC4 channel
... (9)
>
(Dual mode)
>
2. Open Configuration>Physical layer>STM-1 port.
Gmux-2000 Ver. 3.2
6-23
Pseudowire Gateway
Configuration>Physical layer>STM-1 port - (IO 9: EXT PORT 1 CARD TYPE- STM-2)
1.
2.
3.
4.
5.
6.
7.
Port STM[1 - 2]
Connect state
AIS on fail
EED threshold
SD threshold
Clock mode
Save parameters
... (1)
(Connected)
(Enable)
>
(3)
>
(6)
(LBT)
Configuring System Clock

1. Configure Gmux-2000 system clock to be locked to the MSC clock. This clock
will then be distributed to all Gmux-2000 ports. Open
Configuration>System>Clock source>System A>Master clock.
Pseudowire Gateway
2. Master clock source ss pp
3. Save parameters
>
(Rx clk)
... (9/1)
Creating Bundles
Each E1 port (VC12) will have its own dedicated bundle, therefore, for 60 E1
trunks, it is necessary to create 60 bundles, using the same procedure as for
bundle 1.
1. Open Configuration>Connection
Configuration>Connection 1. Bundle ID[1 - 2000]
Pseudowire Gateway
(BUNDLE 0)
... (0)
2. Press X to add the first bundle.

Pseudowire Gateway
Configuration>Connection - (BUNDLE 1)
1. Bundle ID[1 - 2000]
... (1)
2. Connection mode
>
(TDMoIP(CE))
3. PSN type
>
(UDP/IP)
[]>
5. Save parameters
3. Change Connection Mode to TDMoIP (CV) and the PSN type to UDP/IP.
6-24
Gmux-2000 Ver. 3.2
Configuration>Connection 1.
2.
3.
4.
5.
Pseudowire Gateway
(BUNDLE 1)
Bundle ID[1 - 2000]

Connection mode
PSN type
Save parameters
... (1)
>
(TDMoIP(CV))
>
(UDP/IP)
4. Open Configuration>Connection>Connection configuration and configure the

following parameters:
Pseudowire Gateway
2.
3.
4.
5.
6.
7.
8.
Connection State
Function
Routing Parameters
Transparent Jitter size (N*10msec)
Voice Parameters
(BUNDLE 1)
(Disable)
>(UDP/IP+)
>
... (1400)
... (30)
> (4)
>
>
5. Open Configuration>Connection>Connection Configuration>Routing

Parameters and configure the following parameters:
Pseudowire Gateway
...>Connection>Connection Configuration>Routing Parameters -BUNDLE 1)
1.
2.
3.
4.
5.
6.
7.
8.
9.
Destination IP
Next Hop
Source CBID[1 - 8063]
Dest CBID[1 - 8063]
Exit Port
Exit Channel[1 - 10]
TOS Parameters
VLAN Parameters
Save parameters
...
...
...
...
...
...
>
>
(172.17.92.71)
(0.0.0.0)
(1)
(1)
(1/17)
(1)
Assigning Timeslots to Voice Ports

1. To assign timeslots to voice port 1, open Configuration>TS Assignment.
Pseudowire Gateway
1.
2.
3.
4.
Card ss/pp
TS assignment
Assign TS range to bundle
... (1/1)
[]>
>
>
2. Associate voice port 1 to bundle number 1.

3. Connect voice port 1 to destination port 1.
4. Configure the timeslots 1 to 31 of the voice port 1 to carry Voice traffic.
Gmux-2000 Ver. 3.2
6-25
5. Connect the whole timeslot range 1 to 31 to the bundle.

Pseudowire Gateway
Configuration>TS Assignment>Assign TS range to bundle
1.
2.
3.
4.
5.
6.
7.
8.

...
TS type
>
Dest port[1 - 16]
...
From TS[1 - 31]
...
Num of TS[1 - 31]
...
Connect the TS range to bundle
Disconnect the TS range from bundle
(1)
(Voice)
(1)
(1)
(31)
6. Check voice port 1/1 timeslot assignment.

Pseudowire Gateway
TIME SLOT NUM : ts 1 ts 2
Bundle number:
0
0
Ts type:
NC
NC
->>
1. Change cell [1 - 2000]
ts 3
0
NC
ts 4
0
NC
ts 5
0
NC
ts 6
0
NC
ts 7
0
NC
ts 8
0
NC
... (0)
7. To view the other timeslots, press CTRL + R (scroll right).
Map Voice Ports to the STM-1 Link

1. Open Configuration>Physical layer and configure the STM1 module in I/O
slot 9 as follows:
Pseudowire Gateway
1.
2.
3.
4.
I/O[1 - 9]
Operation mode
STM-1 port
VC4 channel
... (9)
>
(Dual mode)
>
Pseudowire Gateway
Configuration>Physical layer>VC4 channel - (IO 9: VC4 PORT 1 CARD TYPE-STM-2)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
6-26
Channel VC4[1 - 2]
Connect state
AIS & RDI on signal label
AIS & RDI on path trace
J1 TX path trace
J1 RX path trace
J1 path trace
EED threshold
SD threshold
Telecom assignment
... (1)
(Connected)
(Enable)
(Enable)
(Enable)
(Disable)
... ()
>
(3)
>
(6)
[]>
Gmux-2000 Ver. 3.2
2. Map the E1 ports to the STM-1 link in accordance with the prescribed
assignment, as follows (for example, voice port 1/1 is mapped to
TUG3-1/TUG2-1/TU12-1).
Pseudowire Gateway
..>VC4 channel>Telecom assignment - (IO 9: VC4 PORT 1 CARD TYPE- STM-2)
TU1
TUG2-1
1/1
add : A
v drop: A
TUG3- 1
TU2
TU3
0/0
0/0
NC
NC
NC
NC
1. Change cell
TU1
0/0
NC
NC
TUG3- 2
TU2
TU3
0/0
0/0
NC
NC
NC
NC
TU1
0/0
NC
NC
TUG3- 3
TU2
TU3
0/0
0/0
NC
NC
NC
NC
... (0/0)
Connecting Bundles
1. Connect bundle number 1 as follows.
Configuration>Connection 1.
2.
3.
4.
Bundle ID[1 - 2000]

Connection mode
PSN type
Pseudowire Gateway
(BUNDLE 1)
... (1)
>
(TDMoIP(CV))
>
(UDP/IP+)
Pseudowire Gateway
2.
3.
4.
5.
6.
7.
Connection State
Routing Parameters
Voice Parameters
Save parameters
(BUNDLE 1)
(Enable)
>
... (1400)
... (30)
>
>
Configuring Voice Ports 2 to 6

1. Repeat the procedure in Creating Bundles to create another 5 bundles
(bundles 2 to 6).
2. Repeat the procedure in Assigning Timeslots to Voice Ports to assign all the
timeslots of the voice ports 2 to 6 of slot 1 as VOICE timeslots.
3. Repeat the procedure in Map Voice Ports to the STM-1, to map the voice
ports 2 to 6 to the next TUs.
4. Repeat the procedure in Connecting Bundles to connect bundles 2 to 6.
Assigning Data Port Timeslots

1. Open all the 31 timeslots of the data port 1/17 (first data channel) using
Configuration>TS Assignment, as follows:
Gmux-2000 Ver. 3.2
6-27
Pseudowire Gateway
1. Card ss/pp
2. TS assignment
3. Assign entire TSs to port
... (1/17)
[]>
Pseudowire Gateway
Configuration>TS Assignment>Assign entire TSs to port
1.
2.
3.
4.
Sub channel number[1 - 10]

Connect entire Time Slots to port
Disconnect entire Time Slots from port
... (1)
2. View the timeslot assignment of data port 1/17 as follows:

Pseudowire Gateway
ts 2
ts 3
ts 4
ts 5
ts 6
ts 7
Channel number: 1
1
1
1
1
1
1
Ts mode:
Connect Connect Connect Connect Connect Connect Connect
->>
3. To view the other timeslots, press CTRL + R (scroll right)
Configuring the East Gmux-2000

Perform the tasks in the Configuring the West Gmux-2000 section again, but this
time on the East Gmux-2000.
Use the following IP addresses:
IP Address
Mask
Default Gateway
CL Interface
172.17.92.71
255.255.255.0
172.17.92.70
GbE Module Port
192.168.5.71
255.255.255.0
192.168.5.1
Therefore, configure the East Gmux-2000 Manager List as follows:

Pseudowire Gateway
1.
2.
3.
4.
5.
MNG NUM[1 - 100]

IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[1 - 4094]
...
...
...
>
(1)
(192.168.5.100)
(172.17.92.70)
(VMUX SLOT 1)
(Yes)
(No)
... (0)
... (0)
For the East Gmux-2000, the destination bundle IP address is

172.17.92.70.
6-28
Gmux-2000 Ver. 3.2
6.6
Inband Management of Gmux-2000 via Voice

Compression TDM Links
The following procedure explains the configuration actions for enabling a network
management station, connected to a central Gmux-2000 unit, to manage a
remote Gmux-2000 unit inband, over a TDM link connecting between VC-E1/16 or
VC-E1/12 modules installed in the central and remote Gmux-2000 units.
The application is shown in Figure 6-4. The connection to the PSN is made
through port 1 of the GbE module in the central Gmux-2000, and the network
management station will connect through the PSN only to this Gmux-2000.
Packet
Switched
Network
Management Station
IP Address:
192.168.5.100
Default Gateway: 192.168.5.70
GbE Port IP Address:
192.168.5.70
GbE Link
TDM Link
Gmux-2000 with
VC-E1/16 and GbE Modules
Online CL IP Address:
172.17.92.70
TDM
Network
TDM Link
Gmux-2000 with
Online CL IP Address: 172.17.92.71
Default Gateway:
172.17.92.70
Figure 6-4. Inband Management of Gmux-2000 via Voice Compression TDM Links
Gmux-2000 Ver. 3.2
Inband Management of Gmux-2000 via Voice Compression TDM Links
6-29
Configuration Procedure
1. Use Configuration>System>Host IP to configure the central and remote
Gmux-2000 CONTROL modules with IP addresses from the same IP subnet.
Example:
Central Gmux-2000 CONTROL module = 172.17.92.70
Remote Gmux-2000 CONTROL module = 172.17.92.71
Default gateway (must be configured as the central Gmux-2000

CONTROL module IP address) = 172.17.92.70
The following figure shows the configuration of the remote Gmux-2000.

Pseudowire Gateway
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
GbE 2/IF 1:
GbE 2/IF 2:
IP ADDRESS
172.17.92.71
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
1. Change cell
IP MASK
255.255.255.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
DEFAULT GATEWAY
172.17.92.70
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
... (0.0.0.0)
>
1 M/ 1 C
----------------------------------------------------------------------------2. Configure the GbE module in the central Gmux-2000 and the network card of
the manager management station with IP addresses in the same IP subnet,
but in subnets different from the subnet of the Gmux-2000 CONTROL
module.
Example:
GbE module = 192.168.5.70
Management station network card = 192.168.5.100
The following figure shows the configuration of the central Gmux-2000.

Nota that in this example the default gateway is left unchanged: in a real
application, you need to enter here the IP address of the PSN edge router
port, through which the connection to the PSN is made.
6-30
Gmux-2000 Ver. 3.2
Pseudowire Gateway
INTERFACE
ONLINE CL:
GbE 1/IF 1:
GbE 1/IF 2:
GbE 2/IF 1:
GbE 2/IF 2:
IP ADDRESS
172.17.92.70
192.168.5.70
0.0.0.0
0.0.0.0
0.0.0.0
1. Change cell
IP MASK
255.255.255.0
255.255.255.0
0.0.0.0
0.0.0.0
0.0.0.0
DEFAULT GATEWAY
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
... (0.0.0.0)
>
1 M/ 1 C
----------------------------------------------------------------------------3. Configure the Manager List in the central Gmux-2000 unit to include the IP
addresses of the management station IP port and its exit interface, and the
remote Gmux-2000 CONTROL module and exit interface.
Example:
192.168.5.100 (this is the IP address of the management station),

exit interface = GbE port 6/1 (or port 8/1, if the GbE module is
inserted in slot 8)
172.17.92.71 (this is the CONTROL module IP address of the remote
Gmux-2000), exit interface = VC-E1/16 or VC-E1/12 in slot 1
The following figure shows the configuration of the central Gmux-2000.

Pseudowire Gateway
MNG NUM
1
2
IP ADDRESS
192.168.5.100
172.17.92.71
NEXT HOP
0.0.0.0
0.0.0.0
INTERFACE
GIG A 6/1
VMUX SLOT 1
>
1 M/ 1 C
----------------------------------------------------------------------------4. Configure the Manager List in the remote Gmux-2000 unit to include the IP
address of the management station, and the next hop = CONTROL module IP
address of the central Gmux-2000 and exit interface.
Example:
Gmux-2000 Ver. 3.2
192.168.5.100 (this is the IP address of the management station),

next hop = 172.17.92.70, exit interface = VC-E1/16 or VC-E1/12 slot 1
6-31
The following figure shows the configuration of the remote Gmux-2000.

Pseudowire Gateway
MNG NUM
1
IP ADDRESS
192.168.5.100
NEXT HOP
172.17.92.70
INTERFACE
VMUX SLOT 1
>
1 M/ 1 C
----------------------------------------------------------------------------5. Configure the management station default gateway as the IP address of the
central Gmux-2000 GbE module (192.168.5.70).
This completes the basic configuration: now, when the management station looks
for the CONTROL module IP address of central Gmux-2000 CONTROL module,
172.17.92.70, or the CONTROL module IP of the remote Gmux-2000,
172.17.92.71, it will use the Gmux-2000 GbE module (192.168.5.70).
You can use Telnet to contact the local Gmux-2000 unit (172.17.92.70) or the
remote Gmux-2000 (172.17.92.71) from the management station, and verify
that you have access to the configuration menus.
6-32
Gmux-2000 Ver. 3.2
Chapter 7
Troubleshooting and
Diagnostics
This Chapter describes Gmux-2000 troubleshooting and diagnostic functions,
which include:
Collection of performance monitoring data
Reporting of configuration (sanity) errors
Alarm and event collection, and reporting of relevant alarms by means of

traps
Diagnostic tests for checking transmission paths
Ping for IP connectivity testing.
These functions can be used to identify problems in the network incorporating

Gmux-2000 units, test the proper operation of each Gmux-2000 unit, and locate
rapidly the cause of the fault: within the Gmux-2000 itself, in its connections to
the network or to a users equipment unit, or in the another network component.
In addition to the general Gmux-2000 functions described in this Chapter, you
can find information on the module-specific diagnostic functions in the
Installation and Operation Manual of each module.
If you need additional support for this product, see Section 7.7 for technical
support information.
7.1
Monitoring Performance
The Gmux-2000 collects transmission performance data for its various ports. The
collected data enables the system administrator to monitor the transmission
performance, and thus the quality of service provided to users, for statistical
purposes.
In addition, when problems are reported by users served by Gmux-2000, the
collected data can be used for diagnostic purposes, because it can help identify
the source of the problem.
The data is continuously collected during equipment operation.
For TDM ports, the basic performance data is calculated for each second, and
accumulated and displayed over a 15-minute (900 second) interval. The data
accumulated within the last 24-hour interval is also stored and displayed.
Gmux-2000 Ver. 3.2
7-1
Chapter 7 Troubleshooting and Diagnostics
Overview of Monitoring Menu

When using the supervisory terminal, the access to the performance monitoring
functions is via the Monitoring menu.
For your convenience, Figure 7-1 shows the structure of the Monitoring menu.
You can use this figure as a navigation map for monitoring activities.
Monitoring
Security Key
1. Statistics
2. Status
3. Event Log
4. Alarm
Physical Layer
Statistics
Connection
1. Physical Layer
2. Connection
1. Bundle Current PM
2. Bundle Intervals PM
Physical Layer
Status
Connection
1. Physical Layer
2. Connection
1. Bundle Counters
Alarm Buffer Type (History)

Event Log
Read Log
1. History
2. Status
3. Both
1. Read Log
2. Clear Log
Clear Log
1. Alarm Buffer Type
2. Alarm Priority
3. Alarm Level
4. Alarm Sub-Level
5. Clear Alarms
Alarm Priority
Alarm Level
Alarm
1. SYSTEM
2. PS_A
3. PS_B
4. PS_C
5. CL_A
6. CL_B
7. IO_1
8. IO_2
9. IO_3
10. IO_4
1. Display System Alarm

2. Display PS Alarms
3. Display CL Alarms
4. Display I/O Alarms
5. Display Bundle Alarm
6. DSP All Alarms
Display PS Alarms
11. IO_5
12. IO_6
13. IO_7
14. IO_8
15. IO_9
16. BUNDLE
17. SPECIFIC
18. ALL
Display CL Alarms
Display I/O Alarms
Depends on Selection on Alarm Level

Alarm Sub-Level

DSP All Alarms
1. Slot
2. "External Port"
3. "Internal Port"
Figure 7-1. Monitoring Menu Structure
7-2
Gmux-2000 Ver. 3.2
Note
The SSH indicator in the top line of the Monitoring menu indicates that the
security key needed for SSH is stored in the CONTROL modules (this key is
generated when a new CONTROL module is first put into operation). If the SSH
indicator does not appear, the CONTROL module should be serviced.
Selecting a Monitoring Task

Use the following procedure to select the type of monitoring activity:
Display performance monitoring statistics for the Gmux-2000 physical

interfaces and connections (bundles)
Display status information for physical interfaces and connections
Read the alarm history recorded in the log file, and clear desired alarms
Read the current alarms. You can select the type of alarms to be displayed.
To navigate to the required screen, use Monitoring.

A typical Monitoring task selection screen is shown in Figure 7-2.
Pseudowire Gateway
Monitoring
1.
2.
3.
4.
Security Key
Statistics
Status
Event log
Alarm
>
>
>
>
>
(SSH)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-2. Monitoring Task Selection Screen
To select a monitoring activity:

1. Type the number of the desired activity, and then press <Enter>.
Displaying Performance Monitoring Statistics

Use the following procedure to read the performance monitoring statistics
collected by the Gmux-2000.
Statistics are collected for the physical layer, and for the active connections
(bundles).
Gmux-2000 Ver. 3.2
7-3
To navigate to the required screen, use Monitoring>Statistics.

A typical Statistics type submenu is shown in Figure 7-3.
Pseudowire Gateway
Monitoring>Statistics
1. Physical layer
2. Connection
>
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-3. Typical Statistics Type Submenu
To select the type of performance monitoring statistics to be displayed:

1. Type the number of the desired type of performance monitoring statistics,
Displaying Physical Layer Statistics Parameters

Use the following procedure to display physical layer performance monitoring
statistics.
This section presents general information, which applies to most types of
physical ports supported by Gmux-2000. For module-specific information, for
example, for voice compression modules, refer to the Installation and Operation
Manual of the corresponding module.
To navigate to the required screen, use Monitoring>Statistics>Physical Layer.
A typical Physical Layer Statistics submenu for an E1 port is shown in Figure 7-4.
Pseudowire Gateway
Monitoring>Statistics>Physical layer
1. I/O[1 9]
2. E1 port
3. VC12 channel
...
>
>
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-4. Typical Physical Layer Statistics Submenu for E1 Port

7-4
Gmux-2000 Ver. 3.2
To select a statistic screen:

1. Select Slot number and then type the number of the desired I/O slot, 1 to 9,
or
Use the F or B key to sequentially display I/O slots in the Slot number field.
2. The other items on the screen are automatically updated in accordance with
the type of ports on the I/O module installed in the corresponding slots.
3. Select the appropriate item to display the performance monitoring statistics
screen for the selected slot and then select a specific port or VC, and also
select whether you want to see statistics for the current 15-minute interval,
or for one of the up to 96 intervals that can be stored. Typical screens are
shown in the following figures:
A typical Port Current interval screen for E1 ports is shown in Figure 7-5.
A typical Port Intervals screen for E1 ports is shown in Figure 7-6.
A typical Port Current screen for VC-12 channels is shown in Figure 7-7.
A typical Port Intervals screen for VC-12 channels is shown in Figure 7-8.
A typical Port Current screen for STM-1 ports is shown in Figure 7-9.
A typical Port Intervals screen for STM-1 ports is shown in Figure 7-9.
A typical Port Current screen for VC-4 channels is shown in Figure 7-11.
A typical Port Intervals screen for VC-4 channels is shown in Figure 7-12.
Refer to Table 7-1 for a description of the performance monitoring parameters.

Pseudowire Gateway
Monitoring>Statistics>Physical layer>E1 port>Port current pm
1. E1 port[1 28]
Time Elapsed [Sec]
ES
SES
UAS
LCV
Valid intervals
...
...
...
...
...
...
...
(1)
(500)
(0)
(0)
(9)
(0)
(0)
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-5. Typical E1 Port Current Statistics Screen
Gmux-2000 Ver. 3.2
7-5
Pseudowire Gateway
Monitoring>Statistics>Physical layer>E1 port>Port intervals pm
1. E1 port[1 28]
... (1)
2. Interval Number[1 96]
... (1)
ES
... (0)
SES
... (0)
UAS
... (9)
LCV
... (0)
>
F next; B prev; > - next interval; < - prev interval
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-6. Typical E1 Port Intervals Screen

Pseudowire Gateway
Monitoring>Statistics>Physical layer>VC12 channel>Port current pm
1. Channel VC12[1 21]
... (1)
Time Elapsed [Sec]
... (614)
ES
... (0)
SES
... (0)
UAS
... (0)
CV
... (0)
Valid intervals
... (0)
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-7. Typical VC-12 Channel>Port Current Screen

Pseudowire Gateway
Monitoring>Statistics>Physical layer>VC12 channel>Port intervals pm
1. Channel VC12[1 21]
... (1)
... (1)
ES
... (0)
SES
... (0)
UAS
... (0)
CV
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-8. Typical VC-12 Channel>Port Intervals Screen
7-6
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Monitoring>Statistics>Physical layer>STM-1 port>Port current pm
1. Port STM[1 2]
... (1)
Time Elapsed [Sec]
... (824)
ES
... (0)
SES
... (0)
SEFS
... (0)
CV
... (0)
Valid intervals
... (0)
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-9. Typical Port Current Screen for STM-1 Port

Pseudowire Gateway
Monitoring>Statistics>Physical layer>STM-1 port>Port intervals pm
1. Port STM[1 2]
... (1)
... (1)
ES
... (0)
SES
... (0)
SEFS
... (0)
CV
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-10. Typical Port Intervals Screen for STM-1 Port

Pseudowire Gateway
Monitoring>Statistics>Physical layer>VC4 channel>Port current pm
1. Channel VC4[1 1]
... (1)
Time Elapsed [Sec]
... (383)
ES
... (0)
SES
... (0)
UAS
... (0)
CV
... (0)
Valid intervals
... (1)
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-11. Typical Port Current Screen for VC-4 Port
Gmux-2000 Ver. 3.2
7-7
Pseudowire Gateway
Monitoring>Statistics>Physical layer>VC4 channel>Port intervals pm
1. Channel VC4[1 1]
... (1)
... (1)
ES
... (0)
SES
... (0)
UAS
... (0)
CV
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-12. Typical Port Intervals Screen for VC-4 Channel

Table 7-1. Physical Layer Performance Monitoring Parameters
Parameter
Description
Interval Number
The number of the 15-minute interval to be displayed, in the range of 1 to 96.

The default value is 0 (zero), which designates the current interval. However, you can
also select another interval, by typing 1 and then pressing <Enter>: you can then enter
the desired interval number, up to the number displayed in the Valid Intervals field.
Valid Intervals
The number of intervals (up 96 intervals) for which performance monitoring information
can be displayed.
Elapsed Time
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
7-8
Gmux-2000 Ver. 3.2
Parameter
Description
ES
Displays the number of errored seconds (ES) in the selected interval.

For SDH ports, an errored second is any second containing one or more of the following
types of errors:
Severely Errored Frame (SEF) defect (also called Out-of-Frame (OOF) event):
A SEF defect is declared after detection of four contiguous errored frame

alignment words.
The SEF defect is terminated when two contiguous error-free frame words are
detected.
Loss of Signal (LOS) defect:
A LOS defect is declared after when no transitions are detected in the incoming
line signal (before descrambling) during an interval of 2.3 to 100 microseconds.
The LOS defect is terminated after a 125-microsecond interval (one frame)

during which no LOS defect is detected.
Loss of Pointer (LOP) defect:
A LOP defect is declared after no valid pointer is detected in eight consecutive

frames. The LOP defect will not be reported while an AIS signal is present.
The LOP defect is terminated after a valid pointer is detected.
Alarm Indication Signal (AIS) received in the SDH overhead.
Coding Violation (CV): a coding violation is declared when a Bit Interleaved Parity
(BIP) error is detected in the incoming signal. The BIP information is collected using
the B1 byte in the Section Overhead.
For PDH (E1) ports, an errored second is a second with one or more coding violations
(CVs or LCVs), and/or one or more of the following defects: reception of AIS, loss of line
signal (for external ports only).
SES
Displays the number of severely errored seconds (SES) in the current interval.
For SDH ports, a SES is any second during which multiple error events of the types
taken into consideration for an ES have occurred.
For PDH (E1) ports, a SES is any second with more than 40 coding violations (CVs or
LCVs), and/or one or more of the defects taken into consideration for an ES.
UAS or SEFS
Displays the number of unavailable seconds (UAS) or severely errored framed seconds
(SEFS) in the current interval.
For SDH ports, an unavailable second is any second in which one or more SEF defects
have been detected.
For PDH (E1) ports, UAS is declared after 10 continuous SESs. During UASs, all the other
defect counters are freezed.
CV
Displays the number of coding violations (CV) in the selected interval.

A coding violation is declared when a Bit Interleaved Parity (BIP) error is detected in the
incoming signal, and it indicates that errors have been detected in the received signal.
This parameter is available only for SDH ports
Gmux-2000 Ver. 3.2
7-9
Parameter
Description
LCV
Displays the number of line coding violations (LCV) in the current interval.
A line coding violation is declared when a line signal decoding error occurs at the receive
side (such errors commonly occur when the receive signal level is too low, usually as a
result of excessive line attenuation between the transmit and receive ports).
This parameter is available only for external (E1) ports
Displaying Connection Statistics for TDMoIP (CE) Bundles

Display performance monitoring data for TDMoIP (CE) connections (bundles).
This section presents general information, which applies to most types of
connections supported by Gmux-2000. For additional module-specific
information, refer to the module Installation and Operation Manual.
To navigate to the required screen, use Monitoring>Statistics>Connection.
To display connection (bundle) statistics:

1. Select the Statistics monitoring task.
2. Select the Connection option. You will see the bundle statistics Connection
Statistics selection submenu. A typical submenu is shown in Figure 7-13.
Pseudowire Gateway
Monitoring>Statistics>Connection
1. Bundle current pm
2. Bundle intervals pm
>
>
>
bundle configuration statistics
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-13. Typical Statistics Submenu Connection Screen for TDMoIP (CE) Bundles
3. Select the type of statistics you want to see:
Statistics for the current 15-minute interval.
Statistics for one of the up to 96 intervals that can be stored
4. After selecting the type of statistics, select the desired Bundle ID by

specifying its number, in the range of 1 to 2000. You can select only existing
TDMoIP (CE) bundles.
5. After selecting a specific bundle, the bundle data are immediately displayed.
A typical Bundle Current screen is shown in Figure 7-14, and a typical Bundle
Intervals screen is shown in Figure 7-15.
7-10
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Monitoring>Statistics>Connection>Bundle current pm
1. Bundle ID[1 2000]
Time Elapsed [Sec]
Sequence Errors Seconds
Jitter buffer Underflows Seconds
Jitter buffer Overflows Seconds
Min Jitter buffer level [Msec]
Max Jitter buffer level [Msec]
Max Jitter buffer deviation [Msec]
Valid Intervals
...
...
...
...
...
...
...
...
...
(1)
(562)
(0)
(0)
(0)
(5)
(5)
(0)
(1)
>
F next; B prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-14. Typical Bundle Current Screen for TDMoIP (CE) Bundles
Pseudowire Gateway
Monitoring>Statistics>Connection>Bundle intervals pm
2. Interval Number[1 - 96]
Sequence Errors Seconds
Jitter buffer Underflows Seconds
Jitter buffer Overflows Seconds
Min Jitter buffer level [Msec]
Max Jitter buffer level [Msec]
Max Jitter buffer deviation [Msec]
...
...
...
...
...
...
...
...
(1)
(1)
(0)
(8)
(5)
(0)
(5)
(5)
>
F next; B prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-15. Typical Bundle Intervals Screen for TDMoIP (CE) Bundles
The connection (bundle) statistics parameters are explained in Table 7-2.
Table 7-2. Connection (Bundle) Statistics Parameters for TDMoIP (CE) Bundles
Parameter
Description
Time Elapsed
Total time (in seconds) since the current interval started
Sequence Errors
Seconds
Total number of seconds with packet sequence errors in the selected interval
Jitter Buffer
Underflows Seconds
Total number of seconds with jitter buffer underflow events in the selected interval
Gmux-2000 Ver. 3.2
7-11
Parameter
Description
Jitter Buffer Overflows

Seconds
Total number of seconds with jitter buffer overflow events in the selected interval
Min Jitter Buffer Level

[Msec]
Actual minimum size of the jitter buffer recorded for this bundle in the selected
interval, in msec
Max Jitter Buffer Level

[Msec]
Actual maximum size of the jitter buffer recorded for this bundle in the selected
interval, in msec
Max Jitter Buffer

Deviation [Msec]
Maximum peak-to-peak jitter variation for this bundle in the selected interval, in
msec
Displaying Status Information

Use the following procedure to display status information.
Status information can be displayed for the physical layer, and for active TDMoIP
(CV) connections (bundles).
To navigate to the required screen, use Monitoring>Status.
A typical Status task selection submenu is shown in Figure 7-16.
Pseudowire Gateway
Monitoring>Status
1. Physical layer
2. Connection
>
>
>
dsp status
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-16. Typical Status Submenu
To select the type of status monitoring activity:

1. Type the number of the desired activity, and then press <Enter>.
Displaying Physical Layer Status Parameters (GbE Modules)

Use the following procedure to display physical layer status information.
This type of information is available for GbE modules, and is used to display and
analyze the traffic characteristics and the switching performance of the module.
7-12
Gmux-2000 Ver. 3.2
To navigate to the required screen, use Monitoring>Status>Physical Layer.

To display physical layer status information:
1. Select the I/O slot in which the module of interest is installed.

You will see the Physical Layer submenu, used to select a specific module
port. A typical Physical Layer submenu for the GbE module is shown in
Figure 7-17.
Pseudowire Gateway
Monitoring>Status> Physical layer
1. I/O[1 9]
2. GbE port
... (6)
>
>
physical configuration status
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-17. Typical Physical Layer Submenu for GbE Module

2. Select the port of interest.
You will see the GbE Port screen, used to select the status parameters to
display. A typical GbE Port screen is shown in Figure 7-18.
Pseudowire Gateway
Monitoring>Status>Physical layer>GbE port
1.
2.
3.
4.
GbE
GbE
GbE
GbE
port
port
port
port
counters
counters (continue)
frame type counters
pause counters
>
>
>
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-18. Typical GbE Port Screen

3. Select the type of parameters to display.
A typical GbE Port Counters screen is shown in Figure 7-19. The
parameters displayed on the screen are explained in Table 7-3.
Gmux-2000 Ver. 3.2
7-13
A typical GbE Port Frame Type Counters screen is shown in

Figure 7-20. The parameters displayed on the screen are explained in
Table 7-4.
A typical GbE Switch Pause Counters screen is shown in Figure 7-21. The
parameters displayed on the screen are explained in Table 7-5.
Pseudowire Gateway
Monitoring>Status>Physical layer>GbE port>GbE port counters
1. GbE port[1 2]
Rx correct pkts
Tx correct pkts
Rx correct octets
Tx correct octets
Rx correct unicast pkts
Tx correct unicast pkts
Rx discard pkts
Tx discard pkts
Rx interface errors
Tx interface errors
Rx unknown protocol
...
...
...
...
...
...
...
...
...
...
...
...
(1)
(202816552)
(197011676)
(891534613)
(304772428)
(202812452)
(197011691)
(0)
(0)
(0)
(0)
(0)
>
F next; B prev; R reset counters
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-19.A. Typical Page 1 of GbE Port Counters Screen

Pseudowire Gateway
Monitoring>Status>Physical layer>GbE port>GbE port counters (continue)
1. GbE port[1
Rx multicast
Tx multicast
Rx broadcast
Tx broadcast
2]
ok
ok
ok
ok
...
...
...
...
...
(1)
(3929)
(0)
(434)
(11)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-19.B. Typical Page 2 of GbE Port Counters Screen
7-14
Gmux-2000 Ver. 3.2
Table 7-3. GbE Port Counters Parameters

Parameter
Description
Rx Correct pkts
Total number of good frames received through the corresponding GbE port
Tx Correct pkts
Total number of good frames transmitted through the corresponding GbE port
Rx Correct Octets
The total number of frames received at the corresponding GbE port that have
been discarded for various reasons (including filtering)
Tx Correct Octets
The total number of frames transmitted by the corresponding GbE port that have
Rx Correct Unicast pkts
Total number of good unicast frames received through the corresponding GbE
port
Tx Correct Unicast pkts
Total number of good unicast frames transmitted by the corresponding GbE port
Rx Discard pkts
The total number of frames received at the corresponding GbE port that have
Tx Discard pkts
The total number of frames transmitted by the corresponding GbE port that have
Rx Iface Errors
Total number of frames with errors received through the corresponding GbE port
Tx Iface Errors
Total number of frames with errors transmitted through the corresponding GbE
port
Rx Unknown Protocol
Total number of frames carrying unidentified protocols received through the

corresponding GbE port
Rx Multicast ok
Total number of good multicast frames received through the corresponding GbE
port
Tx Multicast ok
Total number of good multicast frames transmitted by the corresponding GbE

port
Rx Broadcast ok
Total number of good broadcast frames received through the corresponding GbE
port
Tx Broadcast ok
Total number of good broadcast frames transmitted by the corresponding GbE

port
Gmux-2000 Ver. 3.2
7-15
Pseudowire Gateway
Monitoring>Status>Physical layer>GbE port> GbE port frame type counters
1. GbE port[1 2]
Alignment errors
Fcs errors
Frame too long
...
...
...
...
(1)
(0)
(0)
(0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-20. Typical GbE Port Frame Type Counters Screen

Table 7-4. GbE Port Frame Type Counters Parameters
Parameter
Description
Alignment Errors
Total number of frames with alignment errors detected by the corresponding GbE port
FCS Errors
Total number of frames with checksum errors detected by the corresponding GbE port
Frame Too Long
Total number of frames with length exceeding the maximum detected by the
corresponding GbE port
Pseudowire Gateway
Monitoring>Status>Physical layer>GbE port>GbE port pause counters
1. GbE port[1 2]
Rx pause frames
Tx pause frames
... (1)
... (0)
... (0)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-21. Typical GbE Port Pause Counters Screen
7-16
Gmux-2000 Ver. 3.2
Table 7-5. GbE Port Pause Counters Parameters

Parameter
Description
Rx Pause Frames
Total number of Pause frames received by the corresponding GbE port
Tx Pause Frames
Total number of Pause frames transmitted by the corresponding GbE port
Displaying Connection Status Parameters

Use the following procedure to display connection (bundle) status information.
You can display information only on active bundles.
To navigate to the required screen, use Monitoring>Status>Connection.
To display connection (bundle) counters:

1. Select Connection on Monitoring>Status.
A typical Connection Status task selection screen is shown in Figure 7-22.
Pseudowire Gateway
Monitoring>Status>Connection
1. Bundle counters
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-22. Typical Status Bundle Task Selection Screen

2. Select the Bundle Counters task.
3. Select Bundle ID and then enter the number of the desired bundle. Make sure
to select a bundle that actively carries traffic.
A typical Bundle Counters screen for TDMoIP (CE) bundles is shown in
Figure 7-23. The statistics displayed on the Bundle Counters screen are
explained in Table 7-6.
4. To display parameters for another bundle, repeat Step 3 above.
Gmux-2000 Ver. 3.2
7-17
Pseudowire Gateway
Connectivity Status
Sequence Errors
Frames Tx to PSN
Frames Rx from PSN
...
...
...
...
...
...
...
...
...
...
(7)
(172.17.175.51)
(OK)
(0)
(0)
(0)
(0)
(5)
(5207933)
(5209233)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-23. Typical Bundle Counters Screen for TDMoIP (CE) Bundles
Table 7-6. Bundle Counters Parameters for TDMoIP (CE) Bundles
Parameter
Description
Bundle ID
Index number of selected bundle
Bundle destination IP address
Connectivity Status
The results indicated by the OAM connectivity protocol
Sequence Errors
Total number of packet sequence errors
Jitter Buffer Underflows
Total number jitter buffer underflow events
Jitter Buffer Overflows
Total number jitter buffer overflow events
Min Jitter Buffer Level
Actual minimum size of the jitter buffer recorded for this bundle, in msec
Max Jitter Buffer Level
Actual maximum size of the jitter buffer recorded for this bundle, in msec
Frames Tx to PSN
Total number of frames transmitted toward the PSN
Frames Rx from PSN
Total number of frames received from the PSN
Displaying Connection Performance Monitoring Data for TDMoIP (CV)

Bundles
Use the following procedure to display performance monitoring data on the
traffic carried by TDMoIP (CV) connections (bundles). In addition, you can also
display the state of each bundle and identify its exit port.
This section presents general information applying to compressed voice
connections. For additional module-specific information, refer to the
corresponding module Installation and Operation Manual.
7-18
Gmux-2000 Ver. 3.2
To navigate to the required screen, use Monitoring>Status>Connection.
To display connection (bundle) performance monitoring data:

1. Select the Status monitoring task.
2. Select the Connection option.
3. Select the Bundle Counters option.
4. Select the desired Bundle ID by specifying its number, in the range of 1 to
2000. You can select only existing TDMoIP (CV) bundles.
5. After selecting a specific bundle, the bundle data are immediately displayed.
A typical Connection Status screen is shown in Figure 7-24.
The display includes the following information:
Bundle number and its type (TDMoIP (CV))
Bundle state:
Note
Connected the bundle is connected and can carry traffic

Disconnected the bundle is administratively disconnected (it is
configured with Connect = NO)
IP OOS the bundle cannot carry traffic, because the IP link to its
destination is out-of-service. To correct the problem, first check that
the exit port and the IP communication parameters are correctly
configured (that is, correct destination IP address, and correct next
hop IP address). If IP configuration is correct, the problem may be in
the network: you may use the ping function to check.
Echo Wait the IP link is up, but the bundle cannot carry traffic
because Layer 4 (UDP) is down. In this case, first check the source
and destination CBID parameters.
Coder Wait the IP link is up, but the bundle cannot carry traffic
because the coders have not yet synchronized. In this case, first
check the source and destination coder types and rates.
The bundle exit port, for example, the identification of the TDM link (A, B,
C, D) or the GbE module and port
Bundle counters section, which displays the bundle performance

monitoring parameters.
You can reset the bundle counters by a C (clear) command.

Table 7-7 presents the TDMoIP (CV) bundle performance monitoring parameters.
Note
Rx identifies the receive direction (from the network to the Gmux-2000)

Tx identifies the transmit direction (from the local Gmux-2000 to the
network)
Unless a specific time interval is listed, the displayed values represent the total
accumulated since the bundle has last been connected, or since the last
counters clear command (whichever occurred last).
Gmux-2000 Ver. 3.2
7-19
Pseudowire Gateway
...le counters (BUNDLE 1 TDMoIP(CV) STATE: ECHO WAIT EXIT PORT: GIG A)
Rx Total Frames
Tx Total Frames
Rx 60 Sec Frames
Tx 60 Sec Frames
Rx Total Bytes
Tx Total Bytes
Rx 60 Sec Bytes
Tx 60 Sec Bytes
Tx on Timeout
Tx 60 Sec Timeout
Tx Max Size
Tx 60 Sec Max Size
Rx Total Sg
Tx Total Sg
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
(1)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0
Rx Total Voice
Tx Total Voice
Rx 60 Sec Voice
Tx 60 Sec Voice
Rx Total HDLC
Tx Total HDLC
Rx 60 Sec HDLC
Tx 60 Sec HDLC
Rx Silence Rate
Tx Silence Rate
Freed Seq Num
Miss Seq Num
Longest Miss Seq
...
...
...
...
...
...
...
...
...
...
...
...
...
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0
>
F next; B prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-24. Typical Bundle Counters Screen for TDMoIP (CV) Bundles
Table 7-7. TDMoIP (CV) Bundle Performance Monitoring Parameters
Parameter
Description
Rx Total Frames
Total number of packets received
Tx Total Frames
Total number of data packets transmitted
Rx 60 sec Frames
Number of packets received during the last 60 seconds
Tx 60 sec Frames
Number of packets transmitted during the last 60 seconds
Rx Total Bytes
Total number of received data octets
Tx Total Bytes
Total number of transmitted data octets
Rx 60 sec Bytes
Number of data octets received during the last 60 seconds
Tx 60 sec Bytes
Number of data octets transmitted during the last 60 seconds
Tx on Timeout
Total number of packets transmitted before reaching the maximum configured

size, as a result of reaching the maximum configured packetizing interval
Tx 60 sec Timeout
Number of packets transmitted before reaching the configured size, as a result of

reaching the maximum configured packetizing interval during the last 60 seconds
Tx Max Size
Total number of packets transmitted as a result of reaching the maximum

configured size
Tx 60 sec Max Size
Number of packets transmitted as a result of reaching the maximum frame

configured size during the last 60 seconds
7-20
Gmux-2000 Ver. 3.2
Parameter
Description
Rx Total Sg
Total number of received signaling packets
Tx Total Sg
Total number of transmitted signaling packets
Rx Total Voice
Total number of received voice packets
Tx Total Voice
Total number of transmitted voice packets
Rx 60 sec Voice
Number of voice packets received during last 60 seconds
Tx 60 sec Voice
Number of voice packets transmitted during last 60 seconds
Rx Total Hdlc
Total number of received data packets
Tx Total Hdlc
Total number of transmitted HDLC packets
Rx 60 sec Hdlc
Number of HDLC packets received during last 60 seconds
Tx 60 sec Hdlc
Number of HDLC packets transmitted during last 60 seconds
Rx Silence Rate
Average percentage of silence measured for the receive direction on all the
timeslots connected to the bundle
Tx Silence Rate
Average percentage of silence measured for the transmit direction on all the
timeslots connected to the bundle
Freed Seq Num
Total number of duplicate packets that were received and dropped (the duplication
occurs within the network)
Miss Seq Num
Total number of packets that did not arrive in time, as expected according to their
sequence number (either because they were lost in the network, or reordered)
Longest Miss Seq
The largest interval of consecutively numbered missed packets
7.2
Troubleshooting
Preliminary Checks
In case a problem occurs, perform the following preliminary checks:
Gmux-2000 Ver. 3.2
If the problem is detected the first time the Gmux-2000 is put into operation,
first perform the following checks:
Check for proper chassis and module installation, and correct cable
connections, in accordance with the system installation plan.
Check the system and module configuration parameters in accordance

with the specific application requirements, as provided by the system
administrator.
If the Gmux-2000 nodal clock is to be locked to the clock recovered from

one of the ports of a module installed in the chassis, make sure a suitable
fallback clock source is configured and provides a good clock signal.
If the FLT indicator of a module lights, replace the corresponding module.
Troubleshooting
7-21
When more than one module of the same type is installed, check the ACT
indicators: the ACT indicator of each active module must light. If not lit, first
check the configuration.
Check the displayed alarm messages and refer to Section 7.4 for their
interpretation and associated corrective actions.
Troubleshooting Hardware Problems

If the problem cannot be corrected by performing the actions listed above, refer
to Table 7-8. Identify the best-fitting trouble symptoms and perform the actions
listed under Corrective Measures in the order given, until the problem is
corrected.
Table 7-8. Hardware Troubleshooting Chart

No.
1
Trouble Symptoms
Probable Cause
Corrective Measures
Gmux-2000 does not turn

on
1. No power
Check that power is available at the power

outlets or power distribution panel serving the
Gmux-2000.
Check that both ends of all the Gmux-2000
power cables are properly connected.
2. Blown fuse
For an AC-powered Gmux-2000:
1. Check and if necessary replace the fuses

located on the PI/AC module.
2. If a fuse blows again, replace the

corresponding PS module.
3. If any fuse blows again, replace

Gmux-2000.
For a DC-powered Gmux-2000:
1. Check and if necessary replace the fuse(s)

located on the PI/DC module.
2. If a fuse blows again, try to identify the PS

module that may be causing the problem,
by sequentially removing each PS module
and checking whether the fuse stops
blowing.
3. If the fuse keeps blowing, replace the

Gmux-2000 if any fuse blows again
7-22
Troubleshooting
3. Defective PS module
Replace the suspected PS module
4. Defective Gmux-2000
Replace Gmux-2000
Gmux-2000 Ver. 3.2

No.
2
Trouble Symptoms
Probable Cause
Corrective Measures
The local Gmux-2000

cannot be configured
through its CONTROL DCE
port
1. Connection made to
the inactive CONTROL
module
Check that the connection is made to the

CONTROL DCE connector of the CONTROL
module whose ACT indicator lights
2. Configuration problem Restore the default parameters using the

switches located on the CONTROL modules as
explained in Chapter 3, and then perform the
preliminary supervision terminal configuration
instructions given in Chapter 4
3. External problem
Check the equipment serving as a supervision

terminal and the connecting cable.
If data equipment provides the link between
the supervision terminal and the Gmux-2000,
check its proper operation
The local Gmux-2000

cannot be managed
through its CONTROL ETH
port
Gmux-2000 Ver. 3.2
4. Software not yet

loaded into CONTROL
module, or corrupted
Download the appropriate Gmux-2000

software to the CONTROL modules in
accordance with Appendix B
5. Defective CONTROL
module
Replace the corresponding CONTROL module
1. Configuration
problems
Check the CONTROL ETH port configuration.
2. Problem in the
connection between
the CONTROL ETH port
and the LAN
Check that the LINK indicator of the CONTROL

ETH port lights.
3. External problem
Check the external equipment (for example,

the default gateway and other routers) that
process the traffic coming from the local
Gmux-2000 CONTROL ETH port
4. Defective CONTROL
module
Replace Gmux-2000
Check that the ACT indicator of the CONTROL

module lights
If not, check for proper connection of the cable

between the LAN and the CONTROL ETH port.
Also check that at least one node is active on
the LAN, and that the hub or Ethernet switch
to which the Gmux-2000 CONTROL ETH port is
connected is powered
Troubleshooting
7-23

No.
4
Trouble Symptoms
Probable Cause
The LOSS LOC indicator of 1. Cable connection

an STM1 module port of
problems
the local Gmux-2000 lights

Corrective Measures
Check for proper connections of the cables to
the LINK TX and RX connectors of each STM1
module port.
Repeat check at the users equipment
connected to the port.
2. Other problem
The LOSS REM indicator of 1. Defective STM1

an STM1 module port of
module
the local Gmux-2000 lights
2. External problem
The status indicator of a

local E1-PW-SRV/21 port
lights in red
1. Loss of incoming port

signal
Activate the local loopback at the local STM1

module port.
If the local users equipment connected to

the STM1 module port does not receive its
own signal, check its operation and replace
if necessary
If the problem is not in the equipment

connected to the STM1 module port,
replace the STM1 module

module port. If the local users equipment
connected to the STM1 module port starts
receiving its own signal, replace the STM1
module
module port.

the STM1 module port does not receive its
own signal, check its operation and replace
if necessary

connected to the STM1 module port,
replace the STM1 module
If there are any fault indications on the STM1

module served by this port, first solve the
STM1 problem
2. Defective
Activate the remote loopback on the STM1
E1-PW-SRV/21 module module port connected to the corresponding
E1-PW-SRV/21 port. If the E1-PW-SRV/21 port
status indicator turns off, check its operation
and replace if necessary
7-24

local E1-PW-SRV/21 port
lights in yellow
Troubleshooting
3. Defective STM1
module
Replace the STM1 module
Replace Gmux-2000
External problem
The remote equipment sends AIS.

If problem persists, request troubleshooting of
the remote equipment
Gmux-2000 Ver. 3.2

No.
Trouble Symptoms
Probable Cause
Corrective Measures

local E1-PW/28 port lights
in yellow
External problem
The remote equipment sends AIS. If problem

persists, request troubleshooting of the
remote equipment

1. Cable connection
local E1-PW/28 port lights
problem
in red (loss of incoming E1
signal)
Check that the adapter cable connected to the

module matches the configured E1 interface
type, and then check for proper connection of
the users equipment to the adapter cable
connectors.
Also check for proper connections at the users
equipment connected to the port
2. Other problem
10
The Gmux-2000 cannot

connect to the network
1. Uplink configuration
problems
Activate the local loopback at the local E1 port:

the E1 port does not receive its own signal,
check its operation and replace if necessary

connected to the E1 port, replace the
E1-PW/28 module
Check the uplink port configuration, and the

other parameters that affect routing.
Also check the external equipment (for
example, routers) that processes the traffic
coming from the local Gmux-2000 GbE port
2. Problem in uplink
connections
Check that the LINK indicator of the

corresponding GbE port lights, and that its TX
and RX indicators flash from time to time.
If not, check for proper connection of the
fibers to the GbE port, and to the remote
equipment. Also check that the equipment to
which the GbE port connects is powered and
active
3. Congestion problem
If the PAUSE indicator lights continuously,

check the remote equipment configuration
4. Defective GbE module
Replace the GbE module
Replace Gmux-2000
Handling Service Problems

The main tool used to analyze unsatisfactory service, or service degradation, is to
use the performance statistics and status data collection tools provided by the
Gmux-2000.
Section 7.1 presents a detailed description of the Gmux-2000 performance

monitoring functions, explains the various parameters, and provides guidelines
for interpreting the displayed data.
Gmux-2000 Ver. 3.2
Troubleshooting
7-25
By analyzing the performance statistics and status data, it is possible to identify

the unsatisfactory performance area, and take steps to change the system
configuration and enhance resources such a network bandwidth, etc., as required
to improve the service quality. It is also recommended to check Section 7.6 for
answers to frequently asked questions.
Contact RAD Technical Support Department if you need additional help with your
particular application.
7.3
Detecting Configuration (Sanity) Errors
Gmux-2000 includes an extensive subsystem that continuously checks the validity

of the users configuration activities, and reports any conflicts and errors.
Two types of sanity error messages are reported:
Warning
Minor error that does not prevent using the Gmux-2000.

For example, you will get a warning when a programmed
module is not physically installed in the chassis.
Error
Error that prevents proper operation of the Gmux-2000 in

its intended application. For example, you will get an error
as a result of invalid timeslot assignment.
It is not possible to update the online database when
sanity errors are present.
Displaying Sanity Errors

Sanity errors are generated as a result of a sanity check. A sanity check is
performed in the following cases:
Automatically, whenever you attempt to update the online database, either

by means of the % command, or by selecting Update Database on
Configuration>Database Tools.
In response to a manual check command, by selecting Check Sanity on

Configuration>Database Tools.
In both cases, when problems are detected, you will a Sanity Warnings or Sanity
Errors prompt (in accordance with the error with the highest severity), which
disappears after pressing <Enter>, and the shortcut V View Sanity Log appears
in the prompt line. Figure 7-25 shows a typical Sanity Log screen.
7-26
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>Database tools>
WARNING(013):
WARNING(013):
| WARNING(013):
v WARNING(013):
WARNING(013):
WARNING(013):
MISMATCH
MISMATCH
MISMATCH
MISMATCH
MISMATCH
MISMATCH
BETWEEN
BETWEEN
BETWEEN
BETWEEN
BETWEEN
BETWEEN
HARDWARE
HARDWARE
HARDWARE
HARDWARE
HARDWARE
HARDWARE
AND
AND
AND
AND
AND
AND
DATABASE
DATABASE
DATABASE
DATABASE
DATABASE
DATABASE
IO-2
IO-3
IO-4
IO-5
IO-6
IO-7
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-25. Typical Sanity Log Screen

Each entry starts with the severity level, followed by an error code which
identifies the problem. The code is followed by a short description of the
detected problem, and the affected entity, for example, the number of the I/O
slot or bundle on which the problem has been detected.
Interpreting the Sanity Errors

Table 7-9 lists the error messages generated by Gmux-2000, and explains their
interpretation.
The messages are listed in ascending order of their codes.
Table 7-9. Error Messages

Code
Syntax
Meaning
000
INVALID MASTER CLOCK SOURCE
The selected master clock source is invalid, for example: the

selected port is unconnected, the port is located on a module not
installed or not configured, or it is an unmapped module port
001
MASTER AND FALLBACK CLOCKS

ARE THE SAME
It is not allowed to select the same reference source for both the
master and fallback clocks
002
INVALID FALLBACK CLOCK SOURCE The selected fallback clock source is invalid, for example: the
selected port is unconnected, the port is located on a module not
installed or not configured, or it is an unmapped module port
003
DEFAULT GATEWAY AND IP ARE

EQUAL
The default gateway address is the same as the Gmux-2000

agent IP address. This is not allowed
004
DEFAULT GATEWAY & IP NOT IN

SAME SUBNET
The default gateway and the Gmux-2000 agent IP addresses must

be in the same subnet. Alternatively, specify 0.0.0.0 (the default
gateway)
005
ILLEGAL AGENT IP ADDRESS
The IP address specified for the Gmux-2000 agent is an invalid IP

address (for example, its first byte is 000 or 224, or the last byte
is 000 or 255)
Gmux-2000 Ver. 3.2
7-27
Code
Syntax
Meaning
006
ILLEGAL AGENT DEFAULT

GATEWAY
The default gateway IP address specified for the Gmux-2000

agent is an invalid IP address. This occurs if the address is not
0.0.0.0 and its first byte is 000 or 224, or the last byte is 000 or
255
007
MANAGER IP AND NEXT HOP ARE

THE SAME
While configuring the Manager List, you specified the same IP

address already assigned to the manager as the next hop IP
address. Make sure to select a different IP address, but within the
same subnet
008
ILLEGAL MANAGER IP ADDRESS
The IP address specified for a management station on the

Manager List is an invalid IP address (for example, its first byte is
000 or 224, or the last byte is 000 or 255)
009
ILLEGAL MANAGER NEXT HOP
The next hop IP address specified for a management station on

the Manager List is an invalid IP address (for example, its first
byte is 000 or 224, or the last byte is 000 or 255)
010
MANAGER NEXT HOP IS NOT

REACHABLE
The next hop IP address for the specified management station is

not within the subnet of the Gmux-2000 agent, nor within the
subnet of one of the GbE interfaces
011
MANAGER IP ADDRESS IS NOT

UNIQUE
The IP address specified for a management station on the

Manager List is already used in the network
012
ILLEGAL ALARM REPORT LEVEL
The reporting level selected for this alarm severity is illegal
013
MISMATCH BETWEEN HARDWARE

AND DATABASE
The module physically installed in the specified I/O slot does not
match the module type configured in the database
014
SERVER CARD MAPPED TO

ILLEGAL GBETH IF
The specified pseudowire emulation server or voice compression

module is incorrectly mapped. For example, it is mapped to an
invalid or non-existing GbE port, or is not yet mapped (that is, the
default mapping, 0/0, has not been changed)
015
TIME SLOT MAPPED TO ILLEGAL

BUNDLE
The specified timeslot has been mapped to a bundle that has not
yet been defined.
The user mapped TS to bundle, which does not exist.
016
PORT NC WHILE 1 OF IT'S

BUNDLES ACTIVE
It is not allowed to change the status of the specified port to Not

Connected while one or more of the bundles configured on the
port are in the Connect state and are active
017
STM TU ASSIGNED TO ILLEGAL

CARD
The specified TU of the STM1 module installed in I/O slot SS is

incorrectly mapped (it is connected to a pseudowire emulation
server port located on an empty I/O slot, or the I/O slot is not
equipped and configured with a pseudowire emulation server
module)
018
MORE THAN ONE TU MAPPED TO

SAME DEST
Two TUs of the STM1 module installed in I/O slot SS are mapped
to the same pseudowire emulation server module port
019
PORT IS NOT MAPPED TO STM TU
To carry a bundle, the specified pseudowire emulation server

module port must be mapped to a TU on an STM1 module
7-28
Gmux-2000 Ver. 3.2
Code
Syntax
Meaning
020
STM CARD MAPPED TO T1 SERVER The specified TU of the STM1 module installed in I/O slot SS is
mapped to a T1 pseudowire emulation server port. This is not
allowed (the TU can only be mapped to an E1 pseudowire
emulation server port)
021
SONET CARD MAPPED TO E1

SERVER
The specified TU of the OC3 module installed in I/O slot SS is

mapped to an E1 pseudowire emulation server port. This is not
allowed (the TU can only be mapped to a T1 pseudowire
emulation server port)
022
ILLEGAL IP ADDRESS FOR GB

PORT
The IP address defined for the specified GbE port is invalid (for
example, its first byte is 000 or 224, or the last byte is 000 or
255).
A GbE port must always be assigned an IP address and that IP
address must be valid
023
GB PORT IP IS SAME AS AGENT IP

ADDRESS
The same IP address is assigned both to the specified GbE port

and to the Gmux-2000 agent (that is, the specified GbE port has
the same IP address as that of the CONTROL module)
024
ILLEGAL GATEWAY FOR GB PORT
The IP address defined for the default gateway is invalid (for

example, its first byte is 000 or 224, or the last byte is 000 or
255).
However, the default address (0.0.0.0) is also allowed
025
GB PORT IP AND DEFAULT

GATEWAY EQUAL
The same IP address is assigned both to the specified GbE port

and to its default gateway
026
GB IP AND GATEWAY NOT IN

SAME SUBNET
The default gateway IP address and the IP address assigned to

the specified GbE port must be in the same subnet
027
AGENT DEFAULT GATEWAY AND

GB IP EQUAL
The default gateway of the Gmux-2000 agent and the specified

GbE port have been assigned the same IP address. This is not
allowed
028
AGENT IP AND GB DEFAULT

GATEWAY EQUAL
The default gateway of the specified GbE port and the

Gmux-2000 agent have been assigned the same IP address. This
is not allowed
029
TWO GBs HAVE THE SAME IP

ADDRESS
The GbE ports (as specified in the alarms) have been assigned the
same IP address. This is not allowed
030
CANT CHANGE PARAMETER ON

ACTIVE BUNDLE
Some parameters cannot be changed while a bundle is

connected. The following operations cannot be performed while a
bundle is connected:
Changing the IP address of the GbE port
Changing the module type
Changing the framing (for TDM ports)
Changing the timeslot assignment.
Changing the source and destination of the bundle
Changing the TDM port supporting the bundle.
Before performing any of the operations listed above, disconnect

the bundle
Gmux-2000 Ver. 3.2
7-29
Code
Syntax
Meaning
031
FRAME TYPE CONFLICTS TS

ASSIGNMENT
This message, which is generated only after the specified bundle

is switched to the Connect state, indicates one of the following
timeslot assignment errors:
For a bundle mapped to an unframed port, all the port

timeslots must be chosen
For a port using G.704 multiframe, timeslot 16 cannot be

mapped to a bundle
032
ILLEGAL EXIT PORT

is switched to the Connect state, indicates that the bundle is
mapped to an illegal or non-existing TDM port
033
ILLEGAL TDM PORT

is switched to the Connect state, indicates that the bundle is
mapped to an illegal or non-existing TDM port
034
SOURCE CBID IS NOT UNIQUE

is switched to the Connect state, indicates that more than one
bundle mapped to a given destination IP address has the same
source CBID UDP value.
The source UDP value is defined as follows:
If the payload format is proprietary:

Source UDP = Source CBID+1
Otherwise Source UDP = Source CBID
This check is made for all types of bundles (IP and MPLS)
035
GB PORT CANNOT REACH IP OF

BUNDLE

is switched to the Connect state, indicates that the IP address of
the bundle cannot be reached by the specified GbE port because
the bundle IP address does not comply with at least one of the
following requirements:
In the same subnet with the IP address of its GbE port
The next hop IP address in the same subnet with the GbE port
In the same subnet with one of the static routes

036
BUNDLE IP IS SAME AS IT'S GB

PORT IP

is switched to the Connect state, indicates that the bundle has
the same IP address as its GbE port
037
ILLEGAL IP ADDRESS

is switched to the Connect state, indicates that the IP address
defined for the bundle is invalid (for example, its first byte is 000
or 224, or the last byte is 000 or 255), or that it has the default
value (0.0.0.0).
This is not allowed a bundle must have a valid IP address
7-30
Gmux-2000 Ver. 3.2
Code
Syntax
Meaning
038
BUNDLE GBETH PORT MISMATCH

SERVER IF
The GbE port defined for a bundle must be the same as the GbE
port serving the pseudowire emulation server module supporting
the corresponding bundle.
This message is generated only after the specified bundle is
switched to the Connect state
039
ILLEGAL INTERFACE FOR STATIC

ROUTE
This message, which is generated only after the specified static

route is switched to the Connect state, indicates that this static
route is defined on an incorrect interface number, for example, to
an interface on a non-existing or not configured GbE module
040
ILLEGAL IP ADDRESS FOR STATIC

ROUTE

route is switched to the Connect state, indicates that its defined
IP address is invalid (for example, its first byte is 000 or 224, or
the last byte is 000 or 255), or that it has the default value
(0.0.0.0). This is not allowed a static route must have a valid IP
address
041
ILLEGAL NEXT HOP FOR STATIC

ROUTE

route is switched to the Connect state, indicates that its next hop
IP address is invalid (for example, its first byte is 000 or 224, or
the last byte is 000 or 255), or that it has the default value
(0.0.0.0). This is not allowed a static route must have a valid
next hop IP address
042
IP AND NEXT HOP SAME FOR

STATIC ROUTE

and IP addresses are the same. This is not allowed the
addresses must be different
043
STATIC ROUTE IP SAME AS GBETH

IP

route is switched to the Connect state, indicates that its IP
address is equal to the IP address of the assigned GbE port.
This is not allowed the addresses must be different
044
ILLEGAL STATIC ROUTE SUBNET

MASK

route is switched to the Connect state, indicates that its subnet
mask is not 255.255.255.255.
045
STATIC ROUTE NEXT HOP IS NOT

REACHABLE

IP address is unreachable, because it is neither within the subnet
of the CONTROL module nor within the subnet of one of the
Gmux-2000 GbE interfaces.
046
STATIC ROUTE IP IS NOT UNIQUE

route is switched to the Connect state, indicates that its IP
address is already assigned to another static route. This is not
allowed only one static route may be defined for any specific IP
address
047
GBETH PORTS CAN'T BE ON SAME The IP addresses assigned to the two ports of a GbE module
SUBNET
cannot be in same subnet
Gmux-2000 Ver. 3.2
7-31
Code
Syntax
Meaning
048
SAME SOURCE CBID FOR MPLS

MODE BUNDLES
This message, which is generated only after the specified bundles

are switched to the Connect state, indicates that the source CBID
value is assigned to more than one bundle using MPLS
049
SAME DEST CBID FOR MPLS MODE This message, which is generated only after the specified bundles
BUNDLES
are switched to the Connect state, indicates that the destination
CBID value is assigned to more than one bundle using MPLS
050
BUNDLE ALREADY MAPPED TO

ANOTHER PORT SS:PP:TS
The bundle being configured is already mapped to the port

specified in the message.
The user mapped a bundle to two different E1/T1 ports
051
MORE THAN 16 BUNDLES FOR

PORT
You are trying to connect too many bundles to the specified port
(the maximum is 16).
052
CAN'T CHANGE PARAM AFTER

BUNDLE CREATED
Some of the parameters of a bundle can be configured only when

the bundle is created. The bundle parameters that can be
configured only upon creation are as follows:
Encapsulation
TX circuit bundle type
Payload type
PSN type
To change any of these parameters, first delete the bundle and

then recreate the bundle with the new parameters
053
ILLEGAL NEXT HOP FOR BUNDLE

is switched to the Connect state, indicates that its next hop IP
address is invalid (for example, its first byte is 000 or 224, or the
last byte is 000 or 255).
Alternatively, if the bundle destination IP address is within the
subnet of the GbE port, the next hop IP address must have the
default value (0.0.0.0).
054
ILLEGAL MPLS PAYLOAD FORMAT

FOR BUNDLE

is switched to the Connect state, indicates that its payload
format is invalid.
For MPLS bundles, the payload format must be Standard no RTP
055
ILLEGAL MPLS IP TOS FOR BUNDLE This message, which is generated only after the specified bundle
is switched to the Connect state, indicates that its ToS value is
invalid.
For MPLS bundles, the ToS is determined by the EXP bits, and
must be within the range of 0 to 7
056
ILLEGAL OAM FORMAT FOR

BUNDLE

is switched to the Connect state, indicates that its OAM format is
invalid.
For MPLS bundles, the OAM format must be same as the payload
format
7-32
Gmux-2000 Ver. 3.2
Code
Syntax
Meaning
057
ILLEGAL ADAPTIVE CLOCK MODE

FOR BUNDLE

switched to the Connect state.
When you select ADAPTIVE CLOCK = ENABLED for a bundle, the
timing of the corresponding TDM port must be ADAPTIVE
058
MORE THAN 1 ADAPTIVE BUNDLE

FOR PORT

is switched to the Connect state, indicates that the adaptive
timing mode has already been configured for another bundle
using the same TDM port.
This is not allowed only one bundle of any TDM port may have
its timing mode configured to Adaptive
059
CARD TYPE CHANGED FOR

MASTER CLOCK SRC
The type of module installed in the slot currently configured as

master clock source card type has been changed. Make sure to
reconfigure the master clock source
060
CARD TYPE CHANGED FOR FBACK

CLOCK SRC
The module type of module installed in the slot currently

configured as fallback clock source card type has been changed.
Make sure to reconfigure the fallback clock source
061
ILLEGAL TU MAPPING FOR

OPERATION MODE
The current Gmux-2000 version supports only the terminal mode,

and therefore the only allowed selections for TU routing
(performed by means of the Telecom Assignment screen) for
both ADD and DROP are NC, A or B.
062
ILLEGAL FAR END TYPE

CONFIGURATION
The bundle far end configuration is incompatible with the TDM

port line type and payload format configured for the local bundle
end. This message is generated only after the specified bundle is
063
SAME DEST IP SHOULD HAVE

SAME VLAN ID
When two bundles have the same destination IP address, it is

necessary to configure them with different VLAN numbers.
064
SAME TU ON OTHER MATRIX

SHOULD BE BP
A TU that is bypassed between two VC-3 or VC-4 ports must

remain in the same position in the frame structure (the TU
number remains unchanged)
065
ALL EXT PORTS VC3 MUST HAVE

SAME CONFIG
All the VC-3 ports of a given external SDH port must have the
same configuration (except for the J2 path trace string)
066
LVC'S MUST HAVE SAME SIG

LBL&PATH TRACE
All the low-order (VC-12 or VT-1.5) ports must have the same
signal label and path trace strings.
067
CL AND GIG PORT CANT BE IN

SAME SUBNET
The IP addresses assigned to the GbE uplink ports cannot be in

the subnet of the Gmux-2000 management IP addresses
068
DISCONNECT BUNDLES LINE

TYPE CHANGE
While a bundle is connected to a port, it is not allowed to change

its timeslot assignment, nor change the TDM port line type to or
from UNFRAMED. To make such changes, first disconnect the
bundle from the I/O slot.
Gmux-2000 Ver. 3.2
7-33
Code
Syntax
Meaning
069
MANAGERS NEXT HOP IS SAME

AS HOST IP
You have configured the IP address already assigned to the

Gmux-2000 management (Host IP) as the next hop IP address for
a manager. This is not allowed
070
MANAGERS IP IS AS SAME AS
CL IP

Gmux-2000 management (Host IP) as the IP address of a
manager. This is not allowed
071
NC VC PORT CANT BE MAPPED TO Before trying to map VC ports on an STM-1, make sure that all
SDH MATRIX
the ports are in the Connect state
072
DEST CBID NOT UNIQUE FOR

SAME DEST IP
You have assigned the same destination CBID to two bundles

mapped to same destination IP address. This is not allowed. This
message is generated only after the specified bundle is switched
to the Connect state
073
MPLS LABEL SHOULD BE UNIQUE
You have assigned the same MPLS label to two different bundles.
This is not allowed
074
MPLS LABEL SHOULD BE BIGGER

THAN 15
The MPLS label must be 16 or higher
075
BUNDLE'S IP IS AS SAME AS CL IP
ADDRESS

Gmux-2000 management agent as the destination IP address for
a bundle. This is not allowed
076
DEST TS SHOULD BE UNIQUE FOR The bundle timeslots selected during the port timeslot
PORT
assignment have already been assigned for other purpose. This
message is generated only after the specified bundle is switched
to the Connect state
077
MORE THAN 190 DATA TS FOR

CARD
The total number of HDLC and SS7 timeslots assigned to bundles

on the specified module must not exceed 190. This message is
generated only after the specified bundle is switched to the
Connect state
078
DEST TS FIELD CANNOT BE ZERO
You must configure a destination timeslot for each timeslot

assignment. This message is generated only after the specified
bundle is switched to the Connect state
079
ALL PORTS MUST BE SAME - LBT

OR SYSTEM
All the Connected voice ports on the specified VC-E1/16 or

VC-E1/12 module must use the same clock source: either LBT or
SYSTEM-A
080
ASSIGN RX CLK SRC PORT TO

SYSTEM A
When one of the data ports of the specified VC-E1/16 or

VC-E1/12 module is selected as reference for the Gmux-2000
system (nodal) timing (this may occur when using the Rx Clock
mode), then all the other ports (either voice or data), must be
configured to the SYSTEM A mode
081
CAN'T HAVE TX CLK SRC LIKE

VOICE PORTS
It is not allowed to use an E1 voice port of a VC-E1/16 or

VC-E1/12 module as TX clock source
082
ALL PORTS MUST BE OF SAME

SYSTEM
All the destination ports must be on the same system
7-34
Gmux-2000 Ver. 3.2
Code
Syntax
Meaning
083
STATIC ROUTE IP SAME AS

BUNDLE IP
The IP address configured as next hop address must be

differently from the bundle destination IP address.
084
SECONDARY GB PORT IN BUNDLE
When using redundancy on GbE ports, it is not allowed to specify

a secondary port as the exit port of a bundle
085
SECONDARY GE INTERFACE IN
STATIC ROUTE

a secondary port in a static route definition
086
INTERFACE ALREADY EXIST IN APS You are trying to add an interface already selected for the APS
group being configured
087
APS NUMBER OF CHANNELS

SHOULD BE 2
Make sure to configure exactly two ports as channels in an APS

group
088
SAME PORT IN 2 APSs
You are trying to add an interface already selected for another

APS group to the APS group being configured
089
WRONG CHANNEL CARD TYPE

FOR APS CFG MODE
You are trying to add a channel from a module that does not
support APS
090
CHANNELS MUST BE IN THE SAME The additional channel in the APS group being configured must be
CARD
taken from the same module as the first channel
091
IP ADDRESS DEFINED ON
SECONDARY GB PORT
092
TU MAPPING ON SECONDARY STM No mappings are allowed on an STM-1 port configured as

PORT
secondary port of an APS group
093
2 APSs NEEDED FOR CARD

REDUNDANCY
094
CARD REDUND PRIMARY SLOT

ISN'T EQUAL
095
CARD REDUND SECONDARY SLOT

ISN'T EQUAL
096
PORT ISN'T EQUAL IN CARD

REDUNDANCY APS
097
TU MAPPING ON APS STM

INTERFACE
You are trying to map TUs on an STM-1 port configured as part of

an APS group. This is not allowed perform the mapping on the
port intended as primary before configuring the APS group
098
APS INTERFACE NOT IN CONNECT

STATE
Make sure the ports used as channels of an APS group are both
configured as Connected
099
STM PORTS CAN'T BE CONNECTED You cannot bypass between two STM-1 ports (the installed
TOGETHER
Gmux-2000 version can only operate as a TM (terminal
multiplexer) only
100
TOO MANY BUNDLES FOR CARD
The maximum number of bundles that can be configured on a

VC-E1/16 or VC-E1/12 module is 32
101
IP ADDRESS NOT DEFINED FOR

VMX CARD
Make sure to configure the required IP address for the VC-E1/16

or VC-E1/12 module
Gmux-2000 Ver. 3.2

an IP address defined on a secondary port
When two STM1 modules are installed, it is necessary to

configure two APS groups
When two STM1 modules are installed, it is necessary to

configure two APS groups: one group must include ports 1 of
each STM1 module, and the other group must include ports 2 of
each STM1 module
7-35
Code
Syntax
Meaning
102
MANAGER IP IN ANOTHER
INTERFACE SUBNET
The IP address configured for the management station must be

within the subnet of the Gmux-2000 IP interface on which it is
defined
103
MODEM CANNOT BE IN RELAY

WITH LBR
It is not allowed to configure a VC-E1/16 or VC-E1/12 bundle to

use modem relaying when using the LBRAD coder
104
DST PORT OF TS MUST BE 1 - 8

WITH LBR
When using the LBRAD coder for one of the VC-E1/16 or

VC-E1/12 module bundles, only the ports 1 to 8 can be in use
105
ALL VMX BUNDLES MUST HAVE

SAME LBR CODER
When using the LBRAD coder for one of the VC-E1/16 or

VC-E1/12 module bundles, all the other bundles defined on the
same module must also use the LBRAD coder
106
ILLEGAL PORT(9-16) FOR BUNDLE When using the LBRAD coder for one of the VC-E1/16 or
WITH LBR
VC-E1/12 module bundles, only the ports 1 to 8 can be in use:
the ports 9 to 16 cannot be used
107
PORT SHOULD HAVE SINGLE BNDL Only one bundle with TDMoIP V2 and OAM enabled can be
WITH OAM&V2
configured on each VC-E1/16 or VC-E1/12 module port
108
CLOCK MODE NOT THE SAME IN

BOTH STM PORTS
When two STM-1 ports are used, you must select the same timing
reference sources for both ports
109
STM PORT REDUNDANCY NOT

ALLOWED
When two STM-1 modules are used, you must select the module
redundancy mode when configuring an APS group, that is, the
APS group can include only STM-1 ports from different modules
(for example, port 1 of CL module A with port B of CL module B)
110
CHANNELS CHANGE ONLY AFTER

DISCNT & UPD DB
After changing channels used by an existing TDMoIP (CV) bundle,

first disconnect the bundle, and then update the database for the
changes to take effect
111
CODER CANNOT CHANGE FOR

ACTIVE BUNDLE
You cannot change the coder type and rate for an active TDMoIP
(CV) bundle: first disconnect the bundle, and then update the
database for the changes to take effect
112
VALUE OF CBID CANT BE ZERO
Make sure to configure a non-zero CBID value
113
VALUE OF VLAN ID CANT BE ZERO After enabling VLAN tagging, you must specify a non-zero VLAN
ID
114
ILLEGAL EXIT DATA PORT TS

MAPPING
Make sure to assign timeslots to the exit port of the TDMoIP (CV)
bundle
115
ILLEGAL BACKUP DATA PORT TS

MAPPING
Make sure to assign timeslots to the backup exit port of the

TDMoIP (CV) bundle
7-36
Gmux-2000 Ver. 3.2
7.4
Handling Alarms and Traps
Overview of Alarm Collection and Reporting

Alarm Buffer
The Gmux-2000 continuously monitors critical signals and signal processing
functions. In case a problem is detected, the Gmux-2000 generates time-stamped
alarm messages. The time stamp is provided by an internal real-time clock.
Note
The Gmux-2000 can also monitor one external sense input, and will report its
activation as any other internally-detected alarm.
The alarm messages generated by the Gmux-2000 are explained below.
Internally, the Gmux-2000 stores alarms in an alarm buffer. This alarm buffer can
store up to 256 alarm messages, together with their time stamps. The alarm
history buffer is organized as a FIFO queue, therefore after 256 alarms are
written into the buffer, new alarms overwrite the oldest alarms.
The alarms can be read on-line by the network administrator using a SNMP-based
network management station, a Telnet or SSH host, or a supervision terminal. The
network administrator can then use the various diagnostic tests to determine the
causes of the alarm messages and to return the system to normal operation.
For continuous system monitoring, the following tools are available:
Automatic sending of alarm messages through the supervisory port.
Automatic sending of alarm traps to the user-specified network management

stations.
Automatic sending of event notifications (all traps and alarms, exceeding a

user-configurable severity), to a user-specified remote syslog server.
When the Gmux-2000 is powered down, the alarm messages are erased, and
therefore old alarms will not reappear after the Gmux-2000 is powered up again.
When using the terminal or a Telnet/SSH host, the user also can clear (delete) the
alarms stored in this buffer, after reading them.
Alarm Relays
In addition to the alarm collection and reporting facility, the Gmux-2000 has two
alarm relays with floating change-over contacts: one relay for indicating the
presence of major alarms and the other for minor alarms. Each relay changes
state whenever the first alarm is detected, and returns to its normal state when
all the alarms of the corresponding severity disappear.
The relay contacts can be used to report internal system alarms to outside
indicators, e.g., lights, buzzers, bells, etc., located on a bay alarm or remote
monitoring panel.
Gmux-2000 Ver. 3.2
7-37
Configuring Alarm Handling

Gmux-2000 allows to customize alarm handling, and adapt the factory-default
alarm indications and reporting capabilities to specific application requirements.
During maintenance activities, you can also modify temporarily the alarm
reporting criteria, to reduce cluttering by alarms generated during
troubleshooting, or as a result of an intentional configuration change, while
waiting for service, etc.
When using the supervision terminal, this function is performed by means of the
Configuration>System>Alarms submenu.
A typical Alarms submenu, which serves as a task selection screen, is shown in
Figure 7-26.
Pseudowire Gateway
1.
2.
3.
4.
5.
6.
7.
Attribute
>
Priority
>
Init alarm priority
Threshold
>
Threshold window
>
Report
[]>
Input relay
>
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-26. Typical Alarms Task Selection Submenu
To perform a specific task:

1. Select the desired task:
1. To configure the alarm attribute (normal handling, versus masking or
inversion): use Configuration>System>Alarms>Attribute.
2. To define the alarm priority (severity) level: use
Configuration>System>Alarms>Priority.
3. To return alarm severities to the factory-defaults: use
Configuration>System>Alarms>Init Alarm Priority. You are required to
confirm: the change takes effect only after confirming the action.
4. To modify alarm activation thresholds for events: use
Configuration>System>Alarms Threshold.
5. To define observation windows for alarm filtering: use
Configuration>System>Alarms>Threshold Window.
6. To configure the alarm reporting method and indications: use
Configuration>System>Alarms>Report.
7-38
Gmux-2000 Ver. 3.2
7. To configure external alarm input characteristics and the associated alarm

string: use Configuration>System>Alarms>Input Relay.
2. After performing the desired task in accordance with the corresponding
section below, save the changes by pressing <Esc> to close the current
screen and return to the previous screen.
At this stage, the changes are stored in the Gmux-2000 configuration files
and take effect immediately.
Selecting Alarm Attributes

A typical Attribute screen is shown in Figure 7-27.
Pseudowire Gateway
Configuration>System>Alarms>Attribute
1. Alarm level
2. Alarm attributes
>
[]>
(SYSTEM)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-27. Typical Attribute Screen
To select the alarm level:

The item Alarm Level on the Attribute screen is used to select the target of an
attribute change. When you select this item, a target selection screen is
displayed. A typical screen is shown in Figure 7-28.
The screen provides the following targeting options:
Global, or system-wide Any special attribute (masking or inversion) selected

on this list is globally applied in the whole Gmux-2000. All the alarms are then
accessed in one list, ordered in ascending order of the alarm code numbers.
For this mode, use the default selection, System, as seen in Figure 7-27.
Specific used to apply a special attribute to a specific alarm, globally on the

Gmux-2000 (that is, irrespective of the entity reporting the alarm). For this
mode, use the Specific selection in Figure 7-28. After selecting this item,
Alarm Number appears as an additional item (together with the allowed
selection range) on the screen of Figure 7-27.
Filtered, or localized used when you want the special attribute to effect
only alarms generated by a specific entity (module, port or bundle). You can
filter the alarms in accordance with the reporting entity, by selecting the
target via the screen of Figure 7-28:
Gmux-2000 Ver. 3.2
A specific bundle. The bundle is selected by means of the Bundle Number

item, which appears as an additional item on the screen of Figure 7-27.
7-39
A specific slot (the Alarm Level) and type (referred to below as Alarm Sub
Level). The Alarm Sub Level item opens a selection screen with three
options:
General
All the alarms available for the selected Alarm Level, for
example, all the alarms that can be generated by the
module installed in the selected slot.
This option is relevant to all the slots.
Ext Port
The alarms that can be generated by an external port of the

This option is relevant only to slots with modules that have
external ports, for example, GbE, STM1, or E1-PW-28.
Int Port
The alarms that can be generated by an internal port of the

This option is relevant only to slots with modules that have
internal ports, for example, GbE, STM1, or E1-PW-SRV/21.
The desired external or internal port of the selected slot is selected by an

additional item, Ext. Port No. or Int. Port No., that appears after the
Alarm Sub Level item. A typical Attribute screen with the slot and port
selection fields is shown in Figure 7-29.
Pseudowire Gateway
Configuration>System>Alarms>Attribute>Alarm level (SYSTEM)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
SYSTEM
PS_A
PS_B
PS_C
CL_A
CL_B
IO_1
IO_2
IO_3
IO_4
11.
12.
13.
14.
15.
16.
IO_5
IO_6
IO_7
IO_8
IO_9
BUNDLE
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-28. Typical Attribute Level Selection Screen
7-40
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>System>Alarms>Attribute
1. Alarm level
2. Alarm sub-level
3. Alarm attributes
>
(IO_6)
>
(Slot)
[]>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-29. Typical Attribute Screen with Slot and Port Selection Fields
To select the alarm attributes:

The Alarm Attributes item on the Attribute screen is used to select the attribute
of one or more alarms. When you select this item, an alarm selection screen is
displayed. A typical Alarm Attributes screen is shown in Figure 7-30.
Note
Pseudowire Gateway
...>Alarms>Attribute>Alarm attributes
Alm no. Alarm description
1
REAL TIME CLOCK BATTERY FAILURE
4
FAN FAIL
| 5
FAN NOT EXIST
v 6
TEMPERATURE IS TOO HIGH
7
ALARM BUFFER OVERFLOW
13
DB-INIT SWITCH IS ON
1. Normal
2. Mask
Attribute
Normal
Normal
Normal
Normal
Normal
Normal
3. Invert
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-30. Typical Alarm Attributes Screen

The upper part of the screen contains a table with the code numbers and text
strings of the various alarms, in ascending order of their numbers, followed by
their current attribute.
Note
Gmux-2000 Ver. 3.2
For an explanation of the alarm meaning, refer to Chapter 7.
7-41
To change the attribute, move the cursor to the desired location, and then type
the item number for the new attribute.
The meaning of the various attributes are as follows:
Normal
The alarms are generated in accordance with the conditions

defined in the Interpreting Alarms section below, and reported in
accordance with the selections made using the Report screen.
Selecting Normal for an alarm effectively deletes any special
attribute defined for this alarm.
Mask
A masked alarm does not effect the Gmux-2000 alarm status. As a

result, the various alarm indicators of the Gmux-2000 will not turn
on a result of a masked alarm, and the generation of the
corresponding trap is disabled.
Selecting Mask for an alarm cancels the Invert attribute, if currently
defined for this alarm.
Invert
Change (invert) the interpretation of a selected alarm condition

with respect to Gmux-2000 visual indicators and alarm relays.
Note
It is not possible to invert event alarms, but only state

alarms.
Normally, an alarm is interpreted as being active when the

associated condition, is present (true).
When the alarm is inverted, the normal condition is the
presence of an alarm condition, and the condition that requires
alerting is the absence of the alarm state.
For example, when an E1 port is temporarily out of service, the
alarm indication related to loss-of-signal on the corresponding port
can be inverted. As a result, the general Gmux-2000 alarm
indicators and the SIG LOSS indicator on the E1 server module will
be turned off as long as the loss-of-signal condition is present, and
will turn on when the port returns to normal operation. The same
is true with respect to the alarm relays: if one of the alarm relays is
to be activated by that alarm, then inverting the alarm returns the
alarm relay to its non-alarm state while the alarm state is present.
Alarm inversion does not effect the state of the alarm recorded in
the Gmux-2000 alarm buffer (the alarm buffer shows the true
state).
Selecting Invert for an alarm cancels the Mask attribute, if currently
defined for this alarm.
Note
7-42
When alarms are displayed, masked alarms are identified by an M appearing at

the right-hand side of the alarm line, and inverted alarms are identified by an I.
Gmux-2000 Ver. 3.2
Selecting Alarm Priorities

The Gmux-2000 supports four alarm severity levels (priorities): warning (lowest
level), minor, major, and critical (highest level). The indications provided for each
severity level can be defined by means of the Report screen.
You can change the factory-default priority levels for the desired alarms by
means of the Priority screen.
A typical Priority screen is shown in Figure 7-31.
Pseudowire Gateway
Configuration>System>Alarms>Priority
1. Define alm priority
2. Alarm priority
>
(All)
[]>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-31. Typical Priority Screen
To select alarms for priority changing:

The Define alm priority item on the Priority screen is used to select the target of
a priority change. When you select this item, a target selection screen is
displayed, with two options:
All in this case, all the alarms are accessed in one list, ordered in ascending
order of the alarm code numbers. This is the default selection, as seen in
Figure 7-31.
Specific used to change the priority of a specific alarm. After selecting this
item, Alarm Number appears as an additional item (together with the allowed
selection range) on the screen of Figure 7-31.
To select the alarm priority:

The Alarm Priority item on the Priority screen is used to select the attribute of
one or more alarms. When you select this item, an alarm selection screen is
displayed. A typical Alarm Priority screen is shown in Figure 7-32.
Note
their current priority. When the Define alm priority is Specific, only the selected
alarm is displayed.
Gmux-2000 Ver. 3.2
7-43
Note

To change the displayed priority, move the cursor to the desired location, and
then type the item number, 1 to 4, for the new priority.
Pseudowire Gateway
Configuration>System>Alarms>Priority>Alarm priority
Alm no. Alarm description
1
REAL TIME CLOCK BATTERY FAILURE
2
POWER SUPPLY FAILURE
| 3
POWER SUPPLY DERATING
v 4
FAN FAIL
5
FAN NOT EXIST
6
TEMPERATURE IS TOO HIGH
1. Warning
2. Minor
Priority
Major
Warning
Warning
Critical
Critical
Critical
3. Major
4. Critical
>
1 M/ 1 C
----------------------------------------------------------------------------THE OPERATION WILL EFFECT ONLY AFTER YOU RETURN TO ALARM MAIN MENU!!
Figure 7-32. Typical Alarm Priority Screen
Selecting Alarm Thresholds

Gmux-2000 can use threshold values, in conjunction with the filtering window
defined by means of the Threshold Window screen, to determine when to
generate an alert because the frequency of the specified events is too high:
Note
Alerts are generated when the specified Set threshold is exceeded.
A separately defined Reset threshold is used to cancel the alert when the
frequency of the monitored events decreases below that threshold.
Alerts generated when a threshold is exceeded cannot be masked, even in case

the monitored event is masked by means of the Attribute screen.
You can enable/disable the use of thresholds and change the factory-default
threshold values by means of the Threshold screen. A typical Threshold screen is
To select the alarm level:

Alarm Level on the Threshold screen is used to select the target of an attribute
change. When you select this item, a target selection screen is displayed. A
typical screen is shown in Figure 7-28.
The procedure used to select the alarm level is similar to that described starting
on page 7-39 for the Attribute screen.
7-44
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Configuration>System>Alarms>Threshold
1. Alarm level
2. Alarm threshold
>
(SYSTEM)
[]>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-33. Typical Threshold Screen
To select the alarm threshold:

The Alarm Threshold item on the Threshold screen is used to enable/disable the
use of thresholds and select threshold values for one or more alarms. When you
select this item, an alarm selection screen is displayed. A typical Alarm Threshold
configuration screen is shown in Figure 7-34.
Note
Pseudowire Gateway
Configuration>System>Alarms>Threshold>Alarm threshold
Alm Alarm description
7
ALARM BUFFER OVERFLOW
13
DB-INIT SWITCH IS ON
| 14
DIAL-UP OR SP SWITCH IS ON
v 15
CLOCK WAS CHANGED TO FALLBACK
16
CLOCK WAS CHANGED TO INTERNAL
17
CLOCK WAS CHANGED TO MASTER
1. Change cell
Threshold Set Reset

No
0
0
No
0
0
No
0
0
No
0
0
No
0
0
No
0
0
... (No)
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-34. Typical Alarm Threshold Configuration Screen

their current attribute. When the Alarm Level is Specific, only the selected alarm
is displayed.
Note
Gmux-2000 Ver. 3.2
7-45
To change a parameter, move the cursor to the desired location, and then type
Change cell to change the selected location. The allowed range is automatically
shown next to the Change cell field.
The meaning of the various parameters are as follows:
Threshold
Used to enable (Yes) or disable (No) the use of thresholds for

an alarm.
Default: No
Set
When thresholds are used for the corresponding alarm, selects

the minimum number of times the alarm must occur during the
observation window for the alarm to be declared active. The
allowed range is 1 through 256.
Default: 0
Reset
When thresholds are used for the corresponding alarm, selects

the maximum number of times the alarm may occur during the
observation window for the alarm to be declared inactive. The
allowed range is 1 through 256, but the number entered in
this field must be less than the number entered as the Set
threshold.
Default: 0
Selecting Alarms Threshold Window

Gmux-2000 can use threshold values defined by means of the Threshold screen,
in conjunction with the observation window defined by means of the Threshold
Window screen.
A typical Threshold Window screen is shown in Figure 7-35.
Pseudowire Gateway
Configuration>System>Alarms>Threshold window
1. Alarm window[1 - 30]... (15)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-35. Typical Threshold Window Screen
To select the observation window:

1. Type Alarm Window and then enter the desired window duration, in the
range of 1 to 30 seconds.
2. When done, press <Enter>.
7-46
Gmux-2000 Ver. 3.2
Selecting Alarm Reporting Method

Gmux-2000 has a factory-default set of reporting rules for alarms. You can
change this set and define the alarm reporting method and indications for each
alarm severity (priority) level using the Report screen.
Typical Report screens are shown in Figure 7-36. The screen has two pages: use
the arrow keys to scroll between screen pages.
Note
Pseudowire Gateway
Configuration>System>Alarms>Report
Alarm
Report
Critical on
Yes
Critical off
Yes
| Major on
Yes
v Major off
Yes
Minor on
Yes
Minor off
Yes
Relay-1
Yes
N/A
Yes
N/A
Yes
N/A
Relay-2
Yes
N/A
Yes
N/A
Yes
N/A
Log
Yes
Yes
Yes
Yes
Yes
Yes
Min alarm led

Yes
N/A
Yes
N/A
Yes
N/A
Maj alarm led

Yes
N/A
Yes
N/A
Yes
N/A
1. No
2. Yes
>
1 M/ 1 C
-----------------------------------------------------------------------------

Pseudowire Gateway
Configuration>System>Alarms>Report
^ Alarm
| Major off
Minor on
Minor off
Warning on
Warning off
Event
Report
Yes
Yes
Yes
Yes
Yes
Yes
Relay-1
N/A
Yes
N/A
Yes
N/A
Yes
Relay-2
N/A
Yes
N/A
Yes
N/A
Yes
Log
Yes
Yes
Yes
Yes
Yes
Yes
Min alarm led

N/A
Yes
N/A
Yes
N/A
Yes
Maj alarm led

N/A
Yes
N/A
Yes
N/A
Yes
1. No
2. Yes
>
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 7-36. Typical Report Screens
The Report screen includes a list of the alarm severities, and six columns which
are used to select the action to be taken for each alarm severity and state (ON or
OFF). The fields appearing on the screen are explained below.
Gmux-2000 Ver. 3.2
7-47
Alarm
The alarm state.
Report
YES indicates that the corresponding alarm state is reported

by means of messages sent to the supervisory terminal, and
traps sent to management stations.
Log
YES indicates that the corresponding alarm state is recorded

in the alarm buffer.
Relay-1
YES indicates that the major alarm relay is activated when the
corresponding state occurs. Default setting is to be activated
for major and critical alarm levels.
Relay-2
YES indicates that the minor alarm relay is activated when the
corresponding state occurs. Default setting is to be activated
for minor and higher alarm levels.
Min alarm led
YES indicates that the MIN ALARM indicator lights steadily

when the corresponding state occurs.
Maj alarm led
YES indicates that the MAJ ALARM indicator flashes when the
corresponding condition occurs.
To change an alarm reporting or indication selection:

Move the cursor to the desired location, and then type Change cell to change the
selected location.
To ensure consistent display and reporting of alarm conditions, pay attention to
the following points:
For any alarm function, once it is set to YES at a certain alarm level, it needs
to be set to YES for all the alarm levels above it. For example, if the Led on is
set to be YES for minor alarms, it will also be activated for major and critical
alarms.
For any alarm condition, once it is set to NO at a certain alarm level, it needs
to be set to NO for all the lower alarm levels. For example, if the Blink Led is
set to be activated for major alarms, must also be deactivated for minor,
warning and event alarms.
Report and Log functions can also be independently set when a particular
alarm condition ceases (for example, for Minor off). In this case, all the OFF
alarm conditions above that level must also be set to YES.
Relays and LEDs cannot be activated for alarm OFF conditions, and therefore
N/A appears in the rows corresponding to the end-of-alarm conditions.
Configuring Alarm Input Functions

The Gmux-2000 external alarm input (available in the ALARMS connector of the
chassis see details in Appendix A) can be monitored by the management agent,
and an alarm with a user-selectable string be sent when a specific state is
sensed.
Currently, only one external alarm input is supported.
7-48
Gmux-2000 Ver. 3.2
The required configuration is made by means of the Input Relay screen. A typical
Input Relay screen is shown in Figure 7-37.
Pseudowire Gateway
Configuration>System>Alarms>Input relay
1.
2.
3.
4.
Input alarm relay[1 - 2] ...

Connect
>
Active
>
Alarm string
...
(1)
(No)
(High)
( INPUT ALARM RELAY 1
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-37. Typical Input Relay Screen
To configure the functions of the external alarm input:

1. Leave the default selection for Input alarm relay, because only input 1 is
supported.
2. To toggle the Connect field, type 2 and then press <Enter>. The external
alarm input is monitored only when you select Yes.
3. To toggle the active state (the state that will result in alarm generation) in
accordance with the specific requirements of your application, type 3 and
then press <Enter>:
High means that the alarm is generated when the external alarm input
pins are open-circuited
Low means that the alarm is generated when the external alarm input
pins are short-circuited.
4. To modify the default alarm string, select 4 and then type the desired string
(up to 20 alphanumeric characters). Press <Enter> when done.
Using the Event Log

The Gmux-2000 event log contains all the recorded events in accordance with
their occurrence time stamp. For example, you may find in the event log the time
an alarm has been detected, as well as the time at which the alarm condition
disappeared. Therefore, the event log contains the alarm history of the
Gmux-2000 and can be used to analyze the order of events, for example, for
troubleshooting purposes.
In addition to reading the event log, you may clear the whole log, or selected
parts of it, as the events are no longer of importance. To permit deleting only
those events that are no longer relevant Gmux-2000 provides a wide range of
Gmux-2000 Ver. 3.2
7-49
filtering tools, in accordance with type (history or status), or source (system,

specific module, or even a specific port). Since many records may be generated
after a fault occurs, or during maintenance, clearing the log after the conditions
return to normal is recommended to ensure that maximum storage is available for
new events.
Reading the Event Log
To display the log file:

1. Open the Monitoring menu, and select Event Log.
Pseudowire Gateway
Monitoring>Event log
1. Read log file
2. Clear log
[]>
>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-38. Typical Monitoring Event Log Submenu

2. Select Read Log File.
You will see the Read Log File screen. A typical Read Log File screen is
shown in Figure 7-39. When the screen is first displayed, only the lefthand section is displayed: to view the additional fields, scroll to the right.
Note
The events appear on the Clear Log screen in the order they have been recorded
in the log (the last event appears at the end of the list). For each event, you can
see (from left to right): the alarm code, the source, a short description of the
alarm condition, the severity level, and the time stamp
7-50
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Monitoring>Event log>Read log file
(005)
(004)
(019)
| (019)
v (019)
(019)
SYS
SYS
IO 9
IO 8
IO 7
IO 6
FAN NOT EXIST

FAN FAIL
PROGRAMMED,INSTALLED
MODULE
MODULE
MODULE
MODULE
MIS
MIS
MIS
MIS
Critical
Critical
Major
Major
Major
Major
->>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-39.A. Typical Read Log File Screen (Left-hand Side)

Pseudowire Gateway
Monitoring>Event log>Read log file
SYS
SYS
IO 9
| IO 8
v IO 7
IO 6
FAN NOT EXIST

FAN FAIL
MODULE
MODULE
MODULE
MODULE
MIS
MIS
MIS
MIS
Critical
Critical
Major
Major
Major
Major
14:26:49
14:26:49
14:26:42
14:26:42
14:26:42
14:26:42
<<- ->>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-39.B. Typical Read Log File Screen (Right-hand Side)
Clearing the Log
To clear the desired section of the log:

1. Open the Event Log submenu, and select Clear Log.
2. You will see the Clear Log alarm type selection screen. A typical screen is
Gmux-2000 Ver. 3.2
7-51
Pseudowire Gateway
Monitoring>Event log>Clear log
1.
2.
3.
4.
Alarm
Alarm
Alarm
Clear
buffer type
priority
level
alarms
>
>
>
(Both)
(All)
(ALL)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-40. Typical Clear Log Alarm Type Selection Screen

3. Select Alarm Buffer Type to open the buffer type selection screen:
History clear records from the history log
Status clear records from the current alarms log
Both clear records from the both history log and the current log.
4. You may skip Alarm Priority the only selection is All (no filtering in
accordance with alarm severity).
5. Select Alarm Level to open the Alarm Level selection screen. A typical screen
Pseudowire Gateway
Monitoring>Event log>Clear log>Alarm level (All)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
SYSTEM
PS-A
PS-B
PS-C
CL-A
CL-B
IO-1
IO-2
IO-3
IO-4
IO-5
IO-6
13.
14.
15.
16.
17.
18.
IO-7
IO-8
IO-9
BUNDLE
SPECIFIC
ALL
>
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-41. Typical Alarm Level Selection Screen
7-52
Gmux-2000 Ver. 3.2
6. Select the desired level:
System clear only records associated with the Gmux-2000 system level
PS, CL, IO clear only records associated with a specific PS, CONTROL, or
I/O module
Bundle clear only records associated with a specific bundle
Specific clear only records for specific alarm (option not active).
All clear all the records.
If you selected a module or bundle, the screen changes to include an

additional item, Alarm Sub-level.
7. Select Alarm Sub-level to open the sub-level selection screen. The available
sub-levels depend on the selected level:
For modules, you can select the slot level, or a specific port. The selection
of a specific port is made in two steps: first you select a specific type of
ports (in accordance with the types of ports supported on the selected
module), and then you select the desired port number.
For bundles, you can select a specific port.
8. After selecting the sub-level and a specific type and port number, you are
ready to clear the corresponding records from the event log. A typical screen
Pseudowire Gateway
Monitoring>Event log>Clear log
1.
2.
3.
4.
5.
Alarm
Alarm
Alarm
Alarm
Clear
buffer type
priority
level
sub-level
alarms
>
>
>
>
(History)
(All)
(IO-1)
(E1 port)
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-42. Typical Clear Log Alarm Type Selection Screen with Alarm Sub-Level Options
9. Select Clear Alarms and then press <Enter> to execute the action.
Displaying Alarms
To select alarms of a specific type for display:

1. To select the type of alarms to be displayed, open the Monitoring menu and
then select Alarm.
2. You will see the Alarm submenu. A typical Alarm submenu is shown in
Figure 7-43.
Gmux-2000 Ver. 3.2
7-53
Pseudowire Gateway
Monitoring>Alarm
1.
2.
3.
4.
5.
6.
Display
Display
Display
Display
Display
Dsp all
system alarm[]>
PS alarms
>
CL alarms
>
I/O alarms >
bundle alarm>
alarms
[]>
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-43. Typical Monitoring Alarm Submenu

3. Select the desired type of alarms and then press <Enter>. Additional
selections may appear, depending on the selected type:
For modules, you can select the general level, the slot level, or a specific
port (in accordance with the types and number of ports supported on the
selected module).
For bundles, you can select a specific port.
4. Make the additional selections, and then press <Enter> to display the
requested alarms. If there are no alarms, you will see only a No Alarms for
this level message.
A typical alarm display screen is shown in Figure 7-44.
Pseudowire Gateway
Monitoring>Alarm>Dsp all alarms
(SYS)
(SYS)
(SYS)
| (IO 1)
v (IO 1:E1 1)
(IO 1:E1 1)
FAN FAIL
Critical
FAN NOT EXIST
Critical
CL FLIP HAS OCCURED
Event
PROGRAMMED,INSTALLED MODULE MIS Off
SIGNAL LOSS
Major
LOCAL SYNC LOSS
Major
1
1
1
1
1
1
>

1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-44. Typical Alarm Display Screen
7-54
Gmux-2000 Ver. 3.2
Interpreting Alarms
Table 7-10 lists the alarm messages generated by the Gmux-2000 and explains
their interpretation. The alarm messages are listed in ascending order of their
codes.
For each alarm, Table 7-10 also specifies the type (event or state), and lists the
default severity level for state alarms. The severity level can be modified in
accordance with the specific customers requirements using the
Configuration>System>Alarm screen.
Note
A state alarm is an alarm that is in the ON state while a certain condition is

present, and automatically changes to OFF when the condition is no longer
present. This type of alarm cannot be cleared (removed from the alarm buffer)
while it is in the ON state.
An event alarm is an alarm that records the occurrence of an event. This type of
alarm can be cleared at any time.
System and CONTROL Module Alarms

Table 7-10. Gmux-2000 CONTROL Alarms
Code Message
1
REAL-TIME CLOCK
BATTERY FAILURE
Type
Default
Severity
State
Major
Interpretation
The battery powering the Gmux-2000 internal real-time
clock while the Gmux-2000 is not powered has failed.
POWER SUPPLY FAILURE State
Major
A power supply module is missing, is not turned on or

failed.
Install, turn on, or replace the corresponding power supply
module
POWER SUPPLY
DERATING
FAN FAIL
State
State
Major
Critical
The corresponding power supply provides reduced power,

in response to the activation of its internal protection
circuits.
1.
Check that all the other power supplies are not failed.
2.
Check that the fan tray operates normally.
3.
If the problem persists, replace the power supply.
The fan tray is not installed, or a failure has been detected

in the fan tray.
Install or replace the fan tray
FAN NOT EXIST
State
Critical
The fan tray is not installed, or a failure has been detected

in the fan tray.
TEMPERATURE IS TOO
HIGH
State
Warning The fan tray is not installed, or a failure has been detected
in the fan tray.
Gmux-2000 Ver. 3.2
7-55
Code Message
7
ALARM BUFFER
OVERFLOW
Type
Default
Severity
Event
Major
Interpretation
More than 255 alarms entries have been written in the
history alarm buffer since the last clear command.
Read the messages, and then clear the alarm buffer from
the supervision terminal
HARDWARE FAILURE
State
Major
Technical failure in the module installed in the specified

slot.
Replace the Gmux-2000 I/O module installed in the
specified slot
FILE SYSTEM ERROR
State
Critical
Replace the corresponding CONTROL module.
Note The problem may sometimes be corrected by

formatting the flash disk, an action that should
only be performed by authorized technical support
personnel.
10
LOW DISK SPACE
State
Major
The storage space left on the internal flash disk of the

CONTROL module is too low.
To free space, it is necessary to remove some of the files
that store non-essential data, an action that should only
be performed by authorized technical support personnel
11
CLOCK PIGGY CHANGED

TO STANDBY
State
Warning Problem in CLOCK card (part of the CONTROL module).

Replace the CONTROL module
12
MODULE WAS REMOVED Event
Major
The module installed in the specified slot has been

removed
13
DB INIT SWITCH IS ON
Major
Section DB INIT of switch SW2 on the CONTROL module is

set to ON.
Event
If it is no longer necessary to enforce the default database

parameter values, change setting to OFF (see Chapter 3
for instructions)
14
DIAL-UP OR SP SWITCH
IS ON
State
Major
Reserved for future use
15
CLOCK WAS CHANGED

TO FALLBACK
Event
Major
The main clock source of the Gmux-2000 failed, and the

fallback clock source has been selected.
Check the port providing the master clock source: the
Gmux-2000 replaces the recovered clock when the
corresponding port loses frame synchronization or its
input signal is missing.
16
CLOCK WAS CHANGED

TO INTERNAL
Event
Major
Both the main and fallback clock sources of the

Gmux-2000 failed, and the internal clock source has been
selected.
Check the port providing the master and fallback clock
source: the Gmux-2000 replaces the recovered clock when
the corresponding port loses frame synchronization or its
input signal is missing.
7-56
Gmux-2000 Ver. 3.2
Code Message
17
CLOCK WAS CHANGED

TO MASTER
Type
Default
Severity
Event
Major
Interpretation
The Gmux-2000 switched back to the clock source
selected as the master source.
Normal state - no action required
18
CL FLIP HAS OCCURRED
Event
Major
The other CONTROL module has been selected as the online module.
Check the reason for flipping, and act accordingly
19
20
21
PROGRAMMED,
INSTALLED MODULE
MISMATCH
State
CL-A, B DIFFERENT
SOFT/HARD REVISIONS
Event
DP DIAL CYCLE FAILED
Major
The modules that have been read from the Gmux-2000 do

not match the modules programmed in the database.
Either replace the modules, or change the information
appearing in the database
Event
Major
Major
The CONTROL modules currently installed in the

Gmux-2000 chassis have different software versions
and/or hardware revisions. Use the Inventory menu to
check the reason:
If the hardware versions are different, one of the

modules must be replaced. Contact RAD Technical
Support department.
If the software versions are different, reload the

appropriate version in both modules in accordance
with Appendix B
The current cycle of call attempts failed.

Check the modem connected to the Gmux-2000 serial
port. If the called numbers are often busy, you may also
increase the number of call retries
22
23
DATABASE CHECKSUM
ERROR
State
LOSS OF STATION
CLOCK EXT IN 1
State
Major
Gmux-2000 technical failure (internal database error).

Load the default configuration in the place of the current
database (from the supervision terminal, enter the INIT DB
command)
Minor
The station clock interface located on the CONTROL

module 1 and reports that the clock signal is missing.
Check connections and the equipment providing the clock
signal.
If problem persists, replace the CONTROL module
24
LOSS OF STATION
CLOCK EXT IN 2
State
Minor
The station clock interface located on the CONTROL

module 2 and reports that the clock signal is missing.
Check connections and the equipment providing the clock
signal.
If problem persists, replace the CONTROL module
25
DP PRIMARY CALL
FAILED
Gmux-2000 Ver. 3.2
Event
Major
The call attempts to the primary dial-out number failed. If

the number is not busy, check the modem connected to
the Gmux-2000. If the called number is often busy, you
may also increase the number of call retries
7-57
Code Message
26
DP ALTERNATE CALL
FAILED
Type
Default
Severity
Event
Major
Interpretation
The call attempts to the alternate dial-out number failed.
If the number is not busy, check the modem connected to
the Gmux-2000.
If the called number is often busy, you may also increase
the number of call retries
44
B.R.G FAILURE
Event
Major
45
SFIFO SLIP
Event
Major
46
MANAGEMENT NOT
SUPPORTED IN SOFT
REV
State
Major
You are trying to use DCC management, a function not

supported by the software version currently loaded in the
Gmux-2000
47
DB CONTROL WAS
TAKEN BY SNMP MMI
Event
Major
The Gmux-2000 database is being edited from a

supervision terminal, while it is also being edited by an
SNMP-based network management station.
It is user's responsibility to prevent possible conflicts by
stopping the editing from either the terminal or the
management station
48
DB CONTROL WAS
TAKEN BY TERM MMI
Event
Major
The Gmux-2000 database is being edited by an

SNMP-based network management station, e.g., RADview,
while it is also being edited using a supervision terminal.
It is user's responsibility to prevent possible conflicts by
stopping the editing from either the terminal or the
management station
50
LOOP INBAND ON
State
Minor
52
LOCAL LINE LOOP
State
Minor
53
REMOTE LINE LOOP
State
Minor
54
LOCAL LOOP TOWARD

DTE
State
Minor
55
LAN NOT CONNECTED
State
Minor
The CONTROL ETH port is not connected to an active

Ethernet LAN
56
I/O FLIP HAS OCCURRED Event
Major
57
IO REDUNDANCY NOT
SUPPORTED IN SW REV
Event
Major
You are trying to activate I/O redundancy, a function not

supported by the software version currently loaded in the
Gmux-2000
58
PORT FLIP HAS

OCCURRED
Event
Major
The active port has been changed
59
BUS CAPACITY EXCEEDS
State
Major
The internal bus capacity has been exceeded. Reduce the

traffic load
60
TX FAIL
State
Major
The optical transmitter reports a failure
61
TX DEGRADE
State
Major
The optical transmitter reports a degradation fault
62
POINTER ERROR
Event
Major
A pointer-related fault occurred
72
CRITICAL ALARM
State
Major
A critical alarm has been detected
73
PORT SPEED 100
State
Major
The Ethernet port speed is 100 Mbps
7-58
Gmux-2000 Ver. 3.2
Code Message
Type
Default
Severity
Interpretation
74
PORT SPEED 10
State
Major
The Ethernet port speed is 10 Mbps
75
PORT FULL DUPLEX
State
Major
The Ethernet port operates in the full duplex mode
76
PORT HALF DUPLEX
State
Major
The Ethernet port operates in the half duplex mode
77
PORT LINK UP
State
Major
The Ethernet port reports that the link is up
79
INPUT ALARM RELAY 1
State
Major
The external alarm input is active
80
INPUT ALARM RELAY 2
State
Major
88
CLOCK FAIL
State
Major
The internal clock reports a problem
89
REFERENCE CLOCK FAIL
State
Major
The selected reference clock source failed
91
SOFTWARE MISMATCH
State
Major
A software mismatch has been detected
104
BUNDLE FRAME WITH

CRC ERROR
State
Major
A CRC error has been detected in bundle frames
105
BUNDLE FRAME WITH

ALIGNMENT ERROR
Event
Major
A frame alignment has been detected in bundle frames
106
BUNDLE FRAME
LONGER THAN MAX
vent
Major
The received bundle frame exceeds the maximum length
107
BUNDLE FRAME
SHORTER THAN 4
vent
Major
The received bundle frame is too short
108
BUNDLE FRAME WITH

ABORT INDICATION
vent
Major
The received bundle frame carries an Abort indication
109
LINK IS ACTIVE
State
Minor
The link is up and carries traffic
141
DSP MEMORY TEST FAIL Event
Major
A technical problem occurred
142
BUNDLE IS OUT OF
SERVICE
Major
The bundle is out of service
State
GbE Module Alarms

Table 7-11. GbE Module Alarms
Code Message
8
HARDWARE FAILURE
Type
Default
Severity
State
Major
Interpretation
Hardware problem.
Replace the GbE module
78
PORT LINK DOWN
State
Major
The specified GbE link is down.

Check port connections
81
GBETH CAM L4 POOL1

FULL
State
Major
Too many bundles have been defined on the specified

GbE port, considering the maximum capacity of layer 4
socket pool 1.
Delete unused bundles
Gmux-2000 Ver. 3.2
7-59
Code Message
82
GBETH CAM L4 POOL2

FULL
Type
Default
Severity
State
Major
Interpretation
socket pool 2.
83
GBETH CAM L4 POOL3

FULL
State
Major

socket pool 3.
84
GBETH CAM L4 POOL4

FULL
State
Major

socket pool 4.
110
Major
GBETH POOL BLOCK

OVERFLOW
STM1 Module External SDH Port Alarms

Table 7-12. External SDH Port Alarms
Code Message
8
HARDWARE FAILURE
Type
Default
Severity
Interpretation
State
Major
The STM1 module reports technical failure.

27
29
64
SIGNAL LOSS
AIS OCCURED
LOSS OF FRAME
State
State
State
Major
Major
Major
Loss of port receive signal.

1.
Check cable connections to the port connector.
2.
Check line and/or other communication equipment

providing the port to the remote unit.
3.
Replace the STM1 module installed in the specified

slot of the Gmux-2000
Unframed all ones sequence is received in specific port

data stream.
1.
Reset the STM1 module.
2.
Replace the STM1 module.
A loss of frame (LOF) state exists at the specified STM-1

port.
Check for problems on the SDH link, or at the remote
equipment unit
65
OUT OF FRAME
State
Major
The specified STM-1 port lost frame synchronization.

equipment unit
66
7-60
SIGNAL LABEL LOSS OF

LOCK
State
Major
The STM1 module reports that it cannot detect the signal

label. Check for problems on the SDH link, or at the
remote equipment unit
Gmux-2000 Ver. 3.2
Code Message
69
86
SIGNAL DEGRADED
ERROR
REMOTE FAILURE
INDICATION
Type
Default
Severity
State
Minor
State
Minor
Interpretation
The specified port reports BER exceeding the preset signal
degradation threshold.
1.

equipment unit.
2.
If the problem persists, replace the module
Remote defect indication.

1.
Check the Tx connection.
2.
Check the configuration.
3.

87
90
VC/VT- RDI
State
EXCESSIVE ERROR
DETECTED
State
Minor
Major

1.
2.
3.
4.
The specified port reports BER exceeding the preset signal

degradation threshold.
1.

equipment unit.
2.
STM1 Module Internal VC-4 Port Alarms

Table 7-13. Internal VC-4 Port Alarms
Code Message
62
POINTER ERROR
Type
Default
Severity
State
Major
Interpretation
The loss of pointer (LOP) state is entered when N
consecutive invalid pointers are received by the specified
VC-4 port (N = 8, 9 or 10).
LOP state is exited when 3 equal valid pointers or 3
consecutive AIS indications are received.
equipment unit
67
SIGNAL LABEL
MISMATCH
State
Major
The specified VC-4 port detects a signal label mismatch.

This may indicate incorrect routing of the corresponding
VC.
This alarm condition may occur while a new route is being
prepared.
Gmux-2000 Ver. 3.2
1.
Check routing of corresponding signal.
2.

equipment unit
7-61
Code Message
68
69
70
SIGNAL LABEL
UNEQUIPPED
SIGNAL DEGRADED
ERROR
PATH TRACE ID
MISMATCH
Type
Default
Severity
State
Major
State
State
Minor
Major
Interpretation
The specified VC-4 port receives an unequipped signal
label.
1.
Check routing of the corresponding signal.
2.

equipment unit
The specified port reports BER exceeding the preset

signal degradation threshold.
1.

equipment unit.
2.
The specified VC-4 port detects a path trace mismatch.

VC.
prepared.
71
86
90
7-62
PATH TRACE
UNEQUIPPED
REMOTE FAILURE
INDICATION
EXCESSIVE ERROR
DETECTED
State
State
State
Major
Minor
Major
1.
Check routing of the VC-4 signal.
2.

equipment unit
The STM1 module reports that it receives an unequipped

path trace.
1.
2.

equipment unit

1.
2.
3.
4.

1.

equipment unit.
2.
Gmux-2000 Ver. 3.2
STM1 Module Internal VC-12 Port Alarms

Table 7-14. Internal SDH VC-12 Port Alarms
Code Message
30
63
VC/VT - AIS
LOSS OF POINTER
Type
Default
Severity
Interpretation
State
Major
An all 1 signal label is received by the specified port.
State
Major
1.
Check configuration and routing.
2.
Check the remote equipment unit.
3.
4.
The loss of pointer (LOP) state is entered when N

consecutive invalid pointers are received by the specified
VC-12 port (N = 8, 9 or 10).
LOP state is exited when 3 equal valid pointers or 3
consecutive AIS indications are received.
equipment unit
67
SIGNAL LABEL
MISMATCH
State
Major
The specified VC-12 port detects a signal label mismatch.

VC.
prepared.
68
69
70
SIGNAL LABEL
UNEQUIPPED
SIGNAL DEGRADED
ERROR
PATH TRACE ID
MISMATCH
State
State
State
Major
Minor
Major
1.
Check routing of corresponding signal.
2.

equipment unit
The specified VC-12 port receives an unequipped signal

label.
1.
Check routing of the corresponding signal.
2.

equipment unit

1.
Check for problems on the SDH link, or at the

remote equipment unit.
2.
The specified VC-12 port detects a path trace mismatch.

VC.
prepared.
Gmux-2000 Ver. 3.2
1.
2.

equipment unit
7-63
Code Message
71
87
90
PATH TRACE
UNEQUIPPED
VC/VT - RDI
Type
Default
Severity
State
Major
State
EXCESSIVE ERROR
DETECTED
State
Minor
Major
Interpretation
The STM1 module reports that it receives unequipped
path trace.
1.
2.

equipment unit

1.
2.
3.
4.

1.

equipment unit.
2.
Pseudowire Emulation Server Module Alarms

Table 7-15. E1 (Internal or External) Port Alarms
Code Message
27
28
SIGNAL LOSS
EXCESSIVE BPV
Type
Default
Severity
State
Major
State
Major
Interpretation
Loss of receive signal. SIGNAL LOSS is also indicated when
the front panel SYNC LOS LED lights up.
1.
Check cable connection to the E1 link connector.
2.

connected to the link of the remote unit
The rate of bipolar violations in the port receive signal

exceeds 10-6 during a measurement interval of 1000
seconds.
Problem in network facilities
29
AIS OCCURED
State
Major
AIS is detected on the link.

Check equipment connected to the remote end of the E1
link
32
AIS SYNC LOSS
State
Major
Loss of frame synchronization alarm on the link, caused

by AIS condition.
Check equipment connected to the remote end of the E1
link
34
7-64
LOCAL SYNC LOSS
State
Major
Local loss of frame synchronization alarm on E1 link.

1.
Check cable connection to the link connector.
2.

providing the E1 link to the local server module.
3.
Replace the server module
Gmux-2000 Ver. 3.2
Code Message
35
36
LOCAL MF ALARM
REMOTE MF ALARM
Type
Default
Severity
State
Major
State
Major
Interpretation
Local loss of multiframe synchronization alarm on E1 link.
Active only when Frame Type is Multiframe.
1.
Check that the correct Frame Type is used at the local

and remote ends.
2.
Perform the corrective actions listed for LOCAL SYNC

LOSS
Remote loss of multiframe synchronization alarm on the

specified link.
Active only when Frame Type is Multiframe.
Check the remote equipment
38
REMOTE SYNC LOSS
State
Major
Remote loss of frame synchronization alarm on link.

Check the remote equipment. Perform the following:
39
FRAME SLIP
Event
Major
1.
Check cable connection to the E1 connector of the

remote device.
2.

providing the E1 link to the remote equipment.
3.
Replace the remote equipment
E1 frame slips are detected (not displayed during local loss

of frame synchronization). Updated once per second.
1. Verify the clock settings.
2. Check the far end (unstable clock source).
3. Replace the server module only if steps 1 and 2 do not
correct the problem
40
41
BPV ERROR
EXCESSIVE ERR RATIO
Event
State
Major
Major
Bipolar violations on the link receive signal. Updated once

per second.
1.
Check the TDM equipment and cable connecting it to

the E1 port.
2.
The bit error rate of the port receive signal exceeds 10-3.
Problem in network facilities
42
CRC-4 ERROR
Event
Major
CRC-4 errors detected in the link receive signal. Updated

once per second.
Active only when CRC=Yes.
51
CRC MULTIFRAME
ALIGNMENT LOST
State
Major
1.

the E1 port.
2.
CRC errors detected in the multiframe synchronization

signal of the link receive signal. Updated once per second.
Active only when CRC=Yes and Frame Type is Multiframe.
Gmux-2000 Ver. 3.2
1.

the E1 port.
2.
7-65
Code Message
85
LOSS OF MULTI-FRAME
Type
Default
Severity
Minor
Major
Interpretation
On an E1 main link operating with G.704 multiframe, the
corresponding main link module port has lost multiframe
synchronization
Bundle Alarms
Table 7-16. Bundle Alarms
Code Message
Type
Default
Severity
Interpretation
92
BUNDLE OAM OUT OF

SYNC
State
Major
The OAM signaling mechanism (used to check

connectivity) detected loss of connectivity
93
BUNDLE OAM
CONFIGURATION
MISMATCH
State
Major
Packet discarded due to mismatch in TDMoIP frame

format between the received packet and the bundle
configuration
94
BUNDLE HW LACK OF
TX BUFFERS
Event
Major
Packet discarded due to mismatch between received

packet length and bundle configuration
95
BUNDLE LOCAL FAIL
State
Major
Bundle no longer receives packets
96
BUNDLE LINK FAIL IN

REMOTE UNIT
State
Major
The remote unit reports the reception of a packet with

Local Fail indication (L-bit set)
97
BUNDLE REMOTE FAIL

(RDI)
State
Major
The remote unit reports the reception of a packet with

Remote Fail indication (R-bit set)
98
BUNDLE RX TDMOIP
VERSION MISMATCH
State
Major
Mismatch between local and remote bundle TDMoIP

versions.
99
BUNDLE RX FRAME
LENGTH MISMATCH
State
Major
Packet discarded due to mismatch between received

Ethernet packet length and bundle configuration
100
BUNDLE SEQUENCE
Event
ERROR INSIDE WINDOW
Major
TDMoIP/MPLS packet sequence number error found within

the window
101
BUNDLE SEQUENCE
ERROR OUTSIDE
WINDOW
Event
Major
TDMoIP/MPLS packet sequence number error found

outside the tracking window
102
BUNDLE JITTER BUFFER

UNDERRUN
Event
Major
Underrun has occurred in the jitter buffer
103
BUNDLE JITTER BUFFER

OVERRUN
Event
Major
Overrun has occurred in the jitter buffer
7-66
Gmux-2000 Ver. 3.2
VC-E1/16, VC-E1/12 Alarms

Table 7-17. VC-E1/16, VC-E1/12 Alarms
Code Message
Type
Default
Interpretation
Severity
111
to
120
CH1: TDM ML OVERFLOW

to
CH10: TDM ML OVERFLOW
Event
Major
The corresponding external port subchannel reports an

overflow
121
CH1: Q.50 DISABLE NEW

CALLS
to
CH10: Q.50 DISABLE NEW
CALLS
Event
Major
The corresponding external port subchannel reports

that new calls are blocked, using the ITU-T Rec. Q.50
protocol, because of excessive traffic load
CH1: DISCARD VOICE

PACKETS
to
CH10: DISCARD VOICE
PACKETS
Event
Major
The corresponding external port subchannel reports

that the congestion prevention mechanism started
discarding voice packets because of excessive traffic
load
142
BUNDLE OUT OF SERVICE
Event
Major
The corresponding bundle is out-of-service
143
CH1: BLOCK VBD MODEM

CALLS
to
CH10: BLOCK VBD MODEM
CALLS
Event
Major
The corresponding local voice port reports that the

congestion prevention mechanism blocked new modem
calls
CH1: BLOCK RELAY MODEM Event

CALLS
to
CH10: BLOCK RELAY
MODEM CALLS
Major
The corresponding local voice port reports that the

relay calls
CH1: REMOTE BLOCK VBD

Event
MODEM CALLS
to
CH10: REMOTE BLOCK VBD
MODEM CALLS
Major
The corresponding remote voice port reports that the

calls
CH1: REMOTE BLOCK

RELAY MODEM CALLS
to
CH10: REMOTE BLOCK
RELAY MODEM CALLS
Event
Major
The corresponding remote voice port reports that the

relay calls
BUNDLES WITH DIFFERENT

CODER
Event
Major
The bundles must use the same coder type and rate
to
130
131
to
140
to
152
153
to
162
163
to
172
173
to
182
186
Gmux-2000 Ver. 3.2
7-67
Traps Generated by Gmux-2000

Gmux-2000 generates several types of traps that report special events. These
traps are presented in Table 7-18, together with a description of their formal
object identifier (OID) and attached parameters.
Note
Trap parameters appearing in bold font in Table 7-18 do not appear in the MIB
trap definition.
Table 7-18. Traps List
No.
Trap
Attached Parameters
Interpretation
General Traps
1
rfc1907.coldStart
Reports that the Gmux-2000 has been

powered up, and successfully completed
the cold-start process.
::= { snmpTraps 1 }
OID: 1.3.6.1.6.3.1.1.5.1
In response, a network management

station should perform all the operations
necessary to open the Gmux-2000
element manager application
rfc1907.warmStart
Reports that the Gmux-2000 has been

restarted (for example, by resetting the
CONTROL modules), and successfully
completed the warm-start process
::= { snmpTraps 2 }
OID: 1.3.6.1.6.3.1.1.5.2
3
rfc2863.linkUp
::= { snmpTraps 4 }
ifIndex, ifOperStatus,
openViewSeverity
OID: 1.3.6.1.6.3.1.1.5.4
Reports that the status (ifOperStatus) of

the corresponding link has changed from
down to any other value except
notPresent.
station should update the status color of
the port.
Only the minor and major
openViewSeverity values are used
(warning and critical are not used by
Gmux-2000)
rfc2863.linkDown
::= { snmpTraps 3 }
OID: 1.3.6.1.6.3.1.1.5.3
ifIndex, ifOperStatus,
openViewSeverity
Reports that the status of the

corresponding link (ifOperStatus) has
changed to down from any other value
except notPresent.
station should update the status color of
the port.
Gmux-2000)
7-68
Gmux-2000 Ver. 3.2

No.
Trap
rfc1907.authenticationFailure

Attached Parameters
Interpretation
Reports an SNMP authentication failure
(this is usually the result of an attempt
by a manager using an unauthorized
community to access Gmux-2000)
::= { snmpTraps 5 }
OID: 1.3.6.1.6.3.1.1.5.5
radGen Traps
6
rad.tftpStatusChangeTrap
tftpStatus
Reports a change in the status of the

TFTP protocol (used by the RADView map
application SWDL function)
agnIndication,
agnTestStatus,
openViewSeverity (same
value as agnIndication)
Indicates the Gmux-2000 alarm severity

associated with the reported trap or
event. Only the minor and major
Gmux-2000).
OID: 1.3.6.1.4.1.164.6.1.0.1
7
rad.agnStatusChangeTrap
OID: 1.3.6.1.4.1.164.6.1.0.2
Used by RADView HPOV map application

to provide the node status indication (for
example, select the node color on the
map)
8
cnfg.UpdateTrap
OID: 1.3.6.1.4.1.164.3.3.0.6
sysSSActiveCnfg,
sysSSActiveCnfg, mngIP
(of the manager that
initiated the Update
command)
Reports a Gmux-2000 configuration

update. The mngIP parameter is non-zero
only when the configuration update has
been initiated by an SNMP management
station
DACS Traps
10
rad.sanityCheckTrap
OID: 1.3.6.1.4.1.164.3.3.0.1
Gmux-2000 Ver. 3.2
sysSSanityCheckStatus,
sysDbDownloadCnfgIdxC
md,
mngIP (of the manager
that initiated the Update
command)
Provides information on sanity warnings

and errors detected by the Gmux-2000
sanity check function. The management
station that sent the update command
(which has its update flag set) should
open a pop-up message box after
receiving a setResponse for the update
command from the Gmux-2000. The
update flag should be reset after
receiving this trap, and also after the
time-out interval, if the trap is not
received within this interval
7-69

No.
11
Trap
rad.dacsMuxAlarmsTrap
OID 1.3.6.1.4.1.164.3.3.0.2
Attached Parameters
alrGenDescription,
sysBufferAlrCode,
sysBufferAlrSlot,
sysBufferAlrPort,
sysBufferAlrState,
openViewSeverity
Interpretation
Provides information on alarms detected
by the Gmux-2000. Only the minor and
major openViewSeverity values are used
Gmux-2000). The relevant parameters
depend on the alarm level:
For system level alarms, the following

parameters are not applicable (NA):
sysBufferAlrSlot, sysBufferAlrPort.
For card level alarms, the

sysBufferAlrPort parameter is not
applicable
IPmux Traps
12
bundleConnectionStatusTrap
::= {radSysWanEvents 15}
OID:
1.3.6.1.4.1.164.6.1.3.0.15
ifAlias (of the bundle),

ip2IfOperStatus,
openViewSeverity
Provides information needed to update

the bundle status, following any change
in the ip2IfOperStatus value.
Gmux-2000)
For your convenience, the RFC2863 definitions of ifOperStatus are presented

below:
7-70
up (1) If ifAdminStatus is changed to up(1), ifOperStatus will change to

up(1) if the interface is ready to transmit and receive network traffic.
down (2) If ifAdminStatus is down(2), ifOperStatus must be down(2).

If ifAdminStatus is changed to up(1), ifOperStatus should remain in the
down(2) state if and only if there is a fault that prevents it from going to the
up(1) state.
ifOperStatus will change from up(1) to down(2) if the interface cannot pass
packets to/from the network.
testing (3) A test is active on the interface.

The testing(3) state indicates that no operational packets can be passed.
unknown (4) Interface status cannot be determined.
dormant (5) If ifAdminStatus is changed to up(1), ifOperStatus should

change to dormant(5) if the interface is waiting for external actions (such as
a serial line waiting for an incoming connection).
notPresent (6) Some component is missing.

If ifAdminStatus is changed to up(1), ifOperStatus should remain in the
notPresent(6) state if the interface has missing (typically, hardware)
components.
lowerLayerDown (7) The interface is down due to the state of lower-layer

interface(s).
Gmux-2000 Ver. 3.2
7.5
Testing Gmux-2000 Operation
Overview
Diagnostics tests are available at the following levels:
Gmux-2000 Ver. 3.2
STM-1 port loopbacks. The loopbacks that can be activated on STM-1 ports
include:
Remote loopback: can be used to locate problems within the STM-1

processing sections of STM1 modules installed in the local Gmux-2000,
and in the connections between a local Gmux-2000 STM-1 port and the
users equipment connected to that port.
Local loopback: can be used for end-to-end testing of the STM-1 signal
paths from the local Gmux-2000 unit to the remote equipment, including
the link through the packet-switched network and the connections to the
remote STM-1 users equipment.
E1 internal ports located on pseudowire emulation server (E1-PW-SRV/21)

modules. The loopbacks that can be activated at this level include:
Remote loopback: can be used to locate problems along the internal

signal paths serving an E1 port within the STM1 and E1-PW-SRV/21
modules installed in the local Gmux-2000, and in the external signal paths
down to the local end users equipment connected to that E1 port.
Local loopback: can be used for end-to-end testing of the E1 signal paths
from the local Gmux-2000 unit to the remote equipment, including the
local packet processor serving that E1 port, the link through the packetswitched network and the connections to the remote end users
equipment connected to that E1 port.
E1 external ports located on pseudowire emulation modules with E1

interfaces (E1-PW/28) modules. The loopbacks that can be activated at this
level include:
Remote loopback: can be used to locate problems within the E1

processing sections of E1-PW/28 modules installed in the local
Gmux-2000, and in the connections between a local Gmux-2000 E1 port
and the users equipment connected to that port.
link through the packet-switched network and the connections to the
remote E1 users equipment.
Voice ports located on VC-E1/16, VC-E1/12 modules. The loopbacks that can
be activated at this level include:
Remote loopback: can be used to locate problems within the E1

processing sections of the module installed in the local Gmux-2000, and
in the connections between a local VC-E1/16, VC-E1/12 voice port and the
users equipment connected to that port.
7-71
link through the transmission network and the connections to the remote
users equipment.
Test tone injection toward the local equipment: can be used to check the
complete audio path from a timeslot of a VC-E1/16, VC-E1/12 voice port
toward the end user connected to that port.
Data ports located on VC-E1/16, VC-E1/12 modules. At this level, only the
remote loopback can be activated. This loopback can be used to check
end-to-end the signal paths from the local VC-E1/16, VC-E1/12 data port to
the remote equipment.
Ping for IP connectivity testing. Ping can be used to test the uplink
connections and confirm proper routing of bundles to the desired
destinations. In addition, you can also enable the trace route function, to
check the route taken by the pings.
The following sections describe the signal paths for each type of loopback.
Note
For convenience, all the examples shown below illustrate the signal paths when a
loopback is connected on port 1. The same loopbacks can however be activated
on any other port of the illustrated type, provided it is configured and connected.
Diagnostic Tests for SDH (STM-1) Ports

Remote STM-1 Port Loopback
The remote STM-1 port loopback returns the recovered STM-1 receive signal
provided by the STM-1 transceiver of the tested port toward the equipment
connected to the local STM-1 port. The loopback is activated at the line side of
the STM-1 framer serving the tested port.
Figure 7-45 shows the signal paths when a remote STM-1 port loopback is
activated.
Gmux-2000
STM1 Module
RX
STM-1
Transceiver
STM-1
Framer
TX
Packet
Processor
RX
STM-1
Transceiver
PSN
Interface
Subsystem
GbE
Uplink
STM-1
Framer
TX
Figure 7-45. Remote Loopback on External STM-1 Port

The test signal is provided by the equipment connected to the local STM-1 port,
that must receive its own transmission. While the loopback is activated, the local
STM-1 port continues sending the received payload to the Gmux-2000 transmit
path, for transmission through the packet network to the equipment at the
remote end of the link.
7-72
Gmux-2000 Ver. 3.2
This test checks the connections to the local STM-1 port, including the
transmission plant connecting the local equipment to the STM1 module, and the
STM-1 transceiver of the STM1 module.
Local STM-1 Port Loopback

The local STM-1 port loopback connects the STM-1 transmit signal generated by
the STM-1 framer of the tested port, to the receive input of the framer. This
returns the STM-1 signal toward the equipment at the remote end of the link.
Figure 7-46 shows the signal paths when a local STM-1 port loopback is
activated.
Gmux-2000
STM1 Module
RX
STM-1
Transceiver
TX
STM-1
Framer
Packet
Processor
RX
STM-1
Transceiver
PSN
Interface
Subsystem
GbE
Uplink
STM-1
Framer
TX
Figure 7-46. Local Loopback on External STM-1 Port

While the loopback is activated, the local STM-1 port continues sending the
transmit signal to the STM-1 line.
The test signal is provided by the remote equipment whose payload is routed to
the tested STM-1 port: that equipment must receive its own transmission.
This test fully checks the operation of the local STM-1 port, except for the STM-1
line interface (transceiver); it also checks the Gmux-2000 signal paths that end at
the corresponding STM-1 port, including the transmission through the packet
network connecting the remote equipment to the Gmux-2000.
E1 Port Diagnostic Functions for E1-PW-SRV/21 Modules

Remote Loopback on E1 Port (E1-PW-SRV/21 Module)
The signal paths during a remote loopback on an internal E1 port of an
E1-PW-SRV/21 module are shown in Figure 7-47.
As shown in Figure 7-47, when a remote loopback is activated on an internal E1
port, the E1 framer of that port returns the transmit signal via the receive path of
the same port. The transmit signal is received from the local end users
equipment served by the tested port, through the corresponding STM1 module
and the SDH mapper of the E1-PW-SRV/21 module.
While the loopback is activated, the signal received from the remote E1 port is
ignored. The signal received from the local users equipment remains connected
to the packet processor and it is transmitted to the remote PDH port.
To ensure that the users equipment is capable of providing a good signal, the
remote loopback should be activated on the Gmux-2000 port only after checking
Gmux-2000 Ver. 3.2
7-73
that the end users equipment operates normally while its own remote loopback
is activated.
In this case, if the status indicator of the tested port is off, then while the
remote loopback is activated on the local Gmux-2000 port, the end users
equipment must receive its own signal, and thus it must be frame-synchronized.
Gmux-2000
E1-PW-SRV/21 Module
E1
Framer
Packet
Processor
SDH
Mapper
PSN
Interface
Subsystem
GbE
Uplink
E1
Framer
Figure 7-47. Remote Loopback on E1 Port (E1-PW-SRV/21 Module), Signal Paths
Local Loopback on E1 Port (E1-PW-SRV/21 Module)

The signal paths during a local loopback on an internal E1 port of an
E1-PW-SRV/21 module are shown in Figure 7-48.
Gmux-2000
E1-PW-SRV/21 Module
E1
Framer
Packet
Processor
SDH
Mapper
PSN
Interface
Subsystem
GbE
Uplink
E1
Framer
Figure 7-48. Local Loopback on E1 Port (E1-PW-SRV/21 Module), Signal Paths

As shown in Figure 7-48, when a local loopback is activated on a local internal E1
port, the receive signal of the port is returned by the port framer to the input of
the port transmit path, and is returned toward the remote side through the port
packet processor, the remaining sections of the local Gmux-2000 transmit path
located on the E1-PW-SRV/21 and GbE modules, and the link through the
packet-switched network.
While the loopback is activated, the transmit signal arriving from the local end
users equipment is ignored.
7-74
Gmux-2000 Ver. 3.2
To ensure that the remote equipment is capable of providing a good signal, the
local loopback should be activated on the local Gmux-2000 port only after
checking that the remote end users equipment connected to the tested E1 port
operates normally while its own local loopback is activated.
With the local loopback is activated on the local Gmux-2000 port, the remote end
users equipment must receive its own signal, and thus it must be
frame-synchronized.
E1 Port Diagnostic Functions for E1-PW/28 Modules

Remote Loopback on External E1 Port (E1-PW/28 Module)
The signal paths during a remote loopback on an external E1 port of an E1-PW/28
module are shown in Figure 7-49.
As shown in Figure 7-49, the signal paths are similar to the signal paths described
in the Remote Loopback on E1 Port (E1-PW-SRV/21 Module) section, except that
the transmit signal is received from the line interface unit (LIU) of the tested port
(located on the E1-PW/28 module), not through any other Gmux-2000 module.
To ensure that the users equipment connected to the tested is capable of
providing a good signal, the remote loopback should be activated on the
E1-PW/28 port only after checking that the end users equipment operates
normally while its own remote loopback is activated.
In this case, if the status indicator of the tested port is off, then while the
remote loopback is activated on the local E1-PW/28 port, the end users
equipment must receive its own signal, and thus it must be frame-synchronized.
Gmux-2000
E1-PW/28 Module
RX
E1
Transceiver
E1
Framer
TX
Packet
Processor
RX
E1
Transceiver
PSN
Interface
Subsystem
GbE
Uplink
E1
Framer
TX
Figure 7-49. Remote Loopback on External E1 Port (E1-PW/28 Module), Signal

Paths
Local Loopback on External E1 Port (E1-PW/28 Module)

The signal paths during a local external E1 port loopback are shown in
Figure 7-50.
As shown in Figure 7-50, the signal paths are similar to the signal paths described
in the Local Loopback on E1 Port (E1-PW-SRV/21 Module) section, and therefore
the results are similar.
Gmux-2000 Ver. 3.2
7-75
Gmux-2000
E1-PW/28 Module
RX
E1
Transceiver
E1
Framer
TX
Packet
Processor
RX
E1
Transceiver
PSN
Interface
Subsystem
GbE
Uplink
E1
Framer
TX
Figure 7-50. Local Loopback on External E1 Port (E1-PW/28 Module), Signal Paths
VC-E1/16, VC-E1/12 Voice Port Diagnostic Functions

Remote Loopback on Voice Port
The remote voice port loopback returns the E1 receive signal of the tested port
toward the local equipment connected to the port.
The loopback is activated at the line side of the E1 framer of the tested port,
which receives the signal through the SDH mapper (for ports connected to the
SDH network), or the line interface unit (LIU) of the tested port.
When a remote loopback is activated on an external voice port, the E1 framer

of that port returns the receive signal towards the LIU, via the transmit path
of the same port. Figure 7-51 shows the signal paths when a remote
loopback is activated on an external voice port.
This test checks the connections to the local voice port, including the
transmission plant connecting the local users equipment to the VC-E1/16
voice port, and the E1 line interface of the VC-E1/16 voice port.
When the loopback is activated on a voice port connected to the SDH

network (that is, connected to an SDH port located on the STM1 module via
the Gmux-2000 telecom buses), the E1 framer returns the received signal to
the SDH mapper, via the transmit path of the same port. Figure 7-52 shows
the signal paths when a remote loopback is activated on a voice port
connected to the SDH network.
This test checks the transmission path to the local voice port, including the
SDH transmission plant, the STM1 module, the internal Gmux-2000 paths
connecting the users equipment to the local VC-E1/16 voice port, and the E1
framer of the VC-E1/16 voice port.
In both configurations, the test signal is provided by the equipment connected to

the local voice port, that must receive its own transmission. Note that as long as
the test is activated, that equipment cannot use loopback timing: it must use
either internal timing, or lock its timing to an external clock signal.
While the loopback is activated, the signal received from the remote voice port is
ignored. The signal received from the local users equipment remains connected
7-76
Gmux-2000 Ver. 3.2
to the DSP, which continues sending the received payload for transmission
through the network (E1 or SDH) to the equipment at the remote end of the link.
To ensure that the users equipment connected to the tested port is capable of
providing a good signal, the remote voice port loopback should be activated on
the local VC-E1/16 port only after checking that the end users equipment
Gmux-2000
VC-E1/16
TX
Port
LIU
Voice Port
Framer
RX
Voice
Compression
and
Timeslot
Cross
Connect
Network
Interface
Figure 7-51. Remote Loopback on External Voice Port
Gmux-2000
Telecom
Buses
STM1
Module
To SDH
Network
VC-E1/16
SDH
Mapper
Voice Port
Framer
STM1
Module
Voice
Compression
and
Timeslot
Cross
Connect
Network
Interface
Figure 7-52. Remote Loopback on Voice Port Connected to SDH Network
Local Loopback on Voice Port

The local voice port loopback returns the E1 signal restored from the compressed
voice stream received from the remote end (through the E1 or SDH network
connection), toward the equipment at the remote end of the link.
The loopback is activated at the digital side of the E1 framer of the tested port.
The E1 framer returns the signal restored by the receive path of the DSP serving
the port towards the DSP, via the transmit path of the same port.
Note
When the tested port receives multiple bundles, each bundles signal is
independently looped back.
Figure 7-53 shows the signal paths when a local loopback is activated on an
external voice port. This loopback fully checks the operation of the local
VC-E1/16 voice port, except for the E1 line interface (LIU); it also checks the
internal VC-E1/16 signal paths that end at the tested VC-E1/16 port, including
the transmission path through the network connecting the remote equipment
Gmux-2000 Ver. 3.2
7-77
to the local Gmux-2000, and the connections of the remote equipment to the
far end Gmux-2000.
Gmux-2000
VC-E1/16
TX
Port
LIU
RX
Voice Port
Framer
Voice
Compression
and
Timeslot
Cross
Connect
Network
Interface
Figure 7-53. Local Loopback on External Voice Port
When the local loopback is activated on a voice port connected to the SDH
network (that is, connected to an SDH port via the Gmux-2000 telecom
buses), the tested signal paths do not change. As shown in Figure 7-54, the
only difference is in the paths not included with the loopback.
This test checks the transmission path to the local voice port, including the
SDH transmission plant, the STM1 module, the internal Gmux-2000 paths
connecting the users equipment to the local VC-E1/16 voice port, and the E1
framer of the VC-E1/16 voice port.
Gmux-2000
Telecom
Buses
STM1
Module
VC-E1/16
To SDH
Network
SDH
Mapper
STM1
Module
Voice Port
Framer
Voice
Compression
and
Timeslot
Cross
Connect
Network
Interface
Figure 7-54. Local Loopback on Voice Port Connected to SDH Network

In both configurations, the test signal is provided by the equipment connected to
the remote end, that must receive its own transmission. Note that as long as the
test is activated, that equipment cannot use loopback timing: it must use either
internal timing, or lock its timing to an external clock signal.
While the local loopback is activated, the transmit signal arriving from the local
users equipment is ignored, but the local voice port continues sending the
received signal to the local equipment.
To ensure that the remote equipment is capable of providing a good signal, the
local loopback should be activated on the local VC-E1/16 voice port only after
checking that the remote end users equipment connected to the tested port
7-78
Gmux-2000 Ver. 3.2
With the local loopback is activated on the local VC-E1/16 port, the remote end
users equipment must receive its own signal, and thus it must be
frame-synchronized.
Test Tone Injection

The test tone is a data sequence repeating at a rate of approximately 1 kHz. This
data sequence is identical to the data sequence that would have been generated
if a signal at the test frequency, having a nominal level of 1 mW (0 dBm0), were
applied to the input of the DSP serving the voice port.
Figure 7-55 shows the signal paths.

The test tone can be injected in any desired timeslot of a voice port, toward any
desired local voice channel. When the local test tone injection is activated, the
data received from the remote end in the corresponding timeslot of the local
voice port is replaced by the test tone sequence. The resulting analog signal is
therefore supplied to the local subscriber. As a result, a 1-kHz tone should be
heard clearly and loudly in the earpiece of a telephone set connected to the
corresponding voice channel. Test equipment can also be used to measure the
test tone level; in this case, note that the nominal test tone level is changed in
accordance with the Volume to Line parameter selected for the tested timeslot.
The signal transmitted by the voice channel toward the other end remains
connected to the corresponding transmit timeslot.
At any given time, test tone injection can be activated in timeslots of only one
voice port of the VC-E1/16 module. The number of timeslots is not limited.
Gmux-2000
VC-E1/16
TX
Port
LIU
Voice Port
Framer
Voice
Compression
Timeslot
Cross
Connect
RX
Network
Interface
Test
~ Tone
Figure 7-55. Test Tone Injection Path
VC-E1/16, VC-E1/12 Data Port Diagnostic Functions

Remote Loopback on Data Port
The remote data port loopback returns the E1 receive signal of the tested port
toward the network, via the network connection terminated at the tested port.
The loopback is activated at the line side of the E1 framer of the tested port,
which receives the signal through the SDH mapper (for ports connected to the
SDH network), or the line interface unit (LIU) of the tested port.
Gmux-2000 Ver. 3.2
7-79
When a remote loopback is activated on an external data port, the E1 framer

of that port returns the receive signal towards the LIU, via the transmit path
loopback is activated on an external data port.
Gmux-2000
VC-E1/16
Voice
Port
Interface
Voice
Compression
and
Timeslot
Cross
Connect
Data Port
Framer
TX
Data Port
LIU
RX
Figure 7-56. Remote Loopback on External Data Port

This test checks the whole transmission path between any remote users
equipment that connects through the network to the local data port,
including the interconnecting transmission and switching plant; it also tests
the LIU of the VC-E1/16 data port.
When the loopback is activated on a data port connected to the SDH network
(that is, connected to an SDH port via the Gmux-2000 telecom buses), the E1
framer returns the received signal to the SDH mapper, via the transmit path
loopback is activated on a data port connected to the SDH network.
Gmux-2000
Telecom
Buses
VC-E1/16
Voice Port
Interface
STM1
Module
Voice
Compression
and
Timeslot
Cross
Connect
Data Port
Framer
To SDH
Network
SDH
Mapper
STM1
Module
Figure 7-57. Remote Loopback on Data Port Connected to SDH Network

This test checks the whole transmission path between any remote users
equipment that connects through the network to the local data port,
including the SDH transmission plant, the STM1 module, the internal
Gmux-2000 paths connecting the users equipment to the local VC-E1/16
data port, and the E1 framer of the VC-E1/16 data port.
In both configurations, the test signal is provided by the remote equipment
connected to the local VC-E1/16 through the tested data port: any such
equipment must receive its own transmission.
To ensure that the users equipment connected to the tested port is capable of
providing a good signal, the remote data port loopback should be activated on
7-80
Gmux-2000 Ver. 3.2
the local VC-E1/16 port only after checking that the remote users equipment,
and each equipment along the path, operates normally while its own local
loopback is activated, and all the equipment along the path.
Ping Function
The Gmux-2000 supports the ping function, part of the ICMP protocol. This
function enables checking IP connectivity between a Gmux-2000 IP port and the
desired remote IP host.
The user can select the destination IP address, specify a VLAN, configure the
number of ping packets sent, or enable continuous pinging. In addition, the user
can enable the trace route function, which collects information on the path
followed by the ping packets.
Make sure that the destination IP address is included in the addresses appearing
in the Managers List screen: if not, add a new manager with the required the
destination IP address (if necessary, temporarily delete an inactive manager until
you no longer need to ping that address).
Activating Diagnostic Functions

Overview of Diagnostics Menu Structure
The diagnostics functions described above are operated by means of the
Diagnostics menu. Figure 7-58 shows the structure of the Diagnostics menu.
Diagnostics
Self Test Results
1. Ping
2. Loop Back
3. APS Commands
Ping
Ping
2. VLAN Tagging (No)
3. Ping Repetitions
4. Trace Route
5. Send Ping
or
2. VLAN Tagging (Yes)
3. VLAN ID
4. VLAN Priority
5. Ping Repetitions
6. Trace Route
7. Send Ping
STM1
E1-PW/28, E1-PW-SRV/21
VC-E1/16, VC-E1/12
Loop Back
Loop Back
Loop Back
1. Slot Number
2. STM-1 Port
STM-1 Port
1. STM-1 Port
2. Local Loopback
3. Remote Loopback
or
1. Slot Number
2. E1 Port
or
1. Slot Number
2. E1 Port Voice
3. E1 Port Data
E1 Port Voice
E1 Port
1. E1 Port
2. Local Loopback
3. Remote Loopback
4. Inject Tone (select TS)
5. Inject Tone Test
1. E1 Port
2. Local Loopback
3. Remote Loopback
E1 Port Data
APS Commands
1. APS ID
2. Interface
3. Command
4. Activate Command
1. E1 Port
2. Remote Loopback
Command
1. Normal Operation
2. Force Flip
Figure 7-58. Diagnostics Menu Structure

Gmux-2000 Ver. 3.2
7-81
Selecting a Diagnostics Task

To select the type of diagnostic activity to be performed, and read the results of
the last power-up self-test, use the Diagnostics task selection screen.
Note
When you open the Diagnostics menu, you can see in the top line the results of
the last power up self-test.
A typical Diagnostics task selection screen is shown in Figure 7-59.
Pseudowire Gateway
Diagnostics
Self test results
1. Ping
2. Loop back
3. Aps commands
... (Ok)
>
>
>
>
tests/loops, ping operations
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-59. Typical Diagnostics Task Selection Screen
To select a diagnostic task:

Type the corresponding item number and then press <Enter>.
Performing Ping (IP Connectivity) Checks

Use Diagnostics>Ping to test IP connectivity from the Gmux-2000 to a desired IP
destination.
Note
You must include in the manager list the IP addresses to which you want to send
pings. If not, you will get an IP address should be defined in the manager list!
message.
For a description of the ping function, refer to Appendix C.
A typical Ping screen, as seen when VLAN tagging is enabled, is shown in
Figure 7-60. The parameters appearing on the screen are explained in Table 7-19.
7-82
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Diagnostics>Ping
1.
2.
3.
4.
5.
...
VLAN tagging
VLAN ID[0 - 4095]
VLAN priority[0 - 7]
Ping repetitions
(N)
... (2.3.4.19)
(Yes)
... (12)
... (7)
>
(10)
>

1 M/ 1 C
-----------------------------------------------------------------------------
A. First Page
Pseudowire Gateway
Diagnostics>Ping
... (P)
6. Trace route
7. Send ping
>
(Yes)
>

1 M/ 1 C
-----------------------------------------------------------------------------
B. Second Page
Figure 7-60. Typical Ping Parameters Screen
Table 7-19. Ping Parameters
Parameter
Function
Values
Destination IP
Address
Specifies the IP address to which pings

are sent

periods).
Default: 0.0.0.0
VLAN Tagging
Controls the use of VLAN tagging for the

ping frames
YES VLAN tagging is enabled. When you

select YES, the screen changes to include
the VLAN ID field.
NO VLAN tagging is disabled.
Default: NO
Gmux-2000 Ver. 3.2
7-83
Parameter
Function
Values
VLAN ID

the default VLAN ID number used by the
ping frames.
The allowed range is 1 to 4095. 0 means

that no VLAN ID has been specified.
Default: 0

VLAN Priority

the priority assigned to the ping frames.
The allowed range is 7 (highest priority) to

0 (lowest priority).

Default: 0
Ping Repetitions
Select the number of pings to be sent
The available selections, displayed on a

separate selection screen, are 1, 2, 3, 4 or
Endless Repetitions (that is, pings are sent
until the test is stopped)
Trace Route
Enables/disables the trace route function
NO Trace route function disabled.

YES Trace route function enabled.
Default: NO
To perform pinging:
5. Configure the pinging parameters in accordance with Table 7-19.
6. When ready, select Send Ping.
7. You are notified that pings are sent, and a rotating indicator appears as long
as the pings are being sent. In addition, when Trace Route is enabled, you will
see in the prompt area the list of replies from intermediate nodes detected
by the trace route function, as shown in Figure 7-61. Each reply indicates the
IP address of the replying node, and the round-trip time for the
corresponding reply.
7-84
Gmux-2000 Ver. 3.2
PseudoWire Gateway
Diagnostics>Ping
1.
Ping repetitions
Trace route
Stop ping
... (172.17.170.22)
>
(Endless repeats)
>
(Yes)
>

1 M/ 1 C
----------------------------------------------------------------------------Reply from 172.17.171.1 T=0.020 sec.
Reply from 172.17.132.3 T=0.010 sec.
Reply from 172.17.170.22 T=0.020 sec.
Figure 7-61. Typical Ping Results Screen

8. If Endless Repetitions has been selected, stop the test.
9. Read the test results. The results are explained in Table 7-20.
Table 7-20. Ping Results

Parameter
Description
Packets Sent
Shows the total number of pings sent. The number advances until all the
pings are sent, or until the specified time-out interval expires.
Packets Received
Displays the number of ping responses received before the time-out

interval expires.
Packets Lost
After all the pings have been sent or the specified time-out interval
expires, displays the number of unanswered ping requests.
Success
Displays the percentage of successfully received ping responses, relative

to the total number sent.
Min Round Trip Time (ms)
Displays the minimum measured time between the transmission and

reception of a ping, in milliseconds.
Max Round Trip Time (ms)
Displays the minimum measured time between the transmission and

reception of a ping, in milliseconds.
Average Round Trip Time (ms)
Displays the average time calculated for all the successfully received ping
responses, in milliseconds.
Performing Loopback Tests

Use Diagnostics>Loop Back to perform loopbacks on the desired ports. The
available tests and loopbacks depend on the specific module and port.
A typical Loop Back target selection screen is shown in Figure 7-62.
Gmux-2000 Ver. 3.2
7-85
Pseudowire Gateway
Diagnostics>Loop back
1. Slot number[1 - 9]
2. E1 port
... (3)
>
>
F next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-62. Typical Loop Back Screen
To activate a loopback:
1. Select Slot number and then type the number of the desired I/O slot, 1 to 9,
or
Use the F or B key to sequentially display I/O slots in the Slot number field.
2.
The type of ports on the I/O module installed in the corresponding slot is
automatically updated in the second item.
3. Select E1 port to display the loopback selection screen for the selected slot.
A typical Loop Back screen for E1 ports is shown in Figure 7-63, and a typical
Loop Back screen for STM-1 ports is shown in Figure 7-64.
4. To toggle the state of a loopback, type the number corresponding to the
desired type and then press <Enter>. The new state is displayed next to the
name of the loopback.
7-86
Gmux-2000 Ver. 3.2
Pseudowire Gateway
Diagnostics>Loop back>E1 port
1. E1 port[1 - 21]
2. Local Loop back
3. Remote Loop back
... (1)
(Off)
(Off)
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-63. Typical Loop Back Selection Screen for E1 Ports

Pseudowire Gateway
Diagnostics>Loop back>STM-1 port
1. STM-1 port[1 - 2]
2. Local Loop back
3. Remote Loop back
... (1)
(Off)
(Off)
>
F - next; B - prev
1 M/ 1 C
-----------------------------------------------------------------------------
Figure 7-64. Typical Loop Back Selection Screen for STM-1 Ports
7.6
Frequently Asked Questions
Q. How do I manage remote Vmux-2100 inband over TDM link between a central
Gmux-2000 and a remote Vmux-2100?
Gmux-2000 Ver. 3.2
7-87
Management Station
Packet
Switched
Network
IP Address: 20.20.20.120
GbE Port IP Address:
20.20.20.20
GbE Link
TDM Link
Gmux-2000 with
Online CL IP Address:
10.10.10.10
TDM
Network
E1
Vmux-2100
IP Address:
10.10.10.100
Default Gateway : 10.10.10.10
Figure 7-65. Inband Management of Vmux-2100

1. Check that the Gmux-2000 is running the following software versions (or
higher):
CONTROL module: 2.10N19
VC-E1/16 or VC-E1/12 module: 1.00A7
GbE module: 1.20F1
2. Connect the management station to the GbE module (directly to the

MONITOR port, or through a PSN to the GbE port 1 or port 2 as shown in
Figure 7-65) on the central Gmux-2000.
3. Make sure that the Gmux-2000 CONTROL module IP address and the host
IP address assigned to the remote Vmux-2100 units are in the same IP
subnet.
Example:
Gmux-2000 CONTROL module IP address = 10.10.10.10
Remote Vmux-2100 host IP = 10.10.10.100
Default gateway of remote Vmux-2100 (must be Gmux-2000

CONTROL module IP address) = 10.10.10.10
4. Add the IP address of the management station (20.20.20.120) to the

Vmux-2100 Manager List.
5. Make sure that GbE module in Gmux-2000 and the network card of
manager management station should have IP addresses from the same IP
subnet, but that subnet is different from that used by the Gmux-2000
CONTROL module.
Example:
7-88
Gmux-2000 Ver. 3.2
GbE module = 20.20.20.20
Management station network card IP address = 20.20.20.120
6. Make sure that the Manager List of the Gmux-2000 includes the IP
address of the local management station and its exit interface, and the
remote Vmux-2100 host IP and its exit interface.
Example:
20.20.20.120 (this is the IP address of the management station), exit

interface = GbE port 6/1 (or port 8/1 if the GbE module is inserted in
slot 8)
10.10.10.100 (this is the host IP address of the remote Vmux-2100),
exit interface = VMX slot 1
7. Make sure that the Manager List of the Vmux-2100 includes the IP
address of the management station = 20.20.20.120.
8. Configure the management station default gateway as the IP address of
the central Gmux-2000 GbE module (20.20.20.20)
Now, when the management station looks for the IP address of the
Gmux-2000 CONTROL module, 10.10.10.10, or for the host IP address of
the remote Vmux-2100, 10.10.10.100, it will use the Gmux-2000 GbE
module (20.20.20.20).
9. Use Telnet to contact the local Gmux-2000 (10.10.10.10) or the remote
Vmux-2100 (20.20.20.120) from the management station, and verify that
you have access to configuration menus.
Q. What is the difference between Bundle ID and Destination/Source CBID
parameters used for Gmux-2000 connection configuration?
A. The Bundle ID is an internal administrative number used as a bundle name
within the Gmux-2000 database. This number will not appear in the TDMoIP
packets sent to the PSN.
The destination CBID (Circuit Bundle Identifier) is the destination bundle
number at the far end TDMoIP device. This number will be used by the
Gmux-2000 to send the TDMoIP stream to the far end TDMoIP device, and it
will appear in the Source Port field of the UDP header of the packets sent by
the Gmux-2000.
The Source CBID is the source bundle number at the local Gmux-2000. This
number will be used by the far end TDMoIP device to send the TDMoIP stream
to the Gmux-2000, and it appears in the Source Port field of the UDP header
of packets sent to the Gmux-2000.
The CBID will also be used within the payload of OAM packets, to validate the
TDMoIP connection.
Q. How does the Gmux-2000 power supply redundancy mechanism function?
A. Gmux-2000 can be equipped with up to 3 PS modules (either AC or DC). The
number of power supplies required depends on the Gmux-2000 card
configuration and capacity. Some configurations require 1 PS module, others
may require 2 PS modules. Therefore, when only 1 PS module is required, the
second serves as backup.
Gmux-2000 Ver. 3.2
7-89
When 2 PS modules are operating, they will operate together in loadsharing mode.
If one PS module fails, the remaining PS module can feed the whole
Gmux-2000.
For an AC powered Gmux-2000, each power inlet (PI) is connected to a

separate PS module (one-to-one). In case of a power source failure in one PI,
the first PS module is deactivated, but the second PI feeds the second PS
module and through it the whole Gmux-2000.
For the DC option, each PI is connected to all the power supply modules (allto-all). In case of a power source failure on one PI, the second PI will feed the
whole Gmux-2000 via all the power supply modules.
In the same way, when 2 PS modules are required and 3 modules are
installed, the third module serves as backup.
Q. How do I connect an E1 or T1 interface to the Gmux-2000 pseudowire
emulation module with external E1 or T1 interfaces?
A. Gmux-2000 pseudowire emulation module with external E1 or T1 interfaces
uses a 62-pin D-type connector.
To connect it to the Cat. 5 RJ-45 balanced E1 or T1 interfaces, order the
following patch panel: GMUX-PPANEL/RJ45/28. The patch panel supports
28 E1 or T1 ports.
The connector on the patch panel is a Telco connector. When ordering the
patch panel, it comes with an adapter cable from the 62-pin D-type
connector on the Gmux-2000 side to a Telco connector.
Q. Can ISDN PRA interface traffic be transmitted over the PSN using the
IPmux/Gmux-2000 units?
A. Transferring ISDN PRA interface traffic over the IP network using
IPmux/Gmux-2000 is possible only in a point-to-point application, as the
Gmux-2000 will handle the traffic as data, and will transfer it with the
associated signaling. However, this it is not possible when the application is
point-to-multipoint, i.e., when the Gmux-2000 must split the ISDN PRA
stream, then.
Q. What V5 byte code will cause the Gmux-2000 to issue a Signal Label Mismatch
alarm on the VC-12 level?
A. Gmux-2000 expects to receive the code 010 (async) on the V5 byte of the
VC-12 signal label. Any other value will cause a Signal Label Mismatch alarm
and AIS transmission on the VC-12 level.
Note
The validation of the Signal Label by the Gmux-2000 can be disabled via the
configuration menus.
Q. What is the difference between the Gmux-2000 Alarm Status and Event Log
screens?
A. Alarm Status is displayed under Monitoring>Alarms>Dsp All Alarms. It contains
all the alarms (along with a brief description) that happened until the last
device reset or the last Clear Log command. The alarm status is displayed as a
table with the alarm number at the left, followed by the alarm source (slot,
7-90
Gmux-2000 Ver. 3.2
port or bundle), description, status of the alarm, the number of times the
alarm occurred, and an indicator for special conditions.
Event Log is displayed under Monitoring>Event log>Read Log File. It contains
more information than the alarm status, because each alarm has its own
entry. Gmux-2000 can hold up to 256 entries in the log file, where each entry
represent an alarm. The event log is cyclic, meaning after 256 alarms, the old
ones are overwritten and the alarm ALARM BUFFER OVERFLOW is added (only
once). Each entry (alarm) contains the following information: alarm number,
alarm module (I/O number or bundle), port number, description, status
(Event, Off, Critical, Major, Minor or Warning), timestamp and date.
Q. How many different configuration databases can the Gmux-2000 hold?
A. Up to 5 different databases are supported. Switching between databases is
done on the fly, without the need for device reset.
Q. I want to order a Gmux-2000 with an STM-1/OC3 module. Which modules
should I order for the network and user side?
A. For the network side you should order a GbE module. For the user side you
should order:
For STM-1: one STM-1 module and E1 pseudowire emulation server

modules, where each server module will allow you to deploy 21 E1
streams out of the STM-1 payload. For a full STM-1 you need to order 3
pseudowire emulation server modules.
For OC-3: one OC-3 module and T1 pseudowire emulation server

modules, where each server module will allow you to deploy 28 T1
streams out of the OC-3 payload.
For a full OC-3, you need to order 3 pseudowire emulation server
modules.
Q. What is the input range of the DC power supply for Gmux-2000?

A. The input range of the DC power supply is 36 to 72 VDC.
Q. How many simultaneous Telnet/SSH sessions does Gmux-2000 support?
A. One.
7.7
Technical Support
Technical support for this product can be obtained from the local distributor from
whom it was purchased.
For further information, please contact the RAD distributor nearest you or one of
RAD's offices worldwide. This information can be found at www.rad.com (offices
About RAD > Worldwide Offices; distributors Where to Buy > End Users).
Gmux-2000 Ver. 3.2
Technical Support
7-91
7-92
Technical Support
Gmux-2000 Ver. 3.2
Appendix A
Connection Data
A.1
CONTROL DCE Connector
Connector Data
The CONTROL DCE connector is a 9-pin D-type female connector with RS-232
asynchronous DCE interface, intended for direct connection to a supervision
terminal. The connector is wired in accordance with Table A-1.
Table A-1. CONTROL DCE Connector Wiring

Pin
Function
Direction
Data Carrier Detect (DCD)
From Gmux-2000
Receive Data (RD)
From Gmux-2000
Transmit Data (TD)
To Gmux-2000
Data Terminal Ready (DTR)
To Gmux-2000
Signal Ground (SIG)
Common reference and DC power

supply ground
Data Set Ready (DSR)
From Gmux-2000
Request to Send (RTS)
To Gmux-2000
Clear to Send (CTS)
From Gmux-2000
Ring Indicator (RI)
To Gmux-2000
Connection Data
The connections to the CONTROL DCE connector are made as follows:
Connection to supervision terminal with 9-pin connector: by means of a

straight cable (a cable wired point-to-point).
Connection to supervision terminal with 25-pin connector: by means of a

cable wired in accordance with Figure A-1.
Connection to modem with 25-pin connector (for communication with

remote supervision terminal): by means of a cable wired in accordance with
Figure A-1
Gmux-2000 Ver. 3.2
A-1
Appendix A Connection Data
Connection to modem with 9-pin connector (for communication with remote

supervision terminal): by means of a crossed cable wired in accordance with
Figure A-2.
9 Pin
Connector
To
Gmux-2000
CONTROL DCE
Connector
25 Pin
Connector
TD
RD
RTS
CTS
DSR
DCD
RI
22
DTR
20
GND
Gmux-2000
Side
To Terminal
Terminal Side
Figure A-1. 25-Pin Terminal Cable Wiring - Connection to CONTROL DCE

Connector
9-Pin
Connector
To
Gmux-2000
CONTROL DCE
Connector
TD
RD
RTS
CTS
DSR
DCD
RI
DTR
GND
Gmux-2000
Side
9-Pin
Connector
To Modem
Modem Side
Figure A-2. 9-Pin Crossed Cable Wiring - Connection to CONTROL DCE Connector
A-2
Gmux-2000 Ver. 3.2
A.2
CONTROL ETH Connector
Connector Data
Each Gmux-2000 CONTROL ETH port has a 10/100BASE-TX Ethernet hub interface
terminated in an RJ-45 connector. The port supports the MDI/MDIX crossover
function, and therefore it can be connected by any type of cable (straight or
crossed) to any type of 10/100BASE-TX Ethernet port. The ports also correct for
polarity reversal in the 10BASE-T mode.
Connector pin functions for the MDI state are listed in Table A-2. In the MDIX
state, the receive and transmit pairs are interchanged.
Table A-2. CONTROL-ETH Interface Connector, Pin Functions

Pin
Designation
Function
RxD+
Receive Data output, + wire
RxD
Receive Data output, wire
TxD+
Transmit Data input, + wire
4, 5
TxD
7, 8
Not connected
Transmit Data input, wire
Not connected
Connection Data
Use a standard station cable to connect the CONTROL ETH connector to any type
of 10/100BASE-TX Ethernet port.
Gmux-2000 Ver. 3.2
CONTROL ETH Connector
A-3
A.3
ALARMS Connector
The ALARMS connector is a 9-pin D-type female connector which provides

connections to the following functions:
Major and minor alarm relay contacts
+12V auxiliary supply voltage output (through 340 series resistor and
protection diode) for the external alarm sense circuit
External alarm sense input (to be connected to the +12V auxiliary supply
voltage by external dry contacts).
Connector pin functions are listed in Table A-3.
Caution To prevent damage to alarm relay contacts, it is necessary to limit, by external

means, the maximum current that may flow through the contacts (maximum
allowed current through closed contacts is 1 A; load switching capacity is 60 W).
The maximum voltage across the open contacts must not exceed 60 VDC/30 VAC.
Table A-3. ALARMS Connector Wiring

Pin
A-4
Function
Minor alarm relay normally-open (NO) contact
Minor alarm relay normally-closed (NC) contact
External alarm input IN1
Major alarm relay normally-open (NO) contact
Major alarm relay normally- closed (NC) contact
Minor alarm relay center contact
Reserved
+12V auxiliary output (through 340 series resistor and protection diode)
Major alarm relay center contact
ALARMS Connector
Gmux-2000 Ver. 3.2
A.4
STATION CLOCK Connectors
Connector Data
The STATION CLOCK port has three connectors:
One RJ-45 eight-pin connector, for the balanced interface. Connector wiring is
listed in Table A-4.
Two BNC female coaxial connectors, designated IN (station clock input) and
OUT (nodal clock output), respectively, for the unbalanced interface.
Table A-4. STATION CLOCK Connector, Pin Functions

Pin
Direction
Function
Input
AMI Clock In (ring)/Square Clock Signal In (wire +) (NOTE)
Input
AMI Clock In (tip)/Square Clock Signal In (wire ) (NOTE)
Signal Ground (connection controlled by internal jumper)
Output
AMI Clock Out (ring)/Square Clock Signal Out (wire +) (NOTE)
Output
AMI Clock Out (tip)/Square Clock Signal Out (wire -) (NOTE)
Frame Ground (connection controlled by internal jumper)
Not connected
Not connected
Note
The type of clock signals (AMI per ITU-T Rec. G.703 or RS-485 squarewave)
accepted and generated by these interfaces is selected by software.
Connection Data
You can connect either to the RJ-45 connector or to the coaxial connectors, in
accordance with the station clock interface type selected by means of the
internal settings. Never connect cables to both interfaces.
When connecting cables to the coaxial connectors, pay attention to correct
connection:
Gmux-2000 Ver. 3.2
Connect the clock input cable to the IN connector
Connect the clock output cable to the OUT connector.
STATION CLOCK Connectors
A-5
A.5
Power Connectors
AC Power Connector
AC-powered Gmux-2000 units have three standard IEC three-pin sockets, one for
each AC power supply unit.
DC Power Connector
DC-powered Gmux-2000 units have two three-pin DC power connectors for
connecting two VDC power sources to the DC power supply units.
Each DC supply voltage is separately connected to each DC power supply unit.
Connector wiring is listed in Table A-5, together with a view of the connector
itself.
Table A-5. DC Connector Pin Functions

Pin
A-6
Power Connectors
Function
Positive DC input line
Chassis (frame) ground
Negative DC input line
Gmux-2000 Ver. 3.2
Appendix B
Installing New Software
Releases
B.1
Scope
This Appendix presents procedures for downloading software to the Gmux-2000.

The procedures appearing in this Appendix can be used to:
1. Update the Gmux-2000 software when a new release becomes available.
2. Download again the software in case the stored software has been
corrupted.
3. Download software to a new or repaired CONTROL module.
Overview of Downloading Options

Using the File Utilities Menu
The recommended software downloading method, explained in Section B.2, is
downloading by means of the TFTP protocol, using the File Utilities menu reached
from the main menu.
Network administrators can use this procedure to distribute new software
releases to all the managed Gmux-2000 units in the network from a central
location.
When downloading by TFTP, the new software is always downloaded into the
on-line CONTROL module, and is stored on its flash disk.
If the on-line CONTROL module software has been changed, then after software
decompression is completed, the on-line CONTROL module must be reset by a
users command. Resetting the on-line CONTROL module has two effects:
The new software is activated
The other CONTROL module (which currently stores the previous software
version) is switched on-line.
Therefore, after receiving the messages which indicate flipping (switching) to the
other CONTROL module, repeat the downloading procedure: this time the new
software will be downloaded into the other module. Following the resetting of
the second CONTROL module at the end of software downloading, the original
CONTROL module returns on-line.
Gmux-2000 Ver. 3.2
Scope
B-1
Appendix B Installing New Software Releases
If the software of the CONTROL module has not been changed, it is necessary to
manually reset the currently on-line module.
Using the Boot Menu

Software downloading may also be performed using the boot menu, as explained
in Section B.3. The boot menu can be reached while Gmux-2000 performs
initialization, for example, after power-up.
You may need to start the loading from the boot menu when it is not possible to
activate TFTP from the File Utilities menu (for example, because the Gmux-2000
software has not yet been downloaded or is corrupted). Note however that the
boot menu procedures are recommended only for use by authorized personnel,
because this menu provides many additional options that are intended for use
only by technical support personnel.
Two software downloading options are available from the boot menu:
Downloading using the Xmodem protocol. This is usually performed by

downloading from a PC directly connected to the CONTROL DCE port of the
CONTROL module.
Downloading using the TFTP protocol. This is usually performed by

downloading from a host connected to the CONTROL ETH port of the
CONTROL module, or from a remote location that provides an IP
communication path to this Gmux-2000 port.
When downloading from the boot menu, you connect only to one CONTROL
module (the module to be loaded). Therefore, when updating the software to a
new release, always repeat the process for the second module.
Note
B-2
Scope
screens are given for illustration purposes only, and do not reflect recommended
values.
Gmux-2000 Ver. 3.2
B.2
Software Updating Using File Utilities Menu
Preparations for Using TFTP

The following conditions must be fulfilled before the TFTP protocol can be used
for software downloading:
1. The required suite of protocols (which includes as a minimum the TCP/IP stack
and the TFTP server and client software) must be installed on the other
computer (the computer used to download files and/or accept uploaded
files).
2. The Gmux-2000 must be assigned IP parameters for its management entity
(that is, IP address, the associated subnet mask and a default gateway IP
address for the online CONTROL module) using the Configuration>System>
Management>Host IP screen.
3. The management access options must be properly configured.
4. You must obtain the IP address of the other computer.
5. The TFTP protocol runs over IP, therefore it is necessary to ensure IP
connectivity between the Gmux-2000 and the other computer. For example:
Note
The Ethernet port of the other computer may be directly connected to

one of the Gmux-2000 CONTROL ETH ports. In this case, their IP
addresses must be in the same subnet.
The CONTROL ETH port and the other computer may be attached to the
same LAN. In this case, their IP addresses must be in the same subnet.
The Gmux-2000 and the other computer may be attached to

interconnected LANs (the connection may also be provided via an uplink
port).
IP connectivity can be checked using standard tools such as ping.

6. If you intend to initiate TFTP transfer using a supervisory terminal connected
to the Gmux-2000 CONTROL DCE connector, make sure the Gmux-2000
supervisory port is properly configured. This is performed by means of the
Configuration>System>Serial Port screen.
Alternatively, you may use a Telnet host that can communicate with the
Gmux-2000 either through the CONTROL ETH ports, or through the one of
the uplink ports.
Software Updating Procedure

The following procedure is separately performed on each CONTROL module,
starting with the on-line module. On each module, first you download the
software, and then you activate it.
Gmux-2000 Ver. 3.2
B-3
Before starting:
1. Obtain the list of distribution files to be downloaded, and check that the
required distribution files are stored on the TFTP server. Valid files have the
extension .IMG.
2. Make sure that the TFTP server can communicate with the Gmux-2000, for
example, by sending pings to the IP address assigned to the Gmux-2000
management entity.
To download the software:

1. Open the Utilities menu, and select File Utilities.
Pseudowire Gateway
3. Internal upload
>
>
>
>

1 M/ 1 C
----------------------------------------------------------------------------2. Select Download/upload by TFTP and then press <Enter> to open the
Download/Upload by TFTP screen.
Pseudowire Gateway
Utilities>File utilities>Download/upload by TFTP
1.
2.
3.
4.
5.
6.
Client file name

Server file name
TFTP server IP
TFTP retry timeout
TFTP total timeout
Activate TFTP
...
...
...
...
...
>
()
()
(0.0.0.0)
(0)
(0)
>
% - UPD DB
1 M/ 1 C
-----------------------------------------------------------------------------
B-4
Gmux-2000 Ver. 3.2
3. Define the parameters needed for the TFTP transfer:
Note
Select Client file name and then press <Enter>. Enter the name of the
software file (usually GMUXCL.IMG) as used for the Gmux-2000 CONTROL
module. When done, press <Enter> to continue.
Select Server file name and then press <Enter>. Enter the name of the
desired software distribution file as used on the TFTP server (make sure
to include the path, when necessary). When done, press <Enter> to
continue.
Select TFTP server IP and then press <Enter>. Enter the IP address of the
server that will download the software distribution file (use the dotted
quad format), and then <Enter> to continue.
Select TFTP retry timeout and then press <Enter>. Enter the desired retry
time-out interval, in seconds, for example, 10, and then press <Enter>.
Select TFTP total timeout and then press <Enter>. Enter the desired total
time-out interval, in seconds, for example, 30, and then press <Enter>.
The retry time-out internal specifies the time to wait for connecting to the server
and completing the handshake necessary to start the transfer. After this interval
expires, the CONTROL module will try again, and so on, until the transfer can be
started, or the total time-out interval expires: in this case, the downloading fails.
4. When ready, type % to update the configuration database.
5. Now select the desired operation: select Activate TFTP and then press
<Enter>. You will see the Activate TFTP screen.
Pseudowire Gateway
Utilities>File utilities>Download/upload by TFTP>Activate TFTP
1. File download
2. File upload
>

1 M/ 1 C
----------------------------------------------------------------------------6. Select the desired operation by typing its number. The available selections are
as follows:
Gmux-2000 Ver. 3.2
File Download
Download the specified file from the TFTP server to the

Gmux-2000. This is the selection needed to update or
install new software on the Gmux-2000.
File Upload
Upload a specified software file stored in Gmux-2000 to

the specified TFTP server.
B-5
7. When ready to start the transfer, press <Enter>.

9. After the transfer is successfully completed, the online Gmux-2000 CONTROL
module stores the file on its flash disk.
Note

To activate the new software:
1. Open the Utilities menu, and select File Utilities.
Pseudowire Gateway
3. Internal upload
>
>
>
>

1 M/ 1 C
----------------------------------------------------------------------------2. Select Internal download to open the Internal Download screen.
Pseudowire Gateway
1. CL
2. I/O[1 - 9]
... (0)
>

1 M/ 1 C
----------------------------------------------------------------------------3. Select CL to download software to the CONTROL module.
4. Now select Slot's files, select the file with the proper version, and then press
<Enter> to confirm and return to the Internal Download screen.
B-6
Gmux-2000 Ver. 3.2
Pseudowire Gateway
1. CL
2. Slot's files
3. Start Sw load
>
(GMUXCL.IMG)
>
software download
1 M/ 1 C
----------------------------------------------------------------------------5. When ready, select Start Sw load.
6. Wait for downloading to complete. When successfully completed, you will see
Flash programming succeeded. Perform RESET to run new application.
7. To activate the new software, reset the CONTROL module as follows:
Return to the Utilities menu.
Select Reset.
Select Reset CL to send the reset command.
8. After the resetting is successfully completed, you will see the Gmux-2000
log-in screen.
Note
If after downloading a new software version you cannot establish again

communication with the Gmux-2000, you must initialize the database, using
section 2 (DB INIT) of the internal switch SW2 of the active CONTROL module.
See detailed procedure in Chapter 3.
9. Repeat the transfer to download the file to the other CONTROL module.
Gmux-2000 Ver. 3.2
B-7
B.3
Note
Software Downloading From the Boot

Menuboot menuXmodem
All the screens shown in this section are given for illustration purposes only: your
Gmux-2000 may display different software versions.
Software Downloading Procedure Using Xmodem Protocol

Before starting, copy the prescribed software file to the PC disk.
Preparations for Using Xmodem Protocol

1. Connect the serial RS-232 communication port of a PC running a terminal
emulation program (for example, the HyperTerminal utility available with most
Microsoft Inc. Windows releases) to the CONTROL DCE connector of the
desired Gmux-2000 CONTROL module. Select the emulated terminal type as
VT-100.
2. Configure the communication parameters of the selected serial port for
asynchronous communication for 115.2 kbps, no parity, one start bit, eight
data bits and one stop bit. Turn all types of flow control off.
3. If the Gmux-2000 operates, disconnect its power.
Procedure
1. Start the terminal emulation program in accordance with the configuration
parameters described above.
2. When ready, connect the power to the Gmux-2000, and immediately start
pressing the <Enter> key several times in sequence until you see the boot
manager screen. A typical screen is shown below (the exact version and date
displayed by your Gmux-2000 may be different).
Note
B-8
If you miss the timing, the Gmux-2000 will perform a regular reboot process (this
process starts with Loading and ends with a message to press <Enter> a few
times to display the log in screen).
Software Downloading From the Boot Menuboot menuXmodem
Gmux-2000 Ver. 3.2
GMUX_CL Boot Version 1.50 (Oct 26 2004)

Boot Manager Version 6.07 (Oct 16 2004)
0 - Exit Boot-Manager
1 - Dir
2 - Set Active Software Copy
3 - Delete Software Copy
4 - Download Files or an Application by XMODEM
5 - Format flash
6 - Show basic hardware information
7 - Perform Reset to the board
8 - System Configuration.
9 - Download an Application by TFTP
Press the ESC key to go back to the Main Menu.
Select:
3. Type 4 to select Download Files or an Application by XMODEM. You will see a
message that requests the partition number to which the new software is to
be downloaded, and offers a recommended value.
4. If there is no special reason to select a different value, type the
recommended number and then press <Enter>. A typical display is shown
below:
Select Copy number for download ( 1 )
Select: 1
5. The process starts, and you will see:
Erasing Partition please wait ....
Please start the XMODEM download.
6. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
You will see the Send File window:
Note
Select the prescribed Gmux-2000 software file name (you may use
the Browse function to find it).
In the Protocol field, select Xmodem.
When ready, press Send in the Send File window. You can now monitor
the progress of the downloading in the Send File window.
If downloading fails, repeat the whole procedure.

7. When the downloading process is successfully completed, you will see a
sequence of messages similar to the following:
Gmux-2000 Ver. 3.2
B-9
Loading ...
Decompressing to RAM.
Processing archive: FLASH
Extracting GMUXCL.BIN
..........................................................
.................................................................... CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
8. At this stage, press the <Enter> key several times to go to the log in screen.
9. If necessary, repeat the process for the second CONTROL module.
Note

communication with the Gmux-2000, you must initialize the database using
Software Downloading Procedure Using TFTP Protocol

Preparations for Using TFTP Protocol
The preparations needed for using the TFTP protocol from the boot menu are
similar to the preparations needed to download software from the File Utilities
menu (see Preparations for Using TFTP section on page B-3), except that you
must connect to the CONTROL ETH connector of the desired CONTROL module.
The main difference is that you need to define the IP communication parameters
for the corresponding CONTROL module (IP addresses and the associated subnet
mask and a default gateway IP address).
Note
The IP parameters used for TFTP transfers from the boot menu should be
different from those you intend to use during normal operation.
To define management IP parameters from the boot menu:
1. Connect the Ethernet cable from the TFTP server to the CONTROL ETH
connector of the desired Gmux-2000 CONTROL module.
2. Use the procedure described on page B-8 to display the boot menu.
3. Select System Configuration to start the configuration of the CONTROL
module IP communication parameters, as needed for TFTP transfer.
B-10
Gmux-2000 Ver. 3.2

1 - Dir
5 - format flash
Select:8
IP Address [172.17.171.139]: 168.119.10.101
IP Mask [255.255.255.0]: 255.255.255.0
Default Gateway Address [172.17.171.1]: 168.119.10.1
4. The parameters are displayed in consecutive lines. For each parameter, you
can accept the current values by simply pressing <Enter> to continue, or type
a new value:
IP Address: used to select the IP address of the CONTROL module. To

change the current value, type the desired IP address in the dotted quad
format, and then <Enter> to continue.
IP Mask: used to select the IP subnet mask of the CONTROL module. To

change the current value, type the IP subnet mask address in the dotted
quad format, and then <Enter> to continue.
Default Gateway Address: when the TFTP server is located on a different

LAN, you must define the IP address of the default gateway to be used
by the CONTROL module. Make sure to select an IP address within the
subnet of the assigned CONTROL module IP address. To change the
current value, type the desired IP address in the dotted quad format, and
then <Enter> to end the configuration.
If no default gateway is needed, for example, because the TFTP server is
attached to the same LAN as the CONTROL module being loaded, enter
0.0.0.0.
5. After pressing <Enter>, you will see again the boot menu.
6. Select Perform Reset to the board to reset the CONTROL module. The new
parameters take effect only after the resetting is completed.
Downloading Procedure
To download software from the boot menu using TFTP:

1. On the boot menu, select Download an Application by TFTP and then press
<Enter> to start the TFTP transfer.
Gmux-2000 Ver. 3.2
B-11
2. After you see Please Enter the Target File Name, enter the name of the
desired software distribution file (make sure to include the path, when
necessary). When done, press <Enter> to continue.
3. You will see Please Enter the Server IP address: enter the IP address of the
server that will download the software distribution file, using the dotted quad
format, and then <Enter> to continue.
1 - Dir
5 - format flash
Select:9
Please Enter the Target File Name: C:\bin\GMUXCL.IMG
IP Mask [255.255.255.0]: 255.255.255.0
Default Gateway Address [172.17.171.1]: 168.119.10.1
5. After the transfer is successfully completed, return to the boot menu and
select Exit Boot-Manager.
6. When the Gmux-2000 initialization is ended, the CONTROL module loads the
new software.
Note

7. If necessary, repeat the process for the second CONTROL module.
Note
B-12

communication with the Gmux-2000, you must initialize the database, using
Gmux-2000 Ver. 3.2
Appendix C
Operating Environment
C.1
Overview
This Appendix presents a concise description of the Gmux-2000 operating

environment, to provide the background information required for understanding
the Gmux-2000 configuration and performance monitoring parameters.
This Appendix covers the following issues:
PDH environment Section C.2
SDH environment Sections C.3 through C.7
SONET Environment Section C.8
Ethernet transmission technology Section C.9
IP environment Section C.10
MPLS environment Section C.11
Pseudowire emulation Section C.12
Management using SNMP Section C.13
C.2
PDH Environment
This section presents information on the main characteristics of the

Plesiochronous Digital Hierarchy (PDH) signals. Table C-1 shows the PDH
multiplexing hierarchies used in the main geographical areas.
Table C-1. PDH Multiplexing Hierarchy
Gmux-2000 Ver. 3.2
Multiplex Level
Europe
North America (USA)
Japan
E1 2.048 Mbps
DS1 1.544 Mbps
J1 1.544 Mbps
E2 8.448 Mbps
DS2 6.312 Mbps
6.312 Mbps
E3 34.368 Mbps
DS3 44.736 Mbps
32.064 Mbps
E4 139.264 Mbps
DS4NA 139.264 Mbps
97.729 Mbps
PDH Environment
C-1
Appendix C Operating Environment
E1 Environment
E1 Line Signal Characteristics
E1 signal characteristics are specified in ITU-T Rec. G.703. The nominal data rate
of the E1 signal is 2.048 Mbps. The E1 line signal is encoded in the High-Density
Bipolar 3 (HDB3) code.
HDB3 is based on the alternate mark inversion (AMI) code. In the AMI code, 1s
are alternately transmitted as positive and negative pulses, whereas 0s are
transmitted as a zero voltage level. To prevent the transmission of long strings of
0s, which do not carry timing information, the HDB3 coding rules restrict the
maximum length of a 0 string that can be transmitted through the line to three
pulse intervals. Longer strings of 0s are encoded at the transmit end to
introduce non-zero pulses.
To allow the receiving end to detect the artificially-introduced pulses and enable
their removal to restore the original data string, the encoding introduces
intentional coding violations in the sequence transmitted to the line. The
receiving end detects these violations and when they appear to be part of an
encoded 0 string it removes them.
Coding violations may also be caused by transmission errors. Therefore, any
coding violations that cannot be interpreted as intentional coding violations can
be counted, to obtain information on the quality of the transmission link.
E1 Signal Structure
The E1 line operates at a nominal rate of 2.048 Mbps. The data transferred over
the E1 line is organized in frames. Each E1 frame includes 256 bits.
The E1 frame format, as defined in ITU-T Rec. G.704, is shown in Figure C-1.
8 Bits per
Time Slot
Time Slot 0
Time Slot 16
a. Even Frames (0,2,4-14)

1 0 0 1 1 0 1 1
a. Frame 0
0 0 0 0 X Y X X
FAS
Time Slots 1-15, 17-31
MAS
Channel Data
b. Odd Frames (1,3,5-15)

I 1 A N N N N N
32 Time Slots/Frame
16 Frames/Multiframe
TS
0
TS
1
TS
2
FR
0
TS
3
FR
1
TS
4
b. Frames 1-15
A B C D A B C D
TS
5
FR
2
TS
6
FR
3
TS
7
TS
8
FR
4
TS
9
TS
10
TS
11
FR
5
TS
12
FR
6
TS
13
TS
14
TS
15
FR
7
TS
16
TS
17
FR
8
TS
18
FR
9
TS
19
1 2 3 4 5 6 7 8
TS
20
TS
21
FR
10
TS
22
FR
11
TS TS
23 24
FR
12
TS
25
TS
26
TS
27
FR
13
TS
28
FR
14
TS
29
TS
30
TS
31
FR
15
Notes
I
N
A
FAS
International Bit
National Bits (Sa4 through Sa8)
Alarm Indication Signal (Loss of Frame Alignment - Red Alarm)
Frame Alignment Signal, occupies alternate
(but not necessarily even) frames
ABCD
X
Y
MAS
ABCD Signaling Bits

Extra Bit
Loss of Multiframe Alignment
Multiframe Alignment Signal
Figure C-1. E1 Frame Format

The 256 bits included in a frame are organized of 32 timeslots of eight bits each.
The frame repetition rate is 8,000 per second, therefore the data rate supported
by each timeslot is 64 kbps.
C-2
PDH Environment
Gmux-2000 Ver. 3.2
Timeslot 0
Timeslot 0 of E1 frames is used for two main purposes:
Delineation of frame boundaries. For this purpose, in every second frame,

timeslot 0 carries a fixed pattern, called frame alignment signal (FAS). Frames
carrying the FAS are defined as even frames, because they are assigned the
numbers 0, 2, 4, etc. when larger structures (multiframes) are used.
The receiving equipment searches for the fixed FAS pattern in the data
stream using a special algorithm, a process called frame synchronization.
Once this process is successfully completed, the equipment can identify each
bit in the received frames.
Interchange of housekeeping information. In every frame without FAS (odd

frames), timeslot 0 carries housekeeping information. This information is
carried as follows:
Bit 1 this bit is called the international (I) bit. Its main use is for error
detection using the optional CRC-4 function (CRC-4 stands for Cyclic
Redundancy Check, using a fourth-degree polynomial). This function is
described below.
Bit 2 is always set to 1, a fact used by the frame alignment algorithm.
Bit 3 is used as a remote alarm indication (RAI), to notify the equipment

at the other end that the local equipment lost frame alignment, or does
not receive an input signal.
The other bits, identified as Sa4 through Sa8, are designated national
bits, and are actually available to the users, provided agreement is
reached as to their use. The total data rate that can be carried by each
national bit is 4 kbps.
Multiframes
To increase the information carrying capacity without wasting bandwidth, the
frames are organized in larger patterns, called multiframes. ITU-T Rec. G.704
recommendations define the following types of multiframes:
Basic G.704 framing
G.704 framing with timeslot 16 multiframe.
Basic G.704 Multiframe

The basic G.704 structure consists of two frames, which are identified by means
of the information included in timeslot 0:
The even frame of the pair includes the frame alignment signal (FAS).
The odd frame includes an 1 in bit position 2, and housekeeping information

in the other bits.
The number of timeslots available for users data is 31, and therefore the
maximum payload rate is 1984 kbps.
To enable the transmission of network management information, a separate
timeslot may have to be assigned within the frame. This procedure is called
Gmux-2000 Ver. 3.2
PDH Environment
C-3
common channel signaling (CCS). The CCS information is often transmitted in

timeslot 16.
G.704 Framing with Timeslot 16 Multiframe (G.704 Multiframe)

The G.704 multiframe structure includes 16 frames, which are identified by means of
a separate multiframe alignment signal (MAS) contained in timeslot 16 of each
frame.
The G.704 multiframe structure is generally used when timeslot 16 serves for the
end-to-end transmission of channel-associated signaling (CAS). A typical
application in which timeslot 16 serves for the transmission of signaling is the
transfer of voice channels by means of voice modules, which use
channel-associated signaling.
Since timeslot 16 must be reserved for the transmission of the MAS and system
signaling, only 30 timeslots are available for the users payload, and the maximum
payload rate is 1920 kbps.
When using the G.704 multiframe format, timeslot 16 of each of the 16 frames in
each multiframe carry the following information:
The first four bits of timeslot 16 in multiframe 16 always carry the multiframe
alignment sequence, 0000.
Bit 6 in timeslot 16 in multiframe 0 is used to notify the equipment at the

other end of the link that the local equipment lost multiframe alignment.
The other bits of this timeslot are not assigned mandatory functions.
Channel Associated Signaling

When using the G.704 multiframe format, timeslots 16 in frames 1 through 15 of
each multiframe are available for carrying users information. In general, this
information is the signaling information for the 30 payload timeslots (channels).
As shown in Figure C-1, four signaling bits, designated A, B, C, and D, are
available for each channel, thereby enabling end-to-end transmission of four
signaling states. Note that each frame in the multiframe carries the signaling
information of two channels.
CRC-4 Error Detection

The Gmux-2000 system supports the CRC-4 function in accordance with ITU-T
Rec. G.704 and G.706. The CRC-4 function is used to detect errors in the received
data, and therefore can be used to evaluate data transmission quality over E1
links.
This function can be enabled or disabled by the user, independently for each link.
To enable error detection, additional information must be provided to the
receiving equipment. The additional information is transmitted to the receiving
equipment by using a multiframe structure called CRC-4 multiframes. A CRC-4
multiframe is an arbitrary group of 16 frames. This group is not related in any
way to the G.704 16-frame multiframe structures explained above.
C-4
A CRC-4 multiframe always starts with an even frame (a frame that carries
the frame alignment signal). The CRC-4 multiframe structure is identified by a
PDH Environment
Gmux-2000 Ver. 3.2
six-bit CRC-4 multiframe alignment signal, which is multiplexed into bit 1 of

timeslot 0 of each odd-numbered (1, 3, 5, etc.) frame of the CRC-4
multiframe (i.e., in frames 1 through 11 of the CRC-4 multiframe).
Each CRC-4 multiframe is divided into two submultiframes of 8 frames (2048

bits) each. The detection of errors is achieved by calculating a four-bit
checksum on each 2048-bit block (submultiframe). The four checksum bits
calculated on a given submultiframe are multiplexed, bit by bit, in bit 1 of
timeslot 0 of each even-numbered frame of the next submultiframe.
At the receiving end, the checksum is calculated again on each submultiframe

and then compared against the original checksum (sent by the transmitting
end in the next submultiframe). The results are reported by two bits
multiplexed in bit 1 of timeslot 0 in frames 13, 15 of the CRC-4 multiframe,
respectively. Errors are counted and used to prepare statistic data on
transmission performance.
E1 Alarm Conditions
Excessive bit error rate. The bit error rate is measured on the frame
-3
alignment signal. The alarm threshold is an error rate higher than 10 that
persists for 4 to 5 seconds. The alarm condition is canceled when the error
-4
rate decreases below 10 for 4 to 5 consecutive seconds.
Loss of frame alignment (also called loss of synchronization). This condition

is declared when too many errors are detected in the frame alignment signal
(FAS), e.g., when 3 or 4 FAS errors are detected in the last 5 frames. Loss of
frame alignment is cleared after no FAS errors are detected in two
consecutive frames.
The loss of frame alignment is reported by means of the A bit (Figure C-1).
Loss of multiframe alignment (applicable only when the G.704 multiframe

structure is used). This condition is declared when too many errors are
detected in the multiframe alignment signal (MAS) (same conditions as for
loss of frame alignment).
The loss of multiframe alignment is reported by means of the Y bit
(Figure C-1).
Alarm indication signal (AIS). The AIS signal is an unframed all-ones signal,
and is used to maintain line signal synchronization in case of loss of input
signal, e.g., because an alarm condition occurred in the equipment that
supplies the line signal. Note that the equipment receiving an AIS signal loses
frame synchronization.
T1 Environment
T1 Line Signal
The basic T1 line signal is coded using the alternate mark inversion (AMI) rules,
explained in Section C.2.
The AMI format cannot transmit long strings of zeros, because such strings do
not carry timing information. Therefore, the AMI signal source must generate a
Gmux-2000 Ver. 3.2
PDH Environment
C-5
signal with guaranteed minimum 1 density. The minimum average 1 density

required by the applicable standards is 1:8. Therefore, when a T1 signal is
transmitted over an AMI line, each frame timeslot must include at least one 1
bit. This effectively reduces user data rate to 56 kbps per timeslot, and precludes
the provision of clear channel capability (CCC).
To circumvent this problem, modified line codes are used, that perform zero
suppression by substituting special codes for long 0 strings. The generally
accepted zero suppression methods are B7 and B8ZS.
With B7, the maximum length of 0 strings in the user data must not exceed
seven zeros (when a longer string is detected, the seventh bit is changed to
one, to meet the minimum 1 density requirement and thus ensure that
the remote end can properly recover the clock signal). Although this
requirement can be fulfilled in many applications, it does not provide 64 kbps
clear channel capability. Therefore, when the B7 line code is used, inband
management is not supported.
Only the B8ZS zero suppression method provides clear channel capability, and
the 1 density requirement no longer restricts user data characteristics. This
means that each T1 frame timeslot can support the full 64 kbps.
Since the AMI coding does not affect the signal transmitted to the line, it is also
called transparent coding. This emphasizes the fact that although the other methods
are also transparent to users data, perfect transparency is achieved only when the
zero-string substitution sequences are correctly recognized. Thus, the other methods
are more sensitive to transmission errors (transmission errors may affect the
decoding of zero-string substitution sequences).
T1 Signal Structure
The T1 line operates at a nominal rate of 1.544 Mbps. The data transferred over
the T1 line is organized in frames.
The T1 frame format is shown in Figure C-2.
Byte Organization
8 Bits/Channel
(D4 Frame - See NOTE)
Frame
Organization
Ft C H C H
24 Channels/Frame
or
1 2
Frame = 193 Bits
Fs
CH
13
FR FR
1 2
FR
7
Multiframe
Organization
NOTE:
In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24
8
A
B
Other Frames
Frame 6
Frame 12
Bit B Conveys
Signaling
Information
CH
24
FR FR
11 12
Multiframe
SF (D4) 12 Frames
ESF: 24 Frames
Figure C-2. T1 Frame Format

Each T1 frame includes 193 bits. 192 bits are organized in 24 timeslots of eight
bits each, that carry the payload data. An additional timeslot, including one bit
(the F-bit) carries framing and supervision information. As a result, the data rate
C-6
PDH Environment
Gmux-2000 Ver. 3.2
supported by each payload timeslot is 64 kbps. The data rate of the framing slot
is 8 kbps.
The T1 frame does not include a dedicated timeslot for the transfer of channel
signaling. When end-to-end transfer of signaling is necessary, a technique called
robbed-bit signaling is used. The robbed-bit is the least significant bit (bit 8) of
the channel byte, and is actually robbed only once in every six frames.
In order to enhance link/system supervision capabilities, the frames are organized
in larger patterns, called super-frames. Two types of super-frames are used:
SF (also called D4), consists of 12 T1 frames.
Extended SF (ESF), consists of 24 T1 frames
The SF format provides limited supervision capabilities, such as end-to-end

reporting of local loss-of-signal (yellow alarm), and line loopback.
The ESF format provides improved supervision capabilities, and allows better
utilization of the 8 kbps framing timeslots. The major advantage of the ESF
format is that it supports on-line link performance monitoring (by means of a
2 kbps Cyclic Redundancy Check (CRC) channel) and in addition provides a 4 kbps
end-to-end supervision and control data link. The data link can be used for
performance monitoring and failure reporting, for activation of maintenance
loopbacks, and for transmission of various commands to the far end equipment.
The implementation of the multiframing format is based on the use of various
F-bit patterns. The F-bit pattern is used to perform three functions:
Framing Pattern Sequence (FPS), defines frame and multiframe boundaries.
Facility Data Link (FDL), allows transfer of supervisory data, e.g. alarms, error
performance, test loop commands, etc. to be passed through the T1 link.
Cyclic Redundancy Check (CRC), allows the measurement of the bit error rate
and enhances the reliability of the framing algorithm.
The F-bit pattern defines the structure of frames and multiframes. In the D4 (SF)
frame format, the F-bit of consecutive frames is alternately interpreted as an
Ft bit (terminal framing bit) or Fs bit (frame signaling bit).
Ft pattern: alternating 0's and 1's, defines the frame boundaries.
Fs pattern: fixed 001110 pattern, defines the multiframe boundaries, so that

one frame may be distinguished from another. In particular, the Fs pattern is
needed so that frames 6 and 12 may be identified for the recovery of
signaling bits.
In the ESF frame format, the multiframe structure is extended to 24 frames, but
the frame and channel structure are the same as in the D4 (SF) format.
T1 Alarm Conditions
The basic alarm conditions are the red alarm and the yellow alarm. Note that with
the ESF format, the FDL link can be used for more sophisticated status
transmissions, in accordance with the ANSI Standard T1.403-1989 and AT&T Pub.
54016.
Gmux-2000 Ver. 3.2
PDH Environment
C-7
Red Alarm. A red alarm is generated when the local unit has lost frame
synchronization for more than 2.5 consecutive seconds, or the bit error rate
-2
exceeds 10 for 2.5 consecutive seconds. Loss of frame synchronization may
be caused either by Fs or Ft errors, by the reception of an AIS signal, or by
the loss of the input signal (receive data remains zero for 31 consecutive
bits). In accordance with AT&T TR-62411, a system automatically recovers
synchronization when there has been a period of 10 to 20 consecutive
seconds free of the loss of sync condition.
Since in many system applications this is a overly conservative specification,
the Gmux-2000 system offers faster frame synchronization algorithms, which
allow the user to select a fast mode. In the fast mode, the time
necessary to declare synchronization is reduced to approximately one second
free of the loss of sync condition.
Yellow Alarm. A yellow alarm is sent from the remote unit to inform the local
unit that a red alarm exists at the remote end.
Alarm Indication Signal (AIS). The AIS signal is an unframed all-ones signal,
and is used to maintain line signal synchronization when an alarm condition
occurs in the equipment that supplies the line signal.
T3 Environment
T3 Line Signal
The T3 line signal is coded using the B3ZS rules (for other zero suppression
codes, see E1 Line Signal Characteristics section), that limits the maximum length
of zero runs to 2.
T3 Signal Structure
The T3 line operates at a nominal rate of 44.736 Mbps. The data transferred over
the T3 line is organized in frames. The general structure of a T3 frame (also called
M-frame) is shown in Figure C-3.
M Subframe 1
M Subframe 7
X1 679 bits X2 679 bits P1 679 bits P2 679 bits M1 679 bits M2 679 bits M3 679 bits
M-Frame
(4760 bits)
Figure C-3. T3 Frame Structure

Each T3 frame includes 4760 bits. The 4760 bits consist of seven M-subframes of
680 bits each, that carry the data payload, framing, and supervision information.
M-Subframe Organization
Figure C-4 shows the organization of the seven M-subframes.
C-8
PDH Environment
Gmux-2000 Ver. 3.2

M Subframe
Block 1
. Block 8
X1
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 1,1 (84 bits)
(84 bits) 1,2 (84 bits)
(84 bits) 1,3 (84 bits)
(84 bits)
X2
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 2,1 (84 bits)
(84 bits) 2,2 (84 bits)
(84 bits) 2,3 (84 bits)
(84 bits)
P1
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 3,1 (84 bits)
(84 bits) 3,2 (84 bits)
(84 bits) 3,3 (84 bits)
(84 bits)
P2
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 4,1 (84 bits)
(84 bits) 4,2 (84 bits)
(84 bits) 4,3 (84 bits)
(84 bits)
M0
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 5,1 (84 bits)
(84 bits) 5,2 (84 bits)
(84 bits) 5,3 (84 bits)
(84 bits)
M1
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 6,1 (84 bits)
(84 bits) 6,2 (84 bits)
(84 bits) 6,3 (84 bits)
(84 bits)
M0
Info
Info
Info
Info
Info
Info
Info
Info
F1
C
F0
C
F0
C
F1
(84 bits)
(84 bits) 7,1 (84 bits)
(84 bits) 7,2 (84 bits)
(84 bits) 7,3 (84 bits)
(84 bits)
Stuff Blocks
Legend
Xn = Status
Pn = Parity
Mn = M-Frame Alignment
Fn = Subframe Alignment
Cn,m = Control
Figure C-4. M-Subframe Organization in DS3 Signal

An M-subframe consists of eight 85-bit blocks. The blocks designated 1 through 7
always have the same structure, whereas the structure of block 8 changes in
accordance with the M-subframe.
Each block comprises one overhead (OH) bit, followed by 84 information bits,
resulting in a total of 56 overhead bits per frame. The functions of the overhead
bits are as follows:
M-Frame Alignment Channel. The M-frame alignment channel signal (bits

M1=0, M2=1, and M3=0) is used to identify each of the seven M-subframes.
M-Subframe Alignment Channel. The M-subframe alignment channel signal

(bits F1=1, F2=0, F3=0, and F4=1) is used to identify the frame overhead bit
positions.
P-Bit Channel. The P-bit channel (bits P1 and P2) is used for performance
monitoring.
X-Bit Channel. The X-bit channel (bits X1 and X2) is used as an alarm channel.
C-Bit Channel. The C-bit channel (bits C1, C2, and C3) are reserved for
application-specific uses.
The application type of a DS3 data stream is identified by means of the first
C-bit in M-subframe 1: this bit serves as an application identification channel
(AIC) signal:
For SYNTRAN (M13) applications, the AIC signal is a repeating 100,100...

pattern that is used to identify the start of an M-frame triad.
For C-bit parity applications, the AIC signal is a continuous 1.
Gmux-2000 Ver. 3.2
PDH Environment
C-9
Block Organization
Figure C-5 shows the structure of the eight types of blocks contained in
M-subframes.
The first seven blocks, 1 through 7, are used to carry DS2 tributary data and
overhead data. The overhead bit of these blocks is shared among the five
channels described above.
The eighth block is used for stuffing, to implement positive justification. For
this purpose, one bit of each block can serve as a stuffing bit for the
corresponding DS2 tributary (the bit is identified as Sj, where j is the tributary
number (1 to 7). For applications that use stuffing, the type of bit (stuffing
or data) is indicated by means of the justification control bits in that
subframe (these bits are designated Cj1, Cj2, Cj3, where j is the tributary
number).
The overhead bit of the eighth block is always part of the subframe alignment
channel.
................
Blocks 1 to 7 in
All M Subframes
OH
D1
D2
D3
D4
D5
D6
D7
D1
S1
D2
D3
D4
D5
D6
D7
D1
D1
S2
D3
D4
D5
D6
D7
D1
D1
D2
S3
D4
D5
D6
D7
D1
Block 8
................
D6
D7
D6
D7
D6
D7
D6
D7
D6
D7
D6
D7
D6
D7
D6
D7
................
F1
M Subframe 1
................
................
F1
M Subframe 2
................
................
F1
M Subframe 3
................
................
F1
M Subframe 4
D1
D2
D3
S4
D5
D6
D7
D1
D1
D2
D3
D4
S5
D6
D7
D1
D1
D2
D3
D4
D5
S6
D7
D1
D1
D2
D3
D4
D5
D6
S7
D1
................
................
F1
M Subframe 5
................
................
F1
M Subframe 6
................
................
F1
M Subframe 7
................
OH = Xn, Pn, M1, M0, F1, F0, or Cn,m

Dn = Information Bit from DS2n : n = 1,2....7
Sn = Stuff Opportunity for DS2n : n =1,2....7
Figure C-5. Block Organization in DS3 Signal
Structure of Standard DS2 Tributary Data

Figure C-6 shows the structure of the DS2 frames, which are carried as payload in
the T3 (DS3) signal. The DS3 signal carries seven DS2 streams, where each DS2
C-10
PDH Environment
Gmux-2000 Ver. 3.2
stream, having a nominal data rate of 6.312 Mbps, carries four DS1 (1.544 Mbps)
signals. The multiplexing method is positive justification.
This arrangement ensures compatibility with the DSX-3 cross-connect
requirements of ANSI T1.107.
The DS2 signal is organized using principles similar to those used for the DS3
signal:
The DS2 frame (also called M-frame) contains 1176 bits.
The 1176 bits are organized as four 294-bit M subframes.
Each M subframe comprises six 49-bit blocks.
The DS2 signal structure includes M-frame and M-subframe alignment channels, an
X-bit status channel, and a C-bit control channel. The control channel is used, among
other functions, to control the justification at the DS2 level.
M-Frame
(1176 bits)
M Subframe 1
. . . . . . . . . M Subframe 4
M1 293 bits M2 293 bits M3 293 bits
M Subframe
Block 1
293 bits
. . . . . . . . . . . . . . . . . . . . .
Block 6
Info
Info
Info
Info
Info
Info
M1
C1
F1
C2
C3
F2
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
M2
Info
Info
Info
Info
Info
Info
C1
F1
C2
C3
F2
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
M3
Info
Info
Info
Info
Info
Info
C1
F1
C2
C3
F2
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
Info
Info
Info
Info
Info
Info
C1
F1
C2
C3
F2
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
(48 bits)
Stuff Blocks
Legend
X
Mn
Fn
C
= Status
= M-Frame Alignment
= Subframe Alignment
= Control
Figure C-6. Structure of Standard DS2 Tributary Data
M13 Multiplex Signal Characteristics

This section describes the synchronous DS3 M13 multiplex application
(SYNTRAN), where 28 DS1 channels are multiplexed directly to the DS3 level.
The M13 multiplex signal preserves the M, F, P, and X bits for compatibility with
the DSX-3 cross-connect requirements of ANSI T1.107 (as well as for network
elements and transmission facilities which recognize these overhead bits). The
M13 application performs multiplexing of signals having a common timing source,
Gmux-2000 Ver. 3.2
PDH Environment
C-11
and therefore stuffing is not necessary. As a result, the C-bit (C1, C2, and C3)
positions in the M-subframes are not needed for stuff indication and are available
for network operations and maintenance functions.
The payload bits are organized into 588 eight-bit octets (timeslots), which are
used to directly multiplex 28 DS1 signals. An additional subframe is embedded
inside the asynchronous DS3 frame structure to define a synchronous
superframe of 699 M-frames that contains 595 synchronous subframes.
SYNTRAN Maintenance Features
DS3 Signal Performance Monitoring. An error detection cyclical redundancy

check code (CRC-9) is used to monitor SYNTRAN signal performance via a
9-bit code.
FEBE Indicator. Bit C2 in the first M-frame in a triad is designated as a Far End
Block Error (FEBE) bit. It is used to indicate CRC-9 errors detected at the
receive side (by returning the FEBE bit to the transmitting side).
Alarm Channel. Bit C3 of the M-frame in a triad designated as an alarm and

control channel.
Loopbacks. The alarm and control channel also supports the transmission of
code words to activate and deactivate the line loopback.
Asynchronous DS3 C-Bit Parity Application

This section describes the asynchronous DS3 C-bit parity signal structure, that is
used to multiplex asynchronous 28 DS1 signals to the DS3 signal level.
The asynchronous DS3 C-bit parity signal preserves the M, F, P, X, and C-bits, to
assure compatibility with DS3 equipment and transmission facilities.
C-Bit Maintenance Features
X-Bit Channel. The X-bit channel is used to transmit failure conditions from
the far end to the near end of the system in the same manner as the yellow
alarm.
Far-End Alarm and Control Signals. The third C-bit in M-subframe 1 is used as
a Far-End Alarm and Control (FEAC) signal. This signal is used for two
purposes:
To send alarm and status information from the far-end terminal back to
the near-end terminal.
To initiate DS3 and DS1 loopbacks at the far-end terminal from the
near-end terminal.
C-12
DS3-Path Parity Bits. The three C-bits in M-subframe 3, designated CP-bits,

are used to carry DS3 path parity information. The receiver uses these bits to
determine if an error has occurred in M-frame, by computing the parity based
on the contents of M-frame n and comparing this parity value with the parity
received in the CP-bits in M-frame n+1.
Terminal-to-Terminal Path Maintenance Data Link. The three C-bits in

M-subframe 5 (designated as DL-bits) are used as a 28.2 kbps
terminal-to-terminal path maintenance data link.
PDH Environment
Gmux-2000 Ver. 3.2
The data link uses the Link Access Procedure on the D-channel (LAPD). The
LAPD messages carry DS3 path identification, DS3 idle signal identification,
and DS3 test signal identification information.
DS3 Alarm Conditions
Gmux-2000 Ver. 3.2
DS3 Alarm Indication Signal (AIS). The DS3 AIS is a signal with a valid M-frame
alignment channel, M-subframe alignment channel, and valid P-bits. The
information bits are a 10... sequence, starting with a one (1) after each
M-frame alignment bit, M-subframe alignment bit, X-bit, P-bit, and C-bit
channel. In addition, the C-bits are set to zero (C1=0, C2=0, and C3=0), and
the X-bits are set to one (X1=1 and X2=1).
DS3 Yellow Alarm. The yellow alarm is declared when the DS3 receive path
cannot detect the framing, or detects AIS reception. The yellow alarm is
indicated by setting the X-bits to zero (X1=0 and X2=0) in the DS3 signal
returned. In the non-alarm condition, the X bits are set to one (X1=1 and
X2=1).
Idle Signal. The idle signal is a signal with a valid M-frame alignment channel,
M-subframe alignment channel, and P-bit channel. The information bits are
set to a 1100... sequence, starting with a one-one (11) after each M-frame
alignment, M-subframe alignment, X-bit, P-bit, and C-bit channels. In addition,
the C-bits in M-subframe 3 are set to zero.
PDH Environment
C-13
C.3
SDH Implementation Principles
This section describes the implementation principles for the Synchronous Digital
Hierarchy (SDH), as a background for the detailed presentation of the SDH signal
structures. In the following explanations, the following terms are used to describe
SDH networks:
Network node. The SDH network node is a facility at which signals built in
accordance with the SDH frame structure are generated and/or terminated.
Therefore, a network node provides a convenient access point to add or drop
payload signals, e.g., PDH tributary signals, for transmission over the SDH
network.
SDH transport system. An SDH transport system provides the technical means
to transfer SDH signals between two network nodes.
SDH network. An SDH network is formed by interconnecting the required

number of network nodes by means of SDH transport systems.
Basic SDH Principles

The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two
principles:
1. Direct synchronous multiplexing of individual tributary signals within the
structure of the higher-rate multiplexed signal.
2. Transparent transporting of each individual tributary signal through the
network, without any disassembly except at the two network nodes that
exchange information through that particular signal.
To enable synchronous multiplexing, SDH equipment is designed to permit
efficient and reliable synchronization of the whole network to a single timing
reference.
Direct Multiplexing Approach

Direct multiplexing means that individual tributary signals can be inserted and
removed into the SDH multiplexed signal without intermediate multiplexing and
demultiplexing steps. This capability results in the following characteristics:
Efficient signal transport, as the same SDH transport system can carry various
types of payloads (tributary signals).
Flexible routing, because any tributary can be inserted and removed into the
SDH signal as a single unit, without affecting in any way the other tributary
signals carried by the same SDH signal. This permits to build cost-effective
add/drop multiplexers, the key component of flexible networks, instead of
implementing digital cross-connect systems as entities separated from
multiplexing equipment.
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore provides the network operator full
control over all the operational aspects of SDH networks and equipment units.
C-14
Gmux-2000 Ver. 3.2
This overhead permits the integration of the network management and

maintenance functions within the transport network itself.
General Structure of SDH Signals

The SDH signal is a serial signal stream with a frame structure. Figure C-7 shows
the general structure of SDH signals.
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure. Each SDH frame starts with framing bytes, which enable
equipment receiving the SDH data stream to identify the beginning of each
frame. The location of the other bytes within this frame structure is determined
by its position relative to the framing byte.
The organization of the frame can be easily understood by representing the
frame structure as a rectangle comprising boxes arranged in N rows and M
columns, where each box carries one byte. In accordance with this
representation, the framing byte appears in the top left-hand box (the byte
located in row 1, column 1), which by convention is referred to as byte 1 of the
SDH frame.
N x M Bytes
Order of
Transmission
F B
B B
B
B
N x M Bytes
N Rows
1
2
Order of
Transmission
B B
B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure C-7. 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 C-7). 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.
Gmux-2000 Ver. 3.2
C-15
SDH Frame Organization

As shown in Figure C-8, an SDH frame comprises two distinct parts:
Section Overhead (SOH)
Virtual Container (VC).
N Rows
Section
Overhead
Path Overhead (One Column)
Virtual Container
(VC)
M Columns
Figure C-8. SDH Frame Organization
Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type.
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
Virtual Container (VC)

The VC is an envelope (i.e., a special type of signal structure, or frame) that is
used to transport a tributary signal across the SDH network.
The path followed by a VC within the network may include any number of nodes,
therefore the VC may be transferred from one SDH transport system to another,
many times on its path through the network. Nevertheless, in most cases the VC
is assembled at the point of entry to the SDH network and disassembled only at
the point of exit.
Since the VC is handled as an envelope that is opened only at the path end
points, some of its signal carrying capacity is dedicated to path overhead. The
C-16
Gmux-2000 Ver. 3.2
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.
Gmux-2000 Ver. 3.2
C-17
C.4
STM-1 Frame Structure
Gmux-2000 handles the base-level SDH signal, which is called Synchronous

Transport Mode Level 1 (STM-1).
Description of STM-1 Frame

Figure C-9 shows the STM-1 frame structure.
2430 Bytes/Frame
155.52 Mbps
9 Rows
Section
Overhead
Path Overhead (9 Bytes)
Serial Signal
Stream
STM-1 Virtual Container (VC-4)
Container Capacity = 150.34 Mbps

Payload Capacity = 149.76 Mbps
9 Columns
260 Columns
1 Column
2430 Bytes/Frame x 8 Bits/Byte x 8000 Frames/sec = 155.52 Mbps
Figure C-9. 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
C-18
Gmux-2000 Ver. 3.2
fourth level in the PDH signal hierarchy). The VC-4 signal carrying capacity can
also be subdivided, to permit the transport of multiple lower-level PDH
signals.
Pointers
In Figure C-9, 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.
Gmux-2000 Ver. 3.2
C-19
C.5
SDH Overhead Data
SDH Overhead Data Types

In SDH networks, a transmission path can include three equipment functions:
SDH terminal multiplexer which performs the insertion/removal of tributary

signals into SDH frames
SDH cross-connect switch permits to change the routing of tributary signals

carried in SDH frames
Regenerator used to increase the physical range of the transmission path.
The resulting structure of an SDH transmission path is shown in Figure C-10.

Multiplexer
Section
Multiplexer Section
Regenerator
Section
Regenerator
Section
Regenerator
Section
Tributary
Signals
..
.
SDH
Terminal
Multiplexer
SDH
Terminal
Multiplexer
Tributary
Signals
..
.
SDH Cross-Connect
VC
Assembly
Path
VC
Disassembly
Figure C-10. Structure of Transmission Path in SDH Network

As shown in Figure C-10, 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:
C-20
Section overhead, carried in the first nine columns of the STM-1 frame:
Multiplexer section (MS) overhead carried in overhead rows 5 to 9
Regenerator section (RS) overhead carried in overhead rows 1 to 3
AU pointers carried in overhead row 4.
SDH Overhead Data
Gmux-2000 Ver. 3.2
Path overhead, carried in the first column of a VC-4. The path overhead
carried in the VC-4 is called high-order path overhead; see Section C.6 for a
description of the low-order path overhead.
Figure C-11 shows the detailed structure of the overhead data in STM-1 frames.
Path
Overhead
Section Overhead
Framing
A1
Regenerator
Section
Overhead
(Rows 1 - 3)
AU Pointers
(Row 4)
Framing
A1
Framing
A1
Framing
A2
Framing
A2
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
Z1
B2
Z1
B2
Z1
Z2
Z2
Z2
Pointer
H3
Pointer
H3
Path Status
G1
Bytes reserved for future use
Figure C-11. 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.
Gmux-2000 Ver. 3.2
SDH Overhead Data
C-21
Channel Identifier (C1 Byte)

The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
Parity Check (B1 Byte)

A 8-bit wide bit-interleaved parity (BIP-8) checksum is calculated over all the bits
in the STM-1 frame, to permit error monitoring over the regenerator section. The
computed even-parity checksum is placed in the RSOH of the following STM-1
frame.
Data Communication Channel (D1, D2, D3 Bytes)

The 192 kbps Data Communication Channel (DCC) provides the capability to
transfer network management and maintenance information between
regenerator section terminating equipment.
Orderwire Channel (E1 Byte)

The E1 byte is used to provide a local orderwire channel for voice
communications between regenerators and remote terminal locations.
User Communication Channel (F1 byte)

The F1 byte is intended to provide the network operator with a channel that is
terminated at each regenerator location, and can carry proprietary
communications.
The information transmitted on this channel can be passed unmodified through a
regenerator, or can be overwritten by data generated by the regenerator.
AU Pointers (H1, H2, H3 bytes)

The AU (Administration Unit) pointer bytes are used to enable the transfer of
STM-1 frames within STM-N frames, and therefore are processed by multiplexer
section terminating equipment. Separate pointers are provided for each STM-1
frame in an STM-N frame.
AU pointer function is to link between the section overhead and the associated
virtual container(s).
Multiplexer Section Overhead (MSOH)

A multiplexer section of an SDH network comprises the transmission medium,
together with the associated equipment (including regenerators) that provide the
means of transporting information between two consecutive network nodes
(e.g., SDH multiplexers). One of the network nodes originates the multiplexer
section overhead (MSOH) and the other terminates this overhead.
The functions of the various bytes carried in the STM-1 multiplexer section
overhead are described below.
C-22
SDH Overhead Data
Gmux-2000 Ver. 3.2
Parity Check (B2 Bytes)

A 24-bit wide bit-interleaved parity (BIP) checksum is calculated over all the bits
in the STM-1 frame (except those in the regenerator section overhead). The
computed checksum is placed in the MSOH of the following STM-1 frame.
Protection Switching (K1, K2 Bytes)

The K1 and K2 bytes carry the information needed to activate/deactivate the
switching between the main and protection paths on a multiplexer section.
Data Communication Channel (D4 to D12 Bytes)

Bytes D4 to D12 provide a 576 kbps data communication channel (DCC) between
multiplexer section termination equipment. This channel is used to carry network
administration and maintenance information.
Orderwire Channel (E2 Byte)

The E2 byte is used to provide a local orderwire channel for voice
communications between multiplexer section terminating equipment.
Alarm Signals
Alarm information is included as part of the MSOH. These functions are explained
in Section C.7.
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.
Gmux-2000 Ver. 3.2
SDH Overhead Data
C-23
Signal Label (C2 Byte)

The signal label byte, C2, indicates the structure of the VC-4 container. The signal
label can assume 256 values, however two of these values are of particular
importance:
The all 0s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)
The code 00000001 represents the VC-4 equipped state.
Path Status (G1 Byte)

The G1 byte is used to send status and performance monitoring information from
the receive side of the path terminating equipment to the path originating
equipment. This allows the status and performance of a path to be monitored
from either end, or at any point along the path.
Multiframe Indication (H4 byte)

The H4 byte is used as a payload multiframe indicator, to provide support for
complex payload structures, for example payload structures carrying multiple
tributary units (TUs see Section C.6). If, for example, the TU overhead is
distributed over four TU frames, these four frames form a TU multiframe
structure. The H4 byte then indicates which frame of the TU multiframe is
present in the current VC-4.
User Communication Channel (F2 Byte)

The F2 byte supports a user channel that enables proprietary network operator
communications between path terminating equipment.
Alarm Signals
Alarm and performance information is included as part of the path overhead.
These functions are explained in Section C.7.
C-24
SDH Overhead Data
Gmux-2000 Ver. 3.2
C.6
SDH Tributary Units
The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the
transport of a fourth level (139.264 Mbps) PDH multiplex signal.
To enable the transport and switching of lower-rate tributary signals within the
VC-4, several special structures, called Tributary Units (TUs), have been defined.
The characteristics of each TU type have been specifically selected to carry one of
the standardized PDH signal rates. In addition, a fixed number of whole TUs may
be mapped within the container area of a VC-4.
Tributary Unit Frame Structure

The structure of the tributary unit frame is rather similar to the SDH frame
structure, described in Section 0. With reference to Figure C-8, 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:
Gmux-2000 Ver. 3.2
TU-11: Each TU-11 frame consists of 27 bytes, structured as 3 columns of 9

bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 1.728 Mbps and will accommodate the mapping of a North American DS1
signal (1.544 Mbps). 84 TU-11s may be multiplexed into the STM-1 VC-4.

of 2.304 Mbps and will accommodate the mapping of a CEPT 2.048 Mbps
signal. 63 TU-12s may be multiplexed into the STM-1 VC-4.

SDH Tributary Units
C-25
of 6.912 Mbps and will accommodate the mapping of a North American DS2
signal. 21 TU-2s may be multiplexed into the STM-1 VC-4.

of 49.54 Mbps and will accommodate the mapping of a CEPT 34.368 Mbps
signal or a North American 44.768 DS3 signal. Three TU-3s may be
multiplexed into the STM-1 VC-4.
Figure C-12 illustrates the assembly (multiplexing) of TUs in the VC-4 structure,
for the specific case of the TU-12. For other multiplexing options, see
Figure C-13.
2430 Bytes/Frame
155.52 Mbps
Section
Overhead
9 Rows
VC-4 Path Overhead
Serial Signal
Stream
9 Columns
TU-12
No. 1
TU-12 No.2
to
TU-12 No.62
TU-12
No. 63
260 Columns
1 Column
Figure C-12. VC-4 Carrying TU-12 Payload

As shown in Figure C-12, 63 TU-12s can be packed into the 260 columns of
payload capacity (i.e., the C-4 container) provided by a VC-4. This leaves 8
columns in the C-4 container unused. These unused columns result from
intermediate stages in the TU-12 to VC-4 multiplexing process, and are filled by
fixed stuffing bytes.
SDH Multiplexing Hierarchy

Figure C-13 shows a general view of the SDH multiplexing hierarchy. The
hierarchy illustrates all the both the European and North American PDH multiplex
levels (see Table C-1 for details on the PDH multiplexing hierarchy).
Figure C-13 also shows the utilization of additional SDH signal structures:
C-26
TUG: tributary unit group, is the structure generated by combining several

lower level tributaries into the next higher level tributary. For example, TUG-2
is generated by combining 3 TU-12 or 4 TU-11, and TUG-3 is generated by
combining 7 TUG-2.
AU: administrative unit, is a structure that includes a VC and a pointer to the

beginning of the VC. For example, AU-3 contains one VC-3 and includes a
pointer to the beginning of the VC.
SDH Tributary Units
Gmux-2000 Ver. 3.2
Note
STM-1
(155.520 Mbps)
AUG: administrative unit group, is the structure generated by combining

several lower level administrative units into the next higher level
administrative unit. For example, AUG for the STM-1 level is generated by
combining 3 AU-3 (several AUG can be combined for generating STM-N (N =
4, 16, etc.) structures).
For simplicity, reference is made only to VCs (the actual structure needed to
transport a VC can be found from the SDH or SONET multiplexing hierarchy).
1
1
AU-4
VC-4
AU-3
VC-3
AUG
C-4
139.264 Mbps
(E4)
1
3
44.736 Mbps
(DS3)
3
VC-3
TU-3
C-3
34.368 Mbps
(E3)
TUG3
TU-2
1
7
2
TUG2
Legend
VC-2
C-2
3.152 Mbps
(DS1C)
VT3
TU-11
VC-11
C-11
1.544 Mbps
(DS1)
TU-12
VC-12
C-12
2.048 Mbps
(E1)
Pointer Processing
3
Mapping
6.312 Mbps
(DS2)
Figure C-13. SDH Multiplexing Hierarchy

The flexibility of the SDH multiplexing approach is illustrated by the many paths
that can be used to build the various signal structures. For example, Figure C-13
shows that the STM-1 signal can be generated by the following multiplexing
paths:
Gmux-2000 Ver. 3.2
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 Tributary Units
C-27
C.7
SDH Maintenance Signals

The maintenance signals transmitted within the SDH signal structure are
explained in Table C-2.
Table C-2. SDH Maintenance Signal Definitions

Signal
Description
Loss of Signal (LOS)
LOS state entered when received signal level drops below the value at which an
error ratio of 10 is predicted.
-3
LOS state exited when 2 consecutive valid framing patterns are received,
provided that during this time no new LOS condition has been detected
Out of Frame (OOF)
OOF state entered when 4 or 5 consecutive SDH frames are received with invalid
(errored) framing patterns. Maximum OOF detection time is therefore 625 s.
OOF state exited when 2 consecutive SDH frames are received with valid framing
patterns
Loss of Frame (LOF)
LOF state entered when OOF state exists for up to 3 ms. If OOFs are
intermittent, the timer is not reset to zero until an in-frame state persists
continuously for 0.25 ms.
LOF state exited when an in-frame state exists continuously for 1 to 3 ms
Loss of Pointer (LOP)
LOP state entered when N consecutive invalid pointers are received where N = 8,
9 or 10.
LOP state exited when 3 equal valid pointers or 3 consecutive AIS indications are
received.
Note
Multiplexer Section AIS
The AIS indication is an all 1s pattern in pointer bytes.
Sent by regenerator section terminating equipment (RSTE) to alert downstream

MSTE of detected LOS or LOF state. Indicated by STM signal containing valid
RSOH and a scrambled all 1s pattern in the rest of the frame.
Detected by MSTE when bits 6 to 8 of the received K2 byte are set to 111 for
3 consecutive frames. Removal is detected by MSTE when 3 consecutive frames
are received with a pattern other than 111 in bits 6 to 8 of K2.
Far End Receive Failure

(FERF or MS-FERF)
Sent upstream by multiplexer section terminating equipment (MSTE) within

250 s of detecting LOS, LOF or MS-AIS on incoming signal. Optionally
transmitted upon detection of excessive BER defect (equivalent BER, based on B2
bytes, exceeds 10 ). Indicated by setting bits 6 to 8 of transmitted K2 byte to
110.
-3
Detected by MSTE when bits 6 to 8 of received K2 byte are set to 110 for 3
consecutive frames. Removal is detected by MSTE when 3 consecutive frames are
received with a pattern other than 110 in bits 6 to 8 of K2.
Transmission of MS-AIS overrides MS-FERF
C-28
Gmux-2000 Ver. 3.2
Signal
Description
AU Path AIS
Sent by MSTE to alert downstream high order path terminating equipment (HO
PTE) of detected LOP state or received AU Path AIS. Indicated by transmitting all
1s pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when all 1s pattern is received in bytes H1 and H2 for 3
consecutive frames. Removal is detected when 3 consecutive valid AU pointers
are received
High Order Path Remote

Alarm Indication
(HO Path RAI, also known
as HO Path FERF)
Generated by high order path terminating equipment (HO PTE) in response to

received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
POH G1 byte to 1.
TU Path AIS
Sent downstream to alert low order path terminating equipment (LO PTE) of
detected TU LOP state or received TU path AIS. Indicated by transmitting all 1s
pattern in entire TU-1, TU-2 and TU-3 (i.e., pointer bytes V1-V3, V4 byte, plus all
bytes of associated VC-1, VC-2 and VC-3 loaded by all 1s pattern).
Detected by peer HO PTE when bit 5 of received G1 byte is set to 1 for 10

consecutive frames. Removal detected when peer HO PTE receives 10
consecutive frames with bit 5 of G1 byte set to 0
Detected by LO PTE when all 1s pattern received in bytes V1 and V2 for 3

consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Note
Low Order Path Remote

Alarm Indication
(LO Path RAI, also known
as LO Path FERF)
TU Path AIS is only available when generating and/or receiving floating

mode tributary unit payload structures.
Generated by low order path terminating equipment (LO FTE) in response to

received TU Path AIS. Sent upstream to peer LO PTE.
Indicated by setting bit 8 of LO POH V5 byte to 1.
Detected by peer LO PTE when bit 8 of received V5 byte is set to 1 or 10
consecutive multiframes. Removal detected when peer LO PTE receives 10
consecutive multiframes with bit 8 of V5 byte set to 0.
Note
LO Path RAI is only available when generating and/or receiving floating

mode tributary unit payload structures.
Response to Abnormal Conditions

This section describes the response to the wide range of conditions that can be
detected by the maintenance means built into the SDH frames, and the flow of
alarm and indication signals.
Figure C-14 provides a graphical representation of the flow of alarm and

indication signals through an SDH transmission path.
Gmux-2000 Ver. 3.2
C-29

Low Order Path
High Order Path

Multiplexer Section
Regenerator
Section
LO PTE
HO PTE
MS TE
Regenerator
Section
RS TE
MS TE
LOP
HO PTE
LO PTE
LOP
LOP
AIS
(H1H2)
AIS
(V1V2)
LOS
LOF
LOS
LOF
AIS (X2)
Tributary
AIS
FERF
(X2)
RAI
(G1)
RAI (G1)
RAI
(VS)
RAI (VS)
B1(BIP-8)
B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE
(G1)
FEBE
(G1)
BIP-2
(VS)
FEBE
(VS)
FEBE
(VS)
Legend
Collection
Transmission
Generation
LO
HO
Low Order
High Low Order
PTE
RS TE
MS TE
Path Terminating Equipment

Regenerator Section Terminating Equipment
Multiplexer Section Terminating Equipment
Figure C-14. 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:
C-30
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
Gmux-2000 Ver. 3.2
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.
Gmux-2000 Ver. 3.2
C-31
C.8
SONET Environment
SONET (Synchronous Optical Network) is an alternative standard to SDH, widely

used in North America and other parts of the world. SONET uses similar
implementation principles, and even the frame structures are quite similar to
those used by SDH. Therefore, the following description is based on the
information already presented for SDH in Sections 0 through C.7.
Figure C-15 shows the SONET multiplexing hierarchy.

STS-3
(155.520 Mbps)
1
STS-3
STS-3c
139.264 Mbps
(E4)
1 STS-3c
SPE
44.736 Mbps
(DS3)
VT6
VT6
SPE
6.312 Mbps
(DS2)
VT3
VT3
SPE
3.152 Mbps
(DS1C)
VT1.5
VT1.5
SPE
1.544 Mbps
(DS1)
VT2
VT2
SPE
2.048 Mbps
(E1)
1
2
STS-1
Legend
STS-1
SPE
VT
Group
Pointer Processing
3
Mapping
Figure C-15. SONET Multiplexing Hierarchy

The designations of the main signal structures in the SONET hierarchy are as
follows:
C-32
Containers are replaced by Synchronous Payload Envelopes (SPE) for the

various virtual tributaries (VTs)
Virtual containers (VCs) are replaced by virtual tributaries (VTs), however the
rates are similar to those used in the SDH hierarchy
Tributary unit groups (TUGs) are replaced by virtual tributary groups
The VC-3 level is replaced by the Synchronous Transport Signal level 1

(STS-1), and has the same rate (51.840 Mbps).
3 STS-1 can be combined to obtain one Synchronous Transport Signal level 3

(STS-3) at the same rate as STM-1 (155.520 Mbps). The corresponding
optical line signal is designated OC-3.
SONET Environment
Gmux-2000 Ver. 3.2
C.9
Ethernet Transmission Technology
Introduction to Ethernet Transmission

One of the most successful digital transmission technologies is referred to by the
generic term Ethernet. The Ethernet technology is suitable for a wide range of
physical media: coaxial cable, twisted pairs and optical fibers. The current
standards for Ethernet transmission cover rates from 10 Mbps to 10 Gbps. In
many office LANs, Ethernet runs at 10 Mbps and 100 Mbps (Fast Ethernet);
1000 Mbps (1 Gbps, also called Gigabit Ethernet, or GbE) is rapidly becoming
commonplace.
The basic standards covering Ethernet LANs are included in the IEEE 802.3 family.
In addition to the aspects covered by the IEEE 802.3 standards, there is a wide
range of LAN standards (the IEEE 802 family) that cover other aspects of LAN
transmission, for example, bridging, with particular emphasis on Ethernet LANs.
Ethernet standards (in their broadest interpretation) cover the physical and data
link control layers (layers 1 and 2 in the OSI model; IP is a layer 3 protocol). The
data link control layer is split into two sublayers: media access control (MAC) and
logical link control (LLC).
Ethernet LAN Topologies

Ethernet LANs use a multidrop topology. The LANs can be implemented either in
bus or star (hub-based) topology.
For the Gmux-2000, only the star (hub-based) topology is relevant.
Figure C-16 shows the general structure of a LAN using the star topology.
In the star topology, all the nodes on the LAN are connected to a common unit,
which serves as the hub of the LAN. The hub can be implemented in two ways:
Simple Ethernet hub, which detects the transmitting node and transparently
distributes its signal to all the other nodes. A hub supports only half-duplex
communication (the same as in a bus topology).
Ethernet switch: the switch includes more sophisticated circuits that enable
both half-duplex and full-duplex operation and prevent collisions.
In a star topology, the LAN cables are usually made of two twisted pairs (one
transmit pair and one receive pair). The standard connector type is RJ-45, and its
pin assignment has also been standardized. However, because of the need to use
separate transmit and receive pairs, two types of port pin assignments have
developed: station ports and hub ports (the difference is interchanging of the
transmit and receive pins in the connector). This permits to interconnect
connectors of different types by a cable wired pin-to-pin (straight cable).
A fixed assignment of pin functions in the connectors requires using a crossed
cable (a cable wired to interconnect the transmit pair at one end to the receive
pair at the other end) to interconnect ports of same type. To avoid the need for
using two types of cables (straight and crossed), special methods have been
developed to enable automatic detection of pairs by the Ethernet interface, thus
Gmux-2000 Ver. 3.2
C-33
enabling the interface to select the correct connection irrespective of the type of
cable.
Interfaces operating on twisted pairs are designated in accordance with data
rate: 10BASE-T (10 Mbps), 100BASE-TX (100 Mbps, where X is the number of
pairs) and 1000BASE-T (1000 Mbps, which always uses 2 twisted pairs).
100 Mbps fiber optic interfaces are identified as 100BASE-FX (where X is the
number of fibers, and 1000 Mbps fiber optic interfaces carry a label that indicates
the range (SX for short range, etc.).
Interfaces that support multiple rates are identified as 10/100BASET,
10/100/1000BASET, etc.
10/100BaseT Ethernet Hub
SD
TX Pair
RX Pair
Figure C-16. Star (Hub-Based) Ethernet LAN Topology
Ethernet Communication Protocol

Today, Ethernet is used as a generic term for a LAN transmission technology that
uses Carrier Sense and Multiple Access with Collision Detection (CSMA/CD) to
enable the transmission of short bursts of data (called frames) between two or
more stations (nodes).
All the users have permanent access to the full bandwidth of the transmission
medium but can only use it for short times, by transmitting short data bursts.
Each data burst has a fixed structure, called a frame. The frame structure is
explained below. The connection point of each user to the transmission media is
called a node. For identification purposes, each LAN node has its own unique
number, called MAC address.
Media Access Method

Media access is performed by means of the carrier sense, multiple access
protocol (CSMA) with collision detection (CD), defined by IEEE Standard 802.3.
The protocol defines three basic steps:
C-34
A node that wants to transmit checks that the LAN is free. If another node is
already transmitting, the node waits until the LAN is free.
When the LAN is free, the node starts transmission and sends its frame. Each
node has equal access rights, therefore the first node that starts transmitting
is the one that seizes the LAN.
When two nodes start transmitting at the same instant, a collision occurs. In
this case, the transmitting nodes will continue to transmit for some time, in
order to ensure that all transmitting nodes detected the collision (this is
Gmux-2000 Ver. 3.2
called jamming). After the jamming period, all transmitting nodes stop the
transmission and wait for a random period of time before trying again.
The delay times are a function of collision numbers and random time delay,
therefore there is a good chance that an additional collision between these
nodes will be avoided, and the nodes will be able to transmit their messages.
The basic procedure described above has been developed for half-duplex
communication, because it declares a collision whenever data is received during a
local transmission. However, when using twisted pairs, separate pairs are used
for the transmit and receive directions. Therefore, each node is capable of
simultaneously transmitting and receiving (full-duplex operation), thereby
doubling the effective data rate on the LAN.
Autonegotiation
As mentioned above, modern Ethernet interfaces are often capable of operation
at the two basic rates, 10 Mbps and 100 Mbps, or even at three rates
(10/100/1000 Mbps). Therefore, the rate and operating mode (half-duplex or
full-duplex) are user-configurable options.
When connecting equipment from different vendors to a common LAN, several
operating modes are possible, depending on the specific characteristics of the
equipment interconnected by means of the LAN . These modes are listed below,
in ascending order of capabilities:
Half-duplex operation at 10 Mbps.
Full-duplex operation at 10 Mbps.
To ensure interoperability (which practically means to select the highest transport

capability supported by all the equipment connected to the LAN), two approaches
can be used: manual configuration of each equipment interface, or automatic
negotiation (autonegotiation) in accordance with IEEE Standard 802.3.
The autonegotiation procedure enables automatic selection of the operating
mode on a LAN, and also enables equipment connecting to an operating LAN to
automatically adopt the LAN operating mode (if it is capable of supporting that
mode).
When autonegotiation is enabled on all the nodes attached (or trying to attach)
to a LAN, the process is always successful. However, even if the nodes on an
operating LAN are manually configured for operation in a fixed mode, a
late-comer node with autonegotiation capability can still resolve the LAN
operating rate can be resolved, thereby enabling it to adopt the LAN rate. Under
these conditions, an autonegotiating node cannot detect the operating mode
(half or full duplex), and therefore they will default to half-duplex. Therefore, as a
practical configuration rule, do not enable the full-duplex mode without enabling
autonegotiation, except when all the nodes have been manually configured for
the desired operating mode (which may of course be full duplex).
Gmux-2000 Ver. 3.2
C-35
Basic Ethernet Frame Structure

The frame transmitted by each node contains routing, management and error
correction information. For Ethernet LANs, the characteristics of frames are
defined by IEEE Standard 802.3.
Basic frame lengths can vary from 72 to 1526 bytes and have the typical
structure shown in Figure C-17.
72 to 1526 Bytes
Preamble
SFD
(7 Bytes)
(1 Byte)
MAC Destination
Address
(6 Bytes)
MAC Source
Address
(6 Bytes)
Length/
Type
(2 Bytes)
MAC Client Data

(0 To 1500 Bytes)
Padding
Bytes
Frame
Check
Sequence
(4 Bytes)
Start Frame
Delimiter
Figure C-17. Basic Ethernet Frame Structure
Note
C-36
Preamble. Each frame starts with a preamble of seven bytes. The preamble is
used as a synchronizing sequence for the interface circuits, and helps bit
decoding.
Start-Frame Delimiter (SFD) field consists of one byte. The SFD field
indicates where the useful information starts.
Medium-Access (MAC) Destination Address (DA) field consists of six bytes.

The MAC DA field carries the address of the destination node.
Medium-Access (MAC) Source Address (SA) field consists of six bytes. The
MAC SA field carries the address of the source node.
In conventional notation MAC addresses are represented as 6 pairs of

hexadecimal digits, separated by dashes, for example, 08-10-39-03-2F-C3.
Length/Type field consists of two bytes that indicate the number of bytes
contained in the logical link control (LLC) data field. In most Ethernet protocol
versions, this field contains a constant indicating the protocol type (in this
case, this field is designated EtherType).
MAC Client Data field. The MAC client data field can contain 0 to 1500 bytes
of user-supplied data.
Padding field. The optional padding field contains dummy data, that is used
to increase the length of short frames to at least 64 bytes.
Frame Check Sequence (FCS) field contains four check bytes generated by a
cyclic redundancy check (CRC) code. The FCS field is used to detect errors in
the data carried in the frame.
Gmux-2000 Ver. 3.2
Bridging
Communication between Nodes on Same LAN
A MAC address is unique and identifies a single physical port. Therefore, two
Ethernet nodes attached to the same LAN exchange frame directly, by specifying
the desired MAC destination address, together with the source MAC address.
The node that identifies its MAC address in the destination field can send a
response by copying the source address of the frame to the destination address
field.
Communication between Nodes on Different LANs

To enable nodes on different LANs to communicate, it is necessary to transfer
frames between the two LANs. The device used for this purpose is called MAC
bridge, or just bridge. Two types of bridges are used:
Local bridges, which have Ethernet ports attached to the two LANs. The
bridge control mechanism learns the nodes attached to each LAN by reading
the source MAC addresses of the frames generated by the nodes. When the
destination address of a frame is not on the LAN from which it was received,
the bridge transfers it to the other LAN.
Remote bridges, which are used in pairs. A basic remote bridge has one LAN
port and one WAN port. The WAN port communicates through a link with the
WAN port of the remote bridge connected to the desired remote LAN. In this
case, the traffic addressed to destinations not located on the local LAN is
transferred through the WAN link to the remote bridge.
Using Virtual Bridged LANs

VLAN can be used to provide separation between traffic from different sources
sharing the same physical transmission facilities, and provide information on the
relative priority the user assigns to each frame. The characteristics and use of
virtual LANs (VLANs) and of the MAC bridges capable of handling tagged frames
are defined in IEEE Standard 802.1Q. VLANs are made possible by a slight
modification to the Ethernet frame structure shown in Figure C-17.
The structure of an Ethernet frame with VLAN support is shown in Figure C-18
(for simplicity, the figure does not include the preamble and SFD fields).
Ethernet frames with VLAN support include a tag header immediately after the
source MAC address (therefore, such frames are also referred to as tagged
frames).
The tag header comprises 4 bytes:
Gmux-2000 Ver. 3.2
Two bytes for the tag protocol identifier. For Ethernet-encoded tags in
accordance with IEEE802.1Q, these bytes carry the equivalent of 8100.
Priority (PRI) specified by the user (3 bits: 7 is the highest priority and 0 is
the lowest priority).
One bit for the canonical format indicator (always 0 as shown in Figure C-18).
VLAN ID (12 bits), used to indicate the VLAN to which the frame belongs.
C-37
12
16
20
24
28
31
Destination MAC Address (DA)

Destination MAC Address (DA)
Source MAC Address (SA)
Source MAC Address (SA)

Tag Protocol Identifier (8100)
PRI
EtherType (IP = 0800)
VLAN ID
Ethernet Payload (42 to 1500 Bytes)

Ethernet Payload
.
.
.
CRC
Figure C-18. Structure of Ethernet Frame with VLAN Support
C.10 IP Environment
This section provides background information on the IP environment.
The information presented in this section refers to Version 4 of the IP protocol
(IP4), currently the most widely used protocol version.
Introduction to IP
IP means Internet Protocol. The term IP protocol is often used to indicate a
standardized set of rules and procedures that enable data exchange through a
packet-switched network.
Accordingly, the term Internet indicates the set of networks that use the IP
protocol and are interconnected in a way that, at least in principle, permits any
entity on one network to communicate with any entity on another network.
Note
The term suite of IP protocols is also often used, in recognition of the fact that
the operation of the Internet is actually defined by many related protocols.
IP Networks, IP Hosts and IP Ports

Any entity that can communicate using the IP protocol is called an IP host. The
connection point between an IP host and an IP network is called IP port.
An IP network forms when a number of IP ports can communicate directly (peer
to peer) using the IP protocol, without any intermediaries.
An IP host can have any number of IP ports. Moreover, the ports may be located
on different IP networks.
C-38
IP Environment
Gmux-2000 Ver. 3.2
IP Addresses
To enable IP communication between two IP hosts, it is necessary to find a route
between their IP ports. For this purpose, each IP port is assigned an IP address.
The only purpose of an IP address is to permit unambiguous identification of an
IP port. Therefore, each IP port must be assigned a distinct and unique IP
address.
The IP protocol does not require the IP port to be related in an unambiguous way
to a physical (communication) port. This has two main implications:
Since the IP port is actually a connection to an IP network, any number of IP

ports can share a given physical port.
An IP port may be reached through several physical ports.
By convention, the scope of IP addresses has been extended in two ways:
Note
To permit identification of IP networks

To permit simultaneous addressing of all the ports connected to a IP network
(this operation is called broadcasting).
IP Packet Structure
The information exchanged through IP networks is organized in packets. The
structure of an IP packet, as specified by IP protocol Version 4, is as follows (the
numbers are bit numbers):
0
IP
Version
(4)
IP
Header
Length
16
12
IP Type of Service
(IP TOS)
Fragment Identification
(16 bits)
20
24
28
31
Total IP Packet Length

(total number of octets in header +
payload)
Flags
(3 bits)
Fragment Offset
(13 bits)
(These fields are used for IP packet fragmentation)

Time to Live
(Range: 0 to 255;
when 0, packet is
discarded)
Number of
Upper-Layer
Protocol Carried in
Payload
(IGMP = 2)
(UDP = 17)
IP Header Checksum
Source IP Address
Options (when used)
Padding (as required)
Payload (maximum bytes: 65535 header length)
Gmux-2000 Ver. 3.2
IP Environment
C-39
IP Address Structure
An IP address is a 32-bit number, represented as four 8-bit bytes. Each byte
represents a decimal number in the range of 0 through 255.
The address is written in decimal format, with the bytes separated by decimal
points, e.g., 164.90.70.47. This format is called dotted quad notation.
An IP address is logically divided into two main portions:
Network portion
Host portion.
Network Portion
In general, the network portion is assigned by the Internet Assigned Numbers
Authority (IANA), and its main purpose is to identify a specific IP network.
There are five IP address classes: A, B, C, D, and E. However, only the A, B and C
classes are used for IP addressing. Consult your network manager with respect to
the class of IP addresses used on your network.
The network portion of an IP address can be one, two, or three bytes long, in
accordance with the IP address class.
This arrangement is illustrated below:
IP Address
Byte 1
Class A
Byte 2
Byte 3
Network Portion
Class B
Host Portion
Network Portion
Class C
Byte 4
Host Portion
Network Portion
Host Portion
The class of each IP address can be determined from its leftmost byte, in
accordance with the following chart:
Address Class
First Byte
Address Range
Class A
0 through 127
0.H.H.H through 127.H.H.H
Class B
128 through 191
128.N.H.H through 191.N.H.H
Class C
192 through 223
192.N.N.H through 223.N.N.H
where:
N indicates bytes that are part of the network portion
H indicates bytes that are part of the host portion.
C-40
IP Environment
Gmux-2000 Ver. 3.2
Host Portion
In general, the host portion is used to identify an individual host connected to an
IP network.
After obtaining an IP network address, the using organization is free to assign
host identifiers in accordance with its specific needs.
Note
The following host identifiers have special meanings, and must not be assigned
to an actual host:
The all-zeros host identifier is interpreted as a network identifier.
The all-ones host identifier is interpreted as a broadcast address. Therefore,
a message with an all-ones host identifier is accepted by all the hosts in the
network.
Subnetting
Given the scarcity of IP network addresses, for organizations operating several
relatively small, physically separated, IP networks, e.g., several departmental
networks, it is advantageous to enable several physical networks to share a
common IP network address. Small in this context means that the number of IP
ports connected to each of these networks is small relative to the host address
space for the corresponding IP address class.
The approach taken to enable the sharing of an IP network address by two or
more networks is called subnetting, which means use of subnets. The subnetting
is relevant only within the using organization, and therefore can be freely
selected to meet its specific needs.
To enable subnetting, the meaning of the bits in the host portion of the IP
address is further sub-divided into two portions:
Subnet number. For example, subnet numbers can be used to identify

departmental subnets. The subnet number follows the network identifier.
Host number the last bits of the IP address.
This subdivision is illustrated below:

Net Number
Subnet Number
Host Number
For example, when the subnet includes 16 IP hosts, only the last four bits need
to be reserved for the host number. For an organization which obtained one
global Class C network address, this means that four bits are available to identify
subnets. Therefore, this organization can implement 16 IP subnets, each
comprising up to 16 hosts (except for two subnets that are limited to 15 hosts).
Subnet Masks
Subnet masks are used to indicate the division of the IP address bits between the
net and subnet portion and the host portion.
The mask is a 32-bit word that includes ones in the positions used for net and
subnet identification, followed by zeros up to the end of the IP address.
Gmux-2000 Ver. 3.2
IP Environment
C-41
For example, the default subnet mask for any Class C address (i.e., all the eight
bits in the host address space are used for hosts in the same net) is
255.255.255.000.
However, if the same address is used in a subnet comprising up to 16 hosts and
for which the host numbers range is 00 to 15, the subnet mask changes as
follows:
IP Address
(Dotted-Quad)
192
70
55
13
IP Address (Binary)
1011 1111
0100 0110
0011 0111
0000 0111
Subnet Mask (Binary)
1111 1111
1111 1111
1111 1111
1111 0000
Subnet Mask
(Dotted-Quad)
255
255
255
240
In most applications, the binary subnet mask is built as a contiguous string of

ones, followed by a number of zeros (the number of zeros is selected as
needed, to complete the number of subnet mask bits to 32). Therefore, when
this conventional approach is used, the subnet mask can also be specified simply
by stating the number of ones in the mask. For example, the subnet mask
shown above is specified by stating that it comprises 28 bits.
IP Routing Principles
The exchange of information between IP hosts is made in packets using the
structure specified by the IP protocol. As explained in the IP Packet Structure
section above, IP frames carry, within their header, the IP addresses of the
destination and source hosts.
In accordance with the IP protocol, an IP host checks the addresses of all the
received frames, and accepts only frames carrying its own IP address as the
destination. The source address is then used to enable the destination to
respond to the source.
An IP host will also respond to broadcasts (frames whose destination host
identifier is all-ones).
Note
IP hosts support additional protocols within the IP suite, e.g., protocols used for
connectivity checking, maintenance, etc. Therefore, IP hosts will accept additional
types of messages, which are beyond the scope of this description.
When checking the destination address of an IP frame, an IP host starts by
checking the network identifier. If the network identifier is different, the host will
immediately reject the frame. Therefore, IP hosts can communicate only if they
have the same network identifier.
For example, this means that when a management station managing Gmux-2000
is connected directly, through a LAN, to the Gmux-2000 Ethernet management
port, the network identifier part of the IP address assigned to the Gmux-2000
Ethernet port must be identical to the network identifier of the management
station.
C-42
IP Environment
Gmux-2000 Ver. 3.2
To enable hosts located on different IP networks to communicate, IP routers are

needed. The routers monitor the flowing traffic and identify the IP addresses of
the local hosts connected to them, and then communicate this information to the
other routers which are known to it using special protocols. Therefore, a router
can determine to which other router to send a packet with a foreign IP address.
The user can increase the routing efficiency by specifying a default gateway to
handle IP traffic to other networks (this is always an IP router). When a default
gateway address is specified, packets with IP destinations located on other
networks are sent to the default gateway for processing: the router serving as
default gateway then sends them to their destination.
The default gateway must always be in the same IP subnet as the port sending
traffic to the gateway.
Note
As an alternative, static IP routing may also be used. To define a static route, the
user must specify the next hop, that is, IP address of the next port to which IP
packets are to be forwarded.
Tools for Checking IP Connectivity

Ping Function
The IP protocol is referred to as an unreliable connectionless packet delivery
protocol, because each packet transmitted by an IP host travels on its own
through the network until it eventually reaches its destination. To ensure reliable
delivery, higher layer protocols are used, for example, the widely-used TCP
protocol.
However, using higher layer protocols cannot provide an answer to the need to
check that it is indeed possible to reach the desired IP destination address,
because configuration errors or a network fault, for example, temporary
congestion or failure of critical communication links, may still prevent the
establishment of an IP connection. Therefore, it is often necessary to check for IP
connectivity.
The IP protocol suite includes a special protocol, the Internet Control Message
Protocol (ICMP), that enables IP hosts connected to the Internet to report a wide
range of errors and provide information about the conditions that caused the
errors. Support for this protocol is mandatory on every IP host.
ICMP includes a dedicated connectivity test procedure, implemented by means of
two types of ICMP messages: echo request and echo reply. This procedure is
often referred to as pinging: the host wanting to check IP connectivity to a
destination sends one or more ping (echo request) messages, and the
destination returns an echo reply message for each request. By comparing the
number of pings sent to the number received and the time needed for each reply
to reach the ping source, the source host can obtain useful information regarding
the transmission conditions.
Gmux-2000 Ver. 3.2
IP Environment
C-43
Trace Route
The trace route function is used to find the intermediate IP hosts (routers) that
forward IP packets to a desired destination.
The basic operation method of the trace route function is to sequentially send
ICMP echo request (ping) packets with increasing TTL (time-to-live) values:
The first set of packets have a TTL of 1 (when TTL is set to 1, an IP host will
not forward packets). Thus, only the first host on the route will respond
The next set of packets have a TTL of 2, and therefore they will pass the first
host, but not the second one. This permits identifying the IP address of the
second IP host on the route.
The process continues until the destination responds to the ICMP packets.
The round trip time of each group of packets can also be measured, to detect
excessive delays that may point to congestion on the route.
C-44
IP Environment
Gmux-2000 Ver. 3.2
C.11 MPLS Environment

Introduction to MPLS
Multi-Protocol Label Switching (MPLS) is a highly efficient and flexible routing
approach for forwarding packets over packet-switched networks, irrespective of
the protocol used to build the packets. Therefore, MPLS networks can
transparently forward IP traffic.
A router which supports MPLS is referred to as a Label Switching Router (LSR). A
network comprising interconnected LSRs is called MPLS network.
To use MPLS, network layer packets (for example, IP packets) are converted into
labeled packets by adding a label. A label is attached to each packet when it
enters an MPLS network, and any remaining labels are removed when it leaves
the MPLS network. Note however that MPLS packets do not require the presence
of a network layer header for being forwarded to a destination within the MPLS
network, or to a non-MPLS host directly attached to an LSR.
Note
To allow more complex routing capabilities, MPLS permits attaching a label stack
to each packet (a label stack is an ordered set of labels).
Within the MPLS network, forwarding actions are based only on the labels carried
by the packets. Therefore, labeled packets following a certain path can be
assigned the same label.
Forwarding within the MPLS network is performed as follows:
1. When an LSR receives a packet, it looks up the incoming packet label in a
table to determine what label to attach instead of the current label.
Note
The look up table may be preconfigured by traffic engineering personnel (static

routing), or be dynamically created using dedicated protocols.
2. The LSR replaces the existing label with the new label.
3. The LSR now sends the packet over the appropriate port to the next hop.
Therefore, the LSRs comprised in an MPLS network can forward traffic without
knowing anything about the network protocol used by the packets: only the
ingress LSR located on the edge of the MPLS network must be aware of the
network protocol of the packets it receives from the directly attached non-MPLS
hosts, whereas the egress LSR must be aware of the network protocol of the
packets it forwards to an attached non-MPLS host.
A label-switched path (LSP) connects the ingress LSR to the egress LSR. An LSP is
inherently unidirectional: for bidirectional applications, for example, voice
transport, data communication, etc., two LSPs must be associated. Different
labels may thus be used in each direction.
Since a packet is first assigned a label when it enters the network, the ingress
LSR may use, in determining the assignment, any information it has about the
packet: for example, packets arriving on different ports may be assigned different
Gmux-2000 Ver. 3.2
MPLS Environment
C-45
labels. Moreover, the ingress LSR can select the label in accordance with
considerations such as the packet precedence, or class of service.
MPLS Label Structure

Figure C-19 shows the MPLS label structure.
Byte 1
0
Byte 2
5
Byte 3
Byte 4
2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
Label
EXP
TTL
Figure C-19. MPLS Label Structure

Label
Label value (the label itself). The label is represented by 20 bits, and
thus the range allowed by the standards is 0 to 1048576.
Note that in accordance with the standards, certain values (for
example, 0, 1, 2, 3) have special meaning.
EXP
Three bits for experimental use. The value carried by these bits, which
is in the range of 0 to 7, is usually used to indicate the class of service
(7 indicates the highest priority).
Bottom of stack indicator. When using label stacks, this bit is set to 0
for all the label entries in the stack, except for the last one, in which it
is set to 1 to indicate that no other label follows. See Figure C-20 for
an example.
TTL
Time To Live, consist of 8 bits (range: 0 to 255). The TTL value is

decremented by 1 at each LSR: a packet with TTL = 0 is discarded.
MPLS Packet Structure

Figure C-20 illustrates a typical structure for MPLS packets, identifies the location
of the MPLS header, and also shows the general structure of an MPLS label stack.
Layer 2 Header
MPLS Header
Label n (most recent)
EXP
S=0
TTL
Label 2
EXP
S=0
TTL
Label 1
EXP
S=1
TTL
Additional Labels
Layer 3 Header (e.g., IP)

Layer 4 Header (e.g., UDP) Optional
Payload
Figure C-20. Typical MPLS Packet Structure

C-46
MPLS Environment
Gmux-2000 Ver. 3.2
The MPLS header is inserted after the Layer 2 (data link) header and before any
higher layer header (for example, before the Layer 3 (network layer) header
shown in Figure C-20).
As a minimum, an MPLS header consists of one label having the structure of
Figure C-19, with the S bit set to 1. An MPLS label stack consists several label
entries, each having the structure of Figure C-19, when the bottom label has its S
bit set to 1, and all the other labels have the S bit set to 0.
When an LSR receives a labeled packet, it looks up the label value at the top of
the stack. As a result of a successful lookup, the LSR learns:
1. The next hop to which the packet is to be forwarded
2. The operation to be performed on the label stack before forwarding: either
replace the top label in the stack with another, or pop (remove) an entry off
the label stack, or replace the top label stack entry and then push one or
more additional entries on the label stack.
In addition to learning the next hop and the label stack, the LSR may also learn
the outgoing data link encapsulation, and possibly other information which is
needed to properly forward the packet.
Handing over MPLS Traffic

When the last label is popped (removed) from a packet label stack (resulting in
the stack being emptied), further processing of the packet is based on the
network layer header of the packet. For example, when the network header is an
IP header, the packet can be forwarded to an IP router, which can route the
packet toward its final destination through an IP-based network.
Note that the last label can also be popped by the penultimate LSR, because it
already knows how to forward the packet to its final destination.
When MPLS hosts are directly attached to the edge LSRs, the packet MPLS label
can be directly provided by that host therefore, no IP header needs be inserted
in the packets, thereby reducing the packet overhead and increasing bandwidth
utilization efficiency. For example, in voice compression applications, RAD
supports the AAL2 over MPLS (AAL2oMPLS) encapsulation for the compressed
voice packets: this significantly decreases the overhead length.
C.12 Pseudowire Emulation

Pseudowire Emulation Techniques
Pseudo Wire Emulation Edge-to-Edge (for short, pseudowire emulation), is a
mechanism that emulates the essential attributes of a telecommunications
service (such as an E1 or T1 leased line) over a packet-switched network. From
the perspective of customers edge equipment, using pseudowire emulation
provides the characteristics of an unshared link or circuit of the chosen
telecommunications service.
Gmux-2000 Ver. 3.2
C-47
Pseudowire emulation is intended to provide only the minimum necessary

functionality to emulate the wire, and therefore the functions required of
pseudowires include encapsulating the service-specific payload into packets (for
example, bit streams, etc.) arriving at some ingress port and carrying them across
the packet-switched network over an IP path or MPLS tunnel. In some cases, it is
necessary to perform additional operations to emulate the behavior and
characteristics of the service with the required degree of faithfulness.
Gmux-2000 supports pseudowire emulation services for efficiently carrying TDM
traffic through packet-switched networks as multiple, independently routed
packet streams (internally, each packet stream carries a user-defined bundle).
Packet formats can be selected on a per-stream basis for optimal transmission
over IP- or MPLS-based networks (UDP/IP and MPLS/ETH, respectively, explained
below).
To optimally match the requirements of each application, the following protocols
are supported:
Note

accordance with RFC5087 and ITU-T Rec. Y.1413.
The suffix oPSN is often used to indicate that the packet switched network type,
IP or MPLS, does not matter with respect to the protocol characteristics (for
example, TDMoPSN is used to represent both TDMoIP and TDMoMPLS).


with RFC5086
Pseudowire Emulation over UDP/IP

The User Datagram Protocol (UDP) is a transport protocol (that is, a Layer 4
protocol in the OSI model) that provides an unreliable connectionless delivery
service. UDP uses IP to transport messages among host machines.
One of the main characteristics of UDP is support for multiple destinations within
a given host machine, which means that it enables the multiplexing of traffic from
multiple sources, for example, different software processes running on the host
machine, over the same IP link. The term used to refer to a UDP source (or
destination) is port.
UDP messages are called user datagrams. A datagram consists of two parts:
User datagram header. The UDP datagram header is divided into four 16-bit
fields that specify the port from which them was sent, the port to which the
message is destined, the message length, and a UDP checksum.
Figure C-21 shows the structure of a UDP datagram header.
C-48
Gmux-2000 Ver. 3.2

0

4
12
16
20
24
28
31
Source UDP Port (2 Bytes)
Destination UDP Port (2 Bytes)
Datagram Length (2 Bytes)
UDP Checksum (2 Bytes)
Figure C-21. Structure of UDP Datagram Header
The source and destination fields carry the 16-bit UDP protocol port
numbers used to demultiplex datagrams.
In UDP, the source port is optional: when used, it specifies the port to
which replies should be sent; if not used, it should be zero.
The length field carries the number of bytes in the complete UDP
datagram (UDP header and user data).
The UDP checksum is optional; 0 in the checksum field means that the
checksum has not been computed and the field must be ignored at the
receive side.
User datagram data field. The datagram data field can include up to 65527
bytes. This field is usually used to carry payload such as IP packets, generated
using one of the above-mentioned pseudowire emulation protocols.
Pseudowire Emulation over MPLS

MPLS can be used to transport all the types of TDM traffic, including:
Constant rate traffic: unframed, framed, and fractional data. This type of
traffic, referred to as TDM over MPLS (TDMoMPLS) also includes
uncompressed voice. Uncompressed voice is very similar to constant rate
data, except that it requires special handling of the signaling information,
which can be either CAS or CCS.
Variable rate traffic. With respect to Gmux-2000, this type of traffic includes
compressed voice, and HDLC traffic (CCS is often carried by means of HDLC).
The transport of TDM traffic uses the TDM over MPLS protocol. TDMoMPLS uses
an MPLS header before the TDMoIP data. The resulting packet structure is shown
in Figure C-22.
Tunnel Label
EXP
S=0
TTL
Pseudowire Label
EXP
S=1
TTL
TDMoIP Control Word
Payload
Figure C-22. TDMoMPLS Packet Structure

For an explanation of the general fields of the MPLS packet, refer to Section C.11.
The specific fields are explained below:
Gmux-2000 Ver. 3.2
C-49
Tunnel
Label
The tunnel label is an MPLS label that identifies the MPLS LSP used
to tunnel the TDM packets through the MPLS network (also known
as the transport label). This label is not mandatory.
Pseudowire
Label
The pseudowire label is mandatory, and it is used to carry the

circuit bundle identifier (CBID), as in TDMoIP packets.
Although the payload field of an MPLS packet can also carry IP packets that have
to cross an MPLS network, as explained in Section C.11, it can also carry payload
that has been efficiently encapsulated in one of the following formats:
AAL1 (ATM Adaptation Layer 1, described in ITU-T Rec. I.363.1). This method
enables efficient encapsulation of constant rate traffic. Constant rate traffic
is characterized by static timeslot allocation, and no activity detection.
In the AAL1 mode, the TDMoIP payload consists of between 1 and 30 48octet subframes. The number of subframes must be preconfigured, and
typically it is chosen according to latency and bandwidth constraints (see the
TDMoIP Packetizing Process section of page C-52).
AAL2 (ATM Adaptation Layer 2, described in ITU-T Rec. I.363.2) format is

especially suitable for compressed voice with activity detection, because it
enables efficient utilization of PSN bandwidth.
For TDMoIP applications, the basic AAL2 cells are concatenated in one packet,
with user-configured maximum length and maximum interval for packet filling.
HDLC: the HDLC format is used to efficiently transport HDLC payload such as
CCS (common channel signaling, for example, Signaling Scheme 7 SS7),
which is carried in specific timeslots of E1 and T1 streams. The HDLC format
is intended to operate in the port mode, transparently passing all HDLC data
and control messages over a separate pseudowire connection.
To transport HDLC, the sending gateway monitors the HDLC flags, until a
meaningful frame is detected. The contents of the frame are then transferred
to the receiving gateway, which reconstructs the original HDLC frame.
TDMoIP
TDMoIP is a pseudowire technology for emulating TDM circuits over packet
switched networks, with particular emphasis on IP networks, although it is often
used as a generic term equivalent to TDMoPSN.
TDMoIP (and for that matter TDMoPSN as well) transport capabilities include E1,
fractional E1, T1 and fractional T1 data streams, with and without
channel-associated signaling. Voice can also be transported.
The TDMoIP technology enables transmitting the continuous data stream
generated by TDM equipment as a stream of discrete packets, having a structure
suitable for transmission over packet-switched networks. The data stream
consists of individual timeslots retrieved from the E1 or T1 frame structure; each
independent set of timeslots is referred to as a bundle. The TDMoIP packets are
encapsulated in UDP packets and transported using IP (this is referred to as UDP
over IP, or UDP/IP).
C-50
Gmux-2000 Ver. 3.2
In many applications, the TDMoIP technology must transfer not only the data
stream, but also the original timing (clock rate).
Structure of TDMoIP Packets

Figure C-23 shows the structure of a basic TDMoIP packet. The packet includes
the standard IP packet header, explained in Section E.9, followed by the UDP
datagram carrying the payload, which is encapsulated in the IP packet. However,
the UDP datagram header is slightly modified relative to the standard header:
The UDP source port field is divided into two sections:
Three bits that identify the TDMoIP protocol version
The source port number field, comprising 13 bits, is used to identify the
TDMoIP bundle number. The bundle number serves as a pseudowire label.
The available range of pseudowire labels is 1 to 8063; 0 is not allowed,
the range of ports 8064 to 8190 is reserved, and 8191 is used for OAM
control messages.
The destination UDP port number is 085E.
The checksum is 0 (not calculated).
12
16
IP Version IP Header IP Type of Service

(4)
Length
(IP TOS)
20
28
31
Total IP Packet Length

(total number of octets in header + payload)
Fragment Identification
Flags
Fragment Offset
Upper-Layer
Protocol (UDP=17)
Time to Live
24
IP Header Checksum
Source IP Address
TDMoIP
Version
TDMoIP Bundle Number

(Pseudowire Label)
Destination UDP Port (085E)
UDP Datagram Length
UDP Checksum (always 0 for TDMoIP)

TDMoIP Payload
.
.
.
Figure C-23. Structure of Basic TDMoIP Packets

The TDMoIP payload section of the packet starts with a control word having the
structure shown in Figure C-24.
Byte 1
0
FORMID
Byte 2
7
M
Res
Byte 3
5
Length
Byte 4
5
Sequence Number
Figure C-24. TDMoIP Control Word Structure
Gmux-2000 Ver. 3.2
C-51
FORMID
Format identifier, comprises 4 bits, used to specify the payload

format:
0000 unspecified payload format
1100 AAL1 unstructured payload
1101 AAL1 structured payload
1110 AAL1 structured with CAS payload
1001 AAL2 payload
1111 HDLC payload
Local TDM failure indicator: can be set to 1 to indicate physical

layer loss of signal at the sending gateway, that should trigger AIS
generation towards the destination.
Remote PSN failure indicator: can be set to 1 to indicate that the

sending gateway does not receive packets from the PSN, for
example, because of a failure of the reverse direction of the
bidirectional connection, as a result of congestion or other
network-related fault. May be used to generate RDI.
Defect modifier indicator (optional).
RES
Reserved.
Length
6-bit field used to indicate the length of the TDMoIP packet, in

case padding is needed to meet the minimum transmission unit
requirements of the PSN. Must always be used when the total
packet length is less than 64 bytes.
Sequence
Number
The TDMoIP sequence number (16 bits) provides the common

pseudowire sequencing function, and enables detection of lost
and misordered packets.
Structure of Ethernet Frame Carrying TDMoIP Payload

When the TDMoIP traffic is carried over Ethernet, the basic TDMoIP packet shown
in Figure C-23 is encapsulated in the frame shown in Figure C-17 (without using
VLANs) or Figure C-18 (when using VLANs).
Essentially, this encapsulation adds the corresponding frame header before the
TDMoIP packet, and the CRC field after the packet (compare this encapsulation
with the TDMoMPLS encapsulation shown in Figure C-22).
TDMoIP Packetizing Process

This section describes the process used to build TDMoIP packets.
A simplified diagram of this process, which identifies the main steps of the
process, is shown in Figure C-25. The packetizing process (illustrated here for
Ethernet frames) comprises the following main steps:
C-52
Gmux-2000 Ver. 3.2
1. Splitting the continuous TDM data stream into discrete slices of appropriate
size. The slice size is always an integer number of bytes. For example, in
Figure C-25, the number of TDM bytes per slice, K, is 2.
2. Adding the overhead necessary to transmit each slice over the packet
network and enable reaching the desired destination. Basically, this process
includes the following steps:
1. Inserting the TDM bytes into the payload field of a UDP packet, and
adding the overhead data needed to build a UDP packet.
2. Inserting the UDP packet into the payload field of an IP packet, and
adding the overhead data needed to build an IP packet for transmission
to the desired IP destination.
3. Inserting the IP packet into the payload field of an Ethernet frame, and
adding the MAC overhead needed to build an Ethernet frame for
transmission to the destination MAC address (the MAC address needed to
reach the desired IP destination is determined using the ARP protocol).
For example, in Figure C-25 the resultant overhead comprises a total of
54 bytes.
The actual overhead depends on several factors, one of them being the encoding
method used to transmit CAS information. Figure C-25 also ignores the minimum
interpacket gap, which further increases the overhead.
Note
TDM
Frames
(8000/sec)
....
... .. ...
... .. ... ............................
48N
K
... .. ... ....

Closing
of Frame
K=2
Opening of
New Frame
Ethernet
Frames
Frame
Frame 2
Frame 1
....
Overhead
..........................
F
C
S
1 2 3 4 . . . . . . . . . . . . . . . . . . . . . N48
42 bytes
bytes
52
....
4 bytes
Payload
Figure C-25. Building an Ethernet Frame with TDMoIP Payload

The receiving end performs the steps necessary to reconstruct the original TDM
data stream from the received frames, in the best possible way, where best
means meeting a set of criteria that describe a compromise among several
conflicting requirements. A simplified diagram of this process, which identifies the
main steps of the process, is shown in Figure C-26.
Gmux-2000 Ver. 3.2
C-53

Payload
1 2 3 4 .....................
....
Overhead
N4
8
..........................
Ethernet
Frames
Start of
New Frame
F
C
S
....
End of
Frame
K=2
TDM
Frames
(8000/sec)
....
... .. ...
Frame 1
... .. ... ............................

Frame 2
... .. ... ....

Frame
48N
K
Figure C-26. Retrieving the Payload from an Ethernet Frame with TDMoIP Payload
The number of TDM bytes inserted in each Ethernet frame sent to the network,
which is actually the size of the UDP packet payload field, affects two important
performance parameters:
Bandwidth utilization: because of the relatively short TDMoIP payload, the

bandwidth utilization efficiency depends on the overhead that must be
transmitted to the PSN in order to support the transmission of a certain
amount of payload.
Packetizing delay and the associated delay variance. Bandwidth utilization

efficiency increases when using a large payload size per frame. However,
there are additional aspects that must be considered when selecting the size
of the TDMoIP payload:
Filling time: the filling time, which is the time needed to load the payload
into am Ethernet frame, increases in direct proportion to the number of
bytes in the TDMoIP payload. This is particularly significant for bundles
with few timeslots; for example, a voice channel could be carried by a
single-timeslot bundle. Considering the nominal filling rate (approximately
one byte every 0.125 msec), for E1 streams the time needed to fill a
single-timeslot bundle is as follows:
At 48 TDM bytes per frame: 5.5 msec with CAS support and 5.9 msec
without CAS support
At 384 TDM bytes per frame: 44 msec with CAS support and 47 msec
without CAS support.
For T1 streams, only 24 timeslots are available, but the filling rate is
similar (approximately one byte every 0.125 msec).
Therefore, before considering any other delays encountered along the
end-to-end transmission path, the round-trip (or echo) delay for the
voice channel example presented above is 92 msec at 384 TDM bytes per
frame (including the additional intrinsic delay of module see below).
C-54
Gmux-2000 Ver. 3.2
Such long delays may also cause time-out in certain data transmission
protocols.
Intrinsic jitter: the transmission of packets to the network is performed at

nominally equal intervals (usually, the interval is 1 msec). This means that
every 1 msec the TDMoIP packet processor sends to the network
(through the appropriate Ethernet interface) all the frames ready for
transmission. As a result, the actual payload transmission intervals vary in
an apparently random way whose peak value depends on the bundle size,
an effect called delay variance (or jitter).
For example, a bundle with 6 timeslots will fill a 48-byte payload field of
an Ethernet frame every 1 msec. If the sending instants are not perfectly
synchronized with the filling instants, the sending time will sometimes
occur just in time and sometimes will be delayed by 1 msec relative to the
ideal, creating a peak delay variance of 1 msec at the transmitting side.
The intrinsic jitter in other cases is lower, therefore the delay variance
generated by the Gmux-2000 TDMoIP modules will not exceed 2 msec.
HDLCoPSN Payload Format

The HDLCoPSN payload format is intended to enable efficient transport of HDLC
payload embedded in a TDM (E1 or T1) stream over a separate pseudowire
connection.
This format is not intended for general HDLC payloads, and assumes that the
HDLC messages are always shorter than the maximum packet size.
The HDLC mode should only be used when the majority of the bandwidth of the
input HDLC stream is expected to be occupied by idle flags. A typical application is
carrying CCS (common channel signaling, for example, Signaling Scheme 7 SS7),
which is carried in specific timeslots of E1 and T1 streams, or ISDN PEI signaling.
The HDLC format is intended to operate in the port mode, transparently passing
all HDLC data and control messages.
To transport HDLC, the sending gateway monitors the HDLC flags, until a
meaningful frame is detected. The contents of the frame are then transferred to
the receiving gateway, which reconstructs the original HDLC frame.
CESoPSN Payload Format

The CESoPSN payload format is a structure-aware format that enables
encapsulating structured (nDS0) TDM streams with or without CAS for transport
over packet-switched networks (PSN).
The CESoPSN payload format is designed to include a fixed (user-configurable)
amount of TDM data in each packet. Gmux-2000 implementation supports a
range of 1 to 45 frames of payload per CESoPSN packet: this ensures that
packets do not have to be fragmented for transmission over PSN.
Gmux-2000 Ver. 3.2
C-55
SAToPSN Payload Format

The SAToPSN payload format is a structure-agnostic format that enables
encapsulating TDM bit streams for transport over packet-switched networks
(PSN).
The SAToPSN payload format is designed to ignore any structure included in the
bit stream, and thus can transport unframed streams, as well as any stream with
proprietary or standard framing.
Using Jitter Buffers

Background
Ideally, since frames are transmitted at regular intervals, they should reach the
destination after some fixed delay. If the transmission delay through the network
were indeed constant, the frames would be received at regular intervals and in
their original transmission order.
In practice, the transmission delay varies because of several factors:
Intrinsic jitter at the transmit side, described in the TDMoIP Packetizing

Process section above
Variations in the transmission time through the network, caused by the frame
handling method: frames pass through many switches and routers, and in
each of them the frame (or the packet encapsulated in the frame) is first
stored in a queue with frames or packets from other sources, and is then
forwarded to the next link when its time arrives.
Intrinsic jitter at the receive side, due to the variation in the time needed to
extract the payload from the received packets.
Jitter Buffer Functions

Any network designed for reliable data transmission must have a negligibly low
rate of data loss. Therefore, it is reasonable to assume that essentially all the
transmitted frames reach their destination. Under these circumstances, the rate
at which frames are received from the network is equal to the rate at which
frames are transmitted by their source (provided that the measurement is made
over a sufficiently long time).
As a result, it is possible to compensate for transmission delay variations by using
a large enough temporary storage. This storage, called jitter buffer, serves as a
first-in, first-out buffer.
The buffer has two clock signals:
Write clock, used to load packets into the buffer. Since each packet is loaded
immediately after being successfully received from the network, packets are
written into the buffer at irregular intervals.
Read clock, used to transfer packets to the packet processor at a fixed rate.
The jitter buffer operates as follows:
C-56
Gmux-2000 Ver. 3.2
At the beginning of a session, the buffer is loaded with a conditioning

pattern until it is half full. No bits are read from the buffer at this time.
Therefore, a delay is introduced in the data path.
After the buffer reaches the half-full mark, the read-out process is started.
The data bits are read out at an essentially constant rate. To prevent the
buffer from either overflowing or becoming empty (underflow), the read-out
rate must be equal to the average rate at which frames are received from the
network. Therefore, the buffer occupancy remains near the half-full mark.
The buffer stores the frames in accordance with their arrival order.
Selecting an Optimal Jitter Buffer Size

For reliable operation, the jitter buffer must be large enough to ensure that it is
not emptied when the transmission delay increases temporarily (an effect called
underflow, or underrun), nor fills up to the point that it can no longer accept new
frames when the transmission delay decreases temporarily (an effect called
overflow).
The minimum size of a jitter buffer depends on the intrinsic jitter: usually, the
minimum value is 3 msec. The maximum size is 300 msec.
The theoretically correct value for the size of the jitter buffer of any given bundle
is slightly more than the maximum variation in the transmission delay through the
network, as observed on the particular link between the bundle source and the
destination. For practical reasons, it is sufficient to select a value that is not
exceeded for any desired percentage of time: for example, a value of 99.93%
means that the jitter buffer will overflow or underflow for an accumulated total
of only one minute per day.
Jitter buffers are located at both ends of a link, therefore the delay added by the
buffers is twice the selected value. The resultant increase in the round-trip delay
of a connection may cause problems ranging from inconvenience because of long
echo delays on audio circuits (similar to those encountered on satellite links) to
time-out of data transmission protocols.
Therefore, the size of each jitter buffer must be minimized, to reduce the
round-trip delay of each connection in as far as possible, while still maintaining
the link availability at a level consistent with the application requirements.
Adaptive Timing
Because of the transmission characteristics of packet switching networks, which
use statistical multiplexing, the average rate must be measured over a sufficiently
long interval. The optimal measurement interval is equal to the difference
between the maximum and minimum transmission delays expected in the
network.
As explained above, the buffer is used to store packets for an interval equal to
the maximum expected delay variation. Therefore, this buffer can be used by the
adaptive timing mechanism, to recover a clock having a frequency equal to the
average transmit rate.
The method used to recover the payload clock of a bundle is based on monitoring
the fill level of the jitter buffer: the clock recovery mechanism monitors the buffer
Gmux-2000 Ver. 3.2
C-57
fill level, and generates a read-out clock signal with adjustable frequency. The
frequency of this clock signal is adjusted so as to read frames out of the buffer
at a rate that keeps the jitter buffer as near as possible to the half-full mark. This
condition can be maintained only when the rate at which frames are loaded into
the buffer is equal to the rate at which frames are removed.
Assuming that the IP network does not lose data, the average rate at which
payload arrives will be equal to the rate at which payload is transmitted by the
source. Therefore, the adaptive clock recovery mechanism actually recovers the
original payload transmit clock.
This mechanism described above also generates a clock signal having the
frequency necessary to read-out frames at the rate that keeps the jitter buffer as
near as possible to the half-full mark.
The bundle used as the basis for recovering the adaptive clock can be selected by
the user.
C-58
Gmux-2000 Ver. 3.2
C.13 SNMP Environment

The SNMP management functions of the Gmux-2000 are provided by an internal
SNMP agent. The SNMP management communication uses the User Datagram
Protocol (UDP), a connectionless-mode transport protocol, part of the suite of
protocols of the Internet Protocol (IP). This section covers the information related
to the SNMP environment.
SNMP Principles
The SNMP management protocol is an asynchronous command/response polling
protocol: all the management traffic is initiated by the SNMP-based network
management station, which addresses the managed entities in its management
domain. Only the addressed managed entity answers the polling of the
management station. The only exception to the rule are trap messages, which are
sent by a managed entity asynchronously, to inform the management station of
a significant event.
The managed entities include a function called an SNMP agent, which is
responsible for interpretation and handling of the management station requests
to the managed entity, and the generation of properly-formatted responses to
the management station.
SNMP has evolved to include three main versions:
SNMPv1 basic SNMP version
SNMPv2 basic SNMP version, provides additional operations and enhanced

trap features
SNMPv3 adds security capabilities to be used with SNMPv1 and SNMPv2
SNMP Operations
The SNMPv1 protocol includes four types of operations:
Gmux-2000 Ver. 3.2
getRequest
Command initiated by the management station for

retrieving specific management information from the
managed entity. The managed entity responds with a
getResponse message.
getNextRequest

retrieving sequentially specific management information
from the managed entity. The managed entity responds
with a getResponse message.
setRequest

manipulating specific management information within the
managed entity. The managed entity responds with a
setResponse message.
trap
Message (alert) sent by the managed entity, carrying

unsolicited information on significant events (e.g., startup,
alarms) reported by the managed entity.
SNMP Environment
C-59
The SNMPv2 protocol includes the following additional types of operations:

getBulk

efficiently retrieving large blocks of data.
Inform
Trap (alert) sent by a management station to another

management information, which then sends a response
SNMP Traps
The Gmux-2000 SNMP agent supports the MIB-II authentication trap, and in
addition generates enterprise-specific traps for each alarm message. Traps are
also sent to notify the management station of the following events:
Resetting (warm start trap)
Change in status of the management link (up or down)
Authentication failure (use of wrong community).
Management Information Base

The management information base (MIB) includes a collection of managed
objects. A managed object is defined as a parameter that can be managed, such
as a configuration parameter, a performance statistics value, etc.
The MIB includes the definitions of relevant managed objects. Various MIBs can be
defined for various management purposes, types of equipment, etc.
An object's definition includes the range of values and the access rights:
Read-only
Object value can be read, but cannot be set.
Read-write
Object value can be read or set.
Write-only
Object value can be set, but cannot be read.
Not accessible
Object value cannot be read, nor set.
MIB Structure
The MIB has an inverted tree-like structure, with each definition of a managed
object forming one leaf, located at the end of a branch of that tree. Each leaf in
the MIB is reached by a unique path, therefore by numbering the branching points,
starting with the top, each leaf can be uniquely defined by a sequence of numbers.
The formal description of the managed objects and the MIB structure is provided in
a special standardized format, called Abstract Syntax Notation 1 (ASN.1).
Since the general collection of MIBs can also be organized in a similar structure,
under the supervision of the Internet Activities Board (IAB), any parameter
included in a MIB that is recognized by the IAB is uniquely defined.
To provide the flexibility necessary in a global structure, MIBs are classified in
various classes (branches), one of them being the experimental branch, and
another the group of private (enterprise-specific) branch. Under the private
enterprise-specific branch of MIBs, each enterprise (manufacturer) can be
assigned a number, which is its enterprise number. The assigned number
C-60
SNMP Environment
Gmux-2000 Ver. 3.2
designates the top of an enterprise-specific sub-tree of non-standard MIBs.

Within this context, RAD has been assigned the enterprise number 164.
Therefore, enterprise MIBs published by RAD can be found under
1.3.6.1.4.1.164.
MIBs of general interest are published by the IAB in the form of a Request for
Comment (RFC) document. In addition, MIBs are also often assigned informal
names that reflect their primary purpose. Enterprise-specific MIBs are published
and distributed by their originator, which is responsible for their contents.
Enterprise-specific MIBs supported by RAD equipment, including the Gmux-2000,
are available in ASN.1 format from the RAD Technical Support Department.
Management Domains Under SNMPv1 and SNMPv2

SNMPv1 and SNMPv2 enable, in principle, each management station that knows
the MIBs supported by a device to perform all the management operations
available on that device. However, this is not desirable in practical situations, so it
is necessary to provide a means to delimit management domains.
SNMP Communities
To enable the delimitation of management domains, SNMPv1 and SNMPv2 use
communities. Each community is identified by a name, which is a case-sensitive
alphanumeric string defined by the user. Any SNMP entity (this term includes
both managed entities and management stations) can be assigned by its user
community names.
Access Restriction Using SNMP Communities

In general, SNMPv1 and SNMPv2 agents support two types of access rights:
Read-only: the SNMP agent accepts and processes only SNMP getRequest and
getNextRequest commands from management stations which have the same
read-only community name.
Read-write: the SNMP agent accepts and processes all the SNMP commands
received from a management station with the same write community name.
For each SNMP entity it is possible to define a list of the communities which are
authorized to communicate with it, and the access rights associated with each
community (this is the SNMP community name table of the entity).
For example, the SNMP community name table of the Gmux-2000 SNMP agent
can include three community names.
In accordance with the SNMP protocol, the SNMP community of the originating
entity is sent in each message.
When an SNMP message is received by the addressed entity, first it checks the
originator's community: if the community name of the message originator differs
from the community name specified for that type of message in the agent, the
message it discarded (SNMP agents of managed entities report this event by
means of an authentication failure trap).
Gmux-2000 Ver. 3.2
SNMP Environment
C-61
Gmux-2000 Communities
When using SNMPv1 and SNMPv2 without SNMPv3 security features, the SNMP
agent of the Gmux-2000 is programmed to recognize the following community
types:
Read
SNMP community that has read-only authorization, i.e., the SNMP

agent will accept only getRequest and getNextRequest
commands from management stations using that community.
Write
SNMP community that has read-write authorization, i.e., the

SNMP agent will also accept setRequest commands from
management stations using that community.
Trap
SNMP community which the SNMP agent will send within trap
messages.
SNMPv3 Capabilities
SNMPv1 and SNMPv2 can neither authenticate the source of a management
message, nor provide privacy (encryption).
To overcome these shortcomings, SNMPv3 provides a security framework for
SNMPv1 and SNMPv2 that adds the following main capabilities:
Security features:
Authentication checks the integrity of management data and verifies its

origin, and thus ensures that unauthorized users cannot masquerade as
authorized users
Privacy ensures that unauthorized users cannot monitor the

management information passing from managed systems to the
management system
Authorization and access control ensures that only authorized users

can perform SNMP network management functions and contact the
managed entities.
Administrative features:
Naming of entities
People and policies
Usernames and key management
Notification destinations
Proxy relationships
Remote dynamic configuration of agents via SNMP operations.
SNMP Engine ID
An important parameter defined in relation with SNMPv3 is the SNMP engine ID, a
unique and unambiguous identifier of the function that processes SNMP
messages (it thus also identifies the SNMP entity that corresponds to that
engine).
C-62
SNMP Environment
Gmux-2000 Ver. 3.2
The SNMP engine ID is a string that has an automatically-generated part, and a

user-defined part, which must be unique within the SNMP-managed network.
Gmux-2000 supports text entry for the user-defined part.
The automatically-generated part of the SNMP engine ID changes after each
restart (reboot) of the SNMPv3 protocol. For reasons explained below in the
SNMPv3 Administrative Features section, the SNMP engine ID is the first
parameter to be set whenever SNMPv3 is used and the configuration data and
authorized users must be reconfigured.
SNMPv3 Message Processing

SNMPv3 message processing requires two mechanisms (models): the message
processing model, and a specific security model.
The message processing model performs the following tasks:
In the transmit direction: accepts SNMP protocol data units (PDUs) from the
SNMP agent central processor, encapsulates them in messages, and then
subjects the message to the security model, to insert security-related
parameters in the message header
In the receive direction: accepts incoming messages, uses the security model
to process the security-related parameters in the message header, and
delivers the encapsulated PDU to the SNMP agent central processor
The message processing models supported by Gmux-2000 are as follows:
SNMPv1
SNMPv2c: SNMPv2 with community-based security model
SNMPv2u: SNMPv2 with user-based security model (USM)
SNMPv3
The security models available for Gmux-2000 are as follows:
SNMPv1
SNMPv2c: SNMPv2 with community-based security model
User-based security model (USM)
The user can also enable using any of the above-mentioned models, to match
different management station capabilities: the appropriate model is automatically
selected, in accordance with the model used in the incoming SNMP message.
User-Based Security Model (USM)

The USM, defined in RFC2272, provides authentication and privacy services for
SNMP, to protect against modification of information in transit from an
authorized entity (including modification of message order, delaying or replaying
of valid messages to change their effect, etc.), prevent an unauthorized entity
from performing management operations by assuming the identity of an
authorized entity, and prevent disclosure of the contents of the messages
exchanged between a management station and an agent.
To achieve these goals, USM uses authentication to check the integrity of
transmitted messages, and encryption to prevent disclosure:
Gmux-2000 Ver. 3.2
SNMP Environment
C-63
Authentication mechanisms. Mechanisms that provide integrity checks based

on a secret key are usually called message authentication codes (MAC).
Typically, message authentication codes are used between two parties that
share a secret key in order to validate the information transmitted between
these parties. Therefore, an SNMP engine requires an authentication key and
a privacy key. Separate values of these two keys are maintained for each
local and remote user, and their values must be stored by each user, because
the keys are not accessible via SNMP.
USM authentication protocol is based on the key-Hashing Message
Authentication Code (HMAC), described in RFC2104. HMAC uses a userselected secure hash function and a secret key to produce a message
authentication code. USM allows the use of one of two alternative
authentication protocols, where both generate a 96-bit output that is used
to check message integrity:
HMAC-MD5-96: HMAC is used with MD5 (Message Digest algorithm 5) as

the underlying hash function.
HMAC-SHA-96: HMAC is used with SHA-1 (Secure Hashing Algorithm 1).
Encryption mechanism. USM uses the cipher block chaining (CBC) mode of the
Data Encryption Standard (DES) for encryption, with a key length of 56 bits.
SNMP Security Level

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

The administrative features of SNMPv3 enable determining the entities (users)
that are allowed to manage an entity, for example, the Gmux-2000.
User management. During SNMPv3 configuration, it is necessary to define the

allowed users. For each user, it is possible to select the security level, and the
passwords used for each type of protection (authentication and/or privacy)
needed at the selected level.
Note that the password is only one of the parameters used to automatically
create keys: another parameter is the SNMP engine ID. Therefore, you must
configure the desired SNMP engine ID before starting to define users.
C-64
Target management. As part of the SNMPv3 configuration, you can also

define the managers list. For each manager, you can specify a message
processing model, a security model, and the required security level. You can
also define a list of tags (traps) that can be sent to the corresponding target.
SNMP Environment
Gmux-2000 Ver. 3.2
Index
1
1+1 unidirectional protection, 2-30
1+1 unidirectional protection configuration, 5-63
1-to-1 bidirectional module protection, 2-36
1-to-1 bidirectional port protection, 2-35
1-to-1 bidirectional protection configuration, 5-69
1-to-N protection mode, 2-37
A
AC power, 3-29
connector data, A-6
Accounting Port, 5-25
Adaptive timing, C-57
Admin Status, 5-135
AIS, C-5
Alarms, 7-48
alarm attributes, 7-39
alarm buffer, 7-37
alarm input relay, 7-48
alarm priority, 7-43
alarm relays, 7-37
alarm reporting, 7-47
alarm threshold window, 7-46
alarm thresholds, 7-44
bundle, 7-66
connector data, A-4
E1-PW/28 module, 7-64
E1-PW-SRV/21 module, 7-64
GbE module, 7-59
handling, 7-38
interpreting, 7-55
monitoring, 7-53
pseudowire emulation server module, 7-64
STM1 module
External SDH Port, 7-60
Internal VC-12 Port, 7-63
Internal VC-4 Port, 7-61
System and CONTROL module, 7-55
VC-E1/12 module, 7-67
Alignment Errors, 7-16
Applications
pseudowire emulation services for TDM
transport, 1-10
typical configuration procedure
inband management via voice compression
TDM links, 6-29
transport of framed bundle from E1 trunk, 611
transport of unframed bundle from E1 trunk,
6-3
transport of unframed bundle from SDH
network, 6-15
Gmux-2000 Ver. 3.2
voice trunking application, 6-19

voice compression services, 1-11
APS, 2-29
1+1 unidirectional protection configuration
CH Num, 5-68
Config Mode, 5-65
Interface, 5-68
Name, 5-65
Priority, 5-69
Recovery Mode, 5-66
STM-1 SD Flip Criteria, 5-66
Time to Restore in sec, 5-66
1-to-1 bidirectional APS configuration, 5-74
APS Configuration (GbE ports), 5-74
APS Mapping (GbE ports), 5-78
1-to-1 bidirectional module protection
configuration
1-to-1 bidirectional port protection
configuration, 5-73
Config Mode, 5-74
Name, 5-74
Recovery Mode, 5-74
Time to Restore, 5-74
1-to-N protection configuration, 5-76
Config Mode, 5-77
Name, 5-77
Recovery Mode, 5-77
Time to Restore, 5-77
APS Configuration (STM1 ports), 5-64
APS Mapping (STM1 ports), 5-66
displaying APS interfaces, 5-145
displaying status, 5-146
link aggregation configuration, 5-70
CH Num, 5-72
Config Mode, 5-71
Interface, 5-72
Name, 5-71
Priority, 5-72
PSN interface, 2-33
link aggregation, 2-34
SDH interface, 2-29
Authentication Failure Trap, 5-41
Authentication Port, 5-25
Authentication/Community, 5-41
I-1
Index
B
Backplane Type, 5-131
Blank panels
installation, 3-25
Brackets, 3-26
Bundle
Bundle Counters, 7-17
bundle types, 2-24
configuration parameters, 2-26
configuration procedure, 5-79
maximum number in storage, 2-24
maximum number of active connections
Layer 4 pools, 2-25
maximum number of active connections, 2-24
Monitoring
Statistics
connection parameters for TDMoIP bundles,
7-11
Status, 7-17
Bundle configuration parameters
TDMoIP, 2-26
TDMoIP CV, 2-28
Bundle ID, 7-18
C
Cable connections, 3-28
Card Type, 5-13
CES bundle
configuration procedure
MPLS/ETH networks, 5-102
UDP/IP networks, 5-101
timeslot assignment
individual timeslots, 5-120
CESoPSN, C-55
Check Sanity, 5-4
Choose DB Number, 5-4
Clock interface
selection, 3-22
Clock Source, 5-55
Ext Clock Interface, 5-59
Ext In/Out Clk Mode, 5-59
Ext Out Clock State, 5-59
Fallback Clock, 5-56, 5-59
Master Clock, 5-56
System A, 5-56
Configuration
System
Management SNMPv3 Settings, 5-43
Configuration errors, 7-26
Configuration menu, 4-22, 5-2
Configuration procedure
1-to-1 bidirectional module protection mode, 574
1-to-1 bidirectional port protection mode, 5-73
Alarms, 7-38
bundles, 5-79
CES bundle parameters
I-2

Connections, 5-79
control subsystem redundancy, 5-62
Date & Time Parameters, 5-35
Ethernet port parameters, 5-16
external clock interfaces, 5-59
global management access rights, 5-19
HDLC bundle parameters
UDP/IP Networks, 5-97
I/O Redundancy
PSN Interface Subsystem, 5-69
SDH interface subsystem, 5-63
IP communication parameters, 5-16
Link Aggregation, 5-70
Logistic Parameters, 5-30
management access parameters, 5-18
manager list parameters, 5-26
add new manager, 5-26
edit existing manager/static route destination
station, 5-30
nodal timing references, 5-55
Physical Layer parameters, 5-54
RADIUS server, 5-24
Redundancy, 5-61
SAToPSN bundle parameters
serial port parameters, 5-14
SNMP Management, 5-39
SNMP Management Parameters, 5-40
station clock interfaces, 5-59
syslog
syslog server parameters, 5-32
syslog system address, 5-31
System Parameters, 5-8
system timing flow, 5-55
TDMoIP (CE) bundle parameters
TDMoIP (CV) bundles, 5-103
general parameters, 5-108
routing parameters, 5-105
voice parameters, 5-110
TS Assignment, 5-119
TS Assignment for Voice Compression Modules,
5-124
Data Ports, 5-127
voice ports, 5-125
user access rights, 5-20
user authentication, 5-24
user parameters, 5-18
Configuration sequence
for new Gmux-2000, 5-6
Configuration>Connection submenu
CESoPSN bundles, 4-30, 5-83
HDLC bundles, 5-82
HDLCoPSN bundles, 4-29
SAToPSN bundles, 4-27, 5-81
TDMoIP (CE) bundles, 4-27, 5-81
TDMoIP (CV) bundles, 4-28, 5-84
Configuration>System submenu, 4-23, 4-24, 4-26,
5-9, 5-10, 5-11, 5-12
Configuration>TS Assignment, 4-31, 5-120
Gmux-2000 Ver. 3.2

Connection
Bundle ID, 5-86
Connection Configuration, 5-86
Connection Mode, 5-86
Connections to
alarm port, 3-9
CONTROL module, 3-8
CONTROL-DCE connector, 3-21
E1 port, 3-6
PSN, 3-7
SDH port, 3-7
station clock, 3-8
Connectivity Status, 7-18
CONTROL DCE
connection data, A-1
connector, 3-21
connector data, A-1
CONTROL ETH
connector data, A-3
CONTROL module, 1-23
ACT indicator, 3-21
connections, 3-30
CONTROL-DCE connector, 3-21
CONTROL-ETH connector, 3-21
FLT indicator, 3-21
installation, 3-24
jumpers, 3-22
panel, 3-21
removal, 3-24
replacing during operation, 3-24
SD indicator, 3-21
STATION CLOCK connector, 3-21
STATION CLOCK IN connector, 3-21
STATION CLOCK OUT connector, 3-21
SW1, 3-23
Copying files, 5-157
D
Data Bits, 5-15
Data ports
TS assignment, 5-127
subchannel (entire port), 5-129
Database Tools
create additional database, 5-5
create new database, 5-4
factory defaults
reload, 5-5
load database, 5-5
load hardware, 5-5
Date & Time
NTP, 5-36
NVRAM, 5-35
DBxCONF.BAK, 5-3
DBxCONF.CFG, 5-3
DBxCONF.OL, 5-3
DC power, 3-29
connector data, A-6
Deleting files, 5-159
Destination IP Address, 7-18
Device Info, 5-31
Sys Contact, 5-31
Sys Description, 5-31
Sys Location, 5-31
Gmux-2000 Ver. 3.2
Index
Sys Name, 5-31
Diagnostics
loopback activation, 7-85
overview, 7-71
ping, 7-81, 7-82, 7-85
trace route, 7-81, 7-82, 7-84
Diagnostics menu, 4-33
task selection, 7-82
Dir function, 5-156
Download software
boot menu, B-2, B-8
TFTP, B-10
overview, B-1
TFTP, B-3
Activate TFTP, B-5
Client file name, B-5
File download, B-5
File upload, B-5
Internal download, B-6
preparations, B-3
Server file name, B-5
Slots files, B-6
Start Sw load, B-7
TFTP retry timeout, B-5
TFTP server IP, B-5
TFTP total timeout, B-5
Xmodem, B-8
preparations, B-8
procedure, B-8
Send File, B-9
Transfer, B-9
E
E1
CAS, C-4
CRC-4, C-4
framing, C-3
FRAMED G.704, C-3
FRAMED-MF, C-4
line alarms, C-5
line signal characteristics, C-2
signal structure, C-2
timeslot 0, C-3
E1-PW/28 module, 1-27
indications, 4-4
E1-PW-SRV/21 module, 1-25
indications, 4-4
Error, 7-26
ESD, 3-3
ESF, C-7
Ethernet
autonegotiation, C-35
bridging, C-37
frame structure, C-36
FCS, C-36
length/type, C-36
MAC
DA, C-36
SA, C-36
MAC client data, C-36
padding, C-36
preamble, C-36
SFD, C-36
introduction, C-33
I-3
Index
LAN, C-33
media access, C-34
protocol description, C-34
virtual LAN (VLAN, C-37
Event Log, 7-49
Clear log, 7-51
Alarm buffer type, 7-52
Alarm level, 7-52
Alarm priority, 7-52
Read log file, 7-50
Exist, 5-135, 5-136
EXP bits, C-46
Ext Clock Interface, 5-60
Ext In/Out Clk Mode, 5-60
Ext Out Clock Source, 5-60
Ext Out Clock State, 5-60
F
Factory Default, 5-4
Fan Inventory
Exist, 5-143
Operation Status, 5-143
Status, 5-143
Fan tray, 3-14
installation, 3-15
FCS Errors, 7-16
Features, 1-2
alarm monitoring and reporting, 1-9
Gmux-2000 control functions, 1-8
Gmux-2000 timing, 1-9
power supply, 1-9
pseudowire CE services, 1-5
PSN interfaces, 1-3
SDH interfaces, 1-4
Voice trunking services, 1-6
Format flash disk, 5-159
Frame Too Long, 7-16
Frames Rx from PSN, 7-18
Frames Tx to PSN, 7-18
Framing
ESF, C-7
SF (D4), C-7
Frequently Asked Questions, 7-87
Full Control, 5-22
G
GbE module, 1-29
indications, 4-3
Gmux-2000
alarm interfaces, 2-46
block diagram
TDM pseudowire emulation, 1-16
voice compression, 1-17
configuration sequence, 5-6
installation, 3-21
fan tray
description, 3-14
installation, 3-15
front panel, 1-18, 3-12
functional description, 2-1
TDM traffic flow, 2-2
TDM transport services, 2-1
TDMoIP packet processing, 2-4
I-4

I/O modules, 1-24
E1-PW/28, 1-27
E1-PW-SRV/21, 1-25
GbE, 1-29
STM1, 1-24
VC-E1/12, 1-30
VC-E1/16, 1-30
indicators, 3-12
installation
bracket attachment, 3-26
enclosure, 3-26
management, 2-44
management subsystem, 2-44
modules list, 1-21
package contents, 3-10
additional equipment needed, 3-10
patch panels, 3-6
Patch-28B, 3-6
Patch-28UB, 3-6
PI module
description, 3-16
installation, 3-16
PS module, 1-22
installation, 3-17
rear panel, 1-19
redundancy
PSN interface, 2-33
slot utilization, 1-21
specifications, 1-34
timing subsystem, 2-39
block diagram, 2-39
Grounding, 3-2, 3-28
H
Handling Service Problems
troubleshooting, 7-25
Hardware Problems
troubleshooting, 7-22
HDLC bundle
timeslot assignment
range of timeslots, 5-122
HDLC statistics, 7-20
HDLCoPSN, C-55
HDLCoPSN bundle
timeslot assignment
entire port, 5-123
Host IP, 5-17
Default Gateway, 5-18
IP Address, 5-18
IP Mask, 5-18
HW, 5-133
HW Version, 5-136
I
I/O Inventory, 5-132
Admin Status, 5-138
Component Details, 5-138
Exist (module), 5-138
HW Description, 5-138
Gmux-2000 Ver. 3.2

HW Revision, 5-138
I/O Slot, 5-138
Module Name, 5-138
Operation Status (module), 5-138
Port Information, 5-138
SW Description, 5-138
SW Revision, 5-138
I/O modules, 1-24
E1-PW/28, 1-27
E1-PW-SRV/21, 1-25
GbE, 1-29
installation, 3-25
STM1, 1-24
VC-E1/12, 1-30
VC-E1/16, 1-30
Indications
normal
CONTROL ETH interface status, 4-3
E1-PW/28 status, 4-4
E1-PW-SRV/21 status, 4-4
PSN interface (GbE) status, 4-3
SDH interface (STM1) status, 4-4
system, 4-3
VC-E1/12 status, 4-4
VC-E1/16 status, 4-4
Input Voltage, 5-135
Installation
blank panels, 3-25
bracket attachment, 3-26
connecting AC power, 3-29
connecting DC power, 3-29
connecting to CONTROL module, 3-30
connecting to I/O modules, 3-30
clock interface selection, 3-22
panel, 3-21
factory-default
restore parameters, 3-23
fan tray, 3-15
Gmux-2000
cable connections, 3-28
rear panel, 3-13
Gmux-2000 enclosure, 3-26
brackets for 19 in. racks, 3-26
brackets for ETSI racks, 3-27
grounding, 3-28
I/O modules, 3-25
PI module, 3-16
PS module, 3-17
panel, 3-17
Inventory, 5-130
Bundle, 5-140
Clock, 5-144
Clock State, 5-145
Exist, 5-144
PLL Lock, 5-144
Status, 5-144
Waiting for Sync, 5-144
Fan Device, 5-142
I/O, 5-136
I/O Slot details, 5-137
Port Information, 5-138
menu, 4-21
Redundancy
APS group ID, 5-146, 5-147
Gmux-2000 Ver. 3.2
Index
APS group Name, 5-147
APS group status, 5-146
APS interfaces, 5-145
APS Port Status, 5-146
Flip Cause, 5-147
Flip Date, 5-147
Flip Time, 5-147
Online port, 5-146
Switched Channel, 5-147
System, 5-130
CL, 5-135
I/O Inventory, 5-132
PS, 5-134
SW/HW Revision, 5-134
System information, 5-131
IP environment
IP address, C-39
IP address structure
host portion, C-41
network portion, C-40
subnet masks, C-41
subnetting, C-41
IP connectivity check, C-43
IP hosts, C-38
IP networks, C-38
IP packet, C-39
IP ports, C-38
IP routing, C-42
ping, C-43, C-44
J
Jitter
Jitter
Jitter
Jitter
Jitter
Buffer Overflows, 7-18

Buffer Overflows Seconds, 7-12
Buffer Underflows, 7-18
Buffer Underflows Seconds, 7-11
buffers, C-56
L
Laser safety, 3-3
Layer 4 pools, 2-25
Link aggregation, 2-34
Load Database, 5-4
Load Hardware, 5-4
Log, 7-48
Loopbacks
E1-PW/28 module
local, 7-75
remote, 7-75
E1-PW-SRV/21 module
local, 7-74
remote, 7-73
STM-1 port
local, 7-73
remote, 7-72
VC-E1/12
test tone injection, 7-79
VC-E1/12 data port
remote, 7-79
VC-E1/12 voice port
local, 7-77
remote, 7-76
VC-E1/16
test tone injection, 7-79
VC-E1/16 data port
I-5
Index
remote, 7-79
VC-E1/16 voice port
local, 7-77
remote, 7-76
M
MAC Address, 5-136
Major Alarm State, 5-131
Major LED, 7-48
Management Access, 5-19, 5-24
local authentication, 5-24
remote and local authentication, 5-24
remote authentication, 5-24
SNMP Access, 5-19
Disabled, 5-19
Enabled, 5-19
Managers Only, 5-19
Telnet/SSH Access, 5-19
Disabled, 5-19
Enable Secure, 5-19
Enabled, 5-19
Managers Only, 5-19
Managers Only Secure, 5-19
User Access, 5-20
add new user, 5-21
Password, 5-21
Permission, 5-21
Management subsystem
CONTROL module
Ethernet port, 2-45
functions, 2-44
redundancy, 2-46
serial port, 2-46
external alarm interfaces, 2-46
Manager List, 5-26
Interface, 5-28
IP Address, 5-28
Next Hop, 5-28
Trap, 5-28
VLAN ID, 5-29
VLAN Priority, 5-29
VLAN Valid, 5-28
Manufacturer, 5-135
Master Clock
Ext In-1, 5-57
Ext In-2, 5-57
Internal, 5-57
None, 5-57
Rx Clk, 5-57
Max Jitter Buffer Deviation, 7-12
Max Jitter Buffer Level, 7-12, 7-18
Menu structure
CESoPSN bundles, 4-30, 5-83
HDLC bundles, 5-82
HDLCoPSN bundles, 4-29
SAToPSN bundles, 4-27, 5-81
TDMoIP (CE) bundles, 4-27, 5-81
TDMoIP (CV) bundles, 4-28, 5-84
Configuration>System submenu, 5-9, 5-10, 511, 5-12
I-6

Configuration>System submenu, 4-23, 4-24, 426
Configuration>TS Assignment submenu, 4-31, 5120
Inventory menu, 4-21
main menu, 4-20
Monitoring menu, 4-32
Utilities menu, 4-34, 5-148
Min Jitter Buffer Level, 7-12, 7-18
Minor Alarm State, 5-131
Minor LED, 7-48
Module Name, 5-135
Alarm, 7-53
Event Log, 7-49
Clear log, 7-51
Read log file, 7-50
Statistics, 7-3
Connection for TDMoIP (CE) Bundles, 7-10
Physical Layer, 7-4
Status, 7-12
Bundle Counters, 7-17
bundles, 7-17
Connection, 7-17
Physical layer, 7-12
task selection, 7-3
Monitoring power-up sequence, 4-1
MPLS
introduction, C-45
label structure, C-46
EXP bits, C-46
label value, C-46
S bit, C-46
TTL, C-46
packet structure, C-46
N
Nodal Clock, 5-131
NTP, 5-36
Number of Retries, 5-25
NVRAM, 5-35
O
Online Database, 5-131
Operation
turn on, 4-2
Operation Status, 5-136
Operational Status, 5-135
Overview, 1-1
P
Package contents, 3-10
additional equipment needed, 3-10
Parity, 5-15
Password, 5-21
PDH environment, C-1
Permission, 5-21
PI module
installation, 3-16
Ping function, 7-81, 7-82
Pop Alarm, 5-15
Gmux-2000 Ver. 3.2

Power requirements
AC, 3-5
DC, 3-5
Power supply subsystem, 2-47
Product Name, 5-131
Protection
1-to-1 bidirectional protection, 2-35
1-to-N protection, 2-37
PS Inlet Type, 5-131
PS module, 1-22
installation, 3-17
removal, 3-20
pseudowire emulation
CESoPSN, C-55
HDLCoPSN, C-55
SAToPSN, C-56
TDMoIP, C-50
Pseudowire emulation
introduction, C-47
MPLS, C-49
TDMoMPLS, C-49
UDP, C-48
UDP/IP, C-48
Q
Q.50 overview, 2-22
R
RADIUS Client, 5-24
RADIUS server, 5-24
Read Community, 5-41
Read only, 5-22
Redundancy
CL, 5-62
AUTO, 5-62
CL-A, 5-62
CL-B, 5-62
PSN interface, 2-33
SDH interface
1-to-N protection, 2-37
Relay-1, 7-48
Relay-2, 7-48
Remote, 5-24
Remote&Local, 5-24
Renaming files, 5-158
Report, 7-48
Reset functions, 5-154
Rx Broadcast ok, 7-15
Rx Correct Octets, 7-15
Rx Correct pkts, 7-15
Rx Correct Unicast pkts, 7-15
Rx Discard pkts, 7-15
Rx Iface Errors, 7-15
Rx Multicast ok, 7-15
Rx Pause Frames, 7-17
Rx Unknown Protocol, 7-15
Gmux-2000 Ver. 3.2
Index
S
Safety, 3-1
ESD, 3-3
grounding, 3-2
laser radiation, 3-3
module handling, 3-4
Sanity errors
list, 7-27
SAToPSN, C-56
bundle configuration procedure
SDH
AU pointers, C-22
maintenance signals, C-28
AIS, C-28
alarms, C-29
FERF, C-28
HO Path FERF, C-29
HO Path RAI, C-29
LO Path FERF, C-29
LO Path RAI, C-29
LOF, C-28
LOP, C-28
LOS, C-28
MS-FERF, C-28
OOF, C-28
MSOH, C-22
overhead data, C-20
principles, C-14
section overhead, C-16
frame organization, C-16
tributary units, C-25
SDH multiplexing, C-26
types, C-25
VC (virtual container), C-16
VC assembly/disassembly, C-17
VC-4 path overhead, C-23
Sequence Errors, 7-18
Sequence Errors Seconds, 7-11
Server IP Address, 5-25
SF (D4), C-7
Shared Secret, 5-25
Site requirements, 3-4
AC power, 3-5
ambient, 3-9
connections
alarm port, 3-9
E1, 3-6
Ethernet management port, 3-8
optical cables, 3-8
PSN, 3-7
SDH, 3-7
serial port, 3-8
station clock, 3-8
DC power, 3-5
electromagnetic compatibility, 3-10
front and rear panel clearance, 3-9
SNMP, 4-36
community, C-61
management domains, C-61
principles, C-59
requirements, 4-36
I-7
Index
traps, C-60
SNMP Engine ID Access, 5-42
SNMPv3 Setting
Summary Target Table, 5-52
Summary User Table, 5-52
Targets & Notify, 5-46
Notify, 5-49
Target Address, 5-48
Target Params, 5-47
Trap, 5-50
Users, 5-44
Software downloading
TFTP, B-3
SONET, C-32
Specifications
Gmux-2000 environment, 1-49
Gmux-2000 management, 1-47
Gmux-2000 physical data, 1-50
Gmux-2000 power requirements, 1-49
Gmux-2000 station clock interface, 1-47
Gmux-2000 system, 1-34
Speed, 5-15
SSH, 4-35
general procedures, 4-35
STATION CLOCK
connector data, A-5
statistics
E1 group HDLC, 7-20
T1 group HDLC, 7-20
Statistics
Connection
connection parameters for TDMoIP bundles, 711
Connection for TDMoIP (CE) Bundles, 7-10
CV, 7-9
Elapsed Time, 7-8
ES, 7-9
Interval Number, 7-8
LCV, 7-10
Physical Layer, 7-4
performance monitoring parameters, 7-8
SEFS, 7-9
SES, 7-9
UAS, 7-9
Valid Intervals, 7-8
Status
Physical layer, 7-12
GbE modules, 7-12
GbE Port Counters, 7-15
GbE Switch Frame Type Counters, 7-16
GbE Switch Pause Counters, 7-17
task selection, 7-12
STATUS, 5-133
STM-1
overhead data, C-20
RSOH, C-21
path overhead, C-21
performance monitoring, C-31
pointers, C-19
correcting timing differences, C-19
VC-4, C-19
section overhead, C-18, C-20
I-8

VC (virtual container), C-18
STM1 module, 1-24
indications, 4-4
Stop Bits, 5-15
Supervision terminal, 4-13
ending terminal session, 4-19
menu structure
Configuration>Connection submenu (CESoPSN
bundles), 4-30, 5-83
Configuration>Connection submenu (HDLC
bundles), 5-82
(HDLCoPSN bundles), 4-29
Configuration>Connection submenu (SAToPSN
bundles), 4-27, 5-81
Configuration>Connection submenu (TDMoIP
(CE) bundles), 4-27, 5-81
Configuration>Connection submenu (TDMoIP
(CV) bundles), 4-28, 5-84
Configuration>System submenu, 4-23, 4-24,
4-26, 5-9, 5-10, 5-11, 5-12
Configuration>TS Assignment submenu, 4-31,
5-120
Inventory menu, 4-21
main menu, 4-20
power-up process, 4-15
terminal screen description, 4-15
terminal screens
bottom line, 4-16
header, 4-15
save, 4-16
status indicator, 4-15
UPD DB, 4-19
work area, 4-15
SW, 5-133
SW Version, 5-136
Sys Location, 5-131
Sys Name, 5-131
Sys Up Time, 5-131
Syslog Configuration, 5-33
Syslog Statistics, 5-34
System configuration
Alarms, 7-38
Card Type, 5-13
Clock source, 5-55
configuration options, 4-5
control subsystem redundancy, 5-62
Date & Time, 5-35
Ethernet port parameters, 5-16
I/O redundancy
1-to-1 bidirectional module protection mode,
5-74
1-to-1 bidirectional port protection mode, 573
Gmux-2000 Ver. 3.2

1-to-N protection protection mode, 5-76
PSN interface subsystem, 5-69
SDH interface subsystem, 5-63
IP communication parameters, 5-16
Host IP, 5-17
log-in, 4-6
logistic parameters, 5-30
management access, 5-18
global management access rights, 5-19
user access rights, 5-20
management access parameters
User Access, 5-20
manager list, 5-26
managing databases, 5-3
preliminary configuration, 4-5
preliminary configuration (terminal), 4-5
preliminary configuration sequence, 4-8
program modules, 5-13
general procedure, 5-13
VC-E1/12, 5-13
VC-E1/16, 5-13
serial port parameters, 5-14
SNMP
requirements, 4-36
SNMP management, 5-40
Authentication/Community, 5-41
SSH, 4-35
supervision terminal, 4-13
overview, 4-13
syslog
syslog server parameters, 5-32
syslog system address, 5-31
Telnet, 4-35
requirements, 4-35
timing flow
external clock interfaces, 5-59
nodal timing references, 5-55
station clock interfaces, 5-59
users, 5-18
System utilities, 5-155
T
T1
alarms, C-7
line signal, C-5
T3
line alarms, C-13
line signal, C-8
asynchronous DS3 C-bit parity signal, C-12
asynchronous DS3 C-bit parity signal
maintenance, C-12
DS2 tributary, C-10
M13 multiplex signal, C-11
M-subframe, C-8
M-subframe blocks, C-10
SYNTRAN signal, C-12
TDM over MPLS, C-49
TDMoIP, C-50
Gmux-2000 Ver. 3.2
Index
Ethernet frame with TDMoIP payload, C-52
jitter buffers, C-56
packetizing process, C-52
frame filling time, C-54
intrinsic jitter, C-55
packets, C-51
TDMoIP (CE) bundle
Adaptive Clock, 5-94, 5-95
Connection State, 5-90, 5-94
Dest CBID, 5-90
Destination Bundle, 5-95
Destination IP, 5-93, 5-95
Far End Type, 5-92, 5-95
Inbound Label Tagging, 5-95
Inbound Tunnel Label, 5-96
IP TOS, 5-93
Jitter Buffer in Ms, 5-91, 5-95
Jitter Buffer Size, 5-97
Network Slot Port, 5-93, 5-95
Next Hop, 5-93, 5-95
OAM Connectivity, 5-91
OAM Indication, 5-91
OOS L Bit Mode, 5-92, 5-95
Outbound EXP Bitsl, 5-95
Outbound Label Tagging, 5-95
Outbound Tunnel Label, 5-95
Payload Format, 5-90
Payload Type, 5-92, 5-95
Sensitivity, 5-91
Source Bundle, 5-95
Source CBID, 5-90
TDM Byte in Frame, 5-91, 5-95
TDM Byte per Frame, 5-96
timeslot assignment
entire port, 5-123
VLAN ID, 5-94, 5-96
VLAN Priority, 5-96
VLAN Priority, 5-94
VLAN Tagging, 5-94, 5-96
TDMoIP (CV) bundle
Advanced Voice Parameters, 5-118
Caller ID Type, 5-111
CNG Mode, 5-118
Coder/Rate (kbps), 5-111
Coding, 5-117
general parameters, 5-108
routing parameters, 5-105
voice parameters, 5-110
configuration sequence, 5-103
Connection State, 5-105
Connectivity Packet Rate (Sec), 5-109
Connectivity Timeout Cycles, 5-109
Custom Tone Detection, 5-116
Dest CBID, 5-106
Destination IP, 5-105
Echo Canceller, 5-117
Exit Channel, 5-106
Exit Port, 5-106
Fax/Modem, 5-113
I-9
Index
Function, 5-104
AAL2oMPLS, 5-104
AAL2oMPLS+, 5-104
TDMoIP, 5-104
TDMoIP+, 5-104
Max Bytes in Multiplexed Frame, 5-108
MF Parameters, 5-116
Next Hop, 5-106
Packetizing Interval, 5-109
Source CBID, 5-106
Super Tandem, 5-117
TOS, 5-107
Transparent Jitter Size, 5-108
TS assignment
entire port (voice ports), 5-127
individual timeslots (voice ports), 5-125
Tx delay for Caller ID, 5-111
VAD, 5-117
VLAN Parameters, 5-107, 5-108
Volume from Line, 5-113
Volume to Line, 5-112
Technical support, 7-91
Telnet, 4-35
requirements, 4-35
Testing, 7-71
TFTP
Default Gateway Address, B-11
downloading, B-11
downloading/uploading files, 5-149
File download, 5-151
File upload, 5-151
IP Address, B-11
IP Mask, B-11
Perform Reset to the board, B-11
Time Elapsed, 7-11
Timeout, 5-25
Timeout (sec), 5-15
Timing
adaptive, C-57
adaptive mode, C-57
Timing subsystem, 2-39
block diagram, 2-39
external clock interface, 2-42
external reference signals, 2-41
internal reference signals, 2-41
output signals, 2-40
redundancy, 2-42
Trace route, 7-81, 7-82
Trap Community, 5-41
Traps, 7-68
list, 7-68
OID, 7-68
Troubleshooting
handling service problems, 7-25
hardware problems, 7-22
preliminary checks, 7-21
TS assignment
CESoPSN bundle
compressed voice ports, 5-125
data ports, 5-127
entire port (data port subchannel), 5-129
voice compression modules, 5-124
I-10

HDLC bundle
HDLCoPSN bundle
entire port, 5-123
TDMoIP (CE) bundle
entire port, 5-123
TDMoIP (CV) bundle
entire port (voice ports), 5-127
individual timeslots (voice ports), 5-125
Turn off, 4-4
Tx Broadcast ok, 7-15
Tx Correct Octets, 7-15
Tx Correct pkts, 7-15
Tx Correct Unicast pkts, 7-15
Tx Discard pkts, 7-15
Tx Iface Errors, 7-15
Tx Multicast ok, 7-15
Tx Pause Frames, 7-17
Type, 5-135
U
UDP
introduction, C-48
UDP sockets per IP address, 2-25
Update Database, 5-4
User Change, 5-22
download/upload by TFTP, 5-149
File download, 5-151
File upload, 5-151
File system, 5-155
Copy File, 5-157
Delete File, 5-159
Dir function, 5-156
Format disk, 5-159
Rename File, 5-158
File Utilities, 5-149
Internal Download, 5-151
Internal Upload, 5-153
Reset, 5-154
V
indications, 4-4
indications, 4-4
Viewing Logistic (Inventory) Information, 5-130
VLAN, C-37
ID, C-37
priority, C-37
Voice compression
bandwidth requirements, 2-21
controlling bandwidth consumption, 2-22
fax handling, 2-18
inband signaling, 2-17
operating modes, 2-13
Q.50 overview, 2-22
voice packet processing, 2-20
voice signal handling, 2-15
voice trunk signaling, 2-19
voiceband modem handling, 2-19
Gmux-2000 Ver. 3.2

W
Gmux-2000 Ver. 3.2
Index
Warning, 7-26
Write Community, 5-41
I-11
Index
I-12
Gmux-2000 Ver. 3.2
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel

Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250
E-mail: erika_y@rad.com, Web site: http://www.rad.com
Customer Response Form

RAD Data Communications would like your help in improving its product documentation.
Please complete and return this form by mail or by fax or send us an e-mail with your
comments.
Thank you for your assistance!
Manual Name:
Gmux-2000 Ver. 3.2
Publication Number:
358-200-07/08
Please grade the manual according to the following factors:
Excellent
Installation instructions
Operating instructions
Manual organization
Illustrations
The manual as a whole
What did you like about the manual?
Good
Fair
Poor
Very Poor
Error Report
Type of error(s) or
problem(s):
Incompatibility with product

Difficulty in understanding text
Regulatory information (Safety, Compliance, Warnings, etc.)
Difficulty in finding needed information
Missing information
Illogical flow of information
Style (spelling, grammar, references, etc.)
Appearance
Other
Please list the exact page numbers with the error(s), detail the errors you found (information missing,
unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.
Please add any comments or suggestions you may have.
You are:
Distributor
End user
VAR
Other
Who is your distributor?

Your name and company:
Job title:
Address:
Direct telephone number and extension:
Fax number:
E-mail:
Publication No. 358-200-07/08
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North America Headquarters

900 Corporate Drive
Mahwah, NJ 07430, USA
Tel. 201-5291100
Toll free 1-800-4447234
Fax 201-5295777
E-mail market@radusa.com
www.rad.com
The Access Company

Gmux-2000 - Manual (Version Menu) PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gmux-2000 - Manual (Version Menu) PDF

Uploaded by

Copyright:

Available Formats

INSTALLATION AND

The Access Company

Installation and Operation Manual

North America Headquarters

24 Raoul Wallenberg Street

900 Corporate Drive

20052008 RAD Data Communications Ltd.

Publication No. 358-200-07/08

General Safety Instructions

Do not attempt to adjust the laser drive current.

Do not use broken or unterminated fiber-optic cables/connectors or look

Use of controls, adjustments or performing procedures other than those

Handling Energized Products

Connecting Data and Telecommunications Cables

V.11, V.28, V.35, V.36, RS-530, X.21,

xDSL (without feeding voltage),

TNV-1 Telecommunication Network Voltage-1:

FXS (Foreign Exchange Subscriber)

TNV-2 Telecommunication Network Voltage-2:

FXO (Foreign Exchange Office), xDSL

TNV-3 Telecommunication Network Voltage-3:

Safety Extra Low Voltage:

Pour rduire les risques sincendie, utiliser seulement des conducteurs de

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Mise au rebut du produit

Instructions gnrales de scurit

Mise la terre de protection : la cosse ou la borne marque devrait tre connecte

Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre

Ne tentez pas d'ajuster le courant de la commande laser.

N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans

L'usage de priphriques optiques avec l'quipement augmentera le risque pour

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

Manipuler des produits sous tension

Connexion au courant du secteur

Chapter 2. Functional Description

Chapter 3. System Installation

Chapter 4. Operation and Preliminary Configuration

Chapter 6. Configuring Typical Applications

Chapter 6. Troubleshooting and Diagnostics

Appendix A. Connection Data

Appendix B. Installing New Software Releases

Appendix C. Operating Environment

A caution warns of possible damage to the equipment if a procedure is not

A warning alerts to the presence of important operating and maintenance

Quick Start Guide

Slot for SDH Interface Module

Slot for PSN

I/O 6 Alternate Slot for

S TAT ION CLOCK

S TAT ION CLOCK

2 Slots for CONTROL Modules

Slot Utilization for TDM Traffic Transport Services

Gmux-2000 Ver. 3.2

Quick Start Guide

Installation and Operation Manual

Slot for SDH Interface Module

Slot for PSN

I/O 6 Alternate Slot for

S TAT ION CLOCK