AWY Operator Handbook

SWP 9400AWY R1.0 C.T. OPER.
HDBK
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HANDBOOK STRUCTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CAUTIONS TO AVOID EQUIPMENT DAMAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SECTION 1: INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1–1 SWP INSTALLATION IN PC ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1–1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1–1.1.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1–1.1.2 Operator skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1–1.2 Summary of SW installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1–1.3 SWP loading in PC WINDOWS–NT/2000/XP environment . . . . . . . . . . . . . . . . . . . . . . . 24
1–1.3.1 Installation of 1320CT + NE software from SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . 24
1–1.3.2 Installation of SIBDL program from SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1–1.3.3 End of SW installation from SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1–1.3.4 De–installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1–1.4 CT initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1–1.4.1 Craft Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1–1.4.2 Craft Terminal connection to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1–2 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

1–2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1–2.1.1 NE hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1–2.1.2 Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1–2.1.3 Operator skills and profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1–2.2 Summary of the SWP installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1–2.3 SW download to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
03 041222 S404102601 A.BESTETTI ITAVE G.ZILIANI RTT

A.FUMAGALLI E.CORRADINI–C.NAVA
02 040723 S404070501 A.FUMAGALLI ITAVE G.ZILIANI RTT
V.RODELLA E.CORRADINI–ITAVE
01 040519 A.FUMAGALLI ITAVE G.ZILIANI RTT
G.CONSONNI E.CORRADINI – ITAVE
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 – ALICE 04.10
9400AWY–FSO REL.1.0
SWP VERSION UP TO V1.0.2
OPERATOR’S HANDBOOK
ED 03
3DB 05653 CA AA 1 / 296
296
1–2.4 NE Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1–2.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
1–2.6 Configuration data definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

1–3 NE UPGRADE TO A NEWER SWP ’VERSION’ (SAME SWP ’RELEASE’) . . . . . . . . . . . . . . 75

SECTION 2: AWY/FSO NE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2–1.1 9400 AWY/FSO view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2–1.1.1 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2–1.1.2 Resource Tree Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
2–1.1.3 Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2–1.1.4 Button Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2–1.2 Introduction to the menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2–1.2.1 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
2–1.2.2 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2–1.2.3 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2–1.2.4 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2–1.2.5 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2–2 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2–2.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2–2.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2–2.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2–2.2.2 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2–2.2.3 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2–2.2.4 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2–2.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2–2.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2–2.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2–2.4.1 NE Configuration (V 1.0.0 and V 1.0.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2–2.4.2 NE Configuration (V 1.0.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
2–2.4.3 Link Indentifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2–2.4.4 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
2–2.5 Quick Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2–3 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

2–3.1 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2–3.1.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2–3.1.2 “1+0 extendable” and “1+1” configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
2–3.1.3 Procedure for configuration change from “1+0 extendable” to “1+1” . . . . . . . . . . . . . . 131
2–3.1.4 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
2–3.2 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
2–3.3 Tab panels in the Resource Detail Aarea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
2–3.3.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
2–3.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
2–3.3.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
2–4 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

2–4.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
2–4.1.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
1AA 00014 0004 (9007) A4 – ALICE 04.10
2–4.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
ED 03
3DB 05653 CA AA 2 / 296
296
2–5 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2–5.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2–5.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2–5.2.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2–5.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2–5.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2–5.3 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
2–5.3.1 Tx Radio Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
2–5.3.2 Rx Radio Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
2–5.4 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–5.4.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–5.4.2 Tx Nominal Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–5.4.3 Tx Current Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–5.4.4 ATPC Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2–5.4.5 ATPC Rx Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2–5.5 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2–5.5.1 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
2–6 FSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

2–6.1 Channel#1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
2–6.2 FSO Port#1 – Ch#1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
2–6.2.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
2–6.2.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
2–6.2.3 Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
2–6.3 Laser#1 or Laser#2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
2–7 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

2–7.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
2–7.2 Output External Points (in V.1.0.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
2–7.3 Output External Points (in V.1.0.1 and V.1.0.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
2–8 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

2–8.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
2–8.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . 167
2–8.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . . 168
2–8.2 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
2–8.3 SW key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
2–9 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

2–9.1 Mux Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
2–9.1.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
2–9.1.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
2–9.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
2–9.2.1 Schema Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
2–9.2.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
2–9.3 HST Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
2–9.3.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
2–9.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
2–10 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

2–10.1 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
2–10.1.1 1+0 FSO Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
1AA 00014 0004 (9007) A4 – ALICE 04.10
2–10.1.2 1+0 Radio Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

2–10.1.3 1+1 Radio Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
2–10.2 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
ED 03
3DB 05653 CA AA 3 / 296
296
2–10.3 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
2–11 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

2–11.1 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

2–11.2 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

2–11.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
2–11.4 Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
2–11.5 Current Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
2–12 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

2–12.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . . . 201
2–12.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
2–12.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
2–12.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
2–12.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
2–12.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
2–12.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
2–12.5 Threshold Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
2–13 SW DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

2–13.1 Server Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
2–13.2 Init SW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
2–13.3 SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
SECTION 3: AWY/FSO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

3–1 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
3–1.1 Maintenance of the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
3–1.2 Problems with THE Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
3–2 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

3–2.1 Purpose of this procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
3–2.2 Corrective Maintenance general flow–chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
3–2.3 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
3–2.4 Troubleshooting by means of the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
3–2.4.1 Alarm synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
3–2.4.2 Details on alarms / statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
3–2.5 Description of alarms and of probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
SECTION 4: SWP DESCRIPTION AND VERSIONS . . . . . . . . . . . . . . . . . . . . . . . . 227

4–1 SWP 9400AWY R.1.0 DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4–1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4–1.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4–1.3 Software licence list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
4–2 SWP REG.9400AWY R.1.0 V1.0.0 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . 231

4–2.1 ECT requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
4–2.2 SWP version specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
4–2.2.1 SW Package Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
4–2.2.2 SW Package Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
4–2.2.3 ECT SW Sub–Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
1AA 00014 0004 (9007) A4 – ALICE 04.10
4–2.2.4 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

4–2.3 New features and modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4–2.4 Restrictions and known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
ED 03
3DB 05653 CA AA 4 / 296
296
4–2.5 New features and modifications of SWP versions higher than V.1.0.0 . . . . . . . . . . . . 233



4–3.4 Restrictions and known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
4–3.5 Operative hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
4–3.6 New features and modifications of SWP versions higher than V.1.0.1 . . . . . . . . . . . . 238

SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . 243
A.1 : Functions and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
A.2 : IDU and ODU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
A.2.1 : IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
A.2.2 : ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
A.2.3 : Allowed Equipment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
A.2.4 : Remote Inventory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL . . . . . . . . . . . . 251

B.1 : Allocation of equipment and craft terminal software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
B.2 : Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
B.2.1 : Flash Card types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
B.2.2 : Flash Card identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
B.2.3 : Flash Card contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
B.2.4 : Flash Card upgrade (for 9400AWY only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
B.3 : Equipment control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
B.3.1 : Interfaces (see Fig. 157. on page 243): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
B.3.2 : Operator–Equipment Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
B.3.3 : ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
B.3.4 : RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
APPENDIX C : GENERAL ON SWP INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

C.1 : Troubleshooting situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
C.2 : Common situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
APPENDIX D : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
1AA 00014 0004 (9007) A4 – ALICE 04.10
D.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

D.2 : Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
D.3 : Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
ED 03
3DB 05653 CA AA 5 / 296
296
D.4 : Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
D.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . . . . 266
D.4.2 : TD–32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
D.5 : PC laptop “Dell Latitude” setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

D.6 : Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

D.7 : Changing the ECT–equipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
D.7.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
D.7.2 : Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
APPENDIX E : DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

E.1 : Handbook guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
E.1.1 : Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
E.1.2 : Purpose of the handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
E.1.3 : Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
E.2 : Documentation set description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
E.2.1 : 9400AWY Rel.1.0 product–release–version handbooks . . . . . . . . . . . . . . . . . . . . . . . . . 280
E.2.2 : 9400FSO Rel.1.0 product–release–version handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . 282
E.2.3 : Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0 . . . . . . . . . . . . . . . . . 284
E.2.4 : Specific documentation for SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
E.2.5 : General on Alcatel Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
APPENDIX F : ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
APPENDIX G : GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 6 / 296
296
LIST OF FIGURES AND TABLES
FIGURES
Fig. 1. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


Fig. 4. Windows NT configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Fig. 10. Windows 2000 installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fig. 15. Windows 2000 configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Fig. 18. Windows XP installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Fig. 23. Windows XP configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Fig. 27. De–installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Fig. 28. 9400 AWY Main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Fig. 29. View Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Fig. 30. Resource tree area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Fig. 31. Tab panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Fig. 32. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Fig. 33. Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Fig. 34. Local Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Fig. 35. Ethernet Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Fig. 36. IP configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Fig. 37. IP static routing configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Fig. 38. Create Static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Fig. 39. Point To Point Interface Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Fig. 40. OSPF Area configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Fig. 41. Create New OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Fig. 42. IP Address configuration of Point–To–Point Interfaces screen . . . . . . . . . . . . . . . . . . . . . . . . 99
Fig. 43. Routing information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Fig. 44. Alarm Severities Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Fig. 45. Name of a cloned alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Fig. 46. Clone of an Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Fig. 47. Selection of a new severity in the Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 48. Selection of a new severity in the No Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Fig. 49. System Settings: NE configuration (V 1.0.0 and V 1.0.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Fig. 50. System Settings: NE configuration (V 1.0.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ED 03
3DB 05653 CA AA 7 / 296
296
Fig. 51. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Fig. 52. USM closing warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Fig. 53. System Settings: Link Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Fig. 54. Overhead Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Fig. 55. Quick Installation Procedure: NE Configuration (Step 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Fig. 56. Quick Installation Procedure: Frame Configuration (Step 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Fig. 57. Quick Installation Procedure: Tributaries Configuration (Step 3) . . . . . . . . . . . . . . . . . . . . . . 116
Fig. 58. Quick Installation Procedure: Tributaries Configuration (Step 4) . . . . . . . . . . . . . . . . . . . . . . 117
Fig. 59. Quick Configuration Procedure: Channels Configuration (Step 5) . . . . . . . . . . . . . . . . . . . . . 118
Fig. 60. Quick Configuration Procedure: Local IP Address (Step 6) . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Fig. 61. Quich Installation Procedure: OSPF Area Configuration (Step 7) . . . . . . . . . . . . . . . . . . . . . 120
Fig. 62. Quick Installation Procedure: IP Static Router Configuration (Step 8) . . . . . . . . . . . . . . . . . 121
Fig. 63. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9) . . . . . . . . . . . . . 122
Fig. 64. Quick Configuration Procedure: NMS–V11 Interface Configuration (Step 10) . . . . . . . . . . . 123
Fig. 65. Quick Configuration Procedure: NMS–G703 Interface Configuration (Step 11) . . . . . . . . . 124
Fig. 66. Quick Installation Procedure: Ethernet Configuration (Step 12) . . . . . . . . . . . . . . . . . . . . . . . 125
Fig. 67. Quick Configuration Procedure: Summary (Step 13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Fig. 68. 1+0 FSO Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Fig. 69. 1+0 Radio Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Fig. 70. 1+1 Radio Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Fig. 71. 1+0 EXP Radio Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Fig. 72. 1+0 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Fig. 73. 1+1 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Fig. 74. Main board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Fig. 75. FSO ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Fig. 76. Radio ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Fig. 77. Alarm tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Fig. 78. Configuration tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Fig. 79. Remote Inventory tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Fig. 80. Line Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Fig. 81. Line Interface View: E1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Fig. 82. Line Interface View: E3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Fig. 83. Line Interface View: DS1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Fig. 84. Line Interface View: DS3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Fig. 85. Radio Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Fig. 86. Radio Frequency menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Fig. 87. Rtpc & Atpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Fig. 88. Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Fig. 89. Power Measurement Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Fig. 90. Power Meas Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Fig. 91. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Fig. 92. Example of “Power Measurement File Reading“ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Fig. 93. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . . . . 152
Fig. 94. FSO Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Fig. 95. FSO port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Fig. 96. Measurements screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Fig. 97. Power Measurement Graphic Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Fig. 98. Details Dialog screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Fig. 99. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Fig. 100. Example of “Power Measurement File Reading“ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Fig. 101. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . . 160
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 102. FSO laser configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Fig. 103. Input External Point View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Fig. 104. Output External Points View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
ED 03
3DB 05653 CA AA 8 / 296
296
Fig. 105. Output External Points View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Fig. 106. Configuration of the Craft access state from the Equipment NE view in the OS mode . . 167
Fig. 107. Restart NE call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Fig. 108. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Fig. 109. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Fig. 110. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Fig. 111. Mux Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Fig. 112. Mux Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Fig. 113. Mux Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Fig. 114. Radio Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Fig. 115. Radio Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Fig. 116. Radio Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Fig. 117. Transmission Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Fig. 118. Tx Protection Commands (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Fig. 119. Tx Protection Commands (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Fig. 120. 1+0 FSO available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Fig. 121. Channel 1 Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Fig. 122. Tributaries Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Fig. 123. 1+0 FSO Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Fig. 124. 1+0 Radio available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Fig. 127. 1+0 Radio Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Fig. 128. 1+1 Radio available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Fig. 131. 1+1 Radio Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Fig. 132. Loopback activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Fig. 133. Loopback removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Fig. 134. Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Fig. 135. Summary Block Diagram View: 1+0 FSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Fig. 136. Summary Block Diagram View: 1+0 Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Fig. 137. Summary Block Diagram View: 1+1 HST Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Fig. 138. Summary Block Diagram View: 1+1 FD Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Fig. 139. Radio section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Fig. 140. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826 . . . . . . . . . . 202
Fig. 141. Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Fig. 142. Threshold table association screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Fig. 143. Current Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Fig. 144. History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Fig. 145. Thresholds Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Fig. 146. Threshold table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Fig. 147. Server access configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fig. 148. Init Software Download screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fig. 149. SW Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Fig. 150. SW Unit Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Fig. 151. Corrective Maintenance general flow–chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Fig. 152. Active alarm screem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Fig. 153. (1+0) IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Fig. 154. (1+1) and (1+0 expandable) IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Fig. 155. (1+0) ODU (electrical or optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 156. (1+1) ODU (only electrical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Fig. 157. Interfaces for equipment control and Flash card label on MAIN Unit . . . . . . . . . . . . . . . . . 251
Fig. 158. MAIN unit + FLASH CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
ED 03
3DB 05653 CA AA 9 / 296
296
Fig. 159. FLASH CARD profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Fig. 160. Equipment main parts containing local SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Fig. 161. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Fig. 162. ECT–Equipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . . 263

Fig. 163. ECT–Local external Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Fig. 164. F Interface–Remote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Fig. 165. TD–32 AC modem dip–switch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Fig. 166. Alcatel Lower Layers utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Fig. 167. Example of SWP Release and Version numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Fig. 168. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . 287
TABLES
Tab. 1. Radio application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Tab. 2. FSO application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Tab. 3. Radio application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Tab. 4. FSO application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Tab. 5. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Tab. 8. Loopbacks on the local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Tab. 9. 1+0 FSO loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Tab. 10. 1+0 Radio loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Tab. 11. 1+1 Radio loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Tab. 12. SES Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Tab. 13. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Tab. 14. Alarm information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Tab. 15. General issues of the alarm meanings and their respective maintenance actions . . . . . . . 225
Tab. 16. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Tab. 17. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Tab. 18. Markets, product type, tributaries and modulations forecasted . . . . . . . . . . . . . . . . . . . . . . . 244
Tab. 19. Shelves Equipment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Tab. 20. IDU allowed board/plug–in types in (1+0) configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Tab. 21. IDU allowed board/plug–in types in (1+1) and (1+0 expandable) configurations . . . . . . . . 248
Tab. 22. Allowed board types in optical ODU ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Tab. 23. Available Flash cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Tab. 24. Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Tab. 25. 9400AWY Rel.1.0 product release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Tab. 26. 9400AWY Rel.1.0 Technical Handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Tab. 27. 9400AWY Rel.1.0 Installation and Line–Up Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Tab. 28. 9400AWY Rel.1.0 Documentation on CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Tab. 29. 9400FSO Rel.1.0 product release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Tab. 30. 9400FSO Rel.1.0 Technical Handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Tab. 31. 9400FSO Rel.1.0 Installation and Line–Up Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Tab. 32. 9400AWY Rel.1.0 Documentation on CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Tab. 33. Operator’s Handbooks related to the specific Software Package SWP . . . . . . . . . . . . . . . . 284
Tab. 34. Documentation common to Alcatel Network Elements using 1320CT platform . . . . . . . . . 284
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 10 / 296
296
PRELIMINARY INFORMATION
a) Warranty
Any warranty must be referred exclusively to the terms of the contact of sale of the equipment this
handbook refers to.

ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the
implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or
special, in connection with the furnishing, performance, or use of this material.
b) Information
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
c) Copyright Notification
The technical information of this manual is the property of ALCATEL and must not be copied,
reproduced or disclosed to a third party without written consent.
d) Safety recommendations
The safety recommendations here below must be considered to avoid injuries on persons and/or
damage to the equipment:
1) Service Personnel
Installation and service must be carried out by authorized people having appropriate technical
training and experience necessary to be aware of hazardous operations during installation and
service and of measures to avoid any danger to them, to any other people and to the equipment.
2) Access to the Equipment

Access to the Equipment in use must be restricted to Service Personnel only.
3) Safety norms
Recommended safety norms are not indicated in this manual, but in Handbooks REF. [A] on
page 281 and [E] on page 283. The warning labels that can be found on the equipment parts
are indicated on page 13.
Local safety regulations must be used if mandatory. Safety instructions in such handbook
should be used in addition to the local safety regulations. In the case of conflict between safety
instructions stated in such manual and those indicated in local regulations, mandatory local
norms will prevail. Should not local regulations be mandatory, then safety norms in the above
cited manual will prevail.
e) Service Personnel skill

Service Personnel must have been an adequate technical training on telecommunications and in
particular on the equipment this handbook refers to.
Reading this handbook and the associated handbooks indicated in para.E.2 on page 279 is usually
not enough to properly install, operate and maintain equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 11 / 296
296
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY
Please refer to para.E.1 on page 273.

HANDBOOK STRUCTURE
Information in this handbook is divided into the following parts:
a) FRONT MATTER
• TABLE OF CONTENTS
• LIST OF FIGURES AND TABLES
• PRELIMINARY INFORMATION
• HANDBOOK STRUCTURE
• SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING
• CAUTIONS TO AVOID EQUIPMENT DAMAGE
• QUICK GUIDE
It allows to access immediately the most frequently needed operative pieces of information
contained in this handbook and in other related handbooks.
b) SECTION 1: INSTALLATION on page 21

This part describes in detail the operations necessary for the SWP installation and upgrading (ECT
parts and equipment parts).
c) SECTION 2: AWY/FSO NE MANAGEMENT on page 77

In this section, the description of the menu structure and of all the AWY and FSO NE functionalities
available in the Craft Terminal is given.
d) SECTION 3: AWY/FSO NE MAINTENANCE on page 215

In this section the description of the AWY and FSO NE troubleshooting based on the use of the Craft
Terminal is given.
e) SECTION 4: SWP DESCRIPTION AND VERSIONS on page 227

This section gives information on the Software Packages this handbook refers to, and that are both
independent and independent on the specific SWP Version: commercial information (SWP and
Software Licences P/Ns), PC requirements, SW Package Identification, SW Package Components,
ECT SW Sub–Component, NE MIB Compatibility and additional features of new SWP versions.
f) SECTION 5: APPENDICES on page 241

In this section some additional information and instructions are given:
• Equipment description and components
• SW allocation, Flash Card and equipment control
• General on SWP installation
• ECT–Equipment connection via public switched telephone network
• Documentation Guide
• Acronyms and abbreviations
• Glossary of terms
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 12 / 296
296
SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING
a) Please refer to Technical Handbook to obtain details regarding following information:
• Compliance with European norms

• Safety rules:
TOPIC WARNING LABEL ON EQUIPMENT

General rules
Dangerous Electrical Voltages
Harmful optical signals
For 9400FSO read carefully next page
Risk of explosion
Moving mechanical parts
Heat–radiating mechanical parts
Equipment emitting RF power
• Equipment protection against electrostatic discharges:
TOPIC WARNING LABEL ON EQUIPMENT
Device sensitive to electrostatic discharges
• Electromagnetic Compatibility (EMC norms)
• Other Labels affixed to the Equipment
b) Identical or similar information on Personal Computer, Work–Station etc., other than ALCATEL’s,
loaded with software applications described in this Handbook, is supplied in the Constructor’s
technical documentation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 13 / 296
296
WARNING FOR 9400FSO ODU EQUIPMENT!

CAUTION: USE OF CONTROL OR ADJUSTMENTS OR PERFORMANCE OF PROCEDURES OTHER

THAN THOSE SPECIFIED HEREIN MAY RESULT IN HAZARDOUS LASER RADIATION EXPOSURE!
Product Laser Safety

The following special notes provide the laser safety specifications for the 9400FSO Terminal:
INFORMATION ALERT!
LASER DEVICES PRESENT WITHIN THIS EQUIPMENT ARE HAZARDOUS WHEN VIEWED WITH
OPTICAL INSTRUMENTS.
LASER HAS THE FOLLOWING OUTPUT CHARACTERISTICS UNDER MAXIMUM CONDITIONS:
Laser Type Wavelength (nm) Output Power (mW)

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
VCSEL 835 – 865 16
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
EN –CLASS 1M laser products According to EN 60825–1 ; EN 60825–2
INVISIBLE LASER RADIATION
DO NOT VIEW DIRECTLY WITH OPTICAL

INSTRUMENTS (BINOCULARS OR TELESCOPES)
CLASS 1M LASER PRODUCT

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 14 / 296
296
CAUTIONS TO AVOID EQUIPMENT DAMAGE
a) Antistatic protection device kit
When operating on boards out of the equipment shelf, this kit (see figure below) must be always warn
and its termination must be connected to a grounded structure, to avoids the possible damage of the
electronic devices for electrostatic discharges.
ELASTICIZED BAND
COILED CORD
b) Board’s extraction/insertion levers on ACCESS, MAIN IDU and EXTENSION IDU units
These units are provided with levers to facilitate their extraction and insertion from/into the shelf. In
turn, such levers are provided with screws that:
• must be loosened, before operating on levers for the unit extraction from the shelf; this avoids
the breakage of levers
• must be tightened, after the unit insertion in the shelf; this ensures the equipment EMI–EMC
performance.
Please refer to page 17 for more information [ points h ) , i ) and j ) ].
c) Unit assemblies
Each of the ACCESS, MAIN IDU, EXTENSION IDU and FANS unit assembly (“main board” + “baby
board(s)” + “front plate”) must be considered an unique item from the service and maintenance points
of view. Such an assembly is supplied by Alcatel “as it is” and must never be disassembled.
d) Screw fixing
All boards and dummy plates are provided with screws that, in normal operation conditions, must be
always tightened onto the shelf to avoid their detachment and to ensure the equipment EMI–EMC
performance and correct ventilation.
The screw tightening torque for fixing the units to the subrack must be:
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Exceeding this value may result in screw breaking.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 15 / 296
296
e) IDU–ODU cable disconnection / connection
Before to disconnect or connect the IDU–ODU cable (at IDU or ODU side) switch off the
corresponding MAIN IDU UNIT or EXTENSION IDU UNIT.

f) Craft Terminal connection
To connect the CT cable (at IDU’s F interface and/or PC side):

• verify that the PC is switched off (if switched on, close all running applications, then switch off
it)
• connect suitable cable to IDU’s F interface and PC side
• now the PC can be safely switched on.
g) Craft Terminal disconnection
To disconnect the CT cable (at IDU’s F interface and/or PC side):

• perform the logoff, exiting from the CT applications
• close all other running applications, if any
• switch off the PC
• now the cable can be safely disconnected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 16 / 296
296
h) Right operations for board insertion in the subrack
1) Open the levers before to plug the unit. 2) To mate the plastic body of the connectors:
push on the front panel, balancing the strain
without push on the levers.
4) Fix the unit to the subrack by means

of screws (max tightening torque
specified in point d ) on page 15
3) Push on the levers in order to finish
the connector mating.
i) Forbidden operations for board insertion in the subrack
NO Don’t push just on one lever only.
NO Don’t force the units.
NO Avoid impact during the units handling.
j) To populate an empty subrack

1 ) insert one unit at a time
1AA 00014 0004 (9007) A4 – ALICE 04.10
2 ) fix the unit to the subrack by means of screws, before to insert another unit.
ED 03
3DB 05653 CA AA 17 / 296
296
QUICK GUIDE
C.T. OPERATOR’S HANDBOOK SWP 9400AWY R.1.0

If you need immediate operative information on how to:
GENERAL TOPICS FOR 9400AWY AND 9400FSO
get information on system

read Appendix E on page 273
documentation
get information on safety, EMC,

read page 13
ESD norms and equipment labelling
read:
Chapter 4–1 on page 229

have the description of the system
from the software point of view Appendix A on page 243
Appendix B on page 251
logically configure a station (or

change its configuration) and get:
logically set–up connections
T h i l Handbook
9400AWY Technical (R f [A] on page 281)
H db k (Ref.
logically provision equipment boards
or
get item P/Ns
SO Technical Handbook (Ref.
9400FSO f [E] on page 283)
get operative information regarding
the units in IDU shelf and ODU and read its QUICK GUIDE (same topics)
(connectors, leds, buttons)
HW INSTALLATION
For:
– 9400AWY, get 9400AWY Rel.1.0 Installation Handbook

physically install and cable the (Ref.[B] on page 281) and proceed as specified by it
equipment hardware
– 9400FSO, get 9400FSO Rel.1.0 Installation Handbook
(Ref.[F] on page 283) and proceed as specified by it
continues ..
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 18 / 296
296
.. continues
SWP INSTALLATION AND COMMISSIONING

install SWP (first time) on ECT proceed as specified in chapter 1–1 on page 23
download SWP (first time) into the

proceed as specified in chapter 1–2 on page 59
equipment
For:
– 9400AWY, get 9400AWY Rel.1.0 Line–up Guide

commission equipment (Ref.[C] on page 281) and proceed as specified by it
– 9400FSO, get 9400FSO Rel.1.0 Line–up Guide

(REF.[G] on page 283) and proceed as specified by it
update ECT and equipment with a

newer SWP version (same SWP proceed as specified in chapter 1–3 on page 75
release)
ECT SOFTWARE USAGE FOR EQUIPMENT SW MANAGEMENT
have an overview on menu tree

structure
manage equipment configuration
set–up parameters for maintenance

(configure housekeeping alarms; open SECTION 2 – AWY/FSO NE MANAGEMENT on page
configure the Alarms Management, 77 of this handbook and then search the information
access the Alarm Surveillance and according to the listed topics
show the alarm condition).
access the Events Log file
use of the Performance Monitoring

functionalities
continues ..
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 19 / 296
296
.. continues
9400AWY MAINTENANCE

provision and manage spare parts
get 9400AWY Technical Handbook (Ref. [A] on page 281)
and read its QUICK GUIDE (same topic)
carry out preventive maintenance
get 9400AWY Technical Handbook (Ref. [A] on page 281),

and go to its section MAINTENANCE, chapter Second Level
Maintenance paragraph Corrective Maintenance and
proceed as specified; in any case, such section will usually
lead to the SECTION 3 – AWY/FSO NE MAINTENANCE on
page 215 of this handbook.
carry out corrective maintenance
Alternatively, access directly SECTION 3 – AWY/FSO NE
MAINTENANCE on page 215 of this handbook and proceed
as specified; if a board must be replaced, you will be led to the
use of paragraph Unit Replacement Procedures of the
9400AWY Technical Handbook for the correct replacing
procedures.
9400FSO MAINTENANCE
provision and manage spare parts

get 9400FSO Technical Handbook (Ref.[E] on page 283)
and read its QUICK GUIDE (same topic)
carry out preventive maintenance
get 9400FSO Technical Handbook (Ref.[E] on page 283),

and go to its section MAINTENANCE, chapter Second Level
Maintenance paragraph Corrective Maintenance and
proceed as specified; in any case, such section will usually
lead to the SECTION 3 – AWY/FSO NE MAINTENANCE on
page 215 of this handbook.
carry out corrective maintenance
Alternatively, access directly SECTION 3 – AWY/FSO NE
MAINTENANCE on page 215 of this handbook and proceed
as specified; if a board must be replaced, you will be led to the
use of paragraph Unit Replacement Procedures of the
9400FSO Technical Handbook for the correct replacing
procedures.
To find any other kind of information not listed in the above table, please refer to the TABLE OF
CONTENTS of this handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 20 / 296
296
SECTION 1: INSTALLATION
SECTION CONTENT PAGE

Chapter 1–1 – SWP installation in PC environment

This chapter details all phases necessary to install for the first time a SWP in the PC 23
environment or to upgrade it with a new version of the same SWP.
Chapter 1–2 – SWP download toward NE

This chapter details all phases necessary to install for the first time a SWP in the 59
equipment environment.
Chapter 1–3 – NE Upgrade to a newer SWP ’version’ (same SWP ’release’)

This chapter details all phases necessary to install a new SWP ’version’ in the PC 75
environment as well as in the equipment environment.
The symbol points out references to Other Handbooks.
Referenced handbook P/Ns are given in para.E.2 on page 279.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 21 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
22 / 296
1–1 SWP INSTALLATION IN PC ENVIRONMENT
This chapter details all phases necessary to install for the first time a SWP in the PC environment or to
upgrade it with a new version of the same SWP.
Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 252
and Appendix C on page 259.
Procedures described in this chapter are carried out with the PC disconnected from the NE.
1–1.1 Requirements
1–1.1.1 PC characteristics
For version refer to paragraph on page

V 1.0.0, V 1.0.1 & V 1.0.2 4–2.1 231
1–1.1.2 Operator skills
The operator shall be familiar with the use of personal computers in WINDOWS–NT / WINDOWS 2000
/ WINDOWS XP environment, internally to which the Network Element’s application software operates.
Furthermore, for a number of configuration applications, the operator shall be aware of some
specifications of the International Standard Organization (ISO) and of the standards applied to the
Plesiochronous Digital Hierarchy (PDH) (ITU–T Recommandations).
1–1.2 Summary of SW installation phases
The sequence of installation phases for the SWP loading in PC WINDOWS–NT/XP/2000 environment (PC
is disconnected from Equipment Controller) are as follows:
a) Installation from SWP CD–ROM
1) installation of 1320CT + NE software from SWP CD–ROM

2) installation of SIBDL program from SWP CD–ROM
3) end of SW installation from SWP CD–ROM
b) CT initial configuration
that are described in detail in following paragraphs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 23 / 296
296
1–1.3 SWP loading in PC WINDOWS–NT/2000/XP environment
Procedures described in the following are carried out with the PC disconnected from the NE.

1–1.3.1 Installation of 1320CT + NE software from SWP CD–ROM
This operation must be perfoms at Administrator of the PC, because it subsequently could be to
set IP address .
Hereafter are described the SWP installation procedures to be used for:
– First installation
The first time this SWP is installed on the PC, follow this procedure:
1) First install the Java and LLMan components by using the guided installation mode, described
in the para. 1–1.3.1.1 – CT Products installation guided.
2) Second configure the Alcatel Virtual Network Card by using the procedure described in the para.
1–1.3.1.2 – Alcatel Virtual Network Card configuration.
3) At the end install the other components, by using the automatic installation mode, described in
the para. 1–1.3.1.3 – CT Products automatic installation.
– Complete updating
To update one or more components on the PC, follow this procedure:
1) To update the Java and LLMan components use the guided installation mode, described in the
para. 1–1.3.1.1 – CT Products installation guided.
2) To update the other components use the automatic installation mode, described in the para.
1–1.3.1.3 – CT Products automatic installation.
– Partial automatic updating
To update one or more components, excluded Java and LLMan, use only the automatic installation
mode, described in the para. 1–1.3.1.3 – CT Products automatic installation.
WARNING: During the installation an ALCATEL directory is automatically created, if not already
present.
If ALCATEL directory is already present on the PC, for a correct operation of the FTP
server, this directory must have all upper case characters (i.e. “ALCATEL”).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 24 / 296
296
1–1.3.1.1 CT Products installation guided
In the following is described (step by step) the procedure to install “JRE” and “Alcatel Lower Layer
Manager” with the “CT Products installation guided”.
Operations sequence:
Step 1. Select the “CT Products installation guided” and press “NEXT” button.
Step 2. Select “JRE” (ONLY if you have an OLDER version) and “Alcatel Lower Layer Manager”
components.
WARNING: if try to update JRE and JRE V 1.4.1 is already installed, the procedure automatically
de–install, it WITHOUT making the new installation. Keep attention in this case to the
“Question Window” that appears, which ask you to proceed to the de–installation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 25 / 296
296
Step 3. Press “NEXT” button to execute the installation of the previously selected components.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Step 4. Press “NEXT” button to start the installation of the Lower Layers Manager.
ED 03
3DB 05653 CA AA 26 / 296
296
Step 5. Select “Configure Lower Layer” and press “FINISH” button to complete the operation.
Step 6. Complete the configuration and press OK button.

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. If a network adapter is not running in the PC, you can set the “System identifier”field with a
sequence of 12 “0”. The following window will be displayed.
ED 03
3DB 05653 CA AA 27 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Step 9. Press YES button to confirm.
296
3DB 05653 CA AA
28 / 296
1–1.3.1.2 Alcatel Virtual Network Card for Lower Layers
At first SWP installation on ECT, after installation of Alcatel Lower Layer Manager and before the
installation of other ECT SW components, it is necessary, for NE connection using TCP/IP through serial
port, to configure a Virtual Network Card.

Alcatel Virtual Network Card for Lower Layers is a software component used by Alcatel Lower Layers
Manager to manage TCP/IP packets through the serial port.
Follow this guide to install and configure Alcatel Virtual Network Card for Lower Layers using the
Control Panel.
Refer to para. 1–1.3.1.2.1 on page 29 for intallation on Windows NT 4.0; refer to para. 1–1.3.1.2.2 on page
35 for intallation on Windows 2000; refer to para. 1–1.3.1.2.3 on page 43 for intallation on Windows XP.
1–1.3.1.2.1 Windows NT 4.0
1–1.3.1.2.1.1 Installing the Alcatel Virtual Network Card for Lower Layers
To install the Alcatel Virtual Network Card for Lower Layers select the Adapters tab in the Network Control
Panel applet.
After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following the
instruction of the Windows NT 4.0: Configuring Alcatel Virtual Network Card for Lower Layers section.
Before installing Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please
refer to Windows NT Help).
– Click the Add... button in the Adapter tab of the Network Control Panel applet.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 1. Windows NT installation step 1
ED 03
3DB 05653 CA AA 29 / 296
296
– In the Insert Disk dialog box, type the source path of the driver files copied during installation phase
(e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command Prompt
window to discover the right location of the WinNT folder) and click OK.

– If the dialog box in Fig. 3. appears, the driver is already installed.
Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP
1AA 00014 0004 (9007) A4 – ALICE 04.10
parameters before use it in with Alcatel Lower Layers Manager.
ED 03
3DB 05653 CA AA 30 / 296
296
1–1.3.1.2.1.2 Configuring the Alcatel Virtual Network Card for Lower Layers
To configure the Alcatel Virtual Network Card for Lower Layers use both the Bindings and the Protocols
tabs in the Network Control Panel applet.
Before configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol
(please refer to Windows NT Help).
set IP address .
To install the Alcatel Virtual Network Card for Lower Layers run the Network Control Panel applet from
the Control Panel.
– Select the bindings of Alcatel Virtual Network Card for Lower Layers in the Bindings tab (1), (2) of
the Network Control Panel applet.
– Disable any unneeded component (3), (4).
– Selecting the Protocols tab (5) of the Network Control Panel applet, the either a message box
(Fig. 5. NT configuration step 2) or a dialog box (Fig. 6. NT configuration step 3) may appear.
– Follow the instrucions until the dialog box (Fig. 7. NT configuration step 4) will appear.
5
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 4. Windows NT configuration step 1
ED 03
3DB 05653 CA AA 31 / 296
296
– Click Yes to save changes.

– Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 32 / 296
296
– Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for Lower
Layers and push OK.
*** WARNING ***
If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is
necessary, for a correct ECT functionality, to perform an explicit ECT re–customization by executing the
following command:
– Start → Programs → Alcatel → SNMPCT–K–ADD–ON v... → SNMP Add–On Customization

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 33 / 296
296
– Click Close in the Protocols tab of the Network Control Panel applet.

– The new configuration of Alcatel Virtual Network Card for Lower Layers will be used at the next restart
of the computer.
– If you are configuring or installing the Alcatel Virtual Network Card for Lower Layers you can click Yes.
If you are installing some other component you should click No and restart the computer later.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 34 / 296
296
1–1.3.1.2.2 Windows 2000
To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard from
the Control Panel.

Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP
protocol (please refer to Windows 2000 Help).
Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:
Alcatel Virtual Network Card for Lower Layers has to be installed only once.
instruction of the Windows 2000: Configuring Alcatel Virtual Network Card for Lower Layers section.
– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 10. Windows 2000 installation step 1
ED 03
3DB 05653 CA AA 35 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
36 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
–
ED
03
Click the Have Disk... button in the Select Network Adapter dialog box.
296
3DB 05653 CA AA
37 / 296
– In the Install From Disk dialog box, type the source path of the driver files copied during installation
phase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command
Propt window to discover the right location of the WinNT folder) and click OK.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 38 / 296
296
– Click Next in the Start Hardware Installation dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 39 / 296
296
set IP address .

To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dial–up connections
applet from the Control Panel.
Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP
protocol (please refer to Windows 2000 Help).
the Control Panel.
– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the
Network and Dial–up connections applet.
Fig. 15. Windows 2000 configuration step 1

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 40 / 296
296
– Uncheck any unneeded component in the Properties dialog box General tab (1). Check and select
the Internet Protocol (TCP/IP) component (2) and click Properties (3).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 41 / 296
296
– Configure the IP Address (1) and the Subnet Mask (2) and push OK (3).

1
2
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Manager
to use it.
*** WARNING ***
following command:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 42 / 296
296
1–1.3.1.2.3 Windows XP
To install the Alcatel Virtual Network Card for Lower Layers run the Add Hardware Wizard from the Control
Panel.
instruction of the Windows XP: Configuring Alcatel Virtual Network Card for Lower Layers section.
Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:
Alcatel Virtual Network Card for Lower Layers has to be installed only once.
– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 43 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 18. Windows XP installation step 1
296
3DB 05653 CA AA
44 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
45 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Click the Have Disk... button in the Select Network Adapter dialog box.
296
3DB 05653 CA AA
46 / 296
– In the Install From Disk dialog box, type the source path of the driver files copied during installation
phase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command
Propt window to discover the right location of the WinNT folder) and click OK.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 47 / 296
296
– Click Next in the The wizard is ready to install your hardware dialog box.


1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 48 / 296
296
set IP address .
To configure the Alcatel Virtual Network Card for Lower Layers run the Network connections applet from
the Control Panel.
the Control Panel.
– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the
Network and Dial–up connections applet.
Fig. 23. Windows XP configuration step 1

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 49 / 296
296
– Uncheck any unneeded component (disable always the QoS Packet Scheduler – 1 –) in the
Properties dialog box General tab. Check and select the Internet Protocol (TCP/IP) component (2)
and click Properties (3).

1
2

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 50 / 296
296
– Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK
(4).
1
2
*** WARNING ***
following command:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 51 / 296
296
– Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOS
over TCP/IP (2) and then push OK (3).

1
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers
Manager to use it.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 52 / 296
296
1–1.3.1.3 CT Products installation guided
Hereafter is described the procedure to install all the components except “JRE” and “Alcatel Lower Layer
Manager” with the “CT Products automatic installation”
Operations sequence:
Step 1. Select the “CT Products automatic installation ” and press “NEXT” button.
Step 2. Select all components except “JRE” and “Alcatel Lower Layer Manager”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Step 3. Press “NEXT” button to execute the installation of the previously selected components.
ED 03
3DB 05653 CA AA 53 / 296
296
1–1.3.2 Installation of SIBDL program from SWP CD–ROM
Refer to chapter B.1 for general information on SIBDL program (in particular point 2 ) in para.B.3.2 on
page 257 and point 2 ) in para.C.1 on page 260).

The SIBDL program is not automatically installed by the auto–installation process.
The installation of SIBDL is detailed in the dedicated Section of the:
9400AWY Line Up Guide
or
9400FSO Line Up Guide
N.B. It is not mandatory to install SIBDL in this phase. You can postpone it when necessary (take into
account that you will need the SWP CD–ROM).
1–1.3.3 End of SW installation from SWP CD–ROM
Having reached this phase, you have finished the Software transfer from SWP CD–ROM to the PC
environment. Now, you can extract the SWP CD–ROM from the PC’s CD–ROM unit.
1–1.3.4 De–installation phases
This paragraph describes how de–install from the PC the Software Package required by the Craft Terminal
to manage the relevant Network Element.
This can be useful, for example, when a version of the software package is no more updated.
To de–install the following procedure can be followed:
– with the CD–ROM containing the relevant Software product.
– with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CD–ROM containing the
relevant Software product is not present.
From Control Panel select Add/Remove Programmes and de–install the components shown in the
following figure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 54 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 27. De–installation
296
3DB 05653 CA AA
55 / 296
1–1.4 CT initial configuration
Procedures described in the following are carried out with the PC disconnected from the NE.

1–1.4.1 Craft Terminal configuration
This procedure is necessary to configure the PC in order to manage the Network Elements and includes
the following types of configuration:
– PC hostname
– CT configuration
– Communication Protocol (TCP/IP):
• TCP/IP without a network card
• TCP/IP with a network card
• Switching between the two configurations
– Serial Communication with the NE
– Screen settings
In order to set–up these configurations, refer to:
1320CT Basic Craft Terminal Operator’s Handbook ,

section “INSTALLATION”, chapter “Craft Terminal Configuration”
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 56 / 296
296
1–1.4.2 Craft Terminal connection to the NE
The CT can be connected to the NE through the Serial Port or through the Ethernet Network Port.
Only one connection can be active. The default connection is the Serial port.
1–1.4.2.1 Connection through the Serial Port
This connection is the default connection.
To connect the CT to the NE through the Serial Port:
1) The Alcatel Virtual Network Card for Lower Layers Software has to be installed on the PC (refer
to para. 1–1.3.1.2 on page 29).
N.B. If the IP Address configured for the Alcatel Virtual Card has been changed after the 1320CT
Platform installation, it is necessary to perform a re–customization by entering the following
command:
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.x → SNMP Add–On Customization
N.B. If the connection through Ethernet Network Port has been activated, to activate again the
connection through the Serial Port enter the following command:
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.x → NE Connection → Serial Port
1–1.4.2.2 Connection through the Ethernet Network Port
1) Configure the Network Card on the CT as explained in the 1320CT Basic Craft Terminal
Operator’s Handbook.
2) Enter the NE and enable the Ethernet port on the NE (refer to para. 2–2.2.2 on page 92).
3) Quit the NE and close the Network Element Synthesis application.
4) Activate the CT Connection through the Ethernet Port by the following command:
Start→Programs→Alcatel→SNMPCT–K–ADD–ON v.3.1.x→NE Connection→Ethernet Port
N.B. If the IP Address configured on the Ethernet port has been changed, it is necessary to perform
a re–customization by entering the following commands:
Start → Programs → Alcatel → CT–K– v.3.1.x → Customization
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.x → NE Connection→Ethernet Port

1AA 00014 0004 (9007) A4 – ALICE 04.10
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.x → SNMP Add–On Customization
ED 03
3DB 05653 CA AA 57 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
58 / 296
1–2 SWP DOWNLOAD TOWARD NE
This chapter details all phases necessary to install for the first time a SWP in the equipment environment.
Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 252
and Appendix C on page 259.
Procedures described in this chapter are carried out with the PC connected to the NE.
1–2.1 Requirements
1–2.1.1 NE hardware
The equipment must have been already physically installed, cabled and powered on, according to the
instructions given in the:
9400AWY Installation Handbook

or
9400FSO Installation Handbook
1–2.1.2 Craft Terminal
The Craft Terminal, already loaded with the SWP to be downloaded toward the NE (N.B.), must be
available together with the cable for its connection to the equipment F interface.
N.B. as explained in previous chapter 1–1 on page 23.
1–2.1.3 Operator skills and profile
In addition to skills stated in para.1–1.1.2 on page 23, the Operator must be familiar with all the equipment
functionalities.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 59 / 296
296
1–2.2 Summary of the SWP installation phases
The installation phases are:

a) SW download to the NE, para.1–2.3 herebelow

b) NE Login, para.1–2.4 on page 72
c) Commissioning, para.1–2.5 on page 73
d) Configuration data definition, para.1–2.6 on page 73
1–2.3 SW download to the NE
Through the suitable cable, connect the ECT to the F interface of the MAIN unit (see Fig. 157. on page
251).
N.B. The software download can be performed also by using the Ethernet interface of the PC. The
ECT must be connected to the Ethernet interface of the MAIN unit (see Fig. 157. on page 251).
To activate the Ethernet connection refer to para. 1–1.4.2.2 on page 57. In this case the
download will last only few minutes.
Step 1. Start the ECT
• Start → Alcatel 1320CT
Step 2. Install the current SWP on the platform environment
• On NES (Network Element Synthesis) start “SWP Administrator”: Supervision → Files

Administration (SWP Administrator)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 60 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
•
03
On SWP Administrator windows press install bottom
(C:\ALCATEL\JUSMw0.1.5\ect\swdw\R94AWY\1.0.0)
Browse the SWP file descriptor “R94a.dsc” from the disk
296
3DB 05653 CA AA
61 / 296
Step 3. Start Supervision
• On NES (Network Element Synthesis) start “Supervision”: Supervision → Start

Step 4. Show Equipment
• On NES (Network Element Synthesis) start “Show Equipment”: Supervision → Show

Equipment
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 62 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
Step 5.
03
Setup Server Access Configuration
296
3DB 05653 CA AA
On JUSM start “Server Access Configuration”: SW Download → Server Access Configuration
63 / 296
• In the “FTP Login” window the field “Address” must be set with the same address written in
“Alcatel Lower Layer Manager – IP Network – Local address”. Press “OK” to confirm.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 64 / 296
296
Use System Default botton
When the operator click the Use System Default botton is possibile to set the field ADDRESS in two
different mode:
1) by F interface: to set IP address of the LLMAN to download in interface IF mode
2) by LAN interface: to set IP address of the PC to download the software in LAN mode
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 65 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
•
Step 6.
03
Init SW Download
Wait “List Sw Package” creation ...
296
3DB 05653 CA AA
On JUSM start “Init SW Download”: SW Download → Init SW Download
66 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
•
03
When action is completed, press “Enter” to close message window.
296
3DB 05653 CA AA
Now select a specific SWP to download on the NE, and press “Init download” to start it.
67 / 296
• Confirm the start of software downloading:

• The software downloading in progress is shown by a specific window:
• When the download is over the following window is shown:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 68 / 296
296
Step 7. Activation of the new Software Package on the NE
• On JUSM start “SW Download”: SW Download → SW Download.

• After the software download, two software packages are present in the NE: one “Committed”
and the other “Stand by”. The “NE Software Status Detail” window shows the information.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 69 / 296
296
• To activate the new software package select the software package in “Stand by Status”.

• Now select on “Software Management Action” field “Activation”.
• Press “Apply Action”.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 70 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
•
03
Confirm the selected action.
After this window the NE restarts with the new software package.
296
3DB 05653 CA AA
71 / 296
1–2.4 NE Login
a) Cable connection

Through the suitable cable connect the ECT to the F interface or to the Ethernet interface of the MAIN

unit (refer to Fig. 157. on page 251).
To activate on the CT the connection through the Serial Port or through the Ethernet Port refer to
para. 1–1.4.2 on page 57.
b) Craft Terminal (CT) start–up
1) CT start :
– power on the CT and wait for PC start–up
– Start ⇒ Alcatel 1320CT:
• if choice Alcatel 1320CT is not available, PC is not configured as Craft Terminal:

Software Package loading is necessary
after a while, the “Network Element Synthesis” screen will appear, showing all Network
Elements that can be selected. After this Start operation, all NEs appear with symbol “?”
(it means they are not supervised)
N.B. For a corrected operation, only on some PC with Windows 2000 or XP by using the
serial connection, it is necessary to start the Lower Layers Manager (Start →
Programs → Alcatel → Lower Layers → Lower Layers Manager) before starting the
ECT Platform (Alcatel 1320CT).
c) Start supervision on a selected Network Element (NE)
From screen “Network Element Synthesis” ( see point b ) – 1 ) ) :

1) select the interested Network Element (NE) clicking once left mouse button on it;
N.B. During the creation of the SNMP NE (refer to the 1320CT Basic Craft Terminal
Operator’s Handbook, section 5 “EML CONSTRUCTION”), in the TCP/IP Port field
number “161” must be inserted.
2) while NE selected, with right mouse button choose Start Supervision and with left mouse
button execute it (click once).
Wait until the symbol “?” becomes colored “•” (it means “NE in supervised state”)
N.B. The User Label of the NE must not include the following characters: \ ? : * “ < >
|.
WARNING: Due to a deep fading the radio remote NE can be unreachable. In this condition in the
USM will appear the following message:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 72 / 296
296
– The USM must be closed.
In the NES will appear a broken icon and a red bullet.
– Wait for the automatic restarting of the Supervision (at the end of the fading conditions). The icon in
NES will become whole and the bullet will take the color relevant to the alarms (if any) active in the NE.
– If the Supervision does not start, close and open again the CT.
– If the Supervision does not start, switch off and switch on the PC.
d) Network Element login
From screen “Network Element Synthesis” with NE in supervised state ( see point c ) – 2 ) ):
1) select the interested Network Element (NE) clicking once right mouse button on it;
2) select Show Equipment. All the available menus are explained in Section 2.
WARNING: Before disconnecting the F interface cable or before switching off the NE, stop the
supervision and close the JUSM.
1–2.5 Commissioning
The commissioning instructions are given in:
or
1–2.6 Configuration data definition
The instructions given in the handbook cited in para. 1–2.5 above may not include the definition of all the
Equipment configuration data that could be necessary.
In order to manage this data, refer to the Section 2 AWY/FSO NE MANAGEMENT on page 77.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 73 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
74 / 296
1–3 NE UPGRADE TO A NEWER SWP ’VERSION’ (SAME SWP ’RELEASE’)
This chapter details all phases necessary to install a new SWP ’version’ in the PC environment as well
as in the equipment environment.
This procedure can be used only in the case depicted in point 3 ) on page 261, i.e.:
– ECT and equipment are running with one of the Software Packages with P/N indicated in Tab. 16. on
page 229 and with generic version ’A.B.c’ (’A.B’ is the SW release, ’c’ is the patch level)
– a new version of SWP ’A.B.d’ (d > c), having the same P/N, is delivered to Customer.
Procedure:
1) Requirements: see para.1–1.1 on page 23 and para.1–2.1 on page 59.
2) Carry out the installation of the new SWP version in the ECT environment, as indicated in
chapter 1–1 on page 23.
3) The subsequent phases depend on the compatibility of MIB structure between previous and
new SWP versions. This MIB compatibility is indicated in the suitable chapter–paragraph
(according to SWP Version) in Section 4 on page 227. In case you receive a version higher than
the highest listed on page 227, please refer to the documentation accompanying the SWP
delivery to get this information.
N.B. Usually the MIB structure is fully compatible inside a SWP Release, so that the
following step 4 ) must be taken into consideration.
4) new MIB structure compatible with old MIB structure:
a) perform the SW download with the following Craft Terminal commands (refer to
para.2–13.2 on page 212 for detailed description):
• perform step 1 to 5 in para. 1–2.3 on page 60
• SW Download ⇒ Init SW download
• the screen of Fig. 148. on page 212 opens
• select the new NE–version to be downloaded
• with SWP Version 1.0.1 and 1.0.2 is necessary to select “Forced” option on CT
screen for SW Download activation request
• click on “Init download” button
• then, after about 1/2 hour, ⇒ SW Download ⇒ SW status ⇒ Apply Action to activate
the software.
N.B. The software download can be performed also by using the Ethernet interface
of the PC. In this case the download lasts only few minutes.
b) perform NE logoff followed by NE login.
The result is the Equipment working with the new SWP version nevertheless maintaining the
old configuration data.
5) new MIB structure not compatible with old MIB structure

1AA 00014 0004 (9007) A4 – ALICE 04.10
Procedure presently not necessary.
ED 03
3DB 05653 CA AA 75 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
76 / 296
SECTION 2: AWY/FSO NE MANAGEMENT

Chapter 2–1 – General introduction on views and menus

This chapter describes the organization of the 9400AWY/FSO ULS N.E., 79

presented after the NE login.
EQUIPMENT CONFIGURATION MANAGEMENT
Chapter 2–2 – Configuration
89
This chapter describes the configuration relevant to the equipment management.
Chapter 2–3 – Equipment
This chapter deals with the presentation of the N.E. and the structure of the
127
hierarchical tree, and the types of subracks and boards, that comprise the Network
Element.
Chapter 2–4 – Line Interface
This chapter describes the operations necessary for the configuration setting and 137
verification of each tributary.
Chapter 2–5 – Radio
143
This chapter deals with the management of the Radio transmission features.
Chapter 2–6 – FSO
153
This chapter deals with the management of the FSO transmission features.
Chapter 2–7 – External input and output points
This chapter describes how to display and set the input/output environmental 163
alarms (housekeeping alarms).
FUNCTIONS FOR MAINTENANCE
Chapter 2–8 – Supervision
This chapter describes how to manage the NE access from OS or local ECT and 167
how to restart the NE.
Chapter 2–9 – Protection schemes
171
This chapter deals with the management of the Radio protections.
Chapter 2–10 – Loopbacks
This chapter describes the commands for loopback management, for 181
commissioning or maintenane purposes.
Chapter 2–11 – Diagnosis
This chapter describes how to access the Alarm and Event Log files and explains
the Summary Block Diagram View menu. 195
N.B. The chapter does not describe the Log Browser. Reference must be
done to the specific “ELB Operator’s Handbook”.
Chapter 2–12 – Performance Monitoring
201
This chapter deals with the use of the Performance Monitoring functionalities.
SOFTWARE MANAGEMENT
Chapter 2–13 – Software Management
This chapter deals with the management of the functions related to the software
211
verification/download and to the back–up and restore of equipment configuration
data.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 77 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
78 / 296
2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS
This chapter describes the organization of the 9400 AWY/FSO N.E., presented after the NE login.
First the view organization is introduced, then the accessible menu options are listed.
Some further advices are given for Navigation principles.
N.B. This operator handbook explains the menus for Rel.1.0.0, Rel.1.0.1 and Rel. 1.0.2.
Version 1.0.0 manages the Radio application only (1+0 configuration).
Versions 1.0.1 and 1.0.2 manage the Radio application (1+0, 1+1 and 1+0 EXP configurations)
and the FSO application.
2–1.1 9400 AWY/FSO view organization
The 9400 AWY/FSO view ( see Fig. 28. on page 80 ) contains the following fields, which provide the
operator with the information needed to manage the NE:
• Severity alarm synthesis,

• Domain alarm synthesis,
• Management status control panel,
• View title,
• View area,
• Message/state area.
The Menu bar and the View area contained in the same NE view permit to perform all configuration and
supervision operations and the display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for the
description.
N.B. Fig. 28. on page 80 shows the 9400 AWY in 1+1 configuration.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 79 / 296
296
Severity alarm Domain alarm
synthesis synthesis
Menu
bar

Main tool
bar
View
area
Management
state control panel
Fig. 28. 9400 AWY Main view organization
N.B. For the meaning of the icons in the Severity alarm synthesis, Domain alarm synthesis and the
Management state control panel refer to Section 3 paragraph Alarm synthesis indication in
this handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 80 / 296
296
2–1.1.1 View Area
The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g.
many windows placed one upon another. Each window is selectable (placing it on top of the others) with
a tab shown on the top.

Each panel represents a set of functions. The area consist of the following sets:
– Equipment
– External Points
– Line Interface
– Performance
– Radio (or FSO in V 1.0.1 and V 1.0.2)
– Protection Schemes (for Radio application only in V 1.0.1 and V 1.0.2)
– Loopback
– Sw Download
The following figure shows the tabbed panel organization.
Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ).
RESOURCE
TREE AREA
RESOURCE LIST AREA
RESOURCE DETAIL AREA
Fig. 29. View Areas

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 81 / 296
296
Each tab–panel (e.g. functionalities area) consists of four areas:
– Resource–Tree Area: displays all the available resources of the Radio NE.
– Resource–List Area: may be represented by: Tabular View (e.g., Line Interface Domain) or

Graphical View (e.g., Equipment Domain).
• Tabular View: displays a tabular representation of the selected resource. As default, no tabular
element is shown.
• Graphical View: displays a graphical representation of the selected resource. As default, no

tabular element is shown.
– Resource–Detail Area: displays detailed information of a selected item in the Resource List area.
As a default, no entry view is displayed as a consequence of the default behavior of the Resource
List area.
2–1.1.2 Resource Tree Area
The “Resource Area” displays all the available resources in a tree structure like the protocol stack
hierarchy. The below figure shows an example of the resource tree instance (for the Line Interface
functions):
Fig. 30. Resource tree area
2–1.1.2.1 Selection Criteria
Each tree node consists of two symbols. The first symbol indicates the state of the structure e.g., if the
symbol is ”+” the tree can be expanded to a lower level. The tree structure can be collapsed if the symbol
is “–“. Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphical
representation of the resource.
The user must select the resource by clicking with the mouse to carry out an action that depends on the
type of click.
Each resource listed above may be selected by using the mouse by a:

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Single left click;

– Double left click
ED 03
3DB 05653 CA AA 82 / 296
296
Single left click:
By a single left click the resource is highlighted. This selection causes the activation of the
resource list area, e.g., every time the user selects a resource in the resource tree area the
corresponding Tabular or Graphical representation is displayed in the ”Resource list area” .
Double left click:

Using this type of selection on the items of the resource tree, the user can expand the tree
structure and activate the “Resource list area” displaying the same information described
above. When the tree node is expanded a double click will collapsethe tree node showing the
same information in the “Resource list area”.
2–1.1.3 Resource Detail Area
This area displays the detailed information of the selected object in the Resource list area. It also provides
the types of operations available
2–1.1.4 Button Policy
The possible buttons for selection are the following:
– Apply this button activates the “modify”, but it does not close the window.
– Cancel this button closes the window without modifying the parameters displayed in the window.
– OK this button activates the modify and closes the window
– Close this button closes the window
– Help this button provides the help management for the functions of the supporting window.
Critical configuration choices should require a warning message for user confirmation before to be
activated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 83 / 296
296
2–1.2 Introduction to the menu options
The menu bar allows to perform configuration and supervision functions on the Network Element.

This paragraph lists all menu options and then provides more details on the respective contained entries.

For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where they are detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
From Chapter 2–2 on page 89 details and operating information on all views are given.
In the menu bar, a number of permanent menu items are always displayed. Starting from the left, the
menus are:
– Permanent Menus
• Views (first column). See para.2–1.2.1 on page 85.
To navigate among the views and to set the TMN parameters.
• Configuration (second column). See para.2–1.2.2 on page 87.
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
• Diagnosis (third column). See para.2–1.2.3 on page 87.
To get information on the NE (alarms, performance monitoring, remote inventory).
• Supervision (fourth column). See para.2–1.2.4 on page 88.
To set the supervision states (i.e. Craft Terminal enabling).
• SW Download (fifth column). See para. 2–1.2.5 on page 88.
To manage the NE software (download, MIB management).
• Help (last column).
To activate the help on line.
The menu bar also comprises other menus, presented only when a specific option is selected.
– Other Menus
• Equipment
This menu is present only when the Equipment menu (selected in the View menu or in the
Equipment tab panel) is active. It allows to go back to the supporting equipment of the displayed
object.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 84 / 296
296
2–1.2.1 Views menu introduction
The menu on the left side of the screen, allows to navigate among the views and to set some parameters,
by means of the following entries:
– Previous: Goes back to the previous screen of the application.
– Open Object: Not active.
– Open in New
Window: Not active.
– Duplicate View in
New Window: Not active.
– Equipment: Opens the Equipment view.

Then the “Equipment” menu is available on the menu bar.
See Chapter 2–3 on page 127.
– External Points: Displays and sets the input/output environmental alarm.

– Line Interface: Opens the Line Interface view to configure all the tributary ports.
– Performance: Allows to manage the Performance monitoring.

– Radio: Allows to manage all the functions relevant to the radio channels.
– FSO: Allows to manage all the functions relevant to the FSO channel.
This menu is available in V 1.0.1 and V 1.0.2 only.
– Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.

This menu is available in V 1.0.1 and V 1.0.2 only for the Radio application.
– Loopback: Allows to manage the loopbacks available with the equipment.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 85 / 296
296
N.B. It is possible to enter directly menus Equipment, External Points, Line Interface, Performance,
Radio ( or FSO ), Protection Scheme, Loopback by clicking on the relevant tab panel above the
view area. Refer to Fig. 31. on page 86.

Tab panel
Fig. 31. Tab panels

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 86 / 296
296
2–1.2.2 Configuration menu introduction
This menu allows to set the general configuration of the NE and to show or modify some parameters, by
means of the following entries:
– NE Time: Displays and set the NE local time. See para. 2–2.1 on page 89.
– Network configuration: See para. 2–2.2 on page 90.
– Alarm Severities: Manages the Alarm Severity Assignment Profile.

See para. 2–2.3 on page 101.
– System setting: Allows the system configuration, providing the setting of all the parameters
for the NE setup. See para. 2–2.4 on page 106.
– Quick configuration: Allows a full system configuration through a guided procedure.

2–1.2.3 Diagnosis menu introduction
This menu allows to get information on the NE, by means of the following entries:
– Log Browsing: Manages the events stored in the NE.

Opens the following menu options:
• Alarm log
• Event log
• Software Trace log
– Current configuration
View: Displays the current configuration of the NE.
– Summary Block
Diagram View: Displays a global logical view (strictly related to the physical implementation)
highlighting a synthesis of all the alarms and statuses present in the system
(ODU+IDU).
– Abnormal
condition list: Displays the manually operations active in the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 87 / 296
296
2–1.2.4 Supervision menu introduction
This menu allows to set the supervision states of the NE, by means of the following entries (see chapter
2–8 on page 167) :

– Access State: Manages the supervision access to the NE, via CT or OS.
Opens the following menu options:
• OS
• Requested
– Restart NE: Reset of the NE software.

– SW key: Displays the type of the key stored in the flash card.
2–1.2.5 Download menu introduction
This menu allows to manage the NE software, by means of the following entries (see chapter 2–13 on page
211) :
– Server Access
Configuration: Manages the configuration of the FTP server to be used for the software
download to the NE.
– Initi SW download: Manages the software download to the NE.

– SW status: Shows and manages the status of the software packages installed in the NE
memory banks.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 88 / 296
296
2–2 CONFIGURATION
2–2.1 NE Time
The NE local time can be displayed and/or re–aligned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which you can set the local NE time.
Fig. 32. NE Time dialogue box
The NE Time dialogue box displays the current NE time and the current OS time.
To re–align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
With a click on the Daylight Saving Time (DST) check box the manual management of the summer time
takes place.
The Refresh pushbutton allows to read the time actually present in the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 89 / 296
296
2–2.2 Network Configuration
To get access the Network Configuration option select the Configuration pull down menu, as shown
in the following figure.

Fig. 33. Network Configuration menu
The Network Configuration allows to perform the following operations:
Local Configuration: defines the local NE addresses
Ethernet Configuration: defines the configuration parameters necessary to manage

the local NE providing a LAN Ethernet interface
IP Configuration which comprises:
IP static routing configuration: defines the Host/Network destination address for IP static
routing
OSPF Area configuration: defines the Open Shortest Path First address
IP Address configuration of
Point–To–Point Interfaces : defines the IP address of the interface which use the PPP
protocol
Routing information shows a summary of the information relevant to the routing

which has been configured.
The options are described in next paragraphs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 90 / 296
296
2–2.2.1 Local Configuration
Select the Configuration pull down menu.

Select the Network Configuration option and then, from the cascading menu, the Local Configuration
option.
The dialogue box opens ( see Fig. 34. on page 91 ) which allows to configure the local IP address of the
NE.
This local IP address is the IP address associated to the F interface and to the other interfaces which use
the PPP protocol (the 3 NMS channels).
Apply button is used to perform a configuration change of the data contained in the dialogue box and
closes it; the dialogue is visible until the end of the operations and a wait cursor is displayed.
Close button closes the dialogue.
Help button provides some useful information on the dialogue.
Fig. 34. Local Configuration dialogue box

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 91 / 296
296
2–2.2.2 Ethernet Configuration
Select the Configuration pull down menu.
Select the Network Configuration option and then, from the cascading menu, the Ethernet

Configuration option.
The dialogue box in Fig. 35. on page 92 opens, which allows to define the parameters necessary to
configure the Ethernet interface.
The following areas are present:
– IP Section which comprises:
• IP Address to be assigned to the N.E.

• IP Mask relevant to the IP address
• IP Routing Protocol can be only in “ None” state.If “OSPF” or “ Both“ options of Routing IP
Protocol field are selected, also the “ Associated OSPF Area “ must be set.
• OSPF Area poiner: if as IP Routing Protocol the OSPF protocol has been selected it is possible
to create OSPF areas.
– Enable which comprises two selections to Enable or Disable the Ethernet interface.
Refresh button refresh the information written in the upper port.

Apply button performs a configuration change of the data.
Close button closes the dialog without changes of the data.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 35. Ethernet Configuration dialogue box
ED 03
3DB 05653 CA AA 92 / 296
296
2–2.2.3 IP Configuration
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the IP Configuration option ( see Fig. 36. on page 93).
Fig. 36. IP configuration screen
2–2.2.3.1 IP static routing configuration
The dialog–box opens ( see Fig. 37. on page 94 ) and allows to configure the parameters for IP Static
Routing Configuration.
The following fields and data are present:
[1] IP Address: allows to define the IP address necessary to reach a

specific Host
[2] IP Mask: allows to define the IP Mask to reach a network
[3] Default Gateway IP Address: allows to define the address of the next hop gateway
[4] Interface type: allows to use point to point interfaces made available
by the NE.
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 93 / 296
296
Fig. 37. IP static routing configuration screen
By pressing Create pushbutton the screen in Fig. 38. on page 95 opens.
In the Host or Network Address Choice field select:
– Host to address to a single IP address;
– Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select:
– Default Gateway IP Address for the Ethernet interface;

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Point to Point Interface Index for the NMS channels (NMS–RF, NMS–V11, NMS–G703)
ED 03
3DB 05653 CA AA 94 / 296
296
Fig. 38. Create Static routing
If in the screen of Fig. 38. on page 95 the Default Gateway IP Address check box has been selected,
write in the Default Gateway IP Address field below the relevant IP address.
If in screen in Fig. 38. on page 95 has been selected the Point To Point Interface Index check box,
the screen in Fig. 39. on page 96 opens.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 95 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 39. Point To Point Interface Choice
296
3DB 05653 CA AA
In this screen one of the 3 NMS channels (NMS–RF, NMS–V11, NMS–G703) can be selected.
96 / 296
2–2.2.3.2 OSPF Area configuration
The dialog–box opens ( see Fig. 40. on page 97 ) and allows to configure the parameters for OSPF
(Open Shortest Path First) Area Table Configuration.
– OSPF Area IP Address

– OSPF Area Range Mask
– OSPF Area Stub
The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network)
in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
Fig. 40. OSPF Area configuration screen
WARNING: Area 0 is not managed.

1AA 00014 0004 (9007) A4 – ALICE 04.10
By pressing Create pushbutton the screen in Fig. 41. on page 98 opens.
N.B. 3 areas max. can be created.
ED 03
3DB 05653 CA AA 97 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 41. Create New OSPF Area
296
In the screen write the IP address, the IP mask and select the flag (True/False).
3DB 05653 CA AA
98 / 296
2–2.2.3.3 IP Address configuration of Point–To–Point Interfaces
The dialog–box opens ( see Fig. 42. on page 99 ) and allows to Enable or Disable the three NMS
channels, which use the PPP protocol.
OK button is used to perform a configuration change of the data contained in the dialog–box and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Fig. 42. IP Address configuration of Point–To–Point Interfaces screen

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 99 / 296
296
2–2.2.4 Routing information
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the Routing information option.

The dialog–box in Fig. 43. on page 100 opens.
Fig. 43. Routing information screen
This screen is a read–only screen and displays the routing parameters currently active on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 100 / 296
296
2–2.3 Alarm Severities
By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 44. on page
102 appears.
In this screen in the Profile Name field are listed the 4 default Alarm Severity Profiles:
– Profile “No Alarms”. With this profile all alarms are disabled.
– Profile “Primary Alarms”. This profile enables the emission of the primary alarms. General rules
used to define the alarms severity:
• MAJOR: the alarm affects the service (it is service affecting);
• MINOR or WARNING (according to the impact of the alarm): the alarm doesn’t affects the
service (with the exception of HighBER alarm, which MINOR alarm severity is defined, even if
it is service affecting).
– Profile “No Remote Alarms”. This profile enables the emission of the primary alarms plus EW and
LBER alarm. This profile uses the following rules to define the alarms severity:
• MAJOR: the alarm affects the service (it is service affecting);
• MINOR: the alarm is potentially service affecting but a protection has recovered the service;
• WARNING: the alarm cannot affect the service (independently from any protection).
– Profile “All Alarms”. This profile enables the emission of all the alarms (included AIS and RDI). This
profile uses the same severity of the “Primary alarm” profile, the only difference is that EW, LBER,
AIS and RDI alarms are emitted.
The rules used to define the alarm severity are the same of the “Primary alarm” profile.
N.B. In case of alarms affecting a protection different severities are used for SA and NSA. The same
severity is used both for SA and NSA in case of service independent alarms.
N.B. The rules used to define the profile alarms severity described above, are not applied to the
housekeeping alarms. In this case, in order to enhance the flexibility, a different severity is
assigned to each alarm profile (WAR, MIN and MAJ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 101 / 296
296
Fig. 44. Alarm Severities Profile
In the screen of Fig. 44. on page 102 are available 2 buttons:
– Close: to close the screen.

– Clone: to create a new Alarm Sevetiry Profile. To create a clone refer to para. 2–2.3.1 on page 103.
N.B. Only 2 new profiles can be created.
An Alarm Profile is the complete set of the equipment alarms with their severity in case of Service
Affecting situation and No Service Affecting situation.
Each alarm has its Service Affecting and No Service Affecting attribute, which can differ according to the
Alarm Severity Profile.
N.B. To some objects in the equipment (overhead alarm, input housekeeping alarm, tributaries etc.)
can be assigned an Alarm Profile.
To do this association:
– select the tab panel (Equipment, Line Interface, FSO etc.) in which is present the object
to be associated to a specific Alarm Severity Profile;
– select the object;
1AA 00014 0004 (9007) A4 – ALICE 04.10
– select the Configuration menu in the relevant Resource Detail Area;

– select in the Alarm Profile field the Alarm Profile to be associated.
ED 03
3DB 05653 CA AA 102 / 296
296
2–2.3.1 How to create a new Alarm Severity Profile
– Select in the screen of Fig. 44. on page 102 the Alarm Profile to be cloned.
– Click the Clone pushbutton.

– The screen of Fig. 45. on page 103 appears.
– Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 45. Name of a cloned alarm profile
– Select again the Alarm Severity option from the Configuration menu.
– Select the just created Alarm Profile (Link 1 in the example of Fig. 46. on page 103).
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 46. Clone of an Alarm Severity Profile
ED 03
3DB 05653 CA AA 103 / 296
296
– In this screen are available 4 buttons:
• Close: to close the screen without any change

• Rename: to change the name of the Alarm Severity Profile

• Modify: to modify the Alarm Severity Profile
• Delete: to delete the Alarm Severity Profile.
– Click on the Modify button.
– To modify the severity of an alarm click on the Service Affecting field click on the suitable alarm and
select a new severity (see Fig. 47. on page 104).
Fig. 47. Selection of a new severity in the Service Affecting field

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 104 / 296
296
– To modify the severity of an alarm click on the No Service Affecting field click on the suitable alarm
and select a new severity (see Fig. 48. on page 105).
Fig. 48. Selection of a new severity in the No Service Affecting field
– To save the changes in the Alarm Severity Profile click on Apply. (By clicking on Cancel you quit the
Alarm Severity Profile screen without any change) (see Fig. 48. on page 105).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 105 / 296
296
2–2.4 System Settings
This menu allows the system configuration, providing the setting of all the parameters for the NE setup.

The main window provides 3 tabbed–panels, one for each type of function to be managed:

– NE configuration (V 1.0.0 and V 1.0.1)
– NE configuration (V 1.0.2)
– Link Identifier
– Overhead
WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of the
configuration the “Restart NE” must be performed (refer to para. 2–8.2 on page 168).
WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of
PSU24), to insert the correct type enter the System Settings menu → NE configuration
tab panel; select the correct type; click on Apply and then restart the EC by entering
menu Supervision and by activating command ”Restart NE”.
2–2.4.1 NE Configuration (V 1.0.0 and V 1.0.1)
The user can view and define the NE configuration by selecting the “NE Parameters” tabbed panel.
The window displayed in Fig. 49. on page 106 will appear.
The field “Type” contains all the allowed configurations supported for the NE (radio and FSO). The
operator choice will be applied by selecting the related “Apply” button.
The “Structure” area displays the market, capacity and modulation and, if needed, the ability to change
it, according to NE market configured in the previous screen.
The field ”Market” contains two market types: ETSI or ANSI (refer to Tab. 1. and Tab. 2. ). The operator
choice will be applied by clicking the related “Apply” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 49. System Settings: NE configuration (V 1.0.0 and V 1.0.1)
ED 03
3DB 05653 CA AA 106 / 296
296
The information related to the modulation type is shown in the “Modulation” field. The possible values are
”4QAM” or ”16QAM”. The Capacity and the Modulation can be modified by selecting a different type
according to Tab. 1. for the Radio application and Tab. 2. for the FSO application and then selecting the
”Apply” button to send the new value.
N.B. From 4QAM (PTMax) to 16QAM

– the Alarm incompatible PTx is light ON
– Tx Power value value is empty
– to set new PTx value (range)
– the Alarm incompatible PTx is light OFF
The “Tributary Port Configuration” area is in the lower part of the window. The “Impedance” field allows
the operator to configure the impedance of the E1/DS1 tributary (unbalance 75 ohm or balance 120/100
ohm).
The impedance value will be applied by clicking on the related ”Apply” button.
Tab. 1. Radio application: Market, capacity and modulation
Market Capacity Modulation

ETSI 2xE1 4QAM
4xE1 4QAM / 16QAM
8xE1 4QAM / 16QAM
16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
ANSI 4xDS1 4QAM
8xDS1 4QAM / 16QAM
16xDS1 4QAM / 16QAM
1xDS3 4QAM / 16QAM
Tab. 2. FSO application: Market, capacity and modulation

ETSI 16xE1 4QAM
1xE3 4QAM
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 107 / 296
296
2–2.4.2 NE Configuration (V 1.0.2)
The user can view and define the NE configuration by selecting the “NE Parameters” tabbed panel.
The window displayed in Fig. 49. on page 106 will appear.

The field “Type” contains all the allowed configurations supported for the NE (radio and FSO). The
operator choice will be applied by selecting the related “Apply” button.
The “Structure” area displays the market, capacity and modulation and, if needed, the ability to change
it, according to NE market configured in the previous screen.
The field ”Market” contains two market types: ETSI or ANSI (refer to Tab. 1. and Tab. 2. ). The operator
choice will be applied by clicking the related “Apply” button.
Fig. 50. System Settings: NE configuration (V 1.0.2)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 108 / 296
296
The information related to the modulation type is shown in the “Modulation” field. The possible values are
”4QAM” or ”16QAM”. The operator choice will be applied by clicking the related “Apply” button.
N.B. From 4QAM (PTMax) to 16QAM

– the Alarm incompatible PTx is light ON

– Tx Power value value is empty

– to set new PTx value (range)
– the Alarm incompatible PTx is light OFF
The Capacity can be modified by selecting a different type according to Tab. 1. for the Radio application
and Tab. 2. for the FSO application and then selecting the ”Apply” button to send the new value.
N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field the explicit
confirmation shown in Fig. 51. is requested.
Fig. 51. Confirmation message
N.B. Only one change can be performed in this screen.

When the user confirms the change in the “Type” or “Market” or “Capacity” or “Modulation” field
all the other fields are disabled. To perform another change close the screen and enter again.
N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field (for the “Modulation”
only for the remote NE configuration) at the completion of the operation the CT forces the JUSM
closing with the following warning message (see Fig. 52. ).
Fig. 52. USM closing warning message

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 109 / 296
296
The “Tributary Port Configuration” area is in the lower part of the window. The “Impedance” field allows
the operator to configure the impedance of the E1/DS1 tributary (unbalance 75 ohm or balance 120/100
ohm).

The impedance value will be applied by clicking on the related ”Apply” button.

Tab. 3. Radio application: Market, capacity and modulation

ETSI 2xE1 4QAM
4xE1 4QAM / 16QAM
8xE1 4QAM / 16QAM
16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
ANSI 4xDS1 4QAM
8xDS1 4QAM / 16QAM
16xDS1 4QAM / 16QAM
1xDS3 4QAM / 16QAM
Tab. 4. FSO application: Market, capacity and modulation

ETSI 16xE1 4QAM
1xE3 4QAM
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 110 / 296
296
2–2.4.3 Link Indentifier
The ”Link Identifier” area, shown in Fig. 53. on page 111, displays the current values of parameters
related to link management and, if necessary, modifies them.
The operator choices will be sent to NE by clicking on the related “Apply” button. The parameters involved
are:
– Mismatch detection: this field disables or enables the link identifier mismatch detection.
– Expected Value: this field is the link identifier value expected by the NE (allowed values: 1 to 16).
– Sent Value: this field is the link identifier value transmitted by the NE (allowed values: 1 to 16).
Fig. 53. System Settings: Link Identifier
The operator choice will be applied by selecting the related “Apply” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 111 / 296
296
2–2.4.4 Overhead
The ”Overhead” tabbed panel identifies the parameters for the management of the phone number and
auxiliary interface (Fig. 54. on page 112).

Fig. 54. Overhead Configuration
The field ”Phone Number” in the ”Order Wire Configuration” area allows the operator to read and write
the station number associated to the Engineering Order Wire to be used in the selective call. Possible
values are: 10–99.
N.B. Number 00 is the value associated to the general call.
The parameter will be sent to NE by clicking on the related “Apply” button.
The field ”Type” in the ”Auxiliary Interface Configuration” area allows the operator to change the
interface of the auxiliary channels.
The parameter will be sent to NE by clicking on the related “Apply” button.
The field Alarm Profile allows to associate to the Overhead alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator (refer to para. 2–2.3.1 on page 103).
To associate a different Alarm Profile click on the selection button and make the selection among the
available Alarm Profiles.
N.B. the default associated Alarm Profile is the Primary Alarm profile.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 112 / 296
296
2–2.5 Quick Configuration Procedure
This procedure allows a full system configuration through a guided process, based on a reduced set of
screens. The related windows will be displayed by a “Wizard Tool” according to a specific order.
To start this application, select the “Quick Configuration” option from the “Configuration” menu. The
window in Fig. 55. on page 114 will appear. This window is the first step of the procedure.
The procedure consists of different steps according to the configuration:
– 1+0 configuration:
• 6 steps for the simplified configuration
• 12 steps for the advanced configuration (the advanced configuration can be activated in step
5)
– 1+1 configuration:
• 7 steps for the simplified configuration
• 13 steps for the advanced configuration (the advanced configuration can activated in step 6)
Note on the use of the buttons available in the screens:
– Back: by clicking on this button the procedure goes back to the previous step
– Next: by clicking on this button the procedure goes on the next step
– Finish: this button is active only in the last step. By clicking on this button the operator confirms the
configuration and the new parameters are sent to the equipment.
– Cancel: by clicking on this button the operator quits the procedure without any change in the
configuration.
– Help: by clicking on this button the operator calls the help–on line.
In the following is explained step by step the most complete procedure for 1+1 configuration.
WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of the
configuration the “Restart NE” must be performed (refer to para. 2–8.2 on page 160).
WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of
PSU24), to insert the correct type enter the System Settings menu → NE configuration
tab panel; select the correct type; click on Apply and then restart the EC by entering
menu Supervision and by activating command ”Restart NE”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 113 / 296
296
Step 1

Fig. 55. Quick Installation Procedure: NE Configuration (Step 1)
The first step provides a screen to configure two NE parameters:

– Market (ETSI or ANSI); for FSO application the market is ETSI only;
– Type configuration.
The possible selections for the Type field are:

– Radio application:
• 1+0 (PSU24 or PSU4860): unprotected configuration
• 1+1 HST (PSU24 or PSU4860): Hot Standby protected configuration
• 1+1 FD (PSU24 or PSU4860): Frequency Diversity protected configuration
• 1+0 HST EXP (PSU24 or PSU4860): Hot Standby extendable configuration
• 1+0 FD EXP (PSU24 or PSU4860): Frequency Diversity extendable configuration
– FSO application:
• 1+0 FSO (PSU24,PSU4860,PSUM4860H): unprotected configuration
The market choice implies a first selection of possible frame structure. The type definition implies the
equipment configuration and other related functions: for example, the protection schemes supported.
N.B. for V 1.0.2 only: For the Remote NE in this step the Type and the Market cannot be modified.
To modify them the System Settings menu must be used (refer to para. 2–2.4.2
on page 108).
1AA 00014 0004 (9007) A4 – ALICE 04.10
To go to step 2 click on button “Next”.
ED 03
3DB 05653 CA AA 114 / 296
296
Step 2
The screen shown in Fig. 56. on page 115 provides the fields to set the Structure of the Frame
configuration (Capacity and Modulation).
The capacity implies the choice of modulation; for example, if the tributary structure is 2E1 (for ETSI
market) only 4QAM modulation scheme is supported.
N.B. The association between Capacity and Modulation is shown in Tab. 1. and Tab. 2. on page 107.
Moreover, if the tributary selected is E1 the Impedance also must be selected in the Tributary Port
Configuration (unbalance 75 ohm or balance 120 ohm).
Fig. 56. Quick Installation Procedure: Frame Configuration (Step 2)
In the screen displayed in Fig. 56. on page 115 (and in the following Steps), the “Back” button is enabled
also. It allows the operator to turn back and change the parameters configured in the previous screen.
N.B. in FSO application the applicable capacity is 16E1 or E3 only and modulation is 4 QAM only.
N.B. for V 1.0.2 only: For the Remote NE in this step the Capacity and the Modulation cannot be
modified. To modify them the System Settings menu must be used (refer to
para. 2–2.4.2 on page 108).
1AA 00014 0004 (9007) A4 – ALICE 04.10
To go to the next step click on button “Next”.
To go back to the previous step click on button “Back”.
ED 03
3DB 05653 CA AA 115 / 296
296
Step 3
Step 3 allows the operator to choose, for each tributary configured, the signal mode or disable it
(Fig. 57. on page 116).

Fig. 57. Quick Installation Procedure: Tributaries Configuration (Step 3)
By clicking on the one facility button (“All Framed”, “All Unframed” and “All Disabled”), the operator can
configure all the tributaries with the same values; otherwise he can apply all configuration for each tributary
by selecting the related value from the relevant scroll list.
N.B. This procedure can be used also after the first configuration to perform multiple changes in the
configuration both in the local and in the remote NE.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 116 / 296
296
Step 4
Step 4 allows the operator to choose the restoration criteria (revertive or not revertive for the 3 possible
protections available in the 1+1 configuration (Fig. 58. on page 117):
– Radio protection (Rx EPS)
– Mux protection (Tx EPS)
– HST Tx protection (RF Hot Stand–by)
Fig. 58. Quick Installation Procedure: Tributaries Configuration (Step 4)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 117 / 296
296
Step 5
Step 5 allows the operator to define the basic paramters for each configured channel. The related screen
is shown in the Fig. 59. on page 118:

Fig. 59. Quick Configuration Procedure: Channels Configuration (Step 5)
In the Channel Configuration area the ATPC can be Enabled or Disabled. If enabled, the other ATPC
parameters (min. value, max. value and Rx threshold) must be configured in RTPC & ATPC menu in the
Radio domain (refer to para. 2–5.4 on page 146).
If ATPC is disabled in the RTPC area the power (costantly transmitted) can be selected by writing the
suitable value in the Tx power field.
In the Frequency Value area the Tx operating frequency must be written in the Tx Freq field.
N.B. for V 1.0.2 only: The Tx Frequency value can be changed only on the Local NE (To change the
Tx frequency for the Remote NE use the Radio menu – refer to para. 2–5.3
on page 145).
The Rx Frequency is automatically changed according to the frequency shifter available with the ODU.
All the values must be selected according to the relevant allowed ranges (shown between brackets).
N.B. In case of 1+1HST the choices will be applied to both “channels”. In case of 1+1FD, the same
screen will be reproposed for channel 0 with the same choices applied for channel 1, with the
possibility to change the frequency, but without any possibility to change ATPC/RTPC selection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 118 / 296
296
Step 6
Step 6 performs the network configuration (Fig. 60. on page 119). This window allows to enter to IP
address associated to the F interface of the NE.
N.B. for V 1.0.2 only: The IP Address can be changed only on the Local NE (To change the IP
Address for the Remote NE use the menu Configuration → Network
Configuration → Local Configuration – refer to para. 2–2.2.1 on page 91).
Fig. 60. Quick Configuration Procedure: Local IP Address (Step 6)
For an advanced network configuration the operator must select the “Advanced Configuration” flag.
If the flag has been selected, the screens in the next steps allow the operator to perform a complete
configuration of all the Network parameters.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 119 / 296
296
Step 7
Step 7 allows to configure one or more OSPF Areas (3 areas max.) (Fig. 61. on page 120).

Fig. 61. Quich Installation Procedure: OSPF Area Configuration (Step 7)
To create a new area write a number in the Area Id field, in the IP address field write the address and in
the Range Mask field enter the range associated to the OSPF area and click on Add button.
If the OSPF area must be a stub area, make the selection in the Stub Area check box.
In the upper part of the screen the new OSPF area will appear.
To remove or change an OSPF Area Configuration select the Area in the upper part and click on Remove
or Change button.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 120 / 296
296
Step 8
The following windows for Network Configuration allow the complete IP configuration.
Step 8 configures one or more Static Routers (Fig. 62. on page 121).
Fig. 62. Quick Installation Procedure: IP Static Router Configuration (Step 8)
[1] Host Address: allows to define the IP address necessary to reach a specific Host.
[2] Network Address: it is in alternative to the Host Address; allows to define the IP Mask to reach
a network.
[3] Gateway Address: allows to define the address of the next hop gateway.
[4] PPP: it allows to use the point to point interfaces (the 3 NMS channels) available
with the NE.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 121 / 296
296
Step 9
Step 9 allows the configuration of the NMS–RF channel (Fig. 63. on page 122):

Fig. 63. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9)
The “NMS–RF” interface is a communication interface based on the use of an inframe RF proprietary 64
kbit/s channel. Through the “NMS–RF” interface the NE can exchange management messages with a
remote OS (or Craft Terminal) station.
The NMS–RF channel can be Enabled or Disabled by selection in the NMS RF field.
If enabled, in the Remote Address field will appear the IP address of the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the
associated OSPF area.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 122 / 296
296
Step 10
Step 10 allows the configuration of the NMS–V11 interface (Fig. 64. on page 123):
Fig. 64. Quick Configuration Procedure: NMS–V11 Interface Configuration (Step 10)
Through the “NMS–V11” interface the NE can exchange management messages with an OS (or Craft
Terminal) in the same station.
The NMS–V11 channel can be Enabled or Disabled by selection in the NMS V11 field.
In the Routing IP Protocol field enter the used IP protocl and in case of OSPF protocol select also the
In the PPP_MODE field the following selections can be made:
– DTE mode:
to interface an SDH service channel, where DCE mode is not available because of the common
synchronisation of the SDH network.
– Co–directional mode:
to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 123 / 296
296
Step 11
Step 11 allows the configuration of the NMS–G703 interface (Fig. 65. on page 124):

Fig. 65. Quick Configuration Procedure: NMS–G703 Interface Configuration (Step 11)
Through the “NMS–G703” interface the NE can exchange management messages with an OS (or Craft
Terminal) in the same station.
The NMS–G703 channel can be Enabled or Disabled by selection in the NMS G703 field.
In the Routing IP Protocol field enter the used IP protocl and in case of OSPF protocol select also the
In the PPP_MODE field the following selections can be made:
– DTE mode:
to interface an SDH service channel, where DCE mode is not available because of the common
synchronisation of the SDH network.
– Co–directional mode:
to link adjacent AWY or to interface MUX based on 64 kbit/s, avoiding any V.11/G.703 adapter.
– In frame E1–DS1 mode:

as alternative mode is possible to drop in the G703 64 kbit/s in Tributary 1, Time Slot 1 allowing the
transport of supervision messages along the traffic path.
1AA 00014 0004 (9007) A4 – ALICE 04.10

ED 03
3DB 05653 CA AA 124 / 296
296
Step 12
Step 12 (Fig. 66. on page 125) allows to configure the Ethernet Interface.
Fig. 66. Quick Installation Procedure: Ethernet Configuration (Step 12)
The Ethernet interface can be Enabled or Disabled by selection in the Ethernet configuration field.
If enabled, in the relevant fields below enter the IP address, the IP mask and select the Routing IP
protocol. If the selected routing protocol has been OSPF, select also the area number in the Associated
OSPF Area field.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 125 / 296
296
Step 13
Step 13 is the last step. The screen shown summarizes all the parameters configured during this
procedure and some relevant parameters with default values (Fig. 67. on page 126).

Fig. 67. Quick Configuration Procedure: Summary (Step 13)
All the parameters can still be changed by clicking on the “Back” button. The operator can navigate back
to the desired screen and set the new values.
At the end the operator can confirm the selections by pressing the “Finish” button. All the parameters will
be stored and sent to the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 126 / 296
296
2–3 EQUIPMENT
This chapter describes the types of functions offered to the user for Equipment Management.
N.B. Please refer to Appendix A on page 243 for the detailed description of equipment functions and
components.
The equipment domain deals with the management of the NE as a whole and its physical components
(subrack, boards,..)
The main screen of the Equipment tab panel is shown in Fig. 68. on page 127 for 1+0 FSO configuration.
The main screen of the Equipment tab panel is shown in Fig. 69. on page 128 for 1+0 Radio configuration.
The main screen of the Equipment tab panel is shown in Fig. 70. on page 128 for 1+1 Radio configuration.
In the Resource List Area is shown a graphical representation of the Equipment, which consists of an IDU
and an ODU.
A coloured ball gives information on the status of the associated object. The colour differs according to
the severity of the alarms:
– Green: no alarm
– White: indetermination alarm active (not operative)
– Cyanic: warning alarm active
– Yellow: minor alarm active
– Brown: major alarm active
– Red: critical alarm active
Equipment Status
FSO ODU ODU Status
IDU
IDU Status
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 68. 1+0 FSO Equipment view
ED 03
3DB 05653 CA AA 127 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
IDU
ODU
ODU
IDU
Fig. 70. 1+1 Radio Equipment view

Fig. 69. 1+0 Radio Equipment view
IDU Status
IDU Status
Equipment Status
Equipment Status
ODU Status
296
3DB 05653 CA AA
ODU Status
128 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 71. 1+0 EXP Radio Equipment view
296
3DB 05653 CA AA
129 / 296
2–3.1 IDU level
To enter the IDU level click on the IDU object in the Resource Tree Area or double click on the IDU image
in the Resource Detail Area.

2–3.1.1 1+0 configuration
Configuration available both with 9400AWY and 9400FSO.
The screen in Fig. 72. on page 130 will appear.
IDU Status
ACCESS BOARD Status
IDU ACCESS BOARD

MAIN BOARD
MAIN BOARD
Status
Fig. 72. 1+0 IDU view
The IDU consists of 2 boards:
– Access board
– Main board
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 130 / 296
296
2–3.1.2 “1+0 extendable” and “1+1” configuration
Configurations available with 9400AWY only.

The screen in Fig. 73. on page 131 will appear.

IDU Status
IDU
ACCESS BOARD Status
ACCESS BOARD FANS BOARD

MAIN BOARD
EXTENSION BOARD FANS
EXTENSION MAIN BOARD BOARD
BOARD Status Status
Status
Fig. 73. 1+1 IDU view
The IDU consists of 4 boards:

– Access board
– Main board
– Extension board (not present in “1+0 extendable” configuration)
– Fans board
2–3.1.3 Procedure for configuration change from “1+0 extendable” to “1+1”
There are many ways to proceed for this configuration change, but some of them give no good results.
Thus, follow this procedure to obtain a correct result, without traffic impacts:
1) Install the second ODU unit and the relevant IDU–ODU cable (refer to 9400AWY Installation
Handbook)
2) On IDU, extract the dummy plate closing the Extension board slot
3) Get the Extension board, switch off it, insert it in the shelf and connect the IDU–ODU cable
4) Set, by Local ECT, 1+1 configuration using System Setting function
5) Restart the NE
6) Switch on the Extension board
7) Proceed as specified in the 9400AWY Installation Handbook and Line–Up Guide for the
1AA 00014 0004 (9007) A4 – ALICE 04.10
operations regarding the second ODU installed. In particular, set, by Local CT, Tx Power and
Tx Frequency values related to second ODU.
ED 03
3DB 05653 CA AA 131 / 296
296
2–3.1.4 Board level
To enter a board click on the object in the Resource Tree Area or double click on the board image in the
Resource Detail Area.

As example in Fig. 74. on page 132 is shown the screen of the MAIN IDU board.
BOARD Status
Fig. 74. Main board view

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 132 / 296
296
2–3.2 ODU level
To enter the ODU level click on the ODU object in the Resource Tree Area or double click on the ODU
image in the Resource Detail Area.
The screen in Fig. 75. on page 133 will appear in case of FSO configuration.
The screen in Fig. 76. on page 133 will appear in case of Radio configuration.
Fig. 75. FSO ODU view

1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 76. Radio ODU view
ED 03
3DB 05653 CA AA 133 / 296
296
2–3.3 Tab panels in the Resource Detail Aarea
2–3.3.1 Alarms

The Alarms tab panel provides the fault mangement, which checks the current state of alarms related to
the selected object (Fig. 77. on page 134).
Fig. 77. Alarm tab panel for a selected object
The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are
highlighted. When the alarm disappears it is automatically cleared in the screen.
By putting a tick in the Include alarms from sub–nodes box the alarms currently active in the sub–nodes
of the object will also appear.
For every alarm the following information is given:
– Severity: the severity associated to the alarm and assigned in the Alarm Profile
– Event Time: the time of the generation of the alarm
– Entity: the entity involved in the alarm
– Probable Cause: the probable cause of the alarm
– Managed Object Class: the class of the alarm.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 134 / 296
296
2–3.3.2 Configuration
The “User Label”’ field (Fig. 78. ) only display the label associated to the selected node in the tree.
The field Alarm Profile allows to associate to the object alarms a particular Alarm Profile: a default alarm
profile or an Alarm Profile previously created by the Operator (refer to para. 2–2.3.1 on page 103). To
associate a different Alarm Profile click on the selection button and make the selection among the available
Alarm Profile.
Fig. 78. Configuration tab panel for a selected object
2–3.3.3 Remote Inventory
The information about the unit can be read in the Remote Inventory panel in the Resource Detail Area
as following window shows (Fig. 79. on page 135):
Fig. 79. Remote Inventory tab panel for a selected object

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 135 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
136 / 296
2–4 LINE INTERFACE
This chapter describes the type of functions available for Line Interface Management.
The Line Interface domain deals with the management of the aggregate frame and tributary ports (line
side).
The Line Interface view allows the user to manage the resources of a PDH signal, i.e. frames, tributary
ports (line), etc.
This domain view consists of the following areas (Fig. 80. on page 137):
– Resource Tree Area: displays the frames and tributary ports sorted by the channel number.
– Resource List Area: displays tabular information about the selected resource in the tree area.
– Resource Detail Area: displays, through tabbed windows, the selected object’ s properties in list
area. This area performs the available functions for involved resource.
Fig. 80. Line Interface View
In the Resource List Area is given the information related to the tributaries:
– Type Interface (E1/E3, DS1/DS3)

– Port Number: the port for a given channel and type of port
– Channel Number: the number of a channel
– Rate/Modulation: the bit rate of the tributary
– Signal Mode: the type of frame (Unframed/Framed/Disabled)
1AA 00014 0004 (9007) A4 – ALICE 04.10
To change the Signal Mode select the tributary and change the Signal Mode field in the Resource Detail
Area.
ED 03
3DB 05653 CA AA 137 / 296
296
2–4.1 Tab panels in the Resource Detail Area
2–4.1.1 Alarm

The fault mangement checks the current state of alarms related to the selected tributary.
It is provided by the alarm panel like the one explained in para. 2–3.3.1 on page 134.
2–4.1.2.1 E1/E3 tributaries
The window, shown in Fig. 81. on page 138 and Fig. 82. on page 138, performs all available functions for
a tributary port.
The managed tributary types are: E1, E3.
To define the involved ports, the channel selection in the tree view is first required; therefore the selection
of the desired tributary port in the tabular view enables the “Resource Detail list” to show the available
functions for the single one resource.
Fig. 81. Line Interface View: E1 Tributary Port
Fig. 82. Line Interface View: E3 Tributary Port

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 138 / 296
296
In Fig. 81. on page 138 and Fig. 82. on page 138 the following fields are read only fields:
– Interface Type (E1, E3)
– Port Number: identifies the ports for a given channel and type of port
– Channel Number
The fields, which can be changed, are:
– Signal Mode
– Tx RAI Insertion
– Rx RAI Insertion
– Alarm Profile
Signal Mode (for E1 tributary)
The possible values are:
– Framed for the framed received signal
– Unframed for the unframed received signal
– Disabled
The current state can be modified selecting a different signal mode value and then click on the ”Apply”
button to send the new value to NE.
Signal Mode (for E3 tributary)
– Framed G.751 for the framed received signal
– Framed G.753 for the framed received signal (not applicable)
– Disabled
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 139 / 296
296
Tx RAI Insertion (for E1 tributary only)
This feature is available for framed signals only.
This field refers to the insertion of the RAI signal in Tx side. The possible values are:

– Inibited: it is not possible to force the RAI insertion
– Forced: the RAI insertion is performed
– Enabled: the RAI insertion is possible.
Rx RAI Insertion (for E1 tributary only)
This feature is available for framed signals only.
This field refers to the insertion of the RAI signal in Rx side. The possible values are:
– Inibited: it is not possible to force the RAI insertion
– Forced: the RAI insertion is performed
– Enabled: the RAI insertion is possible.
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm
Alarm Profile.
N.B. the default associated Alarm Profile is the No Alarm profile.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 140 / 296
296
2–4.1.2.2 DS1/DS3 tributaries
The window, shown in Fig. 83. on page 141 and Fig. 84. on page 141, performs all available functions for
a tributary port.
The managed tributary types are: DS1, DS3.
To define the involved ports, the channel selection in the tree view is first required; therefore the selection
of the desired tributary port in the tabular view enables the “Resource Detail list” to show the available
functions for the single one resource.
Fig. 83. Line Interface View: DS1 Tributary Port
Fig. 84. Line Interface View: DS3 Tributary Port
In Fig. 83. on page 141 and Fig. 84. on page 141 the following fields are read only fields:
– Interface Type (DS1/DS3)

– Port Number: identifies the ports for a given channel and type of port
– Channel Number
The fields, which can be changed, are:
– Signal Mode
– Line Coding (AMI/B8ZS: for DS1 tributary only)
– Line length (0–133,133–266, 266–399, 399–533, 533–655: for DS1 tributary only)
– Alarm Profile
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 141 / 296
296
Signal Mode (for DS1 tributary)
– Framed SF for the Super Framed received signal

– Framed ESF for the Extended Super Framed received signal
– Disabled
Signal Mode (for DS3 tributary)
– Framed for the framed received signal

– Disabled
Line Coding (for DS1 tributary only)
This field refers to the coding relevant to the tributary signal. The possible values are:
– B8ZS
– AMI
Line Length (for DS1 tributary only)
This field refers to the length of the connected line. The possible values are:
– 0–133
– 133–266
– 266–399
– 399–533
– 533–655
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm
1AA 00014 0004 (9007) A4 – ALICE 04.10
Alarm Profile.
N.B. the default associated Alarm Profile is the No Alarm profile.
ED 03
3DB 05653 CA AA 142 / 296
296
2–5 RADIO
The Radio domain view allows the user to manage the resources of the radio transmission channel.
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio ports
etc).
– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource List Area: displays tabular information about the selected resource in tree area.
– Resource Detail Area: displays, through tabbed windows, the object’ s properties selected in the
list area. This area enables to execute the available functions for involved resource.
Fig. 85. Radio Domain View
Five tab panels are present in the Resourse Detail Area:
– Alarms: shows the active alarms (refer to para. 2–5.1 on page 144)
– Configuration: configures some radio parameters (refer to para. 2–5.2 on page 144)
– Frequency: sets the Tx RF frequency (refer to para. 2–5.3 on page 145)
– RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (refer
to para. 2–5.4 on page 146)
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–5.5 on page 147).
ED 03
3DB 05653 CA AA 143 / 296
296
2–5.1 Alarm
The fault mangement allows to check the current state of alarms related to the selected object.

It is provided by the alarm panel like that shown in para. 2–3.3.1 on page 134.

2–5.2 Configuration
The window shown in Fig. 94. on page 154 performs all the available functions for a Radio PDH port.
To define the involved port, first select the port/channel in the tabular view: this selection enables the
“Resource Detail list” to show the available functions for the single resource.
2–5.2.1 Local or Remote Transmitter Mute
The information related to the transmitter status is shown in the “Tx Mute” field. To change the transmitter
status choose the desired value (ON for Tx Squelched and OFF for Tx not Squelched) and press the
related “Apply” button.
2–5.2.2 ODU service kit
This field is a read–only field, which displays the state of the Portable Service Kit (connected or not to the
ODU).
2–5.2.3 Alarm Profile
The field Alarm Profile allows to associate a particular Alarm Profile to the object alarms: a default alarm
associate a different Alarm Profile click on the selection button and select among the available Alarm
Profile.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 144 / 296
296
2–5.3 Frequency
This menu (Fig. 86. on page 145) allows to read and, if necessary, to set the frequency parameters.
The information shown concerns the port/channel selected in the Resource Tabular View.
Fig. 86. Radio Frequency menu
2–5.3.1 Tx Radio Frequency
The ”Tx Freq” field in the “Frequency Value” area of tabbed window (Fig. 86. on page 145) shows the
current value of the transmission radio frequency (expressed in kHz). To change this parameter write the
new value in the field and press the ”Apply” button.
The new value must be within the allowed radio frequency range. The allowed range is shown in “Min/Max
Value” fields.
N.B. During the command setting the CT is frozen. Waiting time: max. 30’.
2–5.3.2 Rx Radio Frequency
The ”Rx Freq” field in the “Frequency Value” area of the tabbed window (Fig. 86. on page 145) shows the
current value of the receive radio frequency (expressed in kHz).
It is automatically changed as a consequence of the definition of the Tx frequency according to the

1AA 00014 0004 (9007) A4 – ALICE 04.10
Frequency Shifter.
ED 03
3DB 05653 CA AA 145 / 296
296
2–5.4 RTPC & ATPC
This menu (Fig. 87. on page 146) allows to read and, if necessary, to set the Tx power parameters.
The shown information is related to the channel selected in the Resource Tabular View.

Fig. 87. Rtpc & Atpc
2–5.4.1 ATPC
The ATPC can be Enabled or Disabled.

The new value will be applied when the ”Apply” button is pressed. If the ATPC has been enabled, the
ATPC Range and ATPC Rx Threshold fields must be filled.
2–5.4.2 Tx Nominal Power
The “Nominal Value” field in the “RTPC” area (Fig. 87. on page 146) is a read–only field and shows the
nominal value of the transmitted power (expressed in dBm).
2–5.4.3 Tx Current Power
The “Tx Power” field in the “RTPC” area (Fig. 87. on page 146) shows the current value of Tx power
(expressed in dBm), when the ATPC is disabled . In this case, it is possible to modify this value ERROR
FREE in ATPC Range (Pnom –20 db) with 2 dB max step allowed, by writing the new value and by pressing
the related “Apply” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. During the command setting the CT is frozen. Waiting time: < 15’.
The new value must be within the allowed transmitted power range. This range is shown in the “Power
Value” label of “RTPC” area.
If the Atpc is enabled, the Tx power value cannot be modified.
ED 03
3DB 05653 CA AA 146 / 296
296
2–5.4.4 ATPC Range
The Min Value and Max Value, for Tx Range in the Atpc management, are shown in the ”Atpc Range”
area. The min and max level can be changed by writing the new value in the field.
When the ”Apply” button is pressed the new values will be applied.
2–5.4.5 ATPC Rx Threshold
The value of the power low threshold can be changed by writing the new value in the field.
When the “Apply” button is pressed the new values will be applied.
2–5.5 Power Measurement
The Power Measurements capability is performed through the “Power Meas” tabbed panel in the resource
detail view (Fig. 88. on page 147).
Fig. 88. Power Measurements

1AA 00014 0004 (9007) A4 – ALICE 04.10
The Measurement screen allows the operator to set initial parameters for the required measurement.
ED 03
3DB 05653 CA AA 147 / 296
296
“Measurement interval” fields allow the operator to set the time–duration of the measurement. The
default is Days: 7, Hours: 0, Minutes: 0. A 7–day measurement interval is also the maximum allowed
interval.

“Sample time” field is the period between two consecutive measurement samples. The choice is among

2, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and name for this file is displayed to the
operator. The file is stored in the ALCATEL/CT–Kv3.0.1 directory.
N.B. The file name must not include the following characters: \ ? : * “ < > |.
The log file contains the sample value and records the measurement up to a maximum dimension ( 7 days
for a 2 s sample time).
By clicking on the ”Start“ button the screen “ Power Measurement Graphic “ appears (see Fig. 97. on
page 157).
The Power Measurement Graphic is available only if the CT is connected to the NE.
The screen in Fig. 89. shows the Tx and Rx measurements related to the local NE.
Through this screen the operator can see, in real time, the power transmitted by the local and remote
transmitter (Tx) and the power received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the
Rx curves (local and remote). Note that the colors represent the linked end–point of the two NE; for
example, if the local TX is blue, the remote receiver will also have the same color.
The top of the screen offers all the characteristics present in the current measurement:
– Radio port: gives the symbolic name associated to the radio channel being analized;
– Sample time: indicates the frequency used to send the measurement requests to NE;
– Start time: is the first request time;
– Stop time: is the interval time selected in the previous parameters window, added to the start time;
– Time: is the current response time;
– Log File: is the complete pathname of the file where the received values are stored.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 148 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 89. Power Measurement Graphic
296
3DB 05653 CA AA
149 / 296
By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 89. on
page 149), a new table appears (Fig. 90. on page 150); this table shows the following relevant values of
the received and transmitted power:

– Tx Local End

• max TX local value and date when this value was received for the first time.
• min. TX local value and its current date when this value was received for the first time.
• current TX local value and its current date.
– Tx Far End
• max TX remote value and date when this value was received for the first time.
• min. TX remote value and its current date when this value was received for the first time.
• current TX remote value and its current date.
– Rx Local End
• max Rx local value and date when this value was received for the first time.
• min. Rx local value and its current date when this value was received for the first time.
• current Rx local value and its current date.
– Rx Far End
• max Rx remote value and date when this value was received for the first time.
• min. Rx remote value and its current date when this value was received for the first time.
• current Rx remote value and its current date.
N.B. PTx and PRx levels software readings tolerance is:

– PTx = Real Value ± 3dB
– PRx = Real Value ± 5dB
Fig. 90. Power Meas Details

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 150 / 296
296
2–5.5.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button. The directory of the CT automatically opens
to navigate and get the power measurement file.
N.B. as default, the measurement files are stored in the ALCATEL/CT–Kv3.0.1 directory and have
extension .txt.
Fig. 91. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 88. on page 147 to open the file.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 92. Example of “Power Measurement File Reading“
The button in the lower part of the window allow to flow the graph within the measurement interval.
ED 03
3DB 05653 CA AA 151 / 296
296
Select the .txt file and click with the mouse right push–button to open .txt file with a text editor (e.g.
WordPad) and to see the power information in tabular mode (see Fig. 93. on page 152).

Fig. 93. Example of Power Measurement File Reading (with WordPad)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 152 / 296
296
2–6 FSO
N.B. This menu is available in V.1.0.1 and V.1.0.2 only.

The FSO domain view allows the user to manage the resources of the FSO transmission channel.
This domain view consists of the following areas:
– Resource Tree Area: displays the FSO port.
– Resource List Area: displays tabular information about the selected resource in tree area.
– Resource Detail Area: dislpays, through tabbed windows, the object’ s properties selected in the
list area. This area enables to execute the available functions for involved resource.
In the Resource Tree Area the following objects can be selected:
– Channel#1 refer to para. 2–6.1 on page 154
– FSO Port#1 – Ch#1 refer to para. 2–6.2 on page 155
– Laser#1 or Laser#2 refer to para. 2–6.3 on page 161

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 153 / 296
296
2–6.1 Channel#1
By selecting the Channel 1 object in the Resource Tree Area the screen in Fig. 94. on page 154 appears:

Fig. 94. FSO Domain View
In the Resource List Area is shown the following information:
– Type Interface: the type of the interface (FSO Port only)
– Port number: the number of the port (port 1 only)
– Channel number: the number of the channel (channel 1 only)
– Heater status: the status of the heater installed inside the FSO ODU (Off/On). To activate the Heater
select FSO Port#1 – Ch#1 in the Resource Tree Area and select Configuration in the Resource
Detail Area.
– Rx Power: the power of the received signal in dBm
– Temperature: the internal temperature inside the FSO ODU measured by an internal temperature
sensor.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 154 / 296
296
2–6.2 FSO Port#1 – Ch#1
By selecting the FSO Port#1 – Ch#1 object in the Resource Tree Area the screen in Fig. 95. on page 155
appears.
Fig. 95. FSO port configuration
– Laser Index: the identification number of the 2 Lasers installed in the FSO ODU.
– Laser Status: the status of the Laser (On/Off). To switch on or off a Laser select the Laser object in
the Resource Tree Area and select Configuration in the relevant Resource Detail Area.
Three tab panels are present in the Resourse Detail Area:
– Alarms: shows the active alarms (refer to para. 2–6.2.1 on page 156)
– Configuration: configures some FSO parameters (refer to para. 2–6.2.2 on page 156)
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–6.2.3 on page 156).
ED 03
3DB 05653 CA AA 155 / 296
296
2–6.2.1 Alarm
The fault mangement allows to check the current state of alarms related to the selected object.
It is provided by the alarm panel like that shown in para. 2–3.3.1 on page 134.

The window shown in Fig. 95. on page 155 performs all the available functions for the FSO port.
To define the involved port, first select the port/channel in the tabular view: this selection enables the
“Resource Detail list” to show the available functions for the resource.
2–6.2.3 Measurements
The Measurement screen (see Fig. 96. on page 156) allows the operator to set initial parameters for the
required measurement.
“Measurement interval” fields allow the operator to set the time duration of the measurement. The
default is Days:7, Hours: 0, Minutes: 0. A 7–day measurement interval is also the maximum allowed
interval.
“Sample time” field is the period between two consecutive measurement samples. The choice is among
2, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and name for this file is displayed to the
operator. The file is stored in the ALCATEL/CT–Kv3.0.1 directory.
N.B. The file name must not include the following characters: \ ? : * “ < > |.
The log file contains the sample value and records the measurement up to a maximum dimension ( 7 days
for a 2 s sample time).
Fig. 96. Measurements screen

1AA 00014 0004 (9007) A4 – ALICE 04.10
By clicking on the ”Start“ button the screen “Power Measurement Graphic“ appears (see Fig. 97. on
page 157).
ED 03
3DB 05653 CA AA 156 / 296
296
Fig. 97. Power Measurement Graphic Screen
The Power Measurement Graphic is available only if the CT is connected to NE.
The screen in Fig. 97. on page 157 shows the current Rx measurement and the ODU alarms related to
the local NE.
The top graphic screen area shows the Rx curve, while the bottom area shows the alarms active in the
ODU. The alarms have different colors according to their severity.
The top of the screen offers all the characteristics present in the current measurement:
– FSO port: gives the symbolic name associated to the channel that you are analyzing
– Sample time: indicates the frequency used to send the measurement requests to NE;
– Start time: is the first request time;
– Stop time: is the interval time selected in the previous parameters window, added to the start time;
– Time: is the current response time;
– Log File: is the complete pathname of the file where the received values are stored.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 157 / 296
296
By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 97. on
page 157), a new table appears (Fig. 98. on page 158); this table shows the following relevant values of
the received and transmitted power:

– Rx Local End

• max Rx local value and date when this value was received for the first time.
• min. Rx local value and its current date when this value was received for the first time.
• current Rx local value and its current date.
Fig. 98. Details Dialog screen

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 158 / 296
296
2–6.2.3.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button. The directory of the CT automatically opens
to navigate and get the power measurement file.
N.B. as default the measurement files are stored in the ALCATEL/CT–Kv3.0.1 directory and have
extension .txt.
Fig. 99. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 96. on page 156 to open the file.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 100. Example of “Power Measurement File Reading“
The button in the lower part of the window allow to flow the graph within the measurement interval.
ED 03
3DB 05653 CA AA 159 / 296
296
Select the .txt file and click with the mouse right push–button to open .txt file with a text editor (e.g.
WordPad) and to see the power information in tabular mode (see Fig. 101. on page 160).

Fig. 101. Example of Power Measurement File Reading (with WordPad)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 160 / 296
296
2–6.3 Laser#1 or Laser#2
By selecting the Laser object in the Resource Tree Area the screen in Fig. 102. on page 161 appears.
Fig. 102. FSO laser configuration
– Laser Index: the identification number of the 2 Lasers installed in the FSO ODU.
– Laser Status: the status of the Laser (On/Off). To switch on or off a Laser select Configuration in
the relevant Resource Detail Area.
In the Laser status field 4 options are available:
• On: the selected Laser is switched ON

• Off: the selected Laser is switched OFF
• On All: both Lasers (1 and 2) are switched ON
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Off All: both Lasers (1 and 2) are switched OFF
ED 03
3DB 05653 CA AA 161 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
162 / 296
2–7 EXTERNAL POINTS
This chapter describes the types of functions offered to the user for External Points Management.
There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Fig. 103. on page 163, the tree will be expanded according to the
equipment configuration.
A single left click selection of a tree element causes the activation of the corresponding Tabular
representation displayed in the ”Resource list area”. A click on a row in the Resourse list area opens the
Configuration menu in the Resourse Detail Area. An example of this mechanism is diplayed in the
Fig. 103. on page 163.
2–7.1 Input External Points
An input external point is described by the following parameters (Fig. 103. on page 163):
– Id: identification number

– UserLabel: associates a user–friendly name to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened)
– External State: describes the state (on /off)
– Alarm Profile: describes the associated Alarm Profile
The lower part provides the possible parameters, which can be modified; after a row selection, the user
can modify the User Label, the Polarity and can associate a different Alarm Profile by clicking on the
Selection button.
The operator choices will be sent to NE after selecting the “Apply” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 103. Input External Point View
ED 03
3DB 05653 CA AA 163 / 296
296
2–7.2 Output External Points (in V.1.0.0)
An output external point is described by the following parameters (Fig. 104. on page 164):


– UserLabel: associate a user–friendly name to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened)
– External State: describes the state (on /off)
The lower part provides the possible parameters which can be modified; after a row selection, the user
can modify the User Label, Polarity and External State of the external point selected (On=active; Off=not
active).
The operator choices will be sent to NE by clicking on the “Apply” button.
Fig. 104. Output External Points View

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 164 / 296
296
2–7.3 Output External Points (in V.1.0.1 and V.1.0.2)
Seven output external points are available (Fig. 105. on page 165):
The first four external points (CPO#1, 2, 3, 4) are described by the following parameters:

– UserLabel: a user–friendly name can be associated to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
– External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) are described by the
following parameters:

– UserLabel: a user–friendly name can be associated to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
N.B. These three output external points are automatically activated when the relevant equipment
summarizing alarm is active.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 105. Output External Points View
ED 03
3DB 05653 CA AA 165 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
N.B.
03
296
3DB 05653 CA AA
while is possibile to associate a “Profile alarm” on each input.
It’s not possible to associate an output with an internal alarm,
166 / 296
2–8 SUPERVISION
2–8.1 Access state (allow or inhibit NE Craft access)

The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and the
CT, a Local Access Control (LAC) is available.
If the LAC is ”access denied”, it means that the OS manages the NE and the CT is not allowed to modify
the NE configuration (it can only “read”). In the view, the icon with a key symbol has a circular shape.
If the LAC is “granted”, it means that the CT is allowed to manage the NE. In the view, the icon with a key
symbol has a rectangular shape.
If the LAC is ”requested”, it means that the CT has requested a permission from the OS and is waiting for
a replay.
However, the OS does continue to provide a certain number of services. These services include:
– Alarm reception and processing,
– Performance processing,
– Switching back to the OS access state.
The access state of an NE can be modified from two types of views:
2–8.1.1 Switching from the OS to the Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the Access State
cascading menu as shown in the following figure.
Fig. 106. Configuration of the Craft access state from the Equipment NE view in the OS mode
From the confirmation dialogue box that opens, you can confirm or cancel the ”Craft access” operation
using the Yes or No pushbutton. The request is sent up to the OS which accepts or refuses it.
If the OS doesn’t answer in a predefined time, it is assumed that the NE is in the Craft access state
1AA 00014 0004 (9007) A4 – ALICE 04.10
and can be managed by a Craft Terminal.
ED 03
3DB 05653 CA AA 167 / 296
296
2–8.1.2 Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then from the Access State cascading menu in Fig. 135. on
page 197, select the OS option.

From the confirmation dialogue box that opens, you can confirm or cancel the ”OS access” operation.

The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view indicates whether the NE is
managed by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the
NE. When the communication with the NE is lost, the OS automatically recovers the
communication and forces the state existing before the loss of communication (therefore, Craft
Terminal access can be denied or granted).
2–8.2 Restart NE
The RESTART operation is a software reset and can be executed in normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
Fig. 107. Restart NE call
The following dialogue box opens.
Fig. 108. Restart NE confirmation
Click the OK button to confirm the restart N.E. operation

1AA 00014 0004 (9007) A4 – ALICE 04.10
Click the Cancel button to abort the restart N.E. operation.
ED 03
3DB 05653 CA AA 168 / 296
296
2–8.3 SW key
From the Supervision cascading menu, select the SW key option.

In this screen the type of the key (stored in the flash card installed in the Main IDU unit) is shown.
Fig. 109. SW key screen

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 169 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
170 / 296
2–9 PROTECTION SCHEMES
N.B. This menu is available in V.1.0.1 and V.1.0.2 only for the Radio application.
This domain is present in 1+1 configuration.

– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource List Area: displays tabular informations about the selected resource in tree area.
– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for involved resource.
By clicking on the tree root displayed in Fig. 110. on page 171, the tree will be expanded according to
protection schemes supported.
Fig. 110. Protection Schemes
A single left click selection of an element tree causes the activation of the corresponding Graphical
representation displayed in the “Resource list area”. An exemple of this mechanism is displayed in the
following figure (Fig. 111. on page 172).
Three 1+1 protection schemes have been implemented:

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Mux protection: EPS protection in Tx side

– Radio protection: EPS protection in Rx side
– HST protection: Hot Stand–by protection
ED 03
3DB 05653 CA AA 171 / 296
296
To see the current position of the switches enter the menu Diagnosis –> Summary Block Diagram View
(refer to para. 2–11.4 on page 196).
– The Mux protection corresponds to the Switch Tx in Fig. 137. on page 199 or Fig. 138. on page 200

– The Radio protection corresponds to the Switch Rx in Fig. 137. on page 199 or Fig. 138. on page
200
– The HST protection is implemented in the ODU: one Transmitter is connected to the antenna
(active), the other transmitter is in stand–by. Refer to Fig. 137. on page 199.
2–9.1 Mux Protection Management
The Equipment Protection Management is performed by selecting Mux Protection tree element.
The following windows (Fig. 111. on page 172) allows a complete view of all Ne resource involved in the
EPS protection:
– Schema Parameters
– Channels Parameters
Fig. 111. Mux Protection

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 172 / 296
296
2–9.1.1 Schema Parameters
The window “Schema Parameters” displays the parameters that can be modify.
The Schema parameters are:

– Protection Type: this parameter is defined at creation time and it is read only. The supported type
is: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare).
– Operation type: it defines if automatic restoration from protecting to protected channel is allowed
(revertive mode) or inhibited (not revertive mode).
The operator choice for “Operation Type” will be applied by clicking on “Apply” button.
2–9.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 112. on page 173)
or on the Main #1 element (Fig. 113. on page 174).
Fig. 112. Mux Protection Switch (Spare #0)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 173 / 296
296
Fig. 113. Mux Protection Switch (Main #1)
The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced
and Manual.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),
independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of the switch depends on the commands
generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic
switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does not activate signaling ABN.
Tab. 5. Command priority list

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. to release a previously activated command select None and click on Apply.
ED 03
3DB 05653 CA AA 174 / 296
296
2–9.2 Radio Protection Management
The Radio Protection Management is performed selecting Radio Protection element tree.
The following windows (Fig. 114. on page 175) allows a complete view of all Ne resource involved in a RPS
protection:
Fig. 114. Radio Protection View

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 175 / 296
296
2–9.2.1 Schema Parameter
The Schema Parameters are:

– ”Protection Type” field: defines the protection schema architecture: 1+1;
– ”Operation Type” field: the possible values are revertive (automatic restoration allowed) or
notRevertive (automatic restoration Inhibited).
2–9.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 115. on page 176)
or on the Main #1 element (Fig. 116. on page 177).
Fig. 115. Radio Protection Switch (Spare #0)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 176 / 296
296
Fig. 116. Radio Protection Switch (Main #1)
and Manual.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),
independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 177 / 296
296
2–9.3 HST Transmission Protection Management
The Transmission Protection Management is performed selecting Transmission Protection element tree.

The following windows (Fig. 117. on page 178) allows a complete view of all Ne resource involved in a TPS

protection:
Fig. 117. Transmission Protection View
2–9.3.1 Schema Parameters
The Schema parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported type
are: 1+1 (onePlusOne) ,e.g. a working element is protected by one protecting unit.
– Operation type: it defines if automatic restoration from protecting to protected unit is allowed
(revertive mode) or inhibited (not revertive mode).
1AA 00014 0004 (9007) A4 – ALICE 04.10
The operator choice for “Operation Type” will be applied clicking on “Apply” button.
ED 03
3DB 05653 CA AA 178 / 296
296
2–9.3.2 Commands
To enter the Commands menu click on the Spare #0 element (Fig. 118. on page 179) or on the Main #1
element (Fig. 119. on page 180) in the Tree view.
Fig. 118. Tx Protection Commands (Spare #0)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 179 / 296
296
Fig. 119. Tx Protection Commands (Main #1)
and Manual.
Lockout has higher priority than Forced: the activation connects to the antenna Transmitter 1 (default
transmitter), independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command connects to the
antenna Transmitter 0, independently of the possible active alarms. This command activates signaling
ABN.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 180 / 296
296
2–10 LOOPBACKS
The functions described in this section allow to perform the test operations.
This domain view consists of the following areas:

– Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by
number.
– Resource Filter Area: display the possible filters to apply to loopback search.
– Resource List Area: displays tabular information about the loopback supported by the resource
selected in tree area.
– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for involved resource.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 181 / 296
296
2–10.1 Available Loopbacks
N.B. Tab. 8. shows the loopbacks performed on the local NE, which activation does not cause the
loss of the supervision (UP) of the remote NE and the loopbacks, which activation will cause

the loss of the supervision (DOWN) of the remote NE.

Tab. 8. Loopbacks on the local NE
CH MAIN (1+0) system
TRIBUTARIES UP for nxE1/DS1; DOWN for E3/DS3
IDU–CABLE DOWN
ODU–CABLE DOWN
R.F. DOWN
TRIB. FE UP
TRIB. NE UP
CH SPARE (1+1) system with Spare lock–out
IDU–CABLE UP
ODU–CABLE UP
R.F. UP
TRIB. FE UP
TRIB. NE UP
CH MAIN (1+1) system with Spare lock–out
IDU–CABLE DOWN
ODU–CABLE DOWN
R.F. DOWN
TRIB. FE UP
TRIB. NE UP
CH SPARE (1+1) system with Main forced
IDU–CABLE DOWN
ODU–CABLE DOWN
R.F. DOWN
TRIB. FE UP
TRIB. NE UP
CH MAIN (1+1) system with Main forced
IDU–CABLE UP
ODU–CABLE UP
R.F. UP
1AA 00014 0004 (9007) A4 – ALICE 04.10
TRIB. FE UP
TRIB. NE UP
ED 03
3DB 05653 CA AA 182 / 296
296
2–10.1.1 1+0 FSO Loopbacks
CT
IDU FSO ODU FSO ODU IDU
1 2 4 5 6 7 3
TRIB MUX/ MODEM OPT. OPT. MODEM MUX/ TRIB

DEMUX TxRx TxRx DEMUX
Fig. 120. 1+0 FSO available loopbacks
Tab. 9. 1+0 FSO loopbacks

CT selection in
Loopback Ref. to Loopback
No. the Resourse Location Note
name Fig. type
Tree Area
E1/DS1 Fig. 122. Input loopback at
1 Tributaries Near End External line
Port#xx Fig. 123. tributary level
Loopback toward the
remote station at
E1/DS1 Fig. 121. tributary level. This
2 Channel 1 Near End External line
Port#xx Fig. 123. loopback can be
activated in the local
station only.
Loopback in the
E1/DS1
3 Channel 1 Fig. 121. Far End Internal remote station at
Port#xx
tributary level
Loopback at the IDU
Fig. 121.
4 IDU cable Channel 1 Near End Internal output at aggregate
Fig. 123.
level
Loopback at the ODU
ODU FSO Fig. 121.
5 Channel 1 Near End Internal input at aggregate
cable Fig. 123.
level
Loopback between
ODU FSO Fig. 121. the Modulator output
6 Channel 1 Near End Internal IF
IF #1 Fig. 123. and Demodulator
input
ODU FSO Fig. 121. Optical loopback at
7 Channel 1 Near End Internal
optical Fig. 123. the ODU level
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 183 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 121. Channel 1 Loopback View
Fig. 122. Tributaries Loopback View
296
3DB 05653 CA AA
184 / 296
In the Resource List Area are listed all the loopbacks which can be performed.
In this area the following information is given:
– Channel: the number of the channel (channel 1 only)

– Type Interface: the type of interface in which a loopback can be performed.
– Location: the station in which the loopback is performed (Near End/Far End)
– Type: the type of the loopback (Internal/Internal IF/External Line)
– Modality: the type of the loopback (Loop and Continue only)
– Activation: the activation status of a loopback (Active/Not Active)
In Fig. 123. on page 185 is given the association of all the possible loopbacks and their positions in the
block diagram of the equipment provided by the Summary Block Diagram View option, available in the
Diagnosis menu.
4 IDU 6 ODU FSO

CABLE IF#1
1 Tributaries
5 ODU FSO 7
ODU FSO
(External Line) CABLE Optical
2 Channel
(External Line)
Fig. 123. 1+0 FSO Loopback types

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 185 / 296
296
2–10.1.2 1+0 Radio Loopbacks

CT

IDU ODU ODU IDU
1 2 4 5 6 3
TRIB MUX/ MODEM RF RF MODEM MUX/ TRIB

DEMUX DEMUX
Fig. 124. 1+0 Radio available loopbacks
Tab. 10. 1+0 Radio loopbacks
CT selection in
name Fig. type
Tree Area

Loopback toward the

remote station at
2 Channel 1 Near End External line
station only.
Loopback in the
E1/DS1
3 Channel 1 Fig. 125. Far End Internal remote station at
Port#xx
tributary level
Loopback at the IDU

Fig. 125.
4 IDU cable Channel 1 Near End Internal output at aggregate
Fig. 127.
level
Loopback at the ODU

Fig. 125.
5 ODU cable Channel 1 Near End Internal input at aggregate
Fig. 127.
level
Fig. 125. RF local loopback

6 Radio port Channel 1 Near End Internal
Fig. 127. (Note 1)
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 186 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
187 / 296

Diagnosis menu.
4 IDU
CABLE
1 Tributaries 5 ODU 6 Radio

(External Line) CABLE port
(RF loop)
2 Channel
(External Line)
Fig. 127. 1+0 Radio Loopback types

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 188 / 296
296
2–10.1.3 1+1 Radio Loopbacks
CT
IDU ODU ODU IDU
1 2 4 5 6 3
TRIB MUX/ MODEM RF RF MODEM MUX/ TRIB

DEMUX DEMUX
Fig. 128. 1+1 Radio available loopbacks
Tab. 11. 1+1 Radio loopbacks
CT selection in
name Fig. type
Tree Area

Loopback toward the

remote station at
2 Channel 0 or 1 Near End External line
station only.
Loopback in the
E1/DS1 Fig. 129.
3 Channel 0 or1 Far End Internal remote station at
Port#xx Fig. 131.
tributary level
Loopback at the IDU

Fig. 129.
4 IDU cable Channel 0 or 1 Near End Internal output at aggregate
Fig. 131.
level
Loopback at the ODU

Fig. 129.
5 ODU cable Channel 0 or 1 Near End Internal input at aggregate
Fig. 131.
level
Fig. 129. RF local loopback

6 Radio port Channel 0 or 1 Near End Internal
Fig. 131. (Note 1)
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 189 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
190 / 296

Diagnosis menu.
4 IDU 5 ODU 6 Radio port

CABLE CABLE (RF loop)
1 Tributaries
(External Line)
2 Channel
(External Line)
Fig. 131. 1+1 Radio Loopback types

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 191 / 296
296
2–10.2 How to activate a loopback
N.B. For the loopbacks under Ch. 0 and Ch.1 option must force/lockout all switches to related
Channel; for the loopbacks Tributaries > DSx port#y must only force the radio switch Channel

0 or lockout to Channel 1 independently.

To activate a loopback:
[1] Select the loopback to be activated inside of the of the loopback screen in the USM as shown in
[2] Once the loopback is selected click ACTIVE in the configuration menu and APPLY.
[3] The Loopback is now ACTIVE.
Fig. 132. Loopback activation
WARNING:
When the Loopback commands start the Craft Terminal is not “frozen”. Before to set another command
is recommended to wait 120 to 160 seconds minimun.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 192 / 296
296
2–10.3 How to remove a loopback
To deactivate loopbacks use the folllowing steps:

[1] Select the loopback to be deactivated inside of the loopback screen in the Fig. 133. on page 193.
[2] Once the loopback is selected clik NOT ACTIVE in the configuration menu and APPLY.
[3] The loopback is now deactivated.
N.B. If a force or lockout command was used during the activation, ensure that the command is
removed after the test.
Fig. 133. Loopback removing
WARNING:
When the Loopback commands start the Craft Terminal is not “frozen”. Before to set another command
is recommended to wait 120 to 160 seconds minimun.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 193 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
194 / 296
2–11 DIAGNOSIS
In the Diagnosis menu four options are available as shown in Fig. 134.
Fig. 134. Diagnosis menu
2–11.1 Log Browsing
In the Diagnosis pull–down menu, select the Log Browsing option.
The proposed options:
– Select the Alarm Log option to access the Alarm Log file.
The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.
Refer to the “ELB Operator’s Handbook”.
– Select the Event Log option to access the Event Log file.
The Event Log windows opens, permitting to analyze all the events stored in the NE.
Refer to the “ELB Operator’s Handbook”.
– Software Trace Log option is reserved to the Alcatel technicians.
2–11.2 Remote Inventory
This screen is a read–only screen, which shows all the information on the equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 195 / 296
296
2–11.3 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions (i.e.
the manual operations) currently active in the NE.

The abnormal conditions can be:
– Switch commands Forced or Lockout

– Loopback
– Tx power manual operation
– Tx muting (manual or automatic)
– ODU service kit connected
– FSO laser muting
2–11.4 Summary Block Diagram View
The “Summary Block Diagram View” of the Diagnosis menu displays a global logical view (strictly
related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in
the system (ODU+IDU).
This window also shows a logical view of the signal flowing through the functional block and switches.
Line (and arrow) trace changes in compliance with the current switch status. By clicking on the objects
of the drawing shown in the figure the operator can navigate to the specific view to perform maintenance
operation (for example specific alarm details, equipment details, manual switches, loopback (L),
performance monitoring (P).
The Summary Block Diagram View depends on the configuration:
– 1+0 FSO (see Fig. 135. on page 197)

– 1+0 Radio (see Fig. 136. on page 198)
– 1+1 HST Radio (see Fig. 137. on page 199)
– 1+1 FD Radio (see Fig. 138. on page 200)
In detail, it is possible to:
– navigate from Alarm indicator to related “Alarm Synthesis”;

– navigate from External Point indicator to “External Point” view;
– navigate from Switch indicator to related “Protection Scheme” view;
– navigate from Loopback indicator to specific “Loopback” view; for example, by clicking on (L)
indicator of main board (Ch#1) the operator can navigate to loopback view for PDH tributaries;
– navigate from Performance indicator to specific “Performance” view; for example, by clicking on
(P) indicator (line side) the operator can navigate to “Current Data” view;
– navigate from ODU box to the ”radio view” with automatic selection of the related channel.
To refresh the screen press the Refresh button.
N.B.
• Loopback indicator: yellow letter L means active loop.

• Performance indicator: yellow letter P means active performance.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. In the 1+1 configuration the current position of the switches is also shown.
ED 03
3DB 05653 CA AA 196 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 135. Summary Block Diagram View: 1+0 FSO
296
3DB 05653 CA AA
197 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 136. Summary Block Diagram View: 1+0 Radio
296
3DB 05653 CA AA
198 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
Fig. 137. Summary Block Diagram View: 1+1 HST Radio
3DB 05653 CA AA
199 / 296
Fig. 138. Summary Block Diagram View: 1+1 FD Radio
By pressing the Refresh button the refresh of the screen takes place (active loopback and performance
and position of the switch).
2–11.5 Current Configuration View
This screen is a read–only screen, which shows the current configuration of the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 200 / 296
296
2–12 PERFORMANCE MONITORING
This chapter describes the functions to provide Performance Monitoring management. It explains the
procedures that the operator must perform in order to activate a PM process.
2–12.1 General information on the performance monitoring process
The performance monitoring (PM) gives indication on the quality of the service.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, T1, …) can be derived from the quality of the
aggregate signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
Considering one section (see below), one current register is for 15 min report and one for 24 h report; 96
history data can be stored for 15 min report and 8 history data for 24 h report.
N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errors
have been occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
The radio section monitored is:
– Radio Hop Section: the section between two radio stations inside the protection section
PROPR. FEC MODEM MODEM FEC PROPR.

FRAMING ENCODE RF RF DECODE FRAMING
Radio Hop (before the switch)
Fig. 139. Radio section
The counters supported are the following:
– Errored Seconds
– Severly Errored Seconds
– Background Block Error
– Unavailable Seconds
The primitives used for the hop section quality monitoring is the Reed–Solomon (RS) decoder (block size:
2040 bits). The following table provides, for each frame structure, the main features useful to define a SES.
Tab. 12. SES Thresholds

E3 16E1 8E1 4E1 2E1 DS3 16DS1 8DS1 4DS1
Gross bit rate
39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140
[MHz]
RS Blocks
19200 19200 9600 4800 2400 28000 14000 7000 3500
number/sec.
SES Threshold
5760 5760 2880 1440 720 8400 4200 2100 1050
(Note 1)
1AA 00014 0004 (9007) A4 – ALICE 04.10
(Note 1) Note that according to ITU–T G.826 a second is declared Severely Errored Second if it is a
second period with more than 30 % of errored blocks or at least one defect.
ED 03
3DB 05653 CA AA 201 / 296
296
The flow chart shown below illustrates the recognition of anomalies, defects, errored blocks, ES and SES
according to ITU–T G.826 (12/2002).

Monitored
second
Yes
Defects?
No
No
Anomalies?
Yes
Yes SES
%EB ≥ 30?
(and therefore an ES)
ES
(but not a SES) No
Path in Path in N
No
available available
State? State?
Yes Yes
cES = cES + 1 cES = cES + 1
cBBE = cBBE + EB(s) cSES = cSES + 1
T1313790–98
End
Fig. 140. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 202 / 296
296
2–12.2 Performance menu
The performance view allows the user to activate and monitor the PM process on the selected object.
– Resource Tree Area: displays the threshold for measurement and the object monitoring sorted by
channel number.
– Resource List Area: displays the PM management for the selected resource in the tree area.
Fig. 141. Performance View
The performance reports can be of 2 different types:
– 15 minutes
– 24 hours
The following description explains the functions to provide the PM process with a granularity period of 15
min. The same functions are provided for 24h PM process.
The PM are only of HOP type. The current report can be seen (and configured) and the history PM log
can be seen.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 203 / 296
296
With reference to Fig. 141. on page 203 to see (and configure) the current report:
[1] click on the channel (0 or 1) (in 1+0 configuration channel 1 only)
[2] click on HOP

[3] click on the desired granularity (15 m or 24 h)
[4] click on CD (Current Data).
With reference to Fig. 141. on page 203 to see an history log:
[1] click on the channel (0 or 1) (in 1+0 configuration channel 1 only)
[2] click on HOP
[3] click on the desired granularity (15 m or 24 h)
[4] click on the desired HD (History Data).
To each PM can be associated a threshold table. To associate a threshold table click on HOP in the
Resourse Tree Area. The screen in Fig. 142. will appear.
Fig. 142. Threshold table association screen
In this screen the threshold (1 or 2) and an Alarm Profile can be associated to the report.
1AA 00014 0004 (9007) A4 – ALICE 04.10
To associate an Alarm Profile click on the selection box and selet one of the Alarm Profiles available.
ED 03
3DB 05653 CA AA 204 / 296
296
2–12.3 CD (Current Data)
The window displayed in Fig. 143. on page 205 allows to start and to read the 15min PM report and 24h
PM report.
Fig. 143. Current Data View

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 205 / 296
296
2–12.3.1 CD parameters
The fields displayed in the upper part of Fig. 143. on page 205 allow the operator to check and manage
the parameter of the current data collection.

– “Suspect interval” shows whether the current data are suspect or not.
– “Elapsed Time” field (read–only) displays the elapsed time in the current interval of monitoring.
– “End Period”: display time of the PM in the graphical description and in the tabular description in
the upper part of the screen. By pressing the Refresh button this time changes.
– “Max Interval supp.”: max. number of intervals (reports) which can be suppressed in the History
because they don’t have errors.
– “Num. Interval supp.”: number of intervals (reports) suppressed in the History because they don’t
have errors.
2–12.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 143. on page 205 (Counters Area) allow the
management of performance events.
In the left part of Counters Area, there is a graphical description of the event counter value: BBE (Errored
block), ES (Errored second), SES (Severely Errored Second), UAS (Unavailable second).
N.B. these values refer to the last refresh performed by pressing the Refresh button.
In the right part of Fig. 143. on page 205, there are button choice to perform action on the current data
collection:
– “Reset” button resets the data collection and related counters.
– “Start” button starts the counters for the data collection, when the CD has been stopped.
– ”Refresh” button makes a refresh of the counters.
– “Stop” button stops the counters for the data collection, when the CD has been started.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 206 / 296
296
2–12.4 HD (History Data)
The PM process monitors the parameters during a specified interval (i.e. 15min) and stores their values
in history data. A History Data collection is created automatically at the end of each time interval of Current
Data and deleted when the relative CD is deleted.

2–12.4.1 HD Parameters
The table displayed on the following window (Fig. 144. on page 207) collects the history data for a related
PM report.
Fig. 144. History Data
The table columns hold the value of following parameters:
– End Period: End period of the relevant report
– Elapsed time: elapsed time in the related interval
– Suspect interval: this field describes whether the History Data is suspect or not.
– Counters: the last columns hold the counters value (BBE, ES, SES, UAS).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 207 / 296
296
2–12.5 Threshold Data
This section describes how to see or change the threshold tables assigned to PM counters.

To view the available threshold for PM process, the operator must select the “Thresholds Tables” node

tree in the Resource Tree Area of the Performance View.
By clicking on the threshold table on the view area the parameters of the 2 tables will appears (Fig. 145. on
page 208).
Fig. 145. Thresholds Tables
By clicking on threshold 1 or 2 in the Resourse List Area the screen in Fig. 146. on page 209 will appear.
In the upper part of Fig. 146. on page 209, the “Name” field displays the name assigned to the threshold
table.
In the lower part of Fig. 146. on page 209, low and high threshold for each counter is shown. To change
them, the operator must edit the new values in the table fields and click on the “Apply” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 208 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
Fig. 146. Threshold table configuration
296
3DB 05653 CA AA
209 / 296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
210 / 296
2–13 SW DOWNLOAD
2–13.1 Server Access Configuration

This menu allows to configure the FTP server to be used to download the SWP to the NE.
N.B. The complete procedure to download the SWP to the NE is shown in para. 1–2.3 on page 60.
Fig. 147. Server access configuration screen
User Id and Password are the login information to access the FTP server.
In the Address field write the IP address of the FTP server.
In the Port field write the port to be used and in the Root Directory field write the directory into which the
software has been downloaded.
By clicking on the Use System Default button a screen will appear showing the default configuration.
The CT is the default FTP server with the following parameters:
– User Id: ftp

– Password: ftp
– Address: IP address of the F interface or IP address of the Ethernet interface, if present.
– Port: 15,000
N.B. the System Default can be changed by writing different values in the fields and then by clicking
1AA 00014 0004 (9007) A4 – ALICE 04.10
on button OK.
ED 03
3DB 05653 CA AA 211 / 296
296
2–13.2 Init SW Download
Through this menu software is downloaded to the NE in order to upgrade the NE software version.

To start download select the desired software version and click on the Init download button.

N.B. This screen displays the software packages previously stored through the menu Supervision
–> Files Administration –> Software Administration available in the NES menu.
The Forced check box can be used to force download (i.e. the complete description file is downloaded
to the NE).
If the Forced download is not selected, the system shall first proceed to compare the software to be
downloaded with the software present in the NE. Then only the differences are downloaded.
Fig. 148. Init Software Download screen
When the SW download starts a screen, showing the in progress operation of the download, appears.
Download is aborted when the Abort button is pressed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 212 / 296
296
2–13.3 SW Status
This menu allows to display the information of the software installed in the NE.
The following information is displayed:

– Name: software name
– Version: software version
– Operational state: enabled or disabled
– Current status: committed or standby
By clicking on the Software Units Status button the screen of Fig. 149. on page 213 opens, giving
additional information on the software package.
Fig. 149. SW Status screen

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 213 / 296
296
The following information is displayed on the screen:
– EC: software on the Equipment Controller
– OC_R: software on the ODU Controller (Radio)

– OC_F: software on the ODU Controller (FSO)
Fig. 150. SW Unit Status screen
The Flash card, which stores the NE software, contains 2 banks.
The 2 banks can store 2 different software versions. One bank will be committed (active) and the other
bank will be standby.
N.B. The second bank will appear when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is enabled
(this means that download took place without errors) select Activation or Forced Activation in the
Software Management Action field and click on the Apply Action button.
By selecting Forced Activation the bank to be activated is forced to restart.
By selecting Activation the bank to be activated restarts only if the content of the two banks differ.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 214 / 296
296
SECTION 3: AWY/FSO MAINTENANCE

Chapter 3–1 – Maintenance introduction 216
Chapter 3–2 – Troubleshooting 217
Referenced handbook P/Ns are given in para.E.2 on page 279 of this handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 215 / 296
296
3–1 MAINTENANCE INTRODUCTION
This section is the 9400AWY/FSO Maintenance Manual; it describes mainly the NE troubleshooting based
on the use of the Craft Terminal.

It applies to 9400AWY SWP Rel.1.0.
The document that should be read before starting this document is:
9400AWY Technical Handbooks, section MAINTENANCE

or:
9400FSO Technical Handbooks, section MAINTENANCE
– 9400AWY Rel.1.0 Technical Handbook and 9400FSO R.1.0 Technical Handbook R.1.0.
N.B. In particular, knowing the contents of section “MAINTENANCE” of Technical Handbook is

a must.
– 1320CT Basic Operator’s Handbook V.3.0.1
The maintenance procedures consist of the following steps:
– PC Maintenance. See para.3–1.1 herebelow.
– Problems with the Craft Terminal PC (shut–down and restart ). See para.3–1.2 herebelow.
– Corrective Maintenance (Troubleshooting). See Chapter 3–2 on page 217.
3–1.1 Maintenance of the PC
With regard to the PC maintenance, refer to the constructor’s documentation.
3–1.2 Problems with THE Craft Terminal
This procedure describes how to shutdown and restart the PC should the Craft Terminal SoftWare Product
not be working properly or not responding to the operator’s commands.
In order to shutdown the PC execute the command :
Start > Shutdown
A window (Windows NT Security user dialog) is displayed. It permits to shutdown the computer or restart
it.
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
N.B. In the case this procedure is unsuccesful, carry out the checks indicated in:
9400AWY or 9400FSO Technical Handbooks

section MAINTENANCE,
chapter SECOND LEVEL MAINTENANCE
1AA 00014 0004 (9007) A4 – ALICE 04.10
paragraph TROUBLESHOOTING–PROBLEMS WITH THE CRAFT TERMINAL
ED 03
3DB 05653 CA AA 216 / 296
296
3–2 TROUBLESHOOTING
3–2.1 Purpose of this procedure
Troubleshooting involves detection, location and correction of the failures occurred in the equipment and
replacement of the defective parts.

3–2.2 Corrective Maintenance general flow–chart

As depicted in Fig. 151. herebelow, troubleshooting via Craft Terminal is just a step inside the Corrective
Maintenance process.
START
Alarm acknowledgment and attending (para...)
Trouble–Shooting starting with visual indications (para......)
Other measures
Trouble–Shooting via Craft Terminal.

Identification of a unit to be replaced.
Unit replacement in the IDU (para...). ODU replacement (para...)
System check via Craft Terminal
Try again with N

Fault repaired ?
another unit
Y
If possible, restore replaced unit in the system and perform
system check via Craft Terminal, to verify that is really faulty
Possible intermittent N
Fixed fault ?
failure
Y
Restore spare part in the system and perform
system check via Craft Terminal
Send back faulty unit to Repair Centre together

with Repair Form compiled (para......)
END
Fig. 151. Corrective Maintenance general flow–chart
For detailed information regarding the whole Corrective Maintenance procedure, please refer to:
1AA 00014 0004 (9007) A4 – ALICE 04.10
9400AWY or 9400FSO Technical Handbooks, section MAINTENANCE

chapter SECOND LEVEL MAINTENANCE, paragraph CORRECTIVE MAINTENANCE
ED 03
3DB 05653 CA AA 217 / 296
296
3–2.3 Troubleshooting organization
The troubleshooting procedure is carried out with the help of some tables, reported hereinafter. Anyway
this method does not deal with the following issues (which are to be dealt with otherwise):

– faulty electronic alarm indication, processing and detection circuits
– faulty wiring (back–panel, connectors, etc.)
The following interfaces are present on the equipment for troubleshooting purposes:
• Ethernet interface for the Telecommunication Management Network ( TMN )
• F interface for the Craft Terminal (Local or Remote)
• LEDs located on the NE’s units.
Usually, maintenance is firstly done via software (TMN or Remote Craft Terminal) to locate the faulty
equipment and the faulty unit or the faulty path and then on site to physically correct the trouble.
Maintenance can be done:
• from a TMN network management center
• from a Remote Craft Terminal (RCT) management center
• on site.
TMN network management center: by means of the TMN, the maintenance technician can see the
alarms generated by each equipment of the managed network (see the relevant TMN handbooks).
Remote craft terminal: the operator, connected to a local NE, can remotely manage and troubleshoot
a network composed of max 128 NEs, including itself. This handbook applies.
On site : the operator is on site in case :
1) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT).
2) the equipment is not reachable by the remote manager (TMN or RCT) and therefore is isolated.
3) link problems are present.
4) the trouble has been located and a physical replacement is necessary.
In cases 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 218 / 296
296
The NE is provided with LEDs which indicate:
Centralized Equipment Alarms:
All alarms detected on the units are collected by the MAIN unit, which delivers centralized indications (by
means of LEDs on the front coverplate). Specifically:
• Red LED: detection of a MAJOR (URGENT) alarm.
• Red LED: detection of a MINOR (NOT URGENT) alarm.
• Yellow LED: alarm condition ATTENDED.
• Red LED: detection of a LDI (problem in the local equipment).
• Red LED: detection of an RDI (problem in the remote equipment).
In the case of a MAJOR or MINOR alarm, after locating the alarmed unit, the alarm condition can be
”attended” by pressing the alarm storing push button on the front panel of the MAIN unit.
This condition causes on the front coverplate:
• yellow LED ATTENDED to light up
• red LEDs MINOR and MAJOR to turn off (free to accept other alarms)
If both LEDs are on, the Attend command should be given twice : one to attend the MINOR
alarm and one to attend the MAJOR alarm.
The troubleshooting operation is done by means of the Craft Terminal, and of the optical indicators (LEDs)
present on the NE.
The Craft Terminal is connected to the relative connector on the front coverplate (F interface) of the MAIN
unit.
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault
location and subsequent removal as indicated in para. 3–2.4 on page 220.
To correctly execute the troubleshooting operations the technician must know the equipment
configuration (see Equipment applications on the Craft Terminal).
The following tables should be also consulted when the unit LEDs flash; as a matter of fact, the flashing
condition might be due to external alarm causes usually, related to line problems.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 219 / 296
296
3–2.4 Troubleshooting by means of the Craft Terminal
Troubleshooting proceeds by checking the detailed information on the NE alarm by using the Craft
Terminal.

The information on the NE alarm will be mainly obtained by means of the Craft Terminal through the Alarm
tab panel data.
The troubleshooting procedure is the following.
a) Look at the active alarms on the Control Panel always present on the window (which summarizes
all the NE alarms). Tab. 13. on page 221 describes the meanings of these alarms/statuses and its
respective maintenance actions.
b) In case of alarm, access the Alarm tab panel for troubleshooting.

Para 3–2.4.2 on page 222 explains how to see the alarms.
MAJOR alarm indicates a severe alarm that could affect the current traffic (interrupt or
degrade). Hence, a prompt intervention is necessary to restore the regular operating
condition of the equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 220 / 296
296
3–2.4.1 Alarm synthesis indication
The following troubleshooting table pertains to the alarm and status synthesis given in all the screens.
Tab. 13. Alarm Synthesis indication

Mnemonic Alarm / Status Description Maintenance
Synthesis of alarms that needs immediate

CRI Critical alarm
troubleshooting (typical: NE isolation). NB1.
Synthesis of alarms that needs immediate

MAJ Major (Urgent) alarm
troublshooting. NB1.
Synthesis of alarms for which a deferred intervent
MIN Minor (Not urgent) alarm
can be decided. NB1.
Synthesis of alarms due to failure of other NE in the

WNG Warning alarm
network. NB1.
Synthesis of alarms not associated with the previous

IND Indeterminate alarm
severities. Not operative.
External Point Check the relevant station alarm associated with the
EXTP
(Housekeeping alarm) input housekeeping indication.
EQP Equipment alarm Synthesis of alarms of the Equipment domain.
TRNS Transmission alarm Synthesis of alarms of the Transmission domain.
GREEN LED: NE is under supervision.

SUP Supervision state BROWN LED: NE is not under supervision.
Used in the OS.
GREEN LED: Indicates that the Craft Terminal has

the OS permission to manage the NE (granted).
Local Access state
CYAN LED: Indicates that the Craft Terminal has not
the OS permission to manage the NE (denied).
GREEN LED: Identifies the “ Enable “ operational

state of the connection between NE and Craft Terminal
( SDH service link up ).
COM NE reachable/unreachable
RED LED: Identified the “ Disable ” operational state
of the connection between NE and Craft Terminal
( service link down ).
GREEN LED: Normal operating condition.

AC Abnormal Condition CYAN LED: Detection of an ABNORMAL operative
condition. Type: switch forcing.
Alignment status of the SH MIB respect to the

ALI Alignment
equipment MIB.
NB1: The Alarm Profile can modify the assignment of each alarm root to the various synthesis.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 221 / 296
296
3–2.4.2 Details on alarms / statuses
The troubleshooting proceed by checking the detailed information on the NE alarm by using the Craft
Terminal.

To display the active alarms (refer to Fig. 152. on page 222):
It is also possible to analyze the detailed alarms present on each TP of the Port views of the NE.
[1] Select the Equipment tab panel.
[2] Select one node (or sub–node) in the Resourse Tree Area to check if some alarms are active.
[3] Select the Alarm tab panel in the Resourse Detail Area.
[4] If the node has sub–nodes put a tick in the Include alarms from sub–nodes field to display the
alarms active also in the sub–nodes.
[1]
[2]
[3]
[4]
Fig. 152. Active alarm screem
Detailed information of some alarm are supplied.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 222 / 296
296
The following table summarizes the information obtained in the Alarm view, starting from the left column.
Tab. 14. Alarm information, general description

TITLE DESCRIPTION
Severity severity associated to the alarm and assigned in the Alarm Profile
Event time time of the generation of the alarm
Entity entity involved in the alarm
Probable Cause probable cause of the alarm
Managed Object Class class of the alarm
The information supplied helps the operator during the troubleshooting operations.
Tab. 15. on page 225 supplies general information on the alarm meanings and on the respective
maintenance actions to be done bases on the information given in the applications.
The maintenance action must take account of the board where the alarm is detected.
The Housekeeping alarms are referred to the input external point relevant to the Housekeeping signals.
They are available to the customer by connecting them to a dedicated subrack connector.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 223 / 296
296
3–2.5 Description of alarms and of probable causes
The information provided helps the operator during troubleshooting operations.

N.B. UNIT REPLACEMENT

After having identified a unit to be replaced, in order to carry out the replacement correctly,
please refer to:
9400AWY or 9400FSO Technical Handbooks,

section MAINTENANCE
chapter SECOND LEVEL MAINTENANCE,
paragraph UNIT REPLACEMENT PROCEDURES
WARNING:
Before to disconnect the cable IDU–ODU of N.E., the corresponding IDU unit must be always
turn–off.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 224 / 296
296
Tab. 15. General issues of the alarm meanings and their respective maintenance actions
ALARM MEANING MAINTENANCE ACTION

AIS detection on the tributary in Tx Check the 2 Mbit connected

AIS
side or Rx side equipment
ATPC loop problem Problem on the ATPC loop Communication problem
Battery fail Problem on the Station Battery Check the Station Battery
Excessive errors. Check the link

High BER Excessive BER
(propagation problem)
Demodulator failure affecting the

Dem fail Replace the ODU
demodulated signal
Loss of the incoming signal at the Check the link (propagation

Dem LOS
demodulator input problem)
Replace the ODU; if the alarm is still

Cable LOS Problem on the cable or on the ODU
active replace the cable.
Frequency setting incompatible with Change the frequency or change the

Incompatible Frequency
the ODU P/N ODU
Incompatible PTX Output power out of the limits Replace the ODU
Press the Reset pushbutton on the

Internal Communication
ODU not responding MAIN unit. If the alarm is still active,
Problem
replace the ODU
Check the LAN connection or

LAN failure LAN problem
replace the MAIN unit
Check the correct connection of the

cable between the IDU and the
Link Identifier Mismatch Mismatch on the link identifier relevant ODU. If the connection is
correct, check the link (propagation
problem)
LOF at the Tx tributary input or at Rx

tributary output (with framed Check the E1/DS1 connected
Loss Of Frame (E1/DS1)
tributary) or LOF of the Rx equipment or the line
aggregate signal
Loss Of Frame (Aggregate

LOF of the Rx aggregate signal Check the link (errors)
signal)
Loss Of Signal LOS at the Tx tributary input Check the line
Check the link (propagation

Low BER Low BER at the Rx side
problem)
Internal modulator failure affecting

Mod fail Replace the ODU
1AA 00014 0004 (9007) A4 – ALICE 04.10
the modulated signal
ED 03
3DB 05653 CA AA 225 / 296
296
Tab. 15. General issues of the alarm meanings and their respective maintenance actions
ALARM MEANING MAINTENANCE ACTION

Investigate by using the loopback

Mod LOS No signal at the modulator input
facilities with the CT.
Remote Defect Indication Alarm active in the remote station Check the remote station
Replaceable Unit Problem Problem on a replaceable unit Replace the unit
Replaceable Unit Type Mismatch between the installed unit Change the unit configuration or
Mismatch and the sw configured unit change the unit
Replaceable Unit Type Missing No unit in a configured slot Install the unit

Rx Fail (Radio alarm) No RF received signal
problem)

Rx LOS (FSO alarm) No Optical received signal
problem)
Performance threshold has been

Threshold Cross Errors on the link
crossed
Transmitter degraded (FSO Laser degraded (output power 3 dB

Minor alarm
alarm) below the nominal power)
Replace the ODU if the alarm is

Transmitter Failure (FSO
Transmitter failure present at the same time on LASER
alarm)
1 and LASER
Tx Fail (Radio alarm) Transmitter failure Replace the ODU
Unconfigured Equipment
Unit present in an unconfigured slot Configure the unit
Present
Mismatch on the software version

Version Mismatch between CT software and Download the software version
equipment software
Housekeeping Active input housekeeping Check the housekeeping

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 226 / 296
296
SECTION 4: SWP DESCRIPTION AND VERSIONS
This section gives information on the Software Packages this handbook refers to, and that are both
independent and independent on the specific SWP Versions.
INFORMATION INDEPENDENT ON THE SPECIFIC SWP VERSIONS
Chapter 4–1 – SWP REG.9400AWY R.1.0 description

This chapter gives information on the Software Packages this handbook refers to,
229
and that are independent on the specific SWP Version: commercial information
(SWP and Software Licences P/Ns).
INFORMATION ON THE SPECIFIC SWP VERSIONS

These chapters give operative information regarding the Software Package Version
1.0.x, starting from version V1.0.0: requirements (PC and equipment Firmware), SW
Package Identification, SW Package Components, ECT SW Sub–Component, NE
MIB Compatibility, new features, restrictions and known problems.
Chapter 4–2 – SWP REG.9400AWY R.1.0 V.1.0.0 specific information

231
N.B. Version 1.0.0 manages the Radio application only (1+0 configuration).
Chapter 4–3 – SWP REG.9400AWY R.1.0 V.1.0.1 specific information

N.B. Version 1.0.1 manages the Radio application (1+0 and 1+1 235
configurations) and the FSO application.
Chapter 4–4 – SWP REG.9400AWY R.1.0 V.1.0.2 specific information 239
The symbol points out references to other handbooks.
Referenced handbook P/Ns are given in Appendix E on page 273.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 227 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
228 / 296
4–1 SWP 9400AWY R.1.0 DESCRIPTION
This chapter gives commercial information regarding the Software Packages this handbook refers to, i.e.
the SWP and Software Licences P/Ns.
4–1.1 General
The software products are distributed by Alcatel in a CD–ROM.
In this CD–ROM are contained:
• Software packages for NE management by means of the craft terminal
• Software package of the NE, to be installed in the NE or update the NE (by means of download
function)
The software package used for management allows the dialogue between craft terminal and NE, to
realize all the functions of the NE and EML–ULS ).
The software package used for updating the NE must be installed on the PC and then downloaded on
the NE, thus following product evolution.
Alcatel typically offers several software licences on the software product.
They are referred both to the Network Element software features and to the Craft Terminal software
features.
4–1.2 Software product list and part numbers
Every Software Product is identified by a denomination and a part number and is distributed by a CD–ROM
with the same identifiers, listed on the following table:
Tab. 16. Software products part numbers
Factory
Name ANV Part Number N.B.
Part Number
SWP 9400 AWY R.1.0 CD–ROM 3DB 04798 AAAA 415.201.017 Y 1
N.B. 1 Software Package associated to LCT or RCT SW Licence ( For AWY/FSO ULS NEs).
See para.4–1.3 on page 230 for additional information.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 229 / 296
296
4–1.3 Software licence list and part numbers
Every Software licence is identified by a denomination and a part number, listed on the following table.

Tab. 17. Software licence part numbers
Factory
Name ANV Part Number N.B.
Part Number
SWL–ULS R1.0 FEE 3DB 05638 AAAA 700.500.050 P 1, 3
SWL–LCT 9400 AWY R1.0 FEE 3DB 04811 AAAA 700.500.028 D

2 3
2,
SWL–RCT 9400 AWY R1.0 FEE 3DB 04812 AAAA 700.500.029 E
N.B. 1 Licence for Network Element software features (one per Transceiver):
2 Licence alternative for Craft Terminal software features:

• SWL–LCT: local Craft Terminal functionality
• SWL–RCT: remote Craft Terminal functionality.
3 Software licence valid for AWY and FSO application.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 230 / 296
296
4–2 SWP REG.9400AWY R.1.0 V1.0.0 SPECIFIC INFORMATION
This chapter gives operative information regarding the Software Package Version 1.0.0: requirements (PC
and equipment Firmware), SW Package Identification, SW Package Components, ECT SW
Sub–Component, NE MIB Compatibility, new features, restrictions and known problems.

For versions higher than V1.0.0 please refer to next chapters of this section.
Please refer to para.E.2.5.2 on page 286 for the meaning of SWP Release, Version and Patch Level.
N.B. With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 274.
4–2.1 ECT requirements
For ECT installation it is necessary a PC with the requirements hereafter described:
1) HW Configuration
– CPU: Pentium III 850 MHz

– RAM: 256 Mbytes (512 Mbytes suggested for Windows XP)
– Hard Disk space: 4 Gbytes
– Display Resolution: 1024x768 pixel
– CD–ROM Drive: 24X
– Primary Interface: Serial Port RS–232–C 9.6 to 57.6 Kbits/sec.
– Optional Interface: Ethernet Card 10/100 Mbits/sec.
2) Windows Versions
– Windows NT 4.0 SP3 till SP6

– Windows 2000 till SP4
– Windows XP till SP1
3) Additional requirements
– Netscape Communicator or MS Internet Explorer 4.x or higher.

– Java 2 Run Time Environment versions from 1.3.1–06 to 1.4.1–04
N.B. Each specific Java version could require minimal Windows SP installation.
4) Additional information
– On IDU PQ/ECRC controller it is requested a Raw Loader version V8.1.0 of May 22nd,
2003 or higher.
– Reference SNMP–IM version: 2.14 (SGPA 3.2.4+).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 231 / 296
296
4–2.2 SWP version specific data
N.B. With reference to the Versions stated on this page, please read carefully the
N.B. on page 274.

4–2.2.1 SW Package Identification
Identification Version Date

SWP REG. 9400AWY R1.0 V1.0.0 April 19th, 2004
4–2.2.2 SW Package Components
Name Description Version

SW Package for 2G Radio Regenerator Low
SWP REG. 9400AWY R1.0 V1.0.0
Capacity PDH Equipments
SWC–ECT9400AWY_V10 Equipment Craft Terminal SW Component V1.0.0
SWC–EC9400AWY_V10 Equipment Controller SW Component V1.0.0
SWC–OCR9400AWY_V10 ODU Radio Controller SW Component V1.4.4
SWC–OCF9400AWY_V10 ODU FSO Controller SW Component V1.0.19
SWC–FD9400AWY_V10 File Descriptor for SW Download Component V1.0.0
4–2.2.3 ECT SW Sub–Components
Name Version Description

JRE V1.4.1–04 Java 2 Run Time Environment
LLMAN V3.3.2 Lower Layers Manager
CT–K V3.0.2 P5 Craft Terminal Base Platform
CT–K SNMP Add–On V3.0.3 P2 Craft Terminal Base Platform SNMP Add–On (EML–IM)
CT–K HOL Add–On V1.0.0 P2 Craft Terminal Base Platform Help On–Line Add–On
JUSM–SNMP–COMMON V1.0.0 User Service Manager for SNMP MW NEs
JUSM–SNMP–HELP V0.1.0 Help On–Line for SNMP MW NEs
CT–K Q3 Add–On V3.0.3 P2 Craft Terminal Base Platform Q3 Add–On (EML–IM)
4–2.2.4 NE MIB Compatibility
NE MIB it is not compatible with previous versions (this is the first version) and has to be manually
configured.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 232 / 296
296
4–2.3 New features and modifications
Not Applicable for first release.

N.B. Version 1.0.0 manages the Radio application only (1+0 configuration).
4–2.4 Restrictions and known problems
– For a corrected operation, only on some PC with Windows 2000 or XP using serial connection, due
to an unidentified problem to be solved by ECT Platform, it is necessary to start Low Layers Manager
before to start ECT Platform (Alcatel 1320CT).
– Alarm Surveillance: the application closure is followed by a message error (with Windows NT only).
No impact in the functionality.
– At first activation sometimes, after NES opening, the message “ANTP: Unrecoverable error” appears
also with ANTP deactivasted (with Windows NT only).
– SNMP Agent it is not able to correctly manage event reporting when IP addresses are different on
NMS ports and Ethernet port.
4–2.5 New features and modifications of SWP versions higher than V.1.0.0
Please refer to next chapters of this section.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 233 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
234 / 296

For versions higher than V1.0.1 please refer to next chapters of this section.
N.B. on page 274.
As for V.1.0.0 (see para.4–2.1 on page 231).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 235 / 296
296
N.B. on page 274.

SWP REG. 9400AWY R1.0 V1.0.1 July 8th, 2004
SW Package for 2G Radio Regenerator Low Capacity

SWP REG. 9400AWY R1.0 V1.0.1
PDH Equipments
CT–K V3.0.3 P4a Craft Terminal Base Platform
CT–K SNMP Add–On V3.1.0 P1b Craft Terminal Base Platform SNMP Add–On (EML–IM)

1AA 00014 0004 (9007) A4 – ALICE 04.10
NE MIB it is automatically converted from previous released versions 1.0.0.
ED 03
3DB 05653 CA AA 236 / 296
296
With respect to the previous SWP REG.9400AWY R.1.0 V1.0.0, the SWP REG.9400AWY R.1.0 V1.0.1
introduces the following features and modifications:
a) Version 1.0.1 manages the Radio application (1+0 and 1+0 Exp/1+1 configurations) and the FSO
application.
b) Inserted new management for polarity configuration by CT on Summarizing alarms.
c) It has been modified to “onlyLocal” the tipology of Near–End Tributary E3/DS3 loopback.
d) It has been extended the management of “Service Kit Connected” alarm for Pegaso ASIC alignment
(1 bit of 1 register).
e) Improved management of Soft–Reset associated to new version of Traminer CPLD.
f) Improved management of “Lac State” in caso of NMS system already connected.
g) It has been extended the loopback management to enable the functionality also to NMS system.
h) Improved management of “CardFail” alarm to speed–up HST switching.
i) It has been extended the management of “LossOfSignal” alarm also in case of Auxiliary Interface
configured as V11 Codirectional.
j) Improved management of maintenance operations control.
k) Improved management of alarms related to EPS TX switch position.
l) Improved management of 1+1 configurations for both ETSI and FCC systems.
m ) Improved management of IDU–ODU connection in case of on–line modification of system capacity

and/or modulation.
n) Improved management of Protections control features.
o) Improved management of Performance Monitoring features.
p) Improved management of TMN–RF pointToPoint in case of on–line modification of system capacity.
q) It has been completed the correct management of HST switch in case of contemporary presence of
the alarms (TX Fail and RUP).
r) It has been resolved the problem on incorrect reporting of MAC Address value associated to LAN
interface.
s) It has been inserted a new version of OC Radio SW, aligned to the same version used on UXFLAT
1+0 configuration, with the following modifications:
• Tx Power filtered on Tx Power configuration changement
• Frequency plan V06 modified on local loop for the RX base band LO Frequency
• IDU detection at ODU startup improvement
• Inhibition of the reading ODU remote received power level interruption, for ATPC
• Correction of a bug in the temperature regulation for the overload attenuator
• Modification of DCA thresholds, for UxFlat
• Configuration saving on data changed only, for UxFlat
1AA 00014 0004 (9007) A4 – ALICE 04.10
• New Perseo parameters to improve 16QAM/8E1, for UxFlat

• Use of MVT detection for all the rates in 4QAM, for UxFlat
• New Perseo parameters to improve 4QAM/8E1, for UxFlat
ED 03
3DB 05653 CA AA 237 / 296
296
4–3.4 Restrictions and known problems
– For a corrected operation, only on some PC with Windows 2000 or XP using serial connection, due
to an unidentified problem to be solved by ECT Platform, it is necessary to start Low Layers Manager

before to start ECT Platform (Alcatel 1320CT).

– Alarm Surveillance: the application closure is followed by a message error (with Windows NT only).
– At first activation sometimes, after NES opening, the message “ANTP: Unrecoverable error” appears
also with ANTP deactivasted (with Windows NT only).
4–3.5 Operative hints
a) Installation procedure
It is the same of previous version 1.0.0 but it is necessary to select “Forced” option on CT screen for
SW Download activation request. This warning has been introduced in relevant procedures:
• para.1–2.3 on page 60
• chapter 1–3 on page 75
b) Configuration change from “1+0 extendable” to “1+1” (9400AWY only)
Some ways to proceed for this configuration change do not give good results. The suggested
procedure has been introduced in para.2–3.1.3 on page 131.
4–3.6 New features and modifications of SWP versions higher than V.1.0.1
Please refer to next chapters of this section.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 238 / 296
296
PRELIMINARY INFORMATION
N.B. on page 274.
In case you receive a SWP with version higher than that stated, please refer to
the documentation accompanying the SWP delivery to get this information.
As for V.1.0.0 (see para.4–2.1 on page 231).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 239 / 296
296
N.B. on page 274.


SWP REG. 9400AWY R1.0 V1.0.2c November 10th, 2004

SW Package for 2G Radio Regenerator Low Capacity
SWP REG. 9400AWY R1.0 V1.0.2c
PDH Equipments

CT–K V3.0.3 P4a Craft Terminal Base Platform
CT–K SNMP Add–On V3.1.0 P1b Craft Terminal Base Platform SNMP Add–On (EML–IM)
NE MIB it is automatically converted from previous released version 1.0.0 and it is compatible with last
released version 1.0.1 and previous pre–releases 1.0.2x.
1AA 00014 0004 (9007) A4 – ALICE 04.10
t.b.d.
ED 03
3DB 05653 CA AA 240 / 296
296
SECTION 5: APPENDICES

Appendix A – Equipment description and components

This Appendix sums–up the equipment functions and defines its components from 243
the SW point of view.
Appendix B – SW allocation, Flash Card and equipment control

This Appendix presents the software allocation in the various parts of the equipment,
251
the types of Flash Card and its contents, and the general characteristics of the ECT
and RECT.
Appendix C – General on SWP installation

259
This Appendix introduces the basic information regarding the software installation.
Appendix D – ECT–Equipment connection via public switched telephone

network
This Appendix explains the operations necessary to allow the remote connection to 263
the F–Interface, from a local PC configurated as ECT, through a switched telephone
line of the standard Public Telephone Network.
Appendix E – Documentation Guide

This Appendix contains all information regarding this handbook (purpose,
applicability, history) and the Customer Documentation set it belongs to, in particular 273
the list of the handbooks the Operators should have in order to carry out the required
operations.
Appendix F – Acronyms and abbreviations 289
Appendix G – Glossary of terms 293
Referenced handbook P/Ns are given in para.E.2 on page 279.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 241 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
242 / 296
APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS
This appendix sums–up the equipment functions and defines its components from the SW point of view:
– Functions and configurations on page 244
– IDU and ODU Components on page 245:
• IDU on page 245
• ODU on page 246
• Allowed Equipment Types on page 247
• Remote Inventory Management on page 249
For more detailed in formation from the hardware point of view, please refer to:
9400 AWY Technical Handbook
or:
9400 FSO Technical Handbook
From the software point of view, the equipment management is carried out as explained in Section 2
AWY/FSO NE MANAGEMENT on page 77, in chapters relevant to the EQUIPMENT CONFIGURATION
MANAGEMENT .
The equipment type HSW indicated in Tab. 21. on page 248 is not managed in current SWP
version.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 243 / 296
296
A.1 : Functions and configurations
ULS NE (9400AWY and 9400FSO) has the aim to multiplexer/demultiplexer the main tributaries (up to 16
E1/16 DS1 or 1 E3/1 DS3) with different modulation formats.

The following Tab. 18. summarizes the relation among market, product type tributaries and modulation.

Tab. 18. Markets, product type, tributaries and modulations forecasted
Market Product Type Tributary Modulation
2xE1 4QAM
4xE1 4QAM / 16QAM
AWY 8xE1 4QAM /16QAM
ETSI 16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
16xE1 4PSK
FSO
1xE3 4PSK
4xDS1 4QAM
8xDS1 4QAM / 16QAM
ANSI AWY
16xDS1 4QAM / 16QAM
1xDS3 4QAM / 16QAM
The main functions performed by IDU and ODU of ULS equipment are the following:
– Multiplexer/Demultiplexer
The multiplexer function receives main tributaries (see Tab. 18. ) and generates a PDH frame.
The demultiplexer function receives a PDH frame and generates main tributaries.
– Signal Protection switch (if any)

The function provides one protection channel for the main signal against channel–associated failures
for both hardware failures and temporary signals degradation or losses due to propagation effects
(e.g. rain) according to equipment configuration.
– Radio Physical Interface (AWY)

The function converts a radio frequency signal into an internal logic level signal, and vice versa
(RPPI). Specifically, the following functions are performed:
• Modulation and Tx functions in the transmit side
• Demodulation and Rx functions in the receive side
– Free Space Optics (FSO)

The function converts an optical signal into an internal logic level signal, and vice versa. Specifically,
the following functions are performed:
• Modulation and Tx functions in the transmit side
• Demodulation and Rx functions in the receive side
ULS NE can be composed by:

– one channel (1+0 configurations and 1+0 extendible configurations);
– two channels (1+1 configurations).
1AA 00014 0004 (9007) A4 – ALICE 04.10
The FSO is supported only in 1+0 configuration. The 2+0 and N+1 configurations are not supported.
ED 03
3DB 05653 CA AA 244 / 296
296
A.2 : IDU and ODU Components
The ULS NE is composed by two different parts: the indoor and the outdoor part. In the following they are
described from physical and management point of view.
A.2.1 : IDU
The indoor part is composed by one shelf (see Fig. 153. and Fig. 154. ). It contains the following units:
– (1+0) IDU
• slot 1: ACCESS Unit
• slot 2: Main Unit
slot 1: ACCESS Unit
slot 2: MAIN Unit
Fig. 153. (1+0) IDU
– (1+1) and (1+0 expandable) IDU

• slot 1: ACCESS Unit
• slot 2: Extension Unit
• slot 3: Main Unit
• slot 4: FAN unit
slot 1: ACCESS Unit

slot 4:
slot 2: EXTENSION Unit (N.B.) FAN
Unit
slot 3: MAIN Unit
Fig. 154. (1+1) and (1+0 expandable) IDU
N.B. In the 1+1 sub–equipped configurations (1+0 EXPANDABLE), slot 2 is not used.
The ACCESS unit accommodates the connectors referred to E1/E3/DS1/DS3 tributaries, user service
channel, housekeeping and summarizing, NMS V11 and G703 interfaces, and a telephone jack.
The Main Unit contains the MULDEM, the PQECRC and the Power Supply units. The MULDEM unit
manages the ETSI 1xE3/16xE1 and ANSI 1xDS3/16xDS1 tributaries, the Mux/Demux and the cable
interface functions. The PQECRC unit implements the Equipment and IDU Controller functions. The Data
unit implementing Ethernet functions can be plugged onto the Main unit. It is not supported in the current
release. The Main unit is used both in 1+0 and 1+1 configurations.
The Extension Unit contains the MULDEM and the Power Supply units. The Hitless unit and the Data unit
implementing Ethernet functions can be plugged onto the Extension unit. Data unit is not supported in the
current release. The Extension unit is used only in 1+1 configurations.
The FAN unit contains fans in order to provide the necessary ventilation to the IDU shelf (t is supported
1AA 00014 0004 (9007) A4 – ALICE 04.10
only in “1+0 expandable” and “1+1 configurations”). Only the FAN unit is shown at SNMP interface,
independently from the number of fans composing it.
ED 03
3DB 05653 CA AA 245 / 296
296
A.2.2 : ODU
According to the configuration type, two ODU types are managed in the Outdoor part. They can be:
– ODU (electrical ODU)

– ODUFSO (optical ODU)

The ODU type is implicitly defined by the NE configuration. Each ODU contains a PQECRC unit which
implements the ODU Controller functions.
ODU / ODUFSO
Fig. 155. (1+0) ODU (electrical or optical)
ODU Ch#1 ODU Ch#2
Fig. 156. (1+1) ODU (only electrical)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 246 / 296
296
A.2.3 : Allowed Equipment Types
This paragraph provides information on the allowed equipment types for all the configurations supported
by ULS NE.
[1] Shelves Equipment Types
The following Tab. 19. provides the shelves equipment types allowed for each supported NE
configuration and market type:
Tab. 19. Shelves Equipment Types

Allowed
NE Market Shelf Allowed Equipment Type Equipment
Equipment
Configuration Type position Description Label
Type
(note 1) 1 IDU 1+0 Shelf IDU10 IDU
1+0 ETSI ODU 1+0 4/16 QAM ETSI ODU–E
2 ODU Ch#1
ANSI ODU 1+0 4/16 QAM ANSI ODU–A

1+0 FSO
ETSI 2 ODU 1+0 FSO ETSI ODUFSO–E ODUFSO

ETSI ODU 1+0 4/16 QAM ETSI ODU–E
1+1
1 1 2 ODU Ch#1
(note 2)
ETSI ODU 1+0 4/16 QAM ETSI ODU–E
3 ODU Ch#0
(note 1) The equipment types allowed for IDU shelf are market type independent.
(note 2) All the 1+1 configurations. In case of 1+0 extendible configurations shelf position 3 is not
supported.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 247 / 296
296
[2] : Slots and Sub–slots Equipment Types
The following tables indicate the allowed equipment types for each slot inside each shelf type and
if the equipment expected value is settable by the operator.

• IDU
Tab. 20. IDU allowed board/plug–in types in (1+0) configurations
IDU10
Allowed
Equipment
Position Allowed Equipment Type Description Equipment
Label
Type
1.1 Access Unit ACCESS IDU/ACCESS
Main Unit ±24V Range Supply M24

IDU/MAIN
1.2 Main Unit ±48/±60 V Range Supply M4860
Ch#1
Main Unit ±48/±60 V Range High Power Supply (N.B.) M4860H
N.B. This power supply (“high power” version) is allowed only in case of 1+0 FSO configuration.
Tab. 21. IDU allowed board/plug–in types in (1+1) and (1+0 expandable) configurations
IDU11
Allowed
Equipment
Label
Type
1.1 Access Unit ACCESS IDU/ACCESS
Not provisioned EMPTY

1.2
Extension Unit ±24V Range Supply E24 IDU/EXT Ch#0
(note 1)
Extension Unit ±48/±60 V Range Supply E4860
1.2.1 Hitless Switch unit (not managed in current SWP IDU/EXT/HSW

HSW
(note 2) version) Ch#0
Main Unit ±24V Range Supply M24

1.3 IDU/MAIN Ch#1
Main Unit ±48/±60 V Range Supply M4860
1.4 FAN unit FAN IDU/FAN
(note 1) In the 1+1 sub–equipped configurations this slot is empty.
(note 2) Position 1.2.1 is created only in the 1+1 Hitless configurations (HST and FD).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 248 / 296
296
• Electrical ODU
No slot can be defined inside the Electrical ODU.
• Optical ODU
Tab. 22. Allowed board types in optical ODU ETSI
ODUFSO–E
Allowed
Equipment
Label
Type
2.1 Optical Interface ETSI board OPINT–E ODUFSO/OPINT
2.2 Optical Transceiver board OPTR ODUFSO/OPTR
A.2.4 : Remote Inventory Management
The Remote Inventory feature allows to store the information useful to identify the components of the
product.
From management point of view the Remote Inventory data will be provided by the following equipment
types:
– Main Unit (M24, M4860, M4860H)
– Extension Unit (E24, E4860)
– Hitless Switch Unit (HSW) (not managed in current SWP version)
– Access Unit (ACCESS)
– FAN unit (FAN)
– ODU unit (ODU–E, ODU–A )
– ODU FSO unit (ODUFSO–E)
For all the other equipment types the remoteInventoryStatus columnar object assumes the value
“unavailable”.
The RI data of each sub–components unit (i.e. MULDEM in the IDU, MILOU in the ODU, OPTR in the
ODUFSO) won’t be seen at SNMP management interface but only by means of factory tools.
Also the information about the equipment type can be read from the remote inventory data (‘Unit
mnemonic’ field). All the units are provided in its own remote inventory data this type of information. It is
used to identify the actual equipment type and then, eventually, to provide an equipment mismatch alarm,
if the equipment type read from remote inventory data is different from the equipment expected provided
by the managers.
If it isn’t possible to read the Remote Inventory information, a “Card Fail” alarm is declared.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 249 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
250 / 296
APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL
This Appendix presents:

– the software allocation in the various parts of the equipment, herebelow
– the types of Flash Card and its contents, on page 254

– the general characteristics of the ECT and RECT, on page 256.
Fig. 157. herebelow shows the Interfaces for equipment control
Fig. 158. herebelow shows the MAIN UNIT + FLASH CARD unit assembly view
Fig. 159. herebelow shows the FLASH CARD profile and insertion direction
Ethernet Interface F Interface Flash card

for OS connection for ECT connection label
Fig. 157. Interfaces for equipment control and Flash card label on MAIN Unit
EQUIPMENT CONTROLLER BABY BOARD (PQ/ECRC)

FRONT PLATE
MAIN BOARD
FLASH CARD
Fig. 158. MAIN unit + FLASH CARD
TOP SIDE
INSERTION
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 159. FLASH CARD profile and insertion direction
ED 03
3DB 05653 CA AA 251 / 296
296
B.1 : Allocation of equipment and craft terminal software
Fig. 160. herebelow roughly depicts the NE main parts containing the local SW and the interfaces with the
Operator (Extension Unit and RT–0 are present in 1+1 configuration and are not equipped in 1+0

compact/expandable configurations).

MAIN UNIT
PQ/ECRC SUBUNIT
FLASH
F CARD
EQUIPMENT
Ethernet
CONTROLLER
RAM
MULDEM
SUBUNIT
EXTENSION UNIT
MULDEM
SUBUNIT
RT–0
FLASH
EPROM
ODU
CONTROLLER
RAM
RT–1
FLASH
EPROM
ODU
CONTROLLER
RAM
Fig. 160. Equipment main parts containing local SW

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 252 / 296
296
c) Local software allocation
Once the system has been configured and activated (as explained in Section 1 Installation),
Equipment and Craft Terminal must not necessarily be left connected, because equipment contains
all the software necessary for its working.
This equipment local software comprises programs and configuration data. Programs and data are
managed differently from each other:
1) Equipment Controller
Whole Equipment SW (programs and configuration data) is contained in the Flash Card housed
in MAIN unit’s PQ/ECRC sub–unit (the Flash Card contains also the software (programs and
configuration data) relevant to the peripheral units, i.e., in the figure RTs). See Fig. 158. and
This flash card is removable (i.e. replaceable), and the programs can be overwritten by a SW
download from CT (through F interface) or Network Management Operation System (through
Ethernet interface) to the MAIN unit.
More precisely, the Flash Card contains two independent instances of the Equipment SW
programs (one active, the other stand–by), so that the above cited SW download is actually
done toward the stand–by instance, while equipment goes on working with the SW programs
of the active instance. Swapping between the two instances is done only under Operator’s
request.
2) Peripheral Units
The Peripheral units (RTs) contain their own local SW (programs and configuration data),
housed in a local Flash Eprom (physically not removable). The programs in this local Flash
Eprom can be overwritten by means of a SW download from the Equipment Controller with the
same active–standby duplication described before for the Equipment Controller.
3) Equipment Configuration Data (MIB)

The whole equipment configuration data (together with programs) are stored in the MAIN unit
PQ/ECRC sub–unit Flash Card. Refer to point B.2.3 on page 255 for details.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 253 / 296
296
B.2 : Flash Card
B.2.1 : Flash Card types

A FLASH CARD is plugged into the Main board (see Fig. 158. on page 251) giving the maximum capacity
for the tributaries and the modulation type as reported in the following Tab. 23. (5 possible types of Flash
card).
Tab. 23. Available Flash cards
Flash Card Name Capacity Modulation
Full Flexible Flash Card Full flexible Full flexible
16xE1/DS1 16 QAM Flash Card Full flexible 16 QAM
4xE1/DS1 16 QAM Flash Card Up to 4xE1/DS1 16 QAM
16xE1/DS1 4 QAM Flash Card Full flexible 4 QAM
4xE1/DS1 4 QAM Flash Card Up to 4xE1/DS1 4 QAM
Notes:
1) A 16 QAM Flash card does not allow the transmission of a 4 QAM signal.
2) A 4xE1/DS1 Flash Card does not allow the transmission of a capacity greater than 4xE1/DS1.
3) As far as E3/DS3 tributary rate is concerned, only the Full Flexible Flash card can be selected.
4) The Full Flexible Flash Card allows the transmission of whatever capacity and modulation.
5) In 9400FSO equipment, only the Full Flexible Flash Card can be used.
6) For the P/Ns of the Flash Card types please refer to the:
9400 AWY/FSO Technical Handbook,

section “System composition and configurations”
chapter “IDU part list“
B.2.2 : Flash Card identification
a) the Flash Card P/N is reported on the label affixed on it;
b) moreover, the Flash Card Name is affixed on the label present on the front panel of the Main
Unit (see Fig. 157. on page 251).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 254 / 296
296
B.2.3 : Flash Card contents
The following table indicates the FLASH CARD contents in the various phases of SW management:
NE DATA
BASE
PHASE SW PROGRAMS ROUTING

CONFIGURATION MIB
CONFIGURATION
n.b.1
n.b.2
1) As supplied
Not present Not present Not present
by Factory Defined byy Flash
2) After SWP Card P/N. To be defined by To be defined by
download Not changeable, C.T. C.T.
but with Flash Present
3) After NE data Card upgrade
Present Present
definition (see para B.2.4
herebelow) By a new SWP
MODIFICABILITY⇒ Yes, by C.T. Yes, by C.T.
download n.b.4
SAVE/RESTORE⇒ NO Unmeaningful NO NO n.b.3
NE= Network Element C.T. = Craft Terminal SWP= Software Package
n.b.1 MIB
The system configuration data set is named MIB. Such data are defined by Craft Terminal after
the SWP download. They can be changed only within the limits implicitly defined by the
employed Flash Card type. For its save/restore refer to n.b.3 herebelow.
n.b.2 ROUTING CONFIGURATION DATA
They are:
1. Local configuration ⇒ System’s local address
2. NTP server configuration
3. Interface configuration ⇒ NMS configuration
⇒ Ethernet configuration
4. IP configuration ⇒ IP Static Routing configuration
⇒ OSPF AREA configuration
All those listed parameter are NOT stored into the MIB file because considered unique to a
particular system in a network and are NOT meant to be reproduced on other systems in the
same network because will cause conflicts in the supervision network centre.
n.b.3 The MIB file save/restore to/from a file in the Craft Terminal (or OS) environment is not possible
in SWP first version(s). It should be possible in future versions(s).
n.b.4 A new SWP download is envisaged whenever a new SWP package version or release (new with
respect to that presently loaded in the system) is supplied to Customer (*).
(*) for the meaning of SWP package version and release refer to para.E.2.5.2 on page 286.
B.2.4 : Flash Card upgrade (for 9400AWY only)

Refer to the instructions given in the:
9400AWY Technical Handbook, section “System composition and configurations”

chapter “IDU operative information“, para.”Flash Card”
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 255 / 296
296
B.3 : Equipment control
B.3.1 : Interfaces (see Fig. 157. on page 251):

• The NE can be controlled by the OS (e.g. Alcatel 1353SH) through the Ethernet interface.
• ECT (Equipment Craft Terminal, briefly Craft Terminal) can be connected to the MAIN unit
through a RS232 interface (F interface). This connection can be:
– local (ECT) through a suitable cable supplied with the equipment, or remote (RECT) as
explained in para.B.3 on page 256
– remote through a ECT–equipment connection via public switched telephone network, as

explained in Appendix D on page 263.
B.3.2 : Operator–Equipment Interaction
1) The Local Operator can manage the Equipment software programs and most configuration data
through the Equipment Craft Terminal 1320CT connected to the F interface (see Fig. 160. on
page 252 and Fig. 157. on page 251).
The Craft Terminal characteristics (computer configuration) are listed in chapter 4–2 on page
231.
The Craft Terminal is a project in charge of the local management of single network elements,
providing ITU– compliant Information Model Interface to the Network Element.
Multiple NE management up to 128 Network elements is possible obtaining a remote Craft
Terminal application.
The general information on the Craft Terminal is presented in the:
1320CT Basic Craft Terminal Operator’s Handbook
that the operator has to read before this Handbook.

In this Handbook is given the general description regarding use, navigation, rules, etc., common
to all the NE using the same Craft Terminal.
Furthermore, the same handbook contains the detailed description of common operations as
“Installation” and common screens as “Network Element Synthesis view”.
The Network Element Synthesis view is the first view presented to the operator entering the
application.
Starting from this view it is possible to login to the NE and then to enter the EML–ULS views.
This Operator’s Handbook deals with the EML–ULS views of the Craft Terminal, which directly
allows to manage the Network Element.
A detailed description of the AWY/FSO’s EML–ULS screens is given in the dedicated Sections
2–AWY/FSO NE MANAGEMENT and 3–AWY/FSO MAINTENANCE of this handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 256 / 296
296
2) A further SW application, also available in the PC and OS environment and named SIBDL
(Standard Image Binary Download), deals with the SW download in special cases, which are
detailed in the following. The physical interface for running this application from Craft Terminal
is ’F’ interface.
The installation and use of SIBDL is detailed in the dedicated Section of the:
or
B.3.3 : ECT
ALCATEL TMN management products 1320 CT called Craft Terminals (CT) consists of a compatible
personal computer and application software specially developed for monitoring transmission
equipment. The CT designed to monitor a single transmission equipment is called Equipment Craft
Terminal (ECT) or 1320CT.
For each 9600USY&MDR9000s station an ALCATEL proprietary SWP (SoftWare Package) is

employed, which depends on the product–release and the NE (Network Element) associated to the
specific configuration.
B.3.4 : RECT
The Remote Equipment Craft Terminal is a feature only present in the Single NE Link architecture
which allows the local operator, using an ECT connected to the F interface of the NE, to zoom and
perform a complete set of management operations on all the reachable NEs in the network.
The Remote NE can be physically reached through the NMS channels or Ethernet LAN.
RECT can be connected to any NE pertaining to the same area of the local NE and to any NE
pertaining to different areas (assuming that the DCN network has been correctly designed and hence
inter–area communication is possible from networking viewpoint).
Of course, due to the limitation of the physical resources in the Equipment Controller of the NE, some
network design constraints must be taken into account as the total number of managed NEs (128).
The RECT features and limitations are briefly the following:
1) The RECT function provides a remote login facility similar to those offered by an OS to manage
several configured NEs, included the local one.
2) The contemporaneous presence of the RECT function and an OS is possible. The access
disable flag avoids access conflict between the OS and both RECT and ECT on some
operations as configuration modification and remote control with access filtering.
3) The NE which may be remotely controlled by a RECT must be configured and must be loaded
with the same SW version supporting the RECT function. A NE not supporting RECT function
shall refuse the incoming association issued by a RECT and the ECT displays only local
information.
4) Only three RECTs shall be active at a time over one NE. The coexistence of ECTs and RECTs
in the whole network is guaranteed since the conflict in configuring the NEs is solved locally by
the NE itself.
5) The operator, through the RECT function, is able to see the alarm synthesis of the whole
network .
6) In a network the maximum number of NEs equipped with the RECT function are 128. This value
1AA 00014 0004 (9007) A4 – ALICE 04.10
identifies what it is understood as ”small network” for which the RECT function may replace the
Element Manager.
ED 03
3DB 05653 CA AA 257 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
258 / 296
APPENDIX C : GENERAL ON SWP INSTALLATION
This Appendix introduces the basic information regarding the software installation.
N.B. Before reading this paragraph, it is suggested to read (if not yet done) previous para.B.1 on
page 252.
Fig. 161. depicts the main phases for SW management.
SWP
CD–ROM
1) SWP LOADING IN PC
MS–NT ENVIRONMENT
CRAFT TERMINAL
2) NEW SWP
INSTALLATION
3) NE SWP LOADING
INTO EQUIPMENT
CONTROLLER
(if necessary)
DURATION:
– 1/2 hour with
interface F
– some minutes with
Ethernet interface
4) AUTOMATIC SW
5) NE CONFIG. DOWNLOAD TO
DATA MNGT SUPERVISOR UNITS
(if necessary)
DURATION:
some minutes
1AA 00014 0004 (9007) A4 – ALICE 04.10
Fig. 161. Software management main phases
ED 03
3DB 05653 CA AA 259 / 296
296
The SW management can be distinguished into:
– program management, i.e.:

• (1) and (2) : SWP loading from CD–ROM to the Personal Computer, after which the PC

becomes and can be used as the Equipment Craft Terminal
• (3) NE SWP downloading from ECT toward the Network–Element’s Equipment Controller (EC)
• (4) SW downloading from EC toward the Peripheral Units.
– NE configuration data management:
• (5) NE configuration data definition.
The installation can be distinguished in two main procedures:
– SWP installation in PC environment

that includes tasks (1) and (2) mentioned above.
The relevant operating instructions are given in chapter 1–1 on page 23
– SWP download toward NE

that includes tasks (3) to (5) mentioned above.
The relevant operating instructions are given in chapter 1–2 on page 59
These main procedures are usually carried out sequentially; some different situations are described in
para.C.2 on page 261.
Furthermore, additional procedures are envisaged to be used in special situations, as described in

para.C.1 herebelow.
C.1 : Troubleshooting situations
In the following situations:
1) Flash Card to be replaced
or:
2) NE not in–factory configured
use the SW download through SIBDL program; refer to the dedicated section of the:
or

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 260 / 296
296
C.2 : Common situations
1) Network Element already configured with the more recent SWP version and Craft
Terminal already available.
ECT NE
ECT release = NE release

A.B.c ECT version = NE version A.B.c
This is the typical situation of new installations: the Network Element SW configuration matches
the available Craft Terminal SWP version, so that the NE can be logged–in and the Operator
can carry out the required operations, without any preliminary actions.
2) Network Element already configured with the more recent SWP version, but the Craft
Terminal is not available or has a version older with respect to that of the Network
Element(s).
ECT NE
ECT release = NE release
A.B.c ECT version < NE version A.B.d
In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter
1–1 on page 23. After that, the situation is equal to that of point 1 ) above.
3) Both Network Element and Craft Terminal already configured with a SWP version older
than that made available by the a new SWP version (SAME RELEASE)
ECT NE
running release = SWP release SWP
CD–ROM
A.B.c = A.B.c running version < SWP version
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.1.0.0), in the case a newer version of the same A.B SWP package has to be installed
(e.g.1.0.1).
Refer to Chapter 1–3 on page 75.

After that, the situation is equal to that of point 1 ) above.
N.B. Please refer to para.E.2.5.2 on page 286 for the meaning of SWP Release, Version and Patch
Level.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 261 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
296
3DB 05653 CA AA
262 / 296
APPENDIX D : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED
TELEPHONE NETWORK
D.1 : Introduction
This chapter explains the operations necessary to allow the remote connection to the F–Interface, from
a local PC (with external or internal modem) configured as ECT, through a switched telephone line of the
standard Public Telephone Network, as shown in Fig. 162. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.

F Interface
Port COM

Fig. 162. ECT–Equipment connection via Public Switched Telephone Network

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 263 / 296
296
D.2 : Certified equipment
The connection has been successfully tested:

a) with the following types of modems:

1) Modem Sportster Flash (US Robotics)
2) Modem TD–32 AC (Westermo Teleindustri AB)
3) 3Com 56K Faxmodem
b) with the following types of PC:
1) with external modem:

characteristics as in para.4–2.1 on page 231
2) with internal modem:

PC laptop Dell Latitude:
– Processor equipped: PENTIUM III
– Operating system: Microsoft Windows 2000 v. 5.00.2195 service pack 2
– RAM equipped: 128 Mbytes
– Hard disk equipped: 10 Gbytes
– Internal Modem: 3COM 56K v.90 Mini PCI MODEM
c) and with the following local/remote combinations:
Local Modem Remote Modem
Sportster Flash
Sportster Flash TD 32 AC
3Com 56K Faxmodem
TD 32 AC
TD 32 AC Sportster Flash
3Com 56K Faxmodem
TD 32 AC
PC laptop Dell Latitude as in
Sportster Flash
point b ) 2 ) above
3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customer’s charge.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 264 / 296
296
D.3 : Connection cables
In the following figures, the cables for the connections are described:
PC/ECT (DTE) Local Modem (DCE)

Cannon 9 pins female Cannon 25 pins male
DCD 1 8 DCD
TD 2 3 TD
RD 3 2 RD
DTR 4 4 RTS
DSR 6 5 CTS
RTS 7 6 DSR
CTS 8 20 DTR
GND 5 7 GND
Fig. 163. ECT–Local external Modem cable
Remote Modem (DCE) F Interface (DCE)

Cannon 25 pins male Cannon 9 pins male
TD 2 3 TD
RD 3 2 RD
RTS 4 7 RTS
CTS 5 8 CTS
DSR 6 6 DSR
CTS 20 4 DTR
GND 7 5 GND
Fig. 164. F Interface–Remote Modem cable

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 265 / 296
296
D.4 : Modem setting
D.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem

This modem requires only a SW setting via serial port.
There is a little difference between local and remote modems setting (refer to Fig. 162. on page 263 for
the distinction between “local” and “remote”), relevant to the auto–answer option that must be set in the
remote modem and not set in the local modem.
LOCAL MODEM SETTING
To set the local modem, proceed as follows:
1) Only for external modem: connect the local modem to the PC/ECT with the cable of Fig. 163. on
page 265.
2) Only for external modem: Power and switch on the local modem.
3) On the PC, activate program HyperTerminal and configure the PC–Modem serial line with the
* Bits per second: 38400

* Data Bits: 8
* Parity: None
* Stop Bit: 1
* Flow control: None
4) Execute and store the modem set–up, writing the following commands in the HyperTerminal
program window:
AT&F1<Return> (Best PC default configuration recall)

ATT<Return> (Tone Dialling instead than Pulse Dialling)
ATX3<Return> (Second Signal disabling, avoids problems with PABX)
AT&W0<Return> (Configuration store in NVRAM 0)
5) Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 266 / 296
296
N.B. For confirmation, the modem configuration can be checked writing the command
“ATI4<Return>” in the HyperTerminal program window.
Information displayed should be as follows:
ATI4
U.S. Robotics Sportster Flash 56000 Settings...
B0 E1 F1 L2 M1 Q0 V1 X3 Y0
BAUD=38400 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE CID=0
&A3 &B1 &C1 &D2 &H1 &I0 &K1

&M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004

S07=060 S08=002 S09=006 S10=014 S11=072 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=001 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=012 S40=000
S41=004 S42=000
LAST DIALED #:
REMOTE MODEM SETTING
To set the remote modem, proceed as follows:
a) carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting
b) execute and store the modem set–up, writing in the HyperTerminal program window the same
commands described in step 4 ) for the local modem setting, and adding the following command:
ATS=1<Return> (Auto–answering setting)
c) now, setting has been completed. Modem can be switched off and disconnected, if necessary.
“ATI4<Return>” in the HyperTerminal program window.
Information displayed should be equal to that displayed for the local modem, with only the
difference for field S00:
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 267 / 296
296
D.4.2 : TD–32 AC Modem setting
This modem requires an initial HW set–up via dip–switches and a SW setting via serial port.
To set the modem, both local and remote, proceed as follows:

1) The initial HW set–up via dip–switches is indicated in Fig. 165. herebelow:
ON ON ON
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4
SW3 SW2 SW1
ON ON
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
SW5 SW4
Fig. 165. TD–32 AC modem dip–switch setting
2) Connect the local modem to the PC/ECT with the cable of Fig. 163. on page 265.
3) Power on the local modem (there is no an ON/OFF switch).
4) On the PC, activate program HyperTerminal and configure the PC–Modem serial line with the

* Data Bits: 8
* Parity: None
* Stop Bit: 1
5) Execute and store the modem set–up, writing the following commands in the HyperTerminal
program window:
AT&F1<Return> (Best PC default configuration recall)

AT&K0<Return> (DTE/DCE flow control disabling)
ATA<Return> (Automatic Answer enabling ––> Only on Remote modem and
wait the message “NO CARRIER”)
AT&W0<Return> (Configuration store in NVRAM 0)
AT&Y0<Return> (Configuration Set to load at switch–on: NVRAM 0)
6) Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 268 / 296
296
“AT\S<Return>” in the HyperTerminal program window.
Information displayed should be as follows:
AT\S
CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION

––– –––––––––––––––––––– ––– –––––––––––––––––––– ––– ––––––––––––––––––––
COUNTRY...........IT &A CHR ABORT OPT.....NO *H NEG. SPEED......HIGH
DTE BPS........38400 &B DTR DIAL OPTION...NO S0 RINGS TO ANS.....002
DTE PARITY.....8NONE &C DCD OPTION........ON S1 RING COUNT.......000
LINE SPEED......NONE &D DTR OPTION.........0 S2 <ESC> CHAR.......043
B BELL MODE........OFF &G GUARD TONE......NONE S3 <CR> CHAR........013
E CMD ECHO..........ON &K FLOW CONTROL....NONE S4 <LF> CHAR........010
F LINE MODE.......AUTO &L NETWORK.........PSTN S5 <BS> CHAR........008
L SPKR VOLUME......LOW &Q ASYNC/SYNC.........5 S7 CONNECT TIME.....060
M SPKR CONTROL....CALL &R RTS/CTS.........AUTO S8 PAUSE TIME.......002
N AUTO MODE.........ON &S DSR OPT............0 S12 ESC GUARD TIME...050
Q QUIET............OFF &T ENABLE RDL........NO S30 CONNECT INACT....000
V RESULT FORM.....LONG &X SYNC CLOCK.......INT S32 XON CHAR.........017
W EC MSG.............0 &Y PROFILE........NVM.0 S33 XOFF CHAR........019
X EXT RESULTS........4 \A MAX BLK SIZE.....192 S36 FALLBACK ACTION..007
Y LONG SPACE DISC...NO \G REMOTE FLOW......OFF S37 MODE SELECT......000
%C COMPRESSION.....BOTH \K BRK OPT............5 S48 V42 NEG CTRL.....007
–K EXT. SERVICES......0 \N ECL MODE........AUTO S95 RES. CODE........000
D.5 : PC laptop “Dell Latitude” setting
The following setting must be done:
Control Panel –> Alcatel Lower Layer –> Serial port –> COM3 and Serial port selected
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 269 / 296
296
D.6 : Setting up the connection
In order to activate the connection and operate the ECT in remote way, proceed as specified herebelow.
Refer to Fig. 162. on page 263 for the distinction between “local” and “remote” modems.

N.B. Leaving the remote modem permanently switched on and permanently connected to

F–interface and telephone line, operations set up by steps 1 ) thru 4 ) , it is possible to access
the equipment in any moment.
In order to access the equipment by local ECT, proceed as specified in steps 5 ) thru 14 ) .
1) Connect the remote modem to equipment’s F interface with the cable of Fig. 164. on page 265.
2) Connect the remote modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipment’s F
interface and signed with the ’wall’ symbol).
3) Power and switch on the remote modem.
4) Be sure remote equipment is switched on and correctly working.
5) Connect the local modem to the PC/ECT (with the cable of Fig. 163. on page 265.) on the serial
port assigned for the connection with F interface (usually COM1).
6) Connect the local modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipment’s F
interface).
7) Power and switch on the local modem.
8) On the PC, activate program HyperTerminal and configure the PC–Local Modem serial line with
the following parameters:

* Data Bits: 8
* Parity: None
* Stop Bit: 1
9) For PC laptop Dell Latitude only, type the following command inside HyperTerminal program:
’AT&C0&D0&R1’
N.B. this command must be typed every time the Hyper terminal session is opened (this
command is not stored in the modem NV RAM).
10 ) Execute the telephone call from the PC writing the following command in the HyperTerminal
program window:
ATDnnn<Return>
where “nnn” is the telephone network number associated to the remote telephone line (that
which the remote modem is connected to).
11 ) Wait the message indicating the successful connection between local and remote modems.
N.B. The message text depends on the modem type, as follows:
“CONNECT 14400/ARQ/V32/LAPM/V42BIS“ (Sportster Flash)

“CONNECT 38400” (TD 32 AC)
12 ) Close HyperTerminal program.
13 ) Activate the ECT applicative SW as usual.
14 ) At the end of the job, after having logged out from the ECT applicative SW, close the connection
1AA 00014 0004 (9007) A4 – ALICE 04.10
between local and remote modems, switching off the local modem or physically disconnecting
the cable connecting it to the PC.
ED 03
3DB 05653 CA AA 270 / 296
296
D.7 : Changing the ECT–equipment connection speed
D.7.1 : Introduction
This feature is meant to use modems with speed different from that documented in previous paragraphs,
giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,
56000) with automatic management of modem set–up and phone call at ECT start–up.
As a matter of fact, this feature is not enough to set up the desired configuration.
To make change operative, the following operations should be necessary:
– at equipment side, special pshell text commands must be forwarded through a special cable to be
plugged inside the equipment
– at PC side, the configuration must be set–up as explained in the following para.D.7.2 on page 272.
The default speed is 38400 and must not be changed by Customer !
Customers who need the change of modem speed must require the
operation to be performed by the Technical Assistance Center (TAC) of
relevant Alcatel Selling or Supporting Unit.
DO NOT ATTEMPT TO USE THIS FEATURE

WITHOUT TAC ASSISTANCE.
YOU COULD CAUSE
UNRECOVERABLE ECT UNACCESSIBILITY.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 271 / 296
296
D.7.2 : Configuration at PC side
N.B. Please read carefully paragraph Introduction on page 271.
To configure the modem with the relevant speed, enter the menu Settings –> Control Panel of the

Operating System and open the Alcatel Lower Layers utility. The menu of Fig. 166. opens.
Fig. 166. Alcatel Lower Layers utility
In the Sub–network Type field select Modem.

In the Modem field select the suitable Modem type.
In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK.
In the Phone Number field enter the phone number, which will be automatically called at the ECT start–up.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 272 / 296
296
APPENDIX E : DOCUMENTATION GUIDE
This appendix contains all information regarding:

– this handbook, herebelow
– the Customer Documentation set this handbook belongs to, on page 279
E.1 : Handbook guide
This paragraph contains all information regarding this handbook:
– Handbook applicability on page 274
– Purpose of the handbook on page 275
– Handbook history on page 276

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 273 / 296
296
E.1.1 : Handbook applicability
a) Product-release applicability
This handbook applies to the following product-releases:

• 1+0 or 1+1 for Radio application 9400AWY
PRODUCT RELEASE ANV P/N FACTORY P/N

9411AWY 1.00.00 3DB 05476 AAAA 522.174.410
9413AWY 1.00.00 3DB 05478 AAAA 522.174.500
9415AWY 1.00.00 3DB 05481 AAAA 522.174.600
9418AWY 1.00.00 3DB 04729 AAAA 522.174.000
9423AWY 1.00.00 3DB 05484 AAAA 522.174.700
9425AWY 1.00.00 3DB 05490 AAAA 522.174.900
9428AWY 1.00.00 3DB 05493 AAAA 522.175.000
9432AWY 1.00.00 3DB 05496 AAAA 522.175.100
9438AWY 1.00.00 3DB 04732 AAAA 522.144.100
• 1+0 for Free Space Optics application 9400FSO
PRODUCT RELEASE ANV P/N FACTORY P/N

9400FSO 1.00.00 3DB 04263 AAAA 522.173.500
b) NE applicability
This handbook applies to the following Network Elements (NE): ULS
c) SWP Version applicability

This handbook applies to the following Software Package Releases (SWP) and SWP versions:
SWP ANV & SWP Version

SWP Release
FACTORY P/N (N.B.1)
V.1.0.0 (N.B.2)
SWP 9400AWY R.1.0 CD–ROM ref.Tab. 16. on p
page
g 229 V.1.0.1 (N.B.3)
V.1.0.2
N.B.1 For the meaning of SWP Release and Version, please refer to para.E.2.5.2 on page 286.
The indication of the Versions in this handbook has the following meaning:
this handbook applies starting from the Versions stated in this table, but it could also apply to
subsequent Versions for the following reasons:
a) the Operator Handbook is not modified, unless the new version distributed to the
Customers comprises changes to the man–machine interface, or even in the presence of
minor changes that do not affect negatively the understandability of the procedures
described therein (e.g. a ”button” moved internally to a screen);
b) furthermore, if the screens contained in the handbook show the ”version–release” of the
”product–release”, then they are not replaced in the subsequent versions of handbook if
their contents remains unchanged.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B.2: Version 1.0.0 manages the Radio application only (1+0 configuration).
N.B.3: Versions from 1.0.1 manages the Radio application (1+0 and 1+1 configurations) and the
FSO application.
ED 03
3DB 05653 CA AA 274 / 296
296
E.1.2 : Purpose of the handbook
This handbook belongs to the Customer Documentation set envisaged for the equipment specified in para.
E.1.1 on page 274.
Please refer to para.E.2 on page 279 to have the list and description of such Customer Documentation
set.
This handbook describes the operation and maintenance activities the operators can carry out according
the specific software application(s) referred to in this handbook (see para. E.1.1 on page 274).
This handbook must be used together with the associated Technical Handbook and, with some
exceptions, does not replicate information contained into it.
In particular, all cautions relevant to safety on rules for EMC and ESD, as well as warnings regarding
operations that may cause damages to the equipment, are not duplicated here, but must be retrieved from
the Technical Handbook.
When using this handbook, it is assumed that the Operators know:
• the structure (hardware composition) and all the possible operating modes of the equipment
(product-release) that this handbook refers to.
• how to use a PC and the Windows environment applications.
Before accessing other sections of this handbook, read completely this section in order to have information
on:
– SWP P/Ns and composition
– how to access the other sections of this handbook according to the SWP type (if more than one
envisaged)
– how to manage Craft Terminal SW and Equipment SW for new installations or for upgrading previous
installation to the new SW version.
– how to make ECT–equipment remote connection on Public Switched Telephone Network.
The document that should be read before starting this document is:
– 9400 AWY Technical Handbook from Ed.03 for the Radio application.
– 9400 FSO Technical Handbook for the FSO application.
N.B. In any case, the Technical Handbook must be always available to the Operator in charge
of the equipment software management, as it contains information and documents that are
used in the procedures described in this manual (e.g. the hardware setting documents, the
unit replacement procedures (N.B.), etc.).
Reading the following manual:
– 1320CT Basic Operator’s Handbook V3.0.1
is not strictly necessary before starting this document, but its knowledge is necessary for operating the
procedures introduced by this document and detailed in the other sections of this Handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 275 / 296
296
E.1.3 : Handbook history
The first and the two most recent editions of the document are indicated in the table of contents. Changes
with respect to the previous edition are pointed out by revision bars.

The following Tab. 24. indicates the handbook parts new and modified with respect to the previous edition.
Legend
n = new part m = modified part blank= part unchanged
Tab. 24. Handbook history

HANDBOOK EDITION ⇒ 01 02 03 04 05
FRONT MATTER n
Preliminary information n
Handbook applicability, purpose and history n
Handbook structure n
Safety–EMC–ESD norms and equipment labelling n
Cautions to avoid equipment damage n m
Quick guide n m m
SECTION 1: INSTALLATION n m
1–1 SWP installation in PC environment n m m
1–2 SWP download toward NE n m m
ÉÉ
ÉÉ
1–3 NE Upgrade to a newer SWP ’version’ (same SWP ’release’) n m
SECTION 2: AWY/FSO NE MANAGEMENT n
2–1 General introduction on views and menus n m m
2–2 Configuration n m
2–3 Equipment n m m
2–4 Line Interface n m
2–5 Radio n m
2–6 FSO n m m
2–7 External input and output points n m m
2–8 Supervision n
2–9 Protection schemes n m m
2–10 Loopbacks n m
2–11 Diagnosis n
2–12 Performance Monitoring n m
2–13 Software Download n m
SECTION 3: AWY/FSO NE MAINTENANCE n
3–1 Maintenance introduction n
3–2 Troubleshooting n
table continues
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 276 / 296
296
Tab. 24. Handbook history
HANDBOOK EDITION ⇒ 01 02 03 04 05
SECTION 4: SWP DESCRIPTION AND VERSIONS n m m
4–1 SWP REG.9400AWY R.1.0 description n
ÉÉÉ
4–2 SWP REG.9400AWY R.1.0 V.1.0.0 specific information n m m

4–3 SWP REG.9400AWY R.1.0 V.1.0.1 specific information
ÉÉÉÉÉÉ n m
4–4 SWP REG.9400AWY R.1.0 V.1.0.2 specific information
SECTION 5: APPENDICES
ÉÉÉÉÉÉ
ÉÉÉÉÉÉn
n
A Equipment description and components n m

B SW allocation, Flash Card and equipment control n m m
C General on SWP installation n m
ECT–Equipment connection via public switched telephone
D n
network
E Documentation Guide n m m
F Acronyms and abbreviations n
G Glossary of terms n
E.1.3.1: Notes on on Ed.01
– Draft editions neither validated nor officially released issue, for internal validation purposes:
• Ed.01A–DRAFT created on December 12th, 2003
• Ed.01B–DRAFT created on January 26th, 2004
• Ed.01C–DRAFT created on March 9th, 2004
– Ed.01 created on May 19th, 2004 is the first released and validated version of the handbook.
E.1.3.2: Notes on Ed.02
Ed.02 created on July 23rd, 2004 is the second released and validated version of the handbook.
This issue has been done to align the handbook to the new features of SWP version V.1.0.1; for a summary,
see new Chapter 4–3 SWP R.1.0 V.1.0.1 specific information in section SWP DESCRIPTION AND
VERSIONS.
Changes related to this new version have been introduced throughout the handbook, where necessary.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 277 / 296
296
E.1.3.3: Notes on Ed.03
– Draft editions neither validated nor officially released issue, for internal validation purposes:
• Ed.03A–DRAFT created on November 16th, 2004 (authors G.Ziliani & E.Corradini)

• Ed.03B–DRAFT created on December 3rd, 2004 (author C.Nava)

• Ed.03C–DRAFT created on December 21st, 2004 (authors G.Ziliani & E.Corradini)
– Ed.03 created on December 22nd, 2004 is the third released and validated version of the handbook.
This issue has been done to align the handbook to the new features of SWP version V.1.0.2; for a
summary, see new Chapter 4–4 SWP R.1.0 V.1.0.2 specific information in section SWP
DESCRIPTION AND VERSIONS.
Changes related to this new version have been introduced throughout the handbook, where
necessary.
Other main changes are:
• Cautions to avoid equipment damage in front matter improved
• in addition to changes for V1.0.2, section INSTALLATION has been fully revised and improved
• in addition to changes for V1.0.2, section AWY/FSO NE MANAGEMENT has been fully revised
and improved.
This edition can be used also with previous versions V1.0.0 & V1.0.1.
Revision bars point out major (listed above) and minor (not listed above) modifications with respect
to previous edition.
Revision bars in correspondence of empty lines or empty table rows point out parts eliminated.
Errors found in previous edition have been corrected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 278 / 296
296
E.2 : Documentation set description
This paragraph contains all information regarding the Customer Documentation set this handbook
belongs to:
– 9400AWY Rel.1.0 product–release–version handbooks on page 280
– 9400FSO Rel.1.0 product–release–version handbooks on page 282
– Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0 on page 284
– Specific documentation for SNMP on page 285
– General on Alcatel Customer Documentation on page 285 including:
• Customer–Independent Standard Customer Documentation on page 285
• Product levels and associated Customer Documentation on page 286
• Handbook and CD–ROM supply to Customers on page 288
The list of handbooks given in the following is valid as at the issue date of
this Handbook and can be changed without any obligation for ALCATEL
to update it in this Handbook.
Some of the handbooks listed in the following may not be available as at

the issue date of this Handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 279 / 296
296
E.2.1 : 9400AWY Rel.1.0 product–release–version handbooks
This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for
9400AWY Rel.1.0 product release.

Please refer to following para.E.2.5 on page 285 for a general description of Alcatel Customer
Documentation system.
The standard Customer Documentation in the English language for the 9400AWY Rel.1.0 system is
modularly composed by different handbooks.
Tab. 25. herebelow lists the handbooks.
The [REF] indication in Tab. 25. is relevant to the handbook brief description given in tables Tab. 26. thru’
Tab. 28. and Tab. 33. thru’ Tab. 34. in the following.
Tab. 25. 9400AWY Rel.1.0 product release handbooks

TECHNICAL HANDBOOK REF
9400AWY Technical Handbook [A]
INSTALLATION AND LINE–UP HANDBOOKS
9400AWY Installation Handbook [B]
9400AWY Line–up Guide [C]

OPERATOR’S HANDBOOKS (in alternative, according to SWP used)
9400AWY/FSO CT Operator’s Handbook SWP 1.0 [I]
9400AWY/FSO CT Operator’s Handbook SWP 1.1 [J]

DOCUMENTATION CD–ROM
DCP 9400AWY R.1.0 CD_ROM [D]
1320 CT OPERATOR’S HANDBOOKS
– 1320CT Basic Operator’s Handbook
– AS Operator’s Handbook
– ELB Operator’s Handbook
see Tab. 34. on page 284
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 280 / 296
296
Tab. 26. 9400AWY Rel.1.0 Technical Handbook
ANV P/N
REF HANDBOOK NOTES
Factory P/N
3DB 05653 BAAA

9400 AWY Rel. 1.0 Technical Handbook from ED.03
without Factory P/N
[A]
It provides information regarding AWY equipment description and composition, station
layouts, hardware setting documentation and maintenance.
Tab. 27. 9400AWY Rel.1.0 Installation and Line–Up Handbooks
• The Installation Handbook provides information regarding Equipment installation, according

to Alcatel Installation Engineering Dept. rules.
• The Line–up Guide provides information regarding equipment line up and commissioning,
according to Alcatel Installation Engineering Dept. rules.
ANV P/N
REF HANDBOOK NOTES
Factory P/N
3DB 05653 DAAA

[B] 9400 AWY Rel.1.0 Installation Handbook
without Factory P/N
3DB 05653 EAAA

[C] 9400 AWY Rel.1.0 Line–up Guide
without Factory P/N
Tab. 28. 9400AWY Rel.1.0 Documentation on CD–ROM
ANV P/N
REF CD–ROM TITLE NOTES
Factory P/N
3DB 05653 AAAA

DCP 9400AWY 1.0 CD_ROM
417.200.029
[D] Contains, in electronic format (ACROBAT pdf files), all handbooks listed in Tab. 25. on
page 280 (when all envisaged handbooks are released), with exception of 1320 CT
Operator’s Handbooks
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 281 / 296
296
E.2.2 : 9400FSO Rel.1.0 product–release–version handbooks
This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for
9400FSO Rel.1.0 product release.

Please refer to following para.E.2.5 on page 285 for a general description of Alcatel Customer
Documentation system.
The standard Customer Documentation in the English language for the 9400FSO Rel.1.0 system is
modularly composed by different handbooks.
Tab. 29. herebelow lists the handbooks.
The [REF] indication in Tab. 29. is relevant to the handbook brief description given in tables Tab. 30. thru’
Tab. 34. in the following.
Tab. 29. 9400FSO Rel.1.0 product release handbooks

TECHNICAL HANDBOOK REF
9400FSO Technical Handbook [E]
INSTALLATION AND LINE–UP HANDBOOKS
9400FSO Installation Handbook [F]
9400FSO Line–up Guide [G]

OPERATOR’S HANDBOOKS (in alternative, according to SWP used)
9400AWY/FSO CT Operator’s Handbook SWP 1.0 [I]
9400AWY/FSO CT Operator’s Handbook SWP 1.1 [J]

DOCUMENTATION CD–ROM
DCP 9400FSO R.1.0 CD_ROM [H]
1320 CT OPERATOR’S HANDBOOKS
– 1320CT Basic Operator’s Handbook
– AS Operator’s Handbook
– ELB Operator’s Handbook
see Tab. 34. on page 284
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 282 / 296
296
Tab. 30. 9400FSO Rel.1.0 Technical Handbook
ANV P/N
REF HANDBOOK NOTES
Factory P/N
3DB 05654 BAAA

9400FSO Rel.1.0 Technical Handbook
without Factory P/N
[E]
It provides information regarding FSO equipment description and composition, station
layouts, hardware setting documentation and maintenance.
Tab. 31. 9400FSO Rel.1.0 Installation and Line–Up Handbooks
• The Installation Handbook provides information regarding Equipment installation, according

to Alcatel Installation Engineering Dept. rules.
• The Line–up Guide provides information regarding equipment line up and commissioning,
according to Alcatel Installation Engineering Dept. rules.
ANV P/N
REF HANDBOOK NOTES
Factory P/N
3DB 05654 CAAA

[F] 9400FSO Rel.1.0 Installation Handbook
without Factory P/N
3DB 05654 DAAA

[G] 9400FSO Rel.1.0 Line–up Guide
without Factory P/N
Tab. 32. 9400AWY Rel.1.0 Documentation on CD–ROM
ANV P/N
REF CD–ROM TITLE NOTES
Factory P/N
3DB 05654 AAAA

DCP 9400FSO 1.0 CD_ROM
417.200.030
[H] Contains, in electronic format (ACROBAT pdf files), all handbooks listed in Tab. 29. on
page 282 (when all envisaged handbooks are released), with exception of 1320 CT
Operator’s Handbooks
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 283 / 296
296
E.2.3 : Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0
Tab. 33. Operator’s Handbooks related to the specific Software Package SWP

ANV P/N
REF HANDBOOK NOTES
Factory P/N
9400 AWY/FSO Rel.1.0 3DB 05653 CAAA nb1

[I]
CT Operator’s Handbook SWP 1.0 without Factory P/N this handbook
9400 AWY/FSO Rel.1.0 3DB 05653 FAAA

[J] nb2
CT Operator’s Handbook SWP 1.1 without Factory P/N
Provides AWY/FSO SWP screens and operational procedures for Equipment SW management and
maintenance.
nb1 SWP identification: ref.Tab. 16. on page 229
nb2 SWP identification: t.b.d.
Tab. 34. Documentation common to Alcatel Network Elements using 1320CT platform
Q3CT–P
ANV P/N
REF Version HANDBOOK NOTES
Factory P/N
(N.B.)
1320CT Rel.3.x 3AL 79551 AAAA

3.0.1
Basic Operator’s Handbook 957.140.042 N
[K]
Provides general information and operational procedures common to all 1320CT (Craft
terminal) of Alcatel InfoModel Network Elements.
AS Rel.6.5 3AL 88876 AAAA

3.0.1
Operator’s Handbook without Factory P/N
[L]
Provides detailed information and operational procedures regarding the alarm Surveillance
software embedded in the 1320CT software package.
ELB Rel.2.x 3AL 88877 AAAA

3.0.1
Operator’s Handbook without Factory P/N
[M]
Provides detailed information and operational procedures regarding the Event Log Browser
software embedded in the 1320CT software package.
DCP 1320 CT 3.x 3AL 79552 AAAA

3.0.1
CD_ROM EN 417.100.032
[N]
Contains, in electronic format, the 1320 CT Operator’s Handbook REF.[K] to [N]
N.B. The CT Version is displayed when, on the PC, you select the 1320CT application for its
launch. The Q3CT–P/K Version embedded in the SWP this handbook refers to, is specified
in the paragraph ECT SW Sub–Components of chapter (in Section 4 – SWP
DESCRIPTION AND VERSIONS) related to the SWP version you use.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 284 / 296
296
E.2.4 : Specific documentation for SNMP
The documents relevant to SNMP are not available as individual items, but are directly included in the
SNMP SWP CD–ROMs themselves.
E.2.5 : General on Alcatel Customer Documentation
This paragraph describes in general the Alcatel Customer Documentation system, details the association
between the product levels and the associated documentation, and explains Customer Documentation
characteristics as well as the policies for its delivery and updating.
E.2.5.1: Customer–Independent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as

plant–independent and is always independent of any Customization.
Plant–dependent and/or Customized documentation, if envisaged by the contract, is subjected to

commercial criteria as far as contents, formats and supply conditions are concerned
N.B. Plant–dependent and Customized documentation is not described here.
b) Aims of standard Customer Documentation
Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and
maintaining the equipment according to Alcatel Laboratory design and Installation Dept. choices. In
particular:
• the contents of the handbooks associated to the software applications focus on the explanation
of the man–machine interface and of the operating procedures allowed by it;
• maintenance is described down to faulty PCB location and replacement.
N.B. No supply to Customers of design documentation (like PCB hardware design and
production documents and files, software source programs, programming tools, etc.) is
envisaged.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 285 / 296
296
E.2.5.2: Product levels and associated Customer Documentation
See Fig. 168. on page 287.
a) Products

A ”product” is defined by the network hierarchical level where it can be inserted and by the whole
of performances and services that it is meant for.
E.g. 9400AWY is a product.
b) Product-releases
A ”product” evolves through successive ”product-releases”, which are the real products marketed
for their delivery at a certain ”product-release” availability date. A certain ”product-release” performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive ”product-releases” of the same ”product”.
A ”product–release” comprehends a set of hardware components and at least one “Software
Package” (SWP); as a whole, they identify the possible network applications and the equipment
performances that the specific ”product-release” has been designed, engineered, and marketed for.
c) Configurations and Network Elements

In some cases, a ”product-release” includes different possible “configurations” which are
distinguished from one another by different “Network Element” (NE) types and, from the
management point of view, by different SWPs.
d) SWP Releases and Versions
See Fig. 167. herebelow.

A SWP is identified by the “configuration” name and by the “version” number (tree digits).
The version’s first digit corresponds to the “product–release” number first digit; the second digit
identifies, together with the first, the SWP “release”.
The third digit of the SWP version identifies the Patch Level of the SWP Release.
SWP version
SWP Release
Product Patch Level

Release’s
first digit
SWP evolution for bug fixing purposes 1. 0. 7

or minor additional features
(same SWP Release within same
1. 0. 9
Product–Release)
SWP evolution for additional features 1. 0. 7

(new SWP Release within same Product–Release)
Product Release)
(N.B. see next page) 1. 1. 2
1. 0. 7
SWP evolution for additional features
(new SWP Release of a new Product–Release) 2. 0. 2
Fig. 167. Example of SWP Release and Version numbering

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 286 / 296
296
N.B. Sometimes, different SWP Releases (within the same Product–Release) are commercially
distinguished by different names, e.g. :
SWP version SWP–Release commercial name

1.0.x 1.0
1.1.x 1.0B
1.2.x 1.0C
e) Customer Documentation
A ”product-release–(configuration)” has its own set of standard Customer Documentation, usually

formed of several handbooks, i.e., in general:
• System and Hardware documentation:

– one (or more) Technical Handbook(s)
– an Installation Handbook
– a Commissioning Handbook or Line–Up Guide
• Software documentation:
– a Craft Terminal Operator’s Handbook, associated to the specific SWP–Release
– other Operator’s Handbooks (typically those associated to the SW platform embedded
in the SWP)
PRODUCT
evolution
PRODUCT–RELEASE 1.0 PRODUCT–RELEASE 2.0
ALTERNATIVE CONFIGURATIONS
CONFIG.A CONFIG.B
evolution
PRODUCT SWP REL.1.0 SWP REL.1.1
LEVELS
DOCUMENTATION
CONFIG.A SWP REL.1.0 SWP REL.1.1

System & HW SW SW
Documentation Documentation Documentation
Fig. 168. Example of Product levels and associated Customer Documentation

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 287 / 296
296
E.2.5.3: Handbook and CD–ROM supply to Customers
a) Standard supply
Handbooks and CD–ROMs are standard commercial items and are ordered and delivered as any

other Alcatel commercial item.
Handbooks and CD–ROMs are not automatically delivered together with the equipment they refer
to.
The number of handbooks or CD–ROMs per type to be supplied must be decided at contract level.
b) Product–documentation consistency
Equipment description and lay–out are always general, i.e. they never describe the actual
composition of the equipment supplied to Customer (this task is entrusted to plant–dependent
documentation).
Detailed hardware documentation concerns actually supplied units and is coherent with the
production issue of such units.
Software–associated handbooks are coherent with the supplied SWP release.
Copies of the handbooks regarding a specific product–release previously delivered can be required
specifying P/N and edition.
c) In–advance supply
Whenever handbooks or CD–ROMs are delivered before the relevant equipment delivery, there is
the risk that their contents might not agree with the characteristics of the equipment which will be
delivered: the more they are in advance the less are they likely to agree.
d) Supplying updated handbooks and CD–ROMs to Customers
Supplying updated handbooks or CD–ROMs to Customers who have already received previous
issues is subject to commercial criteria.
By updated handbook delivery, we mean the supply of a complete copy of a new issue of the
handbook (supplying errata–corrige sheets is not envisaged).
e) Copyright notification
The technical information of the handbooks and CD–ROMs supplied to Customers is the property
of ALCATEL and must not be copied, reproduced or disclosed to a third party without written consent.
f) Supply to Customers of Customer Documentation source files
Presently not envisaged.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 288 / 296
296
APPENDIX F : ACRONYMS AND ABBREVIATIONS
N.B. For the explanation of the acronyms of the alarms refer to Section MAINTENANCE
para.3–2.4.1 Alarm synthesis indication on page 221.

ACD: Access Control Domain
ADM: Add/Drop Multiplexer
AIS: Alarm Indication Signal
ALR: Automatic Laser Restart
ALS: Automatic Laser Shutdown
ANSI: American National Standard Institute
APS: Automatic Protection Switching
AS: Alarm Surveillance
ASAP: Alarm Severity Assignment Profile
ATM: Asynchronous Transfer Mode
ATPC: Automatic Transmit Power Control
AVC: Attribute Value Change
BBE: Background Block Error
BER: Bit Error Rate
BIP: Bit Interleaved Parity
BKPV: Back Plane Version
CPI: Control Point Input
CPO: Control Point Output
CRC: Cyclic Redundancy Check
CSES: Consecutive Severely Errored Second
CD: Current Data
CD–ROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee
CPU: Central Processor Unit
CT: Craft Terminal
DEM: DEModulator
DTE: Data Terminal Equipment

1AA 00014 0004 (9007) A4 – ALICE 04.10
DTMF: Dual Tone Multi Frequency
EB: Errored Block
ED 03
3DB 05653 CA AA 289 / 296
296
EC: Equipment Controller
ECC: Embedded Communication Channels
ECT: Equipment Craft Terminal

EFD: Event Forwarding Discriminator
ELB: Event Log Browsing
EML: Element Management Layer
EOW: Engineering Order Wire
EPS: Equipment Protection Switch
ES: Errored Second
ETSI: European Telecommunication Standard Institute
EW: Early Warning
FAD: Functional Access Domain
FD: Frequency Diversity
FEC: Forward Error Corrector
FSO: Free Space Optics
FTP: File Transfer Protocol
GA: General Alarm
GNE: Gateway Network Element
HCS: Higher order Connection Supervision
HBER: High Bit Error Rate
HD: History Data
HET: HETerofrequency
HMI: Human Machine Interface
HS: High Speed
HST: Hot STandby
ID: Identifier
IDU: InDoor Unit
ISO: International Standards Organization
IEEE: Institute of Electrical and Electronics Engineers
IM: Information Manager
IP: Input Port or Internet Protocol

1AA 00014 0004 (9007) A4 – ALICE 04.10
ISO: International Standards Organization
Kbit/s: Kilobits per second
ED 03
3DB 05653 CA AA 290 / 296
296
LAC: Local Access Control
LAN: Local Area Network
LBER: Low Bit Error Rate

LCS: Lower Order Connection Supervision
LO: Local Oscillator
LOF: Loss Of Frame
LOS: Loss Of Signal
LS: Low Speed
MAC: Media Access Control
Mbit/s: Megabits per seconds
MIB: Management Information Base
MLR: Manual Laser Restart
MOC: Managed Object Class
MOD: Modulator
MSp: Manual Switch to protecting channel
MSw: Manual Switch to working channel
NE: Network Element
NML: Network Management Layer
NMS: Network Management System
NSA: Non Service Affecting
NTP: Network Time Protocol
OBPS: On Board Power Supply
OC_F: ODU Controller_FSO
OC_R: ODU Controller_Radio
ODU: OutDoor Unit
OH: OverHead
OP: Output Port
OS: Operation System
OSI: Open Systems Interconnection
OSPF: Open Shortest Path First
PDH: Plesiochronous Digital Hierarchy

1AA 00014 0004 (9007) A4 – ALICE 04.10
PI: Physical Interface
PLL: Phase Locked Loop
ED 03
3DB 05653 CA AA 291 / 296
296
PM: Performance Monitoring
PPP:Point to Point Protocol
PSU: Power Supply Unit

QAM: Quadrature Amplitude Modulation
QOS: Quality Of Service
RAI: Remote Alarm Insertion
RAM: Random Access Memory
RC: Radio Controller
RDI: Remote Defect Indication
RECT: Remote Equipment Craft Terminal
REI: Remote Error Indication
RF: Radio Frequency
RPS: Radio Protection Switching
RS: Reed Solomon
RT: Transceiver
SA: Service Affecting
SC: Service Channel or System Controller
SD: Signal Degrade
SDH: Synchronous Digital Hierarchy
SES: Severly Errored Second
SF: Signal Fail
SSF: Server Signal Fail
SWP: SoftWare Package
TCP: Transmission Control Protocol
TDM: Time Division Multiplexer
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
UAS: UnAvailable Second
UAT: UnAvailable Time
URU: Underlying Resource UnAvailable

1AA 00014 0004 (9007) A4 – ALICE 04.10
USM: User Service Manager
WST: Way Side Traffic
ED 03
3DB 05653 CA AA 292 / 296
296
APPENDIX G : GLOSSARY OF TERMS
Acknowledgment:
When an alarm is taken into account by the application, the operator has to acknowledge it to point out
that he has seen it and that he will react in the right way. During alarm configuration it is possible to set
a maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear
has to be acknowledged.
Administrator:
A user who has access rights to all the Management Domains of the Craft Terminal product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end.
Alarm Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Compact Disk Read Only Memory:

Data saving support from which the information can only be read. Is useful for stocking data due to its
available memory space.
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Digital Communication network:

Communication Network in which the transmission of data is done in a digitized format.
Element Management Layer:

This application is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:

Used to provide protection for cards within an equipment to protect traffic in the event of card failure.
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:

It defines the range of functions which are available to a specified user.
Human Machine Interface:

It is the graphical user interface application through which the operators interact with the system.
History Report:
This function enables operators to get information concerning performances, security or alarms on entities
1AA 00014 0004 (9007) A4 – ALICE 04.10
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
ED 03
3DB 05653 CA AA 293 / 296
296
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITU–T (International Telecommunication
Union).

Kilobits per second:

Unit that correspond to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Megabits per second:

Unit that corresponds to the transmission of 106 bits every second.
Network Access Domain:

Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user
can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.
Network Management Level:

Designates the management functions performed on networks elements assembled in a network.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Operator:
The end–user of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Physical Interface:
Electrical or Electrical/Optical transformers that decouple the line signals and adapt the form of signal for
further transmission. This functional block also manages clock extraction, signal loss monitoring and
loopback functions.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Severity:
1AA 00014 0004 (9007) A4 – ALICE 04.10
Linked to alarms, severities indicate the magnitude related to the failure.
ED 03
3DB 05653 CA AA 294 / 296
296
Telecommunication Management Network:
Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching
supports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
User Profile:
Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the
administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles
installed with Craft Terminal.
User Service Manager:

These are presentation processes used by the Craft Terminal to manage the Human Machine Interface
and facilitate the interaction with the product.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03
3DB 05653 CA AA 295 / 296
296
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
END OF DOCUMENT
296
3DB 05653 CA AA
296 / 296
Craft Terminal Operator’s Handbook
Alcatel 9400AWY & 9400FSO
9400AWY Rel.1.0
11–13–15–18–23–25–28–32–38 GHz
Short–haul low/medium capacity digital microwave radio links
9400FSO Rel.1.0
PDH Low/Medium Capacity Free Space Optic System
SWP 9400AWY R.1.0

(from version V1.0.0)
3DB 05653 CAAA Ed.03

Documentation set for 9400AWY Rel.1.0
Handbook ANV P/N
9400AWY Technical Handbook 3DB 05653 BAAA
9400AWY Installation Handbook 3DB 05653 DAAA
9400AWY Line–up Guide 3DB 05653 EAAA
Documentation set for 9400FSO Rel.1.0
Handbook ANV P/N
9400FSO Technical Handbook 3DB 05654 BAAA
9400FSO Installation Handbook 3DB 05654 CAAA
9400FSO Line–up Guide 3DB 05654 DAAA
Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0
Handbook ANV P/N
9400 AWY/FSO CT Operator’s Handbook SWP 1.0 3DB 05653 CAAA this handbook
9400 AWY/FSO CT Operator’s Handbook SWP 1.1 3DB 05653 FAAA
1320CT Rel.3.x Basic Operator’s Handbook 3AL 79551 AAAA
AS Rel.6.5 Operator’s Handbook 3AL 88876 AAAA
ELB Rel.2.x Operator’s Handbook 3AL 88877 AAAA
When supplied on paper, this handbook is divided by registers, for an easier access to the information
herein contained:
CONTENTS REGISTER
FRONT MATTER:
– TABLE OF CONTENTS
– LIST OF FIGURES AND TABLES
– PRELIMINARY INFORMATION
– SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING
– CAUTIONS TO AVOID EQUIPMENT DAMAGE
– QUICK GUIDE
SECTION 1: INSTALLATION 1
SECTION 2: AWY/FSO NE MANAGEMENT 2
SECTION 3: AWY/FSO MAINTENANCE 3
SECTION 4: SWP DESCRIPTION AND VERSIONS 4
SECTION 5: APPENDICES 5

QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 3DB

05653 CAAA Ed.03
9400AWY & 9400FSO Rel.1.0

SWP REG.9400AWY R.1.0
C.T. OPERATOR’S HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
– No PAGINE TOTALI PER ARCHIVIAZIONE: 298+4 = 302
– DIMENSIONE BINDER SORGENTE (du –ks): 443.620 Mbyte
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:
HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 5 SEPARATORI NUMERATI DA 1 A 5
5 REGISTERS NUMBERED FROM 1 TO 5 ARE NECESSARY
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
i TARGHETTE - LABELS
ii FRONTESPIZIO - FRONT 2
iii FRONT MATTER ⇒ 1/296 20/296
iv INSERIRE SEPARATORE ’1’ - INSERT REGISTER ’1’
v SECTION 1: INSTALLATION ⇒ 21/296 76/296
vi INSERIRE SEPARATORE ’2’ - INSERT REGISTER ’2’
vii SECTION 2: AWY/FSO NE MANAGEMENT ⇒ 77/296 214/296
viii INSERIRE SEPARATORE ’3’ - INSERT REGISTER ’3’
ix SECTION 3: AWY/FSO MAINTENANCE ⇒ 215/296 226/296
x INSERIRE SEPARATORE ’4’ - INSERT REGISTER ’4’
xi SECTION 4: SWP DESCRIPTION AND VERSIONS ⇒ 227/296 240/296
xii INSERIRE SEPARATORE ’5’ - INSERT REGISTER ’5’
xiii SECTION 5: APPENDICES ⇒ 241/296 296/296

1AA 00014 0004 (9007) A4 – ALICE 04.10
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 298
TOTALE FOGLI A4 TOTAL A4 SHEETS: 149
ED 03 RELEASED
3DB 05653 CAAA TQZZA Y 1/ 4
4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
Site
VIMERCATE WTD
Originators 9400AWY REL.1.0

E.CORRADINI
G.ZILIANI 9400FSO REL.1.0
C.NAVA
SWP 9400AWY R1.0 UP V102
Domain : 9400AWY & 9400FSO Rel.1.0

Division : SWP 9400AWY R.1.0
Rubric :
Type : 9400AWY & 9400FSO C.T. OPERATOR’S HDBK
Distribution Codes Internal : External :
Approvals
Name A.FUMAGALLI V.RODELLA A.BESTETTI

App.
Name
App.
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.

• Source files and printable files of this handbook are archived in ePDM:
– Source file: ALICE 6.10 ARCHIVED BY GAPI 3.9.1
– Printable file: PDF file must be opened with ACROBAT Reader Version 5.0 at least.
3DB 05653 CAAA

Ed.03
9400AWY & 9400FSO Rel.1.0
11–38 GHz short–haul low/medium capacity digital microwave radio links

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03 RELEASED
4
9400AWY & 9400FSO Rel.1.0


VOL.1/1
9400AWY & 9400FSO Rel.1.0

VOL.1/1
9400AWY & 9400FSO Rel.1.0

3DB 05653 CAAA Ed.03 C.T. OPERATOR’S HANDBOOK VOL.1/1
9400AWY & 9400FSO Rel.1.0

11–38 GHz short–haul low/medium capacity digital microwave radio links PDH Low/Medium Capacity Free Space Optic System
9400AWY & 9400FSO Rel.1.0

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 03 RELEASED
4
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
03
RELEASED
END OF DOCUMENT
4
3DB 05653 CAAA TQZZA
Y
4/ 4

AWY Operator Handbook

Încărcat de

Informații document

Descriere originală:

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

AWY Operator Handbook

Încărcat de

Drepturi de autor:

Formate disponibile

SWP 9400AWY R1.0 C.T. OPER.

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

HANDBOOK APPLICABILITY, PURPOSE AND HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

CAUTIONS TO AVOID EQUIPMENT DAMAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1–2 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

03 041222 S404102601 A.BESTETTI ITAVE G.ZILIANI RTT

3DB 05653 CA AA 1 / 296

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

2–3 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

2–4 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

2–4.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

3DB 05653 CA AA 2 / 296

2–5.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2–5.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2–6 FSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

2–7 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

2–8 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

2–9 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

2–10 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

2–10.1.2 1+0 Radio Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

3DB 05653 CA AA 3 / 296

2–11 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

2–12 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

2–13 SW DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

SECTION 3: AWY/FSO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

3–2 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

SECTION 4: SWP DESCRIPTION AND VERSIONS . . . . . . . . . . . . . . . . . . . . . . . . 227

4–2 SWP REG.9400AWY R.1.0 V1.0.0 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . 231

4–2.2.4 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

3DB 05653 CA AA 4 / 296

4–3 SWP REG.9400AWY R.1.0 V1.0.1 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . 235

4–3.2 SWP version specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

4–3.2.1 SW Package Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

4–4 SWP REG.9400AWY R.1.0 V1.0.2 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL . . . . . . . . . . . . 251

APPENDIX C : GENERAL ON SWP INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

APPENDIX D : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

D.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

3DB 05653 CA AA 5 / 296

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

APPENDIX E : DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

APPENDIX F : ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

APPENDIX G : GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

3DB 05653 CA AA 6 / 296

Fig. 1. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Fig. 2. Windows NT installation step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3DB 05653 CA AA 7 / 296

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

Fig. 102. FSO laser configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

3DB 05653 CA AA 8 / 296

Fig. 109. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Fig. 110. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Fig. 156. (1+1) ODU (only electrical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

3DB 05653 CA AA 9 / 296

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this