Está en la página 1de 578

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)

TNV-2 Telecommunication Network Voltage-2:


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

FXO (Foreign Exchange Office), xDSL


(with feeding voltage), U-Interface
ISDN

TNV-3 Telecommunication Network Voltage-3:


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

Safety Extra Low Voltage:


Ports which do not present a safety hazard. Usually
up to 30 VAC or 60 VDC.

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
Pseudowire Emulation Server
or
Pseudowire Emulation Module with External Interfaces

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
Pseudowire Emulation
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

Installing Gmux-2000

Quick Start Guide

Installation and Operation Manual


Alternate Slot for SDH Interface Module
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

Slot for SDH Interface Module


or
Voice Compression Module
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 8 Interface Module

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

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

2 Slots for CONTROL Modules


3 Slots for PS Modules

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.

Installing Gmux-2000

Gmux-2000 Ver. 3.2

Installation and Operation Manual

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

Configuration Sequence

Quick Start Guide


Step

Installation and Operation Manual

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 Sequence

Configuration>System>Management>SNMP Engine ID
Configuration>System>Management>SNMPv3
Setting>Users
Configuration>System>Management>SNMPv3
Setting>Targets & Notify
Configuration>System>Management>SNMPv3
Setting> SNMPv1/v3 Mapping

Gmux-2000 Ver. 3.2

Installation and Operation Manual


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

Configuration Sequence

Quick Start Guide

Installation and Operation Manual

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

Configuration Sequence

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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
Application Overview ............................................................................................ 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
Application Overview ............................................................................................ 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
Application Overview ............................................................................................ 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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 1 Introduction

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

Chapter 1 Introduction

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 1 Introduction

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

Chapter 1 Introduction

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 1 Introduction

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

Chapter 1 Introduction

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 1 Introduction

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

Chapter 1 Introduction

Installation and Operation Manual

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

Typical Applications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Typical Applications

1-11

Chapter 1 Introduction

Installation and Operation Manual

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

Typical Applications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction
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


Figure 1-6 shows a Gmux-2000 equipped with voice compression modules that
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.
Up to 5 or 6 VC-E1/16
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

Typical Applications

1-13

Chapter 1 Introduction

Installation and Operation Manual

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


Figure 1-7 shows a Gmux-2000 equipped with voice compression modules that
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.
Up to 5 or 6 VC-E1/16
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

Typical Applications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Typical Applications

1-15

Chapter 1 Introduction

Installation and Operation Manual

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.

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Equipment Description

1-17

Chapter 1 Introduction

Installation and Operation Manual


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

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Equipment Description

1-19

Chapter 1 Introduction

Installation and Operation Manual

Alternate Slot for SDH Interface Module


or
Pseudowire Emulation Server
or
Pseudowire Emulation Module with External Interfaces

Slot for SDH Interface Module


or
Pseudowire Emulation Server
or
Pseudowire Emulation Module with External Interfaces

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 Interface Module

I/O-8

MONITOR

GbE

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

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
Pseudowire Emulation
Servers
and/or
Pseudowire Emulation
Modules with External
E1 Interfaces

FLT

DPW

Fan Tray
System Slots

I/O Slots

2 Slots for CONTROL Modules


3 Slots for PS Modules

Figure 1-13. Typical Gmux-2000 Rear View (Unit Equipped for TDM Traffic Transport Services)
Alternate Slot for SDH Interface Module
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

Slot for SDH Interface Module


or
Voice Compression Module
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
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

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

2 Slots for CONTROL Modules


3 Slots for PS Modules

Figure 1-14. Typical Gmux-2000 Rear View (Unit Equipped for Voice Trunking Services)

1-20

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Equipment Description

1-21

Chapter 1 Introduction

Installation and Operation Manual


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

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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.

Equipment Description

1-23

Chapter 1 Introduction

Installation and Operation Manual

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

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Equipment Description

1-25

Chapter 1 Introduction

Installation and Operation Manual

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.

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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.

Equipment Description

1-27

Chapter 1 Introduction

Installation and Operation Manual

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)

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/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.

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.

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.

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 1 Introduction

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

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

Equipment Description

1-29

Chapter 1 Introduction

Installation and Operation Manual

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

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Equipment Description

1-31

Chapter 1 Introduction

Installation and Operation Manual

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).

Equipment Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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.
The module supports comprehensive diagnostics, including power-up self-test,
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
glance the status of each module port.

Gmux-2000 Ver. 3.2

Equipment Description

1-33

Chapter 1 Introduction

Installation and Operation Manual

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

Technical Specifications

1:N protection for I/O modules with internal


ports (one protection group per chassis)

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 1 Introduction

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

Technical Specifications

1-35

Chapter 1 Introduction

Installation and Operation Manual

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

Technical Specifications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

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

Chapter 1 Introduction

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

Technical Specifications

1-37

Chapter 1 Introduction

Copper Port
Interface
Characteristics
GbE Port
Indications

MONITOR Port
Characteristics

Installation and Operation Manual

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

Module Indicators ACT (green)

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

Technical Specifications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Protocols

Chapter 1 Introduction

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

Packet Switched Network


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

Loopback timing (transmit timing locked to


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

Technical Specifications

1-39

Chapter 1 Introduction

Installation and Operation Manual

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

Automatically performed upon power-up or


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

Packet Switched Network


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)

Technical Specifications

MPLS over ETH

Gmux-2000 Ver. 3.2

Installation and Operation Manual

E1 Internal Port
Characteristics

Chapter 1 Introduction

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

E1 Port Transmit Path


Timing

Loopback timing (transmit timing locked to


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.

Module Indicators ACT (green)

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

Automatically performed upon power-up or


reset
Occupies a single I/O slot (slot 1 to 5, 7, 9)

Technical Specifications

1-41

Chapter 1 Introduction

Installation and Operation Manual

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

Packet Switched Network


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

Basic G.704 framing, with or without CRC-4


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

Technical Specifications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Internal
Voice Port
Interface
Characteristics

Chapter 1 Introduction

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

Basic G.704 framing, with or without CRC-4


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

Technical Specifications

1-43

Chapter 1 Introduction

Installation and Operation Manual

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

Technical Specifications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Voice
Encapsulation Method
Compression (per
Bundle) (Cont.)

Chapter 1 Introduction

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

Technical Specifications

1-45

Chapter 1 Introduction

Installation and Operation Manual

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

E1 Port Transmit Path


Timing

Loopback timing (transmit timing locked to


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

Technical Specifications

Automatically performed upon power-up or reset

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Physical

Chapter 1 Introduction

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

Technical Specifications

1-47

Chapter 1 Introduction

Installation and Operation Manual

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

Technical Specifications

Gmux-2000 Ver. 3.2

Installation and Operation Manual

External Alarm
Interfaces

Alarm Outputs

Chapter 1 Introduction

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

Technical Specifications

1-49

Chapter 1 Introduction

Installation and Operation Manual

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

Technical Specifications

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.

Gmux-2000 Functional Description

2-1

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-3

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-5

Chapter 2 Functional Description

Note

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-7

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-9

Chapter 2 Functional Description

Installation and Operation Manual

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

Voice Compression Module

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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:

Basic G.704 framing, with or without support for CRC-4 in accordance


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.

G.704 framing with timeslot 16 multiframe (G.704 multiframe mode),


with or without support for CRC-4. This framing mode is required for
applications that require CAS.

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

Gmux-2000 Functional Description

2-11

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-13

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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.

Gmux-2000 Functional Description

2-15

Chapter 2 Functional Description

Note

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-17

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-19

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-21

Chapter 2 Functional Description

Installation and Operation Manual

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 Functional Description

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Gmux-2000 Functional Description

2-23

Chapter 2 Functional Description

2.3

Installation and Operation Manual

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

Fractional E1 services, with or without CAS, are supported by means of


TDMoPSN. Without CAS, CESoPSN can also be used

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:

Connection (Bundle) Handling

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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.

Connection (Bundle) Handling

2-25

Chapter 2 Functional Description

Installation and Operation Manual

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.

Connection (Bundle) Handling

Gmux-2000 Ver. 3.2

Installation and Operation Manual

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

Chapter 2 Functional Description

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.

Connection (Bundle) Handling

2-27

Chapter 2 Functional Description

Installation and Operation Manual

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

Connection (Bundle) Handling

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Redundancy (APS) Functions

2-29

Chapter 2 Functional Description

Installation and Operation Manual

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

Redundancy (APS) Functions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Redundancy (APS) Functions

2-31

Chapter 2 Functional Description

Installation and Operation Manual

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

Redundancy (APS) Functions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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.

Redundancy (APS) Functions

2-33

Chapter 2 Functional Description

Installation and Operation Manual

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

Redundancy (APS) Functions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:

Gmux-2000 Ver. 3.2

Redundancy (APS) Functions

2-35

Chapter 2 Functional Description

Installation and Operation Manual

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.
The equipment connected to the GbE ports must use compatible switching
criteria for redundancy to be available:

For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface (in the
topology of Figure 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).

Redundancy (APS) Functions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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).
The recovery mode after a protection switching can be selected in accordance
with the application requirements (revertive or non-revertive, as described
above).
The equipment connected to the GbE ports must use compatible switching
criteria for redundancy to be available:

For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface. 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

Redundancy (APS) Functions

2-37

Chapter 2 Functional Description

Installation and Operation Manual

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

Redundancy (APS) Functions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Chapter 2 Functional Description

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 2 Functional Description

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

Chapter 2 Functional Description

Note

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 2 Functional Description

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

Chapter 2 Functional Description

2.6

Installation and Operation Manual

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

Management Subsystem
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.

Management Subsystem

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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.

Management Subsystem

2-45

Chapter 2 Functional Description

Installation and Operation Manual

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

Management Subsystem

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 2 Functional Description

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

Power Supply Subsystem

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

Power Supply Subsystem

2-47

Chapter 2 Functional Description

2-48

Power Supply Subsystem

Installation and Operation Manual

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

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

3.5

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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.
Alternate Slot for SDH Interface Module
or
Pseudowire Emulation Server
or
Pseudowire Emulation Module with External E1 Interfaces
Slot for SDH Interface Module
or
Pseudowire Emulation Server
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


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
Pseudowire Emulation
Modules with External
E1 Interfaces

FLT

DPW

Fan Tray
System Slots

I/O Slots

2 Slots for CONTROL Modules


3 Slots for PS Modules

Figure 3-3. Gmux-2000 Enclosure, Typical Rear View

Gmux-2000 Ver. 3.2

Gmux-2000 Enclosure

3-13

Chapter 3 System Installation

3.6

Installation and Operation Manual

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.

Installing the Fan Tray

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 3 System Installation

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

Installing the Fan Tray

3-15

Chapter 3 System Installation

3.7

Installation and Operation Manual

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

Installation and Operation Manual

Fuse H1

Chapter 3 System Installation

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.

Installing the Gmux-2000 PS Modules

3-17

Chapter 3 System Installation

Note

Installation and Operation Manual

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

Installing the Gmux-2000 PS Modules

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 3 System Installation

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

Installing the Gmux-2000 PS Modules

3-19

Chapter 3 System Installation

Installation and Operation Manual

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

Installing the Gmux-2000 PS Modules

Gmux-2000 Ver. 3.2

Installation and Operation Manual

3.9

Chapter 3 System Installation

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

Installation of CONTROL Modules

3-21

Chapter 3 System Installation

Installation and Operation Manual

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

Installation of CONTROL Modules

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 3 System Installation

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.

Installation of CONTROL Modules

3-23

Chapter 3 System Installation

Installation and Operation Manual

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

Installation of CONTROL Modules

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Installation and Operation Manual

Chapter 3 System Installation

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

Chapter 3 System Installation

Installation and Operation Manual

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

Operating Instructions

4-1

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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
shown in Figure 4-1.

Operating Instructions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

Operating Instructions

4-3

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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.

Operating Instructions

Gmux-2000 Ver. 3.2

Installation and Operation Manual

4.3

Chapter 4 Operation and Preliminary Configuration

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

Preliminary Configuration Sequence

4-5

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

Preliminary Configuration Sequence

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

Preliminary Configuration Sequence

4-7

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

Configuration>Database Tools>Choose DB Number

To update a new database, first load it


and then update the configuration

Configuration>Database Tools>Load Database


Configuration>Database Tools>Update Database

Reload the factory-default parameters

Configuration>Database Tools>Factory Default

Preliminary Configuration Sequence

Gmux-2000 Ver. 3.2

Installation and Operation Manual


Step

Chapter 4 Operation and Preliminary Configuration

Action

Using

If the Gmux-2000 is equipped with all the


modules, load the hardware configuration.

Configuration>Database Tools>Load Hardware


and then
Configuration>Database Tools>Update Database

Alternatively, configure the modules


installed in the Gmux-2000

Configuration>System>Card Type

Configure CONTROL DCE port parameters

Configuration>System>Serial Port

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>Manager List

Configure Gmux-2000 management access

Configuration>System>Management>Management Access

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
9

Set Gmux-2000 real-time clock:

1. Select the date source, and the 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
10

Configuration>System>Management>SNMP Engine ID
Configuration>System>Management>SNMPv3
Setting>Users
Configuration>System>Management>SNMPv3
Setting>Targets & Notify
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
Configuration>System>Date & Time>Time and Date
parameters
Configuration>System>Date & Time>NTP Server, GMT,
Update Interval
Configuration>Database Tools>Update Database

All the following menus are reached after opening the Configuration menu.

Preliminary Configuration Sequence

4-9

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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.

Preliminary Configuration Sequence

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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.


4. Save the changes.

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.

Preliminary Configuration Sequence

4-11

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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:


1. Open Management on the System menu.
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.

5. Save the changes.

Configure the SNMP management parameters:


1. Open Management on the System menu.
2. Select Device Info on the Management submenu.
3. Enter the prescribed description for each item.
4. Save the changes.
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

Preliminary Configuration Sequence

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 4 Operation and Preliminary Configuration

The community names are case-sensitive.


7. Save the changes.

Set the Gmux-2000 real-time clock:


1. Open Management on the System menu.
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

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

Configuring Gmux-2000 via Supervision Terminal

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

Configuring Gmux-2000 via Supervision Terminal

4-15

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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.

Configuring Gmux-2000 via Supervision Terminal

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 4 Operation and Preliminary Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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).

Configuring Gmux-2000 via Supervision Terminal

4-17

Chapter 4 Operation and Preliminary Configuration

Nothing

Installation and Operation Manual

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

Configuring Gmux-2000 via Supervision Terminal

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

Configuring Gmux-2000 via Supervision Terminal

4-19

Chapter 4 Operation and Preliminary Configuration

4.6

Installation and Operation Manual

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.

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

Menu Structure of Supervision Utility

4-21

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

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
4. Trap (for Manager)
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

Menu Structure of Supervision Utility

4-23

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

Master Clock Source

SNMPv3 = Disabled
Management
1. Device Info
2. Authentication/Community
3. Manager List
4. Management Access
5. Username&Password
6. SNMP Engine ID
7. SNMPv3 - Disabled

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
2. Ext Clock Interface
3. Ext In/Out Clk Mode
4. Ext Out Clock Source
5. Ext Out Clock State

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
3. Init Alarm 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
1. Syslog Configuration
2. Syslog Statistics

Figure 4-9. Configuration>System Submenu Structure (Part 2 of 4)

4-24

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

SNMPv3 = Disabled
Management
1. Device Info
2. Authentication/Community
3. Manager List
4. Management Access
5. Username&Password
6. SNMP Engine ID
7. SNMPv3 - Disabled

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
2. Ext Clock Interface
3. Ext In/Out CLK Mode
4. Ext Out Clock Source
5. Ext Out Clock State

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
3. Init Alarm 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
3. 100Mbps Half Duplex
4. 100Mbps 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
1. Syslog Configuration
2. Syslog Statistics

Recovery Mode
Revertive
Non-Revertive

1. Logging Status
2. Server IP Address
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 4-10. Configuration>System Submenu Structure (Part 3 of 4)

Gmux-2000 Ver. 3.2

Menu Structure of Supervision Utility

4-25

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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

See
Part 1

SNMPv3 = Enabled
Management
1. Device Info
2. Manager List
3. Management Access
4. Username&Password
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
Authentication Protocol
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
2. Ext Clock Interface
3. Ext In/Out Clk Mode
4. Ext Out Clock Source
5. Ext Out Clock State

Alarms

Trap

See
Part 2

1. Attribute
2. Priority
3. Init Alarm 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

Summary Target Table


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
1. Syslog Configuration
2. Syslog Statistics

Figure 4-11. Configuration>System Submenu Structure (Part 4 of 4)

4-26

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual


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

Chapter 4 Operation and Preliminary 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 Configuration

Connection Configuration
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

Menu Structure of Supervision Utility

4-27

Chapter 4 Operation and Preliminary Configuration

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

Installation and Operation Manual

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

Connection Configuration
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

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

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

Chapter 4 Operation and Preliminary Configuration


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 Configuration

Connection Configuration

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
Outbound Label Tagging
Outbound Tunnel Label
Outbund EXP Bits
Inbound Label Tagging
Inbound Tunnel Label
VLAN Tagging
VLAN ID
VLAN Priority

Figure 4-14. Configuration>Connection Submenu HDLCoPSN Bundles

Gmux-2000 Ver. 3.2

Menu Structure of Supervision Utility

4-29

Chapter 4 Operation and Preliminary Configuration


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

Installation and Operation Manual


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 Configuration

Connection Configuration
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 Label Tagging
Outbound Tunnel Label
Outbound EXP Bits
Inbound Label Tagging
Inbound Tunnel Label
VLAN Tagging
VLAN ID
VLAN Priority

Figure 4-15. Configuration>Connection Submenu CESoPSN Bundles

4-30

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration


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
TIME SLOT NUM : ts 1
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
TIME SLOT NUM : ts 1
Bundle Number: 1
TS Type
:
NC

ts 2
1
NC

ts 3
1
NC

ts 4
1
NC

ts 5
1
NC

Assign TS Range to Bundle


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

Only for Framed Modes


Not Supported by Data Ports
of Voice Compression Modules

Assign Entire Port to Bundle


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

Not Supported by Data Ports


of Voice Compression Modules

or
Assign Entire TSs to Port
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

Menu Structure of Supervision Utility

4-31

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

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
Depends on Selected I/O Slot

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 System Alarm


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

Display Bundle Alarm


DSP All Alarms

1. Slot
2. "External Port"
3. "Internal Port"

Figure 4-17. Monitoring Menu Structure

4-32

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 4 Operation and Preliminary Configuration

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

1. Destination IP Address
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

Menu Structure of Supervision Utility

4-33

Chapter 4 Operation and Preliminary Configuration

Installation and Operation Manual

Utilities
Download/Upload by TFTP

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

Menu Structure of Supervision Utility

Gmux-2000 Ver. 3.2

Installation and Operation Manual

4.7

Chapter 4 Operation and Preliminary Configuration

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

Chapter 4 Operation and Preliminary Configuration

Note

Installation and Operation Manual

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

Unless otherwise specified, all the parameter values appearing in the following
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

Installation and Operation Manual

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
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

1.
2.
3.
4.

Card SS/PP
TS Assignment
Assign TS Range to Bundle
Assign Entire Port to Bundle

TS Assignment

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 5-1. Configuration Menu Structure

5-2

Overview

Gmux-2000 Ver. 3.2

Installation and Operation Manual

5.2

Chapter 5 Configuration

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

Managing Gmux-2000 Configuration Databases

5-3

Chapter 5 Configuration

Installation and Operation Manual

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)

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Managing Gmux-2000 Configuration Databases

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

(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

Managing Gmux-2000 Configuration Databases

5-5

Chapter 5 Configuration

Installation and Operation Manual

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

Configuration Sequence

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

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

5-6

Configuration Sequence

Configuration>System>Date & Time>Time and Date


parameters
Configuration>System>Date & Time>NTP Server,
GMT, Update Interval

Gmux-2000 Ver. 3.2

Installation and Operation Manual


Step
12

Action

Chapter 5 Configuration
Using

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
Configuration>System>Management>SNMPv3
Setting>Users
Configuration>System>Management>SNMPv3
Setting>Targets & Notify
Configuration>System>Management>SNMPv3
Setting>SNMPv1/v3 Mapping

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

Configuration Sequence

5-7

Chapter 5 Configuration

5.4

Installation and Operation Manual

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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

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
4. Trap (for Manager)
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

user, tech

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 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
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 5-3.A. Configuration>System Submenu Structure (Part 1 of 4)

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-9

Chapter 5 Configuration

Installation and Operation Manual

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

Master Clock Source

SNMPv3 = Disabled
Management
1. Device Info
2. Authentication/Community
3. Manager List
4. Management Access
5. Username&Password
6. SNMP Engine ID
7. SNMPv3 - Disabled

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
2. Ext Clock Interface
3. Ext In/Out Clk Mode
4. Ext Out Clock Source
5. Ext Out Clock State

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
3. Init Alarm 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
1. Syslog Configuration
2. Syslog Statistics

Figure 5-3.B. Configuration>System Submenu Structure (Part 2 of 4)

5-10

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

SNMPv3 = Disabled
Management
1. Device Info
2. Authentication/Community
3. Manager List
4. Management Access
5. Username&Password
6. SNMP Engine ID
7. SNMPv3 - Disabled

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
2. Ext Clock Interface
3. Ext In/Out CLK Mode
4. Ext Out Clock Source
5. Ext Out Clock State

Alarms

APS Configuration

I/O
1. APS ID
2. APS Configuration
3. APS Mapping

See
Part 2

1. Attribute
2. Priority
3. Init Alarm Priority
4. Threshold
5. Threshold Window
6. Report
7. Input Relay

Name
Config Mode
Recovery Mode
Time to Restore in sec
STM-1 SD Flip Criteria

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
3. 100Mbps Half Duplex
4. 100Mbps 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
1. Syslog Configuration
2. Syslog Statistics

Recovery Mode
Revertive
Non-Revertive

1. Logging Status
2. Server IP Address
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

Configuring System Parameters

5-11

Chapter 5 Configuration

Installation and Operation Manual

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

See
Part 1

SNMPv3 = Enabled
Management
1. Device Info
2. Manager List
3. Management Access
4. Username&Password
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
Authentication Protocol
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
2. Ext Clock Interface
3. Ext In/Out Clk Mode
4. Ext Out Clock Source
5. Ext Out Clock State

Alarms

Trap

See
Part 2

1. Attribute
2. Priority
3. Init Alarm 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

Summary Target Table


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
1. Syslog Configuration
2. Syslog Statistics

Figure 5-3.D. Configuration>System Submenu Structure (Part 4 of 4)

5-12

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
>
Please select item <1 to 3>
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

Configuring System Parameters

5-13

Chapter 5 Configuration

Note

Installation and Operation Manual

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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Serial Port
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)

>
Please select item <1 to 9>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Parameters

5-15

Chapter 5 Configuration

Installation and Operation Manual

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
Configuration>System>Ethernet Port
1. Speed

>

(Auto Negotiation)

>
Please select item <1 to 9>
% - UPD DB
ESC-prev.menu; !-main menu; &-exit; @-debug
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).

3. Save the changes.

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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
Configuration>System>Host IP
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)

>
Please select item <1 to 1>
V view sanity log
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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.
5. Save the changes.

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-17

Chapter 5 Configuration

Installation and Operation Manual

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

Type the desired IP address, using the


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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Parameters

5-19

Chapter 5 Configuration

Note

Installation and Operation Manual

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 )
()
()
()

>
Please select item <1 to 6>
F - next; B - prev; R - remove
ESC-prev.menu; !-main menu; &-exit; @-debug
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)
()
()
()

>
Please select item <1 to 4>
F - next; B - prev; R - remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

B. Typical User Access Screen for Other Levels


Figure 5-9. Typical User Access Screens

5-20

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 5 Configuration

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

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-10. Typical Permission Screen


Gmux-2000 Ver. 3.2

Configuring System Parameters

5-21

Chapter 5 Configuration

Installation and Operation Manual

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.
7. To save the new user definitions in the edited database, select Save All.
8. To update the active database, and thus activate the new user definitions,
type % to save and then confirm the action.
Pseudowire Gateway
Configuration>System>Management>Management access>User Access>Access

(All )

1. Terminal
2. Telnet
3. All

>
Please select item <1 to 5>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-11. Typical Access Screen

5-22

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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.
To navigate to the required screen, use Configuration>System>Management>
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

[]

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

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

Figure 5-13. Typical Display User List Screen

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-23

Chapter 5 Configuration

Installation and Operation Manual

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.

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

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

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

The allowed range is 1 to 4094.

Gmux-2000 Ver. 3.2

Default: 3

Default: 3

Default: 1812

Default: 1813

Configuring System Parameters

5-25

Chapter 5 Configuration

Installation and Operation Manual

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.
To navigate to the required screen, use Configuration>System>Management>
Manager List.
A Manager List screen, as seen when first opened, is shown in Figure 5-15.

Pseudowire Gateway
Configuration>System>Management>Manager list
IP ADDRESS

NEXT HOP

INTERFACE

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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 see the navigation keys available for this screen, type ? (help).
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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
Configuration>System>Management>Manager list
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
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-16. Typical Add New Manager Screen (CL Interface with VLAN Tagging Disabled)
PseudoWire Gateway
Configuration>System>Management>Manager list
1.
2.
3.
4.
5.
6.
7.

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)
(Yes)
... (0)
... (0)

>
Please select item <1 to 5>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-17. Typical Add New Manager Screen (CL Interface with VLAN Tagging Enabled)

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-27

Chapter 5 Configuration

Installation and Operation Manual

Table 5-7. Manager List Parameters


Parameter

Function

Values

IP Address

Used to enter the manager/destination IP


address of the entry

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

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.

Configuring System Parameters

NO Gmux-2000 will not send traps to this


destination.
Default: NO

Default: NO

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Parameter

Function

Values

VLAN ID

When VLAN tagging is enabled, specifies


the VLAN ID number used by the traffic
exchanged with this station.

The allowed range is 1 to 4094.


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
Configuration>System>Management>Manager list
IP ADDRESS
172.171.75.32
->>
1. Change cell

NEXT HOP
172.35.56.89

INTERFACE
CL Interface
... (172.171.75.32)

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

A. Typical Leftmost Section

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-29

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Configuration>System>Management>Manager list
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

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

B. Typical Middle Section


Pseudowire Gateway
Configuration>System>Management>Manager list
TRAP(FOR MANAGER) VLAN VALID VLAN ID VLAN PRIORITY
Yes
Yes
67
6
<<1. Change cell [0 - 7]
... (6)

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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.

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

To navigate to the required screen, use Configuration>System>Management>


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)


()
()
()

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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.
Default: Empty string

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

Configuring System Parameters

5-31

Chapter 5 Configuration

Installation and Operation Manual

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.
3. Save the changes.

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
>

>
Please select item <1 to 2>
V - view sanity log
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-20. Typical Syslog Task Selection Screen


5-32

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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

The allowed range is 1 to 65535.


Default: 514

The default value, 514, matches the


RFC3164 default address.

Gmux-2000 Ver. 3.2

Configuring System Parameters

5-33

Chapter 5 Configuration
Device UDP Port

Installation and Operation Manual

Specifies the local UDP port through


which syslog reports are sent.

The allowed range is 1 to 65535.


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

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Parameters

5-35

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 8>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-23. Typical Date & Time Screen (Internal Clock NVRAM Source)

5-36

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

PseudoWire Gateway
Configuration>System>Date & Time
1. Date source
2. Date format
Current date & time
3. NTP Server IP Address
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)

>
Please select item <1 to 2>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Parameters

5-37

Chapter 5 Configuration

Notes

Installation and Operation Manual

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]

>
Please select item <1 to 26>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-25. Typical Time Zone (GMT) Selection Screen (NTP Source)

5-38

Configuring System Parameters

Gmux-2000 Ver. 3.2

Installation and Operation Manual

5.5

Chapter 5 Configuration

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
Authentication/Community
Manager list
Management access
Username&Password
SNMP Engine ID
SNMPv3

>
>
[]>
>
>
>
(Disabled)

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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.

Configuring Gmux-2000 for SNMP Management

5-39

Chapter 5 Configuration

Installation and Operation Manual

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
shown in Figure 5-27.

PseudoWire Gateway
Configuration>System>Management
1.
2.
3.
4.
5.
6.
7.
8.

Device info
Authentication/Community
Manager list
Management access
Username&Password
SNMP Engine ID
SNMPv3
SNMPv3 setting

>
>
[]>
>
>
>
(Enabled)
>

>
Please select item <1 to 7>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-27. Typical Management Screen (SNMPv3 Enabled)

To disable the SNMPv3 security features:


1. Navigate to Configuration>System>Management.
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

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

To navigate to the required screen, use Configuration>System>Management>


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)

>
Please select item <1 to 4>
ESC-prev.menu; !-main menu; &-exit; @-debug
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)

Up to eight alphanumeric characters.

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)

Up to eight alphanumeric characters.

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

Configuring Gmux-2000 for SNMP Management

5-41

Chapter 5 Configuration

Installation and Operation Manual

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:


1. Navigate to Configuration>System>Management.
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
Configuration>System>Management>SNMP Engine ID
Engine ID
... (800000a40400000000 )
Engine ID Config Type >
(Text)
1. Rest Bytes
... ()

>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-29. Typical SNMP Engine ID Screen

5-42

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
SNMPv3 Factory Defaults
Summary User Table
Summary Target Table

(4)
(370)
... (1500)
>
>
>
[]
[]

>
Please select item <1 to 6>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 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.

The allowed range is 484 to 2147483647.


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

Configuring Gmux-2000 for SNMP Management

5-43

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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)

Alphanumeric string of up to 32 characters.

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

Configuring Gmux-2000 for SNMP Management

5-45

Chapter 5 Configuration

Installation and Operation Manual

Parameter

Function

Values

Authentication
Password

Used to enter the password to be used by


the authentication protocol.

Alphanumeric string of up to 32 characters.


Default: Empty string

This parameter is not displayed when


Authentication Protocol is
usmNoAuthProtocol
Privacy
Password

The password required to use privacy.

Alphanumeric string of up to 32 characters.

This parameter is displayed only when


Privacy Protocol is uusmDESPrivProtoco

Default: Empty string

PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Users
1.
2.
3.
4.
5.

Security Name
Authentication Protocol
Privacy Protocol
Authentication Password
Privacy Password

... (User1)
>
(usmHMACMD5AuthProtocol)
>
(usmDESPrivProtocol)
...
...

>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
----------------------------------------------------------------------------

Figure 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

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

>
>
>
>

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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
Message Processing Model
Security Model
Security Name
Security Level

...
>
>
...
>

()
()
()
()
()

>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-34. Typical Targets Params Screen

Gmux-2000 Ver. 3.2

Configuring Gmux-2000 for SNMP Management

5-47

Chapter 5 Configuration

Installation and Operation Manual

Table 5-15. Target Params Parameters


Parameter

Function

Values

Name

Selects the logistic name assigned to the


target

Alphanumeric string of up to 32 characters.

Message
Processing
Model

Default: Empty string

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

Alphanumeric string of up to 32 characters.

Selects the level of security to be used


when generating SNMP messages for this
target

The available selections are:

Default: Empty string

noAuthNoPriv No authentication, no privacy.


authNoPriv With authentication, no privacy.
authPriv With authentication and privacy.
Default: noAuthNoPriv

To configure the target transport parameters:


1. Navigate to Configuration>System>Management>SNMPv3 setting>Targets &
Notify.
2. Select Target Address.
A typical Target Address screen is shown in Figure 5-35. The parameters
that can be configured are explained in Table 5-16.

PseudoWire Gateway
...tion>System>Management>SNMPv3 setting>Targets & Notify>Target Address
1.
2.
3.
4.

Name
IP Address
Params Name
Tag List

...
...
...
...

()
()
()
()

>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-35. Typical Target Address Screen

5-48

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Table 5-16. Target Address Parameters


Parameter

Function

Values

Name

Selects the logistic name assigned to the


target (see Table 5-15)

Alphanumeric string of up to 32 characters.

Specifies the IP address of this target.

Any valid IP address.

Make sure to add a static route to the target,


if necessary

Default: Empty string

IP Address

Default: Empty string

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
Default: Empty string
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
Default: Empty string

To configure the Notify parameters:


1. Navigate to Configuration>System>Management>SNMPv3 setting>Targets &
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)

>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-36. Typical Notify Screen

Gmux-2000 Ver. 3.2

Configuring Gmux-2000 for SNMP Management

5-49

Chapter 5 Configuration

Installation and Operation Manual

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
Alphanumeric string of up to 32 characters.
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:


1. Navigate to Configuration>System>Management>SNMPv3 setting>Targets &
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)

>
F - Forward; B - Backward; R - Remove
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
that can be configured are explained in Table 5-19.
PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>SNMPv1/v3 Mapping
1.
2.
3.
4.

Community Index
Community Name
Security Name
Transport Tag

...
...
...
...

()
()
()
()

>

ESC-prev.menu; !-main menu; &-exit; @-debug


1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-38. Typical SNMPv1/v3 Mapping Screen

Gmux-2000 Ver. 3.2

Configuring Gmux-2000 for SNMP Management

5-51

Chapter 5 Configuration

Installation and Operation Manual

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

Alphanumeric string of up to 32 characters.

Security Name

Specifies the security name used in SNMPv3


for this community

Alphanumeric string of up to 32 characters.

Transport Tag

Default: Empty string

Default: Empty string

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

>

ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help


1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-39. Typical Summary User Table Screen

Summary Target Table


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

Configuring Gmux-2000 for SNMP Management

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

PseudoWire Gateway
Configuration>System>Management>SNMPv3 setting>Summary Target Table
Address

MPModel SecModel SecName

SecLevel

>

ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help


1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-40. Typical Summary Target Table Screen

Gmux-2000 Ver. 3.2

Configuring Gmux-2000 for SNMP Management

5-53

Chapter 5 Configuration

Installation and Operation Manual

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;
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Installation and Operation Manual

5.7

Chapter 5 Configuration

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

Configuring System Timing Flow

5-55

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 5>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

>
>

>
Please select item <1 to 2>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Timing Flow

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Clock source>System A>Master clock
1. Master clock source

>

(Internal)

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring System Timing Flow

5-57

Chapter 5 Configuration

Installation and Operation Manual

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

>
Please select item <1 to 4>
ESC-prev.menu; !-main menu; &-exit; @-debug
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
Configuration>System>Clock source>System A>Master clock
1. Master clock source
2. Master clock source ss pp
3. Save parameters

>
(Rx clk)
... (9/1)

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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.
6. To update the active database, and thus activate the new user definitions,
type % to save and then confirm the action.
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

Configuring System Timing Flow

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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.
6. To update the active database, and thus activate the new user definitions,
type % to save and then confirm the action.

Gmux-2000 Ver. 3.2

Configuring System Timing Flow

5-59

Chapter 5 Configuration

Installation and Operation Manual

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
STATION CLOCK connector.
RS-485 T1 1.544 MHz clock frequency, at RS-485
levels using the balanced interface in the RJ-45
STATION CLOCK connector.
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

Configuring System Timing Flow

Gmux-2000 Ver. 3.2

Installation and Operation Manual

5.8

Chapter 5 Configuration

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
Configuration>System>Redundancy
1. CL
2. I/O

>
>

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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.

Configuring Redundancy

5-61

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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>.
4. To save the new user definitions in the edited database, select Save All.
5. To update the active database, and thus activate the new user definitions,
type % to save and then confirm the action.

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

Configuring Redundancy

5-63

Chapter 5 Configuration

Installation and Operation Manual

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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
ESC-prev.menu; !-main menu; &-exit; @-debug
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
shown in Figure 5-52.

5-64

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
Recovery mode
Time to restore in sec
STM-1 SD Flip Criteria
1. Change cell

(APS 1)

STM1 Cards
1+1 (Unidirect)
Revertive
300
Enable
... (STM1 Cards)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Alphanumeric string of up to 16 characters.

Selects the APS group configuration

NONE Cancels the protection function.

Config Mode

Default: Empty string

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

Configuring Redundancy

5-65

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS mapping CH NUM

INTERFACE

(APS 1)

PRIORITY

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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)

>
Please select item <1 to 1>
% - UPD DB; S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring Redundancy

5-67

Chapter 5 Configuration

Installation and Operation Manual

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
Configuration>System>Redundancy>I/O>APS mapping CH NUM
1
2

INTERFACE
7/1
7/2

(APS 1)

PRIORITY
High
Low

1. Change cell

... (7/1)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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.
Default: Empty string

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

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Configuring Redundancy

5-69

Chapter 5 Configuration

Installation and Operation Manual

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.
The screen changes to show the APS group configuration options. A
typical screen, as seen after all the parameters have been configured, is
shown in Figure 5-56.

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
1. Change cell

(APS 1)

GBE cards
802.3AD
... (GBE cards)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
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

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
Default: Empty string

Config Mode

Selects the APS configuration

NONE Cancels the protection function.


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.
802.3AD Link aggregation per IEEE 802.3ad
without LACP. This is the mode to be selected.
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

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
is shown in Figure 5-54.
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 /.
Refer to Table 5-24 for a description of APS mapping parameters.

Note

The first port configured in the APS group serves as the primary port. All the
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

Configuring Redundancy

5-71

Chapter 5 Configuration

Installation and Operation Manual

A typical I/O>APS Mapping screen that displays the two channels of an


APS group is shown in Figure 5-57.
Refer to Table 5-24 for a description of APS mapping parameters.
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.
Default: Empty string

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
Configuration>System>Redundancy>I/O>APS mapping CH NUM
1
2

INTERFACE
6/1
6/2

(APS 1)

PRIORITY
High
Low

1. Change cell

... (6/2)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-57. Typical I/O>APS Mapping Screen after Link Aggregation Configuration is Completed
(GbE Modules)
9. After configuring two channels, the configuration of the APS group is
complete, and link aggregation is activated as soon as the Gmux-2000
database is updated.

5-72

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 5 Configuration

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.
The screen changes to show the APS group configuration options. A
typical screen, as seen after all the parameters have been configured, is
shown in Figure 5-58.

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
Recovery mode
Time to restore in sec
1. Change cell

(APS 1)

GbE Ports
1:1 (Bidirect)
Revertive
300
... (GbE Ports)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
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

The first port configured in the APS group serves as the primary port. All the
bundles using this Gmux-2000 module as their network exit port must point to
the primary port.
4. After configuring two channels, the configuration of the APS group is
complete, and 1:1 bidirectional port protection is activated as soon as the
Gmux-2000 database is updated.

Gmux-2000 Ver. 3.2

Configuring Redundancy

5-73

Chapter 5 Configuration

Installation and Operation Manual

Table 5-25. APS Configuration Parameters 1:1 Bidirectional Port Protection Mode (GbE Modules)
Parameter

Function

Values

Name

See Table 5-23

Config Mode

Selects the APS group configuration

NONE Cancels the protection function.


1:1 (BIDIRECT) 1:1 bidirectional protection
mode. This is the mode to be selected.
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.
802.3AD Link aggregation per IEEE 802.3ad
without LACP. See configuration details in the

Configuring Link Aggregation for the PSN Interface


section above.
1:N 1:N protection for I/O modules see
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.
The screen changes to show the APS group configuration options. A
typical screen, as seen after all the parameters have been configured, is
shown in Figure 5-59.

5-74

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
Recovery mode
Time to restore in sec
1. Change cell

(APS 1)

GbE Cards
1:1 (Bidirect)
Revertive
300
... (GbE Cards)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
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 database is updated.

Gmux-2000 Ver. 3.2

Configuring Redundancy

5-75

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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
shown in Figure 5-61.

5-76

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>System>Redundancy>I/O>APS configuration Name
Config mode
Recovery mode
Time to restore in sec
1. Change cell

(APS 1)

PW Cards
N+1
Revertive
300
... (PW Cards)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
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

Selects the APS group configuration

Values

NONE Cancels the protection function.


1:1 (BIDIRECT) 1:1 bidirectional protection
mode. This mode is supported only by GbE
modules see configuration details in the

Configuring Gmux-2000 I/O Redundancy PSN


Interface Subsystem section above.
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 above.
802.3AD Link aggregation per IEEE 802.3ad
without LACP. See configuration details in the

Configuring Link Aggregation for the PSN Interface


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

Configuring Redundancy

5-77

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 1>
% - UPD DB; F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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
Gmux-2000 database is updated.

5-78

Configuring Redundancy

Gmux-2000 Ver. 3.2

Installation and Operation Manual

5.9

Chapter 5 Configuration

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

TDMoIP (TDM over IP) in accordance with RFC5087, and TDMoMPLS in


accordance with RFC5087 and ITU-T Rec. Y.1413 (the term TDMoPSN is used
when information is applicable to both protocols)

HDLCoPSN (HDLC over PSN) in accordance with RFC5087 and RFC4618


(except Clause 5.3 PPP)

CESoPSN (structure-aware TDM circuit emulation over PSN) in accordance


with RFC5086

SAToPSN (structure-agnostic TDM over PSN) in accordance with RFC4553

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

Configuring Connections

5-79

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual


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

Chapter 5 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 Configuration

Connection Configuration
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 5-63. Configuration>Connection Submenu TDMoIP (CE) and SAToPSN


Bundles

Gmux-2000 Ver. 3.2

Configuring Connections

5-81

Chapter 5 Configuration

Installation and Operation Manual


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

HDLC
UDP/IP

MPLS/ETH

Connection Configuration

Connection Configuration

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
Outbound Label Tagging
Outbound Tunnel Label
Outbund EXP Bits
Inbound Label Tagging
Inbound Tunnel Label
VLAN Tagging
VLAN ID
VLAN Priority

Figure 5-64. Configuration>Connection Submenu HDLC Bundles

5-82

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

CES
UDP/IP

MPLS/ETH

Connection Configuration

Connection Configuration
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 Label Tagging
Outbound Tunnel Label
Outbound EXP Bits
Inbound Label Tagging
Inbound Tunnel Label
VLAN Tagging
VLAN ID
VLAN Priority

Figure 5-65. Connection Submenu CESoPSN Bundles

Gmux-2000 Ver. 3.2

Configuring Connections

5-83

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

Installation and Operation Manual


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

Connection Configuration
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 5-66. Configuration>Connection Submenu TDMoIP (CV) Bundles

5-84

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

B. Typical Bundle Screen


Figure 5-67. Typical Configuration>Connection Bundle Selection Screens

Gmux-2000 Ver. 3.2

Configuring Connections

5-85

Chapter 5 Configuration

Installation and Operation Manual

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.
4. To update the online database and activate the new configuration, type %
and then confirm the action.

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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:
UDP Source Port = 8000 + Destination Bundle Number
This means that in the local fail state, the UDP ports numbers are higher than
8000 hexa (32768 decimal).
For TDMoIP (CE) bundles using packet payload Version V2:
UDP Source Port = 2000 + Destination Bundle Number
This means that all the UDP ports numbers are higher than 2000 hexa (8192
decimal).
For CESoPSN and SAToPSN bundles using packet payload Version V2:
UDP Source Port = C000 + Destination 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

Configuring Connections

5-87

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 1>
% - UPD DB
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------

A. Page 1 of Typical Screen

5-88

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)

>
Please select item <1 to 1>
% - UPD DB
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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)

>
Please select item <1 to 1>
% - UPD DB
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Configuring Connections

5-89

Chapter 5 Configuration

Installation and Operation Manual

6. To update the online database and activate the new configuration, type %
and then confirm the action.

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.

The supported range is 1 to 8063.


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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Configuring Connections

5-91

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Parameter

Function

Values

Destination IP

Specifies the IP address of the destination


bundle.

Type in the desired IP address, using the


dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
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
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 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

Configuring Connections

5-93

Chapter 5 Configuration

Installation and Operation Manual

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

When VLAN tagging is disabled, this


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).

When VLAN tagging is disabled, this


parameter is not displayed

Default: 0

Configuring TDMoIP (CE) Bundle Parameters for MPLS/ETH


Networks

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-28 for parameter
descriptions and configuration guidelines.

Table 5-28. TDMoIP (CE) Bundle Parameters MPLS/ETH Networks


Parameter

Function

Connection
State

See Table 5-27

5-94

Configuring Connections

Values

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Parameter

Function

Values

Source Bundle

Selects the number of the source bundle at the


local endpoint of this connection.

The supported range is 1 to 8063.


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
The supported range is 1 to 8063.
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.

The allowed range is 0 to 7.


Default: 0

This parameter is displayed only when Outbound


Label Tagging is ENABLE
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

Configuring Connections

5-95

Chapter 5 Configuration

Installation and Operation Manual

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


Label Tagging is ENABLE

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.

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-29 for parameter
descriptions and configuration guidelines.

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

Configuring Connections

5-97

Chapter 5 Configuration

Installation and Operation Manual

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

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-30 for parameter
descriptions and configuration guidelines.

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

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

Inbound Tunnel Label

See Table 5-28

VLAN Tagging

See Table 5-27

VLAN ID

See Table 5-27

5-98

Configuring Connections

Values

Gmux-2000 Ver. 3.2

Installation and Operation Manual


Parameter

Function

VLAN Priority

See Table 5-27

Chapter 5 Configuration
Values

Configuring SAToPSN Bundle Parameters


Configuring SAToPSN Bundle Parameters for UDP/IP Networks

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-31 for parameter
descriptions and configuration guidelines.

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

Configuring Connections

5-99

Chapter 5 Configuration

Installation and Operation Manual

Configuring SAToPSN Bundle Parameters for MPLS/ETH


Networks

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-32 for parameter
descriptions and configuration guidelines.

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

Only DATA is available

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

Inbound Tunnel Label

See Table 5-28

VLAN Tagging

See Table 5-28

VLAN ID

See Table 5-28

VLAN Priority

See Table 5-28

5-100

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Configuring CES Bundle Parameters


Configuring CES Bundle Parameters for UDP/IP Networks

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-33 for parameter
descriptions and configuration guidelines.

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

Only DATA is available

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

Configuring Connections

5-101

Chapter 5 Configuration

Installation and Operation Manual

Configuring CES Bundle Parameters for MPLS/ETH Networks

To configure the bundle parameters:


1. Select Connection Configuration.
2. Obtain the prescribed parameters, and then use Table 5-34 for parameter
descriptions and configuration guidelines.

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

Only DATA is available

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

Inbound Tunnel Label

See Table 5-28

VLAN Tagging

See Table 5-28

VLAN ID

See Table 5-28

VLAN Priority

See Table 5-28

5-102

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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):
UDP Source Port = 2000 + Destination Bundle Number
This means that all the UDP ports numbers are higher than 2000 hexa, that is,
8192 decimal.

MPLS/ETH MPLS over Ethernet.

3. Select Connection Configuration.


A typical TDMoIP (CV) Connection Configuration screen is shown in
Figure 5-69.

Gmux-2000 Ver. 3.2

Configuring Connections

5-103

Chapter 5 Configuration

Installation and Operation Manual

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)
Connectivity Parameters
>
Voice Parameters
>

>
Please select item <1 to 8>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)

>
Please select item <1 to 7>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-70. Typical TDMoIP (CV) Routing Parameters Screen


2. Obtain the prescribed parameters, and then use Table 5-35 for parameter
descriptions and configuration guidelines.

Table 5-35. TDMoIP (CV) Bundle Routing Parameters


Parameter

Function

Connection
State

Selects the state of the connection defined


by means of this bundle.

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.

Type in 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

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

Configuring Connections

5-105

Chapter 5 Configuration

Installation and Operation Manual

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
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 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
by means of this bundle.

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


generated by this bundle will be sent.

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
generated by this bundle will be sent.
This parameter is not relevant for GbE ports

5-106

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Configuring Connections

5-107

Chapter 5 Configuration

Installation and Operation Manual

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.
When VLAN tagging is disabled, this
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

When VLAN tagging is disabled, this


parameter is not displayed

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Configuring Connections

5-109

Chapter 5 Configuration

Installation and Operation Manual

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)

Please select item <1 to 15>


S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

A. First Page
Pseudowire Gateway
...ig>Connection>Connection configuration>Voice Parameters ...
12.
13.
14.
15.

(P)
VAD
CNG Mode
Advanced Voice Parameters
Save parameters

(BUNDLE 1)

>
(Enable)
>

>
Please select item <1 to 15>
S - Save
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

B. Second Page
Figure 5-71. Typical TDMoIP (CV) Voice Parameters Screen

5-110

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

2. Obtain the prescribed parameters, and then use Table 5-38 for parameter
descriptions and configuration guidelines.

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

Configuring Connections

5-111

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Configuring Connections

5-113

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual


Fax/Modem
(cont.)

Fax
Enables/disables fax signal relaying for this
bundle

Chapter 5 Configuration
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.
This parameter is displayed only when Modem
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

This parameter is displayed only when Modem


is ENABLE

Gmux-2000 Ver. 3.2

Configuring Connections

5-115

Chapter 5 Configuration
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.

Installation and Operation Manual


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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual


Tone Frequency

Chapter 5 Configuration

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.
The selection is made on a separate screen
with the following options.

Gmux-2000 Ver. 3.2

Configuring Connections

5-117

Chapter 5 Configuration
VAD Method
Controls the use of Voice Activity Detection
(VAD) for this bundle

Installation and Operation Manual


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.

The selection is made on a separate screen


with the following options.

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

Configuring Connections

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Chapter 5 Configuration

Installation and Operation Manual


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
TIME SLOT NUM : ts 1
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
TIME SLOT NUM : ts 1
Bundle Number: 1
TS Type
:
NC

ts 2
1
NC

ts 3
1
NC

ts 4
1
NC

ts 5
1
NC

Assign TS Range to Bundle


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

Only for Framed Modes


Not Supported by Data Ports
of Voice Compression Modules

Assign Entire Port to Bundle


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

Not Supported by Data Ports


of Voice Compression Modules

or
Assign Entire TSs to Port
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

Configuring TS Assignment

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>TS Assignment
1.
2.
3.
4.

Card ss/pp
Ts assignment
Assign TS range to bundle
Assign entire port to bundle

... (1/1)
[]>
>
>

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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)

>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Configuring TS Assignment

5-121

Chapter 5 Configuration

Installation and Operation Manual

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

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.
9. To update the online database and activate the new configuration, type %
and then confirm the action.

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.
A typical screen is shown in Figure 5-76.

5-122

Configuring TS Assignment

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)

>
Please select item <1 to 4>
% - UPD DB
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Configuring TS Assignment

5-123

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Configuration>TS Assignment>Assign entire port to bundle
1. Bundle number[1 - 2000]
... (1)
2. Connect entire port to bundle
3. Disconnect entire port from bundle

>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

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.
6. Repeat the procedure for all the desired ports.
7. To update the online database and activate the new configuration, type %
and then confirm the action.

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.

Configuring TS Assignment

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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.
2. Select Ts Assignment to display the individual timeslot assignment screen.
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
leftmost screen section: to see the other sections, scroll to the right.

Pseudowire Gateway
Configuration>TS Assignment>TS assignment
TIME SLOT NUM : ts 1
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

>
Please select item <1 to 4>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-78. Typical Individual Timeslot Assignment Screen for Voice Ports (Left-Hand Side)

Gmux-2000 Ver. 3.2

Configuring TS Assignment

5-125

Chapter 5 Configuration

Installation and Operation Manual

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

Configuring TS Assignment

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Note

Chapter 5 Configuration

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

Configuring TS Assignment

5-127

Chapter 5 Configuration

Installation and Operation Manual

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)

>
Please select item <1 to 3>
ESC-prev.menu; !-main menu; &-exit; @-debug
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.
4. Select Ts Assignment to display the individual timeslot assignment screen.
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
leftmost screen section: to see the other sections, scroll to the right.

5-128

Configuring TS Assignment

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Configuration>TS Assignment>TS assignment
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

>
Please select item <1 to 2>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
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.

Configuring TS Assignment

5-129

Chapter 5 Configuration

Installation and Operation Manual

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

>
[]
>
>
>
[]
[]
>

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Inventory>System
1. System information>
2. SW/HW revision
[]

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

5-131

Chapter 5 Configuration

Installation and Operation Manual

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
>

>
Please select item <1 to 1>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

ESC-prev.menu; !-main menu; &-exit; @-debug


1 M/ 1 C
-----------------------------------------------------------------------------

A. Page 1 of Typical Screen


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
-------------------------------------

ESC-prev.menu; !-main menu; &-exit; @-debug


1 M/ 1 C
-----------------------------------------------------------------------------

B. Page 2 of Typical Screen


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

Viewing Logistic (Inventory) Information

5-133

Chapter 5 Configuration

Installation and Operation Manual

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

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

A. Page 1 of Typical Screen


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

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

B. Page 2 of Typical Screen


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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Viewing Logistic (Inventory) Information

5-135

Chapter 5 Configuration

Installation and Operation Manual

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)

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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
ESC-prev.menu; !-main menu; &-exit; @-debug
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

>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-89. Typical Inventory I/O Slot Selection Screen

Gmux-2000 Ver. 3.2

Viewing Logistic (Inventory) Information

5-137

Chapter 5 Configuration

Installation and Operation Manual

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

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

5-139

Chapter 5 Configuration

Installation and Operation Manual

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. Connection configuration

... (1)
>
(TDMoIP(CE))
>
(UDP/IP)
[]

>

F - next; B - prev;
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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)
Jitter buffer in Ms[0-200]
Sensitivity

Enable
22
23
V2
1
3.00
Sensitive to data

>
F - next; B - prev
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

A. Page 1 of Typical Bundle Inventory Screen


Pseudowire Gateway
Inventory>Bundle>Connection configuration - (BUNDLE 1)
^ 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
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

B. Page 2 of Typical Bundle Inventory Screen

Gmux-2000 Ver. 3.2

Viewing Logistic (Inventory) Information

5-141

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Inventory>Bundle>Connection configuration - (BUNDLE 1)
^ 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
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

C. Page 3 of Typical Bundle Inventory Screen


Figure 5-93. Typical Bundle Inventory Screens (TDMoIP (CE) Bundle)
PseudoWire Gateway
Inventory>Bundle>Connection configuration - (BUNDLE 1)
Connection State
Function
1. Routing Parameters
Max Bytes In Multiplexed Frame[100 - 1461]
Packetizing Interval (Msec)[10 - 90]
2. Connectivity Parameters
3. Voice Parameters

(Disable)
>
(TDMoIP+)
>
... (1400)
... (30)
>
>

>
Please select item <1 to 1>
F - next; B - prev;
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Inventory>Fan

FAN 1-4:
FAN 5-8:

STATUS
Low
Low

EXIST
Yes
Yes

OPERATION STATUS
O.k
O.k

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Viewing Logistic (Inventory) Information

5-143

Chapter 5 Configuration

Installation and Operation Manual

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
--------

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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.
A typical screen is shown in Figure 5-98.

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

>

ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help


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

Viewing Logistic (Inventory) Information

5-145

Chapter 5 Configuration

Installation and Operation Manual

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.
A typical screen is shown in Figure 5-99.

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

>

ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help


1 M/ 1 C
----------------------------------------------------------------------------

Figure 5-99. Typical Inventory>Redundancy>I/O>APS Status Screen

5-146

Viewing Logistic (Inventory) Information

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

Viewing Logistic (Inventory) Information

5-147

Chapter 5 Configuration

Installation and Operation Manual

5.12 Utilities
Overview of Utilities Menu
Figure 5-100 shows the structure of the Utilities menu.
Utilities
Download/Upload by TFTP

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

Installation and Operation Manual

Chapter 5 Configuration

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

>
>
>

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Chapter 5 Configuration

Installation and Operation Manual

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)

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
...>File utilities>Download/upload by TFTP>Activate TFTP
1. File download
2. File upload

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Utilities>File utilities>Internal download
1. CL
2. I/O[1 - 9]

... (0)

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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
Utilities>File utilities>Internal download
1. CL
2. Slot's files
3. Start sw load

>

(N/A)

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Installation and Operation Manual

Chapter 5 Configuration

Pseudowire Gateway
Utilities>File utilities>Internal download
1. CL
2. Slot's files
3. Start sw load

>

(GMUXCL.IMG)

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Utilities>File utilities>Internal upload
1. I/O[1 - 9]

... (0)

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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)

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Installation and Operation Manual

Chapter 5 Configuration

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

>

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

>
>
>
>

>
ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
-----------------------------------------------------------------------------

Figure 5-110. Typical File System Submenu

Gmux-2000 Ver. 3.2

Utilities

5-155

Chapter 5 Configuration

Installation and Operation Manual

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

[]>
[]>

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

To see the navigation keys available for this screen, type ? (help).

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 5 Configuration

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

>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help
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)
[]>

>
ESC-prev.menu; !-main menu; &-exit; @-debug
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

Chapter 5 Configuration

Installation and Operation Manual

Pseudowire Gateway
Utilities>File system>Copy file
1. Enter file name you wish to copy ... ()
2. Enter destination file name
... ()
3. Copy file

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Installation and Operation Manual

Chapter 5 Configuration

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

>

ESC-prev.menu; !-main menu; &-exit; @-debug


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

Chapter 5 Configuration

5-160

Utilities

Installation and Operation Manual

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

Installation and Operation Manual

Table 6-1. Gmux-2000, Outline of Preliminary Configuration Procedure


Step

Action

Using

Select the default database, 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 Configuration>System>Card Type


in 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

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
11

Configuration>System>Management>SNMP Engine ID
Configuration>System>Management>SNMPv3
Setting>Users
Configuration>System>Management>SNMPv3
Setting>Targets & Notify
Configuration>System>Management>SNMPv3 Setting>
SNMPv1/v3 Mapping

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, Configuration>System>Date & Time>Time and Date
set the time of day

3. When NTP synchronization is used,


configure NTP parameters
12

6-2

Save the configured information in the


selected database

Overview

parameters
Configuration>System>Date & Time>NTP Server, GMT,
Update Interval
Configuration>Database Tools>Update Database

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

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 physical layer parameters for each


module, and each module port

Configuration>Physical Layer

Configure timing flow

Configuration>System>Clock Source

Configure redundancy

Configuration>System>Redundancy

Configure connection parameters for each bundle

Configuration>Connection

Configure Gmux-2000 internal routing

Configuration>TS Assignment

Configure Gmux-2000 alarm handling

Configuration>System>Alarms

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
Configuration>Database Tools>Load Database.
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

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

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
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

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

Application 1 Transport of Unframed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

Pseudowire Gateway
Configuration>System>Host IP
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
Configuration>System>Management>Manager list

1.
2.
3.
4.
5.

MNG NUM[1 - 100]


IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[0 - 4095]
VLAN PRIORITY[0 - 7]

...
...
...
>

(1)
(<NMG Station IP>)
(0.0.0.0)
(GIG A-IO 6/1)
(No)
(No)
... (0)
... (0)

4. Save the parameters.


3. Set the SNMP Write community to public to later allow parameters change
using SNMP.
Use Configuration>System>Management>Authentication/Community.
Pseudowire Gateway
Configuration>System>Management>Authentication/Community
1.
2.
3.
4.
5.

Trap community
Read community
Write community
Authentication failure trap
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

Application 1 Transport of Unframed Bundle from E1 Trunk

6-5

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

Pseudowire Gateway
Configuration>System>Management>Management access
1. User Access
2. Telnet/SSH 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
Configuration>System>Clock source>System A>Master clock
1. Master clock source
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
Configuration>Physical Layer
1.
2.
3.
4.
5.
6.

I/O[1 - 9]
E1 port
First GbE IF
Second GbE IF
Delete all slot's bundles
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

Application 1 Transport of Unframed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

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
Assign entire port to bundle
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
Configuration>Connection
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

Application 1 Transport of Unframed Bundle from E1 Trunk

6-7

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

Pseudowire Gateway
Configuration>Connection>Connection configuration -

|
v

^
|
|
v
^
|

Connection state
Source CBID
Dest CBID
Payload format
TDM byte in frame(x48)
Jitter buffer in Ms[0-200]
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
Configuration>TS Assignment>Assign entire port to bundle
1. Bundle number[1 - 2000]
... (1)
2. Connect entire port to bundle
3. Disconnect entire port from bundle

2. Select Connect entire port to bundle.


3. Wait for the Operation Performed message.
Pseudowire Gateway
Configuration>Connection
1.
2.
3.
4.

Bundle number[1 - 2000]


... (1)
Connect entire port to bundle
Disconnect entire port from bundle
Save port assignment

4. Save and update the database.

6-8

Application 1 Transport of Unframed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

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)

2. Open Configuration>System>Management>Manager list.


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.

Authentication failure trap


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


1. Open Configuration>Connection.

Gmux-2000 Ver. 3.2

Application 1 Transport of Unframed Bundle from E1 Trunk

6-9

Chapter 6 Configuring Typical Applications

1.
2.
3.
4.

Bundle ID[1]
Connection mode
PSN type
Bundle connection

Installation and Operation Manual

... (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.

Destination IP address
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]
Destination IP address
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)

Application 1 Transport of Unframed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

6.3

Chapter 6 Configuring Typical Applications

Application 2 Transport of Framed Bundle


from E1 Trunk

Application Overview
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
Assign entire port to bundle
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
1. Open Configuration>Connection.
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

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

Pseudowire Gateway
Configuration>Connection
1.
2.
3.
4.
5.

Bundle ID[1 - 2000]


Connection mode
PSN type
Connection configuration
Save parameters

... (2)
>
(TDMoIP(CE))
(UDP/IP)
[]>

3. Save.
4. Select Connection configuration
Pseudowire Gateway
Configuration>Connection>Connection configuration -

|
v

^
|
|
v
^
|

Connection state
Source CBID
Dest CBID
Payload format
TDM byte in frame(x48)
Jitter buffer in Ms[0-200]
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
Configuration>TS Assignment
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

Application 2 Transport of Framed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

Pseudowire Gateway
Configuration>TS Assignment>Ts assignment
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.

IPmux-11 Configuration
For the following configuration steps, use the latest IPmux-11 Installation and
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

Application 2 Transport of Framed Bundle from E1 Trunk

6-13

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

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
Monitoring>Status>Connection>Bundle counters
1. Bundle ID[1 - 2000]
Destination IP address
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-14

...
...
...
...
...
...
...
...
...
...
...
...
...

(2)
(192.168.100.12)
(OK)
(0)
(0)
(0)
(3)
(5)
(62419)
(62419)
(0)
(2)
(0)

Application 2 Transport of Framed Bundle from E1 Trunk

Gmux-2000 Ver. 3.2

Installation and Operation Manual

6.4

Chapter 6 Configuring Typical Applications

Application 4 Transport of Unframed Bundle


from SDH Network

Application Overview
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.
The application is shown in Figure 6-2.

Note

The configuration procedures illustrated below are based on the use of SNMPv1.

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
Configuration>Physical Layer
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

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

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
Bundle number[1 - 2000]
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.
2. Save the parameters.
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

Application 4 Transport of Unframed Bundle from SDH Network

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

Pseudowire Gateway
Configuration>Connection>Connection configuration -

|
v

^
|
|
v
^
|

Connection state
Source CBID
Dest CBID
Payload format
TDM byte in frame(x48)
Jitter buffer in Ms[0-200]
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
Configuration>TS Assignment>Assign entire port to bundle
1. Bundle number[1 - 2000]
... (3)
2. Connect entire port to bundle
3. Disconnect entire port from bundle

4. Select Connect entire port to bundle.


5. Wait for the Operation Performed message.
Pseudowire Gateway
Configuration>TS Assignment>Assign entire port to bundle
1.
2.
3.
4.

Bundle number[1 - 2000]


... (3)
Connect entire port to bundle
Disconnect entire port from bundle
Save port assignment

6. Save.

Gmux-2000 Ver. 3.2

Application 4 Transport of Unframed Bundle from SDH Network

6-17

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

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

5. Save and update the database.

IPmux-14 Configuration
For the following configuration steps, use the latest IPmux-14 Installation and
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

Application 4 Transport of Unframed Bundle from SDH Network

Gmux-2000 Ver. 3.2

Installation and Operation Manual

6.5

Chapter 6 Configuring Typical Applications

Application 5 Voice Trunking Application

Application Overview
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.
The application is shown in Figure 6-3.

Note

The configuration procedures illustrated below are based on the use of SNMPv1.
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.
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.

Gmux-2000 Ver. 3.2

Application 5 Voice Trunking Application

6-19

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

Pseudowire Gateway
Configuration>System>Card type
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
Configuration>System>Host IP
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.
1. Open Configuration>System>Management>Manager list.
2. Press A to add a manager to the Manager List.
Pseudowire Gateway
Configuration>System>Management>Manager list

1.
2.
3.
4.
5.

MNG NUM[1 - 100]


IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[1 - 4094]
VLAN PRIORITY[0 - 7]

...
...
...
>

(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

Application 5 Voice Trunking Application

Gmux-2000 Ver. 3.2

Installation and Operation Manual

Chapter 6 Configuring Typical Applications

Pseudowire Gateway
Configuration>System>Management>Manager list

1.
2.
3.
4.
5.

MNG NUM[1 - 100]


IP ADDRESS
NEXT HOP
INTERFACE
TRAP(FOR MANAGER)
VLAN VALID
VLAN ID[1 - 4094]
VLAN PRIORITY[0 - 7]

...
...
...
>

(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
Configuration>System>Management>Authentication/Community
1.
2.
3.
4.
5.

Trap community
Read community
Write community
Authentication failure trap
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
Configuration>System>Management>Management access
1. User Access
2. Telnet/SSH 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

Application 5 Voice Trunking Application

6-21

Chapter 6 Configuring Typical Applications

Installation and Operation Manual

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
Configuration>Physical layer
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
Delete all slot's bundles
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]
Assign entire port to bundle
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

Application 5 Voice Trunking Application

Gmux-2000 Ver. 3.2

Installation and Operation Manual

...r>E1 port data 1.


2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Chapter 6 Configuring Typical Applications

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
Configuration>Physical layer
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
Configur