Alcatel 9400AWY Rel.2.0 (Handbook) PDF

1AA 00014 0004 (9007) A4 ALICE 04.
10
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
SWP 9400AWY R2.0 C.T. OPERATORS HDBK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
HANDBOOK STRUCTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . .
14
CAUTIONS TO AVOID EQUIPMENT DAMAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
SECTION 1: INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
11 SWP INSTALLATION IN PC ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.2 Operator skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Reference Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Summary of SW installation / deinstallation phases . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 SWP loading in PC WINDOWSNT/2000/XP (Professional Edition only)
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4.1 Installation of 1320CT + NE software from SWP CDROM . . . . . . . . . . . . . . . . . . . . .
11.4.2 Installation of SIBDL program from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4.3 End of SW installation from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 CT initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5.1 Craft Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5.2 Craft Terminal connection to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 Deinstallation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
21
21
21
21
22
22
52
52
53
53
54
55
12 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1 NE hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2 Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3 Operator skills and profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
57
57
57
57
02
051109
01
050510
ED
DATE
0000023753
A.BESTETTI ITAVE
V.FOSSATI
A.BESTETTI ITAVE
V.FOSSATI
E.CORRADINI ITAVE
G.ZILIANI RTT
E.CORRADINI ITAVE
G.ZILIANI RTT
CHANGE NOTE
APPRAISAL AUTHORITY
ORIGINATOR
9400AWY REL.2.0
OPERATORS HANDBOOK
ED
02
3DB 06687 CA AA
304
1 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Summary of the SWP installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SW download to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NE Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration data definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
58
70
71
71
13 ECT & NE UPGRADE TO A NEW SWP VERSION (SAME SWP RELEASE) . . . . . . . . . .
72
14 FLASH CARD UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Ordering the new Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 Installation of the new Flash Card fully configured in factory . . . . . . . . . . . . . . . . . . .
14.3 Installation of a new Flash Card not configured in factory . . . . . . . . . . . . . . . . . . . . . .
73
73
73
74
SECTION 2: NE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
21 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.1 9400 AWY view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.1 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.2 Resource Tree Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.3 Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.4 Button Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2 Introduction to the menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.1 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.2 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.3 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.4 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.5 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
77
79
80
81
81
82
83
85
85
86
86
22 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.2 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.3 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.4 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.5 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4.1 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4.2 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.5 Quick Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
87
88
89
90
92
93
100
101
103
106
106
109
110
23 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1.2 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1.3 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
129
129
130
132
133
134
134
135
135
24 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
137
ED
02
3DB 06687 CA AA
304
2 / 304

12.2
12.3
12.4
12.5
12.6
1AA 00014 0004 (9007) A4 ALICE 04.10

24.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.1.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
138
138
138
25 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.2.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.3 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.3.1 Frequency menu in Rel. 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.3.2 Frequency menu in Rel. 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.4 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.4.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.4.2 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.5 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.5.1 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
147
148
148
148
148
148
149
149
150
152
153
154
155
158
26 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.2 Output External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
161
162
27 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . .
27.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . .
27.2 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.3 MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.3.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.3.3 Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.3.4 Remove file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27.4 SW key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
165
165
165
166
166
167
168
169
169
170
170
28 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.1 Mux/Demux Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.1.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.1.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.2.1 Rx Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.2.3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3 HST Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
171
172
173
173
175
176
177
177
179
179
180
29 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1.1 1+0 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1.2 1+1 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.2 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.3 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
184
184
187
190
191
210 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
ED
02
3DB 06687 CA AA
304
3 / 304
Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Current Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
193
194
194
198
211 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

211.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . . .
211.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.5 Threshold tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.5.1 How to change a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.5.2 How to create a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.5.3 Threshold table association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
199
201
203
204
204
205
205
206
206
207
207
212 SW DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.1 Server Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.2 Init SW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.3 SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
209
209
210
211
213 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

213.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213.2 MIB management at Network Element Synthesis level and examples . . . . . . . . . . .
213.2.1 MIB backup on ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213.2.2 MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213.2.3 MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213.2.4 MIB restore from ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
213
214
214
214
216
218
1AA 00014 0004 (9007) A4 ALICE 04.10
SECTION 3: NE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

31 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.1 Maintenance of the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.2 Problems with THE Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
220
220
32 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.1 Purpose of this procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.2 Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.4 Troubleshooting by means of the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.4.1 Alarm synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.4.2 Details on alarms / statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5 Warnings on the troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.1 Analog measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.2 NMS 64 kbit/s V.11 and G.703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.4 Empty USM icon in NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.5 NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.6 Configuration change from 4 QAM to 16 QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.7 Quick configuration menu correct use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6 Description of alarms and of probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
221
221
221
222
224
225
226
228
228
228
228
228
229
229
229
230
ED
02
3DB 06687 CA AA
304
4 / 304

210.1
210.2
210.3
210.4
210.5

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

41 SWP 9400AWY R.2.0 DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.3 OEM Software licence list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
235
235
235
236
42 SWP REG.9400AWY R.2.0 V2.0.0 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . .

42.1 ECT requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.3 SWP version specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.3.1 SW Package Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.3.2 SW Package Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.3.3 ECT SW SubComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.3.4 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.4 New features and modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42.5 Restrictions and known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
237
237
237
238
238
238
238
238
239
239
43 SWP REG.9400AWY R.2.0 V2.0.1 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . .

43.1 ECT requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3 Equipment hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.4 SWP version specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.4.1 SW Package Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.4.2 SW Package Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.4.3 ECT SW SubComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.4.4 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.5 New features and modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.6 Restrictions and known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
241
241
241
241
242
242
242
243
243
244
248
1AA 00014 0004 (9007) A4 ALICE 04.10
SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . .
A.1 : Functions and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 : IDU and ODU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1 : IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.2 : ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.3 : Allowed Equipment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.4 : Remote Inventory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3 : Equipment Protection Switching Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.4 : External Points Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
252
253
254
254
255
257
257
258
APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL . . . . . . . . . . . .

B.1 : Allocation of equipment and craft terminal software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 : Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.1 : Flash Card types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.2 : Flash Card identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.3 : Flash Card content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 : Equipment control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.1 : Interfaces (see Fig. 163. on page 251): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.2 : OperatorEquipment Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.3 : ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.4 : RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
259
260
262
262
262
267
269
269
269
270
270
APPENDIX C : GENERAL ON SWP INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
271
ED
02
3DB 06687 CA AA
304
5 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
273
273
APPENDIX D : ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.2 : Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3 : Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.4 : Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . . . .
D.4.2 : TD32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.5 : PC laptop Dell Latitude setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.6 : Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.7 : Changing the ECTequipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.7.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.7.2 : Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
275
275
276
277
278
278
280
281
282
283
283
284
APPENDIX E : DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E.1 : Handbook guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.1.1 : Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.1.2 : Purpose of the handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.1.3 : Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.2 : Documentation set description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.2.1 : 9400AWY Rel.2.0 productreleaseversion handbooks . . . . . . . . . . . . . . . . . . . . . . . . .
E.2.2 : Additional documentation for 1320CT platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.3 : General on Alcatel Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.3.1 : CustomerIndependent Standard Customer Documentation . . . . . . . . . . . . . . . . . . . . .
E.3.2 : Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . .
E.3.3 : Handbook and CDROM supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
285
285
286
287
288
290
290
292
293
293
294
296
APPENDIX F : ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
297
APPENDIX G : GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
ED
02
3DB 06687 CA AA
304
6 / 304

C.1 : Common situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2 : Troubleshooting situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

LIST OF FIGURES AND TABLES

FIGURES
Fig. 1. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 4. Windows NT configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 10. Windows 2000 installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 15. Windows 2000 configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 18. Windows XP installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 23. Windows XP configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 27. Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 28. 9400 AWY Main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 29. View Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 30. Resource tree area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 31. Tab panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 32. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 33. Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 34. Local Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 35. NTP Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 36. Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 37. Ethernet Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 38. IP configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 39. IP static routing configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 40. Create Static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 41. Point To Point Interface Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 42. OSPF Area configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 43. Create New OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 44. IP Address configuration of PointToPoint Interfaces screen . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 45. Routing information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 46. Alarm Severities Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 47. Name of a cloned alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 48. Clone of an Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 49. Selection of a new severity in the Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 50. Selection of a new severity in the No Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
27
28
28
29
30
30
31
32
32
33
34
35
36
37
38
39
40
42
43
44
45
46
47
48
49
50
55
78
79
80
84
87
88
89
90
91
92
93
94
95
96
97
98
99
100
102
103
103
104
105
02
3DB 06687 CA AA
304
7 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
106
107
108
109
111
112
113
114
115
116
118
119
120
121
122
123
124
125
128
128
129
130
131
132
133
134
135
135
137
138
138
141
141
143
144
145
147
148
149
150
151
152
155
156
157
158
158
159
161
162
163
164
165
166
02
3DB 06687 CA AA
304
8 / 304

Fig. 51. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 52. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 53. USM closing warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 54. Overhead Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 55. Quick Installation Procedure: NE Configuration (Step 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 56. Quick Installation Procedure: Frame Configuration (Step 2) . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 57. Quick Installation Procedure: Tributaries Configuration (Step 3) . . . . . . . . . . . . . . . . . . . . . .
Fig. 58. Quick Installation Procedure: Tributaries Configuration (Step 4) . . . . . . . . . . . . . . . . . . . . . .
Fig. 59. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.0) . . . . . . . . .
Fig. 60. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.1) . . . . . . . . .
Fig. 61. Quick Configuration Procedure: Local IP Address (Step 6) . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 62. Quick Installation Procedure: OSPF Area Configuration (Step 7) . . . . . . . . . . . . . . . . . . . . .
Fig. 63. Quick Installation Procedure: IP Static Router Configuration (Step 8) . . . . . . . . . . . . . . . . .
Fig. 64. Quick Configuration Procedure: NMSRF Interface Configuration (Step 9) . . . . . . . . . . . . .
Fig. 65. Quick Configuration Procedure: NMSV11 Interface Configuration (Step 10) . . . . . . . . . . .
Fig. 66. Quick Configuration Procedure: NMSG703 Interface Configuration (Step 11) . . . . . . . . .
Fig. 67. Quick Installation Procedure: Ethernet Configuration (Step 12) . . . . . . . . . . . . . . . . . . . . . . .
Fig. 68. Quick Configuration Procedure: Summary (Step 13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 69. 1+0 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 70. 1+1 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 71. 1+0 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 72. 1+1 IDU/MAIN Ch#1 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 73. 1+1 IDU Ch#0 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 74. Main board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 75. ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 76. Alarm tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 77. Configuration tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 78. Remote Inventory tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 79. Line Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 80. Line Interface View: E1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 81. Line Interface View: E3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 82. Line Interface View: DS1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 83. Line Interface View: DS3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 84. Line Interface View: NMS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 85. Line Interface View: Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 86. Line Interface View: Ethernet Port autonegotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 87. Radio Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 88. Radio Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 89. Radio Frequency menu in Rel. 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 90. Radio Frequency menu in Rel. 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 91. Not standard frequency arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 92. Rtpc & Atpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 93. Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 94. Power Measurement Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 95. Power Meas Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 96. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 97. Example of Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 98. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . . . .
Fig. 99. Input External Point View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 100. Output External Points: CP01 ... CP04 (Manual activation) . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 101. Output External Points: CP01 ... CP04 (Automatic activation) . . . . . . . . . . . . . . . . . . . . . . .
Fig. 102. Output External Points View: FAIL IDU, FAIL ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 103. Configuration of the Craft access state from the Equipment NE view in the OS mode . .
Fig. 104. Restart NE call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

Fig. 105. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 106. MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 107. Backup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 108. Restore screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 109. Activate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 110. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 111. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 112. Mux Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 113. Mux Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 114. Mux Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 115. Radio Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 116. Rx Static Delay menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 117. Radio Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 118. Radio Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 119. Transmission Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 120. Tx Protection Commands (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 121. Tx Protection Commands (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 122. 1+0 available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 123. Channel 1 Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 124. Tributaries Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 125. 1+0 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 126. 1+1 available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 127. Channel 1 Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 128. Tributaries Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 129. 1+1 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 130. Loopback activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 131. Loopback removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 132. Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 133. Summary Block Diagram View: 1+0 without Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 134. Summary Block Diagram View: 1+0 with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 135. Summary Block Diagram View: 1+1 HST without Ethernet ports . . . . . . . . . . . . . . . . . . . . .
Fig. 136. Summary Block Diagram View: 1+1 HST with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . .
Fig. 137. Summary Block Diagram View: 1+1 FD without Ethernet ports . . . . . . . . . . . . . . . . . . . . . .
Fig. 138. Summary Block Diagram View: 1+1 FD with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 139. Radio sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 140. Anomalies, defects, errored blocks, ES and SES according to ITUT G.826 . . . . . . . . . .
Fig. 141. Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 142. Threshold table association screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 143. Current Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 144. History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 145. Threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 146. Thresholds Table creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 147. Server access configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 148. Init Software Download screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 149. SW Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 150. SW Unit Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 151. Allowed MIB management tasks at NE loggedin level . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 152. Allowed MIB management tasks at Network Element Synthesis level . . . . . . . . . . . . . . .
Fig. 153. Launch of MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 154. MIB save to disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 155. MIB save to disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 156. Correspondence between MIB saved folder and MIB saved name . . . . . . . . . . . . . . . . . . .
Fig. 157. Launch of MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 158. MIB load from disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
166
167
168
169
169
170
171
172
173
174
175
176
177
178
179
180
181
184
185
185
186
187
188
188
189
190
191
193
195
195
196
196
197
197
199
200
201
202
203
205
206
207
209
210
211
212
213
213
214
214
215
215
216
217
02
3DB 06687 CA AA
304
9 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
218
221
226
253
259
259
259
260
267
271
275
277
277
280
284
294
295
TABLES
Tab. 1. Additional feature and SWPversion relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 2. Radio application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 3. ATPC Range Rx Threshold for ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 4. ATPC Range Rx Threshold for ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 5. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 8. 1+0 loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 9. 1+1 loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 10. SES Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 11. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 12. Alarm information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 13. General issues of the alarm meanings and their respective maintenance actions . . . . . . .
Tab. 14. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 15. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 16. Markets, tributaries and modulations forecasted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 17. Shelves Equipment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 18. Allowed board/plugin types in IDU Main shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 19. Allowed board/plugin types in IDU Extension shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 20. Characteristics of the protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 21. Available Flash cards for 9400AWY Rel.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 22. Capacity and modulation for 9400AWY R.2.0 flash cards (IDU basic) . . . . . . . . . . . . . . . . .
Tab. 23. Capacity and modulation for 9400AWY R.2.0 flash cards (with 916 E1/DS1 plugin) . .
Tab. 24. Capacity and modulation for 9400AWY R.2.0 flash cards (with E3/DS3 plugin) . . . . . . .
Tab. 25. Capacity and modulation for 9400AWY R.2.0 flash cards (with Ethernet plugin) . . . . . . .
Tab. 26. Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 27. 9400AWY Rel.2.0 product release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 28. 9400AWY Rel. 2.0 Technical Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 29. 9400AWY Rel. 2.0 Installation and LineUp Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 30. Operators Handbooks related to the specific Software Package SWP . . . . . . . . . . . . . . . .
Tab. 32. 9400AWY Rel.2.0 Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 33. Documentation common to Alcatel Network Elements using 1320CT platform . . . . . . . . .
12
107
153
154
174
178
181
184
187
199
225
227
231
235
236
252
255
256
256
257
262
263
264
265
266
288
290
291
291
291
292
292
ED
02
3DB 06687 CA AA
304
10 / 304

Fig. 159. MIB load from disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 160. Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 161. Active alarm screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 162. 9400AWY R.2.0 splitmount system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 163. MAIN Unit front side: interfaces for equipment control and FlashCardlabel position . .
Fig. 164. MAIN Unit back side: Flash Card position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 165. Flash Card profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 166. Equipment main parts containing local SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 167. Flash Card content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 168. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 169. ECTEquipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . .
Fig. 170. ECTLocal external Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 171. F InterfaceRemote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 172. TD32 AC modem dipswitch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 173. Alcatel Lower Layers utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 174. Example of SWP Release and Version numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 175. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . .
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
ED
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 291 and [D] on page 291. The warning labels that can be found on the equipment parts
are indicated on page 14.
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.
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 290 is usually
not enough to properly install, operate and maintain equipment.
02
3DB 06687 CA AA
304
11 / 304
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY
Tab. 1. Additional feature and SWPversion relationship

This handbook describes SWP 9400AWY Rel.2.0, taking into account all system features that are made
available by first SWP version V2.0.0, as well as by successive SWP releasesversions. Following
Tab. 1. sumsup the major additional features (mainly related to new HW items and relevant
performance) that are available starting from a certain SWPversion successive to first SWP version
V2.0.0.
Available from
SWPversion
Additional feature
New ETSI IDU Main and Extension units, with different 3DB xxxxx AB P/N
(refer to para.12.1.1 point [2] on page 57)
mandatory from
V2.0.1
78 GHz ODUs (new 9470AWY product)

V2.0.2
to be confirmed
Frequency shifter management

Security management
ANSI version (DS1/DS3) interfaces and relevant ANSI IDU Main and Extension
units and PlugIns
ANSI version ODUs
V2.0.3
to be confirmed
1AA 00014 0004 (9007) A4 ALICE 04.10
Ed.02 of this handbook is validated in conjunction with SWP versions V2.0.0 to V2.0.1
only. Information relevant to SWP versions > V2.0.1 must be considered preliminary,
subject to change and without any obligation on the part of ALCATEL.
ED
02
3DB 06687 CA AA
304
12 / 304

Please refer to para.E.1 on page 285.
HANDBOOK STRUCTURE
1AA 00014 0004 (9007) A4 ALICE 04.10

Information in this handbook is divided into the following parts:

a)
FRONT MATTER
TABLE OF CONTENTS
HANDBOOK STRUCTURE
SAFETY, EMC, EMF, 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 19

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

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

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

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 SubComponent, NE MIB Compatibility and additional features of new SWP versions.
f)
SECTION 5: APPENDICES on page 249

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
ECTEquipment connection via public switched telephone network
Documentation Guide
Acronyms and abbreviations
Glossary of terms
ED
02
3DB 06687 CA AA
304
13 / 304

Please refer to Technical Handbook (from ED.02) to obtain details regarding following information:
Compliance with European norms
Safety rules:
TOPIC

a)
WARNING LABEL ON EQUIPMENT
General rules
Dangerous Electrical Voltages
Equipment connection to earth
Risk of explosion
Moving mechanical parts
Heatradiating mechanical parts
Equipment emitting RF power
Other labels:
TOPIC
WARNING LABEL ON EQUIPMENT
Device sensitive to electrostatic discharges
1AA 00014 0004 (9007) A4 ALICE 04.10
2002/96/EC WEEE (Waste Electrical and

Electronic Equipment) Logo
b)
ED
Electromagnetic Compatibility (EMC norms)
Other Labels affixed to the Equipment
Identical or similar information on Personal Computer, WorkStation etc., other than ALCATELs,
loaded with software applications described in this Handbook, is supplied in the Constructors
technical documentation.
02
3DB 06687 CA AA
304
14 / 304

a)
Unit assemblies
Each of the IDU MAIN UNIT and IDU EXTENSION UNIT is assembled inside its own box and 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 .
b)
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
c)
Screw fixing
In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) must be always
tightened to avoid item detachment and to ensure the equipment EMIEMC performance.
The screw tightening torque 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.
d)
IDUODU cable disconnection / connection

Before to disconnect or connect the IDUODU cable (at IDU or ODU side) switch off the
corresponding MAIN IDU UNIT or EXTENSION IDU UNIT.
e)
Craft Terminal connection

To connect the CT cable (at IDUs 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 IDUs F interface and PC side
now the PC can be safely switched on.
1AA 00014 0004 (9007) A4 ALICE 04.10
f)
Craft Terminal disconnection

To disconnect the CT cable (at IDUs 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.
ED
02
3DB 06687 CA AA
304
15 / 304
QUICK GUIDE
C.T. OPERATORS HANDBOOK SWP 9400AWY R.2.0

If you need immediate operative information on how to:
GENERAL TOPICS
get information on system
documentation
read Appendix E on page 285
get information on safety, EMC,

EMF, ESD norms and equipment
labelling
read page 14
read:
Chapter 41 on page 235
have the description of the system
from the software point of view
Appendix A on page 251

Appendix B on page 259
logically configure a station (or

change its configuration) and
logically setup connections
logically provision equipment boards
get item P/Ns
get operative information regarding
the units in IDU shelf and ODU
(connectors, leds, buttons)
get:
9400AWY Rel.2.0 Technical Handbook
(Ref. [A] on page 291)
and read its QUICK GUIDE (same topics)
HW INSTALLATION
get:
physically install and cable the
equipment hardware
9400AWY Rel.2.0 Installation Handbook

(Ref. [B] on page 291)
and proceed as specified by it
1AA 00014 0004 (9007) A4 ALICE 04.10
continues ..
ED
02
3DB 06687 CA AA
304
16 / 304

.. continues
SWP INSTALLATION AND COMMISSIONING
install SWP (first time) on ECT
proceed as specified in chapter 11 on page 21
download SWP (first time) into the

equipment

get:
commission equipment
9400AWY Rel.2.0 Lineup Guide

(Ref. [C] on page 291)
and proceed as specified by it
upgrade Flash Card
upgrade ECT and equipment with a

newer SWP version
(same SWP release)
ECT SOFTWARE USAGE FOR EQUIPMENT SW MANAGEMENT

have an overview on menu tree
structure
manage equipment configuration
setup parameters for maintenance
(configure housekeeping alarms;
configure the Alarms Management,
access the Alarm Surveillance and
show the alarm condition).
open SECTION 2 NE MANAGEMENT on page 75 of this

handbook and then search the information according to the
listed topics
access the Events Log file

use of the Performance Monitoring
functionalities
1AA 00014 0004 (9007) A4 ALICE 04.10
continues ..
ED
02
3DB 06687 CA AA
304
17 / 304
MAINTENANCE
provision and manage spare parts
carry out preventive maintenance
get 9400AWY Technical Handbook (Ref. [A] on page 291)

and read its QUICK GUIDE (same topic)
get 9400AWY Technical Handbook (Ref. [A] on page 291),

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 NE MAINTENANCE on page 219
of this handbook.
carry out corrective maintenance
Alternatively, access directly SECTION 3 NE
MAINTENANCE on page 219 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
To find any other kind of information not listed in the above table, please refer to the TABLE OF
CONTENTS of this handbook.
ED
02
3DB 06687 CA AA
304
18 / 304

.. continues

SECTION 1: INSTALLATION
SECTION CONTENT
PAGE
Chapter 11 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.
21
Chapter 12 SWP download toward NE

This chapter details all phases necessary to install for the first time a SWP in the
equipment environment.
57
Chapter 13 CT & NE Upgrade to a new 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.
N.B.
Procedure not meaningful for first version (V2.0.0) of the SWP.
72
Chapter 14 Flash Card upgrade

This chapter details all phases necessary to install a new Flash Card
73
The symbol
points out references to the other Handbooks.
1AA 00014 0004 (9007) A4 ALICE 04.10
Referenced handbook P/Ns are given in para.E.2 on page 290.
ED
02
3DB 06687 CA AA
304
19 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
20 / 304

11 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 260
and Appendix C on page 271.
Procedures described in this chapter are carried out with the PC disconnected from the NE.
11.1 Requirements
11.1.1 PC characteristics
For version
refer to paragraph
on page
V 2.0.0 to V2.0.1
42.1
237
11.1.2 Operator skills

The operator shall be familiar with the use of personal computers in WINDOWSNT / WINDOWS 2000
/ WINDOWS XP (Professional Edition only) environment, internally to which the Network Elements
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) (ITUT Recommendations).
11.2 Reference Information Model

For version
refer to paragraph
on page
V 2.0.0
42.2
237
V 2.0.1
43.2
241
11.3 Summary of SW installation / deinstallation phases

The sequence of installation phases for the SWP loading in PC WINDOWSNT/XP (Professional Edition
only)/2000 environment (PC is disconnected from Equipment Controller) are as follows:
a)
Installation from SWP CDROM

1)
2)
3)
b)
installation of 1320CT + NE software from SWP CDROM

installation of SIBDL program from SWP CDROM
end of SW installation from SWP CDROM
CT initial configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
that are described in detail in following paragraphs.

Para.11.6 on page 55 describes how to to deinstall the Software Package from the PC.
ED
02
3DB 06687 CA AA
304
21 / 304
Procedures described in the following are carried out with the PC disconnected from the NE.
11.4.1 Installation of 1320CT + NE software from SWP CDROM

This operation must be perfomed by the 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. 11.4.1.1 CT Products installation guided.
2)
Second configure the Alcatel Virtual Network Card by using the procedure described in the para.
11.4.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. 11.4.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. 11.4.1.1 CT Products installation guided.
2)
To update the other components use the automatic installation mode, described in the para.
11.4.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. 11.4.1.3 CT Products automatic installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
ED
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).
02
3DB 06687 CA AA
304
22 / 304

11.4 SWP loading in PC WINDOWSNT/2000/XP (Professional Edition only)

environment

11.4.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
ED
if try to update JRE and JRE V 1.4.1 is already installed, the procedure automatically
deinstall, it WITHOUT making the new installation. Keep attention in this case to the
Question Window that appears, which ask you to proceed to the deinstallation.
02
3DB 06687 CA AA
304
23 / 304

1AA 00014 0004 (9007) A4 ALICE 04.10
Step 3. Press NEXT button to execute the installation of the previously selected components.
Step 4. Press NEXT button to start the installation of the Lower Layers Manager.
ED
02
3DB 06687 CA AA
304
24 / 304

1AA 00014 0004 (9007) A4 ALICE 04.10
Step 5. Select Configure Lower Layer and press FINISH button to complete the operation.
Step 6. Complete the configuration and press OK button.

N.B.
ED
If a network adapter is not running in the PC, you can set the System identifierfield with a
sequence of 12 0. The following window will be displayed.
02
3DB 06687 CA AA
304
25 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Step 9. Press YES button to confirm.
02
3DB 06687 CA AA
304
26 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

11.4.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. 11.4.1.2.1 on page 27 for installation on Windows NT 4.0; refer to para. 11.4.1.2.2 on
page 33 for installation on Windows 2000; refer to para. 11.4.1.2.3 on page 41 for installation on Windows
XP.
11.4.1.2.1 Windows NT 4.0
11.4.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.
Fig. 1. Windows NT installation step 1
ED
02
3DB 06687 CA AA
304
27 / 304
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.
1AA 00014 0004 (9007) A4 ALICE 04.10

Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP
parameters before use it in with Alcatel Lower Layers Manager.
ED
02
3DB 06687 CA AA
304
28 / 304

11.4.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).
This operation must be performs at Administrator of the PC, because it subsequently could be to
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 instructions until the dialog box (Fig. 7. NT configuration step 4) will appear.
2
3
4
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 4. Windows NT configuration step 1
ED
02
3DB 06687 CA AA
304
29 / 304
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
02
3DB 06687 CA AA
304
30 / 304
Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for Lower
Layers and push OK.

3
4
*** 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 recustomization by executing the
following command:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Start Programs Alcatel SNMPCTKADDON v... SNMP AddOn Customization
02
3DB 06687 CA AA
304
31 / 304
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
02
3DB 06687 CA AA
304
32 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

11.4.1.2.2 Windows 2000

The System Standby function in the Power Option menu of the Control Panel must be always
disabled (select in the Power Schemes tab panel in the Power schemes field Always On).
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.
Fig. 10. Windows 2000 installation step 1
ED
02
3DB 06687 CA AA
304
33 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
34 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
Click the Have Disk... button in the Select Network Adapter dialog box.
02
3DB 06687 CA AA
304
35 / 304
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
Prompt window to discover the right location of the WinNT folder) and click OK.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
36 / 304
Click Next in the Start Hardware Installation dialog box.
1AA 00014 0004 (9007) A4 ALICE 04.10


ED
02
3DB 06687 CA AA
304
37 / 304
This operation must be performs at Administrator of the PC, because it subsequently could be to
set IP address .
To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dialup 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 Dialup connections applet.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 15. Windows 2000 configuration step 1
ED
02
3DB 06687 CA AA
304
38 / 304

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

1
2
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
39 / 304
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
02
3DB 06687 CA AA
304
40 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

11.4.1.2.3 Windows XP (Professional Edition only)

The System Standby function in the Power Option menu of the Control Panel must be always
disabled (select in the Power Schemes tab panel in the Power schemes field Always On).
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.
ED
Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
02
3DB 06687 CA AA
304
41 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 18. Windows XP installation step 1
ED
02
3DB 06687 CA AA
304
42 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
43 / 304

1AA 00014 0004 (9007) A4 ALICE 04.10

ED
Click the Have Disk... button in the Select Network Adapter dialog box.
02
3DB 06687 CA AA
304
44 / 304
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
Prompt window to discover the right location of the WinNT folder) and click OK.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
45 / 304
Click Next in the The wizard is ready to install your hardware dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED
02
3DB 06687 CA AA
304
46 / 304

This operation must be perfomed by the Administrator of the PC, because it subsequently could
be to 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 Dialup connections applet.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 23. Windows XP configuration step 1
ED
02
3DB 06687 CA AA
304
47 / 304
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
3
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
48 / 304
Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK
(4).

1
2
3
4
*** WARNING ***

following command:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
49 / 304
Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOS
over TCP/IP (2) and then push OK (3).
1AA 00014 0004 (9007) A4 ALICE 04.10
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers
Manager to use it.
ED
02
3DB 06687 CA AA
304
50 / 304

11.4.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Step 2. Select all components except JRE and Alcatel Lower Layer Manager.
Step 3. Press NEXT button to execute the installation of the previously selected components.
ED
02
3DB 06687 CA AA
304
51 / 304
Refer to chapter B.1 for general information on SIBDL program (in particular point 2 ) in para.B.3.2 on
page 270 and point 2 ) in para.C.2 on page 273).
The SIBDL program is not automatically installed by the autoinstallation process.
The installation of SIBDL is detailed in the dedicated Section of the:
9400AWY 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 CDROM).
11.4.3 End of SW installation from SWP CDROM
1AA 00014 0004 (9007) A4 ALICE 04.10
Having reached this phase, you have finished the Software transfer from SWP CDROM to the PC
environment. Now, you can extract the SWP CDROM from the PCs CDROM unit.
ED
02
3DB 06687 CA AA
304
52 / 304

11.4.2 Installation of SIBDL program from SWP CDROM
11.5 CT initial configuration

Procedures described in the following are carried out with the PC disconnected from the NE.
11.5.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 setup these configurations, refer to:
1AA 00014 0004 (9007) A4 ALICE 04.10
1320CT Basic Craft Terminal Operators Handbook ,

section INSTALLATION, chapter Craft Terminal Configuration
ED
02
3DB 06687 CA AA
304
53 / 304
11.5.2 Craft Terminal connection to the NE
Only one connection can be active. The default connection is the Serial port.
11.5.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)
N.B.
The Alcatel Virtual Network Card for Lower Layers Software has to be installed on the PC (refer
to para. 11.4.1.2 on page 27).
If the IP Address configured for the Alcatel Virtual Card has been changed after the 1320CT
Platform installation, it is necessary to perform a recustomization by entering the following
command:
Start Programs Alcatel SNMPCTKADDON v.3.1.x SNMP AddOn 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 SNMPCTKADDON v.3.1.x NE Connection Serial Port
11.5.2.2 Connection through the Ethernet Network Port

1)
Configure the Network Card on the CT as explained in the 1320CT Basic Craft Terminal
Operators Handbook.
2)
Enter the NE and enable the Ethernet port on the NE (refer to para. 22.2.3 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:
StartProgramsAlcatelSNMPCTKADDON v.3.1.xNE ConnectionEthernet Port
N.B.
If the IP Address configured on the Ethernet port has been changed, it is necessary to perform
a recustomization by entering the following commands:
Start Programs Alcatel CTK v.3.1.x Customization
1AA 00014 0004 (9007) A4 ALICE 04.10
Start Programs Alcatel SNMPCTKADDON v.3.1.x NE ConnectionEthernet Port

Start Programs Alcatel SNMPCTKADDON v.3.1.x SNMP AddOn Customization
ED
02
3DB 06687 CA AA
304
54 / 304

The CT can be connected to the NE through the Serial Port or through the Ethernet Network Port.
1AA 00014 0004 (9007) A4 ALICE 04.10

11.6 Deinstallation phases

This paragraph describes how to deinstall 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 deinstall the following procedure can be followed:
with the CDROM containing the relevant Software product.
with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CDROM containing the
relevant Software product is not present.
From Control Panel select Add/Remove Programmes and deinstall the components shown in the
following figure.
Fig. 27. Deinstallation
ED
02
3DB 06687 CA AA
304
55 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
56 / 304
12 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 260
and Appendix C on page 271.
Procedures described in this chapter are carried out with the PC connected to the NE.
12.1 Requirements
12.1.1 NE hardware
[1]
Equipment HW installation
The equipment must have been already physically installed, cabled and powered on, according to
the instructions given in the:
9400AWY Installation Handbook
[2]
Equipment HW constraints from V2.0.1

As far as the ETSI IDU MAIN AND EXTENSION UNITS are concerned:
the use of the units with the new P/N (3DB xxxxx AB) is mandatory when the used SWP
version is 2.0.1
the use of the units with the old P/N (3DB xxxxx AA) is possible only when the used SWP
version is = 2.0.0
For details, please refer to Chapter IDU PART LIST in Technical Handbook (from Ed.02)
12.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 11 on page 21.
12.1.3 Operator skills and profile
1AA 00014 0004 (9007) A4 ALICE 04.10
In addition to skills stated in para.11.1.2 on page 21, the Operator must be familiar with all the equipment
functionalities.
ED
02
3DB 06687 CA AA
304
57 / 304
12.2 Summary of the SWP installation phases
a)
SW download to the NE, para.12.3 herebelow
b)
NE Login, para.12.4 on page 70
c)
Commissioning, para.12.5 on page 71
d)
Configuration data definition, para.12.6 on page 71
12.3 SW download to the NE

Through the suitable cable, connect the ECT to the F interface of the MAIN unit (see Fig. 163. on page
259).
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. 163. on page 259).
To activate the Ethernet connection refer to para. 11.5.2.2 on page 54. 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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
On NES (Network Element Synthesis) start SWP Administrator: Supervision Files

Administration (SWP Administrator)
02
3DB 06687 CA AA
304
58 / 304

The installation phases are:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

On SWP Administrator windows press install bottom
Browse the SWP file descriptor R94a.dsc from the disk

(C:\ALCATEL\JUSMw0.1.5\ect\swdw\R94AWY\2.0.0)
02
3DB 06687 CA AA
304
59 / 304
Step 3.
Start Supervision
On NES (Network Element Synthesis) start Supervision: Supervision Start
Step 4.
Show Equipment
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
On NES (Network Element Synthesis) start Show Equipment: Supervision Show

Equipment
02
3DB 06687 CA AA
304
60 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

Step 5.
ED
Setup Server Access Configuration
On JUSM start Server Access Configuration: SW Download Server Access Configuration
02
3DB 06687 CA AA
304
61 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

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.
ED
02
3DB 06687 CA AA
304
62 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

Use System Default button

When the operator click the Use System Default button the field ADDRESS can be set in two different
modes:
1)
by F interface: set IP address of the LLMAN to download in interface F mode
2)
by LAN interface: set IP address of the PC to download the software in LAN mode
ED
02
3DB 06687 CA AA
304
63 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10

Step 6.
ED
Init SW Download
On JUSM start Init SW Download: SW Download Init SW Download
Wait List Sw Package creation ...
02
3DB 06687 CA AA
304
64 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

When action is completed, press Enter to close message window.
Now select a specific SWP to download on the NE, and press Init download to start it.
02
3DB 06687 CA AA
304
65 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
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:

02
3DB 06687 CA AA
304
66 / 304
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
02
3DB 06687 CA AA
304
67 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
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.

02
3DB 06687 CA AA
304
68 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

Confirm the selected action.
After this window the NE restarts with the new software package.
02
3DB 06687 CA AA
304
69 / 304
12.4 NE Login
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. 163. on page 259).
To activate on the CT the connection through the Serial Port or through the Ethernet Port refer to
para. 11.5.2 on page 54.
b)
Craft Terminal (CT) startup

1)
CT start :
power on the CT and wait for PC startup
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.
c)
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).
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.
2)
During the creation of the SNMP NE (refer to the 1320CT Basic Craft Terminal
Operators Handbook, section 5 EML CONSTRUCTION), in the TCP/IP Port field
number 161 must be inserted.
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: \ ? : * < >
|.
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING: Due to a deep fading the radio remote NE can be unreachable. In this condition in the
USM will appear the following message:
ED
02
3DB 06687 CA AA
304
70 / 304

a)
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.
WARNING:
d)
When the supervision of a NE has been started dont click on the name of the map.
This operation causes the lock of the CT and the CT must be closed and opened again.
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.
12.5 Commissioning
The commissioning instructions are given in:
9400AWY Line Up Guide
12.6 Configuration data definition

The instructions given in the handbook cited in para. 12.5 above may not include the definition of all the
Equipment configuration data that could be necessary.
1AA 00014 0004 (9007) A4 ALICE 04.10
In order to manage this data, refer to the Section 2 NE MANAGEMENT on page 75.
ED
02
3DB 06687 CA AA
304
71 / 304
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 273, i.e.:
ECT and equipment are running with one of the Software Packages with P/N indicated in Tab. 14. on
page 235 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.11.1 on page 21 and para.12.1 on page 57.
2)
Carry out the installation of the new SWP version in the ECT environment, as indicated in
chapter 11 on page 21.
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 chapterparagraph
(according to SWP Version) in Section 4 on page 233. In case you receive a version higher than
the highest listed on page 233, please refer to the documentation accompanying the SWP
delivery to get this information.
N.B.
4)
Usually the MIB structure is fully compatible inside a SWP Release, so that the
following step 4 ) must be taken into consideration.
new MIB structure compatible with old MIB structure:

a)
perform the SW download with the following Craft Terminal commands (refer to
para.212.2 on page 210 for detailed description):
perform step 1 to 5 in para. 12.3 on page 58
SW Download Init SW download
the screen of Fig. 148. on page 210 opens
select the new NEversion to be downloaded
with SWP Versions 2.0.1 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.
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.
perform NE logoff followed by NE login.
1AA 00014 0004 (9007) A4 ALICE 04.10
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

Procedure presently not necessary.
ED
02
3DB 06687 CA AA
304
72 / 304

13 ECT & NE UPGRADE TO A NEW SWP VERSION (SAME SWP RELEASE)

14 FLASH CARD UPGRADE

Please refer to para.B.2 on page 262 for detailed information on Flash Card position, types, identification
and content.
14.1 Ordering the new Flash Card

Whenever the Base configuration of the 9400AWY NE must be upgraded, Customer must order a new
Flash Card:
of the type consistent with the equipment configuration he wants (see Tab. 21. on page 262),
and, already set by Alcatel Factory:
with the same SWPversion (or higher) present in the 9400AWY system to be upgraded,
already present in the FlashCards SW COMMIT VERSION bank
with the same NE network routing data of the system to be upgraded
and preferably, already set by Alcatel Factory:
with the same MIB of the system to be upgraded (for this purpose, Customer can save the MIB
on floppydisk and give it to Alcatel Factory).
14.2 Installation of the new Flash Card fully configured in factory

This simplified procedure can be carried out only if the new Flash Card is delivered with SW and
data as specified in para.14.1 above.
1AA 00014 0004 (9007) A4 ALICE 04.10
After having got the new Flash Card, the phases for the Flash Card upgrading are:
[1]
get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protection
armlet
[2]
if not connected, connect the Craft Terminal (see point e ) on page 15 for cautions), switch it on, start
1320CT and login the NE
[3]
wear the antistatic protection armlet (see point b ) on page 15) and connect its termination to a
grounded structure
[4]
remove the Flash Card cover (see Fig. 164. on page 259). Store tidily cover and screws for their
successive mount
[5]
extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 165. on page
259 for Flash Card profile and insertion direction)
[6]
restore the Flash Card cover removed in step [4] above (screw tightening torque as in point c ) on
page 15)
[7]
now you can take off the antistatic protection armlet
[8]
carry out functional checks by Craft Terminal
[9]
as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Name, get
and stick it over the older one (see Fig. 163. on page 259); (N.B. if possible, remove the older
selfadhesive label before sticking the newer).
ED
02
3DB 06687 CA AA
304
73 / 304
With this procedure, the system is isolated from the supervision network.
In fact, the insertion in a 9400AWY system connected to the network of a Flash Card with:
default or unknown NE network routing data
SW Commit Version unknown or lower than that present on the system

must be absolutely avoided.
After having got the new Flash Card, the phases for the Flash Card upgrading are:
[1]
get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protection
armlet
[2]
if not connected, connect the Craft Terminal (see point e ) on page 15 for cautions), switch it on, start
1320CT and login the NE
[3]
by Craft Terminal, take notice of the NE network routing data currently set (see point c ) on page
268)
[4]
by Craft Terminal, save the MIB data
[5]
isolate the NE from the supervision network

N.B.
Before to isolate the system from the supervision network, inform the supervision center:
if (from the supervision point of view), there are other NEs cascadeconnected to it (and
without supervision ring network) they will be isolated, too.
[6]
wear the antistatic protection armlet (see point b ) on page 15) and connect its termination to a
grounded structure
[7]
remove the Flash Card cover (see Fig. 164. on page 259). Store tidily cover and screws for their
successive mount
[8]
extract the old Flash Card from the Scalable Main Unit and insert the new one. Refer to Fig. 165. on
page 259 for Flash Card profile and insertion direction
[9]
restore the Flash Card cover removed in step [7] above (screw tightening torque as in point c ) on
page 15)
[10] now you can take off the antistatic protection armlet
[11] now you must perform all operations regarding the NE SW download and data definition, as it is was
done at the equipment SW first time installation:
SWP download from C.T. to NE, using the same SWPversion

NE network routing data definition (using data annotated in step [3] above)
MIB data restore (using MIB saved in step [4] above)
[12] carry out functional checks by Craft Terminal

[13] connect the system to the supervision network
1AA 00014 0004 (9007) A4 ALICE 04.10
[14] as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Name, get
and stick it over the older one (see Fig. 163. on page 259); (N.B. if possible, remove the older
selfadhesive label before sticking the newer).
In alternative, if an offline IDU MAIN unit is available at Customer premises, the Flash Card
can be prepared on it, and then installed on the target system as described in previous
para.14.2 on page 73.
ED
02
3DB 06687 CA AA
304
74 / 304

14.3 Installation of a new Flash Card not configured in factory
SECTION 2: NE MANAGEMENT
SECTION CONTENT
PAGE
Chapter 21 General introduction on views and menus

This chapter describes the organization of the 9400AWY ULS N.E., presented after
the NE login.
77
EQUIPMENT CONFIGURATION MANAGEMENT

Chapter 22 Configuration
This chapter describes the configuration relevant to the equipment management.
87
Chapter 23 Equipment
This chapter deals with the presentation of the N.E. and the structure of the
hierarchical tree, and the types of subracks and boards, that comprise the Network
Element.
127
Chapter 24 Line Interface

This chapter describes the operations necessary for the configuration setting and
verification of each tributary.
137
Chapter 25 Radio
This chapter deals with the management of the Radio transmission features.
147
Chapter 26 External input and output points

This chapter describes how to display and set the input/output environmental
alarms (housekeeping alarms).
161
FUNCTIONS FOR MAINTENANCE

Chapter 27 Supervision
This chapter describes how to manage the NE access from OS or local ECT and
how to restart the NE.
165
Chapter 28 Protection schemes

This chapter deals with the management of the Radio protections.
171
Chapter 29 Loopbacks
This chapter describes the commands for loopback management, for
commissioning or maintenance purposes.
183
Chapter 210 Diagnosis

This chapter describes how to access the Alarm and Event Log files and explains
the Summary Block Diagram View menu.
N.B.
The chapter does not describe the Log Browser. Reference must be
done to the specific ELB Operators Handbook.
193
Chapter 211 Performance Monitoring

This chapter deals with the use of the Performance Monitoring functionalities.
199
1AA 00014 0004 (9007) A4 ALICE 04.10
SOFTWARE MANAGEMENT
ED
Chapter 212 Software Management

This chapter deals with the management of the functions related to the software
verification/download.
209
Chapter 213 MIB Management

This chapter deals with the management of the functions related to the backup
and restore of equipment configuration data.
213
02
3DB 06687 CA AA
304
75 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
76 / 304
21 GENERAL INTRODUCTION ON VIEWS AND MENUS

This chapter describes the organization of the 9400 AWY 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. 2.0.0 and Rel. 2.0.1.
21.1 9400 AWY view organization

The 9400 AWY view ( see Fig. 28. on page 78 ) 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Fig. 28. on page 78 shows the 9400 AWY in 1+1 configuration.
02
3DB 06687 CA AA
304
77 / 304
Severity alarm
synthesis
Domain alarm
synthesis
Menu
bar
Main tool
bar
View
area
Management
state control panel
Fig. 28. 9400 AWY Main view organization
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
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.
02
3DB 06687 CA AA
304
78 / 304

21.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
Protection Schemes (in 1+1 configuration only)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 29. View Areas
ED
02
3DB 06687 CA AA
304
79 / 304
ResourceTree Area: displays all the available resources of the Radio NE.
ResourceList 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.
ResourceDetail 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.
21.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
21.1.2.1 Selection Criteria
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
ED
Single left click;

Double left click
02
3DB 06687 CA AA
304
80 / 304

Each tabpanel (e.g. functionalities area) consists of four areas:

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 collapse the tree node showing the
same information in the Resource list area.
21.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
21.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Critical configuration choices generate a warning message for user confirmation before to be activated.
ED
02
3DB 06687 CA AA
304
81 / 304
21.2 Introduction to the menu options
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 22 on page 87 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.21.2.1 on page 83.
To navigate among the views and to set the TMN parameters.
Configuration
(second column).
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
Diagnosis
(third column).
To get information on the NE (alarms, performance monitoring, remote inventory).
Supervision
(fourth column).
To set the supervision states (i.e. Craft Terminal enabling).
SW Download
(fifth column).
See para. 21.2.5 on page 86.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
82 / 304

The menu bar allows to perform configuration and supervision functions on the Network Element.
1AA 00014 0004 (9007) A4 ALICE 04.10

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

Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.

Loopback:
ED
Allows to manage the loopbacks available with the equipment.

02
3DB 06687 CA AA
304
83 / 304
It is possible to enter directly menus Equipment, External Points, Line Interface, Performance,
Radio, Protection Scheme, Loopback by clicking on the relevant tab panel above the view area.
Refer to Fig. 31. on page 84.
N.B.
Tab panel
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 31. Tab panels
ED
02
3DB 06687 CA AA
304
84 / 304

21.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. 22.1 on page 87.
Network configuration:
See para. 22.2 on page 88.
Alarm Severities:
Manages the Alarm Severity Assignment Profile.

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

21.2.3 Diagnosis menu introduction

This menu allows to get information on the NE, by means of the following entries:
Log Browsing:
Current configuration
View:
Displays the current configuration of the NE.
Summary Block
Diagram View:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Abnormal
condition list:
Manages the events stored in the NE.

Opens the following menu options:
Alarm log
Event log
Software Trace log

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).
Displays the manually operations active in the NE.
02
3DB 06687 CA AA
304
85 / 304
This menu allows to set the supervision states of the NE, by means of the following entries (see chapter
27 on page 165) :
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.

MIB Management: Allows to perform backup and restore operations of the MIB.
SW key:
Displays the type of the key stored in the flash card.

21.2.5 Download menu introduction

This menu allows to manage the NE software, by means of the following entries (see chapter 212 on page
209) :
1AA 00014 0004 (9007) A4 ALICE 04.10
Server Access
Configuration:
Manages the configuration of the FTP server to be used for the software
download to the NE.
Init SW download: Manages the software download to the NE.

SW status:
ED
Shows and manages the status of the software packages installed in the NE
memory banks.
02
3DB 06687 CA AA
304
86 / 304

21.2.4 Supervision menu introduction

22 CONFIGURATION
22.1 NE Time
The NE local time can be displayed and/or realigned 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 realign 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.
The NTP status field is a readonly screen, which shows the configuration regarding the Network Time
Protocol performed in the menu Configuration > Network Configuration > NTP Configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Refresh pushbutton causes the refresh of the screen.
ED
02
3DB 06687 CA AA
304
87 / 304
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
NTP Configuration:
allows to enable/disable the Network Time Protocol
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:
IP Address configuration of
PointToPoint Interfaces :
Routing information
defines the Open Shortest Path First address
defines the IP address of the interface which use the PPP

protocol
shows a summary of the information relevant to the routing
which has been configured.
1AA 00014 0004 (9007) A4 ALICE 04.10
The options are described in next paragraphs.
ED
02
3DB 06687 CA AA
304
88 / 304

22.2 Network Configuration
22.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 89 ) 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 34. Local Configuration dialogue box
ED
02
3DB 06687 CA AA
304
89 / 304
By selecting NTP Configuration the dialogbox in Fig. 35. opens, which allows to enable the Network
Time Protocol.
Fig. 35. NTP Configuration dialogue box

To enable the NTP put a tick in the check box of the Enabling NTP protocol field.
If the NTP has been enabled in the Main Server address field write the IP address of the Server, which
distributes the NTP and in the Spare Server address field write the IP address of the Spare Server, if any,
which will distribute the NTP in case of failure in the Main Server.
To configure the setting click on Apply.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Refresh pushbutton causes the refresh of the screen.
ED
02
3DB 06687 CA AA
304
90 / 304

22.2.2 NTP Configuration

22.2.2.1 How to configure the NTP in a network

When the NTP is enabled, one of the NE must be MASTER and all the other NEs must be SLAVEs.
An example is shown in Fig. 36.
NE1
NE2
NE3
NE4
Fig. 36. Map

As example NE1 must be set as Master:
enable the NTP protocol;

in the Main Server address field and in the Spare Server address field write nothing (in this way
the NE is defined as Master).
NE2 is set as Slave:

in the Main Server address field enter the IP address of NE1 (the Master NE);
in the Spare Server address field enter the IP address of NE1.

1AA 00014 0004 (9007) A4 ALICE 04.10

All the other NEs must be set as NE4.
ED
02
3DB 06687 CA AA
304
91 / 304
22.2.3 Ethernet Configuration
Select the Network Configuration option and then, from the cascading menu, the Ethernet
Configuration option.
The dialogue box in Fig. 37. 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 pointer: 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 37. Ethernet Configuration dialogue box
ED
02
3DB 06687 CA AA
304
92 / 304

Select the Configuration pull down menu.

22.2.4 IP Configuration
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the IP Configuration option ( see Fig. 38. on page 93).
Fig. 38. IP configuration screen
22.2.4.1 IP static routing configuration

The dialogbox opens ( see Fig. 39. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Close button closes the dialogue without changing of the data.
ED
02
3DB 06687 CA AA
304
93 / 304

Fig. 39. IP static routing configuration screen

By pressing Create pushbutton the screen in Fig. 40. 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;
Point to Point Interface Index for the NMS channels (NMSRF, NMSV11, NMSG703)
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
ED
No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.
02
3DB 06687 CA AA
304
94 / 304

Fig. 40. Create Static routing
If in the screen of Fig. 40. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
If in screen in Fig. 40. on page 95 has been selected the Point To Point Interface Index check box,
the screen in Fig. 41. on page 96 opens.
ED
02
3DB 06687 CA AA
304
95 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 41. Point To Point Interface Choice
In this screen one of the 3 NMS channels (NMSRF, NMSV11, NMSG703) can be selected.
ED
02
3DB 06687 CA AA
304
96 / 304

22.2.4.2 OSPF Area configuration

The dialogbox opens ( see Fig. 42. 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. 42. OSPF Area configuration screen
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING: Area 0 is not managed.

WARNING:
If the area is a Stub area the functionalities of the Remote Craft Terminal are not fully
guaranteed.
WARNING: When the area is a Stub area, all the interfaces (NMS and Ethernet) must be defined Stub.
ED
02
3DB 06687 CA AA
304
97 / 304
By pressing Create pushbutton the screen in Fig. 43. on page 98 opens.

3 areas max. can be created.
N.B.
Fig. 43. Create New OSPF Area
1AA 00014 0004 (9007) A4 ALICE 04.10
In the screen write the IP address, the IP mask and select the flag (True/False).
ED
02
3DB 06687 CA AA
304
98 / 304

22.2.4.3 IP Address configuration of PointToPoint Interfaces

The dialogbox opens ( see Fig. 44. 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 dialogbox 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 44. IP Address configuration of PointToPoint Interfaces screen
ED
02
3DB 06687 CA AA
304
99 / 304
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the Routing information option.
The dialogbox in Fig. 45. on page 100 opens.
Fig. 45. Routing information screen
This screen is a readonly screen and displays the routing parameters currently active on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Close button closes the dialogue without changing of the data.
ED
02
3DB 06687 CA AA
304
100 / 304

22.2.5 Routing information

22.3 Alarm Severities

By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 46. 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
MAJOR: the alarm affects the service (it is service affecting);
MINOR or WARNING (according to the impact of the alarm): the alarm doesnt 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).
ED
02
3DB 06687 CA AA
304
101 / 304

Fig. 46. Alarm Severities Profile

In the screen of Fig. 46. on page 102 are available 2 buttons:
Close: to close the screen.

Clone: to create a new Alarm Severity Profile. To create a clone refer to para. 22.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
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;
select the Configuration menu in the relevant Resource Detail Area;
select in the Alarm Profile field the Alarm Profile to be associated.
02
3DB 06687 CA AA
304
102 / 304

22.3.1 How to create a new Alarm Severity Profile
Select in the screen of Fig. 46. on page 102 the Alarm Profile to be cloned.
Click the Clone pushbutton.
The screen of Fig. 47. on page 103 appears.
Digit the name to be assigned to the new Alarm Profile and click on Apply.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 47. 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. 48. on page 103).
Fig. 48. Clone of an Alarm Severity Profile
ED
02
3DB 06687 CA AA
304
103 / 304
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. 49. on page 104).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 49. Selection of a new severity in the Service Affecting field
ED
02
3DB 06687 CA AA
304
104 / 304

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. 50. on page 105).

Fig. 50. Selection of a new severity in the No Service Affecting field
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
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. 50. on page 105).
02
3DB 06687 CA AA
304
105 / 304
22.4 System Settings
The main window provides 3 tabbedpanels, one for each type of function to be managed:
NE configuration
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. 27.2 on page 166).
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.
22.4.1 NE Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
The user can view and define the NE configuration by selecting the NE Parameters tabbed panel.
The window displayed in Fig. 51. on page 106 will appear.
The field Type contains all the allowed configurations supported for the NE. 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 the market type: ETSI only in Rel. 2.0.0 and ETSI or ANSI in Rel. 2.0.1. (refer
to Tab. 2. on page 107). The operator choice will be applied by clicking the related Apply button.
Fig. 51. System Settings: NE configuration
ED
02
3DB 06687 CA AA
304
106 / 304

This menu allows the system configuration, providing the setting of all the parameters for the NE setup.

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

Market
Capacity
Modulation
ETSI
2xE1
4QAM
4xE1
4QAM / 16QAM
8xE1
4QAM / 16QAM
16xE1
4QAM / 16QAM
1xE3
4QAM / 16QAM
4xDS1
4QAM
8xDS1
4QAM / 16QAM
16xDS1
4QAM / 16QAM
1xDS3
4QAM / 16QAM
ANSI
(see Tab. 1. on page 12)
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.
WARNING:
When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa) the Tx
power (in case of operation with RTPC) and the ATPC range (in case of operation with
ATPC) of the new modulation scheme must be in the correct range (refer to para. 25.4
on page 152). If the value is out of range the relevant field in the RTPC & ATPC screen
appears empty (automatically is associated a default value, but this value is not displayed).
Fill the field with the suitable value.
The Capacity can be modified by selecting a different type according to Tab. 2. 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. 52. is requested.
Fig. 52. Confirmation message
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
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.
02
3DB 06687 CA AA
304
107 / 304
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. 53. ).
Fig. 53. USM closing warning message
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 (unbalanced 75 ohm or balanced 120ohm
for E1 tributary; balanced 100 ohm for DS1 tributary).
N.B.
The DS1/DS3 tributaries (ANSI market) are not supported in Rel. 2.0.0.
1AA 00014 0004 (9007) A4 ALICE 04.10
The impedance value will be applied by clicking on the related Apply button.
ED
02
3DB 06687 CA AA
304
108 / 304

N.B.

22.4.2 Overhead
The Overhead tabbed panel identifies the parameters for the management of the phone number and
auxiliary interface (Fig. 54. on page 109).
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: 1099.
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. 22.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
the default associated Alarm Profile is the Primary Alarm profile.
02
3DB 06687 CA AA
304
109 / 304
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 111 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 helpon line.
1AA 00014 0004 (9007) A4 ALICE 04.10
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. 28.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.
ED
02
3DB 06687 CA AA
304
110 / 304

22.5 Quick Configuration Procedure

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

Step 1 provides a screen to configure two NE parameters:
Market (ETSI only in Rel. 2.0.0; ETSI or ANSI in Rel. 2.0.1);

Type configuration.
The possible selections for the Type field are:
1+0 unprotected configuration

1+1 HST: Hot Standby protected configuration
1+1 FD: Frequency Diversity protected configuration
N.B.
Every type is available with the following tributaries:

8xE1/8xDS1
16xE1/16xDS1
1xE3/1xDS3
8xE1/8xDS1 + 2 Ethernet ports
and with the following Power Supply Units:
24 Vdc
48/60 Vdc
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
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. 22.4.1 on page 106).
To go to step 2 click on button Next.
ED
02
3DB 06687 CA AA
304
111 / 304
The screen shown in Fig. 56. on page 112 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. 2. on page 107.
Moreover, the Impedance for the E1 tributary also must be selected in the Tributary Port Configuration
(unbalanced 75 ohm or balanced 120 ohm).
Fig. 56. Quick Installation Procedure: Frame Configuration (Step 2)
In the screen displayed in Fig. 56. on page 112 (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.
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. 22.4.1 on page 106).
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
02
3DB 06687 CA AA
304
112 / 304

Step 2 (Frame structure and modulation format)

Step 3 (Tributary configuration)

Step 3 allows the operator to choose, for each tributary configured, the signal mode or disable it
(Fig. 57. on page 113).
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.
WARNING:
In case of the configuration with the two Ethernet ports some tributary ports must be at
least disabled in order to allow the transmission of the Ethernet data.
Refer to the following Table.
Market
Capacity
Number of disabled tributaries
ETSI
2xE1
1
4xE1
1
8xE1
1
16xE1
8
4xDS1
1
8xDS1
1
16xDS1
8
1AA 00014 0004 (9007) A4 ALICE 04.10
ANSI
(see Tab. 1. on page 12)
ED
02
3DB 06687 CA AA
304
113 / 304
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 114):
Radio Protection (Rx RPSHitless Switch)
Mux/Demux Protection (Tx/Rx EPS)
HST Tx Protection (RF Hot Standby)
Fig. 58. Quick Installation Procedure: Tributaries Configuration (Step 4)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
114 / 304

Step 4 (Automatic restoration criteria configuration)

Step 5 (Channel configuration) in Rel. 2.0.0

Step 5 allows the operator to define the basic parameters for each configured channel. The related screen
is shown in the Fig. 59. on page 115:
Fig. 59. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.0)
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. 25.4 on page 152).
If ATPC is disabled in the RTPC area the power (constantly 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.
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. 25.3 on page 149).
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
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.

ED
02
3DB 06687 CA AA
304
115 / 304
Step 5 allows the operator to define the basic parameters for each configured channel. The related screen
is shown in the Fig. 60. on page 116:
Fig. 60. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.1)
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. 25.4 on page 152).
If ATPC is disabled in the RTPC area the power (constantly transmitted) can be selected by writing the
suitable value in the Tx power field.
The system can operate with different types of ODU according to the RF band and to the channel
arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefined
shifters (flexible shifter).
ODU with one Shifter only
1AA 00014 0004 (9007) A4 ALICE 04.10
If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).
In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the Frequency
Range field on the right side) and press pushbutton Apply (the Rx frequency is automatically calculated
by using the inserted Tx frequency and the shifter).
Note: During the command setting the CT is frozen. Waiting time: max 30.
ED
02
3DB 06687 CA AA
304
116 / 304

Step 5 (Channel configuration) in Rel. 2.0.1
ODU with different available Shifters
1AA 00014 0004 (9007) A4 ALICE 04.10

In the Tx frequency field insert the suitable Tx frequency and press pushbutton Apply.
In the Shifter field select the suitable shifter and press pushbutton Apply (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
ED
02
3DB 06687 CA AA
304
117 / 304
Step 6 performs the network configuration (Fig. 61. on page 118). This window allows to enter to IP
address associated to the F interface of the NE.
N.B.
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. 22.2.1 on page 89).
Fig. 61. 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
02
3DB 06687 CA AA
304
118 / 304

Step 6 (Local configuration)
Step 7 (OSPF area configuration)

Step 7 allows to configure one or more OSPF Areas (3 areas max.) (Fig. 62. on page 119).
Fig. 62. Quick 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 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
02
3DB 06687 CA AA
304
119 / 304
Step 8 (IP static route configuration)

The following windows for Network Configuration allow the complete IP configuration.
Step 8 configures one or more Static Routers (Fig. 63. on page 120).
Fig. 63. 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

WARNING:
ED
No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.
02
3DB 06687 CA AA
304
120 / 304
Step 9 (NMS RF channel configuration)

Step 9 allows the configuration of the NMSRF channel (Fig. 64. on page 121):
Fig. 64. Quick Configuration Procedure: NMSRF Interface Configuration (Step 9)
The NMSRF interface is a communication interface based on the use of an inframe RF proprietary
64 kbit/s channel. Through the NMSRF interface the NE can exchange management messages with
a remote OS (or Craft Terminal) station.
The NMSRF 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
02
3DB 06687 CA AA
304
121 / 304
Step 10 (NMS V11 channel configuration)

Step 10 allows the configuration of the NMSV11 interface (Fig. 65. on page 122):
Fig. 65. Quick Configuration Procedure: NMSV11 Interface Configuration (Step 10)
Through the NMSV11 interface the NE can exchange management messages with an OS (or Craft
Terminal) in the same station.
The NMSV11 channel can be Enabled or Disabled by selection in the NMS V11 field.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
synchronization of the SDH network.
Codirectional mode:
to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.

ED
02
3DB 06687 CA AA
304
122 / 304
Step 11 (NMS G703 channel configuration)

Step 11 allows the configuration of the NMSG703 interface (Fig. 66. on page 123):
Fig. 66. Quick Configuration Procedure: NMSG703 Interface Configuration (Step 11)
Through the NMSG703 interface the NE can exchange management messages with an OS (or Craft
Terminal) in the same station.
The NMSG703 channel can be Enabled or Disabled by selection in the NMS G703 field.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the 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
synchronization of the SDH network.
Codirectional mode:
to link adjacent AWY or to interface MUX based on 64 kbit/s, avoiding any V.11/G.703 adapter.

ED
02
3DB 06687 CA AA
304
123 / 304
Step 12 (Ethernet configuration)

Step 12 (Fig. 67. on page 124) allows to configure the Ethernet Interface.
Fig. 67. 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
02
3DB 06687 CA AA
304
124 / 304

Step 13 (Summary)
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. 68. on page 125).
Fig. 68. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
125 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
126 / 304
23 EQUIPMENT

This chapter describes the types of functions offered to the user for Equipment Management.
N.B.
Please refer to Appendix A on page 251 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 differs according to the configuration:
Fig. 69. on page 128 for 1+0 configuration
Fig. 70. on page 128 for 1+1 configuration.
In the Resource List Area is shown a graphical representation of the Equipment, which consists of one
IDU and one ODU in 1+0 configuration and two IDUs and two ODUs in 1+1 configuration.
The IDU consists of different boards according to the configuration: 8xE1/DS1, 16xE1/DS1, E3/DS3 with
or without the Ethernet ports.
1AA 00014 0004 (9007) A4 ALICE 04.10
A colored ball gives information on the status of the associated object (Equipment, ODU, IDU, IDU board).
The colour differs according to the severity of the alarms:
Green: no alarm
White: indetermination alarm active (not operative)
Cyan: warning alarm active
Yellow: minor alarm active
Brown: major alarm active
Red: critical alarm active
ED
02
3DB 06687 CA AA
304
127 / 304

Equipment Status
ODU
ODU Status
IDU
IDU Status
Fig. 69. 1+0 Equipment view
Equipment Status
ODU
Ch#0
ODU
Ch#1
ODU
Status
IDU/MAIN Ch #1
IDU Ch #0
1AA 00014 0004 (9007) A4 ALICE 04.10
IDU Status
Fig. 70. 1+1 Equipment view
ED
02
3DB 06687 CA AA
304
128 / 304

23.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.
23.1.1 1+0 configuration
The screen in Fig. 71. on page 129 will appear.
IDU Status
IDU
MAIN BOARD
Status
Fig. 71. 1+0 IDU view

One IDU is present:
IDU channel#1: the Main IDU.
1AA 00014 0004 (9007) A4 ALICE 04.10
The IDU channel#1 includes the IDU/Main Ch#1 object, which includes according to the configuration type
the following options:
IDU/MAIN/DATA Ch#1 with the 2 Ethernet ports
IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries interface.
ED
02
3DB 06687 CA AA
304
129 / 304
The screen in Fig. 72. on page 130 will appear for the Ch#1 and the screen in Fig. 73. on page 131 will
appear for the Ch#0.
IDU Status
IDU
MAIN BOARD
Status
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 72. 1+1 IDU/MAIN Ch#1 view
ED
02
3DB 06687 CA AA
304
130 / 304

23.1.2 1+1 configuration

IDU Status
IDU
Fig. 73. 1+1 IDU Ch#0 view
Two IDUs are present:
IDU channel#1: the Main IDU
IDU channel#0: the Extension IDU
The IDU channel#1 includes the IDU/Main Ch#1 object which includes according to the configuration type
IDU/MAIN/DATA Ch#1 with the 2 Ethernet ports (this board receives the power supply from the Main
IDU only).
IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries interface.
1AA 00014 0004 (9007) A4 ALICE 04.10
The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration type
IDU/EXT/8xE1/DS1 Ch#0 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
IDU/EXT/1xE3/DS3 Ch#0 with the E3/DS3 tributaries interface.
ED
02
3DB 06687 CA AA
304
131 / 304
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 74. Main board view
ED
02
3DB 06687 CA AA
304
132 / 304

23.1.3 Board level

23.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 75. ODU view
ED
02
3DB 06687 CA AA
304
133 / 304
23.3.1 Alarms
The Alarms tab panel provides the fault management, which checks the current state of alarms related
to the selected object (Fig. 76. on page 134).
Fig. 76. 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 subnodes box the alarms currently active in the subnodes
of the object will also appear.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
134 / 304

23.3 Tab panels in the Resource Detail Area
23.3.2 Configuration

The User Label field (Fig. 77. ) 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. 22.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.
Fig. 77. Configuration tab panel for a selected object
23.3.3 Remote Inventory

The information about the unit can be read in the Remote Inventory panel in the Resource Detail Area
as the following window shows (Fig. 78. on page 135):
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 78. Remote Inventory tab panel for a selected object
ED
02
3DB 06687 CA AA
304
135 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
136 / 304

24 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 menu allows the user to manage the resources of the line interfaces: PDH tributary,
NMS channel and Ethernet port, if has been configured.
This domain view consists of the following areas (Fig. 79. on page 137):
Resource Tree Area: displays the tributary ports sorted by the channel number and the NMS
interfaces.
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. 79. Line Interface View
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Resource List Area is given the information related to the tributaries or to the NMS channels:
Type Interface (E1/DS1 or E3/DS3, Ethernet, NMS 64 kbit/s channel)
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)

To configure a line interface select the interface in the Resource Tree Area and configure the Configuration
tab panel in the Resource Detail Area.
N.B.
ED
In the Resource Tree Area below the Tributary PDH line are shown all the E1/DS1 tributaries
according to the capacity selected in the System Setting menu or in Quick Configuration menu.
02
3DB 06687 CA AA
304
137 / 304
24.1.1 Alarm
The fault management checks the current state of alarms related to the selected tributary.
It is provided by the alarm panel like the one explained in para. 23.3.1 on page 134.
WARNING:
The GFP alarm (alarm present in the Ethernet data interface) if active is shown not in this
tab panel, but in the Alarm tab panel of the Radio menu.
24.1.2 Configuration
There are different tab panels according to the type of interface:
PDH interface (para. 24.1.2.1 on page 138)

NMS interface (para. 24.1.2.2 on page 143)
Ethernet interface (para. 24.1.2.3 on page 143)
24.1.2.1 Tributaries PDH Configuration tab panel

24.1.2.1.1 ETSI Market
The window, shown in Fig. 80. on page 138 for E1 tributary and Fig. 81. on page 138 for E3 tributary,
performs all the available functions for a PDH tributary port.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 80. Line Interface View: E1 Tributary Port
Fig. 81. Line Interface View: E3 Tributary Port
ED
02
3DB 06687 CA AA
304
138 / 304

24.1 Tab panels in the Resource Detail Area

In Fig. 80. on page 138 and Fig. 81. on page 138 the following fields are readonly 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
Line RAI Insertion
Radio 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.
WARNING:
In case of the configuration with the two Ethernet ports some E1 ports must be at least
disabled in order to allow the transmission of the Ethernet data.
Capacity
Number of disabled E1 tributaries
2xE1
1
4xE1
1
8xE1
1
16xE1
8
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
02
3DB 06687 CA AA
304
139 / 304
Line RAI Insertion (for E1 tributary only)
This field refers to the insertion of the RAI signal in Tx side. The possible alternative values are:
Forced: the RAI insertion is performed

Enabled: the RAI insertion is possible.
Radio 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 alternative values are:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
the default associated Alarm Profile is the No Alarm profile.
02
3DB 06687 CA AA
304
140 / 304

This feature is available for framed signals only.
24.1.2.1.2 ANSI Market

Note: refer to Tab. 1. on page 12.

The window, shown in Fig. 82. on page 141 for DS1 tributary and Fig. 83. on page 141 for DS3 tributary,
performs all the available functions for a tributary port.
Fig. 82. Line Interface View: DS1 Tributary Port
Fig. 83. Line Interface View: DS3 Tributary Port

In Fig. 82. on page 141 and Fig. 83. on page 141 the following fields are readonly 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 (0133, 133266, 266399, 399533, 533655 : for DS1 tributary only)
Alarm Profile
Signal Mode (for DS1 tributary)
1AA 00014 0004 (9007) A4 ALICE 04.10
Framed SF for the Super Framed received signal

Framed ESF for the Extended Super Framed received signal
Disabled
ED
02
3DB 06687 CA AA
304
141 / 304
Capacity
Number of disabled DS1 tributaries
4xDS1
1
8xDS1
1
16xDS1
8
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:
0133
133266
266399
399533
533655
1AA 00014 0004 (9007) A4 ALICE 04.10
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm
Alarm Profile.
N.B.
ED
the default associated Alarm Profile is the No Alarm profile.
02
3DB 06687 CA AA
304
142 / 304

WARNING:

24.1.2.2 NMS interfaces Configuration tab panel
Fig. 84. Line Interface View: NMS interface

For the NMS 64 kbit/s channels only the Alarm Profile can be associated.
The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator in menu Configuration > Alarm
Severities. To associate a different Alarm Profile click on the selection button and make the selection
among the available Alarm Profile.
N.B.
The default associated Alarm Profile is the No Alarm profile.
24.1.2.3 Tributaries Data Configuration tab panel

The Ethernet interfaces can be configured according to two different modalities: manual (or default type)
mode (autonegotiation is disabled) or automatic mode (autonegotiation is enabled). In automatic mode
a mechanism of autosensing (the autonegotiation) of the parameters involved is activated. These
parameters are negotiated with the remote Ethernet interface.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following items resume the features supported:
the rate (10 or 100 Mb/s) is always configurable independently of the modality (manual or automatic);
the directionality is always fullduplex (no carrier control mechanism is implemented to use
the halfduplex mode);
when the autonegotiation process fails or when the autonegotiation parameters are changed, the
autonegotiation restart command has to be performed in order to have new configured parameters
effective.
ED
02
3DB 06687 CA AA
304
143 / 304

1 Configuration menu
Fig. 85. Line Interface View: Ethernet Port
In this menu the Ethernet port can be Enabled or Disabled and the Errored Frames can be discarded in
Tx side and in Rx side. To each Ethernet port can also be associated an Alarm Profile.
The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator in menu Configuration > Alarm
Severities. To associate a different Alarm Profile click on the selection button and make the selection
among the available Alarm Profile.
WARNING:
Market
Capacity
Number of disabled tributaries
ETSI
2xE1
1
4xE1
1
8xE1
1
16xE1
8
4xDS1
1
8xDS1
1
16xDS1
8
ANSI
(see Tab. 1. on page 12.)
N.B.
The default associated Alarm Profile is the No Alarm profile.
1AA 00014 0004 (9007) A4 ALICE 04.10
To confirm the new configuration click on Apply.
ED
02
3DB 06687 CA AA
304
144 / 304

2 Autonegotiation
Fig. 86. Line Interface View: Ethernet Port autonegotiation

In this menu the Autonegotiation protocol regarding the Ethernet port can be Enabled or Disabled.
1AA 00014 0004 (9007) A4 ALICE 04.10
To confirm the new configuration click on Apply.
ED
02
3DB 06687 CA AA
304
145 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
146 / 304
25 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. 87. Radio Domain View

Five tab panels are present in the Resource Detail Area:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Alarms: shows the active alarms (refer to para. 25.1 on page 148)
Configuration: configures some radio parameters (refer to para. 25.2 on page 148)
Frequency: sets the Tx RF frequency (refer to para. 25.3 on page 149)
RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (refer
to para. 25.4 on page 152)
Power Meas: performs the Tx and Rx power measurements (refer to para. 25.5 on page 155).
02
3DB 06687 CA AA
304
147 / 304
The fault management 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. 23.3.1 on page 134.
25.2 Configuration
The window shown in Fig. 88. on page 148 performs all the available functions for a Radio channel.
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.
Fig. 88. Radio Configuration menu

25.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.
WARNING:
The Tx Remote Mute automatically works (on and then off) only if performed on the
local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed,
the EC changes the channel in monodirectional way, in order to have the possibility to
send the command to remove the mute. If the Network Element has been restarted after
a MUTE, there is no more possibility to setup the channel, because the remote address
is not known, and, in any case, to setup the channel a bidirectional communication is
needed. The only way to remove the MUTE command is with local CT or from a remote
CT which can reach the Network Element through another supervisory interface.
25.2.2 ODU service kit

This field is a readonly field, which displays the state of the Portable Service Kit (connected or not to the
ODU).
1AA 00014 0004 (9007) A4 ALICE 04.10
25.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.
N.B.
ED
02
3DB 06687 CA AA
304
148 / 304

25.1 Alarm

25.3 Frequency
25.3.1 Frequency menu in Rel. 2.0.0
This menu (Fig. 89. on page 149) 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. 89. Radio Frequency menu in Rel. 2.0.0

25.3.1.1 Tx Radio Frequency
The Tx Freq field in the Frequency Value area of tabbed window (Fig. 89. on page 149) 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
25.3.1.2 Rx Radio Frequency

The Rx Freq field in the Frequency Value area of the tabbed window (Fig. 89. on page 149) 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
Frequency Shifter.
ED
02
3DB 06687 CA AA
304
149 / 304
25.3.2 Frequency menu in Rel. 2.0.1

This menu (Fig. 90. on page 150) allows to read and, if necessary, to set the frequency parameters.
Fig. 90. Radio Frequency menu in Rel. 2.0.1

The system can operate with different types of ODU according to the RF band and to the channel
arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefined
shifters (flexible shifter).
25.3.2.1 ODU with one Shifter only

If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).
In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the Frequency
Range field on the right side) and press pushbutton Apply (the Rx frequency is automatically calculated
by using the inserted Tx frequency and the shifter).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
150 / 304
25.3.2.2 ODU with different available Shifters

In the Tx frequency field insert the suitable Tx frequency and press pushbutton Apply.
In the Shifter field select the suitable shifter and press pushbutton Apply (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
Now the Rx frequency can be changed in order to implement a suitable new shifter. Insert the new value
( 5 MHz respect to the value previously automatically calculated) in the Rx frequency field and press
pushbutton Apply.
WARNING:
The Rx frequency must be 5 MHz respect to the value automatically calculated according
to the Tx frequency and to the shifter.
When the Rx frequency is changed a specific warning message about possible impact on the traffic will
appear. This message requires an explicit confirmation to proceed.
At the end a specific result message appears to inform the operator that the operation has been completed
(or failed in case of failure).
At this point other operations can be normally requested by the operator.
WARNING:
The background of the Shifter field changes to red color and the specific warning message
WARNING: Frequency parameters are not aligned to standard configuration
associated to the selected Shifter.
For more information, refer to technical handbook (N.B.) is written on the Frequency
screen as shown in Fig. 91.
N.B.
Information present from Ed.02 of Technical Handbook.
Fig. 91. Not standard frequency arrangement

To restore a Standard Shifter configuration, the operator has only to apply again the selected (or another
one) Shifter value or to apply again the Tx frequency.
As result, the normal Frequency screen is restored removing both red color as background of the Shifter
field and the specific warning message.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
151 / 304
25.4 RTPC & ATPC

This menu (Fig. 92. on page 152) 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.
Static value of the Tx power

(30 dB range)
Dynamic value of the Tx power
(20 dB range)
ATPC Rx Threshold
Fig. 92. Rtpc & Atpc
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
ED
When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa) the Tx
power (in case of operation with RTPC) and the ATPC range (in case of operation with
ATPC) of the new modulation scheme must be in the correct range. If the value is out of
range the relevant field in the RTPC & ATPC screen appears empty (automatically is
associated a default value, but this value is not displayed).
Fill the field with the suitable value.
02
3DB 06687 CA AA
304
152 / 304
25.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.
WARNING:
[1]
In 1+1 Configuration (HST or FD) the ATPC information, sent back from the Rx side to Tx
side, is the information relevant to the channel (protecting or protected) currently active
in the EPS protection scheme. The two transmitters are, therefore, driven by the same
ATPC control signal.
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]
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.
WARNING:
During the reconfiguration phase or during the activation of a new software the alarm
ATPC loop is active.
It is recommended to use the following Tab. 3. (for ETSI) and Tab. 4. (for ANSI) in order to
set the ATPC threshold. The ATPC shape is calculated using the following max capacity:
E3 for ETSI
DS3 for ANSI

Tab. 3. ATPC Range Rx Threshold for ETSI
4
QAM
1AA 00014 0004 (9007) A4 ALICE 04.10
16
QAM
ED
TH
7/8
GHz
11
GHz
13
GHz
15
GHz
18
GHz
23
GHz
25
GHz
28
GHz
32
GHz
38
GHz
Min
Value
66
68
67
67
65
65
64
64
63
63
Max
Value
60
60
60
60
60
55
50
50
50
50
Min
Value
62
64
63
63
61
61
60
60
59
59
Max
Value
60
60
60
60
60
55
50
50
50
50
02
3DB 06687 CA AA
304
153 / 304
4
QAM
16
QAM
TH
15
GHz
18
GHz
23
GHz
38
GHz
Min
Value
65
63
63
59
Max
Value
60
60
55
50
Min
Value
61
59
59
55
Max
Value
60
59
55
50

Tab. 4. ATPC Range Rx Threshold for ANSI
The applied rule is:

ATPC Rx threshold setting
Frequency Band
Min Value
Max Value
7/8,11,13, 15 & 18 GHz
PRxth + 15 dB
60 dBm
23 GHz
PRxth + 15 dB
55 dBm
25 & 38 GHz
PRxth + 15 dB
50 dBm
PRxth: Received power level correspondent to BER 106 according to modulation scheme,
payload and ETSI/FCC standard
25.4.2 RTPC
[1]
Nominal Power
The Nominal Value field in the RTPC area is a readonly field and shows the nominal value of the
transmitted power (expressed in dBm).
[2]
Tx Power
The Tx Power field in the RTPC area 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
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the ATPC is enabled, the Tx power value cannot be modified.
ED
02
3DB 06687 CA AA
304
154 / 304

25.5 Power Measurement

The Power Measurements capability is performed through the Power Meas tabbed panel in the resource
detail view (Fig. 93. on page 155).
Fig. 93. Power Measurements

The Measurement screen allows the operator to set initial parameters for the required measurement.
Measurement interval fields allow the operator to set the timeduration of the measurement. The
default is Days: 7, Hours: 0, Minutes: 0. A 7day 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/CTKv3.0.1 directory.
1AA 00014 0004 (9007) A4 ALICE 04.10
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. 93. on
page 155).
ED
02
3DB 06687 CA AA
304
155 / 304
The Power Measurement Graphic is available only if the CT is connected to the 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 endpoint 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 analyzed;
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.
Fig. 94. Power Measurement Graphic

By clicking on Show details box, on the left side of the Power Measurement Graphic (see Fig. 94. on
page 156), a new table appears (Fig. 95. on page 157); this table shows the following relevant values of
the received and transmitted power:
1AA 00014 0004 (9007) A4 ALICE 04.10
Tx Local End
ED
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.
02
3DB 06687 CA AA
304
156 / 304

The screen in Fig. 94. shows the Tx and Rx measurements related to the local NE.

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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 95. Power Meas Details
WARNING:
If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HST Configuration the
transmitter is in standby).
If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field
the information in dBm is 99, probably the supervision has been lost. The confirmation of the loss
of the supervision is given by a broken red icon in NES screen.
ED
02
3DB 06687 CA AA
304
157 / 304
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/CTKv3.0.1 directory and have
extension .txt.
Fig. 96. Name of File ( Log File ) selected screen
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the desired file and click the Start button in Fig. 93. on page 155 to open the file.
Fig. 97. 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
02
3DB 06687 CA AA
304
158 / 304

25.5.1 How to read a Power Measurement file

Select the .txt file and click with the mouse right pushbutton to open .txt file with a text editor (e.g.
WordPad) and to see the power information in tabular mode (see Fig. 98. on page 159).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 98. Example of Power Measurement File Reading (with WordPad)
ED
02
3DB 06687 CA AA
304
159 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
160 / 304

26 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. 99. on page 161, 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 Resource list area opens the
Configuration menu in the Resource Detail Area. An example of this mechanism is displayed in the
Fig. 99. on page 161.
26.1 Input External Points

An input external point is described by the following parameters (Fig. 99. on page 161):
Id: identification number

UserLabel: associates a userfriendly 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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 99. Input External Point View
ED
02
3DB 06687 CA AA
304
161 / 304
26.2 Output External Points
The first four external points (CPO#1, 2, 3, 4) (Fig. 100. on page 162) are described by the following
parameters:
UserLabel: a userfriendly 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.
Criteria: Manual or Automatic. The output can be activated manually by the CT by selecting Manual
(Fig. 100. on page 162) or automatically by selecting Automatic (Fig. 101. on page 163). In this case
a new field appears (Event) in which it is possible to select the alarm, the generation of which will
cause the activation of the external point output.
External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The operator choices will be sent to NE by clicking on the Apply button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 100. Output External Points: CP01 ... CP04 (Manual activation)
ED
02
3DB 06687 CA AA
304
162 / 304

Seven output external points are available:

Fig. 101. Output External Points: CP01 ... CP04 (Automatic activation)
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 102. on page 164)
are described by the following parameters:
UserLabel: a userfriendly 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
The operator choices will be sent to NE by clicking on the Apply button.
ED
02
3DB 06687 CA AA
304
163 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 102. Output External Points View: FAIL IDU, FAIL ODU
ED
02
3DB 06687 CA AA
304
164 / 304

27 SUPERVISION
27.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:
27.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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 103. 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 doesnt answer in a predefined time, it is assumed that the NE is in the Craft access state
and can be managed by a Craft Terminal.
ED
02
3DB 06687 CA AA
304
165 / 304
Select the Supervision pull down menu. Then from the Access State cascading menu 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).
27.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. 104. Restart NE call

The following dialogue box opens.
Fig. 105. Restart NE confirmation

Click the OK button to confirm the restart N.E. operation
Click the Cancel button to abort the restart N.E. operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
ED
After the activation of the Restart NE Command (or after the pressing of the HW reset
pushbutton) the LLM icon is frozen and the supervision of the local NE and the remote
NEs is lost.
02
3DB 06687 CA AA
304
166 / 304

27.1.2 Switching from the Craft Terminal access state back to the OS access state

27.3 MIB Management

This menu (Fig. 106. on page 167) refers to the management of the MIB (Management Information Base).
The MIB includes all the system configuration data, except the routing configuration data:
Systems local address
Interface configuration
NMS configuration
Ethernet configuration
IP configuration
IP Static Routing configuration

OSPF Area configuration
IP Address configuration of point to point configuration
1.
Local configuration
2.
NTP server configuration
3.
4.
Fig. 106. MIB Management
1AA 00014 0004 (9007) A4 ALICE 04.10
The routing configuration data 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.
ED
02
3DB 06687 CA AA
304
167 / 304
This menu (Fig. 107. on page 168) allows to save on the CT the NE configuration. To backup the
configuration write the filename in the Backup field (Lower part) and press Confirm Backup.
WARNING: The backup file name must not include the following characters: space, &, /.
Fig. 107. Backup screen

Confirm the backup operation to start the operation.
In the upper part appears the list of the previously created backups.
1AA 00014 0004 (9007) A4 ALICE 04.10
By pressing Refresh the list is updated with the insertion of the just created backup.
ED
02
3DB 06687 CA AA
304
168 / 304

27.3.1 Backup
27.3.2 Restore

This menu (Fig. 108. on page 169) allows to download to the NE a previously created backup.
Fig. 108. Restore screen

Select one of the backups to be downloaded in the upper part and press Confirm Restore.
(By pressing the Reset pushbutton the previous selection is cancelled and a new selection can be made).
Confirm the restore operation to start the operation.
To activate the new configuration enter command MIB Management > Activate.
27.3.3 Activate
1AA 00014 0004 (9007) A4 ALICE 04.10
This command (Fig. 109. on page 169) allows to activate the configuration just downloaded with the
restore.
Fig. 109. Activate command
ED
02
3DB 06687 CA AA
304
169 / 304
27.3.4 Remove file

This menu allows to remove from the list of the backups one particular backup.
To remove a backup select the backup file in the upper part and press Confirm Remove.
Confirm the operation to start the operation.
By pressing Refresh the list of backups in the upper part of the screen is updated.
27.4 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 110. SW key screen
ED
02
3DB 06687 CA AA
304
170 / 304
28 PROTECTION SCHEMES

This domain is present in 1+1 configuration only.

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 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. 111. on page 171, the tree will be expanded according to
protection schemes supported.
Fig. 111. 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 example of this mechanism is displayed in the
following figure (Fig. 112. on page 172).
1AA 00014 0004 (9007) A4 ALICE 04.10
Three 1+1 protection schemes have been implemented:
ED
Mux/Demux protection: EPS protection in Tx and Rx sides

Radio protection: RPS Hitless Switch in Rx side
HST protection: Hot Standby protection
02
3DB 06687 CA AA
304
171 / 304
Mux/Demux protection corresponds to the Switch Tx and the Rx output switch in Fig. 136. on page
196 or Fig. 138. on page 197
The Radio protection corresponds to the Switch RPS HS in Fig. 136. on page 196 or Fig. 138. on
page 197
The HST protection is implemented in the ODU: one Transmitter is connected to the antenna
(active), the other transmitter is in standby. Refer to Fig. 136. on page 196. The HST protection
is available only if the HST configuration has been selected.
28.1 Mux/Demux Protection Management

The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.
The following window (Fig. 112. on page 172) allows a complete view of all Ne resource involved in the
EPS protection:
Schema Parameters
Channels Parameters
1AA 00014 0004 (9007) A4 ALICE 04.10
To read the
correct
indication
on the switch
status press
here to refresh
the screen
Fig. 112. Mux Protection
ED
02
3DB 06687 CA AA
304
172 / 304

To see the current position of the switches enter the menu Diagnosis > Summary Block Diagram View
(refer to para. 210.4 on page 194).
28.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.
28.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 113. on page 173)
or on the Main #1 element (Fig. 114. on page 174).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 113. Mux Protection Switch (Spare #0)
ED
02
3DB 06687 CA AA
304
173 / 304

Fig. 114. 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Command
N.B.
ED
Priority
Lockout
Forced
Automatic switch
Manual
to release a previously activated command select None and click on Apply.

02
3DB 06687 CA AA
304
174 / 304
28.2 Radio Protection Management

The Radio Protection Management is performed by selecting the Radio Protection element tree.
The following window (Fig. 115. on page 175) allows a complete view of all Ne resource involved in a RPS
protection:
Rx Static Delay
Schema Parameters
Channels Parameters
To read the
correct
indication
on the switch
status press
here to refresh
the screen
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 115. Radio Protection View
ED
02
3DB 06687 CA AA
304
175 / 304

28.2.1 Rx Static Delay
Fig. 116. Rx Static Delay menu

The Rx Static Delay must be compensated during the installation.
Two compensating modes are possible:
Automatic
Manual
The two modes are alternative.

To activate the Automatic mode click on the Align pushbutton (the compensation procedure is
automatically done).
To activate the Manual mode:
[1]
click on the Start pushbutton;
[2]
write the values in the Channel 0/1 fields (N.B.);
[3]
click on the Apply pushbutton to send the value to the NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Write in one field the suitable value (in range 031) and in the other field write 0.
02
3DB 06687 CA AA
304
176 / 304

The Schema Parameters are:
Protection Type field: defines the protection schema architecture: 1+1 Hitless;
Operation Type field: the possible values are revertive (automatic restoration allowed) or
notRevertive (automatic restoration Inhibited).
28.2.3 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 117. on page 177)
or on the Main #1 element (Fig. 118. on page 178).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 117. Radio Protection Switch (Spare #0)
ED
02
3DB 06687 CA AA
304
177 / 304

Fig. 118. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Command
N.B.
ED
Priority
Lockout
Forced
Automatic switch
Manual

02
3DB 06687 CA AA
304
178 / 304
28.3 HST Transmission Protection Management

The Transmission Protection Management is performed selecting Transmission Protection element tree.
The following windows (Fig. 119. on page 179) allows a complete view of all Ne resource involved in a TPS
protection:
Schema Parameters
Channels Parameters
To read the
correct
indication
on the switch
status press
here to refresh
the screen
Fig. 119. Transmission Protection View

1AA 00014 0004 (9007) A4 ALICE 04.10
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).
The operator choice for Operation Type will be applied clicking on Apply button.
ED
02
3DB 06687 CA AA
304
179 / 304
To enter the Commands menu click on the Spare #0 element (Fig. 120. on page 180) or on the Main #1
element (Fig. 121. on page 181) in the Tree view.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 120. Tx Protection Commands (Spare #0)
ED
02
3DB 06687 CA AA
304
180 / 304

28.3.2 Commands

Fig. 121. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Command
N.B.
ED
Priority
Lockout
Forced
Automatic switch
Manual

02
3DB 06687 CA AA
304
181 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
182 / 304
29 LOOPBACKS
1AA 00014 0004 (9007) A4 ALICE 04.10

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 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.
ED
02
3DB 06687 CA AA
304
183 / 304
29.1.1 1+0 Loopbacks

N.B.
The loopbacks can be activated on the local NE only.
N.B.
The DATA block in Fig. 122. is present with the Ethernet port option only.
CT
IDU
IDU
ODU
ODU
DATA
DATA
MUX/
DEMUX
MODEM
RF
RF
MODEM
MUX/
DEMUX
TRIB
TRIB
Fig. 122. 1+0 available loopbacks
Tab. 8. 1+0 loopbacks
No.
Loopback
name
CT selection in
the Resource
Tree Area
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 125. Near End External line Input loopback at tributary level.
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 125. Near End
Internal
Loopback toward the remote

station at tributary level.
Not available.
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 125.
Internal
Loopback in the remote station

at tributary level.
IDU cable
Channel 1
Fig. 125. Near End External line
Loopback at the IDU output at

aggregate level.
ODU
cable
Channel 1
Loopback at the ODU input at

aggregate level.
RF
Channel 1
RF local loopback.
(Note 1)
Ref. to
Fig.
Location
Far End
Loopback
type
Note
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio > Configuration)
1AA 00014 0004 (9007) A4 ALICE 04.10
Note 2: For the DS1/DS3 tributaries refer to Tab. 1. on page 12.
ED
02
3DB 06687 CA AA
304
184 / 304

29.1 Available Loopbacks
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 123. Channel 1 Loopback View
Fig. 124. Tributaries Loopback View
ED
02
3DB 06687 CA AA
304
185 / 304

In the Resource List Area are listed all the loopbacks which can be performed.
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. 125. on page 186 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.
1 Tributaries
(External Line)
IDU
CABLE
ODU
CABLE
6 Radio
port
(RF loop)
2 Channel
(External Line)
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 125. 1+0 Loopback types
ED
02
3DB 06687 CA AA
304
186 / 304

In this area the following information is given:

29.1.2 1+1 Loopbacks
N.B.
The loopbacks can be activated on the local NE only.
N.B.
The DATA block in Fig. 126. is present with the Ethernet port option only.
CT
IDU
IDU
ODU
ODU
DATA
DATA
MUX/
DEMUX
MODEM
RF
RF
MODEM
MUX/
DEMUX
TRIB
TRIB
Fig. 126. 1+1 available loopbacks
Tab. 9. 1+1 loopbacks
No.
Loopback
name
CT selection in
the Resource
Tree Area
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 129. Near End External line Input loopback at tributary level.
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 129. Near End
Internal
Loopback toward the remote

station at tributary level.
Not available.
E1/DS1
Port#xx or
E3/DS3
Tributaries
Fig. 129.
Internal
Loopback in the remote station

at tributary level.
IDU cable
Channel 0 or 1
Loopback at the IDU output at

aggregate level.
ODU
cable
Channel 0 or 1
Loopback at the ODU input at

aggregate level.
RF
Channel 0 or 1
RF local loopback.
(Note 1)
Ref. to
Fig.
Location
Far End
Loopback
type
Note
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio > Configuration).
1AA 00014 0004 (9007) A4 ALICE 04.10
Note 2: For the DS1/DS3 tributaries refer to Tab. 1. on page 12.
ED
02
3DB 06687 CA AA
304
187 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 127. Channel 1 Loopback View
Fig. 128. Tributaries Loopback View
ED
02
3DB 06687 CA AA
304
188 / 304
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. 129. on page 189 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
ODU
CABLE 5 CABLE
Radio port
6 (RF loop)
1 Tributaries
(External Line)
Channel
(External Line)
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 129. 1+1 Loopback types
ED
02
3DB 06687 CA AA
304
189 / 304
N.B.
For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to the
related Channel; for the Tributaries loopbacks must only be forced to the radio switch to Channel
0 or lockout to Channel 1.
To activate a loopback:
[1]
Select the suitable loopback to be activated by clicking on the relevant object in the Resource Tree
Area or by selecting the relevant row in the Resource List Area.
[2]
The screen in Fig. 130. on page 190 will appear. (In this screen has been selected the loopback on
tributary E1, Near End).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 130. Loopback activation

[3]
Select Active in the Activation field.
[4]
Click on Apply.
[5]
The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the relevant
loopback will change from Not Active to Active).
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 minimum.
ED
02
3DB 06687 CA AA
304
190 / 304

29.2 How to activate a loopback
29.3 How to remove a loopback

To deactivate loopbacks use the following steps:

[1]
Select the suitable loopback to be removed by clicking on the relevant object in the Resource Tree
Area or by selecting the relevant row in the Resource List Area.
[2]
The screen in Fig. 131. on page 191 will appear. (In this screen has been selected the loopback on
tributary E1, Near End).
Fig. 131. Loopback removing

[3]
Select Not Active in the Activation field.
[4]
Click on Apply.
[5]
The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the
relevant loopback will change from Active to Not Active).
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING:
When the Loopback commands start the Craft Terminal is not frozen. Before to set another command
is recommended to wait 10 to 25 seconds.
ED
02
3DB 06687 CA AA
304
191 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
192 / 304

210 DIAGNOSIS
In the Diagnosis menu four options are available as shown in Fig. 132.
Fig. 132. Diagnosis menu
210.1 Log Browsing

In the Diagnosis pulldown 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 Operators 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 Operators Handbook.
Software Trace Log option is reserved to the Alcatel technicians.
210.2 Remote Inventory
1AA 00014 0004 (9007) A4 ALICE 04.10
This screen is a readonly screen, which shows all the information on the equipment.
ED
02
3DB 06687 CA AA
304
193 / 304
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
210.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 with or without the Ethernet ports (see Fig. 133. on page 195, Fig. 134. on page 195)
1+1 HST with or without the Ethernet ports (see Fig. 135. on page 196, Fig. 136. on page 196)
1+1 FD with or without the Ethernet ports (see Fig. 137. on page 197, Fig. 138. on page 197)
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.
ED
In the 1+1 configuration the current position of the switches is also shown.
02
3DB 06687 CA AA
304
194 / 304

210.3 Abnormal Condition List
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 133. Summary Block Diagram View: 1+0 without Ethernet ports
Fig. 134. Summary Block Diagram View: 1+0 with Ethernet ports
ED
02
3DB 06687 CA AA
304
195 / 304

1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 135. Summary Block Diagram View: 1+1 HST without Ethernet ports
Fig. 136. Summary Block Diagram View: 1+1 HST with Ethernet ports
ED
02
3DB 06687 CA AA
304
196 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 137. Summary Block Diagram View: 1+1 FD without Ethernet ports
Fig. 138. Summary Block Diagram View: 1+1 FD with Ethernet ports
ED
02
3DB 06687 CA AA
304
197 / 304


By pressing the Refresh button the refresh of the screen takes place (active loopback and performance
and position of the switch).
210.5 Current Configuration View
1AA 00014 0004 (9007) A4 ALICE 04.10
This screen is a readonly screen, which shows the current configuration of the NE.
ED
02
3DB 06687 CA AA
304
198 / 304

211 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.
211.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, DS1, ) 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
Radio Link Section: the section identifying the protected section.
PROPR.
FRAMING
FEC
ENCODE
MODEM
RF
FEC
DECODE
MODEM
RF
PROPR.
FRAMING
Radio Hop (before the switch)

Radio Link (after the switch)
Fig. 139. Radio sections

The counters supported are the following:
Errored Seconds
Severely Errored Seconds
Background Block Error
Unavailable Seconds
The primitives used for the hop section quality monitoring is the ReedSolomon (RS) decoder (block size:
2040 bits). The following table provides, for each frame structure, the main features useful to define a SES.
Tab. 10. SES Thresholds
E3
1AA 00014 0004 (9007) A4 ALICE 04.10
Gross bit rate
[MHz]
16E1
8E1
4E1
2E1
DS3
16DS1
8DS1
4DS1
39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140
RS Blocks number/sec.
19200
19200
9600
4800
2400
28000
14000
7000
3500
SES Threshold (Note 1)
5760
5760
2880
1440
720
8400
4200
2100
1050
(Note 1) Note that according to ITUT 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
02
3DB 06687 CA AA
304
199 / 304

The flow chart shown below illustrates the recognition of anomalies, defects, errored blocks, ES and SES
according to ITUT G.826 (12/2002).
Monitored
second
Yes
Defects?
No
No
Anomalies?
Yes
%EB 30?
ES
(but not a SES)
Yes
SES
(and therefore an ES)
No
Path in
available
State?
Yes
cES = cES + 1
cBBE = cBBE + EB(s)
No
Path in
available
State?
Yes
cES = cES + 1
cSES = cSES + 1
T131379098
End
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 140. Anomalies, defects, errored blocks, ES and SES according to ITUT G.826
ED
02
3DB 06687 CA AA
304
200 / 304
211.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
1AA 00014 0004 (9007) A4 ALICE 04.10
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 of HOP or LINK type. The current report can be seen (and configured) and the history PM log
can be seen.
ED
02
3DB 06687 CA AA
304
201 / 304
[1]
click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click
on LINK to see the LINK report
[2]
click on the desired granularity (15 m or 24 h)
[3]
click on CD (Current Data).
With reference to Fig. 142. on page 202 to see an history log:

[1]
click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click
on LINK to see the LINK report
[2]
click on the desired granularity (15 m or 24 h)
[3]
click on the desired HD (History Data).
To each PM can be associated a threshold table. To associate a threshold table click on HOP or LINK in
the Resource Tree Area in Fig. 142.
Fig. 142. Threshold table association screen
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Counter Thresholds field select the threshold to be associated and click on Apply.
To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select
one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
ED
02
3DB 06687 CA AA
304
202 / 304

With reference to Fig. 142. on page 202 to see (and configure) the current report:

211.3 CD (Current Data)

The window displayed in Fig. 143. on page 203 allows to start and to read the 15min PM report and 24h
PM report.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 143. Current Data View
ED
02
3DB 06687 CA AA
304
203 / 304
The fields displayed in the upper part of Fig. 143. on page 203 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 (readonly) 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 dont have errors.
Num. Interval supp.: number of intervals (reports) suppressed in the History because they dont
have errors.
N.B.
An interval is defined as suspect if at least one of the following conditions occurs in the
collection period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the PM data in the equipment
performance counters have been reset during the interval.
211.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 143. on page 203 (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.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the right part of Fig. 143. on page 203, 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.
ED
02
3DB 06687 CA AA
304
204 / 304

211.3.1 CD parameters

211.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.
211.4.1 HD Parameters
The table displayed on the following window (Fig. 144. on page 205) collects the history data for a related
PM report.
Fig. 144. History Data
1AA 00014 0004 (9007) A4 ALICE 04.10
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).
ED
02
3DB 06687 CA AA
304
205 / 304
211.5 Threshold tables
There are threshold tables for the HOP and for the LINK.
There are two default tables: threshold 1 and 2.
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.
N.B.
For the association of the threshold tables to the PM refer to para. 211.5.3 Threshold table
association.
211.5.1 How to change a threshold table
Fig. 145. Threshold table

Click on the threshold in the Resource Tree Area in the Resource List Area: the threshold screen will
appear.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the upper part of the screen, the Name field displays the name assigned to the threshold table.
In the lower part of the screen, 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.
ED
02
3DB 06687 CA AA
304
206 / 304

This section describes how to see or change or create the threshold tables assigned to PM counters.

211.5.2 How to create a threshold table
Fig. 146. Thresholds Table creation

Click on Threshold Tables HOP (or LINK) node tree in the Resource Tree Area of the Performance view.
The Threshold Data Creation screen will appear.
In the upper part write the name of the new table.
In the lower part write the values for the Low and High thresholds.
To create the new table click on Create.
211.5.3 Threshold table association

To each PM can be associated a Threshold Table.
To associate a Threshold Table click on HOPChannel#0 (or Channel#1) or on LINK in the Resource
Tree Area. The 15min&24h tab panel will appear.
In the Counter Thresholds field select the threshold to be associated and click on Apply.
1AA 00014 0004 (9007) A4 ALICE 04.10
To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select
one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
ED
02
3DB 06687 CA AA
304
207 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
208 / 304

212 SW DOWNLOAD
212.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. 12.3 on page 58.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
the System Default can be changed by writing different values in the fields and then by clicking
on button OK.
02
3DB 06687 CA AA
304
209 / 304
N.B.
The first part of the procedure to download the SW to the NE is shown in para. 12.3 on page
58.
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

Recommended operation:
Before to start the software download it is recommended to disable the

ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.
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
WARNING:
ED
The download time from the CT to the NE flash is 2530 min. approx.
At 50% of this time starts the download to the first ODU, which lasts 1520 min. approx.
At the end of this time interval starts the download of the second ODU, if present, which
lasts 1520 min.
02
3DB 06687 CA AA
304
210 / 304

212.2 Init SW Download
212.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. The committed status refers to the software currently in use.
By clicking on the Software Units Status button the screen of Fig. 149. on page 211 opens, giving
additional information on the software package.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 149. SW Status screen
ED
02
3DB 06687 CA AA
304
211 / 304
EC: software on the Equipment Controller
OC_R: software on the ODU Controller (Radio) (The total download time of the ODU software is 17
to 20 min approx. with some SES after 15 seconds from the activation) (Note 1)
FFENI, FGAIA, FGAEX, FMEDU, FPONT: FPGA firmware version (Note 1)
Note 1:
during the download of the ODU and FPGA software arises the alarm Firmware Download On
Going. This alarm disappears when the download is over. The download lasts 2 minutes for
every FPGA starting from the activation of the alarm.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
212 / 304

The following information is displayed on the screen:

213 MIB MANAGEMENT

213.1 Introduction
This function allows the backup and/or restore of the MIB and is carried out at two levels:
the first is available at NE loggedin level, and allows operations depicted in Fig. 151. below:
NE XXX Flash Card
NE XXX Flash Card
MIB
MIB
MIB BackUp
MIB Restore
NE AAA MIB backup file
NE XXX MIB backup file
NE ZZZ MIB backup file
ECT
ECT
MIB delete
Fig. 151. Allowed MIB management tasks at NE loggedin level

From operative point of view, this management is described in para.27.3 on page 167.
the second is available at Network Element Synthesis level (independently of whether or not the
NE is logged in), and allows operations shown in Fig. 152. below (it depicts save/load using
floppydisk, but the operation can be done through any available read/write computer resource):
Save to
disk
1AA 00014 0004 (9007) A4 ALICE 04.10
ECT
Load from
disk
ECT
Fig. 152. Allowed MIB management tasks at Network Element Synthesis level
From operative point of view, this management and whole applicative examples are described in the
following paragraphs.
ED
02
3DB 06687 CA AA
304
213 / 304
213.2.1 MIB backup on ECT

This operation, carried out by ECT with the NE loggedin, allows to save the MIB from NE to ECT (see
MIB backup in 27.3.1 on page 168).
213.2.2 MIB save to disk
This operation, carried out by ECT through the Network Element Synthesis screen, allows to save MIB
from ECT to a floppy disk.
N.B.
This example depicts the Save to disk by using the floppydisk, but the operation can be done
through any available read/write computer resource.
1)
Launch the task as follows:
Fig. 153. Launch of MIB save to disk

2)
The following screen appears:
in field Look in (1) the PC directory where MIBs are stored is shown
click on Find Now button (2)

1
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 154. MIB save to disk phase 1

3)
ED
The following screen appears:
02
3DB 06687 CA AA
304
214 / 304

213.2 MIB management at Network Element Synthesis level and examples

a table showing the MIBs stored in the PC directory is shown

select the MIB you want to save (3)
click on OK (4)
the usual window to choose a save target directory appears (5); select it and start the save
at save end, a confirmation message is shown (6) indicating also the name of the saved
folder; see N.B. on next page.
3
4
6
5
Fig. 155. MIB save to disk phase 2
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
The saved MIB folder name acronym does not correspond to the name of the MIB that you have
selected to be saved. In order to know such a correspondence open the saved folder: in the
userlbl.txt you can find such name.
Fig. 156. Correspondence between MIB saved folder and MIB saved name
ED
02
3DB 06687 CA AA
304
215 / 304
This operation, carried out by ECT through the Network Element Synthesis screen, allows to load a MIB
previously saved on a floppy disk into ECTs MIB area.
N.B.
This example depicts the Load from disk by using the floppydisk, but the operation can be
done through any available read/write computer resource.
1)
Launch the task as follows:
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 157. Launch of MIB load from disk
ED
02
3DB 06687 CA AA
304
216 / 304

213.2.3 MIB load from disk

2)
After launch of MIB load from disk, proceed as follows:
in the screen that opens, click on Browse button (1)
select the device from which carry out the load operation (2) and open it (3)
in the opened directory (4) , select the MIB folder to load (5) , then click Open (6)
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 158. MIB load from disk phase 1
ED
02
3DB 06687 CA AA
304
217 / 304
... procedure continues
in the screen that opens, click on Find Now button (7)
in the subsequent screen, select the MIB (N.B.) that must be loaded (8), then click on OK
button (9)
at load end, a confirmation message is shown (10) .

N.B.
the MIB name corresponds to that you had previously saved.
10
Fig. 159. MIB load from disk phase 2
213.2.4 MIB restore from ECT
1AA 00014 0004 (9007) A4 ALICE 04.10
This operation, carried out by ECT with the NE loggedin, allows to restore the MIB from ECT to NE (see
MIB restore in para. 27.3.2 on page 169).
ED
02
3DB 06687 CA AA
304
218 / 304

3)
1AA 00014 0004 (9007) A4 ALICE 04.10

SECTION 3: NE MAINTENANCE
SECTION CONTENT
PAGE
Chapter 31 Maintenance introduction
220
Chapter 32 Troubleshooting
221
The symbol
points out references to the other Handbooks.
Referenced handbook P/Ns are given in para.E.2 on page 290 of this handbook.
ED
02
3DB 06687 CA AA
304
219 / 304
This section is the 9400AWY Maintenance Manual; it describes mainly the NE troubleshooting based on
the use of the Craft Terminal.
It applies to 9400AWY SWP Rel.2.0.
The document that should be read before starting this document is:

N.B.
In particular, knowing the contents of section MAINTENANCE of Technical Handbook is

a must.
1320CT Basic Operators Handbook V.3.x
The maintenance procedures consist of the following steps:
PC Maintenance. See para.31.1 herebelow.
Problems with the Craft Terminal PC (shutdown and restart ). See para.31.2 herebelow.
Corrective Maintenance (Troubleshooting). See Chapter 32 on page 221.
31.1 Maintenance of the PC

With regard to the PC maintenance, refer to the constructors documentation.
31.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 operators 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 unsuccessful, carry out the checks indicated in:
1AA 00014 0004 (9007) A4 ALICE 04.10
9400AWY Technical Handbooks

section MAINTENANCE,
chapter SECOND LEVEL MAINTENANCE
paragraph TROUBLESHOOTINGPROBLEMS WITH THE CRAFT TERMINAL
ED
02
3DB 06687 CA AA
304
220 / 304

31 MAINTENANCE INTRODUCTION
32 TROUBLESHOOTING

32.1 Purpose of this procedure

Troubleshooting involves detection, location and correction of the failures occurred in the equipment and
replacement of the defective parts.
32.2 Corrective Maintenance general flowchart

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

Other measures
TroubleShooting 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
another unit
Fault repaired ?
Y
If possible, restore replaced unit in the system and perform
system check via Craft Terminal, to verify that is really faulty
Possible intermittent
failure
N
Fixed fault ?
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 160. Corrective Maintenance general flowchart

For detailed information regarding the whole Corrective Maintenance procedure, please refer to:
9400AWY Technical Handbooks, section MAINTENANCE
chapter SECOND LEVEL MAINTENANCE, paragraph CORRECTIVE MAINTENANCE
ED
02
3DB 06687 CA AA
304
221 / 304
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 (backpanel, 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 NEs 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
In cases 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal.
ED
02
3DB 06687 CA AA
304
222 / 304

32.3 Troubleshooting organization
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. 32.4 on page 224.
To correctly execute the troubleshooting operations the technician must know the equipment
configuration (see Equipment applications on the Craft Terminal).
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
223 / 304
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. 11. on page 225 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 32.4.2 on page 226 explains how to see the alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
224 / 304

32.4 Troubleshooting by means of the Craft Terminal
32.4.1 Alarm synthesis indication

The following troubleshooting table pertains to the alarm and status synthesis given in all the screens.
Tab. 11. Alarm Synthesis indication
Mnemonic
Critical alarm
Synthesis of alarms that needs immediate

troubleshooting (typical: NE isolation). NB1.
MAJ
Major (Urgent) alarm
Synthesis of alarms
troubleshooting. NB1.
MIN
Minor (Not urgent) alarm
Synthesis of alarms for which a deferred intervent

can be decided. NB1.
Warning alarm
Synthesis of alarms due to failure of other NE in the

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

severities. Not operative.
EXTP
External Point
(Housekeeping alarm)
Check the relevant station alarm associated with the

input housekeeping indication.
EQP
Equipment alarm
Synthesis of alarms of the Equipment domain.
Transmission alarm
Synthesis of alarms of the Transmission domain.
Supervision state
GREEN LED: NE is under supervision.

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

the OS permission to manage the NE (granted).
CYAN LED: Indicates that the Craft Terminal has not
the OS permission to manage the NE (denied).
NE reachable/unreachable
GREEN LED: Identifies the Enable operational

state of the connection between NE and Craft Terminal
( SDH service link up ).
RED LED: Identified the Disable operational state
of the connection between NE and Craft Terminal
( service link down ).
AC
Abnormal Condition
GREEN LED: Normal operating condition.

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

equipment MIB.
IND
TRNS
SUP
COM
NB1:
1AA 00014 0004 (9007) A4 ALICE 04.10
Maintenance
CRI
WNG
ED
Alarm / Status Description
that
needs
immediate
The Alarm Profile can modify the assignment of each alarm root to the various synthesis.
02
3DB 06687 CA AA
304
225 / 304
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. 161. on page 226):
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 subnode) in the Resource Tree Area to check if some alarms are active.
[3]
Select the Alarm tab panel in the Resource Detail Area.
[4]
If the node has subnodes put a tick in the Include alarms from subnodes field to display the
alarms active also in the subnodes.
[1]
[2]
[3]
[4]
Fig. 161. Active alarm screen
1AA 00014 0004 (9007) A4 ALICE 04.10
Detailed information of some alarm are supplied.
ED
02
3DB 06687 CA AA
304
226 / 304

32.4.2 Details on alarms / statuses
The following table summarizes the information obtained in the Alarm view, starting from the left column.

Tab. 12. 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. 13. on page 231 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
227 / 304
32.5.1 Analog measurements

In case of two CT connected to the NE, as shown in the figure below, and at the same time both open on
the menu Radio Power Meas, the analog measurements relevant to the PTx rem (Tx power of the
Remote NE) and the PRx rem (Rx power of the Remote NE) could have some instabilities (i.e. an
intermittent +99 dBm is reported for the PTx rem and 99 dBm is reported for the PRx rem).
ODU
Station A
IDU
ODU
Station B
IDU
32.5.2 NMS 64 kbit/s V.11 and G.703

For a correct operation the NMS channel has to be configured in one station as DTE and in the other
station as Codirectional.
This selection can be done in the Quick Configuration Procedure in Step 10 (for NMS V.11 channel) and
in Step 11 (for NMS G.703 channel) or in the Menu Configuration Network Configuration IP
Configuration IP Point to Point Configuration.
32.5.3 Loopbacks
For a correct activation of every loopback (Loopback menu):
the relevant tributary must be enabled (Quick Configuration Procedure Step 3)
the local transmitter must be not muted (Menu Radio Configuration)
Note 1: The loopback will become active after 67 sec. approx. (24 sec. approx. for the RF loopback).
Note 2: The time for a new set is 10 to 25 sec. approx.
1AA 00014 0004 (9007) A4 ALICE 04.10
32.5.4 Empty USM icon in NES

Enter Windows Task Manager and stop the process relevant to the empty USM.
ED
02
3DB 06687 CA AA
304
228 / 304

32.5 Warnings on the troubleshooting

32.5.5 NE unreachable
Due to a deep fading the radio remote NE can be unreachable. In this condition in the USM will appear
the following message:
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.
32.5.6 Configuration change from 4 QAM to 16 QAM

With 16 QAM the max. Tx power must be typically 3 dB below the max. Tx power of the 4 QAM (refer to
the attached Test Result Sheet).
32.5.7 Quick configuration menu correct use
1AA 00014 0004 (9007) A4 ALICE 04.10
The Quick Configuration menu must be used during the first installation to configure completely the NE
and also if some multiple configuration changes must be done (i.e. change of all the tributaries from
Framed to Unframed or viceversa for the E1 signal or from Unframed to Framed SF or Framed
ESF or viceversa for the DS1 signal both in the Local and Remote NE).
ED
02
3DB 06687 CA AA
304
229 / 304
32.6 Description of alarms and of probable causes
N.B.
UNIT REPLACEMENT
After having identified a unit to be replaced, in order to carry out the replacement correctly,
please refer to:
9400AWY Technical Handbooks,
section MAINTENANCE
chapter SECOND LEVEL MAINTENANCE,
paragraph UNIT REPLACEMENT PROCEDURES
WARNING:
1AA 00014 0004 (9007) A4 ALICE 04.10
Before to disconnect the cable IDUODU of N.E., the corresponding IDU unit must be always
turnoff.
ED
02
3DB 06687 CA AA
304
230 / 304

The information provided helps the operator during troubleshooting operations.
Tab. 13. General issues of the alarm meanings and their respective maintenance actions
1AA 00014 0004 (9007) A4 ALICE 04.10

ALARM
MEANING
MAINTENANCE ACTION
AIS
AIS detection on the tributary in Tx Check the tributary connected

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
High BER
Excessive BER
Excessive errors. Check the link

(propagation problem)
Dem fail
Demodulator failure affecting the

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

demodulator input
problem)
Cable LOS
Problem on the cable or on the ODU
Incompatible Frequency
Frequency setting incompatible with Change the frequency or change the

the ODU P/N
ODU
Incompatible PTX
Output power out of the limits
Replace the ODU
Internal Communication
Problem
ODU not responding
Press the Reset pushbutton on the

MAIN unit. If the alarm is still active,
replace the ODU
LAN failure
LAN problem
Check the LAN connection or

replace the MAIN unit
Link Identifier Mismatch
Mismatch on the link identifier
Check the correct connection of the

cable between the IDU and the
relevant ODU. If the connection is
correct, check the link (propagation
problem)
Loss Of Frame
LOF at the Tx tributary input or at Rx

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

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

problem)
Mod fail
Internal modulator failure affecting

Replace the ODU
the modulated signal
ED
Replace the ODU; if the alarm is still

active replace the cable.
02
3DB 06687 CA AA
304
231 / 304
Tab. 13. General issues of the alarm meanings and their respective maintenance actions
1AA 00014 0004 (9007) A4 ALICE 04.10
MEANING
MAINTENANCE ACTION
Mod LOS
No signal at the modulator input
Investigate by using the loopback

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
Mismatch between the installed unit Change the unit configuration or

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
Check the link (propagation

problem)
Threshold Cross
Performance threshold has been

Errors on the link
crossed
Tx Fail (Radio alarm)
Transmitter failure
Unconfigured Equipment
Present
Unit present in an unconfigured slot Configure the unit
Version Mismatch
Mismatch on the software version

Download the software version
between CT software and
equipment software
Housekeeping
Active input housekeeping
ED
Replace the ODU
Check the housekeeping
02
3DB 06687 CA AA
304
232 / 304

ALARM

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.
SECTION CONTENT
PAGE
INFORMATION INDEPENDENT ON THE SPECIFIC SWP VERSIONS

Chapter 41 SWP REG.9400AWY R.2.0 description
This chapter gives information on the Software Packages this handbook refers to,
and that are independent on the specific SWP Version: commercial information
(SWP and Software Licences P/Ns).
235
INFORMATION ON THE SPECIFIC SWP VERSIONS

These chapters give operative information regarding the Software Package Version
2.0.x, starting from version V2.0.0: requirements (PC and equipment Firmware),
Reference Information Model, SW Package Identification, SW Package
Components, ECT SW SubComponent, NE MIB Compatibility, new features,
restrictions and known problems.
Chapter 42 SWP REG.9400AWY R.2.0 V.2.0.0 specific information
237
Chapter 43 SWP REG.9400AWY R.2.0 V.2.0.1 specific information
241
The symbol
points out references to the other handbooks.
1AA 00014 0004 (9007) A4 ALICE 04.10
Referenced handbook P/Ns are given in Appendix E on page 285.
ED
02
3DB 06687 CA AA
304
233 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
234 / 304

41 SWP 9400AWY R.2.0 DESCRIPTION

This chapter gives commercial information regarding the Software Packages this handbook refers to, i.e.
the SWP and Software Licences P/Ns.
41.1 General
The software products are distributed by Alcatel in a CDROM.
In this CDROM 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 EMLULS ).
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.
41.2 Software product list and part numbers

Every Software Product is identified by a denomination and a part number and is distributed by a CDROM
with the same identifiers, listed on the following table:
Tab. 14. Software products part numbers
1AA 00014 0004 (9007) A4 ALICE 04.10
REF
Name
ANV Part Number
Notes
(a)
SWP 9400AWY R.2.0 CDROM
3DB 06690 AA
Software Package
associated to LCT or
RCT SW Licence.
(b)
SWP OPTICSIM WTD SNMP V218 CDROM
3DB 04799 AC
For version 2.0.0
(c)
SWP OPTICSIM WTD SNMP V220 CDROM
3DB 04799 AE
For version 2.0.1
ED
02
3DB 06687 CA AA
304
235 / 304
41.3 OEM Software licence list and part numbers

Every Software licence is identified by a denomination and a part number, listed on the following table.
Tab. 15. Software licence part numbers
Name
ANV Part Number
N.B.
SWLULS R2.0 FEE
3DB 06819 AAAA
SWLLCT 9400 AWY R2.0 FEE
3DB 06820 AAAA
SWLRCT 9400 AWY R2.0 FEE
3DB 06821 AAAA
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Licence for Network Element software features (one per Transceiver):
Licence alternative for Craft Terminal software features:
SWLLCT: local Craft Terminal functionality
SWLRCT: remote Craft Terminal functionality.
02
3DB 06687 CA AA
304
236 / 304

42 SWP REG.9400AWY R.2.0 V2.0.0 SPECIFIC INFORMATION

This chapter gives operative information regarding the Software Package Version 2.0.0: requirements (PC
and equipment Firmware), Reference Information Model, SW Package Identification, SW Package
Components, ECT SW SubComponent, NE MIB Compatibility, new features, restrictions and known
problems.
Please refer to para.E.3.2 on page 294 for the meaning of SWP Release, Version and Patch Level.
With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 286.
N.B.
42.1 ECT requirements

For ECT installation it is necessary a PC with the requirements hereafter described:
1)
HW Configuration
2)
Pentium III 850 MHz

256 Mbytes (512 Mbytes suggested for Windows XP)
4 Gbytes
1024x768 pixel
24X
Serial Port RS232C 9.6 to 57.6 Kbits/sec.
Ethernet Card 10/100 Mbits/sec.
Windows Versions
3)
CPU:
RAM:
Hard Disk space:
Display Resolution:
CDROM Drive:
Primary Interface:
Optional Interface:
Windows 2000 till SP4

Windows XP till SP2: It is mandatory deactivate the Firewall installed.
Windows NT partially supported: CTK 3.2 and related Q3/SNMP addon deliveries can
be run on Windows NT but you have to take in account some restrictions in Almap PC 6.5
and PC 7.0 components. They must be considered as Craft Terminal platform restrictions
in Windows NT environment.
Additional requirements
Netscape Communicator or MS Internet Explorer 4.x or higher.

Java 2 Run Time Environment versions from 1.3.106 to 1.4.104
N.B.
Each specific Java version could require minimal Windows SP installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
Reference SNMPIM version: 2.18 (SGPA 3.4.1).

Related SWP: REF.(b) in Tab. 14. on page 235.
ED
02
3DB 06687 CA AA
304
237 / 304
With reference to the Versions stated on this page, please read carefully the
N.B. on page 286.
N.B.
42.3.1 SW Package Identification

Identification
Version
Date
SWP REG. 9400AWY R2.0
V2.0.0
April 16th, 2005
42.3.2 SW Package Components

Name
Description
Version
SW Package for Radio Regenerator Low Capacity PDH

Equipments AWY Scalable
V2.0.0
SWCECT9400AWY_V20
Equipment Craft Terminal SW Component
V2.0.8
SWCEC9400AWY_V20
Equipment Controller SW Component
V2.0.10
SWCOCR9400AWY_V20
ODU Radio Controller SW Component
V1.7.7
SWCFFENI9400AWY_V20
Fenice FPGA JBC Image File Component
V1.0.13
SWCFGAIA9400AWY_V20
Gaia FPGA JBC Image File Component
V1.0.0
SWCFGAEX9400AWY_V20
GaiaExt FPGA JBC Image File Component
V1.0.2
SWCFMEDU9400AWY_V20 Medusa FPGA JBC Image File Component
V1.0.1
SWCFPONT9400AWY_V20
Ponto FPGA JBC Image File Component
V1.0.1
SWCFD9400AWY_V20
File Descriptor for SW Download Component
V2.0.0
42.3.3 ECT SW SubComponents

Version
Name
JRE
V1.4.104
LLMAN
V3.4.0
Description
Java 2 Run Time Environment
Lower Layers Manager
CTK
V3.2.0 P6
Craft Terminal Base Platform
CTK SNMP AddOn
V3.1.2 P4
Craft Terminal Base Platform SNMP AddOn (EMLIM)
CTK HOL AddOn
V1.1.0 P0
Craft Terminal Base Platform Help OnLine AddOn
CTK NECONF AddOn
V1.25
Craft Terminal NE Type&Release Configuration AddOn
JUSMSNMPCOMMON
V2.0.8
User Service Manager for SNMP MW NEs
JUSMSNMPHELP
V2.0.3
Help OnLine for SNMP MW NEs
CTK Q3 AddOn
V3.1.1 P2
Craft Terminal Base Platform Q3 AddOn (EMLIM)
1AA 00014 0004 (9007) A4 ALICE 04.10
42.3.4 NE MIB Compatibility

Due to different IDU scalable HW platform (9400AWY Rel.2.0), ULS V2.0.0 MIB is not compatible with ULS
V1.0.x MIB (9400AWY Rel.1.0 and 9400FSO Rel.1.0). The NE data must be manually configured.
ED
02
3DB 06687 CA AA
304
238 / 304

42.3 SWP version specific data
1AA 00014 0004 (9007) A4 ALICE 04.10

42.4 New features and modifications
Complete management of IDU scalable HW platform (9400AWY Rel.2.0) for ETSI market
Complete management of 8E1, E3 and Data plugins
N.B.
The IDU hardware of 9400AWY Rel.1.0 and the 9400FSO Rel.1.0 hardware are not supported
by SWP REG. 9400AWY R2.0.
42.5 Restrictions and known problems

This for EC:
a)
It has been temporary inhibited the management of Attended button.

An investigation has to be done in order to verify the state of associated pin.
b)
Restrictions related to configuration with data plugin and frame structure 16E1:
ED
Before changing the configuration FROM 1+0 or 1+1 with 8E1 plugin TO 1+0 or 1+1 with Data
plugin (frameStructure=16E1), it is necessary to disable tributary from 9 to 16 and remove
loopback from trib.9 to trib.16
The inhibition of loopback activation on tributary from 9 to 16 with Data plugin is not
implemented yet.
02
3DB 06687 CA AA
304
239 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
240 / 304

43 SWP REG.9400AWY R.2.0 V2.0.1 SPECIFIC INFORMATION

This chapter gives operative information regarding the Software Package Version 2.0.1: requirements (PC
and equipment Firmware), Reference Information Model, SW Package Identification, SW Package
Components, ECT SW SubComponent, NE MIB Compatibility, new features, restrictions and known
problems.
Please refer to para.E.3.2 on page 294 for the meaning of SWP Release, Version and Patch Level.
With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 286.
N.B.
43.1 ECT requirements

They are the same as for V2.0.0 (for details, refer to para.42.1 on page 237).

Reference SNMPIM version: 2.20 (SGPA 3.4.2).
Related SWP: REF.(c) in Tab. 14. on page 235.
43.3 Equipment hardware requirements
1AA 00014 0004 (9007) A4 ALICE 04.10
Please refer to para.12.1.1 point [2] on page 57.
ED
02
3DB 06687 CA AA
304
241 / 304
43.4 SWP version specific data
8BW03051 0033 FMZZA ED.03 25/10/2005 (Release Note SWP REG.9400AWY R.2.0)
With reference to the Versions stated in this paragraph, please read carefully
the N.B. on page 286.
N.B.
43.4.1 SW Package Identification

Identification
Version
Date
V2.0.1
Oct 11th, 2005
43.4.2 SW Package Components

Name
Description
Version
SW Package for Radio Regenerator Low Capacity PDH

Equipments AWY Scalable
V2.0.1
SWCECT9400AWY_V20
Equipment Craft Terminal SW Component
V2.1.5
SWCEC9400AWY_V20
Equipment Controller SW Component
V2.1.8
SWCOCR9400AWY_V20
ODU Radio Controller SW Component
V2.2.17
SWCFFENI9400AWY_V20
Fenice FPGA JBC Image File Component
V1.0.16
SWCFGAIA9400AWY_V20
Gaia FPGA JBC Image File Component
V1.0.0
SWCFGAEX9400AWY_V20
GaiaExt FPGA JBC Image File Component
V1.0.6
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
SWCFMEDU9400AWY_V20 Medusa FPGA JBC Image File Component
V1.0.1
SWCFPONT9400AWY_V20
Ponto FPGA JBC Image File Component
V1.0.1
SWCFGAAE9400AWY_V20
Gaia AE FPGA JBC Image File Component
V2.0.1
SWCFGAAX9400AWY_V20
GaiaExt AE FPGA JBC Image File Component
V2.0.1
SWCFD9400AWY_V20
File Descriptor for SW Download Component
V2.0.1
02
3DB 06687 CA AA
304
242 / 304

NOTE FOR ALCATEL INTERNAL USE: information in this chapter is retrieved from document:
43.4.3 ECT SW SubComponents

Name
ISIPSOSPPC
Version
V2.5.0F P135
Description
PSOSsystem Library for PQUICC processors
TLXSLXDDPPC
V8.1.0.P128
Platform tools and script file for SUN Solaris
KSPQ1GECRC
V8.1.0 P136
Kernel Subsystem Generic Part for PQUICC
KSPQ1SECRC
V8.1.0 P135
Kernel Subsystem EC Specific Part for PQUICC
RWLPQ1SECRC
V8.1.0
Raw Loader EC Specific for PQUICC
CSPQ1GENQB3
V7.3.3
Q3 Interface Management Generic Part for PQUICC
CSPQ1GEN8021E
V8.1.0.P10
Client Download Module Library for PQUICC
MGTPQXGEN
V9.0.0.P20
IP Management
CSPQXGENRTG
V9.0.0.P11
OSPF & RIP Routing Protocols Management
CSPQ1GENSNMPV91
V7.3.2
SNMP Protocol Management
KSPQ1GENIPNTP
V7.2.1
NTP Management
VFSPQ1GEN
V8.1.0
File System for PQUICC
DMMAGEN
V7.1.1
DM and MA Generic Part for PQUICC
GRFPRECOMPSLX
V1.0.0
GRF PreCompiler Product for SUN Solaris
GRFRUNTIMEPQ1
V1.0.0
GRF RunTime Library for PQUICC
INTECOC
V1.1.20
ECOC IDU/ODU Interface
SVIINTERFACE
V10.2.0
SNMP Virtual Interface
SGPA
V3.4.1
SNMP Generic Program Agent for 2G Radio Equipments
VHM
V2.1.8
Virtual Hardware Module
43.4.4 NE MIB Compatibility
1AA 00014 0004 (9007) A4 ALICE 04.10
NE MIB is compatible with previous release 2.0.0.
ED
02
3DB 06687 CA AA
304
243 / 304
43.5 New features and modifications
[1]
This for ECT:

1)
Warning message on Set Frequency Parameters
2)
Warning message on TX Mute function
3)
USM instability: alarm surveillance improvement.
4)
Quick Configuration improvement: shifter management
5)
Quick Configuration improvement: pause after change of NE type from 1+0 to 1+1 and
viceversa
6)
Summary Block: block of NMS alarm has been added
7)
OSPF area management: mask information has been removed
8)
MIB management menu: Restore and Activation improvement
9)
Alarm Loss of GFP on Ethernet Port egressing (Rx Side) is reported at CT
10 ) Link Identifier has been removed from System Settings parameters

11 ) Added management of allowedDS1LineLenght table
12 ) Improvement management of Frequency Shifter
13 ) Improvement management of Static Delay
14 ) Removed inhibition in 8E1/DS1 ETH configuration to allow DS3 frame structure
15 ) Solved problems on Rx NEAREND loopback for FCC configuration
16 ) NEType allowed list improvement
17 ) QC: added shifter management
18 ) GFPCon alarm improvement
19 ) Power Meas graph improvement
20 ) Configuration View: data parameters
21 ) New Frequency Shifter management
1AA 00014 0004 (9007) A4 ALICE 04.10
22 ) PMDS improvement (SH only)
ED
02
3DB 06687 CA AA
304
244 / 304

With respect to previous SWP V2.0.0, new features and modifications are:

[2]
This for EC:

1)
The functionality of automatic EPLD download (GAIA and GAIA_AE) has been removed,
because it has been verified that, for GAIA components, the reading of EPLD version (made
by IDUSW during restarts and after board poweron) creates impacts on traffic.
2)
To avoid strictly dependencies to HW codes, it has been changed the algorithm used to
enable/disable the automatic FPGA/EPLD download and to enable/disable ATTENDED button
(based on remote inventory contents): for this reason, to avoid unexpected behavior, before
activate new SW package 2.0.1h it has to be kept attention on remote inventory of the boards.
The automatic FPGA/EPLD download and the attended button are DISABLED ONLY on boards
ED.2 and on boards ED.3, and, as consequence, they are ENABLED in ALL OTHER CASES.
These editions are recognized by means of UNIT PART NUMBER (stored in remote Inventory);
the automatic FPGA/EPLD download it is DISABLED ONLY when the contents of UNIT PART
NUMBER is one of the following:
MULDEM MAIN: 3DB06395AAAA
MULDEM EXTENSION : 3DB06404AAAA

The download can be anyway disabled putting the file NOAUTOSWDW under
/home/admlcng/debug folder, but the management of the attended button CANNOT be
disabled and using boards without the right management of this button there could be
misalignment on alarm management (both on NMS and on leds).
1AA 00014 0004 (9007) A4 ALICE 04.10
It has been also changed the algorithm used to recognize different GAIA components
(GAIA/GAIA_AE): it is retrieved idCode directly from GAIA and this information is used to select
the right file image to download.
3)
Inserted filter of EarlyWarning alarm in case of nearend E3/DS3 loopback presence
4)
Updated HBER threshold values (FENICE) in ANSI configurations (4/8/16DS1 and DS3) with
the same values used for ETSI market.
5)
It has been inserted a check on backup contents (during restore operation) to verify if the
configuration saved is compatible with SW key: for this reason it has been changed the
database and backup made with previous prerelease are no more compatible if it is used a
SW KEY different from FULLFLEXIBLE.
6)
6) Inserted new management in case of change of ETH rate 10/100 or 100/10

This behavior can be disabled putting the file noMedusaSpeed in /home/admlcng/ debug
folder (the file is read ONLY during EC startup)
7)
Inserted filter of EarlyWarning alarm in case of IDU cable loopback presence
8)
Inserted modifications on versions check for FPGA/EPLD automatic download
9)
A modification in EC database has been made; for this reason in case of downgrade to previous
EC version there could be some problems related to NOT ENABLED pointToPoint interfaces:
after downgrade all pointToPoint are enabled (they can be deactivated by CT/NMS).
10 ) The automatic FPGA/EPLD download HAS BEEN ENABLED ONLY ON BOARD ED.4
The edition is recognized by means of UNIT PART NUMBER (stored in remote Inventory):
MULDEM MAIN : 3DB 06395 AAAB and 3DB 06395 ABAA
MULDEM EXTENSION : 3DB 06404 AAAB and 3DB 06404 ABAA

The download can be disabled putting the file NOAUTOSWDW under /home/admlcng/ debug
folder.
ED
02
3DB 06687 CA AA
304
245 / 304
12 ) Inserted management of EXAR Low Cost (modified EXAR default configuration).

13 ) Inserted management of ODUSMT (it is managed as standard ODU).
14 ) Inserted management to mask IDUODU driver read (B_FULL inhibition) when IDU cable
loopback is executed.
15 ) Inserted inhibition of LinkIdentifier enable and updating.
16 ) Reported all modifications and improvements inserted in new SWP AWY 1.0.2 (Telus version):
Inserted retry (5) on Pegaso (SPI) read in case of fail, before declare card fail alarm
The successfully retries are traced on SWTrace log file in the following way Recovered
error in reading Pegaso reg#x ch#y after n retry.
In case of Loss of Signal on tributary #1 and #9 a check on exar register #0 contents is

done: in case the content is not the expected the register is reconfigured and a specific
trace is inserted on SWTrace log file.
After a card fail (both HW or SW) the board is completely reconfigured .
Inserted traces in SWTrace log file to trace all card fail detection.
17 ) Resolved problem in management of CONF_SW_RPS_KO pin on Gutturnio after EXTENSION
switchoff/disconnection and connection with EXTENSION powered off.
18 ) Resolved problem related to usage of addresses 0.0.0.x in OSPF .
19 ) Alignment to Ominx Scalable 1+0 and 1+1 ANSI files Ed.2
20 ) The automatic FPGA/EPLD download HAS BEEN ENABLED ONLY ON BOARD ED.4
The edition is recognized by means of UNIT PART NUMBER (stored in remote Inventory):
MULDEM MAIN : 3DB06395AAAB
MULDEM EXTENSION : 3DB06404AAAB

The download can be disabled putting the file NOAUTOSWDW under /home/admlcng/ debug
folder.
21 ) Added management of new GAIA/GAIA_EXT image files (for new Altera components): new
components are mounted ONLY on boards ED.4 and are recognized by means of ICS (stored
in remote inventory):
ICS 2 identify new GAIA/GAIA_EXT components

22 ) Added alarm notification during FPGA/EPD download
23 ) Enabled ATTENDED button management only on boards ED.4
This remove the restriction present in previous prereleases and in release 2.0 (It has been
temporary inhibited the management of Attended button)
24 ) Added management of Clock 39Mhz alarm as CARD FAIL root
1AA 00014 0004 (9007) A4 ALICE 04.10
25 ) Updated management of CONF_SW_RPS_KO pin: EXT card missing alarm and fail on
CYPRESSHITLESS configuration are taken into account.
26 ) Inserted management of specific forcing commands for EPS and HST protection: these
commands are used during maintenance operation on MAIN MULDEM board (pin MAIN3 and
MAIN4).
ED
02
3DB 06687 CA AA
304
246 / 304

11 ) Inserted management of Transparent Ethernet (1530 bytes) (modified Medusa default

configuration)

27 ) Inserted management for specific maintenance operation on MAIN board: to avoid earlier
switch of RPS protection on main board (in case ODU is not yet configured), the switch is
permitted ONLY at the end of ODU configuration. This mechanism has been implemented using
FAIL_ODU_MAIN pin on Gutturnio: this pin is put in FAIL state when ODU ch#1 is disconnected
or when CARD FAIL is detected on MAIN MULDEM board. The pin is put in ACTIVE state when
the alarm is switched off and ODU is configured.
28 ) Updated HW configuration for SERVICE CHANNELS
29 ) Added management of allowedDS1LineLenght table
30 ) Added management of flexible delay during ODUSW download: different delay time is used
according to ODUSW running .
31 ) Improvement management of allowedFrequencyShifter table update
32 ) Improvement management on FrequencyShifter update in 1+1HST
33 ) Improvement management on LABEL associated to PdhFrameHOPThresholdData and
PdhFrameLinkThresholdData
34 ) Improvement management on Market change: the frameStructure is automatically updated
(the little frame allowed by SWKEY is chosen)
This remove the restriction present in previous prerelease (The market change has to be
executed with Quick Configuration and not with System Setting menu)
35 ) Solved problems on DATA plugin (Medusa registers corruption)
36 ) Solved problems on FAREND loopback
37 ) Solved problem to permit many restore operations before the backup activation (MIB
management)
38 ) Added management of 1+1 FCC configuration (Ominx Scalable 1+1 ANSI files Ed.1)
For information related to supported HW configuration refer to release note inserted in Omnix
Scalable 1+1 ANSI files
Management of all equipment configurations (DS1/DS3/DATA)
Tributary management and specific DS1 parameters: LineCode and LineLenght
Loopback management
Performance Monitoring management

39 ) Added management of IFTable
40 ) Added management of ODUSW not compatible with new shifter messages: in this case new
messages are not sent. This behavior is active during SWMISMATCH
1AA 00014 0004 (9007) A4 ALICE 04.10
41 ) Added management of MIB upgrading changing FROM 1+0 or 1+1 with 8E1 plugin TO 1+0
or 1+1 with DATA plugin (frameStructure=16E1):
Tributary from 9 to 16 are automatically disabled
Loopback active on tributary from 9 to 16 are automatically removed

42 ) Added management of 1+0 FCC configuration (Ominx Scalable 1+0 ANSI files Ed.1):
Management of all equipment configurations
Tributary management and specific DS1 parameters: LineCode and LineLenght
Loopback management
Performance Monitoring management
ED
02
3DB 06687 CA AA
304
247 / 304
44 ) Improvement management of Filter History Data retrieval (this function can be enabled only
from NMS manager)
45 ) Improvement management on radio measurement function
46 ) Improvement on ODUSW download: reduced pause time between each block to speedup
the transfer.
[3]
This for ODU:

1)
Upgrade of MRU boards part number
2)
ODU 78 Implementation of exception cases for shifter management
3)
SWPN 3CC14614AAAA
4)
ODU 78 new parameter to calculate Prx
5)
Exotix shifters case for 8 GHz (precision 10khz instead of 1Mhz)
6)
EEPROM address on MRU board same as TIFU board
7)
No alarm after shifter update
8)
Add new boards remote inventories
9)
Tx Power shutdown on IDU/ODU com failure
10 ) Data clock inversion only on CR boards (Perseo parameter)

11 ) Add new boards remote inventories
12 ) Data clock inversion only on CR boards (Perseo parameter)
43.6 Restrictions and known problems

This for ECT:
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
ED
For Windows 2000 and Windows XP it is mandatory set Power schemes equal to Always
On into Power Options Properties.
02
3DB 06687 CA AA
304
248 / 304

43 ) Solved problem related to maintenance action on MAIN board: during EC restart the KTPS
command is checked and maintained.
1AA 00014 0004 (9007) A4 ALICE 04.10

SECTION 5: APPENDICES
ED
SECTION CONTENT
PAGE
Appendix A Equipment description and components

This Appendix sumsup the equipment functions and defines its components from
the SW point of view.
251
Appendix B SW allocation, Flash Card and equipment control

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

This Appendix introduces the basic information regarding the software installation.
271
Appendix D ECTEquipment connection via public switched telephone

network
This Appendix explains the operations necessary to allow the remote connection to
the FInterface, from a local PC configurated as ECT, through a switched telephone
line of the standard Public Telephone Network.
275
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
the list of the handbooks the Operators should have in order to carry out the required
operations.
285
Appendix F Acronyms and abbreviations
297
Appendix G Glossary of terms
301
02
3DB 06687 CA AA
304
249 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
250 / 304

APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS

Please refer to Tab. 1. on page 12 for system features and SWPversion relationship
This appendix sumsup the equipment functions and defines its components from the SW point of view:
Functions and configurations
on page 252
IDU and ODU Components
on page 253:
IDU
on page 254
ODU
on page 254
Allowed Equipment Types
on page 255
Remote Inventory Management
on page 257
Equipment Protection Switching Management on page 257
External Points Management
on page 258
For more detailed in formation from the hardware point of view, please refer to:
9400AWY Rel.2.0 Technical Handbook (REF.[A] on page 291) from ED.02
1AA 00014 0004 (9007) A4 ALICE 04.10
From the software point of view, the equipment management is carried out as explained in Section 2
NE MANAGEMENT on page 75, in chapters relevant to the EQUIPMENT CONFIGURATION
MANAGEMENT .
ED
02
3DB 06687 CA AA
304
251 / 304
ULS NE has the aim to multiplexer/demultiplexer the main tributaries (up to 16xE1 / 16xDS1 or 1xE3 /
1xDS3) with different modulation formats.
The following Tab. 16. resumes the relation among market, tributaries and modulation.
Tab. 16. Markets, tributaries and modulations forecasted
Market
ETSI
ANSI
Tributary
Modulation
2xE1
4QAM
4xE1
4QAM / 16QAM
8xE1
4QAM /16QAM
16xE1
4QAM / 16QAM
1xE3
4QAM / 16QAM
4xDS1
4QAM
8xDS1
4QAM /16QAM
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. 16. above) 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 channelassociated 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

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
ULS NE can be composed by:
one radio channel (1+0 configurations);
two radio channels (1+1 configurations).
1AA 00014 0004 (9007) A4 ALICE 04.10
The 2+0 configuration is not supported.
ED
02
3DB 06687 CA AA
304
252 / 304

A.1 : Functions and configurations

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.
9400AWY R.2.0 1+0 SPLITMOUNT SYSTEM

ODU Ch#1
Antenna
ODU
IDUODU cable
NE
ULS
IDU
MAIN SHELF
IDU Ch#1
9400AWY R.2.0 1+1 SPLITMOUNT SYSTEM

ODU Ch#0
ODU Ch#1
Antenna
Antenna
ODU
IDUODU cables
NE
ULS
EXTENSION SHELF
IDU Ch#0
IDU
1AA 00014 0004 (9007) A4 ALICE 04.10
MAIN SHELF
IDU Ch#1
Fig. 162. 9400AWY R.2.0 splitmount system
ED
02
3DB 06687 CA AA
304
253 / 304
The indoor part is composed by one or two units/shelves (see Fig. 162. on page 253):
IDU Main Unit

Ch#1
IDU Extension Unit

Ch#0
[1]
IDU Main Unit

The IDU Main unit is used both in 1+0 and 1+1 configurations.
Four different types of IDU Main Unit are envisaged (with different P/Ns):
IDU Main Unit for ETSI market, for 24 V Power Supply
IDU Main Unit for ETSI market, for 48/60 V Power Supply
IDU Main Unit for ANSI market, for 24 V Power Supply
IDU Main Unit for ANSI market, for 48/60 V Power Supply
The IDU Main Unit provides the external interfaces for the 8xE1 (ETSI version) or 8xDS1 (ANSI
version) tributaries, user service channel, housekeeping and summarizing alarms, NMS V11 and
G703 interfaces and a telephone jack. It contains the MONOM, the PQECRC and the Power Supply
units. The MONOM unit manages 8E1/DS1 tributaries, the Mux/Demux and the cable interface
functions. The PQECRC unit implements the Equipment and IDU Controller functions.
[2]
a)
Software Key on IDU Main unit

A Software Key (Flash Card) is always plugged onto the Main board allowing flexibility in
choosing user interfaces. Refer to para.B.2 on page 262 for details.
b)
Optional plugin unit for IDU Main unit

An optional plugin unit (alternative between them, with different P/Ns) for:
additional 8xE1 plugin or 8xDS1 plugin
or 1xE3 plugin or 1xDS3 plugin
or Data plugin implementing Ethernet interfaces

can be plugged onto the IDU Main unit.
IDU Extension Unit

The IDU Extension Unit is used only in 1+1 configurations.
Four different types of IDU Extension Unit are envisaged (with different P/Ns):
IDU Extension Unit for ETSI market, for 24 V Power Supply
IDU Extension Unit for ETSI market, for 48/60 V Power Supply
IDU Extension Unit for ANSI market, for 24 V Power Supply
IDU Extension Unit for ANSI market, for 48/60 V Power Supply
The IDU Extension Unit contains the MONOE, the Power Supply and the Hitless Switch units.
c)
Optional plugin unit for IDU Extension unit

An optional plugin unit (alternative between them, with the same P/Ns of those envisaged for
the IDU Main Unit) for:
additional 8xE1 plugin or 8xDS1 plugin
or 1xE3 plugin or 1xDS3 plugin

must be plugged onto the IDU Extension unit, when the same type of plugin unit is equipped
on the IDU Main unit .
Note: even if equipped on the IDU Main unit, Data plugin is not envisaged on IDU Extension
unit.
1AA 00014 0004 (9007) A4 ALICE 04.10
A.2.2 : ODU
According to the configuration type, one or two electrical ODU are managed in the Outdoor part. Each ODU
contains a PQECRC unit. It implements the ODU controller functions.
ED
02
3DB 06687 CA AA
304
254 / 304

A.2.1 : IDU

A.2.3 : Allowed Equipment Types

This paragraph provides information on the allowed equipment types for all the configurations supported
by ULS NE.
In the following tables, the list of allowed equipment types for each physical position, includes the whole
set of possible types, but, according to the NE configuration defined by the managers, only one value will
be present for each physical position.
N.B.
[1]
Both IDU and ODU shelves are numbered inside a virtual rack (equipmentPosition = 1). All the
IDUs, ODUs and contained positions will be numbered accordingly.
Shelves Equipment Types
The following Tab. 17. provides the shelves equipment types allowed for each supported NE
configuration (see support domain section for the list of supported configurations).
The shelves are numbered according to the following sequence rule:
IDU Ch#1
ODU Ch#1
IDU Ch#0
ODU Ch#0
Tab. 17. Shelves Equipment Types

NE
Configuration
1+0
1+0 ETH
(note 2)
Market
Type
Position
Allowed Equipment Type

Description
Allowed
Equipment
Type
Equipment
Label
(note 1)
1.1.0.0
IDU Main Shelf
IDUM
IDU Ch#1
ODU 1+0 4/16 QAM ETSI
ODUE
ODU Ch#1
ODU 1+0 4/16 QAM ANSI
ODUA
IDU Main Shelf
IDUM
IDU Ch#1
ODUE
ODU Ch#1
ODUA
IDU Extension Shelf
IDUE
IDU Ch#0
ODUE
ODU Ch#0
ODUA
ETSI
1.2.0.0
ANSI
(note 1)
1.1.0.0
ETSI
1.2.0.0
1+1
(note 3)
ANSI
(note 1)
1.3.0.0
ETSI
1.4.0.0
ANSI
(note 1) The equipment types allowed for IDU shelf are market type independent.
(note 2) All the 1+0 configurations.
1AA 00014 0004 (9007) A4 ALICE 04.10
(note 3) All the 1+1 configurations.
ED
02
3DB 06687 CA AA
304
255 / 304
[2]
Slots and Subslots Equipment Types
1)
IDU
IDUM
Tab. 18. Allowed board/plugin types in IDU Main shelf

Position
1.1.1.0
1.1.1.1
Allowed Equipment Type Description
Allowed
Equipment
Type
Main Unit 24 V Supply
M24S
Main Unit 48/60 V Range Supply
M4860S
8xE1/DS1 plugin unit
P8E1DS1
P1E3DS3
2xEthernet plugin unit
P2DATAS
Equipment Label
IDU/MAIN Ch#1
IDU/MAIN/<note 1> Ch#1
(note 1) The label is one of the following:
E1, when the 8xE1/DS1 plugin is provisioned and it configured to work in E1 mode
DS1, when the 8xE1/DS1 plugin is provisioned and it configured to work in DS1 mode.
DATA, when the 2xDATA plugin is provisioned.
IDUE
Tab. 19. Allowed board/plugin types in IDU Extension shelf
Position
1.3.1.0
Allowed Equipment Type Description
Allowed
Equipment
Type
Ext. Unit 24 Supply
E24S
Ext. Unit 48/60 V Range Supply
E4860S
P8E1DS1
P1E3DS3
Equipment Label
IDU/EXT Ch#0
1.3.1.1
IDU/EXT/<note 1> Ch#0
(note 1) The label is one of the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
2)
ODU
No slot can be defined inside the Electrical ODU.
ED
02
3DB 06687 CA AA
304
256 / 304

The following tables indicate the allowed equipment types for each slot inside each shelf type.

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 are provided by the following equipment
types:
Main Unit
(M24S, M4860S)
Extension Unit
(E24S, E4860S)
Ethernet plugin
(P2DATAS)
PDH Tributary optional plugsin

(P8E1DS1, P1E3DS3)
ODU unit
(ODUE, ODUA)
For all the other equipment types the remoteInventoryStatus columnar object assumes the value
unavailable.
The RI data of each subcomponents unit (i.e. MONOM in the IDU, MILOU in the ODU) cannot 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 must be 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 is not possible to read the Remote Inventory information, a Card Fail alarm is declared.
A.3 : Equipment Protection Switching Management

Just one EPS protection scheme is supported. It provides protection both of the PDH multiplexer and of
the demultiplexer functional blocks.
The following Tab. 20. defines the characteristics of this protection scheme.
Tab. 20. Characteristics of the protection scheme
Parameter Type
Value
Protection group type
1+1
Switching type
Single ended
Restoration criteria
Revertive/Non Revertive
Switching condition
Equipment failures
Operator commands
Lockout spare Forced switch from main to spare Manual

switch from main to spare and viceversa
1AA 00014 0004 (9007) A4 ALICE 04.10
The configuration of this protection scheme is performed by the NE in conjunction with the equipment
provisioning process (declaration of boards).
ED
02
3DB 06687 CA AA
304
257 / 304
ULS NE has the capability to monitor 6 input contacts (housekeeping alarms) and 4 output contacts
(housekeeping controls).
The polarity of each external point can be configured through the SNMP management interface.
External output points can be automatically controlled by the agent or manually used by the operator. In
the first case the event that controls the output state is assigned by the operator. The allowed events are
defined in the following table:
Allowed
Event Id
Allowed Event
Allowed Event description
Major Alarm
OR of critical and mayor alarms
Minor Alarm
OR of minor and warning alarms
Service Affecting Alarm
OR of service affecting alarms
Line side LOS Alarm
OR of PDH tributaries and Ethernet interfaces LOS alarms
Cable Loss IDU Alarm
OR of cable loss IDU alarms
Radio Signal Fail Alarm
OR of radio signal fail and HBER alarms
Local Defect Indication
see Technical Handbook for the primitives
Remote NE Failure Indication
see Technical Handbook for the primitives
Also the summarizing alarms are managed via SNMP interface. They are managed according to the rules
described in the following table:
Index
Value
UserLabel
External
State
Polarity
Criteria
Automatic
Event
Automatic
Event Id
Readwrite
Readonly
Read
write
Read
only
Readonly
Readonly
Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Fail IDU
All the 1+0

All the 1+1
All the 1+1
on/ off
activeLow/
activeHigh
automatic
Fail ODU
Ch#1
Fail ODU
Ch#0
02
3DB 06687 CA AA
304
258 / 304

A.4 : External Points Management

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 262
the general characteristics of the ECT and RECT, on page 269.

Fig. 163. herebelow shows the Interfaces for equipment control
Fig. 164. herebelow shows the FLASH CARD position on back side of MAIN unit
Fig. 165. herebelow shows the FLASH CARD profile and insertion direction
Flash card
label
Ethernet Interface
for OS connection
F Interface
for ECT connection
Fig. 163. MAIN Unit front side: interfaces for equipment control and FlashCardlabel position
Flash card
Flash card cover
Fig. 164. MAIN Unit back side: Flash Card position
CONNECTOR
SIDE
INSERTION
TOP SIDE
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 165. Flash Card profile and insertion direction
ED
02
3DB 06687 CA AA
304
259 / 304
Fig. 166. herebelow roughly depicts the NE main parts containing the local SW and the interfaces with the
Operator (Extension Unit and RT0 are present in 1+1 configuration and are not equipped in 1+0
configuration).
MAIN UNIT
PQ/ECRC SUBUNIT
FLASH
CARD
F
Ethernet
EQUIPMENT
CONTROLLER
RAM
MONOM
SUBUNIT
EXTENSION UNIT
MONOE
SUBUNIT
RT0
FLASH
EPROM
ODU
CONTROLLER
RAM
RT1
FLASH
EPROM
ODU
CONTROLLER
RAM
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 166. Equipment main parts containing local SW
ED
02
3DB 06687 CA AA
304
260 / 304

B.1 : Allocation of equipment and craft terminal software

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:
a)
SW resident in Equipment Controller and Flash Card

Whole Equipment SW (programs and configuration data) is contained in the Flash Card housed in
MAIN units PQ/ECRC subunit (the Flash Card contains also the software (programs and
configuration data) relevant to the peripheral units, i.e., in the figure RTs). See Fig. 164. and
Fig. 165. on page 259.
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, as shown in Fig. 167. on page 267, the Flash Card contains two independent
instances of the Equipment SW programs (one active, the other standby), so that the above cited
SW download is actually done toward the standby instance, while equipment goes on working with
the SW programs of the active instance. Swapping between the two instances is done only under
Operators request.
b)
SW resident in 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
activestandby duplication described before for the Equipment Controller.
c)
Equipment Configuration Data
1AA 00014 0004 (9007) A4 ALICE 04.10
The whole equipment configuration data (together with programs) are stored in the MAIN unit
PQ/ECRC subunit Flash Card. Refer to point B.2.3 on page 267 for details.
ED
02
3DB 06687 CA AA
304
261 / 304
B.2 : Flash Card
B.2.1 : Flash Card types

A FLASH CARD is plugged into the Main board (see Fig. 164. on page 259) allowing flexibility in choosing
user interfaces as in the following Tab. 21. (6 possible types of Flash card):
Tab. 21. Available Flash cards for 9400AWY Rel.2
NAME
P/N
4E1DS1 4 QAM FLASH CARD
3DB 06571 AA
4E1DS1 4/16 QAM FLASH CARD
3DB 06572 AA
8E1/DS1 4 QAM FLASH CARD
3DB 06606 AA
8E1/DS1 4/16 QAM FLASH CARD
3DB 06607 AA
4 QAM FLASH CARD
3DB 06573 AA
FULL FLEXIBLE FLASH CARD
3DB 06574 AA
The following tables show the possible combinations of interface types and numbers that can be supported
by each of the six types of flash cards defined in Tab. 21. above:
Tab. 22. on page 263, to be used when no tributary plugin is equipped
Tab. 23. on page 264, to be used when tributary 916 E1/DS1 plugin is equipped
Tab. 24. on page 265, to be used when tributary E3/DS3 plugin is equipped
Tab. 25. on page 266, to be used when Ethernet plugin is equipped
1AA 00014 0004 (9007) A4 ALICE 04.10
B.2.2 : Flash Card identification
ED
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. 163. on page 259).
02
3DB 06687 CA AA
304
262 / 304


Tab. 22. Capacity and modulation for 9400AWY R.2.0 flash cards (IDU basic)
Flash Card Name
4E1DS1 4QAM
4E1DS1 4/16QAM
8E1DS1 4QAM
8E1DS1 4/16QAM
4QAM
1AA 00014 0004 (9007) A4 ALICE 04.10
FULL FLEXIBLE
ED
without plugin (IDU basic)
Int.N#
& type
Supported configuration
Supported modulation
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
16E1
na
na
16DS1
na
na
E3
na
na
DS3
na
na
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
16E1
na
na
16DS1
na
na
E3
na
na
DS3
na
na
02
3DB 06687 CA AA
304
263 / 304
Tab. 23. Capacity and modulation for 9400AWY R.2.0 flash cards (with 916 E1/DS1 plugin)
4E1DS1 4QAM
4E1DS1 4/16QAM
8E1DS1 4QAM
8E1DS1 4/16QAM
4QAM
with 916 E1/DS1 plugin
Int.N#
& type
Supported Modulation
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
16E1
1E116E1
4 QAM

Flash Card Name
FULL FLEXIBLE
16DS1
1DS116DS1
4 QAM
E3
na
na
DS3
na
na
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
16E1
1E116E1
4 and 16 QAM
16DS1
1DS116DS1
4 and 16 QAM
E3
na
na
DS3
na
na
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
264 / 304
Tab. 24. Capacity and modulation for 9400AWY R.2.0 flash cards (with E3/DS3 plugin)

Flash Card Name
4E1DS1 4QAM
4E1DS1 4/16QAM
8E1DS1 4QAM
8E1DS1 4/16QAM
4QAM
1AA 00014 0004 (9007) A4 ALICE 04.10
FULL FLEXIBLE
ED
with E3/DS3 plugin
Int.N#
& type
Supported Modulation
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 QAM
8E1
1E18E1
4 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 QAM
16E1
na
na
16DS1
na
na
E3
E3
4 QAM
DS3
DS3
4 QAM
2E1
1E12E1
4 QAM
4E1
1E14E1
4 and 16 QAM
8E1
1E18E1
4 and 16 QAM
4DS1
1DS14DS1
4 QAM
8DS1
1DS18DS1
4 and 16 QAM
16E1
na
na
16DS1
na
na
E3
E3
4 and 16 QAM
DS3
DS3
4 and 16 QAM
02
3DB 06687 CA AA
304
265 / 304
Tab. 25. Capacity and modulation for 9400AWY R.2.0 flash cards (with Ethernet plugin)
Flash Card Name
4E1DS1 4QAM
4E1DS1 4/16QAM
8E1DS1 4QAM
8E1DS1 4/16QAM
4QAM
TDM BW (a)
ETHERNET
BW (b)
(a)+ (b)
Supported
Modulation
2E1
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
2E1
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 and 16 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
2E1
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 QAM
8E1
0E18E1
8E10E1
8E1
4 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
8DS1
0DS18DS1
8DS10DS1
8DS1
4 QAM
2E1
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 and 16 QAM
8E1
0E18E1
8E10E1
8E1
4 and 16 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
8DS1
0DS18DS1
8DS10DS1
8DS1
4 and 16 QAM
2E1
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 QAM
8E1
0E18E1
8E10E1
8E1
4 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
8DS1
0DS18DS1
8DS10DS1
8DS1
4 QAM
16E1
0E18E1
16E10E1
16E1
4 QAM
0DS18DS1
16DS10DS1
16DS1
4 QAM
na
E3
E3
4 QAM
na
DS3
DS3
4 QAM
0E12E1
2E10E1
2E1
4 QAM
4E1
0E14E1
4E10E1
4E1
4 and 16 QAM
8E1
0E18E1
8E10E1
8E1
4 and 16 QAM
4DS1
0DS14DS1
4DS10DS1
4DS1
4 QAM
8DS1
0DS18DS1
8DS10DS1
8DS1
4 and 16 QAM
16E1
0E18E1
16E10E1
16E1
4 and 16 QAM
16DS1
E3
DS3
2E1
FULL FLEXIBLE
16DS1
E3
1AA 00014 0004 (9007) A4 ALICE 04.10
DS3
ED
0DS18DS1
16DS10DS1
16DS1
4 and 16 QAM
na
E3
E3
4 and 16 QAM
na
51,184Mbps
51,184Mbps
4 and 16 QAM
02
3DB 06687 CA AA
304
266 / 304

with Ethernet plugin

Int.N#
& type

B.2.3 : Flash Card content

Whole Equipment configuration data and programs are contained in the Flash Card, as shown in
Fig. 167. below:
SW instances
SW
COMMIT
VERSION
(ACTIVE)
NE Data
Base
configuration
SW
STANDBY
VERSION
(not active)
MIB
NE network
routing data
Fig. 167. Flash Card content

[1]
SW instances
The SW COMMIT VERSION is that used by the system.
The SW STANDBY VERSION instance is created the first time a SW download from ECT to the NE
is carried out.
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.3.2 on page 294.
As supplied by Alcatel factory:
usually only the SW COMMIT VERSION is present
unless differently required by Customer, the SWPversion downloaded in Factory is the most
recently released at the date of Flash Card delivery to the Customer.
The management of these SW instances is described in Chapter 212 Software Management

on page 209.
[2]
NE data
N.B.
a)
as shown in Fig. 167. above, differently from SW instances, NE data are present as single
instances in the Flash Card.
Base configuration
It is defined by Flash Card P/N.
1AA 00014 0004 (9007) A4 ALICE 04.10
It is not changeable, but with Flash Card upgrade (see chapter 14 on page 73).
ED
02
3DB 06687 CA AA
304
267 / 304
MIB
Most (but not all) configuration data set is named MIB (Management Information Base).
Such data are defined by Craft Terminal and can be changed only within the limits (Base
configuration) implicitly defined by the employed Flash Card type.
if the Flash card is supplied together with 9400AWY equipment, NE configuration data are
consistent with the actual HW configuration
if the Flash card is supplied alone, usually and unless differently required by Customer,
NE configuration data are set to default values
MIB can be saved as a file in the Craft Terminal environment, as well can be restored in the Flash
Card retrieving this file from the Craft Terminal, as described in detail in Chapter 213 MIB
Management on page 213.
c)
NE network routing data

Defined by Craft Terminal, they are:
1. Local configuration Systems local address
2. NTP server configuration
3.
Interface configuration
4.
IP configuration
NMS configuration
Ethernet 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.
if, before delivery, Customer communicates the NE network routing data values, they are
stored in the supplied Flash card by Factory
otherwise, the NE network routing data are set to default values.

[3]
System restart
The system restart (reloading of all RAMs present in the system with information stored in the Flash
Card) is without traffic interruption and is carried out:
after the activation of a new SWP
after power off/on
after EC/OC reset (manual of after new SWP activation)
after plugin insertion
1AA 00014 0004 (9007) A4 ALICE 04.10
[4]
FPGA download
As a whole, the correct performance of a certain SWP is granted if the system software works
together with the FPGAs SW versions specifically required by the SWP itself. When a new SWP is
loaded into the NE, the SW versions present in the equipped FPGA may not be consistent with those
expected, so FPGA upgrade could be necessary.
When a new SWP is loaded from ECT into the ULS NE, also the SW images of FPGAs are loaded
into the PQ/ECRC. Each of these SW images is downloaded automatically toward the relevant FPGA
only in case the FPGA version currently running is lower than that made available by the new SWP.
The FPGA version comparison and the possible FPGA download are without traffic interruption and
are launched every time a system restart is carried out.
ED
02
3DB 06687 CA AA
304
268 / 304

b)
B.3 : Equipment control

B.3.1 : Interfaces (see Fig. 163. on page 259):
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 following para.B.3.3 and B.3.4 on page 269
remote through a ECTequipment connection via public switched telephone network, as

explained in Appendix D on page 275.
B.3.2 : OperatorEquipment 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. 166. on
page 260 and Fig. 163. on page 259).
The Craft Terminal characteristics (computer configuration) are listed in chapter 42 on page
237.
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 Operators Handbook (REF.[G] on page 292)
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 EMLULS views.
This Operators Handbook deals with the EMLULS views of the Craft Terminal, which directly
allows to manage the Network Element.
A detailed description of the 9400AWY EMLULS screens is given in the dedicated Section of
this handbook:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
SECTION 2: NE MANAGEMENT on page 75
02
3DB 06687 CA AA
304
269 / 304
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 (if the application is made
available to Customers) of the:
9400AWY Rel.2.0 Line Up Guide (REF.[C] on page 291)
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 9400AWY station an ALCATEL proprietary SWP (SoftWare Package) is employed, which
depends on the productrelease 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
interarea 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)
2)
3)
4)
5)
1AA 00014 0004 (9007) A4 ALICE 04.10
6)
ED
The RECT function provides a remote login facility similar to those offered by an OS to manage
several configured NEs, included the local one.
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.
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.
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.
The operator, through the RECT function, is able to see the alarm synthesis of the whole
network .
In a network the maximum number of NEs equipped with the RECT function are 128. This value
identifies what it is understood as small network for which the RECT function may replace the
Element Manager.
02
3DB 06687 CA AA
304
270 / 304

2)

APPENDIX C : GENERAL ON SWP INSTALLATION

This Appendix introduces the basic information regarding the software installation.
N.B.
Before reading this appendix, it is suggested to read (if not yet done) previous Appendix B on
page 259.
Fig. 168. depicts the main phases for SW management.

SWP
CDROM
1) SWP LOADING IN PC
MSNT 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
5) NE CONFIG.
4)
DATA MNGT
AUTOMATIC SW
DOWNLOAD TO
SUPERVISOR UNITS
(if necessary)
1AA 00014 0004 (9007) A4 ALICE 04.10
DURATION:
some minutes
Fig. 168. Software management main phases
ED
02
3DB 06687 CA AA
304
271 / 304
The SW management can be distinguished into:
program management, i.e.:
(1) and (2) : SWP loading from CDROM 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 NetworkElements 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 11 on page 21
SWP download toward NE

that includes tasks (3) to (5) mentioned above.
The relevant operating instructions are given in chapter 12 on page 57
These main procedures are usually carried out sequentially; some different situations are described in
para.C.1 on page 273.
1AA 00014 0004 (9007) A4 ALICE 04.10
Furthermore, additional procedures are envisaged to be used in special situations, as described in

para.C.2 on page 273.
ED
02
3DB 06687 CA AA
304
272 / 304

C.1 : Common situations

1)
Network Element already configured with the more recent SWP version and Craft
Terminal already available.
NE
ECT
ECT release = NE release
A.B.c
A.B.c
ECT version = NE version
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 loggedin 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).
NE
ECT
ECT release = NE release
A.B.d
A.B.c
ECT version < NE version
In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter
11 on page 21. 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)
NE
ECT
running release = SWP release

A.B.c
A.B.c
running version < SWP version
SWP
CDROM
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.2.0.0), in the case a newer version of the same A.B SWP package has to be installed
(e.g.2.0.1).
Refer to Chapter 13 on page 72.
After that, the situation is equal to that of point 1 ) above.
N.B.
Please refer to para.E.3.2 on page 294 for the meaning of SWP Release, Version and Patch
Level.
C.2 : Troubleshooting situations

In the following situations:
1)
Flash Card to be replaced

or:
2)
NE not infactory configured
1AA 00014 0004 (9007) A4 ALICE 04.10
use the SW download through SIBDL program; refer to the dedicated section (if the application is
made available to Customers) of the:
ED
9400AWY Rel.2.0 Line Up Guide (REF.[C] on page 291)
02
3DB 06687 CA AA
304
273 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
3DB 06687 CA AA
304
274 / 304

APPENDIX D : ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED

TELEPHONE NETWORK
D.1 : Introduction
This chapter explains the operations necessary to allow the remote connection to the FInterface, 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. 169. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.

F Interface
Port COM

1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 169. ECTEquipment connection via Public Switched Telephone Network
ED
02
3DB 06687 CA AA
304
275 / 304
D.2 : Certified equipment
a)
b)
c)

The connection has been successfully tested:

with the following types of modems:
1)
Modem Sportster Flash (US Robotics)
2)
Modem TD32 AC (Westermo Teleindustri AB)
3)
3Com 56K Faxmodem
with the following types of PC:

1)
with external modem:

characteristics as in para.42.1 on page 237
2)
with internal modem:

PC laptop Dell Latitude:
Processor equipped:
Operating system:
RAM equipped:
Hard disk equipped:
Internal Modem:
PENTIUM III
Microsoft Windows 2000 v. 5.00.2195 service pack 2
128 Mbytes
10 Gbytes
3COM 56K v.90 Mini PCI MODEM
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Testing the connection with different types of modems is fully on Customers charge.
ED
02
3DB 06687 CA AA
304
276 / 304
D.3 : Connection cables

In the following figures, the cables for the connections are described:
PC/ECT (DTE)
Cannon 9 pins female
DCD
TD
RD
DTR
DSR
RTS
CTS
GND
Local Modem (DCE)

Cannon 25 pins male
8
3
2
DCD
TD
RD
4 RTS
5 CTS
6 DSR
20 DTR
7 GND
1
2
3
4
6
7
8
5
Fig. 170. ECTLocal external Modem cable
Remote Modem (DCE)
F Interface (DCE)
Cannon 25 pins male
Cannon 9 pins male
TD
RD
RTS
CTS
DSR
CTS
GND
2
3
4
5
6
3
2
7
8
6
20
7
4
5
TD
RD
RTS
CTS
DSR
DTR
GND
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 171. F InterfaceRemote Modem cable
ED
02
3DB 06687 CA AA
304
277 / 304
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. 169. on page 275 for
the distinction between local and remote), relevant to the autoanswer 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. 170. on
page 277.
2)
Only for external modem: Power and switch on the local modem.
3)
On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Bits per second: 38400
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
4)
Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return>
ATT<Return>
ATX3<Return>
AT&W0<Return>
1AA 00014 0004 (9007) A4 ALICE 04.10
5)
ED
(Best PC default configuration recall)

(Tone Dialling instead than Pulse Dialling)
(Second Signal disabling, avoids problems with PABX)
(Configuration store in NVRAM 0)
Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.
02
3DB 06687 CA AA
304
278 / 304

D.4 : Modem setting

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
&M4
&B1
&N0
S00=000
S07=060
S15=000
S25=005
S33=000
S41=004
&C1
&P0
&D2
&R2
S01=000
S08=002
S16=000
S27=001
S34=000
S42=000
&H1
&S0
&I0
&T5
S02=043
S09=006
S18=000
S28=008
S35=000
&K1
&U0
S03=013
S10=014
S19=000
S29=020
S36=014
&Y1
S04=010
S11=072
S21=010
S30=000
S38=000
S05=008
S12=050
S22=017
S31=128
S39=012
S06=004
S13=000
S23=019
S32=002
S40=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 setup, 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>
c)
now, setting has been completed. Modem can be switched off and disconnected, if necessary.
N.B.
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
S00=001
ED
(Autoanswering setting)
S01=000
S02=043
S03=013
S04=010
S05=008
S06=004
02
3DB 06687 CA AA
304
279 / 304
D.4.2 : TD32 AC Modem setting

This modem requires an initial HW setup via dipswitches and a SW setting via serial port.
To set the modem, both local and remote, proceed as follows:
1)
The initial HW setup via dipswitches is indicated in Fig. 172. 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. 172. TD32 AC modem dipswitch setting

2)
Connect the local modem to the PC/ECT with the cable of Fig. 170. on page 277.
3)
Power on the local modem (there is no an ON/OFF switch).
4)
On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
5)
Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return>
AT&K0<Return>
ATA<Return>
1AA 00014 0004 (9007) A4 ALICE 04.10
AT&W0<Return>
AT&Y0<Return>
6)
ED
(Best PC default configuration recall)

(DTE/DCE flow control disabling)
(Automatic Answer enabling > Only on Remote modem and
wait the message NO CARRIER)
(Configuration store in NVRAM 0)
(Configuration Set to load at switchon: NVRAM 0)
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
02
3DB 06687 CA AA
304
280 / 304

N.B.
AT\S<Return> in the HyperTerminal program window.
Information displayed should be as follows:
AT\S
CMD DESCRIPTION / OPTION

COUNTRY...........IT
DTE BPS........38400
DTE PARITY.....8NONE
LINE SPEED......NONE
B
BELL MODE........OFF
E
CMD ECHO..........ON
F
LINE MODE.......AUTO
L
SPKR VOLUME......LOW
M
SPKR CONTROL....CALL
N
AUTO MODE.........ON
Q
QUIET............OFF
V
RESULT FORM.....LONG
W
EC MSG.............0
X
EXT RESULTS........4
Y
LONG SPACE DISC...NO
%C COMPRESSION.....BOTH
K EXT. SERVICES......0
CMD
&A
&B
&C
&D
&G
&K
&L
&Q
&R
&S
&T
&X
&Y
\A
\G
\K
\N
DESCRIPTION / OPTION
CHR ABORT OPT.....NO

DTR DIAL OPTION...NO
DCD OPTION........ON
DTR OPTION.........0
GUARD TONE......NONE
FLOW CONTROL....NONE
NETWORK.........PSTN
ASYNC/SYNC.........5
RTS/CTS.........AUTO
DSR OPT............0
ENABLE RDL........NO
SYNC CLOCK.......INT
PROFILE........NVM.0
MAX BLK SIZE.....192
REMOTE FLOW......OFF
BRK OPT............5
ECL MODE........AUTO
CMD DESCRIPTION / OPTION

*H NEG. SPEED......HIGH
S0 RINGS TO ANS.....002
S1 RING COUNT.......000
S2 <ESC> CHAR.......043
S3 <CR> CHAR........013
S4 <LF> CHAR........010
S5 <BS> CHAR........008
S7 CONNECT TIME.....060
S8 PAUSE TIME.......002
S12 ESC GUARD TIME...050
S30 CONNECT INACT....000
S32 XON CHAR.........017
S33 XOFF CHAR........019
S36 FALLBACK ACTION..007
S37 MODE SELECT......000
S48 V42 NEG CTRL.....007
S95 RES. CODE........000
D.5 : PC laptop Dell Latitude setting

The following setting must be done:
1AA 00014 0004 (9007) A4 ALICE 04.10
Control Panel > Alcatel Lower Layer > Serial port > COM3 and Serial port selected
ED
02
3DB 06687 CA AA
304
281 / 304
D.6 : Setting up the connection
N.B.
Leaving the remote modem permanently switched on and permanently connected to

Finterface 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 equipments F interface with the cable of Fig. 171. on page 277.
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 equipments 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. 170. on page 277.) 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 equipments F
interface).
7)
Power and switch on the local modem.
8)
On the PC, activate program HyperTerminal and configure the PCLocal Modem serial line with
the following parameters:
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
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
CONNECT 38400
(Sportster Flash)
(TD 32 AC)
12 ) Close HyperTerminal program.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
between local and remote modems, switching off the local modem or physically disconnecting
the cable connecting it to the PC.
ED
02
3DB 06687 CA AA
304
282 / 304

In order to activate the connection and operate the ECT in remote way, proceed as specified herebelow.
Refer to Fig. 169. on page 275 for the distinction between local and remote modems.

D.7 : Changing the ECTequipment 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 setup and phone call at ECT startup.
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 setup as explained in the following para.D.7.2 on page 284.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
DO NOT ATTEMPT TO USE THIS FEATURE

WITHOUT TAC ASSISTANCE.
YOU COULD CAUSE
UNRECOVERABLE ECT INACCESSIBILITY.
ED
02
3DB 06687 CA AA
304
283 / 304
D.7.2 : Configuration at PC side

Please read carefully paragraph Introduction on page 283.
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. 173. opens.
Fig. 173. Alcatel Lower Layers utility
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Subnetwork 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 startup.
ED
02
3DB 06687 CA AA
304
284 / 304

N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10

APPENDIX E : DOCUMENTATION GUIDE

This appendix contains all information regarding:
this handbook, herebelow
the Customer Documentation set this handbook belongs to, on page 290
general on Alcatel Customer Documentation,
on page 293
E.1 : Handbook guide

This paragraph contains all information regarding this handbook:
Handbook applicability
on page 286
Purpose of the handbook
on page 287
Handbook history
on page 288
ED
02
3DB 06687 CA AA
304
285 / 304
E.1.1 : Handbook applicability

Product-release applicability
This handbook applies to the following product-releases:
PRODUCT
RELEASE
ANV P/N
9470AWY
2.00.00
3DB 05470 AAAA
9411AWY
2.00.00
3DB 06539 AAAA
9413AWY
2.00.00
3DB 06541 AAAA
9415AWY
2.00.00
3DB 06543 AAAA
9418AWY
2.00.00
3DB 06545 AAAA
9423AWY
2.00.00
3DB 06547 AAAA
9425AWY
2.00.00
3DB 06551 AAAA
9428AWY
2.00.00
3DB 06553 AAAA
9432AWY
2.00.00
3DB 06555 AAAA
9438AWY
2.00.00
3DB 06557 AAAA
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 Release
SWP 9400AWY R.2.0 CDROM
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10

a)
ED
SWP P/N
SWP Version
(N.B.)
REF.(a) in Tab. 14. on page 235
V2.0.0 & V2.0.1
For the meaning of SWP Release and Version, please refer to para.E.3.2 on page 294.
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 manmachine 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 versionrelease of the
productrelease, then they are not replaced in the subsequent versions of handbook if
their contents remains unchanged.
02
3DB 06687 CA AA
304
286 / 304

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 286.
Please refer to para.E.2 on page 290 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 286).
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 ECTequipment remote connection on Public Switched Telephone Network.
The document that should be read before starting this document is:

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 Operators Handbook V3.0.1
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
287 / 304
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. 26. indicates the handbook parts new and modified with respect to the previous
edition.
Legend
n
= new part
= modified part
blank= part unchanged
Tab. 26. Handbook history

HANDBOOK EDITION
FRONT MATTER
02
Preliminary information
Handbook applicability, purpose and history
Handbook structure
Safety, EMC, EMF, ESD norms and equipment labelling
Cautions to avoid equipment damage
Quick guide
11
SWP installation in PC environment
12
SWP download toward NE
13
CT & NE Upgrade to a newer SWP version (same SWP

release)
14
Flash Card upgrade
04
05
21
General introduction on views and menus
22
Configuration
23
Equipment
24
Line Interface
25
Radio
26
External points
27
Supervision
28
Protection schemes
29
Loopbacks
210 Diagnosis
211
212 Software Download
213 MIB Management
Performance Monitoring
03
1AA 00014 0004 (9007) A4 ALICE 04.10
01
31
Maintenance introduction
32
Troubleshooting
table continues
ED
02
3DB 06687 CA AA
304
288 / 304

E.1.3.1: List of the editions and modified parts
Tab. 26. Handbook history

HANDBOOK EDITION

41
SWP REG.9400AWY R.2.0 description
42
SWP REG.9400AWY R.2.0 V.2.0.0 specific information
43
SWP REG.9400AWY R.2.0 V.2.0.1 specific information
01
02
03
04
05
Equipment description and components
SW allocation, Flash Card and equipment control
General on SWP installation
ECTEquipment connection via public switched telephone

network
Documentation Guide
Acronyms and abbreviations
Glossary of terms
E.1.3.2: Notes on Ed.01
Draft editions neither validated nor officially released issue, for internal validation purposes:
Ed.01ADRAFT created on April 5th, 2005.
Ed.01 created on May 10th, 2005 is the first released and validated version of the handbook,
associated to SWP version V2.0.0.
E.1.3.3: Notes on Ed.02
Draft editions neither validated nor officially released issue, for internal validation purposes:
Ed.02ADRAFT created on September 26th , 2005.
Ed.02 created on November 9th, 2005 is the second released and validated version of the handbook
(N.B.), and has been done for the following major changes:
This issue has been done to align the handbook to the new features of SWP version V2.0.1.
Nevertheless, handbook can be used also in association with SWP former version V2.0.0.
Changes related to this new version have been introduced throughout the handbook, where
necessary.
Moreover, many operative instructions have been improved, according to suggestions and
requests from field operation teams.
Revision bars point out all modifications with respect to ED.01.
Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated
or shifted in other places of the handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
This edition is validated in conjunction with SWP versions V2.0.0 to V2.0.1 only. Some
features not strictly pertaining to such versions are described, too. For them, please refer
to the additional feature and SWPversion relationship, summedup in Tab. 1. on
page 12.
02
3DB 06687 CA AA
304
289 / 304
This paragraph contains all information regarding the 9400AWY Rel.2.0 Customer Documentation and
is organized as follows:
9400AWY Rel.2.0 productreleaseversion handbooks

Additional documentation for 1320CT platform
herebelow
on page 292
E.2.1 : 9400AWY Rel.2.0 productreleaseversion handbooks

This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for
9400AWY Rel.2.0 product release.
Please refer to following para.E.3 on page 293 for a general description of Alcatel Customer
Documentation system.
The list of handbooks given here below is valid 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 here below may not be available at the issue date of this
Handbook.
The standard Customer Documentation is in the English language and is composed by different
handbooks.
Tab. 27. herebelow lists the handbooks.
The [REF] indication in Tab. 27. is relevant to the handbook brief description given in tables Tab. 28. thru
Tab. 32. in the following.
Tab. 27. 9400AWY Rel.2.0 product release handbooks
TECHNICAL HANDBOOK
REF
[A]
INSTALLATION AND LINEUP HANDBOOKS

[B]
[C]
Interference investigation procedure
[E]
OPERATORS HANDBOOKS
9400AWY CT Operators Handbook SWP 2.0
[D]
DOCUMENTATION CDROM
DCP 9400AWY R.2.0 CD_ROM
[F]
1320 CT OPERATORS HANDBOOKS
1AA 00014 0004 (9007) A4 ALICE 04.10
1320CT Basic Operators Handbook
AS Operators Handbook
ELB Operators Handbook

see Tab. 33. on page 292
ED
02
3DB 06687 CA AA
304
290 / 304

E.2 : Documentation set description
Tab. 28. 9400AWY Rel. 2.0 Technical Handbooks

REF
HANDBOOK
9400 AWY Rel. 2.0 Technical Handbook
[A]
ANV P/N
NOTES
3DB 06687 BAAA
Provides information regarding AWY equipment description and composition, station

layouts, hardware setting documentation and maintenance.
Tab. 29. 9400AWY Rel. 2.0 Installation and LineUp Handbooks
REF
The Installation Handbook provides information regarding Equipment installation, according

to Alcatel WTD LAB. rules.
The Lineup Guide provides information regarding equipment line up and commissioning,
according to Alcatel WTD LAB. rules.
HANDBOOK
ANV P/N
NOTES
[B]
9400 AWY Rel.2.0 Installation Handbook
3DB 06687 DAAA
[C]
9400 AWY Rel.2.0 Lineup Guide
3DB 06687 EAAA
Tab. 30. Operators Handbooks related to the specific Software Package SWP
REF
HANDBOOK
9400 AWY Rel.2.0
CT Operators Handbook SWP 2.0
[D]
ANV P/N
NOTES
3DB 06687 CAAA
this handbook
Provides AWY SWP screens and operational procedures for Equipment SW management and
maintenance.
Tab. 31. Handbooks common to all Alcatel Radio Transmission products

REF
HANDBOOK
1AA 00014 0004 (9007) A4 ALICE 04.10
[E]
ED
ANV P/N
NOTES
3DB 04165 EAAA
Describes the measurement procedure for the interference searching in the various RF bands
used by Alcatel Radio Transmission products.
02
3DB 06687 CA AA
304
291 / 304
Tab. 32. 9400AWY Rel.2.0 Documentation on CDROM

CDROM TITLE
DCP 9400AWY 2.0 CD_ROM
ANV P/N
NOTES
REF
3DB 06687 AAAA
Contains, in electronic format (ACROBAT pdf files), all handbooks listed in Tab. 27. on
page 290 (when all envisaged handbooks are released), with exception of 1320 CT
Operators Handbooks for which the CDROM REF.[J] (herebelow) is envisaged
[F]
E.2.2 : Additional documentation for 1320CT platform
Tab. 33. Documentation common to Alcatel Network Elements using 1320CT platform
REF
CTK
Version
(N.B.)
3.0.1
HANDBOOK
1320CT Rel.3.x
Basic Operators Handbook
ANV P/N
NOTES
3AL 79551 AAAA
[G]
Provides general information and operational procedures common to all 1320CT (Craft
terminal) of Alcatel InfoModel Network Elements.
3.0.1
AS Rel.6.5
Operators Handbook
3AL 88876 AAAA
[H]
Provides detailed information and operational procedures regarding the alarm Surveillance
software embedded in the 1320CT software package.
3.0.1
ELB Rel.2.x
Operators Handbook
3AL 88877 AAAA
[I]
Provides detailed information and operational procedures regarding the Event Log Browser
software embedded in the 1320CT software package.
3.0.1
[J]
DCP 1320 CT 3.x

CD_ROM EN
3AL 79552 AAAA
Contains, in electronic format, the 1320 CT Operators Handbook REF.[G] to [I]
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The CT Version is displayed when, on the PC, you select the 1320CT application for its
launch.
02
3DB 06687 CA AA
304
292 / 304

E.3 : 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.
This paragraph is fully applicable to the 2nd generation Radio Product families of Alcatel WTD (Wireless
Transmission Division) only.
E.3.1 : CustomerIndependent Standard Customer Documentation

a)
Definition
Standard Customer Documentation, referred to hereafter, must be always meant as
plantindependent and is always independent of any Customization.
Plantdependent 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.
b)
Plantdependent and Customized documentation is not described here.
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 manmachine interface and of the operating procedures allowed by it;
maintenance is described down to faulty PCB location and replacement.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
No supply to Customers of design documentation (like PCB hardware design and

production documents and files, software source programs, programming tools, etc.) is
envisaged.
02
3DB 06687 CA AA
304
293 / 304
E.3.2 : Product levels and associated Customer Documentation
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. 9400 AWY is a product.
b)
Product-releases
A product evolves through successive productreleases, which are the real products marketed
for their delivery at a certain productrelease availability date. A certain productrelease performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive productreleases of the same product.
A productrelease 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 productrelease has been designed, engineered, and marketed for.
c)
Configurations and Network Elements

In some cases, a productrelease 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. 174. herebelow.
A SWP is identified by the configuration name and by the version number (tree digits).
The versions first digit corresponds to the productrelease 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
Releases
first digit
SWP evolution for bug fixing purposes
and/or minor additional features
(same SWP Release within same ProductRelease)
1.
0.
1.
0.
SWP evolution for main additional features

(new SWP Release within same ProductRelease)
(N.B. see next page)
1.
0.
1.
1.
1.
0.
2.
0.
SWP evolution for additional features

(new SWP Release of a new ProductRelease)
1AA 00014 0004 (9007) A4 ALICE 04.10
Patch Level
Fig. 174. Example of SWP Release and Version numbering
ED
02
3DB 06687 CA AA
304
294 / 304

See Fig. 175. on page 295.

N.B.
e)
Sometimes, different SWP Releases (within the same ProductRelease) are commercially
distinguished by different names, e.g. :
SWP version
SWPRelease commercial name
1.0.x
1.0
1.1.x
1.0B
1.2.x
1.0C
Customer Documentation
A productrelease(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 LineUp Guide
Software documentation:
a Craft Terminal Operators Handbook, associated to the specific SWPRelease
other Operators Handbooks (typically those associated to the SW platform embedded

in the SWP)
PRODUCT
evolution
PRODUCTRELEASE 1.0
PRODUCTRELEASE 2.0
ALTERNATIVE CONFIGURATIONS
CONFIG.A
SWP REL.1.0
PRODUCT
LEVELS
CONFIG.B
evolution
SWP REL.1.1
DOCUMENTATION
CONFIG.A
System & HW
Documentation
SWP REL.1.0
SW
Documentation
SWP REL.1.1
SW
Documentation
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 175. Example of Product levels and associated Customer Documentation
ED
02
3DB 06687 CA AA
304
295 / 304
E.3.3 : Handbook and CDROM supply to Customers

Standard supply
Handbooks and CDROMs are standard commercial items and are ordered and delivered as any
other Alcatel commercial item.
Handbooks and CDROMs are not automatically delivered together with the equipment they refer
to.
The number of handbooks or CDROMs per type to be supplied must be decided at contract level.
b)
Productdocumentation consistency
Equipment description and layout are always general, i.e. they never describe the actual
composition of the equipment supplied to Customer (this task is entrusted to plantdependent
documentation).
Detailed hardware documentation concerns actually supplied units and is coherent with the
production issue of such units.
Softwareassociated handbooks are coherent with the supplied SWP release.
Copies of the handbooks regarding a specific productrelease previously delivered can be required
specifying P/N and edition.
c)
Inadvance supply
Whenever handbooks or CDROMs 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 CDROMs to Customers

Supplying updated handbooks or CDROMs 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 erratacorrige sheets is not envisaged).
e)
Copyright notification
The technical information of the handbooks and CDROMs 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Presently not envisaged.
ED
02
3DB 06687 CA AA
304
296 / 304

a)

APPENDIX F : ACRONYMS AND ABBREVIATIONS

N.B.
For the explanation of the acronyms of the alarms refer to Section MAINTENANCE
para.32.4.1 Alarm synthesis indication on page 225.
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
CDROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee
CPU: Central Processor Unit
CT: Craft Terminal
DEM: DEModulator
1AA 00014 0004 (9007) A4 ALICE 04.10
DTE: Data Terminal Equipment

DTMF: Dual Tone Multi Frequency
EB: Errored Block
ED
02
3DB 06687 CA AA
304
297 / 304
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
1AA 00014 0004 (9007) A4 ALICE 04.10
IM: Information Manager

IP: Input Port or Internet Protocol
ISO: International Standards Organization
Kbit/s: Kilobits per second
ED
02
3DB 06687 CA AA
304
298 / 304
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
1AA 00014 0004 (9007) A4 ALICE 04.10
OSPF: Open Shortest Path First

PDH: Plesiochronous Digital Hierarchy
PI: Physical Interface
PLL: Phase Locked Loop
ED
02
3DB 06687 CA AA
304
299 / 304
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
1AA 00014 0004 (9007) A4 ALICE 04.10
UAT: UnAvailable Time

URU: Underlying Resource UnAvailable
USM: User Service Manager
WST: Way Side Traffic
ED
02
3DB 06687 CA AA
304
300 / 304

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
ED
02
3DB 06687 CA AA
304
301 / 304
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 enduser 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
Linked to alarms, severities indicate the magnitude related to the failure.
ED
02
3DB 06687 CA AA
304
302 / 304

International Telegraph and Telephone Consultative Committee:

Standard organization for telecommunications. Now called the ITUT (International Telecommunication
Union).

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
3DB 06687 CA AA
304
303 / 304
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
02
3DB 06687 CA AA
304
304 / 304
Craft Terminal Operators Handbook
Alcatel 9400AWY
Rel.2.0
78111315182325283238 GHz
shorthaul low/medium capacity digital microwave radio links
SWP 9400AWY R.2.0
3DB 06687 CAAA Ed.02
Documentation set for 9400AWY Rel.2.0

Handbook
ANV P/N
3DB 06687 BAAA
3DB 06687 DAAA
3DB 06687 EAAA
3DB 04165 EAAA
9400AWY CT Operators Handbook SWP 2.0
3DB 06687 CAAA
1320CT Rel.3.x Basic Operators Handbook
3AL 79551 AAAA
1330AS Rel.6.5 Operators Handbook
3AL 88876 AAAA
ELB Rel.2.x Operators Handbook
3AL 88877 AAAA
this handbook
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
QUICK GUIDE
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N:
9400AWY Rel.2.0
SWP 9400AWY R.2.0
C.T. OPERATORS HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (source & pdf)
No PAGINE TOTALI PER ARCHIVIAZIONE: 306+4 = 310

DIMENSIONE BINDER SORGENTE (du ks): 425.635 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
(facciate)
No pages
1AA 00014 0004 (9007) A4 ALICE 04.10
fase
step
ED
numerate
numbered
da from
a to
TARGHETTE - LABELS
FRONTESPIZIO - FRONT
PARTE INIZIALE FRONT MATTER
1/304
18/304
INSERIRE SEPARATORE 1 - INSERT REGISTER 1
19/304
74/304
75/304
218/304
SECTION 3: MAINTENANCE
219/304
232/304
10
11
233/304
248/304
12
13
249/304
304/304
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
306
TOTALE FOGLI A4 TOTAL A4 SHEETS:
153
02
RELEASED
3DB 06687 CAAA TQZZA
4
1/ 4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
Site
VIMERCATE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
WTD
Originators
E.CORRADINI
G.ZILIANI RTT
9400AWY REL.2.0
SWP 9400AWY R.2.0
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
9400AWY REL.2.0
SWP 9400AWY R.2.0
SWP 9400AWY R.2.0 C.T. OPER.HANDBOOK
Internal :
External
:
Approvals
Name
App.
A.BESTETTI
Name
App.
R.PELLIZZONI
V.FOSSATI
P.CREMONESI
PUBLISHING NOTES
Labels are done according to A-Italy binder format.

Source files and printable files of this handbook are archived in ePDM:
Source files: ALICE 6.10 ARCHIVED BY GAPI 3.10.1
Printable file: PDF file must be opened with ACROBAT Reader Version 5.0 at least.
(N.B. : it has been created with ACROBAT DISTILLER 7.0)
3DB 06687 CAAA

Ed.02
9400AWY Rel.2.0
1AA 00014 0004 (9007) A4 ALICE 04.10
SWP 9400AWY R.2.0

78111315182325283238 GHz
ED
02
RELEASED
4
2/ 4
9400AWY Rel.2.0
78111315182325283238 GHz
SWP 9400AWY R.2.0

VOL.1/1
9400AWY Rel.2.0
78111315182325283238 GHz
SWP 9400AWY R.2.0
VOL.1/1
9400AWY Rel.2.0
78111315182325283238 GHz
SWP 9400AWY R.2.0
VOL.1/1
9400AWY Rel.2.0
78111315182325283238 GHz shorthaul low/medium capacity digital microwave radio links
SWP 9400AWY R.2.0

VOL.1/1
9400AWY Rel.2.0
78111315182325283238 GHz
SWP 9400AWY R.2.0
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
VOL.1/1
RELEASED
4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
02
RELEASED
4/ 4

Alcatel 9400AWY Rel.2.0 (Handbook) PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Alcatel 9400AWY Rel.2.0 (Handbook) PDF

Transféré par

Droits d'auteur :

Formats disponibles

1AA 00014 0004 (9007) A4 ALICE 04.

All rights reserved. Passing on and copying of this

SWP 9400AWY R2.0 C.T. OPERATORS HDBK

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

SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . .

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

11 SWP INSTALLATION IN PC ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

Summary of the SWP installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13 ECT & NE UPGRADE TO A NEW SWP VERSION (SAME SWP RELEASE) . . . . . . . . . .

14 FLASH CARD UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

24.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

211 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

213 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

SECTION 3: NE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

All rights reserved. Passing on and copying of this

All rights reserved. Passing on and copying of this

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

42 SWP REG.9400AWY R.2.0 V2.0.0 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . .

43 SWP REG.9400AWY R.2.0 V2.0.1 SPECIFIC INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

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

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

1AA 00014 0004 (9007) A4 ALICE 04.10

APPENDIX D : ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

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

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

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

All rights reserved. Passing on and copying of this

C.1 : Common situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Fig. 51. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Fig. 105. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Fig. 159. MIB load from disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

Access to the Equipment

Service Personnel skill

HANDBOOK APPLICABILITY, PURPOSE AND HISTORY

Tab. 1. Additional feature and SWPversion relationship

78 GHz ODUs (new 9470AWY product)

Frequency shifter management

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Please refer to para.E.1 on page 285.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Information in this handbook is divided into the following parts:

LIST OF FIGURES AND TABLES