Marconi MSH 86x SLAT Procedures

GENERAL INDEX
GENERAL INDEX.....................................................................................................................1
PRELIMINARY INFORMATION ........................................................................................... 31

INTRODUCTION .................................................................................................................................31
Contents of handbook.......................................................................................................................31
Conventions used in this handbook..................................................................................................31
HARDWARE REQUIREMENTS .........................................................................................................31
Hardware Platform ............................................................................................................................31
SOFTWARE REQUIREMENTS..........................................................................................................32
Local Controller for Unix Operating System .....................................................................................32
Local Controller for Windows NT Operating System .......................................................................33
Local Controller for Windows 2000 Operating System ....................................................................33
Year 2000..........................................................................................................................................33
INSTALLATION AND CONNECTION OF THE PC TO THE EQUIPMENT ......................................33
Personal Computer Installation.........................................................................................................33
INSTALLATION OF SOFTWARE PLATFORM..................................................................................33
Unix Operating System with OSF/MOTIF ........................................................................................33
Retix LT610.......................................................................................................................................34
Windows NT / 2000 Operating System ............................................................................................34
X-NutCracker ....................................................................................................................................34
INSTALLATION OF LOCAL CONTROLLER......................................................................................35
Local Controller for SCO/Unix ..........................................................................................................35
Users and Directories .......................................................................................................................35
Installation Procedure for SCO/Unix.................................................................................................36
Local Controller for Windows NT / 2000...........................................................................................40
Installation Procedure for Windows NT / 2000.................................................................................41
Customizing the LC Configuration for SCO/Unix Version................................................................46
Customizing the LC Configuration for Windows NT / 2000 Version ................................................47
Connect the Personal Computer to the Equipment .........................................................................49
Connect Personal Computer to a Printer .........................................................................................53
USERS INTERFACE ............................................................................................................ 54

WORKING AREA ................................................................................................................................54
How to Move a Window in the Working Area...................................................................................55
How to Move a Window to the Front ................................................................................................57
Menu Selection .................................................................................................................................58
Information Boxes .............................................................................................................................59
DIALOG BOXES..................................................................................................................................60
STARTING LOCAL CONTROLLER .................................................................................... 63
COPYRIGHT - Refer To Title Page Marconi

.
339-1063/14 Navigation Page Book Contents
Issue:1
MSH8X - OPERATOR'S HANDBOOK
GENERAL INDEX
SCO/UNIX VERSION ..........................................................................................................................63

WINDOWS NT / 2000 VERSION ........................................................................................................64
LOCAL CONTROLLER MAIN WINDOW ...........................................................................................67
Initial Printer Selection ......................................................................................................................68
Initial Printer Setup............................................................................................................................68
NEs Domain Management ...............................................................................................................69
Control Session Activation................................................................................................................71
SHUTTING DOWN THE COMPUTER ...............................................................................................73
SCO UNIX Shut Down Procedure....................................................................................................73
Windows NT / 2000 Shut Down Procedure......................................................................................73
DXC MAIN MENU.................................................................................................................. 74

GENERAL INFORMATION.................................................................................................................74
Operational Feature ..........................................................................................................................75
DXC Messages .................................................................................................................................75
Alarm Summary Indication................................................................................................................76
Signallers...........................................................................................................................................76
Other Indications ...............................................................................................................................78
MANAGING SUBRACK CONFIGURATION ....................................................................... 79

PRINTER: SELECTION ......................................................................................................................79
NE MODEL: SELECTION ...................................................................................................................79
NE MODEL: DEFINING LOCATION AND ALARM INTERFACE ......................................................80
Rack Visual Indications.....................................................................................................................81
CONTROL AND TIMING SUBRACK: COMMISSIONING.................................................................82
Control and Timing Subrack: equipping ...........................................................................................83
Control and Timing Subrack: displaying operational state...............................................................84
Control and Timing Subrack: modifying unit configuration...............................................................84
Control and Timing Subrack: removing a unit ..................................................................................84
Control and Timing Subrack: displaying inventory data...................................................................84
Control and Timing Subrack: displaying software version ...............................................................84
Input Ground Contacts: configuring..................................................................................................85
Output Ground Contacts: configuring...............................................................................................86
Output Ground Contacts: switching..................................................................................................87
Ground Contacts: reading state........................................................................................................87
MATRIX SUBRACK: COMMISSIONING (DXC 4/1) ..........................................................................88
Matrix Subrack: equipping unit (DXC 4/1) ........................................................................................88
Matrix Subrack: displaying information (DXC 4/1) ...........................................................................89
Matrix Subrack: modifying configuration (DXC 4/1) .........................................................................90
Matrix Subrack: decommissioning (DXC 4/1) ..................................................................................90
Matrix Subrack: displaying free accesses (DXC 4/1) .......................................................................90
Matrix Subrack: displaying accesses status (DXC 4/1) ...................................................................90
Matrix Subrack: displaying traffic information (DXC 4/1)..................................................................91
Matrix Subrack: displaying inventory data (DXC 4/1).......................................................................91

.
339-1063/14 Navigation Page 2 Book Contents
Issue:1
GENERAL INDEX
Matrix Subrack: displaying software details (DXC 4/1) ....................................................................91

TYPE 2 SUBRACK: COMMISSIONING .............................................................................................92
Type 2 Subrack: equipping ...............................................................................................................92
Type 2 Subrack: displaying information............................................................................................93
Type 2 Subrack: modifying configuration .........................................................................................94
Type 2 Subrack: decommissioning ..................................................................................................94
Type 2 Subrack: displaying matrix accesses map ...........................................................................94
Type 2 Subrack: displaying inventory data.......................................................................................95
Type 2 Subrack: displaying software details ....................................................................................95
TYPE 3 SUBRACK: COMMISSIONING .............................................................................................96
Type 3 Subrack: equipping ...............................................................................................................96
Type 3 Subrack: displaying information............................................................................................98
Type 3 Subrack: modifying configuration .........................................................................................98
Type 3 Subrack: decommissioning ..................................................................................................99
Type 3 Subrack: displaying inventory data.......................................................................................99
Type 3 Subrack: displaying software details ....................................................................................99
TYPE 4 SUBRACK: COMMISSIONING ...........................................................................................100
Type 4 Subrack: equipping .............................................................................................................100
Type 4 Subrack: displaying information..........................................................................................101
Type 4 Subrack: modifying configuration .......................................................................................102
Type 4 Subrack: decommissioning ................................................................................................102
Type 4 Subrack: displaying matrix accesses map .........................................................................102
Type 4 Subrack: displaying inventory data.....................................................................................103
Type 4 Subrack: displaying software details ..................................................................................103
TYPE 6E SUBRACK: COMMISSIONING.........................................................................................115
Type 6E Subrack: equipping...........................................................................................................115
Type 6E Subrack: displaying information .......................................................................................120
Type 6E Subrack: modifying configuration.....................................................................................120
Type 6E Subrack: decommissioning ..............................................................................................121
Type 6E Subrack: displaying inventory data ..................................................................................121

.
Issue:1
GENERAL INDEX
Type 6E Subrack: displaying software details................................................................................121

TYPE 7E SUBRACK: COMMISSIONING.........................................................................................128
Type 7E Subrack: equipping...........................................................................................................128
Type 7E Subrack: displaying information .......................................................................................133
Type 7E Subrack: modifying configuration.....................................................................................133
Type 7E Subrack: decommissioning ..............................................................................................134
Type 7E Subrack: displaying inventory data ..................................................................................134
Type 7E Subrack: displaying software details................................................................................134
BOOSTER SUBRACK: COMMISSIONING......................................................................................135
Booster Subrack: equipping............................................................................................................135
Booster Subrack: displaying information ........................................................................................136
Booster Subrack: modifying configuration......................................................................................136
Booster Subrack: decommissioning ...............................................................................................136
Booster Subrack: displaying inventory data ...................................................................................137
Booster Subrack: displaying software details.................................................................................137
UNIT: COMMISSIONING ..................................................................................................................137
Unit: equipping (DXC 4/1) ...............................................................................................................137
Auxiliary Unit: equipping .................................................................................................................144
Unit: displaying information.............................................................................................................144
Unit: modifying configuration...........................................................................................................144
Unit: decommissioning....................................................................................................................145
Unit: resetting ..................................................................................................................................145
PORT: CONFIGURATION ................................................................................................................146
Port: configuring operational parameter .........................................................................................147
Port: displaying operational parameters .........................................................................................172
Port: modifying operational parameters..........................................................................................172
Port: removing configuration...........................................................................................................172
2Mbit/s Port: configuring global parameters...................................................................................173
2Mbit/s Port: displaying global parameters.....................................................................................174
2Mbit/s Type 2 Port: configuring global parameters.......................................................................174
2Mbit/s Type 2 Port: displaying global parameters ........................................................................175
34Mbit/s Port: configuring global parameters.................................................................................176
34Mbit/s Port: displaying global parameters ..................................................................................176
34Mbit/s T-Mux Port: selecting the channel to discard ..................................................................177
140Mbit/s T-Mux Port: configuring the VC-12 POH .......................................................................177
140Mbit/s T-Mux Port: displaying the VC-12 POH.........................................................................178
4x34Mbit/s Videocodec Port: configuring global parameters.........................................................178

.
Issue:1
GENERAL INDEX
4x34Mbit/s Videocodec Port: displaying global parameters ..........................................................179

2Mbit/s Port: configuring the G703/G704 frame characteristics ....................................................179
2Mbit/s Port: displaying the G703/G704 frame characteristics......................................................180
1x45Mbit/s T-Mux Port: setting the VC-12 parameter....................................................................180
1x45 T-Mux Mbit/s Port: displaying the VC-12 parameter .............................................................181
STM-1 Port: setting HPOM alarm suppression state .....................................................................182
STM-1 Type 2 Port: setting C2 mismatch detection state..............................................................182
34/45Mbit/s, 140Mbit/s, STM-N and NxSTM-1 Ports: displaying the SOH bytes status...............182
STM-N and 2xSTM-1 Ports: managing the optical parameters.....................................................182
STM-N Port: configuring VC-4 operational parameter ...................................................................184
LPOM Ports: configuring LO VC operational parameter (DXC 4/1) ..............................................187
LPOM Ports: displaying LO VC operational parameter .................................................................191
STM-N Port: configuring frame and supervisory unequipped state...............................................192
AU Group Definition ........................................................................................................................195
SONET STS-1 Setup......................................................................................................................199
Port Mode Setup .............................................................................................................................203
SYNCHRONIZATION.......................................................................................................... 204
SYNCHRONIZATION: DISPLAYING INFORMATION.....................................................................204
SYNCHRONIZATION: DEFINING A PORT SUBRACK AS SYNCHRONIZATION SOURCE.......206
Synchronization: defining a port as synchronization source ..........................................................206
Synchronization: displaying port parameters .................................................................................208
Synchronization: removing a synchronization port.........................................................................209
SYNCHRONIZATION: DEFINING PRIORITY TABLE FOR THE MAIN OSCILLATOR.................209
SYNCHRONIZATION: DEFINING PRIORITY TABLE FOR SECONDARY OSCILLATOR ...........211
SYNCHRONIZATION: CONFIGURING MODE ...............................................................................212
SYNCHRONIZATION: SWITCHING SYSTEM SYNCHRONIZATION SOURCE ..........................215
SYNCHRONIZATION: SWITCHING EXTERNAL OUTPUT SYNCHRONIZATION SOURCE......216
SYNCHRONIZATION: CALIBRATING THE TIMING SELECTOR OSCILLATOR UNIT................217
SYNCHRONIZATION: SELECTING THE TIMING SIGNAL ON TEST POINT OF TS...................218
SYNCHRONIZATION: SETTING PLL CUT FREQUENCY .............................................................219
SYNCHRONIZATION: RESTORING OOF SYNCHRONIZATION SOURCE.................................220
PROTECTION AND TEST .................................................................................................. 221

CT SUBRACK PROTECTION: DISPLAYING UNIT STATE............................................................221
CT SUBRACK PROTECTION: SWITCHING ...................................................................................222
CT SUBRACK PROTECTION: DISPLAYING SIO LINE STATE.....................................................223
MATRIX SUBRACK PROTECTION: DISPLAYING .........................................................................223
MATRIX SUBRACK PROTECTION: SWITCHING ..........................................................................223
PORT SUBRACK PROTECTION: SELECTION ..............................................................................224
Port Controller Protection: displaying .............................................................................................224
Port Controller Protection: switching...............................................................................................224
Multiplexing Section Protection: configuring...................................................................................225
Multiplexing Section Protection: displaying ....................................................................................233

.
Issue:1
GENERAL INDEX
Multiplexing Section Protection: removing......................................................................................233

Multiplexing Section Protection: modifying .....................................................................................233
Multiplexing Section Protection: switching......................................................................................234
NxSTM-1 Unit Protection: configuring ............................................................................................235
NxSTM-1 Unit Protection: displaying information...........................................................................235
NxSTM-1 Unit Protection: removing ...............................................................................................235
NxSTM-1 Unit Protection: switching ...............................................................................................236
63x2Mbit/s Unit Protection: configuring ..........................................................................................237
63x2Mbit/s Unit Protection: displaying information.........................................................................237
63x2Mbit/s Unit Protection: removing.............................................................................................237
63x2Mbit/s Unit Protection: switching.............................................................................................238
4x34Mbit/s T-Mux Unit Protection: configuring...............................................................................238
4x34Mbit/s T-Mux Unit Protection: displaying information .............................................................238
4x34Mbit/s T-Mux Unit Protection: removing .................................................................................239
4x34Mbit/s T-Mux Unit Protection: switching .................................................................................239
1x45Mbit/s T-Mux Unit Protection: configuring...............................................................................239
1x45Mbit/s T-Mux Unit Protection: displaying information .............................................................240
1x45Mbit/s T-Mux Unit Protection: removing .................................................................................240
1x45Mbit/s T-Mux Unit Protection: switching .................................................................................240
2Mbit/s Unit Protection: configuring ................................................................................................241
2Mbit/s Unit Protection: displaying information...............................................................................241
2Mbit/s Unit Protection: removing...................................................................................................242
2Mbit/s Unit Protection: switching...................................................................................................242
4x34Mb/s Videocodec Unit Protection: configuring........................................................................243
4x34Mb/s Videocodec Unit Protection: displaying information ......................................................243
4x34Mb/s Videocodec Unit Protection: removing ..........................................................................243
4x34Mb/s Videocodec Unit Protection: switching ..........................................................................244
3x34-45Mbit/s Unit Protection: configuring.....................................................................................244
3x34-45Mbit/s Unit Protection: displaying information ...................................................................245
3x34-45Mbit/s Unit Protection: removing........................................................................................245
3x34-45Mbit/s Unit Protection: switching........................................................................................246
3x34-45Mbit/s Line Protection: configuring ....................................................................................247
3x34-45Mbit/s Line Protection: displaying information...................................................................248
3x34-45Mbit/s Line Protection: removing .......................................................................................248
3x34-45Mbit/s Line Protection: switching .......................................................................................249
140Mbit/s Line Protection: configuring ...........................................................................................250
140Mbit/s Line Protection: displaying information ..........................................................................250
140Mbit/s Line Protection: removing ..............................................................................................250
140Mbit/s Line Protection: switching ..............................................................................................251
140Mb T-Mux Line Protection: configuring.....................................................................................251
140Mbit/s T-Mux Line Protection: displaying information...............................................................252
140Mbit/s T-Mux Line Protection: removing...................................................................................252
140Mbit/s T-Mux Line Protection: switching...................................................................................252
DXC TYPE THREE PROTECTION: SELECTION ...........................................................................253

.
Issue:1
GENERAL INDEX
DXC Type Three Protection: configuring........................................................................................254

DXC Type Three Protection: displaying information ......................................................................256
DXC Type Three Protection: modifying..........................................................................................256
DXC Type Three Protection: switching ..........................................................................................257
DXC Type Three Protection: removing ..........................................................................................258
DXC Type Three Protection: swapping role...................................................................................258
PROTECTIONS LIST: FILTER .........................................................................................................259
Protections List: reading .................................................................................................................259
PORT SUBRACK PROTECTION: SETTING THE WTR PERIOD..................................................259
HOLD OFF: MANAGEMENT ............................................................................................................260
PORT LOOPBACKS: MANAGING ...................................................................................................261
Loopbacks: configuring the mapping state.....................................................................................261
Loopbacks: displaying the mapping state ......................................................................................261
2Mbit/s Port Loopback: configuring ................................................................................................262
2Mbit/s Port Loopback: displaying state.........................................................................................262
63x2Mbit/s Unit Port Loopback: configuring...................................................................................263
63x2Mbit/s Unit Port Loopback: displaying state............................................................................264
4x34Mbit/s T-Mux Unit Port Loopback: configuring .......................................................................264
4x34Mbit/s T-Mux Unit Port Loopback: displaying state ................................................................265
NxSTM-1 Port Loopback: configuring ............................................................................................265
NxSTM-1 Port Loopback: displaying state .....................................................................................266
STM-N Port Loopback: configuring ................................................................................................266
STM-N Port Loopback: displaying state .........................................................................................267
140Mbit/s Port Loopback: configuring ............................................................................................267
140Mbit/s Port Loopback: displaying state.....................................................................................268
140Mbit/s T-Mux Port Loopback: configuring.................................................................................268
140Mbit/s T-Mux Port Loopback: displaying state .........................................................................268
1x45Mbit/s T-Mux Port Loopback: configuring...............................................................................269
1x45 Mbit/s T-Mux Port Loopback: displaying state.......................................................................269
1x45Mbit/s T-Mux Port Loopback: channel configuration ..............................................................270
1x45 Mbit/s T-Mux Port Loopback: displaying channel state.........................................................271
34/45 Mbit/s Port Loopback: configuring ........................................................................................271
34/45 Mbit/s Port Loopback: displaying state.................................................................................272
Loopback: displaying ......................................................................................................................272
TEST STATE: MANAGEMENT.........................................................................................................273
WIRING TEST: EXECUTION............................................................................................................273
Wiring Test: displaying information.................................................................................................274
MATRIX SUBRACK TEST: ACTIVATING (DXC 4/1).......................................................................276
Matrix Subrack Test: displaying information (DXC 4/1) .................................................................277
PORT/MATRIX SUBRACK LINK TEST: ACTIVATION (DXC 4/1) ..................................................277
Port/Matrix Subrack Link Test: displaying information (DXC 4/1)..................................................278
DATABASE TEST: ACTIVATION .....................................................................................................279
CCU FAULT HISTORY BUFFER: DISPLAYING .............................................................................279
CCU STATE: CONFIGURING ..........................................................................................................280

.
Issue:1
GENERAL INDEX
MANAGING CROSS-CONNECTIONS .............................................................................. 281

CROSS-CONNECTIONS: MANAGEMENT (DXC 4/1)....................................................................281
Concatenated Traffic Type .............................................................................................................282
Cross-Connection: configuring (DXC 4/1) ......................................................................................284
Cross-Connection: displaying information (DXC 4/1).....................................................................285
Cross-Connection: removing (DXC 4/1).........................................................................................285
Broadcast Cross-Connection: adding a leg (DXC 4/1) ..................................................................286
Broadcast Cross-Connection: removing a leg (DXC 4/1) ..............................................................287
Monitor Cross-Connection: adding (DXC 4/1)................................................................................287
Monitor Cross-Connection: displaying information (DXC 4/1) .......................................................288
Monitor Cross-Connection: removing (DXC 4/1)............................................................................289
Cross-Connection: managing the administrative state (DXC 4/1) .................................................289
Cross Connections: restoration (DXC 4/1) .....................................................................................290
Cross-Connection: forced deletion (DXC 4/1) ................................................................................292
Cross-Connection: displaying the port/matrix fail alarms (DXC 4/1)..............................................292
CROSS-CONNECTION: MANAGING LIST FILTERS (DXC 4/1)....................................................293
Cross-Connection: displaying list (DXC 4/1) ..................................................................................293
SNC PROTECTION: MANAGING (DXC 4/1) ...................................................................................293
SNC Protection: configuring (DXC 4/1) ..........................................................................................294
SNC Protection: displaying information (DXC 4/1).........................................................................295
SNC Protection: modifying (DXC 4/1) ............................................................................................296
SNC Protection: removing (DXC 4/1).............................................................................................296
SNC Protection: switching (DXC 4/1) .............................................................................................296
SNC Protection: setting the WTR period (DXC 4/1).......................................................................298
SNC Protection: swapping role (DXC 4/1) .....................................................................................298
SPLIT CROSS-CONNECTION: MANAGING (DXC 4/1) .................................................................300
Split Cross-Connection: configuring accesses (DXC 4/1)..............................................................300
Split Cross-Connection: displaying a list of accesses (DXC 4/1)...................................................302
Split Cross-Connection: removing an access (DXC 4/1) ...............................................................302
UNIDIRECTIONAL DROPPED CONNECTIONS: MANAGING (DXC 4/1) .....................................302
Unidirectional Dropped Connection: configuring (DXC 4/1)...........................................................302
Unidirectional Dropped Connection: selecting the drop leg channel (DXC 4/1)............................303
Unidirectional Dropped Connection: displaying information (DXC 4/1) .........................................304
Unidirectional Dropped Connection: removing (DXC 4/1) .............................................................304
Unidirectional Dropped Connection: switching (DXC 4/1) .............................................................304
TANDEM CONNECTION: MANAGING............................................................................................305
Tandem Connection: creating.........................................................................................................305
Tandem Connection: configuring....................................................................................................306
Tandem Connection: displaying .....................................................................................................308
AUXILIARY UNIT CONNECTION: MANAGING...............................................................................309
Auxiliary Unit Connection: configuring............................................................................................311
Auxiliary Unit Connection: removing...............................................................................................313
Auxiliary Unit Connection: displaying..............................................................................................313

.
Issue:1
GENERAL INDEX
MANAGING ALARMS ........................................................................................................ 314

ALARMS: MANAGING ATTRIBUTES (DXC 4/1).............................................................................314
Alarms: configuring attributes (DXC 4/1) ........................................................................................315
Alarms: displaying attributes (DXC 4/1)..........................................................................................315
ALARMS: MANAGING MONITORING STATE ................................................................................316
Alarms: configuring the monitoring state ........................................................................................317
Alarms: displaying monitoring state................................................................................................318
ALARM: FILTERING..........................................................................................................................318
ALARMS: CONFIGURING SOH BYTE PERSISTENCY .................................................................319
ALARMS: CONFIGURING REPORTING STATE ............................................................................320
ALARMS: FILTERING OF THE FREE PDH PORTS FAULT ..........................................................320
ALARMS: SERIAL LINK OFF INHIBITION.......................................................................................321
ALARMS: AIS / RDI MASKING .........................................................................................................321
ALARMS: PORT MODE....................................................................................................................321
ACTIVE ALARMS: FILTERING OF THE LIST .................................................................................323
Active Alarms: displaying ................................................................................................................323
ALARMS: DISPLAYING SUBRACKS/UNITS ACTIVE ALARMS ....................................................324
Alarms: displaying subrack active alarms.......................................................................................325
Active Alarms: acknowledgement push-button ..............................................................................325
Active Alarms: displaying alarmed unit...........................................................................................326
Active Alarms: displaying unit active alarms...................................................................................327
ALARMS: MANAGING THE EVENT HISTORY FILE ......................................................................327
Alarms: removing the selected file..................................................................................................328
Alarms: displaying the alarm history file .........................................................................................328
Alarms: removing all alarm history files ..........................................................................................328
ALARMS: DISPLAYING THE LOG FILE ..........................................................................................328
ALARMS: CONFIGURING THE LOG FULL THRESHOLD.............................................................328
ALARMS: CLEARING THE ALARM LOG ........................................................................................328
ALARMS: FAULT ACKNOWLEDGE ................................................................................................329
ALARMS: ENABLING/DISABLING PARKING MODE .....................................................................329
ALARMS: DISPLAYING SIGNAL DB LOG FILE..............................................................................329
ALARMS: RESETTING SIGNAL DB LOG FILE...............................................................................329
ALARMS: UPDATING ALARM COUNTERS....................................................................................329
PERFORMANCE MONITORING........................................................................................ 330

STM-1 AND PDH PORT PERFORMANCE PARAMETERS: CONFIGURING THRESHOLDS (DXC
4/1) .....................................................................................................................................................330
PERFORMANCE PARAMETER: MANAGING EXCEPTIONS THRESHOLDS .............................333
Performance Parameter: configuring exception thresholds...........................................................334
Performance Parameter: restoring default exception thresholds...................................................335
Performance Parameter: displaying the exception thresholds ......................................................335
PERFORMANCE: DATABASE USAGE...........................................................................................335
PERFORMANCE: LO LIMIT CONFIGURATION .............................................................................336
PERFORMANCE: LO CURRENT LOAD..........................................................................................336

.
Issue:1
GENERAL INDEX
PERFORMANCE: MANAGING DATA DISPLAYING ......................................................................337

Performance: displaying data .........................................................................................................338
PERFORMANCE: RESETTING ALL NE REGISTERS ...................................................................339
PERFORMANCE: RESETTING REGISTERS OF A SELECTED PORT........................................339
Performance: resetting register ......................................................................................................340
PERFORMANCE: MANAGING DATA COLLECTION.....................................................................340
Performance: start maintenance based collection .........................................................................341
Performance: stop maintenance based collection .........................................................................342
Performance: start service based collection...................................................................................343
Performance: stop service based collection...................................................................................344
Performance: modifying data collection parameter........................................................................344
Performance: displaying collection state ........................................................................................344
Performance: displaying started monitored entities .......................................................................345
SECURITY AND SYSTEM MANAGEMENT ..................................................................... 346

SECURITY: MODIFYING PASSWORD ...........................................................................................346
SECURITY: MODIFYING USER PASSWORD................................................................................346
SYSTEM: SETTING NE DATE AND TIME.......................................................................................346
SYSTEM: CONFIGURING TIMEOUT ..............................................................................................346
System: configuring session inactivity ............................................................................................347
System: configuring EM response time..........................................................................................347
System: configuring session database open time out....................................................................347
SYSTEM: LINE UP: MANAGING......................................................................................................347
Line Up: configuring ports (DXC 4/1)..............................................................................................348
Line Up: provisioning cross-connections (DXC 4/1).......................................................................348
Line Up: decommissioning the ports ..............................................................................................350
Line Up: removing cross-connections ............................................................................................350
SYSTEM: CHECKING THE SOFTWARE RELEASE ......................................................................351
System: checking subrack software release ..................................................................................351
System: checking equipment software details ...............................................................................352
SYSTEM: PERFORMING DATABASE BACKUP ............................................................................352
SYSTEM: DOWNLOADING SW AND DB ON C&T SUBRACK......................................................353
SYSTEM: DOWNLOADING SW ON COMMU.................................................................................354
SYSTEM: DOWNLOADING SW ON MCU.......................................................................................354
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE 2 SUBRACK ........................................355
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE 3/6/7 SUBRACK ..................................356
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE E SUBRACK........................................357
SYSTEM: DOWNLOADING SW ON STM-4 UNIT...........................................................................358
SYSTEM: DOWNLOADING SW ON STM-16 UNIT.........................................................................359
SYSTEM: DOWNLOADING SW ON 2XSTM-1 UNIT ......................................................................359
SYSTEM: DOWNLOADING SW ON 4XSTM-1 UNIT ......................................................................360
SYSTEM: DOWNLOADING SW ON 4X140-155MBIT/S UNIT .......................................................361

.
Issue:1
GENERAL INDEX
SYSTEM: DOWNLOADING SW ON AUXILIARY UNIT ..................................................................361

SYSTEM: DOWNLOADING SW ON 63X2MBIT/S UNIT.................................................................362
SYSTEM: DOWNLOADING SW ON 4X34MBIT/S T-MUX UNIT ....................................................363
SYSTEM: DOWNLOADING SW ON BOOSTER UNIT ...................................................................365
SYSTEM: DOWNLOADING SW ON PREAMPLIFIER UNIT ..........................................................365
SYSTEM: DOWNLOADING SW ON TYPE 3/6/7 MIU.....................................................................366
SYSTEM: DOWNLOADING SW ON TYPE E MIU ..........................................................................367
SYSTEM: SWITCHING THE FLASH MEMORY BANKS ................................................................368
System: switching banks on C&T subrack .....................................................................................368
System: switching banks on CommU.............................................................................................369
System: switching banks on MCU..................................................................................................369
System: switching banks on PCU of type 2 subrack......................................................................369
System: switching banks on PCU of type 3/6/7 subrack................................................................370
System: switching banks on PCU of type E subrack .....................................................................371
System: switching banks on STM-4 Unit........................................................................................371
System: switching banks on STM-16 Unit......................................................................................371
System: switching banks on 2xSTM-1 Unit....................................................................................372
System: switching banks on 4xSTM-1 Unit....................................................................................372
System: switching banks on 4x140-155Mbit/s Unit........................................................................373
System: switching banks on Auxiliary Unit .....................................................................................373
System: switching banks on 63x2Mbit/s Unit .................................................................................373
System: switching banks on 4x34Mbit/s T-Mux Unit......................................................................374
System: switching banks on Booster Unit ......................................................................................375
System: switching banks on Pramplifier Unit .................................................................................375
System: switching banks on Type 3/6/7 MIU .................................................................................376
System: switching banks on Type E MIU.......................................................................................376
SYSTEM: DISPLAYING COMMAND LOG DATABASE..................................................................376
SYSTEM: RESETTING COMMAND LOG DATABASE...................................................................376
SYSTEM: DECOMMISSIONING NE DATABASE ...........................................................................377
SYSTEM: PARTIAL DECOMMISSIONING OF NE DATABASE.....................................................377
SYSTEM: RESTARTING CCU .........................................................................................................378
SYSTEM: UPGRADING TEST FROM DXC 4/1 512X512 TO DXC 4/4..........................................378
REAL-TIME MONITOR WINDOW...................................................................................... 379

ALARM AREA....................................................................................................................................379
EVENT AREA ....................................................................................................................................379
FAULT DETECTION PROCEDURE .................................................................................. 385

.
Issue:1
GENERAL INDEX
SPI - SYNCHRONOUS PHYSICAL INTERFACE ALARMS............................................................385

TxClockFail (SPI) ....................................................................................................................385
RxClockFail (SPI) ....................................................................................................................385
FreqOutOfRange (SPI)...............................................................................................................386
TxLaserPwrHigh (SPI) ...............................................................................................................386
TxLaserPwrLow (SPI)................................................................................................................386
DescramblerFail (SPI) ...............................................................................................................387
ScramblerFail (SPI) ................................................................................................................387
LOS_LOF (SPI) .......................................................................................................................387
LOS (SPI)...............................................................................................................................387
LaserFail (SPI) .......................................................................................................................388
LaserDegrade (SPI) ................................................................................................................388
TxPulseLoss (SPI) ....................................................................................................................388
RS - REGENERATOR SECTION ALARMS.....................................................................................389
LOF (RS) ...............................................................................................................................389
DCCrLAPDDisconnected (RS)....................................................................................................389
RS-TIM (RS) ............................................................................................................................389
MS - MULTIPLEX SECTION ALARMS.............................................................................................390
MS-AIS (MS) [LC] .....................................................................................................................390
MS-RDI (MS) [LC] .....................................................................................................................390
MS-EXC (MS)........................................................................................................................390
MS-DEG (MS)........................................................................................................................391
SSMMismatch (MS) ................................................................................................................391
DCCmLAPDDisconnected (MS) .................................................................................................391
AU-4 / AU-3 - ADMINISTRATIVE UNIT ALARMS............................................................................392
AU-LOP (AU-4 / AU-3) .........................................................................................................392
AU-AIS (AU-4 / AU-3) [LC] ........................................................................................................392
TxAURejustFail (AU-4 / AU-3) ..................................................................................................392
RxAURejustFail (AU-4 / AU-3) ..................................................................................................393
AU-Mtx-LOP (AU-4 / AU-3) ......................................................................................................393
AU-Mtx-AIS (AU-4 / AU-3) ......................................................................................................393
VC-4 - HIGH ORDER VC ALARM ....................................................................................................394
HP-TIM (VC-4) .........................................................................................................................394
HP-PLM (VC-4).....................................................................................................................394
HP-LOM (VC-4).....................................................................................................................394
HP-RDI (VC-4) [LC] ..................................................................................................................395
HP-AIS (VC-4) [LC] ..................................................................................................................395
HP-DEG (VC-4).....................................................................................................................396
HP-EXC (VC-4).....................................................................................................................396
HP-UNEQ (VC-4).....................................................................................................................396
RDIPayload (VC-4) [LC] ...........................................................................................................397
RDIServer (VC-4) [LC] ..............................................................................................................397
RDIConnectivity (VC-4) [LC].......................................................................................................397
TC-ISF (VC-4) .........................................................................................................................398

.
Issue:1
GENERAL INDEX
TC-UNEQ (VC-4).....................................................................................................................398
TC-DEG (VC-4).....................................................................................................................398
TC-EXC (VC-4).....................................................................................................................399
RDI-OR (VC-4) .........................................................................................................................399
HO-V4-FAIL_A (VC-4)..............................................................................................................399
HO-V4-FAIL_B (VC-4)..............................................................................................................400
HO-LOM VCnV (VC-4)..............................................................................................................400
HO-SQM VCnV (VC-4)..............................................................................................................400
HO-LOA VCnV (VC-4)..............................................................................................................401
HO-LOA RecVCnV (VC-4) ........................................................................................................401
HO-INCJ1-Mism VCnV (VC-4) ...................................................................................................401
HO-UneqMtx (VC-4)..................................................................................................................402
TU3 / TU2 / TU12 - TRIBUTARY UNIT ALARMS.............................................................................402
LPOM-LOP (TU3 / TU2 / TU12) .............................................................................................402
LPOM-AIS (TU3 / TU2 / TU12) [LC] ...........................................................................................403
LPOM-DEG (TU3 / TU2 / TU12) [LC]........................................................................................403
LPOM-EXC (TU3 / TU2 / TU12) [LC]........................................................................................403
LPOM-UNEQ (TU3 / TU2 / TU12) [LC] ...................................................................................404
LPOM-RDI (TU3 / TU2 / TU12) [LC].......................................................................................404
LPOM-TIM (TU3 / TU2 / TU12) [LC].......................................................................................404
LPOM-PLM (TU3 / TU2 / TU12) [LC]........................................................................................405
V4-FAIL_A (TU3 / TU2 / TU12) ............................................................................................405
V4-FAIL_B (TU3 / TU2 / TU12) ............................................................................................405
TC-ISF (TU3 / TU2 / TU12) ....................................................................................................405
TC-UNEQ (TU3 / TU2 / TU12) ................................................................................................406
TC-DEG (TU3 / TU2 / TU12) ................................................................................................406
TC-EXC (TU3 TU2 TU12) ..................................................................................................407
VC-3 - LOW ORDER VC ALARMS...................................................................................................407
LP-TIM (VC-3) .........................................................................................................................407
LP-PLM (VC-3) .........................................................................................................................407
LP-LOM (VC-3).....................................................................................................................408
LP-RDI (VC-3) [LC] ..................................................................................................................408
LP-AIS (VC-3) [LC] ..................................................................................................................409
LP-DEG (VC-3).....................................................................................................................409
LP-EXC (VC-3) .........................................................................................................................409
LP-UNEQ (VC-3).....................................................................................................................410
RDIPayload (VC-3) [LC] ...........................................................................................................410
RDIServer (VC-3) [LC] ..............................................................................................................410
RDIConnectivity (VC-3) [LC].......................................................................................................411
VC-12 - LOW ORDER VC ALARMS.................................................................................................411
LP-LOP (VC-12) .......................................................................................................................411
LP-AIS (VC-12) [LC] ................................................................................................................411
LP-RDI (VC-12) [LC] ................................................................................................................412
LP-EXC (VC-12) .......................................................................................................................412

.
Issue:1
GENERAL INDEX
LP-DEG (VC-12)...................................................................................................................413
LP-PLM (VC-12) .......................................................................................................................413
LP-TIM (VC-12) .......................................................................................................................413
LP-UNEQ (VC-12)...................................................................................................................414
V4-FAIL_A (VC-12)...............................................................................................................414
V4-FAIL_B (VC-12)...............................................................................................................414
TU-TC-PATH-AIS (VC-12) .........................................................................................................414
TU-TC-PATH-UNEQ (VC-12)......................................................................................................415
TU-TC-PATH-RDI (VC-12).........................................................................................................415
TU-VC-PATH-RDI (VC-12).........................................................................................................415
TU-RFI (VC-12) .......................................................................................................................416
TU-NO-RxTraceId (VC-12).........................................................................................................416
TU-NO-RxSigLab (VC-12)..........................................................................................................416
2MB - 1.5 AND 2MBIT/S PDH INTERFACE ALARMS ....................................................................417
TxBufferContention (2Mb) ..........................................................................................................417
RxBufferContention (2Mb)..........................................................................................................417
PDH-LOS (2Mb) ......................................................................................................................418
PDH-AIS (2Mb) [LC] ...............................................................................................................418
PDH-EXC (2Mb) ......................................................................................................................418
PDH-DEG (2Mb) ......................................................................................................................419
PDH-LOF (2Mb) ......................................................................................................................419
CRC4Mismatch (2Mb)...............................................................................................................419
CRC4RAI (2Mb) [LC] ...............................................................................................................420
PDH-RAI (2Mb) [LC] ...............................................................................................................420
34MB - 34 AND 45MBIT/S PDH INTERFACE ALARMS .................................................................420
TxBufferContention (34Mb) ........................................................................................................420
RxBufferContention (34Mb)........................................................................................................421
PDH-LOS (34Mb) ....................................................................................................................421
PDH-AIS (34Mb) [LC] .............................................................................................................422
PDH-EXC (34Mb) ....................................................................................................................422
PDH-DEG (34Mb) ....................................................................................................................422
PDH-LOF (34Mb) ....................................................................................................................423
PDH-TxFail (34Mb).................................................................................................................423
PDH-INParityError (34Mb)..........................................................................................................423
PDH-INClockFail (34Mb) ...........................................................................................................424
45MbYellowSignal (34Mb)..........................................................................................................424
45MbIdleSignal (34Mb).............................................................................................................424
140MB - 140MBIT/S PDH INTERFACE ALARMS ...........................................................................425
TxBufferContention (140Mb) ......................................................................................................425
RxBufferContention (140Mb)......................................................................................................425
PDH-LOS (140Mb) ..................................................................................................................425
PDH-AIS (140Mb) [LC] .........................................................................................................426
PDH-EXC (140Mb) ..................................................................................................................426
PDH-DEG (140Mb) ..................................................................................................................426

.
Issue:1
GENERAL INDEX
PDH-LOF (140Mb) ..................................................................................................................427

PDH-TxFail (140Mb)...............................................................................................................427
PDH-INParityError (140Mb)........................................................................................................427
PDH-INClockFail (140Mb) .........................................................................................................427
PDH-RAI (140Mb) [LC] ...........................................................................................................428
RDI (140Mb) .........................................................................................................................428
8MBCH - ALARMS OF 8MBIT/S CHANNELS OF A T-MUX UNIT ................................................429
AIS (8MbCh) [LC] ..................................................................................................................429
LOF (8MbCh).........................................................................................................................429
EXC (8MbCh).........................................................................................................................429
DEG (8MbCh).........................................................................................................................429
RAI (8MbCh) [LC] ..................................................................................................................430
34MBCH - ALARMS OF 34MBIT/S CHANNELS OF A T-MUX UNIT ............................................430
AIS (34MbCh).......................................................................................................................430
LOF (34MbCh).......................................................................................................................430
EXC (34MbCh).......................................................................................................................431
DEG (34MbCh).......................................................................................................................431
RAI (34MbCh).......................................................................................................................431
VIDEOCOD - 34MBIT/S VIDEOCODEC INTERFACE ALARMS ....................................................432
TxBufferContention (VideoCod) .................................................................................................432
RxBufferContention (VideoCod).................................................................................................432
PDH-LOS (VideoCod) .............................................................................................................433
PDH-AIS (VideoCod) .............................................................................................................433
PDH-EXC (VideoCod) .............................................................................................................433
PDH-DEG (VideoCod) .............................................................................................................434
PDH-LOF (VideoCod) .............................................................................................................434
PDH-LOMF (VideoCod)..........................................................................................................434
VC2-5C - CONCATENATED VIRTUAL CONTAINER ALARMS.....................................................435
LP-LOP (VC2-5c) .....................................................................................................................435
LP-AIS (VC2-5c) [LC] ..............................................................................................................435
LP-EXC (VC2-5c) .....................................................................................................................436
LP-DEG (VC2-5c) .................................................................................................................436
LP-PLM (VC2-5c) .....................................................................................................................436
LP-UNEQ (VC2-5c) .................................................................................................................437
2MBPDHCH - ALARMS OF 2MBIT/S CHANNELS OF A T-MUX UNIT..........................................437
AIS (2MbPDHCh) [LC] ...........................................................................................................437
LOF (2MbPDHCh).................................................................................................................437
EXC (2MbPDHCh).................................................................................................................437
DEG (2MbPDHCh).................................................................................................................437
RAI (2MbPDHCh) [LC] ...........................................................................................................437
RxFailure (2MbPDHCh) .........................................................................................................438
ST
MX1STU - 1 STAGE MATRIX UNIT ALARMS..............................................................................438
MissingUnit (Mx1StU) .............................................................................................................438
UnitAddressError (Mx1StU)........................................................................................................439

.
Issue:1
GENERAL INDEX
RxSyncLoss (Mx1StU) .............................................................................................................439

RxClockLoss (Mx1StU) .............................................................................................................439
STM-1_nParityError (Mx1StU) ...................................................................................................439
TmngPulseLossn:n+1 (Mx1StU) ................................................................................................440
SyncPulseLossn:n+1 (Mx1StU) .................................................................................................440
MX2STU - 2ND STAGE MATRIX UNIT ALARMS..............................................................................440
STM-1_nParityError (Mx2StU) ...................................................................................................441
MX3STU - 3RD STAGE MATRIX UNIT ALARMS..............................................................................442
STM-1_nParityError (Mx3StU) ..................................................................................................443
TxSyncLoss1stHalf (Mx3StU) ....................................................................................................443
TxSyncLoss2ndtHalf (Mx3StU) ..................................................................................................443
MXIN - MATRIX INPUT SIDE ALARMS (FROM SIDE) ...................................................................444
UNEQAccess (MxIn) ..............................................................................................................444
MIUAddrError (MxIn) ..............................................................................................................444
UnitFail (MxIn) .........................................................................................................................444
MXOUT - MATRIX OUTPUT SIDE ALARMS (TO SIDE).................................................................445
UNEQAccess (MxOut) ...........................................................................................................445
UnitFail (MxOut).......................................................................................................................445
MCU - MATRIX CONTROL UNIT ALARMS.....................................................................................445
MxNotCnfg (MCU)..................................................................................................................445
AND(MxPSU)Fail (MCU) ............................................................................................................446
AND(MxBatt)Fail (MCU) ............................................................................................................446
Line_AFail (MCU).....................................................................................................................446
Line_BFail (MCU).....................................................................................................................446
Mx_AMx_BFail (MCU) .............................................................................................................447
MTX_CntrFail (MCU) .............................................................................................................447
MxBatt1..4Fail (MCU) .............................................................................................................447
UnitProtVerMism (MCU).............................................................................................................447
AND(MxBatt1-2)Fail (MCU)........................................................................................................447
AND(MxBatt3-4)Fail (MCU)........................................................................................................448
MTX_HwCntrFail (MCU).............................................................................................................448
SubrackAlarmAck (MCU) ...........................................................................................................448
MTU - MATRIX TIMING UNIT ALARMS...........................................................................................448
MissingUnit (MTU) ..................................................................................................................448
TSU_Aloss (MTU) ..................................................................................................................449
TSU_Bloss (MTU) ..................................................................................................................449

.
Issue:1
GENERAL INDEX
ClockOutLoss (MTU)..............................................................................................................449
SyncOutLoss (MTU) ..................................................................................................................449
UnitPowerFail (MTU)..............................................................................................................450
MPSU - MATRIX POWER SUPPLY ALARMS.................................................................................450
MissingUnit (MPSU) ...............................................................................................................450
UnitFail (MPSU).......................................................................................................................450
BattFail (MPSU).......................................................................................................................451
MX13STU_86 - 1ST/3RD STAGE MATRIX UNIT ALARMS ...............................................................451
MissingUnit (Mx13StU_86).....................................................................................................451
UnitAddressError (Mx13StU_86)................................................................................................451
RxSyncLoss (Mx13StU_86).....................................................................................................452
RxClockLoss (Mx13StU_86).....................................................................................................452
UnitDistrClockLoss (Mx13StU_86).............................................................................................452
UnitPowerFail (Mx13StU_86).................................................................................................452
I/OmoduleMissingUnit (Mx13StU_86)........................................................................................452
I/OModulePowerFail (Mx13StU_86) ...........................................................................................453
STM-1_I_nParityError (Mx13StU_86) .........................................................................................453
STM-1_III_nParityError (Mx13StU_86) .......................................................................................453
TmngPulseLossn:n+1 (Mx13StU_86) .........................................................................................453
SyncPulseLossn:n+1 (Mx13StU_86) ..........................................................................................454
SignalLossn:n+1 (Mx13StU_86) ................................................................................................454
TxSyncLoss1stHalf (Mx13StU_86) .............................................................................................454
TxSyncLoss2ndtHalf (Mx13StU_86) ...........................................................................................454
TxClockFail1stHalf (Mx13StU_86) ..............................................................................................455
TxClockFail2ndHalf (Mx13StU_86) .............................................................................................455
MX2STU_86 - 2ND STAGE MATRIX UNIT ALARMS .......................................................................455
MissingUnit (Mx2StU_86)........................................................................................................455
UnitAddressError (Mx2StU_86)...................................................................................................456
RxSyncLoss (Mx2StU_86)........................................................................................................456
RxClockLoss (Mx2StU_86)........................................................................................................456
UnitDistrClockLoss (Mx2StU_86)................................................................................................456
UnitPowerFail (Mx2StU_86)....................................................................................................457
STM-1_nParityError (Mx2StU_86) ..............................................................................................457
MX1STU_91 - 1ST STAGE MATRIX UNIT ALARMS........................................................................457
MissingUnit (Mx1StU-91).........................................................................................................457
TmngPulseLossn:n+1 (Mx1StU_91) ...........................................................................................459
SyncPulseLossn:n+1 (Mx1StU_91) ............................................................................................459
MX2STU_91 - 2ND STAGE MATRIX UNIT ALARMS .......................................................................459

.
Issue:1
GENERAL INDEX
MX3STU_91 - 3RD STAGE MATRIX UNIT ALARMS .......................................................................461
STM-1_1:16TxSyncLoss (Mx3StU_91) ......................................................................................462
STM-1_17:32TxSyncLoss (Mx3StU_91) ....................................................................................462
MXIN_91 - MATRIX INPUT SIDE ALARMS (FROM SIDE) .............................................................463
UNEQAccess (MxIn_91).........................................................................................................463
MIUAddrError (MxIn_91).........................................................................................................463
UnitFail (MxIn_91) ...................................................................................................................463
MXOUT - MATRIX OUTPUT SIDE ALARMS (TO SIDE).................................................................464
UNEQAccess (MxOut_91)......................................................................................................464
MIUAddrError (MxOut_91)......................................................................................................464
UnitFail (MxOut_91) ................................................................................................................464
MCU - MATRIX CONTROL UNIT ALARMS.....................................................................................465
MissingUnit (MCU_91) ............................................................................................................465
UnitFail (MCU_91)...................................................................................................................465
MxNotCnfg (MCU_91) ............................................................................................................465
AND(MxPSU)Fail (MCU_91)......................................................................................................466
AND(MxBatt)Fail (MCU_91) .......................................................................................................466
Line_AFail (MCU_91)................................................................................................................466
Line_BFail (MCU_91)................................................................................................................466
Mx_A_Mx_BFail (MCU_91)........................................................................................................466
Line_A_Line_BFail (MCU_91).....................................................................................................467
MasterSlaveFail (MCU_91) ........................................................................................................467
MasterSlaveLinkOff (MCU_91) ...................................................................................................467
MTU_91 - MATRIX TIMING UNIT ALARMS ....................................................................................467
MissingUnit (MTU_91).............................................................................................................467
TSU_Aloss (MTU_91)............................................................................................................468
TSU_Bloss (MTU_91)............................................................................................................468
ClockOutLoss (MTU_91).........................................................................................................468
SyncOutLoss (MTU_91).............................................................................................................468
MPSU_91 - MATRIX POWER SUPPLY ALARMS...........................................................................469
MissingUnit (MPSU_91) ..........................................................................................................469
UnitFail (MPSU_91).................................................................................................................469
BattFail (MPSU_91).................................................................................................................469
PORTUNIT - PORT UNIT ALARMS .................................................................................................470
MissingUnit (PortUnit)..............................................................................................................470
UnitTypeMismatch (PortUnit) ......................................................................................................470

.
Issue:1
GENERAL INDEX
UnitFail (PortUnit) ....................................................................................................................470

CntrlBusFail (PortUnit)..............................................................................................................470
MxASignalFail (PortUnit).........................................................................................................471
MxBSignalFail (PortUnit).........................................................................................................471
Mx_AClockFail (PortUnit)..........................................................................................................471
Mx_BClockFail (PortUnit)..........................................................................................................471
TxOHBusDispFail (PortUnit)........................................................................................................471
SelfTestFail (PortUnit)..............................................................................................................472
UnexpUnit (PortUnit) .................................................................................................................472
UnitHWMismatch (PortUnit) .......................................................................................................472
PwrFail (PortUnit) ....................................................................................................................472
SyncSrcFail (PortUnit)..............................................................................................................473
AsicFail (PortUnit) ....................................................................................................................473
5VNegFail (PortUnit) .................................................................................................................473
RxRegClockFail (PortUnit)..........................................................................................................473
PowerProblem (PortUnit)..........................................................................................................474
UnitError (PortUnit) .................................................................................................................474
LTU-Fail (PortUnit) ................................................................................................................474
LTU-Mismatch (PortUnit)........................................................................................................474
CK-OOF (PortUnit) ................................................................................................................475
TmpOutOfRange (PortUnit)......................................................................................................475
BiasOutOfLimits (PortUnit) .......................................................................................................475
PumpLaserFail (PortUnit)........................................................................................................475
AlsApsdActive (PortUnit)........................................................................................................476
EmissionPwrOut (PortUnit).......................................................................................................476
PCU - PORT CONTROL UNIT ALARMS .........................................................................................476
MissingUnit (PCU) ...................................................................................................................476
UnitFail (PCU)..........................................................................................................................477
UnitProtVerMism (PCU)..............................................................................................................477
OR(Batt)Fail (PCU) ...................................................................................................................477
PCU_A_PCU_BFail (PCU)..........................................................................................................477
CtrlBusFault (PCU) ...................................................................................................................477
FailFan (PCU)..........................................................................................................................478
ANDFailFanContr (PCU) ..........................................................................................................478
ORFailFanContr (PCU) ............................................................................................................478
OverT (PCU)..........................................................................................................................478
MissingFan (PCU) .................................................................................................................479
S3Mismatch (PCU) .................................................................................................................479
NoAdjacency (PCU) .................................................................................................................479
PPSU - PORT SUBRACK POWER SUPPLY ALARMS ..................................................................480
MissingUnit (PPSU) .................................................................................................................480
PSUFail (PPSU) .......................................................................................................................480
IDU - IDENTIFICATION UNIT ALARMS...........................................................................................481
MissingUnit (IdU) .....................................................................................................................481

.
Issue:1
GENERAL INDEX
SubrackIdMismatch (IdU) ............................................................................................................481

SubrackTypeMismatch (IdU).......................................................................................................481
AUXU - AUXILIARY UNIT ALARMS.................................................................................................482
MissingUnit (AuxU) ..................................................................................................................482
UnitTypeMismatch (AuxU)...........................................................................................................482
UnitFail (AuxU) ........................................................................................................................482
CntrlBusFail (AuxU) ..................................................................................................................483
SelfTestFail (AuxU) ..................................................................................................................483
UnexpUnit (AuxU) .....................................................................................................................483
MIU - TRIB./MATRIX INTERFACE UNIT ALARMS .........................................................................484
MissingUnit (MIU) ....................................................................................................................484
WrongUnit (MIU)........................................................................................................................484
UnitFail (MIU)...........................................................................................................................484
CntrlBUSFail (MIU) ....................................................................................................................485
Clock_AFail (MIU) ....................................................................................................................485
Clock_BFail (MIU) ....................................................................................................................485
SyncFail (MIU).......................................................................................................................485
PLLOutSyncFail (MIU)................................................................................................................486
SyncPortClockFail (MIU) .............................................................................................................486
ASIC_1Fail (MIU) ...................................................................................................................486
ASIC_2Fail (MIU) ...................................................................................................................487
NegPwrFail (MIU) ....................................................................................................................487
MIUSelfTestFail (MIU) ................................................................................................................487
Clock_A_Clock_BFail (MIU) ........................................................................................................488
HWMismatch (MIU) ....................................................................................................................488
PLL388MhzUnlock (MIU) ............................................................................................................488
388MHz_I/O_ModA..EFail (MIU).................................................................................................488
MIUMX - MATRIX INTERFACE / MATRIX ACCESS ALARMS.......................................................489
FrameSyncFail (MIUMx) ...........................................................................................................489
MxClockFail (MIUMx) ...............................................................................................................489
ParityError (MIUMx)...................................................................................................................489
DestinationAddrError (MIUMx) ....................................................................................................489
AccLOS (MIUMx)......................................................................................................................489
MIUPORT - MATRIX INTERFACE / STM-1 PORT ACCESS ALARMS .........................................490
DispFail (MIUPort) ....................................................................................................................490
MIU_MSP - MATRIX INTERFACE MSP ALARMS ..........................................................................490
MSP_INV (MIU_MSP) .............................................................................................................490
MSP_PAM (MIU_MSP) .........................................................................................................491
MSPModeMismatch (MIU_MSP) ................................................................................................491
MIU_T3/6/7 - TRIB./MATRIX INTERFACE UNIT ALARMS.............................................................491
MissingUnit (MIU_T3/6/7)........................................................................................................491
WrongUnit (MIU_T3/6/7) ...........................................................................................................492
UnitFail (MIU_T3/6/7) ..............................................................................................................492
CntrlBUSFail (MIU_T3/6/7)........................................................................................................492

.
Issue:1
GENERAL INDEX
Clock_AFail (MIU_T3/6/7)........................................................................................................492
Clock_BFail (MIU_T3/6/7)........................................................................................................493
SyncPortClockFail (MIU_T3/6/7).................................................................................................493
NoMonitClock (MIU_T3/6/7)....................................................................................................493
PLLOutSyncFail (MIU_T3/6/7) ...................................................................................................494
SyncFail (MIU_T3/6/7) ..........................................................................................................494
ClockOutOfFrequency (MIU_T3/6/7) ..........................................................................................494
MasterSlaveLinkFail (MIU_T3/6/7)..............................................................................................494
ASIC_1Fail (MIU_T3/6/7).......................................................................................................495
ASIC_2Fail (MIU_T3/6/7).......................................................................................................495
BackPanelUnknown (MIU_T3/6/7)..............................................................................................495
MIUSelfTestFail (MIU_T3/6/7)....................................................................................................495
Clock_A_Clock_BFail (MIU_T3/6/7)............................................................................................496
HW_Mismatch (MIU_T3/6/7)....................................................................................................496
388MHz_I/O_ModA..EMiss (MIU_T3/6/7) .................................................................................496
388MHz_I/O_ModA..EPowerFail (MIU_T3/6/7)..........................................................................496
ImSwDownloading (MIU_T3/6/7) ................................................................................................496
ImSwDownloadingFail (MIU_T3/6/7) ..........................................................................................497
MIU_6E - TRIB./MATRIX INTERFACE UNIT ALARMS...................................................................497
MissingUnit (MIU 6E_7E) ........................................................................................................497
WrongUnit (MIU 6E_7E) ...........................................................................................................497
UnitFail (MIU 6E_7E)...............................................................................................................498
CntrlBUSFail (MIU 6E_7E) ........................................................................................................498
Clock_AFail (MIU 6E_7E) ........................................................................................................498
Clock_BFail (MIU 6E_7E) ........................................................................................................498
SyncPortClockFail (MIU 6E_7E) .................................................................................................499
NoMonitClock (MIU 6E_7E) ....................................................................................................499
PLLOutSyncFail (MIU 6E_7E)....................................................................................................499
SyncFail (MIU 6E_7E) ..........................................................................................................500
ClockOutOfFrequency (MIU 6E_7E)...........................................................................................500
MasterSlaveLinkFail (MIU 6E_7E) ..............................................................................................500
ASIC_1Fail (MIU 6E_7E) .......................................................................................................500
ASIC_2Fail (MIU 6E_7E) .......................................................................................................501
BackPanelUnknown (MIU 6E_7E) ..............................................................................................501
MIUSelfTestFail (MIU 6E_7E) ....................................................................................................501
Clock_A_Clock_Bfail (MIU 6E_7E) ............................................................................................501
HW_Mismatch (MIU 6E_7E) ....................................................................................................502
388MHz_I/O_ModA..EMiss (MIU 6E_7E)..................................................................................502
388MHz_I/O_ModA..EPowerFail (MIU 6E_7E) ..........................................................................502
ImSwDownloading (MIU 6E_7E).................................................................................................502
ImSwDownloadingFail (MIU 6E_7E)...........................................................................................502
CCU - CENTRAL CONTROL UNIT ALARMS ..................................................................................503
MissingUnit (CCU) ...................................................................................................................503
CCULinkOff (CCU) ...................................................................................................................503

.
Issue:1
GENERAL INDEX
Download_Failed (CCU).............................................................................................................503
NMS_LinkOff (CCU) ...................................................................................................................504
MEMU - MEMORY EXPANSION UNIT ALARMS............................................................................504
MissingUnit (MemU) ................................................................................................................504
MemUWriteError (MemU)...........................................................................................................504
ChecksumError (MemU) ............................................................................................................505
SizeRegisterError (MemU) ..........................................................................................................505
SIOU - SERIAL EXPANSION UNIT ALARMS..................................................................................505
MissingUnit (SIOU) ..................................................................................................................505
EthLinkOff (SIOU) .....................................................................................................................506
SIOU_A_SIOU_BFail (SIOU) ......................................................................................................506
SIOLINE - SERIAL I/O LINE ALARMS .............................................................................................506
SerialLinkOff (SIOLine)..............................................................................................................506
COMMU - COMMUNICATION AND Q INTERFACE UNIT ALARMS .............................................506
MissingUnit (CommU) .............................................................................................................506
EthLinkOff (CommU).................................................................................................................507
CommU_A_CommU_BFail (CommU) ........................................................................................507
No Adjacencies (CommU) .........................................................................................................507
TSU - TIMING SELECTOR OSCILLATOR UNIT ALARMS.............................................................508
MissingUnit (TSU)....................................................................................................................508
ExtSrc_1Fail (TSU)....................................................................................................................508
ExtSrc_2Fail (TSU)....................................................................................................................508
SystemOscFail (TSU)................................................................................................................509
ExtOutOscFail (TSU)................................................................................................................509
SystemOscDEG (TSU)...............................................................................................................509
PwrFail (TSU) ..........................................................................................................................510
FuseFail (TSU)......................................................................................................................510
TDULinkFail (TSU)....................................................................................................................510
TSU_A_TSU_BFail (TSU)...........................................................................................................510
UnitFail (TSU) ..........................................................................................................................511
ExtOutSqlchDisabled (TSU) ........................................................................................................511
ExtSrc1OOF (TSU)....................................................................................................................511
ExtSrc2OOF (TSU)....................................................................................................................511
Ext1/2 AIS (TSU).......................................................................................................................511
Ext1/2 LOS (TSU)...................................................................................................................512
TDU - TIMING DISTRIBUTOR UNIT ALARMS................................................................................512
MissingUnit (TDU) ...................................................................................................................512
LocalTSUMissing (TDU)..............................................................................................................512
RemoteTSUMissing (TDU)..........................................................................................................512
OutClockFail (TDU) ...................................................................................................................513
OutSyncFail (TDU) ...................................................................................................................513
CTPSU - CONTROL AND TIMING EQPT. POWER SUPPLY ALARMS........................................513
MissingUnit (CTPSU)...............................................................................................................513
CTPSUFail (CTPSU)..............................................................................................................514

.
Issue:1
GENERAL INDEX
SYNCSRC - TIMING SELECTOR-OSCILLATOR UNIT SYNCH SOURCES ALARMS ................514

SyncSourceFail (SyncSrc) .........................................................................................................514
TSU_OOF (SyncSrc).................................................................................................................514
PARU - PARALLEL INTERFACE UNIT ALARMS ...........................................................................515
MissingUnit (ParU)...................................................................................................................515
AND(PortSubPSU)Fail (ParU).....................................................................................................515
AND(PortSubBatt)Fail (ParU)......................................................................................................515
OR(CT_A_PSU)Fail (ParU).........................................................................................................515
OR(CT_B_PSU)Fail (ParU).........................................................................................................516
AND(CT_B_PSU)Fail (ParU) ......................................................................................................516
OR(CT_A_Batt)Fail (ParU)..........................................................................................................516
SPI_STM4 - STM-4 SYNCHRONOUS PHYSICAL INTERFACE ALARMS....................................516
DescramblerFail (SPI_STM4).....................................................................................................516
ScramblerFail (SPI_STM4) .....................................................................................................516
LaserFail (SPI_STM4) ............................................................................................................517
LaserDegrade (SPI_STM4) .....................................................................................................517
LOS (SPI_STM4)..................................................................................................................517
LaserAtlX50 (SPI_STM4) .........................................................................................................518
LaserTxPowThrHigh (SPI_STM4)............................................................................................518
LaserTxPowThrLow (SPI_STM4) ............................................................................................518
LaserHighTemp (SPI_STM4) ..................................................................................................518
TimingProblems (SPI_STM4)..................................................................................................519
SPI_NXSTM1 - NXSTM-1 SYNCHRONOUS PHYSICAL INTERFACE ALARMS .........................519
DescramblerFail (SPI_NxSTM1) ................................................................................................519
ScramblerFail (SPI_NxSTM1).................................................................................................519
LaserFail (SPI_NxSTM1)........................................................................................................520
LaserDegrade (SPI_NxSTM1).................................................................................................520
LOS (SPI_NxSTM1) .............................................................................................................520
TxFail (SPI_NxSTM1) ..........................................................................................................521
LaserAtlX50 (SPI_NxSTM1).....................................................................................................521
LaserTxPowThrHigh (SPI_NxSTM1) ..........................................................................................521
LaserTxPowThrLow (SPI_NxSTM1)...........................................................................................521
LaserHighTemp (SPI_NxSTM1) ................................................................................................522
LineCardError (SPI_NxSTM1).................................................................................................522
TimingProblem (SPI_NxSTM1).................................................................................................522
MxACKFail (SPI_NxSTM1).....................................................................................................522
MxBCKBFail (SPI_NxSTM1).....................................................................................................523
OHBusFail (SPI_NxSTM1)........................................................................................................523
SPI_STM16 - STM-16 SYNCHRONOUS PHYSICAL INTERFACE ALARMS ...............................523
DescramblerFail (SPI_STM16) ..................................................................................................523
ScramblerFail (SPI_STM16) ...................................................................................................524
LaserFail (SPI_STM16) ..........................................................................................................524
LaserDegrade (SPI_STM16) ...................................................................................................524
LOS (SPI_STM16)................................................................................................................524

.
Issue:1
GENERAL INDEX
TxFail (SPI_STM16).............................................................................................................525
LaserAtlX50 (SPI_STM16) .......................................................................................................525
LaserTxPowThrHigh (SPI_STM16).............................................................................................525
LaserTxPowThrLow (SPI_STM16) .............................................................................................525
LaserHighTemp (SPI_STM16) .................................................................................................526
TimingProblems (SPI_STM16)................................................................................................526
WaveLenghtDrift (SPI_STM16)...................................................................................................526
RS_STM4 - STM-4 REGENERATOR SECTION ALARMS.............................................................527
LOF (RS_STM4)...................................................................................................................527
RS-TIM (RS_STM4) ................................................................................................................527
DCCrLAPDDisconnected (RS_STM4)........................................................................................527
RS_NXSTM1 - NXSTM-1 REGENERATOR SECTION ALARMS ..................................................528
LOF (RS_NxSTM1) ..............................................................................................................528
RS-TIM (RS_NxSTM1)............................................................................................................528
DCCrLAPDDisconnected (RS_NxSTM1) ...................................................................................528
RS-UAT_Eve (RS_NxSTM1) .................................................................................................528
RS_STM16 - STM-16 REGENERATOR SECTION ALARMS.........................................................529
LOF (RS_STM16) ................................................................................................................529
RS-TIM (RS_STM16) ..............................................................................................................529
DCCrLAPDDisconnected (RS_STM16)......................................................................................529
MS_STM4 - STM-4 MULTIPLEX SECTION ALARMS ....................................................................530
MS-AIS (MS_STM4) [LC] ..........................................................................................................530
MS-RDI (MS_STM4) [LC] ..........................................................................................................530
MS-EXC (MS_STM4)............................................................................................................530
MS-DEG (MS_STM4)............................................................................................................531
DCCmLAPDDisconnected (MS_STM4) .....................................................................................531
MS_NXSTM1 - NXSTM-1 MULTIPLEX SECTION ALARMS ..........................................................532
MS-AIS (MS_NxSTM1) [LC]......................................................................................................532
MS-RDI (MS_NxSTM1) [LC]......................................................................................................532
MS-EXC (MS_NxSTM1) .......................................................................................................532
MS-DEG (MS_NxSTM1) .......................................................................................................533
DCCmLAPDDisconnected (MS_NxSTM1).................................................................................533
MS-UAT_Eve (MS_NxSTM1).................................................................................................533
S1-Change (MS_NxSTM1) ....................................................................................................533
MS_STM16 - STM-16 MULTIPLEX SECTION ALARMS ................................................................534
MS-AIS (MS_STM16) [LC] ........................................................................................................534
MS-RDI (MS_STM16) [LC] ........................................................................................................534
MS-EXC (MS_STM16)..........................................................................................................534
MS-DEG (MS_STM16)..........................................................................................................535
DCCmLAPDDisconnected (MS_STM16) ...................................................................................535
NXSTM1_140 - 140MBIT/S PDH INTERFACE ALARMS (4X140-155MBIT/S UNIT) ....................536
LOF (NxSTM1_140) .............................................................................................................536
LOS (NxSTM1_140) .............................................................................................................536
AIS (NxSTM1_140) [LC] ......................................................................................................536

.
Issue:1
GENERAL INDEX
EXC (NxSTM1_140) .............................................................................................................537

DEG (NxSTM1_140) .............................................................................................................537
ATL (NxSTM1_140) .............................................................................................................537
PRBS-ERR (NxSTM1_140) ...................................................................................................538
DS2 - ALARMS OF 6MBIT/S CHANNELS OF A T-MUX UNIT ......................................................538
AIS (DS2) ...........................................................................................................................538
LOF (DS2) ............................................................................................................................538
RAI (DS2) ...........................................................................................................................538
DS3 - 45MBIT/S PDH INTERFACE ALARMS..................................................................................539
LOS (DS3) ............................................................................................................................539
LOF (DS3) ............................................................................................................................539
AIS (DS3) ...........................................................................................................................539
RAI (DS3) ...........................................................................................................................540
INPUT-DEG (DS3)....................................................................................................................540
INPUT-EXC (DS3)....................................................................................................................540
IDLE-SIGNAL (DS3)................................................................................................................541
AIC-MISM (DS3) .......................................................................................................................541
RxClockFail (DS3)....................................................................................................................541
TxClockFail (DS3)....................................................................................................................542
NE-EQP-FAIL-SA (DS3).............................................................................................................542
NE-EQP-FAIL-NSA (DS3)...........................................................................................................542
NE-LOS (DS3) ......................................................................................................................543
NE-LOF (DS3) ..........................................................................................................................543
NE-HBER (DS3) .......................................................................................................................543
NE-AIS (DS3) ..........................................................................................................................543
NE-IDLE (DS3) ......................................................................................................................543
RE-EQP-FAIL-SA (DS3).............................................................................................................543
RE-EQP-FAIL-NSA (DS3)...........................................................................................................544
RE-LOS (DS3) ......................................................................................................................544
RE-LOF (DS3) ..........................................................................................................................544
RE-AIS (DS3) ..........................................................................................................................544
RE-IDLE (DS3) ......................................................................................................................545
63X2MBPDHCH - 1.5 AND 2MBIT/S PDH INTERFACE ALARMS.................................................545
TxBufferContention (63x2MbPDHCh)........................................................................................545
RxFailure (63x2MbPDHCh)....................................................................................................545
PDH-LOS (63x2MbPDHCh)....................................................................................................546
PDH-AIS (63x2MbPDHCh) [LC] .............................................................................................546
PDH-EXC (63x2MbPDHCh)....................................................................................................546
PDH-DEG (63x2MbPDHCh)....................................................................................................547
PDH-LOF (63x2MbPDHCh)....................................................................................................547
InputCRC4Mismatch (63x2MbPDHCh) .....................................................................................547
FAW-EXC (63x2MbPDHCh) [LC] .............................................................................................548
PDH-RAI (63x2MbPDHCh) [LC] .............................................................................................548
TxFail (63x2MbPDHCh) [LC] .................................................................................................548

.
Issue:1
GENERAL INDEX
FAW-DEG (63x2MbPDHCh) [LC] .............................................................................................548

OutgoingPDH-LOF (63x2MbPDHCh) [LC] .................................................................................549
OutgoingCRC4Mismatch (63x2MbPDHCh) [LC] .........................................................................549
OutgoingPDH-AIS (63x2MbPDHCh) [LC]...................................................................................550
OutgoingCRC4EXC (63x2MbPDHCh) [LC] .................................................................................550
OutgoingCRC4DEG (63x2MbPDHCh) [LC] ................................................................................550
4X34MBPDHCH - 34MBIT/S T-MUX PDH INTERFACE ALARMS.................................................551
PDH-LOS (4x34MbPDHCh)....................................................................................................551
PDH-AIS (4x34MbPDHCh) [LC] .............................................................................................551
PDH-EXC (4x34MbPDHCh)....................................................................................................551
PDH-DEG (4x34MbPDHCh)....................................................................................................552
PDH-LOF (4x34MbPDHCh)....................................................................................................552
TxFail (4x34MbPDHCh) [LC] .................................................................................................552
PDH-RAI (4x34MbPDHCh) [LC] .............................................................................................553
PDH-INClockFail (4x34MbPDHCh) [LC] ....................................................................................553
3X34_45MB_VC3 - LOW ORDER VC ALARMS (3X34_45MB_VC3) ............................................553
LOP (3x34_45Mb_VC3) .........................................................................................................553
AIS (3x34_45Mb_VC3) [LC] ..................................................................................................554
FERF (3x34_45Mb_VC3) [LC] ..............................................................................................554
EBER (3x34_45Mb_VC3).....................................................................................................555
DEG (3x34_45Mb_VC3) .........................................................................................................555
PLM (3x34_45Mb_VC3) .........................................................................................................555
TIM (3x34_45Mb_VC3) .........................................................................................................556
UNEQ (3x34_45Mb_VC3).....................................................................................................556
V4-FAIL_A (3x34_45Mb_VC3).............................................................................................556
V4-FAIL_B (3x34_45Mb_VC3).............................................................................................556
34 AND 45MBIT/S PDH INTERFACE ALARMS (3X34_45MBPDHCH) .........................................557
RxBufferContention (3x34_45MbPDHCh) .................................................................................557
PDH-LOS (3x34_45MbPDHCh) .............................................................................................557
PDH-AIS (3x34_45MbPDHCh) [LC].......................................................................................558
PDH-EXC (3x34_45MbPDHCh) .............................................................................................558
PDH-DEG (3x34_45MbPDHCh) .............................................................................................558
PDH-LOF (3x34_45MbPDHCh) .............................................................................................558
PDH-45Mb-LOMF (3x34_45MbPDHCh) ...................................................................................559
PDH-TxFail (3x34_45MbPDHCh) ..........................................................................................559
PDH-INClockFail (3x34_45MbPDHCh) ....................................................................................560
45MbYellowSignal (3x34_45MbPDHCh) ...................................................................................560
45MbIdleSignal (3x34_45MbPDHCh) ......................................................................................560
VIRTUAL CONCATENATED ALARM ..............................................................................................561
HP-TIM (VC4_4V)....................................................................................................................561
LOM (VC4_4V)........................................................................................................................561
HP-RDI (VC4_4V)....................................................................................................................561
AU-AIS (VC4_4V)....................................................................................................................562
HP-DEG (VC4_4V) ...............................................................................................................562

.
Issue:1
GENERAL INDEX
HP-EXC (VC4_4V) ...............................................................................................................562

HP-UNEQ (VC4_4V) ...............................................................................................................563
TC-ISF (VC4_4V)....................................................................................................................563
TC-UNEQ (VC4_4V) ...............................................................................................................563
TC-DEG (VC4_4V) ...............................................................................................................564
TC-EXC (VC4_4V) ...............................................................................................................564
HO-V4-FAIL_A (VC4_4V) .......................................................................................................565
HO-V4-FAIL_B (VC4_4V) .......................................................................................................565
HO-LOM_VCnV (VC4_4V).......................................................................................................565
HO-SQM_VCnV (VC4_4V) ......................................................................................................565
HO-LOA_VCnV (VC4_4V) .......................................................................................................566
HO-LOA_RecVCnV (VC4_4V).................................................................................................566
HO-INC_J1_MismVCnV (VC4_4V)..........................................................................................566
HO-UneqMtx (VC4_4V) ...........................................................................................................567
HP-TIM (VC4_16V)..................................................................................................................567
LOM (VC4_16V)......................................................................................................................567
HP-RDI (VC4_16V)..................................................................................................................568
AU-AIS (VC4_16V)..................................................................................................................568
HP-DEG (VC4_16V) .............................................................................................................569
HP-EXC (VC4_16V) .............................................................................................................569
HP-UNEQ (VC4_16V) .............................................................................................................569
TC-ISF (VC4_16V)..................................................................................................................570
TC-UNEQ (VC4_16V) .............................................................................................................570
TC-DEG (VC4_16V) .............................................................................................................570
TC-EXC (VC4_16V) .............................................................................................................571
HO-V4-FAIL_A (VC4_16V) .....................................................................................................571
HO-V4-FAIL_B (VC4_16V) .....................................................................................................572
HO-LOM_VCnV (VC4_16V).....................................................................................................572
HO-SQM_VCnV (VC4_16V) ....................................................................................................572
HO-LOA_VCnV (VC4_16V) .....................................................................................................573
HO-LOA_RecVCnV (VC4_16V)...............................................................................................573
HO-INC_J1_MismVCnV (VC4_16V)........................................................................................573
HO-UneqMtx (VC4_16V) .........................................................................................................574
CORRESPONDENCE BETWEEN ALARM SOURCE TYPE AND CARD TYPE...........................574
TROUBLE SHOOTING BLOCK DIAGRAMS...................................................................................576
Data Interconnection Diagram (DXC 4/1).......................................................................................578
Data Interconnection Diagram (DXC 4/4 512x512) .......................................................................586
Synchronization Distribution Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 - DXC 4/1 512x512)588
Synchronization Distribution Diagram (DXC 4/4 512x512)............................................................589
Synchronization Distribution Diagram (DXC 4/1 32x32) ................................................................590
Control Architecture Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 - DXC 4/1 512x512) ........591
Control Architecture Diagram (DXC 4/4 512x512) .........................................................................592
Control Architecture Diagram (DXC 4/1 32x32) .............................................................................593
TROUBLE SHOOTING PROCEDURES ..........................................................................................594

.
Issue:1
GENERAL INDEX
Unit Internal Fault Trouble Shooting Procedure.............................................................................594

Bit Error Rate Trouble Shooting Procedure....................................................................................594
Database Failure Trouble Shooting Procedure (DXC 4/4) ............................................................597
Database Failure Trouble Shooting Procedure (DXC 4/1) ............................................................598
DATA DICTIONARY & MESSAGES.................................................................................. 600

OPERATIVE STATES .......................................................................................................................600
Administr. State...............................................................................................................................600
Availability State..............................................................................................................................600
Active Bank .....................................................................................................................................601
Boot EPROM Software Details.......................................................................................................601
Bank 1 Software Details..................................................................................................................601
Bank 2 Software Details..................................................................................................................601
Unit ID..............................................................................................................................................601
Matrix Unit ID...................................................................................................................................602
Controller & Timing Units ID ...........................................................................................................602
Unit Type - Control & Timing Subrack ............................................................................................603
Unit Type - Matrix Subrack .............................................................................................................604
Unit Type - Port Subrack.................................................................................................................604
Cross-connection Channel Role.....................................................................................................606
Conf. State ......................................................................................................................................608
Connected Unit ...............................................................................................................................608
Conn.ed Subrack ............................................................................................................................608
From Side........................................................................................................................................608
Line Id..............................................................................................................................................609
Loopback State ...............................................................................................................................609
Mapping Loopback State ................................................................................................................609
Monitor Status .................................................................................................................................609
Num. of Tribut..................................................................................................................................610
Num.................................................................................................................................................610
Operational State ............................................................................................................................610
Path Protection................................................................................................................................610
Protection Mode ..............................................................................................................................611
Switching Commands .....................................................................................................................611
Protection Role................................................................................................................................611
Protection Status.............................................................................................................................612
Protection Type ...............................................................................................................................614
Report Note.....................................................................................................................................616
Report Type ....................................................................................................................................617
SDH Traffic Type.............................................................................................................................618
SUBRACK ID ..................................................................................................................................618
To Side ............................................................................................................................................618
X Connection Kind ..........................................................................................................................619
Signal Type .....................................................................................................................................619

.
Issue:1
GENERAL INDEX
Subrack Type ..................................................................................................................................619

Standby State..................................................................................................................................620
Synch Source..................................................................................................................................620
ALARMS ............................................................................................................................................621
Alarm Sources.................................................................................................................................621
Alarms Category .............................................................................................................................625
Alarms States..................................................................................................................................626
Alarms Types ..................................................................................................................................626
PERFORMANCE MANAGEMENT ...................................................................................................627
COMPLIANCE MESSAGES .............................................................................................................627
ERROR MESSAGES ........................................................................................................................638
WARNING MESSAGES....................................................................................................................642
COMMUNICATION.............................................................................................................. 644
COMMUNICATION: BACKUP AND RESTORE ..............................................................................645
COMMUNICATION: OSI RESET DEFAULT....................................................................................645
COMMUNICATION: SET GLOBAL PARAMETERS........................................................................645
Communication: routing mode........................................................................................................646
Communication: ethernet parameters ............................................................................................646
Communication: router parameters................................................................................................649
COMMUNICATION: SETTING INTERNAL CIRCUIT STATE .........................................................651
COMMUNICATION: CONFIGURING DCC ......................................................................................651
COMMUNICATION: ENABLING.......................................................................................................655
STATIC ROUTE.................................................................................................................................655
RAP Table.......................................................................................................................................655
MESA Table ....................................................................................................................................656
MESA Range Table ........................................................................................................................656
Communication: add RAP ..............................................................................................................658
Communication: add MESA ...........................................................................................................660
Communication: add MESA/RANGE .............................................................................................661
Communication: delete RAP/MESA...............................................................................................662
COMMUNICATION: DCC PROFILES CONFIGURATION..............................................................662
Communication: manage DCC profile............................................................................................663
COMMUNICATION: ETHERNET PROFILES CONFIGURATION ..................................................665
Communication: manage ethernet profile ......................................................................................666
COMMUNICATION: ROUTER PROFILES CONFIGURATION ......................................................668
Communication: manage router profile ..........................................................................................669
COMMUNICATION: TRANSPORT PROFILES CONFIGURATION ...............................................671
EM DATABASE: MANAGING DXC................................................................................... 673

EM DATABASE: UPLOADING/DOWNLOADING............................................................................673
EM DATABASE: PASSING THROUGH MODE...............................................................................675
EM DATABASE: CHECKING ALIGNMENT .....................................................................................676
ISSUE OF EM MESSAGES TOWARDS THE NES.........................................................................676

.
Issue:1
GENERAL INDEX
PORT LABEL MANAGEMENT .........................................................................................................677
HOW TO............................................................................................................................... 680

CONFIGURATIONS ..........................................................................................................................680
Commission the System .................................................................................................................680
Configure the Synchronization........................................................................................................683
Configure Communication Parameter ............................................................................................684
Manage Cross-Connections ...........................................................................................................685
Manage Alarms...............................................................................................................................685
Configure Performance Monitoring.................................................................................................686
HOW TO SELECT OBJECTS ........................................................................................................687
How To Print Information ................................................................................................................689
How To Select a File.......................................................................................................................691
How to save the alarm log files in word format...............................................................................691

.
Issue:1
PRELIMINARY INFORMATION
This Chapter describes the type of symbols and conventions that have been used in describing the
Local Controller software.
INTRODUCTION
Contents of handbook
The Local Operator's Handbook describes the operating procedures used for accessing options
available for managing the DXC.
Conventions used in this handbook

<Key> Indicates that a key must be pressed to execute the action currently discussed in the text,
e.g.: <Return> means that the Return key must be pressed. This type of convention is used within
the text.
The symbol * followed by text indicates an action that must be performed by the Operator. For
example.
* Select option SEARCH.
Indicates that the Operator must select the option SEARCH on the menu displayed.
The [LC] symbol indicates that the relevant option is available only for the Local Controller Application
and it can not be managed by the Network Management Centre. The [NM] symbol indicates that the
relevant option is available for the Network Management Centre only.
HARDWARE REQUIREMENTS
The Local Controller can be supplied either for use in a Windows NT based system or a Unix based
system. In the following text, the hardware requirements for both platforms are presented.
Hardware Platform
The application operates on Personal Computers with the following suggested configuration:
For a Desktop following requirement must be housed:
Processor Intel PENTIUM or Celeron 233 MHz
Display 17 1024x768 SVGA (256 colour)
Graphic Card SVGA GRAPHICAL ADAPTER 1024x768 resolution 256 colors with
external output
Memory 64Mbytes (minimum) for Unix Operating System or 128Mbytes
(suggested) for Windows NT, 2000 Operating System
Hard disk 1 GIGABYTES HARD DISK (minimum)
Floppy disk 3.5" FLOPPY DISK DRIVER
Others disk CD ROM Drive
External ports n. 1 SERIAL INTERFACE RS232 (9 pin, at least 19200 bps)

.
Issue:1
Interfaces: - one parallel port (Centronics) for the printer

- one RS232 serial port for the mouse (if the mouse does not have a
dedicated port)
- one dedicated RS232 serial port for the connection to the DXC
- one Ethernet Card (suggested SMC 8003 or 8013 series) if the
connection of the Local Controller via Q interface is needed. (for Unix
O.S. only)
Input / Output - Printer
device
- Keyboard
- Mouse
For a NOTEBOOK PC the following requirement must be housed:
Processor PENTIUM (minimum 120Mhz) or Celeron (minimum 233Mhz)
Display 10" COLOR MONITOR (resolution 800x600)
Graphic Card SVGA GRAPHICAL ADAPTER 1024x768 resolution 256 colors with
external output
Memory 32 MBYTES RAM (minimum) - 64 Mb recommended
Hard disk 1 GIGABYTES HARD DISK (minimum)
Floppy disk 3.5" FLOPPY DISK DRIVER
Others disk CD ROM Drive
External ports n. 1 SERIAL INTERFACE RS232 (9 pin, at least 19200 bps)
n. 1 PARALLEL INTERFACE
Input device TRACKBALL (OR MICROSOFT MOUSE)
keyboard US/GB KEYBOARD
SOFTWARE REQUIREMENTS
The Local Controller can be supplied for a Unix based system or for a Windows NT / 2000 based
system. In the following text, the software requirements for both platforms are presented separately.
Local Controller for Unix Operating System

The following programs have to be installed on the Personal Computer:
n SCO/Unix ODT Lite rel. 3.x or SCO/Unix Open Server rel. 5.x
n SCO/RETIX LT-610 version 2.31 (only if the Remote Login via Q interface is required); this
software works coupled with SCO/Unix ODT Lite rel. 3.0

.
Issue:1
Local Controller for Windows NT Operating System

n Windows NT Version 4.0 (Workstation or Server);
n X-NutCracker v. 2.1.315 or equivalent X-Window emulator;
n X-NutCracker RunTime Library rel. 3.0 (user distribution version 1.3 is recommended).
IMPORTANT If you do not use X-NutCraker but an equivalent emulator, ensure that the X-
Window emulator is active after the system start-up.
Local Controller for Windows 2000 Operating System

n Windows 2000
n X-Nut Cracker rel. 3.0
n Exceed rel. 6.2
IMPORTANT If you do not use X-NutCraker but an equivalent emulator, ensure that the X-
Window emulator is active after the system start-up.
NOTICE Exceed rel 6.2 has only been tested under Windows 2000.
Year 2000
Be sure that the software installation is 100% year 2000 compliant. Contact SCO (www.SCO.com)
or MICROSOFT (www.microsoft.com) for the latest news about their products.
In the following the proper patches are listed:
n Windows NT 4.0: Service Pack 4.0
n SCO 3.0: UOD426D
n SCO 5.0.0: OSS603A
n SCO 5.0.2/5.0.4: OSS601A
n SCO 5.0.5: No patches
INSTALLATION AND CONNECTION OF THE PC TO THE EQUIPMENT

Personal Computer Installation
The PC should be installed in accordance with the manufacturers installation instructions.
INSTALLATION OF SOFTWARE PLATFORM

Unix Operating System with OSF/MOTIF
The Personal Computer must be configured by means of System-Setup procedure in accordance
with the computer installation manual before installing SCO.
SCO is installed as described in the SCO Installation Handbook. Different configurations are
possible, depending on the type of available devices (monitor, keyboard, mouse).

.
Issue:1
Starting Up the UNIX System

* Switch on the monitor and then switch on the computer.
* After the prompt, the following messages are displayed:
SCO System V/386
BOOT
...
...
<Return>
* After prompt:
INIT SINGLE USER MODE
Type CONTROL-d to proceed with normal startup,
(or give root password for system maintenance):<Ctrl-D>
* After prompt:
Current System Time ...
Enter New Time ([yymmdd]hhmm):<Return>
* After login prompt:
login: root<Return>
password:
Configuring a Printer
A printer must be configured in Unix in order to print reports from the Local Controller. The printer is
connected to the parallel port (/dev/ip0); use the sysadmsh command to create the printer (refer
to the SCO Unix Handbook for a detailed description of the installation).
Retix LT610
Install LT610 following the instructions given with the Retix documentation.
Windows NT / 2000 Operating System

Install Windows NT / 2000 following the instructions given within the Microsoft Windows NT /2000
documentation. Different configurations are possible, depending on the type of available devices
(monitor, keyboard, mouse).
Configuring a printer
A printer must be configured in order to print reports from the Local Controller. The printer is
connected to the parallel port LPT1.
To configure the printer use the following menu of Windows NT / 2000: Start -> Settings -> Control
Panel -> [Printers] -> [Add Printer]
Refer to the Windows NT / 2000 handbook and to the printer documentation for a detailed
description both of the procedure and of the parameters to be set.
X-NutCracker
Install the X-NutCracker emulator for X-Window on the Windows NT / 2000 platform, follow the
installation rules given with the NutCracker and the Windows NT / 2000 documentation.
Note X-NutCracker emulator is included in the installation CD ROM of the Local Controller.
It is suggested to select the Express Installation model when requested by the X-
NutCracker installation procedure.

.
Issue:1
IMPORTANT If the Nutcracker libraries are installed into a PC where Windows NT 4.0 Service
Pack 6 is loaded, the system can not use these libraries and a Fatal Error
window will appear. To solve this problem the Operating System must be
installed in manual mode, and the NutCracker libraries have to be loaded before
the Service Pack 6. You have not this problem if you have another Service Pack
(e.g. SP 4) and after installing the NutCracker libraries you upgrade the Service
Pack.
INSTALLATION OF LOCAL CONTROLLER

In the following the installation procedure for the Local Controller, both for SCO/Unix and Windows
NT / 2000 operating systems, are given. In both cases the installation of the Local Controller is
supported by a specific installation program.
Local Controller for SCO/Unix

The Local Controller application is an OSF MOTIF application completely compatible with OSF
MOTIF Style Guide. It is integrated into SCO Open Desktop and can be installed using the Unix
standard environment.
The installation procedure must be performed by the system administrator of the Unix Operating
System (root).
To activate the automatic boot procedure, after the starting up of the PC, type at the system prompt
the following command: unix auto.
Users and Directories

The figure below shows the organization of directories of the Local Controllers environment.
The directory /u/DXC41_XY/script contains the C-shell script necessary for the correct running of
the local controller application, which are added to the users .Xdefaults.<hostname> file used by
the LC application.
The directory /u/DXC41_XY/DM_script contains the Desktop shell script necessary to start the LC
process from the Desktop Manager and the LC_r X.Y icon file.
All the executable files are contained in the /u/DXC41_XY/exe.

.
Issue:1
The databases are contained in the /u/DXC41_XY/exe/DB directory.

The OSI configuration files are contained in the /u/DXC41_XY/exe/OSI_cnf directory.
The /u/DXC41_XY/exe/BM directory contains all the bitmaps displayed by the LC application.
The log application errors file LC_LOG is stored is in the <user home directory>/log sub-directory.
The file soft_ver_dxc.cnf copied in the authorized users home directory by the installation
procedure, list the unit software releases compatible with the current equipment release. It is read
when the Local Controller issues the command: System - > Check SW Release
Note After a release upgrading, remind to update the file soft_ver_dxc.cnf (for further
information refer to the Equipment Manual, section "Release Upgrading").
The English catalogue files are contained in the /u/DXC41_XY/exe/EngCat directory.
The Italian catalogue files are contained in the /u/DXC41_XY/exe/ItaCat directory.
The osi_set.msg file, which is copied in the OSI_cnf sub-directory of the Local Controller
authorized user, contains the list of the OSI files that must be sent to the Communication Unit to set
the OSI protocol configuration parameters.
When the local Controller start-up procedure fails, open the file LC_LOG by double clicking on the
corresponding icon in the log sub-directory window.
Installation Procedure for SCO/Unix

The installation procedure is based on the custom facility and it consists of the following steps:
* Configuration of the Local Controller user in Unix Operative System.
* Configuration of RS232 connections.
* Installation of the Local Controller application files.
Configure a New LC User for SCO Lite Rel. 3.0
In the following the user YYYY is added as a new Local Controllers user. His account must be
created using the procedure below:
* Login as root.
* Run the sysadmsh command.
* Select Accounts -> User -> Create
Username : [YYYY ]
Comment : [ ............]
Modify defaults? Yes
and in the next mask:
Login group : Default
Login shell : Specify
[/bin/csh ]
Home directory : Default (or specify)
[ Create home ]
User ID number : Default
Type of user : Default
and at the end confirm the creation. After the creation define the password for the user.
* Exit the sysadmsh shell pressing the <F2> key.

.
Issue:1
Configure a New LC User for SCO Open Server Rel. 5.0

In the following the user YYYY is added as a Local Controllers new user. His account must be
created using the procedure below:
* Login as root.
* Start the Desktop Manager with the command startx
* Choose the System Administrator icon
* Choose the Account Manager
* Choose Users -> Add new user from the menu bar
Login : [YYYY ]
Comment : [ ............]
Login group : Default (or specify)
Login shell : Select csh using the button on the right side
Home directory : Default (or specify)
User ID number : Default
Type of user : Default
and at the end confirm the creation. After creation define the password for the user.
* Exit the System Administrator closing all the opened windows.
Installation of the Local Controller Files
The installation procedure is based on the Unix custom facility. Since the Local Controller installation
does not overwrite the installation of previous releases the user decides to remove or to keep them.
For the de-installation procedure of previous releases refer to the related documentation. Old
releases cannot be active at the same time as the new one. The current release of the Local
Controller application runs only with the current release of the DXC Network Element.
During the installation procedure the Operator is asked to type the authorized Local Controller
application user name, created before running the installation procedure. The Local Controller user
must be different from the Local Controller user of the previous releases in order to keep the old and
the new releases.
In order to install the local controller application it is necessary to execute the

following steps.
* Login the system as root, and enter the command custom from the root home directory.
* For SCO Lite rel 3.x, select:
Install -> A New Product -> Entire Product
else for SCO Open Server rel 5.x
Software -> Install New -> from <host> -> select media -> Full Installation
* If You use floppy disk kit, insert floppy disk volume number 1 in the correct drive and
press return to continue.
The custom facility displays the information about the data compressed in the floppy disks.
* Insert all the floppy disks containing the LC software when the Unix prompt requests
them.
* If You use CD kit, select the installation directory (for further information refer to the
"readme.txt" file contained in the CD).

.
Issue:1
At the end of the decompression procedure another procedure automatically starts in order to
control the Unix Operating System version and other environment configurations that must be set up
for the Local Controller application. If these requirements are not fulfilled the procedure fails and the
installation is aborted, conversely the content of the floppy disks is loaded.
After that all the LC files are copied from the floppy disks and the initialization procedure is
executed, it asks the operator to type the authorized LC users name, then check the presence of
the user.
When an error occurs (the user does not exist or his login shell is different from /bin/csh), the
initialization procedure asks the operator to interrupt the installation or to insert a correct user name.
The installation procedure copies the .Xdefaults-<hostname> file used by the Local Controller
application in the home directory of the authorized user. If this file already exists in the user home
directory the installation procedure copies the Local Controller default settings to the .Xdefaults-
<hostname> file, saving the old files in .Xdefaults.sav.
If the user home directory contains a .startxrc, .cshrc, .mwmrc or .login file, they are saved in
.startxrc.sav, .cshrc.sav, .mwmrc.sav, .login.sav in order to avoid conflicts with the correct start
up of the Local Controller application. The directory LC_r X.Y.obj, is created, the DXC41_LC icon
file and the Desktop shell script to start the Local Controller application from Open Desktop Window
are copied into it.
* If necessary, customize the Local Controller by configuring:
- local controller baud rate (9600,19200, 38400). Serial speed configuration must be
changed by the system administrator according to this baudrate parameter;
- monochromatic or colour screen;
- type of connection used by the local controller (See details below).
The Local Controller can be connected to the DXC via a RS232 dedicated line or using an ethernet
LAN, via Q interface. Choosing the RS232 connection type, the correct device name associated to
the configured serial port must be inserted (or the default value /dev/tty1a associated to the COM1
can be kept).
If only the COM2 serial port is available, enter the correct tty associated to the Local Controller
serial port.
For the Ethernet connection define the PC address (or keep the default one). If you define a new
address, the script will restart the OSI stack.
During this phase of the installation, the mkdev dxc41_XY command is executed. The same
command can be executed later by the system administrator to change the Local Controller
application configuration. For example to enable the Local Operator to use the Ethernet or the serial
connection alternatively, to set the colour or monochromatic monitor, to define the serial baudrate or
to choose Italian or English Local Controller application language.
A new kernel will be created and this will be used as default kernel answering Y(es) at the following
questions:
Do you want this kernel to boot by default?
Do you want the kernel environment rebuilt?
A system reboot must be performed exiting from the installation procedure.

.
Issue:1
It is possible to exit from the installation procedure of any moment by typing Q (quit), when the
preparation or initialization script is running.
After the completion of the installation procedure it is necessary to reboot the system in order to
activate the new OS configuration tuning according to LC requirements. In order to do that it is
necessary to issue two times the command sync and then the command reboot.
Removal of the Local Controller files
In order to remove the LC application it is necessary to execute the following steps:
* Log in the system as root, and enter the command custom from the root home directory.
* Select Remove
* Select DXC41_XY LC product
* Select Entire Product
* Insert the authorized LC application user name
* Answer Y if you want remove script to delete the users file .Xdefaults.<hostname>
(modified by the local controller application installation procedure), N otherwise.
For SCO Open Server rel.5.0 select the DXC41_XY LC product before selecting the Software
Remove operation. To do so use the <tab> key to move between the menu bar and the product list,
the arrow keys to scroll the product list and the <enter> key to select the product (if you run custom
from the ScoLogin the mouse pointer can be used).

.
Issue:1
Local Controller for Windows NT / 2000

The Local Controller application must be integrated into Windows NT / 2000 Desktop, in order to
obtain a Local Controller entry in the menu Start -> Programs. At the end of the installation
procedure the Local Controller can be activated using the following command: Start -> Programs -
> SDH Local Controllers -> LC DXC v xx.yy -> Local Controller
The installation procedure must be carefully followed, in order to properly install the Local Controller
application into the Windows NT / 2000 Desktop environment. This procedure can only be
performed by the system administrator of the Windows NT system, named Administrator.
Users and Directories
The figure below shows the organization of directories of the Local Controllers environment.
<Installation Directory> is where the SDH Local Controller is installed. The default path is:
"C:\Program Files\SDH_LC\DXC"
NOTICE In the DXC directory is installed the DataFocus NuTCracker RunTimeLib v3.0
The directory UTIL contains the Korn-Shell script and the Batch file necessary for the correct restart
of the Local Controller application if problems occur. The sub-directory CMD contains the
commands to manage text files; read/write and convert them into Unix format.
The directory EXE contains all the executable files and the desktop batch file to start the Local
Controller from the LC DXC menu.
Note Within this directory (C:\Program Files\SDH_LC\DXC\Rel<xxyy>\EXE by default) is
located the file soft_ver_dxc.cnf (to be substituted each release updating). This file is
not recognise as an internal registered file type, anyway it can be opened and
modified by means of a generic text editor (notepad or wordpad, for example).
Refer To:
Equipment Description, section "Maintenance", chapter "Release Upgrading"

.
Issue:1
The EXE/BM directory contains all the bitmaps displayed by the application.
The EXE/bin directory contains all the named pipes used by the application.
The EXE/log directory contains all the log files where the application errors are stored and all the
Local Controller configuration files.
The EXE/DB directory contains all the alarm log files and the archive files (history files and NE
configuration).
The EXE/Eng and the EXE/Ita directories contain the strings catalogue for English and Italian
Languages.
The OSI directory contains the OSI configuration files and the osi_set.msg file. The latter file
contains the list of the OSI files that must be sent to the Communication Unit to set the OSI protocol
configuration parameters.
Installation Procedure for Windows NT / 2000

Depending on Windows NT / 2000 security management, the suggested sequence to install the SW
module is:
1. Login the system as Administrator;
2. Define a new user account;
Note This operation is not mandatory but it is suggested in order to define an user
belonging to the "Users" group.
3. Install NuTC Xserver;
4. Install NuTC library;
5. Install DXC Local Controller;
6. At the end of the installation a computer restart is suggested.
The product can be delivered using the following media:
n floppies;
n CD ROM;
n Exe files.
Depending on the media used the DXC Local Controller installation can be different. Refer to the
appropriate procedure.
IMPORTANT In the following the [xxxx] represents the icon whose name is xxxx
Creating a New User Account

The steps described in the following allow to define a new user belonging to the "Users" group. This
operation is not mandatory.
IMPORTANT This procedure has to be performed during the installation of the Local
Controller. It is not necessary during the upgrading.
* Activate the User Manager window selecting Start -> Programs -> Administrative
Tools (Common) -> User Manager

.
Issue:1
* Create the New user selecting the menu User -> New User
* Enter user data (suggested user account lcdxc)
* Click on Profile

.
Issue:1
* Select the Local Path (i.e.: C)

* Close all the windows, pressing the OK buttons and exiting the User Manager.
Installing the NutCracker Run Time Library
IMPORTANT This procedure must be performed during the installation of the Local Controller.
It is not necessary during the upgrading.
* Insert the floppy disk labelled NutCRACKER Run Time Lib v3.0 #1 (S38-0546/01.03,
K38-0174/01.03) in the correct drive.
* Double click on [My Computer] -> [3 1/2 Floppy (A:)]
* Double click on the [setup.bat] icon.

.
Issue:1
* The product is installed successfully only if you press: YES,OK or Next and never
CANCEL or NO. The installation wizard displays the information about the software in the
floppy diskettes and asks if you want to continue the installation. If you continue with the
installation you can see successive confirmation windows. When asked from installation
wizard, insert required floppy disks (disk n.2).
Installing the Local Controller Software from Floppies
* Insert the floppy disk labelled Local Controller num. 1 in the correct drive.
* Double click on [My Computer] -> [3 1/2 Floppy (A:)]
* Double click on the executable [Setup] icon.
* The product is installed successfully only if you press: YES, OK or Next and never
installation you can see successive confirmation windows. When asked from installation
wizard, insert required floppy disks ("Local Controller" disk from n.2 to n.5)
This operation copies some few files onto your system. Refer to "install.log" file for further
information.
* Choice Italian or English language when the procedure asks you. This installs Local
Controller language-depending files.
* At the end of the procedure remove the last floppy disk and reboot the system.

.
Issue:1
Installing the Local Controller Software from CD ROM

* Insert the CD.
* Select the Local Controller to be installed.
The automatic installation will start.
installation you can see successive confirmation windows.
If the automatic installation doesn't work, browse the CD, select the appropriate folder and double
click on the "setup" icon. See documentation onboard CD ROM (readme.txt) for further information.
IMPORTANT If the CD contains only the self extracting files, refer to the following " Installing
the Local Controller Software from Exe Files" procedure.
Installing the Local Controller Software from Exe Files

Having the EXE auto-extracting files (i.e. obtained from E-mail or downloaded from Web page):
* Extract all the EXE files in a temporary folder simply by clicking on them or dragging them
using the right click of the mouse.
* Open the temporary folder then double click on [setup.exe] icon.
installation you can see successive confirmation windows.
* Delete content of temporary folder
Removal of the Local Controller Files
In order to remove a specific version of the LC application it is necessary:
* Make sure the application is not running.
* Double click on [My Computer] -> [Control Panel] -> [Add/Remove Program] icon.
* Double click on "SDH LC DXC v.xxyy" item.
The same result can be obtained using the menu:
[Start] -> [Programs] -> [SDH Local Controllers] -> [DXC v.xxyy] -> [Uninstall]
Removal of the NutCracker Files
In order to remove NutCracker application it is necessary:
* Make sure the application is not running.
* Double click on [My Computer] -> [Control Panel] -> [Add/Remove Program] icon.
* Double click on "NutCracker" item.
NutCracker is active at the computer startup then some in use file will not be removed by the
uninstall facility. To delete them the Operator has to:
* Perform a computer restart
(the application has been removed then is not started).
* Delete manually the following files:
- nutconf.cpl

.
Issue:1
- X11.dll
- ncmsgs.dll
- nutc.dll
- nutcom.dll
- socket.dll
- dxelmsgs.dll
How to Install Add-On Files
The following modules can be added to the product:
n Nationalisation,
n Equipment downloadable files.
These modules are delivered as self-extracting files.
To install the self extracting files:

Follow the procedure described in: Installing the Local Controller Software from Exe Files
Customizing the LC Configuration for SCO/Unix Version

Configuration of the RS232 Serial Port
Current configuration of the serial lines of the UNIX system can be checked and modified by the
system administrator. The following procedure describes how to configure a new serial board.
* Login the system as root and enter the command mkdev serial (A list of the currently
configured serial line ports is displayed).
* If needed, define a new serial line selecting the option Install a new serial board.
* Answer the following questions as described:
Would you like to install:
1. one port card
The card is configured as:
1. COM1
or
2. COM2
Choose the number relevant to the card to be configured
Which card do you have:
1. IBM-COM2
Please enter the baud rate to be used on the modem device :
<baudrate>
The following /etc/gettydefs (F) entries support <baudrate> baud
lines:
1. <baudrate> (where baudrate must be 9600 - 19200 - 38400)
Choose the baudrate 9600bit/s
Modify the system file ? yes

.
Issue:1
* Relink the kernel and run the new one issuing two times the command sync and then the
command reboot
Utility mkdev
Current configuration of the Local Controller can be checked and modified by the system
administrator. The following procedure describes how to set a new configuration.
1. Login as root.
2. If you are in graphic mode, open a UNIX shell.
3. Digit the command:
mkdev dxc41_<LC version>
Example:
mkdev dxc41_63
4. Follow the program instructions to configure the parameters:
- baud rate (9600 bit/s)
- monitor (monochromatic or colour)
- serial interfaces tty1a (COM1) or tty2a (COM2)
- language (English or Italian)
Customizing the LC Configuration for Windows NT / 2000 Version

Utility Tools
IMPORTANT Use of these tools is recommended only to a skilled operator.
The following tools are available selecting the menu:

Start -> Programs -> LOCAL CONTROLLERS -> UTILITY
1. SET_ENVVAR: Edits envvar.bat file in order to set some environmental values.
IMPORTANT If wrong values are set, Local Controller will not work properly.
A copy of the previous envvar.bat file is available as envvar.bak.
2. TAIL: Dragging a text file over this icon, it displays the last rows of the file, while they are
written (like the tail f Unix command).
3. ALARMTAIL: Performs tail operation over alarm.dat file.
Note Only for expert users or Marconi personnel.
4. EDIT: This is the old edit of the DOS system. It can read a UNIX file dragging a unix-formatted
text file on its icon. After the save command, the editor automatically produces a the file in
DOS format.
5. DOS2UNIX: If You want export a file in Unix format, dragging it over this icon. Your file will be
reformatted in Unix mode and Unix computer will be able to read this.
6. README: shows the readme.txt file.
Setting the Language of the LC
At every time, after installation, you can change selected language, simply by click [Set Italian] or
[Set English] icons from Start menu ([Start] -> [Programs] -> [SDH Local Controllers] -> [DXC
v.xxyy] -> [Set English / Italian]). If it doesn't work, try to execute "ita.bat" and "eng.bat" files in a

.
Issue:1
"DOS shell" window. The files are located in the selected installation directory: by default it's
C:\Program Files\SDH_LC\DXC\rel<xxyy>
Configuration of the RS232 Serial Port
The default serial line is COM2; if it is necessary to use another COM the operator will have to open,
by an ASCII editor (like notepad), the file envvar.bat in the local controller directory EXE; then he
must look for the row set TTY_A_NAME=COM2 and change it consequently (i.e. set
TTY_A_NAME=COM1).
* Activate the window for port configuration. double clicking on [My Computer] -> [Control
Panel] -> [Ports]
* Set the correct values for the COM2 serial port by pressing the button Settings
* Set the Baud Rate to 9600, the Data Bits to 8, the Parity to None, the Stop Bits to
1, the Flow Control to None, as shown in the following picture.
* Close all the windows, pressing the OK and Close buttons.

Setting the Screen Resolution
Make sure you have a sufficient screen resolution (we suggest a 256-colour - 1024x768 pixel
resolution). To set this parameter select [My Computer] -> [Control Panel] -> [Display] and the
Settings option.
If you cannot use a 1024x768 resolution we strongly recommend at least a 800x600 resolution. In
such case select the option Always on top in the Taskbar Property menu.

.
Issue:1
Connect the Personal Computer to the Equipment

The DXC can be connected to the Personal Computer in two different ways:
n Using the serial port (F interface)
n Using the Communication Unit through the Q interface. (Only for the Local Controller
based on Unix O.S.)
F Interface
The connection of the equipment to the PC can be obtained using the serial port 1 (COM1; tty1a) or
serial port 2 (COM2; tty2a).
Information relevant to the assignment of the serial ports is given in the PC Operating Instruction
Manual. The PC serial interface must be connected to the F interface connector of the DXC 4/1
128x128, DXC 4/1 256x256, DXC 4/4 512x512, DXC 4/4 1024x1024 (Fig. 1) or DXC 4/1 32x32
(Fig. 2).
The cable and the connectors used in order to prepare the PC cable for the F interface, together
with the relevant cabling instructions, are described in the Equipment Manual in Section 2
Installation.
Q Interface
The connection via Q interface (Remote Login) can be used only if the Personal Computer is
equipped with an ethernet card and the software for the management of the OSI communication
(Retix LT610) has been installed.
Connection is made by means of an ethernet cable connecting the ethernet interface of the
Personal Computer to the BNC connector (10 BASE 2) available on the front panel of the
Communication Unit of the DXC (Fig. 3).
There is also available a 10 BASE 5 interface that can be activated using hardware settings on the
Communication Unit (Fig. 1, Fig. 2 and Fig. 3).

.
Issue:1
Fig. 1 Connection of the Personal Computer to

DXC 4/1 128x128, DXC 4/1 256x256, DXC 4/4
512x512, DXC 4/4 1024x1024

.
Issue:1
Fig. 2 Connection of the Personal Computer to

DXC 4/1 32x32

.
Issue:1
Fig. 3 Connection of the Personal Computer to the

DXC via Q Interface (10 BASE 2)

.
Issue:1
Connect Personal Computer to a Printer

The printer should be connected to parallel port 1 (UNIT 0; dev/lp0 for the Unix operating System) of
the PC (see Fig. 1 and Fig. 2). Information about the assignment of the ports can be found in the PC
Operating Instructions.
The parallel (Centronics) interface on the printer has to be used. Check whether the printer interface
is correctly configured. Information about this can be found in the operating instructions for the
printer.
Connection Centronics cable (commercial).
Assignment Centronics standard.
IMPORTANT The printer must be configured before being accessed. Instructions to configure
the printer under Unix or Windows NT operating systems can be found in the
respective documentation.

.
Issue:1
USERS INTERFACE
WORKING AREA
The OSF/Motif Desktop forms the LC work area. The organisation of the facilities offered by the
desktop can be divided into four basic areas (Fig. 4):
1. Main Menu: which makes available all the options of LC.
2. Selection Window: used to select subracks and units.
3. Dialog Box: used to write or read data.
4. Real Time Monitor Window: used to alarm and event monitoring.
Main Menu
Selection Window
Dialog Box
Real Time Monitoring Window
Fig. 4 LC Working Area
Each operation opens a window in the Working Area displaying the data relevant to the operation.
More than one window can be opened on the Working Area depending on the type of operation to
be executed.

.
Issue:1
USERS INTERFACE
How to Move a Window in the Working Area

Since more than one window can be opened in the Working Area it can be necessary to move a
window in order to display information which are hidden by other windows.
To move a window proceed as follows:

* Position the mouse on the Title Bar of the window (Fig. 5).
* Click the left-hand button of the mouse and drag the window to the new position.
Fig. 5 Move Window: 1 step
* Release mouse button when You are in the desired position. The window has been
moved to the new position (Fig. 6).

.
Issue:1
USERS INTERFACE
Fig. 6 Move Window: 2 step

.
Issue:1
USERS INTERFACE
How to Move a Window to the Front

When many windows are displayed on the Working Area can be necessary to access a window that
is not completely displayed.
To move a window proceed as follows:

* Position the mouse on one (visible) border of the window (Fig. 7) which is back.
* Click the left-hand button of the mouse. The window is moved to the front (Fig. 8).
Fig. 7 Move a window to the front: 1 step

.
Issue:1
USERS INTERFACE
Fig. 8 Move a window to the front: 2 step
Menu Selection
In each Selection Window is available an option bar (Menu Selection) containing the options which
are made available after an object selection.
Options can be selected using the mouse.

Only options available for the current action can be selected (options not selectable are greyed).
The option File-Exit is used to close the Selection Window and return to the main menu.

.
Issue:1
USERS INTERFACE
Information Boxes
Selection Windows contains some areas (Information Boxes) where are displayed information
about the operational states of the objects shown.
Normally the operational states are displayed using a scroll box (the information displayed can be
scrolled up or down using the scroll-bar). The information are read-only and no modifications can be
made.
Also the lists are considered as Information Boxes which are used to display the status of the
object which is going to be selected.
There are many different operational states available for the Information Boxes depending on the
action to be performed (e.g.: Equipment Commissioning, Alarms, etc.).

.
Issue:1
USERS INTERFACE
DIALOG BOXES
A menu command opens a Dialog Box. A dialog box is a convenient way to view and set multiple
options.
When youre selecting options in dialog boxes, you work with seven basic types of on screen
controls: command buttons, lists, pull-down options, sliders, arrow buttons, text boxes and card
active alarm buttons.
Text boxes Card Active Alarm Push Button
Lists Scroll bar
Pull-down options
Text box
Command buttons
Slider
Arrow button

.
Issue:1
USERS INTERFACE
Command Buttons
The dialog boxes in the example have two command buttons: APPLY and CLOSE. If you choose
APPLY, LC will execute the command using the data entered. If you choose CLOSE the dialog box
is put away (nothing changes and no action occurs).
Lists
Information can be displayed in a list. List can be scrolled using a scroll bar if the contents do not fit
in the space provide (see also Scroll-bars).
Pull-Down Options
A pull-down option makes available a list of fixed values for a certain field.
To select a value:
* Position the mouse on the pull-down option (e.g.: System Oscillator Frequency (38.88
MHz)).
* Click the left-hand mouse button.
* Choose the desired option and confirm by clicking again.
Sliders
In this case positioning the cursor on the bar, pressing the left-hand button of the mouse and sliding
the mouse can modify data values.
The value of the field will be one reached when the button is released. The value is indicated in the
text box near to the slider.
Arrow Buttons
The arrow button is used to increase or decrease a numerical value that is displayed in a text box
near the arrow itself.
To modify the value click with the left-hand mouse button on the up arrow (to increase) or on the
down arrow (to decrease).

.
Issue:1
USERS INTERFACE
Text Boxes
There are two different types of text boxes: read-only text box and keyboard input text box.
A read-only text box is used to display a value (the Operator cannot modify or type data in these
types of boxes).
In the case of a keyboard input text box the data are entered by position the mouse onto the
specific field and clicking the left-hand mouse button. A cursor will appear and the Operator can type
the desired value.
Card Active Alarm Push Button
This facility displays the list of the active alarms detected in the selected unit/ subrack.
See Also:
Alarms: displaying subrack active alarms, Active Alarms: displaying unit active
alarms

.
Issue:1
STARTING LOCAL CONTROLLER
This Chapter describes the procedures for starting the SDH Local Controller.
SCO/UNIX VERSION
* Login as Local Controller User
Username:
Password:
The SCO Login can be enabled or disabled.
If SCO Login is disabled the user must log into the system and then must type the command startx
to start the Desktop Manager.
* Double-click on the authorised users directory icon of the Local Controller (e.g.
DXC41_XY).
* Double-click on the LC_r X.Y icon (where X.Y is the current release of the Local
Controller).
The SDH Local Controller Main menu will be displayed.
Troubleshooting
The following advices can be used whenever there are problems in the installation or starting up of
the Local Controller.
Installing the Local Controller, after activating the installation of the Local Controllers files
(Software menu of the custom application), nothing happens.
Wait. In some computers (notebook) the identification of the floppy disk driver as a media for the
installation can take some minutes.
At the end of the installation procedure, a warning message about a validation error appears.
Dont worry about this message. The installation procedure modifies some files to make them
compatible with the Local Controller: this causes a failure in their integrity check.

.
Issue:1
WINDOWS NT / 2000 VERSION

After the installation, the Local Controller is initialized with default values in the NE configuration file.
If changes in the default values are needed, follow the first starting up procedure.
IMPORTANT Be sure that the X-Window emulator is already installed and active at the system
start-up
Starting Up Procedure
* Login the system as Local Controller user (if created).
* Start the Local Controller selecting
Start -> Programs -> SDH Local Controllers -> DXC v.xxyy -> Local Controller
* When a black DOS window appears, minimize it.
* Activate the Network Element Configuration window clicking on [DOMAIN] in the Local
Controller window.
* Select the DXC and modify (if needed) its NE configuration clicking on the element dxc
and selecting the menu Actions -> Modify
* Apply the modifications and close the open windows.
Reset Procedure
In case of problems during LC execution or LC crash a reset procedure can be necessary.
* Select: Start -> Programs -> SDH Local Controllers -> DXC v.xxyy -> Reset
NOTICE Use of this procedure is recommended only for skilled operator.
The reset procedure can be summarised in the following steps:

1. the procedure automatically removes some shared data;
2. the procedure asks to the Operator to close LC windows (if any);
3. Nutcracker services are stopped and then restarted;
4. The "Tune Nutcracker" window appears. Change one value and then restore it. This forces an
X-Server restart. Close windows with OK
5. Task Manager window appears. Follow the instructions and kill the LC processes. Closing the
window the procedure will finish.
Troubleshooting
The following advices can be used whenever there are problems in the installation or starting up of
the Local Controller.
You cant install the software (by CD-ROM).
The Autorun function may dont work correctly. Read the file readme.txt for more information.
After the appearing of the black initial window, nothing happens, but the sentence Cant open
display seems to appear just before the window closes.
The X-server process is probably not active. Be sure to activate the X-server before starting the
Local Controller:
a. Login the system as Administrator.
b. Press simultaneously the keys Ctrl Alt Del to enter the Windows NT / 2000 Security
window.

.
Issue:1
c. Select the option Task Manager.

d. Select the option Processes in the Windows NT / 2000 Task Manager window.
e. Verify that the processes NUTKSERV.EXE and NUTCXSRV.EXE are active.
f. Close the Windows NT / 2000 Task Manager window.
g. If the X-NutCracker is not active: Double click on [My Computer] -> [Control Panel] ->
[NutC] Select [Default X server] and set [Nutcracker DEV X server].
Note If you make a link to your Xserver executable in the [Startup] folder, every time the
computer starts, the Xserver will be automatically started too.
The Local Controller starts, but when you try to login the system halts.
If your PC is a Notebook (or anyway, if you dont use COM2) follow the procedure Configuration of
the RS232 Serial Port in the chapter Customizing the LC Configuration for SCO/Unix- Windows
NT / 2000 Version to modify the environment file.
If your PC has not a network connection, verify the installation of the Remote Access Services
(RAS):
a. Double click on [My Computer] -> [Control Panel] ->[Network]
b. Select Services and verify on Network Services the presence of Remote Access Service
(RAS).
c. If this option is not in the list, select [Add] -> [Remote Access Service] and the [OK]
Note During the installation, the system will ask you for a modem. Skip the automatic
research facility and select a [standard] [9600] modem configuration. The installation
requires the Windows NT / 2000 CD-ROM.

.
Issue:1
The Local Controller starts, but in the black window the following message appears:
X Toolkit Warning: Cannot convert string <Key>DRemove to
type VirtualBinding
Do not worry about this message.
After the installation of all the software, the Local Controller doesnt work if you are logged as lcdxc
user. The Local Controller starts only if you are logged as Administrator.
As a consequence of the security management of Windows NT / 2000, the right installation
sequence is:
a. Login as Administrator.
b. Create the lcdxc user.
c. Install the NuTC X server.
d. Install the NuTC Run Time Lib.
e. Install the Local Controller
If you already installed the software, use the following procedure to give the rights to the lcdxc user:
a. Login as Administrator.
b. Double click on [My Computer] - right click on [C:] - click on Properties.
c. In the Properties windows, click on Security and then click on Permission.
d. Select the two Replace Permission on options and then click on Add....
e. In the Add window, click on Show Users, select lcdxc and then Type of Access - Full
Control.
The F Interface Window appears almost black.
Iconize it and then re-open it.
In the [Network Element Configuration] window, strange values appear.
It happens when the NE.cnf configuration file is missing or corrupted. Dont try to delete these
values. In the first Local Controller Installation floppy disk, the default NE.cnf configuration file is
present. Copy this file in the folder: C:\Program File\SDH_LC\DXC\rel<xxYY>\EXE\Db
The Local Controller window is closed and the cursor is not able to select anything.
Probably the Local Controller has been closed using the Windows NT / 2000 button (at the top right
of the window frame). The Local Controller can be reset using the [Reset] script in the users
directory.
IMPORTANT Never use the Windows NT / 2000 button to exit the Local Controller. Use
always the [Exit] option in the Local Controllers menu [File].
Link seems to have some problems: link down, (or) sometimes it goes down without apparent reason
(or) DB upload does not correctly end.
Try to disable the FIFO buffer for the used serial interface (COM1 or COM2). This setting can be
accessed following the path: START-> Settings-> Control Panel-> [Ports]-> [Settings]->
[Advanced]-> [FIFO Enabled]

.
Issue:1
LOCAL CONTROLLER MAIN WINDOW

Use this window to activate the Local Controller or to manage the Remote Login.
Monitor
Selecting the MONITOR button it is possible to access the Network Monitoring Session (e.g. for the
detection of all the Network Elements alarms). This option is not yet available.
Domain
Selecting the DOMAIN button it is possible to manage the local configuration (NEs type
configuration, NEs location and addresses) of the network elements domain.
See Also:
NEs Domain Management
NE Control
Selecting the NE CONTROL button it is possible to select a NE to start a Control Session (eg. to
change NE configuration and collect NE alarms).
See Also:
Control Session Activation

.
Issue:1
Initial Printer Selection

Path (File-Print Select)
Use this option to display and select the printer used to print the information available for some
reports when displayed. This information is stored in a file so that is not necessary to perform the
printer selection each time the user logs in.
To select a printer:
* Select the printer in the list.
* Press APPLY.
Initial Printer Setup

Path (File-Printer Option)
Use this option to define the size of the font used to print the information available for some reports
when displayed.
To select the font size:

* Select the Font Size.
* Press APPLY.

.
Issue:1
NEs Domain Management

Use this option to manage the network elements domain (NEs type configuration, NEs location and
addresses).
Adding a New Network Element

Path (Actions-Add NE)
This option allows to create a new NE configuration with the definition of NE id. name, NE Location
and addresses.
To add a new NE:

* Enter the Network Element Name (any alphanumeric character).
* Enter the NETWORK ELEMENT LOCATION (any alphanumeric character).
* Enter the NETWORK SAP ADDRESS used to identify the equipment in the managed
network.

.
Issue:1
The NSAP is a globally unique address that identifies a point to which other systems can send data.
This address is divided in three different groups of information: Address Area, System Id and
Selector. The NSAP value must be the same entered in the Equipment.
The Address area can be a hexadecimal number of up to 13 bytes long (26 digits). It identifies the
area in which the equipment is inserted and must be the same of the Local Controller Personal
Computer. LC Hostsystem, and all NEs of the domain must be in the same area.
To display the PC Address area in a SCO system set in a Unix shell the command
/usr/bin/osi/nsap the PC NSAP will be displayed: the first 26 digits are the address area Id..
In Windows NT / 2000 system the way to display this information depends on the device
configuration (accessible from the Control Panel) and it changes according to the vendor software.
The System Id. is a 6 hexadecimal number string (12 digits) which identifies single equipment and
must be unique in the whole network.
Its format is user defined and can be used for example to code Exchange, floor and row of the NE
i.e.:
00 A0 AD 03 02 01
Row #1
Floor #2
Exchange #3
The Selector is an hexadecimal number (2 digits) used to define if the previous information are
related to an NSAP address (01) or to a network entity title (00).
For this reason the selector value must be always 01.
IMPORTANT NSAP must be entered the first time using Local Controller via the F interface.
* Press APPLY
See Also:
Communication: set global parameters
Reading the Network Element Configuration
Path (Actions-Get Address)
This option allows to display the NE configuration data.
Modifying the Network Element Configuration
Path (Actions-Modify)
This option allows to change the NE configuration data. The values shown are those currently in
use.
To modify the NE configuration:

* Type the new values in the proper fields.
* Press APPLY.

.
Issue:1
Deleting a Network Element

Path (Actions-Delete)
This option is used to remove a Network Element from the list.
To delete a Network Element:

* Select the NE to be deleted.
* Press APPLY.
Control Session Activation

Selecting the NE CONTROL button it is possible to select a local or remote NE to start a Control
Session (eg. to change NE configuration and collect NE alarms). The "Network Element
Configuration" window is displayed. Local NE is the default USER ACCESS.
Activating a Control Session on the Local NE

* Press APPLY
The system will show the login window.
* Insert the equipment username and password.

There are four different users available in the equipment:
read_user:
read only user. This user allows read operation only.
write_user:
read/write user. This user allows any equipment modifications except the supervisor user password
changing, the calibration of the oscillator in the TSU, the PLL cut frequency and the modification of
a card type for a trib. unit
Default Password: Write_user

.
Issue:1
supervisor:
this user has all the rights to perform any operation.
Default Password: Supervisor
fielduser:
this user has the same rights of supervisor.
The operator to log in as fielduser has to:
- set the stand-by CCU in monitor mode (following the procedure describes in
Section 4 - Release Upgrading of the Equipment Manual);
- extract the CCU not in monitor mode;
- open a monitor session;
- check the active bank using the command "C";
- enter the command R <active bank number> (RUN).
Now it will be possible to start the LC application and log in as fielduser (with the CCU in monitor
mode).
The password is always Fielduser and can not be changed. This user can change the password
of the other two users (write_user and supervisor).
The fielduser rights can not be disabled from the Element Manager;
this user has the maximum priority.
* Press APPLY
Activating a Control Session on a Remote NE
IMPORTANT The Remote Access functionality needs the Retix LT610 software supported by
SCO Lite rel. 3.0 operating system. Windows and SCO Lite rel. 5.0 operating
system do not support Retix then LC running on this systems will not manage
this facility.
* Select, using the mouse, the Remote NE option.

* Press APPLY.
A window for Network Element selection is displayed.
* Select, using the mouse, the NE to control in the available list.

* Insert the equipment username and password at the bottom of the window.
* Select option Actions-Start.

.
Issue:1
Having entered the correct Username and Password the Local Controller Main Menu is displayed.
Login Password is stored into the non-volatile memories of the equipment. For security reasons only
the Operators involved in the management of the equipment should know the password.
See Also:
NEs Domain Management, Security: modifying password
SHUTTING DOWN THE COMPUTER

Before switching off the computer it is necessary to perform the shutting down procedure of the
operating system.
In the following two procedures are given: one for SCO Unix operating system and the other for
Windows NT.
SCO UNIX Shut Down Procedure

The operator must log in as root (supervisor) and must execute from a shell the command:
shutdown -g0 -i0 -y
Windows NT / 2000 Shut Down Procedure

The operator must choose the menu Start -> Shut Down and then the option Shut down the
computer
Note For further information see the operating system manual.

.
Issue:1
DXC MAIN MENU
GENERAL INFORMATION
The Main Menu Window makes available all main options of Control Application. The Main Menu
Window is divided into the following parts:
n Operational feature;
n DXC messages;
n Alarm summary indication;
n Signallers;
n Other indications.
Fig. 9 DXC Main Menu (Italy)
Fig. 10 DXC Main Menu (other Countries)
Two types of indicators are available depending on the alarm scheme chosen.
See Also:
NE Model: selection

.
Issue:1
DXC MAIN MENU
Operational Feature
The Operational Feature are all main functions available for managing the DXC. After selection of
an option with the mouse a pull-down menu appears.
File
To quit the Control Application and configure a printer.
Equipment Configuration
To manage the configuration (subracks, units and ports), to define the equipment protections (1+1
and 1:N), to define the synchronisation, to enable/disable maintenance loops and tests and for
configuring the network addresses.
Connection Configuration
To manage the cross-connections of the equipment, to define the path protections, Tandem
Connection termination and Auxiliary Connection.
Fault
To manage the alarms (category, priority and reporting) and to display active alarms.
Performance
To manage the quality data collection.
Security
To change Users password.
System
To manage miscellaneous system functions e.g.: system restart, time, SW download, etc.
Database
To manage DXC database upload/download, to set the passing through mode and to check the
DXC database alignment [NM].
DXC Messages
In the Message Area of the Main Menu are displayed messages relevant to the type and location
of DXC.
Location Name
In this box is displayed the DXC location. This information can be written by the User during the
equipment commissioning by means of the option NE Model Setup

.
Issue:1
DXC MAIN MENU
Equipment Type
In this box is displayed the equipment type and matrix size: MSH96 (1024x1024), MSH91
(512x512), MSH86 (512x512), MSH84 (256x256), MSH80 (128x128) or MSH83 (32x32). This
parameter is modifiable by the User during the equipment commissioning using the option NE
Model Setup.
NE Port Mode Default
In this box is displayed the default Port Mode configuration.
Test State Indication
This field indicates if the equipment is in a Test State condition. This state can be configured by the
user and it allows to perform test on the matrix.
See Also:
Test State: management
Alarm Summary Indication

For each alarm category the status (ON/OFF) and the number of active alarms (if present) are
displayed. Indication box in the example means that 14 Not Urgent alarms are active.
As illustrated in the previous page the type of these indication boxes depends on the alarm scheme.
The meaning of these indicators (Alarm Counter) appears at the bottom of the main menu when the
mouse pointer is moved on them.
Signallers
The signallers of the Main Menu are used to display information on:
a. Current Access Rights
b. TMN Status
c. NE Status
d. Log Status
e. Interface In Use
The different icons used to display the indications are explained below:
The meaning of each signaller appears at the bottom of the main menu when the mouse pointer is
moved on the icon.

.
Issue:1
DXC MAIN MENU
Current Access Rights

This indication represents the LC access right that can be: READ / WRITE ( I ) or READ ONLY ( II ).
TMN Status
This indication shows the conditions of connection:
The icon ( I ) means that DXC equipment is accessible by the Local Controller. If DXC is already
controlled by the TMN the icon will change (II) in order to inform the Operator that Equipment is not
accessible by the LC for modifying but only for reading.
NE Status
The online status signaller is used to display the online status of the controller unit (communication
between CCU and all the other equipment units).
The icon can be OPERATIVE ONLINE ( I ), OPERATIVE OFFLINE ( II ).
Mux Controller OFFLINE means that the Central Control Unit is not able to communicate with the
controllers composing the equipment.
Log Status
This signaller displays the status of the DXC alarm log file. Icon ( I ) means that the number of
stored alarms does not exceed the set threshold for the alarm log; Icon ( II ) means that the
maximum number of alarms has been stored in the Alarm Log file.

.
Issue:1
DXC MAIN MENU
Interface In Use
F INTERFACE ( I ) for connection to the Personal Computer (LC) and Q INTERFACE ( II ) for
connection to the Ethernet network (TMN or Remote Login).
Other Indications
After a command is entered the Control Application starts to execute it and data are transferred
through the serial port or through the Q interface. During this operation the Command In Progress
Indicator lights on and no operation can be performed.
In the main menu lower right corner the CCU Protocol Version is displayed.
In the main menu title bar the Software version is displayed.
The meaning of indication appears at the bottom of the main menu when the mouse pointer is
moved on it.

.
Issue:1
MANAGING SUBRACK CONFIGURATION
PRINTER: SELECTION
Path (File-Print Select) [LC]
Use this option to display and select the printer used to print the information available for some
report (e.g.: alarms). This information is stored in a file so that is not necessary to perform the printer
selection each time the user logs in.
To select a printer:
* Select the printer in the list.
* Press APPLY.
See Also:
How To Print Information
NE MODEL: SELECTION
Path (Equipment Configuration-Node Setup-NE Model Setup)
This option is used to specify the type of Digital Cross-Connect (DXC) managed by the Control
Application (DXC 4/4 512x512, DXC 4/4 1024x1024, DXC 4/1 512x512, DXC 4/1 256x256, DXC
4/1 128x128, DXC 4/1 32x32).
NE model describes the hardware installed on the Controller & Timing and Matrix subracks.
It is used to:
1. Set the max number of available MTX access;
2. Set the max number of available SIO units (2 on MSH83, 6 on MSH80, 8 on MSH91, 10 on
other models);
3. Set Alarm Source types for Matrix Alarm reporting;
4. Configure Matrix subrack management;
5. Set up Controller & Timing subrack and Matrix subracks layout on LC/EM HCI.
This window is automatically displayed when the equipment is commissioned for the first time or has
been decommissioned.
To select the NE type:

* Select the NE Type (Matrix Size):
MSH83 (32x32)
Synchronous Digital Cross-Connect for 32 STM-1.
MSH80 (128x128)
MSH84 (256x256)
MSH86 (512x512)

.
Issue:1
MSH91 (512x512)
MSH96 (1024x1024)
* Press APPLY.
The NE Type has to be configured according to the CCU software. If the Operator tries to define a
NE Type not supported by the CCU software, the message "Not Supported" will be displayed.
NE MODEL: DEFINING LOCATION AND ALARM INTERFACE

Path (Equipment Configuration-Node Setup-Set Site Name)
This option is used to define the type of alarm processing and the site name where the equipment is
located.
Furthermore it allows to define Parallel I/O Unit management (for MSH83 or for Not MSH83
Controller & Timing subrack).
As the previous option this window is automatically displayed when the equipment is commissioned
for the first time or has been decommissioned.
To set the local alarm interface and the location name:

* Use Local Alarm Interface pull-down menu to set the alarm interface configuration (refer
to the Documentation supplied with the equipment for more information).
IMPORTANT The FOG and Italy2 Local Alarm Interface need specific hardware settings on
the Parallel Expansion Unit. Refer to the "Equipment Manual" - section 3.
* Enter in the Location Name the identification of the equipment in the network (i.e.: the
exchange where the equipment is located). The field can be left empty if no identification
is needed.
* Press APPLY.

.
Issue:1
Rack Visual Indications

According to the selected Local Alarm Interface three different rack lamp configurations are
available:
Sweden and Italy
Red:
Active Not Acknowledged.
Yellow:
Active Acknowledged.
Green:
Not Used.
Denmark, Canada, Norway, FOG and Italy2
Red:
Active Not Acknowledged Urgent.
Yellow:
Green:
Active Not Acknowledged Not Urgent.
Bahrain
Red:
Active, Not Acknowledged, Urgent and Not Urgent.
Yellow:
Green:
Active, Acknowledged and Not Acknowledged, Indicative.

.
Issue:1
CONTROL AND TIMING SUBRACK: COMMISSIONING

Path (Equipment Configuration-Subrack Commissioning-Control & Timing Subrack)
This option is used to manage the unit configuration of the Control and Timing Subrack of the DXC
equipment.
The units commissioned by the Operator are the Serial Expansion Units (A and B), Timing Selector-
Oscillator Units (A and B) and Communication and Q Interface Units (A and B).
All other units are equipped (and cannot be decommissioned) by default by the system because
they are necessary for the operation of the equipment.
To commission CT Subrack and to activate the Action menu:

* Select the Control and Timing Subrack.
* Select the unit.
See Also:
How To Select Objects, Operative States

.
Issue:1
Control and Timing Subrack: equipping

Path (Action-C&T card management-Create)
This option is used to equip units into the Control and Timing Subrack.
Equipping a Serial Expansion Unit
The Serial Expansion Unit is the first type of unit to be equipped in the Control and Timing Subrack.
The Serial Expansion Units are used to connect all peripheral subracks (Ports Subracks and Matrix
Subracks) and units (Timing Selector-Oscillator Unit) to the Central Control Unit.
Each Serial Expansion Unit makes available a maximum of 18 serial lines for connecting the
peripheral units. The first Serial Expansion Unit connects the Matrix Subracks and the Timing
Selector-Oscillator Units using the first four lines. The remaining fourteen serial lines are used for
controlling the port subracks.
Both Worker (A) and Protection (B) Serial Expansion Units are provisioned at the same time.
To equip a Serial Expansion Unit:

* Enter the Number of equipped lines used in the selected Serial Expansion Unit. The
number of serial lines equipped depending on the number of Ports Subracks to be further
connected (1 Ports Subrack = 1 serial line).
For the first Serial Expansion Unit at least four serial lines must be equipped since they are
necessary to connect the Central Control Unit to the Timing Selector Oscillator Units (A and B) and
to the Matrix Controller Units (A and B).
The information defined for the Serial Expansion Unit A (Selected WORKER SIO CARD) must also
applied to the Serial Expansion Unit B (PROTECTION SIO CARD).
* Press APPLY.
Equipping a Timing Selector Oscillator Unit
The Timing Selector Oscillator Unit contains the main oscillator of the equipment. Two units are
available, one is the working unit (providing synchronisation) the other is in stand-by state.
Both Worker (A) and Protection (B) Timing Selector Units are provisioned at the same time.
To equip a Timing Selector Unit:

* Press APPLY.
The serial lines (Line Id) used for each Timing Selector Oscillator Unit (WORKER and
PROTECTION) are indicated in the dialog box.
Equipping Communication and Q Interface Unit
The Communication and Q Interface Unit has to be equipped if the DXC is remotely controlled by
means of Local Controller Remote Login or by means of NMC (Network Management Centre) and
to manage DCCs (Data Communication Channels of the STM-N interfaces).
If the 1+1 unit protection or the load sharing is required, take care to provision also the
Communication Unit B unit.
To equip a Communication and Q Interface Unit:

* Press APPLY.

.
Issue:1
See Also:
Operative States
Control and Timing Subrack: displaying operational state

Path (Action-Subrack Management-Read)
This option is used to display information on the operational state of the units present in the Control
and Timing Subrack.
See Also:
Control and Timing Subrack: equipping, Operative States
Control and Timing Subrack: modifying unit configuration

Path (Action-Subrack Management-Modify)
This option becomes active only when a Serial Expansion Unit has been selected. It allows to
modify (increase) the Number of equipped lines, this operation is necessary for example if new
port subracks have been added.
See Also:
Control and Timing Subrack: removing a unit

Path (Action-Subrack Management-Delete)
This option is used to decommission a unit of the Control and Timing Subrack. Only Serial
Expansion Units, Timing Selector Oscillator Units and Communication and Q Interface Units can be
decommissioned. A Serial Expansion Unit cannot be decommissioned until all peripheral subracks
(port subracks and matrix subracks) using the serial lines have not been decommissioned.
See Also:
Control and Timing Subrack: displaying inventory data

Path (Action-Inventory Data)
This option is used to display information relevant to the different units of the CT Subrack. The
window shows information about the card identification, the card type, the serial number, the part
number and the revision of the card.
See Also:
Operative States
Control and Timing Subrack: displaying software version

Path (Action-Subrack Software Details)
This option is used to display information relevant to the different units of the CT Subrack. The
window shows information about the card identification, the card type, the active bank, the boot
EPROM code and the code of software loaded into the flash EEPROM Bank 1 or 2.
IMPORTANT A W before the boot EPROM code means Wrong Card Fitted.
See Also:

.
Issue:1
Operative States
Input Ground Contacts: configuring

Path (Action-PAR Unit I/O Contacts-INPUT Contacts Config)
This option is used to configure the 4 input ground contacts (Input Contact #1-pin 37, Input Contact
#2-pin 34, Input Contact #3-pin 35, Input Contact #4-pin 36) of the Parallel Interface Unit, available
for the user.
IMPORTANT To activate this menu, select the Parallel Interface Unit.
To configure input ground contacts:

* Set the input ground contact to Enabled/Disabled.
* Select the Logic of the input ground contact. Possible options are:
ACTIVE LOW
When the contact state is OFF, the alarm criterion is active.
ACTIVE HIGH
When the contact state is ON, the alarm criterion is active.
* Set the Identification of the ground contact. Any alphanumeric string can be set.
* Set the Alarm Priority for the alarm criteria carried by the ground contact.
* Set the Alarm Category for the alarm criteria carried by the ground contact.

.
Issue:1
* Press APPLY.
Use REFRESH to display the current status of each ground contact in the Contact State box.
See Also:
Operative States, Ground Contacts: reading state
Output Ground Contacts: configuring

Path (Action-PAR Unit I/O Contacts-OUTPUT Contacts Config)
This option is used to configure the output ground of the Parallel Interface Unit, available for the
user.
For the "Italy2 Local Alarm Interface" (Equipment Configuration-Node Setup-Set Site Name) only
one output ground contact will be available.
To configure output ground contacts:

* Set the output ground contact to Enabled/Disabled.
* Select the Logic of the output ground contact. Possible options are:
ACTIVE LOW
When the contact state is OFF, the alarm criterion is active.
ACTIVE HIGH
When the contact state is ON, the alarm criterion is active.
* Set the Identification of the ground contact. Any alphanumeric string can be set.
* Press APPLY.
Use REFRESH to display the current status of each ground contact in the Contact State box.
See Also:
Operative States, Output Ground Contacts: switching, Ground Contacts: reading
state

.
Issue:1
Output Ground Contacts: switching

Path (Action-PAR Unit I/O Contacts-OUTPUT Contacts Switch)
This option is used to switch the status of the output ground contacts of the Parallel Interface Unit,
available for the user.
For the "Italy2 Local Alarm Interface" (Equipment Configuration-Node Setup-NE Model Setup)
only one output ground contact will be available.
To switch the status of the output ground contacts:

* Set the Contact State for the chosen output contact.
* Press APPLY.
Use REFRESH to update the status of each ground contact.
See Also:
Operative States, Output Ground Contacts: configuring
Ground Contacts: reading state

Path (Action-PAR Unit I/O Contacts-Contacts Read)
This option is used to display the status and the configuration of the 4 input and 2 output ground
contacts of the Parallel Interface Unit, available for the user.
See Also:
Operative States, Input Ground Contacts: configuring, Output Ground Contacts:
configuring, Output Ground Contacts: switching

.
Issue:1
MATRIX SUBRACK: COMMISSIONING (DXC 4/1)

Path (Equipment Configuration-Subrack Commissioning-Matrix Subrack)
This option is used to equip or to modify the Matrix equipment.
To commission Matrix equipment and to enable the Action menu:

Select the Matrix Subrack equipment.
See Also:
Matrix Subrack: equipping unit (DXC 4/1)

Path (Action-Matrix subrack management-Create)
This option is used to equip the Matrix Subracks. During the commissioning of the Matrix Subrack
the Operator has to indicate its position in the exchange (optional) and the number of pairs of I and
III stage units fitted.
The Control Application selects automatically all the matrix subracks and the Operator can equip all
the I Stage and III Stage or I/III Stage Units that are in the Matrix subracks (Matrix Equipment A and
B).

.
Issue:1
To commission the Matrix Subrack:

* Enter in MATRIX Position the positions of the rack and subrack in the exchange (Row,
Side A/B, Rack and Subrack).
The Serial I/O Line Connection information box reports the serial line (of the Serial Expansion
Unit) used to connect the Matrix Subracks to the Control and Timing equipment. The first serial line
(Line_1) is used to connect the Matrix Subrack A and the second serial line (Line_2) is used to
connect the Matrix Subrack B.
Each Matrix Subrack is connected to the Control and Timing Subrack using two serial lines (Worker
and Protection). In case of faulty of the main line (Worker) the connection is automatically passed
to the other line (Protection) without interruption or malfunctioning of the equipment.
For the correct operation of the equipment verify that the Matrix Subracks have been correctly
connected to the serial lines of the Control and Timing Subrack (refer to Installation).
* Enter in the field Equipped matrix card the number of I Stage/III Stage Units to be
equipped.
Each couple of cards (I Stage and III Stage) allows the connection of up to eight, in case of DXC 4/1
128x128/32x32 or sixteen, in case of DXC 4/1 256x256 equivalent STM-1 signals (matrix
accesses).
Note that for DXC 4/1 512x512 one matrix card houses both I and III Stage then a single card allows
the connection of up to sixteen equivalent STM-1 signals (matrix accesses).
The I Stage Units and the III Stage Units must be fitted into the subrack starting from the left side
and all the units must be adjacent, no empty positions can be left between two units.
Refer To:
Equipment Manual, section 1.4 "Equipment Composition".
The field Free matrix accesses reports the number of matrix accesses that are not yet connected
to any ports subrack.
When installing the matrix for the first time the initial value of this field is set to
16*<n_of_equipped_matrix_cards> for the DXC 4/1 256x256 and DXC 4/1 512x512 equipment and
8*<n_of_equipped_matrix_cards> for the DXC 4/1 128x128/32x32 equipment. This field is useful
when upgrading the equipment to know if it is possible to add new port subracks without adding new
cards.
* Press APPLY.
See Also:
Operative States
Matrix Subrack: displaying information (DXC 4/1)

This option is used to display information on the unit fitted in the Matrix Subracks, the serial lines
used to connect the Matrix Subrack to the Control and Timing Subrack and the matrix accesses
available.
See Also:
Matrix Subrack: equipping unit (DXC 4/1), Operative States

.
Issue:1
Matrix Subrack: modifying configuration (DXC 4/1)

This option is used to modify the operational parameters assigned to the Matrix Subracks. For
example, to add new matrix cards (I Stage Units and III Stage Units) when all the matrix accesses
are used for the port subracks.
The number of accesses can be always increased; to decrease the number it is necessary first to
verify that the accesses are not used.
See Also:
Matrix Subrack: decommissioning (DXC 4/1)

This option is used to decommission the Matrix Subracks.
The Operator can decommission the Matrix Subrack only when all matrix accesses are free (not
used for any port subrack).
See Also:
Matrix Subrack: displaying free accesses (DXC 4/1)

Path (Action-Free Accesses)
This option is used to display the free accesses of each Matrix Subrack.
The number of equipped accesses (# Equipped Acc) and the number of free accesses (# Free
Acc) are displayed at the top of the dialog box.
The operational state of each free matrix access is displayed in the MATRIX FREE ACCESS.
Enabled indicates that the access is equipped and free of alarms, Disabled indicates that the
access is alarmed.
See Also:
Matrix Subrack: displaying accesses status (DXC 4/1), Operative States
Matrix Subrack: displaying accesses status (DXC 4/1)

Path (Action-Accesses Status )
This option is used to display the operational state of the used matrix accesses.
For each matrix access (Access) are indicated the following information:
Operational State
Indicates whether the matrix access is operative (Enabled) or is out-of-service (Disabled).
Configuration State
Indicates whether the matrix access is equipped (Equipped) or not.
Connected Subrack Identifier
Identifier of the port subrack connected to the matrix access.

.
Issue:1
Subrack Access
STM-1 access of the port subrack connected to the matrix access.
See Also:
Matrix Subrack: displaying free accesses (DXC 4/1), Operative States
Matrix Subrack: displaying traffic information (DXC 4/1)

Path (Action-Traffic Information)
This option is used to display the status of the connection between the port subrack and matrix.
For each port subrack connected to the Matrix A and to the Matrix B is indicated the information
relevant to the Matrix Interface Units (A and B), the port units/channels connected to the matrix (or
No Card Connected if no ports are connected to the matrix) and the link status.
See Also:
Operative States
Matrix Subrack: displaying inventory data (DXC 4/1)

This option is used to display information relevant to the different units of the Matrix Subrack. The
window shows information about the card identification, the card type, the serial number, the part
number and the revision of the card.
See Also:
Operative States, Control and Timing Subrack: displaying inventory data
Matrix Subrack: displaying software details (DXC 4/1)

This option is used to display information relevant to the software loaded in to the Matrix Controller
Units present in the Matrix Subrack. The window shows information about the card identification, the
card type, the active bank, the boot EPROM code and the code of software loaded into the flash
EEPROM Bank 1 or 2.
IMPORTANT A W before the boot EPROM code means, if present, Wrong Card Fitted.
See Also:
Operative States

.
Issue:1
TYPE 2 SUBRACK: COMMISSIONING

Path (Equipment Configuration-Subrack Commissioning-TYPE-2 Subrack)
This option is used to equip (or decommission) Type 2 Ports Subracks.
To commission Type 2 Subrack and to enable the Action menu:

Select, in the rack layout, one of the available positions (empty field). This position should represent,
as far as possible, the physical disposition of the subrack.
See Also:
Type 2 Subrack: equipping

Path (Action-Subrack Management-Create)
This option is used to equip a new Type 2 Ports Subrack.
To commission Type 2 Subrack:

* Enter the Subrack Id. This value is used to identify the port subrack. Values are in the
range 01 to 86.
The same value of the Subrack Id must be set on the Identification Unit of the subrack to be
equipped. The value selected for the Subrack Id (using internal pre-settings on the Identification
Unit) is displayed on a front panel display of the Identification Unit.

.
Issue:1
* Enter the positions of the rack and subrack in the exchange (Row, Side A/B, Rack and
Subrack). Side A/B is used to identify the position of the rack for the back-to-back
installation. Subrack identifies the physical position within the rack (1=bottom, 2=middle,
3=top).
* Select the MATRIX ACCESSES used to connect the STM-1 signals outgoing from the
Type 2 Ports Subrack to the Matrix Subrack (two matrix accesses are used).
IMPORTANT The matrix access order must be according to the installation.
* Enter in the SIO Card Id. the Serial Expansion Unit used to connect the port subrack to
the Control and Timing Subrack.
S1A/B
Serial Expansion Unit (Pos. 7) - normal working/protection.
S2A/B
S3A/B
S4A/B
Serial Expansion Unit (Pos. 10) - normal working/protection
(only for DXC 4/1 512x512 and DXC 4/1 256x256).
S5A/B
* Enter in the SIO Line Id. the serial port used for the connection (Line_1 to Line_18).
Before selecting the serial line check that the connection between Control and Timing Subrack and
Type 2 Ports Subrack have been correctly made (refer to Description Installation for more
information on the connections required).
Up to 14 serial lines (Line_5 to Line_18) are available for connection to the Ports Subracks in the
first Serial Expansion Unit (SIO_1). Ups to 18 serial lines (Line_1 to Line_18) are available in the
other Serial Expansion Units (SIO_2 to SIO_5).
* Press APPLY.
See Also:
Operative States, Control and Timing Subrack: equipping, Matrix Subrack:
commissioning (DXC 4/1)
Type 2 Subrack: displaying information

This option is used to display information on the operational state of the Type 2 Ports Subrack
together with serial interfaces and accesses in use.
See Also:
Type 2 Subrack: equipping, Operative States

.
Issue:1
Type 2 Subrack: modifying configuration

This option is used to modify the operational parameters assigned to a Type 2 Ports Subrack. It is
possible to modify:
n the Subrack Position in the telephone exchange;
n the Serial I/O Line Connection;
n the Matrix Accesses (if not cross-connected).
See Also:
Type 2 Subrack: decommissioning

This option is used to decommission a Type 2 Ports Subrack.
A Type 2 Subrack can be decommissioned only when it is in the following

conditions:
a. All cross-connections using the selected port subrack have been removed.
b. All protections using the selected port subrack have been removed.
c. All synchronisation sources using the selected port subrack have been removed.
d. All Tributary Units have been decommissioned.
e. All Tributary Unit Ports have been decommissioned.
f. All performances have been stopped.
See Also:
Type 2 Subrack: displaying matrix accesses map

Path (Action-Matrix Accesses Map)
This option is used to display the map of connections between the matrix subrack and the selected
Type 2 Subrack.
In the two boxes are shown the two STM-1 accesses connecting the matrix subrack to the port
subrack.
Slot num indicates the 63 VC-12 channels available for each STM-1 access.
In the Card Id field are displayed the card connected to the relevant STM-1 channel (or Free slot if
channel is not yet connected).
In the Port Id field are listed the ports involved in the connection (1 to 16).

.
Issue:1
Type 2 Subrack: displaying inventory data

This option is used to display information relevant to the different units of the Type 2 Subrack. The
window shows factory information about the card identification, the card type, the serial number, the
part number and the revision of the card.
See Also:
Type 2 Subrack: displaying software details

This option is used to display information relevant to the SW on the units present in the Type 2 Port
Subrack.
The window shows information about the card identification, the card type, the active bank, the boot
See Also:
Operative States

.
Issue:1

This option is used to equip (or decommission) a Type 3 Ports Subracks.
NOTICE Type 3 Subrack can be managed by DXC 4/1 512x512.

See Also:

This option is used to equip a new Type 3 Port Subrack.

.
Issue:1

* Enter the Subrack Id. This value is used to identify the port subrack.
This Id number must be already configured on the Identification Unit (by hardware settings). The O
has to insert the same number in this field.
* Enter the positions of the subrack in the exchange (Row, Side A/B, Rack and Subrack).
Side A/B is used to identify the position of the rack in the back-to-back installation.
Subrack identifies the physical position within the rack (1=bottom, 2=middle, 3=top).
* Specify the Matrix Accesses used by this Port Equipment for transmitting internal data
streams from ports to matrices and vice-versa.
The MATRIX ACCESSES field is a schematic representation of the port subrack connection area
with the relevant data cable connector physical co-ordinates (Y01, YO2, YO3, Y04 - Matrix
Accesses).
The Matrix Accesses field shall specify the physical Matrix Accesses (connectors on the rear side
of the matrix) where the eight internal data streams of the Port Subrack are connected. In the DXC
4/1 each cable carry two of the eight internal data streams.
Under the assigned matrix accesses are indicate the relevant internal data streams (the notation Px
has to be intended as the AUG-1 stream necessary to carry the traffic managed by the unit in
position Px).
* Enter in the SIO Card Id. field the Serial Expansion Unit used to connect the port subrack
to the Control and Timing Subrack.
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
* Enter in the SIO Line Id. field the serial port used for the connection (Line_1 to Line_18).
first Serial Expansion Unit (SIO_1). Up to 18 serial lines (Line_1 to Line_18) are available in the
* Use V4 Fail A/B to enable/disable the detection of the V4-FAIL_A/B alarm relevant to
each connected channel. This facility is useful to perform a detailed diagnostic operation.

.
Issue:1
In case of one matrix defect, the related "Matrix A Fail" or "Matrix B Fail" alarms will be
shown but to check which is/are the channel/s effectively failed the options V4 Fail A/B
can be enabled; the "V4 Channel Fail A" or "V4 Channel Fail B" alarms, related to the
corresponding failed channel, will arise.
Refer To:
* Press APPLY.
The MIUMx WIRING SCHEME push button allows accessing a window that displays the
relationship among the Matrix Interface Unit accesses, the physical cable connectors from and to
the matrix and the internal channels associated to the traffic units.
Refer To:
Equipment Manual, section 2.3 "Electrical Connection".
See Also:
Operative States, Control and Timing Subrack: equipping, Fault Detection Procedure,
Matrix Subrack: commissioning (DXC 4/1)

See Also:

possible to modify:
n the Matrix Accesses (if not cross-connected);
n the detection state of the V4 Fail A/B alarms;
See Also:

.
Issue:1


conditions:
See Also:

See Also:

Subrack.
See Also:
Operative States

.
Issue:1


See Also:


range 01 to 86.
equipped. The value selected for the Subrack Id (using internal pre-settings on the Identification
Unit) is displayed on a front panel display of the Identification Unit.

.
Issue:1
installation. Subrack identifies the physical position within the rack (1=bottom, 2=middle,
3=top).
* Select the MATRIX ACCESSES used to connect the STM-1 signals outgoing from the
Type 4 Ports Subrack to the Matrix Subrack (two matrix accesses are used).
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
* Press APPLY.
See Also:
commissioning (DXC 4/1)

See Also:

.
Issue:1

possible to modify:
See Also:


conditions:
See Also:
Type 4 Subrack: displaying matrix accesses map

Path (Action-Matrix Accesses Map)
This option is used to display the map of connections between the matrix subrack and the selected
Type 2 Subrack.
In the two boxes are shown the two STM-1 accesses connecting the matrix subrack to the port
subrack.
Slot num indicates the 63 VC-12 channels available for each STM-1 access.
In the Card Id field are displayed the card connected to the relevant STM-1 channel (or Free slot if
channel is not yet connected).
In the Port Id field are listed the ports involved in the connection (1 to 16).

.
Issue:1

See Also:

Subrack.
See Also:
Operative States

.
Issue:1

This option is used to equip (or decommission) Type 5 Port Subracks.
To commission a Type 5 Subrack and to enable the Action menu:

See Also:

This option is used to equip a new Type 5 Port Subrack and to specify the matrix accesses used for
the connection to the Matrix Subracks.
Make sure that the Operator has previously provisioned the matrix accesses for the port subrack
going to be equipped.

range 01 to 86.

.
Issue:1
equipped. The value selected for the Subrack Id (using internal hardware settings on the
Identification Unit) is displayed on a front panel of the Identification Unit itself.
installation (optional). Subrack identifies the physical position within the rack (1=bottom,
2=middle, 3=top).
* Specify the MATRIX ACCESSES used by the Port Equipment for transmitting internal
data from ports to matrices and vice-versa.
The maximum number of displayed matrix accesses corresponds to the number previously
assigned while equipping the Matrix Subracks.
In the MATRIX ACCESSES box, the matrix accesses used to connect the eight internal channels
(STM-1 Port 1/2 to STM-1 Port 7/8) of the Port Subrack must be specified.
For the DXC 4/1 the STM-1 ports are grouped into four couples (1/2, 3/4, 5/6 and 7/8) as they are
wired during the installation. For each pair of ports the relevant matrix accesses must be specified
(e.g.: STM-1 Port 1/2 <--> MX_acc_1/2).
For the DXC 4/4 512x512 the STM-1 ports are grouped into two groups of ports. Each couple of
port subrack connectors (STM-1 Port 1/2 STM-Port 5/6 and STM-1 Port 3/4 STM-Port 7/8)
manages four different internal channels.
Before selecting the matrix accesses check that the connections have been correctly made between
Matrix Subrack and Type 5 Ports Subrack (refer to Description Installation for more information on
the connections required).
* Enter in the SIO Card Id the Serial Expansion Unit used to connect the port subrack to
the Control & Timing Subrack.
S1A/B
S2A/B
S3A/B
S4A/B
(only for DXC 4/1 512x512, DXC 4/1 256x256, DXC 4/4 512x512 and DXC 4/4 1024x1024).
S5A/B

.
Issue:1
* Press APPLY.
See Also:
commissioning (DXC 4/1), General Index

See Also:

possible to modify:
See Also:


conditions:
d. All 155Mbit/s Tributary Units and 140Mbit/s Tributary Units have been decommissioned.
See Also:

.
Issue:1

See Also:

Subrack.
See Also:
Operative States

.
Issue:1

This option is used to equip (or decommission) a Type 6 Ports Subracks.

See Also:

This option is used to equip a new Type 6 Port Subrack.
* Specify the matrix accesses configuration for the subrack selecting the proper choice in
the Scheme Selection field.
Subrack 6 supports two standard configurations, listed below, for MSP and Card Protections:
All Accesses
Subrack equipped with 16 matrix accesses.
This kind of configuration is optimized for:
- 8 traffic units with a equivalent capacity of 2 STM-1 each one (2xSTM-1 Opt) MSP 1:N protected.
- 4 traffic units with a equivalent capacity of 4 STM-1 each one (eg.: 4xSTM-1 El., 4x140/155Mbit/s
or STM-4) 1:N protected (MSP or Card Protection supported).
Half Accesses
Subrack equipped with 8 matrix accesses.
This kind of configuration is optimized for:
- 4 traffic units with a equivalent capacity of 2 STM-1 each one (2xSTM-1 Opt) MSP 1+1 protected.
- 2 traffic units with a equivalent capacity of 4 STM-1 each one (e.g.: 4xSTM-1 El.,
4x140/155Mbit/s or STM-4) MSP 1:1 protected.

.
Issue:1
DXC 4/1
DXC 4/4
.

.
Issue:1

This Id number must be already configured on the Identification Unit (by hardware settings). The
operator must insert the same number in this field.
The MATRIX A (MATRIX A MASTER/SLAVE for DXC 4/4) field is a schematic representation of
the port subrack connection area with the relevant data cable connector physical co-ordinates (Y01,
YO2, YO3, Y04 - MAA = Matrix Accesses A, MAB = Matrix Accesses B, MAC = Matrix Accesses C,
MAD = Matrix Accesses D).
of the matrix) where the sixteen internal data streams of the Port Subrack are connected. In the
DXC 4/1 each cable carry two of the sixteen internal data streams (from AUG-1 Port 1/2 to AUG-4
Port 3/4 stream), while in the DXC 4/4 each cable carry four halves of the sixteen internal data
streams, sixteen halves to/from Master Matrix and sixteen halves to/from Slave Matrix (from AUG-
1/2 Port 1/2 to AUG-3/4 Port 3/4 stream). For DXC 4/4 the MATRIX A SLAVE field has to be
intended as a copy of the MATRIX A MASTER field (MAC Accesses correspond to MAA accesses
and MAD Accesses correspond to MAB Accesses).
Under the assigned matrix accesses are indicate the relevant internal data streams.

.
Issue:1
NOTICE If the MSP 1+1 architecture is required the protection units accesses (MAC and
MAD Accesses for DXC 4/1, MAB and MAD Accesses for DXC 4/4) must not
be equipped.
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
* Specify the Port Controller Version used in the subrack.
CP Card Version 67
This Port Controller has to be used only on Subrack Type 6/7.
CP Card Version E
This Port Controller can be used on Subrack Type 6/7/6E/7E.
* Define, as far as the NxSTM-1 Units is concern, the protection type managed by the
subrack (Prot. Type Supp. - Protection Type Supported).
In particular the meaning of the three selectable choice is:
MSP (no 2XSTM1 MSP 1:N)
This selection is applied to the whole subrack and allows to create MS protection schemes with the
exception of 2xSTM-1 MSP 1:N. Equipping the subrack with 2xSTM-1 units, slot 5 can be used for

.
Issue:1
traffic or 1+1 MSP protection only (unit fitted in the physical slot 7b), no 2xSTM-1 MSP 1:N can be
created.
Card Protection
This selection is applied to the whole subrack and allows to create a card protection scheme. No
N:1 MSP protection can be configured. Choosing this item make sure to use the proper card
protection modules.
MSP (2XSTM1 MSP 1:N only)
This selection is applied to the whole subrack and allows to create 2xSTM-1 MSP 1:N protection
scheme. Equipping the subrack with 2xSTM-1 units, slot 5 can be used for protection only (unit
fitted in the physical slot 7a). No STM-4, 4xSTM-1 or 4x140-155Mbit/s Units can be equipped in
position 6.
Refer To:
* Press APPLY.
Refer To:
See Also:
Matrix Subrack: commissioning (DXC 4/1), General Index

See Also:

possible to modify:
n the MSP protection supported.
NOTICE It is possible to modify the Prot. Type Supp. only if it has been defined as MSP
(no 2XSTM1 MSP 1:N or 2XSTM1 MSP 1:N only) and if the new value to set is

.
Issue:1
a MSP protection as well. It is not possible to modify Prot. Type Supp. from
MSP to Card Protection and vice-versa without deleting the whole subrack.
The transition between the two protection is allowed if:
From no 2XSTM1 MSP 1:N to 2XSTM1 MSP 1:N only

The modification is accepted unless card P5 is equipped as 2xSTM-1 or card P6 as 4xSTM-1 (of
any type) or STM-4 (of any type). Moreover if some MSP 1+1 is configured the command is
refused.
From 2XSTM1 MSP 1:N only to no 2XSTM1 MSP 1:N
The modification is accepted unless card P5 is equipped as 2xSTM-1.
See Also:


conditions:
See Also:

See Also:

Subrack.

.
Issue:1

.
Issue:1
See Also:
Operative States
TYPE 6E SUBRACK: COMMISSIONING

Path (Equipment Configuration-Subrack Commissioning-TYPE-6E Subrack)
This option is used to equip (or decommission) a Type 6E Ports Subracks.
NOTICE Type 6E Subrack can be managed by DXC 4/1 512x512 and DXC 4/4
1024x1024 only.
To commission Type 6E Subrack and to enable the Action menu:

See Also:
Type 6E Subrack: equipping

This option is used to equip a new Type 6E Port Subrack.
Subrack 6E supports a number of configurations, listed below, for MSP and Card Protections:
40 Access
Subrack equipped with 40 matrix accesses (maximum capacity managed by the subrack). This
kind of configuration is optimized for 10 traffic units with a equivalent capacity of 4 STM-1 each one
(eg.: 4xSTM-1 El./Opt or STM-4) not protected (no MSP or Card Protection supported).

.
Issue:1
20 Access
Subrack equipped with 20 matrix accesses. This kind of configuration is optimized for 10 traffic
units with a equivalent capacity of 2 STM-1 each one (eg.: 2xSTM-1 Opt) not MSP protected.
32 Access
Subrack equipped with 32 matrix accesses. This kind of configuration is optimized for 8 traffic units
with a equivalent capacity of 4 STM-1 each one (eg.: 4xSTM-1 El./Opt or STM-4) 1:N protected
(MSP or Card Protection supported).
16 Access
with a equivalent capacity of 2 STM-1 each one (i.e.: 2xSTM-1 Opt) 1:N MSP protected.
20 MSP Access
Subrack equipped with 20 matrix accesses (DXC 4/1 only). This kind of configuration is optimized
for 5 traffic units with a equivalent capacity of 4 STM-1 each one (i.e.: 4xSTM-1 El./Opt or STM-4)
1+1 MSP protected.
10 MSP Access
Subrack equipped with 10 matrix accesses (DXC 4/1 only). This kind of configuration is optimized
for 5 traffic units with a equivalent capacity of 2 STM-1 each one (i.e.: 2xSTM-1 Opt) 1+1 MSP
protected.
* Define the first Free matrix accesses used to equip the subrack.
* Press APPLY.
IMPORTANT It is possible to specify configurations different from those proposed in the

Scheme Selection window.
The previous configurations are used to help the Operator in the first
commissioning of the subrack but they are not fixed. It is possible to modify the
matrix accesses scheme specified setting the proper fields in the next window.
Note that Type 6E subrack must have at least 2 matrix access equipped

.
Issue:1
For DXC 4/1 the following window will be displayed:

.
Issue:1
To commission Type 6E Subrack:

This Id number must be configured on the Identification Unit (by hardware settings). The operator
must insert the same number in this field.
* It possible to specify in a Subrack Distance field two possible values:
Near
cable length = < 50m
Far
50 < cable length < 100m
Its default value is Near. It shall be possible to change in any moment this parameter selecting
Subrack Configuration - Modify.
IMPORTANT If you change the distance parameter during the normal traffic operation you will
cause the total traffic loss for the involved subrack.
* Starting from the Free matrix accesses previously specified the system proposes a
matrix access order used by this Port Equipment for transmitting internal data streams
from ports to matrices and vice-versa. However it is possible to modify this order using
the relevant arrow buttons.
NOTICE Depending on the subrack scheme selected some matrix accesses could not be
defined because unnecessary for the traffic management.
The Matrix Accesses field is a schematic representation of the port subrack connection area with
the relevant data cable connector physical co-ordinates (Y01->Y16 IM1 = I/F Module 1, IM2 = I/F
Module 2, IM3 = I/F Module 3).
of the matrix) where the internal data streams of the Port Subrack are connected. In the DXC 4/1
each cable carry two of the internal data streams (from AUG-1/2 Port 1 to AUG-3/4 Port 10 stream),
while in the DXC 4/4 each cable carry four halves of the internal data streams, four halves to/from
Master Matrix and four halves to/from Slave Matrix (from AUG-1/2 Port 1/2 to AUG-3/4 Port 9/10
stream).
Under the assigned matrix accesses are indicated the relevant internal data streams.

.
Issue:1
If the MSP or Card Protection architecture is required the protection units accesses must not be
equipped.
Refer To:
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B

.
Issue:1
Type 6E Ports Subrack have been correctly made (refer to Description Installation for more
* Define if the subrack is equipped with the Environmental Cooling Units (Heat
Dissipation) or not.
* Press APPLY.
Note For this Subrack only the Port Controller E can be used.
Refer To:
See Also:
Type 6E Subrack: displaying information

This option is used to display information on the operational state of the Type 6E Ports Subrack
See Also:
Type 6E Subrack: equipping, Operative States
Type 6E Subrack: modifying configuration

This option is used to modify the operational parameters assigned to a Type 6E Ports Subrack. It is
possible to modify:
n the Matrix Accesses (if they are not assigned to an equipped card);

.
Issue:1
See Also:
Type 6E Subrack: decommissioning

This option is used to decommission a Type 6E Ports Subrack.
A Type 6E Subrack can be decommissioned only when it is in the following

conditions:
See Also:
Type 6E Subrack: displaying inventory data

This option is used to display information relevant to the different units of the Type 6E Subrack. The
See Also:
Type 6E Subrack: displaying software details

This option is used to display information relevant to the SW on the units present in the Type 6E
Port Subrack.
See Also:
Operative States

.
Issue:1


See Also:

Subrack 7 supports two standard configurations, listed below, for MSP and Card Protections:
All Accesses
with a equivalent capacity of 16 STM-1 each one not protected.
Half Accesses
with a equivalent capacity of 16 STM-1 MSP 1+1 protected.

.
Issue:1
D X C 4 /1
D X C 4 /4

.
Issue:1

The MATRIX A field is a schematic representation of the port subrack connection area with the
relevant data cable connector physical co-ordinates (Y01, YO2, YO3, Y04 - MAA = Matrix Accesses
A, MAB = Matrix Accesses B, etc.).
of the matrix) where the thirty-two internal data streams of the Port Subrack are connected.
In the DXC 4/1 each cable carry two of the thirty-two internal data streams (from AUG-1/2 Port 1 to
AUG-15/16 Port 2 stream), while in the DXC 4/4 each cable carry four halves of the thirty-two
internal data streams, thirty-two halves to/from Master Matrix and thirty-two halves to/from Slave
Matrix (from AUG-1/2/3/4 Port 1 to AUG-13/14/15/16 Port 2 stream). For DXC 4/4 the MATRIX A
SLAVE field has to be intended as a copy of the MATRIX A MASTER field (the correspondences
among the accesses are: MAC Accesses <-> MAA accesses, MAD Accesses <-> MAB Accesses,
MAG Accesses <-> MAE Accesses and MAH Accesses <-> MAF Accesses).
Under the assigned matrix accesses are indicate the relevant internal data streams.
NOTICE If the MSP 1+1 architecture is required the protection unit accesses (MAC, MAD,
MAG and MAH Accesses) must not be equipped.

.
Issue:1
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
* Use V4 Fail A/B to enable/disable the detection of the VA-FAIL_A/B alarm relevant to
* Specify the Port Controller Version used in the subrack.
CP Card Version 67
This Port Controller has to be used only on Subrack Type 6/7.
CP Card Version E
This Port Controller can be used on Subrack Type 6/7/6E/7E.
* Press APPLY.
The MIUMx WIRING SCHEME push button allows to access a window that displays the relationship
among the Matrix Interface Unit accesses, the physical cable connectors from and to the matrix, and
the internal channels associated to the traffic units.
Refer To:

.
Issue:1
See Also:

See Also:

possible to modify:
n the detection state of the V4 Fail A/B alarms.
See Also:


conditions:
See Also:

.
Issue:1

See Also:

Subrack.
See Also:
Operative States

.
Issue:1
TYPE 7E SUBRACK: COMMISSIONING

Path (Equipment Configuration-Subrack Commissioning-TYPE-7E Subrack)
This option is used to equip (or decommission) a Type 7E Ports Subracks.
NOTICE Type 7E Subrack can be managed by DXC 4/1 512x512 and DXC 4/4
1024x1024 only.
To commission Type 7E Subrack and to enable the Action menu:

See Also:

This option is used to equip a new Type 7E Port Subrack.
Next list reports a number of standard configurations for Subrack 7E:
80 Access
Subrack equipped with 80 matrix accesses (maximum capacity managed by the subrack). This
kind of configuration is optimized for 5 traffic units with a equivalent capacity of 16 STM-1 each
one.
64 Access
with a equivalent capacity of 16 STM-1 each one. The slot in position number five will be the
protecting unit.

.
Issue:1
48 Access
with a equivalent capacity of 16 STM-1 each one. This Subrack is optimized for 1+1 MSP
protection on STM-16 interfaces plus an extra STM-16 not protected.
* Define the first Free matrix accesses used to equip the subrack.
* Press APPLY
IMPORTANT It is possible to specify configurations different from those proposed in the

Scheme Selection window.
The previous configurations are used to help the Operator in the first
commissioning of the subrack but they are not fixed. It is possible to modify the
matrix accesses scheme specified setting the proper fields in the next window.
Note that a slot must have 0 or 16 matrix accesses equipped.
Type 7E Subrack can not have 0 matrix accesses, it has to have at least 16
matrix accesses equipped.

.
Issue:1

.
Issue:1
To commission Type 7E Subrack:

* It possible to specify in a Subrack Distance field two possible values:
Near
cable length = < 50m
Far
50 <cable length < 100m
Its default value is Near. It shall be possible to change in any moment this parameter selecting
Subrack Configuration - Modify.
NOTICE If you change the distance parametr during the normal traffic operation you will
cause the total traffic loss for the involved subrack.
* Starting from the Free matrix accesses previously specified the system proposes a
matrix access order used by this Port Equipment for transmitting internal data streams
from ports to matrices and vice-versa. However it is possible to modify this order using
the relevant arrow buttons.
NOTICE Depending on the subrack scheme selected, in some slot, all matrix accesses
could not be defined because unnecessary for the port management.
The Matrix Accesses field is a schematic representation of the port subrack connection area with
the relevant data cable connector physical co-ordinates (Y01->Y16 IM1 = I/F Module 1, IM2 = I/F
Module 2, IM3 = I/F Module 3, IM4 = I/F Module 4, IM5 = I/F Module 5).
of the matrix) where the internal data streams of the Port Subrack are connected. In the DXC 4/1
each cable carry two of the internal data streams (from AUG-1/2 Port 1 to AUG-3/4 Port 10 stream),
while in the DXC 4/4 each cable carry four halves of the internal data streams (from AUG-1/2 Port
1/2 to AUG-15/16 Port 4/5 stream).
Under the assigned matrix accesses are indicated the relevant internal data streams.

.
Issue:1
Connection Area
Connection Unit
IM1 IM2 IM3 IM4 IM5
Y01
Y02
Y03
Y04
Y05
Y06
Y07
Y08
Y09
Y10
Y11
Y12
Y13
Y14
Y15
Y16
To Matrix
From Matrix
Refer To:
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
Type 7E Ports Subrack have been correctly made (refer to Description Installation for more

.
Issue:1
* Press APPLY.
Note For this Subrack only the Port Controller E can be used.
Refer To:
See Also:
Type 7E Subrack: displaying information

This option is used to display information on the operational state of the Type 7E Ports Subrack
See Also:
Type 7E Subrack: modifying configuration

This option is used to modify the operational parameters assigned to a Type 7E Ports Subrack. It is
possible to modify:
n the Matrix Accesses (if no one card is equipped in the slot that used those matrix
accesses);
See Also:

.
Issue:1
Type 7E Subrack: decommissioning

This option is used to decommission a Type 7E Ports Subrack.
A Type 7E Subrack can be decommissioned only when it is in the following

conditions:
See Also:
Type 7E Subrack: displaying inventory data

This option is used to display information relevant to the different units of the Type 7ESubrack. The
See Also:
Type 7E Subrack: displaying software details

This option is used to display information relevant to the SW on the units present in the Type 7E
Port Subrack.
See Also:
Operative States

.
Issue:1
BOOSTER SUBRACK: COMMISSIONING

Path (Equipment Configuration-Subrack Commissioning-Booster Subrack)
This option is used to equip (or decommission) Booster Subracks.
IMPORTANT Type 6E Subrack can be managed by DXC 4/1 512x512 and DXC 4/4
1024x1024 only.
To commission a Booster Subrack and to enable the Action menu:

See Also:
Booster Subrack: equipping

This option is used to equip a new Booster Subrack.
To commission a Booster Subrack:

range 01 to 86.
equipped. The value selected for the Subrack Id (using internal hardware settings on the
Identification Unit) is displayed on a front panel of the Identification Unit itself.
installation (optional). Subrack identifies the physical position within the rack (1=bottom,
2=middle, 3=top).
* Enter in the SIO Card Id the Serial Expansion Unit used to connect the port subrack to
the Control & Timing Subrack.

.
Issue:1
S1A/B
S2A/B
S3A/B
S4A/B
S5A/B
Booster Subrack have been correctly made (refer to Description Installation for more information on
the connections required).
* Press APPLY.
See Also:
Operative States, Control and Timing Subrack: equipping, General Index
Booster Subrack: displaying information

This option is used to display information on the operational state of the Booster Subrack together
with serial interfaces in use.
See Also:
Booster Subrack: equipping, Operative States
Booster Subrack: modifying configuration

This option is used to modify the operational parameters assigned to a Booster Subrack. It is
possible to modify:
n the Serial I/O Line Connection.
See Also:
Booster Subrack: decommissioning

This option is used to decommission a Booster Subrack.

.
Issue:1
A Booster Subrack can be decommissioned only when it is in the following

conditions:
n All Booster Units have been decommissioned.
See Also:
See Also:
Operative States
Booster Subrack: displaying inventory data

This option is used to display information relevant to the different units of the Booster Subrack. The
See Also:
Booster Subrack: displaying software details

This option is used to display information relevant to the SW on the units present in Booster. The
window shows information about the card identification, the card type, the active bank, the boot
See Also:
Operative States
UNIT: COMMISSIONING
Path (Equipment Configuration-Card Commissioning)
This option is used for managing the units of Matrix Subracks and Port Subracks.
To enable the Action menu:

* Select the subrack.
* Select the slot.
See Also:
Unit: equipping (DXC 4/1)

Path (Action-Card Management-Create)
Procedure described in the following indicates how a unit can be equipped into the Ports Subracks.
The following units can be equipped (or unequipped):

.
Issue:1
In Type 2 Subrack:
n 16x2Mbit/s Tributary Unit
n 16x2Mbit/s Tributary Unit (G.703/G.704)
n 16x2Mbit/s Tributary Unit Type 2
n 16x2Mbit/s Tributary Unit Type 2 (G.703/G.704)
n 3x34Mbit/s Tributary (async.) Unit
n 4x34Mbit/s Video Codec Tributary Unit
Note The 4x34Mbit/s Video Codec and 3x34/45Mbit/s Tributary Units can be equipped in
slots 1, 2 and 5, 6 only (slots 2 and 6 are used for protection).
In Type 3 Subrack:
n 63x2Mbit/s Tributary Unit
n 4x34Mbit/s Tributary (T-Mux) Unit
Note The 63x2Mbit/s Tributary Units can be equipped in slots 1, 4 and 7, 10 only (slot 6 is
used for protection). The 4x34Mbit/s T-Mux, 3x34Mbit/s and 3x45Mbit/s Tributary
Units can be equipped in all the slots (slots 5 and 6 are used for protection).
In Type 4 Subrack:
n 1x45Mbit/s Tributary (T-Mux) Unit
NoteThe units equipped in the even slots are used for protection.
In Type 5 Subrack:
n STM-1 G.703 Electrical Mux Unit
n STM-1 G.703 Electrical Mux Unit (Type 2)
n Optic/Mux Unit Standard Type
n Optic/Mux Unit Type 2
n 140Mbit/s Tributary (G.703) Unit
n 140Mbit/s Tributary (T-Mux) Unit

.
Issue:1
In Type 6 Subrack:
n STM-4 Optic/Mux Unit
n 2xSTM-1 Optic/Mux Unit
n 4xSTM-1/140Mbit/s Electric/Mux Unit
n 4xSTM-1 Electric/Mux Unit
Note STM-4 Optic/Mux Unit, 4xSTM-1/140 and 4xSTM-1 Electric/Mux Units can be
equipped in slots 1, 3, 5, 6 and 8 (slot 5 is used for protection). 2xSTM-1 Optic/Mux
Units can be equipped in all the slots. Remind that for each couple of slot (starting
from the slot 1) only a capacity of four equivalent STM-1 is available, then it is not
possible, for example, equip an STM-4 unit in slot 1 and a 2xSTM-1 unit in slot 2,
because a capacity of six equivalent STM-1 should be necessary.
In Type 6E Subrack:
n STM-4 Optic/Mux Unit Type 2
n 2xSTM-1 Optic/Mux Unit Type 3
n 4xSTM-1/140Mbit/s Electric/Mux Unit
n 4xSTM-1 Electric/Mux Unit Type 3
n Optical Amplifier Unit (Booster)
n Optical Preamplifier Unit
n 2 ch. Bidirectional WDM Mux/Demux (East/West)
Note Units have to be equipped according to the selected matrix accesses scheme.
In Type 7 Subrack:
n Auxiliary Unit
In Type 7E Subrack:
In Type Booster Subrack:
All other units are equipped by default since they are necessary for the operation of the equipment.
IMPORTANT The 140Mbit/s Tributary (T-Mux) Unit Type 2 (code: 131-7678/02) can be
configured either as 140Mbit/s Tributary (G.703) Unit or as 140Mbit/s Tributary
(T-Mux) Unit.

.
Issue:1
To commission a card:
* Use CARD Type to select the type of unit to be commissioned.
For a Port Subrack the following cards are displayed:
2MB 16x2Mbit/s Tributary Unit
2MB-T2 16x2Mbit/s Tributary Unit Type 2
63x2Mb 63x2Mbit/s Tributary Unit
4x34-VC 4x34Mbit/s Video Codec Tributary Unit
34/45MB 3x34Mbit/s or 3x45Mbit/s Tributary Unit
3x34MB 3x34Mbit/s Tributary Unit
3x45MB 3x45Mbit/s Tributary Unit
TMUX-4x34 Transmux 4x34Mbit/s Tributary Unit
TMUX-45 Transmux 45Mb/s Tributary Unit
TMUX140 Transmux 140Mb/s Tributary Unit
140Mb 140Mbit/s Tributary Unit
STM1-El Electric/Mux Unit
STM1-Opt Optic/Mux Unit
2XSTM1-Opt Optic/Mux Unit
4xSTM1-El Electric/Mux Unit
4xSTM1-140 Electric/Mux Unit
Optical Amplifier Unit (Booster)

.
Issue:1
Optical Preamplifier Unit

2 ch. Bidirectional WDM Mux/Demux (East/West)
* Use Card Version to select the type of card. The selection must be performed according
to the selected card type (previos step)
STM1 El
Standard Type
STM-1 G.703 Electrical Mux Unit, HW code 131-7230/02
STM-1 Type 2
STM-1 G.703 Electrical Mux Unit Type 2, HW code 131-7230/03
STM-1 Opt
Standard Type
Optic/Mux Unit, HW code 131-6786/**
STM1-Type 2
TMUX140
Transmux 140Mb/s Tributary Unit, HW code 131-7678/02
140Mb
140Mbit/s Tributary Unit, HW code 131-7677/01
TMUX-45
Transmux 45Mbit/s Tributary Unit, HW code 131-9593/01
TMUX-4x34
Transmux 4x34Mbit/s Tributary Unit, HW code 131-2126/01
63x2Mb
63x2Mbit/s Tributary Unit, HW code 131-8120/01
2MB
Standard Type
16x2Mbit/s Tributary Unit, HW code 131-6788/02
CRC-4 Type
16x2Mbit/s Tributary Unit (G.703/G.704) HW code 131-8923/01
2MB-T2
Standard Type
16x2Mbit/s Tributary Unit Type 2, HW code 131-9124/01

.
Issue:1
CRC-4 Type
16x2Mbit/s Tributary Unit (G.703/G.704) HW code 131-9124/02
34/45MB
Standard Type
3x34Mbit/s Tributary (async.) Unit, HW code 131-7636/02
45Mb
Note These two units are intended to be used in Type 2 Subrack.
3x34MB
3x45MB
4x34-VC
4x34Mbit/s Video Codec Tributary Unit, HW code 131-8741/01
STM4-Opt
Standard Type
STM4 Type 2
2XSTM1-Opt
NxSTM1 Type 3
4xSTM1-El
Standard Type
Electric/Mux Unit, HW code 131-9547/01
NxSTM1 Type 3
4xSTM1-140

.
Issue:1
STM16-Opt
Standard Type
T2 Type LPOM (Grey)
ST Type WDM (Grey Selected)
ST Type DWDM (Coloured)
MUX-4/3 (Grey)
Optic/Mux Unit, HW code 151-2223/07
Boost
Optical Amplifier Unit, Booster HW code 131-9117/**
PreAmpl
Optical Preamplifier Unit, Preamplifier HW code 131-9705/**
Filter
2 ch WDM Bid Mux/Demux (East), HW code 131-9542/**
2 ch WDM Bid Mux/Demux (West), HW code 131-9543/**
* Press APPLY.
See Also:
Multiplexing Section Protection: configuring
Refer To:
Equipment Description, section "Equipment Composition"

.
Issue:1
Auxiliary Unit: equipping

Path (Action-Card Management-Create)
Procedure described in the following indicates how an Auxiliary Unit can be equipped into the Ports
Subracks.
Note Auxiliary Unit can be equipped in the Type 7 Port Subrack only.
To commission an Auxiliary Unit:

* Type in the PHONE NUMBER text box the phone number to be assigned.
* Press APPLY.
See Also:
Auxiliary Unit Connection: managing
Unit: displaying information

Path (Action-Card Management-Read)
This option is used to display information on the operational state of the units present in the Port
Subracks and Matrix Subrack.
See Also:
Unit: equipping (DXC 4/1), Operative States
Unit: modifying configuration

Path (Action-Card Management-Modify)
This option is used to modify the Card Type and Version for a selected port unit.
IMPORTANT The Card Type menu is available only if You are logged in as Supervisor.
Note If you choose a MUX 4/3 you can not change the card version. You must delete it and
then create the new one.
See Also:

.
Issue:1
Unit: decommissioning
Path (Action-Card Management-Delete)
Procedure described in the following indicates how to decommission tributary units belonging to the
Port Subracks.
All the other units cannot be decommissioned since they are necessary for the operation of the
equipment.
A Tributary Unit can be decommissioned only when it is in the following

conditions:
n All cross-connections using the selected tributary unit have been removed.
n All protections using the selected tributary unit have been removed.
n The selected unit is not used as buffer unit for the protection of the left one (only for
16x2Mbit unit in the DXC 4/1).
n All synchronisation sources using the selected tributary unit have been removed.
n All ports have been deleted.
See Also:
Unit: resetting
Path (Action-Reset)
This option is used to reset a card. The command causes a reprogramming of the unit.
NOTICE A reset of the port units causes a short interruption of the traffic.
The following units can be reset:

n All units of the port subracks with the exception of the Identification Unit and Power Supply
Units.
n Serial Expansion Units, Communication Units, Timing Selector of Control and Timing
Subrack.
n Matrix Controller Unit of Matrix Subrack.

.
Issue:1
PORT: CONFIGURATION
Path (Equipment Configuration-Port Configuration)
This option is used to configure the ports specifying the operational parameters (e.g. error ratio,
signal type). This operation must be carried out after the commissioning of the cards (port units) in
order to make them available for the cross-connections. The port configuration enables the network
alarms detection.

* Select the port subrack containing the unit to be configured.
* Select the Tributary Unit to be configured.
* Select the port to be configured.
* Define the ports selection criteria by clicking on the exclusive buttons SINGLE or
MULTIPLE in the Selection Mode field. MULTIPLE selection allows to select (and
configure) more than one port at the same time, SINGLE allows to select only one port.
Note This facility is available for the 63x2Mbit/s Units only.
In case of multiple selection all the selected ports will be configured with the same operational
parameter.
The option ALL, available in the Port Selection box, allows to configure all the ports of the unit in the
same way (only for 16x2Mbit/s, 3x34Mbit/s, 3x45Mbit/s, 4x34Mbit/s Videocodec - belonging to DXC
4/1 -, 4xSTM1/140Mb and NxSTM-1 Units).

.
Issue:1
* Use Jn I/O mode to select the format for the configuration of the J0 byte (section trace)
and the J1 byte (path trace). The possible formats are ASCII and HEX. Using the ASCII
format it is possible to insert the path trace as an alphanumeric sequence.
* In case a 4xSTM1/140Mb Unit has been chosen, define if the selected port has to be
configured as STM-1 or 140Mbit/s port by checking the Port Mode exclusive buttons.
Note After having configured a 4xSTM1/140Mb port, to change the Port Mode it is
necessary remove the whole port configuration.
Port: configuring operational parameter

Path (Action-Port Management-Create)
Use this option to create a new port (2Mbit/s, 34-45Mbit/s, 4x34Mbit/s Videocodec, 140Mbit/s,
140Mb T-Mux, STM-1, STM-4 or STM-16) assigning the relevant operational parameters.
STM-16 Port (MUX 4/3)
This option is relevnt to STM-16 MUX 4/3.
* Use Protocol Mode to choose which multiplexing path will be manage by the card
(SONET AU-3 management; SDH AU-4 management).
Note This facilities is related to STM-16 MUX 4/3 only.
* Set the Port Mode Value.
* Use AIS on RS-TIM to enable/disable the downstream injection of AIS indication to the
Matrix when a Trace Identifier Mismatch has been detected.
* Use RDI on RS-TIM to enable/disable the MS-RDI indication to the line when a Trace
Identifier Mismatch has been detected.

.
Issue:1
* Use AIS on MS-EXC to enable/disable the downstream injection of AIS indication to the
Matrix when an excessive bit error rate (>10-3) is detected on the bytes B2.
* Use RDI on MS-EXC to enable/disable the MS-RDI indication to the line when an
excessive bit error ratio (>10-3) is detected on the bytes B2.
* Use MS/HO/LO DEG Count Mode to select the type of error rate evaluation mode
(Poisson or ETSI).
If Poisson has been selected.
Use MS DEG Threshold (10-5 to 10-9) to set the threshold for considering the incoming stream
degraded. This calculation uses the bytes B2.
If ETSI has been selected.
Enter the percentage of BBE (DEG Threshold) detected on the bytes B2 (MS) and the number of
errored seconds which are activating/deactivating a bad/good period.
* Use Sect Trace Mode to set the type of section trace.
Single Byte Rx - Tx
A single byte value is expected in the J0 byte (section trace). A single byte value is sent into the J0
byte.
15 Bytes Rx - Single Tx
A 15-bytes value is expected in the J0 byte. A single byte value is sent into the J0 byte.
Single Rx - 15 Bytes Tx
A single byte value is expected in the J0 byte. A 15-bytes value is sent into the J0 byte.
15 Bytes Rx - Tx
A 15-bytes value is expected in the J0 byte. A 15-bytes value is sent into the J0 byte.
* Use Sect Trace (J0) Exp to set the value expected on Byte J0.
* Use Sect Trace (J0) Conf to set the value sent on Byte J0. Values lower than 7F
(standard character set) are allowed for every byte if the HEX format for the configuration
has been selected.
* Use Sect Trace Transmission to enable/disable the Section Trace management. If
Section Trace has been disabled a value 01 single byte is sent.
* Use Sect Trace Mism Detection to enable/disable the issue of J0 mismatch alarm in
presence of a wrong Section Trace on the receive side.
IMPORTANT If you set Sonet mode, J0 trasmission and J0 mismatch detection will be
disabled.

.
Issue:1
* Use Line Expected SS Bit value to define the expected SS bit value for a framing
according to SDH or SONET specifications.
Note When the Line Expected SS Bit value is configured as SONET, only passing
through VC-4 cross-connections are allowed.
* Use Line Configured SS Bit value to define the SS bit value sent to the line.
* Use Optical Protection to enable/disable the optical protection of the unit.
This option is used for testing purposes. It is suggested to set it to Enabled.
NOTICE Setting this option to disable the equipment can be considered as potentially
dangerous.
Refer To:
Safety Rules for SDH Equipment Handbook.
Note For STM-4 Unit, the Optical Protection works only for the long-haul Units.
* Press APPLY.
Note The port frame and the VC-4s will be configured with the default parameter.
In the LOM Defect Recovery Time field, the time of handling of the AU-4-Xv multiframe error
has to be indicated. The value inserted represents the time to wait for the correct multiframe to
be restored.
In the SQM Defect Issue Thr. field the Operator has to indicate the number of defect
multiframes after that an SQM alarm will arise.
In the SQM Defect Clear Thr. field the Operator has to indicate the number of correct frames (with
correct sequencing) that have to be received for clearing the SQM alarm.
IMPORTANT The new fields LOM Defect Recovery Time, SQM Defect Issue Thr. and SQM
Defect Clear Thr. are exclusively related to the new STM-16 MUX-4/3 optical
units; when we configure a versions of STM-16 units different from MUX-4/3 ,
these new fields are not available.
See Also:
AU Group Definition, Alarms: port mode

.
Issue:1
STM-16/4 Port (Standard Type)

(Poisson or ETSI).

.
Issue:1
Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx
has been selected.
dangerous.
Refer To:
Note For STM-4 Unit, the Optical Protection works only for the long-haul Units.
* Press APPLY.
See Also:
Alarms: port mode

.
Issue:1
STM-1 Port (4xSTM-1/140Mbit/s and NxSTM-1 Unit)

This option applies to 4xSTM-1/140Mbit/s or NxSTM-1 Unit port defined as STM-1.

(Poisson or ETSI).

.
Issue:1
Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx
has been selected.
dangerous.
Refer To:
Note For 2xSTM-1 Optical Unit only.
* Press APPLY.
See Also:
Alarms: port mode

.
Issue:1
STM-1 Port (Type 2)

This option applies to STM-1 G.703 Electrical/Optical Mux Type 2.
* Use AIS on VC Unequip enable/disable the downstream injection of AIS indication to the
Matrix when a HP-Payload Label Unequipped is detected.
* Use RDI on VC Unequip enable/disable the HP-RDI indication to the line when a HP-
Payload Label Unequipped is detected.
* Use AIS on HO-TIM to enable/disable the downstream injection of AIS indication to the
Matrix when a HO Trace Identifier Mismatch has been detected.
* Use RDI on HO-TIM to enable/disable the RDI indication to the line when a Trace

.
Issue:1
* Use AIS on PLM to enable/disable the downstream injection of AIS indication to the
Matrix when a HP-Payload Label Mismatch has been detected.
* Use RDI on PLM to enable/disable the HP-RDI indication to the line when a HP-Payload
Label Mismatch has been detected.
* Use AIS on HO-EXC to enable/disable the downstream injection of AIS indication to the
Matrix when a HO EXC (excessive bit error ratio - >10-3) has been detected.
* Use RDI on HO-EXC to enable/disable the RDI indication to the line when a HO EXC
(excessive bit error ratio - >10-3) has been detected.
(Poisson or ETSI).
Use HO PATH DEG Thr. (10-5 to 10-9) to set the threshold for considering the VC-payload degraded
on the Virtual Containers (VC-4). This calculation uses the byte B3 (VC-4 and VC-3) and the byte
V5 (VC-2, VC-12).
Enter the number of BBE (DEG Threshold) detected on the bytes B2 (MS) and the number of
Enter the number of BBE (DEG Threshold) for the VC (HO PATH) and the number of errored
seconds which are activating/deactivating a bad/good period.
Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx

.
Issue:1
has been selected.
* Use Path Trace Mode to set the type of path trace.
Single Byte Rx - Tx
A single byte value is expected in the J1 byte (path trace). A single byte value is sent into the J1
byte.
15 Bytes Rx - Tx
* Use Path Trace (J1) Exp to set the value expected on Byte J1.
* Use Path Trace (J1) Conf to set the value sent on Byte J1. Values lower than 7F
has been selected.
* Use Signal Label Exp to set logical state expected on byte C2.The following values can
be assigned: Equip (non spec.), TUG structured, Locked TU, Async. 34 Mb, Async 140
Mb, FDDI, ATM, MAN.
* Use Signal Label Conf to set logical state sent on byte C2 (see above).
* Use Path Trace (J1) Transmission to enable/disable the Path Trace management. If
Path Trace has been disabled a value 01 single byte is sent.
* Use Path Trace (J1) Mism Detection to enable/disable the issue of J1 mismatch alarm
in presence of a wrong path trace on the receive side.
* Use HO PATH-PROT SW CRITERIA to set the criteria for the high order path protection
switch of the selected port.

.
Issue:1
NON INTRUSIVE
The switch is caused by the following alarms: AU_AIS, AU_LOP, HP_UNEQ, HP_TIM, HP_DEG,
HP_EXC. This is the most sensitive SNC Protection for high order VC.
INHERENT
The switch is caused by the following alarms: AU_AIS, AU_LOP. This is the least sensitive SNC
protection for high order VC.
PARTIAL NOT INTRUSIVE
The switch criteria for the SNC protection of the high order VC, can be enabled by the operator
(Apart from the AU_AIS and AU_LOP switch criteria).
* Use H1 byte SS bit value to set the port for a framing according to SDH or SONET
specifications.
* Use Laser Restart Delay to insert a delay for the automatic restart of the laser after an
interruption (only for Optic/Mux Units).
* Press APPLY.

.
Issue:1
STM-1 Port (Type 1)

This option applies to STM-1 G.703 Electrical/Optical Mux Type 1.
To configure a STM-1 port:

* Use EXC to enable/disable the downstream injection of AU-AIS indication to the Matrix
when an excessive bit error ratio (>10-3) is detected on byte B2 (MS-EXC).
* Use C2 Mismatch to enable/disable the downstream injection of AIS indication to the
Matrix when a C2 mismatch is detected (HP-PLM).
* Use J1 Mismatch to enable/disable the downstream injection of AIS indication to the
Matrix when a J1 mismatch is detected (HP-TIM).
* Use RDI to select the type of management for the RDI alarm.
Automatic
Enables the issue of Remote Defect Indication alarm (bits 6, 7 and 8 of byte K2) in case of alarms.
* Use Laser Restart Delay to insert a delay for the automatic restart of the laser after an
interruption (only for Optic/Mux Units).
* Use MS DEG Threshold (10-5 to 10-9) to set the threshold for the error rate check on B2
bytes.
* Use HO Mux Path to define the High Order Multiplexing Path.
* Use HO PATH DEG Thr. (10-5 to 10-9) to set the threshold for the error rate check on the
Virtual Containers (VC-12 or VC-4).

.
Issue:1
* Use H1 byte SS bit value to set the port for a framing according to SDH or SONET
specifications.
* Use C2 Expected to set logical state expected on byte C2. The following values can be
assigned: Equip (non spec.), TUG structured, Locked TU, Async. 34 Mb, Async 140 Mb,
FDDI, ATM, MAN.
* Use C2 Configured to set logical state sent on byte C2 (see above). The following
values can be assigned: Equip (non spec.), TUG structured.
* Use J1 Expected to set all 0s (or all 1s) expected in byte J1 (Path Trace).
* Use J1 Configured to set all 0s (or all 1s) sent to byte J1 (Path Trace).
* Press APPLY.
140Mbit/s port (4xSTM-1/140Mbit/s and NxSTM-1 Unit)
This option applies to 4xSTM-1/140Mbit/s Unit port defined as 140Mbit/s.
To configure a 140Mbit/s port:

* Use Line Prot. Switch on AIS to enable/disable the line protection switching when an
AIS is detected on the 140Mbit/s PDH input.
* Use Line Prot. Switch on SF to enable/disable the line protection switching when a
Signal Failure is detected on the 140Mbit/s PDH input.
* Use AIS on PDH AIS to enable/disable the issue of a full AIS signal towards multiplexing
path in presence of AIS detected on the incoming plesiochronous signal.
* Use Line DEG Threshold (10-5 to 10-9) to set the threshold for the error rate check on the
140Mbit/s PDH input.
* Use Signal Type to check the frame alignment word (Framed) according to ITU-T Rec.
G.751, G.755, G.757, (in case of failure an AIS is forwarded downstream) or a signal
unstructured without alignment word (Unframed).
* Press APPLY.

.
Issue:1
140Mbit/s port

* Use Line EXC to enable/disable the downstream injection of AIS indication to the Matrix
when an excessive bit error rate (10-3) is detected on 140Mbit/s PDH input.
* Use HO EXC to enable/disable the downstream injection of AIS indication to the line
when an excessive bit error rate (10-3) is detected on the VC-4 (byte B3).
* Use C2 Mismatch to enable/disable the downstream injection of AIS indication to the line
when a C2 mismatch is detected (HP-PLM).
* Use J1 Mismatch to enable/disable the downstream injection of AIS indication to the line
when a J1 mismatch is detected (HP-TIM).
Single Byte Rx - Tx
byte.

.
Issue:1
15 Bytes Rx - Tx
has been selected.
* Use Signal Label Exp to set logical state expected on byte C2. The following values can
be assigned: Async. 140Mb, Equip. (not spec.).
Path Trace has been disabled a value 00 is sent in all bytes.
* Use Signal Type to check the frame alignment word (Framed) according to ITU-T Rec.
G.751, G.755, G.757, (in case of failure an AIS is forwarded downstream) or a signal
unstructured without alignment word (Unframed).
* Use HO PATH DEG Thr. (10-5 to 10-9) to set the threshold for the error rate check on the
Virtual Containers (VC-4).
* Use Line Prot. Switch on AIS to enable/disable the line protection switching when AIS is
detected on the 140Mbit/s PDH input.
* Press APPLY.

.
Issue:1
140Mb T-Mux port
To configure a 140Mbit/s T-Mux port:

* Use AIS on EXC to enable/disable the downstream injection of AIS indication to the
Matrix when an excessive bit error rate (10-3) is detected on 140Mbit/s PDH input.
* Use AIS on PLM to enable/disable the downstream injection of AIS indication to the line
when a Payload Label Mismatch is detected on the VC-12.
* Use AIS on VC Uneq to enable/disable the downstream injection of AIS indication to the
line when an Unequipped label is detected on the VC-12.
* Use AIS & RDI on TIM to enable/disable the downstream injection of AIS indication to
the line and the issue of the RDI indication to the Matrix when a trace identifier mismatch
is detected on the VC-12.
* Use RDI on EXC to enable/disable the injection of the RDI indication to the Matrix when
an excessive bit error rate (10-3) is detected on the VC-12 incoming from the Matrix.
* Use RDI on PLM to enable/disable the injection of the RDI indication to the Matrix when
a Payload Label Mismatch is detected on the VC-12.
* Use RDI on VC Uneq to enable/disable the injection of the RDI indication to the Matrix
when an Unequipped label is detected on the VC-12.
* Use Line Prot. Switch on AIS to enable/disable the line protection switching when an
AIS is detected on the 140Mbit/s PDH input.
* Use O-R bits Value to select the desired value (0 or 1) for the stuffing bits O and R

.
Issue:1
* Use LO PATH DEG Thr. (10-5 to 10-9) to set the threshold for the error rate check on the
Virtual Containers (VC-12).
* Use Path Trace (J2) Mism Detection to enable/disable the detection of mismatch on the
path trace of all the VC-12 managed by the unit.
* Use Path Trace Mode to set the type of path trace for all the VC-12 managed by the unit.
Possible options are:
Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx
* Use 2Mb CHANNEL TO DISCARD to select the 2Mbit/s channel contained in the
incoming 140Mbit/s plesiochronous signal to be lost. On the line side the selected
channel (discarded towards the matrix side) is replaced with an AIS signal.
IMPORTANT In the 140Mbit/s signal are present 64x2Mbit/s signals but only 63x2Mbit/s can
be multiplexed to the matrix. By default the 64th 2Mbit/s stream (pos. 444) is
discarded.
* Press APPLY.

.
Issue:1
2Mbit/s ports (63x2Mbit/s Unit)

2Mbit/s PDH input.
* Use PDH-AIS Regeneration to enable/disable the downstream injection of AIS indication
to the Matrix when AIS is detected on 2Mbit/s PDH input.
* Use Signal Type to select the type of signal checked by the unit.
Unframed
2Mbit/s signal unframed.
Framed
2Mbit/s signal framed according to G703/G.704.
* Use PDH CRC-4 to enable/disable the CRC framing check in the 2Mbit/s signal.
* Use PDH Traffic Rate to define the input signal traffic rate (1,5 or 2Mbit/s).
IMPORTANT The sixty-three ports managed by the unit have to be considered divided in two
groups: the first group includes the ports from 1 to 32 the second group the ports
from 33 to 63. Within each group the ports must be configured to manage the
same traffic rate (PDH Traffic Rate - 1,5 or 2Mbit/s signal).
See Also:
2Mbit/s Type 2 Port: configuring global parameters, 2Mbit/s Port: configuring the
G703/G704 frame characteristics, LPOM Ports: configuring LO VC operational
parameter (DXC 41), Alarms: port mode

.
Issue:1
2Mbit/s ports (Standard Type and CRC-4 Type)

* Use Signal Label Expected to set logical state expected on bits 5, 6 and 7 of byte V5.
The following values can be assigned: VC Eq non specific., Async Floating, VC
Unequipped.
* Use Signal Label Configured to set logical state sent on bits 5, 6 and 7 of byte V5 (see
above).
* Press APPLY.
If this operation is carried out for the first time having selected APPLY the system displays a
message requiring the modification of the port global parameters.
Select OK for modifying now the port global parameters and make the proper window to be
displayed.
See Also:
2Mbit/s Port: configuring global parameters, 2Mbit/s Port: configuring the G703/G704
frame characteristics, General Index

.
Issue:1
2Mbit/s-T2 ports (Standard Type and CRC-4 Type)
To configure a 2Mbit/s-T2 port:
IMPORTANT If this operation is carried out for the first time, the Port Global Parameters
window is displayed. Set the port global parameters for all the ports managed by
the 16x2Mbit./s Tributary Unit (as described in the paragraph 2Mbit/s Type 2
Port: configuring global parameters), then press FORWARD.
VC-12.
15 Bytes Rx - Tx
has been selected.
* Use Signal Label Exp to set logical state expected on bits 5, 6 and 7 of byte V5. The
default value is set to Async floating.
* Use Signal Label Conf to set logical state configured on bits 5, 6 and 7 of byte V5. The
default value is set to Async floating.
* Press APPLY.
See Also:
2Mbit/s Type 2 Port: configuring global parameters, 2Mbit/s Port: configuring the
G703/G704 frame characteristics

.
Issue:1
34/45Mbit/s port (Type 2 Subrack)

* Use RDI on VC Unequip to enable/disable the injection of the RDI indication to the
Matrix when an Unequipped signal label is detected on byte C2 of the VC-3.
* Use AIS on VC Unequip to enable/disable the injection of AIS indication to the line when
an Unequipped signal label is detected on byte C2 of the VC-3.
* Use PDH AIS Regeneration to enable/disable the issue of a full AIS signal towards
multiplexing path in presence of AIS detected on the incoming plesiochronous signal.
Single Byte Rx - Tx
byte.

.
Issue:1
15 Bytes Rx - Tx
has been selected.
* Use Signal Label Exp to set logical state expected on byte C2. The following values can
be assigned: Async. 34-45Mb, Equip. (not spec.).
Path Trace has been disabled a value 00 is sent in all bytes.
* Press APPLY.
If is this operation is carried out for the first time (immediately after the unit commissioning), having
selected APPLY the system displays a message requiring the modification of the port global
parameters.
Select OK for modifying now the port global parameters and make the proper window to be
displayed.
See Also:
34Mbit/s Port: configuring global parameters
34Mb port (4x34Mbit/s Transmux Unit)
To configure a 4x34Mbit/s port:

34Mbit/s PDH input.
* Press APPLY.
See Also:
Operative States, LPOM Ports: configuring LO VC operational parameter (DXC 41)
34Mb-VC port (4x34Mbit/s VideoCodec Unit)
To configure a 4x34Mbit/s port:

* Press APPLY.
See Also:
4x34Mbit/s Videocodec Port: configuring global parameters, Operative States

.
Issue:1
34/45Mbit/s port (Type 3 Subrack)

34-45Mbit/s PDH input.
* Use 34-45 Mb Signal Framing to set the checking of a frame not structured without
alignment word (Unframed) or a frame structured with alignment word (Framed).
* Use PDH AIS Regeneration to enable/disable the issue of a full AIS signal towards
multiplexing path in presence of AIS detected on the incoming plesiochronous signal.
* Press APPLY.
See Also:
Operative States, LPOM Ports: configuring LO VC operational parameter (DXC 41)

.
Issue:1
45Mb T-Mux port
To configure a 45Mbit/s T-Mux port:

* Use PDH-AIS on LP-PLM to enable/disable the injection of AIS indication to the line
when a Payload Label Mismatch is detected on the VC-12 incoming from the Matrix.
* Use PDH-AIS on LP-TIM to enable/disable the injection of AIS indication to the line when
a trace identifier mismatch is detected on the incoming VC-12.
* Use PDH-AIS on LP-Uneq to enable/disable the injection of AIS indication to the line
when an Unequipped signal label is detected on byte C2 of the VC-12 incoming from the
Matrix.
* Use RDI on LP-EXC to enable/disable the injection of the RDI indication to the Matrix
when an excessive bit error rate (10-3) is detected on the VC-12 incoming from the
Matrix.
* Use RDI on LP-PLM to enable/disable the injection of the RDI indication to the Matrix
when a Payload Label Mismatch is detected on the VC-12 incoming from the Matrix.
* Use RDI on LP-TIM to enable/disable the issue of Remote Defect Indication alarm (bit 4
of byte V5) towards the Matrix in case of trace identifier mismatch on the
VC-12.
* Use RDI on LP-Uneq to enable/disable the injection of the RDI indication to the Matrix
when an Unequipped signal label is detected on byte C2 of the VC-3.

.
Issue:1
(Poisson or ETSI).
Use LO PATH DEG Thr. (10-5 to 10-9) to set the threshold for considering the VC payload degraded
on the Virtual Containers (VC-12). This calculation uses the byte V5 (VC-2, VC-12).
Enter the number of BBE (DEG Threshold) detected on the bytes V5 (LO) and the number of
* Define the DS2 Channel Configuration by checking the relevant DS1, E1 exclusive
buttons.
The unit receive a DS3 (multiframed digital signal at 45Mbit/s) which is demultiplied on 7
DS2 (multiframed digital signal at 6Mbit/s). This signal can be demultiplied on four DS1
(1,5 Mbit/s as defined by ANSI T1.107) or on three E1 (2Mbit/s as defined by ITU-T
G747).
* Use DS3 Idle Signal to enable/disable the DS3 idle signal condition.
The DS3 idle signal is a particular condition on that the 45Mbit/s T-Mux Unit is not cross-
connected but the frame configuration is correct.
When the 45Mbit/s T-Mux Unit is not cross-connected the possible options are:
Disabled
The unit output is disable.
Transmit Idle Signal
Transmission of a idle signal.
Transmit AIS Signal
Transmission of a AIS signal.
Note When the 45Mbit/s T-Mux Unit receive a DS3 Idle Signal, the DS3 IdleSignal alarm is
reported.
* Use FEAC Monitoring Enable to enable/disable the monitoring of the Far-End Alarm
and Control bit. This bit is used for remote alarm and state indication or DS3/DS1 remote
loopback request.
* Press APPLY.
See Also:
2Mbit/s Type 2 Port: configuring global parameters, 4x34Mbit/s Videocodec Port:
configuring global parameters, Operative States

.
Issue:1
Port: displaying operational parameters

Path (Action-Port Management-Read)
This option is used to display the operational parameters selected for an already configured port.
See Also:
Port: configuring operational parameter, Operative States
Port: modifying operational parameters

Path (Action-Port Management-Modify)
This option is used to modify the operational parameters assigned to an already configured port.
See Also:
Port: removing configuration

Path (Action-Port Management-Delete)
This option is used to decommission a port on a port subrack.
A port can be decommissioned only when it is in the following conditions:
a. All connections using the selected port have been removed
b. All protections using the selected port have been removed
c. Synchronisation sources using the selected port have been removed
A window will be displayed depending on the type of port selected. An information summary
regarding the port configuration is given in the window.
See Also:

.
Issue:1

Path (Action-Port 2Mb Global Param.-Setup)
This option is used for setting port parameters that are applied to all the 16x2Mbit/s ports present in
the 16x2Mbit/s Tributary Unit (e.g.: Line DEG Threshold).
To set 2Mbit/s port global parameters:

* Use EXC to enable/disable the downstream injection of AIS indication to the Matrix when
an excessive bit error ratio (10-3) is detected on 2Mbit/s PDH input and the injection of
AIS to the PDH line when an excessive bit error ratio (10-3) is detected on the VC-12
(byte V5).
* Use Signal Label Mismatch to enable/disable the injection of AIS indication to the line
when a signal label mismatch is detected.
VC12.
2Mbit/s PDH input.
* O-R bit Value
Not used (for future applications).
* Press APPLY.
See Also:

.
Issue:1
2Mbit/s Port: displaying global parameters

Path (Action-Port 2Mb Global Param.-Read)
This option is used for displaying the parameters that are applied to all 2Mbit/s ports.
See Also:
2Mbit/s Port: configuring global parameters, Operative States
2Mbit/s Type 2 Port: configuring global parameters

Path (Action-Port 2Mb Type2 Global Param.-Setup)
This option is used to configure the port parameters applied to all the ports supported by the
16x2Mbit/s-T2 Tributary Unit. This window is also activated when configuring for the first time a port
within the unit. In this case, the window is closed by the button FORWARD instead of APPLY.
To set 2 Mbit/s-T2 port global parameters:

* Use PDH-AIS on LP-PLM to enable/disable the injection of AIS indication to the line
when a payload label mismatch is detected on the incoming VC-12.
* Use PDH-AIS on LP-TIM to enable/disable the injection of AIS indication to the line when
a trace identifier mismatch is detected on the incoming VC-12.
* Use PDH-AIS on LP-Uneq to enable/disable the injection of AIS indication to the line
when a VC-Uneq label is detected on the incoming VC-12.
* Use PDH-AIS Regeneration to enable/disable the downstream injection of AIS indication
to the Matrix when AIS is detected on 2Mbit/s PDH input.
* Use RDI on LP-EXC to enable/disable the issue of Remote Defect Indication alarm (bit 4
of byte V5) towards the Matrix when an excessive bit error rate (>10-3) is detected on byte
V5 (bit 1,2).
* Use RDI on LP-PLM to enable/disable the issue of Remote Defect Indication alarm (bit 4
of byte V5) towards the Matrix in case of payload label mismatch on the VC-12.

.
Issue:1
* Use RDI on LP-TIM to enable/disable the issue of Remote Defect Indication alarm (bit 4
of byte V5) towards the Matrix in case of trace identifier mismatch on the VC-12.
* Use RDI on LP-Uneq to enable/disable the issues of Remote Defect Indication alarm (bit
4 of byte V5) towards the Matrix in case a LP-Uneq label is detected on the incoming VC-
12.
* Use LO PATH DEG Count Mode to select the type of error rate evaluation mode
(Poisson or ETSI).
2Mbit/s PDH input.
* O-R bits Value
Not used (for future applications).
* Press APPLY (or FORWARD if this window was activated by a Port Configuration
operation).
2Mbit/s Type 2 Port: displaying global parameters

Path (Action-Port 2Mb Type2 Global Param.-Read)
This option is used for displaying the parameters that are applied to all 2Mbit/s ports.
See Also:
2Mbit/s Type 2 Port: configuring global parameters, Operative States

.
Issue:1

Path (Action-Port 34Mb Global Param.-Setup)
This option is used for setting port parameters that are applied to all the ports present in the 3x34 or
3x45Mbit/s Tributary Unit.
To set 34-45Mbit/s port global parameters:

* Use LINE DEG Threshold (10-5 to 10-9) to set the threshold for the error rate check on
the 34-45Mbit/s PDH input.
* Use 34-45 Mb Signal Framing to set the checking of a frame not structured without
alignment word (Unframed) or a frame structured with alignment word (Framed).
VC-3.
* Press APPLY.
See Also:
34Mbit/s Port: displaying global parameters

Path (Action-Port 34Mb Global Param.-Read)
This option is used for displaying parameters that are applied to all the 34-45Mbit/s ports.
See Also:
34Mbit/s Port: configuring global parameters, Operative States

.
Issue:1
34Mbit/s T-Mux Port: selecting the channel to discard

Path (Action-Channel To Discard)
This option is used to select the 2Mbit/s channel contained in the incoming 34Mbit/s plesiochronous
signals to be lost. On the line side the selected channel (discarded towards the matrix side) is
replaced with an AIS signal.
* Select the CHANNEL TO DISCARD
* Press APPLY
140Mbit/s T-Mux Port: configuring the VC-12 POH

Path (Action-TMUX140 VC12 POH-Setup)
This option is used to configure the low order path overhead of the VC-12 channels obtained from
the 2Mbit/s plesiochronous signals incoming from T-Mux port.
To set VC-12 POH:

* Use CHANNEL Selection to choose the channel to be modified. (ALL for all 2Mbit/s
channels).
has been selected.
* Press APPLY.
See Also:
140Mbit/s T-Mux Port: displaying the VC-12 POH

.
Issue:1
140Mbit/s T-Mux Port: displaying the VC-12 POH

Path (Action-TMUX140 VC12 POH-Read)
This option is used to display the VC12 channel POH configuration for the selected 140Mb/s T-Mux
Card.
To display the current configuration of a VC12 path overhead:

* Use CHANNEL Selection to choose the channel. The parameters in use are
automatically displayed in the relevant fields.
See Also:
140Mbit/s T-Mux Port: configuring the VC-12 POH
4x34Mbit/s Videocodec Port: configuring global parameters

Path (Action-Port 4x34Mb VC Global Param.-Setup)
This option is used for setting port parameters that are applied to all the ports present in the
4x34Mbit/s Videocodec Tributary Unit.
To set 4x34Mbit/s Videocodec port global parameters:

* Use Signal Label Mismatch to enable/disable the injection of AIS indication to the line
when a signal label mismatch is detected.
input video signal.
VC-3.
* Press APPLY.

.
Issue:1
See Also:
4x34Mbit/s Videocodec Port: displaying global parameters
4x34Mbit/s Videocodec Port: displaying global parameters

Path (Action-Port 4x34Mb VC Global Param.-Read)
This option is used for displaying parameters that are applied to all the 34Mbit/s Videocodec ports.
See Also:
4x34Mbit/s Videocodec Port: configuring global parameters
2Mbit/s Port: configuring the G703/G704 frame characteristics

Path (Action-Port Frame Configuration-Setup)
This option is used for modifying the 2Mbit/s frame characteristics of the 16x2Mbit/s Tributary Unit
(G703/G704).
To change the frame characteristics:

* Use Input Signal Type to select the type of signal checked by the unit.
Unframed
2Mbit/s signal unframed.
Framed
2Mbit/s signal framed according to G703/G.704.
* Use CRC-4 Monitoring to enable/disable the CRC framing check in the 2Mbit/s signal.
* Use RAI & E-Bit Monitoring to enable/disable the check of the Remote Alarm Indication
(RAI).
* Press APPLY.

.
Issue:1
See Also:
2Mbit/s Port: displaying the G703/G704 frame characteristics, Unit: equipping (DXC
4/1)
2Mbit/s Port: displaying the G703/G704 frame characteristics

Path (Action-Port Frame Configuration-Read)
This option is used for displaying the 2Mbit/s frame characteristics of the 16x2Mbit/s Tributary Unit
(G703/G704).
See Also:
1x45Mbit/s T-Mux Port: setting the VC-12 parameter

Path (Action-VC12 parameter / DEG-Setup)
This option is used to configure the parameters of the VC-12 channels managed by the 1x45 T-Mux
Unit.
To set the VC-12 parameter:

* Select the VC-12 channel which parameters have to be configured using the VC12
CHANNEL Sel. scroll list.
* Use PDH/LO DEG Count Mode to select the type of error rate evaluation mode
(Poisson or ETSI).

.
Issue:1

Use LO PATH DEG Thr. (10-5 to 10-9) to set the threshold for considering the payload degraded on
the Virtual Containers (VC-12). This calculation uses the byte V5 (VC-2, VC-12).
Enter the number of BBE (DEG Threshold) for the VC (LO PATH) and the number of errored
has been selected.
* Use Signal Label Expected to set logical state expected on bits 5, 6 and 7 of byte V5.
The default value is set to Async floating.
* Use Signal Label Configured to set logical state configured on bits 5, 6 and 7 of byte
V5. The default value is set to Async floating.
* Use Path Trace (J2) Mism Detection to enable/disable the detection of mismatch on the
path trace of all the VC-12 managed by the unit.
* Use PDH AIS TIM to enable/disable the downstream injection of AIS indication to the line
when a trace identifier mismatch is detected on the VC-12.
* Use LP RDI on TIM to enable/disable the issue of the RDI indication to the Matrix when a
trace identifier mismatch is detected on the VC-12.
* Press APPLY
See Also:
1x45 T-Mux Mbit/s Port: displaying the VC-12 parameter

Path (Action-VC12 parameter / DEG-Read)
This option is used for displaying the parameters of the VC-12 channels managed by the 1x45 T-
Mux Unit.
See Also:
1x45Mbit/s T-Mux Port: setting the VC-12 parameter

.
Issue:1
STM-1 Port: setting HPOM alarm suppression state

Path (Action-HPOM Alarm Suppression)
This functionality performed at CCU level, concerns the correlation among network alarms,
generated independently by each Port Unit, making use of the information stored in the cross-
connection database. The aim of this functionality is to reduce the amount of alarms. At cross-
connection creation/deletion time, the CCU changes automatically the monitoring state of the
alarms involved, as below defined. If the functionality is enabled (default), the following alarms are
not monitored:
VC-4 Cross-connection
HP-UNEQ, HP-TIM, HP-PLM, HP-EXC, HP-DEG, HP-RDI (always not monitored).
IMPORTANT The default status of this option is enabled
See Also:
STM-1 Type 2 Port: setting C2 mismatch detection state

Path (Action-C2 Mismatch Detection Enable)
This option is used to enable/disable the detection of mismatch on the signal label C2 (within the
VC-4 Path Overhead) for the selected STM-1 Type 2 port. This option is available only for the STM-
1 Type 2 optical and electrical Mux units.
See Also:
34/45Mbit/s, 140Mbit/s, STM-N and NxSTM-1 Ports: displaying the SOH

bytes status
Path (Action-Get Overhead)
This option is used to display the status of the SOH bytes for the 34/45Mbit/s Tributary Units
(belonging to DXC 4/1), 140Mbit/s Tributary Units, STM-1 G703 Electrical and Optical Mux Unit
Type 2, STM-N Unit and for NxSTM-1 Unit.
See Also:
STM-N and 2xSTM-1 Ports: managing the optical parameters

Path (Action-Optical Parameters)
This option is used to display the optical parameters (Tx and Rx power, threshold and modulation
current, temperature, status of the laser transmitter) of the STM-4, STM-16, 2xSTM-1 Optical/Mux
Unit and STM-1 Optical/Mux Unit Type 2.
* Use Optical Protection to enable/disable the optical protection of the managed unit. This
option can be used for testing purposes. It is suggested to set it to Enabled.
In the Lambda field you can read the laser wavelenght.
* In Tx Power [dBm] you can set the Transmission Power of the laser.

.
Issue:1
This two fields are related to STM-16 DWDM only.

Note For the STM-4/16 and 2xSTM-1 Optical/Mux Unit the Optical Protection state can
not be set because it has already been configured in the Port Configuration window.
This field shown only the value previously chooses.
dangerous.
Refer To:
* Press REFRESH to update the optical parameters displayed, press APPLY to confirm
the optical protection setting.
See Also:

.
Issue:1
STM-N Port: configuring VC-4 operational parameter

Path (Action-VC-4 Configuration)
This option is used to assign the VC-4 operational parameter to the configured NxSTM-1, 4x140-
155Mbit/s and STM-N Unit (with exception of STM-1 Unit).
To configure the VC-4 operational parameters:

* Select the AUG relevant to the VC-4 to be configured.
The option ALL allows configuring in the same way the VC-4 channels belonging to all AUGs.
* Use AIS on HO-TIM to enable/disable the downstream injection of AIS indication to the
Matrix when a High Order Path Trace Identifier Mismatch has been detected.
* Use RDI on HO-TIM to enable/disable the HO-RDI indication to the line when a High
Order Path Trace Identifier Mismatch has been detected.
* Use AIS on HO-PLM to enable/disable the downstream injection of AIS indication to the
Matrix when a High Order-Payload Label Mismatch has been detected.
* Use RDI on HO-PLM to enable/disable the HO-RDI indication to the line when a High
Order -Payload Label Mismatch has been detected.
* Use AIS on VC Unequip enable/disable the downstream injection of AIS indication to the
Matrix when a High Order -Payload Label Unequipped is detected.

.
Issue:1
* Use RDI on VC Unequip enable/disable the HO-RDI indication to the line when a High
Order -Payload Label Unequipped is detected.
* Use AIS on HO-EXC to enable/disable the downstream injection of AIS indication to the
* Use RDI on HO-EXC to enable/disable the HO-RDI indication to the line when an
* MS/HO/LO DEG Count Mode display the type of error rate evaluation mode previously
configured in the Port Configuration window (see "Port: configuring operational
parameter" subparagraph).
If in the port configuration window Poisson has been selected
-5 -9
Use HO PATH DEG Thr. (10 to 10 ) to set the threshold for considering the VC payload
degraded on the Virtual Containers (VC-4). This calculation uses the byte B3 (VC-4).
If in the port configuration window ETSI has been selected
Enter the percentage of BBE (DEG Threshold) for the VC (HO PATH) and the number of errored

Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx
has been selected.
* Use Signal Label Exp to set logical state expected on byte C2.The following values can
be assigned: Equip (non spec.), TUG structured, Locked TU, Async. 34 Mb, Async 140
Mb, FDDI, ATM, MAN.
Path Trace has been disabled a value 01 single byte is sent.

.
Issue:1
* Use Mode (in the HO PATH-PROT SW CRITERIA field) to set the criteria for the high
order path protection switch of the selected port.
NON INTRUSIVE
The switch is caused by the following alarms: AU_AIS, AU_LOP, HP_UNEQ, HP_TIM, HP_DEG,
HP_EXC. This is the most sensitive SNC Protection for high order VC.
INHERENT
The switch is caused by the following alarms: AU_AIS, AU_LOP. This is the least sensitive SNC
protection for high order VC.
The switch criteria for the SNC protection of the high order VC, can be enabled by the operator
(Apart from the AU_AIS and AU_LOP switch criteria).
* Use C2 Mismatch Detection to enable/disable the detection of mismatch on the signal
label C2 (within the VC-4 Path Overhead) for the selected AU.
* Use HPOM Alarm Suppression State to enable/disable the monitoring of some HP
network alarm. The aim of this functionality is to reduce the amount of alarms.
If the functionality is enabled (default), the following alarms are not monitored:
VC-4 Cross-connection
HP-UNEQ, HP-TIM, HP-PLM, HP-EXC, HP-DEG, HP-RDI (always not monitored)
* Press APPLY.
See Also:
Port: configuration, STM-1 Type 2 Port: setting C2 mismatch detection state, STM-N
Port: configuring frame and supervisory unequipped state, STM-1 Port: setting HPOM
alarm suppression state

.
Issue:1
LPOM Ports: configuring LO VC operational parameter (DXC 4/1)

Path (Action-VC Configuration-Setup)
This option is used to assign the LO VC operational parameter to the configured NxSTM-1 Type 3,
STM-16 Type LPOM, STM-4 Type 2 Units, 63x2Mbit/s Unit, 4x34Mbit/s T-Mux Unit and
3x34/45Mbit/s Unit (for the Type 3 Subrack).
63x2Mbit/s Unit, 4x34Mbit/s T-Mux Unit and 3x34/45Mbit/s Unit
To configure the LO VC operational parameters:

* Select the TU and/or the 2Mbit/s port to be configured (port in case of 63x2Mbit/s Unit,
TU/Port in case of 4x34Mbit/s T-Mux Unit).
* Use RDI on LP-TIM to enable/disable the LO-RDI indication to the matrix when a Low
* Use AIS on LP-TIM to enable/disable the downstream injection of AIS indication to the
line when a Low Order Path Trace Identifier Mismatch has been detected.
* Use RDI on LP-Unequip enable/disable the LO-RDI indication to the matrix when a Low
Order -Payload Label Unequipped is detected.
* Use AIS on LP-Unequip enable/disable the downstream injection of AIS indication to the
line when a Low Order -Payload Label Unequipped is detected.
* Use RDI on LP-EXC to enable/disable the LO-RDI indication to the matrix when an
excessive bit error ratio (>10-3) is detected.
* Use AIS on LP-EXC to enable/disable the downstream injection of AIS indication to the
line when an excessive bit error rate (>10-3) is detected.

.
Issue:1
* Use RDI on LP-SLM to enable/disable the LO-RDI indication to the matrix when a Low
Order -Signal Label Mismatch has been detected.
* Use AIS on LP-SLM to enable/disable the downstream injection of AIS indication to the
line when a Low Order-Signal Label Mismatch has been detected.
IMPORTANT In case the selected unit is a 63x2Mbit/s the configured fault actions will be
enabled/disabled for all the first or second group of thirty-two ports (the two
groups include ports from 1 to 32 and ports from 33 to 63).
* LO PATH DEG Count Mode to select the type of error rate evaluation mode (Poisson or
ETSI).
Use LO PATH DEG Thr. (10-5 to 10-9) to set the threshold for considering the incoming stream
degraded. This calculation uses the bit 1 and 2 of the V5 byte.
Enter the percentage of BBE (DEG Threshold) detected on the bit 1 and 2 of the V5 byte (LO) and
the number of errored seconds which are activating/deactivating a bad/good period.
Single Byte Rx - Tx
byte.
15 Bytes Rx - Tx
* Use Path Trace Expected to set the value expected on Byte J2.
* Use Path Trace Configured to set the value sent on Byte J2. Values lower than 7F
has been selected.
* Use Path Trace Transm. to enable/disable the Path Trace management. If Path Trace
has been disabled a value 00 is sent in all bytes.
* Use Path Trace Mism. Detection to enable/disable the issue of J2 mismatch alarm in
presence of a wrong path trace on the receive side.
* Use SL Mism Detect to enable/disable the detection of mismatch on the signal label (bit
5, 6 and 7 of the V5 byte) for the selected TU.
* Press APPLY.

.
Issue:1
NxSTM-1 Type 3 and STM-4 Type 2 Unit
To configure the LO VC operational parameters:

* Select the AUG (in case of STM-N Unit).
* Use TU filter to define the VCs level to configure (VC12, VC2, VC3, ALL).
* Define the TU selection criteria by clicking on the exclusive buttons SINGLE or MULT. in
the TU Sel. Mode field. MULT. selection allows to select (and configure) more than one
TU at the same time, SINGLE allows to select only one TU.
* Select the TU. The number and the type of displayed TU depending on the configured
frame structure.
The button UNIT LIMITATIONS defines the limitations for the configuration chosen.
See Also:
STM-N Port: configuring frame and supervisory unequipped state
* LO PATH DEG Count Mode to select the type of error rate evaluation mode (Poisson or
ETSI).
Use LO PATH DEG Thr. (10-5 to 10-9) to set the threshold for considering the incoming stream
degraded. This calculation uses: the bit 1 and 2 of the V5 byte for VC-12 and VC-2, the B3 byte for
the VC-3.

.
Issue:1

Enter the percentage of BBE (DEG Threshold) detected on the bit 1 and 2 of the V5 byte (VC-12
and VC-2) or on the B3 byte (VC-3) and the number of errored seconds which are
activating/deactivating a bad/good period.
* Use Mode (in the LO PATH-PROT SW CRITERIA field) to set the criteria for the low
order path protection switch of the selected TU.
NON INTRUSIVE
The switch is caused by the following alarms: TU_AIS, TU_LOP, LP_UNEQ, LP_TIM, LP_DEG,
LP_EXC. This is the most sensitive SNC Protection for low order VC.
INHERENT
The switch is caused by the following alarms: TU_AIS, TU_LOP. This is the least sensitive SNC
protection for low order VC.
The switch criteria for the SNC protection of the low order VC, can be enabled by the operator
(Apart from the TU_AIS and TU_LOP switch criteria).
* Use RDI on LP-TIM to enable/disable the LO-RDI indication to the line when a Low
* Use RDI on LP-Unequip enable/disable the LO-RDI indication to the line when a Low
Order - Payload Label Unequipped is detected.
* Use RDI on LP-EXC to enable/disable the LO-RDI indication to the line when an
excessive bit error ratio (>10-3) is detected.
Note RDI is sent only in LSU (Low Order Supervisory Unequipped) mode.
See Also:
Single Byte Rx - Tx
A single byte value is expected in the J1/J2 byte (path trace). A single byte value is sent into the
J1/J2 byte.
A 15-bytes value is expected in the J1/J2 byte. A single byte value is sent into the J1/J2 byte.
A single byte value is expected in the J1/J2 byte. A 15-bytes value is sent into the J1/J2 byte.
15 Bytes Rx - Tx
A 15-bytes value is expected in the J1/J2 byte. A 15-bytes value is sent into the J1/J2 byte.
* Use Path Trace Expected to set the value expected on Byte J1/J2.
* Use Path Trace Configured to set the value sent on Byte J1/J2. Values lower than 7F
has been selected.
Note Path Trace configured is sent only in LSU (Low Order Supervisory Unequipped)
mode.
See Also:

.
Issue:1
* Use Path Trace Transm. to enable/disable the Path Trace management.

* Use Path Trace Mism. Detection to enable/disable the issue of J1/J2 mismatch alarm in
presence of a wrong path trace on the receive side.
* Set the Alarm Detection state to enable/disable the detection of the LO-VC alarms.
IMPORTANT The detection of the TU-AIS and TU-LOP alarms is always active and it causes
the insertion of an AIS signal toward the matrix.
If the LO PATH-PROT SW CRITERIA Mode is set to NON INTRUSIVE or
PARTIAL NOT INTRUSIVE the Alarm Detection must be enabled.
* Press APPLY.
Path Trace Management
Depending on LSU and Alarm Detection state the Path Trace value displayed in the Received field
is:
n if there are no cross connections and LSU is disabled then "0xFFFFFFFF" value is
displayed;
n if there are cross connections but Alarm Detection is disabled then "0xFFFFFFFF" value is
displayed;
n if there are cross connections with Alarm Detection enabled but FROM side is not connected
then "0xFFFFFFFF" value is displayed;
In all other cases the actual value detected by the card is displayed.
See Also:
Port: configuration, STM-1 Type 2 Port: setting C2 mismatch detection state, STM-N
Port: configuring frame and supervisory unequipped state, STM-1 Port: setting HPOM
alarm suppression state
LPOM Ports: displaying LO VC operational parameter

Path (Action-VC Configuration-Read)
This option is used to read the LO VC operational parameter configured for the NxSTM-1, STM-16
T2 LPOM, STM-4 Unit Type 3, 63x2Mbit/s Unit, 4x34Mbit/s T-Mux Unit and 3x34/45Mbit/s Unit (for
the Type 3 Subrack).
See Also:
LPOM Ports: configuring LO VC operational parameter (DXC 41)
LPOM Ports: configuring LO VC operational parameter (DXC 41)

.
Issue:1

Path (Action-Frame and Supervisory Unequipped Config)
This option is available for the:
n NxSTM-1 Units;
n 4x140-155Mbit/s Units (configured as STM-1);
n STM-N Units (except STM-1 Type Standard).
It allows to configure the multiplexing structure for each VC-4 and to generate a supervisory
unequipped signal. Furthermore, the Frame Configuration window, displays channel information
relevant to the cross-connected sides (TO and FROM) and to the supervisory unequipped state
(Sup uneq).
NOTICE The frame structure option is available only for DXC 4/1 and DXC 4/4
1024x1024.
For DXC 4/1 the VC-4 frame can be structured at any level while for DXC 4/4
1024x1024 the VC-4 frame can be structured at VC-3 level only.
Note If no explicit configuration is given for a not cross-connected SDH port, High Order
Supervisory Unequipped signal is inserted by default. This state is automatically
disabled when the channel is connected and/or demultiplied.

.
Issue:1
To configure the frame structure of a STM-N channel:

* Select in the AUG Selection box the AUG to be multiplied/demultiplied by clicking on it.
The option ALL allows configuring in the same way all the AU frame, belonging to the STM-N port.
* Select in the Action field the Change Frame option.
The desired multiplexing structure configuration can be defined. A click on a not demultiplied
channel provokes its expansion to its lower order VCs. A click on an already exploded channel
causes the contraction of the lower order VCs.
* Press APPLY to confirm the configuration.
To configure the supervisory unequipped state of a STM-N channel:

* Select in the AUG Selection box the AUG that supervisory unequipped state has to be
modified.
The option ALL allows to configure in the same way all the AU frame, belonging to the STM-N port.
* Select in the Action field the Change Supervisory Uneq. option.
The desired Supervisory Uneq. state can be defined by clicking on the VC channel (the configured
state will be displayed in the window below the item Sup. Uneq.).
* Press APPLY to confirm the configuration.
Remind that:
a VC can be configured as Supervisory Unequipped only if it has not been demultiplied
or cross-connected;
a VC-12, VC-2 or VC-3 can be configured as Supervisory Unequipped only if the VC-4
channel which they belong is not cross-connected (this option is available for DXC 4/1
only);
by default the Supervisory Unequipped state for the Low Order VC is disabled (DXC 4/1
only);
it is not possible to demultiply a VC-4 belonging to a STM-16 or 4x140/155Mbit/s Unit
because these unit are able to handle VC-4 level only; in this case Change Frame
Action is not allowed;
it is not possible to demultiply a cross-connected channel. If the Change Frame Action
has been applied to a cross-connected channel (demultiplexing) or a channel containing
cross-connected channels (re-establishment of upper hierarchical level) in the row
relevant to the resulting channel/s, below the item FROM and/or TO (depending on the
type of cross-connection), the Busy indication will be displayed to remind the
impossibility to perform the selected operation. If the Busy indication has been ignored
pushing APPLY button a relevant message will be displayed.
Free item indicates that the relevant side is not cross-connected. Other items are
relevant to the type of cross-connections.
In a type 5 subrack it is possible to configure the frame structure of a worker channel/unit involved in
a MSP 1:N but the same change will be applied to all the other unit belonging to the MSP group.
In this case a warning message is displayed and a confirmation is required.

.
Issue:1
Type 6 subrack does not have this limitation.

See Also:
Port: configuration, STM-N Port: configuring frame and supervisory unequipped
state, Multiplexing Section Protection: configuring
Automatic C2 Configuration
Depending on the frame configuration this function sets the C2 value (signal label) automatically.
This means that configuring at LO a VC-4 frame previously not structured (using the Frame and
Supervisory Unequipped Config option) the related C2 configuration will be modified in TUG
Structured
Vice-versa its C2 configuration will be set as Equip (no spec)
However it is still possible to modify the C2 settings.
See Also:
Port: configuration, STM-N Port: configuring VC-4 operational parameter, STM-1 Type
2 Port: setting C2 mismatch detection state
The following table summarises the C2 configuration modification against the frame configuration
change.
Frame Configuration C2 Configuration
From To
VC-4 not LO structured VC-4 LO structured C2 Expected: TUG Structured
C2 Configured: TUG Structured (*)
VC-4 LO structured VC-4 not LO structured C2 Expected: Equip (no spec)
C2 Configured: Equip (no spec) (*)
C2 Mismatch Detection: Disabled
Note(*) This information is meaningful for STM-1 Type 2 Unit only. This is the
only unit allowing transmitted C2 value configuration.
NOTICE In case of MSP 1+1, any frame modification on the worker port is automatically
configured on the protection one too. As a consequence the related C2 settings
will be updated as well.

.
Issue:1
AU Group Definition
Path (Action-AU Group Definition)
This option is used to configure a concatenated AU traffic type. This functionality allows operating
on the network port, suitably to connect the high order container. The units that allow the
concatenated frame configuration are the STM-4 (Standard and Type 2) and STM-16 (Standard,
LPOM, MUX-4/3, DWDM).
By Local Operator is possible to set the high order concatenation on the specific port. By this
function is possible to:
n CREATE VIRTUAL CONCATENATION (it allows to create virual concatenations of AU).
n CREATE CONTIGUOUS CONCATENATION (it allows to create contiguous concatenations
of AU).
n DELETE VIRTUAL / CONTIGUOUS CONCATENATION (it allows to delete the
concatenations of AU).
n SET SUPERVISORY UNEQUIPPED (it indicates the enable state of supervisory
unequipped of single VC).
n SET VIRTUAL PARAMETERS (it allows to set other parameters useful for the management
of the Virtual Concatenation).

.
Issue:1
Restrictions
The following operations are not allowed:
n to configure a concatenation on TX side or Rx side only;
n to set up a concatenation different from: AU-4-4c, AU-4-4c/4v (for STM-16 MUX 4/3 only),
AU-4-16c/16v (for STM-16 MUX 4/3 only), and AU-3-3c, AU-3-12c, AU-3-12c/12v, AU-3-
48c/48v (for STM-16 MUX 4/3 in SONET mode only);
n to concatenate TUG-structured AUs;
n to concatenate a cross-connected AU, even if on one side (from or to) only;
n to concatenate channels which the Tandem Connection function has been previously
activated on;
n to set up a concatenation involving channels where performance monitoring has been set up
yet;
n set up a split cross-connection on a AU-nC cross-connection.
n With reference to AU-4 concatenations: at STM-16 traffic layer, to configure concatenations
where the head AU-4 index is different from 1, 5, 9 and 13;
n With reference to AU-3 concatenations: to set up a concatenation whose head AU-3 is not
the first within the AUG (for AU-3-3c) and moreover whose head AU-3 belongs to an AUG
whose index is different from 1, 5, 9, and 13 (for AU-3-12c, AU-3-12c/12v);
n to modify the Supervisory Unequipped enable state on cross-connected traffic.
Note that concerning management of AU-3-mC concatenated traffic, the STM-16 MUX 4/3 card will
convert such kind of traffic (line side) into the corresponding AU-4s (matrix side) as follows:
n an AU-3-3C concatenation will be mapped into a single AU-4;
n an AU-3-12C concatenation will be mapped into an AU-4-4C one;
n an AU-3-12C / 12V concatenation will be mapped into an AU-4-4C / 4V one;
n an AU-3-48C / 48V concatenation will be mapped into an AU-4-16C / 16V one.
To create a Virtual concatenation:

* Select CREATE VIRTUAL CONCAT.
* Select a group of AUG or AU considering the restrictions listed previously (head
AUG/AU).
* Press APPLY.
To create a Contiguous concatenation:

* Select CREATE CONT. CONCAT.
* Select a group of AUG or AU considering the restrictions listed previously (head
AUG/AU).
* Press APPLY.
To delete a Virtual / Contiguous concatenation:

* Select DELETE V. / C. CONCAT.
* Select only one AUG/AU of concatenation before created.

.
Issue:1
* Press APPLY.
Select SET SUPERVISORY UNEQUIPPED to change the state.
The state of the first AUG/AU of each group (head AUG/AU) will be the state of concatenated cross-
connection.
Note The modification of Supervisory Unequipped enable state on a concatenated AUG/AU
is significant only on the first AUG/AU, the AU Group configuration window marks the
modification on all AUG/AUs in the group, meaning the operation is valid on the whole
traffic.
To Set Virtual Parameters:

* Press SET VIRTUAL PARAMETERS.
* Select the group of AUG/AU.
* Create a virtual concatenation by means of CREATE VIRTUAL CONCAT. button.
* Choose one of four (sixteen) AUG previously concatenated.
The button
displays the list of alarms detected in the card.

After setting VIRTUAL PARAMETERS this window will appear:

.
Issue:1
* Set in J1 Mode the matrix side path trace definition between one of following values:
Single Byte Rx - Tx
A single byte is expected in the J1 byte coming from Matrix. A single byte value is sent into the J1
byte Matrix side.
15 Bytes Rx Single Tx
A 15 bytes value is expected in the J1 byte coming from Matrix. A single byte value is sent into the
J1 byte Matrix side.
Single Rx 15 Bytes Tx
A single byte is expected in the J1 byte coming from Matrix. A 15 bytes value is sent into J1 byte
Matrix side.
15 Bytes Rx - Tx
A 15 bytes value is expected in the J1 byte coming from Matrix.. A 15 bytes value is sent into J1
byte Matrix side.
* Set in J1 Expected Matrix the value expected on byte J1 Matrix side.
In J1 Received Matrix is possible to read the value received on byte J1 Matrix side.
In the fields LOM Defect Recovery Time, SQM Defect Issue Thr., SQM Defect Clear Thr. It is
possible to read the values before set in the Port Configuration for STM-N (VC-4 configuration
window).
See Also:
* By means of TIM Matrix Detection is possible to enable / disable the detection of the
Trace Identifier Mismatch coming from Matrix. (Only for Virtual concatenation).
* By means of AIS on TIM Mtx is possible to enable / disable the fault action of the Alarm
Identification Signal going to line in case of Trace Identifier Mismatch matrix side.
The field AIS on LOM controls the line side AIS insertion fault action when detecting a Loss of
Multiframe defect recostructing a contiguous concatenation from a virtual one.
The field AIS on SQM controls the line side insertion fault action when detecting a SQM defect
reconstructing a contiguous concatenation from a virtual one.
The field AIS on LOA controls the line side AIS insertion fault action when detecting a Loss of
Alignment defect recostructing a contiguous concatenation from a virtual one.
The field AIS on LOA Rec controls the line side AIS insertion fault action when detecting a
Recoverable Loss of Alignment defect recostructing a contiguous concatenation from a virtual one.
This four fields are set Enable by default.
* In the Differential Delay bar you can tune the delay between a reference VC-4 and
another VC-4-4v in the same multiframe. After this time after a Loss Of Alignment (LOA)
alarm will arise. The Differential Delay bar is divided in 128000 microsec in steps of 125
miscrosec.
The differential delay is set to Autoadaptive by default. The STM-16 MUX-4/3 card can
automatically recover the incoming delay of each VC-4 in a virtual concatenation to be
reconstructed in a time going from 0.125 to 250 ms.

.
Issue:1
If the differential delay is set to Manual, the card will wait for a VC-4 in a virtual concatenation up to
the delay set by user (128ms maximum due to hardware limitations).
IMPORTANT When converting an AU-4-Xv coming from matrix into a AU-4-Xc towards the
line, the following specific defects can be detected:
a Defect LOM: Loss Of Multiframe: each AU-4-Xv (a frame) belongs to a
group (a multiframe) of 256 virtually concatenated AUs. Each group has its own
identification (ID) into the H4 POH byte; if a received AU-4-Xv has an
unexpectded ID, a defect LOM is generated by the card;
b Defect SQM: Wrong Sequence Number: inside a 256 AU-4-Xv multiframe,
each of them carries a progressive number into the H4 POH byte; if the
sequence is broken, a SQM defect is issued;
c Defect LOA: Loss of Alignment: when creating a contiguous concatenation
from a virtual one, each AU-4 must fit into its correct position; if an AU-4 is not
received into the expected position, a LOA defect is detected.
See Also:
Concatenated Traffic Type
SONET STS-1 Setup

Path (Action-SONET STS-1 Setup)
This option is used to configure the operational parameters for the STS-1 channels managed by the
MUX 4/3 unit type. Moreover it is also possible to configure the parameters of the STS
concatenated traffic type (STS-3c, STS-12c, STS-48c).
NOTICE This option is available only for STM-16 MUX4/3 Unit Type and will be
accessible selecting, in the Port Configuration window during the creation of the
port, the SONET protocol mode.

.
Issue:1
To configure a SONET STS-1 operational parameter:

* Select the STS-3 relevant to the STS-1 to be configured.
The option ALL allows configuring in the same way the STS-1 channels belonging to all STS-3.
* Select, in the STS-1 sel. field, the STS-1 channel to be configured, or, in case of
concatenated traffic type, the STS-1 head channel.
* Use RDI on HO-TIM to enable/disable the HO-RDI indication to the line when a High
Order Path Trace Identifier Mismatch has been detected in Supervisory Unequipped
state.
* Use RDI on VC Unequip enable/disable the HO-RDI indication to the line when a High
Order -Payload Label Unequipped is detected in Supervisory Unequipped state..
* Use RDI on HO-EXC to enable/disable the HO-RDI indication to the line when an
excessive bit error ratio is detected on the bytes B3 in Supervisory Unequipped state.
* MS/HO/LO DEG Count Mode display the type of error rate evaluation mode previously
configured in the Port Configuration window (see "Port: configuring operational
parameter" subparagraph).
If in the port configuration window Poisson has been selected
-5 -9
Use PATH DEG Thr. (10 to 10 ) to set the threshold for considering the VC payload degraded on
the Virtual Containers. This calculation uses the byte B3.
If in the port configuration window ETSI has been selected
Enter the percentage of BBE (DEG Threshold) for the VC (HO PATH) and the number of errored

.
Issue:1

Single Byte Rx - Tx
byte in Supervisory Unequipped state.
A 15-bytes value is expected in the J1 byte. A single byte value is sent into the J1 byte in
Supervisory Unequipped state.
A single byte value is expected in the J1 byte. A 15-bytes value is sent into the J1 byte in
Supervisory Unequipped state.
15 Bytes Rx - Tx
A 15-bytes value is expected in the J1 byte. A 15-bytes value is sent into the J1 byte in Supervisory
Unequipped state.
* Use Path Trace (J1) Conf to set the value sent on Byte J1 in Supervisory Unequipped
state.
NOTICE Changing J1 Tx Mode (J1 Conf) on the head VC of a virtual concatenation

causes the modification of matrix side J1 Mode.
For STS-1 traffic type, the J1 mode set will be apply to all three STS-1
concerned that AUG.
Path Trace has been disabled a value 01 single byte is sent in Supervisory Unequipped
state.
* Use Mode (in the PATH-PROT SW CRITERIA field) to set the criteria for the path
protection switch of the selected channel.
NON INTRUSIVE
The switch is caused by the following alarms: AIS, LOP, UNEQ, TIM, DEG, EXC. This is the most
sensitive SNC Protection. The Alarm Suppresion must be disabled.
INHERENT
The switch is caused by the following alarms: AIS, LOP. This is the least sensitive SNC protection .
The switch criteria for the SNC protection of the VC, can be enabled by the operator (Apart from
the AIS and LOP switch criteria). The Alarm Suppresion must be disabled.

.
Issue:1
* Use Alarm Suppression State to enable/disable the monitoring of some path alarms
(UNEQ, TIM, DEG, EXC, RDI). The aim of this functionality is to reduce the amount of
alarms.
If the functionality is enabled (default disabled), the following alarms are not monitored:
HP-UNEQ, HP-TIM, HP-EXC, HP-DEG, HP-RDI for STS-3c, STS-12c or STS-48c traffic
type (AU-3-3c, AU-3-12c, AU-3-12c/12v, AU-3-48c/48v concatenations), LP-UNEQ, LP-
TIM, LP-EXC, LP-DEG, LP-RDI for STS-1 traffic type.
* Press APPLY.

.
Issue:1
Port Mode Setup

Path (Action-Port Mode Setup)
This option allows to choose a specified value for the port configured. The default value has been
set in NE Port Mode Setup field. Changing this state only the card involved will change the Port
Mode State.
* Select the value in the Port Mode Value.

* Press APPLY.
See Also:
Alarms: port mode

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: DISPLAYING INFORMATION

Path (Equipment Configuration-Synchronization-Sync Read)
This option displays a report of synchronization in use.
TS DYNAMIC STATE
contains information on the "Dynamic Holdover" status for TSU.
In particular, the current status of the internal system clock (T0) selector is reported (configured
mode).

.
Issue:1
SYNCHRONIZATION
ACTIVE SYSTEM SYNC SOURCE

contains information on the synchronisation in use for the main oscillator.
SYSTEM SYNC SOURCES PRIORITY CONF.
indicates information on the priorities of the synchronisation sources used for the main oscillator
and information about their operation. Synchronisation sources are listed and the quality level
received on byte S1 is shown for each of them.
ACTIVE EXTERNAL OUTPUT SYNC SOURCE
contains information on the synchronisation in use for the external output oscillator.
EXT. OUTPUT SYNC SOURCES PRIORITY CONF.
indicates information on the priorities of the synchronisation sources used for the external output
oscillator and information about their operation.
Synchronisation sources are listed, and the quality level received on byte S1 is shown for each of
them.

.
Issue:1
SYNCHRONIZATION
TIMING MARKER CONFIGURATION

displays information about the parameters used for switching the synchronisation sources in case
of fault.
SYSTEM SYNC OUTPUT
indicates the synchronisation mode configured for the main oscillator.
EXTERNAL OUTPUT
indicates the synchronisation mode configured for the external output oscillator.
EXTERN SOURCE INPUT FORMAT
displays information on the synchronisation parameters configured for the external clock inputs.
EXTERN SOURCE OUTPUT FORMAT
displays information on the synchronisation parameters configured for the external clock outputs.
Click on REFRESH to have an information updating and on CLOSE to quit the window.
See Also:
Synchronization: defining a port subrack as synchronization source,
Synchronization: defining priority table for the main oscillator, Synchronization:
defining priority table for secondary oscillator, Synchronization: configuring mode,
Operative States, Synchronization: setting PLL cut frequency
SYNCHRONIZATION: DEFINING A PORT SUBRACK AS

SYNCHRONIZATION SOURCE
Path (Equipment Configuration-Synchronization-Sync Setup-Subrack Sync Source)
This option is used to indicate the tributary port (STM-N and for the DXC 4/1 also the 2Mbit/s and
the 140Mbit/s T-Mux ports) used as synchronisation source.
IMPORTANT It is possible to configure a STM-16 MUX 4/3 SONET mode as synchronization

source, only if the Timing Marker is disabled. In this case Timing Marker wont be
available up to the synchronisation source will be deleted.

* Select on the Port Subrack to be used as synchronization source.
Synchronization: defining a port as synchronization source

Path (Action-Setup)
Use this option to select the port used for synchronization.
Only one port can be assigned as synchronization source for every port subrack.
IMPORTANT For Secondary Oscillator only 2Mbit/s (for DXC 4/1) and STM-N ports are
available.

.
Issue:1
SYNCHRONIZATION
To define a subrack as synchronisation source:

* Select the tributary unit to be used as synchronisation source.
* Select the port to be used as synchronisation source (Port Id).
* Use Quality Level to select the type of synchronisation quality level associated to a PDH
port.
Quality Level - G.811
0010 in bit 5-8 of S1 byte.
Quality Level - G.812 transit
Quality Level - G.812 local
Quality Level - G.813
Quality Level - Dont use for sync
* The ASSOCIATED DONT USE FOR SYNC box contains two push-buttons used to set
and reset the port that must not be used as Sync Source.

.
Issue:1
SYNCHRONIZATION
Synchronization: configuring DONT USE FOR SYNC

Use this option to define an STM-N port sending value dont use in the byte S1. This operation is
necessary to avoid timing loops between two stations when they are synchronised by means of
STM-N streams.
The STM-N port defined as dont use for sync wont be used for synchronisation of the equipment.
* Select the STM-N port.

* Press OK.
After having selected OK the system displays a message box to inform the user that modification
will be effective only after the APPLY push button in the previous window (Action-Setup) has been
pressed.
Synchronization: displaying port parameters

Path (Action-Read)
This option is used for displaying the port used as synchronization source and the synchronization
parameters defined for this port.
See Also:
Synchronization: defining a port as synchronization source, Operative States

.
Issue:1
SYNCHRONIZATION
Synchronization: removing a synchronization port

Path (Action-Delete)
Use this option to remove a port used as synchronization source.
A synchronization port can be removed only when it is not defined in the Synchronization Priority
Table.
To delete the synchronization source:

* Press APPLY.
See Also:
Synchronization: defining a port as synchronization source, Operative States
SYNCHRONIZATION: DEFINING PRIORITY TABLE FOR THE MAIN

OSCILLATOR
Path (Equipment Configuration-Synchronization-Sync Setup-Sync Priority Table-System)
This option is used to define a synchronisation priority table for the main oscillator (internal and line
clock).
In normal working conditions the equipment will use the highest priority source (with the best quality
level); if the main clock source is alarmed the equipment will use the next one available in the table.
If all the synchronisation sources defined in the table are not available the equipment automatically
operates in the holdover mode (i.e. equipment is using the last reference clock).
In the Active Sync Source box are indicated information on the active synchronisation source used
for the main oscillator.

.
Issue:1
SYNCHRONIZATION
In the STM-N sending QL <-- 1111 box are displayed all STM-1 ports associated to the Active
Sync Source which are sending the status dont use (all 1s in the byte S1).
The Minimum QL (present value) text box indicates the quality level of the synchronisation source
in use.
A window for the selection of the synchronisation priority is shown. On the right side is shown the list
of the available sources (SYNC SOURCES NOT in USE).
Subracks synchronisation sources available for selection have been previously defined using the
option Subrack Sync Source.
To define the synchronisation priority table:

* Select the synchronisation source to be assigned (e.g.: STM1-Opt.).
The selected source is displayed in reverse video and in the information box are shown the relevant
parameters.
* Move the selected synchronisation source to the desired Priority number (SYNC
SOURCES in USE).
The synchronisation source is moved from SYNC SOURCES NOT in USE to the selected position.
Repeat the above steps for all synchronisation sources to be get in use.
* Press APPLY.
See Also:
Synchronization: defining a port as synchronization source, Operative States,
Synchronization: setting PLL cut frequency

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: DEFINING PRIORITY TABLE FOR SECONDARY

OSCILLATOR
Path (Equipment Configuration-Synchronization-Sync Setup-Sync Priority Table-External
Output)
This option is used to define a synchronisation priority table for the external output oscillator.
In the Active Sync Source box are indicated information on the active synchronisation source used
for the secondary oscillator (external output).
in use.
To define the synchronisation priority table:

* Select a synchronisation source from the SYNC SOURCES NOT IN USE field (e.g.:
Ext_Source).
The selected source is displayed in reverse video and in the information box are shown the relevant
parameters.
* Move the selected synchronisation source to the desired Priority number (SYNC
SOURCES in USE).
The synchronisation source is moved from SYNC SOURCES NOT in USE to the selected position.
Repeat the above steps for all synchronisation sources to be get in use.
* Press APPLY.
See Also:
Synchronization: defining a port as synchronization source, Operative States,
Synchronization: setting PLL cut frequency

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: CONFIGURING MODE

Path (Equipment Configuration-Synchronization-Sync Setup-Sync Mode)
This option is used to select the type of synchronisation mode used for synchronising the internal
oscillator and the external synchronisation output.
To define the synchronisation mode:

* Use Timing Marker to enable/disable the management of the byte S1.
Disabled TM sent value is displayed only when Timing Marker is set to disabled.
It indicates the value sent on the byte S1 (dont use).
* If the Timing Marker has been enabled, define the Minimum accepted QL (Minimum
Synchronisation Quality Level accepted).
* Use Configured Mode (SYSTEM SYNC OUTPUT) to select the mode of
synchronisation for the internal oscillator.
Free Running
Equipment is synchronised using the internal oscillator.

.
Issue:1
SYNCHRONIZATION
Normal Revertive
Equipment is synchronised using a tributary port or an external clock source (slave). Equipment
restores the available highest priority synchronisation source after repair of a failure that caused
synchronisation sources to be switched.
Normal Not Revertive
Equipment is synchronised using a tributary port or an external clock source (slave). Equipment
does not restore the available highest priority synchronisation source.
No Switch
Sync Selection is forced on one configured sync source selectable from the scrollable list that
appears at the bottom
Internal Clock Disabled

Internal clock from the Control & Timing Subrack disabled (not yet available).
Forced Holdover
Sync Mode forced to holdover. Equipment is synchronised using the last reference clock.
* Select the WTR Period in half minutes. Value entered represents the time the equipment
waits to restore the synchronisation to the highest priority one. This information is enabled
only if the Revertive mode has been selected (Normal Revertive).
* Use Configured Mode (EXTERNAL OUTPUT) to select the mode of synchronisation for
the external output clock (only if needed).
Normal Revertive/Normal Not Revertive
See SYSTEM SYNC OUTPUT.
Locked To System Oscillator
External Output is synchronised using the clock generated by the main oscillator.
* Use Squelch to enable/disable the squelch of the external synchronisation sources in
output.
* Select the type of clock signal for the external synchronisation sources in input and in
output (EXTERN SOURCE INPUT FORMAT/EXTERN SOURCE OUTPUT FORMAT)
and assign the relevant Quality Level (only for the external sources in input). The signal
can be NRZ (kHz) or HDB3 (kbit).
Following the Configuration Mode selection (Free-running, Normal, ...) the Control Application will
automatically display the relevant priority configuration windows.
* Press FORWARD button to display the next dialog box and use BACKWARD to return
to the previous one.
The next dialog box is displayed if the operator has chosen Normal Revertive or Normal Not
Revertive for the System Oscillator. In the dialog box operator can select the priorities for the
synchronisation sources.

.
Issue:1
SYNCHRONIZATION
The next dialog box is displayed if it has been chosen Normal Revertive or Normal Not Revertive
for the External Output. In the dialog box operator can select the priorities for the synchronisation
sources.
* Press APPLY.

.
Issue:1
SYNCHRONIZATION
in use while the Minimum QL (to be config) value indicates the quality level configured in the
synchronisation mode management window
Note The quality level of the synchronization source in use (Minimum QL (present value))
has to match the minimum accepted level (Minimum accepted QL) configured in the
synchronization mode management window. In case of quality level mismatch
(Minimum QL (present value) worst than Minimum QL (to be config)) the
messages "Wrong Quality Level" will appear.
IMPORTANT After the system is synchronised using a valid reference clock source, verify the
correct operational mode of the internal PLL checking the PLL cut frequency.
See Also:
Synchronization: defining priority table for the main oscillator, Synchronization:
defining priority table for secondary oscillator, Synchronization: setting PLL cut
frequency
SYNCHRONIZATION: SWITCHING SYSTEM SYNCHRONIZATION

SOURCE
Path (Equipment Configuration-Synchronization-Sync Setup-Sync Source Switch-
System)
This option causes the manual switch of the sync source of the main oscillator generating the
synchronising signals for the System.
To switch the System Sync Source:

* Select the sync source being the destination of the switch command, in the Sync
Sources in Use table.
* Use Mode to select the command to be executed. The possible options are:
Manual
It causes the manual switch of the main oscillator sync source to the selected one, only if the
selected source has not problems. In case of failure in the switched sync source, the configured
synchronisation mode criteria are applied.
Clear
It clears the manual switch command. The configured synchronisation mode criteria are applied.
* Press APPLY.
See Also:
Synchronization: configuring mode

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: SWITCHING EXTERNAL OUTPUT

SYNCHRONIZATION SOURCE
Path (Equipment Configuration-Synchronization-Sync Setup-Sync Source Switch-External
Output)
This option causes the manual switch of the sync source of the secondary oscillator generating the
External Output synchronising signals.
To switch the External Output Sync Source:

* Select the sync source being the destination of the switch command, in the Sync
Sources in Use table.
* Use Mode to select the command to be executed. The possible options are:
Manual
It causes the manual switch of the main oscillator sync source to the selected one, only if the
selected source has not problems. In case of failure in the switched sync source, the configured
synchronisation mode criteria are applied.
Clear
It clears the manual switch command. The configured synchronisation mode criteria are applied.
* Press APPLY.
See Also:
Synchronization: configuring mode

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: CALIBRATING THE TIMING SELECTOR

OSCILLATOR UNIT
Path (Equipment Configuration-Synchronization-TS Subrack Calibration)
This option allows to calibrate the internal oscillator clock selecting a sync source as reference. This
operation should be performed periodically in order to adjust the internal oscillator clock.
The TSU calibration is not strictly necessary and the suggested period is 1 or 2 years.
IMPORTANT This option is available only if You are logged in as Supervisor.
To calibrate the Timing Selector Oscillator Unit:

* Select the Timing Selector/Oscillator unit to calibrate.
* Select on the synchronisation source used as reference (SYNC SOURCE SELECTION).
Only the synchronisation sources previously defined are made available.
* Press APPLY
See Also:
Operative States, Synchronization: setting PLL cut frequency

.
Issue:1
SYNCHRONIZATION
SYNCHRONIZATION: SELECTING THE TIMING SIGNAL ON TEST POINT

OF TS
Path (Equipment Configuration-Synchronization-Test Point)
This option allows to select the clock signal to be checked at the coaxial measurement point on the
front panel of the Timing Selector Oscillator Units.
To check the clock signals:

* Select on the Timing Selector/Oscillator unit to be checked.
* Use Test Point Output to select the clock signal to be checked.
The following values are available:

System Oscillator Frequency (38.88 MHz)
38.88 MHz clock signal generated by the main oscillator.
Internal Output Frequency (9.72 MHz)
9.72 MHz clock signal sent to port subracks and matrix subracks.
Ext. Out Osc. Frequency (22.528 MHz)
22.528 MHz clock signal generated by the secondary oscillator (for external output clock).
External Input - 1/2 (2048 kbit)
2048 kbit/s clock received from the external connector (1 or 2).

.
Issue:1
SYNCHRONIZATION
External Input - 1/2 (2048 kHz)

2048 kHz clock received from the external connector (1 or 2).
Internal Clock
Internal use only.
* Press APPLY.
SYNCHRONIZATION: SETTING PLL CUT FREQUENCY

Path (Equipment Configuration-Synchronization-PLL Cut Frequency)
This option is used to set the cut frequency of the PLL Low Pass Filter within the Timing Selector
Oscillator Unit.
The slave clock can be viewed as a low-pass filter for the differences between the actual input
phase and the ideal input phase of the reference (noise transfer).
Reccomendations G.812 and G.813 specifies the constraints for these filters. Consider that:
n G.812 Transit is the Type V;
n G.812 Local is the Type VI;
n G.813 is the SEC.
Cut frequency can be set separately for the three different types of timing Selector Oscillator Units
(G813, G812 Local, G812 Transit).
The default values for each Timing Selector type are:
G.812 Transit
0.1Hz
G.812 Local
1Hz
G.813
8.2Hz

.
Issue:1
SYNCHRONIZATION
To select the cut frequency:

* Select the desired value.
* Press APPLY.
SYNCHRONIZATION: RESTORING OOF SYNCHRONIZATION SOURCE

Path (Equipment Configuration-Synchronization-OOF Restoration)
When the system declares a synchronisation source as OOF (Out of Frequency) it is important to
note that this source will not be used again even if the synchronisation mode is "Normal Revertive".
This option is used to restore the synchronisation source that has been discharged. The procedure
will update the priority table and acknowledge the "discarded" synchronisation source as a valid
source.
In the "OOF Restoration" window are also displayed synchronisation information and the priority
tables for the system and the external output.
To restore a OOF synchronisation source:

* Select in the OOF SYNC SOURCES TO RESTORE field the OOF synchronisation
source to restore.
* Press the APPLY push button.

.
Issue:1
PROTECTION AND TEST
CT SUBRACK PROTECTION: DISPLAYING UNIT STATE

Path (Equipment Configuration-Protection-Controller & Timing Protection-Card Protection
Scheme)
This option is used to display the protection status of the different units present in the Control and
Timing Subrack. The type of protection available is 1+1.
The following units are protected in the Control and Timing Subrack:
a. Central Control Unit.
b. Memory Expansion Unit.
c. Communication and Q Interface Unit.
d. Timing-Selector Oscillator Unit.
To display the protection status of a unit:

* Select the unit which protection information has to be displayed.
* The system displays information relevant to the Working Unit (REQUESTED
RESOURCE).
Use the scroll-bars to display information relevant to the Protection Unit (PARTNER RESOURCE).
Note For Communication and Q Interface Unit protection remind to commission both unit.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
CT SUBRACK PROTECTION: SWITCHING

Path (Equipment Configuration-Protection-Controller & Timing Protection-Protection
Switch)
This option allows the switching of the Control and Timing Subrack units.
To switch a duplicated unit:

* Select the unit to be switched.
* Use Command Switch to select the type of command to be executed.
Note For the CCU and Mem Unit only Manual switch and Clear Command are available.
* Press APPLY.
Use REFRESH button to perform an update of the protection state (Protection role, Stand-by
state, Protection status, Operational state).
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
CT SUBRACK PROTECTION: DISPLAYING SIO LINE STATE

Path (Equipment Configuration-Protection-Controller & Timing Protection-SIO Line
Scheme)
This option is used to display the protection status of the serial lines (Serial Expansion Unit)
connecting Control and Timing Subrack to the other subracks (Matrix Subracks and Ports Subracks)
and to the Timing Selector Units.
* Select a Serial Expansion Unit.
A list of all serial lines in use (Line #) is displayed for both working and protection units (S1A and
S1B).
* Select the desired serial line (e.g.: Line_1).
In the Protection Information box are displayed information on the operational state of the
selected line for the working line (REQUESTED RESOURCE) and, clicking on the scroll bar, for the
protection line (PARTNER RESOURCE)
See Also:
Operative States
MATRIX SUBRACK PROTECTION: DISPLAYING

Path (Equipment Configuration-Protection-Matrix Protection-Protection Scheme)
This option is used to display the protection status of the Matrix Subracks. Matrix Subrack A is
protected 1+1 using Matrix Subrack B.
Only Not Revertive mode is available for Matrix Subrack.
Matrix Subrack A is used for normal operation (WORKER) and Matrix Subrack B (PROTECTION) is
used for protection.
See Also:
Operative States
MATRIX SUBRACK PROTECTION: SWITCHING

Path (Equipment Configuration-Protection-Matrix Protection-Protection Switch)
This option allows the Operator to switch from the worker Matrix (A) to the protection Matrix (B) and
vice-versa.
To switch a Matrix Subrack:

* Press APPLY.
Matrix Interface Units relevant to the switched Matrix Subrack (A or B) are also switched.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
PORT SUBRACK PROTECTION: SELECTION

Path (Equipment Configuration-Protection-Subrack Protection)
This option allows the Operator to select the types of protection managed in the Port Subracks.

* Select the Port Subrack.
IMPORTANT In case of 2xSTM-1 MSP or Card Protection make sure that the subrack
supports the protection type (Prot. Type Supp.).
Port Controller Protection: displaying

Path (Action-Port Controller Protection-Protection Scheme)
This option is used to display the protection status of the Port Controller Unit present in the Port
Subracks.
Port Controller Unit A (PCA) is used for normal operation (WORKER) and Port Controller Unit B
(PCB) is used for protection (PROTECTION).
See Also:
Operative States
Port Controller Protection: switching

Path (Action-Port Controller Protection-Protection Switch)
This option allows the Operator to switch a Port Controller and DCC Access Unit from normal
Worker side to Protection side and vice-versa.
To switch a Port Controller Unit:

* Press APPLY.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST

Path (Action-Multiplexing Section Protection-Protection Scheme-Create)
Path (Action-NxSTM1 MSP Protection-Protection Scheme-Create)
This option is used to select the type of protection (1+1 or N+1) used for the Optic/Mux Units (or
Electric/Mux Units).
In the following are described the composition rules for the MS Protection relevant to the different
subracks.
NOTICE Both worker and protection ports have to be equipped and configured.
Within a protection group the ports have to be configured with the same VC-4
operational parameters. Different MS and RS operational parameters are
allowed.
See Also:
Unit: equipping (DXC 4/1), Port: configuration
Type 5 subrack
STM-1 Unit:
In the 1+1 protection the first four tributaries (1 to 4), starting from the left side of the subrack, are
protected using tributaries in positions 5 to 8 (P1 is protected by P5, P2 is protected by P6, and so
on).
In the N+1 protection the tributary 9 is used to protect all the other tributaries (1 to 8).
Position
Protection Type
P1 P2 P3 P4 P5 P6 P7 P8 P9
STM-1 MSP 1+1
W1 W2 W3 W4 P1 P2 P3 P4
STM-1 MSP 1:N
W1 W2 W3 W4 W5 W6 W7 W8 P
W: Worker Unit P: Protection Unit
Note An STM-1 Type Standard cannot protect an STM-1 Type 2 and vice-versa; the worker
and protection unit must have the same configuration. Note that an STM-1 Optic/Mux
Unit can protect an STM-1 Electric/Mux Unit (of the same Type) and vice-versa.
The options available for the Type 5 port subrack are:
n one group of N+1 Protection (1<=N<=8);
n four groups of 1+1 Protection;
n M groups of 1+1 Protection and one group of N:1 Protection (N<=8-(Mx2)).
NOTICE Consider the following restriction:

- The protection channel must have the same port and frame configuration as
the protected one.

.
Issue:1
PROTECTION AND TEST
MSP and DXC Type III Protection (DXC 4/1 only)

On Type 5 Subrack consider the following limitations:
n A resource (port or accesses) can not be used, at the same time, as protection of both MSP
and DXC Type III protection.
n A resource (port or accesses) can not be defined, at the same time, both Worker and
Protection.
The only case in which both protection type are allowed is: a resource defined as worker in both
MSP and DXC Type III protection.
See Also:
Type 6 Subrack
IMPORTANT Make sure the Protection Type Supported by the subrack is the MSP (no
2XSTM-1 MSP1:N) or, in case of 2xSTM-1 MSP 1:N, the MSP (2XSTM-1
MSP1:N only)
See Also:
STM-4 Unit:
In the 1+1 protection the STM-4 Unit number 1 is protected by the STM-4 Unit number 6 and STM-
4 Unit number 3 is protected by the STM-4 Unit number 8. In the N+1 protection the STM-4 Unit
number 5 is used to protect all the other STM-4 units.
4xSTM-1 or 4x140-155Mbit/s Unit:
th th
In the 1+1 protection the n port of the Unit number 1 is protected by the n port of the Unit number
th th
6 and the n port of the Unit number 3 is protected by the n port of the Unit number 8. In the N+1
th th
protection the n port of the Unit number 5 is used to protect all the n ports of the other 4xSTM-1
or 4x140-155Mbit/s units.
IMPORTANT Different protection schemes on the same unit are not allowed.
This means that if on a 4xSTM-1 or 4x140-155Mbit/s Unit one port has been
protected with a 1+1 protection scheme, the other ports belonging to the same
unit can be protected only with a 1+1 protection scheme.
Protection Mode (Revertive/Not Revertive) and Type Unidirectional/Bidirectional)
can be different.
2xSTM-1 Unit:
th
In the 1+1 protection the n port of the first four Units (1 to 4), starting from the left side of the
th th
subrack, is protected using the n port of the Units in positions 5 to 8. In the N+1 protection the n
th
port of the Unit number 5 is used to protect all the n ports of the 2xSTM-1 units inserted in the
slots number 1, 3, 6 and 8.

.
Issue:1
PROTECTION AND TEST
The following table summarises the possible Type 6 port subrack configurations:
Position
Protection Type
P1 P2 P3 P4 P5 P6 P7 P8
STM-4; 4XSTM-1;
4XSTM-1/140Mbit/s W1 W2 P1 P2
MSP 1+1
STM-4; NXSTM-1*;
4XSTM-1/140Mbit/s W1 W2 P W3 W4
MSP 1:N
2xSTM-1 MSP 1+1 W1 W2 W3 W4 P2 P1 P4 P3
W: Worker Unit P: Protection Unit
*: 4XSTM-1 and 2XSTM-1 Units
Different protection architectures (at unit level) are allowed.

- In case of 4x140-155Mbit/s Protection the Port Mode of the involved ports
must be the same.
- Due to different configurable parameter a 4x140-155Mbit/s Unit can not protect
a 4xSTM-1 Unit (and vice-versa).
- If the MSP 1+1 architecture is required the protection units accesses 1
(MAC and MAD Accesses for DXC 4/1, MAB and MAD Accesses for DXC
4/4) have to be not equipped.

.
Issue:1
PROTECTION AND TEST
Type 6E Subrack
STM-4 Unit:
In the MSP 1+1 protection the STM-4 Units number 1, 2, 5, 7, 8 are protected respectively by the
STM-4 Units number 3, 4, 6, 9 and 10. It is possible to configure two groups of MSP 1:N and 1:M
(N+M< 8) where the protection units have to be slot number 5 and/or 6.
4xSTM-1/ 2xSTM-1 or 4x140-155Mbit/s Unit:
th th
In the 1+1 protection the n port of the units number 1, 2, 5, 7, 8 is protected respectively by the n
port of the units number 3, 4, 6, 9 and 10. It is possible to configure two groups of MSP 1:N and
th
1:M (N+M< 8) where the n port of the units number 1, 2, 3, 4, 7, 8, 9 and 10 can be protected by
th
the n port of the number 5 and/or 6.
Note For DXC 4/4 using a MSP 1+1 protection scheme P5 and P6 are not configurable.
Position
Protection Type
P1 P2 P3 P4 P5 P6 P7 P8 P9 P10
No protection
STM-4 /2xSTM-1
Opt. W W W W W W W W W W
4x(STM-1
El./140Mbit/s)
1:N CARD
PROTECTION W1 W2 W3 W4 P ----- W5 W6 W7 W8
4xSTM-1
El./140Mbit/s
(N<8)
MSP 1:N
STM-4 /2XSTM-1 W W W W Pa Pb W W W W
Opt. (N<8)
MSP 1+1
STM-4 /2xSTM-1
Opt. W1 W2 P1 P2 W3 P3 W4 W5 P4 P5
4x(STM-1
El./140Mbit/s)
W: Worker Unit P: Protection Unit M.A.: Matrix Accesses
Note P5 and P6 are the resources for 1:N protection schemes and can protect all the other
units in worker. They can not protect themselves except for 1+1 protection scheme.
IMPORTANT According to the Matrix Accesses scheme, different protection architectures are
supported.

- In case of 4x140-155Mbit/s Protection the Port Mode of the involved ports
must be the same.
- Due to different configurable parameter a 4x140-155Mbit/s Unit can not protect
a 4xSTM-1 Unit (and vice-versa).

.
Issue:1
PROTECTION AND TEST
- If the MSP 1+1 architecture is required the protection units accesses have to be
not equipped.
See Also:
Type 7 Subrack
STM-16 Unit:
In the type 7 subrack only two STM-16 Unit can be equipped therefore only 1+1 MSP is available.
The first STM-16 Unit, starting from the left side of the subrack, is protected using the second STM-
16 Unit
The options available for the Type 7 port subrack are:
n one group of 1+1 Protection.

- If the MSP 1+1 architecture is required the protection unit accesses
(MAC, MAD, MAG and MAH Accesses for DXC 4/1, MAB, MAD, MAF and
MAH Accesses for DXC 4/4) must not be equipped.
- The protection channel must have the same frame configuration as the
protected one and must not be cross-connected.
Type 7E Subrack
STM-16 Unit:
In the 1+1 protection the STM-16 Units number 1 and 3 are protected respectively by the STM-16
Units number 2 and 4, while unit number 5 is not protected. In the N+1 protection the STM-16 Unit
number 5 is used to protect all the other STM-16 units.
Position
Protection Type
P1 P2 P3 P4 P5
NO PROTECTION W W W W
MSP 1+1 W1 P1 W2 P2 W
MSP 1:N W1 W2 W3 W4 P
IMPORTANT According to the Matrix Accesses scheme, different protection architectures are
supported.
Note The STM-16 MUX 4/3 does not support MSP 1:N protection. If the card is configured
in Sonet mode is possible to do only MSP 1+1 unidirectional.
The STM-16 MUX 4/3 can be protected only by another STM-16 MUX 4/3.
See Also:

.
Issue:1
PROTECTION AND TEST

.
Issue:1
PROTECTION AND TEST
To define a MSP Protection:

* Select the tributary unit to be protected (one of the tributaries in positions 1 to 4).
Make sure that the port used for protection has been configured using the Port Management, VC-4
Configuration and Frame and Supervisory Unequipped Configuration options (with exception of
STM-1 Type Standard).
* Use Protection Mode to select the type of operation.
* Use Protection Type to select the type of protection needed.
According to the involved unit different items will be available:
STM-1 Unit:
1+1 Unidirectional
To enable the 1+1 unidirectional protection.
1+1 Bidirectional
To enable the 1+1 bidirectional protection.
N+1 Bidirectional
To enable the 1:N bidirectional protection (with N <= 4).
NxSTM-1 Unit:
NxSTM-1 MSP 1+1 Unidir

NxSTM-1 MSP 1+1 Bidir
NxSTM-1 MSP N+1Bidir
To enable the 1:N bidirectional protection.
STM-4 Unit:
STM-4 MSP 1+1 Unidir

STM-4 MSP 1+1 Bidir
STM-4 MSP 1:N Bidir
To enable the 1:N bidirectional protection (with N <= 4).
STM-16 Unit:

STM-16 MSP 1+1 Bidir
STM-16 MSP 1+1 Unidir (FE Sign)
To enable the 1+1 unidirectional protection with proprietary Far-End status Signalling (for DXC 4/4
512x512 only).
This functionality allows to send a "switching signal" (on K2 byte) when a SF/SD condition is
detected, at the same time, on both worker and protection line.

.
Issue:1
PROTECTION AND TEST
IMPORTANT STM-16 interfaces unidirectional MSP 1+1 with proprietary Far-End status
signalling can be realised only if the connected far-end equipment supports the
relevant protocol.
* In case of NxSTM-1 Unit, select in the PORT field the port to be protected.
* Use MSP Chan Prio. to define the priority (Low or High) for SF and SD switching criteria
for every protected channel.
* Assign the APS Channel number (this field will be displayed only if N+1 Bidirectional
"Protection Type" has been selected), relevant to the selected protected channel, to
define a hierarchy among peer MSP Channel Priority (1 is the highest priority).
This means that if conditions of the same level are detected at the same time on different
protected channels having the same MSP Chan Prio., the channel with the lowest APS
Channel number takes priority.
Note This parameter acts as "MSP channel identifier" therefore in a MSP group same APS
Channel are not allowed even if the involved channel have different MSP Channel
Priority (MSP Chan Prio.).
Note If a unit is a synchronization source and is MSP 1:N Protected, it issues a "DO NOT
USE FOR SYNC" as quality level (byte S1) to prevent timing loops.
* Use SNCP-MSP Priority exclusive button to define which protection switch will have
precedence in case of simultaneous activation of MSP and SNCP on Type 5 / 6 / 6E / 7 /
7E subracks.
If MSP is selected no SNCP switch will take place, otherwise, selecting SNCP both
protections will be activated.
Note This setting will be applied to all the MSP protected STM-N of the selected subrack.
* Press APPLY.
The system automatically assigns the tributary unit used as protection unit.
Repeat same procedure for all STM-N Tributary Units to be protected N+1.
In the SUBRACK <shelf num> PROTECTION SCHEME box are displayed the type of protection
selected and the tributary units used.
The PROTECTION Information box displays information on the operational state of the working
and protection units.
See Also:
Port: configuration, STM-N Port: configuring frame and supervisory unequipped
state, STM-N Port: configuring VC-4 operational parameter

.
Issue:1
PROTECTION AND TEST
Multiplexing Section Protection: displaying

Path (Action-Multiplexing Section Protection-Protection Scheme-Read)
This option is used to display information about an existing MSP Protection (Protection Mode,
Protection Type, etc.) used for the Electric/Mux Units (or Optic/Mux Units).
To display information about a MSP Protection:

* Select the tributary unit.
* In case of NxSTM-1 Unit, select the port in the PORT field.
In the SUBRACK <shelf num> PROTECTION SCHEME box are displayed all 1+1 and N+1
protections enabled in the subrack.
In the PROTECTION Information box are displayed information on the operational state of the
working and protection units.
See Also:
Multiplexing Section Protection: configuring, Operative States
Multiplexing Section Protection: removing

Path (Action-Multiplexing Section Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected Electric/Mux Unit (or Optic/Mux
Unit).
To delete a MSP protection:

* Select the tributary unit whose protection must be removed.
* Press APPLY.
See Also:
Multiplexing Section Protection: modifying

Path (Action-Multiplexing Section Protection-Protection Scheme-Modify)
This option is used to modify the Protection Mode (Revertive/Not Revertive) of an existing 1+1 MSP
Protection.
NOTICE This option is available for Type 6, 6E, 7 and 7E subracks only.
To modify a MSP Protection:

* Use Protection Mode to select the type of operation.
* Press APPLY.
See Also:

.
Issue:1
PROTECTION AND TEST
Multiplexing Section Protection: switching

Path (Action-Multiplexing Section Protection-Protection Switch)
This option allows the Operator to switch a MSP protection from the worker unit to the protection
unit and vice-versa.
To switch a MSP protection:

* Select the tributary unit to be switched (Worker or Protection).
Operator can select either a working unit or protection unit for the 1+1 protection. For the N+1
protection Operator must select the worker unit only.
* In case of NxSTM-1 Unit, select in the PORT field the port to be protected.
* Press APPLY.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
NxSTM-1 Unit Protection: configuring

Path (Action-NxSTM1 Card Protection-Protection Scheme-Create)
This option is used to protect the NxSTM-1 or 4x155-140Mbit/s Units. In the N+1 protection the
tributary in position 5 is used to protect all the other tributaries (1,3,6 and 8).
IMPORTANT The protection unit ports has to be "not configured".
To define a Unit Protection:

* Select the NxSTM-1 or 4x155-140Mbit/s Unit to be protected (one of the tributaries in
positions 1,3,6 or 8).
* Use Protection Mode to select the Revertive/Not Revertive mode of the protection.
* Press APPLY.
Repeat same procedure for all NxSTM-1 Unit to be protected N+1.
See Also:
Operative States, Type 6 Subrack: equipping
NxSTM-1 Unit Protection: displaying information

Path (Action-NxSTM1 Card Protection-Protection Scheme-Read)
This option is used to display information on the protection used for the NxSTM-1 or 4x155-
140Mbit/s Units.
To display information about a NxSTM-1 or 4x155-140Mbit/s Unit Protection:

The system displays information on the unit involved in the protection.
See Also:
NxSTM-1 Unit Protection: configuring, Operative States
NxSTM-1 Unit Protection: removing

Path (Action-NxSTM1 Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected NxSTM-1 or 4x155-140Mbit/s
Unit.
To delete a NxSTM-1 or 4x155-140Mbit/s Unit Protection:

* Select the NxSTM-1 or 4x155-140Mbit/s Unit whose protection has to be removed.
* Press APPLY.
See Also:
NxSTM-1 Unit Protection: configuring, Operative States

.
Issue:1
PROTECTION AND TEST
NxSTM-1 Unit Protection: switching

Path (Action- NxSTM1 Card Protection-Protection Switch)
This option allows the Operator to switch traffic from the worker unit to the protection unit and vice-
versa.
To switch a unit protection:

* Select the NxSTM-1 or 4x155-140Mbit/s Unit to be switched (Worker).
* Press APPLY.
Use REFRESH button to perform an update of the protection state (PROTECTION Information).
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
63x2Mbit/s Unit Protection: configuring

Path (Action-63x2Mb Card Protection-Protection Scheme-Create)
This option is used to protect the 63x2Mbit/s Units. The protection scheme is N+1: the tributary in
position 6 is used to protect all the other tributaries (1,4,7 and 10).
IMPORTANT The protection unit ports have to be "not configured".

* Select the 63x2Mbit/s Unit to be protected (one of the tributaries in positions 1, 4, 7 or
10).
* Press APPLY.
Repeat same procedure for all 63x2Mbit/s Unit to be protected N+1.
See Also:
63x2Mbit/s Unit Protection: displaying information

Path (Action-63x2Mb Card Protection-Protection Scheme-Read)
This option is used to display information on the protection used for the 63x2Mbit/s Units.
To display information about a 63x2Mbit/s Unit Protection:

See Also:
63x2Mbit/s Unit Protection: configuring, Operative States
63x2Mbit/s Unit Protection: removing

Path (Action-63x2Mb Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 63x2Mbit/s Unit.
To delete a 63x2Mbit/s Unit Protection:

* Select the 63x2Mbit/s Unit whose protection has to be removed.
* Press APPLY.
See Also:

.
Issue:1
PROTECTION AND TEST
63x2Mbit/s Unit Protection: switching

Path (Action-63x2Mb Card Protection-Protection Switch)
versa.

* Select the 63x2Mbit/s Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
4x34Mbit/s T-Mux Unit Protection: configuring

Path (Action-4x34-TMUX Card Protection-Protection Scheme-Create)
This option is used to protect the 4x34Mbit/s T-Mux Units. Two N+1 protection schemes can be
configured:
1. the tributary in position 6 can be used to protect all the tributaries in position 1, 4, 7 and 10;
NOTICE The same positions can be used for the 63x2Mbit/s Units.
2. the tributary in position 5 can be used to protect all the tributaries in position 2, 3, 8 and 9.
IMPORTANT The protection unit ports have to be "not configured".

* Select the 4x34Mbit/s T-Mux Unit to be protected (one of the tributaries in positions 1, 4,
7 or 10.
* Press APPLY.
Repeat same procedure for all 4x34Mbit/s T-Mux Unit to be protected N+1.
See Also:
4x34Mbit/s T-Mux Unit Protection: displaying information

Path (Action-4x34-TMUX Card Protection-Protection Scheme-Read)
This option is used to display information on the protection used for the 4x34Mbit/s T-Mux Units.
To display information about a 4x34Mbit/s T-Mux Unit Protection:


.
Issue:1
PROTECTION AND TEST
See Also:
4x34Mbit/s T-Mux Unit Protection: configuring, Operative States
4x34Mbit/s T-Mux Unit Protection: removing

Path (Action-4x34-TMUX Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 4x34Mbit/s T-Mux Unit.
To delete a 4x34Mbit/s T-Mux Unit Protection:

* Select the 4x34Mbit/s T-Mux Unit whose protection has to be removed.
* Press APPLY.
See Also:
4x34Mbit/s T-Mux Unit Protection: switching

Path (Action-4x34-TMUX Card Protection-Protection Switch)
versa.

* Select the 4x34Mbit/s T-Mux Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
1x45Mbit/s T-Mux Unit Protection: configuring

Path (Action-45-TMUX Card Protection-Protection Scheme-Create)
This option is used to protect the 1x45Mbit/s Tributary Units. In the 1x45Mbit/s T-Mux Unit protection
(1+1) the tributaries in the even positions are used to protect the tributaries in the odd positions (the
tributary in position 2 protects the tributary in position 1, etc.).

* Select the 1x45Mbit/s Tributary Unit to be protected (one of the tributaries in positions 1,
3, 5, 7).
* Press APPLY.
Repeat same procedure for all 1x45Mbit/s Tributary Unit to be protected (1+1).
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
1x45Mbit/s T-Mux Unit Protection: displaying information

Path (Action-45-TMUX Card Protection-Protection Scheme-Read)
This option is used to display information on the protection used for the 1x45Mbit/s T-Mux Units.
To display information about a 1x45Mbit/s T-Mux Unit Protection:

The system displays information on the tributary unit involved in the protection.
See Also:
1x45Mbit/s T-Mux Unit Protection: removing

Path (Action-45-TMUX Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 1x45Mbit/s T-Mux Unit.
To delete a 1x45Mbit/s T-Mux Unit Protection:

* Select the 16x2Mbit/s Tributary Unit whose protection must be removed.
* Press APPLY.
See Also:
1x45Mbit/s T-Mux Unit Protection: switching

Path (Action-45-TMUX Card Protection-Protection Switch)
versa.

.
Issue:1
PROTECTION AND TEST

* Select the 1x45Mbit/s T-Mux Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
2Mbit/s Unit Protection: configuring

Path (Action-2Mb Card Protection-Protection Scheme-Create)
This option is used to protect the 16x2Mbit/s Tributary Units. In the N+1 protection the tributary in
position 9 is used to protect all the other tributaries (1 to 8).

* Select the 16x2Mbit/s Tributary Unit to be protected (one of the tributaries in positions 1
to 8).
* Use Protection Mode to select the Revertive mode of the protection.
* Press APPLY.
Repeat same procedure for all 16x2Mbit/s Tributary Unit to be protected N+1.
IMPORTANT In case of N+1 protection group the higher unit slot number has the maximum
priority than other.
See Also:
Operative States
2Mbit/s Unit Protection: displaying information

Path (Action-2Mb Card Protection-Protection Scheme-Read)
This option is used to display information on the protection used for the 16x2Mbit/s Tributary Units.
To display information about a 16x2Mbit/s Unit Protection:

The system displays information on the tributary unit involved in the protection.
See Also:

.
Issue:1
PROTECTION AND TEST
2Mbit/s Unit Protection: removing

Path (Action-2Mb Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 16x2Mbit/s Tributary Unit.
To delete a 2Mbit/s Unit Protection:

* Select the 16x2Mbit/s Tributary Unit whose protection must be removed.
* Press APPLY.
See Also:
2Mbit/s Unit Protection: switching

Path (Action-2Mb Card Protection-Protection Switch)
versa.

* Select the 16x2Mbit/s Tributary Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
4x34Mb/s Videocodec Unit Protection: configuring

Path (Action-4x34Mb VC Card Protection-Protection Scheme-Create)
This option is used to protect the 4x34Mbit/s Videocodec Tributary Units. The type of protection is
the 1+1 protection of the tributary unit (P2 protects P1 and P6 protects P5).
To define a 4x34Mb Videocodec Unit Protection:

* Select the 4x34Mbit/s Tributary Unit to be protected.
* Use Protection Mode to select the Not Revertive mode of the protection.
Note Only Not Revertive mode is available.
* Press APPLY.
See Also:
Operative States
4x34Mb/s Videocodec Unit Protection: displaying information

Path (Action-4x34Mb VC Card Protection-Protection Scheme-Read)
This option is used to display the protections used for the 4x34Mbit/s Videocodec Tributary Units.
To display information about a 4x34Mb/s Videocodec Unit Protection:

The system displays information on both tributaries involved in the unit protection.
See Also:
Operative States, 4x34Mb/s Videocodec Unit Protection: configuring
4x34Mb/s Videocodec Unit Protection: removing

Path (Action-4x34Mb VC Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 34Mbit/s Tributary Unit.
To delete a 4x34Mb/s Card Protection:

* Select the 4x34Mbit/s Videocodec Tributary Unit of which protection must be removed.
* Press APPLY.
See Also:
Operative States, 4x34Mb/s Videocodec Unit Protection: configuring

.
Issue:1
PROTECTION AND TEST
4x34Mb/s Videocodec Unit Protection: switching

Path (Action-4x34Mb VC Card Protection-Protection Switch)
This option allows the Operator to switch traffic from the worker to the protection unit and vice-versa.
To switch a 4x34Mb unit protection:

* Select the 4x34Mbit/s Videocodec Tributary Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
3x34-45Mbit/s Unit Protection: configuring

Path (Action-3x34/45Mb Card Protection-Protection Scheme-Create)
This option is used to protect the 3x34 or 3x45Mbit/s Tributary Units.
NOTICE If protection card is providing service, performance data collection is stopped

and all counters are no more updated.
Type 2 Subrack
The type of protection is the 1+1 protection of the tributary unit (P2 protects P1 and P6 protects P5).
IMPORTANT The unit protection wont be applicable if the line protection is already set.
Type 3 Subrack
The type of protection is the N+1: the tributary in position 6 is used to protect the tributaries in
position 1, 4, 7 and 10, the tributary in position 5 is used to protect the tributaries in position 2, 3, 8
and 9.

.
Issue:1
PROTECTION AND TEST
To define a 3x34-45Mb Unit Protection:

* Select the 3x34 or 3x45Mbit/s Tributary Unit to be protected.
* Use Protection Mode to select the Not Revertive mode of the protection.
* Press APPLY.
See Also:
Operative States
3x34-45Mbit/s Unit Protection: displaying information

Path (Action-3x34/45Mb Card Protection-Protection Scheme-Read)
This option is used to display the protections used for the 3x34Mbit/s or 3x45Mbit/s Tributary Units.
To display information about a 3x34-45Mbit/s Unit Protection:

The system displays information on both tributary involved in the unit protection.
See Also:
3x34-45Mbit/s Unit Protection: configuring, Operative States
3x34-45Mbit/s Unit Protection: removing

Path (Action-3x34_45Mb Card Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 34Mbit/s or 3x45Mbit/s Tributary
Unit.
To delete a 3x34-45Mbit/s Unit Protection:

* Select the 3x34-45Mbit/s Tributary Unit of which protection must be removed.
* Press APPLY.
See Also:

.
Issue:1
PROTECTION AND TEST
3x34-45Mbit/s Unit Protection: switching

Path (Action-3x34_45Mb Card Protection-Protection Switch)
This option allows the Operator to switch traffic from the worker to the protection unit and vice-versa.
To switch a 3x34-45Mb unit protection:

* Select the 3x34Mbit/s Tributary Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
3x34-45Mbit/s Line Protection: configuring

Path (Action-3x34_45Mb Line Protection-Protection Scheme-Create)
This option is used to protect the 3x34 or 3x45Mbit/s Tributary lines. The type of protection is the
1+1 protection of the tributary line managed by the tributary unit and the Port Control Unit.
IMPORTANT The line protection wont be applicable if the unit protection is already set.
IMPORTANT The configuration state of the 34-45Mb protection unit must be Equipped only.
To define a 3x34-45Mb Line Protection:

* Select the 3x34 or 3x45Mbit/s Tributary Unit to be protected.
* Select the channel to be protected or All to protected every single channel.
* Press APPLY.
Note Only Not Revertive Protection Mode is available.
See Also:

.
Issue:1
PROTECTION AND TEST
3x34-45Mbit/s Line Protection: displaying information

Path (Action-3x34_45Mb Line Protection-Protection Scheme-Read)
This option is used to display the protections used for the 3x34-45Mbit/s Tributary Units.
To display information about a 3x34-45Mbit/s Line Protection:

* Select the 3x34 or 3x45Mbit/s Tributary Unit.
* Select the channel (or All if every single channel is protected).
The system displays information on both tributaries involved in the unit protection.
See Also:
3x34-45Mbit/s Line Protection: configuring, Operative States
3x34-45Mbit/s Line Protection: removing

Path (Action-3x34_45Mb Line Protection-Protection Scheme-Delete)
To delete a 3x34-45Mbit/s Line Protection:

* Select the 3x34-45Mbit/s Tributary Unit of which protection must be removed.
* Press APPLY.
See Also:
3x34-45Mbit/s Line Protection: configuring, Operative States

.
Issue:1
PROTECTION AND TEST
3x34-45Mbit/s Line Protection: switching

Path (Action-3x34_45Mb Line Protection-Protection Switch)
This option allows the Operator to switch from the WORKER to the PROTECTION line and vice-
versa.
To switch a 3x34-45Mb line protection:

* Select the 3x34-45Mbit/s Tributary Unit of which lines have to be switched. (Worker).
* Select the channel to be switched or All for every single channel.
* Press APPLY.
Use REFRESH button to perform an update of the protection state.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
140Mbit/s Line Protection: configuring

Path (Action-140Mb Line Protection-Protection Scheme-Create)
This option is used to protect the 140Mbit/s Tributary Units (1+1 protection). Remind that in the 1+1
protection (Type 5 Subrack) the first four tributaries (1 to 4), starting from the left side of the subrack,
are protected using tributaries in positions 5 to 8 (1+1).
To define a 140Mb Line Protection:

* Select the 140Mbit/s Tributary Unit to be protected.
* Use Protection Mode to select the protection operation type.
* Press APPLY.
Only 1+1 140Mbit/s line protection type is available (140Mb PDH 1+1).
See Also:
Operative States
140Mbit/s Line Protection: displaying information

Path (Action-140Mb Line Protection-Protection Scheme-Read)
This option is used to display the 140Mbit/s Tributary Units protection information.
To display information about the 140Mbit/s Line Protection:

* Select the 140Mbit/s Tributary Unit.
See Also:
140Mbit/s Line Protection: configuring, Operative States
140Mbit/s Line Protection: removing

Path (Action-140Mb Line Protection-Protection Scheme-Delete)
To delete a 140Mbit/s Line Protection:

* Select the 140Mbit/s Tributary Unit whose protection must be removed.
* Press APPLY.
See Also:
140Mbit/s Line Protection: configuring, Operative States

.
Issue:1
PROTECTION AND TEST
140Mbit/s Line Protection: switching

Path (Action-140Mb Line Protection-Protection Switch)
This option allows the Operator to switch from the worker to the protection line and vice-versa.
To switch a 140 Mb unit protection:

* Select the 140Mbit/s Tributary Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
140Mb T-Mux Line Protection: configuring

Path (Action-TMUX140 Line Protection-Protection Scheme-Create)
This option is used to protect the 140Mbit/s T-Mux Tributary Units (1+1 protection). Remind that in
the 1+1 protection (Type 5 Subrack) the first four tributaries (1 to 4), starting from the left side of the
subrack, are protected using tributaries in positions 5 to 8 (1+1).
To define a 140 Mbit/s T-Mux Line Protection:

* Select the 140Mbit/s T-Mux Tributary Unit to be protected.
* Use Protection Mode to select the protection operation type (Not Revertive/ Revertive).
* Press APPLY
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
140Mbit/s T-Mux Line Protection: displaying information

Path (Action-TMUX140 Line Protection-Protection Scheme-Read)
This option is used to display the 140Mbit/s T-Mux Tributary Units protection information.
To display information about the 140Mbit/s T-Mux Line Protection:

* Select the 140Mbit/s T-Mux Tributary Unit.
See Also:
140Mb T-Mux Line Protection: configuring, Operative States
140Mbit/s T-Mux Line Protection: removing

Path (Action-TMUX140 Line Protection-Protection Scheme-Delete)
This option is used to remove the protection assigned to a selected 140Mbit/s T-Mux Tributary Unit.
To delete a 140Mbit/s T-Mux Line Protection:

* Select the 140Mbit/s T-Mux Tributary Unit of which protection must be removed.
* Press APPLY.
See Also:
140Mbit/s T-Mux Line Protection: switching

Path (Action-TMUX140 Line Protection-Protection Switch)
This option allows the Operator to switch from the worker line to the protection unit and vice-versa.

.
Issue:1
PROTECTION AND TEST
To switch a 140Mbit/s T-Mux Line Protection:

* Select the 140Mbit/s T-Mux Tributary Unit to be switched (Worker).
* Press APPLY.
See Also:
Operative States
DXC TYPE THREE PROTECTION: SELECTION

Path (Equipment Configuration-Protection-DXC TYPE III Protection)
DXC type III functionality protects a VC-4 channel containing LO-VCs cross-connected.
It is possible to protect all LO-VCs contained in a VC-4 of a STM-n TUG structured (VC-4 worker)
with the LO-VCs contained in the same position in another VC-4 of a STM-n TUG structured (VC-4
protection).
Basically this kind of trail protection provides VC-4 SNC-P and LO cross-connections. As a
consequence the LO channels belonging to the protected VC-4 are protected.
The protection is activated in case of HO switching criteria detection.
This option is used to select the VC-4 to protect.
In the following are listed the restrictions applied in the selection of the worker channel:
n the related unit must be equipped and the involved port configured;
n STM-n port must be connected to a matrix access;
n it must be not involved into a VC-4-nc;
n it must not be cross-connected at VC-4 level;
n all the channels must not be involved in path protection either as worker or as protection
resource; in particular the TO side also of cross connections (broadcast included) must not
be involved in path protection;
n no Unidirectional Dropped Connections are allowed;
n no SPLIT accesses are allowed;
n the related port can not be used as MSP protection resource (1+1 or 1:N).
The supported LO cross-connections are:
n monodirectional (only Rx or Tx Type supported);
n bidirectional (only RxTx Type supported);
n broadcast (only Rx side).
Special Handling of some cross connection types:
n broadcast cross connection are allowed but Rx side only will be protected;
n monitor cross connection can be involved in Rx DXC Type III Protection as broadcast
cross connection.
n in case of contiguous concatenation, an high order path protection (DXC Type III) can not be
set up on AU-nC channels;

.
Issue:1
PROTECTION AND TEST
n in case of contiguous concatenation with conversion to virtual, a DXC Type III protection can
be set up on channels cross-connected as AU-nV (virtual at matrix side) if the protection
channels are configured as Aus not concatenated.
To select the VC-4 channel to be protected (and to activate Action menu):

* Select the port subrack.
* Select the PORT containing the channel to connect (in case of NxSTM-1 Unit).
* Select the AUG.
DXC Type Three Protection: configuring

Path (Action-Create)
Use this option to define the partner resource on a DXC type III protection.
In the following are listed the restriction applied in the selection of the protection channel:
n the related unit must be equipped and the involved port configured;
n STM-n port must be connected to a matrix access;
n all LO channels must be not cross-connected;
n no Unidirectional Dropped Connections are allowed;
n no SPLIT access are allowed;
n the related port can not be used as Worker or Protection MSP resource (1+1 or 1:N).

.
Issue:1
PROTECTION AND TEST
To select the protection VC-4 channel:

* Select the PORT (in case of NxSTM-1 or 4xSTM-1/140Mbit/s Unit).
* Select the AUG.
* Set the Hold Off time for SF and SD criteria.
* Use Protection Mode to enable (Revertive) or disable (Not Revertive) the restoration of
the traffic on the worker channel after repair of a failure that caused paths to be switched.
* Define the Protection Type to be created:
Rx Trail Protection
The system chooses from which resource (worker or protection) receives the channel: only the
receive side is protected (selection criteria).
Tx Trail Protection
The system sends the signal on both resources (worker and protection): only the transmit side is
protected (redounded).
RxTx Trail Protection
The system transmits the signal on both resources (worker and protection transmit side) and
selects from which resource (worker or protection receive side) receives the channel.
* Press APPLY.
See Also:
Multiplexing Section Protection: configuring, Hold off: Management

.
Issue:1
PROTECTION AND TEST
DXC Type Three Protection: displaying information

Path (Action-Read)
This option is used to display information on the DXC Type Three Protection used for the selected
resource.
To display information about a DXC Type Three Protection:

* Select the unit.
See Also:
DXC Type Three Protection: configuring, Operative States
DXC Type Three Protection: modifying

Path (Action-Modify)
This option is used to modify the protection mode of an existing DXC Type Three Protection.
To modify a DXC Type Three Protection:

* Select the AUG.
the traffic on the worker channel after repair of a failure that caused paths to be switched.
* Press APPLY.
See Also:

.
Issue:1
PROTECTION AND TEST
DXC Type Three Protection: switching

Path (Action-Protection Switch)
versa.
To switch a DXC Type Three Protection:

* Press APPLY.
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
DXC Type Three Protection: removing

This option is used to remove the DXC Type Three Protection: assigned to a selected Unit.
To delete a DXC Type Three Protection Protection:

* Select the Unit whose DXC Type Three Protection has to be removed.
* Press APPLY.
See Also:
DXC Type Three Protection: swapping role

Path (Action-Prot Role Swap)
This option is used to swap the roles between the worker and the protection channel of a DXC Type
Three Protection.
To swap the DXC Type Three protection roles:

* Select the worker resource whose role must be swapped.
* Press APPLY.
Note After a role swap on DXC Type Three Protection status is not correctly displayed for a
short time.
See Also:
Operative States, DXC Type Three Protection: configuring, DXC Type Three
Protection: modifying, DXC Type Three Protection: removing, DXC Type Three
Protection: switching

.
Issue:1
PROTECTION AND TEST
PROTECTIONS LIST: FILTER

Path (Equipment Configuration-Protection- Protections List)
This option is used to display a list of the trail protections active in the equipment.
In particular this facility allows setting a filter on the report in order to disable the displaying of some
protection type.
To select the displaying parameter:

* Select the Protection Type to be displayed.
Protections List: reading

Path (Action-Read)
Use this option to display a list of the trail protections active in the equipment.
The report will be according to the selected filter.
See Also:
Protections List: filter
PORT SUBRACK PROTECTION: SETTING THE WTR PERIOD

Path (Protection-WTR Period- STM1 MSP WTR / STM4 MSP WTR / STM16 MSP WTR /
Line Protection WTR / Card Protection WTR)
These option are used to set the restoration time (WTR) for the Multiplexing Section Protection
STM-1, STM-4, STM-16 ports), Line Protection (140Mbit/s and 140 T-Mux ports - in the DXC 4/1)
and the Card Protection (NxSTM-1 and 4x140-155Mbit/s Units). Traffic is restored on the worker
line when no alarms are present for the WTR time.
WTR is enabled only when protection mode has been set to revertive.
To set the WTR:

* Indicate the WAIT TO RESTORE PERIOD in minutes (1 to 30 min).
* Press APPLY.
The WTR period applies to all MSP protections (1+1 and N+1) and Line Protection (1+1 for
140Mbit/s and 140 T-Mux - in the DXC 4/1).
See Also:
Multiplexing Section Protection: configuring, 140Mbit/s Line Protection: configuring,

.
Issue:1
PROTECTION AND TEST
HOLD OFF: MANAGEMENT

Path (Equipment Configuration-Protection-Hold off Management)
The hold-off time is the time between declaration of signal degrade (SD) or signal fail (SF) and the
initialization of the protection switching algorithm and it is useful for interworking of protection
schemes. A hold off timer is started when a defect condition is declared and when the timer expires,
protection switching is initiated if a defect condition is still present at this point.
The operator can define the hold-off time between 100ms and 20s in 100ms steps.
The Matrix Controller expects the hold-off time before achieving the change. When an alarm arises
the hold-off timer is activated; after this time the Matrix Controller checks the channel in Worker and
if it has some alarms yet, the traffic will change on the another channel.
It is possible to apply the hold off timer to the SNC-P at all VC levels and to DXC type III protection.
Note The LO Hold Off Timer is managed only for DXC 4/1 256x256, DXC 4/1 512x512 (any
VC level) and DXC 4/4 512x512, DXC 4/4 1024x1024 (VC-3 level).
To set a Hold off Time:

* Indicate Signal Degrade Hold Off (SD) (0 to 20 seconds in steps of order of 100ms).
* Indicate Signal Failure Hold Off (SF) (0 to 20 seconds in steps of order of 100ms).
* Press APPLY.

.
Issue:1
PROTECTION AND TEST
Note The default hold-off time shall be 0 seconds. The value 0 sec. means hold-off
disabled.
IMPORTANT The command applies the hold off time only to the protections that have the
worker channel on the selected port.
PORT LOOPBACKS: MANAGING

Path (Equipment Configuration-Loopback test)
Use this option to enable/disable testing loopbacks of Port Subracks.

Note A Remote Loopback activation is feasible only if the selected port is not the
synchronization source.
See Also:
Loopbacks: configuring the mapping state

Path (Action-2Mb Port Loopback-Mapping State-Setup)
This option performs a remote loop of all the 2Mbit/s ports (Mapping) for a selected 16x2Mbit/s
Tributary Unit.
The Mapping Loopback can not be performed if the 2Mbit/s ports are cross-connected.
To enable the mapping state:

* Use Mapping Loopback State to activate/deactivate the loop (Enable/Disable).
* Press APPLY.
Loopbacks: displaying the mapping state

Path (Action-2Mb Port Loopback-Mapping State -Read)
Use this option to display whether the Mapping loopback has been enabled in a selected
16x2Mbit/s Tributary Unit. In the Mapping Loopback state box is indicated the state of the
Mapping loopback (Enable/Disable).
See Also:
Loopbacks: configuring the mapping state

.
Issue:1
PROTECTION AND TEST
2Mbit/s Port Loopback: configuring

Path (Action-2Mb Port Loopback-Port State-Setup)
This option is used to activate or deactivate a test loop of the 2Mbit/s tributary signal processed by
the 16x2Mbit/s Tributary Unit. Loop can be activated in anyone of the 16 ports.
To enable a 2 Mbit/s port loopback:

* Use Port Loopback State to activate/deactivate the loop in the selected port.
No Loopback
Loopback is deactivated.
Local Loopback
Signal loopback activated on the matrix side.
Remote Loopback
Signal loopback activated on the line side.
Port not configured
Port has not been configured (read-only value).
Note Only Not Transparent Forward Mode can be configured.
* Press APPLY.
2Mbit/s Port Loopback: displaying state

Path (Action-2Mb Port Loopback-Port State-Read)
This option is used to display the presence of port loopbacks enabled in the 16x2Mbit/s Tributary
Unit Port.
See Also:

.
Issue:1
PROTECTION AND TEST
63x2Mbit/s Unit Port Loopback: configuring

Path (Action-Type 3 Loopback-Setup)
This option is used to activate or deactivate a test loop of the 2Mbit/s tributary signal processed by

* Select the port in the PORT Sel. field (only configured ports will be displayed).
No Loopback
Local Loopback
Remote Loopback
* Use the Forward Mode to select the type of signal forwarded to the other side when port
is looped:
Transparent
Data signal sent to the other side.
Not Transparent
AIS sent to the other side.
* Press APPLY.

.
Issue:1
PROTECTION AND TEST
63x2Mbit/s Unit Port Loopback: displaying state

Path (Action-Type 3 Loopback-Read)
Unit Port.
See Also:
4x34Mbit/s T-Mux Unit Port Loopback: configuring

This option is used to activate or deactivate a test loop of the 34Mbit/s tributary signals processed by

No Loopback
Local Loopback
Remote Loopback
is looped:
Transparent
Not Transparent
NOTICE Not Transparent Local Loopback is not available. Transparent Local Loopback
needs a valid and not alarmed input signal on PDH ports to properly work (a
warning message will appear to inform the Operator) .
* Press APPLY.
See Also:

.
Issue:1
PROTECTION AND TEST
4x34Mbit/s T-Mux Unit Port Loopback: displaying state

Path (Action-Type 3 Loopback-Read)
Unit Port.
See Also:
4x34Mbit/s T-Mux Unit Port Loopback: configuring
NxSTM-1 Port Loopback: configuring

Path (Action-NxSTM1 Loopback-Setup)
This option is used to activate or deactivate a test loop of the STM-N signal processed by the
NxSTM-1 Unit.
synchronization source and if no DCC is enable on it.
To enable a STM-1 port loopback:

* Use the Port Loopback State to activate/deactivate the loop in the selected port.
No Loopback
Local Loopback
Remote Loopback
is looped:
Transparent

.
Issue:1
PROTECTION AND TEST
Not Transparent
* Press APPLY.
NxSTM-1 Port Loopback: displaying state

Path (Action-NxSTM1 Loopback-Read)
This option is used to display the presence of port loopbacks enabled in the NxSTM1 Tributary
Units.
See Also:
NxSTM-1 Port Loopback: configuring
STM-N Port Loopback: configuring

Path (Action-STM-1 Loopback-Setup)
This option is used to activate or deactivate a test loop of the STM-N signal processed by the
Optic/Mux Unit (or also Electric/Mux Unit in case of STM-1 signal).
synchronization source and if no DCC is enable on it.
Standard Type STM-1 Port
To enable a STM-1 port loopback:

No Loopback
Local Loopback
Remote Loopback
* Press APPLY.
Type 2 STM-1 Port
To enable a STM-1 Type 2 port loopback:

No Loopback
Local Loopback
Remote Loopback
is looped:
Transparent

.
Issue:1
PROTECTION AND TEST
Not Transparent
* Press APPLY.
STM-4 and STM-16 Port
To enable a STM-N port loopback:

No Loopback
Local Loopback
Remote Loopback
is looped:
Transparent
Not Transparent
* Press APPLY.
STM-N Port Loopback: displaying state

Path (Action-STM-1 Loopback-Read)
This option is used to display the presence of port loopbacks enabled in the STM-N Units.
See Also:
STM-N Port Loopback: configuring

Path (Action-140Mb/140TMUX Port Loopback-Setup)
Use this option to activate or deactivate a test loop of the 140Mbit/s tributary signal processed by the
140Mbit/s Tributary Unit.
To enable a 140Mbit/s port loopback:

No Loopback
Local Loopback
Remote Loopback
is looped:

.
Issue:1
PROTECTION AND TEST
Transparent
Not Transparent
* Press APPLY.
140Mbit/s Port Loopback: displaying state

Path (Action-140Mb/140TMUX Port Loopback-Read)
This option is used to display the presence of test port loopbacks enabled in the 140Mbit/s Tributary
Units.
See Also:
140Mbit/s T-Mux Port Loopback: configuring

Path (Action-140Mb/140TMUX Port Loopback-Setup)
Use this option to activate or deactivate a loop of the 140Mbit/s tributary signal processed by the
140Mbit/s T-Mux Tributary Unit.
To enable a 140Mbit/s port loopback:

No Loopback
Local Loopback
Remote Loopback
* Press APPLY.
140Mbit/s T-Mux Port Loopback: displaying state

Path (Action-140Mb/140TMUX Port Loopback-Read)
This option is used to display the presence of test port loopbacks enabled in the 140Mbit/s T-Mux
Tributary Units.
See Also:
140Mbit/s T-Mux Port Loopback: configuring

.
Issue:1
PROTECTION AND TEST
1x45Mbit/s T-Mux Port Loopback: configuring

Path (Action-45-TMUX Loopback-DS3 state-Setup)
This option is used to activate or deactivate a test loop of the DS3 channel processed by the
1x45Mbit/s T-Mux Tributary Unit.
To enable a 45Mbit/s port loopback (DS3 channel):

* Use DS3 Loopback State to activate/deactivate the loop in the port.
Local loopback
Remote Loopback
Signal loopback activated on the line side
No loopback
is looped:
Transparent
Not Transparent
* Press APPLY.
1x45 Mbit/s T-Mux Port Loopback: displaying state

Path (Action-45-TMUX Loopback-DS3 state-Read)
This option is used to display the presence of test port loopbacks enabled in the 1x45Mbit/s T-Mux
Tributary Units
See Also:
1x45Mbit/s T-Mux Port Loopback: configuring

.
Issue:1
PROTECTION AND TEST
1x45Mbit/s T-Mux Port Loopback: channel configuration

Path (Action-45-TMUX Loopback-Channel state-Setup)
This option is used to activate or deactivate a test loop of the DS1/E1 channels managed by the
1x45Mbit/s T-Mux Tributary Unit.
In this window are listed the twenty-eight channels that can be managed by the 1x45Mbit/s T-Mux
Tributary Unit. This number as to be intended as a maximum value and it can be reached only if the
all DS2 channels have been structured as DS1 (1,5 Mbit/s as defined by ANSI T1.107).
Each group of four channel (starting from the first position in the window) is a DS2 channel
(remember that a DS2 channel can be demultiplied on four DS1 or on three E1).
In case some DS2 channels have been configured to carry E1 channels (2Mbit/s as defined by ITU-
T G747) some field in the window, that represent a possible channel, will be not available.
To enable a DS1/E1 loopback (1,5/2Mbit/s channel):

* Use DS1/E1 Loopback State to activate/deactivate the loop in the port.
Local loopback

.
Issue:1
PROTECTION AND TEST
Remote Loopback
No loopback
is looped:
Transparent
Not Transparent
* Press APPLY.
1x45 Mbit/s T-Mux Port Loopback: displaying channel state

Path (Action-45-TMUX Loopback-Channel state-Read)
This option is used to display the presence of test loopbacks enabled in the DS1/E1 channels
managed by the 1x45Mbit/s T-Mux Tributary Units
See Also:
1x45Mbit/s T-Mux Port Loopback: channel configuration
34/45 Mbit/s Port Loopback: configuring

Type 2 Subrack
Path (Action-3x34/45Mb Port Loopback-Setup)
This option is used to activate or deactivate a test loop of the 34-45Mbit/s Tributary signal processed
by the 34-45Mbit/s Tributary Unit.
To enable a 34-45 Mbit/s port loopback:

* Use Port Loopback State to activate/deactivate the loop in the three available ports.
Local loopback
Remote Loopback
No loopback
is looped:
Transparent
Not Transparent
* Press APPLY.

.
Issue:1
PROTECTION AND TEST
Type 3 Subrack
This option is used to activate or deactivate a test loop of the 34-45Mbit/s Tributary signal processed
by the 3x34-45Mbit/s Tributary Unit.
To enable a 34-45 Mbit/s port loopback:

No Loopback
Local Loopback
Remote Loopback
is looped:
Transparent
Not Transparent
* Press APPLY.
34/45 Mbit/s Port Loopback: displaying state

Type 2 Subrack
Path (Action-3x34/45Mb Port Loopback-Setup)
Type 3 Subrack
Path (Action- Type 3 Loopback -Read)
This option is used to display the presence of test port loopbacks enabled in the 3x34/45Mbit/s
Tributary Units
See Also:
34/45 Mbit/s Port Loopback: configuring
Loopback: displaying
Path (Equipment Configuration-Test-Loopback List)
This option is used to display the list of all the loopbacks active in the equipment.
Furthermore for each loopback its configuration is reported (Loopback_State and Forward Mode)
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
TEST STATE: MANAGEMENT

Path (Equipment Configuration-Test-NE Test State)
This option allows to masks the alarm due to a test session open on the matrix.
If the Matrix Global Test or/and Subrack Link Test have to be performed the Operator has to:
* Perform a forced switch on the matrix not involved in the test;
* Enable the Test State on the matrix where the test has to be launched;
* Activate the test.
This is the correct sequence of actions to start a test session on the matrix. Once a test session has
been completed the Operator has to:
* Disable the Test State;
* Perform a clear switch on the matrix.
To enable/disable the Test State:

* Select the matrix on which a test session has to be opened/closed.
* Define the test state (Enable/Disable) using the Test State scroll list.
* Press APPLY.
When the test state is enable, a proper indication will be displayed in the local controller main
window.
See Also:
Operative States, General Information
WIRING TEST: EXECUTION

Path (Equipment Configuration-Test-Wiring Tests)
Use this option to perform a test of the correct wiring of the timing, control and data signals relevant
to Control and Timing Subrack, Matrix Subrack, Port Subrack.

Select the subrack to be tested.
See Also:

.
Issue:1
PROTECTION AND TEST
Wiring Test: displaying information

Path (Action-Read)
Control and Timing Subrack
Use this option to check the correct connection (wiring) of the control signal connecting Serial
Expansion Unit to Timing Selector Oscillator Unit (refer to Documentation supplied with the
equipment for more details).
The message Passed indicates that the connection is correctly made, the message Failed
indicates a problem.

.
Issue:1
PROTECTION AND TEST
Port Subrack
Use this option to check the wiring of the data signals connecting port subrack to matrix subrack,
and to check the wiring of the control and timing signals connecting port subrack to the CT Subrack
(refer to Documentation supplied with the equipment for more details).
PORT MATRIX ACCESS Test box displays the state of data connections from port subrack to
matrix subracks.
In the box are listed the accesses (Tx and Rx Side) connecting port subrack to matrix A and matrix
B. For each access the message Passed indicates the correct wiring, the message Failed indicates
that the relevant data cable is not connected or is plugged into a wrong connector.
SERIAL I/O LINE test box displays information about the control cables connecting the port subrack
to CT Subrack. Message Passed indicates the correct wiring, the message Failed indicates that the
relevant cable is not properly working.
In the SYNCHRONIZATION LINE Test box are displayed the information about the timing cables
connecting port subrack to CT Subrack.

.
Issue:1
PROTECTION AND TEST
Matrix Subrack
Having selected the Matrix Subrack, the correct connection (wiring) of control and timing cables
connecting Matrix Subrack to CT Subrack is shown (refer to Installation for more details).
DXC 4/1 DXC 4/4
Serial I/O Line Test box contains information about the serial line connecting matrix A and matrix B
to the CT subrack.
Sync. Line Test box contains information about the timing signals connecting matrix A and matrix B
to the CT Subrack. Performing the test on the DXC 4/4 Matrix also the information about the timing
signals connecting matrix A Slave and matrix B Slave to the CT Subrack are reported.
MATRIX SUBRACK TEST: ACTIVATING (DXC 4/1)

Path (Equipment Configuration-Test-Matrix Global Test)
This option is used to test the internal STM-1 links between Ist to IInd and IInd to IIIrd stage units using
a test pattern.
To start the Matrix Global test:
IMPORTANT This test will be activated into a matrix only if it is in test state and the traffic is
forced switched into the other one matrix.
* Select the Matrix Subrack to be tested.

* Select Action-Start Test
See Also:
Operative States

.
Issue:1
PROTECTION AND TEST
Matrix Subrack Test: displaying information (DXC 4/1)

Path (Action-Read)
For each card the system display one of the following messages depending by the test result:
Passed
Test successfully passed.
Failed
Test not passed, card failed.
Card Missing
Card equipped but not inserted.
Unequipped Card
Card unequipped.
PORT/MATRIX SUBRACK LINK TEST: ACTIVATION (DXC 4/1)

Path (Equipment Configuration-Test-Subrack Link Test)
This option is used to verify the interconnection among the port subracks and the matrix subracks
using a test pattern.

.
Issue:1
PROTECTION AND TEST
To start the subrack link test:
IMPORTANT This test will be activated into a matrix only if it is in test state and the traffic is
forced switched into the other one matrix.
* Select a port subrack.

* Use MATRIX exclusive buttons (either A or B) to select the matrix subrack.
* Use SIDE exclusive buttons to select the direction to be verified:
FROM
From the selected port subrack to the selected matrix subrack.
TO
From the selected matrix subrack to the selected port subrack.
* Select Action-Start Test from the menu bar.
Port/Matrix Subrack Link Test: displaying information (DXC 4/1)

Path (Action-Read)
For each subrack access the system display one of the following messages depending by the test
result:
Connected-Passed
Access connected to a matrix access - Test passed.

.
Issue:1
PROTECTION AND TEST
Connected-Failed
Access connected to a matrix access - Test not passed, cards/cable failed.
Not Connected
Port subrack access not configured.
DATABASE TEST: ACTIVATION

Path (Equipment Configuration-Test-X Conn. Global Test)
This option is used to verify the cross-connection database. All the wrong cross-connections (not
congruent with the database structure) will be notified.
To start cross-connection global test:

* Press OK.
An Event Message is displayed in the Real Time Monitor Window. A different message is displayed
depending on the type of problem that has been detected.
A message No errors detected, test completed indicates that the test has been successfully
completed. If a different message is present proceed as follows:
a. Delete the involved cross-connection/s.
See Also:
Cross-Connection: managing list filters (DXC 4/1), CCU Fault History Buffer:
displaying
CCU FAULT HISTORY BUFFER: DISPLAYING

Path (Equipment Configuration-Test- CCU Fault History Buffer)
This option allows to create a log file of the possible errors that have caused a CCU restart (not due
to management operation that means not requested by the operator). The last part of the code
executed by the CCU preceding a CCU restart is saved in the backup memory of the Memory
Expansion Unit; using this option the content of this memory can be saved in a file (binary
proprietary format) and subsequently sent to the supplier to analysed the problem.
Note The content of this memory is overridden each time a restart occurs then it is useful
perform this operation after each restart.

.
Issue:1
PROTECTION AND TEST
To select the directory where the file has to be saved:

* Select the directory in the DIR. : field and then the file.
* Press OK
Select FILTER to change the types of files displayed according to the selected filter.
Note The default directory is the Application Software installation directory.
CCU STATE: CONFIGURING

Path (Equipment Configuration-Online State)
The NE Online State represents the status of the Central Control Unit (CCU) regarding its control
capabilities on the other peripheral units in the equipment.
In ONLINE state the CCU unit communicates with the Local Controller and also with all the units; in
OFFLINE state the CCU unit communicates only with the Local Controller and has no control on
peripheral units.
The UPGRADING state is used when the equipment software release has to be upgraded.
The Central Control Unit must be Off-Line in order to perform a decommissioning of the
equipment.
To modify the operational state of the Central Control Unit:

* Use Online State to select the operational state of the CCU
(ONLINE/OFFLINE/UPGRADING).
* Press APPLY.
IMPORTANT When CCU state is changed from OFF LINE to ON LINE a message box
appears prompting the User to shutdown the LC application.
See Also:
System: partial decommissioning of NE database, System: restarting CCU, system:
Line Up: managing

.
Issue:1
MANAGING CROSS-CONNECTIONS
CROSS-CONNECTIONS: MANAGEMENT (DXC 4/1)

Path (Connection Configuration-Cross Connection Management)
Before starting the Connection Management make sure that all ports needed have been correctly
configured.
Note Remind that for STM-N channels (except for STM-1 Type Standard) any cross-
connection creation must match the pre-defined frame configuration of all the involved
VCs.
Use this option to make a cross-connection.
To select the incoming channel (and to activate Action menu):

* Select the PORT containing the channel to connect (in case of NxSTM-1 or 4xSTM-
1/140Mbit/s Unit).
* Select the AUG (in case of STM-N channel).
* Use SDH Traffic Type to select the type of cross-connection to be made (VC12, VC2,
VC2-5c, VC3, VC4 or VC4-4c, VC4-4v, VC4-16v).
* Select the SDH channel.

.
Issue:1
Concatenated Traffic Type

It is possible to perform concatenations at VC-4 and VC-2 level.
In case of VC-4 the possible concatenations are VC-4-4c, VC-4-4v / 16v while for the VC-2 is VC-2-
5c.
When a contiguous concatenated SDH Traffic Type (VC2-5c or VC-4-4c) is selected it is possible
to select more than one SDH channel (Chan Id in case of VC2-5c concatenation or AUG in case of
VC4-4c concatenation) simply clicking on it.
In the "To" channel selection window an indication will appear to remind the number of channel to
select (VC-2-5c).
VC4-4c Traffic Type

It is possible to cross-connect a contiguous concatenated traffic type. In this kind of connection the
stream are sent to the matrix in form of VC-4 channels. The matrix provides to concatenate them in
VC-4-Xc (X= 4) which are sent to the other line and/or to a STM-4 or STM-16 tributary.
In this case, the concatenation have been previously configured by means of the AU Group
Definition in the Port Configuration menu item.
See Also:
AU Group Definition
NOTICE Consider the following restrictions:

a it is not allowed to cross-connect separately the VCs previously grouped in
a VC-4-Xc;
b it is not allowed any more to cross-connect as concatenated some VCs that
are not grouped;
c split connections are not allowed on a configured VC-4-Xc traffic type;
d an UDC can be created on a configured VC-4-Xc if the drop side of the
connection has been configured as VC-4-Xc;
e monitor connections are allowed if the derived side has been configured as
VC4-Xc;
f broadcast connections are allowed if the leg has been configured as VC-4-
Xc.

.
Issue:1
VC4-4v, VC-4-16v Traffic Type

It is possible to cross-connect a virtual concatenated traffic type. The STM-16 VC-4-16c (or VC-4-
4c) signal incoming from the tributary side is converted into indipendent VC-4s that must be cross-
connected separately and can be sent all over the network by means of different media. The VC-4-
16v incoming from the network are sent to the STM-16 Optical Unit for the VC-4-16c/16v and then
converted in VC-4-16c, while a VC-4-4v incoming from the network are sent to the STM-16 Optical
Unit for the VC-4-4c/4v conversion and then converted in VC-4-4c to be sent to line.
IMPORTANT The STM-16 VC-4-16c signal incoming is accepted only if it will convert in a
virtual concatenaton.
NOTICE Consider the following restrictions:

a it is not allowed the cross connection of AU-Xc (X= 4, 16), if the Au are
configured as AU-Xv;
b the cross connection of AU-Xv has to be performed singularly for each AU;
c monitor connections are not allowed.
See Also:
AU Group Definition
VC2-5c Traffic Type
It is possible concatenate only VC-2 belonging to the same VC-4.
See Also:
How To Select Objects, Operative States, Port: configuration, STM-N Port:
configuring frame and supervisory unequipped state

.
Issue:1
Cross-Connection: configuring (DXC 4/1)

Path (Action-X Connection-Create)
Use this option to create the outgoing channel of a cross-connection indicating the type of operation
(bidirectional, unidirectional or broadcasting).
To select the outgoing channel:

* Select the port subrack to be used for the outgoing connection.
* Select the tributary unit to be used for the connection.
1/140Mbit/s Unit).
* Select the AUG containing the channel to connect (in case of STM-N channel).
* Select the channel to be used for the outgoing connection. Both sides of channel (From
side and To side) must be in the Free State in order to allow the bidirectional
connection.
* Select the type of cross-connection (X Connection Kind).
Bidirectional
To make a bidirectional cross-connection (both Tx and Rx paths are used).

.
Issue:1
Unidirectional
To make a unidirectional cross-connection (only one path is used; unused path can be assigned to
another unidirectional connection).
Broadcast
To make a broadcasting cross-connection. Use then the option Leg Management to add
secondary legs.
In the field SDH Traffic Type is shown the type of multiplexing previously selected.
* Press APPLY.
IMPORTANT In the condition when 2 VC-3 cross connections are currently active on an STM-
1 card and a 3rd new VC-3 cross connection needs to be created, traffic
disturbance may affect the existing 2 VC-3 Cross-Connections. The following
message will be displayed:
!!! Warning !!! If One Of The Involved Units Is A STM-1 Type 1 This
Operation Could Hit For A Short Time Other VC-3 Cross Connection...
Press OK to proceed or CANCEL to quit the operation.
IMPORTANT In the 16x2Mb Unit the 16 channels are handled in 4 groups of 4 channels each,
in such a way that you must use the same traffic type (e.g. bidirectional or
unidirectional) within each individual group.
Unit active alarm

The Active Alarm button
allows to display a list of the all active alarm present in the relevant unit.
This facility is accessible from all the windows/options that involve a port unit or the matrix and CT
subrack.
See Also:
Broadcast Cross-Connection: adding a leg (DXC 4/1), Operative States, Port:
configuration, Active Alarms: displaying unit active alarms
Cross-Connection: displaying information (DXC 4/1)

Path (Action-X Connection-Read)
This option is used to display the connection parameters relevant to a selected cross-connection.
See Also:
Cross-Connection: configuring (DXC 4/1), Operative States
Cross-Connection: removing (DXC 4/1)

Path (Action-X Connection-Delete)
This option is used to delete a cross-connection.
A connection can be removed only when it is in all of the following conditions:

a. Tandem Connection has been removed (if any)
b. Path Protection has been removed (if any)

.
Issue:1
c. Monitor connection has been removed (if any)

d. Administrative State of the connection is Unlocked
The Delete option allows the Operator to remove all types of cross-connections (bidirectional,
unidirectional and broadcasting). For the broadcasting cross-connections after selection of the
Delete option all incoming (master) and outgoing channels (tributaries) are deleted.
However, the Operator can delete the secondary cross-connections one-by-one using the option
Delete Leg.
See Also:
Cross-Connection: configuring (DXC 4/1), Operative States
Broadcast Cross-Connection: adding a leg (DXC 4/1)

Path (Action-Leg Management-Add)
Use this option to add secondary legs to a broadcasting cross-connection. This option becomes
active only when the master leg has been selected.
To add a secondary leg to a broadcasting connection:

* Select the port subrack to be used for the connection (secondary leg).
* Select the tributary unit to be used for the connection.
1/140Mbit/s Unit).

.
Issue:1
* Select the channel to be used for the connection.
* Press APPLY.
See Also:
Cross-Connection: configuring (DXC 4/1), Operative States, Active Alarms:
displaying unit active alarms
Broadcast Cross-Connection: removing a leg (DXC 4/1)

Path (Action-Leg Management-Delete)
This option is used only for broadcast cross-connections. Using this option the Operator can modify
a broadcast connection, deleting selected secondary cross-connections (and then eventually adding
new ones) or deleting the entire broadcasting connection.
If all secondary cross-connections are deleted the entire broadcasting connection is deleted.
A secondary connection can be removed only when it is in all of the following

conditions:
a. Tandem Connection has been removed (if any)
b. Path Protection has been removed (if any)
c. Monitor connection has been removed (if any)
d. Administrative State of the connection is Unlocked
See Also:
Broadcast Cross-Connection: adding a leg (DXC 4/1), Operative States
Monitor Cross-Connection: adding (DXC 4/1)

Path (Action-Monitor Management-Add)
This option is used to create a monitor cross-connection. Monitor Connection is added to the main
connection and allows the Operator to check the operation of the incoming (or outgoing) channel
(for example by connecting a test instrument to the monitor port).
The channel used as monitor connection must have a traffic type compatible with the monitor
channel.
The channel used as monitor connection must be of the same type as the input channel (e.g.: if the
input channel is a 140Mbit/s Tributary Unit the monitor connection must use only a 140Mbit/s
Tributary Unit).
Note The use of the monitor access function does not influence the traffic.

.
Issue:1
To add a monitor connection:

* Select the tributary unit to be used as monitor connection.
1/140Mbit/s Unit).
* Select the channel to be used as monitor. The monitoring channel must be in the Free
state (To side).
* Press APPLY.
See Also:
Operative States, Active Alarms: displaying unit active alarms
Monitor Cross-Connection: displaying information (DXC 4/1)

Path (Action-Monitor Management-Read)
This option is used to display the channel used for a monitor cross-connection.
See Also:
Monitor Cross-Connection: adding (DXC 4/1), Operative States

.
Issue:1
Monitor Cross-Connection: removing (DXC 4/1)

Path (Action-Monitor Management-Delete)
This option is used to delete a monitor connection.
A connection can be removed only when it is in the following condition:

a. Administrative State of the connection is Unlocked
See Also:
Monitor Cross-Connection: adding (DXC 4/1), Operative States
Cross-Connection: managing the administrative state (DXC 4/1)

Path (Action-X Connection-Administrative State)
This option is used to lock/unlock a cross connection. When a connection has been locked no
actions can be performed on it (e.g.: Deleting, Path Protection, Adding a Monitor Cross-Connection)
until its administrative state is unlocked.
To lock a Cross Connection:

* Use TO CHANNEL Selection (or LEG CHANNEL Selection, MONITOR Channel
Selection, etc.) box to select the relevant outgoing channel.
* Use Administrative state to set the locked/unlocked state of the connection.
* Press APPLY
See Also:
Operative States, CCU State: configuring, Active Alarms: displaying unit active
alarms

.
Issue:1
Cross Connections: restoration (DXC 4/1)

Path (Action-Manual Restoration)
This option allows to move all not path protected cross connections from one port unit ("Source"
port) to another one ("Destination" port) at the same time.
To perform a Manual Restoration "Source" and "Destination" port units must satisfy the following
requirements:
1. "Source" and "Destination" port units types can be:
for STM-1 Optic/Electric Mux Unit (STM1 Opt/El): Standard Type or STM1-Type 2;
Transmux 140Mb/s Tributary Unit (TMUX140);
STM-4 Optic/Mux Unit (STM4-Opt), STM-16 Optic/Mux Unit (STM16-Opt), NxSTM-1
Optic/Electric Mux Unit (4xSTM1-El, 2XSTM1-Opt) or 4xSTM-1/140Mbit/s Unit
(4xSTM1-140) configured as STM-1.
2. Manual Restoration is feasible only if the two port unit types are:
both STM-N (Optical and/or Electrical in case of STM-1);
both NxSTM-1 (Optical and/or Electrical in case of 4xSTM-1);
both TMUX 140Mb/s;
an STM-1 and a TMUX 140Mb/s.
3. "Source" and "Destination" units must be equipped;
4. "Source" and "Destination" ports must be configured and unlocked;
5. "Source" and "Destination" ports must not be involved in:
MSP 1+1 Protection (unidirectional or bidirectional)
MSP 1:N Protection (unidirectional or bidirectional)
PDH 140Mb/s Line Protection.
6. In case a channel belonging to "Source" is configured as Tandem Connection Termination on
matrix side, the relevant "Destination" channel can not be configured as Tandem Connection
Termination on line side (the command will be aborted).
7. Matrix Accesses of "Destination" port must be connected (the unit can not be a protection
unit);
8. "Destination" port must support only path protected cross connections or no cross
connections and the cross connections on "Source" port must not overlap any already
existing path protected cross connections on "Destination" port;
9. Cross connections on "Source" port must not be locked;
10. if both involved ports are of the same type, the SDH parameters of the two ports must match:
if both ports are STM-1 Standard Type, "Signal Label" Expected and Configured must be
equal;
if both ports are TMUX 140 Mb/s, the "Channel to Discard" parameters must be equal;
if both ports are STM-1 Type 2, STM-4 or NxSTM-1 the two ports must have the same
frame structure.

.
Issue:1
11. if "Source" port is a STM-1 and "Destination" port is a TMUX 140 Mb/s, only simple VC-12
cross connections will be moved;
12. if "Source" port is an TMUX 140 Mb/s and "Destination" port is a STM-1 Type 2, the frame
structure of the latter must be "TUG structured" for "ALL VC-12".
* Select the Subrack containing the unit to be used as source of cross connection using:
Connection configuration - Cross connection management
* Select the unit.
* Select Action - Manual restoration
* Select the Subrack containing the unit to be used as destination of cross-connection
* Select the unit. Take care that the selected unit must have already been configured (no
cross-connection)
* Press APPLY
See Also:
Tandem Connection: configuring, Port: configuration, STM-N Port: configuring frame
and supervisory unequipped state

.
Issue:1
Cross-Connection: forced deletion (DXC 4/1)

Path (Action-Forced Delete-Port)
This option is used to delete cross connections even if they are path protected, monitored or locked.
The command works on a port basis, it takes effect on all the port channels.
IMPORTANT The operation is allowed when the controller status is set to OFF-LINE.
After the selection of the command, the system asks for a confirmation.
* Press OK to confirm the operation.
See Also:
CCU State: configuring
Cross-Connection: displaying the port/matrix fail alarms (DXC 4/1)

Path (Action-Port card MTX Fail)
This option is used to display a list of the cross-connection affected by Matrix Fail Alarm.
Note This facility is implemented for Type 5, Type 2 and Type 4 subracks.
Alarmed channel is indicated in the field Chan_id. MTX_A_Fail and MTX_B_Fail indicate the alarm
is due to the matrix A and matrix B.
Conn_Chan_id indicates the other channel of cross-connection.
Traffic and XConn_ty provide information on the type of cross-connection.
See Also:

.
Issue:1
CROSS-CONNECTION: MANAGING LIST FILTERS (DXC 4/1)

Path (Connection Configuration-Cross Connection-List)
This option is used to display a list of all cross-connections present in the equipment.
To select the Cross-Connection type to be displayed:

* Use Administrative state to select the administrative state of the connections to be
displayed (Unlocked, Locked or All values for all types).
* Use SDH Traffic Type to select the type of traffic to be displayed (VC12, VC2, VC2-5c,
VC3, VC4, VC4-nc or All values for all types).
* Use X Connection Kind to select the type of cross-connections to be displayed
(Unidirectional, Bidirectional, Broadcast, Monitor or All values for all types).
Cross-Connection: displaying list (DXC 4/1)

Path (Action-Read)
The system displays a window containing a list of all cross-connections present in the equipment.
In the window are displayed the information relevant to the cross-connection (FROM and TO
channel, Type of connection, type of Traffic, Administrative state, Signal type that indicates if the
traffic is concatenated, simple, split channel) and to the associated path protection (FROM and TO
channel protection channel), if present.
See Also:
Operative States
SNC PROTECTION: MANAGING (DXC 4/1)

Path (Connection Configuration-Path Protection-Management)
Use this option to manage the Subnetwork Connection Protection.
IMPORTANT For STM-16 MUX 4/3 Sonet mode, the alarm suppression must be correctly set
on all STS-1, because if you apply a change on a STS-1, this change will be
applied on all STS-1 belonging to the same STS-3, independently from the fact
that SNCP has been configured on all STS-3.
To select the channel to be protected (and to activate Action menu):

* Select the Type 5, 6, 6E, 7, 7E Ports Subrack used for the connection.
* Select the Tributary Unit (STM-N) used for the connection.
1/140Mbit/s Unit).
* Select the SDH Traffic Type.
* Select the channel to be protected.
Note For Virtual concatenated the configuration of Worker and Protection has to be the
same for each group.
Path protection for Virtual concatenated traffic must be set independently on each AU.

.
Issue:1
See Also:
Operative States, SONET STS-1 Setup
SNC Protection: configuring (DXC 4/1)

Path (Action-Path Protection-Create)
This option is used to add a SNC protection connection; it is available only for connections not yet
protected.
* Select the Type 5, 6, 6E, 7, 7E Ports Subrack to be used for the SNC protection.
* Select the Electric/Mux Unit (or Optic/Mux Unit) to be used for the SNC protection.
* Select the PORT containing the channel to be used for the SNC protection (in case of
NxSTM-1 or 4xSTM-1/140Mbit/s Unit).
* Select the AUG containing the channel to be used for the SNC protection (in case of
STM-N channel).
* Select the free channel/AUG to be used for the SNC protection.
In case of more than one channel/AUG is necessary to protect the cross-connection (VC-nC cross-
connection), an indication will appear to remind the number of channel/AUG to select:

.
Issue:1
the traffic on the worker after repair of a failure that caused paths to be switched.
* Set the Hold Off time for SF and SD criteria.
See Also:
Hold off: Management
* Press APPLY.
Clicking on the "Signal Degrade Thresholds" a window that shows the pre-defined Signal Degrade
Thresholds appears.
See Also:
Cross-Connections: management (DXC 4/1)
SNC Protection: displaying information (DXC 4/1)

Path (Action-Path Protection-Read)
Use this option to display information about a SNC protection connection.
This window displays information on the protection mode, on the worker designation, on the
protection state and also an indication of protected and in use channel status.
Use REFRESH push button to update the protection status.
Thresholds appears.
See Also:
Operative States, SNC Protection: configuring (DXC 4/1)

.
Issue:1
SNC Protection: modifying (DXC 4/1)

Path (Action-Path Protection-Modify)
Use this option to modify the Protection Mode (Revertive/Not Revertive) of an already stored SNC
protection connection.
Press APPLY.
SNC Protection: removing (DXC 4/1)

Path (Action-Path Protection-Delete)
This option is used to remove an SNC protection connection.
See Also:
SNC Protection: switching (DXC 4/1)

Path (Action-Protection Switch)
Using this option it is possible to switch an SNC protected connection from the worker side to the
protection side and vice versa.
a. VC2-5C Cross Connection:

.
Issue:1
b. VC4-4C Cross Connection:
c. Other Cross Connection types:

.
Issue:1
To switch the SNC protection:

* Press APPLY.
Use REFRESH push button to update the protection status.
Thresholds appears.
See Also:
Operative States
SNC Protection: setting the WTR period (DXC 4/1)

Path (Action-WTR Period)
This option is used to set the restoration time (WTR) for the SNC Protection. Traffic is restored on
the worker path when no alarms are present for the WTR time.
WTR is enabled only when protection mode has been set to revertive.
To set the WTR:

* Indicate the WAIT TO RESTORE PERIOD in periods, 30 seconds each (30sec to 30
min).
* Press APPLY.
SNC Protection: swapping role (DXC 4/1)

Path (Action-Prot Role Swap)
This option is used to swap the roles between the worker and the protection channel of SNC
protected connections. The role can be modified only if no monitor cross-connection is present on
the worker channel.
a. VC2-5C Cross Connection:

.
Issue:1
b. VC4-4C Cross Connection:
c. Other Cross Connection types:

.
Issue:1
To swap the SNC protection roles:

* Select the worker channel whose role must be swapped.
* Press APPLY.
See Also:
Operative States, SNC Protection: configuring (DXC 4/1), SNC Protection: modifying
(DXC 4/1), SNC Protection: removing (DXC 4/1), SNC Protection: switching (DXC 4/1)
SPLIT CROSS-CONNECTION: MANAGING (DXC 4/1)

This option is used to manage the split accesses.
Split Cross-Connection: configuring accesses (DXC 4/1)

Path (Connection Configuration-Split Access-Create)
Use this option to create the split accesses. For unidirectional cross connections, this operation
allows the connection between the FROM port and the selected TEST port, the original TO port
transmits AIS. For bidirectional connections it is possible to create a split access either unidirectional
or bidirectional. In the first case the operation is the same as for the unidirectional connections (the
selected direction is split). In the case of bidirectional split access both FROM and TO ports are
connected to the TEST port, the original TO port transmits AIS.
To select the cross connection to be splitted:

* Select the X Connection Kind.
* Press OK.
IMPORTANT The splittable cross connections must satisfy the conditions shown in the
window.
According to the previous selection a list of connection (and the relevant information) will be
displayed.

.
Issue:1
* From the list select the cross connection to be split.

See Also:
Operative States, Cross-Connection: configuring (DXC 4/1)
Split Cross-Connection: selecting the test port (DXC 4/1)
To select the cross connection to be splitted:

* Select the port subrack containing the test port.
* Select the unit.
* Select the port to be configured as TEST port for the split access.
IMPORTANT The TEST port must be already configured.
* Select the type of split access (unidirectional or bidirectional).

* Press APPLY.

.
Issue:1
Split Cross-Connection: displaying a list of accesses (DXC 4/1)

Path (Connection Configuration-Split Access-Read)
This option is used to display a list of configured split accesses.
See Also:
Operative States, Split Cross-Connection: configuring accesses (DXC 4/1)
Split Cross-Connection: removing an access (DXC 4/1)

Path (Connection Configuration-Split Access-Delete)
This option is used to delete a configured split accesses.
To select the split access to be deleted:

* Select the split access to be deleted from the list.
* Press OK.
See Also:
Operative States, Split Cross-Connection: configuring accesses (DXC 4/1)
UNIDIRECTIONAL DROPPED CONNECTIONS: MANAGING (DXC 4/1)

Use this option to manage Unidirectional Dropped Connections.
Note For DXC 4/1 512x512 this option is not yet available.
Unidirectional Dropped Connection: configuring (DXC 4/1)

Path (Connection Configuration-Unidirectional Dropped Connection-Create)
To select the type of cross connection to use for the UDC:


.
Issue:1
* Select the X Connection Kind.

* Press OK.
IMPORTANT The cross connections (FROM and Protection channels) to be used to create a
unidirectional dropped connection must satisfy the conditions showed in the
window.
When using broadcast connections as Worker or Protection, a Master
connection must be selected.
The channel selection window appears.

* Select the WORKER and PROTECTION channels to be dropped.
See Also:
Operative States
Unidirectional Dropped Connection: selecting the drop leg channel

(DXC 4/1)
This option is used to configure the drop leg of a Unidirectional Dropped Connection.
To select the drop leg of the Unidirectional Dropped connection:

* Select the card.

.
Issue:1

* Select the drop leg port for the UDC.
IMPORTANT The drop leg port must be already configured.
* Press APPLY.
Unidirectional Dropped Connection: displaying information (DXC 4/1)

Path (Connection Configuration-Unidirectional Dropped Connection-Read)
The system displays a window containing a list of all Unidirectional Dropped Connections present in
the equipment.
See Also:
Operative States, Unidirectional Dropped Connection: configuring (DXC 4/1)
Unidirectional Dropped Connection: removing (DXC 4/1)

Path (Connection Configuration-Unidirectional Dropped Connection-Delete)
The system displays a window containing a list of all Unidirectional Dropped Connections present in
the equipment.
To delete a Unidirectional Dropped connection:

* Select the UDC from the list.
* Press APPLY.
See Also:
Unidirectional Dropped Connection: switching (DXC 4/1)

Path (Connection Configuration-Unidirectional Dropped Connection-Switch)
This option is used to switch the protection on the drop leg of the Unidirectional Dropped
Connection.
To switch a Unidirectional Dropped connection:

* Select the UDC from the list.
* Press APPLY.
See Also:

.
Issue:1
TANDEM CONNECTION: MANAGING

This option allows to define the Tandem Connection Termination. A Tandem Connection is set-up to
provide monitoring for a segment of a path. The Tandem Connection Termination function marks
the end points of a Tandem Connection. Specific information is added by the Source function at the
in side of Tandem Connection, this information is extracted to establish defect detection and
performance monitoring for the path segment associated to the Tandem Connection.
Tandem Connection: creating

Path (Connection Configuration-Tandem Connection-Setup)
This option is used to select the channel on which a VC Tandem Connection has to be created. The
channel to be selected (STM-N, NxSTM-1 ports or 4x140/155Mbit/s ports configured as 155Mbit/s)
must satisfy the following requirements:
1. for the STM-1 Unit the relevant card version must be STM1-Type 2
2. in case of LO VC Tandem Connection for the STM-4 Unit the relevant card version must be
STM4 Type 2 and for the 4xSTM-1 must be NxSTM1 Type 3.
To select the channel used for a Tandem Connection:

* Select the PORT (in case of STM-N, NxSTM-1 ports or 4x140/155Mbit/s ports configured
as 155Mbit/s).

.
Issue:1
* Select the AUG.

* Define the TC Type to specify the traffic type to be monitored.
* Define the channel selection criteria by clicking on the exclusive buttons SINGLE or
configure) more than one channel at the same time, SINGLE allows to select only one
channel.
In case of multiple selection all the selected channels will be configured with the same
operational parameter.
* Select the SDH channel/s.
Unit Limitations push button makes available a list of the restrictions applied to the STM-4 and
NxSTM-1 units.
See Also:
How To Select Objects, Operative States, Port: configuration, STM-N Port:
configuring frame and supervisory unequipped state
Tandem Connection: configuring

Path (Action-Setup)
This option allows to configure the channel used as Tandem Connection Termination.
NOTICE LO Tandem Connection on MUX 4/3 Sonet mode is accepted only on Matrix
side.
To configure the channel involved in the Tandem Connection:

* Select the TC Side to define if the matrix is included in the Tandem Connection path
(Matrix side) or only the Line side is involved (Line side).

.
Issue:1
NOTICE Selecting the Matrix side, the involved channel has to be connected.
* Select the VC TC State to define the role of the selected port/channel:

Disabled
The channel/port is not used for the Tandem Connection.
Source
The channel/port acts as Source (Transmit Side).
Sink
The channel/port acts as Sink (Receive Side).
Sink & Source
The port acts as Sink and Source.
* Use the VC TC Mode to select the byte N1/N2 coding (ETSI Mode or ITUT (CCIT)
Mode)
Note ITUT (CCIT) Mode is not yet managed.
* Use the Sink Count Mode to define the count mode for the Tandem Connection error
rate evaluation (Bip Single Error or Bip Block Error).
Note Bip Single Error mode is not yet managed.
* Use Unit Count Mode to select the type of unit error rate evaluation mode (Poisson or
ETSI).
For STM-1 Unit Type 2 the count mode and the DEG thresholds are the same previously defined
during the port configuration while, for STM-N and NxSTM-1 Units, these parameters can be
different from the once set on the port configuration.
Use Poisson DEG Threshold (10-5 to 10-9) to set the threshold for considering the incoming stream
degraded. This calculation uses the byte B3 and N1 for the HO level, and the byte V5 (bit 1 and 2
relevant to the BIP-2) and N2 for the LO.
Enter the percentage of BBE (DEG Threshold) detected and the number of errored seconds which
are activating/deactivating a bad/good period. The BBE counting is based on the comparison
with the byte B3 and N1 for the HO, and V5 (bit 1 and 2 relevant to the BIP-2) and N2 for the LO.
* Select Sink AIS on ISF to insert an AU-AIS on the appropriate outgoing signal when an
Incoming Signal Failure (ISF) is received from the Source direction.
* Select Sink AIS on TC_UNEQ to insert an AU-AIS on the appropriate outgoing signal
when a Tandem Connection Unequipped (TC-UNEQ) is received from the Source
direction.
Note These two options can be accessed when Sink or Sink & Source VC TC State has
been selected.
The default value for AIS on TC_UNEQ in LO Tandem Connection is Disabled. The

.
Issue:1
choice of Enabled or Disabled for AIS on ISF will involve all the TU-3 belonging to the
same AUG where a LO Tandem Connection is configured as Sink or Sink&Source.
* Press APPLY.
See Also:
Cross Connections: restoration (DXC 4/1)
Configuring as Tandem Connection Termination a channel belonging to a line MSP protected, in
case of activation of the protection, the same configuration will be moved on the protection side.
See Also:
Tandem Connection: displaying

Path (Connection Configuration-Tandem Connection-Read)
This option allows to displays the operational parameters of the configured Tandem Connection
Termination.
Note If a Tandem Connection Termination has been configured on a protected channel, in
case of protection activation, the Tandem Connection will be always displayed on the
worker side, even if the TC has been moved.
See Also:
Operative States, Tandem Connection: configuring

.
Issue:1
AUXILIARY UNIT CONNECTION: MANAGING

Path (Connection Configuration-Auxiliary Card Connections- Auxiliary X-Conn
Management)
The Auxiliary Card works as a matrix card directly on the SOH bytes of the SDH frame, but can also
access them via an external G.703 64Kbit/s co-directional and/or V11 Nx64Kbit/s contra-directional
interface.
Data connections have access to 40 SOH bytes, with a speed of 64Kbit/s, but they can also use
DCC bytes (contra-directional interface) in order to obtain faster transmissions: 192Kbit/s or
576Kbit/s (fast V11). Furthermore, it is also possible to create 2 phonic connections from one NE to
another, by using the serial outputs available on each shelf (EOW Extension).
This option allows to select the auxiliary channel that will be used for an auxiliary connection.
To select the auxiliary channel to connect:

* Select the Port Subrack on which an auxiliary connection has to be defined.
* Define the type of channel by using the Type pull down option.
Phone EOW1/2
The bytes E1 and E2 provide orderwire channels (EOW - Engineering Order Wire) for voice and
communication between the local and the remote equipment connected to the STM-N interfaces.

.
Issue:1
E1 is a part of the RSOH while E2 is a part of the MSOH.

This service allows also a 64kbit/s connection between the local and the remote equipment
connected to the STM-N interfaces, making use of the F1 byte of the RSOH.
For a maximum of two STM-N interfaces it is possible to use both E1 and E2 as EOW channels.
This implies that each one of these STM-N interfaces uses a double EOW capacity.
If both E1 and E2 of the same STM-N interface is used for EOW, E1 is used for selective calls and
E2 for omnibus calls.
G.703
The free bytes of SOH, in the STM-N interface, are used for point-to-point connections between the
local G.703 co-directional interface and the remote equipment connected to the STM-N interfaces.
V11
The free bytes of SOH, in the STM-N interface, are used for a point-to-point connections between
the local V11 contra-directional interface and the remote equipment connected to the STM-N
interfaces.
A 3x64Mbit/s V.11 can be used to carry DCCr (192kbit/s) while a 9x64Mbit/s V11 channel can carry
DCCm (576kbit/s).
* Select the channel by clicking on it in the CHANNEL Selection field.
The EOW can be also accessed by means of a standard 2 wire analogue interface or a 4 wire
(analogue or digital) interface. These interfaces are called EOW extensions and they allow to create
a point-to-point connection between two equipment which do not communicate by traffic links (only
Direct connection is allowed).
Ext. Dig.
Digital EOW Extension.
Ext. An.
Analogue EOW Extension.
See Also:
Auxiliary Unit Connection: configuring
Refer To:
Equipment Manual, section "Functional Description"

.
Issue:1

This option allows to create an auxiliary connection. The layout of the window changes in
relationship to the Type of channel selected in the previous window.
The Phone EOW1/2 channel type gives access to all the options available (Direct, Ring and By-
Pass connection can be configured) while the other types of channels (G.703 and V11) allow only
point-to-point connections (then only Direct connection kind can be selected).
To configure the EOW channels:

* Select the kind of phonic/data connection using the X Connection Kind pull down menu.
The Auxiliary Unit allows three kind of connection:
Direct
Uses any SOH accessible byte (including E1 and E2) from an SDH interface and creates a phonic
connection between the data stream coming from the card involved (one channel used).
Ring
Connects any SOH accessible byte (including E1 and E2) from an SDH interface to the same or a
different SOH byte on another SDH interface and creates a phonic connection between the data
stream coming from the card involved (two channels used).

.
Issue:1
By-Pass
Connects any SOH accessible byte (including E1 and E2) from an SDH interface to the same or a
different SOH/POH byte on another SDH interface via the internal "Digital By-pass function",
preserving the integrity of the end-to-end 64 kbit/s channel (two channels used).
The following steps have to be performed according to the chosen X Connection Kind option.
* Define if the equipment is used as Ring Master using the relevant pull down menu.
* If the system has been configured as Ring Master use the Ring CAI pull down menu to
define the side of the EOW ring on which the CAI has to be sent (CAI is a tone to check
the ring integrity).
Channel 1/2 identifies the first/second channel selected (see the following steps).
* Select in the left column the byte of the first channel used for the connection (this channel
is defined in the AUXILIARY CONNECTION window).
The RSOH and MSOH bytes are displayed as MS/RS: x-y, where x is the number of the row and y
the number of the column.
* Select the second channel by clicking on it in the CHANNEL Selection field.
Note Digital and analogue EOW extension can not act as second channel for the
connection. To define a connection via EOW extension select the relevant interface in
the AUXILIARY CONNECTION main window (first channel).
* Select in the right column the byte of the second channel used for the connection.
The RSOH and MSOH bytes are displayed as MS/RS: x-y, where x is the number of the row and y
the number of the column.
NOTICE The byte used in the first channel has to be different from the byte used in the
second channel. This restriction is due to the access to the same OH Bus.
* Press APPLY to confirm the creation of the EOW channel.

See Also:
Auxiliary Unit Connection: managing, Auxiliary Unit Connection: removing, Auxiliary
Unit Connection: displaying

.
Issue:1
Auxiliary Unit Connection: removing

Use this option to remove an Auxiliary Connection.
If all the auxiliary connections belonging to the same area (EOW1 or EOW2) are deleted, the area is
set to "offline". This state lasts even if after the deletion another auxiliary connection is created in the
area.
During this condition, if a connection has been established, the unit can receive a call originated
from another Auxiliary Unit, but is unable to make a call, until a reset has been performed, using the
button on the front panel of the card. This procedure allows to re-insert the unit in a service area.
See Also:
Auxiliary Unit Connection: displaying

Path (Connection Configuration-Auxiliary Card Connections- Auxiliary X-Conn List)
This option allows to displays Auxiliary Connection information.
See Also:

.
Issue:1
MANAGING ALARMS
ALARMS: MANAGING ATTRIBUTES (DXC 4/1)

Path (Fault-Config-Attributes)
Use this option to set the attributes (PRIORITY VALUE, and CATEGORY) for each single alarm.
To enable the Action menu (and to modify the alarm parameters):

* Select in the Alarm Source Identifier box the source of the relevant alarm.
* Select in Alarm Type box the alarm that you want to monitor/modify.
See Also:

.
Issue:1
MANAGING ALARMS
Alarms: configuring attributes (DXC 4/1)

Path (Action-Setup)
Use this option to set a new alarm priority and category (urgent, not-urgent, etc.) of a selected
alarm. Each alarm has default values for priority and category.
To set the alarm priority and category:

* Using the Alarm Priority sliding bar (or arrow buttons) set the new priority value for the
selected alarm in the range 1 to 255 (1 is the highest priority, 255 the lowest).
* Use Alarm Category box to set the new category for the alarm.
* Press APPLY.
See Also:
Alarms: displaying attributes (DXC 4/1)

Path (Action-Read)
Use this option to display the priority and category of a selected alarm.
See Also:
Cross-Connection: displaying the port/matrix fail alarms (DXC 4/1), Alarms:
configuring attributes (DXC 4/1)

.
Issue:1
MANAGING ALARMS
ALARMS: MANAGING MONITORING STATE

Path (Fault-Config-Monitoring)
Use this option to enable/disable the reporting of each alarm indication. By default the report of all
the alarms is enabled.

* Select the Subrack with the unit where the alarm is detected.
* Select the unit where the alarm is detected.
* Select the AUG (in case of STM-N Unit) or the Port Id (in case of NxSTM-1 or
4x140/155Mbit/s Unit).
* Select in the ALARM NUMBER Selection box the Alarm Source Type and the Alarm
Source Number of the alarm.
See Also:

.
Issue:1
MANAGING ALARMS
Alarms: configuring the monitoring state

Path (Action-Setup)
Use this option to enable/disable the alarm reporting (Monitoring State).
The enabled alarms are displayed in the MONITORED Alarm Type box, the disabled alarms are
displayed in the NOT MONITORED Alarm Type box.
To disable an alarm:
* Click with the mouse on the alarm listed in the MONITORED Alarm Type box.
The alarm will be automatically moved to the NOT MONITORED Alarm Type box.
* Press APPLY.
To enable an alarm:
* Click with the mouse on the alarm listed in the NOT MONITORED Alarm Type box.
The alarm will be automatically moved to the MONITORED Alarm Type box.
* Press APPLY.
See Also:

.
Issue:1
MANAGING ALARMS
Alarms: displaying monitoring state

Path (Action-Read)
Use this option to display the Monitoring State of the alarms.
The enabled alarms are displayed in the MONITORED Alarm Type box, the disabled alarms are
displayed in the NOT MONITORED Alarm Type box.
See Also:
Cross-Connection: displaying the port/matrix fail alarms (DXC 4/1), Alarms:
configuring the monitoring state
ALARM: FILTERING
Path (Fault-Config-Filtering)
This option is used to filter the alarms that are reported to Local Controller, Alarm Log and TMN
(Telecommunication Management Network).
For example, if a threshold of 150 has been specified, only alarms having a priority lower than or
equal to 150 will be reported.
To select the alarm filtering:

* Use Local Controller to specify the threshold for alarms displayed by the Local
Controller.
* Use Alarm Log to specify the threshold for alarms registered by the alarms archive.
* Use Element Manager to specify the threshold for alarms issued to the TMN
(Telecommunication Management Network).

.
Issue:1
MANAGING ALARMS
* Use Get Active Alarms Mode to define the kind of the alarms that will be displayed by
pushing the Card Active Alarm push button (or selecting the Card Active Alarm option
in the Action menu).
NOTICE Every time the Control Application is restarted this parameter is set to "Active-
not-masked" (default value).
* Press APPLY.
See Also:
Alarms: configuring the log full threshold, Alarms: displaying subracks/units active
alarms, Active Alarms: filtering of the list
ALARMS: CONFIGURING SOH BYTE PERSISTENCY

Path (Fault-Config-Persistency)
This option is used to manage the persistency for the detection of the SOH byte indication (bytes J0,
J1, K2, S1, C2, G1). It is possible to specify the number of frames that the byte has to be received
with the same value in order to change its state for the alarm detection/suppression.
To manage the SOH byte persistency:

* Modify the number of frames (value range from 1 to 5) that the system verifies before
changing the state of the SOH byte.
* Press APPLY.

.
Issue:1
MANAGING ALARMS
ALARMS: CONFIGURING REPORTING STATE

Path (Fault-Config-Reporting State)
Use this option is to Enable/Disable notification of alarms and event messages from the Equipment.
To modify the reporting state of the alarms:

* Use F Event Reporting State to enable/disable the notification of the messages to the
Local Controller.
* Use Q Event Reporting State to enable/disable the notification of the messages to the
Telecommunication Management Network.
* Use Log Event Reporting State to enable/disable the notification of the messages to the
Alarm Log.
* Press APPLY.
Note Software Error Reporting State is used only for factory test.
ALARMS: FILTERING OF THE FREE PDH PORTS FAULT

Path (Fault-Config-Free PDH port fault mask)
This option is used to enable/disable the detection of the network alarms of all the configured PDH
ports not yet cross-connected.
NOTICE This operation is allowed when the controller status is set to OFF-LINE.

.
Issue:1
MANAGING ALARMS
ALARMS: SERIAL LINK OFF INHIBITION

Path (Fault-Config-Serial Link Off Inhibition)
This option is used to automatically mask the Serial Link Off alarm associated to a SIO line not
equipped. This option is set Disable by default. If you choose the Enable state, the alarm that should
arise, cause of subrack configuration missing, will be not monitored.
ALARMS: AIS / RDI MASKING

Path (Fault-Config-Set Default AIS/RDI)
This option allows to decide if an AIS (Alarm Indication Signal) or a RDI (Remote Defect Indication)
alarm has to be monitored. The default state is Disable.
ALARMS: PORT MODE

Path (Fault-Config-NE Port Mode Setup)
The Port Mode functionality is implemented on DXC equipment in order to prevent alarms being
raised during trail provisioning action, i. e. when port set-up and cross-connection have been done
but no valid traffic signal is present. Port mode is a status assigned to each physical traffic port. In
particular the Port Mode function is applied at physical layer, so that only the LOS alarm is hidden,
or not, to the management system. Please note that the LOS defect will be anyway detected and
the standard consequent action and inhibition rules will be performed, independently from the status
assigned to the port.
Note This option is available on the Type 3, 6, 6E, 7, 7E Subracks.

.
Issue:1
MANAGING ALARMS
Port Mode supports three different states:

Auto
The AUTO state corresponds to a situation with Port Mode function enabled, in which all defects
are detected but the LOS indication is not reported to the management system. It differs from Not
Monitored (NMON state) because, when the LOS defect is cleared, the port automatically transits
to the Monitored (MON) state.
Monitored
The Monitored (MON state) corresponds to a situation with Port Mode function disabled, in which
all defects are detected and reported to the management system.
Not Monitored
The Not Monitored (NMON state) corresponds to a situation with Port Mode function enabled, in
which all defects are detected but the LOS indication is not reported to the management system.
Please note that if a LOS defect is detected, all defects of the lower order layers are automatically
inhibited by it and so hidden to the management system. On the contrary if LOS defect is not
present all defects, if detected, shall be reported to the management system according to the
standard inhibition rules.
The state applied in this field will be the state displayed when you will configure a port.
Note If you are in Monitored state and you want to set Auto, the comand is ignored if the
port is not in LOS, otherwise if the port is in LOS is possible to change state (from
MON to AUTO). If the CCU is in Off-line state no alarms are detected and all changes
on the Port Mode will be accepted without any check.
See Also:
Port: configuration

.
Issue:1
MANAGING ALARMS
ACTIVE ALARMS: FILTERING OF THE LIST

Path (Fault-Active Report-Active Alarm List)
This option is used to display all alarms active in the equipment.
It is possible to set a filter on the report to disable the display of some alarms.
To enable the Action menu (and to select the searching parameters):

* Use Alarm State to define the alarm state to be displayed (Active-masked, Active-not-
masked, All-Alarms)
* Use Alarm Category to set the alarms category to be displayed (Urgent, Not-Urgent,
Indicative, External, Internal, MLQ, All-Alarms).
* Use Report Type to specify the type of alarm report to be displayed.
Highest Priority
The alarms are displayed following the alarm priority degree.
All Alarms
All alarms are displayed.
Active Alarms: displaying

Path (Action-Read)
This option is used to display a list of all alarms present in the equipment.
See Also:

.
Issue:1
MANAGING ALARMS
ALARMS: DISPLAYING SUBRACKS/UNITS ACTIVE ALARMS

Path (Fault-Active Report-NE Alarms Summary)
This option allows to display and acknowledge the alarms active in each subrack and unit.
In the window is graphically displayed the layout of each rack and the relevant subracks.
The button REFRESH updates the alarms in each subrack.
The button FORWARD is used to navigate in the other subracks.
For each subrack are available the following buttons:

.
Issue:1
MANAGING ALARMS
In each subrack box is also available a subrack alarm summary represented by a row of signallers:
In each signaller is indicated the total number of alarms present for each alarm category.
Different categories are displayed, depending on the type of alarm processing that has been
chosen.
See Also:
Alarms: displaying subrack active alarms

Use this push-button to display all alarms present in the selected subrack.
System will show the following selection box:
Use the proper button to choose between the alarms or the abnormal conditions (forced MSP
protection switch or forced 140Mbit/s, 34Mbit/s, 45Mbit/s line protection switch) and press OK to
activate the report window.
The Subrack Active Alarms window will appear immediately after the button
is pushed for all the other subracks.

See Also:
Active Alarms: acknowledgement push-button
Use this push-button to acknowledge the alarms of the subrack.

Select OK to acknowledge all the subrack alarms and CLOSE to return to the previous window.

.
Issue:1
MANAGING ALARMS
Active Alarms: displaying alarmed unit

By means of this button it is possible to display the alarms relevant to a specific unit.
A group of signallers is present in each unit to indicate the different alarm categories.
In each signaller is indicated the total number of alarms present for each alarm category.
Different categories are displayed, depending on the type of alarm processing that has been
specified.

.
Issue:1
MANAGING ALARMS
See Also:
Active Alarms: displaying unit active alarms

Use the
push-button to display all alarms present in the relevant unit.

This facility is also accessible from all the windows relevant to the port units or the matrix and CT
subracks (i.e. protection and cross connection). This option is available selecting the Card Active
Alarm item in the Action menu.
See Also:
ALARMS: MANAGING THE EVENT HISTORY FILE

Path (Fault-Event Report-History DB)
When the Local Controller is connected to the F Interface an event history file is created on the hard
disk of the PC.
A label containing Year_Month_Day followed by suffix ah designates the history file. Information
concerning active or cleared alarms are automatically stored in the history file.
In the file are also stored information related to other events occurred in the system (e.g. loopback,
service mode indication, lamp test).

Select the desired history file in the list.

.
Issue:1
MANAGING ALARMS
Alarms: removing the selected file

Use this option to remove the selected history file from the hard disk.
Alarms: displaying the alarm history file

Path (Action-Read)
Use this option to display all events stored in the selected history file.
See Also:
Alarms: removing all alarm history files

Path (Action-Delete All)
Use this option to remove all history files from the hard disk.
ALARMS: DISPLAYING THE LOG FILE

Path (Fault-Event Report-NE Log DB-Read)
Alarm log is a file stored on the Central Control Unit containing a wrap around list of alarms and
other events (e.g. protection switches).
Alarm Log is managed in wrap-around mode: when the log is full, incoming events are overwriting
the older ones. A Log Full Alarm indication arises when the Alarm Log size exceeds a presettable
threshold.
See Also:
ALARMS: CONFIGURING THE LOG FULL THRESHOLD

Path (Fault-Event Report-NE Log DB-Log Full Threshold)
This option is used to set the log full alarm threshold. Since the alarm log has a maximum size of
1000 events, using this option Operator can select after how many events the system will send a
Log Full alarm indication.
* Use Log Full Alarm Threshold (0 to 100) to select the threshold percentage for the
Alarm Log size. An alarm will be generated when the selected threshold will be reached.
* Press APPLY.
See Also:
Alarm: filtering
ALARMS: CLEARING THE ALARM LOG

Path (Fault-Event Report-NE Log DB-Reset)
Use this option to clear the alarm log file and to start a new alarm collection.
This operation is clearing the Log Full alarm (if present).
See Also:
Alarms: displaying the log file

.
Issue:1
MANAGING ALARMS
ALARMS: FAULT ACKNOWLEDGE

Path (Fault-Fault Acknowledge)
Using this option the operator can acknowledge all alarms currently present in the equipment.
ALARMS: ENABLING/DISABLING PARKING MODE

Path (Fault-Parking)
Use this option to enable/disable the alarm sent to Local Controller, Alarm Log File, Element
Manager and to switch-off all rack lamps on the equipment, for example during a maintenance
phase.
When Parking state is enabled all rack yellow lamps and all yellow LEDs on identification units blink
every second.
To enable (disable) the parking mode:

* Use Parking State to enable/disable the alarms.
* Press APPLY.
ALARMS: DISPLAYING SIGNAL DB LOG FILE

Path (Fault-Event Report-Signal DB-Read) [LC]
Use this option to display the Signal DB Log File. The DB Log File collects operation and run-time
errors of the Local Controller.
ALARMS: RESETTING SIGNAL DB LOG FILE

Path (Fault-Event Report-Signal DB-Reset) [LC]
Use this option to clear the Signal DB Log File.
See Also:
Alarms: displaying signal DB log file
ALARMS: UPDATING ALARM COUNTERS

Path (Fault-Refresh Alarm Counters)
Selecting "OK" in the confirmation window, all the icons state (virtual lamps, indications) and the
values (messages, counters) present in the main window of the LC will be updated.

.
Issue:1
PERFORMANCE MONITORING
STM-1 AND PDH PORT PERFORMANCE PARAMETERS: CONFIGURING

THRESHOLDS (DXC 4/1)
Path (Performance-NE Configuration-Operating Threshold Setup)
Using this menu it is possible to preset the thresholds for the SES (severely errored seconds) and
for the UAS (UnAvailable Second) relevant to STM-1 and PDH Port.
For each SDH monitored entity (e.g. VC-4 Near End) it is possible to specify the percentage of
errored blocks which are causing the issue of a SES while for PDH monitored entity (e.g. 2Mb) the
thresholds have to be specified as number of Errored Frame Alignment Signal (in case of signal
structured but not organized in blocks) or number of Error Detection Code (in case of signal
structured and organized in blocks).

.
Issue:1
To set the thresholds for SES and UAS:

* In the CV THRESHOLD VALUES FOR SES CLASSIFICATION field is possible to
preset the thresholds for SES (Severely Errored Second), i.e. the percentage of errored
blocks detected in one second needed to classify that second as SES. Such threshold
by default (according to the G.826 reccomendation) is defined 30% (quantity of errored
blocks detected in the observation period).
* In the SONET PDH field is possible to set the SES thresholds for checking the quality of
the plesiochronous 45Mbit/s channel (DS3 configured as C-Bit Parity Mode) received by
the 1x45Mbit/s T-Mux unit. Such thresholds can be selected in the ranges shown in
brackets.
By default all the parameters values are set to 45.
* Within the SUE THRESHOLD (Start of Unavailable Event) field it is possible to preset the
number of consecutive SES (SES Value) needed to start an unavailable period.
The SES Value threshold is presettable within the range 2 to 10 (with a default value of 10). When
the number of consecutive SES exceeds the SES Value, UAS is increased once per second for the
entity and a Unavailable time starts. The consecutive SES counted are considered to be part of
the Unav. period.
* Within the TUE SECOND THRESHOLD (Termination of Unavailability Events) field it is
possible to preset the number of consecutive EFS (Error Free Second) needed to
terminate an unavailable period.
The Free Value threshold is presettable within the range 2 to 10 (with a default value of 10). When
the number of consecutive EFS (Error Free Second) exceeds the Free Value, the incrementing of
the UAS cease and the Unav. time stops. The consecutive EFS counted are considered to be part
of available time.
* Within the C-SES THRESHOLD (Consecutive SES) field it is possible to preset the
number of Consecutive Severely Errored Seconds (C-SES) needed to raise the C-SES
event.
The CSES Value threshold is presettable within the range 2 to 9 (with a default value of 5). When
the number of consecutive CSES (Consecutive Severely Errored Seconds) exceeds the CSES
Value, a C-SES event will be generated.
* In the PDH FAS THRESHOLD VALUES FOR SES CLASSIFICATION field is possible
to set the out of frame threshold set for performance measurement on plesiochronous
local side tributary, i.e. the number of out of frame blocks detected (checking the Frame
Aligment Signal) in one second needed to classify that second as SES.
The following parameters can be set for checking quality of the incoming plesiochronous 2Mbit/s
signal. The threshold can be selected in the range shown in brackets.
Incoming Ne 2Mb Framed (1..1500)

2Mbit/s Near End entity type. The threshold to be specified is relevant to a received 2Mbit/s signal,
structured, not CRC-4.
Incoming Ne 2Mb Framed CRC-4 (1..1000)
2Mbit/s Near End entity type. The threshold to be specified is relevant to a received 2Mbit/s signal,
structured and CRC-4.

.
Issue:1
Incoming Fe 2Mb Framed CRC-4 (1..1000)

2Mbit/s Far End entity type. The threshold to be specified is relevant to a received 2Mbit/s signal,
structured and CRC-4.
Outgoing Ne 2Mb Framed CRC-4 (1..1000)
2Mbit/s Near End entity type. The threshold to be specified is relevant to a transmitted 2Mbit/s
signal, structured and CRC-4.
Outgoing Fe 2Mb Framed CRC-4 (1..1000)
2Mbit/s Far End entity type. The threshold to be specified is relevant to a transmitted 2Mbit/s
signal, structured and CRC-4.
The following parameters can be set for checking the quality of the plesiochronous 34/45Mbit/s
channels. The threshold can be selected in the range shown in brackets.
Framed 34_45Mbit/s Ne (1..52)
34-45Mbit/s Near End entity type. The threshold to be specified is relevant to a received 34-
45Mbit/s signal, structured.
PDH Framed 34_45Mbit/s Fe (1..52)
34-45Mbit/s Far End entity type. The threshold to be specified is relevant to a received 34-45Mbit/s
signal, structured.
The following parameter can be set for checking the quality of the plesiochronous 140Mbit/s
channel. The threshold can be selected in the range shown in brackets.
Framed 140Mbit/s (1..69)
140Mbit/s Near End entity type. The threshold to be specified is relevant to a received 140Mbit/s
signal, structured.
The following parameter can be set for checking the quality of the plesiochronous 45Mbit/s VC3
channel. The threshold can be selected in the range shown in brackets.
Framed 45Mb/VC3 Ne (1..2444)
45Mbit/s VC3 Near End entity type. The threshold to be specified is relevant to a received 45Mbit/s
signal, structured.
* Press APPLY.
See Also:
Performance Management

.
Issue:1
PERFORMANCE PARAMETER: MANAGING EXCEPTIONS

THRESHOLDS
Path (Performance-NE Configuration-Exceptions Threshold Setup)
In the DXC it is possible to configure sixteen sets of exception threshold sets related to the
aggregation period (15 minutes or 24 hour), which give an immediate indication of Performance
Degradation.
To enable the action menu:

* Click on the Entity Type to select the entity to be monitored.
* Click on the Set Id to select the set of performance thresholds to be configured.
See Also:

.
Issue:1
Performance Parameter: configuring exception thresholds

Path (Action-Set)
Use this option to preset the Exception Threshold for the following performance parameters:
n BBE (Background Block Error)
n ES (Errored Second)
n SES (Severely Errored Seconds)
n UAS (UnAvailability Seconds)
n OFS (Out of Frame Seconds)
n PSC (Protection Switch Count)
n PSD (Protection Switch Duration)
n PJE-POS (Pointer Justification Event - Positive)
n PJE-NEG (Pointer Justification Event - Negative)
n C-SES (Consecutive Severely Errored Seconds)
n related to the selected entity in the aggregation period (15 minutes or 24 hour).
To set the exception threshold:

* Enter the desired threshold for each performance parameter and for each register (15
minutes or 24 Hours). Allowed values are indicated between brackets.
* Press APPLY.
See Also:

.
Issue:1
Performance Parameter: restoring default exception thresholds

Path (Action-Set default)
Use this option to set the default values for the selected set of exception thresholds.
* Press APPLY.
See Also:
Performance Parameter: displaying the exception thresholds

Path (Action-Read)
Use this option to display the Exception Thresholds.
See Also:
Performance Parameter: configuring exception thresholds
PERFORMANCE: DATABASE USAGE

Path (Performance-NE Configuration-Number Monitored Entities)
This option is used to get an indication of the performances Quality database current usage.
The information displayed in the window are:
Monitored Entities Service Started

Number of monitored entities started in Service Mode
Monitored Entities Maintenance Started
Number of monitored entities started in Maintenance Mode
Monitored Entities Service Free
Number of available entities which collection can be started in Service Mode
Monitored Entities Maintenance Free
Number of available entities which collection can be started in Maintenance Mode

.
Issue:1
Other Information option allows accessing a window where all the possible entities that can be
monitored are listed.
Performance Details facility allows to perform an integrity check on the Quality Database
(comparison between the information stored in the Configuration Database against information
stored in the Quality Database) and to get information about the performance data collections state
on the configured unit.
IMPORTANT Since this test takes about 4 minutes, to guarantee a correct result, it can be
activated only in the period starting from the fifth to the tenth minute of a fifteen
minutes register (before the system requests the data).
PERFORMANCE: LO LIMIT CONFIGURATION

Path (Performance-NE Config-Performance LO Limit Configuration)
This option is used to display the maximum number of LO monitorable entities for each card having
this capability.
PERFORMANCE: LO CURRENT LOAD

Path (Performance-Performance Monitoring START/STOP-Performance LO Limit Current
Load)
This option is used to display the current load condition in terms of LO monitorable entities started
on the selected card.
To display the current value from Performance Monitoring START/STOP:

* Select the Subrack Id.
* Select the Card Id.
* Select Action-Performance LO Limit Current Load.
Note The crossing of the values limit will be hinder with a relevant compliance
(Performance card limit).

.
Issue:1
PERFORMANCE: MANAGING DATA DISPLAYING

Path (Performance-Performance DataBase-Data Display)
Using the Performance Database menu it is possible to display and reset the contents of
performance data registers.
To enable the Action menu (and to display performance data):

* Select the unit.
* Select the port (Port Id).
* Select the Entity Type
* Select the Resource Identifier (in case the selected unit manages more than one entity
of the choosen type).
* Use Report Type to select the type of performance register to be displayed.
15 Min. Current
Performance data accumulated in the port during current 15min. period.
15 Min. Recent
Performance data relevant to the last 4 hours (16 samples of 15 minutes) accumulated in the
Central Control Unit.
24 Hour Current
Performance data relevant to the current 24 hours.

.
Issue:1
24 Hour Previous
Performance data relevant to the previous 24 hours.
* Use Date and Time to define the reference for the 15 Min. Recent registers to be read.
* In case the 15 Min. Recent register has been selected define the Number of register to
be read from the first one identified by the date and time previously selected.
* Press APPLY.
See Also:
Operative States, Performance Management, Performance: managing data collection
Performance: displaying data

Path (Action-Read)
Use this option to display the performance data relevant to a selected performance entity.
NOTICE Selecting the "PDH Near End" performance entity relevant to a 140Mbit/s port
with a "Signal Type" configured as "Unframed", the "Wrong Entity Type"
message will be displayed. This compliance appears to remind that it is
impossible the calculation of the selected performance entity for an "Unframed"
signal.
This window shows the performance data in the selected register with an indication of the report
date and time.
The Report Note field contains the following information:
Time Reset
Present only if a Time Reset has occurred.

.
Issue:1
Sample Incomplete
Present only if a sample is incomplete.
Worker or Protection Data
If available, it shows which card the data come from; if unavailable, it is set to Worker by default.
Report Note
Data information.
See Also:
Report Note
Use the REFRESH push-button to perform reading of the select register without closing the window.
Note The REFRESH push-button is only present with 15 Min Current option.
See Also:
Operative States, Performance Management, Performance: managing data collection
PERFORMANCE: RESETTING ALL NE REGISTERS

Path (Performance-Performance DataBase-Reset-All NE Data)
This option is used to reset (clear) all the performance data stored in the Performance Database of
the Central Control Unit.
Note The current registers can not be reset
See Also:
Performance: resetting registers of a selected port
PERFORMANCE: RESETTING REGISTERS OF A SELECTED PORT

Path (Performance-Performance Database-Reset-Port Data)
Use this option to reset the performance data relevant to a selected port.
According to the involved subrack two different procedures are available:
To make available the menu for Type 2 and 5 subrack:

* Select the unit.
* In case the unit has only one port select it. If the unit has more the one port select the
option All.
To make available the menu for Type 3/6/6E/7/7E subrack:

* Select the unit.
* Select the Entity Type.
Note For Type 3/6/6E/7/7E subracks it is possible to reset the performance data relevant to
a specific entity type.

.
Issue:1
See Also:
Performance: resetting register

Path (Action-Reset)
Use this option to reset the performance data relevant to:
n a selected port (Port Id) in case of Type 2 and 5 subracks.
n a selected Entity Type in case of Type 3/6/6E/7/7E subracks.
See Also:
Performance: resetting all NE registers, Performance: resetting registers of a
selected port
PERFORMANCE: MANAGING DATA COLLECTION

Path (Performance-Performance Monitoring START / STOP)
Use this option to manage the start/stop of performance data for each port.
IMPORTANT Before starting performance it is necessary to set the date and time used by the
DXC internal real time clock.

* Select the unit.

.
Issue:1

* Select the Entity Type
* Select the Resource Identifier (in case the selected unit manages more than one entity
of the choosen type).
* Use AUG with PJE counter enabled to select the AUG (in case of STM-4 or STM-16
Unit) on which the PJE (Pointer Justification Event) counting is performed.
Note The UNIT LIMITATIONS button describes the limitations for the configuration
choosen
See Also:
Performance: start maintenance based collection

Path (Action-Start Maintenance)
This option is used to start a maintenance based collection on a selected resource. Furthermore it`s
possible to specify which set and type of exception events have to be reported.
Maintenance based mode counts the performance parameter over both 24h and 15m time periods
(both the 24h and 15m register are generated).
This kind of evaluation is based on information relevant to each direction of transport indipendently
then it`s possible to define the transmit side to be monitored (Near End and/or Far End termination
collection reporting).

.
Issue:1
To enable the performance data collection:

* In case the selected entity type is VC-4 define if the PJE counting has to be started on
the relevant AUG or not.
* Use Working Mode to select the type of performance collection.
Excep 15m and 24h disabled, UAT rep. State disabled
24h and 15m performance exceptions disabled and UAT reporting disabled.
Excep 15m and 24h disabled, UAT rep. State enabled
24h and 15m performance exceptions disabled and UAT reporting enabled.
Excep 15m disabled, Excep 24h enabled, UAT rep. State enabled
15m performance exceptions disabled, 24h performance exceptions enabled and UAT reporting
enabled.
Excep 15m and 24h enabled, UAT rep. State disabled
24h and 15m performance exceptions enabled and UAT reporting disabled.
Excep 15m enabled, Excep 24h disabled, UAT rep. State enabled
15m performance exceptions enabled, 24h performance exceptions disabled and UAT reporting
enabled.
Excep 15m and 24h enabled, UAT rep. State enabled
24h and 15m performance exceptions enabled and UAT reporting enabled.
* Assign a set of exception thresholds to the resource by selecting the Set Id (a number in
the range 1-16).
* Press APPLY to confirm.
See Also:
Performance: stop maintenance based collection

Path (Action-Stop Maintenance)
This option is used to stop a maintenance based collection on a selected resource.
To disable the performance data collection:

Press APPLY to confirm.
See Also:
Performance: start maintenance based collection

.
Issue:1
Performance: start service based collection

Path (Action-Start Service)
This option is used to start a service based collection on a selected resource. Furthermore it`s
possible to specify which set and type of exception events have to be reported.
Service based mode counts the performance parameter over 24h time period only (only the 24h
register is generated).
This kind of evaluation is based on information relevant to both direction of transport togheter then
the performance data collection is started/stopped at the same time on both the transmit (Near End
and, if it exists, Far End termination).
To enable the performance data collection:

* In case the selected entity type is VC-4 define if the PJE counting has to be started on
the relevant AUG or not.
* Use Working Mode to select the type of performance collection.
Excep 24h disabled, UAT rep. State disabled
24h performance exceptions and UAT reporting disabled.
Excep 24h disabled, UAT rep. State enabled
24h performance exceptions disabled and UAT reporting enabled.

.
Issue:1
Excep 24h enabled, UAT rep. State disabled

24h performance exceptions enabled and UAT reporting disabled.
Excep 24h enabled, UAT rep. State enabled
24h performance exceptions and UAT reporting enabled.
* Assign a set of exception thresholds to the resource by selecting the Set Id (a number in
the range 1-16).
See Also:
Performance: stop service based collection

Path (Action-Stop Service)
This option is used to stop a service based collection on a selected resource.
To disable the performance data collection:

Press APPLY to confirm.
See Also:
Performance: start service based collection
Performance: modifying data collection parameter

Path (Action-Modify)
This option is used to modify the performance collection parameters assigned to the selected entity:
Working Mode and Set Id.
Note The kind of service (maintenance or service) can not be modified.
See Also:
Performance: start maintenance based collection, Performance: start service based
collection
Performance: displaying collection state

Path (Action-Read Perf Monitoring Conf-All Monitored Entities)
This facility is used to display the monitoring state configured for each unit of the selected subrack.
NOTICE To enable this option only the subrack has to be selected.
See Also:
collection

.
Issue:1
Performance: displaying started monitored entities

Path (Action-Read Perf Monitoring Conf-Only Started Monitored Entities)
This facility is used to display a list of the unit on which a performance data collection has been
started. Furthermore correlate information will be showed.
See Also:
collection

.
Issue:1
SECURITY AND SYSTEM MANAGEMENT
SECURITY: MODIFYING PASSWORD

Path (Security-Change Own Password) [LC]
Use this option to modify the current User password. New password is stored in the non-volatile
memories of the equipment and is active in the next login.
To modify the current password:

* Enter the Old Password.
* Enter the New Password.
* Re-enter the new password to verify (Confirm Password).
* Press APPLY.
SECURITY: MODIFYING USER PASSWORD

Path (Security-Change User Password) [LC]
Use this option to modify the password assigned to Write_User. New password is stored in the non-
volatile memories of the equipment and is active in the next login.
To modify the current password:

* Enter the Username to be modified (Write_User).
* Enter the New Password.
* Re-enter the new password to verify (Confirm Password).
* Press APPLY.
SYSTEM: SETTING NE DATE AND TIME

Path (System-Date and Time-Time Update)
Use this option to set the date and time used by the DXC internal real time clock.
To define the system date and time:

* Use DXC<matrix type and size> Date and Time to set the date and time of the DXC
equipment.
In the LOCAL CONTROLLER Date and Time the date and time of the Personal Computer are
displayed.
* Press APPLY.
SYSTEM: CONFIGURING TIMEOUT

By means of this menu it is possible to set the LC idle time and the Element Manager reply time.

.
Issue:1
System: configuring session inactivity

Path (System-Timeout-Session Inactivity)
This option is used to set the idle time for a session. If the LC user does not perform any operation
during the configured time, the Central Control Unit will quit the application.
To set LC idle time:

* Use TIMEOUT to enable/disable the idle time check.
* If TIMEOUT is enabled use Minutes sliding bar or spinners to assign the desired value.
* Press APPLY
System: configuring EM response time

Path (System-Timeout-EM Response)
This option is used to set the reply time waited by CCU, during a login session, for receiving a
message from NMC. A write access is granted to the LC user if no message is received within the
specified time, conversely a read-only access is given.
To set EM Response timeout:

* Use TIMEOUT to enable/disable the EM Replay time.
* If TIMEOUT is enabled, use Seconds sliding bar or spinners to assign the desired value.
* Press APPLY.
System: configuring session database open time out

Path (System-Timeout-Session DB open)
This option is used to set the maximum time for which the database will be left open. The database
is opened on reading/writing operations; if during an open database session the database has to be
accessed the Operator will receive the "Database Busy" compliance. The programmability
(increasing) of this timer can be appropriated for some reading operations that sometimes required
a lot of time.
To set EM Session DB open timeout:

* Use Minutes sliding bar or spinners to assign the desired value (64-720).
* Press APPLY.
SYSTEM: LINE UP: MANAGING

Path (System-Line Up)
This option is used to perform a port subracks self-configuration for testing and setting up purposes.
IMPORTANT This operation is allowed only when CCU state is set to OFF-LINE.
To perform a port subrack line up:

* Set the CCU to Off-Line State.

.
Issue:1
IMPORTANT All the port units in the subrack must be in equipped state only.
* Select from the relevant menu the action to be performed on the chosen subrack.
* Set the CCU On-Line State.
See Also:
Line Up: configuring ports (DXC 4/1)

Path (Action-Port Config)
This option is used to automatically configure all the ports of the subrack. The ports are configured
with default values.
If there are already configured ports in the subrack an error box will be displayed.
In case of type 2 subrack completely provisioned with 16x2Mbit/s tributary units (8 cards) the port
configuration procedure follows this scheme:
n All ports of the cards N. 1, 2 and 3 will be configured.
n The 16th port of card N. 4 wont be configured.
n All ports of the cards N. 5, 6 and 7 will be configured.
n The 16th port of card N. 8 wont be configured.
This is due to the capacity of equipment internal STM-1 flows carrying the traffic from port subrack
to matrix subrack (1 STM1=63x2Mbit/s).
* Press OK in the message box to confirm the operation
Line Up: provisioning cross-connections (DXC 4/1)

Path (Action-X Conn Config)
This option creates a standard cross connection scheme using all the configured ports. The option
also provides remote loopbacks on 140Mbit/s TMUX tributary units (if present).
The type of connections depends on the port subrack:
n Type 7E Subrack:
STM-16 Units
a series of VC-4 unidirectional connections is realized among the AUs of the STM-16 cards. An
unidirectional VC-4 connection chain is created connecting the AU channels having the same AU
number of each card consecutively between them.
The AUs belonging to the last card are connected with the relevant AU of the first one.
n Type 7 Subrack:
STM-16 Units
a series of VC-4 unidirectional connections is realized among the AUs of the two STM-16 cards. An
unidirectional VC-4 connection chain is created connecting the AU channels having the same AU
number of each card consecutively between them.

.
Issue:1
n Type 6E Subrack:
STM-4 Units
a series of VC-4 unidirectional connections is realized among the AUs of the STM-4 cards. The
cards, providing a protection function are not checked. An unidirectional VC-4 connection chain is
created connecting the AU channels having the same AU number of each card consecutively
between them.
The AUs belonging to the last card are connected with the relevant AU of the first one
NxSTM-1 Units
An unidirectional VC-4 connection chain is created connecting the AU-4 channels of each port
consecutively between them.
On the same unit the AU-4 of the first port is connected to the AU-4 of the second port, the AU-4 of
the second port is connected to the AU-4 of the third port and so on.
The AU-4 of the last port is connected to the AU-4 of the first port belonging to the next unit.
The AU-4 belonging to the last port of the last unit is connected with the first AU-4 of the first one.
The cards, providing a protection function are not checked.
4xSTM-1/140Mbit/s Units
a series of VC-4 unidirectional connections is realized among the STM-1 and/or 140Mbit/s cards. A
VC-4 unidirectional connections will be also realized between the last port to the first automatically.
n Type 6 Subrack:
STM-4 Units
a series of VC-4 unidirectional connections is realized among the AUs of the four STM-4 cards (P1,
P3, P6 and P8; P5 is not checked because it provides only a protection function). An unidirectional
VC-4 connection chain is created connecting the AU channels having the same AU number of each
card consecutively between them.
NxSTM-1 Units
An unidirectional VC-4 connection chain is created connecting the AU-4 channels of each port
consecutively between them.
On the same unit the AU-4 of the first port is connected to the AU-4 of the second port, the AU-4 of
the second port is connected to the AU-4 of the third port and so on.
The AU-4 of the last port is connected to the AU-4 of the first port belonging to the next unit.
The AU-4 belonging to the last port of the last unit is connected with the first AU-4 of the first one.
For the 4xSTM-1 and 4x140/155Mbit/s Units, the unit in position P5 is not checked because it
provides only a protection function, while for 2xSTM-1 Units, P5 is checked only if the protection
supported by the subrack is not the 2XSTM1 MSP 1:N.
n Type 5 Subrack:
STM-1 and 140Mbit/s Units
a series of VC-4 unidirectional connections is realized among the STM-1 and/or 140Mbit/s cards. A
VC-4 unidirectional connections will be also realized between the last port to the first automatically.
140Mbit/s T-Mux Units
63 VC-12 unidirectional connections are realized on 140Mbit/s TMUX tributary unit (matrix side).

.
Issue:1
n Type 4 Subrack:
1x45Mbit/s T-Mux Unit
a series of VC-12 unidirectional connections are realized among the 28 DS1 managed by each unit
(the first is connected to the second, the second to the third and so on). The last DS1 is connected
to the first one belonging to the next unit.
The DS1 belonging to the last port of the last unit is connected with the first DS1 of the first one.
Unit equipped in slots 2, 4, 6 and 8 are not involved in the test because they provide only protection
function (no matrix accesses available).
n Type 3 Subrack:
63x2Mbit/s Unit
a VC-12 unidirectional connection is realized between the transmission and the reception side of
each port managed by the unit (the from side of the first port is connected to the to side of the
same one and so on).
4x34Mbit/s T-Mux Unit
each 2Mbit/s sub-channel managed by the unit (the from side of the first 2Mbit/s channel is
connected to the to side of the same one and so on).
3x34-45Mbit/s Unit
each port managed by the unit (the from side of the first port is connected to the to side of the
same one and so on).
n Type 2 Subrack:
All the Units
a series VC-3/VC-12 unidirectional connections are realized among the 3x34-45Mb/16x2Mb cards.
If more than one 3x34-45Mb/16x2Mb cards are present a VC3/VC-12 unidirectional connection will
be realized between the last port of the previous card to the first of the next one automatically. A
VC-3/VC-12 unidirectional connection will also realized between the last port of the last card and
the first port of the first card.
These cross-connections can be used to check the correct operation of a port subrack.
* Press OK in the message box to confirm the operation
Line Up: decommissioning the ports

Path (Action-Port Delete)
This option is used to automatically decommission all the ports of a subrack. A port subrack cannot
be decommissioned if cross connections are present. This option can only be applied after deletion
of all cross connections by means of the proper command.
* Press OK in the message box to confirm the operation.
Line Up: removing cross-connections

Path (Action-X Conn Delete)
Use this option to delete the standard cross connection scheme.
* Press OK in the message box to confirm the operation.

.
Issue:1
SYSTEM: CHECKING THE SOFTWARE RELEASE

This option performs a software compatibility check on the units present in the subracks. This check
is based on a file named software_versions.config. which is matched with the information
extracted from the units. The file is supplied with the software and contains a list of the software
versions for all units.
It is possible to verify a single subrack or the whole equipment.
System: checking subrack software release

Path (System-Check SW Release-Subrack)
This option is used to verify the software release compatibility of a selected subrack.
To read information related to a single subrack

* Select the subrack to be checked.
* Click on FILE SELECTION to select the file software_ver_dxc.cnf
* Select Action-Read
IMPORTANT A W before the Unit name means Wrong Card Fitted.
See Also:
How To Select a File

.
Issue:1
System: checking equipment software details

Path (System-Check SW Release-NE)
This option is used to verify the software release compatibility on the whole equipment.
To read information related to the equipment:

* Click on FILE SELECTION to select the software_versions.config file.
* Select Action-Read
See Also:
How To Select a File, System: checking subrack software release
SYSTEM: PERFORMING DATABASE BACKUP

Path (System-Backup) [LC]
This option is used to backup into a selected file the equipment database stored into the Memory
Expansion Unit.
Only the write_user and supervisor are allowed to perform this operation.
To backup the database:

* Use Target System Type to specify the type of backup to be made.
CCU Database on prov. service
To backup the equipment database present in the Memory Expansion Unit.
* Click on FILE SELECTION to select the file used to backup the database.
* Press APPLY.
During the command execution the APPLY push-button and the main menu option will be disabled.
A control window is displayed allowing the operator to abort the operation. A real time indication
gives the performed backup percentage.

.
Issue:1
IMPORTANT The LC user access rights become read/only until the Backup operation is
completed.
See Also:
System: downloading Sw and DB on C&T subrack, How To Select a File
SYSTEM: DOWNLOADING SW AND DB ON C&T SUBRACK

Path (System-Download-Download C&T) [LC]
This option is used:
a. to download a new database on the Memory Expansion Units
b. to download a new software release on the units (Central Control Unit)
IMPORTANT The download operation can be performed only if the status of the Central
Control Unit has been changed to Off Line.
Read carefully the Release Upgrading chapter (Equipment Manual, Section 4)
before proceeding.
The database to be downloaded must have been previously saved using the backup option.
The software to be downloaded into the units must have been copied from the Distribution Floppy to
the hard disk of PC.
To download the database or the software:

* Use Target System Type to select the type of download.
CCU Software on prov. service
To download the software on the Central Control Unit which is providing service.
CCU Database on prov. service
To download the database on the Memory Expansion Unit via the Central Control Unit which is
providing service.
* Click on FILE SELECTION to select the file to be downloaded on the Target System
Type.
* Press APPLY.
A control window is displayed to allow the user to abort the operation. A real time indication gives
the performed download percentage.
IMPORTANT After a Unit SW download operation it is necessary to perform a memory bank

switching in order to activate the downloaded software.
The LC user access rights become read/only until the download operation is
completed.
See Also:
System: performing database backup, Operative States, System: switching the flash
memory banks, How To Select a File

.
Issue:1
SYSTEM: DOWNLOADING SW ON COMMU

Path (System-Download-Download COMM) [LC]
This option is used to download the software on the flash memories of the Communication and Q
Interface Unit.
IMPORTANT Read carefully the Release Upgrading chapter (Equipment Manual, Section 4)
before proceeding
To download the software:

* Select the Communication Unit/s to be upgraded (information about the active software
are displayed).
* Click on FILE SELECTION to select the file to be downloaded into the Target System
Type.
* Press APPLY.
See Also:
System: downloading Sw on PCU of the Type 5 Subrack
SYSTEM: DOWNLOADING SW ON MCU

Path (System-Download-Download MTX Cntr) [LC]
This option is used to download the software on the flash memories of the Matrix Controller Units.
before proceeding

* Select the Matrix Controller Unit/s to be upgraded (information about the active software
are displayed).
Type.
* Press APPLY.
See Also:

.
Issue:1
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE 2 SUBRACK

Path (System - Download - Download PC - PC-TYPE-2) [LC]
This option is used to download the software on the flash memories of the Port Controller Units of
the Type 2 Port Subracks.
before proceeding
The software to be downloaded on the units must have been copied from the Distribution Floppy to

* Select the Port Controller Unit to be upgraded (information about the active software are
displayed).
Type.
* Press APPLY.

Until the SW download is completed, and in particular until the unit selection
window is opened, it will not be possible to perform any operations.
See Also:
Operative States, System: switching the flash memory banks, How To Select a File

Path (System - Download - Download PC - PC-TYPE-5) [LC]
before proceeding

displayed).
Type.
* Press APPLY.

.
Issue:1

See Also:
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE 3/6/7 SUBRACK

Path (System - Download - Download PC - PC-TYPE-3/6/7) [LC]
the Type 3/6/7 Port Subracks.
before proceeding

displayed).
Type.
* Press APPLY.

See Also:

.
Issue:1

Path (System - Download - Download PC - PC-TYPE-4 [LC]
before proceeding

displayed).
Type.
* Press APPLY.

See Also:
SYSTEM: DOWNLOADING SW ON PCU OF THE TYPE E SUBRACK

Path (System - Download - Download PC - PC-E) [LC]
the Types E Port Subracks.
before proceeding

displayed).
Type.
* Press APPLY.

.
Issue:1

See Also:
SYSTEM: DOWNLOADING SW ON STM-4 UNIT

Path (System - Download - Download Port Card - STM4) [LC]
This option is used to download the software on the flash memories of the STM-4 Units housed in
before proceeding

* Select the Unit/s to be upgraded (information about the active software are displayed).
Type.
* Press APPLY.

See Also:
Operative States, System: switching the flash memory banks, How To Select a File

.
Issue:1
SYSTEM: DOWNLOADING SW ON STM-16 UNIT

Path (System - Download - Download Port Card - STM16) [LC]
This option is used to download the software on the flash memories of the STM-16 Units housed in
the Type 7 / 7E Port Subrack.
before proceeding

* Choose unit card version
Type.
* Press APPLY.

See Also:
System: downloading Sw on STM-4 Unit
SYSTEM: DOWNLOADING SW ON 2XSTM-1 UNIT

Path (System - Download - Download Port Card - 2xSTM1) [LC]
This option is used to download the software on the flash memories of the 2xSTM-1 Units housed in
the Type 6/6E Port Subracks.
before proceeding

Type.
* Press APPLY.

.
Issue:1

See Also:
SYSTEM: DOWNLOADING SW ON 4XSTM-1 UNIT

Path (System - Download - Download Port Card - 4xSTM1) [LC]
This option is used to download the software on the flash memories of the 4xSTM-1 Units housed in
the Type 6/6E Port Subracks.
before proceeding

Type.
* Press APPLY.

See Also:

.
Issue:1
SYSTEM: DOWNLOADING SW ON 4X140-155MBIT/S UNIT

Path (System - Download - Download Port Card - 4xSTM1-140) [LC]
This option is used to download the software on the flash memories of the 4x140-155Mbit/s Units
housed in the Type 6/6E Port Subracks.
before proceeding.

Type.
* Press APPLY.

See Also:
SYSTEM: DOWNLOADING SW ON AUXILIARY UNIT

Path (System - Download - Download Port Card - Auxiliary) [LC]
This option is used to download the software on the flash memories of the Auxiliary Units housed in
the Type 6/6E/7 Port Subracks.
before proceeding.

Type.
* Press APPLY.

.
Issue:1

See Also:
SYSTEM: DOWNLOADING SW ON 63X2MBIT/S UNIT

Path (System - Download - Download Port Card 63x2) [LC]
This option is used to download the software on the flash memories of the 63x2Mbit/s Units housed
in the Type 3 Port Subracks.
before proceeding.

Type.
* Press APPLY.

See Also:

.
Issue:1
SYSTEM: DOWNLOADING SW ON 4X34MBIT/S T-MUX UNIT

Path (System - Download - Download Port Card TMUX-4x34) [LC]
This option is used to download the software on the flash memories of the 4x34Mbit/s T-Mux Units
housed in the Type 3 Port Subracks.
before proceeding.

Type.
* Press APPLY.

See Also:

before proceeding.

Type.
* Press APPLY.

.
Issue:1

See Also:

before proceeding.

Type.
* Press APPLY.

See Also:

.
Issue:1
SYSTEM: DOWNLOADING SW ON BOOSTER UNIT

Path (System - Download - Download Port Card Booster) [LC]
This option is used to download the software on the flash memories of the Booster Units housed in
the Type 6E/7 Port Subracks and Booster Subrack.
before proceeding.

Type.
* Press APPLY.

See Also:
SYSTEM: DOWNLOADING SW ON PREAMPLIFIER UNIT

Path (System - Download - Download Port Card Preampl.) [LC]
This option is used to download the software on the flash memories of the Booster Units housed in
the Type 6E/7 Port Subracks and Booster Subrack.
before proceeding.

Type.
* Press APPLY.

.
Issue:1

See Also:
SYSTEM: DOWNLOADING SW ON TYPE 3/6/7 MIU

Path (System - Download Download IM IM-TYPE 3/6/7.) [LC]
This option is used to download the software on the flash memories of the Matrix Interface Unit
housed in the Type 3/6/7 Port Subracks.
before proceeding.

* Select the Matrix Interface Unit to be upgraded (information about the active software are
displayed).
Type.
* Press APPLY.

See Also:
System: downloading Sw on PCU of the Type 3/6/7 Subrack

.
Issue:1
SYSTEM: DOWNLOADING SW ON TYPE E MIU

Path (System - Download Download IM IM-TYPE-E.) [LC]
This option is used to download the software on the flash memories of the Matrix Interface Unit
housed in the Type E Port Subracks.
before proceeding.

* Select the Matrix Interface Unit to be upgraded (information about the active software are
displayed).
Type.
* Press APPLY.

See Also:
System: downloading Sw on PCU of the Type E Subrack

.
Issue:1
SYSTEM: SWITCHING THE FLASH MEMORY BANKS

System: switching banks on C&T subrack
Path (System-Switch Bank-Switch Bank C&T)
Use this option to switch the active flash memory bank of the Central Control Unit.
Switching of the memory banks of the Central Control Unit causes a hot restart of the equipment.
before proceeding
To switch the flash bank:

* Use Target System Type to select the unit where the memory bank has to be switched.
* Press APPLY.
See Also:
Operative States, System: restarting CCU

.
Issue:1
System: switching banks on CommU

Path (System-Switch Bank-Switch Bank COMM)
This option is used to switch the flash memory banks of the Communication and Q Interface Unit.
before proceeding
To switch the memory banks of the Communication Units:

* Select the Communication Unit which memory banks have to be switched (information
about the active software are displayed).
* Press APPLY.
See Also:
System: switching banks on PCU of type 5 subrack
System: switching banks on MCU

Path (System-Switch Bank-Switch Bank MTX Cntr)
This option is used to switch the flash memory banks of the Matrix Controller Units.
before proceeding
To switch the memory banks of the Matrix Controller Units:

* Select the Matrix Controller Unit which memory banks have to be switched (information
* Press APPLY.
See Also:

Path (System - Switch bank - Switch Bank PC - PC-TYPE-2)
This option is used to switch the flash memory banks of the Port Controller Units of the Type 2
Subrack.
before proceeding
To switch the memory banks of the Port Controller Units:

* Select the Port Controller Unit which memory banks have to be switched (information
* Press APPLY.

.
Issue:1

Subrack.
before proceeding

* Press APPLY.
See Also:
System: switching banks on PCU of type 3/6/7 subrack

Path (System - Switch bank - Switch Bank PC - PC-TYPE-3/6/7)
This option is used to switch the flash memory banks of the Port Controller Units of the Type 3/6/7
Subrack.
before proceeding

* Press APPLY.
See Also:

Subrack.
before proceeding

* Press APPLY.

.
Issue:1
See Also:
System: switching banks on PCU of type E subrack

Path (System - Switch bank - Switch Bank PC - PC-TYPE-E) [LC]
This option is used to switch the flash memory banks of the Port Controller Units of the Type E
Subrack.
before proceeding

* Press APPLY.
See Also:
System: switching banks on STM-4 Unit

Path (System - Switch bank - Switch Bank Port Card - STM4)
This option is used to switch the flash memory banks of the STM-4 Unit housed in the Type 6/6E
Subrack.
before proceeding
To switch the memory banks of the STM-4 Units:

* Select the Unit which memory banks have to be switched (information about the active
software are displayed).
* Press APPLY.
See Also:
Operative States

Path (System - Switch bank - Switch Bank Port Card - STM16)
This option is used to switch the flash memory banks of the STM-16 Unit housed in the Type 7, 7E
Subrack.
before proceeding
To switch the memory banks of the STM-16 Units:


.
Issue:1
* Press APPLY.
See Also:
System: switching banks on 2xSTM-1 Unit

Path (System - Switch bank - Switch Bank Port Card - 2xSTM1)
This option is used to switch the flash memory banks of the 2xSTM-1 Unit housed in the Type 6/6E
Subrack.
before proceeding
To switch the memory banks of the 2xSTM-1 Units:

* Press APPLY.
See Also:
System: switching banks on 4xSTM-1 Unit

Path (System - Switch bank - Switch Bank Port Card - 4xSTM1)
This option is used to switch the flash memory banks of the 4xSTM-1 Unit housed in the Type 6/6E
Subrack.
before proceeding
To switch the memory banks of the 4xSTM-1 Units:

* Press APPLY.
See Also:

.
Issue:1
System: switching banks on 4x140-155Mbit/s Unit

Path (System - Switch bank - Switch Bank Port Card - 4xSTM1-140)
This option is used to switch the flash memory banks of the 4x140-155Mbit/s Unit housed in the
Type 6/6E Subrack.
before proceeding
To switch the memory banks of the 4x140-155Mbit/s Units:

* Press APPLY.
See Also:
System: switching banks on Auxiliary Unit

Path (System - Switch bank - Switch Bank Port Card - Auxiliary)
This option is used to switch the flash memory banks of the Auxiliary Unit housed in the Type 6E/7
Subrack.
before proceeding
To switch the memory banks of the Auxiliary Units:

* Press APPLY.
See Also:
System: switching banks on 63x2Mbit/s Unit

Path (System - Switch bank - Switch Bank Port Card - 63x2)
This option is used to switch the flash memory banks of the 63x2Mbit/s Unit housed in the Type 3
Subrack.
before proceeding
To switch the memory banks of the Auxiliary Units:

* Press APPLY.

.
Issue:1
See Also:
System: switching banks on 4x34Mbit/s T-Mux Unit

Path (System - Switch bank - Switch Bank Port Card TMUX-4x34)
This option is used to switch the flash memory banks of the 4x34Mbit/s T-Mux Unit housed in the
Type 3 Subrack.
before proceeding
To switch the memory banks of the 4x34Mbit/s T-Mux Units:

* Press APPLY.
See Also:

Path (System - Switch bank - Switch Bank Port Card 3x34)
Subrack.
before proceeding
To switch the memory banks of the 3x34Mbit/s Units:

* Press APPLY.
See Also:

Path (System - Switch bank - Switch Bank Port Card 3x45)
Subrack.
before proceeding
To switch the memory banks of the 3x45Mbit/s Units:


.
Issue:1
* Press APPLY.
See Also:
System: switching banks on Booster Unit

Path (System - Switch bank - Switch Bank Port Card Booster)
This option is used to switch the flash memory banks of the Booster Unit housed in the Type 6E/7
Subrack and Booster Subrack.
before proceeding
To switch the memory banks of the Booster Units:

* Press APPLY.
See Also:
System: switching banks on Pramplifier Unit

Path (System - Switch bank - Switch Bank Port Card Preamplifier)
This option is used to switch the flash memory banks of the Booster Unit housed in the Type 6E/7
Subrack and Booster Subrack.
before proceeding
To switch the memory banks of the Preamplifier Units:

* Press APPLY.
See Also:

.
Issue:1
System: switching banks on Type 3/6/7 MIU

Path (System-Switch Bank-Switch Bank IM-TYPE-3/6/7)
This option is used to switch the flash memory banks of the Matrix Interface Units.
before proceeding
To switch the memory banks of the Type 3/6/7 Matrix Interface Units:
* Select the Matrix Interface Unit which memory banks have to be switched (information
* Press APPLY.
See Also:
System: switching banks on Type E MIU

Path (System-Switch Bank-Switch Bank IM-TYPE-E)
This option is used to switch the flash memory banks of the Matrix Interface Units.
before proceeding
To switch the memory banks of the Type E Matrix Interface Units:

* Select the Matrix Interface Unit which memory banks have to be switched (information
* Press APPLY.
See Also:
SYSTEM: DISPLAYING COMMAND LOG DATABASE

Path (System-Command Log DB-Read)
This option is used to display a log file containing all commands previously issued by the Operator.
Only commands that produce database modifications (Create/Modify/Delete) are saved into the log
file.
* Use MORE to scroll the database pages.
* Use ABORT or CLOSE to close the window
SYSTEM: RESETTING COMMAND LOG DATABASE

Path (System-Command Log DB-Reset)
This option is used to delete the Command Log Database.
See Also:
System: displaying command log database

.
Issue:1
SYSTEM: DECOMMISSIONING NE DATABASE

Path (System-DataBase Decommission) [LC]
This option is used to delete all database information stored into the Memory Expansion Units.
Once this operation has been performed the equipment has been fully decommissioned (no cross-
connection, synchronization and subracks are present in the database).
The database can be decommissioned only if the status of the Central Control Unit has been
changed to Off Line.
See Also:
SYSTEM: PARTIAL DECOMMISSIONING OF NE DATABASE

Path (System-Partial DataBase Decommission)
This option is used to delete all database information stored within the Memory Expansion Units,
except the following:
n NE model;
n Communication and Q interface units configuration;
n OSI parameters;
n Port Subracks NSAPs and routing mode configuration (centralised or distributed).
This option can be used to decommission the NE database, without losing the communication and
control via Q interface.
IMPORTANT The database can be decommissioned only if the status of the Central Control
Unit has been changed to Off Line.
It is possible to choose the status of the CCU at the system restart. Possible status are:
On line
At the system restart, the CCU takes the control of the peripheral units. The blank database is
copied to all peripheral units, erasing all the configuration parameters.
Off line
At the system restart, the CCU does NOT take the control of the peripheral units. The configuration
parameters on the peripheral units are kept frozen.
Upgrading
The Upgrading option is used when performing an upgrading of the Equipment release.
See Also:

.
Issue:1
SYSTEM: RESTARTING CCU

Path (System-System Restart)
This option is used to restart the equipment performing a reset of the Central Control Unit and
peripheral cards.
To restart the equipment:

* Use Restart Mode to restart of the equipment.
Hot Restart
Equipment restart without traffic interruption (peripheral units are reprogrammed).
Cold Restart
Equipment restart with possible traffic interruption (hardware reset of peripheral units).
* Press APPLY.
The Control Application is automatically quit due to the CCU restart.
SYSTEM: UPGRADING TEST FROM DXC 4/1 512X512 TO DXC 4/4

Path (System-MSH9x DB Upgrade Test...)
This option checks whether the DXC 4/1 512x512 can be upgraded to the DXC 4/4 1024x1024.
This implies the following requirements on the DXC 4/1 512x512:
n the DXC 4/1 512x512 release is equivalent to DXC 4/4 1024x1024 release. This means that
the DXC 4/1 512x512 must be in release 9.1.1 and DXC 4/4 1024x1024 must be in release
9.1.1;
n the DXC 4/1 512x512 does not have any type 2, 3 or 4 subracks;
n the equipped Type 5 Subracks on the DXC 4/1 512x512 must be completely wired;
n the subracks installed on the DXC 4/1 512x512 must be wired exactly as indicated in the
Equipment Manual; Moreover, matrix accesses must be contiguous into groups of eight;
n the DXC 4/1 512x512 electrical 140 T-Mux units are all configured as 140Mbit/s tributary
units;
n the DXC 4/1 512x512 cross connection are all VC-4 type;
n the DXC 4/1 512x512 does not have any UDC cross-connection;
n the DXC 4/1 512x512 does not have any DXC Type III protection on non-connected VC-4s.
A dialog box informs the operator on the test result.

.
Issue:1
REAL-TIME MONITOR WINDOW
[LC]
Real-Time Monitor Window is automatically activated when Control Application is activated.
This window is divided in two different parts: Alarm Area and Event Area.
ALARM AREA
[LC]
In this box are displayed information about the alarms detected in the equipment.
See Also:
Cross-Connection: displaying the port/matrix fail alarms (DXC 4/1), Operative States
EVENT AREA
[LC]
In this box are displayed information about the non-alarm events (i.e.: activation of protection,
changeover of synchronisation, exceeding of performance thresholds, etc).
Event Type
In this field is displayed the type of event that has occurred in the equipment. The following
messages can be displayed.
PERFORMANCE THRESHOLD EXCEEDING
This event indicates that the performance threshold has been exceeded for the displayed entity.
UNAVAILABLE TIME START/STOP
This event indicates that the unavailable time has started (or stopped) for the displayed entity.
TS CALIBRATION END
This event indicates that the calibration of the Timing Selector Oscillator Unit has been performed.
The result of the operation is also displayed (success or fault).
LOG FULL ACTIVE/INACTIVE
If ACTIVE indicates that Alarm Log size has reached the defined threshold (Log Full); if INACTIVE
Alarm Log has been cleared or the threshold has been increased.

.
Issue:1
INTERFACE CONGESTION START/STOP

This event indicates a logical channel overflow induced by the spontaneous events between DXC
and EM/LC. In this case neither spontaneous event nor error indication will be sent. The
Congestion occurs when the event "receiver" (EM or LC) is not able to manage all the alarms
issued by the DXC; in this case the CCU internal message queues exceed a set threshold and the
congestion state arises. This event is also represented by means of an indication on the window as
shown below:
ALARM BURST START/STOP

This event occurs when the spontaneous event stream issued by the CCU exceeds a set threshold
(more than 100 alarms for more than 3 seconds). During the Burst the alarms are not sent to the
Element Manager but the software error indications will continue to be issued. This event is also
represented by means of an indication on the window as shown below:
NE INITIALIZATION END
This event indicates that the equipment restart is over.
PROTECTION SWITCH
This event indicates that an automatic switch (due to a failure) or a Operators command) switch
has occurred in the displayed resource.
CCU RESTART REQUEST
This event indicates that an HOT or a COLD Restart or has been requested.
PERFORMANCE DATA CLEAR
This event indicates that one or more performance registers have been cleared.
CCU OFFLINE
This event indicates that the CCU status has been modified in OFFLINE
MATRIX PROGRAMMING ERROR
This event indicates that a wrong setting up has been performed on the matrix.
ALARM ACKNOWLEDGEMENT
This event indicates that an alarm has been acknowledged
Information
In this field are displayed the information relevant to the Event Type. Different messages are
displayed depending on the Event Type.
LOG FULL
Active/Inactive
ALARM BURST START/STOP
Start/Stop
INTERFACE CONGESTION START/STOP
Start/Stop
NE INITIALIZATION END
CCU Hot Startup
CCU Cold Startup

.
Issue:1
PERFORMANCE DATA CLEAR

Event Cause:
Operator Request
Fault State
DBQ Cold Restart.
Subrack.
Unit.
CCU OFFLINE
Event Cause:
Operator Request
MATRIX PROGRAMMING ERROR
Event Cause:
DB Error
HW Error
Unrecognized
ALARM ACKNOWLEDGEMENT
Subrack Id
Unit Id:
PERFORMANCE THRESHOLD EXCEEDING
Subrack Id
Unit Id
Resource Id
Entity Type
Report Type
Event Cause
Parameter count
Threshold Exceed
UNAVAILABLE TIME START/STOP
Subrack Id
Subrack Type
Unit Id
Resource Id
Entity Type
Period State
TS CALIBRATION END
Subrack Id
Unit Id
Result

.
Issue:1
PROTECTION SWITCH
(for System Osc. - Mode Prot or Ext. Out Osc. Mode Prot)
Cause :
Subrack Id:
Unit Id:
Old Sync Mode:
New Sync Mode:
Protection type:
PROTECTION SWITCH
(for System Osc. - Input Src Prot or Ext. Out Osc. Input Src Prot)
Cause :
From Subrack id / Unit id
To Subrack id / Unit id
Sync Source id:
PROTECTION SWITCH
(for Rx Path Protection or Tx Path Protection or Rx/Tx Path Protection)
Cause :
On Matrix:
From Subrack id / Unit id / Channel id
To Subrack id / Unit id / Channel id
Protection role:
Protection type:
PROTECTION SWITCH
(for Matrix Protection)
Cause :
Protection role:
Protection type:
PROTECTION SWITCH
(for MI Protection or PC Protection or SIO Protection)
Cause :
From Subrack id / Unit id
To Subrack id / Unit id
Protection role:
Protection type:
Meanings of the above parameters:
Subrack Id
See Also:
Operative States
Unit Id
See Also:
Operative States
Cause
Resource Operation
Switching has automatically occurred due to a failure detected in the equipment.

.
Issue:1
Management Operation
Switching has manually occurred due to an Operators command.
Remote Operation
Switching has occurred on commands from the remote port (only for MSP protection).
Event Cause
See Also:
Entity Type
See Also:
New Sync Mode
No Mode
No synchronisation mode defined (free-running).
Normal Revertive
Oscillator is using the synchronisation defined in the
Synchronisation Table (Revertive Mode enabled).
Normal Not Revertive
Oscillator is using the synchronisation defined in the
Synchronisation Table (Revertive Mode disabled).
Old Sync Mode
Same as New Sync Mode.
On Matrix
Matrix Subrack on which path protection has been performed.
Parameter Count
<number>
Quality value calculated for the displayed Entity Type.
Period State
Start
Start of the unavailability period.
Stop
End of the unavailability period.
Protection Role
See Also:
Operative States

.
Issue:1
Protection Type
See Also:
Operative States
Resource Id
<number>
Port number.
Sync Source Id
01..EXT1/EXT2
Identifier of the synchronisation source (port subrack or external clock).
Threshold Exceeded
<number>
Value of the performance threshold that has been exceeded.

.
Issue:1
FAULT DETECTION PROCEDURE
All the alarm messages are listed in this section.

They are organized according to the alarm source order as they are shown in the Control
Application. Besides each alarm message, the source, the category and the priority number are
shown. Moreover the cause (Problem) of the alarm and the procedure to face it (Action) are
described: at the cause n will correspond the action n
NOTICE The [LC] note indicates that the relevant alarm, for default configuration, is not
monitored by the NMC (Network Management Centre).
See Also:
Managing Alarms
SPI - SYNCHRONOUS PHYSICAL INTERFACE ALARMS

In the following all the alarms detected at the SPI (Synchronous Physical Interface) level are
reported.
TxClockFail (SPI)
Category: URG_INT_155Mb Priority: 62
The transmitted 9.72MHz line clock signal is missing.
Problem:
1. Unit Internal Failure
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble Shooting Procedure
RxClockFail (SPI)
Loss of clock signal extracted from the received STM-1 stream.
Problem:
1. Consequence of alarms MS-AIS, LOS
2. Fault on the far-end transmitter
Action:
1. Follow the standard site procedure for the network alarms
2. Check the alarms of the far-end equipment

.
Issue:1
FreqOutOfRange (SPI)
The PLL circuit on the transmit side is unlocked.
Problem:
1. Consequence of synchronisation alarms
Action:
1. Follow the standard site procedure for the main alarms
TxLaserPwrHigh (SPI)
OPTICAL UNIT ONLY. Excessive bias current increasing
Problem:
1. Unit Internal Failure (fault on the laser power control loop)
Action:
TxLaserPwrLow (SPI)
OPTICAL UNIT ONLY. The output power is less then the 81% (1db) of the operating power
Problem:
1. Consequence of alarm: LOS
Action:

.
Issue:1
DescramblerFail (SPI)
Failure of the descrambler circuit
Problem:
Action:
ScramblerFail (SPI)
Failure of the scrambler circuit
Problem:
Action:
LOS_LOF (SPI)
Category: URG_EXT_155MbPriority: 61
Loss of incoming STM-1 line signal or loss of frame alignment (supported by Type 2 STM-1 Unit).
Note The attributes of this alarm cannot be modified, it has the same attributes of LOS.
Problem:
1. Consequence of far-end equipment transmitter failure or line interruption
Action:
1. Disconnect the Tx and Rx connectors and loop output to input using a test patch cord. If the
alarm goes OFF, check the status of the far-end equipment and the line.
alarm stays ON, proceed as indicated in:
LOS (SPI)
Loss of incoming STM-1 line signal (supported by Type 1 STM-1 Unit).
Problem:

.
Issue:1
Action:
LaserFail (SPI)
OPTICAL UNIT ONLY. Failure of the laser. The Tx power is 3dB lower or greater than the nominal
value
Note Supported only by STM-1 Optical Unit Type 2.
Problem:
1. Unit Internal Failure.
Action:
LaserDegrade (SPI)
OPTICAL UNIT ONLY. The bias voltage of the laser is 50% greater than the nominal value
Problem:
1. This alarm is always caused by Unit Internal Failure
Action:
TxPulseLoss (SPI)
OPTICAL UNIT ONLY. The laser is not transmitting
Problem:
1. Consequence of alarms: LOS
Action:

.
Issue:1
RS - REGENERATOR SECTION ALARMS

In the following all the alarms detected at the RS (Regenerator Section Alarms) level are reported.
LOF (RS)
Loss of STM-1 frame alignment
Problem:
1. Consequence of far-end equipment transmitter failure
Action:
alarm goes OFF, check the status of the far-end equipment
DCCrLAPDDisconnected (RS)
Category: IND_155Mb Priority: 70
Errors in the link access procedure configuration check on DCCr channel
Problem:
1. Wrong LAPD configuration
Action:
1. Using the Control Application to check the local and remote LAPD configuration for the STM-1
interfaces (NETWORK must be connected to USER)
RS-TIM (RS)
Mismatch between the received and the expected path trace identifier byte (J0)
Problem:
1. Transmitter on the far-end equipment configured with a different path trace identifier
Action:
1. Check the local and far-end configuration.

.
Issue:1
MS - MULTIPLEX SECTION ALARMS

In the following all the alarms detected at the MS (Multiplex Section Alarms) level are reported.
MS-AIS (MS) [LC]

Multiplex Section Alarm Indication Signal received from a remote regenerator equipment
MS-AIS defect is detected by the MS Termination function when the pattern 111 is observed in bits
6, 7 and 8 of the K2 byte (before scrambling) in at least three consecutive frames
Problem:
1. Fault on the far-end regenerator
Action:
1. Check the status of the far-end regenerator
MS-RDI (MS) [LC]

The Multiplex Section Remote Defect Indication is used to return an indication (applied within 250
s) to the transmit end that the received end has detected an incoming section defect or is receiving
MS-AIS.
An incoming MS-RDI is detected by the MS Termination function when the pattern 110 is
observed in bits 6, 7 and 8 of the K2 byte (before scrambling) in at least two consecutive frames
Problem:
1. Consequence of one of the following alarms detected on the receive side of the far-end
multiplexer:
LOS
LOF
MS-AIS
MS-EXC
Action:
1. Check the status of the far-end multiplexer and follow the trouble-shooting procedure for the
detected alarm
MS-EXC (MS)
An Excessive error defect is detected if the equivalent Bit Error Rate (BER) exceeds a threshold of
10-3 on the received signal. Errors are calculated by checking the BIP-24 on the received data and
the corresponding value present in bytes B2
Problem:
1. Excessive degradation of the optical fibre
Coupling attenuation
Failure of the far-end transmitter

.
Issue:1
Action:
Bit Error Rate Trouble Shooting Procedure
MS-DEG (MS)
Category: NURG_EXT_155Mb Priority: 82
A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) exceeds a preset
threshold in the range of 10-5 to 10-9 (the threshold can be configured via software). Errors are
calculated by checking the BIP-24 on the received data and the corresponding value present in
bytes B2
Problem:
1. Degradation of the optical fibre
Malfunction of the far-end transmitter
Unit Internal Failure
Action:
SSMMismatch (MS)
Synchronization Status Message Mismatch. The quality level (QL) of the incoming stream (bits 5 to
8 of byte S1) is worst than the minimum QL allowed
Problem:
1. The network element transmitting the stream has a synchronisation source quality worst than
the QL configured locally
Action:
1. Check synchronization of the far-end equipment
DCCmLAPDDisconnected (MS)
Errors in the link access procedure configuration check on DCCm (bytes D4 to D12) channel
Problem:
1. Wrong LAPD (Link Access Protocol for D-channel) configuration
Action:
1. Using the Control Application check the local and remote LAPD configuration for the STM-1

.
Issue:1
AU-4 / AU-3 - ADMINISTRATIVE UNIT ALARMS

In the following all the alarms detected at the AU (Administrative Units Alarms) level are reported.
AU-LOP (AU-4 / AU-3)

Category: URG_EXT Priority: 90
Loss Of Administrative Unit Pointer.
Problem:
1. Transmitter of the far end equipment is configured for a different multiplexing path (AU-3/AU-
4) or standard (SONET/SDH)
Action:
1. Use the Control Application to check the local configuration, check the remote configuration.
2. Check the status of the far-end equipment and the local and far-end configuration
AU-AIS (AU-4 / AU-3) [LC]

Administrative Unit Alarm Indication Signal received from the remote equipment AU-AIS defect is
detected by the MS Adaptation function when all 1 in the entire AU including AU pointer are
observed (for three or more frames)
Problem:
1. Fault on the far end equipment
Action:
1. Check the status of the far-end equipment
TxAURejustFail (AU-4 / AU-3)

Category: URG_INT Priority: 92
A buffer memory overflow error on the mux asic (transmit side) due to an excessive slip between
internal and line Tx clock
Problem:
1. Consequence of a synchronisation alarm
Action:

.
Issue:1
RxAURejustFail (AU-4 / AU-3)

A buffer memory overflow error on the mux asic (receive side) due to an excessive slip between
internal and line Rx clock
Problem:
1. Consequence of: failure on the far-end transmitter
Action:
AU-Mtx-LOP (AU-4 / AU-3)

Loss Of Administrative Unit Pointer of the proprietary stream on Matrix side.
Problem:
1. Port Unit internal failure or Trib./Matrix Interface Unit failure. Matrix internal failure.
Action:
AU-Mtx-AIS (AU-4 / AU-3)

Category: IND_Generic Priority: 91
Administrative Unit Alarm Indication Signal received on Matrix side from the transmitting Port Unit.
Problem:
1. Fault on the transmitting Port Unit
Action:
1. Check the status of the transmitting Port Unit

.
Issue:1
VC-4 - HIGH ORDER VC ALARM

In the following all the alarms detected at the VC (Virtual Containers Alarms) level are reported.
HP-TIM (VC-4)
Problem:
Action:
1. Check the local and far-end configuration
HP-PLM (VC-4)
Mismatch between the received and expected payload label byte value (C2)
Problem:
1. Transmitter on the far-end equipment configured to work with a different payload
Action:
HP-LOM (VC-4)
A Loss of the TU multiframe event is reported when N x H4 values are received consecutively not
correctly in sequence with any part of the multiframe sequence (2 N 10)
Problem:
Action:
1. Use the Control Application to create a local loop-back on the unit. If the alarm goes OFF,
check the status of the far-end equipment
2. Use the Control Application to create a local loop-back on the unit. If the alarm stays ON,
proceed as indicated in:

.
Issue:1
HP-RDI (VC-4) [LC]

High order Path Remote Defect Indication is used to return an indication to the transmit end that the
received end has received an invalid VC-4-Xc/VC-4/VC-3 signal. An incoming HP-RDI is detected
by the High Order path Termination function when value 1 in bit 5 of the G1 byte within two frames
is observed
Problem:
1. Consequence of of the following alarms detected on the receive side of the far-end
equipment:
SPI-LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP
AU-AIS
HP-TIM
HP-PLM
HP-LOM
Action:
1. Check the status of the far-end equipment and follow the trouble-shooting procedure for the
main alarm
HP-AIS (VC-4) [LC]

High order Path Alarm Indication Signal declared by the High Order path Termination (HPT,
140Mb/s PDH port) or by the Higher Order Path Overhead Monitor (HPOM). HP-AIS defect is
detected by the HPT or the HPOM when all 1 in the entire AU including AU pointer are observed
(for three or more frames)
Problem:
Action:

.
Issue:1
HP-DEG (VC-4)
Category: NURG_EXT Priority: 102
A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) on the received
higher level payload exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be
configured via software). Errors are calculated by checking the BIP-8 on the received data and the
corresponding value present in byte B3
Action:
1. Check if the same alarm is detected at the termination of the path. If the alarm is DETECTED,
follow the procedure for the path termination alarm
2. Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, proceed as indicated in:
HP-EXC (VC-4)
An Excessive error defect is detected when the equivalent Bit Error Rate (BER) exceeds a threshold
of 10-3 on the received signal. Errors are calculated by checking the BIP-8 on the received data and
the corresponding value present in byte B3 (see above)
Action:
1. Check if the same alarm is detected at the termination of the path. If the alarm DETECTED,
2. Check if the same alarm is detected at the termination of the path. If the alarm NOT
HP-UNEQ (VC-4)
An Unequipped defect is declared when five consecutive VC-4 frames contain the 00000000
pattern in byte C2
Problem:
1. Signal Label (C2) transmission on the far-end equipment not configured
Action:
1. Check the far-end configuration

.
Issue:1
RDIPayload (VC-4) [LC]

Remote Payload Defect Indication (applicable to ATM equipment only) is used to return an
indication to the transmit end that the received end has received an LCD signal (Loss of Cell
Delineation). An incoming RDIPayload is detected by the HPT or by the HPOM function when the
pattern 010 is observed in bits 5, 6 and 7 of the G1 byte in at least three consecutive frames
(according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (if ATM equipment)
Action:
RDIServer (VC-4) [LC]

Remote Server Defect Indication is used to return an indication to the transmit end that the received
end has received an AIS or LOP signal. An incoming RDIServer is detected by the HPT or by the
HPOM function when the pattern 101 is observed in bits 5, 6 and 7 of the G1 byte in at least three
consecutive frames (according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (AIS, LOP)
Action:
RDIConnectivity (VC-4) [LC]

Remote Connectivity Defect Indication is used to return an indication to the transmit end that the
received end has received an TIM or UNEQ signal. An incoming RDIConnectivity is detected by the
HPT or by the HPOM function when the pattern 110 is observed in bits 5, 6 and 7 of the G1 byte in
at least three consecutive frames (according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (TIM, UNEQ)
Action:

.
Issue:1
TC-ISF (VC-4)
Indication of Failure on an Incoming Signal (ISF) detected at the origination point of the Tandem
Connection. This signal (all "1" in the IEC code - bits from 1 to 4 of the N1 byte) is generated by the
"Source" side and transmitted toward the "Sink" side. When an ISF is received at the end of the
Tandem Connection an AU-4 AIS shall be inserted in the appropriate outgoing signal.
Problem:
1. Fault on the far end equipment or along the line
Action:
1. Check the status of the far-end equipment or of the line
TC-UNEQ (VC-4)
The Unequipped Tandem Connection defect is detected if five consecutive VC-4 frames contain all
"0" in the N1 byte pattern and it is cleared if in five consecutive VC-4 frames contain a valid N1 byte
pattern.
Problem:
1. This alarm indicate that the "Source" side is not configured or there is a "Source" and "Sink"
configuration mismatch.
Action:
1. Check the configuration status of the "Source" and "Sink" equipment
TC-DEG (VC-4)
Errors are assumed to be distributed in a "bursty" fashion. The number of detected Errored Blocks is
evaluated over a one second period. A second is declared BAD if then number of Errored Block
during this second (E) reaches or exceeds a preset threshold DEGTHR. On the contrary, if E <
DEGTHR the second is declared GOOD. DEG alarm indication is activated if M consecutive BAD
seconds are detected. DEG alarm indication is removed if M consecutive GOOD seconds are
detected. The value of M is in the range from 2 to 10, while DEGTHR is programmable to values
from 0 to N, being N the number of blocks per second. The default value of M is 3 seconds and the
default value of DEGTHR is 30 % errored blocks during one second.
Note Note that according to ETS 300 417-1-1 an AIS signal has zero errored blocks. Thus
as a consequence if an higher order defect causing AIS downstream stays persistent
during a second this second shall be counted as a GOOD second. This leads to the
conclusion that the DEG defect will be cleared within M seconds if an higher order
defect causing AIS downstream stays persistent.
Two thresholds for the declaration of a GOOD/BAD second (DEGTHRB and DEGTHRG) and for the
activation/deactivation of a DEG indication (Mon and Moff) should be provided.
TC DEG detection shall be suppressed while SSF is received.

.
Issue:1
Problem:
Malfunction of Source transmitter
Action:
TC-EXC (VC-4)
An Excessive error defect is detected when the equivalent Bit Error Rate (BER) calculated by the
"Sink" on the received signal (Tandem Connection monitoring) exceeds a threshold of 10-3. The
detection criteria are the same for the TC-DEG alarm.
Problem:
Failure of the Source transmitter
Action:
RDI-OR (VC-4)
Logic OR of the Enhanced-RDI alarms (Server-Connectivity-Payload).
Problem:
Action:
HO-V4-FAIL_A (VC-4)
Category: NURG_INT_Mx Priority: 55
Errors detected on the diagnostic message (V4 Protocol) received with the data (VC-4 channel)
from the Matrix A.
Action:
1. Check the active alarms on Matrix A, Port Unit involved in the connection and MIU
2. Check the data interconnection cable

.
Issue:1
Data Interconnection Diagram (DXC 4/1), General Index
HO-V4-FAIL_B (VC-4)
from the Matrix B.
Action:
1. Check the active alarms on Matrix B, Port Unit involved in the connection and MIU
HO-LOM VCnV (VC-4)

Loss of Multiframe in a VC-4-nV concatenated traffic type. If several H4 values are received
consecutively not correctly in sequence with any part of the multiframe sequence, then a loss of
multiframe (LOM) event is reported. This alarm is associated to a STM-16 MUX 4/3 card and
concerns the Virtual Concatenations.
Problem:
1. Errors during the reconstruction of the virtual concatenated traffic type.
Action:
1. Check the remote equipment where the VC-4s come from and their paths.
HO-SQM VCnV (VC-4)

Loss of Sequence defect is detected if the accepted sequence number does not match the
expected Sequence number. The received sequence number (SQ) is recovered from the H4 byte,
bits 1-4 in multiframe 14 and 15. The alarm is associated to a STM-16 MUX 4/3 card and concerns
the Virtual Concatenations.
Problem:
1. The number of received multiframes with not correct SQ has exceeded the threshold set
(SQM Defect Issue Thr).
Action:

.
Issue:1
HO-LOA VCnV (VC-4)

Loss of Alignment: is detected when creating a contiguous concatenation from a virtual one, each
AU-4 must fit into its correct position; if an AU-4 is not received into the expected position, a LOA
defect is detected.The alarm is associated to a STM-16 MUX 4/3 card and concerns the Virtual
Concatenations.
Problem:
1. Error during the positioning of the VC-4s. The VC-4 has been inserted in a wrong position.
Action:
1. Check the cross connections.
HO-LOA RecVCnV (VC-4)

Recoverable Loss of Alignment is detected if the alignment process cannot perform the alignment of
the individual VC-4s to a common multiframe start (e.g. LOA is activated if the differential delay
exceeds the size of the alignment buffer). The alarm is associated to a STM-16 MUX 4/3 card and
Problem:
1. Problem reconstructing virtual concatenation. The delay between a VC-4 and the following
one has exceeded the threshold allowed. It could arise as consequence of a not proper
Differantial Delay.
Action:
1. Try to pass to Autoadaptive mode in the Differantial Delay bar.
HO-INCJ1-Mism VCnV (VC-4)

Mismatch between the received and the expected high order path trace identifier byte detected on
the VC-4 coming from the matrix and belonging to a virtual concatenated traffic type. The alarm is
associated to a STM-16 MUX 4/3 card and concerns the Virtual Concatenations.
Problem:
Action:

.
Issue:1
HO-UneqMtx (VC-4)
pattern in byte C2. This alarm is detected on the matrix side and it is relevant to a VC-4-nV
concatenated traffic type. The alarm is associated to a STM-16 MUX 4/3 card and concerns the
Virtual Concatenations.
Problem:
1. Transmitter on the far-end equipment not configured
Action:
TU3 / TU2 / TU12 - TRIBUTARY UNIT ALARMS

Note This alarm source is managed only by DXC 4/1 and partially DXC 4/4 1024x1024,
where the TU-3 alarm source is monitored.
In the following all the alarms detected at the TU (Tributary Unit Alarms) level are reported.
LPOM-LOP (TU3 / TU2 / TU12)

Loss Of TU Pointer. A Loss Of Pointer failure is detected when N consecutive NDF (New Data Flag)
or Invalid Pointers (three or more of the four N-bits do not match the pattern 0110) are received (8
N 10)
Problem:
1. Alarm active on the far-end transmitter
Action:
2. Delete the VC connection on the far-end equipment where the path is terminated, and create
on the remote STM-1 Interface a unidirectional connection between Tx and Rx of the alarmed
VC. If the alarm goes OFF, check the status of the far-end equipment
3. Delete the VC connection on the far-end equipment where the path is terminated, and create
VC. If the alarm stays ON, proceed as indicated in:

.
Issue:1
LPOM-AIS (TU3 / TU2 / TU12) [LC]

Tributary Unit Alarm Indication Signal received from the remote equipment. TU-AIS defect is
detected by the HP Adaptation function when all 1 in the entire TU including TU pointer are
observed (for three or more frames)
Problem:
Action:
LPOM-DEG (TU3 / TU2 / TU12) [LC]

A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) on the received lower
level payload exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be configured
via software). Errors are calculated by checking:
- for the TU2/TU12 the BIP-2 on the received data and the corresponding value present in the bit 1
and 2 of the byte V5
- for the TU3 the BIP-8 on the received data and the corresponding value present in byte B3
Action:
LPOM-EXC (TU3 / TU2 / TU12) [LC]

of 10-3 on the received signal. Errors are calculated by checking:
- for the TU2/TU12 the BIP-2 on the received data and the corresponding value present in the bit 1
and 2 of the byte V5
- for the TU3 the BIP-8 on the received data and the corresponding value present in byte B3
Action:

.
Issue:1
LPOM-UNEQ (TU3 / TU2 / TU12) [LC]

The VC "unequipped" is generated to indicate that the VC is not connected (via switching matrix) to
any source point. The unexpected reception of a VC "unequipped" indicates that a connection error
has occurred on the path. Unequipped alarm indication is activated when the Signal Label (bits from
5 to 7 of the byte V5 for TU-2 and TU-12, byte C2 for TU-3) of the VC is "0".
Problem:
1. Signal Label transmission on the far-end equipment not configured
Action:
LPOM-RDI (TU3 / TU2 / TU12) [LC]

Remote Defect Indication is used to return an indication to the transmit end that the received end
has received an invalid signal. RDI indication is detected when:
- for TU-2 and TU-12, the received bit 8 of byte V5 is equal to "1" for 5 consecutive frames.
- for TU-3, the received bit 8 of byte G1 is equal to "1" for 5 consecutive frames.
Problem:
1. Consequence of alarm:
LP-TIM
LP-PLM
LP-EXC
LP-UNEQ
detected on the receive side of the far-end equipment
Action:
main alarm
LPOM-TIM (TU3 / TU2 / TU12) [LC]

Mismatch between the received and the expected path trace identifier byte (byte J2 for TU-2 and
TU-12, byte J1 for TU-3)
Problem:
Action:

.
Issue:1
LPOM-PLM (TU3 / TU2 / TU12) [LC]

Mismatch between the received and expected payload label byte value (bits from 5 to 7 of the byte
V5 for TU-2 and TU-12, byte C2 for TU-3).
Problem:
Action:
V4-FAIL_A (TU3 / TU2 / TU12)

Errors detected on the diagnostic message (V4 Protocol) received with the data (VC-12, VC-2 or
VC-3 channel) from the Matrix A.
Action:
V4-FAIL_B (TU3 / TU2 / TU12)

Errors detected on the diagnostic message (V4 Protocol) received with the data (VC-12, VC-2 or
VC-3 channel) from the Matrix B.
Action:
TC-ISF (TU3 / TU2 / TU12)

Connection. This signal (all "1" in the IEC code) is generated by the "Source" side and transmitted
toward the "Sink" side.
Problem:
Action:

.
Issue:1
TC-UNEQ (TU3 / TU2 / TU12)

"0" in the N byte pattern and it is cleared if in five consecutive VC-4 frames contain a valid N byte
pattern.
Problem:
Action:
TC-DEG (TU3 / TU2 / TU12)

Problem:
Action:

.
Issue:1
TC-EXC (TU3 TU2 TU12)

"Sink" on the received signal (Tandem Connection monitoring) exceeds a threshold of 10-3. The
detection criteria are the same for the TC-DEG alarm.
Problem:
Action:
VC-3 - LOW ORDER VC ALARMS

Note For DXC 4/1 and DXC 4/4 1024x1024 only.
LP-TIM (VC-3)
Mismatch between the received and expected path trace identifier byte (J1)
Problem:
Action:
LP-PLM (VC-3)
Mismatch between the received and expected payload label byte value (bit 5, 6 and 7 of byte V5)
Problem:
1. Transmitter on the far-end equipment configured to work with a different payload label
Action:

.
Issue:1
LP-LOM (VC-3)
correctly in sequence with any part of the multiframe sequence (2 N 10). For TU-3 the insertion
of AIS downstream is not applicable
Problem:
Action:
1. Set with the Control Application a local loop-back on the unit. If the alarm goes OFF, check
the status of the far-end equipment
2. Set with the Control Application a local loop-back on the unit. If the alarm stays ON, proceed
as indicated in:
LP-RDI (VC-3) [LC]

Category: IND_34-45Mb Priority: 101
Lower order Path Remote Defect Indication is used to return an indication to the transmit end that
the received end has received a TU-2/TU-1 path AIS or signal failure. An incoming LP-RDI is
detected by the LPOM or by the LPT function when value 1 in bit 8 of the V5 byte within two
multiframes is observed
Problem:
LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP
AU-AIS
HP-TIM
HP-PLM
TU-LOP
LP-PLM
LP-TIM
LP-EXC

.
Issue:1
Action:
main alarm
LP-AIS (VC-3) [LC]

Lower order Path Alarm Indication Signal declared by the Lower Order path Termination (PDH port)
or by the Lower Order Path Overhead Monitor (LPOM). LP-AIS defect is detected by the HPT or the
HPOM when all 1 in the entire TU including TU pointer are observed (for three or more frames)
Problem:
Action:
LP-DEG (VC-3)
via software). Errors are calculated by checking the BIP-8 on the received data and the
Action:
LP-EXC (VC-3)
the corresponding value present in byte B3 (see above)
Action:

.
Issue:1
LP-UNEQ (VC-3)
pattern in byte C2
Problem:
Action:
RDIPayload (VC-3) [LC]

Remote Payload Defect Indication (applicable to ATM equipment only) is used to return an
indication to the transmit end that the received end has received an LCD signal (Loss of Cell
Delineation). An incoming RDIPayload is detected by the HPT or by the HPOM function when the
pattern 010 is observed in bits 5, 6 and 7 of the G1 byte in at least three consecutive frames
(according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (if ATM equipment)
Action:
RDIServer (VC-3) [LC]

Remote Server Defect Indication is used to return an indication to the transmit end that the received
end has received an AIS or LOP signal. An incoming RDIServer is detected by the HPT or by the
HPOM function when the pattern 101 is observed in bits 5, 6 and 7 of the G1 byte in at least three
consecutive frames (according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (AIS, LOP)
Action:

.
Issue:1
RDIConnectivity (VC-3) [LC]

Remote Connectivity Defect Indication is used to return an indication to the transmit end that the
received end has received a TIM or UNEQ signal. An incoming RDIConnectivity is detected by the
HPT or by the HPOM function when the pattern 110 is observed in bits 5, 6 and 7 of the G1 byte in
at least three consecutive frames (according to Rec. G.707 Appendix VII)
Problem:
1. Fault on the far end equipment (TIM, UNEQ)
Action:
VC-12 - LOW ORDER VC ALARMS

Note For DXC 4/1 only
LP-LOP (VC-12)
N 10)
Problem:
1. Wrong or damaged cabling between matrix and port subrack
2. Trib./Matrix Interface Unit Internal Failure
Action:
Data Interconnection Diagram (DXC 4/1)
LP-AIS (VC-12) [LC]

Lower order Path Alarm Indication Signal declared by the Lower Order Path Termination (LPT, PDH
port) or by the Lower Order Path Overhead Monitor (LPOM). LP-AIS defect is detected by the HPT
or the HPOM when all 1 in the entire TU including TU pointer are observed (for three or more
frames)
Problem:
Action:

.
Issue:1
LP-RDI (VC-12) [LC]

the received end has received a TU path AIS or signal failure. An incoming LP-RDI is detected by
the Lower Order Path Termination function when value 1 in bit 8 of the V5 byte within two frames
is observed
Problem:
1. Consequent action of alarm:
LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP
AU-AIS
HP-TIM
HP-PLM
HP-LOM
TU-LOP
LP-PLM
LP-TIM
LP-EXC
Action:
main alarm
LP-EXC (VC-12)
the corresponding value present in bit 1 and 2 of byte V5
Problem:
Failure on the far-end transmitter

.
Issue:1
Action:
LP-DEG (VC-12)
corresponding value present in bit 1 and 2 of byte V5
Problem:
Malfunction on the far-end transmitter
Action:
LP-PLM (VC-12)
Mismatch between the received and expected payload label value (bit 5-6-7 of V5)
Problem:
Action:
LP-TIM (VC-12)
Mismatch between the received and expected low order path trace identifier (byte J2)
Problem:
1. Transmitter on the far-end equipment configured with a different low order path trace identifier
Action:

.
Issue:1
LP-UNEQ (VC-12)
An Unequipped defect is declared when five consecutive VC-12 frames contain the 000 pattern in
bit 5, 6 and 7 of byte V5
Problem:
Action:
V4-FAIL_A (VC-12)
Category: NURG INT Mx Priority: 55
from the Matrix A.
Action:
V4-FAIL_B (VC-12)
from the Matrix A.
Action:
TU-TC-PATH-AIS (VC-12)
Category: IND Generic Priority: 121
Connection.
This signal ("1" in the bit 4 of the N2 byte) is generated by the "Source" side and transmitted toward
the "Sink" side. When an ISF is received at the end of the Tandem Connection an AU-4 AIS shall be
inserted in the appropriate outgoing signal.
Problem:

.
Issue:1
Action:
NOTICE Alarm not yet managed.
TU-TC-PATH-UNEQ (VC-12)
Category: URG EXT Priority: 100
"0" in the N2 byte pattern and it is cleared if in five consecutive VC-12 frames contain a valid N2
byte pattern.
Problem:
Action:
TU-TC-PATH-RDI (VC-12)
Category: IND 2Mb Priority: 123
The Tandem Connection - Remote Defect Indication indicates to the far end that defects have been
detected within the Tandem Connection at the near end Tandem Connection sink (bit 8 in the 73rd
multiframe).
Problem:
1. Consequence of failure detected on the received signal.
Action:
main alarm
TU-VC-PATH-RDI (VC-12)
is observed
Note Supported by 45 T-Mux Unit only.
Problem:
1. Consequent action of alarms detected on the receive side of the far-end equipment

.
Issue:1
Action:
main alarm
TU-RFI (VC-12)
The VC-12 path Remote Failure Indication (RFI) is sent back by the VC-12 termination. This alarm
is declared when the bit n.4 of the V5 byte is set to 1.
Note A failure is a defect that persists beyond the maximum time allocated to the
transmission system protection mechanism.
Problem:
Action:
TU-NO-RxTraceId (VC-12)
Category: NURG INT 2Mb Priority: 100
No LO path trace identifier byte (J2) received.
Problem:
1. Path trace identifier on the far-end equipment not configured
Action:
TU-NO-RxSigLab (VC-12)
Category: NURG INT 2Mb Priority: 100
No LO payload label (bit n.5, 6, and 7 of the V5 byte) received.
Problem:
1. Payload label on the far-end equipment not configured
Action:

.
Issue:1
2MB - 1.5 AND 2MBIT/S PDH INTERFACE ALARMS

In the following all the alarms detected at the PDH Interface level are reported.
TxBufferContention (2Mb)
Category: URG_EXT_2Mb Priority: 81
A buffer memory overflow/underflow error detected when it is not possible to insert the incoming
2Mbit/s signal into the C-12
Problem:
1. Incoming 2Mbit/s signal out of bit rate tolerance ( 50 ppm) or jitter value to high: probable
failure on the PDH connected equipment
Action:
1. Check the quality of the signal and the status of the PDH equipment
RxBufferContention (2Mb)
A buffer memory overflow/underflow error detected when it is not possible to extract the 2Mbit/s
signal from the C-12
Problem:
1. Problem on the synchronization quality of the 2Mbit/s in input on the far-end equipment
2. Mismatch in the network synchronization configuration
3. Consequence of a synchronization alarm
4. Consequence of a synchronization alarm on the far-end equipment
5. Internal unit failure
Action:
1. Check the quality on the input signal on the far-end station
2. Check with the Control Application the sync configuration for the local equipment and check
the sync configuration for the remote equipment
3. Follow the standard procedure for the main alarms
4. Check the alarms on the remote equipment

.
Issue:1
PDH-LOS (2Mb)
Loss of incoming tributary signal
Problem:
2. Consequent action of connected PDH equipment failure or line interruption
Action:
1. Disconnect the Tx and Rx coaxial cables and loop output with input using a test patch cord
and if the alarm stays ON, proceed as indicated in:
and if the alarm goes OFF, check the line and the PDH equipment status
PDH-AIS (2Mb) [LC]

Alarm Indication Signal received from the connected PDH equipment
Problem:
1. Fault on the connected PDH equipment
Action:
1. Check the status of the PDH equipment
PDH-EXC (2Mb)
of 10-3 on the received Tributary signal
Problem:
1. Consequent action of connected PDH equipment failure or line attenuation
Action:

.
Issue:1
PDH-DEG (2Mb)
A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) on the Tributary Input
exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be configured via software)
Problem:
Action:
IMPORTANT This procedure will put the 2Mb channel out of service
PDH-LOF (2Mb)
Loss of frame alignment on the incoming tributary signal
Problem:
1. Consequent action of connected PDH equipment failure or problems along the line
Action:
and if the alarm goes OFF, check the PDH equipment status and the line
CRC4Mismatch (2Mb)
Wrong CRC4 bit sequence
Problem:
1. Wrong configuration of the connected PDH equipment. It is probably preset for not using the
CRC4 function
Action:
1. Check configuration of the PDH equipment

.
Issue:1
CRC4RAI (2Mb) [LC]
Category: IND _2Mb Priority: 83

CRC4 remote alarm indication received from the PDH connected equipment, which is detecting
errors on the received CRC4 bit sequence
Problem:
1. Bit error rate along the line which connects the local tributary output and the remote PDH
equipment
Action:
1. Check the line and the PDH equipment status
PDH-RAI (2Mb) [LC]

Remote alarm indication received from the PDH connected equipment, which is detecting errors on
the received 2Mbit/s signal
Problem:
1. Excessive bit error rate or failures along the line which connects the local tributary output and
the remote PDH equipment
Action:
34MB - 34 AND 45MBIT/S PDH INTERFACE ALARMS

Note For DXC 4/1 only.
Category: URG_EXT_34-45Mb Priority: 81
A buffer memory overflow/underflow error detected when it is not possible to insert the 34/45Mbit/s
signal into the C-3
Problem:
1. 34Mbit/s Input out of bit rate tolerance ( 30 ppm) or jitter value to high: probable failure on the
PDH connected equipment
Action:

.
Issue:1
Category: URG_INT_34-45Mb Priority: 81
A buffer memory overflow/underflow error detected when it is not possible to extract the 34/45Mbit/s
signal from the C-3
Problem:
4. Consequence of a synchronisation alarm on the far-end equipment
Action:
PDH-LOS (34Mb)
Problem:
Action:

.
Issue:1
PDH-AIS (34Mb) [LC]

Problem:
Action:
PDH-EXC (34Mb)
Problem:
Action:
PDH-DEG (34Mb)
Category: NURG_EXT_34-45Mb Priority: 84
exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be configured via
software).
Problem:
Action:
IMPORTANT This procedure will put the 34 or 45Mb channel out of service

.
Issue:1
PDH-LOF (34Mb)
Loss of the 34 or 45Mbit/s frame alignment word
Problem:
1. Consequent action of connected PDH equipment failure
Action:
and if the alarm goes OFF, check the PDH equipment status
PDH-TxFail (34Mb)
Loss of the 34 or 45Mbit/s signal transmitted towards the PDH network
Problem:
Action:
PDH-INParityError (34Mb)
Category: NURG_EXT_34-45Mb Priority:55
Parity check errors on the incoming 34-45Mbit/s signal
Problem:
1. 34-45Mbit/s remote equipment failure or problems along the line
Action:
IMPORTANT This procedure will put the 45Mbit/s link out of service
and if the alarm goes OFF, check the line and the 45Mbit/s remote equipment status

.
Issue:1
PDH-INClockFail (34Mb)
Loss of clock signal extracted from the received tributary stream
Problem:
Action:
45MbYellowSignal (34Mb)
Yellow signal indication received on the 45Mbit/s frame
Problem:
Action:
45MbIdleSignal (34Mb)
Idle signal indication received on the 45Mbit/s frame
Problem:
Action:

.
Issue:1
140MB - 140MBIT/S PDH INTERFACE ALARMS

Category: URG_EXT_140MbPriority:81
A buffer memory overflow/underflow error detected when is not possible to insert the 140Mbit/s
signal into the C-4
Problem:
1. 140Mbit/s in Input out of bit rate tolerance ( 15 ppm) or jitter value too high: probable failure
on the PDH connected equipment
Action:
Category: URG_INT_140Mb Priority:81
A buffer memory overflow/underflow error detected when is not possible extract the 140Mbit/s signal
from the C4
Problem:
1. Problem on the synchronization quality of the 140Mbit/s input on the far-end equipment
Action:
1. Check the quality on the input signal at the far-end station
PDH-LOS (140Mb)
Problem:
1. Consequence of connected PDH equipment failure or line interruption

.
Issue:1
Action:
1. Disconnect the Tx and Rx coaxial cables and loop output to input using a test patch cord. If
the alarm goes OFF, check the line and the PDH equipment status
the alarm stays ON, proceed as indicated in:
PDH-AIS (140Mb) [LC]

Category: IND_140Mb Priority:82
Problem:
Action:
PDH-EXC (140Mb)
Problem:
1. Consequence of connected PDH equipment failure or line attenuation
Action:
1. Disconnect the Tx and Rx coaxial cables and loop output to input using a test patch cord . If
PDH-DEG (140Mb)
Category: NURG_EXT_140Mb Priority:84
Problem:
Action:
IMPORTANT This procedure will take the 140Mb channel out of service

.
Issue:1
PDH-LOF (140Mb)
Loss of the 140Mbit/s frame alignment word
Problem:
Action:
PDH-TxFail (140Mb)
Loss of the 140Mbit/s signal transmitted towards the PDH network
Problem:
Action:
PDH-INParityError (140Mb)
Foreseen for future uses
PDH-INClockFail (140Mb)
Problem:

.
Issue:1
Action:
1. Disconnect the Tx and Rx coaxial cables and loop output to input using a test patch cord and
if the alarm goes OFF, check the line and the PDH equipment status.
2. Disconnect the Tx and Rx coaxial cables and loop output to input using a test patch cord and
if the alarm stays ON proceed as indicated in:
PDH-RAI (140Mb) [LC]

Remote Alarm Indication received from the PDH connected equipment, which is detecting errors on
Problem:
Action:
RDI (140Mb)
Remote Defect Indication is used to return an indication to the transmit end that the received end
has received an invalid signal.
Problem:
1. Fault on the far end equipment.
Action:
main alarm

.
Issue:1
8MBCH - ALARMS OF 8MBIT/S CHANNELS OF A

T-MUX UNIT
In the following all the alarms detected at the PDH Channels level are reported.
AIS (8MbCh) [LC]

Alarm Indication Signal received from the remote 8Mbit/s PDH equipment
Problem:
1. Fault is probably on the 8Mbit/s PDH equipment or along the line
Action:
LOF (8MbCh)
Category: URG_EXT_8Mb Priority:81
Problem:
Action:
EXC (8MbCh)
of 10-3 on the received 8Mbit/s Tributary channel
Problem:
1. Fault is probably caused by excessive bit error rate along the line
Action:
DEG (8MbCh)
A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) on the 8Mbit/s
Tributary Input channel exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be
configured via software)
Problem:
1. Fault is probably caused by bit error rate along the line

.
Issue:1
Action:
RAI (8MbCh) [LC]

Remote Alarm Indication received from the 8Mbit/s PDH equipment, which is detecting errors on the
received signal
Problem:
1. Excessive bit error rate or failures along the line
Action:
34MBCH - ALARMS OF 34MBIT/S CHANNELS OF A

T-MUX UNIT
AIS (34MbCh)
Category: IND_34-45Mb Priority:82
Problem:
Action:
LOF (34MbCh)
Category: URG_EXT_34-45Mb Priority:81
Problem:
Action:

.
Issue:1
EXC (34MbCh)
of 10-3 on the received 34Mbit/s Tributary channel
Problem:
1. Fault is probably caused by excessive bit error rate along the line
Action:
DEG (34MbCh)
A Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) on the 34Mbit/s
Tributary Input channel exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be
configured via software).
Problem:
1. Fault is probably caused by bit error rate along the line
Action:
RAI (34MbCh)
Category: IND _34-45Mb Priority:83
Remote Alarm Indication signal received from the 34Mbit/s PDH equipment, which is detecting
errors on the received signal
Problem:
Action:

.
Issue:1
VIDEOCOD - 34MBIT/S VIDEOCODEC INTERFACE ALARMS

In the following all the alarms detected at the Port VideoCodec level are reported.
TxBufferContention (VideoCod)
A buffer memory overflow/underflow error detected when is not possible to insert the tributary signal
into the appropriate container
Problem:
1. 140Mbit/s in Input out of bit rate tolerance ( 15 ppm) or jitter value to high: probable failure on
the PDH connected equipment
Action:
RxBufferContention (VideoCod)
Category: URG_INT_34-45Mb Priority:81
A buffer memory overflow/underflow error detected when is not possible to extract the tributary
signal from the appropriate container
Problem:
Action:

.
Issue:1
PDH-LOS (VideoCod)
Problem:
1. Consequence of connected equipment failure or line interruption
Action:
1. Disconnect the Tx and Rx coaxial cables and loop output with input using a test patch cord . If
the alarm goes OFF, check the line and the connected equipment status
PDH-AIS (VideoCod)
Problem:
1. Fault on the connected equipment
Action:
1. Check the status of the connected equipment
PDH-EXC (VideoCod)
of 10-3 on the received Tributary Input
Problem:
1. Consequence of connected equipment failure or line attenuation
Action:

.
Issue:1
PDH-DEG (VideoCod)
channel exceeds a preset threshold in the range of 10-5 to 10-9 (the threshold can be configured via
software)
Problem:
1. Consequence of connected equipment failure or line attenuation
Action:
PDH-LOF (VideoCod)
Loss of the VIDEO_CODEC frame alignment word
Problem:
1. Consequence of connected equipment failure
Action:
PDH-LOMF (VideoCod)
Loss of the VIDEO_CODEC signal multiframe indication
Problem:
Action:

.
Issue:1
VC2-5C - CONCATENATED VIRTUAL CONTAINER ALARMS

In the following all the alarms detected at the Concatenated Virtual Container level are reported.
LP-LOP (VC2-5c)
Category: URG_EXT Priority:120
N 10)
Problem:
Action:
1. Delete on the far-end equipment where the path is terminated the VC connection and create
VC. If the alarm goes OFF, check the status of the far-end equipment
2. Delete on the far-end equipment where the path is terminated the VC connection and create
VC. If the alarm stays ON, proceed as indicated in:
LP-AIS (VC2-5c) [LC]

port) or by the Lower Order Path Overhead Monitor (LPOM). LP-AIS defect received from the
remote equipment is detected by the HPT or the HPOM when all 1 in the entire TU including TU
pointer are observed (for three or more frames)
Problem:
Action:

.
Issue:1
LP-EXC (VC2-5c)
of 10-3 on the received signal. Errors are calculated by checking the BIP-2 on each of the received
channel and the corresponding value present on each bit 1 and 2 of the byte V5
Problem:
Action:
LP-DEG (VC2-5c)
Category: NURG_EXT Priority:123
via software). Errors are calculated by checking the BIP-2 on each of the received channel and the
corresponding value present on each bit 1 and 2 of the byte V5
Problem:
Action:
LP-PLM (VC2-5c)
Mismatch between the received and expected payload label byte value (bit 5, 6 and 7 of V5 byte).
The check is performed on the first VC-2 only (Master)
Problem:
Action:

.
Issue:1
LP-UNEQ (VC2-5c)
bit 5, 6 and 7 of V5 byte. The check is performed on the first VC-2 only (Master)
Problem:
1. Transmitter on the far-end equipment not configure
Action:
2MBPDHCH - ALARMS OF 2MBIT/S CHANNELS OF A T-MUX UNIT

AIS (2MbPDHCh) [LC]

Problem:
Action:
LOF (2MbPDHCh)
Alarm not managed
EXC (2MbPDHCh)
Alarm not managed
DEG (2MbPDHCh)
Alarm not managed
RAI (2MbPDHCh) [LC]
Category: IND _2Mb Priority:83

Alarm not managed

.
Issue:1
RxFailure (2MbPDHCh)
signal from 34Mbit/s signal.
Problem:
Action:
MX1STU - 1ST STAGE MATRIX UNIT ALARMS

Note For DXC 4/1 only (not for DXC 4/1 512x512)
In the following all the alarms detected at the Mx1StU (1st Stage Matrix Unit Alarms) level are
reported.
MissingUnit (Mx1StU)
Category: NURG_INT_Mx Priority:40
Unit equipped but not fitted in the subrack
Problem:
1. Unit configured but not fitted
Action:
1. Insert the unit

.
Issue:1
UnitAddressError (Mx1StU)
Communication problems with MCU
Problem:
Matrix Control Unit Internal Failure
Action:
RxSyncLoss (Mx1StU)
Loss of supermultiframe sync signal from MTU
Action:
Synchronization Distribution Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 - DXC 4/1
512x512), Synchronization Distribution Diagram (DXC 4/1 32x32)
RxClockLoss (Mx1StU)
Loss of clock signal from MTU
Action:
STM-1_nParityError (Mx1StU)
Mismatch in the parity check of the nth STM-1 signal between Trib./Matrix Interface and
Concentrator Unit or Trib./Matrix Interface Unit and matrix. Parity value is calculated on all bits of
STM-1 frame and is inserted into the sixth byte of the first row (overrides one byte A2 of the next
frame) (n = 1 to 16)
Action:

.
Issue:1
TmngPulseLossn:n+1 (Mx1StU)
Loss of clock signal from the Trib./Matrix Interface Unit or Trib./Matrix Interface and Concentrator
Unit. This alarm is relevant to a couple of matrix accesses n:n+1 (n = 1, 3, 5, 7,9,11,13,15)
Action:
SyncPulseLossn:n+1 (Mx1StU)
The frame sync signal incoming from the Trib./Matrix Interface Unit or Trib./Matrix Interface and
Concentrator Unit is out of phase respect to the matrix frame sync. This alarm is relevant to a couple
of matrix accesses n:n+1 (n = 1,3,5,7,9,11,13,15)
Action:
MX2STU - 2ND STAGE MATRIX UNIT ALARMS

In the following all the alarms detected at the Mx2StU (2nd Stage Matrix Unit Alarms) level are
reported.
Unit not fitted in the subrack
Problem:
Action:
1. Insert the unit
Communication problems with Matrix Control Unit
Problem:

.
Issue:1
Action:
RxSyncLoss (Mx2StU)
Loss of supermultiframe sync signal from the Matrix Timing Unit
Action:
Loss of clock signal from the Matrix Timing Unit
Action:
Mismatch in the parity check of the nth STM-1 signal between I Stage Unit and II Stage Unit (n = 1
to 32)
Action:

.
Issue:1
MX3STU - 3RD STAGE MATRIX UNIT ALARMS

In the following all the alarms detected at the Mx3StU (3rd Stage Matrix Unit Alarms) level are
reported.
Problem:
Action:
1. Insert the unit
Problem:
Action:
RxSyncLoss (Mx3StU)
Action:

.
Issue:1
Action:
Mismatch in the parity check of the nth STM-1 signal between II Stage Unit and III Stage Unit (n=1
to 32)
TxSyncLoss1stHalf (Mx3StU)
Loss of frame sync signal to transmit towards the Matrix Interface Unit (1st half of the matrix
accesses managed by the card - STM-1_1:16).
Problem:
Action:
TxSyncLoss2ndtHalf (Mx3StU)
Problem:
Action:

.
Issue:1
MXIN - MATRIX INPUT SIDE ALARMS (FROM SIDE)

In the following all the alarms detected at the MxIn (Matrix Input Side Alarms) (from side) level are
reported.
UNEQAccess (MxIn)
I Stage Unit handling the access is missing
Note For DXC 4/1 512x512 see the description given for the alarm:
MissingUnit (Mx13StU_86)
Action:
MIUAddrError (MxIn)
Error in the communication between Trib./Matrix Interface Unit and I Stage Unit. A code relevant to
the matrix access used is inserted into the STM-1 stream overriding the fifth byte of the first row
(one A2)
Action:
UnitFail (MxIn)
Alarm detected on an access handled by the I Stage Unit - I/III Stage Unit for DXC 4/1 512x512 - or
by the Trib/Matrix Interface
Problem:
1. Problem on the data interconnection cable or on the Trib./Matrix Interface Unit
2. I Stage Unit Internal Failure
Action:
1. Check the active alarms on the MIU and check the data interconnection cable

.
Issue:1
MXOUT - MATRIX OUTPUT SIDE ALARMS (TO SIDE)

In the following all the alarms detected at the MxOut (Matrix Output Side Alarms) (To side) level are
reported.
UNEQAccess (MxOut)
III Stage Unit or I/III Stage Unit (in case of DXC 4/1 512x512) handling the access is missing
Action:
UnitFail (MxOut)
Internal unit failure on the III Stage Unit - I/III Stage Unit (in case of DXC 4/1 512x512) - handling the
access
Problem:
1. III Stage Unit Internal Failure or Trib./Matrix Interface Unit internal fault
Action:
MCU - MATRIX CONTROL UNIT ALARMS

In the following all the alarms detected at the MCU (Matrix Control Unit Alarms) level are reported.
MxNotCnfg (MCU)
Error programming the matrix
Problem:
1. Wrong Configuration
Action:
1. Check the matrix configuration

.
Issue:1
AND(MxPSU)Fail (MCU)
Category: URG_INT_AND(PSU) Priority:40
Failure of all Power Supply Units of the Matrix Subrack
Note Not managed by DXC 4/1 512x512
Problem:
1. Power Supply Unit Internal Failure
Action:
AND(MxBatt)Fail (MCU)
Category: URG_INT_AND(Batt) Priority:40
Failure of all battery voltages in at least one Power Supply Unit of the Matrix Subrack (not for DXC
4/1 512x512) or failure of all battery voltages of the Matrix Subrack (in case of DXC 4/1 512x512)
Problem:
1. Power cable damaged, fuse blown or thermal-magnetic breakers activated
Action:
1. Check breaker, fuses and cable
Line_AFail (MCU)
Communication fail on serial link A between Matrix Control Unit and Serial Expansion Unit
Action:
Line_BFail (MCU)
Communication fail on serial link B between Matrix Control Unit and Serial Expansion Unit
Action:

.
Issue:1
Mx_AMx_BFail (MCU)
The Central Control Unit detects that there is at least one failure on both Matrix Equipments and/or
at least one "matrix" failure on connected Port Subracks (both Matrix Equipments are disabled)
Action:
1. Check the active alarms on Matrix A and B
MTX_CntrFail (MCU)
Category: URG_INT_Mx Priority: 40
Communication to both the Serial Expansion Units is interrupted
Action:
MxBatt1..4Fail (MCU)
Category: NURG_EXT_Mx Priority: 40
Failure of battery voltages 1..4 (only for DXC 4/1 512x512).
Problem:
Action:
UnitProtVerMism (MCU)
Incompatibility between CCU software and MCU software version
Note This alarm is managed only by DXC 4/1 512x512
Action:
1. Check software release running on CCU and MCU
AND(MxBatt1-2)Fail (MCU)
Failure of battery voltages 1 and 2 (only for DXC 4/1 512x512).
Problem:
Action:

.
Issue:1
AND(MxBatt3-4)Fail (MCU)
Failure of battery voltages 3 and 4 (only for DXC 4/1 512x512).
Problem:
Action:
MTX_HwCntrFail (MCU)
MCU hardware failure (only for DXC 4/1 512x512).
Action:
SubrackAlarmAck (MCU)
Acknowledgement of the subrack alarm. This is not an alarm/fault indicator.
MTU - MATRIX TIMING UNIT ALARMS

In the following all the alarms detected at the MTU (Matrix Control Timing Alarms) level are
reported.
MissingUnit (MTU)
Category: URG_INT_Mx Priority:40
Problem:
Action:
1. Insert the unit

.
Issue:1
TSU_Aloss (MTU)
Loss of clock and frame sync signals from Timing Distributor Unit A
Action:
TSU_Bloss (MTU)
Loss of clock and frame sync signals from Timing Distributor Unit B
Action:
ClockOutLoss (MTU)
Failure of the internal oscillator of the Matrix Timing Unit
Problem:
Action:
SyncOutLoss (MTU)
Matrix Timing Unit is not able to generate the supermultiframe sync signal
Problem:
Action:

.
Issue:1
UnitPowerFail (MTU)
Power supply failure (for DXC 4/1 512x512 only)
Problem:
Action:
MPSU - MATRIX POWER SUPPLY ALARMS

In the following all the alarms detected at the MPSU (Matrix Power Supply Alarms) level are
reported.
MissingUnit (MPSU)
Unit not fitted into the subrack
Problem:
Action:
1. Insert the unit
UnitFail (MPSU)
Internal failure on the unit. Secondary voltages are not issued
Problem:
Action:

.
Issue:1
BattFail (MPSU)
Category: NURG_EXT_OR(Batt) Priority:40
Failure of at least one battery voltage
Problem:
Action:
MX13STU_86 - 1ST/3RD STAGE MATRIX UNIT ALARMS

Note For DXC 4/1 512x512 only
In the following all the alarms relevant to Mx13StU_86 cards (DXC 4/1 512x512 1st/3rd Stage
Matrix Unit Alarms) are reported.
Problem:
Action:
1. Insert the unit
UnitAddressError (Mx13StU_86)
Problem:
Action:

.
Issue:1
RxSyncLoss (Mx13StU_86)
Action:
512x512)
RxClockLoss (Mx13StU_86)
Action:
512x512)
UnitDistrClockLoss (Mx13StU_86)
Loss of clock signal from TDU
Action:
512x512)
UnitPowerFail (Mx13StU_86)
Power supply failure
Problem:
1. Unit internal failure
Action:
I/OmoduleMissingUnit (Mx13StU_86)
I and III Stage I/O Module Unit not fitted into the subrack.
Problem:
1. Unit not fitted

.
Issue:1
Action:
1. Insert the unit
2. Replace the unit
I/OModulePowerFail (Mx13StU_86)
I and III Stage I/O Module Unit power supply failure.
Problem:
Action:
1. Replace the unit
STM-1_I_nParityError (Mx13StU_86)
Action:
STM-1_III_nParityError (Mx13StU_86)
Mismatch in the parity check of the nth STM-1 signal between the second stage and the third stage
of the matrix. Parity value is calculated on all bits of STM-1 frame and is inserted into the sixth byte
of the first row (overrides one byte A2 of the next frame) (n = 1 to 32)
Action:
TmngPulseLossn:n+1 (Mx13StU_86)
Unit. This alarm is relevant to a couple of matrix accesses n:n+1
(n=1, 3, 5, ..., 15)
Action:

.
Issue:1
SyncPulseLossn:n+1 (Mx13StU_86)
of matrix accesses n:n+1 (n=1, 3, 5, ..., 15)
Action:
SignalLossn:n+1 (Mx13StU_86)
Loss of signal incoming from the Trib./Matrix Interface Unit or Trib./Matrix Interface and
Concentrator Unit. This alarm is relevant to a couple of matrix accesses n:n+1 (n=1, 3, 5, ..., 15)
Action:
TxSyncLoss1stHalf (Mx13StU_86)
Problem:
Action:
TxSyncLoss2ndtHalf (Mx13StU_86)
Problem:
Action:

.
Issue:1
TxClockFail1stHalf (Mx13StU_86)
Failure of the clock signal to transmit towards the Matrix Interface Unit (1st half of the matrix
Problem:
Action:
TxClockFail2ndHalf (Mx13StU_86)
Failure of the clock signal to transmit towards the Matrix Interface Unit (2st half of the matrix
Problem:
Action:
MX2STU_86 - 2ND STAGE MATRIX UNIT ALARMS

Note For DXC 4/1 512x512 only
In the following all the alarms relevant to Mx2StU_86 cards (DXC 4/1 512x512 2nd Stage Matrix
Unit Alarms) are reported.
Problem:
Action:
1. Insert the unit

.
Issue:1
Problem:
Action:
Action:
512x512)
Action:
512x512)
UnitDistrClockLoss (Mx2StU_86)
Loss of clock signal from TDU
Action:
512x512)

.
Issue:1
UnitPowerFail (Mx2StU_86)
Problem:
1. Unit internal failure
Action:
STM-1_nParityError (Mx2StU_86)
Mismatch in the parity check of the nth STM-1 signal between the first stage and the second stage
of the matrix. Parity value is calculated on all bits of STM-1 frame and is inserted into the sixth byte
of the first row (overrides one byte A2 of the next frame) (n = 1 to 64)
Action:
MX1STU_91 - 1ST STAGE MATRIX UNIT ALARMS

In the following all the alarms detected at the Mx1StU_91 (1st Stage Matrix Unit Alarms) level are
reported.
MissingUnit (Mx1StU-91)
Problem:
Action:
1. Insert the unit

.
Issue:1
Problem:
Action:
Action:
Synchronization Distribution Diagram (DXC 4/4 512x512)
Action:
Action:
Data Interconnection Diagram (DXC 4/4 512x512)

.
Issue:1
TmngPulseLossn:n+1 (Mx1StU_91)
Unit. This alarm is relevant to a couple of matrix accesses n:n+1 (n=1, 3, 5, ..., 31)
Action:
SyncPulseLossn:n+1 (Mx1StU_91)
of matrix accesses n:n+1 (n=1, 3, 5, ..., 31)
Action:
MX2STU_91 - 2ND STAGE MATRIX UNIT ALARMS

In the following all the alarms detected at the Mx2StU_91 (2nd Stage Matrix Unit Alarms) level are
reported.
Problem:
Action:
1. Insert the unit

.
Issue:1
Problem:
Action:
Action:
Action:
Mismatch in the parity check of the nth STM-1 signal between I Stage Unit and II Stage Unit (n = 1
to 64)
Action:

.
Issue:1
MX3STU_91 - 3RD STAGE MATRIX UNIT ALARMS

In the following all the alarms detected at the Mx3StU_91 (3rd Stage Matrix Unit Alarms) level are
reported.
Problem:
Action:
1. Insert the unit
Problem:
Action:
Action:

.
Issue:1
Action:
Mismatch in the parity check of the nth STM-1 signal between II Stage Unit and III Stage Unit (n = 1
to 64)
STM-1_1:16TxSyncLoss (Mx3StU_91)
Loss of frame sync signal to transmit towards the Matrix Interface Unit
Problem:
Action:
STM-1_17:32TxSyncLoss (Mx3StU_91)
Loss of frame sync signal to transmit towards the Matrix Interface Unit
Problem:
Action:

.
Issue:1
MXIN_91 - MATRIX INPUT SIDE ALARMS (FROM SIDE)

In the following all the alarms detected at the MxIn_91(Matrix Input Side Alarms) (from side) level
are reported.
UNEQAccess (MxIn_91)
I Stage Unit handling the access is missing
Action:
MIUAddrError (MxIn_91)
(one A2)
Action:
UnitFail (MxIn_91)
Alarm detected on the I Stage Unit or on the Trib/Matrix Interface handling the access
Problem:
1. I Stage Unit Internal Failure or Trib./Matrix Interface Unit internal fault
Action:

.
Issue:1
MXOUT - MATRIX OUTPUT SIDE ALARMS (TO SIDE)

In the following all the alarms detected at the MxOut_91(Matrix Output Side Alarms) (To side) level
are reported.
UNEQAccess (MxOut_91)
III Stage Unit handling the access is missing
Action:
MIUAddrError (MxOut_91)
(one A2)
Action:
UnitFail (MxOut_91)
Internal unit failure on the III Stage Unit handling the access
Problem:
1. III Stage Unit Internal Failure or Trib./Matrix Interface Unit Internal Failure
Action:

.
Issue:1
MCU - MATRIX CONTROL UNIT ALARMS

In the following all the alarms detected at the MCU_91 (Matrix Control Unit Alarms) level are
reported.
MissingUnit (MCU_91)
Problem:
Action:
1. Insert the unit
UnitFail (MCU_91)
Failure of Matrix Control Unit
Problem:
MxNotCnfg (MCU_91)
Error programming the matrix
Problem:
1. Wrong Configuration
Action:
1. Check the matrix configuration

.
Issue:1
AND(MxPSU)Fail (MCU_91)
Failure of all Power Supply Units of the Matrix Subrack
Problem:
Action:
AND(MxBatt)Fail (MCU_91)
Category: URG_INT_AND(Batt) Priority:40
Failure of all battery voltages in at least one Power Supply Unit of the Matrix Subrack
Problem:
Action:
Line_AFail (MCU_91)
Communication fail on serial link A between Matrix Control Unit and Serial Expansion Unit
Action:
Control Architecture Diagram (DXC 4/4 512x512)
Line_BFail (MCU_91)
Communication fail on serial link B between Matrix Control Unit and Serial Expansion Unit
Action:
Mx_A_Mx_BFail (MCU_91)
The Central Control Unit detects that there is at least one failure on both Matrix Equipments and/or
at least one "matrix" failure on connected Port Subracks (both Matrix Equipments are disabled)
Action:
1. Check the active alarms on Matrix A and B

.
Issue:1
Line_A_Line_BFail (MCU_91)
Communication to both the Serial Expansion Units is interrupted
Action:
MasterSlaveFail (MCU_91)
Failure in the connection between Master and Slave Matrices
Action:
MasterSlaveLinkOff (MCU_91)
Failure on the proprietary protocol between Master and Slave Matrices
Action:
MTU_91 - MATRIX TIMING UNIT ALARMS

In the following all the alarms detected at the MTU_91 (Matrix Control Timing Alarms) level are
reported.
MissingUnit (MTU_91)
Problem:
Action:
1. Insert the unit

.
Issue:1
TSU_Aloss (MTU_91)
Loss of clock and frame sync signals from Timing Distributor Unit A
Action:
TSU_Bloss (MTU_91)
Loss of clock and frame sync signals from Timing Distributor Unit B
Action:
ClockOutLoss (MTU_91)
Failure of the internal oscillator of the Matrix Timing Unit
Problem:
Action:
SyncOutLoss (MTU_91)
Matrix Timing Unit is not able to generate the supermultiframe sync signal
Problem:
Action:

.
Issue:1
MPSU_91 - MATRIX POWER SUPPLY ALARMS

In the following all the alarms detected at the MPSU_91 (Matrix Power Supply Alarms) level are
reported.
MissingUnit (MPSU_91)
Problem:
Action:
1. Insert the unit
UnitFail (MPSU_91)
Internal failure on the unit. Secondary voltages are not issued
Problem:
Action:
BattFail (MPSU_91)
Problem:
Action:

.
Issue:1
PORTUNIT - PORT UNIT ALARMS

In the following all the alarms detected at the PortUnit (Port Unit Alarms) level are reported.
MissingUnit (PortUnit)
Category: URG_INT Priority:40
Problem:
Action:
1. Insert the unit
UnitTypeMismatch (PortUnit)
Wrong unit fitted in a port slot
Problem:
1. Wrong unit fitted or wrong configuration
Action:
1. Check the configuration and, if necessary replace the unit
UnitFail (PortUnit)
Internal unit failure. Alarm is detected when the Port Control Unit is not able to configure the units
Problem:
Action:
CntrlBusFail (PortUnit)
Loss of communication with the Port Control Unit
Problem:
1. Unit Internal Failure or PCU Internal Fault

.
Issue:1
Action:
MxASignalFail (PortUnit)
Errors detected on the diagnostic message received with the data from the matrix
Action:
MxBSignalFail (PortUnit)
Errors detected on the diagnostic message received with the data from the matrix
Action:
Mx_AClockFail (PortUnit)
Loss of clock from Trib./Matrix Interface Unit A
Action:
Mx_BClockFail (PortUnit)
Loss of clock from Trib./Matrix Interface Unit B
Action:
TxOHBusDispFail (PortUnit)
Mismatch during the parity check on the overhead bus
Problem:
Unit Internal Failure on the Port Controller Unit

.
Issue:1
Action:
SelfTestFail (PortUnit)
Internal unit failure
Problem:
Action:
UnexpUnit (PortUnit)
Category: NURG_INT Priority:41
Unexpected card fitted
Problem:
1. Mismatch between software and hardware configuration
Action:
1. Create the configuration for the inserted unit
UnitHWMismatch (PortUnit)
Correct unit type but not correct hardware version
Problem:
1. The type of unit fitted in the specific position is of the correct type but not of the correct
hardware version
Action:
1. Modify the unit configuration or replace the inserted unit with a spare unit of the correct
hardware version
PwrFail (PortUnit)
Problem:
Action:

.
Issue:1
SyncSrcFail (PortUnit)
Synchronization pulses missing from Trib./Matrix Interface Unit towards the port unit
Problem:
1. Trib./Matrix Interface Unit internal failure
Port Unit Internal Failure
Action:
AsicFail (PortUnit)
Action:
5VNegFail (PortUnit)
Failure of the -5V voltage from the Power Supply Unit
Problem:
Action:
1. Check the -5.7 Volt Voltage on the measurement point on the front panel on the Power
Supply Unit (tolerance 5%): Voltage acceptable, proceed as indicated in:
Supply Unit (tolerance 5%): Voltage not acceptable, proceed as indicated in:
RxRegClockFail (PortUnit)
The clock cannot be recovered from the incoming signal
Problem:
Action:

.
Issue:1
PowerProblem (PortUnit)
Power failure.
Problem:
Action:
UnitError (PortUnit)
Action:
LTU-Fail (PortUnit)
140/155Mbit/s I/O module failure.
Problem:
1. Module missing
2. Power fail
3. Module failure
Action:
1. Insert the module
2. Replace the associated traffic unit
3. Replace the module
LTU-Mismatch (PortUnit)
Line terminal unit mismatch.
Problem:
1. Module mismatch
Action:
1. Insert the proper module

.
Issue:1
CK-OOF (PortUnit)
Internal clock out of frequency (PLL unlocked to the clock incoming from the TDU).
Problem:
Action:
TmpOutOfRange (PortUnit)
The temperature has passed the range accepted.
Problem:
1. Environmental conditions
Action:
1. Check the temperature in the site
BiasOutOfLimits (PortUnit)
This alarm indicates that laser bias current is out of limits.
Problem:
1. Unit Internal failure
Action:
PumpLaserFail (PortUnit)
This alarm indicates that laser does not work properly.
Problem:
1. Ageing / Current Shock
Action:
1. Replace the laser

.
Issue:1
AlsApsdActive (PortUnit)
Automatic Laser Shutdown Active. Automatic Power Shutdown Device Active.
Problem:
1. Loss of signal
Action:
1. Check the line
EmissionPwrOut (PortUnit)
This alarm indicates failure in the emission of power of Booster or Preamplifier.
Problem:
1. Ageing / Current Shock
Action:
2. Replace the laser
PCU - PORT CONTROL UNIT ALARMS

In the following all the alarms detected at the PCU (Port Control Unit Alarms) level are reported.
MissingUnit (PCU)
Category: NURG_INT_CA Priority:40
Problem:
Action:
1. Insert the unit

.
Issue:1
UnitFail (PCU)
Internal failure of the Port Control Unit
Action:
Control Architecture Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 - DXC 4/1
512x512), Control Architecture Diagram (DXC 4/1 32x32), General Index
UnitProtVerMism (PCU)
Incompatibility between CCU software and PCU software version
Action:
1. Check software release running on CCU and PCU
OR(Batt)Fail (PCU)
Failure of one battery voltage in the Port Subrack
Problem:
Action:
PCU_A_PCU_BFail (PCU)
Category: URG_INT_MCF Priority:40
The Central Control Unit cannot communicate to both the Port Control Units using both the Serial
Expansion Units
Action:
CtrlBusFault (PCU)
Category: NURG_INT_MCF Priority: 41
Failure of both Port Control Units (A and B).
Action:

.
Issue:1
FailFan (PCU)
Category: URG_INT_CA Priority:41
Fan module failed.
Problem:
1. Failure of at least one of the five fans
Action:
1. Check or replace the fan
ANDFailFanContr (PCU)
Both of the Fan Controller are failed or missing
Problem:
1. Both the Fan Controllers are failed or missing.
Action:
1. Check or insert the Fan Controllers.
ORFailFanContr (PCU)
At least one Fan Controller is failed or missing
Problem:
1. Failure or missing of at least one Fan Controller.
Action:
1. Check or insert the Fan Controller.
OverT (PCU)
Temperature out of range.
Problem:
1. The temperature has passed the range accepted.
Action:
1. Check the environmental conditions and the fan modules..

.
Issue:1
MissingFan (PCU)
Fan module missing.
Problem:
1. At least one of the fans is not present.
Action:
1. Insert the fan.
S3Mismatch (PCU)
Mismatch between the Port Controller software and its card type (e.g. : Port Controller Type E with a
software relevant to Port Controller Type 6/7).
Problem:
1. The software downloaded in the Port Controller is not the right one.
Action:
1. Download the proper software.
NoAdjacency (PCU)
Category: NURG_INT_MCF Priority:41
The Communication and Q Interface Units does not detect any adjacencies (layer 3) on the ethernet
network.
Problem:
1. Ethernet disconnected.
2. The remote OSI devices do not communicate (router, NM, etc.).
3. Wrong OSI configuration.
Action:
1. Check the ethernet cable.
2. Check the remote OSI devices.
3. Verify the OSI configuration.

.
Issue:1
PPSU - PORT SUBRACK POWER SUPPLY ALARMS

In the following all the alarms detected at the PPSU (Port Subrack Power Supply Alarms) level are
reported.
MissingUnit (PPSU)
Category: NURG_INT_OR(PSU) Priority:40
Note Not managed by Type 6/7 Subracks
Problem:
Action:
1. Insert the unit
PSUFail (PPSU)
Failure of at least one Power Supply Unit of the Port Subrack
Note Not managed by Type 6/7 Subracks
Problem:
Action:

.
Issue:1
IDU - IDENTIFICATION UNIT ALARMS

In the following all the alarms detected at the IDU (Identification Unit Alarms) level are reported.
MissingUnit (IdU)
Problem:
Action:
1. Insert the unit
SubrackIdMismatch (IdU)
Identifier of the port subrack defined using unit presettings different from the identifier defined in the
equipment data base (by means of Control Application)
Problem:
Action:
1. Check the unit hardware presettings and by using the Control Application define the same ID
SubrackTypeMismatch (IdU)
Mismatch in subrack type configuration
Problem:
1. Wrong subrack configuration by Control Application
2. PCU inserted in a wrong subrack
Action:
1. Check subrack configuration
2. Replace the PCU

.
Issue:1
AUXU - AUXILIARY UNIT ALARMS

In the following all the alarms detected at the AuxU (Auxiliary Unit Alarms) level are reported.
MissingUnit (AuxU)
Problem:
Action:
1. Insert the unit
UnitTypeMismatch (AuxU)
Wrong unit fitted in a port slot
Problem:
Action:
UnitFail (AuxU)
Problem:
Action:

.
Issue:1
CntrlBusFail (AuxU)
Loss of the communication with the Port Control Unit
Problem:
1. Unit Internal Failure or Port Control Unit Internal Failure
Action:
SelfTestFail (AuxU)
Failure of the unit self test
Problem:
Action:
UnexpUnit (AuxU)
Unexpected fitted card
Problem:
Action:
1. Create the configuration for the inserted unit

.
Issue:1
MIU - TRIB./MATRIX INTERFACE UNIT ALARMS

In the following all the alarms detected at the MIU (Matrix Interface Unit Alarms) level are reported.
MissingUnit (MIU)
Category: NURG_INT_COMMON Priority:40
Problem:
Action:
1. Insert the unit
WrongUnit (MIU)
Wrong unit fitted into the subrack (wrong SW release)
Problem:
Action:
UnitFail (MIU)
Problem:
Action:

.
Issue:1
CntrlBUSFail (MIU)
Problem:
Action:
Clock_AFail (MIU)
Loss of clock from Timing Distributor Unit A
Action:
512x512), Synchronization Distribution Diagram (DXC 4/1 32x32), General Index
Clock_BFail (MIU)
Loss of clock from Timing Distributor Unit B
Action:
SyncFail (MIU)
Loss of synchronization signal
Action:

.
Issue:1
PLLOutSyncFail (MIU)
Unit unable to generate a synchronisation output
Problem:
Action:
SyncPortClockFail (MIU)
The clock signal extracted from the Rx interface of one port for synchronization of the equipment is
missing
Problem:
1. Consequence of an Rx alarm detected on the port involved
2. Port Unit Internal Failure
Trib./Matrix Interface Unit internal failure
Action:
1. Follow the trouble-shooting procedure for the main alarm
ASIC_1Fail (MIU)
Failure of ASIC 1 within MIU
Problem:
Action:
1. This alarm induces alarms on the tributary port in slots 1, 2, 5, 6, 9 of the Type 2 Port
equipment (DXC4/1 only). Proceed as indicated in:

.
Issue:1
ASIC_2Fail (MIU)
Problem:
Action:
1. This alarm induces alarms on the tributary port in slots 3, 4, 7, 8, 9 of the Type 2 Port
equipment (DXC4/1 only). Proceed as indicated in:
NegPwrFail (MIU)
Failure of the -5V voltage from the Power Supply Unit
Problem:
Action:
Supply Unit (tolerance 5%). Voltage acceptable, proceed as indicated in:
Supply Unit (tolerance 5%). Voltage not acceptable, proceed as indicated in:
MIUSelfTestFail (MIU)
Problem:
Action:

.
Issue:1
Clock_A_Clock_BFail (MIU)
Category: URG_INT_COMMON Priority:40
Both clock signals from Timing Distributor Units A and B are missing
Action:
HWMismatch (MIU)
Category: NURG_INT_COMMON Priority: 42
Correct unit type but not correct hardware version
Problem:
1. The type of unit fitted in the specific position is correct but its hardware version is wrong
Action:
hardware version
PLL388MhzUnlock (MIU)
The PLL circuit on the transmit side is unlocked.
Problem:
Action:
388MHz_I/O_ModA..EFail (MIU)
Failure of I/O Module A..E for Matrix Interface (I/O 388MHz data)
Problem:
1. Module Failure
2. Module not fitted
3. Power fail
Action:
2. Insert the module

.
Issue:1
MIUMX - MATRIX INTERFACE / MATRIX ACCESS ALARMS

In the following all the alarms detected at the MIUMX (Matrix Interface / Matrix Access Alarms) level
are reported.
FrameSyncFail (MIUMx)
Frame synchronization failure incoming from III Stage Unit
Action:
MxClockFail (MIUMx)
Loss of clock signal from III Stage Unit
Action:
ParityError (MIUMx)
Parity mismatch between Trib./Matrix Interface Unit and Matrix Equipment
Action:
DestinationAddrError (MIUMx)
Destination address error (problem in the communication between III Stage Unit and Trib./Matrix
Interface Unit)
Action:
AccLOS (MIUMx)
Loss of matrix signal incoming from III Stage Unit.
Action:

.
Issue:1
MIUPORT - MATRIX INTERFACE / STM-1 PORT ACCESS ALARMS

In the following all the alarms detected at the MIUPort (Matrix Interface / STM-1 Port Access
Alarms) level are reported.
DispFail (MIUPort)
Mismatch in the parity between the Tributary port and Trib./Matrix Interface Unit
Problem:
1. Induced alarm due to tributary port (in slot n) alarmed or missing
Action:
1. Check the Port n alarms
MIU_MSP - MATRIX INTERFACE MSP ALARMS

In the following all the alarms detected at the MIU_MSP (Matrix Interface MSP Alarms) level are
reported.
MSP_INV (MIU_MSP)
Invalid APS (Automatic Protection Switch) protocol (MSP). Mismatch between the expected value of
the received K2 (bits 1 to 5 of byte K2) and sent K1 byte. MSP bytes is accepted as valid only when
identical bytes are received in three consecutive frames
Note A detected failure of the received K1 or K2 is considered as equivalent to an SF
(Signal Failure) condition on the protection section (MSP bytes are transmitted on the
protection section)
Problem:
1. Wrong MSP configuration
2. Internal failure on the local or far-end protection Line Unit
Action:
1. Check with the Control Application the local MSP configuration
Check the far-end MSP configuration

.
Issue:1
MSP_PAM (MIU_MSP)
Multiplex Section Protection Architecture Mismatch. Mismatch between the MSP (multiplexing
section protection) architecture configuration (1+1, 1:N or 1+N)
Problem:
Action:
MSPModeMismatch (MIU_MSP)
Mismatch between the MSP (multiplexing section protection) protection configuration mode
(revertive or not revertive)
Problem:
Action:
MIU_T3/6/7 - TRIB./MATRIX INTERFACE UNIT ALARMS

In the following all the alarms detected at the MIU (Matrix Interface Unit Alarms) level are reported.
MissingUnit (MIU_T3/6/7)
Problem:
Action:
1. Insert the unit

.
Issue:1
WrongUnit (MIU_T3/6/7)
Problem:
Action:
UnitFail (MIU_T3/6/7)
Problem:
Action:
CntrlBUSFail (MIU_T3/6/7)
Problem:
Action:
Clock_AFail (MIU_T3/6/7)
Action:

.
Issue:1
Clock_BFail (MIU_T3/6/7)
Action:
SyncPortClockFail (MIU_T3/6/7)
missing
Problem:
Action:
NoMonitClock (MIU_T3/6/7)
Loss of the 128KHz reference clock of the protection synchronization source.
Problem:
Action:

.
Issue:1
PLLOutSyncFail (MIU_T3/6/7)
Problem:
Action:
SyncFail (MIU_T3/6/7)
Action:
ClockOutOfFrequency (MIU_T3/6/7)
The clock signal generated by the CT equipment (9.72 MHz) and the unit internal clock (38.88MHz)
are not phase locked.
Problem:
1. System Oscillator degrade
Action:
1. Calibrate the System Oscillator
MasterSlaveLinkFail (MIU_T3/6/7)
Loss of connection between MIU Master and MIU Slave.
Problem:
1. Unit internal failure or back-panel failure
Action:

.
Issue:1
ASIC_1Fail (MIU_T3/6/7)
Problem:
Action:
ASIC_2Fail (MIU_T3/6/7)
Problem:
Action:
BackPanelUnknown (MIU_T3/6/7)
Unknown back-panel code.
Problem:
2. Wrong back-panel
Action:
2. Check the back-panel type
MIUSelfTestFail (MIU_T3/6/7)
Problem:
Action:

.
Issue:1
Clock_A_Clock_BFail (MIU_T3/6/7)
Action:
HW_Mismatch (MIU_T3/6/7)
Correct unit type but not correct hardware version. The MIU slave is not compatible with the MIU
master or the MIU master is not compatible with the matrix type.
Problem:
Action:
hardware version
388MHz_I/O_ModA..EMiss (MIU_T3/6/7)
Missing I/F Module A..D for Matrix Interface (I/O 388MHz data)
Problem:
Action:
1. Insert the unit
388MHz_I/O_ModA..EPowerFail (MIU_T3/6/7)
I/F Module A..D for Matrix Interface (I/O 388MHz data) power fail.
Problem:
1. Module failure
Action:
ImSwDownloading (MIU_T3/6/7)
Download in progress on the Matrix Interface Type 3/6/7

.
Issue:1
ImSwDownloadingFail (MIU_T3/6/7)
Download failed on the Matrix Interface Type 3/6/7
Problem:
1. File corrupted
2. Link down
Action:
1. Replace file
2. Repeat download
MIU_6E - TRIB./MATRIX INTERFACE UNIT ALARMS

In the following all the alarms detected at the MIU_6E/7E (Matrix Interface Unit Alarms) level are
reported.
MissingUnit (MIU 6E_7E)

Problem:
Action:
1. Insert the unit
WrongUnit (MIU 6E_7E)

Problem:
Action:

.
Issue:1
UnitFail (MIU 6E_7E)

Problem:
Action:
CntrlBUSFail (MIU 6E_7E)

Problem:
Action:
Clock_AFail (MIU 6E_7E)

Action:
Clock_BFail (MIU 6E_7E)

Action:

.
Issue:1
SyncPortClockFail (MIU 6E_7E)

missing
Problem:
Action:
NoMonitClock (MIU 6E_7E)

Loss of the 128KHz reference clock of the protection synchronization source.
Problem:
Action:
PLLOutSyncFail (MIU 6E_7E)

Problem:
Action:

.
Issue:1
SyncFail (MIU 6E_7E)

Action:
ClockOutOfFrequency (MIU 6E_7E)

The clock signal generated by the CT equipment (9.72 MHz) and the unit internal clock (38.88MHz)
are not phase locked.
Problem:
1. System Oscillator degrade
Action:
1. Calibrate the System Oscillator
MasterSlaveLinkFail (MIU 6E_7E)

Loss of connection between MIU Master and MIU Slave.
Problem:
1. Unit internal failure or back-panel failure
Action:
ASIC_1Fail (MIU 6E_7E)

Problem:
Action:

.
Issue:1
ASIC_2Fail (MIU 6E_7E)

Problem:
Action:
BackPanelUnknown (MIU 6E_7E)

Unknown back-panel code.
Problem:
2. Wrong back-panel
Action:
2. Check the back-panel type
MIUSelfTestFail (MIU 6E_7E)

Problem:
Action:
Clock_A_Clock_Bfail (MIU 6E_7E)

Action:

.
Issue:1
HW_Mismatch (MIU 6E_7E)

Correct unit type but not correct hardware version. The MIU slave is not compatible with the MIU
master or the MIU master is not compatible with the matrix type.
Problem:
Action:
hardware version
388MHz_I/O_ModA..EMiss (MIU 6E_7E)

Missing I/F Module A..E for Matrix Interface (I/O 388MHz data)
Problem:
Action:
1. Insert the unit
388MHz_I/O_ModA..EPowerFail (MIU 6E_7E)

I/F Module A..E for Matrix Interface (I/O 388MHz data) power fail.
Problem:
1. Module failure
Action:
ImSwDownloading (MIU 6E_7E)

Download in progress on the Matrix Interface Type 6E/7E
ImSwDownloadingFail (MIU 6E_7E)

Problem:
1. File corrupted
2. Link down
Action:
1. Replace file
2. Repeat download

.
Issue:1
CCU - CENTRAL CONTROL UNIT ALARMS

In the following all the alarms detected at the CCU (Central Control Unit Alarms) level are reported.
IMPORTANT In the event of failure of both Memory Expansion units or Database failure, follow
the Database Failure Trouble Shooting Procedure in the paragraph Trouble
Shooting Procedures.
MissingUnit (CCU)
Problem:
Action:
1. Insert the unit
CCULinkOff (CCU)
Internal ethernet link connection interrupted
Action:
Download_Failed (CCU)
Failure in the download procedure
Problem:
1. Failure during the download procedure
Action:
1. Repeat the download

.
Issue:1
NMS_LinkOff (CCU)
Category: URG MLQ Priority: 41
Link-down with the Network Management System.
Problem:
1. Ethernet connection interrupted
2. Communication and Q Interface Units failure
Action:
1. Check the Network Management System connection
MEMU - MEMORY EXPANSION UNIT ALARMS

In the following all the alarms detected at the MemU (Memory Expansion Unit Alarms) level are
reported.
MissingUnit (MemU)
Problem:
Action:
1. Insert the unit
MemUWriteError (MemU)
Errors detected writing on the memory
Problem:
Action:

.
Issue:1
ChecksumError (MemU)
Checksum error while writing data in the memories
Problem:
Action:
SizeRegisterError (MemU)
Errors accessing memories
Problem:
1. Unit Internal Failure or software transitory error
Action:
SIOU - SERIAL EXPANSION UNIT ALARMS

In the following all the alarms detected at the SIOU (Serial Expansion Unit Alarms) level are
reported.
MissingUnit (SIOU)
Problem:
Action:
1. Insert the unit

.
Issue:1
EthLinkOff (SIOU)
Failure of the internal ethernet
Action:
SIOU_A_SIOU_BFail (SIOU)
The Central Control Unit cannot communicate to both the Serial Input/Output Units
Action:
SIOLINE - SERIAL I/O LINE ALARMS

In the following all the alarms detected at the SIOLine (Serial I/O Line Alarms) level are reported.
SerialLinkOff (SIOLine)
Interruption of the serial lines connecting the Serial Expansion Unit to the peripheral units (Timing
Selector-oscillator Units, Matrix Control Units, Port Control Units)
Action:
COMMU - COMMUNICATION AND Q INTERFACE UNIT ALARMS

In the following all the alarms detected at the Commu (Communication and Q Interface Unit Alarms)
level are reported.
MissingUnit (CommU)
Problem:
Action:
1. Insert the unit

.
Issue:1
EthLinkOff (CommU)
Failure of the internal ethernet
Action:
CommU_A_CommU_BFail (CommU)
The Central Control Unit cannot communicate to both the Communication and Q Interface Units
Action:
No Adjacencies (CommU)
The Communication and Q Interface Units does not detect any adjacencies (layer 3) on the ethernet
network.
Problem:
1. Ethernet disconnected.
2. The remote OSI devices do not communicate (router, NM, etc.).
3. Wrong OSI configuration.
Action:
1. Check the ethernet cable.
2. Check the remote OSI devices.
3. Verify the OSI configuration.

.
Issue:1
TSU - TIMING SELECTOR OSCILLATOR UNIT ALARMS

In the following all the alarms detected at the TSU (Timing Selector oscillator Unit Alarms) level are
reported.
MissingUnit (TSU)
Category: NURG_INT_SYNC Priority:40
Unit equipped but not fitted into the subrack
Problem:
Action:
1. Insert the unit
ExtSrc_1Fail (TSU)
Category: NURG_EXT_SYNC Priority:45
Loss of signal on External Source 1 (kHz signal)
Problem:
1. Signal 1 absence
Action:
1. Using a frequency counter, verify the presence of 2048kHz external synchronization signal 1.
If the signal is present, replace the Timing Selector-oscillator Unit
ExtSrc_2Fail (TSU)
Loss of signal on External Source 2 (kHz signal)
Problem:
1. Signal on External Source 2 (kHz signal) absence
Action:
1. Using a frequency counter, verify the presence of 2048kHz external synchronization signal 2.If
the signal is present, replace the Timing Selector-oscillator Unit

.
Issue:1
SystemOscFail (TSU)
Internal failure of the main oscillator (SYSTEM)
Problem:
Action:
ExtOutOscFail (TSU)
Internal failure of the secondary oscillator (EXT OUT)
Problem:
Action:
SystemOscDEG (TSU)
The main oscillator is not properly working
Action:
1. Force to free running both Timing Selector-oscillator Unit. Using a frequency counter with
accuracy equal or greater than 0.1 ppm check the free running frequency value of both Timing
Selector-oscillator Units.
Configure the working mode of Timing Selector-oscillator Unit in normal revertive and
check, by using the front panel measuring point, the value of 38.88Mhz internal clock.
If the value of the 38.88MHz is 10ppm for G.813 and G.812Local and 1 ppm for
G.812Transit with respect to free running frequency.
Replace Timing Selector-oscillator Unit or delete from the system priority table the
highest synchronising source

.
Issue:1
PwrFail (TSU)
Problem:
Action:
FuseFail (TSU)
Fuse blown
Problem:
Action:
TDULinkFail (TSU)
Failure of the link between Timing Selector-oscillator Unit and both Timing Distributor Units
Action:
TSU_A_TSU_BFail (TSU)
Failure of both Timing Selector-oscillator Unit (A and B)
Problem:
1. Unit Internal Failure or Serial Expansion Unit Internal Failure
Action:

.
Issue:1
UnitFail (TSU)
Failure of both Serial Expansion Units (A and B)
Action:
ExtOutSqlchDisabled (TSU)
Indication of External Output Squelch disabled
Problem:
1. With this message the system is notifying the user about the disabling of the external output
squelch
ExtSrc1OOF (TSU)
Out of frequency of the External Synchronization Source 1 detected by both TSU
Problem:
1. Both TSU are unable to lock to External Source 1.
Action:
1. Check the EXT1 sync source.
ExtSrc2OOF (TSU)
Out of frequency of the External Synchronization Source 2 detected by both TSU
Problem:
1. Both TSU are unable to lock to External Source 2.
Action:
1. Check the EXT2 sync source.
Ext1/2 AIS (TSU)

Category: NURG_EXT_SYNC Priority: 48
AIS detected on External Input 1/2
Problem:
1. Alarm on External Input 1/2
Action:
1. Check the EXT1/2 sync source

.
Issue:1
Ext1/2 LOS (TSU)

Category: NURG_EXT_SYNC Priority: 48
Loss Of Signal detected on External Input 1/2
Problem:
1. Signal lost on External Input 1/2
Action:
1. Check the EXT1/2 sync source
TDU - TIMING DISTRIBUTOR UNIT ALARMS

In the following all the alarms detected at the TDU(Timing Distributor Unit Alarms) level are
reported.
MissingUnit (TDU)
Unit equipped but not fitted into the subrack
Problem:
Action:
1. Insert the unit
LocalTSUMissing (TDU)
Local Timing Selector-oscillator Unit (A for TDU A, B for TDU B) missing
Action:
RemoteTSUMissing (TDU)
Remote Timing Selector-oscillator Unit (A for TDU B, B for TDU A) missing
Action:

.
Issue:1
OutClockFail (TDU)
Unit is unable to distribute the clock
Problem:
Action:
OutSyncFail (TDU)
Unit is unable to distribute the supermultiframe sync signal
Problem:
Action:
CTPSU - CONTROL AND TIMING EQPT. POWER SUPPLY ALARMS

In the following all the alarms detected at the CTPSU(Control Timing Eqpt. Power Supply Alarms)
level are reported.
MissingUnit (CTPSU)
Problem:
Action:
1. Insert the unit

.
Issue:1
CTPSUFail (CTPSU)
Failure of Power Supply Unit of the Control Subrack
Problem:
Action:
SYNCSRC - TIMING SELECTOR-OSCILLATOR UNIT SYNCH SOURCES

ALARMS
In the following all the alarms detected at the SyncSrc (Timing Selector-oscillator Unit Synch
Sources Alarms) level are reported.
SyncSourceFail (SyncSrc)
Loss of all the sync sources selected in the priority table
Problem:
1. Equipment working in Holdover mode
Action:
1. Check the configuration and the alarms of the sync sources
TSU_OOF (SyncSrc)
Out of frequency of the Subrack Synchronization Source
Problem:
1. Both TSU are unable to lock to the Subrack Synchronization Source
Action:
1. Check the Subrack Synchronization Source.

.
Issue:1
PARU - PARALLEL INTERFACE UNIT ALARMS

In the following all the alarms detected at the TDU (Timing Distributor Unit Alarms) level are
reported.
MissingUnit (ParU)
Problem:
Action:
1. Insert the unit
AND(PortSubPSU)Fail (ParU)
Failure of both Power Supply Units of the Port Equipment Subrack
Problem:
Action:
AND(PortSubBatt)Fail (ParU)
Category: URG_EXT_AND(PSU) Priority:40
Both the power cables from battery are missing
Problem:
Action:
OR(CT_A_PSU)Fail (ParU)
Failure of one Power Supply Unit of the Control and Timing Equipment A
Problem:
Action:

.
Issue:1
OR(CT_B_PSU)Fail (ParU)
Failure of one Power Supply Unit of the Control and Timing Equipment B
Problem:
Action:
AND(CT_B_PSU)Fail (ParU)
Failure of both Power Supply Units of the Control and Timing Equipment B
Problem:
Action:
OR(CT_A_Batt)Fail (ParU)
Failure of one battery voltages in the Control and Timing Equipment A
Problem:
Action:
SPI_STM4 - STM-4 SYNCHRONOUS PHYSICAL INTERFACE ALARMS

In the following all the alarms detected at the STM-4 SPI (Signal Physical Interface) level are
reported.
DescramblerFail (SPI_STM4)
Problem:
Action:
ScramblerFail (SPI_STM4)

.
Issue:1
Problem:
Action:
LaserFail (SPI_STM4)
OPTICAL UNIT ONLY Failure of the laser. The Tx power is 3dB lower or greater than the nominal
value
Problem:
Action:
LaserDegrade (SPI_STM4)
OPTICAL UNIT ONLY The bias voltage of the laser is 50% greater than the nominal value
Problem:
Action:
LOS (SPI_STM4)
Loss of incoming STM-4 line signal.
Problem:
Action:

.
Issue:1
LaserAtlX50 (SPI_STM4)
Laser temperature out of range.
Problem:
Action:
LaserTxPowThrHigh (SPI_STM4)
Laser TX power high threshold crossed.
Problem:
Action:
LaserTxPowThrLow (SPI_STM4)
Laser TX Power Low Threshold crossed.
Problem:
Action:
LaserHighTemp (SPI_STM4)
Note This alarm is managed by 2xSTM-1 Unit only.
Problem:
Action:

.
Issue:1
TimingProblems (SPI_STM4)
Internal synchronization failure.
Problem:
Action:
SPI_NXSTM1 - NXSTM-1 SYNCHRONOUS PHYSICAL INTERFACE

ALARMS
In the following all the alarms detected at the NxSTM-1 SPI (Signal Physical Interface) level are
reported.
DescramblerFail (SPI_NxSTM1)
Problem:
Action:
ScramblerFail (SPI_NxSTM1)
Problem:
Action:

.
Issue:1
LaserFail (SPI_NxSTM1)
value
Problem:
Action:
LaserDegrade (SPI_NxSTM1)
Problem:
Action:
LOS (SPI_NxSTM1)
Problem:
Action:

.
Issue:1
TxFail (SPI_NxSTM1)
Failure of the laser transmission section.
Problem:
Action:
LaserAtlX50 (SPI_NxSTM1)
Available for future use.
LaserTxPowThrHigh (SPI_NxSTM1)
Problem:
Action:
LaserTxPowThrLow (SPI_NxSTM1)
Problem:
Action:

.
Issue:1
LaserHighTemp (SPI_NxSTM1)
Problem:
Action:
LineCardError (SPI_NxSTM1)
Line clock errors. This alarm is supported by 2xSTM-1 Unit only.
Note Not yet managed.
TimingProblem (SPI_NxSTM1)
Problem:
Action:
MxACKFail (SPI_NxSTM1)
Loss of clock from Matrix Interface Unit A
Problem:
Action:

.
Issue:1
MxBCKBFail (SPI_NxSTM1)
Loss of clock from Matrix Interface Unit B
Problem:
Action:
OHBusFail (SPI_NxSTM1)
Overhead bus failed.
Problem:
Action:
SPI_STM16 - STM-16 SYNCHRONOUS PHYSICAL INTERFACE ALARMS

In the following all the alarms detected at the STM-16 SPI (Signal Physical Interface) level are
reported.
DescramblerFail (SPI_STM16)
Category: URG_INT_2Gb Priority: 62
Problem:
Action:

.
Issue:1
ScramblerFail (SPI_STM16)
Problem:
Action:
LaserFail (SPI_STM16)
value
Problem:
Action:
LaserDegrade (SPI_STM16)
Problem:
Action:
LOS (SPI_STM16)
Category: URG_EXT_2Gb Priority: 61
Problem:
Action:

.
Issue:1
TxFail (SPI_STM16)
Failure of the laser transmission section.
Problem:
Action:
LaserAtlX50 (SPI_STM16)
Problem:
Action:
LaserTxPowThrHigh (SPI_STM16)
Problem:
Action:
LaserTxPowThrLow (SPI_STM16)
Problem:
Action:

.
Issue:1
LaserHighTemp (SPI_STM16)
Problem:
Action:
TimingProblems (SPI_STM16)
Problem:
Action:
WaveLenghtDrift (SPI_STM16)
The wavelenght set is out of range.
Note This alarm is only for the STM-16 coloured card.
Problem:
Action:

.
Issue:1
RS_STM4 - STM-4 REGENERATOR SECTION ALARMS

In the following all the alarms detected at the STM-4 RS (Regenerator Section Alarms) level are
reported.
LOF (RS_STM4)
Problem:
Action:
RS-TIM (RS_STM4)
Problem:
Action:
DCCrLAPDDisconnected (RS_STM4)
Problem:
Action:

.
Issue:1
RS_NXSTM1 - NXSTM-1 REGENERATOR SECTION ALARMS

In the following all the alarms detected at the NxSTM-1 RS (Regenerator Section Alarms) level are
reported.
LOF (RS_NxSTM1)
Problem:
Action:
RS-TIM (RS_NxSTM1)
Problem:
Action:
DCCrLAPDDisconnected (RS_NxSTM1)
Problem:
Action:
RS-UAT_Eve (RS_NxSTM1)
Category: No Category Priority: 128
RS UAT Event.

.
Issue:1
RS_STM16 - STM-16 REGENERATOR SECTION ALARMS

In the following all the alarms detected at the STM-16 RS (Regenerator Section Alarms) level are
reported.
LOF (RS_STM16)
Problem:
Action:
RS-TIM (RS_STM16)
Problem:
Action:
DCCrLAPDDisconnected (RS_STM16)
Category: IND_2Gb Priority: 70
Problem:
Action:

.
Issue:1
MS_STM4 - STM-4 MULTIPLEX SECTION ALARMS

In the following all the alarms detected at the STM-4 MS (Multiplex Section Alarms) level are
reported.
MS-AIS (MS_STM4) [LC]

Problem:
Action:
MS-RDI (MS_STM4) [LC]

MS-AIS. An incoming MS-RDI is detected by the MS Termination function when the pattern 110 is
Problem:
LOS
LOF
MS-AIS
MS-EXC
detected on the receive side of the far-end multiplexer
Action:
detected alarm
MS-EXC (MS_STM4)
Problem:

.
Issue:1
Action:
MS-DEG (MS_STM4)
An Signal Degrade defect is detected when the equivalent Bit Error Rate (BER) exceeds a preset
bytes B2
Problem:
Action:
DCCmLAPDDisconnected (MS_STM4)
Problem:
Action:

.
Issue:1
MS_NXSTM1 - NXSTM-1 MULTIPLEX SECTION ALARMS

In the following all the alarms detected at the MS (Multiplex Section Alarms) level are reported.
MS-AIS (MS_NxSTM1) [LC]

Problem:
Action:
MS-RDI (MS_NxSTM1) [LC]

Problem:
LOS
LOF
MS-AIS
MS-EXC
Action:
detected alarm
MS-EXC (MS_NxSTM1)
Problem:

.
Issue:1
Action:
MS-DEG (MS_NxSTM1)
bytes B2
Problem:
Action:
DCCmLAPDDisconnected (MS_NxSTM1)
Problem:
Action:
MS-UAT_Eve (MS_NxSTM1)
Category: No Category Priority: 128
MS UAT Event.
S1-Change (MS_NxSTM1)
Category: --- Priority: 50
S1 byte (Synchronization Status Message) change event.

.
Issue:1
MS_STM16 - STM-16 MULTIPLEX SECTION ALARMS

In the following all the alarms detected at the STM-16 MS (Multiplex Section Alarms) level are
reported.
MS-AIS (MS_STM16) [LC]

Multiplex Section Alarm Indication Signal received from a remote regenerator equipment MS-AIS
defect is detected by the MS Termination function when the pattern 111 is observed in bits 6, 7
and 8 of the K2 byte (before scrambling) in at least three consecutive frames
Problem:
Action:
MS-RDI (MS_STM16) [LC]

Problem:
LOS
LOF
MS-AIS
MS-EXC
Action:
detected alarm
MS-EXC (MS_STM16)
Problem:

.
Issue:1
Action:
MS-DEG (MS_STM16)
Category: NURG_EXT_2Gb Priority: 82
bytes B2
Problem:
Action:
DCCmLAPDDisconnected (MS_STM16)
Problem:
Action:

.
Issue:1
NXSTM1_140 - 140MBIT/S PDH INTERFACE ALARMS (4X140-155MBIT/S

UNIT)
In the following all the alarms detected at the 140Mbit/s PDH Interface level are reported (4x140-
155Mbit/s unit).
LOF (NxSTM1_140)
Problem:
Action:
LOS (NxSTM1_140)
Loss of incoming tributary signal.
Problem:
Action:
AIS (NxSTM1_140) [LC]

Problem:
Action:

.
Issue:1
EXC (NxSTM1_140)
Problem:
Action:
DEG (NxSTM1_140)
Problem:
Action:
ATL (NxSTM1_140)
ATL is a Remote Defect Indication used to return an indication to the transmit end that the received
end has received an invalid signal.
Problem:
1. Fault on the far end equipment.
Action:
main alarm

.
Issue:1
PRBS-ERR (NxSTM1_140)
Not yet managed.
DS2 - ALARMS OF 6MBIT/S CHANNELS OF A

T-MUX UNIT
In the following all the alarms detected at the 6Mbit/s PDH Channels level (DS2) are reported.
AIS (DS2)
Problem:
Action:
LOF (DS2)
Problem:
Action:
RAI (DS2)
Remote Alarm Indication received from the 6Mbit/s PDH equipment, which is detecting errors on the
received signal
Problem:
Action:

.
Issue:1
DS3 - 45MBIT/S PDH INTERFACE ALARMS

In the following all the alarms detected at the 45Mbit/s PDH Interface level (DS3) are reported.
LOS (DS3)
Loss of incoming tributary signal.
Problem:
1. Consequence of connected PDH equipment failure or line interruption
Action:
LOF (DS3)
Loss of the 45Mbit/s frame alignment word.
Problem:
Action:
AIS (DS3)
Alarm Indication Signal received from the remote 45Mbit/s PDH equipment.
Problem:
Action:

.
Issue:1
RAI (DS3)
Remote Alarm Indication (called also Yellow Alarm) received from the PDH connected equipment,
which is detecting errors on the received 45Mbit/s signal
Problem:
1. Consequence of alarm
NE-EQP-FAIL-SA
LOS
LOF
AIS
detected on the far-end multiplexer.
Action:
detected alarm
INPUT-DEG (DS3)
Problem:
Action:
INPUT-EXC (DS3)
Problem:

.
Issue:1
Action:
IDLE-SIGNAL (DS3)
DS3 Idle Signal is a particular condition on that the DS3 channel of the 45Mbit/s T-Mux Unit is not
cross-connected but its frame configuration is correct. When a DS3 Idle Signal is received, an AIS
signal is transmitted downstream.
Problem:
1. DS3 Idle Signal received.
Action:
AIC-MISM (DS3)
Application Identification Channel Mismatch (in the DS3 C-Bit mode the bits C11).
Problem:
1. Transmitter on the far-end equipment configured in different mode
Action:
RxClockFail (DS3)
Loss of clock signal extracted from the received stream.
Problem:
1. Consequence of alarms AIS, LOS
2. Fault on the far-end transmitter
Action:

.
Issue:1
TxClockFail (DS3)
The transmitted line clock signal is missing.
Problem:
Action:
NE-EQP-FAIL-SA (DS3)
Category: NURG_INT_34-45Mb Priority: 62
Near-End Equipment Failure - Service Affecting.
Problem:
1. Both matrices failed (clock and diagnostic signal failed).
2. Tx DS3 clock failed.
3. Rx DS3 clock failed.
4. Power failure.
Loss of signal on transmission side.
Action:
1. Check the alarm on the Matrix Interface Unit and follow the relevant procedure
TxClockFail (DS3)
RxClockFail (DS3)
NE-EQP-FAIL-NSA (DS3)
Near-End Equipment Failure - Not Service Affecting.
Problem:
1. Matrix A or B failed (clock or diagnostic signal failed).
2. CCU link down.
Action:
1. Check the alarm on the Matrix Interface Unit and follow the relevant procedure
Control Architecture Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 - DXC 4/1 512x512)

.
Issue:1
NE-LOS (DS3)
Near End Loss of Signal failure event. NE-LOS is declared when the LOS defect persists for 2.5s
(+/- 0.5s) - LOS failure.
See Also:
LOS (DS3)
NE-LOF (DS3)
Near End Loss of Frame failure event. NE-LOF is declared when the LOF defect persists for 2.5s
(+/- 0.5s) - LOF failure.
See Also:
LOF (DS3)
NE-HBER (DS3)
Near End Excessive error failure event. NE-HBER is declared when the INPUT-EXC defect persists
for 2.5s (+/- 0.5s) - EXC failure.
See Also:
INPUT-EXC (DS3)
NE-AIS (DS3)
Near End Alarm Indication Signal event. NE-AIS is declared when the AIS defect persists for 2.5s
(+/- 0.5s) - AIS failure.
See Also:
AIS (DS3)
NE-IDLE (DS3)
Near End Idle failure event. NE-IDLE is declared when the IDLE-SIGNAL defect persists for 2.5s
(+/- 0.5s) - IDLE-SIGNAL failure.
See Also:
IDLE-SIGNAL (DS3)
RE-EQP-FAIL-SA (DS3)
Remote End Equipment Failure (Service Affecting) indication event.
Problem:
1. Consequence of alarm NE-EQP-FAIL-SA detected on the far-end multiplexer.

.
Issue:1
Action:
detected alarm
RE-EQP-FAIL-NSA (DS3)
Remote-End Equipment Failure (Not Service Affecting) indication event.
Problem:
1. Consequence of alarm NE-EQP-FAIL-NSA detected on the far-end multiplexer.
Action:
detected alarm
RE-LOS (DS3)
Remote-End Loss of Signal event.
Problem:
1. Consequence of alarm LOS detected on the receive side of the far-end multiplexer.
Action:
detected alarm
RE-LOF (DS3)
Remote-End Loss of Frame event.
Problem:
1. Consequence of alarm LOF detected on the receive side of the far-end multiplexer.
Action:
detected alarm
RE-AIS (DS3)
Remote-End Alarm Indication Signal event.
Problem:
1. Consequence of alarm AIS detected on the receive side of the far-end multiplexer.
Action:
detected alarm

.
Issue:1
RE-IDLE (DS3)
Remote-End Idle condition event.
Problem:
1. Consequence of alarm IDLE-SIGNAL detected on the receive side of the far-end multiplexer.
Action:
detected alarm
63X2MBPDHCH - 1.5 AND 2MBIT/S PDH INTERFACE ALARMS

TxBufferContention (63x2MbPDHCh)
A buffer memory overflow/underflow error detected when it is not possible to insert the incoming
2Mbit/s signal into the C-12
Problem:
1. Incoming 2Mbit/s signal out of bit rate tolerance ( 50 ppm) or jitter value to high: probable
failure on the PDH connected equipment
Action:
RxFailure (63x2MbPDHCh)
Problem:
Action:

.
Issue:1

PDH-LOS (63x2MbPDHCh)
Problem:
Action:
PDH-AIS (63x2MbPDHCh) [LC]

Problem:
Action:
PDH-EXC (63x2MbPDHCh)
Problem:
Action:

.
Issue:1
PDH-DEG (63x2MbPDHCh)
Problem:
Action:
PDH-LOF (63x2MbPDHCh)
Problem:
Action:
InputCRC4Mismatch (63x2MbPDHCh)
Wrong CRC4 bit sequence
Problem:
1. Wrong configuration of the connected PDH equipment. It is probably preset for not using the
CRC4 function
Action:

.
Issue:1
FAW-EXC (63x2MbPDHCh) [LC]

Frame Alignment Word excessive bit error rate. An Excessive error defect is detected when the
equivalent Bit Error Rate (BER) exceeds a threshold of 10-3 on the received Tributary signal
(framed).
Problem:
Action:
PDH-RAI (63x2MbPDHCh) [LC]

Problem:
Action:
TxFail (63x2MbPDHCh) [LC]

Category: Priority:
Problem:
Action:
FAW-DEG (63x2MbPDHCh) [LC]

Frame Alignment Word Degrade. A Signal Degrade defect is detected when the equivalent Bit Error
Rate (BER) on the Tributary Input (framed signal) exceeds a preset threshold in the range of 10-5 to
10-9 (the threshold can be configured via software)

.
Issue:1
Problem:
Action:
OutgoingPDH-LOF (63x2MbPDHCh) [LC]

Loss of frame alignment on the tributary signal coming from the matrix.
Problem:
1. Consequent action of remote PDH equipment failure or problems along the line
Action:
OutgoingCRC4Mismatch (63x2MbPDHCh) [LC]

Wrong CRC4 bit sequence received on the matrix side.
Problem:
1. Wrong configuration of the remote PDH equipment. It is probably preset for not using the
CRC4 function
Action:

.
Issue:1
OutgoingPDH-AIS (63x2MbPDHCh) [LC]

Alarm Indication Signal received on the matrix side.
Problem:
1. Fault on the remote PDH equipment
Action:
OutgoingCRC4EXC (63x2MbPDHCh) [LC]

Excessive error defect detected on the CRC4 framed signal coming from the matrix.
Problem:
1. Consequent action of remote PDH equipment failure or line attenuation
Action:
OutgoingCRC4DEG (63x2MbPDHCh) [LC]

Signal Degrade defect detected on the CRC4 framed signal coming from the matrix.
Problem:
1. Consequent action of remote PDH equipment failure or line attenuation
Action:

.
Issue:1
4X34MBPDHCH - 34MBIT/S T-MUX PDH INTERFACE ALARMS

PDH-LOS (4x34MbPDHCh)
Problem:
Action:
PDH-AIS (4x34MbPDHCh) [LC]

Problem:
Action:
PDH-EXC (4x34MbPDHCh)
Problem:
Action:

.
Issue:1
PDH-DEG (4x34MbPDHCh)
Problem:
Action:
PDH-LOF (4x34MbPDHCh)
Problem:
Action:
TxFail (4x34MbPDHCh) [LC]

Problem:
Action:

.
Issue:1
PDH-RAI (4x34MbPDHCh) [LC]
Category: IND _34-45Mb Priority: 83

Problem:
Action:
PDH-INClockFail (4x34MbPDHCh) [LC]

Problem:
Action:
3X34_45MB_VC3 - LOW ORDER VC ALARMS (3X34_45MB_VC3)

LOP (3x34_45Mb_VC3)
N 10)
Problem:
1. Wrong or damaged cabling between matrix and port subrack
2. Trib./Matrix Interface Unit Internal Failure
Action:

.
Issue:1
AIS (3x34_45Mb_VC3) [LC]

port) or by the Lower Order Path Overhead Monitor (LPOM). LP-AIS defect is detected by the HPT
or the HPOM when all 1 in the entire TU including TU pointer are observed (for three or more
frames)
Problem:
Action:
FERF (3x34_45Mb_VC3) [LC]

is observed
Problem:
1. Consequent action of alarm:
LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP
AU-AIS
HP-TIM
HP-PLM
HP-LOM
TU-LOP
LP-PLM
LP-TIM
LP-EXC
Action:

.
Issue:1
main alarm
EBER (3x34_45Mb_VC3)
the corresponding value present in bit 1 and 2 of byte V5
Problem:
Action:
DEG (3x34_45Mb_VC3)
corresponding value present in bit 1 and 2 of byte V5
Problem:
Malfunction on the far-end transmitter
Action:
PLM (3x34_45Mb_VC3)
Mismatch between the received and expected payload label value (bit 5-6-7 of V5)
Problem:
Action:

.
Issue:1
TIM (3x34_45Mb_VC3)
Mismatch between the received and expected low order path trace identifier (byte J2)
Problem:
1. Transmitter on the far-end equipment configured with a different low order path trace identifier
Action:
UNEQ (3x34_45Mb_VC3)
bit 5, 6 and 7 of byte V5
Problem:
Action:
V4-FAIL_A (3x34_45Mb_VC3)
from the Matrix A.
Action:
V4-FAIL_B (3x34_45Mb_VC3)
from the Matrix A.
Action:

.
Issue:1
34 AND 45MBIT/S PDH INTERFACE ALARMS (3X34_45MBPDHCH)

RxBufferContention (3x34_45MbPDHCh)
Problem:
Action:
PDH-LOS (3x34_45MbPDHCh)
Problem:
Action:

.
Issue:1
PDH-AIS (3x34_45MbPDHCh) [LC]

Problem:
Action:
PDH-EXC (3x34_45MbPDHCh)
Problem:
Action:
PDH-DEG (3x34_45MbPDHCh)
Problem:
Action:
PDH-LOF (3x34_45MbPDHCh)

.
Issue:1
Problem:
Action:
PDH-45Mb-LOMF (3x34_45MbPDHCh)
Loss of the VIDEO_CODEC signal multiframe indication
Problem:
Action:
PDH-TxFail (3x34_45MbPDHCh)
Loss of the 34 or 45Mbit/s signal transmitted towards the PDH network
Problem:
Action:

.
Issue:1
PDH-INClockFail (3x34_45MbPDHCh)
Problem:
Action:
45MbYellowSignal (3x34_45MbPDHCh)
Yellow signal indication received on the 45Mbit/s frame
Problem:
Action:
45MbIdleSignal (3x34_45MbPDHCh)
Idle signal indication received on the 45Mbit/s frame
Problem:
Action:

.
Issue:1
VIRTUAL CONCATENATED ALARM

HP-TIM (VC4_4V)
Problem:
Action:
LOM (VC4_4V)
Problem:
1. Consequence of far-end equipment transmitter failure.
Action:
HP-RDI (VC4_4V)
is observed
Problem:
equipment:
SPI-LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP

.
Issue:1
AU-AIS
HP-TIM
HP-PLM
HP-LOM
Action:
main alarm
AU-AIS (VC4_4V)
140Mb/s PDH port) or by the Higher Order Path Overhead Monitor (HPOM). AU-AIS defect is
Problem:
Action:
HP-DEG (VC4_4V)
Action:
HP-EXC (VC4_4V)
An Excessive error defect is detected when the equivalent Bit Error Rate (BER) exceeds the
threshold on the received signal. Errors are calculated by checking the BIP-8 on the received data
and the corresponding value present in byte B3 (see above)
Action:

.
Issue:1
HP-UNEQ (VC4_4V)
pattern in byte C2
Problem:
Action:
TC-ISF (VC4_4V)
Tandem Connection an AU-4 AIS shall be inserted in the appropriate outgoing signal if the AIS on
TC-ISF fault action has been enabled.
Problem:
Action:
TC-UNEQ (VC4_4V)
pattern.
Problem:
Action:

.
Issue:1
TC-DEG (VC4_4V)
Problem:
Action:
TC-EXC (VC4_4V)
"Sink" on the received signal (Tandem Connection monitoring) exceeds the threshold. The detection
criteria are the same for the TC-DEG alarm.
Problem:
Action:

.
Issue:1
HO-V4-FAIL_A (VC4_4V)
from the Matrix A.
Action:
HO-V4-FAIL_B (VC4_4V)
from the Matrix B.
Action:
HO-LOM_VCnV (VC4_4V)
Loss of Multiframe in a VC-4-nV concatenated traffic type. If several H4 values are received from
matrix consecutively not correctly in sequence with any part of the multiframe sequence, then a loss
of multiframe (LOM) event is reported. This alarm is associated to a STM-16 MUX 4/3 card and
Problem:
Action:
HO-SQM_VCnV (VC4_4V)
received from matrix, bits 1-4 in multiframe 14 and 15. The alarm is associated to a STM-16 MUX
4/3 card and concerns the Virtual Concatenations.
Problem:

.
Issue:1
Action:
HO-LOA_VCnV (VC4_4V)
Loss of Alignment: is detected when creating a contiguous concatenation from a virtual one, and the
differential delay between the VC-4 of reference and any other VC-4-v in the same multiframe
exceeds the size of alignment buffer. Note that if the value set for differential delay with manual
method is inadequate but the buffer overflow is recovable with the auto-adaptive method, a HO-LOA
RecVCnV is raised. The alarm is associated to a STM-16 MUX 4/3 card and concerns the Virtual
Concatenations.
Problem:
Action:
HO-LOA_RecVCnV (VC4_4V)
the individual VC-4s to a common multiframe start, but the buffer overflow is recoverable with the
auto-adaptive method. The alarm is associated to a STM-16 MUX 4/3 card and concerns the Virtual
Concatenations.
Problem:
Differantial Delay.
Action:
HO-INC_J1_MismVCnV (VC4_4V)
Problem:
1. Transmitter on the far-end equipment configured with a different path trace identifier.
Action:

.
Issue:1
HO-UneqMtx (VC4_4V)
Problem:
1. Transmitter on the far-end equipment not configured.
Action:
1. Check the far-end configuration.
HP-TIM (VC4_16V)
Mismatch between the received and the expected path trace identifier byte (J1).
Problem:
Action:
LOM (VC4_16V)
Problem:
Action:

.
Issue:1
HP-RDI (VC4_16V)
is observed
Problem:
equipment:
SPI-LOS
LOF
RS-TIM
MS-AIS
MS-EXC
AU-LOP
AU-AIS
HP-TIM
HP-PLM
HP-LOM
Action:
main alarm
AU-AIS (VC4_16V)
140Mb/s PDH port) or by the Higher Order Path Overhead Monitor (HPOM). HP-AIS defect is
Problem:
Action:

.
Issue:1
HP-DEG (VC4_16V)
Action:
HP-EXC (VC4_16V)
An Excessive error defect is detected when the equivalent Bit Error Rate (BER) exceeds the
threshold on the received signal. Errors are calculated by checking the BIP-8 on the received data
and the corresponding value present in byte B3 (see above)
Action:
HP-UNEQ (VC4_16V)
pattern in byte C2
Problem:
Action:

.
Issue:1
TC-ISF (VC4_16V)
Tandem Connection an AU-4 AIS shall be inserted in the appropriate outgoing signal if the AIS on
TC-ISF fault action has been enaled.
Problem:
Action:
TC-UNEQ (VC4_16V)
pattern.
Problem:
Action:
TC-DEG (VC4_16V)

.
Issue:1
Problem:
Action:
TC-EXC (VC4_16V)
"Sink" on the received signal (Tandem Connection monitoring) exceeds the threshold. The detection
criteria are the same for the TC-DEG alarm.
Problem:
Action:
HO-V4-FAIL_A (VC4_16V)
from the Matrix A.
Action:

.
Issue:1
HO-V4-FAIL_B (VC4_16V)
from the Matrix B.
Action:
HO-LOM_VCnV (VC4_16V)
Loss of Multiframe in a VC-4-nV concatenated traffic type. If several H4 values are received
consecutively not correctly in sequence with any part of the multiframe sequence, then a loss of
multiframe (LOM) event is reported. This alarm is associated to a STM-16 MUX 4/3 card and
Problem:
Action:
HO-SQM_VCnV (VC4_16V)
bits 1-4 in multiframe 14 and 15. The alarm is associated to a STM-16 MUX 4/3 card and concerns
the Virtual Concatenations.
Problem:
Action:

.
Issue:1
HO-LOA_VCnV (VC4_16V)
Loss of Alignment: is detected when creating a contiguous concatenation from a virtual one, and the
differential delay between the VC-4 of reference and any other VC-4-v in the same multiframe
exceeds the size of alignment buffer. Note that if the value set for differential delay with manual
method is inadequate but the buffer overflow is recovable with the auto-adaptive method, a HO-LOA
RecVCnV is raised. The alarm is associated to a STM-16 MUX 4/3 card and concerns the Virtual
Concatenations.
Problem:
Action:
HO-LOA_RecVCnV (VC4_16V)
the individual VC-4s to a common multiframe start, but the buffer overflow is recoverable with the
auto-adaptive method. The alarm is associated to a STM-16 MUX 4/3 card and concerns the Virtual
Concatenations.
Problem:
Differantial Delay.
Action:
HO-INC_J1_MismVCnV (VC4_16V)
Problem:
Action:

.
Issue:1
HO-UneqMtx (VC4_16V)
Problem:
Action:
CORRESPONDENCE BETWEEN ALARM SOURCE TYPE AND CARD

TYPE
The following table shown the correspondence between the network alarm source and the unit type.
The different columns identifies:
Alarm Source
The alarm source relevant to the network alarm detected on the equipment.
Source Number
The alarm source identifier. This number identifies the alarm source monitored on the unit. For
example, consider the AU-4 alarm source; in a STM-4 Unit, 4 AU-4 alarm source are present, in a
STM-16 Unit, 16
AU-4 alarm source are present.
Unit Type
The type of unit.
Port Id
The port identifier. This number identifies the physical port present on the unit.
ALARM SOURCE SOURCE UNIT TYPE PORT ID
NUMBER
SPI 1 STM-1 1
RS 1 STM-1 1
MS 1 STM-1 1
SPI_STM4 1 STM-4 1
RS_STM4 1 STM-4 1
MS_STM4 1 STM-4 1
SPI_STM16 1 STM-16 1
RS_STM16 1 STM-16 1
MS_STM16 1 STM-16 1
AU 4 1 STM-1 1

.
Issue:1
AU 4 1..4 STM-4 1
AU 4 1..16 STM-16 1
AU 4 1 140Mb 1
VC 4 1 STM-1 1
VC 4 1..4 STM-4 1
VC 4 1..16 STM-16 1
VC 4 1 140Mb 1
AU 3 1..3 3x34Mb 1..3 (*)
VC 3 1..3 3x34Mb 1..3 (*)
TU 3 1..3/12 STM-1/4 1
TU 2 1..21/84 STM-1/4 1
TU 12 1..63/252 STM-1/4 1
VC 12 1..16 16x2Mb 1..16 (*)
VC 12 1..63 63x2Mb 1..63 (*)
VC 12 1..63 4x34 T-MUX 1..4
VC 12 1..63 140 T-MUX 1
VC 12 1..28 45 T-MUX 1
Port 2MB 1..16 16x2 1..16 (*)
Port 2MB (63x2) 1..63 63x2 1..63 (*)
Port 2MB (DS1) 1..28 45 T-MUX 1
Port 34MB 1..3 34MB 1..3 (*)
Port 34MB 1..4 4x34 T-MUX 1..4 (*)
Port 140MB 1 140MB 1
Port 140MB 1 140 T-MUX 1
34MB Subch.PDH 1..4 140 T-MUX 1
8MB Subch.PDH 1..4 4x34 T-MUX 1..4
2MB Subch.PDH 1..16 4x34 T-MUX 1..4
VIDEOCODEC 1..4 VIDEO CODEC 1..4
VC 2-5C 1..4 VIDEO CODEC 1..4
8MB Subch.PDH 1..4 3x34Mb 1

.
Issue:1

DS2 1..7 45 T-MUX 1
DS3 1 45 T-MUX 1
SPI_NxSTM1 1..4 4xSTM-1 1..4 (*)
RS_NxSTM1 1..4 4xSTM-1 1..4 (*)
MS_NxSTM1 1..4 4xSTM-1 1..4 (*)
AU 4 1..4 4xSTM-1 1..4 (*)
VC 4 1..4 4xSTM-1 1..4 (*)
TU 3 1..12 4xSTM-1 (VC-12) 1..4
TU 2 1..84 4xSTM-1 (VC-12) 1..4
TU 12 1..252 4xSTM-1 (VC-12) 1..4
140_NxSTM1 1..4 4xSTM-1/140 1..4 (*)
SPI_NxSTM1 1..2 2xSTM-1 1..2 (*)
RS_NxSTM1 1..2 2xSTM-1 1..2 (*)
MS_NxSTM1 1..2 2xSTM-1 1..2 (*)
AU 4 1..2 2xSTM-1 1..2 (*)
VC 4 1..2 2xSTM-1 1..2 (*)
TU 3 1..6 2xSTM-1 1..2
TU 2 1..42 2xSTM-1 1..2
TU 12 1..126 2xSTM-1 1..2
Note(*) PORT ID is identified by SOURCE NUMBER.
Note For the TU-12, TU-2, TU-3 ALARM SOURCES the PORT ID is identified by SOURCE
NUMBER divided the number of TU-x in VC-4.
TROUBLE SHOOTING BLOCK DIAGRAMS

These diagrams should help the user to find the relationship between a unit detecting an internal
alarm and another part of the system (other units and cables).
The following block diagrams are included:
n Data Interconnection Diagram, this is a simplified representation of the path followed by
the internal data streams between Port Equipment and Matrix;
n Synchronization Distribution Diagram, this is a simplified representation of the path
followed by the internal synchronization signals from the Control and Timing Equipment to
the Matrix and Port Equipment;

.
Issue:1
n Control Architecture Diagram, this is a simplified representation of the path followed by

the internal control signals from the Control and Timing Equipment to the Matrix and Port
Equipment.
Once the operator knows which part of the system is involved he will be able to solve the problem
using the procedures given in the Alarm List column Action contained in the previous tables.

.
Issue:1

From Port to Matrices (DXC 4/1 128x128)

.
Issue:1

.
Issue:1

.
Issue:1

.
Issue:1
From Matrices to Ports (DXC 4/1 128x128)

.
Issue:1

.
Issue:1

.
Issue:1

.
Issue:1

.
Issue:1

.
Issue:1
Synchronization Distribution Diagram (DXC 4/1 128x128 - DXC 4/1

256x256 - DXC 4/1 512x512)

.
Issue:1

.
Issue:1

.
Issue:1
Control Architecture Diagram (DXC 4/1 128x128 - DXC 4/1 256x256 -

DXC 4/1 512x512)

.
Issue:1

.
Issue:1

.
Issue:1
TROUBLE SHOOTING PROCEDURES

A collection of trouble shooting procedures are included here in. These procedures cover the most
common problems:
n Card Internal Fault Trouble Shooting Procedure;
n Bit Error Rate Trouble Shooting Procedure.
References to these procedures are made in the paragraph Alarm List.

When a card internal fault condition is detected proceed as follows:
1. Reset the microprocessor of the unit using the Control Application: select Equipment
Configuration -> Card Commissioning menu and choose the subrack and the relevant unit.
Then, select Action -> Reset
This is always hitless (no traffic lost).
If the alarm condition remains active:
2. Perform a card hardware reset (pull out and re-insert the faulty unit). If the alarm condition
remains active:
3. Replace the unit
To minimize traffic disturbance periods during extraction/insertion of tributary and switch units it is
suggested, when a protection path is available, to switch traffic to the protection if it has not
automatically activated (manual switch on the protection side).
Note that operations on the Controller and Timing Subrack Units will never lead to a traffic
disturbance period since these units are duplicated.
Interruption periods are:
n trib. units, unit protected. Interruption time: less than 4 sec.
n STM-1 units, MSP1+1 protected. Interruption time: less than 50ms.
n 140Mbit/s units, 1+1 line protected. Interruption time: less than 50ms.
n Other units, unprotected. Interruption time: time to replace the unit (~10 sec)

When a bit error rate 10-3 (EXC) or from 10-5 to 10-9 (Signal Degrade - threshold configurable via
software) is detected proceed as follows:
Bit Error Rate on the STM-1 optical signal
IMPORTANT The following procedure will take the line traffic out of service.
Therefore proceed only if it is absolutely necessary, or if the traffic is protected
1. Use the Control Application to make a local loopback using the menu Equipment
Configuration -> Loopback Test
If the alarm stays ON:

1. Follow the:

.
Issue:1
If the alarm goes OFF:

1. Remove the local loopback and create a remote loopback on the far-end multiplexer

It means that there is a failure on the far-end equipment.

1. Disconnect the Tx and Rx optical fibre cables.
2. Using an optical test cable connect the Tx side of the optical unit with the input of an
adjustable optical attenuator. Connect an optical power meter to the output of the attenuator.
3. Press the front panel push-button for the test laser restart
Refer To:
Equipment Manual, Section 3 Setting Up chapter Front Panel Devices
4. Adjust the attenuator to measure an optical power of -34dbm (minimum sensitivity) on the
power meter. Disconnect the power meter.
5. Using an optical cable connect the output of the attenuator to the Rx side of the Optical/Mux
Unit.
6. Press the front panel push-button for the short laser restart.

1. Follow the:

It means that there is an excessive degradation of the optical fibre or fault on the far-end transmitter:
1. Check, using an optical power meter, the received optical power
Note To measure the received optical power the automatic laser shutdown circuit must be
disabled as indicated in:
Equipment Manual, Section 3 Setting Up chapter Hardware Settings
If the measured value is in the range between 0dBm and -34dBm:

1. Follow the:
If the measured value is below -34dBm:

The problem could be a probable signal attenuation due to poor connector coupling or to the optical
fibre line or failure on the far-end equipment.
If the measured value is above 0dBm:

There is a failure on the far-end transmitter

.
Issue:1
Bit Error Rate on the STM-1 electrical signal

IMPORTANT The following procedure will take the line traffic out of service. Therefore proceed
only if it is absolutely necessary, or if the traffic is protected
1. Use the Control Application to activate a local loopback using the menu Equipment

1. Follow the:

1. Remove the local loopback and set on the far-end multiplexer a remote loopback.

There is a failure on the far-end equipment.

There are problems on the connectors or on the coaxial cable.
Bit error rate on the VC payload
only if it is absolutely necessary, or if the traffic is protected
1. Delete on the far-end equipment (where the path is terminated) the VC connection and create
on the STM-1 Interface an unidirectional connection between TX and RX of the alarmed VC.

There is a failure on the far-end equipment.

Check on the equipment if a protection is available for the faulty unit.
If a protection unit is available:
IMPORTANT The following step will insert transient errors on all the VCs terminated on the
relevant unit. Therefore proceed only if it is absolutely necessary.
1. Use the Control Application to send a manual switch command to the protection unit; the
menu is: Equipment Configuration -> Protection -> Subrack Protection
2. If the alarm goes OFF, follow the:
3. If the alarm stays ON, the problem could be a degradation of the optical power, problems in
connector coupling or failure in transit equipment. In this case check the connections and the
status of the transit equipment.

.
Issue:1
If a protection unit is not available:
only if it is absolutely necessary, or if the traffic is protected.
1. Use the Control Application to make a local loopback using the menu: Equipment
2. If the alarm goes OFF, follow the:
3. If the alarm stays ON, the problem could be a degradation of the optical power, problems in
connector coupling or failure in transit equipment. In this case check the connections and the
status of the transit equipment.
Database Failure Trouble Shooting Procedure (DXC 4/4)

This procedure should be performed only if both Memory Expansion units have a failure or in the
event of DXC database failure.
* Extract all the Serial Expansion units (both Worker and Protection side).
* Extract both the failed Memory Expansion units (MemU).
* Insert one new MemU. If necessary scratch it using the procedure described in:
Equipment Manual, chapter Release Upgrading
* Run the Control Application and put the CCU in OFFLINE state using the menu:
Equipment Configuration -> Online State
* Restore the DXC database; three different procedures are given according to the
availability of the backup database.
If a backup file of the database is available:

Perform a Database restoration by means of backup file following the procedures given in:
System: downloading Sw and DB on C&T subrack
If the Element Manager (EM) database is aligned with the DXC database and if the
EM allows DXC database downloading:
Perform a Database restoration by means of EM. Using the Control Application reconfigure, if
necessary, the Communication parameters of the DXC; then use the EM to download the
Database to the DXC (according to the procedures given in the documentation of the EM).
See Also:
Communication: set global parameters, Communication: configuring DCC,
Communication: enabling
If no backup database is available:

Perform a Manual database restoration reconfiguring the whole DXC equipment using the menus
of the Control Application.
* Insert the second MemU, then insert back all the Serial Expansion units.
* Insert the second MemU and the Serial Expansion units.

.
Issue:1
* Put the CCU in ONLINE state using the menu: Equipment Configuration -> Online
State
Database Failure Trouble Shooting Procedure (DXC 4/1)

This procedure should be performed only if both Memory Expansion units have a failure or in the
event of DXC database failure.
* Extract all the Serial Expansion units (both Worker and Protection side).
* Extract both the failed Memory Expansion units (MemU).
* Insert one new MemU (if necessary scratch it using the procedure described in:
Equipment Manual, chapter Release Upgrading
* Run the Control Application and put the CCU in OFFLINE state using the menu:
Equipment Configuration -> Online State
* Restore the DXC database; three different procedures are given according to the
availability of the backup database.
If a backup file of the database is available:

Perform a Database restoration by means of backup file following the procedures given in:
System: downloading Sw and DB on C&T subrack
If the Element Manager (EM) database is aligned with the DXC database and if the
EM allows DXC database downloading:
Perform a Database restoration by means of EM. Using the Control Application reconfigure, if
necessary, the Communication parameters of the DXC; then use the EM to download the
Database to the DXC (according to the procedures given in the documentation of the EM).
See Also:
Communication: set global parameters, Communication: configuring DCC,
If no backup database is available:

Perform a Manual database restoration reconfiguring the whole DXC equipment using the menus
of the Control Application.
* Insert the second MemU
If the DXC is in Equipment Rel. 6.3 (DXC 4/1 32x32 and DXC 4/1 128x128) or
equivalent Rel. 2.3 (DXC 4/1 256x256) or greater:
* Insert back all the Serial Expansion units.
State

.
Issue:1
If the DXC is in Equipment Rel. lower than 6.3 (DXC 4/1 32x32 and DXC 4/1
128x128) or equivalent Rel. 2.3 (DXC 4/1 256x256):
IMPORTANT The following steps must be followed only if the DXC is in Equipment release
lower than Rel. 6.3 (DXC 4/1 32x32 and DXC 4/1 128x128) or equivalent Rel.
2.3 (DXC 4/1 256x256)
* Extract both Matrix Controller units (MCU A and MCU B), then insert back all the Serial
Expansion units (starting from Worker Side A)
State
* Leaving both MCUs extracted, switch the traffic to the Matrix Equipment B using the
command forced switch to protection in the menu: Equipment Configuration ->
Protection -> Matrix Protection -> Protection Switch
Note The Matrix Equipment B is now providing service, the Matrix Equipment A can be re-
initialized.
* Insert back the MCU A on the Matrix Equipment A. Wait until the MCU unit is re-
initialized by the CCU unit (a few minutes).
* Switch the traffic to the Matrix Equipment A using the command forced switch to worker
in the menu:
Equipment Configuration -> Protection -> Matrix Protection -> Protection Switch
Note The Matrix Equipment A is now providing service, the Matrix Equipment B can be re-
initialized.
* Insert back the MCU B on the Matrix Equipment B. Wait until the MCU unit has been re-
initialized by the CCU unit (few minutes).
* Send a clear command to the protection of the Matrix subsystem using the menu:
Equipment Configuration -> Protection -> Matrix Protection -> Protection Switch
Note The Matrix Equipment A is still providing service, but the tributary units can switch to
the Matrix Equipment B.

.
Issue:1
DATA DICTIONARY & MESSAGES
OPERATIVE STATES
In the Equipment Commissioning windows are displayed information about each object (e.g.:
subracks, units, etc.).
Administr. State
Lock
This state refers to cross-connections. When a connection has been locked, no actions can be
performed on it (e.g.: Delete) until its administrative state is unlocked.
Unlock
This state refers to Matrix Subrack, units, serial lines and cross-connections. The state indicates
the normal operation of the object.
Shutting Down
not yet managed.
Availability State
In-test
not yet managed.
Failed
This state refers to ports, units, subracks, serial links, cross-connections. Indicates that the object
is faulty.
Powered-off
not yet managed.
Off-line
This state refers to units. Indicates that a unit is not yet in-service (e.g.: during the power-on).
Operational State is Disabled.
Off-duty
not yet managed.
Dependency
This state refers to Port Units, Serial Lines. Indicates that the object is not operating due to a
failure in another unit.
Degraded
This state refers to Matrix subrack. The state indicates a minor fault in the matrix. The Operational
State is Enabled.
Not-installed
This state refers to Matrix Subrack, units, ports and serial lines. The state indicates that the object
has been removed. Operational State is Disabled.
Log-full
This state refers to the alarm log. It indicates that the number of alarms stored in the alarm log has
reached the threshold set by the Operator.

.
Issue:1
Unexpected-card-fitted
The state indicates that the unit is fitted in the shelf but not equipped. The state is graphically
represented with a question mark displayed in the slot.
Active Bank
Data Unavailable
This value refers to units. The value indicates that the data relevant to the software are not
available
Bank_1/Bank_2
This value refers to units. The value indicates active memory bank
Boot EPROM Software Details

Data Unavailable
Same as Active Bank
Sxx-xxxx/xx.xx
This value refers to units. The value indicates the version of the software loaded in the boot
EPROM present in the units.
Bank 1 Software Details

Data Unavailable
Same as Active Bank
Sxx-xxxx/xx.xx
This value refers to units. The value indicates the version of the software loaded in the flash
EEPROM bank 1.
Bank 2 Software Details

Data Unavailable
Same as Active Bank
Sxx-xxxx/xx.xx
This value refers to units. The value indicates the version of the software loaded in the flash
EEPROM bank 2.
Unit ID
P1..P10
Port Unit (2Mbit/s, 140Mbit/s, STM-1, etc.).
MI_A
Matrix Interface Unit A
MI_AM
Master Matrix Interface Unit A
MI_AS1..3
Slave Matrix Interface Unit A
MI_B
Matrix Interface Unit B
MI_BM
Master Matrix Interface Unit B

.
Issue:1
MI_BS1..3
Slave Matrix Interface Unit B
PCA
Port Controller Unit A
PCB
Port Controller Unit B
AUX
Auxiliary Unit
ID
Identification Unit
PWA
Power Supply Unit A
PWB
Power Supply Unit B
Matrix Unit ID
1S.1..n
I Stage Unit
2S.1..n
II Stage Unit
3S.1..n
III stage Unit
CNTR
Matrix Controller Unit
DST
Matrix Timing Unit
PWA..D
Power Supply Unit A..D
Controller & Timing Units ID

S1..nA
Serial Expansion Unit A
S1..nB
Serial Expansion Unit B
CCU.A
Central Control Unit A
CCU.B
Central Control Unit B
CC.A
Communication Unit A
CC.B
Communication Unit B

.
Issue:1
TS.A
Timing Selector Oscillator Unit A
TS.B
Timing Selector Oscillator Unit B
TD.A
Timing Distributor Unit A
TD.B
Timing Distributor Unit B
M.A
Memory Expansion Unit A
M.B
Memory Expansion Unit B
PAR
Parallel Unit
PWA..D
Power Supply Unit A..D
Unit Type - Control & Timing Subrack

CCU
Central Control Unit.
MEM
Memory Expansion Unit.
C&T-PWR
Power Supply Unit (CT)
TS
Timing Selector-oscillator Unit
TD
Timing Distributor Unit
COMM
Communication & Q Interface Unit
PAR
Parallel Unit
SIO
Serial Expansion Unit

.
Issue:1
Unit Type - Matrix Subrack

1^Stage
I Stage Unit.
2^Stage
II Stage Unit.
3^Stage
III Stage Unit.
1^3^Stage
I/III Stage Unit.
Mx-PWR
Power Supply Unit (Matrix)
Mx-DIST
Timing Unit (Matrix)
Mx-CNTR
Control Unit (Matrix)
Unit Type - Port Subrack

STM16-Opt
STM-16 Tributary Unit (optical)
STM4-Opt
STM1-Opt
Boost
Optical Amplifier (Booster).
STM1-El
Electrical STM-1 Trib. Unit
4xSTM1-El
Electrical 4xSTM-1 Trib. Unit
2xSTM1-Opt
Optical 2xSTM-1 Trib. Unit
4xSTM1-140
Electrical 4x140/155Mbit/s Trib. Unit
TMUX-45
1x45Mbit/s Tributary Unit
140MB
140Mbit/s Tributary Unit
TMUX140
140Mbit/s TMUX Tributary Unit
AUX
Auxiliary & Service Channel Unit

.
Issue:1
AUX-67
Auxiliary & Service Channel Unit (type 6 and 7)
2MB
2MB-T2
16x2Mbit/s Tributary Unit Type 2
34/45MB
3x34/45Mbit/s Tributary Unit (type 2)
3x34MB
3x34Mbit/s Tributary Unit (type 3)
3x45MB
3x45Mbit/s Tributary Unit (type 3)
4x34-VC
4x34Mbit/s VideoCodec Tributary Unit
TMUX-4x34
4x34Mbit/s TMUX Tributary Unit
63x2Mb
MI_2
Trib/Matrix Interface & Concentrator Unit (type 2)
MI_5
Trib/Matrix Interface Unit (type 5)
MI_67M
Master Trib/Matrix Interface Unit (type 6 and 7)
MI_67S
Slave Trib/Matrix Interface Unit (type 6 and 7)
PC_2
Ports Control Unit (type 2)
PC_5
Ports Control Unit (type 5)
PC_67
Ports Control Unit (type 6 and 7)
PC-E
Ports Control Unit (type E)
PWR
Power Supply Unit (PORT)
ID
Identification Unit
ID_67
Identification Unit (type 6 and 7)

.
Issue:1
Preampl
Optical Preamplifier Unit
Filter
2 ch WDM Bid Mux/Demux (East/West)
Cross-connection Channel Role

Not connected
This value refers to a channel (incoming or outgoing). It indicates that the channel is not used by a
connection (see also From side and To Side).
From
This value refers to a channel (incoming). It indicates that the channel is used for a unidirectional
point-to-point connection (only Rx ).
To
This value refers to a channel (outgoing). It indicates that the channel is used for a unidirectional
point-to-point connection (only Tx ).
Bidirectional
This value refers to a channel (incoming and outgoing). It indicates that the channel is used for a
bidirectional point-to-point connection.
Master
This value refers to a channel (incoming). It indicates that the channel is used as main connection
(source) of a broadcasting connection.
Tributary
This value refers to a channel (outgoing). It indicates that the channel is used as secondary
connection (leg) of a broadcasting connection.
Monitor
This value refers to a channel (outgoing). It indicates that the channel is used for a monitor
connection.
Protection From
This value refers to a channel (incoming). It indicates that the channel is used for Path Protection of
a unidirectional connection (only Rx ).
Protection To
This value refers to a channel (outgoing). It indicates that the channel is used for Path Protection of
a unidirectional connection (only Tx ).
Protection Bidirectional
This value refers to a channel (incoming or outgoing). It indicates that the channel is used for Path
Protection of a bidirectional connection.
Unidir. Split From
This value refers to a channel. It indicates that the channel is the "incoming" channel of the TEST
port for the unidirectional split access of a unidirectional cross-connection.
Unidir. Split To
This value refers to a channel. It indicates that the channel is the "outgoing" channel of the TEST
port for the unidirectional split access of a unidirectional cross-connection.

.
Issue:1
Bidir. Split
This value refers to a channel (incoming and outgoing). It indicates that the channel is used as
bidirectional split access of a bidirectional connection.
Unidir. Splitted From
This value refers to a splitted channel. It indicates that the channel is the "incoming" channel of a
splitted unidirectional/bidirectional connection.
Unidir. Splitted To
This value refers to a splitted channel. It indicates that the channel is the "outgoing" channel of a
splitted bidirectional connection.
Bidir. Splitted
splitted bidirectional connection (bidirectional split access type). This channel is connected to the
TEST port.
Bidir. Spl Conn
splitted bidirectional connection (bidirectional split access type). This channel is not connected to
the TEST port.
Unidir. Spl Conn From
This value refers to a channel. It indicates that the channel is the "incoming" channel of a splitted
bidirectional connection (unidirectional split access type). This channel is not connected to the
TEST port.
Unidir. Spl Conn To
This value refers to a channel. It indicates that the channel is the "outgoing" channel of a splitted
unidirectional/bidirectional connection (unidirectional split access type).
In case of bidirectional connection this channel is not connected to the TEST port.
UDC Prot From
This value refers to a channel. It indicates that the channel is the "incoming" protection channel of a
Unidirectional Dropped Connection protection (unidirectional cross-connection kind).
UDC Drop
This value refers to a channel. It indicates that the channel is the drop leg channel of a
UDC Work From
This value refers to a channel. It indicates that the channel is the "incoming" worker channel of a
UDC Broad Prot From
This value refers to a channel. It indicates that the channel is the "incoming" protection channel of a
Unidirectional Dropped Connection protection (broadcast cross-connection kind).
UDC Broad Drop
This value refers to a channel. It indicates that the channel is the drop leg channel of a
UDC Broad Work From
This value refers to a channel. It indicates that the channel is the "incoming" worker channel of a

.
Issue:1
Conf. State
Unequipped
This state refers to subracks, units, ports and serial lines. The state indicates that the object has
not been equipped.
Equipped
This state refers to subracks, units, ports and serial lines. The state indicates that the object has
been equipped.
Configured
This state refers only to ports. The state indicates that the port has been configured. Only ports in
Configured state can be used for connections.
Connected Unit
..........
This value refers to serial lines. The value indicates the unit with which the serial line of the Control
& Timing Subrack is connected.
Conn.ed Subrack
Mx_A/Mx_B/01.....
This value refers to serial lines. The value indicates the identifier of the subrack at which the serial
line* is connected. The serial line can be connected to the Matrix Subrack (e.g. MATRIX_A) or to a
Ports Subrack (e.g. 01).
From Side
Connected
This state refers to an incoming channel. It indicates that the channel has been used in a
connection.
Free
This state refers to an incoming channel. It Indicates that the channel is available for a connection
(unused).
Busy
connection with bit rate different from the actually selected one.
Protection
This state refers to a protection channel. It indicates that the channel is used to protect a cross
connection.
Conn_vcnc
concatenated cross connection.
Prot_vcnc
This state refers to a protection channel. It indicates that the channel is used to protect a
DXC3_prot
This state refers to an incoming channel. It indicates that the channel has been used in DXC Type
3 protection.

.
Issue:1
Line Id
Line_1 .....
This value refers to serial lines. The value indicates that the serial line is used to connect the
Control & Timing Subrack to the other subracks. Each line is identified by a number (e.g. Line_1 is
the first serial line available in the Serial Expansion Unit starting from the top of the connection
panel).
Loopback State
Port Not Configured
This state refers to ports. The state indicates that the port has not been configured. In this state the
loops cannot be activated.
No Loopback
This state refers to ports. The state indicates that no loops have been activated in the selected
port.
Local Loopback
This state refers to ports. The state indicates that a local loopback have been activated in the
selected port. (matrix side)
Remote Loopback
This state refers to ports. The state indicates that a remote loopback have been activated in the
selected port.(line side)
Mapping Loopback
This state refers to 2Mbit/s ports. The state indicates that a remote loopback have been activated
in all the 2Mbit/s ports of the involved unit.(line side)
Mapping Loopback State

Enabled
This state refers to 2Mbit/s ports. The state indicates that the 2Mbit/s loop has been enabled in all
the ports of the 16x2Mbit/s Tributary Unit (mapping).
Disabled
This state refers to 2Mbit/s ports. The state indicates that the mapping has been disabled in the
16x2Mbit/s Tributary Unit.
Monitor Status
Not monitorable
This state refers to an incoming channel. It Indicates that the monitor connection cannot be added
(this state is always applied to the incoming channel).
Not Monitored
This state refers to an outgoing channel. It Indicates that the monitor connection has not been
added.
Monitored
This state refers to an outgoing channel. It Indicates that the monitor connection has been added.

.
Issue:1
Num. of Tribut.
<num>
This value refers to a broadcasting connection. It indicates the number of secondary cross-
connections (legs) available.
Num.
<num>
This value refers to multiple objects (e.g.: ports, serial lines, matrix accesses, STM-1 channels,
etc.). When referred to a 2Mbit/s Tributary Unit indicates the number of the 2Mbit/s port.
When referred to a Matrix Interface Unit indicates the number of the matrix access.
When referred to a VC-12 indicates its position in the STM-1 frame.
When referred to a serial line indicates the serial port of the Serial Expansion Unit.
For single objects the value is set to 1.
Operational State
Enabled
This state refers to subracks, units, ports and serial lines. The state indicates that the object is
operational.
Disabled
This state refers to subracks, units, ports and serial lines. The state indicates that the object is not
operational.
Path Protection
Unprotected
This state refers to a channel (incoming or outgoing). It indicates that the channel is not protected.
Rx Path Protection
This state refers to a channel (incoming). It indicates that the channel is protected by another
channel (unidirectional connection - only Rx ).
Tx Path Protection
This state refers to a channel (outgoing). It indicates that the channel is protected by another
channel (unidirectional connection - only Tx ).
TxRx Path Protection
This state refers to a channel (incoming or outgoing). It indicates that the channel is protected by
another channel (bidirectional connection).
UDC Protection
This state refers to a channel (incoming or outgoing). It indicates that the channel is UDC
protected.

.
Issue:1
Protection Mode
Not Revertive
This state refers to a tributary unit. It indicates that in case of fault of normal working unit the traffic
is permanently switched to the protection unit.
Revertive
This state refers to a tributary unit. It indicates that in case of fault of normal working unit the traffic
is switched to the protection unit. Traffic is switched back to the normal working unit as soon as the
failure has been cleared.
Switching Commands
In the next list are indicated all commands available for switching the worker side to the protection
side and vice-versa for a selected protected resource.
Forced Switch to Worker
To force the switch to the normal operating side.
Forced Switch to Protection
To force the switch to the protection side.
Manual Switch to Worker
To switch to the normal operating side. Unlike Forced Switch to Worker, it does not make the
switch if there are malfunctions in the normal operating side.
Manual Switch to Protection
To switch to the Protection side. Unlike Forced Switch to Protection, it does not make the switch if
there are malfunctions in the Protection side.
Clear
To free the protection (remove a previous forced switch). If the protection is revertive, it resets to
the normal state (Worker resource to providing service state and Protection resource to standby
state).
Lockout
Protection is locked to normal operating side (Worker) and cannot be modified.
Exercise
Equipment simulates the activation of the MSP protection by sending the activation message in the
link (check of the MSP protocol). This command is not yet available.
Protection Role
No protected
This state refers to Matrix Subrack, units (only units which can be protected) and serial lines. The
state indicates that the object cannot be protected.
Protection
state indicates that the object is used for protection.
Worker
state indicates that the object is used for normal service.

.
Issue:1
Auxiliary
This state refers to Communication Unit. The state indicates that the card is used for protection.
Protection Status
No request
No switch operation has been requested.
Do not revert
The protection switch has been executed and the traffic is forced on the target resource (Not
Revertive protection mode) also if the fault on the previous providing service resource has been
recovered.
Exercise Completed
Not yet managed.
Manual switch to protection completed
The requested "Manual switch to protection" Command Switch has been executed.
Manual switch to worker completed
The requested "Manual switch to worker" Command Switch has been executed.
Auto switch SF completed
Switching has been automatically executed due to a Signal Failure (SF) detected by the providing
service resource.
Auto switch SD completed
Switching has been automatically executed due to a Signal Degrade (SD) detected by the
providing service resource.
Auto switch SD pending
The Worker side has detected a SF condition and consequently it requires the switch on the
partner resource but the switch can not be performed.
Forced switch to protection completed
The requested "Forced switch to protection" Command Switch has been executed.
Forced switch to prot. completed, auto switch SF pending
Forced switch on the protection resource has been executed also if the target resource detects a
SF condition and consequently it requires the switch on the partner resource (worker).
Forced switch to prot. completed, auto switch SD pending
Forced switch on the protection resource has been executed also if the target resource detects a
SD condition and consequently it requires the switch on the partner resource (worker).
Lockout
Protection is locked to normal providing service side (Worker) and can not be modified.
Lockout, auto switch SF pending
The Worker side has detected a SF condition and consequently it requires the switch on the
partner resource but the protection is locked to normal providing service side (Worker) than no
switch can be performed.
The "resource operation" command stays pending.

.
Issue:1
Lockout, auto switch SD pending

The Worker side has detected a SD condition and consequently it requires the switch on the
partner resource but the protection is locked to normal providing service side (Worker) than no
switch can be performed.
The "resource operation" command stays pending.
Reverse request
The switching has occurred on command from the remote port (only for bidirectional MSP). The
local resources do not require any switch (no failure detected); the switching command is caused
by remote operation.
Lockout, SF on protection
The protection is locked to normal providing service side (Worker) and a SF condition (Signal
Failure) is detected on the protection resource.
Lockout, SD on protection
The protection is locked to normal providing service side (Worker) and a SD condition (Signal
Degrade) is detected on the protection resource.
SF on protection
A SF condition (Signal Failure) is detected on the protection resource.
SD on protection
A SD condition (Signal Degrade) is detected on the protection resource.
Auto switch SF to prot. completed, SD on prot.
Switching on the protection resource has been automatically executed due to a Signal Failure (SF)
on the worker resource.
The switching occurs also if the protection resource detect a Signal Degrade (SD) because a SF
takes priority.
Wait to restore
The protection resource is providing service and is waiting the WTR period to define if the traffic
can be switched back on the worker resource (no alarms present).
Forced switch to Wrk completed
The requested "Forced switch to worker" Command Switch has been executed.
Protection unavailable, auto switch SF pending
The providing service resource has detected a Signal Failure (SF) and it has automatically
requested a switching (Resource Operation) but the command is pending because there is not
available protection (unavailable protection resource or protection not configured).
Protection unavailable, auto switch SD pending
The providing service resource has detected a Signal Degrade (SD) and it has automatically
available protection (unavailable protection resource).
Protection unavailable, forced switch pending
The requested forced switch (Management Operation) can not be executed because the partner
resource in not available
Protection unavailable, manual switch pending
The requested manual switch (Management Operation) can not be executed because the partner
resource in not available

.
Issue:1
Auto switch DF completed

Switching has automatically executed due to a Device Failure (DF) on the providing service
resource.
Lockout, DF on protection
The protection is locked to normal providing service side (Worker) and a DF condition (Device
Failure) is detected on the protection resource.
DF on protection
A DF condition (Device Failure) is detected on the protection resource.
Protection unavailable, auto switch DF pending
The providing service resource has detected a Device Failure (DF) and it has automatically
available protection (unavailable protection resource).
No protection status
No protection configured.
Protection Type
No Protection
Protection not defined for the selected resource.
1+1 Unidirectional
1+1 Multiplexing Section Protection of 155Mbit/ s Tributary Unit (unidirectional).
1+1 Bidirectional
1+1 Multiplexing Section Protection of 155Mbit/ s Tributary Unit (bidirectional).
N+1 Unidirectional
N+1 Multiplexing Section Protection of 155Mbit/ s Tributary Unit (unidirectional).
N+1 Bidirectional
N+1 Multiplexing Section Protection of 155Mbit/ s Tributary Unit (bidirectional).
Matrix Protection
1+1 Protection of Matrix Subrack.
SIO Protection
1+1 Protection of Serial Expansion Unit.
SIO Line Protection
1+1 Protection of a serial line of Serial Expansion Unit.
COMM Protection
1+1 Protection of Communication and Q Interface Unit.
SEL Protection
1+1 Protection of Timing Selector-oscillator Unit.
DSTR Protection
1+1 Protection of Timing Distributor Unit.
CCU Protection
1+1 Protection of Central Control Unit.
MEM Protection
1+1 Protection of Memory Expansion Unit.

.
Issue:1
16x2Mb Card Prot.

N+1 Protection of 16x2Mbit/s Tributary Unit.
MI Protection
1+1 Protection of Matrix Interface Unit.
PC Protection
1+1 Protection of Ports Control and DCC Access Unit.
Rx Path Protection
Path protection of the receive path.
Tx Path Protection
Path protection of the transmit side.
TxRx Path Protection
Path protection of both transmission paths.
140Mb MSP 1+1 Unidir
1+1 Protection of the 140Mbit/s line (unidirectional).
The port involved in this kind of protection is a 140Mbit/s belonging to a 4x140-155Mbit/s Unit.
140Mb MSP 1+1 Bidir
1+1 Protection of the 140Mbit/s line (bidirectional).
The port involved in this kind of protection is a 140Mbit/s belonging to a 4x140-155Mbit/s Unit.
140Mb PDH 1+1
1+1 Protection of the 140Mbit/s line.
System Osc.-Input Src Prot
Protection of the synchronization sources used to synchronize the main oscillator.
Ext. Out. Osc.-Input Src Prot
Protection of the synchronization sources used to synchronize the secondary oscillator.
System Osc.-Mode Prot
Protection of equipment synchronization for the main oscillator.
Ext. Out. Osc.-Mode Prot
Protection of equipment synchronization for the secondary oscillator.
34/45Mb Card Prot.
1+1 or 1+N Unit Protection of 34/45Mbit/s Tributary Unit.
3x34/45Mb Line Prot.
1+1 Line Protection of 34/45Mbit/s line.
UDC Protection
Unidirectional Dropped Connection Protection.
1+1 Multiplexing Section Protection of STM-4 Tributary Unit (unidirectional).
STM-4 MSP 1+1 Bidir
1+1 Multiplexing Section Protection of STM-4 Tributary Unit (bidirectional).
STM-4 MSP 1:N Bidir
N+1 Multiplexing Section Protection of STM-4 Tributary Unit (bidirectional).

.
Issue:1

1+1 Multiplexing Section Protection of STM-16 Tributary Unit (unidirectional).
STM-16 MSP 1+1 Bidir
1+1 Multiplexing Section Protection of STM-16 Tributary Unit (bidirectional).
STM-16 MSP 1+1 Unidir (FE Sign)
1+1 Multiplexing Section Protection of STM-16 Tributary Unit with Far End protocol (unidirectional).
NxSTM1 MSP 1+1 Unidir
1+1 Multiplexing Section Protection of NxSTM-1 or 4x140/155Mbit/s Tributary Unit (unidirectional).
NxSTM1 MSP 1+1 Bidir
1+1 Multiplexing Section Protection of NxSTM-1 or 4x140/155Mbit/s Tributary Unit (bidirectional).
NxSTM1 MSP 1:N Bidir
N+1 Multiplexing Section Protection of NxSTM-1 or 4x140/155Mbit/s Tributary Unit (bidirectional).
45-TMUX Card Prot.
N+1 Protection of 1x45Mbit/s T-Mux Tributary Unit.
Rx Trail Prot.
Trail protection of the receive path.
Tx Trail Prot.
Trail protection of the transmit side.
TxRx Trail Prot.
Trail protection of both transmission and reception paths.
NxSTM1 Card Prot.
N+1 Unit Protection of NxSTM-1 or 4x140/155Mbit/s Tributary Unit.
63x2Mb Card Prot.
N+1 Unit Protection of 63x2Mbit/s Tributary Unit.
4x34-TMUX Card Prot.
N+1 Unit Protection of 4x34Mbit/s Tributary Unit.
Type 3 Card Prot.
N+1 Unit Protection on Type 3 Subrack Units.
Report Note
No report note
Quality samples have been correctly collected.
No Count
Quality counters have been stopped during the period at which sample refers.
Sample lost
Quality sample lost due to problem in the units that are managing the quality data collection (Port
Units or Port Controller Units).
Sample lost memory fail
Quality sample lost due to problem in the Memory Expansion Unit (BRAM problems).
Sample corrupted
Quality sample is not congruent.

.
Issue:1
Counter Overflow
Data size is higher than the maximum one.
Only 24h Available
The Operator requests a 15m register for a ME started in Service Mode.
Data Not Available
Data unavailable.
Selected TU modified
Selected TU has been modified during the collection period (only for Monitored Entity TU12).
Sample incomplete
Quality sample has been calculated on a period lower than the number of seconds forming the
period itself:
n<900 sec. for duration of 15 min;
n<86400 sec. for the previous 24 hours;
n<number of sec. spent in the current day for the current period of 24 hours.
Time Reset
Time has been modified while a quality data collection is running. Obtained results can belong to a
different duration.
Worker Data
Quantity data refers to the worker side
Protection Data
Quantity data refers to the protection side
Report Type
15 Min Current
Quality data collection relevant to the current 15 minutes.
15 Min Previous
Quality data collection relevant to the previous 15 minutes.
15 Min Recent
Quality data collection relevant to the last 8 hours (31 samples of 15 minutes).
24 Hours Current
Quality data collection relevant to the current day.
24 Hours Previous
Quality data collection relevant to the previous day.

.
Issue:1
SDH Traffic Type

VC-12
VC-12 used as traffic type.
VC2-5c
VC-2-5c used as traffic type.
VC-3
VC-4
VC4-nc
VC-4-nc used as traffic type.
SUBRACK ID
01...
Identification code of port subrack (Type 2 or Type 5).
MTX_A
Matrix Subrack A
MTX_B
Matrix Subrack B
MTX_AS
Slave Matrix Subrack A (DXC 4/4 only)
MTX_BS
Slave Matrix Subrack B (DXC 4/4 only)
CT
Control & Timing Subrack
To Side
Connected
This state refers to an outgoing channel. It Indicates that the channel has been used in a
connection.
Free
This state refers to an outgoing channel. It Indicates that the channel is available for a connection
(unused).
Busy
connection with bit rate different from the actually selected one.
Protection
This state refers to a protection channel. It indicates that the channel is used to protect a cross
connection.
Conn_vcnc

.
Issue:1
Prot_vcnc
concatenated cross connection protection.
DXC3_prot
This state refers to an outgoing channel. It Indicates that the channel has been used in a DXC
Type 3 protection.
X Connection Kind
Unidirectional
This value refers to a connection. It indicates that the connection is unidirectional.
Bidirectional
This value refers to a connection. It indicates that the connection is bidirectional.
Broadcast
This value refers to a connection. It indicates that the connection is broadcasting.
Monitor
This value refers to a connection. It indicates that a leg is used to monitor one of the end points of
the cross-connections.
Signal Type
This field concerns the cross-connection. There are different possibilities:
1..4
Relevant to VC-4 Xc cross-connection.
5
Relevant to VC-2 5c cross-connection.
Simple
For all the other cross-connection.
Split
For the split cross-connection.
Subrack Type
C&T Subrack
Control and Timing Subrack
TYPE-2 Subrack
2-34Mbit/s Tributary Ports Subrack
TYPE-3 Subrack
TYPE-4 Subrack
1x45Mbit/s T-Mux Tributary Ports Subrack
TYPE-5 Subrack
TYPE-6 Subrack
622Mbit/s Tributary Ports Subrack

.
Issue:1
TYPE-7 Subrack
2,5Gbit/s Tributary Ports Subrack
TYPE-6E Subrack
622Mbit/s Tributary Ports Subrack
TYPE-7E Subrack
2,5Gbit/s Tributary Ports Subrack
TYPE-BE Subrack
Booster Unit Subrack
512x512 Matrix
Matrix Subrack (DXC 4/4 512x512)
512x512 Mtx_86
1024x1024 Mtx_96
256x256 Matrix
128x128 Matrix
32x32 Matrix
Standby State
No prot
state indicates that the object is not providing protection.
Standby
state indicates that the object is not presently used in the protection to provide service.
Prov Service
state indicates that the object is presently used in the protection to provide service.
Synch Source
Enabled
This state refers to ports. The state indicates that the port is configured as a sync. source and it is
sending a good clock signal to the TS unit.
Disabled
This state refers to ports. The state indicates that the port is configured as a sync. source and it is
not sending a good clock signal to the TS unit.

.
Issue:1
ALARMS
Alarm Sources
All the DXC alarm roots are assembled in several alarm sources following the location and the kind
of the alarm.
The available ALARM SOURCES are given in following list.
Digital Stream and Interface Alarm Source
SPI
Synchronous Physical Interface alarms
SPI_NxSTM1
NxSTM-1 Synchronous Physical Interface alarms
SPI_NxSTM1_140
4x140-155Mbit/s Synchronous Physical Interface alarms
SPI_STM4
STM-4 Synchronous Physical Interface alarms
SPI_STM16
STM-16 Synchronous Physical Interface alarms
RS
Regenerator Section alarms
RS_NxSTM1
NxSTM-1 Regenerator Section alarms
RS_STM4
STM-4 Regenerator Section alarms
RS_STM16
STM-16 Regenerator Section alarms
MS
Multiplex Section alarms
MS_NxSTM1
NxSTM-1 Multiplex Section alarms
MS_STM4
STM-4 Multiplex Section alarms
MS_STM16
STM-16 Multiplex Section alarms
AU-4
140Mbit/s Administrative Unit alarms
AU-3
34/45Mbit/s Administrative Unit alarms
VC-4
High order Virtual Container alarms
TU-3
34/45Mbit/s Tributary Unit alarms

.
Issue:1
TU-2
6Mbit/s Tributary Unit alarms
TU-12
2Mbit/s Tributary Unit alarms
VC-3
High order Virtual Container alarms
VC-12
Low order Virtual Container alarms
2Mb
1.5/2Mbit/s PDH interface alarms
34Mb
34/45Mbit/s PDH interface alarms
140Mb
140Mbit/s PDH interface alarms
8MbCh
8Mbit/s channels of a T-Mux Unit alarms
34MbCh
34Mbit/s channels of a T-Mux Unit alarms
VideoCod
34Mbit/s VideoCodec interface alarms
VC2 -5c
Concatenated Virtual Container alarms
2MbPDHCh
2Mbit/s Channels of a T-Mux Unit alarms
DS2
alarms of 1x45Mbit/s T-Mux Unit DS2 Channels
DS3
alarms of 1x45Mbit/s T-Mux Unit DS3 Channels
4x34MbPDHCh
alarms of 4x34Mbit/s T-Mux Unit
63x2MbPDHCh
alarms of 63x2Mbit/s Unit
3x34_45Mb_VC3
VC-3 alarms of 3x34/45Mbit/s Unit
3x34_45MbPDHCh
alarms of 3x34/45Mbit/s Unit

.
Issue:1
Matrix Equipment Alarm Source

Mx1StU
1st Stage Matrix Unit alarms
Mx2StU
2nd Stage Matrix Unit alarms
Mx3StU
3rd Stage Matrix Unit alarms
MxIn
Matrix Input Side alarms (from side)
MxOut
Matrix Output Side alarms (to side)
MCU
Matrix Control Unit alarms
MTU
Matrix Timing Unit alarms
MPSU
Matrix Power Supply alarms
Mx13StU_86
1st/3rd Stage Matrix Unit alarms
Mx2StU_86
Mx13StU_96
1st/3rd Stage Matrix Unit alarms
Mx2StU_96
Mx1StU_91
1st Stage Matrix Unit alarms
Mx2StU_91
Mx3StU_91
3rd Stage Matrix Unit alarms
MxIn_91
Matrix Input Side alarms (from side)
MxOut_91
Matrix Output Side alarms (to side)
MCU_91
Matrix Control Unit alarms
MTU_91
Matrix Timing Unit alarms
MPSU_91
Matrix Power Supply alarms

.
Issue:1
Port Equipment Alarm Source

PortUnit
Port Unit alarms
PCU
Port Control Unit alarms
PPSU
Port Subrack Power Supply alarms
IdU
Identification Unit Alarms
AuxU
Auxiliary Unit Alarms
Trib./Matrix Interface Unit Alarm Source
MIU_T3/5
Type 3/5 Trib./Matrix Interface Unit alarms
MIUMx
Matrix Interface / Matrix access alarms
MIUPort
Matrix Interface / STM-1 port access alarms
MIU_MSP
Matrix Interface MSP (Multiplex Section Protection) alarms
MIU_T3/6/7
Type 3/6/7 Matrix Interface Unit alarms
MIU_T6E/7E
Type 6E/7E Matrix Interface Unit alarms
Control and Timing Equipment Alarm Source
CCU
Central Control Unit alarms
MemU
Memory Expansion Unit alarms
SIOU
Serial Expansion Unit alarms
SIOLine
Serial I/O line alarms
CommU
Communication and Q Interface Unit alarms
TSU
Timing Selector-oscillator Unit alarms
TDU
Timing Distributor Unit alarms
CTPSU
Control and Timing Equipment Power Supply alarms

.
Issue:1
SyncSrc
Timing Selector/Oscillator Unit synchronisation sources alarms
ParU
Parallel Interface Unit alarms
ParUGndC
Ground Contacts alarms
Alarms Category
URG
Urgent Alarm
NURG
Not Urgent Alarm
IND
Indication Alarm
INT
alarm within the equipment
EXT
alarm outside the equipment
MLQ
Alarm on the Q Interface
2Mb
alarm of a 2Mbit/s channel
8Mb
34-45Mb
alarm of a 34/45Mbit/s channel
140Mb
155Mb
alarm of an STM-1 channel
622Mb
alarm of a STM-4 channel
2Gb
alarm of an STM-16 channel
SYNC
alarm of a synchronisation circuit
OR(PSU)
OR alarm of one Power Supply Unit
AND(PSU)
AND alarm of both Power Supply Units

.
Issue:1
OR(Batt)
OR alarm of one battery voltage
AND(Batt)
AND alarm of both battery voltages
Mx
Alarm of the Switching Matrix
CA
Alarm of the Controller
MCF
Message Communication Function alarm.
COMMON
Common Alarm
Generic
Generic Alarm
Alarms States
Inactive
Alarm has been cleared.
Active
Alarm has been detected in the equipment.
Active_not_ack
Alarm has been detected in the equipment and it is not yet acknowledged by the Operator.
Active-ack
Alarm has been detected in the equipment and it has been acknowledged by the Operator.
Active_not_ack_NotMon
Alarm has been detected in the equipment, it is not yet acknowledged by the Operator and it has
been masked.
Active_ack_NotMon
Alarm has been detected in the equipment, it has been acknowledged by the Operator and it has
been masked.
Active-masked
Alarm has been detected in the equipment, and it has been masked.
Active-not-masked
Alarm has been detected in the equipment, and it has been not masked.
Alarms Types
Refer To:
Fault Detection Procedure

.
Issue:1
PERFORMANCE MANAGEMENT
Refer To:
DXC Synchronous Digital Cross-Connect Equipment Handbook, (Volume 1), Section
Information for the System Engineer.
The messages are managed by the equipment and the Control Application running on the PC
platform. They are displayed in the Control Application by means of a dialog box.
COMPLIANCE MESSAGES
They inform the Operator about problems, errors while executing a command.
0 - Success
Command has been successfully completed.
4 - Data Base Failure
Problem in the Memory Expansion Units, detected while writing in the system database.
5 - Data Base Busy
Database present in the Memory Expansion Unit is locked due to another operation in progress
(e.g.: another Operator is accessing the database, Network Management System operation, etc.).
6 - IPC Failure
Presence of an internal failure.
7 - Bram Failure
Error during Read/Write operation on Backup RAM on Memory Expansion Unit.
8 - PSOS Error
Operating System failure.
9 - Matrix is not in Test State
The Operator has tried to perform a Matrix test (Matrix Global Test or Subrack Link Test) when the
NE Test State is disabled.
10 - Wrong Amend Type
Wrong action has been selected.
11 - Wrong Value in Message
Sent message is uncorrected. Repeat selection.
12 - Generic Error
Indicates a generic error detected by the software.
13 - Not Supported
The selected function is not managed in this card.
14 - Wrong AUG Selected
The PJE (Pointer Justification Event) counting is performed on a different AUG. Select the AUG
used for PJE counting.
15 - NE Model Unknown
Equipment model has not been selected yet. Select NE Model.

.
Issue:1
16 - No More DBC Memory

No more Configuration Data Base memory. The maximum number of monitored accesses has been
reached.
17 - Card Version Mismatch
Protection and protected cards with a different hardware release.
18 - Signal Label Mismatch
Different signal label parameter configured into the selected cards.
19 - Wrong Aux Card Type
Auxiliary card is not a 16x2Mbit/s card (in 16x2Mbit/s 1:N protection configuration).
20 - Wrong Card Type
Selected card type not support the requested action.
21 - Wrong Card Slot
For the current action a wrong position has been selected.
22 - Card Equipped
Current action can not be executed due to a card which is equipped (e.g.: decommissioning of a
port subrack when one or more port units are still equipped).
23 - Card Unequipped
Current action can not be executed due to a card that has not been equipped (e.g.: configuration of
a protection without having equipped the protection unit).
24 - Card Locked
Not yet managed.
25 - Last Card of a Pair
Operator tried to delete the last card of an Equipment Protection Pair (CCU, MEM, Port Controller,
Matrix Interface Unit).
26 - Aux Card Unequipped
1+N card protection can not be configured because one of the 16x2Mbit/s Tributary Units,
necessary for the electrical continuity of the protection, is not equipped in the shelf.
27 - Port Parameter Mismatch
Port used as protection port can not be used since the port parameters are different from those
configured for the worker port.
28 - Port Mode Mismatch
Current action can not be executed because the Port Mode the of involved port is not allowed. In
case of 4x140-155Mbit/s Unit, the Port Mode identifies if the port acts as 140Mbit/s or STM-1.
29 - SS Bit Mismatch
Operator has tried to modify the content of the SS byte H1 (SDH / SONET compatibility).
30 - Port Not Config
Current action can not be executed due to a port that has not yet been configured. Configure the
selected port.
31 - Port Config
Current action can not be executed because the selected port is still configured.

.
Issue:1
32 - Port Locked
Not yet managed.
33 - Port Cross Connected
Current action can not be executed due to a port which is used for a cross-connection (e.g.: port can
not be deleted, MSP protection can not be defined).
34 - Too Many Subrack DCC
Configuration command rejected. The Operator can configure up to 8 DCC channels per port
subrack.
35 - High Order MUX Path Mismatch
Selected channel is not compatible with the traffic type defined for the selected STM-1 port (e.g.:
selection of AU3 when the STM-1 port has been configured as AU4).
36 - Too Many Network Element DCC
Configuration command rejected. The Operator can configure up to 64 DCC channel per Network
Element.
37 - PDH Code Mismatch
Operator has tried to modify the type of line coding.
38 - No Port in Message
Port number has not been specified in the command sent.
39 - Too Many Ports Configured in Subrack
Operator has tried to configure too many ports of those supported for the selected subrack.
40 - Subrack Unequipped
Selected subrack has not yet equipped.
41 - Subrack Equipped
Operator has tried to decommission a Matrix Subrack with Port Subrack still configured.
42 - Subrack Locked
Not yet managed.
43 - AUG Not Connected
Operator has tried to make a cross-connection using a port of a Port Subrack having the relevant
matrix access not yet connected to the Matrix Subrack. Define the matrix accesses connecting the
Port Subrack to the Matrix Subrack.
44 - Subrack Type Mismatch
Operator has tried to modify the type of subrack.
45 - Wrong Subrack Id
For the current action has been specified a wrong subrack.
46 - No Matrix Access
Current action can not be executed because no matrix access is available in the Matrix Subrack.
Add new cards to the Matrix Subrack and configure the new accesses.
47 - Loopback Enabled
Port can not be deleted due to a loopback enabled on the port itself. Remove the loopback.

.
Issue:1
48 - No More VC12 for 2Mb or TMUX

Configuration command rejected. The maximum number of configured VC-12 into the Network
Element has been reached.
49 - Too Many 140TMUX Cards
Configuration command rejected. The maximum number of configured 140Mbit/s T-Mux cards into
the Network Element has been reached.
50 - Matrix Access Unequipped
Operator has tried to equip a port subrack using matrix accesses not yet equipped.
51 - Matrix Access Connected
Operator has tried to:
1. equip a port subrack using matrix accesses already used for other ports subrack
2. to configure an 1+1 MSP on a subrack where all the matrix accesses are equipped. In this
case only the worker unit/s accesses have to be equipped.
53 - AUG Access Mismatch
Error in the Subrack Commissioning (From and To matrix cable mismatch).
54 - Matrix Access Mismatch
Mismatch between the specified incoming matrix accesses and the relevant outgoing matrix
accesses.
55 - Matrix Locked
Not yet managed.
56 - CCU Master
The Equipment configuration Card commissioningReset command has no effect on the
System restart menu.
active CCU. Resetting on CCU card in System
60 - ES Card Unequipped
Operator has tried to configure a peripheral unit (Timing Selector Oscillator Unit, Matrix Subrack or
Port Subracks) without having first configured the Serial Expansion Unit. Equip the Serial Expansion
Unit.
61 - ES Card Mismatch
Violation of the Serial Expansion Unit protection scheme.
62 - ES Line Unequipped
Operator has tried to configure a peripheral unit using a serial line of the Serial Expansion Unit
which is not yet configured. Equip the serial line used.
63 - ES Line Connected
Operator has tried to configure a peripheral unit using a serial line of the Serial Expansion Unit
which is already used. Select a different serial line.
64 - ES Line Mismatch
Violation of the serial lines protection scheme.
65 - ES Card Locked
Not yet managed.
66 - ES Line Locked
Not yet managed.

.
Issue:1
67 - ES Line Inv for Sync

Operator has tried to configure as synchronization source a port subrack connected to one of the
last 6 serial ports of the Serial Expansion Unit No. 5.
72 - Selected TU
The requested action can not be performed because the selected TU is used for performance
monitoring.
73 - UDC Equipped
Unidirectional Dropped connection has been defined.
74 - UDC Unequipped
Unidirectional Dropped connection has not yet been defined.
75 - Split Equipped
Split connection has been defined.
76 - No More Split
Configuration command rejected. The maximum number of configured split connection into the
Network Element has been reached.
77 - Split Unequipped
Split connection has not yet been defined.
78 - Connected Splitted
Channel selected for the cross-connection is already used for a split connection.
79 - No Cross Connection to handle
This message will be displayed during a manual restoration function when the source card manages
path protection cross connections only or when into destination card one or more than one
channel(s) is already cross connected.
80 - Wrong Traffic Type
A wrong type of traffic has been selected (e.g.: if VC-3 has been selected for a 2 Mbit/s port).
81 - Wrong Channel Id
Wrong channel identifier has been selected for the current action.
82 - Channel Connected
Channel selected for the cross-connection is already used for another cross-connection.
83 - Vc-nc Config
The selected channel belongs to a concatenated traffic type.
84 - Too Many Legs
Maximum number of legs for the broadcasting connection has been reached (max. 16 legs).
85 - Too Many Broadcast
Maximum number of broadcasting cross-connection available for the equipment has been reached.
86 - Traffic Mismatch
Operator has tried to add a broadcasting leg having a traffic type different from the master.
87 - Cross Connection Not Equipped
Operator has tried to delete or protect a cross-connection not yet equipped.

.
Issue:1
88 - Broadcast Unequipped
Operator has tried to use a broadcasting cross-connection not yet defined.
89 - Wrong Connection Type
Operator has tried to define in a 2 Mbit/s port a cross-connection of a type different from the
previous ports (for a 16x2Mbit/s Units only). The 2 Mbit/s ports must be cross-connected in groups
of four ports having the same type of cross-connections. For example, if a unidirectional cross-
connection has been defined in port 1, then in ports 2, 3 and 4 only unidirectional cross-connections
can be defined; port 5 can have a bidirectional cross-connection.
90 - Frame Config Mismatch
Operator tried to create a MSP protection on units having different frame configuration.
91 - Cross Connection Locked
Operator has tried to modify a cross-connection (e.g.: delete, add a path protection, etc.) while it
was in the locked state. Unlock the cross-connection using the relevant option.
92 - This Is Not a Cross Connection
Selected channel is not used for a cross-connection.
93 - This Is Not a Broadcast
Selected channel is not used for a broadcasting cross-connection.
94 - This Is Not a Monitor
Selected channel is not used for a monitor cross-connection.
95 - Monitor Equipped
Monitor cross-connection has been defined.
96 - Monitor Unequipped
Monitor cross-connection has not yet been defined.
97 - TU Unequipped
Current action cannot be executed because the TU is not yet used for a cross-connection.
98 - No VC-nc Master
Operator has selected a VC-nc channel different from the master.
99 - VC-nc Chain Error
The selected channels can not be concatenated. The selected channel sequence is wrong.
100 - Partial Success
It is used in the command of Set Start/Stop Performance Monitoring, in case even the succesful is
interupted due to the excessive loading on the card.
101 - Communications Unequipped
Operator has tried to start the OSI protocol without having configured the NSAP or the MAC.
102 - DCC Not Enabled
A not configured DCC channel has been selected.
103 - Too Many Port DCC
Operator has tried to configure a DCCr and a DCCm on the same STM-1 port.
104 - Protocol Started
OSI protocol of the Communication Unit has been started.

.
Issue:1
105 - DCC Enabled

DCC configuration command rejected when the destination port as defined as protection port (1+1)
or port decommission command rejected when a DCC channel is still configured.
106 - Reachable Prefix Address Already Configured
Reachable prefix address already configured. Verify the OSI configuration file.
107 - Profile Not Configured
DCC profile not configured into Database. Verify the DCC profile parameters into the configuration
file.
108 - Protocol Reset Failed
Operator has sent a wrong Protocol Reset File into the equipment.
109 - Auxiliary NSAP Cannot Be Defined Without Equipment NSAP
Operator tried to configure the <Auxiliary> NSAP without previously configure the <Equipment>
NSAP.
110 - NE Locked
Not yet managed.
140 - Timing Card Unequipped
Current action has failed due to a Timing Selector Oscillator Unit not yet equipped in the subrack.
Equip Timing Selector Oscillator Unit.
141 - Sync Source Not in Table
The selected synchronization source is not present in the priority table.
142 - No Sync Source in NE
Operator has tried to calibrate the Timing Selector Oscillator Unit before defining the
synchronization sources.
143 - Sync Source Unequipped
Selected port cannot be used as synchronization source because the port has not been yet
configured as shelf Sync Source.
144 - Active Sync Source
Operator has tried to delete the active synchronization source.
145 - No Free Run Sync Mode
Operator has tried to decommission the Timing Selector Oscillator Unit without setting the
synchronization mode to free running.
146 - Wrong Sync Mode
Sync source switch cannot be executed due to a synchronization mode different of normal.
147 - Sync Src Switch Fail
Switching of the synchronization sources in the Timing Selector Oscillator Unit has failed due to an
internal alarm.
148 - Wrong Quality Level
Mismatch between the quality level of the synchronization source in use and the minimum accepted
quality level configured in the synchronisation management window. The configured minimum
accepted level is better then the level of the synchronization source in use.

.
Issue:1
149 - Don't Use For Sync Port

Operator has tried to use a port dont use for sync for the MSP line protection.
150 - Invalid Srec
Check-sum error has been detected while down-loading the software or the database in the CCU.
Repeat again the download.
151 - SRec Out Of Sequence
Wrong sequence of commands is issued by Control Application.
152 - S3-File does not store data for requested file transfer
Downloading file format in different for the expected one (e.g.: you have selected CCU software on
prov. service as Target System Type and the incoming file format is for CCU Database)
153 - Wrong Data To Flash
Flash Memory write error occurred while software down-load was in progress. Repeat the download
or change the flash memory.
155 - Internal Communication Timeout Expired
Command sent from the CCU to the peripheral units has expired due to a timeout.
156 - Count Mismatch
During a download has been received a number of records different of that expected. Repeat again
the download.
157 - Mem Checksum Failure
Download procedure failed for internal writing error.
158 - Bank Out Of Order
Flash memory switch has failed due to a bank failure.
159 - Erasing Flash
Download cannot be performance because the flash memory deletion is in progress.
160 - Wrong Alarm Source Type
Selected alarm source is not supported.
161 - Wrong Source Number
Selected alarm number is not supported.
162 - Wrong Alarm Type
Selected alarm type is not supported.
164 - No Active Alarm
Operator has requested an active alarm report but no active alarms were present in the system.
165 - Parking Enabled
Operator tried to acknowledge active alarms while parking mode was enabled.
170 - Protection Config
Operator has tried to:
1. delete the configuration of a port used for MSP or card protection (to delete the unit remove
the protection).
2. define a protection resource as synchronization source (a protection resource can not be used
as synchronization source).

.
Issue:1
171 - MSP 1+1 Protection Port

Operator has tried to make a cross-connection using an MSP protection port.
172 - MSP 1+N Traffic Mismatch
1:N protection configuration command rejected.
173 - Wrong Protection Scheme
Violation of selected protection scheme.
174 - Another Protection Mode Already Used
Configuration command rejected because another protection mode (revertive/not revertive) is
already configured in the selected 34-45Mb card.
175 - Another Protection Type Already Configured
Configuration command rejected because:
1. another protection type (line/card) is already configured in the selected unit (i.e.: 34-45Mb
Unit).
2. another MSP architecture (1+1 / N+1) is already configured in the selected unit (on the ports
belonging to the same NxSTM-1 or 4x140-155Mbit/s Unit the MSP architecture must be the
same).
176 - Protection Not Config
Operator has tried to switch the protection on objects not configured for protection.
177 - Protection Command Failed
Manual switch command has failed.
178 - Line Protection Config
Configuration command rejected because the line protection is already configured in the selected
34-45Mb card.
179 - Card Protection Config
Configuration command rejected because the card protection is already configured in the selected
34-45Mb card.
180 - Event LOG Empty
Alarm Log is empty.
181 - Event LOG Rep Active
A reset of the Alarm Log has been requested while a report has been in progress.
190 - No Date and Time
Date and time have not yet been configured in the equipment.
191 - Command Already Ended
The abort command sent before is already ended.
192 - Abort Failure
Aborting of a command has failed.
193 - NE Online
Operator has tried to set the on line state to on-line while the state is already set to this value or to
perform a Database Decommission or Down-load while the, on line state is on-line.

.
Issue:1
194 - NE Offline
Operator has tried to set the on line state to off-line when the state was already set to this value or
to perform an action on periphery system while the on line state is off-line.
195 - NE Upgrade
Operator has tried to set the on line state to upgrade when the state was already set to this value.
197 - In/Out Contact Equipped
Operator has tried to configure the FOG or Italy2 Local Alarm Interface when the input/output
ground contacts was equipped.
200 - Wrong Entity Type
Selected port does not support that entity type.
201 - No More Memory
Memories used for storing the quality data are full.
202 - Performance Count Stopped
Indicates that the quality data collection counters have been stopped.
203 - Performance Count In Progress
Indicates that the Operator has tried to enable the performance data in a port where it was already
enabled or he has tried to delete a port enabled for the performance data collection.
204 - No Selected TU
Indicates that for the current action no TU has been selected.
205 - Counters Reset, No Data Stored
Indicates that upon a request of quality data display no data were available in the database.
206 - Performance Query Active
Indicates that the quality database is locked due to another operation. Repeat the command.
207 - Wrong Protection Status
Matrix Global test and Subrack Link test rejected because these tests require a force switch of the
traffic into the other one matrix equipment.
208 - Performance Upload In Progress
The requested action can not be executed due to EM data record uploading.
209 - No Performance On Subrack
No started performance on the selected subrack.
210 - TC Configured
Port can not be deleted due to a Tandem Connection Termination configured on the port itself.
Disable the Tandem Connection termination state.
211 - APS Channel Dup.
Indicates that the Operator has inserted an APS Channel already used by another unit of the same
protection group.
212 - Wrong Perf Operation Type
This message is given on test condition only.
213 Performance Configuration Already Used
The selected performance configuration (Set Id, Monitored Entity, 15min./24hrs registers, etc.) has
been already started.

.
Issue:1
215 - PDH Requirements Mismatch

The port can monitor the selected entity type only if properly configured (i.e. framed/unframed traffic
type).
217 - Wrong PC Type
The type of Port Controller configured is wrong.
218 - Subrack Eqp Mismatch
The type of Subrack configured is not correct.
219 - Port Unequipped
The action required can not be performed because the port is not equipped.
220 - Session open with only READ access mode
Indicates that the Operator is logged in with the read-only rights.
221 - Incorrect password
Indicates that a wrong password has been entered.
222 - NE session already open with this identifier
Indicates that another control session has been open (Control Application or Network Management
System).
223 - Disconnect Indication, Session refused
Indicates that the entered user name is not correct.
224 - Invalid Message Format
Indicates a wrong message sent.
225 - Unknown Message Id
Indicates a wrong message sent.
229 - Old password incorrect
Indicates that a wrong old password has been inserted while modifying the password.
230 - Invalid user name
Indicates that a wrong user name has been indicated while modifying the password.
231 - No login
Indicates that the login session has been closed automatically, for example if no messages are
received for a certain period from the Control Application. Run again the Control Application.
232 - Incorrect access rights
Indicates that a read-only Operator has tried to modify the equipment configuration.
233 - Command failed
Indicates that the last command sent to the equipment is failed. Repeat again the last command.
234 - Incorrect access mode
Not yet available.
235 - NE is starting up
Indicates that the equipment is not yet ready due to a restart or a switching-on. Wait until the restart
is over.
236 - Command could not be executed because it was already in progress
Get command already required form Network Management operator.

.
Issue:1
237 - There is a File Transfer command in progress

EM as tried to access in Read/Write mode the equipment while a database backup/download was
in progress.
238 - EM Timeout cannot be modified
The EM response time can not be modified because the EM is controlling the equipment.
239 - Data value out of range
Command rejected. Selected value great than the maximum one.
240 - Success, but is necessary an updating of DBC
EM has the control and a database realignment procedure has started.
246 - There is another VTC already configured on Matrix Side
The selected port has been already configured as Tandem Connection Termination on matrix side.
247 - There is another VTC already configured on Line Side
The selected port has been already configured as Tandem Connection Termination on line side.
248 - Too many Comm DCC
It has been reached a max number of configurable DCC on Comm.
249 - Too many PC protected DCC
It has been reached a max number of configurable DCC on Port Controller.
250 - Channel Conn Path Prot
The action required can not be performed because the channel is SNC protected.
251 - Too many PC not protected DCC
It has been reached a max number of configurable not protected DCC on Port Controller.
255 - Success More Data
Indicates that more data are available for the current report.
257 ANOTHER CONTROL SESSION ACTIVE ON THIS NE
Another user is logged in on NE. Try to reset the LC software and disconnect the serial line cable
(PC to equipment) for more than 30 sec.
ERROR MESSAGES
The error messages inform the operator that an error has occurred in the equipment or in the
Control Application application.
1 - No Printer Available
Selected printer is not available to print the current report.
2 - Invalid File Selected
The file name has not correctly specified.
3 - Cannot Create Selected File
The file specified cannot be created.
4 - No Printer Selected
The printer has not been selected.
5 - Data Error
Indicates that a wrong character has been specified for the NSAP or MAC (only hex numbers must
be entered).

.
Issue:1
6 - Message Length Error

Indicates that the sent message has a not valid length.
7 - Signal DB Empty
Indicates that the Operator has tried to read the Signal DB when no messages are stored.
8 - No Such File
Indicates that the selected file does not exist.
9 - New And Confirm Password Mismatch
Indicates that the new password has not been correctly entered.
10 - Invalid Selection
Indicates that the port selected as dont use for sync is not available.
11 - File Not Exist
Indicates that the indicated file is not existing.
12 - Invalid File Format
Indicates that the file specified for the software download is not in the correct format (s3...).
13 - Command Failed
The command has not correctly completed.
14 - Number Of Selected AUG/Channels Mismatch
Indicates that the channels selected for the incoming VC-nc connection and for the outgoing are
different.
15 - Error Opening The Selected File
Selected file cannot be opened.
16 - Line-Up Impossible - Online State Online
Indicates that the Line-Up cannot be perform because the Online State is Online. This operation is
allowed when the controller status is set to OFF-LINE.
17 - One Or more Ports Config - All Ports Must Be Only Equipped
Indicates that the Line-Up cannot be perform because one or more ports are configured. To
execute current action is necessary all port must be only equipped.
18 - One Or more Ports Not Config
Operator has tried to perform a Cross Connection Configuration before to configure the involved
ports.
19 - Line-Up Impossible - There Arent Equipped Cards
Indicates that the Line-Up cannot be perform because there are not equipped cards. To perform
current action is necessary all cards must be equipped.
20 - Forced Delete Impossible - Online State Online
Indicates that the option Forced Delete cannot be perform because the Online State is Online.
This operation is allowed when the controller status is set to OFF-LINE.
21 - Line-Up Impossible - Online State Upgrading
Indicates that the Line-Up cannot be perform because the Online State is Upgrading. This
operation is allowed when the controller status is set to OFF-LINE.

.
Issue:1
22 - Forced Delete Impossible - Online State Upgrading

Indicates that the option Forced Delete cannot be perform because the Online State is Upgrading.
This operation is allowed when the controller status is set to OFF-LINE.
23 - Realignment Not Started
The realignment can not start because communication problems are detected.
24 - Realignment Fail On No Single User
The realignment can not be executed because more than one user opened a session on the same
NE.
25 - Realignment Fail On Command In Progress
The realignment can not be executed because another user is modifying the database.
26 - Realignment Not Stopped
The requested action (configuration operation) can not be executed because there is a realignment
in progress.
27 - Sorry, Command Is Running
The selected action has been already requested and it is in progress.
28 - Database Error
Internal database error (checksum error).
29 - No DXC Update Permissions
The Operator has not the access rights to perform the selected action.
30 - There arent 3x34/45Mb Line Protection
The Operator has tried to enable the performance data for the units 3x34/45Mb/s in slot P2 or P6
without configure a Line Protection.
31 - Incorrect Access Right
The Operator cannot perform the selected action with the current access right.
32 - See Alarm Type LOS
The Operator has selected the alarm source SPI and the alarm type LOS_LOF in the option:
Fault-Config-Attributes
35 - Command Aborted
The command has been interrupted.
36 - Abort Command Fails
37 - Cannot Open Selected File
Error in the opening of the selected file; it cannot be opened.
39 - File Transfer Error
Check-sum error has been detected while down-loading the software or the database in the CCU.
Repeat again the download.
41 - Message Timeout
File transfer expired due to a time-out.
42 - Abort Command Refuse By The NE

.
Issue:1
43 - Invalid S Format Of Download File

Downloading file extension in different format for the expected one.
44 - File Transfer Already In Progress
Indicates that another file transfer has been already performed.
45 - Error In File Writing
Operator has not the correct access rights to perform writing operation.
46 - Error In File Reading
Operator has not the correct access rights for reading the file.
47 - !! There Arent Output Contacts Configured!!
Option Output contacts switch rejected because there are not output contacts configured.
48 - Data Error (In Equipment MAC Address)
Operator has inserted a wrong hexadecimal value in the MAC address field.
49 - Data Error (In Auxiliary MAC Address)
Operator has inserted a wrong hexadecimal value in the MAC address field of the auxiliary unit.
50 Port In Service But Not Available
The selected port works correctly but its configuration can not be modified. It is reserved for specific
application.
52 Port Reserved
The selected port is reserved for specific application and its configuration can not be modified.
53 Invalid File Name !
The specified file name is not valid.
54 File ./log/PRINT.TXT created.
The specified text file has been created. This file is created every time that the Operator performs a
printing of reports (from Windows NT O.S.).
55 !! THERE IS A PROTECTION CONFIGURED !!
This message is displayed when the Operator tries to configure the frame structure of a protection
channel/unit involved in a MSP.
190 - Link Error
The connection is not working properly.
191 - Link Down
The connection has been interrupted.
192 - Message Timeout
This message is displayed when the LC user has not performed any operation during the configured
session inactivity time; the Central Control Unit will quit the Control Application application.

.
Issue:1
WARNING MESSAGES
The warning messages inform the operator that the action being performed can have certain
consequences.
File Exists. Overwrite it?
Indicates that the Operator has selected a file that is already existing. Confirm to overwrite the file.
Are You Sure?
Indicates that the Operator has selected an action that needs a confirm because could affect some
process or entails the performing of other operation.
!!! Warning!!! If One Of The Involved Units Is A STM-1 Type 1 This Operation Could
Hit For A Short Time Other VC-3 Cross Connection...
This message is displayed when 2 VC-3 cross connections are currently active on a STM-1 card
and the Operator creates a 3rd new VC-3 cross connection; in this case traffic disturbance may
affect the existing 2 VC-3 Cross-Connections.
Be Careful!!! There Is A Dont Use For Sync Associated Port...
This message is displayed when the Operator tried to change the Subrack synchronization Source
with an associated Dont Use for Sync port.
This Command Could Affect Performance Counts!
This message is displayed when the Operator change date and time during a data performance
collection.
Remember Setting The MAC Address For This Unit!
This message is displayed when the Operator has equipped a Communication Unit.
Warning: The Requested Action Is Not Fully Reliable For Units: 131-7636/01 And 131-
7636/02. Unit 131-7636/03 Does Not Show The Problem
This message is displayed when the Operator performs, on the 3x34Mbit/s Tributary (async.) Unit,
an action (i. e. Loopback 34Mb) that for the specified version may affect the existing condition.
Note: SNCP Switch Can Take Place Without Alarm Signalling Due To Masking Or
Hierarchy Of Alarms..
This indication is present on the field relevant to HO PATH-PROT SWITCH CRITERIA. The criteria
for the high order path protection switch can be mask then they do not generate signalling, in any
case SNCP switch take place.
!! Warning!!: The SNCP Switching Criteria May Be Different For The Two Involved
Ports.
The Operator has performed a SNC Protection but the two involved ports have different SNCP
Switching Criteria.
All Ports Of Card Will Be Deleted
The Operator has performed a deleting of all unit ports.
Note: When Supervisory Unequipped is Enabled, Signal Label Values Are
Overridden
Label present on the STM-1 Type 2 configuration mask. When the Operator enables the Higher
Order Unequipped Generator (available only for STM-1 Type 2 Units), the configured Signal Label
values are overridden (new value will be all 0 - Unequipped- in the byte C2).

.
Issue:1
!! WARNING !! EM DataBase is already aligned with NE.

This message is displayed when the Operator runs a realignment operation on NE already aligned.
!! WARNING !! Inconsistent configuration.
This message is displayed when the Operator runs a realignment operation but the DB considered
as valid (to be downloaded) is corrupted.
!! WARNING !! Download function will overwrite the current NE configuration
The Operator performs a DB downloading from EM.
NOTE : the settings in this menu will be active starting from the next 15 min. period.
Label present on the performance configuration masks. When the Operator modify some
performance parameters, the configured values will be used starting from the next 15 min. period
(next register).
NOTE : when "All" is selected the default values for the involved items are displayed.
Label present on the "Performance Exception Threshold Configuration" configuration mask
(Performance-NE Configuration-Exception Threshold Setup). When the Operator selects the
All item in the Set Id scroll list all the Entity Type default exception thresholds are displayed.
EM DataBase is aligned with NE.
This message is displayed as result of a "Check DB Alignment" test.
Inconsistent configuration.
This message is displayed as result of a "Check DB Alignment" test. The DB is corrupted.
EM DataBase is not aligned with NE.
This message is displayed as result of a "Check DB Alignment" test.
The Selected TU is used for all Aug.
The selected TU under monitoring is used for all the AUG.
The Operation is Traffic Affecting!
The selected operation could affect the traffic.
!! WARNING !! Any change on the selected card, will be applied to all cards involved
in the MSP 1
This warning message is displayed when the Operator tries to configure the frame structure of a
worker channel/unit involved in a MSP (1+1 or N+1): the same change will be applied to all the other
units belonging to the MSP group.
!! WARNING !! Wrong switch could require a manual hardware switch !
This message is displayed when the Operator performs a "Bank Switch".
!! WARNING !! previous selected TU will be removed !!!
This message is displayed when the Operator configure the exception threshold of a TU (Selected
TU). In this case the previous selected TU exception configuration will be removed.

.
Issue:1
COMMUNICATION
It is possible to modify, using the Control Application, the configuration of the OSI parameters used
by the Port Controller and Communication Units of the DXC.
The configuration options allow a modification up to layer 4 of the communication protocol.
Marconi SDH equipment implements the protocols specified by the following recommendations.
On layer 2:
n On Ethernet:
ISO 8802-3 (CSMA/CD)
ISO 8802-2 (LLC)
n On DCC:
CCITT Q.920/921 (LAPD)
On layer 3:
n ISO 8473 (CLNP)
n ISO 9542 (ESIS)
n ISO 10589 (ISIS)
On layer 4:
n ISO 8073 (OSI Transport)
Modification of the OSI protocol parameters may be needed in order to guaranteed the
interoperability between SDH equipment developed by Marconi and SDH equipment developed by
other manufacturer. Such interoperability may be required on Ethernet Q interface (QB3) and/or
Qecc (Data Communication Channel).
Note that, with few exceptions (e.g.: a System Id length different for two systems within the same
ISIS domain), it is not necessary to configure the protocol parameters exactly in the same way, to
allow the interoperability between systems of different manufacturers. Anyway, consistent
discrepancies in the values of some parameters, such as the LAPD, ESIS and ISIS timer values can
cause communication failures.
The information related to layer 4 profiling may be used to improve the performance of the
communication between the equipment and the Element Manager.
IMPORTANT The Operator has to take into account that a wrong OSI protocol configuration
can affect the communication.
Before applying any command it is suggested to perform a backup of the OSI parameters.

.
Issue:1
COMMUNICATION
COMMUNICATION: BACKUP AND RESTORE

In order to backup OSI parameters, addresses and routing configuration the Operator has to
perform a database backup from LCT.
IMPORTANT In release 10.2 (EM DXC v. 9.4), the OSI and NSAP data will not be stored in the
EM database. Then a database upload operation from EM will not get any OSI
and NSAP data.
To restore OSI data a database download from LCT will be necessary.

See Also:
System: performing database backup, System: downloading Sw and DB on C&T
subrack
COMMUNICATION: OSI RESET DEFAULT

Path (Equipment Configuration-Communication Configuration-OSI Rest Default)
This option is used to restore the default OSI parameters.
Selecting the option a confirmation window will appear.
COMMUNICATION: SET GLOBAL PARAMETERS

Path (Equipment Configuration-Communication Configuration-NE COMMS)
This option is used, mainly, to assign the addresses to each entity able to act as OSI router:
Communication Units and Port Controllers.
NE COMM window is divided in different fields and columns.
The upper field is a read only section that shown for each communication resource:
Sub. Id
It is the subrack identifier: C&T stand for Control and Timing (in case we refer to a Communication
Unit) while a number is used to identify the Port Subracks (in case of Port Controller Unit). The
identifier number for the Port Subrack is the same displayed on the Identification Unit.
NSAP Address
Network Service Access Point Address (identify of the element).
MAC Address
Medium Access Control Address (physical access to an Ethernet LAN).
Rout. Mode
Routing mode for the Port Subracks. The OSI messages received by the Port Subrack can be
routed by the Port Controller (distributed routing) or by the Communication Unit (centralised
routing).
Eth. State
Operational state of the Q interface.
The lower field is an information box that display all the parameters set for the selected
communication resource.

.
Issue:1
COMMUNICATION
Communication: routing mode

Path (Action-Routing Mode-Setup/Read)
The routing mode configuration describes how the OSI protocol will be managed on the Port
Subrack.
Distributed Routing
Distributed Routing is based on the addition of routing functions in the Port Controllers.
With this feature the Port Controllers now become stand-alone OSI routers and each contains a full
3-layer protocol stack. The DXC therefore becomes a collection of routers, each with its own NSAP
and MAC addresses.
The following subrack types offer STM-1 port and will be capable of supporting the Distributed
Routing function: Type 6, 6E, 7 and 7E.
IMPORTANT The subrack has to be equipped with the Port Controllers Type E.
Centralized Routing
Default routing mode. In this condition the router functionality are carried out by the Communication
Unit only.
To set the Routing Mode:

* Select a Communication Entity in the NE COMM window
* Select Action- Routing Mode - Setup
* Select the Routing Mode
* Press APPLY
To read the Routing Mode:

* Select Action- Routing Mode - Read
* Press CLOSE to exit.
Communication: ethernet parameters

Path (Action-Ethernet Parameters-Setup/Read)
The ethernet parameters refer to the Q interface.
On the DXC both Control and Timing and Port Subracks can have Q interfaces.
For each physical ethernet interface the Operator has to specify: MAC address, ethernet profile and
the ethernet state.
As far as the Communication Unit is concerned, take into account that:
n If Load Sharing is enabled, the MAC addresses of both Communication Units (called <Main>
and <Auxiliary>) must be configured and must be set to different values.
n If Load Sharing is disabled, only the MAC address of the <Main> Communication Unit must
be configured.
The MAC address of both Port Controller Units (<Main> and <Auxiliary>) has to be configured.

.
Issue:1
COMMUNICATION
To set the Ethernet Parameters:

* Select Action - Ethernet Parameters - Setup
* Select the COMM (Communication Unit - in case of Control and Timing) or the Port
Controller (in case of Port Subrack) resource (Main or Auxiliary) whose ethernet
parameters has to be set.
Note To the Main resource is associated the address used by the NMC to reach the
equipment.
* Select the Ethernet Profile. Eight Ethernet Profiles are available. A profile represents a
configuration of the ethernet circuit parameters (metric values, ISO 9542 timers and
options, maximum packet size managed, router priorities). Each profile can be modified
according to the DCN characteristics.
* Enter the Ethernet MAC Address in hexadecimal. Make sure that the same value has
been indicated in the NMC (Network Management Centre).
The first three bytes represent the factory identifier number (00 A0 AD) and their value
can be changed by the User.
IMPORTANT MAC address can be set on the provisioned units only.
* Use Ethernet State to enable/disable the ethernet circuit.

* No Adjacency Switch option is used to enable/disable the detection of the No
Adjacency alarm.
NOTICE The alarm No Adjacency is raised in case of Ethernet connection enabled

and no adjacency (layer 3) detected on the Ethernet network. This alarm is
associated to the card managing the Ethernet connection, i.e. CommU for the
central routing, both Port Controller (Type E) in a subrack enabled to peripheral

.
Issue:1
COMMUNICATION
routing. It is possible to enable/disable (default = disabled) the No adjacency

alarm to drive the switch of Port Controller.
* Press APPLY.
To read the Ethernet Parameters:

* Select Action - Ethernet Parameters - Read
See Also:
Communication: ethernet profiles configuration
Protection for ethernet disconnection
For each subrack enabled to peripheral (distributed) routing with an Ethernet connection associated
it is possible (by default not) set the Port Controller switch in case of Ethernet failure.
The switch is driven by the detection of the No Adjacency alarm; if the Port Controller acting as
Communication providing service detects the alarm then both Communication and Controller
functions are switched: the Communication providing service card becomes auxiliary and working
Controller functions, the auxiliary Communication card becomes providing service and stand by
for Controller functions.
In the subracks managing distributed routing:
n The MAIN Communication resource is the Port Controller in Stand-by mode
n The AUXILIARY Communication resource is the Port Controller Providing Service
If also the auxiliary PC card presents a No Adjacency alarm, the switch is not performed.
In order to detect the No Adjacency alarm both Port Controllers in a subrack enabled to peripheral
routing monitor the Ethernet connection:
1. If the Port Controller is running at network layer the alarm is raised when no layer 3
adjacencies are detected on Ethernet network, as at present for CommU.
2. If the Port Controller is not running network layer (redundant configuration) the alarm is raised
if the card doesnt detect any broadcast message (hello message) in the Ethernet link for
more than 5 minutes and is cleared when a broadcast message is detected.

.
Issue:1
COMMUNICATION
Communication: router parameters

Path (Action-Router Parameters-Setup/Read)
Router Parameters window is used to set the:
n IS-IS router type,
n IS-IS router profile,
n NSAP address,
n manual area addresses,
for the Communication Unit/s and the Port Controller Units.
To setup router parameters:

* Select Action - Router Parameters - Setup
* Select the COMM (Communication Unit - in case of Control and Timing) or the Port
Controller (in case of Port Subrack) resource (Main or Auxiliary) whose ethernet
parameters has to be set.
Note Auxiliary COMM router parameters must be set only if Load Sharing option has
been enabled.

.
Issue:1
COMMUNICATION
* Define the IS-IS Router Type. Value can be 1 (level 1 routing only), or 3 (both level 1 and
level 2 routing). The default value is 1 (range 1, 3).
Note Level 1 router (local router): as defined in the ISIS protocol (ISO 10589). Level 2
router (area router): as defined in the ISIS protocol (ISO 10589). router is a
synonymous for Intermediate System, as defined in the above recommendations.
* Define the Address Area Length (range 1..13).
* Enter the NSAP address in hexadecimal.
The Address area is a hexadecimal of up to 13 bytes (Len Address Area 1..13). It
identifies the area in which the device is inserted.
The System Id. is a 6 hexadecimal number string (12 digits) which identifies single
equipment and must be unique in the whole network.
NOTICE Note that all the systems within a ISIS domain must have the same length for the
System Id.
The Selector is automatically set by the system.
NOTICE The main NSAP is required, the auxiliary NSAP is required only if more than 8
DCC in the subrack have to be managed.
* Specify the two manual area addresses (2, 3) which this router recognizes as
synonymous of its own area address (which is taken from the first part of the NSAP Id).
Each Area Address is preceded by its length (Len Man Area Address 1, 2).
* Set the Router Profile. Two configurable router profiles are available.
* Press APPLY.
To read the Ethernet Parameters:

* Select Action - Router Parameters - Read
See Also:
Communication: ethernet parameters, Communication: router profiles configuration,
Communication: configuring DCC

.
Issue:1
COMMUNICATION
COMMUNICATION: SETTING INTERNAL CIRCUIT STATE

Path (Equipment Configuration-Communication Configuration-Internal Circuit Control-
Setup/Read)
This option allows to enable/disable the OSI communication circuit between the two Communication
Units (whether Load Sharing mode is enabled).
If the circuit has been enabled a Communication Unit has the capability of re-routing OSI packets to
the other using the internal ethernet link.
To enable/disable the internal ethernet OSI circuit:

* Select Equipment Configuration - Communication Configuration - Internal Circuit
Control - Setup
* Use the Ethernet state push button to enable/disable the internal ethernet OSI circuit.
* Press APPLY.
To read the internal ethernet OSI circuit state:

* Select Equipment Configuration - Communication Configuration - Internal Circuit
Control - Read
See Also:
Communication: router parameters, Communication: configuring DCC
COMMUNICATION: CONFIGURING DCC

Path (Equipment Configuration-Communication Configuration-DCC Configuration) [LC]
This option is used to configure the Data Communication Channels. By means of this option it is
possible to set the STM-N port used for transmission of DCC.
The window shows the configuration in use for DCC channels (if configured).
To Delete a DCC channel:

* Select the DCC channel to be deleted in the available list
* Select Action-Delete
To Delete all DCC channels:

* Select Action-Delete All
* Press OK to confirm the operation
To Configure DCC channels:

* Select Action-Add

.
Issue:1
COMMUNICATION
* Select the Type 5, 6, 6E, 7 or 7E port subrack

* Select the STM-N or NxSTM-1 unit
* Select the port.
IMPORTANT Port must be configured.
* Use DCC Type to select the Regenerator Section (RS DCC) or the Multiplex Section (MS
DCC) in the STM-N overhead.
* Use LAPD Configuration to set the Link Access Procedure Device role (User /
Network).
* Use COMM to assign the DCC to one Communication Unit
(CC_PROV_SERVICE/CC_STAND_BY).
* Use DCC Protection to declare the DCC protection status
(PROTECTED/NOT_PROTECTED).
IMPORTANT If the equipment is provided with one CommU only, the DCCs must be
configured as protected (If only one Communication Unit is active, only the
PROTECTED DCC are routed).
* The PC Protection option is available for type 6 and 6E subrack only and allows to
define if the DCC is kept operational even if only one Port Controller is working on the
subrack (PROTECTED).

.
Issue:1
COMMUNICATION
Because of a hardware limitation, T6/7 Port Controller Unit can handle up to 8 DCCs, while Type 6
Subrack may have up to 16 STM-N interfaces. With this feature, it is possible to configure up to 16
DCCs for each Subrack, having each Port Controller handling 8 of them.
The DCC configured in a subrack are assigned as follow:
Protected DCC managed by the Stand-by PCU (Main resource);
Not protected DCC managed by the Providing Service PCU (Auxiliary resource).
Note Remember to set the MAC and NSAP addresses of the resource managing the DCC
if distribuited routing will be used on that shelf.
* Press APPLY
To Modify a DCC channel:

* Select, in the available list, the DCC channel whose configuration has to be modified
* Select Action-Modify
* Use DCC Profiles to set the profiles associated to the selected DCC.
* Use LAPD Configuration to set the Link Access Procedure Device role (User /
Network).
* Use COMM to assign the DCC to one Communication Unit
(CC_PROV_SERVICE/CC_STAND_BY).
* Use DCC Protection to declare the DCC protection status
(PROTECTED/NOT_PROTECTED).
IMPORTANT If only one Communication Unit is active, only the PROTECTED DCC are routed
* The PC Protection option is available for type 6 and 6E subrack only and allows to
define if the DCC is kept operational even if only one Port Controller is working on the
subrack (PROTECTED).
* Press APPLY

.
Issue:1
COMMUNICATION
Protection of DCCs in case of MSP 1+1 and MSP 1:N

In case of MSP 1+1 or MSP 1:N a DCC can be protected creating manually a DCC on the
protection side.
NOTICE Note that the DCCs to be protected by the MSP 1:N must be of the same type (R
or M) and having the same LAPD configuration (USER or NETWORK).
In case of MSP 1:N or MSP 1+1 bidirectional a DCC can be protected in two different ways:
DCC manual protection:

the Operator has to create manually a DCC on the protection side;
this DCC is used to protect the DCC of the worker side.
The DCC on the worker side and the DCC on the protection side run at the same time.
DCC automatic protection:
if no DCC is manually created on the protection side when the MSP protection is activated, the
DCC is automatically deleted from the worker side and created on the protection side.
Only one DCC at time runs.
The CCU database is not modified, so the Control Application displays the DCC on the worker side
only.
Protection of DCCs in case of Unit Protection
In case of 4xSTM-1 T2/T3 or 4x140-155Mbit/s Unit protection a DCC is protected in this way:
DCC automatic protection:
when the MSP protection is activated, the DCC is automatically deleted from the worker side and
created on the protection side.
Only one DCC at time runs.
NOTICE Note that the DCCs to be protected by the Unit Protection must be of the same
type (R or M) and having the same LAPD configuration (USER or NETWORK).
Using the DCC manual protection, the DCCs defined in the not active unit do not run; this condition
raises an DCC r/s LAPD Disconnected alarm.
See Also:
Operative States, Communication: DCC profiles configuration, Communication: set
global parameters

.
Issue:1
COMMUNICATION
COMMUNICATION: ENABLING
Path (Equipment Configuration-Communication Configuration-Communication Control-
Setup/Read) [LC]
Use this option to enable/disable the OSI communication protocol used for connection to NMC.
Check that the correct NSAP and MAC have been entered before enabling the OSI protocol.
To activate/deactivate the OSI protocol:

* Use Protocol Stack Status to enable (Protocol Stack Started) or disable (Protocol
Stack Stopped) the OSI communication protocol.
* Press APPLY.
To read the OSI protocol state:

* Select Equipment Configuration - Communication Configuration - Communication
Control - Read
See Also:
Communication: ethernet parameters, Communication: router parameters
STATIC ROUTE
Path (Equipment Configuration-Communication Configuration-Static Route)
The management of the IS-IS dynamic routing protocol can be replaced (partially) with static routing
tables, in order to reduce the communication overhead.
Two basic static routing strategies are managed on the SDH equipment:
n use of RAP (Reachable Address Prefixes) tables;
n use of MESA (Manual End System Adjacencies) tables.
The RAP is mainly used on Inter-Domain routing, where no dynamic option is available, while the
MESA is used on Intra-Domain routing, when no IS-IS and ES-IS are managed.
Furthermore, the DXC is able to manage the MESA Range routing strategy that allows to overtake
the limit of the MESA strategy.
RAP Table
Between different domains no dynamic routing is supported, therefore on each Level 2 IS on the
domain boundary, a RAP table can be configured, in order to forward data packets from on domain
to another.
To each circuit outgoing from a domain an address prefix can be assigned. Whenever a data packet
cannot be forwarded using the dynamic routing, a check on its area address is performed. If the
packet matches at least on prefix, then it is forwarded on the circuit associated to the longest prefix
(best match). If there are more matching prefixes with the same length (highest), then the packet is
forwarded onto the circuit associated to the prefix with the lowest cost (if the cost is the same, the
selection is random).

.
Issue:1
COMMUNICATION
MESA Table
Within a domain, a NE not managing the dynamic routing (i.e. ES-IS and IS-IS protocols) can be
reached using a MESA table.
The MESA is a static adjacency to a number of NEs. Whenever the circuit on which the adjacency
is configured is ON, the MESA gives access to the Manual End System neighbours, just like after a
dynamic exchange of ES-IS packets on that circuit.
MESA Range Table

Manual End System Adjacencies have the advantage that it is not necessary to setup the SDH NE
as a level 2 router to use them, and that it is not necessary to have a different area (meaning a
different domain) for each route configured. On the other hand, they have the disadvantage that
each route can give access to [20/SystemIdLength] (typically, 3) End Systems, at most, while a
single RAP can give access to a virtually unlimited number of systems. For example, if there were
an STM-N ring containing 20 elements, it would be possible to reach all the elements from the
gateway by configuring just one RAP, but 7 MESAs would be needed.
This is the reason why a third type of static routing has been introduced, namely Manual ES
Adjacency Range.
With this type of static route, it is possible to configure, on a given circuit, up to three sets of ES
identifiers for each of which a manual adjacency is created. Each set can contain up to 255
identifiers.
The constraint on the identifiers is that they must all be contiguous, so that it is possible to enter just
the start and the width of the range. This is not a real constraint, as the network addressing plan can
be designed in accordance with this assumption.
This option is used to add/delete a RAP, a MESA or a MESA Range.
IMPORTANT Erasing a DCC with a MESA/RAP associated, the static configuration will still
remain stored in the database. The Operator has to remove it manually. If the
Operator does not remove it, some problems could arise when a DCC will be re-
configured and re-used with dynamic routing.

.
Issue:1
COMMUNICATION
In this window are displayed all the RAP, MESA and MESA Range configured on the Q interface of
the Communication Units and on the DCC channels.
Note Static Routing is not applied to the Q interface on the Subracks.
For each static route (row) is displayed:
RAP/MESA identifier - Pfx Id
It is an integer value, which uniquely identifies the Reachable Address Prefix (RAP) within the
Network Element (NE). This may be useful when there are more than one RAP (or Manual End
System Adjacencies - MESA) associated to the same SubNetwork Point of Attachment (SNPA). In
this case the prefix identifier allows to distinguish between them.
RAP/MESA type - Prefix Type
The RAP (ADDRESS_PFX), MESA (MANUAL_ADJ) or MESA Range (MANUAL_ADJ_range)
can be associated to: Main (COMM_A), Auxiliary (COMM_B), both (both_COMM) Communication
Unit or to a point to point circuit (ptp - i.e.: DCC channel).
These static routing strategies can be applied to two different circuits:
n A broadcast circuit (broad) supports an arbitrary number of End Systems, and additionally
is capable to transmit a single PDU to all or a subset of these systems in response to a
single Unit Data Request.
n A point-to-point circuit (ptp) supports exactly two systems. The two systems can be either
two End Systems or an End System and a single Intermediate System (i.e. DCC channel).
On a broadcast circuit, it is possible to assign a static route to both COMMs simultaneously or just to
one of them. This is useful, because the two cards may be connected to different ethernet sub-
networks.
As far as point-to-point circuits are concerned, on the other hand, this distinction does not make
sense, because only one COMM at a time may handle a given DCC.
Therefore, the static route is associated to both COMMs, but only used on the COMM actually
managing the DCC.
The possible choices for RAP are:
n ADDRESS_PFX_broad_both_COMM: RAP (reachable address prefix) associated to both
Communication Units on broadcast circuit
n ADDRESS_PFX_ptp: RAP (reachable address prefix) associated to a point-to-point circuit
n ADDRESS_PFX_broad_COMM_A: RAP associated to Communication Unit A on broadcast
circuit
n ADDRESS_PFX_broad_COMM_B: RAP associated to Communication Unit B on broadcast
circuit
The possible choices for MESA are:
n MANUAL_ADJ_broad_both_COMM: MESA associated to both COMM on broadcast circuit
n MANUAL_ADJ_ptp: MESA associated to both COMM on point-to-point circuit
n MANUAL_ADJ_broad_COMM_B: MESA associated to Communication Unit B on
broadcast circuit

.
Issue:1
COMMUNICATION
n MANUAL_ADJ_broad_COMM_A: MESA associated to Communication Unit A on

broadcast circuit
The possible choice for MESA range is:
n MANUAL_ADJ_range_ptp: MESA range associated to a point-to-point circuit.
Conclusions
RAP and MESA broadcast:
a. can be associated either to COMM_A, to COMM_B, or both_COMM
b. are not managed on Port Subrack configured in distributed routing mode
RAP, MESA and MESA range point to point are associated to a DCC:
a. if the DCC is managed in centralised routing mode, the static route will be managed by the
COMM managing the DCC (A or B)
b. if the DCC is managed in distributed routing mode, the static route will be managed by the
Port Controller managing the DCC (A or B)
SNPA/Sh-Card-Port
Subnetwork Point of Attachment (Ethernet MAC address of the statically addressed destination
system), in case of ethernet interface, or Shelf/Card/Port indication, in case of DCC channel.
Communication: add RAP

Path (Action-Add RAP)
It is possible to add a RAP on:
n COMM Main (broadcast);
n COMM Auxiliary (broadcast);
n Both COMM (broadcast);
n a DCC Channel (point to point).

.
Issue:1
COMMUNICATION
To add a RAP:
* After selecting the option (Action-Add RAP) click on the circuit where the RAP has to
be configured.
* Press OK push button.
In the window that will appear:
* Assign a prefix identifier using the arrow buttons in the RA Identifier field (range 1 to
512).
* Use RA length in semioctets to define the prefix length.
NOTICE Note that the prefix length is expressed in semioctets.
* Define the default metric value for the route (RA default metric - 1..63).
* Insert the reachable address prefix (Destination System Id).
* In case of Communication Unit, specify the SNPA address (SNPA Identifier).
Note For the DCC this is a read only field showing the relevant shelf/card/port.
To read a RAP:
* Select the rap and use the item Action-Read RAP.
In the window that will Rap details are displayed:
See Also:

.
Issue:1
COMMUNICATION
Communication: add MESA

Path (Action-Add MESA)
It is possible to add a MESA on:
n COMM Main;
n COMM Auxiliary;
n Both COMM;
n a DCC Channel.
To add a MESA:
* After selecting the option (Action-Add MESA) click on the circuit where the MESA has
to be configured.
* Assign a manual adjacencies identifier using the arrow buttons in the RA Identifier field
(range 1 to 512).
* Use Number of Destination System Id to define the number of manual adjacencies
(system Id) to be configured on this circuit.
* Insert the system Id addresses of the adjacencies.
* In case of Communication Unit, specify the SNPA address (SNPA Identifier).
Note For the DCC this is a read only field showing the relevant shelf/card/port.

.
Issue:1
COMMUNICATION
To read a MESA:
* Select the MESA then choose the item Action-Read MESA.
In the window that will appear there are the Mesa details:
See Also:
Communication: add MESA/RANGE

Path (Action-Add/Read MESA/RANGE)
As described previously, with this type of static route it is possible to configure, on a given circuit, up
to three sets of ES identifiers (system Ids) for each of which a manual End System adjacency is
created on the circuit.
The constraint on the identifiers is that they must all be contiguous, so that it is possible to enter just
the start and the width of the range.
When static routes are configured on DCCs, the DXC still uses dynamic IS-IS and ES-IS routing
strategies towards the remaining part of the network (including the NMS).
It is possible to add a MESA Range on DCCs only.
To add a MESA Range:

* After selecting the option (Action-Add MESA/RANGE) click on the DCC where the
MESA Range has to be read.

.
Issue:1
COMMUNICATION
* Assign a manual adjacencies identifier using the arrow buttons in the RA Identifier field
(range 1 to 512).
* Insert the starting System Id address for each MESA range.
* For each set of ES identifier (System Id) specify the Range.
To read a MESA range:

* Select the MESA range then choose (Action-Read MESA/RANGE).
In the window that will appear the MESA range details will be displayed:
See Also:
Communication: delete RAP/MESA

Path (Action-Delete RAP/MESA)
Use this option to delete a RAP, a MESA or a MESA Range.
COMMUNICATION: DCC PROFILES CONFIGURATION

Path (Equipment Configuration-Communication Configuration-Profiles Configuration-DCC
Profiles)
A DCC profile is a set of values for the OSI stack parameters related to a DCC Interface. The DDCr
are associated to the profile 1 while the DCCm are associated to the profile 2. Both profiles contain
the default values for all the parameters.
IMPORTANT If the profile 1 and the profile 2 are changed from the default configuration, they
will not have the default configuration when new DCCs will be created.

.
Issue:1
COMMUNICATION
Communication: manage DCC profile

Path (Action-Read/Modify/Add)
This option allows the configuration of layer 2 and layer 3 protocols for a given DCC profile (existing
or a new one). Each data communication channel (DCC) embedded in an STM-N frame connected
to the DXC equipment is associated to a DCC profile.
NOTICE Only network experts are supposed to tune these parameters: erroneous
configurations can lead to misfunctioning on the NE or the entire network. Some
of the following parameters cannot be set indipendently from the others but must
satisfy inequalities known by network skilled people.
To add a DCC profile:

After selecting the option Action-Add
* Assign a DCC profile identifier (Id). Eight different profiles can be created.
* Define the DCC physical interface to which this profile will be associated. This
parameter is actually a layer 1 parameter, and describes the physical channel used for
this DCC, which may be the RS_DCC (D1-D3), or the MS_DCC (D4-D12) channel.
* Set the LAPD modulo of operation; it can be either 8 or 128.
* Set the Window size on LAPD (k). The range is: [0-7], if lapd module is 8, and [0-127] if
lapd module is 128. The default value is 7
* Define the level 1 default metric This is the default level 1 circuit metric value. This
parameter says the cost of using this circuit to the level 1 routing algorithm.

.
Issue:1
COMMUNICATION
* Set the external domain attribute for the DCC channel. If this attribute is set to enable,
neither IS-IS nor ES-IS routing PDUs are sent or processed when received on this circuit.
* Set the maximum layer 3 packet size supported. This is the maximum size of data
packets generated by layer 3 on this circuit, in bytes.
* Modify the ISIS Hello Timer parameter to define the default interval of generation of the
ISIS Hello PDUs (in seconds). It is just performed to reduce the overhead traffic on
ethernet.
* Define the retransmission count on LAPD (n200). This is the number of times that a
message is retransmitted on LAPD when it is not acknowledged by the partner.
* Define the maximum length of the LAPD frame size, in bytes . This parameter acts as a
limit on the size of messages which may be transmitted or received on LAPD. If a
message exceeds the limit, it is discarded on both transmission and reception sides.
* Select the ISO 9542 options. This is the bit mask for the ISO 9542 (ESIS) functions
supported These functions are related to the collection of End and Intermediate Systems
attached to a single Subnetwork, defined in terms of the system types, NSAP addresses
present, Network Entities present, and to the correspondence between systems and
SNPA addresses. In particular can be set:
configuration
Configuration function permits End Systems to discover the existence and reachability of
Intermediate Systems and permits Intermediate Systems to discover the existence and reachability
of End Systems.
redirect
Route redirection function allows Intermediate Systems to inform End Systems of (potentially)
better paths to use when forwarding NPDUs to a particular destination.
notification
Report configuration function is used by End Systems and Intermediate Systems to inform each
other of their reachability and current subnetwork address(es).
checksum
The protocol error processing function checks if the PDU encoding is correct. Any protocol error
PDU will be discarded.
* Set the lapd congestion timer. This is the maximum time to wait for a congested link to
become uncongested, expressed in tenth of seconds.
* Set the retransmit timer on LAPD (t200), expressed in tenths of second. This is the time
waited for by the system before re-transmitting an unacknowledged packet. The range is
[1-400] (but must be smaller than t203), the default is 10 (1 second).
* Set LAPD idle timer (t203), expressed in tenths of second. The range is [t200-400], the
default is 96 (15 seconds).
* Modify the IS configuration timer (default ISO 9542 IS configuration timer).The shorter
the Configuration Timer, the more quickly other systems on the subnetwork will become
aware when the reporting system becomes available or unavailable (Intermediate
System Hello packet generation timer).

.
Issue:1
COMMUNICATION
* Modify the ES configuration timer (default ISO 9542 ES configuration timer).The shorter
aware when the reporting system becomes available or unavailable (End System Hello
packet generation timer).
* Modify the default ISO 9542 holding time multiplier.
* Press APPLY
To read a DCC profile:

Select the option Action-Read
* Press CLOSE to exit
See Also:
Communication: set global parameters, Communication: configuring DCC
COMMUNICATION: ETHERNET PROFILES CONFIGURATION

Path (Equipment Configuration-Communication Configuration-Profiles Configuration-
Ethernet Profiles)
Eight Ethernet Profiles are available. A profile represents a configuration of the ethernet circuit
parameters (metric values, ISO 9542 timers and options, maximum packet size managed, router
priorities). Each profile can be modified according to the DCN characteristics.

.
Issue:1
COMMUNICATION
Communication: manage ethernet profile

Path (Action-Read/Modify/Add)
This option allows the configuration of layer 2 and layer 3 protocols for a given ethernet circuit. Each
Q interface is associated to an ethernet profile.
To add/modify an ethernet profile:

After selecting the option Action-Add/Modify
* Assign an Ethernet Profile Identifier (Id). Eight different profiles can be created.
* Set the external domain attribute for the DCC channel. If this attribute is set to enable,
neither IS-IS nor ES-IS routing PDUs are sent or processed when received on this circuit.
* Select the ISO 9542 options. This is the bit mask for the ISO 9542 (ESIS) functions
supported These functions are related to the collection of End and Intermediate Systems
attached to a single Subnetwork, defined in terms of the system types, NSAP addresses
present, Network Entities present, and to the correspondence between systems and
SNPA addresses. In particular can be set:
configuration
Configuration function permits End Systems to discover the existence and reachability of
Intermediate Systems and permits Intermediate Systems to discover the existence and reachability
of End Systems.

.
Issue:1
COMMUNICATION
redirect
Route redirection function allows Intermediate Systems to inform End Systems of (potentially)
better paths to use when forwarding NPDUs to a particular destination.
notification
Report configuration function is used by End Systems and Intermediate Systems to inform each
other of their reachability and current subnetwork address(es).
checksum
The protocol error processing function checks if the PDU encoding is correct. Any protocol error
PDU will be discarded.
* Set the Level 2 status for the ethernet circuit (Level 2 only circuit). If the level 2 status is
enabled, the system will only act as a level 2 router, not as level 1 router.
* Assign the level 1 designated router priority (priority to become the level 1 designated
router).
* Assign the level 2 designated router priority (priority to become the level 2 designated
router).
* Define the ISO 9542 redirect timer, in seconds
* Define the IS configuration timer (default ISO 9542 IS configuration timer).The shorter
aware when the reporting system becomes available or unavailable (Intermediate
System Hello packet generation timer).
* Define the ES configuration timer (default ISO 9542 ES configuration timer).The shorter
aware when the reporting system becomes available or unavailable (End System Hello
packet generation timer).
* Define the ISO 9542 holding time multiplier.
* Press APPLY.
To read an ethernet profile:

After selecting the option Action-Read.
See Also:

.
Issue:1
COMMUNICATION
COMMUNICATION: ROUTER PROFILES CONFIGURATION

Router Profiles)
A router profile is a set of values for the layer 3 protocol parameters related to each router entity in
the equipment (Communication and Port Controller Units of the DXC). Two Router Profiles are
available in order to maintain the possibility to modify independently the router parameters for the
two resources: main and auxiliary.

.
Issue:1
COMMUNICATION
Communication: manage router profile

Path (Action-Read/Modify)
This option allows the configuration of the parameter template for the routers present in the DXC
equipment: Communication and Port Controller Units. Note that modifying any value the same
modification will be applied to all routers using it.
To add/modify a router profile:

After selecting the option Action-Modify
* Set partition repair state (IS-IS partition repair enabling as defined in the ISO 10589
Recommendation).This is a read only field.
* Define the system id length (system Id length, within the NSAP address, in bytes). This
is a read only value set to 6 bytes.
Note All the systems within a ISIS domain must have the same length for the System Id.
* Set the Complete snp Interval (Complete Sequence Number PDU interval, in seconds).
* Set the Partial snp Interval (Partial Sequence Number PDU interval, in seconds).
* Define the Max Paths Split (maximum number of equal cost paths which are recorded
by the decision process).
* Define the Max Area Addresses This is the maximum number of Area Addresses
handled by the router.

.
Issue:1
COMMUNICATION
Note Not that, anyway, a maximum number of 3 addresses may be configured on this
equipment. The only use of this parameter is that, within an area, all the level 1
Intermediate System must have the same value for it (note that the parameter value is
output within the IS-IS PDUs).
* Set the Max Virtual Adjacencies (maximum number of virtual adjacencies). Virtual
adjacencies are used for Partition Repair.
* Set the poll es hello rate (End System Hello rate as defined in the ISO 9542
Recommendation).
* Set the waiting time (Waiting time as defined in the Recommendation ISO 10589).
* Select the ISO 8473 options. This is the bit mask for the CNLS options supported. In
particular can be set:
Complete Src Rtg
Complete Source Routing supported. The PDU has to follow the path specified by the originating
End System. This path is a list of Intermediate System NE titles and the destination is not included.
The PDU will pass through the ISs present in the list and in the same order. If the specified path
cannot be taken, the PDU will be discarded.
Partial Src Rtg
Partial Source Routing supported. As in complete source routing, the PDU pass through the ISs
present in the list and in the order specified but, in this case the PDU can take any necessary path
to reach the next IS in the list, also IS not included in the list. The PDU will not be discarded unless
one of the systems can not be reached from any available path.
Error Report Flag
Set Error Report flags in originated Data NPDUs. The originator of a PDU controls the generation
of Error Report PDUs. An Error Report flag in the originated PDU is set by the source to indicate
that an Error Report PDU has to be returned if the initial PDU or any PDUs derived from it are
discarded; if the flag is not set, Error Report are not generated.
US GOSIP V1
US GOSIP V1 Unclassified Security supported.
US GOSIP Vd21
US GOSIP Vd21 Unclassified Security supported
* Define the ISO 8473 Clnp Checksum state (checksum of the originated ISO 8473 data
packets).
* Set the designated router isis hello timer.
* Set the clnp lifetime (Lifetime of the originated packets, as described in ISO 8473).
* Set the Originating Level1 lsp Buffer Size.
* Set the Originating Level2 lsp Buffer Size.
* Press APPLY
To read a router profile:

After selecting the option Action-Read
See Also:

.
Issue:1
COMMUNICATION
COMMUNICATION: TRANSPORT PROFILES CONFIGURATION

Transport Profiles-Read/Setup)
This option allows the Transport Module configuration.
All the changes performed at this level are just performed to make the Transport connection more
stable, and producing a lesser overhead traffic for OSI layers 3 and 4. This means that a Link Down
event may take more time to be discovered, though.
To setup a transport profile:

* Configure the Inactivity Timer This parameter describes the amount of time that
Transport maintains a layer 4 connection on which no data is being transferred, before it
terminates the connection. It is expressed in tenths of second.
* Set the Lower Bound For Retransmit Timer The range is: [1-<UpperRetransmitTime>]
* Set the Upper Bound For Retransmit Timer The range is: [<LowerRetransmitTime>-
65535]
* Configure the Initial Retransmit Timer This parameter describes the amount of time that
Transport initially waits without receiving a TPDUs acknowledgement, before it
retransmits the TPDU. Transport automatically adjusts this parameter individually for
each connection, based on peer entity responsiveness (and, implicitly, network
performance). The range is: [<LowerRetransmitTime>-<UpperRetransmitTime>]

.
Issue:1
COMMUNICATION
* Configure the Window Timer This parameter describes the period of inactivity that can
occur before Transport sends a hello packet to the peer entity where a connection is
established (in tenths of second). It must be bigger than the Local Acknowledgement
delay (note that the Local Acknowledgement delay is expressed in milliseconds).
* Configure the Local Acknowledgement Delay This parameter describes the maximum
amount of time that Transport can delay the acknowledgement of a received TPDU (in
milliseconds). It must be lower than the Window Timer (note that the Window Timer is
expressed in tenths of seconds).
* Set the Local Flow Control Interval This parameter describes the available resources
checking interval (in milliseconds). If Transport has no receive credit available, it checks
the available resources each time the interval specified by this parameter has passed,
until credit becomes available.
* Set the Initial Window Size This parameter describes the initial number of
unacknowledged TPDUs that can be outstanding on a connection. Transport will
automatically adjust the window size up to the Credit Value.
* Set the Max Retransmit Count This parameter describes the maximum number of times
that the local transport entity will retry to transmit a TPDU that requires
acknowledgement.
* Set the credit (target window size) This parameter describes the expected window size,
that is, a target value for the maximum number of unacknowledged TPDUs that can be
outstanding on a connection.
* Set the max tpdu size.
To read a transport profile:

After selecting the option Action-Read
See Also:

.
Issue:1
EM DATABASE: MANAGING DXC
EM DATABASE: UPLOADING/DOWNLOADING
Path (Database-Realignment) [NM]
This option is used to upload/download equipment configuration stored in the NE into the EM
database.
The upload operation may be necessary in case of a misalignment between the EM and the DXC
databases or during the provisioning of a new NE. In the latter case the configuration stored within
the DXC (using the Control Application) must be loaded in the EM database by means of this
functionality.
To upload NE database:
* Select DATABASE UPLOAD (all NEs configuration)
* Press APPLY
EM database. Then a DATABASE UPLOAD (all NEs configuration) operation
from EM will not get any OSI and NSAP data.
To upload only the NEs cross-connections:

* Select DATABASE UPLOAD (only X-Conn)
* Press APPLY

.
Issue:1
To upload only the NEs alarm configuration parameters (category, priority):

* Select DATABASE UPLOAD (only Alarm Monitoring)
* Press APPLY
To download the database on a already decommissioned NE:

Before activate this operation be careful that the NE have been partial decommissioned by the
Control Application.
* Select DOWNLOAD (NE already decommissioned)
* Press APPLY
To download the database on a not decommissioned NE:

The NE is automatically decommissioned, the database is downloaded and then the NE is restarted
without activating the downloaded configuration (controller off-line).
* Select DOWNLOAD (automatic decommissioning - restart offline)
* Press APPLY
EM database. A DOWNLOAD operation from EM will download configuration
parameters only, not any OSI and NSAP data (that will be not overwritten). In
order to restore OSI data a database download from LCT will be necessary.
To download only the NEs alarm configuration parameters (category, priority):

* Select DOWNLOAD (only Alarm Monitoring)
* Press APPLY
See Also:
Managing Subrack Configuration, EM Database: passing through mode

.
Issue:1
EM DATABASE: PASSING THROUGH MODE

Path (Database-Pass Through) [NM]
This option is used for disabling the EM database from the management of the DXC. When
PassThrough mode is active every request is directly forwarded to the Network Element without
read/write on the EM database.
IMPORTANT To enable or disable the PassThrough mode you have to be single user on that
DXC, belong to nmcgroup and the NE must have the Don't Send To NE mode
set to OFF.
To enable or disable the PassThrough mode:

* Open the GUI (Graphical User Interface) for a DXC.
* Select the button PassThrough from Database menu.
* Use Passthrough mode push-button to select the database status:
ON
EM database disabled.
OFF
EM database enabled.
* Press APPLY.
See Also:
EM Database: uploading/downloading

.
Issue:1
EM DATABASE: CHECKING ALIGNMENT

Path (DataBase-Check DB Alignment) [NM]
This option is used to verify the alignment state between the DXC database at NE layer and the
DXC database at EM layer. At the end of the test an information window that inform the user on the
check result is displayed.
IMPORTANT After a EM DB Restore a manual alignment of the equipment configuration DB is

suggested. According to the required configuration an upload or download
command should be performed.
See Also:
EM Database: uploading/downloading
ISSUE OF EM MESSAGES TOWARDS THE NES

Path (Database-DontSendToNE)[NM]
This option is used to enable/disable the EM-DXC messages sent to the DXC. When messages to
current NE are disabled, modifications in the network are stored only in the EM-DXC database
without modifying this current NE database.
IMPORTANT If commands have been disabled no messages are sent to the specific NE. This
causes a misalignment of the EM-DXC and the specific NE database. Never
attempt to use this option during normal operation of the network.
To enable/disable issue of EM commands:

* Be sure to be single user on your DXC, be sure your user belongs to nmc group, be sure
PassThrough mode is OFF
* Open the DXC-GUI.
* Press the DontSendToNE button from Database menu.
* Select ON and then press Apply.
The string DONT SEND TO NE MODE: ON will appear in a message box.

If you try to enable Don't Send To NE mode and you are not single user or PassThrough mode is
ON or your user does not belong to nmc group, a proper message box is displayed.
See Also:
EM Database: passing through mode

.
Issue:1
PORT LABEL MANAGEMENT

Path (Equipment Configuration-Port Configuration- Port Label Management)[NM]
The option is used to associate a mnemonic name to a physical port on the cross connect
equipment. The physical name of the port can be retrieved at any time by means of the same
command.
The logic port labels defined can be then used in the DXC Element Manager to rapidly select the
correspondent port. Also a quality data collection can be planned on logical port basis.
To enable the Port Label management internally at EM-DXC is essential to set the environmental
variable PORT_LABEL_CONFIGURATION and BT_ PORT_LABEL_CONFIGURATION in the
opportune way.
The setting of these variables has to be done after EM-DXC installation (by default the
management is disable).
Three different case are possible:
1. PORT_LABEL_CONFIGURATION 0
BT_PORT_LABEL_CONFIGURATION 0
Port Label management disable
Port Label management enable
Port Label management for BT enable
At start-up time an extra window is arranged with the main menu. This have the purpose of listing
the logical ports which have been used to select physical ports as explained in the following. At the
beginning the window is empty.

.
Issue:1
Together with the windows related to the usage of ports, the selection window is automatically
displayed. It can be quitted using the CLOSE push-button if its usage is not needed. A menu item is
otherwise available among the pull-down options to call back the window when required.
To select a port:
* Use Port Label to choose the logical name assigned to the port. The list includes all the
names defined. After the selection is made the port location is displayed in the Subrack
Id, Card Id and Port Id.
* Press APPLY.
The port chosen is selected by the system inside the current working window. The selected logical
name is then written in the monitor window.
Once the "PORT LABEL SELECTION" window is open, if there are no port labels on NE, FILTER
and SEARCH push buttons will be grayed out. Otherwise, if at least one port label have been
created on NE, the two buttons named above will be active.
FILTER works such as UNIX "grep" command: the Operator has to insert a string and clicking on
FILTER push button the UH interface will return all port labels containing the string specified;
To operate a SEARCH the Operator has to insert a Subrack_Id, Card_Id and Port_Id in the right
boxes. By clicking on the SEARCH push button the port label matching inserted data will be shown;
if the three inserted values do not match any existing port label, a "NOT FOUND" message box will
be visualized.

.
Issue:1
To create a port label:

* Select the subrack, the card, the port and the Port Label Management option.
Note In the Port Label Management for BT is possible to create a Port Label on an
equipped port, in other case the port has to be configured.
* Insert the string for the Port Label.
* Press APPLY.
To remove a port label:

* Select the subrack, the card and the Port Label Management menu from the Graphical
User Interface (GUI) of EM-DXC.
* Insert an empty string.
* Press APPLY.
Note The Port Label Selection that defines the list of Port Label setted is displayed in the
following Graphical User Interface (GUI):
Card Commissioning
Port Configuration
Subrack Protection Management
DXC Type III Protection
Subrack Syncronization Sources
Loopback Test
Cross Connection Management
Path Protection Management
Tandem Connection Management
Alarm Monitoring
Performance Monitoring.

.
Issue:1
HOW TO...
This chapter contains additional information to configure and use the Control Application.
Once a Login operation is performed for the first time or after a database decommissioning, the
DXC is fully unequipped.
In the following the configuration procedures, in chronological order, are listed.
IMPORTANT Between steps verify the presence of alarms and eventually fix them.
CONFIGURATIONS
This paragraph is a collection of procedures used to configure and the main subsystems of the
equipment: Control, Synchronization, Communication and Cross Connection. Furthermore some
basic test functions are indicated.
Commission the System

In order to commission the system the Operator has to perform the steps listed below:
Select the NE (Network Element) Model
The Operator has to select the right NE Type (Matrix Size). The NE Type has to be configured
according to the CCU software.
The following executable file types are supported:
CCU_8x04SW
Supported NE Model : MSH80/83/84/86
Database Size : MSH86
Run on : 131-7404/04
CCU_9x04SW
Supported NE Model : MSH91/96
Database Size : MSH96
Run on : 131-7404/04
If the Operator tries to define a NE Type not supported by the CCU software, the message "Not
Supported" will be displayed.
See Also:
NE Model: selection
Define location and alarm interface
For all the DXC equipment the management of the rack alarm unit, ground contacts and virtual
lamps can be selected in the Local Alarm Interface list. Optionally the system location name can
be stored in the equipment memory (MEM).
See Also:
NE Model: defining location and alarm interface

.
Issue:1
HOW TO...
Commission the Control and Timing Subrack

The first subrack to be equipped is the Control and Timing. The Operator must commission the
following units: Serial Expansion Unit, Timing Selector Oscillator Unit, and Communication and Q
Interface Unit (if used).
All the other units are automatically equipped by the system.
See Also:
Control and Timing Subrack: commissioning, Control and Timing Subrack: equipping
Commission Matrix Subracks
To configure the Matrix Subracks the Operator must specify the number of first stage and third
stage units fitted.
See Also:
Matrix Subrack: commissioning (DXC 4/1), Matrix Subrack: equipping unit (DXC 4/1),
General Index
Commission Port Subracks
For each Port Subrack the Operator must specify:
* the Subrack Id number that is the same number displayed on the Identification Unit.
* the Matrix Accesses used by the Port Subrack for transmitting internal data stream from
ports to matrices and vice-versa.
NOTICE If the MSP 1+1 architecture is required the protection units accesses have to be
not equipped.
* the Serial Line used by the control system to manage the Port Subrack.
* In case of type 6, the protection managed by the subrack (Prot. Type Supp. - Protection
Type Supported).
Note that equipping a Port Subracks the Unexpected Unit alarm raises for each Tributary Unit
present in the subrack.
See Also:
Type 2 Subrack: commissioning, Type 3 Subrack: commissioning, General Index,
Type 5 Subrack: commissioning, Type 6 Subrack: commissioning, Type 6E Subrack:
commissioning, Type 7 Subrack: commissioning, Type 7E Subrack: commissioning
Commission Units
For each Port Subrack all the Tributary Units must be commissioned. This action informs the control
system about the type of the unit fitted in a certain slot in the subrack.
See Also:
Unit: commissioning, Unit: equipping (DXC 4/1), Port: configuration, Port:
configuring operational parameter
Note that this action will clear the correspondent Unexpected Unit alarm.

.
Issue:1
HOW TO...
Set NE Date and Time

Set the date and time used by the DXC internal clock.
See Also:
System: setting NE date and time
Check the Software Release
Verify the software release compatibility on the units present in the subracks using the built-in test.
See Also:
System: checking the software release, System: checking subrack software release,
System: checking equipment software details
Run the Matrix and Port Subrack Test
Run the Matrix Global test and the Port Subrack link test in order to verify the matrix equipment
(units and internal subrack links) and the cable connecting the port subracks to matrices.
To perform the Matrix Global or/and Subrack Link Test the Operator has to:
1. Perform a forced switch on the matrix not involved in the test;
2. Enable the Test State on the matrix where the test has to be launched;
3. Activate the test.
This is the correct sequence of actions to start a test session on the matrix. Once a test session has
been completed the Operator has to:
1. Disable the Test State;
2. Perform a clear switch on the matrix.
See Also:
Matrix Subrack Test: activating (DXC 4/1), Port/Matrix Subrack Link Test: activation
(DXC 4/1), General Index
Define Operational Parameters for the Ports
Configure all the operational parameters for the ports that are going to carry traffic. Once a port is
configured the network alarm detection will be enabled.
Remember that for Type 3, 6, 7, 6E and 7E Port Subracks, in order to automatically mask the LOS
alarm for not used ports, there is the Port Mode facility.
NOTICE In case of NxSTM-1 or 4x155-140Mbit/s unit protection (1:N) group the

protection unit ports have to be "not configured".
See Also:
Port: configuration, Port: configuring operational parameter, STM-1 Port: setting
HPOM alarm suppression state, STM-1 Type 2 Port: setting C2 mismatch detection
state, STM-N Port: configuring VC-4 operational parameter, STM-N Port: configuring
frame and supervisory unequipped state, Alarms: port mode

.
Issue:1
HOW TO...
Filter the Free PDH Port Faults

If requested, the Monitoring of the Network Alarm detected by the configured PDH ports in Type 2 ,
Type 4 and Type 5 Port Subracks, not yet cross-connected, can be disabled.
This facility is also available for Type 3 Port Subrack and for 4xSTM-1/140Mbit/s units.
See Also:
Alarms: filtering of the free PDH ports fault
Configure Protections in Port Subracks
Configure all the MSP (STM-N, NxSTM-1 and 4x155-140Mbit/s Units), Line (3x34/45Mbit/s,
140Mbit/s Line Protection) and Unit (1x45Mbit/s T-Mux, 16x2Mbit/s, 63x2Mbit/s, 4x34Mbit/s
Videocodec, 4x34Mbit/s T-Mux, 3x34/45Mbit/s, NxSTM-1 and 4x155-140Mbit/s Unit Protection)
Protections needed.
See Also:
Port Subrack Protection: selection, Multiplexing Section Protection: configuring, Port
Subrack Protection: setting the WTR period
The system is now commissioned and ready for carrying traffic. The system oscillator is in free
running mode.
Configure the Synchronization

In order to synchronise the system oscillator it is necessary to follow the steps listed below.
n Define a Port as Synchronization Source: define an incoming data stream as available
synchronisation source. Note that the relevant port must be configured;
n Set the Synchronisation Priority Table for the System Oscillator: define the priority table for
the system oscillator;
n Configure the Synchronisation Mode for the System Oscillator: configure the
synchronisation mode. The oscillator will be able to use the synchronisation source specified
in the priority table in revertive or not revertive way;
n Define the Synchronisation Priority Table and the Synchronisation Mode for the External
Output Oscillator.
Perform same steps for synchronising external output oscillator.
The latter is able to provide a clock signal (2KHz or 2Mbit/s) for synchronising external equipment.
After the system is synchronised using a valid reference clock source, verify the correct operational
mode of the internal PLL checking the PLL cut frequency.
See Also:
SYNCHRONIZATION

.
Issue:1
HOW TO...
Configure Communication Parameter

To enable the communication to the NMC, the following steps must be performed.
Set the NSAP and MAC addresses
First of all the Operator has to specify from which resource the DCC will be managed. The DCCs
can be routed by the Communication Units (centralised routing) or by the Port Controller Units
(distributed routing).
In the centralised routing (default) the communication function is fully provided by the
Communication Unit.
With the distributed routing feature the Port Controllers now become stand-alone OSI routers and
each contains a full 3-layer protocol stack. The DXC therefore becomes a collection of routers, each
with their own layer-3 address (NSAP).
To define the routing mode for each subrack it is necessary to assign NSAP and the MAC
addresses to each entity able to act as OSI router: Communication Units and Port Controllers.
See Also:
Configure DCC
Enable the DCC management in all the required SDH ports.
The port must be configured.
To configure the DCC the Operator has to specify:
1. the DCC type (DCCm or DCCr);
2. the DCC LAPD side (User or Network);
3. the Communication Card (Providing Service or Auxiliary) that handles the DCC from a routing
point of view;
4. the protection state of the DCC (protected or not protected);
5. if it will be protected at Port Controller Level
When the load sharing is not enabled or one of the two Communication Card is not running Not
protected DCC are not handled, while, if the OSI protocol stack is started and at least one
Communication Card is working, protected DCC are always handled.
See Also:
Communication: configuring DCC
Enable Communication
Enable the communication protocol stack.
See Also:

.
Issue:1
HOW TO...
Manage Cross-Connections
Create Cross-Connections
The ports involved in the cross-connection have to be configured. In order to make the cross-
connection the Operator must select the first and the second port. In the unidirectional or broadcast
cross-connection the selection order is important because establishes the direction of the data traffic
(source->destination - master->leg).
See Also:
Cross-Connections: management (DXC 4/1), General Index
Configure Sub-Network Connection Protection
The SNCP can be configured on a VC-n channel already cross-connected. The Operator must
select the VC-n channel in the SDH port (STM-N) to be protected and then the protection one (on
another STM-N port).
See Also:
SNC Protection: managing (DXC 4/1), SNC Protection: configuring (DXC 4/1), General
Index
Manage Alarms
Display and Acknowledge the Active Alarm in Each Subrack and Unit
There are three different ways to get the alarm list:
* On equipment basis;
* On subrack basis;
* On unit basis.
Moreover the Operator can acknowledge alarms (all in one shot or one by one).
See Also:
Alarms: displaying subracks/units active alarms, Alarms: displaying subrack active
alarms, Active Alarms: acknowledgement push-button, Active Alarms: displaying
alarmed unit, Active Alarms: displaying unit active alarms
Manage the Event History File
If the PC running the Control Application is connected the alarm messages are stored in files
(history).
See Also:
Alarms: managing the event history file, Alarms: removing the selected file, Alarms:
displaying the alarm history file, Alarms: removing all alarm history files

.
Issue:1
HOW TO...
Configure Performance Monitoring

The quality data collection can be started on each configured Tributary Unit.
Enable Performance Data Collection / Exception
This option is used to start a "Maintenance" or "Service" based collection on a selected resource.
Furthermore it`s possible to specify which set and type of exception events have to be reported.
Maintenance based mode counts the performance parameter over both 24h and 15m time periods
(both the 24h and 15m register are generated). This kind of evaluation is based on information
relevant to each direction of transport independently then it`s possible to define the transmit side to
be monitored (Near End and/or Far End termination collection reporting).
Service based mode counts the performance parameter over 24h time period only (only the 24h
register is generated). This kind of evaluation is based on information relevant to both direction of
transport together then the performance data collection is started/stopped at the same time on both
the transmit sides (Near End and, if it exists, Far End termination).
See Also:
Performance: managing data collection, Performance: displaying started monitored
entities
Manage Data Displaying
The quality data can be read by means of the current/previous/recent register.
See Also:
Performance: managing data displaying

.
Issue:1
HOW TO...
HOW TO SELECT OBJECTS

A Selection Window is a window used to select different objects (e.g.: subracks, units, ports,
etc.).
A Selection Window consists of the following parts:

1. Menu Selection;
2. Object Selection (e.g.: Subrack, Unit, Port, AUG or channel);
3. Information Boxes.
Object Selection
To select a subrack (e.g.: a port subrack) proceed as follows.

Operator can select a subrack using the graphic representation of the rack (Rack Layout).
* Position the mouse on the subrack (if subrack is not shown in the box use the scroll-bar
to move left or right the subracks).
* Click with the left-hand mouse button. The selected subrack becomes darker.

.
Issue:1
HOW TO...
..or using the list.
* Position the mouse on the subrack.

* Click with the left-hand mouse button. The selected subrack is displayed in reverse video.
IMPORTANT Only subracks used for the running action can be selected (e.g.: only port
subracks can be selected when configuring the ports). Unused subracks cannot
be selected (they are indicated with grey labels in the graphic representation and
they are not listed).
To select a unit (e.g.: a 140Mbit/s Tributary Unit) proceed as follows.

Operator can select a unit using the graphic representation of the subrack (Cards Layout).
* Position the mouse on the unit (if unit is not shown in the box use the scroll-bar to move
left or right the units).
* Click with the left-hand mouse button. The selected unit becomes darker.

.
Issue:1
HOW TO...
..or using the list.

* Position the mouse on the unit.
* Click with the left-hand mouse button. The selected unit is displayed in reverse video.
IMPORTANT Only units used for the running action can be selected (e.g.: only tributary units
can be selected when configuring the ports). Unused units cannot be selected
(they are indicated with grey labels in the graphic representation and they are
not listed).
To select a port proceed as follows.

* Position the mouse on the port.
* Click with the left-hand mouse button. The selected port is displayed in reverse video.
To select a channel or a AUG proceed as follows.

* Position the mouse on the channel/AUG (if the channel/AUG is not shown in the box use
the scroll-bar to scroll up or down the list).
* Click with the left-hand mouse button. The selected channel/AUG is displayed in reverse
video.

It is possible to print the information displayed for some report windows on a system printer
connected to the Personal Computer (or available in the network). Alternatively the Operator can

.
Issue:1
HOW TO...
decide to print the information on a file. Depending on the Operating System on which the Control
Application is based, two different procedures are available.
Printing on SCO/UNIX environment
Using the Control Application based on SCO/UNIX environment the PRINT push button is not
available. Instead of it two different menu can be accessed in order to:
n send information to the system printer,
n copy the information on a selected file.
To send the information to the system printer:

Position the mouse on area where the information to be printed are displayed.
* Click the right-hand mouse button.
* Select option Print.
Screen
The information displayed in the current screen are sent to the printer (only for postscript printers).
List
All the information available in the current screen (also those available using the scroll bars) are
sent to the printer (available for all types of printers).
To copy the information on a selected file:

Position the mouse on area where the information to be printed are displayed.
* Click the right-hand mouse button.
* Select option Copy To File.
Screen
The information displayed in the current screen are copied to the selected file (the output is a
postscript file). Only information displayed in the window are copied!
List
All the information available in the current screen (also those available using the scroll bars) are
copied in a file (ASCII format).
* Select the file.
* Press OK.
Printing on Windows NT environment
The information displayed for some report windows can be printed using the PRINT push button.
Further than the system printer connected to the Personal Computer (or available in the network),
the output is sent also in a file named PRINT.TXT in the log directory.

.
Issue:1
HOW TO...

This window is used to select a file. The same window is used for different options every time that a
file selection is needed.
To select a file:
* Select the directory where files are located (DIR.) and then the file (FILES).
* Press OK.
Select FILTER to change the types of files displayed according to the selected filter.
How to save the alarm log files in word format

The alarm log has a maximum size of 1000 events and it is managed in wrap-around mode: when
the log is full, incoming events overwrite the old ones.
In order to keep an archive the alarm log file can be saved on the PC hard disk (or on a different
media) as a text file (by means of the Control Application).
This test file could be not correctly formatted (no right spacing between the words).
In the following is given the procedure to obtain this file and to save it as a word document (a file
type which page format can be simply managed).
In particular the procedure changes depending on the Operating System used.
How to save the log file as a Word document in UNIX O.S.:

Note Word application can be used on a Windows PC only.
1. Open the alarm log window
See Also:

.
Issue:1
HOW TO...

2. Push repeatedly the MORE push button till` all the report ends (MORE push button
disappears).
3. Position the mouse pointer on the event or alarm area.
4. Click the right-hand mouse button.
5. Select option Copy To File > List
See Also:
6. Define the destination directory and the file name.
See Also:
7. Open a UNIX shell by double clicking on the UNIX icon on the desktop.
8. Go to the directory where the file has been saved.
9. Verify that the file is present by using the ls command.
10. Insert a floppy disk formatted in DOS mode in the correct drive.
11. Type the command:
doscp <file name> <drive letter>:
12. Verify the content of the floppy disk by using the command:
dosdir <drive letter>:
13. Insert the floppy disk in the correct drive of a Windows PC.
14. Launch Microsoft Word application.
15. Open the file contained in the floppy disk by selecting the option: File -> Open
16. Save the file as a Word Document choosing a directory in the hard disk.

.
Issue:1
HOW TO...
How to save the log file as a Word document in Windows O.S.:

1. Open the alarm log window.
See Also:
2. Push repeatedly the MORE push button till` all the report ends (MORE push button
disappears).
3. Disconnect the system printer (in order to avoid an undesired printout) and click on the PRINT
push button.
Using Application Software release greater than 7.x an error message will appear.
Further than the system printer connected to the Personal Computer (or available in the
network), the output is sent also in a file named PRINT.TXT in the log directory.
See Also:
4. Launch Microsoft Word application.
5. Open the PRINT.TXT file by selecting the option: File -> Open
6. Save the file as a Word Document choosing a directory in the hard disk.
IMPORTANT PRINT.TXT file is replaced each time a print command is selected.

.
Issue:1
.
Issue:1

Marconi MSH 86x SLAT Procedures

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Marconi MSH 86x SLAT Procedures

Încărcat de

Drepturi de autor:

Formate disponibile

GENERAL INDEX

PRELIMINARY INFORMATION ........................................................................................... 31

USERS INTERFACE ............................................................................................................ 54

STARTING LOCAL CONTROLLER .................................................................................... 63

COPYRIGHT - Refer To Title Page Marconi

SCO/UNIX VERSION ..........................................................................................................................63

DXC MAIN MENU.................................................................................................................. 74

MANAGING SUBRACK CONFIGURATION ....................................................................... 79

COPYRIGHT - Refer To Title Page Marconi

Matrix Subrack: displaying software details (DXC 4/1) ....................................................................91

COPYRIGHT - Refer To Title Page Marconi

Type 6E Subrack: displaying software details................................................................................121

COPYRIGHT - Refer To Title Page Marconi

4x34Mbit/s Videocodec Port: displaying global parameters ..........................................................179

PROTECTION AND TEST .................................................................................................. 221

COPYRIGHT - Refer To Title Page Marconi

Multiplexing Section Protection: removing......................................................................................233

COPYRIGHT - Refer To Title Page Marconi

DXC Type Three Protection: configuring........................................................................................254

COPYRIGHT - Refer To Title Page Marconi

MANAGING CROSS-CONNECTIONS .............................................................................. 281

COPYRIGHT - Refer To Title Page Marconi

MANAGING ALARMS ........................................................................................................ 314

PERFORMANCE MONITORING........................................................................................ 330

COPYRIGHT - Refer To Title Page Marconi

PERFORMANCE: MANAGING DATA DISPLAYING ......................................................................337

SECURITY AND SYSTEM MANAGEMENT ..................................................................... 346

COPYRIGHT - Refer To Title Page Marconi

SYSTEM: DOWNLOADING SW ON AUXILIARY UNIT ..................................................................361

REAL-TIME MONITOR WINDOW...................................................................................... 379

FAULT DETECTION PROCEDURE .................................................................................. 385

COPYRIGHT - Refer To Title Page Marconi

SPI - SYNCHRONOUS PHYSICAL INTERFACE ALARMS............................................................385

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

PDH-LOF (140Mb) ..................................................................................................................427

COPYRIGHT - Refer To Title Page Marconi

RxSyncLoss (Mx1StU) .............................................................................................................439

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

UnitFail (PortUnit) ....................................................................................................................470

COPYRIGHT - Refer To Title Page Marconi

SubrackIdMismatch (IdU) ............................................................................................................481

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

SYNCSRC - TIMING SELECTOR-OSCILLATOR UNIT SYNCH SOURCES ALARMS ................514

COPYRIGHT - Refer To Title Page Marconi

COPYRIGHT - Refer To Title Page Marconi

EXC (NxSTM1_140) .............................................................................................................537

COPYRIGHT - Refer To Title Page Marconi

FAW-DEG (63x2MbPDHCh) [LC] .............................................................................................548

COPYRIGHT - Refer To Title Page Marconi

HP-EXC (VC4_4V) ...............................................................................................................562

COPYRIGHT - Refer To Title Page Marconi

Unit Internal Fault Trouble Shooting Procedure.............................................................................594

DATA DICTIONARY & MESSAGES.................................................................................. 600

COPYRIGHT - Refer To Title Page Marconi

Subrack Type ..................................................................................................................................619

EM DATABASE: MANAGING DXC................................................................................... 673

COPYRIGHT - Refer To Title Page Marconi

PORT LABEL MANAGEMENT .........................................................................................................677