Application Note

Alcatel 1511 BA
Configuration
Application Note
3AL 42463 KAAA PCZZA 01 Released
Alcatel assumes no responsibility for the accuracy of the information presented, which is subject to
change without notice.
Alcatel and the Alcatel logo are registered trademarks of Alcatel. All other trademarks are the property
of their respective owners.
Copyright 2005 Alcatel.

All rights reserved.
Disclaimers
Alcatel products are intended for commercial uses. Without the appropriate network design
engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous
environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life-support machines, or weapons
systems, in which the failure of products could lead directly to death, personal injury, or severe physical
or environmental damage. The customer hereby agrees that the use, sale, licence or other distribution
of the products for any such application without the prior written consent of Alcatel, shall be at the
customer's sole risk. The customer hereby agrees to defend and hold Alcatel harmless from any claims
for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale,
licence or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel products.
Please note that this information is provided as a courtesy to assist you. While Alcatel tries to ensure
that this information accurately reflects information provided by the supplier, please refer to the
materials provided with any non-Alcatel product and contact the supplier for confirmation. Alcatel
assumes no responsibility or liability for incorrect or incomplete information provided about
non-Alcatel products.
However, this does not constitute a representation or warranty. The warranties provided for Alcatel
products, if any, are set forth in contractual documentation entered into by Alcatel and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the
English version and any other version of a document, the English version shall prevail.
PRINTED ON
RECYCLED PAPER
Contents
Contents
1— Introduction 1
1.1 Introduction ...........................................................................................................2
1.2 1511AN Multiplexer ..............................................................................................2
1.3 Connecting the ECT .............................................................................................3
2— Configuration Subracks/Boards 5
2.1 Introduction ...........................................................................................................6
2.2 Declare the Subrack .............................................................................................7
2.3 Declaration of the Boards .....................................................................................9
3— Configuration Path Protection 13

3.1 Introduction .........................................................................................................14
3.2 Release 7.x Mode ...............................................................................................14
3.3 Path Protection Mode .........................................................................................15
3.4 Declaration of the Connections ..........................................................................16
3.5 Circuit Protection ................................................................................................18
3.6 Tribslave Protection ............................................................................................20
3.7 Configuration of the Circuits ...............................................................................22
Sa-MUX and Multipoint Configuration ............................................................23
3.8 Path Protection Enabled .....................................................................................25
3.9 Station configuration ...........................................................................................26
Clock Protection Parameter Fields .................................................................26
General Parameter Fields ...............................................................................27
TMN Parameter Fields ....................................................................................28
Payload Parameter Fields ..............................................................................28
3.10 Tributary Configuration .......................................................................................28
3.11 TMN Path Protection ..........................................................................................29
TMN Station Configuration .............................................................................30
4— Configuration Connections/Circuits 33
4.1 Declaration of the Circuits ..................................................................................34
Normal Configuration ......................................................................................34
LANTRIB Configuration ..................................................................................36
4.2 Creation of the Connections ...............................................................................38
4.3 Save/Send the Configuration to the NE ..............................................................40
4.4 Config 2 on the MUX ..........................................................................................41
5— Configuration Masks 43
5.1 Introduction .........................................................................................................44
5.2 The Logical Address ...........................................................................................44
5.3 The Alarm Masks ................................................................................................45
3AL 42463 KAAA PCZZA Edition 01 Released I

Contents
6— Connection overview 47
6.1 Consulting the Connection Overview ..................................................................48
7— Maintenance Memory Application 49

7.1 What is Maintenance Memory? ..........................................................................50
7.2 Configuration ......................................................................................................50
8— Configuration Switch 53
8.1 Introduction .........................................................................................................54
8.2 Creation of a Configuration .................................................................................54
8.3 Receiving a Configuration ...................................................................................55
8.4 Setting the Active Configuration .........................................................................55
8.5 Displaying the Active Configuration ....................................................................56
9— Alarm, Status and Remote Controls 57

9.1 Introduction .........................................................................................................58
9.2 Alarm and Status ................................................................................................59
9.3 Remote Control ...................................................................................................60
Enabling/Disabling a Loop ..............................................................................60
9.4 Logging ...............................................................................................................60
10 — Performance Monitoring 63
10.1 Introduction .........................................................................................................64
10.2 G.784 Performance Monitoring ...........................................................................64
Starting PM .....................................................................................................65
Displaying PM Data ........................................................................................65
10.3 G.826 Performance Monitoring ...........................................................................67
10.4 Logging PM Data ................................................................................................67
11 — Trib-trib Connections 69
11.1 Connection of Tributaries in the same MUX .......................................................70
12 — FAQ 71
12.1 Troubleshooting ..................................................................................................72
13 — Appendix 75
13.1 Configuration Updates ........................................................................................76
Principle Configuration Updates .....................................................................76
Parameter Changes causing the NE to Reset ................................................76
13.2 Clock Protection = on .........................................................................................76
Clock Synchro Mode: Clock Master ................................................................76
Clock Synchro Mode: Clock Slave ..................................................................76
13.3 Clock Protection =off ..........................................................................................77
clock Synchro Mode: Clock Master ................................................................77
Clock Synchro Mode: Clock Slave ..................................................................77
13.4 CR Alarm ............................................................................................................77
TR alarm .........................................................................................................77
II Released 3AL 42463 KAAA PCZZA Edition 01

Contents
MAP alarm ......................................................................................................78

13.5 Tips and Tricks ...................................................................................................78
3AL 42463 KAAA PCZZA Edition 01 Released III

Contents
IV Released 3AL 42463 KAAA PCZZA Edition 01

1 — Introduction
1.1 Introduction 1-2
1.2 1511AN Multiplexer 1-2
1.3 Connecting the ECT 1-3
3AL 42463 KAAA PCZZA Edition 01 Released 1 / 82

1 — Introduction
1.1 Introduction
This application note gives a short description about the configuration of the
MUltipleXer (MUX)-part of the 1511 BA (or 1511 AN). For a detailed description of the
equipment and the procedures (installation, configuration, maintenance,...) refer to the
User Manual.
1.2 1511AN Multiplexer
The 1511AN is a flexible and modular network element. Some rules, however, must be
followed to configure a system properly.
Caution: Carefully check the strap positions on the boards and the subrack. Wrong
settings may disturb the initialisation and the operation of the MUX. This checking
should be done before the equipment is configured and is put in service.
For the configuration and supervision of the MUX different applications have been
developed *.
• The main configuration application
This application is used to declare the subrack, the boards, the connections,...
• The application for thresholds and masks
This application is used to define some 2Mbit/s parameters, the alarm mask and the
management settings.
• The Earth & (AS&C) application
This application is used to for alarm/status read out and the enabling/disabling of
loops and commands.
• The Administrative application
This application is used to set the Time Of Day.
• The Performance Monitoring Application
This application is used to start/stop the performance monitoring and to display the
results.
The performance monitoring is divided in two parts:
• G.784 for the 2Mbit/s interfaces;
• G.826 for certain tributary circuits.
• The Configuration Switch
This application is used to allow the activation/deactivation of the second
configuration.
Notes:
• This application note is based on the use of the Equipment Craft Terminal (ECT).
Most of the settings can also be done via the Office Craft Terminal (OCT) and the
Mediation Function. The user interface, however, is similar.
• Before the OCT and the mediation function can be used, the equipment must be
manageable and certain parameters must have been programmed via the ECT.
• The requested Alcatel software must be installed on the ECT/OCT.
• * If not all the applications are available, the equipment is in a special state (e.g.
configuration loss). The normal state will be restored after the sending of a valid
configuration (the 2 configuration applications).
2 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

1 — Introduction
1.3 Connecting the ECT
Once the ECT is connected to the F-interface of the Common Network Controller Circuit
(CNCC), the Alcatel 1321NX Network Element Craft Terminal Application Software
(NECTAS) software can be launched. The 'synthesis' screen appears and all available
Network Elements (NEs)* are listed with their assigned Ql-address (e.g. M:0 S:1).
Caution: Use the 9-pin (female) connector on the CNCC to connect the craft terminal;
do NOT use the 9-pin connector on the PCMC2bis board.
Some basic rules:
• The CNCC is a NE that also supervises other NEs:
• 2Mbit/s MUX l51xMX;
• optical line equipment such as 1521FL, 1531FL;
• automatic protection switch APS2M;
• ...
• The supervision bus between the CNCC and the managed NEs is called the Ql-bus.
• Straps and/or switches are used to assign Ql-addresses. The straps are mounted on the
subrack or a dedicated board (QEXA);
• Each time NEs are removed or added, the CNCC must be restarted to allow the update
of the configuration;
• Verify if the NECTAS/ Network Office Craft Terminal Application Software
(NOCTAS) is compatible with the operating system and the equipment that must be
managed;
• Verify if the correct application software has been installed on the Craft Terminal
(CT).
To start an application, the list of available applications must be called. This is done by
clicking twice on the NE identification (left part of the line). A list that contains the
applications for this particular NE will appear. This list can also be displayed by clicking
once on the NE identification (left part of the line) and selecting 'Application_Choice' on
the menu line.
The application itself is selected and launched by clicking twice on the application title
or by clicking once on the application line and the 'OK' button.
* NE: some equipment that can be managed as being a unit (CNCC, APS, 1511PL, ...).

1 — Introduction
Figure 1-1 Main Synthesis Screen (NECTAS)
1 2 4
3
1 Q1 address of this NE (e.g. = 6)
2 NE identification and release: CNCC release 6.1 and MUX release 6.0
3 Click twice to display the available applications for this NE
4 Synthesis info for this NE: TC, AE, DC, LC are active
Figure 1-2 Supported Applications
1 2
1 CNCC
2 MUX (initial state)
3 MUX (configured state)
4 Double click here to select this application

2 — Configuration Subracks/Boards
2.2 Declare the Subrack 2-7
2.3 Declaration of the Boards 2-9

2.1 Introduction
Different levels have been defined for the configuration of a MUX and its boards/
interfaces.
Figure 2-1 Main Configuration Application
1 Subrack level
The type of subrack must be specified. If more than one MUX is supported, a
selection on MUX level must be done.
2 Board level
This means the board itself and the settings that are done on board level and that are
affecting all the circuits on the board (e.g. signalling conversion for the Earth &
Mouth (E&M) wires).
3 Circuit level
A board may contain different circuits (1,3,4,6,15,...). A circuit is an elementary unit
that may have its own settings (e.g. gain on an POTS board).
4 Connections
The connections between the tributaries and the aggregate 2Mbit/s link must be
specified.
5 Additional functions
Functions such as EOC, tone generator, ... must be configured if used.
Note: To create a configuration the user has to define/configure these levels.

When the main configuration application has been started, the main screen is displayed.
Pull down menus are used to display/select the available options.
2.2 Declare the Subrack
The subrack is selected via the option 'Configuration - New subrack'. A list that contains
the available subracks will be displayed.
Some subracks have been designed to be equipped with more than one MUX. These
subracks must be seen as existing of smaller subracks sharing the supervision Q1 bus and
the power distribution. Each MUX will be representing one line in the main synthesis
screen. Each MUX is a NE on its own.
Note: If the subrack contains different MUX systems, the user has to select one of the
MUX systems.
The dialog box 'Variant' is used to select the part of the subrack (the MUX system) while
the other dialog boxes will provide additional information.
Notes:
• If the correct MUX is not selected, a configuration can be created and sent but the
results are unpredictable.
• If only one multiplexer will be equipped in a subrack that supports more than one
multiplexer, the multiplexer that should be used is determined by the layout of the
subrack:
• 3AL42912: the leftmost MUX
• 3AL42914: the rightmost MUX
• If PCMC2bis boards are used as tributaries (slave controllers), additional
configuration rules must be applied.
Figure 2-2 Subrack Variants

In this example, the subrack 3AL42914 has been selected. This subrack contains two
MUX systems. The rightmost part of the subrack (XX-2) will be used in this application
note.
Figure 2-3 Subrack - Selection
3AL42914 2
XX-1 XX-2
1 6 7 17
1 Subrack type
2 Subrack part
The subrack (or a part of it) is now displayed. A small box represents a slot position in
the selected (part of the) subrack.
Figure 2-4 Subrack View
1 2
1 Slot (position) in the subrack / physical slot number

2 Slot (position) in the MUX part of the subrack / logical slot number

Remarks:
• The subrack may contain boards that are not belonging to the MUX itself. These
boards can be declared as 'non-MUX' boards to indicate the slot that is occupied by
this board. There are no other actions possible via the main configuration application
of the MUX for these boards.
• Non-MUX boards that can be declared: 15x1FL, APS2M, CNCC, 1511PL, ...
• If a subrack contains more than one MUX system, the slot numbering on the display
is adapted and a difference is made between the physical slot number and the logical
slot number.
• The physical slot number is the slot number in the subrack itself. The logical slot
number starts counting from the first slot belonging to this MUX. The subrack view
will display both slot numbers.
• This application is using the database on the PC. Every modification is based on this
database. The real configuration of the MUX will be updated after a 'SEND'
command that will send the configuration from the craft terminal to the MUX.
2.3 Declaration of the Boards
A board can be declared by clicking twice in the box that represents its slot position (or
by selecting a position and using the selection 'Configuration-Declare/Modify board').
A list that contains the supported boards for the selected position will be displayed. The
board can be selected now.
Use the sequence below to declare the boards:
1 The master controller
2 The slave controller and the tributaries

Figure 2-5 Board Level - Selection of Slot/Board (N*64kbit)
1
2
4
1 Board level
2 Selected slot
3 OK
4 Select the board
If parameters must be set (by hardware or by software) the settings must be entered while
the board is declared (the available options/selections depend on the board type). These
parameters have an impact on board level. If parameters exist on circuit level, it will be
indicated during the creation of a circuit.
The hardware settings (straps) can be displayed by selecting the option 'Display straps'.
The database now visualises the strap settings, according to the selected options.
Caution: The software cannot verify the actual hardware settings. The displayed straps
are based on the settings the operator entered during the creation of the board/circuit.

Figure 2-6 Board Level - Settings (15ch E&M)
1 Settings on board level (hardware settings via straps/switches or software controlled

settings)
2 Straps on board level, according to the settings
3 Display Straps button
4 OK
The selected board and its parameters are accepted by selecting the' Apply' option. The
database on the PC is updated. By selecting 'Close' the main screen will become visible
again.
A declared board becomes a small black box instead of a white box. The graphical
representation of the board depends on the board itself (tributary, DCIDC/
PCMC2bis,...).
A circuit on a board is visualised as a small box below the board icon itself.

Figure 2-7 Board Level
1 5
2 4
6
1 DC/DC
2 Selected board
3 Board contains 15 circuits
4 Board contains 4 circuits
5 non-MUX board
6 Selected board info

3 — Configuration Path Protection
3.2 Release 7.x Mode 3-14
3.3 Path Protection Mode 3-15
3.4 Declaration of the Connections 3-16
3.5 Circuit Protection 3-18
3.6 Tribslave Protection 3-20
3.7 Configuration of the Circuits 3-22
3.8 Path Protection Enabled 3-25
3.9 Station configuration 3-26
3.10 Tributary Configuration 3-28
3.11 TMN Path Protection 3-29

3.1 Introduction
Note: If no path protection is used in your equipment, please skip this chapter and refer
to chapter 4.
It is advisable, if Telecommunication Management Network (TMN) master station
protection is needed, in order to minimize your inputs, to complete the Sa MUX +
multipoint configuration window first before going in to path protection mode. If doing
so some inputs will be duplicated from the ‘Normal map’ to the ‘Map1’.
Depending on the used subrack the rack position of the master (red), primary and
additional slave (green) controllers are defined in case of path protection. Consult the
PCMC-controllers user manual in order to see which rack positions can be used for the
slave controllers.
TRIButaries (TRIBs) can be installed in allowed free positions of the subrack, the
configuration tool checks whether that is allowed.
3.2 Release 7.x Mode
If path protection mode is not selected, then the CT operates in the same look & feel as
in release 7.x.

3.3 Path Protection Mode
For not protected connections it is advisable to make these connections before entering
the path protection mode. Otherwise these connections must be made in both maps.
If path protection is needed the option ‘enter the Path protection mode’ in the
Configuration window has to be activated. If done the option is marked with a flag.
Figure 3-1 Enter the Path Protection Mode
• Resetting this option can only be done by re-initialization of the subrack.

• Selecting the path protection mode can only be done after the declaration of the
subrack, configuration and at least the master (red position) and the primary slave
controller (green position). The following window will come up as a warning.
Figure 3-2 Warning Screen
• A new button called ‘MAP’ is introduced in the ‘defining of the circuits' window. In
the path protection mode the maps (Normal map and Map1) have to be configured for
each defined circuit.

3.4 Declaration of the Connections
The declaration of the connections is explained in Figure 2-3 and 2-4.
Figure 3-3 Equipment Configuration Window
1
4 5
1 Defined board
2 Defined circuit

3 Map selector: Normal/Map 1

4 Slave controller for path protection
5 Master controller
Note: In this version MAP2 is not yet implemented.

Warning: 'RX/TX Crossed (Upper and Lower) Internal Bus' on the Primary slave
controller with path protection is NOT allowed (see figure 3-5).
Figure 3-5 Board Configuration Window

3.5 Circuit Protection
Any circuit of a tributary can be path protected through the slave controller and master
controller.
To achieve this:
3
2
1 Select a circuit. Therefore put the cursor on the circuit. Click the mouse button and
hold the button. An icon will come up.
2 Drag this icon to the slavetrib (or to the master controller depending on the ‘system’
configuration). While doing this action the selected controller will flash in blue.
3 Release the button when the mouse is positioned on the wanted controller. The
‘Tributary Circuit Connection’ window will come up.
The window is devided in three sub windows: ‘Tributary’, ‘Bus’ and ‘2Mbits/s
Timeslot /Tributary’. The ‘Tributary’ sub window only shows the selected tributary
with the connected slot and circuit.
4 The ‘Bus’ sub window allows to:
• choose the bus [1 or 2].
• choose the TimeSlot (TS) [any free TS from 1 to 31] (the system proposes the first free
TS).
• select the ‘Consecutive Allocation’ option showing the timeslot allocation of the internal
bus.

5 The ‘2Mbits/s Timeslot /Tributary’ sub window allows to:

• select the controller (already declared in previous screen), but can be changed to another
if needed
• reserve a 2 Mbits/s timeslot for the connection of the selected circuit
• set the ‘Signalling’. A number of possibilities are shown, choose signaling 120 for the
connection to the primary.
6 At this point the ‘Normal map’ is configured. Now the same actions need to be done
for the ‘map1’ (if master was connected in ‘Normal map’ use now primary slave in
‘map1’ or visa versa).
Figure 3-7 Tributary Circuit Connection Window
4 5

3.6 Tribslave Protection
A Tribslave is a slave controller used as a kind of Nx64k board with flexible user ports.
User ports can be anything between 1 TS and 30 TSs depending on the used bandwidth.
The "user ports" in this case are not hardware related like on a tributary board, but are the
tribslave's timeslots on the 2Mbits.
Follow these steps to achieve this:
Figure 3-8 Trib Slave Protection Part 1
2 1
1 Select a controller. Click the mouse button and hold the button. An icon will come up.
2 Drag this icon to the primary slave controller (or to the master controller depending
on the system configuration). While doing this action the selected controller will
flash in blue. Releasing the button will perform the ‘2Mbits/s Timeslot <> 2Mbits/s
Timeslot’ window.
3 Select the desired bandwidth.
4 Select the ‘Allocation’ button to perform the ‘TS allocation of PCM controller’
window. This window shows the used TSs. If connected to the slave controller: use
signalling 120 on the primary slave side.
For each part of the ‘2Mbits/s Timeslot <> 2Mbits/s Timeslot’ window the TS
allocation table can be consulted.
5 Next to this the 2Mbit TS of the Tribslave need to be set in path protection mode. Use
figure 3-9 to follow the different steps.
First change from ‘Normal Map’ to ‘MAP1’.
6 Select the tribslave controller.

7 Drag and drop to the master controller. As a result the ‘TS allocation of PCM
controller’ window will pop up.
8 Click the ‘Allocation’ button of the Tribslave controller. The ‘TS allocation of PCM
controller’ window will pop up.
9 The already allocated TS of the former map are seen in blue.
10 Hit one of them in order to allocate the TS to the master controller. Now the ‘2Mbits/
s Timeslot <> 2Mbits/s Timeslot’ window will pop up, including the update info.
11 Finally the allocated TS will come up in the ‘2Mbits/s Timeslot <> 2Mbits/s
Timeslot’ window.
Figure 3-9 Trib Slave Protection Part 2
10
11

3.7 Configuration of the Circuits
The configuration of the circuits is explained in Figure 2-10.
Figure 3-10 Configuration of the EOC Circuits
2
1
1 Select the board by double clicking on the symbol, or by selecting the board and via
option ‘Declare/Modify board’ in the ‘configuration window’. A double click on the
desired circuit also gives the same result.
2 Select the circuit option.
3 Perform the bit allocation by selecting the number of bits
Formula: Number of bits >= (RQ2 speed / 2000) +1
Examples: 1200 = 2 bit, 2400 = 3 bits, 4800 = 4 bits

Sa-MUX and Multipoint Configuration

The ‘Sa MUX and Multipoint’ window is used to set he internal connections. This
window can be selected via the ‘Connection’ pull down menu of the ‘Equipment
Configuration window’ (see figure 3-4).
Configuration of the Master Controller of the Master EOC Station:
Figure 3-11 Sa MUX and Multipoint Window
1
6
4 7
8
5
1 Select the master controller position, consult in the ‘Equipment Configuration’

window in which slot position the master controller is installed (slot number in red).
2 The master will come up on top in the multipoint function window (white window),
therefore start with the master of the multipoint.
3 Select in the ‘Mode’ window the ‘Master’ (master of the multipoint) button.
4 Select in the ‘New member’ window the ‘EOC’ button.
5 Select the position of the controller and the circuit number (meaning EOC channel).
6 Confirm by selecting ‘Add’ in the ‘Multipoint function’ window. Hereby the member
will be filled in the ‘Multipoint function’ window and the ‘Mode’ window will skip
from master to slave. The slave part Sa- MUX & MPT connections can be performed.
7 Four types can be chosen in the ‘New member’ window:
• ‘Sa Mux’: which bit is pre-defined in former option.
• ‘Multipoint’: select in the identification window the slot position of the slave, member,
bus and internal TS.
• ‘External TS’: select a time slot in the identification window (be sure not to use already
reserved TS).
• ‘EOC’: Figure 3-12 shows in the master NE the relations between the master controller
and the slave controller.
8 Apply.

Figure 3-12 Relation Master/Slave Controller in the MUX
Bus & TS
Configuration of the Primary Slave Controller of the Master EOC Station:

This procedure is similar with the master controller of the master MUX.
1 Select the slave controller (green slot number figure 3-4).
2 The ‘Multipoint function’ window shows the MPT link which was made for the
master controller.
3 Available buttons in the ‘New Member’ window can be added:
• In case of ‘External TS’ button: Timeslot can be chosen in the ‘Identification’
window.
• In case of ‘Multipoint’ button: Position and member can be chosen in the ‘Identification’
window.
• ‘Sa Mux’ button.
4 Apply to confirm.
Note 1: In case of Sa-MUX on Slave controller, the Sa-bit(s) are not filled in
automatically.
Note 2:On the controllers on which no EOC circuit is declared you need to fill in the Sa-
bit(s) manually:
1 Consult the ‘Bit Allocation’ window on the EOC circuit of the master controller.
2 Click on the desired Sa-bit(s).
3 Apply to confirm.
Alternative: Select the same Sa-bit(s) that are filled in the "Sa MUX & Multipoint"
window of the master controller and switch to the slave controller: The Sa-bit(s) will be
taken over.

This ends the procedure for the Normal map. Both maps (‘Normal map’ and ‘Map1’ have
to be configured. Therefore go back to the beginning of the procedure and proceed
configuration of the master controller and the slave controller of the MUX.
Due to synchronisation reasons, changes in the TMN configuration needs to be done in
both maps (‘Normal Map’ and‘Map1’).
• Go back to 4 of the ‘Sa MUX and Multipoint’ window.
Configuration of the Slave EOC Stations:
Analog on the configuration of a Master MUX, the SLAVE MUXs have to be
configured. Keep in mind that some parameters need to be synchronized with the ones
used for the Master MUX, and this for all connected Slave MUXs using TMN path
protection.
• Go back to 1 of the ‘Sa MUX and Multipoint’ window.
Backup Path configuration of the SLAVE MUXs: analog to ‘Normal Path’.
• Go back to step 4 of the ‘Sa MUX and Multipoint’ window.
3.8 Path Protection Enabled
Changing the path protection state between enabled/disabled results in a controlled

restart (software initiated one) of the NE.
Figure 3-13 Path Protection Enabled
1 Path protection on/off button

3.9 Station configuration
This window is divided in 4 parts: ‘General’, ‘Payload’, ‘TMN’ and ‘Clock’.
Figure 3-14 Station Configuration Window
1 2
5 6 3
Clock Protection Parameter Fields

Following parameters determine the behaviour of the clock protection (see figure 3-14):
1 Protection - On/Off
This parameter enables/disables the clock switching mechanism.
If the clock switching mechanism is in the off state then only the highest priority
clock source is taken into account, depending on the 'clock synchro mode'.
In case this parameter indicates 'master: ...' the highest priority clock source is the
internal clock or the external clock (see step 3).
If the 'clock synchro mode' indicates 'slave: ...' then the 'preferred active path'
parameter indicates the highest priority clock.
2 Revert to Original Path - Yes/No
In case the 'revert' parameter is 'on' the clock switch algorithm selects always to
regenerate the clock from the side which has the highest priority (see step 3) and a
valid clock indication.
In case the 'revert' parameter is 'off' no clock switching takes place as long the
selected clock remains good.

3 Clock Source
This parameter indicates if the NE is a clock master or clock slave.
To configure the NE as clock slave select one of the 'Slave: ....' modes, all modes
behave the same, the highest priority clock is indicated by the 'Preferred active path'
parameter (see step 2).
In case of clock master the NE distributes the clock and the 'good' clock indication in
both directions. Three choices are possible to configure the NE as master, namely:
• 'Master: internal clock', the clock is always the internal clock.
• 'Master: External->Master Internal clock', the highest priority clock is the external clock
and the backup clock is the internal clock.
• 'Master: External->Master Regenerated clock', the highest priority clock is the external
clock and the backup clock is the master (depending of the preferred path) regenerated
clock.
• Additional slave.
4 Preferred Active Path - master/slave
Indicates which side (master or slave controller) of the NE has the highest priority in
the clock selection mechanism. This parameter is only applicable if the clock synchro
mode is one of slave modes (see step 3).
5 X-bit for Clock Protection
With this parameter the X-bit can be selected which is used to pass the 'good' clock
indication between adjacent NE's. The selected x-bit must be the same for all NEs in
a chain.
Note that changing the selected x-bit causes the NE to do a controlled restart.
6 Clock End Point
Indicates if a NE is connected to another element type.
Note that the x-bit at a 'clock end point' is not forwarded/interpreted.
The x-bit is always driven to 1 and the clock is by default always 'good'.
7 Error persistency
General Parameter Fields

Following parameters determine the behaviour:
• Primary Slave Controller position
• Secondary Slave Controller position
• Additional Slave Controller position

TMN Parameter Fields

Following parameters determine the behaviour of the TMN protection:
• Protection - On/Off
• Revert to Original Path - Yes/No
• EOC Channel for TMN
• TMN Mode
• Preferred Active Path
• Sa bit
• Error persistency
Payload Parameter Fields

Following parameters determine the behavior of the Payload:
• Error persistency
• BER treshold
3.10 Tributary Configuration
First be sure that the connections are already declared, for instance the signaling
selectors, the maps, Protected / Not protected mode.
Figure 3-15 Configuration of the Tributaries - Tributary Window
2 3
1 Rack position of the tributaries

2 Not protected circuits are grey
3 Defined circuits for path protection

For each installed tributary board a ‘Tributary ‘window is available called a tributary
POS-ition. Depending on the installed tributary some circuits can be declared. For
declared circuits four buttons can be set. This buttons can only be accessed after path
protection is made on that circuit.
Table 3-1 Explication of the Buttons
Preferred Active Path
Checked means that all connections declared in the Normal Map

are applicable
Not checked means that all connections declared in the Map1 are
applicable
Protected Mode
Checked means individually circuits can be set in the Protected

mode
Not checked means individually circuits can be set in the Not Protected
mode
Revert to Original Path (Works only if Protected mode is checked)
Checked means when the original path becomes available the

circuit will switch to the original path
Not checked means when the original path becomes available the
circuit will NOT switch to the original path and stays in the
backup path
Mode for Backup Path

Checked Quiet/AIS is sent to the backup path
Not checked data is broadcasted to the Normal and Backup path as

well
Note: Protected circuits are in black, not protected circuits are grey coloured.
3.11 TMN Path Protection
A network consists of a Master MUX and some Slave MUXs:

• The Master MUX needs 2 EOC channels (1 for the Mediation Device (e.g. A1322VD)
and 1 for the CNCC).
• The Slave MUX needs only 1 EOC channel (for the CNCC).
A multipoint is the link between the master & the slave controller of the MUX. The RQ2
path is protected via the multipoint function of the controller. The multipoint consists of
1 master and has to be realized on the first line, followed by some slaves. This action has
to be performed for the master controller and the slave controller of the MUX. And this
for the ‘Normal Path’ and ‘Backup Path’ as well.
A MUX has a master controller and a slave controller.

TMN Station Configuration

Figure 3-16 shows the ‘TMN Station Configuration’ window:
Figure 3-16 TMN Station Configuration Window
3
1
4
5
Master MUX
How to configure the master MUX (see figure 3-16):
1 Choose the ‘TMN Mode’: The station (also called MUX) has to be defined as master
station or slave station.
• A network consists of one master MUX while the other MUXs of the network has to be
defined as slave MUX.
• In case of master MUX a mediation device is connected via a remaining EOC channel of
the master controller.
2 Choose a ‘Sa bit’ for TMN Protection: ( - , Sa4, Sa5, Sa6, Sa7 or Sa8).
Note: This selected Sa-bit has to be used for all other NE in the network.
3 Choose the ‘EOC channel for TMN’ protection: ( - ,1 or 2).
4 Choose the ‘Preferred Active Path’: (‘Normal map’, ‘map1’ or ‘map2’).
5 Apply to confirm.
This ends the procedure for the ‘Preferred Active Path’. Now if needed the backup path
can be configured. Therefore go back to the beginning of the procedure and proceed
configuration of the master controller and the slave controller of the MUX.
• Go back to 4 of the ‘TMN Station Configuration’ window.
Due to synchronisation reasons, changes in the TMN configuration needs to be done in
both maps (‘Normal Map’ and ‘Map1’).

Slave MUX
Analog on the configuration of a master MUX, the slave MUXs have to be configured.
Keep in mind that some parameters need to be synchronized with the ones used for the
master MUX, and this for all connected slave MUXs using TMN path protection.
• Go back to 1 of the ‘TMN Station Configuration’ window.
Backup Path configuration of the SLAVE MUXs: analog to ‘Normal Path’.
• Go back to 4 of the ‘Station Configuration’ window.


4 — Configuration Connections/Circuits
4.1 Declaration of the Circuits 4-34
4.2 Creation of the Connections 4-38
4.3 Save/Send the Configuration to the NE 4-40
4.4 Config 2 on the MUX 4-41

4.1 Declaration of the Circuits
The normal configuration of the circuits and the LANTRIB configuration are explained
separately below.
Normal Configuration
To define/declare a circuit follow the procedure below and see figure 4-1:
1 Click twice on the box that visualises the circuit (or by selecting 'Configuration-
Declare/Modify Circuit'). If this circuit is not been defined yet, it should be a white
box.
A list with the available settings (on circuit level) will be displayed and the
parameters can be adjusted now.
Note: The timeslot(s) that must be selected, is a timeslot on the internal bus, not on
the G.703/G. 704 link.
2 By selecting 'Apply' the settings are stored in the database on the PC.
3 The option 'Display straps' can be used to visualise the strap settings.
4 By selecting 'Close' the main screen will become visible again.
Note: It is not necessary, however, to use every time the ‘Close’ option. By modifying
the dialog boxes for slot position, circuit level, board level, number... It is possible to
define boards / circuits without returning to the main screen after every operation.
5 A circuit that has been defined will be visualised by a small box with a black
background that contains a small triangle.

Figure 4-1 Circuit Level - Declaration
2
3
5 5
The boards and the circuits are defined now. There is, however, not yet a connection with
the 2Mbit/s aggregate. Every timeslot that has been defined up to now, was related to the
internal bus that is used to carry the information from the aggregate to the tributary and
vice versa.
The selectable options can be related to software settings or hardware jumpers or straps).
The software cannot verify the hardware settings and the operator should take care that
the required hardware settings are done and verified. The 'Display Straps' option displays
the straps as should be set for the entered settings.

LANTRIB Configuration
Declaring the Board

The LAN TRIButary (LANTRIB) is declared like any other normal tributary board. It
has access to both busses. The rectangles beneath the board symbol represents the busses
instead of the circuits.
Figure 4-2 Board Declaration
Declaring the Circuit

The LANTRIB has only one circuit. But this circuit can have access to one (upper) bus
in Point-to-Point mode, or to both busses in Cascading mode. Selecting the circuit part
of the LANTRIB opens a dedicated ‘LANTRIB’ configuration window (see figure 4-3).
Figure 4-3 LANTRIB Configuration Window

1

This window is divided in three regions:

1 Common parameters
This region contains the common parameters of the board and is always filled in.
Default buttons can be used to select the default values. Parameter ranges can be seen
by hovering over the input fields.
‘Timeslot allocation’ is/are the time slot(s) used on the upper connector. It can be
bus 1 or 2 depending on the position of the LANTRIB in the subrack.
These are the only parameters needed in Point-to-Point mode. Change ‘Type of
Configuration’ to ‘Point-to-Point’ if this type of configuration is needed. All other
parameters will be grayed out in this case.
2 Cascading parameters
Only available when ‘Type of Configuration’ is set to ‘Cascading’. The lower bus is
also used in this case. The number of time slots on the lower bus must be the same as
the number of time slots of the upper bus. The time slot allocation bar becomes red
when there is a time slot allocation error. ‘Spanning Tree Mode’ can be enabled in
Cascading mode.
‘Number of stations’:
• Load balancing: If load balancing is used, the number of stations used in the LAN has
to be entered here in order to provide an equal bandwidth to all stations.
• Ring network: In a ring network, the ‘number of stations’ has to be set on 2. This is the
default value. No load balancing is performed here.
3 Spanning Tree parameters
Here all the spanning tree parameters are entered. Spanning tree can only be enabled
in Cascading mode.
The following buttons are also located on the ‘LANTRIB’ configuration window:
• Apply
Saves all parameters into the internal database and go back to the board window.
• Close
Closes the window without saving.
• Delete
Press delete to ‘unlock’ previous declared bus time slots and connections. Declared
time slot allocations are grayed out.
Making Connections
After configuring the LANTRIB circuit, the connections to the controller(s) must be
made. In case of Point-to-Point only one set of time slots located on the upper connector.
The second rectangle stays white in this case.
Both busses are available in Cascading mode. Normally connections are made to two
different controllers.
Path Protection
Path protection is only possible in Point-to-Point mode. There is no sense in using
Cascading mode in a path protection configuration. Enable spanning tree mode if path
protection is needed.

However the Cascading mode can be used not protected (connections in both maps to the
same controller) in a protection mode.
4.2 Creation of the Connections
The connections are defined between the internal bus (the tributary circuits) and the
G.703/G.704 link. Using the Time Space Switch (TSS) on the Pulse Code Modulation
(PCM) controller, connections are set up with a granularity of 64 kbit/s.
A connection can be created by 'dragging’ the circuit to the controller (or by selecting the
circuit and the command 'Connection-Create'). With ‘dragging’ is meant selecting a
circuit by clicking once on the circuit icon and moving it to the PCM controller while
keeping the mouse button pressed.
During this action, the cursor may have two forms.
Table 4-1 Cursor Forms
Symbol Description
No connection is possible: the mouse pointer is positioned on an object or circuit
where no connection can be made
A connection is possible: the mouse pointer is positioned on a board or circuit where

a connection can be made
A signalling type must be specified for each connection.

Notes:
• This signalling type (also called 'Signalling Selector') is very important for the
treatment of events/alarms and signalling conditions.
• The selection of the signalling selector should be based on recommendations from the
support team.
• The signalling selector to be selected depends on:
• The circuit. The configuration application only displays the signalling selectors that are
compatible be used with this circuit.
• The service or operating mode that must be offered
- e.g. pots or hot line for a tributary board
- e.g. Nx64kbit/s with or without network alarm
- e.g. 64kbit/s connection with AIS or idle pattern in case of alarm
- ...

Figure 4-4 Creating a Connection
1
2
Internal 4
bus 1 PCMC2bis
slot 5
circuit 1 SS 221 2Mbit/s
SPCMS4 TS1 slot 8
1 Tributary circuit
2 Internal bus time slot
3 2Mbit/s aggregate board and time slot
4 Signalling selector
When the connections are defined, it can be helpful to display the connections that are
already existing. If the option 'Connection, Overview' is selected, a list that contains the
connections and the signalling types is displayed. If more than one PCMC2 controller is
equipped in the MUX, it is also possible to select the controller.
If needed the signalling selector can be modified or the connection can be deleted.

Figure 4-5 Connection Overview

1
1 Selected board to display the connections
Notes:
• Connections between PCMC2bis boards (Master-Slave) are not described in this
application note.
• The 1511BA also supports the feature 'Trib-Trib' connections (not described here).
4.3 Save/Send the Configuration to the NE
The configuration has now been prepared. It must, however, be sent to the equipment
before it becomes active.
Before sending a configuration to the equipment, it must be saved on the hard disk or a
floppy disk. It is a good practice to save the configuration under a recognisable name.
• To save a configuration to disk, we use the option 'File > Save as'. The application will
display a file header that can be used to store some comments*.
• To send a configuration to the NE, we use the option 'File > Send'. If we did not save
the configuration before, the application will save the configuration using the current
file name.
The application will now send the configuration to the CNCC, afterwards the CNCC
sends the configuration to the MUX itself. The communication between CNCC and
MUX is indicated by the 'ST' flag that goes on (in the alarm synthesis screen).
The moment this indication goes off, the configuration has been sent to the MUX.
Note: *These comments are not stored in the NE itself (only on the disk).

4.4 Config 2 on the MUX
The MUX contains two configuration banks for the main configuration. If one of these
banks is not valid, a status or an alarm will be raised: 'C1' or 'C2'. Most of the times the
'C2' alarm is active since a configuration has been sent to the first bank only.
To clear this alarm, two options are available:
• Modify the alarm masks to prevent that this state becomes an alarm indication.
• Save a valid configuration in the second bank.
Figure 4-6 Config 2 on the MUX
File saved/opened in /Alcatel/151XMX60

3 (release independent)
1 Saved and sent as configuration 1 (bank 1)

2 Select files for config 1 or config 2
3 Select the retrieval of config 1 or config 2


5 — Configuration Masks
5.2 The Logical Address 5-44
5.3 The Alarm Masks 5-45

5.1 Introduction
This application is used during the configuration of the MUX.

The most important parameters that can be set are:
• The address for supervision (logical address) if a mediation function is used.
• The alarm masks for the supervision and the maintenance memory.
To set up a configuration, we can:
• Load a configuration from disk (Option 'File, Open');
• Start from a default configuration (Option 'File, Default Status');
• Receive the configuration from the NE (Option 'File, Receive').
If the configuration has been modified, it must be saved (option 'File, Save as') and be
sent to the MUX (option ('File, Send').
5.2 The Logical Address
The logical address is used for the communication with the mediation function.
Figure 5-1 Logical Address
3
2
1 Must be selected
2 Enable logical address
3 Logical address
The parameters are accessible via' System > Equipment'.

5.3 The Alarm Masks
The alarm masks are used to determine what kind of an alarm should be generated by an
event. Every event that happens in the MUX will be compared with the alarm masks for:
• Urgent alarm
• Non-urgent alarm
• External alarm (Signal Failure)
There are also masks for the maintenance memory.
Figure 5-2 Alarm Masks 1

Figure 5-3 Alarm Masks 2
1 Loss Of Signal (LOS) generates an urgent alarm and is stored in the maintenance
memory. No signal failure is generated.
2 Alarm Indication Signal (AIS) on 2Mbit/s generates no urgent/non-urgent alarms,
signal failure is generated. It is not stored in the maintenance memory.

6 — Connection overview
6.1 Consulting the Connection Overview 6-48

6 — Connection overview
6.1 Consulting the Connection Overview
The connection overview window allows seeing the settings for the master and slave
controllers (PCMC2bis), the tributaries and the internal bus.
Note: Select a map before selecting a connection overview.
Figure 6-1 Connection Overview
1 Selected map
2 Clicking on ‘Overview’ brings up the ‘Connection Overview’ window

7 — Maintenance Memory Application
7.1 What is Maintenance Memory? 7-50
7.2 Configuration 7-50

7.1 What is Maintenance Memory?
The Maintenance Memory (MM) can be found in the NE itself. It is used to store events,
even without the craft terminal connected. Using this feature the alarm history can be
verified or analysed.
In the 1511BA the maintenance memory is a function of the CNCC board where it
handles the CNCC and the underlying NEs (MUX, 1521FL,...).
So called 'Maintenance Memory masks' are used to determine if a certain event must be
stored in the maintenance memory. Once the maintenance memory is filled up for 100%,
the oldest entries are deleted (circular buffer).
7.2 Configuration
MM commands:
• The maintenance memory masks are defined via the application 'Configuration >
Thresholds and Masks'
• To Consult/Save/Clear the maintenance, a dedicated application 'Maintenance
Memory' is available.
• To consult the MM, the operator first has to 'Receive' the MM.
• If the operator selects 'File, Receive', the MM is sent from the CNCC to the craft
terminal. The operator may define additional filters that are used by the application to
build up the display. Only the matching events that were stored in the MM are
displayed.
• By sending the command 'Clear' to the CNCC, the maintenance memory is cleared.
• It is also possible to store the MM on the disk or to print the contents of the MM.
Figure 7-1 Maintenance Memory

Figure 7-2 Maintenance Memory Windows
1 ON
2 OFF


8 — Configuration Switch
8.2 Creation of a Configuration 8-54
8.3 Receiving a Configuration 8-55
8.4 Setting the Active Configuration 8-55
8.5 Displaying the Active Configuration 8-56

8.1 Introduction
Two configurations can be stored on the PCMC2 board. One of these configurations is
called the' active configuration' and is used by the system to determine the declared
board, circuits, connections, ...
The application 'Configuration Switch' allows the operator to determine the active
configuration.
8.2 Creation of a Configuration
To set up a configuration, the 'Equipment Configuration (Main)' application must be

used.
Note: The double configuration only exists for the Configuration Application (Main).
• When the option 'File > Save' or 'File > Save as' has been selected the user must
indicate whether the configuration will be saved as the 'first' or 'second' configuration.
Note: Configuration 1 and 2 have a different file extension.
• When the option 'File > Open' has been selected the user must indicate whether the
'first' or 'second' configuration will be displayed.
• When the option 'File > Send' has been selected, the loaded or created configuration
will be sent to the equipment.
The used configuration is displayed in the title bar of the Configuration - Main task (using
[x]).

8.3 Receiving a Configuration
When the user selects the 'File > Receive' option, the configuration number must be
selected (default is configuration 1).
Figure 8-1 Config 1 and 2
1 Receive/send configuration number
8.4 Setting the Active Configuration
To set up the active configuration, the application 'Configuration Switch' has to be used.

8.5 Displaying the Active Configuration
The active configuration is displayed via the 'AS&C' application.
Figure 8-2 Active Configuration
1 Active configuration

9 — Alarm, Status and Remote Controls
9.2 Alarm and Status 9-59
9.3 Remote Control 9-60
9.4 Logging 9-60

9.1 Introduction
This application allows the operator to retrieve detailed information from the 1511BA
(MUX part). The synthesis line of NECTAS only indicates the presence of alarm
conditions without specifying additional info. Also the available software controlled
loops are accessible via this application.
The application 'Alarm, Status and remote Controls' (for a NE) is started by clicking
twice on the application name or by clicking once on the application name and selecting
'OK'. The application will retrieve the configuration from the equipment (if needed) and
a graphical presentation of the NE is shown.

9.2 Alarm and Status
By using the two mouse buttons the operator can zoom in/out (left button to zoom in,
right button to zoom out). If the cursor becomes a magnifying glass, a zoom in can be
performed.
The alarm/status of the equipment is displayed using different colours:
• green: OK
• Yellow: non urgent alarm
• red: urgent alarm
• magenta: status (no alarm)
The mapping event/alarm is based on the alarm masks that are defined in the 'Thresholds
& Masks' application.
Figure 9-1 Alarm and Status Windows
1 Synthesis
2 Alarm, Status and remote control
3 Zoom in

9.3 Remote Control
Most of the equipment will accept remote controls:

• loops (e.g. on timeslot level)
• switch on/off for line feedings
• switch over commands for protection switching
• ...
Figure 9-2 Remote Control
ANAL.LOOP on Uk0 INTF

Analogue loop on Uk0 interface is set.
Enabling/Disabling a Loop
The operator has to select a loop using the option 'Remote Control > All' or 'Remote
Control > Current display'. If 'Current display' is selected, only the loops that can be
enabled/disabled on the equipment/circuit that is displayed will be available.
After selecting a loop a message box will be displayed to indicate that the remote control
is sent to the equipment. To be sure that the loop itself is activated, the ‘AS&C’ display
has to be checked, the loop is indicated as a status/alarm.
9.4 Logging
As long as the application' Alarm, Status and remote Controls' is active, the alarms are
stored in logging files. Using the 'History' option the log files can be consulted/printed.
Next time the application is launched, the logging starts on top of the existing file*. An
indication will be put in the file to indicate the 'resynchronisation'.
Notes:
• If the application is terminated, the logging stops but the log file is not deleted.
• * Two log files (about 3000 entries each) are used. If both files are filled up, the oldest
file is deleted and created again.

Figure 9-3 Logging of Synthesis and AS&C
Also the synthesis creates a logging. It is accessible via the main menu bar.
Figure 9-4 AS&C Logging


10 — Performance Monitoring
10.2 G.784 Performance Monitoring 10-64
10.3 G.826 Performance Monitoring 10-67
10.4 Logging PM Data 10-67

10.1 Introduction
Most network elements contain hardware/software for Performance Monitoring (PM).

Most of the performance monitoring is done on 2Mbit/s links (the RX and/or RX/TX
side). The used variables to calculate the PM data depend on the NE itself and the settings
(e.g. with or without CRC4).
Two performance-monitoring definitions are used:
• G.784 for the 2Mbit/s links (RX with CRC-4 activated)
• G.826 for a number of tributary links (e.g. U6-VAM)
10.2 G.784 Performance Monitoring
The performance monitoring data contains:

• Errored Seconds (ES)
• Severely Errored Seconds (SES)
• UnAvailable time (UA)
This information can be calculated for a period of 15 minutes or 24 hours. In the NE
itself, registers are used to collect the information for the selected period. Once the period
has finished, the registers are 'frozen' and can be read out by the craft terminal. The new
information is put in another set of registers. Using this mechanism, a buffer for a few
periods is available in the NE.
Figure 10-1 G.784 Performance Monitoring

Notes:
• If the registers are not read out, the information will be overwritten after 3 or 4
periods.
• The CRC-4 must be enabled to generate PM data.
Starting PM
Before PM data is available, the process must be started in the NE itself. This is done via
the 'Performance Monitoring' application on the craft terminal.
The user has to select (option 'Mode'):
• Period (15' or 24 h)
• Retrieve mode:
• Manual: the operator has to issue the command to read out the counters in the NE
• Auto: the craft terminal automatically reads the counters in the NE each 15' or 24h
• Start/Stop PM process for a monitor point in the NE
• The PM process for each monitor point can be activated/deactivated.
• If the option 'Start' is selected a list with the available monitors is displayed. A
PCMC2bis only has one monitor point (RX).
Displaying PM Data
Once the data is collected from the NE, it will be formatted and displayed. Colours are
used to indicate the results of the PM period.
The user can define two thresholds that are used by the craft terminal to determine the
colour to use:
• Green: no errors at all
• Magenta: errors but below the lowest threshold
• Yellow: errors but between the lower and higher threshold
• Red: errors, above the higher threshold
If needed, a zoom can be commanded to display the number of errors for this period.

Figure 10-2 PM - Selection & Display 1
Figure 10-3 PM - Selection & Display 2

10.3 G.826 Performance Monitoring
Some tributaries are supporting the G.826 Performance Monitoring. The PM data can be
displayed using the application 'G.826 Performance Monitoring'. The PM data for all
available circuits will be displayed.
Figure 10-4 G.826 Performance Monitoring
10.4 Logging PM Data
As long as the craft terminal is connected and the PM application is running, the PM data
is logged on the hard disk. If the craft terminal is not connected or the PM application is
not running, the only source for the data are the PM counters in the NE itself. This is,
however, only for a limited period.


11 — Trib-trib Connections
11.1 Connection of Tributaries in the same MUX 11-70

11 — Trib-trib Connections
11.1 Connection of Tributaries in the same MUX
Most of the time a 1511BA MUX is used to connect tributary circuits to an aggregate
2Mbit/s link on the PCMC2bis board via the internal bus 1 and 2.
It is possible to install additional PCMC2bis boards as 'slave' aggregates for ‘drop and
insert’ applications or grooming. Additional features such as bus crossing allow the
connection from tributaries to slave controllers.
The trib-trib connection feature allows the connection of tributaries in the same MUX
(e.g. a Constant Bit Rate (CBR) circuit and a POTS circuit in the same MUX) or
PCMC2bis-trib connections without bus crossing. The configuration steps required for
this feature are not described in detail.
Figure 11-1 Trib-trib Connections

12 — FAQ
12.1 Troubleshooting 12-72

12 — FAQ
12.1 Troubleshooting
This is a list of possible problems you might encounter together with their proposed
solutions.
Table 12-1 FAQ
Problem Suggested action
Some controllers (PCMC2) are not seen Check the following items:
by the CNCC. • Has the CNCC been reset after the installation of the
controller? If not, reset the CNCC.
• Are the backpanel strapping (on the back panel or the
QEXA board) ok?
• Is the Q1 cable installed and fault free (if more than one
subrack is supervised by the CNCC).
• Are there no overlapping Q1-addresses between line
equipment and PCMC2bis controllers?
• Is the table 'Info about MUX' already modified?
Unexpected alarms are displayed; these • Check the internal bus (bus crossing on the PCMC2bis.
alarms do not make sense. Maybe a wrong selection is disturbing the internal bus
that is also used to send alarms from the tributaries to the
PCMC2bis controller.
• If you are using a VAM tributary or an ISDN tributary,
check the clock source of the master controller. A looped
(via a plug) 2Mbit/s without the internal clock selected can
disturb the PLL on the tributary board.
I cannot save/load a configuration on a Nectas/Noctas uses a dedicated directory scheme to store

floppy disk the applications and the configuration files. If you want store
configuration files on a floppy, you can:
• Store the files on the hard disk [16] and use the file
manager to copy the files to the floppy. Afterwards you
can copy the files back from floppy to hard disk.
Note: Nectas/Noctas stores the configuration files in the
directory '\ALCATEL\xxxxx'; xxxxx is the NE identification
(e.g. '151XMX60 for the MUX, release 6.0')
• Create the directory structure on the floppy. Afterwards, it
will be recognised by Nectas/Noctas and you can save/
load configurations on floppy.
I cannot display the PM data, all the time Probably the CRC4 has not been enabled. The MUX needs
'No data' is displayed. the CRC4 error data to calculate the performance monitoring
data.
I've set up a configuration with a number Most likely there is a synchronisation problem and slips are
of MUX equipments, a DACS,... but there causing these errors. Check carefully the settings for the
are sometimes bit errors (PM and BER clock source on all involved network elements.
test), 'DF' or 'EF' indications in the
embedded operation channels.
A link does not become operational. The Most likely the CRC-4 settings are not compatible.
AS&C on one of the MUXs reports
'Frame Alignment Loss'.
I need more than one PCMC2bis in a It is possible to use more than one PCMC2bis in a MUX. This
MUX. configuration can be used for Drop & Insert applications or for
the grooming of 2MbitIs links.
The usage of additional PCMC2bis boards in a MUX require
additional configuration steps and are described in other
application notes.

12 — FAQ
Figure 12-1 1511BA - Configuration

12 — FAQ

13 — Appendix
13.1 Configuration Updates 13-76
13.2 Clock Protection = on 13-76
13.3 Clock Protection =off 13-77
13.4 CR Alarm 13-77
13.5 Tips and Tricks 13-78

13 — Appendix
13.1 Configuration Updates
Principle Configuration Updates

Any change of parameters related to the clock protection has as result that the clock
protection mechanism is triggered to select the highest priority clock independent of the
'revert' parameter.
In case the clock protection is switched off and the highest priority clock is not available
then no clock switch takes place until the highest priority clock becomes good or the
current selected clock becomes bad (any good to bad transition).
Parameter Changes causing the NE to Reset

There are two cases where configuration changes result in a controlled reset of the NE,
namely:
• Changing the selected x-bit (see 3.9)
• Changing the selected Sa bit (see 3.9)
13.2 Clock Protection = on
With the clock protection ‘on’ the clock synchro mode can be ‘clock master’ or ‘clock
slave’.
Clock Synchro Mode: Clock Master

Clock master (preferred path parameter does not matter) clock priorities:
Table 13-1 Clock Master Clock Priorities
Internal Internal
External/Internal External [1] -> Internal
External/Regenerated External [2] -> Master (depending of preferred path) Regenerated

External [3] -> Internal
External [4]
• [1] loss of external clock

• [2] loss of external clock, NE acts as configured as slave
• [3] loss of master (depending of preferred path) regenerated clock, indicated by x-
bit=1, or TFC1 alarms
• [4] no good clock available anymore, set x-bit=1
Clock Synchro Mode: Clock Slave

The clock slave priority clock priorities depending on preferred path:

13 — Appendix
Table 13-2 Clock Slave Clock Priorities
Master Slave Regenerated [1] Primary Slave Regenerated [2] -> Internal
Primary Slave Regenerated [2] Master Slave Regenerated [1] -> Internal [3]
• [1] loss of good clock at master side, indicated by x-bit=1, or TFC1 alarms
• [2] loss of good clock at slave side, indicated by x-bit=1, or TFC1 alarms
• [3] no good clock available anymore, set x-bit=1
13.3 Clock Protection =off
With the clock protection ‘off’ the clock synchro mode can be ‘clock master’ or
‘clock slave’.
clock Synchro Mode: Clock Master

Clock master (preferred path parameter does not matter) clock priorities:
Table 13-3 Clock Master Clock Priorities
Internal Internal
External/Internal External [1] -> Internal [2]
External/Regenerated External [1] -> Internal [2]
• [1] loss of external clock

• [2] x-bit are always driven to 0
Clock Synchro Mode: Clock Slave

The clock slave clock priorities depending on preferred path:
Table 13-4 Clock Slave Clock Priorities
Master Slave Regenerated [1] Internal
Primary Slave Regenerated [2] Internal
• [1] loss of good clock at master side, indicated by x-bit=1, or TFC1 alarms
• [2] loss of good clock at slave side, indicated by x-bit=1, or TFC1 alarms
13.4 CR Alarm
Indicates that the preferred clock is not the selected clock.
TR alarm
Indicates that the active TMN path is not the preferred one.
3EC 36103 AAAA TCZZA Edition 0113-77

10 Februari 2003 NNP 90-xxxx-xx
13 — Appendix
MAP alarm
For each circuit 6 alarms are possible: 3 (N, 1, 2) for the Map and 3 (N, 1, 2) for the
alarms.
Note: Map2 is not implemented (future use)
13.5 Tips and Tricks
A list of tips and tricks:

• Watch out where to position (green positions only) the primary slave controller. Only
these slave PCMC controllers positions put the slave regenerated clock on the
backplane.
• Disable of TMN Path protection: The end station of a network has to be configured
as TMN END STATION. If not, the network will be unstable and the network
becomes unreachable.
• Declaring an EOC on the slave controller of a slave station in Path protected mode is
not allowed.
• Signaling: When a connection is created a Signaling type has to be selected. Some
restrictions has to be considered: e.g. RAC Signaling 120 is not allowed and should
be 304
Consult also the Signalling Types Overview (3AL 42464 AAAA ANAAA) for more info
• Use always Signaling 120 to the primary slave controller in path protecting mode
• If protection is enabled but you create a not protected circuit (connections in both
maps to the same controller) to the Slave PCMC2 controller, you have to choose the
correct signaling selector (for instance Hot Line in case of signaling and not 120
Transparent)
• Consistence maps: changing something in a certain map, after that path protection has
been set up, It is mandatory to do the same changes in the other map.

Abbreviations
1511AN old name for 1511 BA (Business Access). 1511 BA is the official name of this equipment
AIS Alarm Indication Signal
AS&C Alarm, Status and remote Control
CBR Constant Bit Rate
CNCC Common Network Controller Circuit
CT Craft Terminal
ECT Equipment Craft Terminal
ES Errored Seconds
E&M Earth & Mouth
LANTRIB LAN TRIButary
LOS Loss of Signal
MM Maintenance Memory
MS Microsoft
MUX MUltipleXer
NE Network Element
NECTAS Network Element Craft Terminal Application Software
NOCTAS Network Office Craft Terminal Application Software
OCT Office Craft Terminal
PC Personal Computer
PCM Pulse Code Modulation
PCMC PCM Controller
PM Performance Monitoring
SES Severely Errored Seconds
SWDL Software Download
SWP Software Package
TMN Telecommunication Management Network
TRIB TRIButary

TS Time Slot
TSS Time Space Switch
UA UnAvailable time

82

Application Note

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Application Note

Transféré par

Droits d'auteur :

Formats disponibles

Alcatel 1511 BA

Copyright 2005 Alcatel.

3— Configuration Path Protection 13

3AL 42463 KAAA PCZZA Edition 01 Released I

7— Maintenance Memory Application 49

9— Alarm, Status and Remote Controls 57

II Released 3AL 42463 KAAA PCZZA Edition 01

MAP alarm ......................................................................................................78

3AL 42463 KAAA PCZZA Edition 01 Released III

IV Released 3AL 42463 KAAA PCZZA Edition 01

1.1 Introduction 1-2

1.2 1511AN Multiplexer 1-2

1.3 Connecting the ECT 1-3

3AL 42463 KAAA PCZZA Edition 01 Released 1 / 82

1.2 1511AN Multiplexer

2 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

1.3 Connecting the ECT

3AL 42463 KAAA PCZZA Edition 01 Released 3 / 82

Figure 1-1 Main Synthesis Screen (NECTAS)

Figure 1-2 Supported Applications

4 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

2.1 Introduction 2-6

2.2 Declare the Subrack 2-7

2.3 Declaration of the Boards 2-9

3AL 42463 KAAA PCZZA Edition 01 Released 5 / 82

Figure 2-1 Main Configuration Application

Note: To create a configuration the user has to define/configure these levels.

6 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

2.2 Declare the Subrack

Figure 2-2 Subrack Variants

3AL 42463 KAAA PCZZA Edition 01 Released 7 / 82

Figure 2-3 Subrack - Selection

Figure 2-4 Subrack View

1 Slot (position) in the subrack / physical slot number

8 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

2.3 Declaration of the Boards

3AL 42463 KAAA PCZZA Edition 01 Released 9 / 82

Figure 2-5 Board Level - Selection of Slot/Board (N*64kbit)

10 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

Figure 2-6 Board Level - Settings (15ch E&M)

1 Settings on board level (hardware settings via straps/switches or software controlled

3AL 42463 KAAA PCZZA Edition 01 Released 11 / 82

Figure 2-7 Board Level

12 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

3.1 Introduction 3-14

3.2 Release 7.x Mode 3-14

3.3 Path Protection Mode 3-15

3.4 Declaration of the Connections 3-16

3.5 Circuit Protection 3-18

3.6 Tribslave Protection 3-20

3.7 Configuration of the Circuits 3-22

3.8 Path Protection Enabled 3-25

3.9 Station configuration 3-26

3.10 Tributary Configuration 3-28

3.11 TMN Path Protection 3-29

3AL 42463 KAAA PCZZA Edition 01 Released 13 / 82

3.2 Release 7.x Mode

14 / 82 Released 3AL 42463 KAAA PCZZA Edition 01

3.3 Path Protection Mode

Figure 3-1 Enter the Path Protection Mode

• Resetting this option can only be done by re-initialization of the subrack.

Figure 3-2 Warning Screen

3AL 42463 KAAA PCZZA Edition 01 Released 15 / 82