Académique Documents
Professionnel Documents
Culture Documents
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
C.T. OPERATORS HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
fase
step
ED
da from
a to
96
1/96
96/96
258
1/258
258/258
24
1/24
24/24
1/10
10/10
TARGHETTE - LABELS
FRONTESPIZIO - FRONT
10
11
10
396
198
04
numerate
numbered
RELEASED
957.207.022 TQZZA
1/ 4
Site
CONCOREZZO
WTD
Originators
M.CORBETTA
E.CORRADINI
C.NAVA
9600LSY REL.1.0
SWP REG.9600LSY R1.0
C.T. OPERATORS HANDBOOK
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
Approvals
Name
App.
G.CONSONNI
A.FUMAGALLI
Name
App.
957.207.022 A
3DB 02838 AAAA
Ed.04
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
STM 1/0 Long Haul Digital Radio Relay System
ED
04
RELEASED
957.207.022 TQZZA
2/ 4
9600LSY Rel.1.0
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
VOL.1/1
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
STM 1/0 Long Haul Digital Radio Relay System
C.T. OPERATORS HANDBOOK
957.207.022 A Ed.04
VOL.1/1
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
STM 1/0 Long Haul Digital Radio Relay System
957.207.022 A Ed.04
957.207.022 A Ed.04
VOL.1/1
9600LSY Rel.1.0
VOL.1/1
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
STM 1/0 Long Haul Digital Radio Relay System
957.207.022 A Ed.04
ED
04
VOL.1/1
RELEASED
957.207.022 TQZZA
3/ 4
ED
04
RELEASED
957.207.022 TQZZA
4/ 4
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Alcatel 9600LSY
STM1/0 Long Haul Digital Radio Relay System
9600LSY Rel.1.0
957.207.022 A Ed.04
Handbook
this
Handbook
When supplied on paper, this handbook is divided by registers, for an easier access to the information
herein contained:
CONTENTS
REGISTER
SECTION 4: SIBDL
957.207.022 A Ed.04
SECTION 1: INTRODUCTION
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Purpose of the handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Handbook structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
13
14
16
18
19
25
SWP DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
31
31
04
020722
S402071501
03
020524
S402040401
01A 011109
ED
proposaldraft
DATE
CHANGE NOTE
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
M.CORBETTA ITACO
APPRAISAL AUTHORITY
ORIGINATOR
9600LSY REL.1.0
SWP REG.9600LSY R1.0
C.T. OPERATORS HANDBOOK
ED
04
957.207.022 A
3DB 02838 AA AA
6
1/ 6
31
32
33
33
INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
4 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 LHR System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 LHR system layout and equipping rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 ECT and RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
40
41
51
53
53
57
59
61
62
63
7 HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
65
65
65
65
66
69
70
70
71
71
APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
75
75
75
76
77
81
12 DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Productreleaseversion handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 General on Alcatel Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
84
87
ED
04
957.207.022 A
3DB 02838 AA AA
6
2/ 6
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
12
14
15
15
17
3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
27
29
29
31
33
35
35
37
38
40
41
42
43
45
46
6 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Introduction and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Set and change or remove board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Board administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 Show supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
47
75
77
78
79
82
7 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Board View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
83
85
8 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
89
90
101
101
115
115
116
ED
04
957.207.022 A
3DB 02838 AA AA
6
3/ 6
120
122
11 RADIO PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 ATPC/Power and Threshold Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 ATPC Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Power Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Manual operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Power Setting in Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 ATPC Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Gain Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 HOP Section Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9 Squelch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10 Radio Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Frequency Reuse Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.12 Equalization Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.13 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14 V.C.O. State Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.16 Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
126
128
129
129
130
131
132
134
136
137
138
140
142
143
144
149
12 OVERHEAD MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.8 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
151
151
154
155
157
164
165
166
13 LOOPBACK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 Types of Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Caution: recoverable and unrecoverable loopbacks (with RECT) . . . . . . . . . . . . . . . . .
13.3 Loopback management starting from Port view menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Loopback management starting from Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . .
167
167
168
171
178
183
183
186
15 ALARMS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
189
194
196
197
17 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3 Display Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.4 Display History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.5 PM Threshold Table Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6 PM Threshold Table Modification or Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
199
204
207
209
211
213
ED
04
957.207.022 A
3DB 02838 AA AA
6
4/ 6
18 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1 General and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2 Software Download Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.3 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4 Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.5 MIB management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.6 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215
215
217
218
220
222
223
225
226
227
227
228
229
248
249
251
252
253
256
257
258
258
258
258
258
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
4
4
2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 MAINTENANCE OF THE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
7
7
7
10
ED
04
957.207.022 A
3DB 02838 AA AA
6
5/ 6
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
4
4
2 SIBDL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
END OF DOCUMENT
ED
04
957.207.022 A
3DB 02838 AA AA
6
6/ 6
SECTION 4: SIBDL
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Purpose of the handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Handbook structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 Notes on Ed.01Aproposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2 Notes on Ed.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3 Notes on Ed.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.4 Notes on Ed.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.5 Notes on Ed.04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1 List of the editions and modified parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
13
14
16
16
16
16
17
17
18
18
19
25
SWP DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
31
31
31
32
33
33
33
04
020722
S402071501
03
020524
S402040401
01A 011109
ED
proposaldraft
DATE
CHANGE NOTE
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
M.CORBETTA ITACO
APPRAISAL AUTHORITY
ORIGINATOR
9600LSY REL.1.0
SWP REG.9600LSY R1.0
C.T. OPERATORS HANDBOOK
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
1 / 96
SW Package Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SW Package Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ECT SW SubComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DipSwitches setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
34
34
34
35
INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
4 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 LHR System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 LHR system layout and equipping rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 System layout and hardware components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Equipment provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 ECT and RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
40
41
41
45
51
53
53
53
57
58
59
61
62
63
7 HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
65
65
65
65
66
66
67
67
67
67
68
69
69
69
69
70
70
71
71
APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
75
75
75
76
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
2 / 96
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
77
77
79
81
12 DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Productreleaseversion handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1 Specific equipment handbooks and CDROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2 Related equipment handbooks and CDROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 General on Alcatel Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 CustomerIndependent Standard Customer Documentation . . . . . . . . . . . . . . . . . . . . .
12.2.2 Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . .
12.2.3 Typical contents of Technical & Craft Terminal Operators Handbooks . . . . . . . . . . . . .
12.2.4 Documentation on paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.5 Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.6 Handbook and CDROM supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
84
84
86
87
87
88
90
92
94
96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
3 / 96
FIGURES
Fig. 1. Regenerator and WMSN station rack configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 2. Base Band shelf board equipment (slot numbering and board type and numbering) . . . . . .
Fig. 3. Transceiver shelf equipment (slot numbering and board types and numbering) . . . . . . . . . .
Fig. 4. Layout of max 8 channels in single polarization configurations . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 5. Layout of max 8 channels in double polarization configurations . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 6. Single polarization per rack expansion procedure in the transceiver subrack . . . . . . . . . . . .
Fig. 7. Two polarization per rack expansion procedure in the transceiver subrack with the H
channels on the left side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 8. 2 polarization per rack expansion procedure in the transceiver subrack with V channel on
the left side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 9. Expansion procedure with reused channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 10. Fan shelf (slot numbering and board types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 11. LHR system (N+1 / N+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 12. Equipment main parts containing local SW (LHR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 13. System Controller assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 14. FLASH CARD profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 15. WMSN system (N+1 / N+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 16. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 17. Selecting Software Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 18. Directory selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 19. ECTEquipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . . .
Fig. 20. ECTLocal Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 21. F InterfaceRemote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 22. TD32 AC modem dipswitch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 23. Example of SWP Release and Version numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 24. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . .
TABLES
Tab. 1. Quick guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 2. Handbook history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 3. Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 4. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 5. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 6. ESC DipSwitch Bank I4 setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 7. ESC DipSwitch Bank I1 setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 8. LHR Terminal Regenerator System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 9. Couples of Radio Channels that can be used for protected service channels and WST . .
Tab. 10. Equipping rules for FANS assembled unit in Basebandshelf . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 11. Handbooks related to the specific product hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 12. Handbooks related to the specific product SW management and local product control . .
Tab. 13. Handbooks common to all Alcatel Radio Transmission products . . . . . . . . . . . . . . . . . . . . .
Tab. 14. Handbooks common to Alcatel Network Elements using 1320CT platform . . . . . . . . . . . . .
Tab. 15. Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 16. Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 17. Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
04
41
42
42
45
46
47
48
49
49
50
53
55
56
56
58
59
68
68
75
76
76
79
88
89
7
16
18
31
32
35
36
40
40
50
84
84
85
85
85
86
86
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
4 / 96
HANDBOOK GUIDE
SECTION CONTENT
ED
PAGE
PRELIMINARY INFORMATION
QUICK GUIDE
11
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
5 / 96
PRELIMINARY INFORMATION
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:
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)
3)
Safety norms
Recommended safety norms are not indicated in this manual, but in Handbook REF. [A] on
page 84. The warning labels that can be found on the equipment parts are indicated on page
9.
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.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
6 / 96
a)
QUICK GUIDE
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
N.B.
In the documentation on CDROM, this table represent hyperlinks to the referenced parts.
commission equipment
Tab. 1. continues ..
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
7 / 96
.. continues Tab. 1.
If you need immediate operative information on how to:
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
To find any other kind of information not listed in the above table, please start reading para.1.4 on page
14, and then search the information according to the handbook structure described.
N.B.1
The QUICK GUIDE in LHR Technical Handbook is available starting from its ED.02.
N.B.2
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
8 / 96
a)
Please refer to 9600LSY/LHR Technical Handbook to obtain details regarding following information:
Safety rules:
TOPIC
General rules
Dangerous Electrical Voltages
Risk of explosion
b)
ED
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.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
9 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
10 / 96
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 DOCUMENT GUIDE
1.1 Introduction
This chapter contains all information regarding this handbook is organized as follows:
Handbook applicability
on page 12
on page 13
Handbook structure
on page 14
Handbook history
on page 16
Document history
on page 18
on page 19
Glossary of terms
on page 25
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
11 / 96
This handbook applies to the following Product Releases, Network Elements (NE) and Software Packages
(SWP):
PRODUCT
RELEASE
ANV P/N
FACTORY P/N
9640LSY
(4 GHz)
1.00.00
522.171.110
9647LSY
(4.7 GHz)
1.00.00
522.171.210
9662LSY
(6.2 GHz)
1.00.00
522.171.310
9667LSY
(6.7 GHz)
1.00.00
522.171.410
9674LSY
(7 GHz)
1.00.00
522.171.510
9681LSY
(8 GHz)
1.00.00
522.171.610
9610LSY
(10 GHz)
1.00.00
522.171.910
9611LSY
(11 GHz)
1.00.00
522.171.710
9613LSY
(13 GHz)
1.00.00
522.171.810
SWP Release
SWP REG.9600LSY R.1.0
NE
SWP Version
(N.B.)
LHR
1.0.10
For the meaning of SWP Release and Version, please refer to para.12.2.2 on page 88.
N.B.
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:
ED
04
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.
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
12 / 96
the structure (hardware composition) and all the possible operating modes of the equipment
(product-release) that this handbook refers to.
Before accessing other sections of this handbook, read completely this section in order to have information
on:
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.
The document that should be read before starting this document is:
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.).
N.B.
Paragraph Unit Replacement Procedures is available starting from ED.02 of
9600LSY/LHR Technical Handbook.
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
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
13 / 96
Quick Guide
It allows to access immediately the most frequently needed operative pieces of information
contained in this handbook and in other related handbooks.
SWP DESCRIPTION
This part lists and describes the Software Packages this Handbook refers to, and includes the
following chapters:
ED
INSTALLATION
This part describes in detail the operations necessary for the SWP installation and upgrading
(ECT parts and equipment parts) and includes the following chapters:
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
14 / 96
APPENDICES
In this part some additional information and instructions are given.
This part includes the following chapters:
General information
Software management
Appendices
Please read chapter Document guide at beginning of SECTION 2: LHR NE MANAGEMENT for a
more detailed guide.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
15 / 96
This handbook is a collection of documents (each contained in a specific section) which can
have editions different from one another.
The section edition indicated in the following table is that of the corresponding document
enclosed in the handbook.
The Edition and the completion date of the whole handbook are those of section 1 (HANDBOOK
GUIDE).
Tab. 2. Handbook history
HANDBOOK EDITION
01
02
03
04
05
06
SECTION EDITION
INTRODUCTION
01
02
03
04
LHR NE MANAGEMENT
01
02
03
04
LHR NE MAINTENANCE
01
02
02
02
SIBDL MANUAL
01
02
02
02
Ed.02 issued on March 08, 2002 has been done mainly to correct some errors in Section 2 LHR NE
MANAGEMENT. Other changes are relevant to the handbook quality improvement, in particular:
a new QUICK GUIDE at the beginning of handbook allows to access immediately the most frequently
needed operative pieces of information contained in this handbook and in other related handbooks.
a new chapter Document guide in all sections, for better leading to the desired information and for
better tracing changes in the various editions.
in all sections, some chapters have been shifted with respect to each other, for more logical
information sequence.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
16 / 96
Security Management extension to support different Operator profiles (see para.3.1.1 on page 33
in this section)
On Power Measurements function, some power values have been removed (see chapter Radio
Parameters in section 2 LHR NE MANAGEMENT)
Not Intrusive BER Measurements function has been introduced (see chapter Port View in section
2 LHR NE MANAGEMENT)
Moreover:
the description of RFCOH Management (feature already present in previous SWP version but not
documented in handbook Ed.02) has been introduced (see new chapter Way side traffic and
service channels protection management in section 2 LHR NE MANAGEMENT)
other modifications have been introduced in sections 1 and 2 for handbook quality improvements and
error corrections.
1.5.5 Notes on Ed.04
Ed.04 issued on July 22, 2002 has been done to align the handbook to the SWP Version 1.0.10 (see
para.3.1.2 on page 34 in this section). New features and specific modifications introduced by this Version
are the following:
On all alarms a specific management of Additional Text field has been inserted.
Such field can be displayed by Operator through Alarm Surveillance ECT/SH tool as additional
information to better understand and identify associated entity.
Additional Text field is not available on related records stored inside Alarm Log.
A new feature to activate from ECT a procedure for FPGA upgrade has been introduced.
Moreover other modifications have been introduced in sections 1 and 2 for handbook quality
improvements and error corrections.
Revision bars point out major (listed above) and minor (not listed above) modifications with respect to
previous edition.
Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
17 / 96
The document history hereafter reported is relevant to this section INTRODUCTION. At the beginning
of the other sections making up this handbook, there is a document history specific for the section.
= new part
= modified part
= part unchanged
02
03
04
Document guide
SWP DESCRIPTION
System overview
Hardware installation
APPENDICES
11
ED
12 Documentation guide
04
05
INSTALLATION
01
m
m
m
n
n
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
18 / 96
DEM: DEModulator
EB: Errored Block
EC: Equipment Controller
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
19 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
20 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
21 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
22 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
23 / 96
XC: CrossConnection
WST: Way Side Traffic
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
24 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
25 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
26 / 96
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
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.
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.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
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.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
27 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
28 / 96
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SWP DESCRIPTION
ED
SECTION CONTENT
PAGE
31
33
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
29 / 96
The symbol
Handbook.
In the documentation on CDROM they represent hyperlinks to the handbooks referenced to.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
30 / 96
Refer to para.1.4 on page 14 for an overview of the scopes and contents of this part.
2.1 General
The software products are distributed by Alcatel in a CDROM.
In this CDROM are contained:
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 EMLUSM ).
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 (only one for this equipment).
They are referred both to the Network Element software features and to the Craft Terminal software
features.
Name
SWP REG. 9600LSY R.1.0
N.B.
ED
04
Factory
Part Number
N.B.
415.201.006 E
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
31 / 96
Factory
Part Number
700.500.008 J
700.500.009 K
700.500.0010 F
700.500.011 U
700.500.012 V
700.500.013 W
700.500.014 X
Name
N.B.
3
SWLRCT ( Remote Craft Terminal )
9600LSY Rel 1.0 LICENCE FEE
N.B.
ED
04
700.500.015 Y
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
32 / 96
Every Software licence is identified by a denomination and a part number, listed on the following table.
With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 12.
In case you receive a SWP with version higher than that stated, please refer to
the documentation accompanying the SWP delivery to get this information.
N.B.
Pentium II 200MHz
64MB
(128MB suggested)
2GB
(4GB suggested)
12
(14 suggested)
1024x768 pixels
Additional HW requirements:
CDRom drive
Ethernet card (optional)
Floppy Disk drive (optional)
Additional SW requirements:
Windows NT 4.0 SP3 or Windows 2000
Netscape Communicator or MS Internet Explorer 4.x
Reference firmware release and related specific contents are the following:
SWP9600LSYSU
SU_ESC
SU_HK
SU_SMA
SU_RRA_STBY
SU_RRA
SU_MODEM128_STM1
SU_MODEM128_STM0
SU_TRI
SU_FANS
SU_ROUTER_LH
DAIANA
ENTONI
SCIARON
NUNZIA
SANDRA
ED
04
V1.0.12
V2.1.4
V2.0.2
V2.1.6
V2.1.8
V2.1.7
V2.1.9
V2.1.8
V2.0.13
V2.0.2
V2.0.1
V1.0.1
V1.0.7
V1.0.2
V1.0.7
V1.0.2
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
33 / 96
Version
Date
V1.0.10
Description
Version
V1.0.10
SWCECT9600LSY_V20
V2.0.21
SWCEC9600LSY_V20
V2.0.14
SWCRC9600LSY_V20
V2.0.22
SWCFD9600LSY_V10
V1.0.10
Version
V1.3
Description
Java 2 Run Time Environment
Q3CTP
V1.5.1.6
LLMAN
V1.2.1
USMMWCOMMON
V2.0.21
USMMWREGLSY
V1.0.10
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
34 / 96
With reference to the Versions stated on this page, please read carefully the
N.B. on page 12.
N.B.
DipSwitches details are hereafter reported, remember that 1 value correspond to Open or Off while 0
value corresponds to Close or On.
3.1.6.1 EQTYPE
EQTYPE field is fixed to 0110 (Dec. 6) to indicate Long Haul system (there are no Dipswitch banks to
set).
3.1.6.2 BKPV (BacKPanel Version) field
According to following Tab. 6.
Tab. 6. ESC DipSwitch Bank I4 setting
BKPV
I4 switches
Dec
Description
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
35 / 96
Dec
Equip.
Type
Subrack
BB
Subrack TRI
STM0/
STM1
Space
Diversity
STM0
SRTRI1HET
0
0
0
0
0
1
1
0
1
2
1+1
HET
STM1
SRBB11
STM0
SD
STM1
SD
SRTRISD1HET
0
STM0
SRTRIN
STM1
N+1
SRBBN1
STM0
SD
STM1
SD
SRTRISDN
0
STM0
SRTRIN
STM1
N+0
SRBBN0
10
STM0
SD
STM1
SD
SRTRISDN
0
11
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
36 / 96
INSTALLATION
SECTION CONTENT
ED
PAGE
39
53
59
64
65
71
71
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
37 / 96
The symbol
Handbook.
In the documentation on CDROM they represent hyperlinks to the handbooks referenced to.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
38 / 96
Refer to para.1.4 on page 14 for an overview of the scopes and contents of this part.
4 SYSTEM OVERVIEW
This chapter replicates some information still present in the 9600LSY/LHR Technical Handbook, that can
be useful as refresh for the Operator in charge of the equipment software management, and is organized
as follows:
on page 40
on page 41
on page 41
Equipment provisioning
on page 45
on page 51
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
39 / 96
The LHR system can interface from two up to eight channels (STM0/STM1 Electrical or Optical signals
and the corresponding Radio parts) and up to eight WST channels. The system configurations allowed
are with Radio Protection Switching (N+1 without/with Occasional Traffic) or without Radio Protection
Switching (N+0), according to the following table:
Tab. 8. LHR Terminal Regenerator System Configurations
SYSTEM CONFIGURATION
N+0
N+1
N+1 &
Occasional
(1:N)
ALL
CH
CH
CH
max WST
2+0
1+1
1+1
& Occ.
2 unpr.
or 1 prot.
3+0
2+1
2+1
& Occ.
3 unpr. or
1 prot.+1 unpr.
4+0
3+1
3+1
& Occ.
4 unpr. or
1 prot.+2 unpr.
5+0
4+1
4+1
& Occ.
5 unpr. or
1 prot.+3 unpr.
6+0
5+1
5+1
& Occ.
6 unpr. or
1 prot.+4 unpr.
7+0
6+1
6+1
& Occ.
7 unpr. or
1 prot.+5 unpr.
8+0
7+1
7+1
& Occ.
8 unpr. or
1 prot.+6 unpr.
NR. of
channels
unpr.= unprotected
prot.= protected
Occ.= occasional
Tab. 9. Couples of Radio Channels that can be used for protected service channels and WST
CHx
0
0
1
1
8
ED
04
CHy
1
9
2
9
9
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
40 / 96
TRU
RRA/MODEM
AND ACCESS
AREA
(BASEBAND
SHELF)
ADDITIONAL
HOUSEKEEPING
(optional)
FANS FOR
RRA/MODEM
TRU
1650
SMC
SHELF
RRA/MODEM
AND ACCESS
AREA
(BASEBAND
SHELF)
Rx
BRANCHING
Rx
BRANCHING
TRANSCEIVER
SHELF
TRANSCEIVER
SHELF
Tx
BRANCHING
Tx
BRANCHING
REGENERATOR
WMSN
FANS FOR
1650SMC
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
41 / 96
S
Y
S
C
O
S
E
R
V
R
M
R
D
A
0
1
M
D
1
R
M
R
D
A
2
2
R
M
R
D
A
3
3
P
S
F
1
24 25
R
M
R
D
A
4
4
R M
R D
A 5
5
R
R
A
6
M
D
6
R M
R D
A 7
7
R M
R D
A 8
8
R M
R D
A 9
9
P
S
U
0
P
S
U
1
P
S
U
2
P
S
U
3
P
S
U
4
P
S
U
5
P
S
U
6
P
S
U
7
P
S
U
8
P
S
U
9
P
S
F
2
26
27
28
29
30
31
32
33
34
35
36
2 3
R
R
A
0
10 11 12 13 14 15 16 17 18 19 20 21 22 23
Fig. 2. Base Band shelf board equipment (slot numbering and board type and numbering)
T
R
I
0
T
R
I
1
T
R
I
2
T
R
I
3
T
R
I
4
T
R
I
5
T
R
I
6
T
R
I
7
T
R
I
8
T
R
I
9
10
Fig. 3. Transceiver shelf equipment (slot numbering and board types and numbering)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
42 / 96
RRA
Performs the following main functions :
b)
c)
MD Modem unit
Performs the following main functions:
Terminal modulator
Terminal demodulator
XPIC
STM1 Modem with one 2 Mbit/s WST service stream: to be used in both alternate and copolar
frequency arrangements with all the spacings including 28 MHz.
The STM0 Modem without WST service stream: utilized in 7 , 8 and 13 GHz bands with 14
MHz channel spacing in both alternate and copolar frequency arrangements.
Each modem can be equipped with an optional plugin board . This board gives the access to the
IF signals necessary to the demodulator for XPIC or for Space Diversity functionalities. In case of
presence of both functions the modem must be equipped with two identical plugin boards.
d)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
43 / 96
Channel communication for TMN utilizing a QB3 interface (BNC connector) info model based
F interface (RS232 toward the local PC) (SUBD 9 pin connector) towards Local Craft
Terminal
f)
g)
h)
i)
ED
TRI Transceiver
Performs the following main functions:
The transmitter includes an IF amplifier, a SSB up converter, a local oscillator and a RF power
amplifier.
The utilization of a high rejection SSB upconverter permits to avoid the use of a RF filter at the
output, allowing a wideband utilization of the unit.
The Automatic Transmitted Power Control (ATPC) function is included in the transceiver in
order to decrease the Tx power output and dissipation in case of normal propagation and to
push the maximum power up in deep fading conditions. This function may be disabled and the
level of the transmitted RF power can be manually set by Craft Terminal configuration.
The receiver includes a low noise RF preamplifier, an automatic imagine rejection down
converter, an IF filter, a main amplifier with AGC and a local oscillator.
A space diversity receiver, to be used in junction with a baseband signal combiner, is also
available as countermeasure to the selective fading due to the multipath propagation of the
signal.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
44 / 96
e)
in Base Band shelf, units SYSCO, SERV, PSF1 and PSF2 are always equipped
b)
the number associated to RRA, MD and PSU groups is related to physical (but not necessarily also
logical) channel (0 9). The same number identifies the associated TRI
PHYSICAL CHANNEL
c)
TR SHELF
RRA0
MD0
PSU0
TRI0
RRA1
MD1
PSU1
TRI1
....
....
....
....
....
RRA9
MD9
PSU9
TRI9
only 8 RRA, MD and PSU groups and the associated TRI can be equipped at most. The slot positions
that must be used depend on the system configuration; in particular:
1)
with single polarization configurations, RRA, MD, PSU and TRI groups must be equipped in
the logical number sequence 0, 1, 2, 3, 4, 5, 6, 7 (see Fig. 6. on page 47).
Thus, in these configurations, RRA, MD, PSU and TRI groups 8 and 9 are never equipped, as
depicted in Fig. 4. herebelow;
S R
R
R
R
R
E R
D
D
S R
D
D
A
A
A
A
0
3
C V
2
1
2
1
3
0
O
R M R M R M
R D R D R D
D
A 5 A 6 A 7
A
4
5
4
7
6
R
R
T
R
R M R M
R D R D
A 8 A 9
9
8
UNITS
NEVER
EQUIPPED
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
45 / 96
with double polarization configurations, RRA, MD, PSU and TRI groups must be equipped in
the sequence 0, 8, .... (see Fig. 7. on page 48, Fig. 8. on page 49 and Fig. 9. on page 49).
Thus, in these configurations, RRA, MD, PSU and TRI groups 4 and 5 are never equipped, as
depicted in Fig. 5. herebelow;
S R
R
M
R
R
E R
D
D
S R
D
D
A
A
A
A
0
3
C V
1
2
2
1
3
0
O
R M R M R M
R D R D R D
D
A 5 A 6 A 7
A
4
5
4
7
6
R M R M
R D R D
A 8 A 9
9
8
R
R
UNITS
NEVER
EQUIPPED
d)
ED
in the unused slots, dummy plates mus be equipped to ensure EMC performance as well as
equipment correct ventilation;
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
46 / 96
2)
a)
If the branching unit utilizes a single polarization, the transceivers and the branching unit will be
added using the slots starting from left and going toward the right side of the subrack, as shown in
the next Fig. 6.
The maximum channel number depends on the channel plan. In every case the maximum number
of transceiver that can be housed in the subrack is 8.
The slot used for the protection transceiver (slot 1) is fixed and it is the first on the left of the subrack.
The example reported in the figure is limited to 4 channels.
1+1/2+0 configuration
expansion to 2+1/3+0
expansion to 3+1/4+0
H (V)
Fig. 6. Single polarization per rack expansion procedure in the transceiver subrack
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
47 / 96
If the branching unit utilizes two antenna polarizations , the transceivers and the branching unit
will be added installing them stating from the side walls and filling the subrack going toward the
subrack centre, in position left or right depending on the polarization of each transceiver, as shown
in the next figure.
The slot used for the protection transceiver (slot 1) is fixed and it is the first on the left of the subrack.
So, the antenna polarization of the radio channel used for protection (H or V) defines which branching
(H or V) will be installed at the left side of the rack. For the above reason, it is important to keep
in mind that H or V positions are not strictly associated to the left or right side of the subrack.
The maximum channel number depends on the channel plan.
The example reported in Fig. 7. is limited to 4 channels. It refers to a system with spare channel on
H antenna polarization and, consequently, with transceivers and branching connected to H
polarization on the left side of the subrack.
1+1/2+0 configuration
expansion to 2+1/3+0
(adding 1 RT on V pol)
expansion to 3+1/4+0
(adding 1 RT on H pol)
2 4
V V
H
2
2
1
4
1
4
5
Fig. 7. Two polarization per rack expansion procedure in the transceiver subrack with the H channels
on the left side
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
48 / 96
b)
c)
The next Fig. 8. shows the other possibility, in which the spare channel (2) utilizes the V polarization
and, consequently, the transceivers and branching are connected to V polarization and are
installed on the left side of the subrack.
1+1/2+0 configuration
(1 RT on H pol and
1 RT on V pol)
expansion to 2+1/3+0
expansion to 3+1/4+0
(adding 1 RT on V pol)
(adding 1 RT on V pol)
Fig. 8. 2 polarization per rack expansion procedure in the transceiver subrack with V channel on the
left side
The above figure shows only two of the possible expansions that depend on the mixing of (H) and
(V) transceivers that must be utilized.
d)
The next Fig. 9. gives an example of the installation of the units in case of frequency reuse technique
utilization in a 7+1 protected terminal. At first, the terminal utilizes the first 4 channels (with channel
4 V as spare channel). The successive expansion of the system is performed adding the channels
working on the same frequencies but transmitted on the opposite antenna polarization.
3+1/4+0 configuration
7+1/8+0 configuration
1 3
4 2
3 1
V V
H H
H H
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
49 / 96
Fans provisioning
FANS SHELF provisioning
Presently, there can be either one or two FAN shelves, see Fig. 1. on page 41:
b)
FAN shelf for 1650SMC is mandatory whenever the 1650SMC shelf is equipped.
FANSL
A
FANSL
B
equipped
not equipped
POLARIZATION
single polarization
(see Fig. 6. on page 47)
two antenna polarizations
(see Fig. 7. on page 48)
CONFIGURATION
FANSLA
FANSLB
up to
2+1 / 3+0
NE
3+1 / 4+0
all
As far as the ADMshelfs FANSshelf is concerned, only one FAN ASSEMBLED unit is envisaged
(FANSL B, on the rack right side).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
50 / 96
a)
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 1320 CT.
For each station an ALCATEL proprietary Software Package (SWP) is to be employed:
Equipment Management
Transmission Management
Test management
Synchronization management
Radio Management
Overhead Management
Connection Management
Software Management
Security Management
Support Management
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 Equipment
Controller, to zoom and perform a complete set of management operations on all the reachable SDH
NEs in the SDH.
The Remote NE can be physically reached through QB3/Qecc.
The Remote Craft Terminal feature applies in NR5 to both Q3 and QB3* NEs, with the exception of
DXC. The feature is basically the same as for NR3 NEs, with the usual difference related to the
support of TSDIM interface for the management of Q3 NEs.
Despite the fact that this is supposed to be a NE related feature, it becomes a network feature
considering that the network can be composed of both Q3 and QB3* NEs and that an harmonization
is necessary between the two technologies.
The IMCT is able to manage both Q3 and QB3* NEs (in the sense that both QB3* and Q3 application
are working simultaneously), but it shall be connected to a Q3 NE. Viceversa Nectas CT will keep
on being able to manage only QB3* NEs, and it shall obviously be connected to a QB3* NE.
Its worth reminding that 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).
As far as DXC is concerned, the RECT feature is not supported, i.e. a DXC CT can be connected
to only one DXC at a time.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
51 / 96
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 QB3 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 SDH network the maximum number of QB3 NEs equipped with the RECT function are 32
and the maximum number of NEs (QB3* NEs and QB3 NEs) manageable by the RECT function
are 64. These figures identify what it is understood as small SDH network for which the RECT
function may substitute the Element Manager.
2)
3)
4)
5)
6)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
52 / 96
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 (64),
the number of the QB3 NEs (32), the number of the QB3* NEs (32), the number of associations
permanently open (31) between the CT and the remote NEs.
RRA
SW
RFCOH
DCCR
MD
TR
WST 2Mb/s
RRA
RFCOH
SW
MD
TR
DCCR
WST 2Mb/s
CMI 1
RRA
DCCR
ECT
RFCOH
SW
MD
TR
DCCR
F
EOW
QB3
OS
SC
DCCR
SERVICE
64 Kb
WST 2Mb/s
DCCR
DCCR
CMI 0
RRA
DISTRIB.
MD
RFCOH
TR
RADIO
PROTECTION
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
53 / 96
a)
Interfaces:
The LHR NE can be controlled by the OS (e.g. Alcatel 1353SH) through the Q interface.
ECT (Equipment Craft Terminal, briefly Craft Terminal) can be connected to the LHR unit
through a RS232 interface (F interface, see Fig. 13. on page 56).
b)
2)
Peripheral Units
Peripheral units (SERVICE, RRAs, MODEMs, RTs, as well SYSCO itself) 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 (SYSCO) with the same activestandby duplication
described before for SYSCO (SYSCO can also decide autonomously to download the
programs in Supervisory Units Flash Eprom of the Peripheral Units).
3)
As explained before, whole Equipment configuration data (together with programs) is contained
in SYSCO boards ESCON subunit Flash Card. Most (but not all) configuration data set is
named MIB and can be saved as a file in the Craft Terminal (or OS) environment, as well can
be restored in the Flash Card retrieving this file from the Craft Terminal (or OS).
Data that cannot be saved/restored are those relevant to network routing, that is, according to
the Craft Terminal Men:
Configuration Comm.Routing
Local Configuration
OS Configuration
NTP Server Configuration
LAPD Configuration
Ethernet Configuration
RAP Configuration
MESA Configuration.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
54 / 96
Fig. 12. on page 55 roughly depicts the LHR main parts containing the local SW and the interfaces with
the Operator:
ESC
ESCON SUBUNIT
F
Q
EQUIPMENT
CONTROLLER
FLASH
CARD
RADIO CONTROLLER
SUPERVISOR UNIT
RAM
ESC
SUPERVISOR UNIT
CANBUS
RAM
SERVICE
SERVICE
SUPERVISOR UNIT
FLASH
EPROM
RRA0
RRA
SUPERVISOR UNIT
FLASH
EPROM
MODEM0
MODEM
SUPERVISOR UNIT
FLASH
EPROM
RT0
RT
SUPERVISOR UNIT
FLASH
EPROM
RRAn
RRA
SUPERVISOR UNIT
FLASH
EPROM
MODEMn
MODEM
SUPERVISOR UNIT
FLASH
EPROM
RTn
RT
SUPERVISOR UNIT
FLASH
EPROM
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
55 / 96
Flash Card
F INTERFACE
System Controller
main board
TOP SIDE
INSERTION
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
56 / 96
1)
A further SW application, also available in the PC and OS environment and named SIBDL
(Standard Image Binary Download), deals with SW download in special cases, which are
detailed in the following. The physical interface for running this application from Craft Terminal
is F interface.
The installation and use of SIBDL is detailed in the dedicated Section of this handbook:
SIBDL
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
57 / 96
5.2.1 WMSN
RRA
SW
RFCOH
MD
CMI 7
DCCR
WST 2Mb/s
RRA
RFCOH
SW
MD
TR
DCCR
WST 2Mb/s
1650SMC
CMI 2
RRA
RFCOH
SW
MD
TR
CMI 1
DCCR
DCCR
CMI 0
EOW
F
QB3
SC
Nx64
Kb
DCCR
SERVICE
64 Kb
WST 2Mb/s
DCCR
DCCR
RRA
ECT
OS
DISTRIB.
RFCOH
MD
TR
RADIO
PROTECTION
For the detailed description of the 1650SMC EMLUSM screens please refer to the 1650SMC handbooks.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
58 / 96
Before reading this chapter, it is suggested to read (if not yet done) previous chapter 5 on page
53.
1) SWP LOADING IN PC
MSNT ENVIRONMENT
2) NEW SWP
6) MIB
INSTALLATION
BACKUP
CRAFT TERMINAL
3) NE SWP LOADING
INTO EQUIPMENT
CONTROLLER
(if necessary)
DURATION
2 hours ABOUT
S
Y
S
C
O
5) NE CONFIG.
4) SW DOWNLOAD
TO SUPERVISOR UNITS
(if necessary)
DURATION
5 minutes ABOUT
DATA MNGT
7) MIB
RESTORE
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
59 / 96
Taking into account that, as previously explained, the SW management should be distinguished into:
(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)
(7) NE configuration data restore from Equipment Craft Terminal (MIB restore, if necessary)
purpose of this chapter is to give summary information about software management in the various
situations.
N.B.
ED
Please refer to para.12.2.2 on page 88 for the meaning of SWP Release, Version and Patch
Level.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
60 / 96
1)
Network Element(s) 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(s) 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 para.8.4
on page 66. After that, the situation is equal to that of point 1 ) above.
3)
Network Element(s) already configured with a SWP release older than that present in the
Craft Terminal.
NE
ECT
ECT release > NE release
B.B.x
A.A.y
versions unmeaningful
Refer to chapter 10 on page 71.
After that, the situation is equal to that of point 1 ) above.
Both Network Element(s) and Craft Terminal already configured with a SWP release older
than that made available by the a new SWP RELEASE.
4)
NE
ECT
A.B.c
SWP
CDROM
D.E.f
Both Network Element(s) and Craft Terminal already configured with a SWP version
older than that made available by the a new SWP version (SAME RELEASE)
NE
ECT
A.B.c
A.B.c
SWP
CDROM
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.1.0.6), in the case a newer version of the same A.B SWP package has to be installed
(e.g.1.0.8).
Refer to chapter 9 on page 71.
After that, the situation is equal to that of point 1 ) above.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
61 / 96
2)
use the SW download through SIBDL program (refer to the specific section in this handbook):
SIBDL
b)
proceed as specified on para.6.3 on page 63, taking into account that step a ) (SW download) could
be not strictly necessary.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
62 / 96
a)
b)
c)
d)
Reinsert the Equipment Controller card and wait about 2 minutes for ESCON restart: in this situation
MIB structure is reset to a default configuration.
e)
Extract again the Equipment controller card and set switch 2 to OFF position.
f)
Reinsert the Equipment Controller card and wait about 2 minutes for ESCON restart.
g)
restoring MIB data base previously saved, as indicated in dedicated sections of this
handbook:
LHR Ne Management , chapter MIB management
and manually reconfiguring network configuration data not saved in MIB (ref. point 3 ) on
page 54).
h)
i)
j)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
63 / 96
ED
04
957.207.022 A
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
7 HARDWARE INSTALLATION
SC.1:INTRODUCTION
3DB 02838 AA AA
96
64 / 96
Before starting the installation procedures, it is suggested to give a look to previous chapters
5 on page 53 and 6 on page 59.
b)
2)
3)
4)
5)
NE Profile management
6)
dipswitch check
8)
9)
LHR SW download
c)
Commissioning
d)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
65 / 96
the autoinstallation process starts with the installation of 1320CT basic platform software
product, meant to reside in PC environment only, with the aim of interfacing the NEs and
allowing their management.
b)
when so requested by the installation procedure, confirm all default values (N.B.)
c)
d)
when so requested by the installation procedure, confirm all default values (N.B.)
N.B.
These phases are fully detailed, together with the various options, in:
1320CT Basic Craft Terminal Operators Handbook ,
section INSTALLATION
WARNING: the cited section is NEtype independent, so you do not find 9600LSY
specific screens but example screens; nevertheless you should not find problems
in understanding the option meanings, that are valid for all NE types.
e)
More information about 9600LSY software package(s) are given in SWP DESCRIPTION (chapter
3 on page 33).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
66 / 96
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).
PC hostname
CT configuration
Screen settings
In order to setup these configurations, refer to:
1320CT Basic Craft Terminal Operators Handbook ,
section INSTALLATION, chapter Craft Terminal Configuration
ED
This phase is not necessary to going on with the installation. If necessary, it can be done when
decided.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
67 / 96
N.B.
This description is retrieved from 1320CT Basic Operators Handbook, section EML
construction, chapter Administrating files, paragraph Software Administration and is
repeated here for ease of operation.
This phase must be manually carried out by the Operator and has the scope of making the new equipment
software package available for its downloading toward the equipment controller and the peripheral units.
This operation is independent from the NE management state and must be executed with the following
procedure:
1)
From the Supervision pull down menu select the File Administration and then the Software
Administration option, as shown in Fig. 17. herebelow.
2)
In the figure that opens (see Fig. 18. herebelow as an example) select the directory where the
NE software package is installed: Alcatel / usm / ect / swdw / <equipment name> / <version>
/ <descriptor file>.
The NE software package can also be selected from the CDROM used for the installation of
the NE software. In this case, after inserting the CDROM in the driver, choose the following:
ect / swdw / <equipment name> / <version> / <descriptor file>.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
68 / 96
3)
Click on Open to activate the installation file selected. At the end of the process, a confirmation
message is displayed.
4)
At this point the NE Software Package is installed in another directory and available to be
downloaded on the Network Element.
2)
3)
4)
After having connected to the NE Network, the Operator should decide what to do with ANTP (disabled,
Client, Server).
2)
3)
4)
i.e. , after having loggedin the NE, according to the Craft Terminal Men:
ED
04
a)
b)
then, after about 2 hours, Download Unit Info Activate to activate software.
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
69 / 96
8.6 Commissioning
Data definition
In order to manage this data, refer to the sections in this handbook:
LHR Ne Management
2)
Data save
In any case, after having completed the Equipment Configuration, the Operator should save the
relevant data:
ED
04
writing somewhere data that are not saved by MIB backup (see point 3 ) on page 54).
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
70 / 96
ECT and equipment are running with one of the Software Packages with P/N indicated in Tab. 4. on
page 31 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.
Carry out the installation of the new SWP version in the ECT environment, as indicated in
para.8.4 on page 66.
2)
The subsequent phases depend on the compatibility of MIB structure between previous and
new SWP versions. This MIB compatibility is indicated in the suitable paragraph of chapter 3
in this document.
N.B.1
Usually the MIB structure is fully compatible inside a SWP Release, so that the
following case a ) must be taken into consideration.
N.B.2
The indication given in the paragraph is relevant to the version stated in para.3.1.2
(page 34). In case you receive a version higher than that stated, please refer to the
documentation accompanying the SWP delivery to get this information.
a)
b)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
71 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
72 / 96
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
APPENDICES
ED
SECTION CONTENT
PAGE
75
83
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
73 / 96
Refer to para.1.4 on page 14 for an overview of the scopes and contents of this part.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
74 / 96
F Interface
Port COM
Remote
Modem
Local
Modem
b)
Remote Modem
Sportster Flash
Sportster Flash
TD 32 AC
TD 32 AC
TD 32 AC
1AA 00014 0004 (9007) A4 ALICE 04.10
Sportster Flash
Testing the connection with different types of modems is fully on Customers charge.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
75 / 96
PC/ECT (DTE)
DCD
TD
RD
DTR
DSR
RTS
CTS
GND
In the following figures, the cables for the connections are described:
8
3
2
DCD
TD
RD
4 RTS
5 CTS
6 DSR
20 DTR
7 GND
1
2
3
4
6
7
8
5
F Interface (DCE)
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
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
76 / 96
Connect the local modem to the PC/ECT with the cable of Fig. 20. on page 76.
2)
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>
5)
ED
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
77 / 96
For confirmation, the modem configuration can be checked writing the command
ATI4<Return> in the HyperTerminal program window.
Information displayed should be as follows:
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
N.B.
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
S02=043
S09=006
S18=000
S28=008
S35=000
&I0
&T5
&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)
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.
For confirmation, the modem configuration can be checked writing the command
ATI4<Return> in the HyperTerminal program window.
Information displayed should be equal to that displayed for the local modem, with only the
difference for field S00:
S00=001
ED
(Autoanswering setting)
04
S01=000
S02=043
S03=013
S04=010
S05=008
S06=004
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
78 / 96
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)
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
Connect the local modem to the PC/ECT with the cable of Fig. 20. on page 76.
3)
4)
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
5)
Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return>
AT&K0<Return>
ATA<Return>
AT&W0<Return>
AT&Y0<Return>
6)
ED
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
79 / 96
For confirmation, the modem configuration can be checked writing the command
AT\S<Return> in the HyperTerminal program window.
Information displayed should be as follows:
AT\S
ED
04
CMD
&A
&B
&C
&D
&G
&K
&L
&Q
&R
&S
&T
&X
&Y
\A
\G
\K
\N
DESCRIPTION / OPTION
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
80 / 96
N.B.
Connect the remote modem to equipments F interface with the cable of Fig. 21. on page 76.
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)
4)
5)
Connect the local modem to the PC/ECT (with the cable of Fig. 20. on page 76.) 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)
8)
On the PC, activate program HyperTerminal and configure the PCLocal Modem serial line with
the following parameters:
* Bits per second: 38400
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
9)
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).
10 ) Wait the message indicating the successful connection between local and remote modems.
N.B.
(Sportster Flash)
(TD 32 AC)
13 ) 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
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
81 / 96
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
82 / 96
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
12 DOCUMENTATION GUIDE
This chapter contains all information regarding the Customer Documentation and is organized as follows:
INFORMATION REGARDING 9600LSY REL.1.0 CUSTOMER DOCUMENTATION
Productreleaseversion handbooks
on page 84
gives the list and description of the Customer Documentation set this handbook belongs to.
ED
on page 87
on page 87
on page 88
Documentation on paper
on page 92
Documentation on CDROM
on page 94
on page 96
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
83 / 96
This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for
9600LSY Rel.1.0 product release
Please refer to following para.12.2 on page 87 for a general description of Alcatel Customer
Documentation system.
The list of handbooks given here below is valid as at the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available as at the issue date of this
Handbook.
REF
HANDBOOK
FACTORY
Part No.
955.203.292 Q
THIS
HDBK
or NOTE
955.203.302 S
[B]
Provides information regarding Equipment installation, according to Alcatel
Installation Engineering Dept. rules.
9600LSY/LHR Rel.1.0 & 2.0
Line Up Guide
955.203.312 K
[C]
Provides information regarding equipment line up, according to Alcatel Installation
Engineering Dept. rules.
Tab. 12. Handbooks related to the specific product SW management and local product control
REF
HANDBOOK
9600LSY Rel.1.0
CT Operators Handbook SWP 1.0
FACTORY
Part No.
957.207.022 A
THIS
HDBK
or NOTE
[D]
Provides 9600LSY screens and operational procedures for Equipment SW
management and maintenance.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
84 / 96
REF
[E]
HANDBOOK
FACTORY
Part No.
955.203.374 Z
THIS
HDBK
or NOTE
Describes the measurement procedure for the interference searching in the various
RF bands used by Alcatel Radio Transmission products.
Tab. 14. Handbooks common to Alcatel Network Elements using 1320CT platform
REF
HANDBOOK
1320CT Version1.3.x
Basic Operators Handbook
FACTORY
Part No.
957.130.542 E
[F]
Provides general information and operational procedures common to all 1320CT
(Craft terminal) of Alcatel InfoModel Network Elements.
1330AS Rel.5.0
Operators Handbook
THIS
HDBK
or NOTE
ED.03
on
957.130.442 A
[G]
Provides detailed information and operational procedures regarding the alarm
Surveillance software embedded in the 1320CT software package.
ELM Rel.5.0 Operators Handbook
[H]
957.130.462 E
Provide detailed information and operational procedures regarding the Event Log
Management software embedded in the 1320CT software package.
REF
[I]
ED
417.200.017 D
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
85 / 96
REF
HANDBOOK
[J]
FACTORY
Part No.
955.100.922 C
417.100.026
REF
[K]
Contains, in electronic format, the following handbooks: REF.[J]
12.1.2.2 Handbooks and CDROMs of 1650SMC
1650SMC has its own:
Technical Handbook
Installation Handbook
Commissioning Handbook
CT Operators Handbook
CDROM containing the above cited handbooks.
Their P/Ns are not indicated here, as they depend on the Product release and Software Package version.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
86 / 96
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)
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;
N.B.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
87 / 96
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. 9600USY is a product (STM1/0 Urban Digital Radio Link).
b)
Product-releases
A product evolves through successive product-releases, which are the real products marketed
for their delivery at a certain product-release availability date. A certain product-release performs
more functionalities than the previous one.
E.g. 9600USY Rel.1.0 and 9600USY Rel.2.0 are two successive product-releases 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 product-release has been designed, engineered, and marketed for.
c)
d)
Patch Level
1.
0.
1.
0.
1.
0.
1.
1.
1.
0.
2.
0.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
88 / 96
N.B.
e)
Sometimes, different SWP Releases (within the same ProductRelease) are commercially
distinguished by different names, e.g. :
SWP version
1.0.x
1.0
1.1.x
1.0B
1.2.x
1.0C
Customer Documentation
A product-release(configuration) has its own set of standard Customer Documentation, usually
formed of several handbooks, i.e., in general:
an Installation Handbook
Software documentation:
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
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
89 / 96
a)
Technical Handbook
It is usually composed by a main handbook and enclosed documents. Information is divided into
the following levels (not necessarily in this sequence):
MAIN HANDBOOK:
GENERAL INFORMATION
INFORMATIVE LEVEL
OPERATIVE LEVEL
the equipments items (P/Ns, equipping rules, labels for remote inventory)
the unit assembly/subassembly and front panel drawings, with the usage description
of the access points (connectors, visual indicators, buttons)
Station Layouts (where applicable) : lists and describes the most common of all the
available system configurations envisaged for the specific configuration the handbook is
meant for. For each configuration a station layout (with cable interconnection diagram) and
a simple system block diagram are present.
Hardware Setting Documentation & Annexes : lists the enclosed documents having
P/N different from that of the handbook (they can be used also as annexes to other
handbooks) and describes how to use the Hardware Setting Documents enclosed.
ENCLOSED DOCUMENTS : Hardware Setting Documents and other documents for specific
purposes (typical examples: ODU repair procedures, branching detailed configurations and
drawings, etc.)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
90 / 96
b)
SECTION 1: INTRODUCTION containing the following main parts (not necessarily in this
sequence):
SWP description : lists and describes the Software Packages the Handbook refers to.
Installation : describes in detail the operations necessary for the SWP installation and
upgrading (ECT parts and equipment parts).
SECTION 2: NE MANAGEMENT : gives the description of the menu structure and of all the NE
functionalities available in the Craft Terminal. This section is organized in several chapters
grouped according to the following general scheme:
General information
Software management
Depending on the SWP contents, other sections can be present in the handbook, to describe other
specific applications or features.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
91 / 96
Handbook languages
Handbook standard language is English. As far as handbooks supplied in other languages,
translation is relevant to the text and the drawings within the text.
With regard to Operators Handbooks containing screen prints of the software applications, the
screens included are in the language envisaged by the applicative software supplied to the Customer
(e.g. an Operators Handbook translated in Russian has the screens in English if the user interface
is not in Russian).
Engineering documentation (like selected sheets of unit schematics and component layout given
only as hardware presetting documentation) is bilingual ItalianEnglish.
c)
Handbook identification
ED
the name of the configuration, if more than one is envisaged within the product-release,
the first two digits of the SWPversion as far as Operators Handbook is concerned,
.....
the handbook issue date. The date on the handbook does not refer to the date of printing, but
to the date on which the handbook source file has been completed and released for production.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
92 / 96
a)
d)
Handbook updating
The documentation is maintained updated according to the technical changes of the product it refers
to, provided that these technical changes does really impact Customer Documentation (e.g.:
generally, bugfixing releases do not impact the Operators Handbook). Updating of handbooks,
when necessary, is done synchronously with the products industrial technical change, in due time
for having the new product version and the handbooks associated new edition available at the same
time.
1)
the sections/chapters modified with respect to the previous edition are listed in a suitable
Handbook History Table in the Handbook Guide section;
a specific note in the same section sumsup the reasons for the change;
in the affected chapters, revision bars on the left of the page indicate modifications in text
and drawings (this is done after the first officially released and validated version).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks)
are not modified unless the new SWP version distributed to Customers implies
manmachine interface changes or in case of slight modifications not affecting the
understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the SWP
version marking, they are not replaced in the handbooks related to a subsequent
version if the screen contents are unchanged.
2)
A new product-release changes the handbook P/N and the edition starts from 01. In this case,
the modified parts of the handbook are not listed.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
93 / 96
Standards
CDROMs are generated according to ISO 9660 norms.
A master CDROM is obtained as follows:
each source document is converted into .pdf format by Adobe Acrobat Distiller 4.0;
bookmarks are generated for complex documents in order to make the navigation inside the
documents easier;
some hyperlinks, which make the navigation through the various handbooks easier, are
manually added. The following hyperlinks are standard:
from the INDEX document toward each individual file contained in the CDROM
from section Hardware Setting Documentation & Annexes of each Technical Handbook,
toward each specific document listed in the section itself (these documents could be
collected in a separate file).
The files processed in this way are then transferred on a PC where a master CDROM is recorded.
Suitable checks are made in order to have a virusfree product.
The CDROM can be used both in PC and Unix WS environments or any other environment for which
a suitable Reader has been envisaged by Adobe.
In order to open correctly the pdf files contained in the CDROM, the use of Acrobat Reader Version
4.0 at least is mandatory.
The CDROM does not contain the Acrobat Reader program. Getting it and installing it on the
Customer specific platform is on Customers charge.
c)
CDROM identification
ED
1)
by the following external identifiers, that are printed both on the booklet and the CDROM upper
surface:
2)
and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CDROM itself has been created.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
94 / 96
a)
d)
CDROM updating
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive
system, the AlcatelInformationSystem automatically rises a warning toward the Customer
Documentation department, indicating the list of CDROMs that must be updated to include the new
editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CDROM.
Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks
composing the collection.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
95 / 96
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)
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)
END OF DOCUMENT
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
96 / 96
a)
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 List of the editions and modified parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
11
11
11
11
12
14
14
15
15
17
19
20
21
22
22
23
24
24
25
26
26
3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
27
29
29
29
30
04
020715
updated
A.FUMAGALLI ITACO
03
020524
updated
A.FUMAGALLI ITACO
proposaldraft
A.FUMAGALLI ITACO
E.CORRADINI
CHANGE NOTE
APPRAISAL AUTHORITY
01A 011109
ED
DATE
C.NAVA ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
M.CORBETTA ITACO
ORIGINATOR
9600LSY REL.1.0
SWP REG.9600LSY R1.0
C.T. OPERATORS HANDBOOK
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
1 / 258
31
33
35
35
35
36
37
38
40
41
42
43
45
46
6 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Introduction and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Equipment configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Set and change or remove board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Board administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Setting a board in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Setting a board out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Consulting a Boards Administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.1 Remote Inventory Subrack Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.2 Remote Inventory Board Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 Show supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
47
50
75
77
77
77
77
78
79
79
81
82
7 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Board View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Port Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2 Show Supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
83
85
86
87
8 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.1 Physical Media option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.2 Optical Laser Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.3 Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.4 BER Not Intrusive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
89
90
91
93
94
97
101
101
101
102
103
105
107
109
111
113
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
2 / 258
115
115
115
116
120
122
11 RADIO PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 ATPC/Power and Threshold Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 ATPC Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Power Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Manual operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Power Setting in Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 ATPC Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Gain Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 HOP Section Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9 Squelch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10 Radio Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Frequency Reuse Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.12 Equalization Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.13 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14 V.C.O. State Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15.1 Power Measurement Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.16 Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
126
128
129
129
130
131
132
134
136
137
138
140
142
143
144
145
149
12 OVERHEAD MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.1 Cross-Connection Management dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.2 Main Cross-Connection dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.3 Search OH TP dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.8 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
151
151
154
155
157
158
161
163
164
165
166
13 LOOPBACK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 Types of Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Caution: recoverable and unrecoverable loopbacks (with RECT) . . . . . . . . . . . . . . . . .
13.3 Loopback management starting from Port view menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.1 Port Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.2 Loopbacks Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.3 Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Loopback management starting from Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.1 Loopback Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.2 Loopback Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
167
167
168
171
171
172
173
178
178
182
183
183
185
186
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
3 / 258
189
189
189
193
194
196
197
17 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.2 Supported Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.3 Granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.4 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.5 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3 Display Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.4 Display History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.5 PM Threshold Table Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6 PM Threshold Table Modification or Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6.1 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6.2 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
199
200
201
202
202
203
204
207
209
211
213
213
213
18 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1 General and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1.2 Software Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2 Software Download Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.3 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4 Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.5 MIB management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.6 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215
215
216
216
217
218
220
222
223
225
226
227
227
228
229
230
234
235
236
237
245
245
245
246
247
248
249
251
252
253
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
4 / 258
15 ALARMS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 Alarm Severity Assignment Profile (ASAP) management . . . . . . . . . . . . . . . . . . . . . . .
15.1.2 Allow/Inhibit Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
04
255
255
255
255
256
257
258
258
258
258
258
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
5 / 258
FIGURES
Fig. 1. LHR Main view organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 2. NE LHR Main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 3. Configuration of the Craft access state from the Equipment NE view in the OS mode. . . . .
Fig. 4. Getting and/or setting the local NE time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 5. NE Time dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 6. Set Manager List dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 7. Local Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 8. OS Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 9. NTP Server Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 10. LAPD Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 11. Ethernet Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 12. RAP Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 13. MESA Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 14. Equipment Overview NE level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 15. Equipment Overview Rack Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 16. Equipment Overview Subrack level ( example ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 17. Equipment menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 18. Selecting the Equipment ( Rack ) to display ( Open Object ) . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 19. Rack screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 20. Base Band screen with the selectable modules view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 21. SYStem COntroller card ( SYSCO ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 22. SERVice card ( SERV ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 23. Allowed Boards Equipment Types Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 24. MoDemodulator card ( MD 128 1W1 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 25. RRA card ( RRA 1W1 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 26. Selectable modules view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 27. Board view MD 128 1W1 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 28. Board view RRA 1 ( Electrical Interface ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 29. SDH Port view Electrical Interface ( RRA ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 30. PDH Port view ( RRA ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 31. Selectable Optical STM1 module view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 32. Board view Optical module STM1 ( IS11 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 33. SDH Port view Optical Interface ( Optical module STM1 ) screen . . . . . . . . . . . . . . . . . . . .
Fig. 34. Board view SERV screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 35. PDH Port view ( SERVICE ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 36. Power Supply Filter ( PSF 12 ) Board screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 37. Subrack Transceiver ( SRTRI 1 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 38. Transceiver card ( TRI 128 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 39. Board view ( TRI 128 ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 40. SDH Board view ( Rx ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 41. SDH Port view Rad_S ( Rx ) screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 42. SRFANS Subrack Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 43. Fans card Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 44. List of different boards relevant to an NE slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 45. Example of boards change with a Lock representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 46. Getting a boards administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 47. Software Description dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 48. Remote Inventory screen at Subrack Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 49. Update Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 50. Remote Inventory Output Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
04
16
28
29
31
31
33
39
40
41
42
44
45
46
47
48
48
49
53
54
55
56
57
57
58
59
60
61
62
63
63
64
65
66
67
68
69
70
71
72
72
73
73
74
75
76
77
78
79
80
80
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
6 / 258
ED
04
80
81
82
83
84
85
86
87
90
91
92
93
94
95
96
97
98
99
102
103
103
105
106
107
107
109
110
110
111
111
113
113
116
117
117
118
118
120
121
122
123
123
124
126
127
128
129
130
131
131
132
133
133
134
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
7 / 258
ED
04
135
136
136
137
137
138
139
140
141
142
142
143
143
144
145
146
148
149
150
150
154
155
156
156
158
160
161
162
163
164
164
165
166
166
167
167
167
168
169
170
171
172
173
174
174
175
175
176
176
177
177
178
179
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
8 / 258
ED
04
179
180
180
181
182
182
183
184
185
186
186
187
188
189
190
191
192
193
193
194
195
196
196
197
199
205
208
210
212
214
215
217
217
218
219
220
221
221
222
223
226
230
231
235
248
248
249
253
254
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
9 / 258
ED
04
14
51
151
151
152
152
153
213
238
240
241
243
243
244
244
244
250
250
257
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
10 / 258
TABLES
Tab. 1. Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 2. LHR N.E. Composition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 3. Termination Bytes for the RSOH OverHead related to the SERVICE card . . . . . . . . . . . . . .
Tab. 4. Termination Bytes for the RSOH OverHead related to the TPHDEV module . . . . . . . . . . .
Tab. 5. Termination Bytes for the RFCOH OverHead related to the SERVICE card . . . . . . . . . . . . .
Tab. 6. Termination Bytes for the RFCOH OverHead related to the TPHDEV module . . . . . . . . . .
Tab. 7. RSOHRFCOH Bytes crossconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 8. Maximum Performance Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 9. N+0/N+1 Base Band shelves slots configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 10. N+0/N+1 Base Band slots configuration shelf type dependent . . . . . . . . . . . . . . . . . . . . . . .
Tab. 11. Base Band 1+1 shelf slots configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 12. N+1/N+0 Transceiver shelves slots configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 13. N+1/N+0 Transceiver slots configuration shelf type dependent . . . . . . . . . . . . . . . . . . . . . .
Tab. 14. 1+1 Transceiver shelves slots configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 15. 1+1 Transceiver slots configuration shelf type dependent . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 16. Fan shelf slot configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 17. 1:N RPS protection type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 18. 1+1 RPS protection type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 19. Radio channels role for WST and Service Channels protections . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE
1.1 Scope
1.1.1 Document scope
In the following pages the description of the menu structure and of all the functionalities available in the
LHR Version 1.0 of the Craft Terminal is given.
1.1.2 Target audience
This document is intended for all users.
The documents that should be read before starting this document are:
The sections of this Handbook that should be read before starting this document are:
SECTION 1: Introduction
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Handbook Guide.
1.2.2 Glossary of terms
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
11 / 258
ED
GENERAL INFORMATION
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
12 / 258
SOFTWARE MANAGEMENT
APPENDICES
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
13 / 258
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. 1. indicates the handbook parts new and modified with respect to the previous edition.
Legend
n
m
blank
= new part
= modified part
= part unchanged
02
03
04
Document guide
NE management supervision
Equipment management
Board view
Port view
11
Radio parameters
12 Overhead management
15 Alarms management
17 Performance Monitoring
ED
04
13 Loopback management
18 Software Management
01
05
m
n
m
m
m
m
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
14 / 258
This chapter describes the organization of the LHR N.E., presented after the NE login.
First the view organization is introduced, then the accessible menu options are listed.
At the end, some further advices are given for Navigation principles.
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.
This document only comprises the information on the fields that differ according to the NE type:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
15 / 258
Severity alarms
synthesis
Menu bar
View title
View area
Message/state
area
Management
state control panel
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
16 / 258
The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph lists all menu options and then provides more details on the respective contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where they are detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
From Chapter 3 on page 27 details and operating information on all views are given. They are not
presented according to the menu option sequence, but according to a functional subdivision.
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).
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).
Supervision
(fourth column).
Download
(fifth column).
Radio
To show information about the functions and features of the radio Equipment (ATPC, Switch ,
Gain ).
Help
(last column).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
17 / 258
Other Menus
Equipment
To manage the NE as a whole by setting the boards which compose it. From the Equipment view
the Board view can be accessed.
Board
To show the physical port available in a specific board. It is the entry point for the Port view.
Port
To set and show (detailed alarm view) the transmission resources referred to the Port.
External Points
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
18 / 258
The menu bar also comprises other menus, presented as an alternative, only when a specific object or
option is selected.
Backward:
Forward:
Equipment:
External Points:
Refresh:
Open Object:
Allows to navigates and shows the contents of the selected object: the current
view changes.
It is equivalent to a double click on the selected object in the view area.
Open in Window:
Close:
Close the EMLUSM view, without stopping the supervision of the NE.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
19 / 258
This menu allows to set the general configuration of the NE and to show or modify some parameters, by
means of the following entries:
Alarm Severities:
Set SdhNe Alarm severities: Sends the Alarm Severity Assignment Profile to the equipment level.
NE Time:
Performance:
Comm/Routing:
Local configuration
OS Configuration
Overhead:
OH Cross Connection
OH Phone Parameters
OH Tp Creation
OH Tp Deleting
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
20 / 258
This menu allows to get information on the NE, by means of the following entries:
Alarms:
Performance data:
Not implemented
Log Browsing:
View Remote Inventory: Displays the remote inventory data, previously stored in the Craft Terminal
by means the upload remote inventory performed in the Supervisory
menu.
Abnormal Condition List: Displays the list of the object class and the name of the boards that are in
the abnormal condition.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
21 / 258
Access State:
Alarms:
Upload Remote Inventory:Stores the Remote Inventory data in the Craft Terminal.
Restart NE:
This menu allows to set the supervision states of the NE, by means of the following entries:
This menu allows to manage the NE software, by means of the following entries:
Initial download:
Units info:
Show the status of the software package installed in the NE memory banks.
Mib management
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
22 / 258
RPS:
Configure
=>Schema
=>Units
Static Delay
=> Rx Side
Switch
Synthesis
Extra Traffic
RFCOH:
Configure
Switch
Synthesis
Frequency:
Power Measurement:
ATPC:
This function allows the operator other to enable or disable the ATPC function
( Automatic Transmit Power Control ) of the equipment, also to modify the TX
power level.
Opens the following menu options:
ATPC Identifier
Squelch:
Gain:
Hop Trace:
This function allows the operator to verify one hop section trace of Equipment.
Frequency Reuse: Displays what is the Associated Channel ( Main/Reused ) in Frequency Reuse
case.
Equalization Delay: This function allows the operator to make the Equalization Delay measures.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
23 / 258
This menu allows to manage the NE as a whole, and to set the boards that compose it, by means of the
following entries:
Set:
Modify:
Remove:
Set in service:
Reset:
Software description:
Remote Inventory:
This menu allows to show the physical port available in a specific board (alarm synthesis and port symbol)
and to access the port view, by means of the following entries:
Port Access:
.Not implemented
Show supporting equipment: Allows to navigate to the upper subrack level. See para.7.2.2 on
page 87.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
24 / 258
TP configuration:
AU4 Concatenation:
Performance:
Loopback:
Physical Media:
of
the
TP
of
the
ports.
Refresh:
Allows to show a complete overview on the signal flow, opening all TPs
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
25 / 258
This menu allows to display and set the input/output environmental alarm (housekeeping alarm), by
means of the following entries:
Configuration:
Display:
2.2.11 Help
Not implemented
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
26 / 258
3 NE MANAGEMENT SUPERVISION
The LHR Main views are shown in the following figures ( see Fig. 2. on page 28 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
27 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
28 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Fig. 3. 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
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
29 / 258
Select the Supervision pull down menu. Then the Access State cascading menu in Fig. 3. on page
29, select the OS... option from.
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).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
30 / 258
4.1.2 Switching from the Craft Terminal access state back to the OS access state
The NE local time of a selected NE 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 get and/or set the local NE time.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
31 / 258
If the Network time Protocol (NTP) protocol is not supported, the NTP Protocol enabled message is
greyed.
In this case, the Set NE Time With OS Time message is not greyed and the user can set the NE Time
manually.
If the NTP protocol is supported, then the NTP Protocol enabled message is not greyed and two different
operating conditions can be defined:
NTP protocol enabled (in the NTP Server Configuration option at para 5.5 on page 41):
In this case, the Set NE Time With OS Time message is greyed and the user cannot set the NE Time
manually.
NTP protocol not enabled (in the NTP Server Configuration option at para 5.5 on page 41):
In this case, the Set NE Time With OS Time message is not greyed and the user can set the NE Time
manually.
If you do not want to set the NE local time, click the Close pushbutton to close the dialogue box.
To realign the NE time to the OS time basis, click the Set NE Time With OS Time radio button and either
click the Apply pushbutton to validate or the Close pushbutton to cancel and close the dialogue box. The
OS time comes from the workstation date configuration, which corresponds to the standard GMT time.
N.B.
ED
The OS system realigns the time of all supervised NEs periodically and automatically with a
configured periodicity. This periodicity is common to all NEs.
If you set the NE time, you will force the change, with an immediate effect on the NE. However
it will not have any effect on the periodic and automatic mechanism.
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
32 / 258
The NE Time dialogue box displays the current date and time of the OS and the NE.
Manager List: each manager connected to the NE is highlighted in the list. The user can set a
manager clicking on the denomination.
Several managers can be enabled simultaneously, having the NE in charge.
The Manager List contains the list of the managers ( i.e. RM, SY, EML) that work on the NE. The LHR
Administrator (SH. or Craft Terminal) should set the Manager List only to remove a manager in case
of emergency (i.e. the Manager misses the NE connection).
NE Domain: this field allows to select a domain among that displayed in the list and to assign it to
the NE.
The different domains could be assigned to different operators.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
33 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
34 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
nodes supporting the ISIS link state routing protocol; these nodes will be called adaptive
routers; the ISIS protocol floods the network with link state information in order to build a
complete consistent picture of the network topology. Using the ISIS routing protocol in a TMN
facilitates installation and operation, thanks to the self learning and automatic network
reconfiguration capabilities of these protocols in case of failure; moreover, the use of these
standardized routing protocols guarantees interoperability in a multivendor environment.
nodes not supporting these protocols; these nodes will be called static routers.
Networks partitions consisting of the former type of node will be called adaptive routing domains;
networks partitions consisting of the later type of node will be called static routing domains.
Moreover, a node that has to take routing decisions must be able to become an Intermediate Systems,
all others can be made End Systems
5.1.1 Partitioning into Routing Subdomains
In order to reduce the overhead associated with a distributed adaptive routing, it may be useful to subdivide
an adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level
1 subdomain should fulfil the following requirements:
a level 1 subdomain should form a connected subnetwork; this subnetwork should have only
a few links to the outside world as compared with the number of internal links;
each node must belong to exactly one level 1 subdomain;
each node that is connected to a foreign level 1 subdomain must become a level 2
intermediate system; level 1 intermediate systems only know how to communicate with IS
in the same area; obviously, there must be at least one level 2 intermediate system per level
1 subdomain;
level 2 intermediate systems must form a connected network, because level 1 paths cannot be
utilized for level 2 communications. Such a network will be called level 2 backbone.
In the simplest case, all nodes within a level 1 subdomain share the same area address. In general, it is
allowed to have multiple synonymous area addresses within a level 1 subdomain. The synonymous list
is used to ease partitioning in the future. There is a basic rule, which must be followed by two neighboring
level 1 intermediate systems within a subdomain: there must be at least one area address in common
between their two synonymous lists, otherwise they are not able to communicate with each other.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
35 / 258
In certain situations, it might be convenient to partition a given network into separate routing domains,
where no routing information is exchanged between these domains. The major benefits of this partitioning
are: reduction of memory, processing and traffic overhead, because there is no exchange of routing
information between the domains. Communication between separate routing domains must be achieved
through the use of Reachable Address Prefixes (RAP).
A Reachable Address Prefixes represents a static routing information unit. It can only be associated with
a link of a level 2 intermediate system, whereby this link crosses routing domain boundaries. A Reachable
Address Prefixes is handled in the same way as an information a foreign level 1 subdomain within its own
domain. A Reachable Address Prefixes indicates that any packet whose destination network address
NSAP matches the prefix may be forwarded via the link that the prefix is associated.
For example, let us consider a network which is split into two separate routing domains:
In order to enable the communication, the Reachable Address Prefixes in routing domain A must contain
area address b and the Reachable Address Prefixes in routing domain B must contain area address a.
One of the routing domains, connected through the use of Reachable Address Prefixes, can be a static
routing domain; in such a condition, the communication can be achieved through the use of Manual End
System Adjacencies (MESA).
A prerequisite for the use of Manual End System Adjacencies is that the area addresses of the connected
nodes must be the same; as a consequence, the nodes must belong to the same level 1 subdomain.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
36 / 258
The Communication and Routing views allow to perform the following operations:
Local Configuration:
OS Configuration:
Interfaces Config.
which comprises:
LAPD Configuration:
Ethernet Configuration:
which comprises:
RAP Configuration:
MESA Configuration:
To get access in the Configuration pull down menu, as shown in the following figure select the
Comm/Routing option from.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
37 / 258
Select the Configuration pull down menu. Select the Comm/Routing option and then, from the
cascading menu, the Local Configuration option.
The dialogue box opens ( see Fig. 7. on page 39 ) allows to configure the local address of the NE.
The following fields are present:
a Presentation Selector identifies a presentation entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Section Selector identifies a section entity at the location identified by the NSAP Address. The
presented value must not be modified.
a Transport Selector identifies a transport entity at the location identified by the NSAP Address.
The presented value must not be modified.
a Network Service Access Point (NSAP) Address identifies a location in the network. The first
field of the NSAP address, AFI, determines the NSAP format.
The AFI field is 2 characters long (2 hexadecimal digits) and, depending on the its value, the
length of the NSAP address is variable from 16 characters to 40 characters:
the value for AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).
the value for AFI 39 identifies the ISODCC format which is 40 characters long.
the value for AFI 47 identifies the GOSIPV2 format which is 40 characters long.
In all cases the last two fields of the NSAP address are:
Network Selector: provides the distinction among the users of the network service and is
2 characters long.
In the view, the NSAP is managed as simple strings of characters without any preformatting
because of the variable format:
a first string, two characters long, which identifies the AFI field
a second string, of variable length, which identifies the remaining NSAP address
a Synonymous Area Addresses section allows to have multiple synonymous area addresses within
a level 1 subdomain. The compilation of the two network addresses is optional and, if they are
inserted, the last two fields, of the mandatory address and of the synonymous addresses System Id
and Network Selector, must be the same.
an Intermediate System section determines whether the local NE acts as a level 1 or as a level 2
intermediate system. Note that a level 2 intermediate system performs the level 1 functions too.
Ok 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.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
38 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
39 / 258
Select the Configuration pull down menu. Select the Comm/Routing option and then, from the
cascading menu, the OS Configuration option.
The dialogue box opens ( see Fig. 8. ) allows to configure the addresses of the Main and Spare OSs
connected to the local NE.
The following fields are present:
Main OS Address section contains the same graphical object as the Local Address section in the
Local Configuration dialogue box.
Spare OS Address section contains the same graphical object as the Local Address section in the
Local Configuration dialogue box.
Ok 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.
Cancel button closes the dialogue without changing of the data.
Help button provides some useful information on the dialogue.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
40 / 258
5.4 OS Configuration
Enabling NTP Protocol section allows to enable or disable the NTP Protocol.
Main NTP Server Address section contains the same graphical object as the Local Address section
in the Local Configuration dialogue box.
Spare NTP Server Address section contains the same graphical object as the Local Address section
in the Local Configuration dialogue box.
If the NTP server is coincident with the OS (same hardware), then the same NSAP address as the OS must
be assigned.
Ok 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.
Cancel button closes the dialogue without changing of the data.
Help button provides some useful information about the dialogue.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
41 / 258
Select the Configuration pull down menu. Select the Comm/Routing=>Interfaces Configuration
option and then, from the cascading menu, the LAPD Configuration option.
The dialogue box opens ( see Fig. 10. ) allows to configure a LAPD port for each LAPD channel in the NE.
The view simulates a real notebook; it allows the user to select the pages of the notebook by using the
pointing device (upper part of the figure); each page represents a specific LAPD port of Regeneration
Section and its respective pointing device displays the complete user label of the RS TTP associated with
the port. The display of the view can be required directly by the port view containing the RS functional
blocks; this way, only the LAPD configuration parameters of the selected RS TTP are displayed ( see para
8.2 on page 90 ).
In detail, each page contains the following data:
LAPD Interface field allows to define or remove an LAPD Port on the selected RS TTP.
LAPD Role field indicates the role of a given LAPD Port (User/Network) according the LAPD protocol.
This connection is a must to establish a connection between two NE: one User role with one Network
role must be connected.
Apply button performs a configuration change of the data contained in the selected page.
Close button closes the dialogue without changing of the data.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
42 / 258
Ethernet Interface field allows to define or remove a Local Area Network Port for the access to the
Data Communication Network.
MAC Address section allows to display the address of the Network Element in the Ethernet LAN; it
is a readonly field.
L2 Only Parameter field indicates if the port can be used for level 2 traffic only, so as to
reducing the traffic through the port...
L1 Default Metric is a not modifiable field, Priority field can be set ( default value for
Ethernet is 64 )
L2 Default Metric is a not modifiable field, Priority field can be set ( default value for
Ethernet is 64 ) .
Routing Ip 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.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
43 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
44 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
if the element is empty, displays the none value and allows to select a LAPD port or a LAN
port, which will be used to reach the addressed area.
if the element isnt empty, displays the selected port and allows to change it.
Area Address Prefix section allows the user to address the separate domains. The Area Address
Prefix represents an NSAP address without the System Id and Network Selector fields.
MAC Address section allows to address the elements of a domain to be reached the Ethernet LAN;
this field is managed as a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and to 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.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
45 / 258
Select the Configuration pull down menu. Select the Comm/Routing=>OSI Routing Configuration
option and then, from the cascading menu, the MESA option.
The dialogue box opens ( see Fig. 13. ) allows to configure the Manual ES Adjacencies table.
Each element of the MESA table allows to link a LAPD port or a LAN port of the local NE to an End System
element; the ES element must be in the same area as that of the local NE. If the addressed element is
the OS, then the LAN port will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook by using the
pointing device (upper part of the figure); each page represents a specific element of the MESA table and
its respective pointing device displays the element counter.
In detail, each page contains the following data:
if the element is empty, displays the none value and allows to select a LAPD port or a LAN port,
which will be used to reach the End System element.
if the element isnt empty, displays the selected port and allows to change it.
MAC Address section allows to address the elements in the Ethernet LAN; this field is managed as
a simple string of 12 digits.
Apply button is used to perform a configuration change of the data contained in the complete MESA 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.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
46 / 258
6 EQUIPMENT MANAGEMENT
This chapter, describes the main features of the Craft Terminal, referred to the Network Element
management views, obtained by means of EMLUSM. These features constitute the headings of each
of the paragraphs below.
This chapter deals with the presentation of the N.E. and the structure of the hierarchical tree, and the types
of boards and subracks that comprise the LHR Network Element.
A navigation through different levels of the NE hierarchy is performed by clicking on object twice:
the first level shows the NE level of the Equipment view ( see Fig. 14. on page 47 );
a double click on it allows to read the rack level of the Equipment view ( see Fig. 15. on page
48 );
a double click on it allows to read the subrack level of the Equipment view ( see Fig. 16. on page
48 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
47 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
48 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
In the Subrack view ( see Fig. 16. on page 48) it is possible to use the options offered by the Equipment
menu ( see Fig. 17. on page 49 ) by clicking on the menu bar.
Alarms indications are present at the NE level.
In the Maintenance section, details are given on this indication.
All options are described in the next paragraphs, starting from the operation to set and change the boards
present on the Equipment.
The board administrative state that decides the in/out of service of the board is also described.
removal of a board
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
49 / 258
N + 0 (1:n) Configuration ( where N is minor or equal of 8 ). In this case all radio channels are
independent between them and the Hitless switch function is not provide.
In each of the Configuration above, the managed signal can be STM1 or subSTM1.
ED
Transceiver Subrack
Fans Subracks
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
50 / 258
This section provides information on the equipment types configurations of the LHR NE.
SUBRACK
MODULES LABEL
( DENOMINATION )
SUBMODULES LABEL
( DENOMINATION )
SYSCO ( Slot 1 )
(SYStem COntroller card)
MEMDEV
( Daughter 1 )
Memory Device
HKDEV ( Daughter 2 )
( Additional housekeeping)
SERV
RRA
RACKLHR
( Rack )
SRBB
( Baseband )
MD
( Slot 2 )
( SERVice card )
( Slot
3579
111315
17 1921 )
( RRA card ) 0 to 9
( Slot 46810
121416
182022 )
( MoDem card ) 0 to 9
PSF
CH n SCP
( Daughter 1 )
Protected Service
Channel
TPHDEV ( Daughter 2 )
( Additional voice )
IS1.1 ( Daughter 1 )
( Optical module STM 1 )
IFWCO
( Daughter 1 )
( IF module )
IFWXP
( Daughter 2 )
( IF module )
( Slot 2536 )
( PSF board ) 12
PSU
( Slot 26 to 35 )
( PSL4860 board ) 0 to 9
RX
( Daughter 3 )
( Receiver module )
SRTR
( Transceiver )
RX
( Daughter 4 )
( Receiver module S. D. )
LO ( Daughter 12 )
( Local Oscillator module )
SRFANS
( Fan Subrack 3)
ED
04
FANSL ( Slot 12 )
( Fan card )
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
51 / 258
The System Controller card ( SYSCO ) is composed of the function blocks Equipment and Radio
Controller, and the Memory Device module ( MEMDEV ).Then it is composed of the Additional
housekeeping module ( HKDEV ) to expand the number of housekeeping, and the external connectors
for the QB3 and F Interfaces. The HKDEV is external SYSCO board.
The Service card ( SERV ) is composed of the Additional voice module ( TPHDEV ) for adding a voice
channel. Then it is composed of the Auxiliary Service Channels ( AUX/EOW ) circuit , the protection of the
WST channels, and of the Switch Logic of the RPS protection *( in case of 1+1 and N+1 configurations).
The RRA cards ( RRA 0 to 9 channels ) are connected to the transmission line through one Optical or
Electrical Interface. The Optical Interface is an Optical Module inside to the RRA card ( IS1.1 )( see
Fig. 25. on page 59 ), instead the Electrical Interface is a function block of the RRA card.
The RRA 0 situated in slot 3 of the Base Band Rack , is used as a standby radio channel in N+1 and 1+1
Configurations, otherwise it is used as a main radio channel in N+0 Configuration.
The Modem card ( MD ) is composed of the modulator and demodulator function blocks. In case of Space
Diversity Configuration the Modem card employ an IF module ( IFWCO ). In case of Frequency reuse
Configuration ( XPIC ) is used another IF module ( IFWXP ). The IFWCO and IFWXO can be combined.
The Power Supply Unit boards ( PSL4860 0 to 9 ) power the Base Band Rack. Each PSU board supplies
one Modem card and two RRA card ( for example PSL4860 0 supplies MD 0, RRA 0 and RRA 1,
PSL4860 1 supplies MD 1, RRA 1 and RRA 0).
The Power Supply Filter boards ( PSF 12 are protected ) is composed of the filter section for the PSU
boards, and of DC/DC converter to supply the System Controller and Service cards. The two PSF boards
are in protection between them.
6.1.1.1.2 Transceiver
Every Transceiver card ( TRI 0 to 9 ) is composed of one transmitter function block and of DC/DC
converter module for power supply. Then it is composed of one Receiver module and two Local
Oscillator modules ( one for the receiver side, the second for the transmitter side ).
In case of Space Diversity Configuration the Transceiver card contains a second Receiver module (RX)
( Daughter 4 ) ( see Tab. 2. on page 51 ).
There are two different types of Transceiver card 128 QAM, depending on the output power level:
ED
The SRFANS 1 ( Fan Subrack 1 ) which provide the necessary ventilation to the possible ADM
Equipment.
The SRFANS 2 ( Fan Subrack 3 ) which provide the necessary ventilation to the LHR Equipment
( Base Band and Transceiver sides ).
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
52 / 258
The screen above allows the operator to select all Equipment levels ( Subracks, Modules, Submodules)
of the LHR N.E. to be displayed.
Select the object (i.e. Subrack)
Selecting the Views option in the menu bar and then click on Open object pull downmenu choice.
Fig. 19. on page 54 shows the selecting of the Base Band Subrack ( SRBB11 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
53 / 258
Selecting the Views option in the menu bar and then click on Open object ( or by clicking twice over
the Subrack in examen ) the next screen it opens ( in this case SRBB11 see Fig. 20. on page 55 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
54 / 258
Fig. 20. Base Band screen with the selectable modules view
The screen above includes all the selectable modules of the BaseBand Subrack ( SRBBN1 ).
The operator can get access to each of these modules. As example the module corresponding to System
Controller card ( SYSCO ) has been selected.
By clicking twice on the selected module the next screen opens ( see Fig. 21. on page 56 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
55 / 258
Starting from the Unit screen the operator can get access to all the circuit parts ( Daughters ) consists of.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
56 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
57 / 258
The screen above allows to configure and modify the Modules/boards according to the equipment.
Para. 6.2 ( Set & Change ) on page 75 includes the procedure to configure and replace a unit (BOARD).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
58 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
59 / 258
By means the Show Supported Port option from the Equipment menu ( see Fig. 26. on page 60 ),the
operator can get access to the Board view screen ( see Fig. 27. on page 61, Fig. 28. on page 62 and
Fig. 34. on page 67 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
60 / 258
The screen above shows an example of SDH Board ( in this case is the SDH Board MoDem card ).Clicking
twice on the square in the high left position, the SDH Port view screen it opens ( see also Fig. 40. on page
72 for the Radio section ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
61 / 258
Clicking twice on the below square in the left of the screen, the SDH Port view screen it opens ( see
Fig. 29. on page 63 ).
In the same way in the upper square, the PDH Port view screen it opens ( see Fig. 30. on page 63 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
62 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
63 / 258
Starting of the RRA card view ( see Fig. 31. on page 64 ), by means the Show Supporting Port option
from Equipment menu ,the Board view of Optical module STM1 ( IS11 ) screen it opens ( see Fig. 32. on
page 65 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
64 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
65 / 258
Fig. 33. SDH Port view Optical Interface ( Optical module STM1 ) screen
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
66 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Clicking twice on the connectors symbol ( AUX ), the PDH Port view screen it opens ( see Fig. 35. on
page 68 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
67 / 258
The screen above shows the Plesiochronous Physical Interface with the relevant alarms ( LOS and URU,
refer to Chapter Maintenance ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
68 / 258
When an equipment unit has no Terminal Points, inside the relevant screen appears the writing This board
does not contain physical TP ( refer as example Fig. 36. on page 69 and Fig. 43. on page 74 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
69 / 258
Clicking twice one of the two transceivers checked with the padlock symbol the screen it open (see
Fig. 38. on page 71).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
70 / 258
In the screen above the operator can select the Four modules which the Transceiver is composed:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
71 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
72 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
73 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
74 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The boards can be set, changed, or removed by using the menu options of the Equipment view.
a)
A new board may be created in either an empty slot or in replacement of an existing board that is Out of
Service ( without the lock symbol ).
Click the empty slot in which a board has to be added, or an existing board Out of Service in order
to change it ( see next para. 6.3 on page 77 for in/out of service info ).The outline becomes
highlighted to show that operations can be done on it.
In the Equipment pull down menu of Fig. 17. on page 49, Select the Set option.
The following figure shows an example of a dialogue box containing a list of the different types of
boards.
N.B.
The list of boards displayed during a Change Board operation is restricted to those the
equipment may accept in the selected slot. Therefore the list will vary depending on which slot
has been selected.
For details on the boards identified by the acronyms and on the NE physical composition, refer
to the Technical Handbook.
Choose the board type required by clicking on the corresponding item in the list. The name of the
board is highlighted. Click the OK pushbutton to validate the choice made.
The board representation appears in the NE view in the slot when the board change is effective.
A lock representation appears over the board ( see Fig. 45. on page 76 ).
In the Set Board dialogue box, the Cancel pushbutton cancels the operation and closes the dialogue
box. The Help pushbutton opens a Help view which provides information on the context.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
75 / 258
Removing a board
Click the board to by removed ( Out of Service board, see next para. 6.3 on page 77 ).
The outline of the slot becomes highlighted. This indicates that the board is selected and that
operations can be done on the slot.
If the slot you are working on is already empty, no name appears below it.
In the Equipment pull down menu of Fig. 17. on page 49, Select the Remove option.
From the confirmation dialogue box that opens, you can confirm or cancel the Remove Board
operation.
c)
Modify a board
N.B.
This procedure can be done to replace an existing board with another type without
previously remove it.
Choose the board type required by clicking on the corresponding item in the list. The name of the
board is highlighted. Click the OK pushbutton to validate the choice made.
Choose the board type required by clicking on the corresponding item in the list. The name of the
board is highlighted. Click the OK pushbutton to validate the choice made.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
76 / 258
b)
The operator can decide whether to set a board in service or out of service, if it is allowed by the NE.
N.B.
In the Equipment view,a lock representation appears over the boards that are in the in service
state.
The boards administrative (in service or out of service) state is indicated on the Board view as shown
in the following figure.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
77 / 258
This function allows the operator to display information on the software(s) that is(are) present in the selected
board.
Click a board whose software is to be investigated. The outline of the slot becomes highlighted. This
indicates that the board is selected and that operations can be done on the slot.
In the Equipment pull down menu of Fig. 17. on page 49, select the Software description option
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
78 / 258
In the Equipment pull down menu, select the Remote Inventory option
Two options are available ( see the following figure ):
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
79 / 258
A question appears similar of Fig. 49. to that where is possible to update remote inventory subrack or not.
Printer Destination
Printer
Output Format
Postscript
ASCII
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
80 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
81 / 258
In the Equipment menu, click the Show Supporting Equipment menu option to navigate to the
equipment that supports the selected board.
A window like that shown in Fig. 53. opens.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
82 / 258
7 BOARD VIEW
7.1 Introduction
The Board View allows to show the physical port available in a specific board and to access the Port
view.
The Board View is reached starting from a Subrack view and then selecting the Show Supporting
Port option in the Equipment pull down menu ( see previous chapter ).
An example of Board view with the presented port is shown in Fig. 54. on page 83.
At the bottom of the view, the Alarms and Status indications relevant to the board level are present, as
indicated in the example.
This information comprises: the In/Out of service status of the board; the board status like missing
or mismatch ; the EPS condition ( if supported ); and other indications specific to the individual units
( e.g. high laser temperature ).
Details on these indications are given in the Maintenance section.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
83 / 258
A port type is described with a Board rectangular view and a Port identification.
The Port identification is usually internal to the rectangular board ( see Fig. 55. ).
The operator gets a representation of the port alarm synthesis for each port.
The messages displayed on the top view provide the port denomination.
The messages displayed on the bottom provide information on the Board alarms.
A message under the mouse facility provides the port name and type or the alarm name. A message
appears in the message area on the bottom left corner of the view.
By doubleclicking a Board view, it is also possible open its corresponding Port view ( see Fig. 57. on page
86 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
84 / 258
Port Access:
Not implemented
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
85 / 258
Navigating to the Port view permits to show a detailed alarm presentation of the port and to set its relevant
configurations, as shown if the following figure for a typical example.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
86 / 258
In the Board menu, click the Port Access menu option to access the Port view.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
87 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
88 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
8 PORT VIEW
8.1 Introduction
This chapter describes the operations necessary for the configuration setting and verification of each port.
The Port View permits to set and show the transmission resources (TP) referred to the specific Port: it
permits to check the detailed alarms presented by each TP of the Port, and the available menu permits
to configure the port.
In these views are presented only the TP specific of the port.
The menu differs according the port type (SDH, PDH).
The Port view is reached selecting the Show Supported Port option in the Equipment pull down
menu, then double clicking on the selected board the relevant Board view is available presenting the
ports ( see Fig. 54. on page 83 ).
By double clicking on a board view, the corresponding port view is opened ( see Fig. 57. on page 86 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
89 / 258
Selecting the Port option in the menu bar of Fig. 57. on page 86 the complete pull down Port menu is
presented ( see Fig. 59. on page 90 ).
Fig. 59. Port view SDH ( on the left ) and PDH ( on the right ) option menu
The menu differs according the port type (SDH, PDH), and is introduced in the following:
TP configuration:
Set parameters for the Signal Label and Path Trace overhead on
Synchronous TPs.
AU4 Concatenation:
Not operative.
Performance:
Physical Media:
Refresh:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
90 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
91 / 258
For the description of the LAPD configuration refer to the para 5.6 on page 42 of this handbook.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
92 / 258
This command allows to get detailed information on the optical characteristics of the port that is visualized.
Firstly select an optical board and then click on Optical Laser Configuration option from the Physical
media pull down menu to visualize the parameters of the selected optical port.
The Fig. 62. shows an example of the parameters of the selected interface.
N.B.
This dialogue box can only be read. You cannot write in the entry boxes.
The wavelength of the laser source: the units are nanometers (nm = 109 m).
The use of the port: describes whether the laser port is used for intraoffice transmissions on long
distances (Long Haul ] 40 km) or for infraoffice transmissions on short distances (Short Haul ]
15 km).
To close the dialogue box click on the Cancel push button.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
93 / 258
Automatic laser shutdown (ALS) is useful in case of a loss of communication between two NEs due to
optical fiber breakdown. For safety reasons it may be necessary to shutdown the laser to enable the fixing
of the communication link.
The automatic laser shutdown function can only be configured from the optical ports of the equipment.
Select the Physical media option and then from the cascading menu the Als Management option .
The Automatic Laser Shutdown State dialogue box opens ( see Fig. 63. ). From this window it is only
possible to create the ALS function ( all the ALS commands are greyed ). Select the Apply button and
open again the Als Management option to configure the ALS and Restart parameters. Fig. 64. on page
95 opens.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
94 / 258
The aim of this paragraph is to describe the optical port hence the laser sources.
b)
When the laser is forced to ON or OFF, it is restarted or stopped and the Automatic Laser Shutdown
is disabled, if it was not already so.
1)
2)
c)
d)
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
95 / 258
f)
When all the different parameters have been configured, select the Apply button to confirm the setting
and close the dialogue box.
The Close button allows you to cancel the choices made.
Note that the ALS procedure is activated ( if enable ) only when the fiber has been interrupted and the
ALS state has not to be confused with the laser state.
ALS states ( see Fig. 65. ), displayed by the functional state message area of the optical port,which are:
Active = The ALS has been activated.
Off = No Laser has been activated.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
96 / 258
e)
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
97 / 258
The STOP button allows the operator to stop BER measurement data collection. It is sensitive only if a
BER measurement is in progress.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
98 / 258
Fig. 68. shows the Overflow condition when the violations and the elapsed time exceed threshold defined
(32 bit).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
99 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
100 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Configure
Switch
Synthesis
Extra traffic
The first two entries are always available and display a secondary window.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
101 / 258
RPS Automatic Switch .The label changes according to the state and the icon lights on when the state
differs from NoOone.
These states are not upgraded from notification in the LHR 1+1 NE when a successful Automatic Switch
occurs.
In this case, the entry in the Port menu bar, select the refresh option ( see Fig. 69. on page 102 ), starts
a request to an NE to upgrade the functional states.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
102 / 258
The following functional states are displayed on the screen Fig. 71. on page 103:
Fig. 70. RPS Configure (Schema) option offered by the RADIO menu bar
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
103 / 258
In the upper part of the window a tree list provides all existing schema with protecting elements as root
nodes and the protected elements as leaves.
When the operation is over, the following information is displayed to the user in this box:
To set the configuration parameters, the user shall modify the elements.
If Apply button is disabled the elements ( configuration parameters ) are not modificable.
The Close button removes the dialogue.
The Help button provides some useful information on the dialogue capabilities.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
104 / 258
This dialogue ( see Fig. 71. on page 103 ) allows to display the configuration parameters for RPS
Configure schema.
Fig. 72. RPS Configure (Units) option offered by the RADIO menu bar
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
105 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
106 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Fig. 74. RPS Switch option offered by the RADIO menu bar
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
107 / 258
The lower part provides the possible protection commands on the selected ports.
The possible commands issued towards the NE include: lockout, force to and manual to.
For each command, the related release command is provided.
When an Ok button is clicked, the operation is started, at the end of the request, the dialogue will disappear.
If any errors arise during the request, an error dialogue is presented.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
108 / 258
In the upper part a tree list provides all existing schema with the protecting elements as root nodes and
the protected elements as leaves. The user selects in this list a protected and/or protecting port ( its
mandatory to choose a protected port to start protection commands, while the protecting port is
determinate when protected port is chosen).
This operation fills the protecting and/or protected elements text fields with the selected ports.
Checks are made to see whether the selected ports are in the same scheme.
Automatic delay alignment (Rx side) both for direct way and indirect way
the first column contains user label associated to a protecting or protected Ports
the second column contains the value of static alignment (shift value) applied to signal coming from
Direct Way (0 to 255)
the third column contains the value of static alignment (shift value) applied to signal coming from
Indirect Way (0 to 255)
the fourth column contains the indication of actual Status (No operation active, auto alignment,
manual alignment); the manual alignment is not available.
The operator may select an item of the scrolled matrix, that makes the entire row selected ( see Fig. 78. on
page 110 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
109 / 258
If no selection is performed all buttons except Close and Help are insensitive.
The Set operation executes the auto alignment (auto alignment string appears for an instance in
status field) and the shift values appears in Direct Way and in Indirect Way .
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
110 / 258
Selecting the RPS => Synthesis option in the Radio menu a dialogue box appears
It is possible to have a complete view of all NE resources involved in an RPS Protection Scheme.
It is possible by a dialogue box containing a matrix to collect all the RPS protected/protecting ports
information.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
111 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
112 / 258
This command allows to request the status (suspended/resumed) of the Extra Traffic on main unit.
Selecting the RPS => Extra Traffic option in the Radio menu a dialogue box appears
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
113 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
114 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Switch
Synthesis
The configuration parameters for the WST and Service Channels protection are:
switching type
operation type
protection scheme
external commands
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
115 / 258
Selecting the RFCOH => Configure option in the Radio menu (see Fig. 83. on page 116) and then, from
the cascading menu, a dialogue box appears (see Fig. 84. on page 117)
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
116 / 258
1:n
It displays a tree list with the protecting units. It allows to choose a protecting unit, e.g. a protection schema.
(WST or Service Channel).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
117 / 258
1:n
1:n
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
118 / 258
the configuration parameters for the selected WST/Service Channels protection schema:
The Apply button is enable or disable (grayed) according the NE setting present in resource file. If Apply
button is disable the elements (configuration parameters) are not modificable.
The Close button removes the dialog.
The Help button provides some useful information about the capabilities of the dialog
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
119 / 258
Selecting the RFCOH => Switch option in the Radio menu (see Fig. 88. ) a dialogue box appears (see
Fig. 89. on page 121).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
120 / 258
The Help button provides some useful information about capabilities of the dialog.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
121 / 258
Selecting the RFCOH => Synthesis option in the Radio menu a dialogue box appears.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
122 / 258
It displays a tree list with the protecting units. It allows to choose a protecting unit, e.g. a protection schema.
(WST or Service Channel).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
123 / 258
Switch Type (last operator command): No Request, Forced Switch, Lockout, Hw Forcing
Automatic Switch: noOne, earlyWarning, lowBer, highBer, signalFail for WST, signalFail for
Service Channels
The Help button provides some useful information about the capabilities of the dialog.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
124 / 258
11 RADIO PARAMETERS
In the following are showed the Radio side parameters with the related screens which are:
ED
Frequency Agility
Power Measurement
ATPC/Power Setting
Squelch
Gain
Hop Trace
Frequency Reuse
Equalization Delay
V.C.O. Status
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
125 / 258
The ATPC/Power and Threshold Setting item menu is always available, and it is sensitive always also
if ATPC capability is not supported by the NE.
The Automatic Transmitted Power Control (ATPC) management capability is performed by means of the
following Radio menu option:
the first column contains Channel Number associated to a physical radio port
the second column contains all the user label associated to a physical radio port
the third column contains the indication about the ATPC status (possible value: Enabled/Disabled)
the fourth column contains the indication about the ATPC Manual operations status ( possible value:
Active, Not Active ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
126 / 258
If no selection is performed, all buttons, except Close and Help, are disabled.
Buttons changes sensitivity accordingly these conditions:
Set buttons is enable only if ATPC is Disable
Manual changes accordingly of value of the selected Manual filed.
Configure is enabled if a row is selected.
Enable this function enable the ATPC functionality. It is performed by clicking on Enable button. If
the operation is correctly performed, the ATPC status is changed on line.
Disable this function disable the ATPC functionality. It is performed by clicking on Disable button.
If the operation is correctly performed, the ATPC status is changed on line.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
127 / 258
This function Configure the ATPC. It is performed by clicking on Configure button ( see Fig. 95. on page
127 ).
In the ATPC Configure screen ( see Fig. 96. on page 128 ) it is possible to modify the ATPC parameters
(Atpc Range, and Low Power Threshold level) by uparrows and downarrows with step of 0.1 dBm or
by writing directly in the field. The new value is considered when OK button is pressed; value must be
inside the range values visible in window otherwise an error message box appears. Before the operation
is performed, an explicit confirm is required by means of a confirmation box.
NB:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
128 / 258
This function starts Manual Operation Session functionality, if not already in opened, and then opens the
ATPC Management screen in manual mode. If the start of Manual Operation Session is correctly
performed, the ATPC status is changed on line.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
129 / 258
This function allows to modifies the TX power level when Manual Operation is Active. It is accessible
across Manual button ( see Fig. 95. on page 127 ) that opens the new screen ( see Fig. 98. on page
130 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
130 / 258
To activate the new number the operator has to press the Ok button. The dialog disappears.
To verify the success of the new setting, the operator has to reopen the dialog.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
131 / 258
The RX Gain level Management is performed by means of the following radio menu item:
The 0 value in Gain Level or in Gain Level Diversity means that the related receiver is set in
automatic gain mode.
The operator can modify the Gain Level value . If the NE supports the Space Diversity, also the gain level
related to the diversity can be modified. If the space diversity is not supported the field Gain Level
Diversity is not visible. To come back in automatic gain mode for both receivers, this operation is
performed with Stop Manual button.
Click on Apply to confirm the operation.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
132 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
133 / 258
The management of Hop section trace is performed by means of the following Radio menu item.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
134 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
135 / 258
The Squelch management is performed by means of the following radio menu item:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
136 / 258
The Radio Abnormal Condition List is performed by means of the following radio menu item:
Fig. 108. Radio Abnormal Condition List option offered by the Radio menu
Selecting the Radio Abnormal Condition List option in the Radio menu ( see Fig. 108. ) a dialogue box
appears ( see Fig. 109. on page 137 ).
The first thing the operator has to perform is to choose the radio port, this is done pressing the Choose
Radio Port button which allows to choose the radio port ( see Fig. 102. on page 133 ); then after pressing
OK button on the fields Channel: and Radio Port: are filled with the chosen radio port information
and all the Manual Operations active are listed (relative only TRI ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
137 / 258
The Frequency Reuse Management is performed by means of the following radio menu :
Radio Port
Carrier Status
Channel
In the Associated Channel, NE User Label, Ne Location Name the operator can set the information,
about the Channel Frequency Reused.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
138 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
139 / 258
The equalization delay management is performed by means of the following radio menu item:
In case of Frequency Reuse the delay may by applied only to one way (and in Manual Mode): main or
reused, so if the two set delays are both different from 0 the operation is refused.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
140 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
141 / 258
11.13 Frequency
The Frequency management is performed by means of the following Radio menu option:
the first column contains the channel number associated to a physical radio port
the second column contains the user label associated to a physical radio port
the third column contains the value of TX frequency
the fourth column contains the value of RX frequency
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
142 / 258
the first column contains the channel number associated to a physical radio port .
the second column contains the user label associated to a physical radio port .
the third column contains the V.C.O. role ( Master or Slave ).
the fourth column contains the indication of actual status ( Internal or External ). For the Master
the Status is always Internal .
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
143 / 258
The Power Measurements capability is performed by means of the following Radio menu option:
By selecting the Power Measurement => Graphic Power Meas. option in the Radio menu ( see
Fig. 118. ) a dialogue box appears ( see Fig. 119. on page 145 ), showing the parameters used to set the
starting Power Measurement screen.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
144 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
145 / 258
By selecting first Radio Port, then clicking on Ok button ( see Fig. 119. on page 145 ) the new screen
Power Measurement Graphic appears ( see Fig. 120. ).
The top of the screen offers all the characteristics present in the current measurement:
the radio port item gives the symbolic name associated to the radio channel that you are analyzing
the sample time item indicates the frequency used to send the measure requests to NE;
the stop time item is the interval time selected in the previous parameters window, added to start time;
Log File item is the complete pathname of the file where the received values are stored.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
146 / 258
By clicking on show details square, on the left side on Power Measurement Graphic ( see Fig. 120. on
page 146 ), a new table appears ( Fig. 121. on page 148 ); this table shows the following relevant values
of the received and transmitted power:
max TX local value and date when this value was received for the first time.
min. TX local value and his current date when this value was received for the first time.
max TX remote value and date when this value was received for the first time.
min. TX remote value and his current date when this value was received for the first time.
max Rx local value and date when this value was received for the first time.
min. Rx local value and his current date when this value was received for the first time.
max Rx remote value and date when this value was received for the first time.
min. Rx remote value and his current date when this value was received for the first time.
max Rx local diversity value and date when this value was received for the first time.
min. Rx local diversity value and his current date when this value was received for the first time.
max Rx remote diversity value and date when this value was received for the first time.
min. Rx remote diversity value and his current date when this value was received for the first time.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
147 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
148 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The Power Measurement File Reading is performed by means of the following Radio menu option:
Fig. 122. Power Measurements File Reading option offered by Radio menu
By selecting the Power Measurement => File Reading option in the Radio menu, the Directory C:
ALCATEL/USMmw2.0.1 related appears ( see Fig. 123. on page 150 ).
In the middle of this screen it is possible to choose the name of the file ( Log File ) selected in the previous
screen Power Measurement parameters ( see Fig. 119. on page 145 ).
By clicking on the Apri button, the Power Measurements File Reading selected ( for example
_r01sr2sl0 2.txt ) appears ( see Fig. 124. on page 150 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
149 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
150 / 258
12 OVERHEAD MANAGEMENT
12.1 Introduction
This chapter describes how to manage the Overhead ( OH ) bytes of the N.E.
The possible operations are:
Overhead crossconnection.
OH Termination
The operator has to be able to terminate OverHead TP and the OverHead Bytes ( RSOH and
RFCOH).
In Tab. 3. and Tab. 4. are show the RSOH Termination Bytes.
Tab. 3. Termination Bytes for the RSOH OverHead related to the SERVICE card
TERMINATION
SIGNAL
BYTES
TYPES
G 703
==>
V. 11
( 64 k CTP )
( 11 CTP )
V. 24
( 24 CTP )
E1
Q. 23
( Q 23 CTP )
X
F1
Future Use
National Use
Tab. 4. Termination Bytes for the RSOH OverHead related to the TPHDEV module
TERMINATION
SIGNAL
BYTES
TYPES
==>
G 703
Q. 23
( 64 k CTP )
( Q 23 CTP )
E1
F1
Future Use
National Use
N.B.
ED
04
For only TPHDEV module the G 703 signal type can be crossconnected exclusively
with the Q 23 signal type provided by the same module.
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
151 / 258
Tab. 5. Termination Bytes for the RFCOH OverHead related to the SERVICE card
TERMINATION
SIGNAL
BYTES
TYPES
G 703
==>
V. 11
( 64 k CTP )
( 11 CTP )
V. 24
( 24 CTP )
Q. 23
( Q 23 CTP )
E1
User Channel
The Termination Ports V.11 ( three at 64 K/b abc and one at 64 K/b or 128K/b d ) always can be
cross connected between them, taking account that ONLY ONE of the third ( c ) with the fourth ( d)
can be cross connected.
The steps an operator has to do in order to perform the OH bytes termination are the following:
Tab. 6. Termination Bytes for the RFCOH OverHead related to the TPHDEV module
TERMINATION
SIGNAL
BYTES
TYPES
==>
G 703
Q. 23
( 64 k CTP )
( Q 23 CTP )
E1
User Channel
N.B.
ED
04
For Only TPHDEV module the G 703 signal type can be crossconnected exclusively
with the Q 23 signal type provided by the same module.
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
152 / 258
OH Crossconnection
The steps an operator has to do in order to perform the crossconnection are the following:
BYTES
RSOH BYTES
ED
==>
E1
User Channel
E1
rs Order Wire
F1
rs User Channel
Future Use
rs Future Use
National Use
rs National Use
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
153 / 258
To access select Overhead option from the Configuration pull down menu; the following options are
presented in the cascading menu, as shown in the following figure:
OH TP creation
OH TP deleting
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
154 / 258
12.4 OH TP creation
Select the View pull down menu. Select the Overhead option and then from the cascading menu the OH
TP creation option.
The OH TP creation dialog opens (see Fig. 126. ) and allows to create the OH TP to cross connect.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH TPs to be created. The Choose button starts
the TP Search with predefined filtering ( see Fig. 127. on page 156 ); this screen allows the
operator to visualize only not created OH TPs.
On the Termination Points field is possible to select and choose the Termination Bytes, clicking
twice on the TP list ( see Fig. 133. on page 163 ).
Apply button is used to perform a create request of the tp displayed in the OH Tp field. After having
performed the create request, the OH Tp field is set to empty (see Fig. 128. on page 156).
Close button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
155 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
156 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Click on Create ; a new screen called Main Cross-Connection is opened ( see Fig. 131. on page
161 ).
Click on Choose relative to the Input field ; a new screen called Search for OverHead Cross
Connection Input is opened ( see Fig. 132. on page 162 ).
On the Equipment field select the Port, then in Termination Points field select the RSOH
bytes.
In the Main Cross-Connection screen repeat the same operation on the Output field.
Click on OK on the Main Cross-Connection screen to terminate the creation of the RSOH bytes.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
157 / 258
Supported operations
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several crossconnections/termination at the same time.
Unlike the normal crossconnections, the OH xconnections are automatically active at the moment of their
creation.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
158 / 258
The Delete button is enabled only if at least one item is selected from the list.
A special dialog will ask the user for a confirmation.
the create button is always enabled. It brings up the Main crossconnection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation
dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for
single items, yes to all/cancel for multiple items
When used for OH purposes, the Cross-Connection Management dialog doesnt support the following
functionalities:
Activate/Deactivate
cross
connections/terminations:
all
connections/terminations are automatically active since their creation
the
OH
cross
After a successful search, a read only list of cross-connections matching the search criteria appears
(see Fig. 130. on page 160). The number of matching cross-connections is displayed in the upper left
corner of the list. The list contains information concerning the following parameters for each
cross-connection:
Prot. State
detailed switching information in the format:
<protection state> <traffic ind> (<location>:<signal state><switch status>,
[<location>:<signal state><switch status>])
State
connection state indicating whether cross-connection is A(ctivated) or D(eactivated)
Dir.
Direction-related connection type:
bi(directional)
Input
signal source; contains the TP type and physical location of the port according to the format
<rack#><subr.#><board#><port#>,<port#>#TP
Protecting Input
protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Output
signal destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP .
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
159 / 258
Cross-connections with an active ConnectionFailed alarm are disabled and displayed in red
letters within the list.
At the bottom of the dialog is a range of buttons to start actions on the listed cross-connections. Before
starting any action apart from creation or printing, mark at least one cross-connection.
To mark several cross-connections (multi-select) that are listed in succession, select the first
cross-connection of a block with a mouse click and the last one with a mouse click while pressing the
<Shift> key.
Or, mark a number of individual cross-connections by clicking the mouse button while pressing the
<Control> key.
Deselect cross-connections by clicking on the respective row while simultaneously pressing the <Control>
key. To deselect a number of cross-connections at a time, press the <Shift> key and hold it down while
moving the mouse pointer to the last entry.
All actions that may affect traffic must be confirmed. A confirmation dialog pops up in this case and the
user has to confirm the requested action.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
160 / 258
N.B.
By clicking on the proper portions of the dialog and on the proper buttons, the operator can perform the
operations hereafter listed: (see Fig. 132. on page 162)
In order to do that the operator can either type in the involved TPs ID or use the TP Search dialog.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
161 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
162 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The Search OH TP dialog ( see Fig. 133. on page 163 ) currently offers:
navigation rack/subrack/board/port
a list of TPs to choose from
When used in the OH domain, this dialog is a subcase of the most generic Search OH TP.
The operator can choose among a list of:
all the possible OH TPs belonging to a specified board/port: board/port selected and no TP class
selected
all the OH TPs already connected ( also accordingly to the connection type )
all the OH TPs not yet connected
a combination of the above options
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
163 / 258
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH TP deleting option.
The OH TP deleting dialog opens ( see Fig. 134. ) and allows to delete the OH TP no more involved in
an OH crossconnection.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH TPs to be deleted. The Choose button
starts the TP Search with predefined filtering; the TP Search dialog allows the operator
to visualize only created and not crossconnected OH TPs.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
164 / 258
12.6 OH TP deleting
The Operator can to select the omnibus called ( 00 ) by means the handset.
The TPHDEV module, related to the SERVice card allows another telephone number is available.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
165 / 258
This command is used to generate and print a list of TPs according to the current filter selection (see
Fig. 133. on page 163 ).
The command opens the following dialog:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
166 / 258
12.8 Print
13 LOOPBACK MANAGEMENT
The commands of this menu item are for the management of the loopback commands, for commissioning
or maintenance purposes.
RST
SPI
RPS
RST
RFCOH
MODEM
RT
RSPI
RRA
MD
TRI
RST
SPI
RST
RPS
RFCOH
MODEM
RT
RSPI
RRA
MD
TRI
SPI
RST
RST
RPS
MODEM
RFCOH
RT
RSPI
RSPI
RRA
MD
TRI
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
167 / 258
A LHR Network Element can be controlled, besides by the local Craft Terminal (ECT), by a Remote Craft
Terminal (RECT). In certain conditions, that are explained here, loopbacks setup by RECT are not
recoverable by RECT, therefore their settingup by RECT must be avoided.
The remote control by RECT is carried out by means of the DCC channel which allows to access the
Equipment Controller from the Remote Craft Terminal, as depicted in Fig. 142. herebelow.
STATION A
STATION B
radio channels x,y
TR
TR
D1D3
MD
MD
RPS
RPS
radio channels x,y
D4D12
D1D3
RRA
RRA
SEMF
SEMF
D4D12
D1D3
F
MCF
MCF
1320CT
QB3
QB3
channels 0, 1
channels 0, 9
channels 1, 2
channels 1, 9
channels 8, 9
Figure in Fig. 143. on page 169 shows the position of the Equipment Controller EC with respect to the
loopback points A,B,C (these loopbacks are named as indicated in previous Fig. 139. thru Fig. 141. ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
168 / 258
Therefore, having defined x&y the couple of radio channels transporting the service channel, the following
rules must be followed for loopback settingup:
loopbacks on channels x&y (used for DCC communication purposes) setup by the local or remote
Craft Terminal:
if only one DCC channel is available, i.e., when any of CHx or CHy is unavailable for
any reason, the loopback cannot be removed by the Remote Craft Terminal, according
to the direction from which the RECT tries (unsuccessfully) to access the controlled NE,
because its EC is not reachable, as depicted in Figures and in Fig. 143. on page
169.
b)
if both DCC channels are available, the loopback remotion by RECT is possible; obviously:
unrecoverable loopbacks must never be setup on both channels CHx and CHy
no failure on the other channel (not loopedback) CHx or CHy should occur in the
meanwhile
otherwise the same unrecoverable condition of previous point a ) will occur.
RT
BB
A
C
EC
RT
BB
A
RECT
EC
RT
BB
A
RECT
EC
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
169 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
170 / 258
EC
EC
BB
1320CT
or OS
RT
STATION 3
RT
ALLOWED LOOPBACKS
(RECOVERABLE BY RECT)
STATION 0
BB
C
RT
C
B
EC
B
EC
BB
RECT CONTROL
RT
RT
STATION 1
STATION 2
IBB
EC
EC
BB
STATION 0
BB
STATION 3
1320CT
or OS
RT
RT
EC
BB
EC
BB
STATION 1
STATION 2
RT
N.B.
b)
From the Operators point of view, the modality starting from Port View menu is of easiest
execution.
The Loopbacks can be managed directly selecting the Loopback in Port menu
Two functions are performed:
Loopback Management
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
171 / 258
Selecting the Port Loopback Configuration (see Fig. 145. on page 171) option in the Port =>Loopback
menu a dialogue box appears (see Fig. 146. )
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
172 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
173 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
174 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
175 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
176 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
177 / 258
b)
From the Operators point of view, the modality starting from Port View menu is of easiest
execution.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
178 / 258
N.B.
Select the Create button and new dialog box appears (see Fig. 158. )
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
179 / 258
Click the Choose Tp button to select a Termination Point (see Fig. 159. )
Click OK button to confirm and the Fig. 160. on page 180 appears.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
180 / 258
When the Termination Point has been selected click the OK button to confirm the operation.
NB: the Timed Loopbacks field is not managed and thus Start/Stop loopbacks time is not editable.
The configured loopbacks are listed into the Current Loopbacks Table (see Fig. 161. )
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
181 / 258
Select the Loopback Management option in the Configuration menu (see Fig. 162. ) a dialogue box
appears (see Fig. 163. on page 182)
Select in the Current Loopbacks Table the loopback and to confirm the operation clicking the Delete
button. At the end of this operation the loopback will be deleted.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
182 / 258
After selecting this menu option, the External Points view is displayed in the current window instead of the
current view.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
183 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
184 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
185 / 258
To configure an external point, click the concerned line, then select the Configuration option from the
External Points pull down menu as shown in the following figure.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
186 / 258
When the External Point Configuration is complete, click the OK pushbutton to validate the choice and
close the dialogue box. The Cancel pushbutton cancels the configuration and closes the dialogue box.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
187 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
188 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
15 ALARMS MANAGEMENT
Alarms are always present on the operators workspace. The different types of alarms, their number, and their
severity levels, are represented in all Equipment views (NE views, Board views, and Port views). An icon
representation is used. This way you can know the number of alarms and their severities relating to the
equipment at any time.
The following paragraphs describe how to configure the Alarms Management and access the Alarm
Surveillance and show the alarm condition.
From the Configuration pull down menu, select the Alarm Severities... option .
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
189 / 258
Profile No Remote Alarms shows the alarm criteria configuration defined for path
alarms.
This profile is choice as Default Configuration Alarm.
Profile Primary Alarms shows the alarm criteria configuration defined for primary
alarms.
Profile No Alarms.With this profile all alarms are disabled (non alarms).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
190 / 258
If you Clone an ASAP the created ASAP is identified by the next number (10002, ....).
The max number of ASAPs is six.
N.B.
The number of severities and the number of probable causes is fixed. The ASAP function only
allows to modify of the severities assigned to the probable causes, it does not allow to add,
remove or modify these severities and causes.
N.B.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
191 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
192 / 258
This option allows to send an ASAP to a previously selected object ( rack, subrack, board, port and TP).
The system provides facilities to allow/inhibit the spontaneous notifications of the incoming alarms.
g)
N.B.
h)
Inhibiting alarm notification means that alarms are not forwarded to the CT, but are still
generated by the NE.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
193 / 258
NE Alarms:
In the current release, all NE alarms are listed also when selecting a filter option.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
194 / 258
This chapter describes the access to the Alarm Surveillance information of the NE.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
195 / 258
Selecting the Diagnosis pull down menu ( see Fig. 179. on page 196 ), then selecting Abnormal
Condition
List option. The screen relative it opens ( see Fig. 180. on page 196 ). This screen shows the Type and
the
Name of the forcing of Equipment.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
196 / 258
This option allows to relieve the abnormal conditions related to the N.E..
In the Diagnosis pulldown menu, select the Log Browsing option. The following options are
offered:
Fig. 181. Log Browsing option in the Network Element context view
The Logld1 and Logld2 options are offered
Select the Log Browsing option to access the Event Log file.
The Configuration and Log Browsing ELM windows open, permitting to analyze all events and alarms
stored in the NE.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
197 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
198 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
17 PERFORMANCE MONITORING
This chapter deals with the use of the Performance Monitoring functionalities.
17.1 Introduction
In the current release software the Performance Monitoring are supported in both Line and Radio sides
of the board.
Selecting the circuit Regenerator Section Termination ( RST radio or RST line ), and then selecting the
Performance function on Port menu option ( see Fig. 182. on page 199 ), it is possible to see the
Performance Monitoring configurations ( see next para. 17.2 on page 204 ).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
199 / 258
For the purpose of quality supervision, the values of the error counters can be compared to user-defined
threshold levels. If a counter value crosses a threshold level, then a notification (threshold crossing alarm)
is issued.
The mains performance management functions are the following:
Configuration of the quality thresholds that generate alarms and log records whenever preset values
are exceeded.
17.1.1 Overview
These functions are described in the following chapters and are supplemented by general information
concerning performance monitoring on the NE.
Chapter Configuration deals with the configuration of the performance monitoring features
Chapter Display Current Data deals with the display of the current performance data
Chapter Display History Data deals with the display of the history performance data
Chapter PM Threshold Table Selection deals with the selection of the threshold tables
Chapter PM Threshold Table Modification/Display deals with the modification and display of the
threshold tables.
The Operator is taking account that the LHR N.E.s and so in Regenerator side, ONLY the
Unidirectional Performance Monitoring of a selected TP is supported.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
200 / 258
The Performance Monitoring domain counts these errors during specified granularity periods (15 min.,
24h) and stores the values in history data logs.
Background Block Error (BBE): a BBE counter measures the number of errored blocks that one
not part of an SES.
Errored Second (ES): a one second period with one or several errored blocks or with a defect.
Severely Errored Second (SES): a one second period that contains > 30% of errored blocks, or
at least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
NearEndUnAvailable Second (UAS): an Unavailable Second is a second that is part of the
Unavailable Time.
Further definitions:
ED
Errored Block (EB): a block in which one or several bits associated with the block are errored.
Unavailable Time (UAT): an unavailable time period begins at the onset of 10 consecutive SES
events. These 10 seconds are considered to be part of the unavailable time. A new available time
period begins at the onset of 10 consecutive non-SES events.
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
201 / 258
17.1.3 Granularity
This NE supports unidirectional PM of 15 minute and 24 hour granularities. When the monitoring period
is over, the performance data is stored in the associated history data log. If 15 minute is free error, the
period isnt stored in history data log.
Time stamping of history records is performed using UTC (as for all alarms).
The measurement intervals start at 00 : 00 (UTC) for the 24-hour periods and at xx : 00, xx : 15, xx : 30
and xx : 45 for the 15-minute periods.
17.1.4 Data Collection
N.B.
The PM data is not counted on those boards that were plugged out at the moment when data
collection was enabled (see PM Configuration dialogue). Nevertheless, the PM data is
counted on boards that were plugged in at the moment when data collection was enabled, but
were plugged out and back in some time during data collection.
If an equipment or line protection switching occurs during a counting interval, the NE does not make a
complete performance measurement for the protected TPs.
Only the period between the last switch and the end of the counting window is counted.
The interval is marked for suspect data and the elapsed time indicates the length of the measured period.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
202 / 258
17.1.5 Thresholds
For quality supervision purposes, the errors accumulated by the performance counters can be compared
to given threshold levels. If a counter value crosses a threshold level, a Threshold Crossing Alarm (TCA)
is sent to the Alarm Manager.
The threshold values are set in threshold tables together with a severity level and a flag indicating whether
crossing this value should be notified by an alarm and logged or only stored in the current problem list.
The user can create, modify, and delete such tables.
Different thresholds can be assigned for near end and far end and for15 minutes and 24 hours
granularities.
The TCA only reports the value of the counter that has crossed the threshold; it does not provide a
complete set for all counters. Therefore, the user has to explicitly retrieve all current performance data after
receiving an alarm. The user can retrieve this information from a dialogue.
Concerning the clearance of the 15 min. and 24 h TCAs the system behavior is different in the two cases:
24 h (implicit clearance):
A TCA is reported for each interval in which its respective threshold has been crossed. The system
implicitly clears the TCAs at the end of the 24 hour period.
The value for the lower threshold is fixed to 0 (only a single threshold is provided by a threshold
table).
An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and
SES had not reached the low threshold (lower threshold equal to 0).
The TCA even in case of a suspect interval is cleared if no unavailability was detected and the lower
threshold had not been reached.
Additionally, an explicit clearance of the TCAs for all granularity periods is done if any of the following
events occurs during the current interval:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
203 / 258
Select the Port menu option and open the PM Configuration dialogue (see Fig. 183. on page 205) by
clicking in Configure Monitoring menu option.
This PM Configuration dialogue is used as the main interface to all PM services. Every
configuration of all monitoring intervals is defined using this dialogue.
The PM Configuration dialogue is designed as a notebook consisting of a text field, to identify the
selected TP, and a number of page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
Each page label presents a range of parameters for one near end granularity period (15 min. or 24 h),
which form together a dataset. To select a special page label, click the top part of the label:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
204 / 258
17.2 Configuration
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
205 / 258
Activate any item within the page label by selecting the respective Radio button.
Mode
Data Collection
Select this button to a activate performance monitoring. Disabling Data Collection leads to
clearance of the current and all history data of this entity.
N.B.
When disabling all current data sets at once, an error message might appear, indicating
the failure is due to some other problems. In this case, close the dialogue, reopen it, and
repeat your request.
Create History Data
If this item is selected, a history data collection is performed in the selected entity for the
corresponding TP.
Note that, on disabling this mode item, no history data is available. Nevertheless, the datasets
collected prior to deactivation are not cleared and are displayed after re-enabling the item, as
long as the number of displayed datasets does not exceed 16 (for 15 min. granularity) or 3 (for
24 hours granularity).
Notifications
N.B.
This parameter can only be selected during creation and cannot be subsequently
modified.
Suppress Additional Threshold
Disabled:the alarm is generated every time the value exceed the upper threshold ( value up).
Enabled: after a first alarm generation, the alarm is generated again when the value exceed the
upper threshold ( value up ) after the lower threshold ( value down ) has been exceeded.
Threshold Table
Attach a threshold table to the selected TP. Only assign threshold tables that match the granularity
period of the datasets (i.e. a 15 min. threshold table must not be assigned to a 24 h dataset).
Otherwise the Transmission view is blocked and can only be released by closing and reopening
the PM Configuration window and the Transmission view.
Click Attach... to open the PM Threshold Table Select dialogue ( see Fig. 186. on page 212 ) and
configure the threshold table ( see Chapter 17.5 on page 211 ).
Select Remove to disassociate the threshold table from the entity.
N.B.
The attachment of a threshold table can only be applied successfully, if Data Collection
is enabled. The user can recognize that the apply was not successful when the busy cursor
does not appear.
Confirm the configuration with the Apply button before closing the dialogue. Otherwise, the configuration
would go lost.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
206 / 258
This Current PM Data dialogue is used to show the results and status of the Performance
Monitoring counters.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
Each page label presents a range of parameters for one near end and far end granularity period (15min.
or 24h) which form together a dataset. To select a special page label, click the top part of the label:
N.B.
If a page label is unselectable after a refresh action, close the dialogue and reopen it.
This dialogue display all datasets available that are related to the TP selected and recorded in the current
monitoring interval.
Administrative State
Indicates whether the PM collection is locked for the local user or not.
Operational State
Indicates whether PM is enabled or disabled.
Suspect Data
Indicates whether collection errors occurred during the collection period.
Threshold Table
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
207 / 258
The Unavailable ThresholdCrossed entry indicates that both alarms are active. Since the
text field is too small to display the full text at a time, use the cursor to scroll the text field
in this case.
Elapsed Time
Indicates the time elapsed since the instant when the monitoring interval was started. This
information tells the user whether data collection covers the whole period.
Reset button is used to restart the counting period. Two buttons are present for nearend and farend
periods.
At the bottom, the PM results are listed.
N.B.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
208 / 258
N.B.
This PM History Data dialogue is used to show the stored Performance Monitoring counting.
The PM History Data dialogue is designed as a notebook consisting of a text field, to identify the selected
TP, and a number of page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
Each page label presents a range of parameters for one near end and far end granularity period (15min.
or 24h). To select a special page label, click on the top part of the label.
All available datasets (entities), are related to the selected TP are displayed in the table:
The number of recorded events concerning an entity is subdivided into near end and far end data
Elapsed Time
indicates whether the data collection was complete (see para.17.1.4 on page 202)
susp
indicates the suspect data where collection errors are occurred during the collection period.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
209 / 258
If the limit of 16 datasets (for 15 min. granularity) and 3 datasets (for 24 h granularity) is reached, then the
oldest set in the list is cleared when the next data set arrives.
N.B.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
210 / 258
In case of 15 min. entities, max. of 16 datasets recorded in the previous 16 monitoring intervals can be
displayed simultaneously for each counter; the 24h entities display max. of 3 datasets (previous 3
monitoring intervals). These figures cannot be changed by the user.
N.B.
Do not open several dialogues at the same time by using both possibilities. Since these
dialogues are not synchronized, they could display different contents.
Note that a threshold table cannot be deleted if it is attached to a PM entity. An error message informs
the user about this situation. The Delete function is not implemented yet.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
211 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
212 / 258
Modify the alarm Severity for each PM attribute in the case a threshold is crossed.
3)
Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
5)
To modify more than one threshold table, do not close the dialogue, but select the next threshold
table in the PM Threshold Table Selection dialogue and press the Modify button
(see Fig. 186. on page 212).
2,159,100
207,273,600
536,100
51,753,600
900
86,400
SES, FESES
810
78,760
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
213 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
214 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
18 SOFTWARE MANAGEMENT
This chapter deals with the management of the functions related to the software verification/download and
to the backup and restore of equipment configuration data. The basic principles of these management
functions are explained in section 1 (Introduction) of this handbook.
Software Management
OPERATOR
MANAGER
Download
Control
Event
Report
AGENT
NE
Software Downloading
OPERATOR
Transfer
Request
SERVER
CLIENT
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
215 / 258
Software Package: Software Package stands for a piece of software which can be executed by an
NE of a given type. It consists of one or several Software Units and a Descriptor File. A software
package is identified by its name, release, version, and edition.
On the NE (i.e. once downloaded), a software package can be:
a standby version: a software package that is neither the active version nor the boot
version
Software Unit: A Software Unit is a part of a software package which is either an executable code
or a data segment of a given board within an NE. A software unit is also identified by its name, release,
version, and edition.
Descriptor File: A Descriptor File contains information on the software package it belongs to and
lists the component software units. Each software package must have a descriptor file, otherwise it
would not be possible to interpret the contents of the package.
Commit (active) version: the software version currently running on the NE.
Standby version: a software version that has been downloaded on the NE, but is not in the
active state.
Two main functions are involved in software downloading:
ED
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
216 / 258
The naming conventions used for Download Management are the following:
All software download operations are carried out from the Software Download Manager.
To display the Software Download Manager menu from the main view, select the NE on which you want
to perform download operations, then select the Download pull down menu. The following menu is displayed:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
217 / 258
You can request the NE to start / abort a software download operation. After selecting the desired NE, you
must choose an available software package, set the required download / activation attributes, and then
start the download process. All of these operations can be performed from the SW downloading dialogue
box.
From the Download cascading menu, select the Init download option.
The Software download initiate dialogue box opens.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
218 / 258
Click the Forced pushbutton to set the forced download attribute: then download all software units of the
Descriptor file.
If you want stop the download operation, click the Cancel pushbutton in the Software download initiate
dialogue box to close it.
Click the OK pushbutton to start the download. From the confirmation dialogue box that opens, you can
confirm or cancel the download. If you confirm the operation, then the SW download initiate dialogue box
disappears and the Software download in progress dialogue box is displayed ( see Fig. 192. ), from which,
if necessary, you can abort the software download.
You can monitor the download progress by means of the Software download in progress dialogue box,
which also enables you to possibly abort the current download.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
219 / 258
The operator can get information on the software package of the NE at any moment, even if no download
operations have been performed previously.
For this, purpose from the Download pull down menu select the Units info option.
The following dialogue box opens.
The Detail button allows to give more information on a selected software package.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
220 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
221 / 258
From the Download pull down menu, select the MIB management option. The following window is displayed:
Available backups on local server: gives the list of the backups available on the Craft Terminal,
Backup name: to enter a new backup name.
Click the Activate pushbutton, to activate an already restored MIB. Only at this point it becomes effective
on the NE.
Click the Close pushbutton, to exit from the NE MIB management window.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
222 / 258
18.6 Restart NE
The restart operation is a software reset and can be executed in normal traffic conditions.
A restart operation activates the Commit (active) version in any case.
From the Supervision cascading menu, select the Restart NE option.
The following dialogue box opens.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
223 / 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
224 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
This chapter presents the system from the management software point of view and is organized as follows:
Functional description
on page 226
Configurations
on page 227
on page 227
on page 228
Equipment management
on page 229
Fans shelf
on page 234
Transceiver shelf
on page 235
Physical Connectors
on page 236
Compatible boards
on page 245
Transmission management
on page 248
Radio management
on page 249
Performance Monitoring
on page 251
on page 252
Overhead management
Phonic parameters
on page 253
on page 255
on page 255
on page 255
on page 255
on page 256
Connection management
on page 257
Software management
on page 258
on page 258
Security management
on page 258
Support management
on page 258
Test management
on page 258
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
225 / 258
A Radio Relay System is composed of two terminal stations ( Radio Terminal ) which may be separated
by one or more repeater stations ( Radio Repeater ).
These Radio Terminal manage the following:
physical layer
Optical fibre
or
Coaxial cable
Optical fibre
or
Coaxial cable
Radio terminal
Radio terminal
The main functions performed by the radio systems are the following:
Radio
The function converts a radio frequency signal into an internal logic level STM1 signal, and vice
versa. Specifically, the following functions are performed:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
226 / 258
19.2 Configurations
The identification of the configuration is obtained by means of the provisioning process. A check against
the provisioned configuration is performed reading the dip switch position. The following table contains
the list of configuration supported in the current release.
Configuration
1+1 HET
N+0 (N=1 .. 8)
N+1 (N=1 .. 7)
in N+1 configuration (N minor 8), one channel, among N main channels (protected), can be
transmitted on the spare channel (protecting) by hitless switch function; moreover, this configuration
can be used to transmit an occasional main channel (extra traffic) on the spare;
in 1+1 configuration, the protected channel is permanently transmitted on the spare channel
(protecting) by hitless switch function; extra traffic cannot be supported.
in N+0 configuration (N minor or equal 8), these channels are independent each other (there is only
a communality in terms of service channels and, eventually, of WST management, see below), hitless
switch function is not provided.
In each of the configuration above, the managed signal can be a STM1 or subSTM1.
Each of these channels transmits one main signal, but it can also transmit, according to the configuration,
auxiliary ones:
They are transmitted using the radio frame complementary overhead (RFCOH, an arbitrary and
unstandardized extra SDH frame overhead).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
227 / 258
The management of the SDH radio NEs could be divided in several components called domains, where
each of them addresses a specific aspect of management. The following domains were thus identified :
the equipment domain is responsible for managing the NE as a whole, controlling audible and visual
alarms and maintaining the current date and time of the NE. It is also in charge of configuring and
supervising the physical entities (rack, subrack, boards) of the NE. This domain manages also
power supplies and external points.
the transmission management domain : it is in charge of reflecting the current transport capabilities
of the NE. It configures and monitors transport functions performed in the equipment.
the radio management domain : it is in charge of reflecting the current transport capabilities of the
NE for radio specific parts. It configures and monitors transport functions performed in the radio
physical layer.
the performance management domain : it is responsible for monitoring the quality of transmission.
the overhead management domain is in charge of the management of the overhead access for the
electrical or optical interface.
the radio overhead management domain is in charge of the management of the overhead access
for the radio interface.
the communication and routing management domain covers all the mechanisms involved in the
exchange of management information between elements of the TMN. It defines management rules
for the establishment and the release of associations and for the use of the directory service.
the support management domain is responsible for event logging and reporting, and for
configuration of alarm severity assignment.
the security management domain is responsible for controlling any Q3 OS trying to open an
association with the NE. The Q3 OS may control the local terminal access. Human operators at the
F interface may be granted specific access rights (user profile with password and authorized
operations).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
228 / 258
shelf 2:
Base Band shelf
shelf 4:
Transceiver shelf
shelf 1, 3:
Fans shelf
The equipment types associated to the racks and shelves and shown at Q/F interfaces are described in
the following table.
Num.
Equipment Type
Label
Rack
RACKLHR
SRBB11
SRBBN0
(note 1)
SRBBN1
(note 1)
Notes
Transceiver SRTRI1HET
(note 2)
SRFANS
(note 3)
(note 3) The fans shelf upper is necessary to cool the ADM shelf (if any); the other one, between
Base Band shelf and Transceiver shelf, can be present to cool LHR equipment.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
229 / 258
2 3
S
Y
S
C
O
S
E
R
V
R
M
R
D
A
0
1
M
D
1
R
M
R
D
A
2
2
R
M
R
D
A
3
3
P
S
F
1
24 25
10 11 12 13 14 15 16 17 18 19 20 21 22 23
R
R
A
0
The base band shelf (see Fig. 199. ) contains the following units:
slot
1:
SYStem COntroller card
slot
2:
SERVice card.
slots
3, 5, 7, 9, 11,
slots
4, 6, 8, 10, 12,
slot
23, 24:
these slots are not equipped in the current release.
slot
25:
PSF1 card
slots
2635:
PSU cards
slot
36:
PSF2 card
R
M
R
D
A
4
4
R M
R D
A 5
5
R
R
A
6
M
D
6
R M
R D
A 7
7
R M
R D
A 8
8
R M
R D
A 9
9
P
S
U
0
P
S
U
1
P
S
U
2
P
S
U
3
P
S
U
4
P
S
U
5
P
S
U
6
P
S
U
7
P
S
U
8
P
S
U
9
P
S
F
2
26
27
28
29
30
31
32
33
34
35
36
The SERVice (SERV) card contains the auxiliary AUX/EOW service channels, the protection of the WST
channels and the service channels, the switch logic of the RPS protection (used only in case of 1+1 and
N+1 configurations) and it can host a module (TPHDEV), adding a voice channel.
The RRA units are connected to the transmission line through one optical (see Fig. 200. ) or electrical
interface. The electrical interface is placed directly on RRA units, instead the optical one on a optical
module placed inside the RRA unit itself (a drawer into the front panel).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
230 / 258
Slot 3 is used as a standby radio channel in N+1 and 1+1 configurations otherwise it is used as a main
radio channel in N+0 configuration. In N+1 and 1+1 configurations, this slot can be equipped by a RRAS
(RRA standby) unit and only in N+1, the same interface previously described for the RRA (optical) can
be provided, if extra traffic is actuated; in N+0 configuration, this slot can be equipped by a RRA unit, in
this case the optical interface module can be provided.
Just one physical RRA unit exists both for transmission of STM1 signal or subSTM1 one.
The same thing is applied to the RRAS unit. Logical card type are used to distinguish the way of working
of the cards.
Module
STM1
port
RRA unit
The PSF boards contain the filter for the PSU boards and the DC/DC converter to supply System
Controller and SERVICE boards; the two PSF boards are in protection between them.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
231 / 258
At Q/F interfaces the management of WST and Service Channels protection is performed using logical
equipment type (modules) contained in Service units, according to the following rules:
service channel protection on channel 0 and 1 and no WST protection: CH01SCP has to be
provisioned
service channel protection on channel 0 and 9 and no WST protection: CH09SCP has to be
provisioned
service channel protection on channel 1 and 2 and no WST protection: CH12SCP has to be
provisioned
service channel protection on channel 1 and 9 and no WST protection: CH19SCP has to be
provisioned
service channel protection on channel 8 and 9 and no WST protection: CH89SCP has to be
provisioned
service channel and WST protection on channel 0 and 1: CH01SCPWP has to be provisioned
service channel and WST protection on channel 0 and 9: CH09SCPWP has to be provisioned
service channel and WST protection on channel 1 and 2: CH12SCPWP has to be provisioned
service channel and WST protection on channel 1 and 9: CH19SCPWP has to be provisioned
service channel and WST protection on channel 8 and 9: CH89SCPWP has to be provisioned.
The equipment types associated to base band shelf and shown at Q/F interfaces are described in the
following table.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
232 / 258
The couple of radio channels which carry both the protected service channels and WST ones (if any) is
defined via software. These channels can be chosen among the following five couples:
channels 0, 1
channels 0, 9
channels 1, 2
channels 1, 9
channels 8, 9
Num.
Equipment Type
SYSCO
Massmemory device
MEMDEV
up to 1
Additional
housekeeping device
HKDEV
SERVICE card
SERV
up to 1 Tph device
Label
TPHDEV
Notes
RRA1W1
RRA0W0
up to 8
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
233 / 258
Equipment Type
Label
Opt.
STM1
module
up to 1
up to 8
Notes
S.1.1
IS1.1
IF subSTM1 0 WST
module with combiner IF0W0CO
function
up to 8
up to 8 PSU 48/60 V
2
Battery filter
PSL4860
PSF
slot 12:
FANSL card
The FANS shelf contains two fans units, in order to provide the necessary ventilation to the equipment;
each fan unit contains four fans.
The equipment types associated to this shelf and shown at Q/F interfaces is described in the following
table.
Num.
Equipment Type
up to 2
ED
Fan card
04
Label
FANSL
Notes
It includes four fans.
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
234 / 258
Num.
slot 110:
TRI card
T
R
I
0
T
R
I
1
T
R
I
2
T
R
I
3
T
R
I
4
T
R
I
5
T
R
I
6
T
R
I
7
T
R
I
8
T
R
I
9
10
Equipment Type
up to 8
Transceiver
128 QAM
Transceiver
128 QAM
Label
standard TRI128
high
up to 16 Receiver module
(note 1)
Notes
It includes Tx, DC/DC converter modules.
RX128
(note 2)
(note 3)
(note 1) In order to realize the transceiver function management, the RX and LO modules have to
be added to TRI128 or TRI128HP module.
(note 2) In the space diversity configuration, each transceiver contains two receivers, otherwise it
has one receiver only.
(note 3) Each transceiver always contains two local oscillator modules (one for rx, one for tx).The
same type of local oscillator is used for both the functions.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
235 / 258
The supporting field of the physicalConnectorList attribute of the sdhEquipmentR instances depends on
the card type and contains a pointer to the corresponding transport objects. Only the cards reported in the
following table have the field not empty.
SERVICE card
TPH device
Label
Number of
objects
Objects
IS1.1
labelledOSPITTPBid
v11TTPBid
v24TTPBid
4
(note 1)
pPITTPBidR1
q23DTMFTTPBid
q23DTMFTTPBid
pPITTPBidR1
up to 1
labelledESPITTPBid
pPITTPBidR1
up to 1
labelledESPITTPBid
up to 1
labelledESPITTPBid
pPITTPBidR1
RRAS0W0
up to 1
labelledESPITTPBid
TRI128
radioSPITTPBidR1
TRI128HP
radioSPITTPBidR1
SERV
TPHDEV
RRA1W1
RRA0W0
RRAS1W1
(note 1) 3 associated to G.703 interfaces, 1 to 2Mbit WST ones only if STM1 signals are
supported.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
236 / 258
Allowed Equipment
Type
Label
Creation/
Deletion
Replaceable
Rack
RACKLHR
1.1
not provisioned
FANS Shelf
(ADM cooling)
SRFANS
1.2
not provisioned
1+1 Base Band Shelf
N+0 Base Band Shelf
N+1 Base Band Shelf
SRBB11
SRBBN0
SRBBN1
1.3
not provisioned
FANS Shelf
(LHR cooling)
SRFANS
1.4
not provisioned
1+1 HET Transceiver Shelf
N+1 / N+0 Transceiver Shelf
1+1 HET Transceiver Shelf with
Space Diversity
N+1 / N+0 Transceiver Shelf with
Space Diversity
SRTRI1HET
SRTRIN
SRTRISD1HET
SRTRISDN
The following Tab. 9. thru Tab. 16. indicate the allowed equipment types for each slot inside each shelf
type, if a creation/deletion operation can be performed by the operator and if the board can be physically
replaced.
The bold enhanced configuration is the default value.
N.B.
ED
As already said, a check against the provisioned configuration is performed reading dipswitch
position used to identify the configuration supported: in this way, a mismatch is pointed out when
the subrack equipment types (Base Band and Transceiver subrack) are not coherent with the
configuration of the dipswitches.
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
237 / 258
Slot
Label
Creation/
Deletion
Replaceable
SYSCO
1.1
Massmemory device
MEMDEV
1.2
not provisioned
Housekeeping device
HKDEV
SERV
2.1
not provisioned
Ch. 0, 1 for Serv. Ch. prot. module
Ch. 0, 9 for Serv. Ch. prot. module
Ch. 1, 2 for Serv. Ch. prot. module
Ch. 1, 9 for Serv. Ch. prot. module
Ch. 8, 9 for Serv. Ch. prot. module
Ch. 0, 1 for Serv. Ch. & WST prot. module
Ch. 0, 9 for Serv. Ch. & WST prot. module
Ch. 1, 2 for Serv. Ch. & WST prot. module
Ch. 1, 9 for Serv. Ch. & WST prot. module
Ch. 8, 9 for Serv. Ch. & WST prot. module
(note 1)
CH01SCP
CH09SCP
CH12SCP
CH19SCP
CH89SCP
CH01SCPWP
CH09SCPWP
CH12SCPWP
CH19SCPWP
CH89SCPWP
2.2
not provisioned
Tph device
TPHDEV
Y=
5, 7,
9, 11,
13, 15,
17, 19,
21
not provisioned
RRA STM1 1 WST card
RRA subSTM1 0 WST card
(note 2)
RRA1W1
RRA0W0
Y.1
not provisioned
Optical STM1 module
IS1.1
Z=
4, 6,
8, 10,
12, 14,
16, 18,
20, 22
not provisioned
Modem 128QAM STM1 1 WST module
Modem 128QAM subSTM1 0 WST module
(note 2)
MD1281W1
MD1280W0
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
238 / 258
SRBBN0 / SRBBN1
Slot
Z.1
not provisioned
IF STM1 1 WST module with Combiner function (note 3)
IF subSTM1 0 WST module with Combiner
function (note 4)
IF STM1 1 WST module with XPIC function
(note 5)
Label
Creation/
Deletion
Replaceable
IF1W1CO
IF0W0CO
IF1W1XP
Z.2
not provisioned
IF STM1 1 WST module with XPIC function
(note 3)
IF1W1XP
23
not provisioned
24
not provisioned
25
PSF
X=
26..35
not provisioned
48/60 V Power Supply unit
PSL4860
36
PSF
(note 1) The creation of the CHxySCP and CHxySCPWP modules is allowed only if the boards
(RRA, MD and TRI) of x and y channels have been already configured.
As WST channels can be carried only by STM1 signals, the provisioning of the CHxySCPWP
equipment types is allowed only if the RRA and MD boards of the x and y channels have been
configured, respectively, with RRA1W1 and MD1281W1 equipment types.
When the Service card is removed, the 2 Mbit/s protected/unprotected signal switch selects always
one unprotected hardware configuration; in this way, if the 2 Mbit/s signal software configuration is
protected, there will be a mismatch to the new hardware configuration; when the Service card is
plugged in, the prospective mismatch is removed. To avoid the mismatch when the Service card is
missing, the operator should change the equipment type from CHxySCPWP to CHxySCP.
(note 2) In order to define the bit rate of the signal at radio port, only coherent equipment types
related to the RRA and MD boards are allowed (RRA1W1/RRAS1W1 and MD1281W1 or
RRA0W0/RRAS0W0 and MD1280W0).
(note 3) Allowed only if the containing slot has been provisioned with the MD1281W1 equipment
type and Space Diversity configuration.
(note 4) Allowed only if the containing slot has been provisioned with the MD1280W0 equipment
type and Space Diversity configuration.
(note 5) Allowed only if the containing slot has been provisioned with the MD1281W1 equipment
type and not Space Diversity configuration.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
239 / 258
Tab. 10. N+0/N+1 Base Band slots configuration shelf type dependent
Shelf
Type
Label
Creation/
Deletion
Replaceable
SRBBN0
not provisioned
RRA STM1 1 WST card
RRA subSTM1 0 WST card
(note 1)
RRA1W1
RRA0W0
SRBBN1
not provisioned
RRA STM1 1 WST standby card
RRA subSTM1 0 WST standby card
(note 1)
RRAS1W1
RRAS0W0
SRBBN0
&
SRBBN1
not provisioned
Optical STM1 module
IS1.1
Slot
3.1
(note 1) In order to define the bit rate of the signal at radio port, only coherent equipment types
related to the RRA and MD boards are allowed (RRA1W1/RRAS1W1 and MD1281W1 or
RRA0W0/RRAS0W0 and MD1280W0).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
240 / 258
SRBBN0 / SRBBN1
SRBB11
Slot
Label
Creation/
Deletion
Replaceable
SYSCO
1.1
Massmemory device
MEMDEV
1.2
not provisioned
Housekeeping device
HKDEV
SERV
2.1
not provisioned
Ch. 0, 1 for Serv. Ch. prot. module
Ch. 0, 9 for Serv. Ch. prot. module
Ch. 0, 1 for Serv. Ch. & WST prot. module
Ch. 0, 9 for Serv. Ch. & WST prot. module
(note 1)
CH01SCP
CH09SCP
CH01SCPWP
CH09SCPWP
2.2
not provisioned
Tph device
TPHDEV
not provisioned
RRA STM1 1 WST standby card
RRA subSTM1 0 WST standby card
(note 2)
RRAS1W1
RRAS0W0
Y = 5,
21
not provisioned
RRA STM1 1 WST card
RRA subSTM1 0 WST card
(note 2)
(note 3)
RRA1W1
RRA0W0
Y.1
not provisioned
Optical STM1 module
IS1.1
not provisioned
Z = 4,
6, 22
not provisioned
Modem 128QAM STM1 1WST module
Modem 128QAM subSTM1 0WST module
(note 2)
(note 4)
MD1281W1
MD1280W0
Z = 8,
10, 12,
14, 16,
18, 20
not provisioned
Y=
9,
13,
17,
ED
7,
11,
15,
19
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
241 / 258
Z.1
not provisioned
IF STM1 1WST module with Combiner function (note 5)
IF subSTM1 0WST module with Combiner
function (note 6)
IF STM1 1WST module with XPIC function
(note 7)
Label
Creation/
Deletion
Replaceable
Slot
IF1W1CO
IF0W0CO
IF1W1XP
Z.2
not provisioned
IF STM1 1WST module with XPIC function
(note 5)
IF1W1XP
23
not provisioned
24
not provisioned
25
PSF
X=
26, 27
34, 35
not provisioned
48/60 V Power Supply unit
(note 8)
PSL4860
36
PSF
(note 8) If the couple of channels 0 and 9 is chosen, the PSU 0 and 9 have to be provisioned
(respectively in the slots 26 and 35). If, in addition, the protection of power supply for RRA boards
is required, two other PSU boards have to be provisioned: PSU 1 and 8 (respectively, in the slots 27
and 34).
If the couple of channels 0 and 1 is chosen, the PSU 0 and 1 have to be provisioned (respectively,
in the slots 26 and 27) ; in this case, the protection of power supply for RRA boards is automatically
achieved.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
242 / 258
SRTRIN / SRTRISDN
Slot
Label
Creation/
Deletion
Replaceable
X=1..N
(N=10)
not provisioned
Transceiver standard 128 QAM card
Transceiver high power 128 QAM card
TRI128
TRI128HP
Y (note 1)
X.1
LO
X.2
LO
X.3
RX module (note 2)
RX128
X.4
(note 1) The creation of the TRI card will generate an automatic creation of the contained physical
components with the related equipmentExpected (LO, RX128).
(note 2) Subslot X.3 is equipped by a RX module used to manage the Rx main signal, subslot
X.4 the RX diversity one.
Tab. 13. N+1/N+0 Transceiver slots configuration shelf type dependent
SRTRIN / SRTRISDN
Slot
Shelf Type
Label
Creation/
Deletion
Replaceable
SRTRIN
not provisioned
SRTRISDN
RX module
RX128
X.4
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
243 / 258
Creation/
Deletion
Replaceable
TRI128
TRI128HP
Y (note 1)
LO
X.2
LO
X.3
RX module (note 3)
RX128
Slot
Label
X=1,
2, 10
not provisioned
Transceiver standard 128 QAM card
Transceiver high power 128 QAM card
(note 2)
X.1
X.4
3..9
not provisioned
Shelf Type
Label
Creation/
Deletion
Replaceable
SRTRI1HET
not provisioned
SRTRISD1HET
RX module
RX128
X.4
SRFANS
ED
Slot
Label
Creation/
Deletion
Replaceable
not provisioned
FANSL card
FANSL
not provisioned
FANSL card
FANSL
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
244 / 258
SRTRI1HET / SRTRISD1HET
TRI128
TRI128HP
TRI128
TRI128HP
each RRA and MD board of the band base subrack is powered by one PSU; each PSU is
connected with another one in load sharing way (the power supply protection is only to RRA
board); SYSCO and SERV are powered by DC/DC converter inside the PSF unit;
The equipment protection scheme associated to converters in load sharing is not represented at the Q/F
interfaces.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
245 / 258
LHR NE has the capability to monitor 22 input contacts and provides 10 output contacts through the
System Controller (SYSCO) card. It is possible to expand the number of the input contacts adding a
daughter board (HKDEV device) with others 18 input contacts (40 input contacts in all).
Input Housekeeping (externalInputPoint)
Reference
User Label
Default value
Notes
HK_IN_x
CPIx
x = 1..22
HK_IN_AUX_z
CPI_AUXz
z = 23..40
Reference
User Label
Default value
Notes
HKy
CPOy
y = 1..10
The configuration of the input and output housekeeping will be preserved in case of restart.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
246 / 258
Position
Length
(Byte)
Encoding
Mandatory /
Optional
Format identifier
ASCII 22
Company identifier
12
ASCII
Unit mnemonic
36
ASCII
CLEI code
711
10
ASCII
1218
14
ASCII
1925
14
ASCII
Factory identifier
2627
ASCII
Serial number
2835
16
ASCII
Date identifier
36
ASCII 00
Date
3739
ASCII
Customer field
4062
46
ASCII
Checksum
63
BIN
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
247 / 258
up to 8 SDH ports
up to 8 radio ports
STM1 port
Radio Port
n=1..8
Fig. 203. Radio functional block diagram for LHR NE
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
248 / 258
RRA
RPS
MD
RFCOH
TRI
Tx
Mod
RSPI
Dem
Rx
LHR can transmit a STM1 signal or a sub STM1 one at radio interface. The information about the signal
type (STM1 or sub STM1) managed at radio interface is acquired by the equipment type of the RRA
board: STM1 signal when the RRA1 is provisioned, sub STM1 one when RRA0 is provisioned.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
249 / 258
According to the configuration two different RPS protection scheme types are supported by LHR NE: (1:N)
and (1+1). The following tables define the characteristics of both these types.
Tab. 17. 1:N RPS protection type parameters
Parameter
Values
Architecture type
1:N
Switching type
Single ended
Operation type
Revertive
Switching time
<= 10 ms
Priority
Applicable
External commands
Values
Architecture type
1+1
Switching type
Single ended
Operation type
Not Revertive
Switching time
1 ms
Priority
Not Applicable
External commands
Manual switch,
protecting
Force
switch,
Lockout
The configuration of the protection schemes is performed by the NE in conjunction with the equipment
provisioning process (declaration of boards). The protection schemes are not subject to explicit
configuration at the F or Q interface in terms of number and instance of boards which participate in a
protection scheme and their protection role (main / standby).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
250 / 258
The Performance Monitoring is responsible for quality events counting and reporting.
This paragraph concerns the monitoring of the common functional blocks supported by the LHR NE. For
the specific radio blocks: RSPI and RPS, refer to the next para.19.9.
LHR NE supports only the performance monitoring process with the maintenance purpose:
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
251 / 258
The radio specific performance monitoring defines new radio specific performance primitives, events and
parameters with associated requirements for data collection, threshold and history treatment. It covers the
following items:
Early Warning
Low BER
High BER
Signal Fail, it is generated by the RSPI functional block alarms (rx side) and by the fail of the
cards that handle the signal inside the radio section (i.e. RX, DEM).
The one second performance events are the following (listed with increasing priority):
N.B.
The RPS criteria can be monitored also in the N+0 configuration, even if in this configuration,
the hop and link (outside the protection) sections are coincident.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
252 / 258
V.11 ports
64/128 kbit/s
(note 1)
V.24 ports
RS232
G.703 ports
64kbit/s
Q.23 ports
DTMF
RSOH RFCOH bytes crossconnections
Engineering Orderwire unit phonic parameters
(note 1) The first three V.11 ports receive a 64 kbit/s signal and the fourth one a 128 kbit/s
(crossconnectible only to RFCOH bytes). Only one between the third and fourth can be
crossconnected.
RST
(line side)
RSOH bytes
RPS
RSPI
SERVICE CHANNELS
MATRIX
G.
7
0
3
p
o
r
t
V.
1
1
V.
2
4
Q.
2
3
p
o
r
t
p
o
r
t
p
o
r
t
RFCOH bytes
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
253 / 258
The following Fig. 206. shows the containment relationships of the objects related to the overhead bytes
(RSOH and RFCOH) and to the auxiliary ports and their connection relationships (between RSOH and
RFCOH bytes and between auxiliary ports and RFCOH bytes).
SDHNE
radioSPITTP
pPITTP
v11TTP
rfcohServiceChannelsCTP
rfcohServiceChannelsTTP
6
q23DTMFTTP
radioUserChannelCTP
radioOrder
WireCTP
rsOrderWireCTP
1
rsUser
ChannelCTP
q23DTMFCTP
rsNational
UseCTP
v11CTP
10
rsFuture
UseCTP
LEGEND
Connectivity Pointer
Termination Point
Point of Flexibility (crossconnection)
Containment/Naming relationship
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
254 / 258
Two telephone numbers are assigned to the NE (the second telephone number is available when the
TPHDEV module on the SERVICE board is provided).
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
255 / 258
the 2 Mbit/s Way Side Traffic (WST) channels management, they represent a service traffic in
addition to the main one;
Both the WST and service channels are transmitted using the radio frame complementary overhead
(RFCOH, an arbitrary and unstandardized extra SDH frame overhead).
One 2 Mbit/s Way Side Traffic can be inserted in each STM1 channel, sub STM1 channels
cannot transport any 2 Mib/s WST.
According to the configuration, LHR can support 1 protected and up to 8 unprotected WST
channels or up to 8 unprotected ones.
Only fixed connectivity between WST port and rfcohWSTTTPBid object is supported.
The requirements that the Service channels management must meet are listed here after:
ED
The service channels are : D1D3, ATPC, DSI, MC, 1 order wire channel and 6 user channels.
The service channels above listed are protected as a unique entity in 1+1 (this protection is
independent of WST channels protection) in all the configurations except the 4+0/4+1 East
West one (not supported in the current release).
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
256 / 258
The following table defines the characteristics of the WST and Service Channel protection.
Parameter
Values
Architecture type
1+1
Switching type
Single ended
Operation type
Not Revertive
Priority
Not Applicable
External commands
The configuration of the protection schemes is performed by the NE in conjunction with the equipment
provisioning process (declaration of boards).
Here after the role (protected and protecting) for each allowed couple of channels, is provided.
Tab. 19. Radio channels role for WST and Service Channels protections
Protecting
Protected
channel 0
channel 1
channel 0
channel 9
channel 1
channel 2
channel 1
channel 9
channel 8
channel 9
The distinction of the channels in protecting and protected is merely formal: in fact, in not revertive
configuration (this is the operation type of both these protections), the protecting channel becomes
protected after a switch and viceversa.
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
257 / 258
The software management is responsible for management of downloading operation, software version,
backup and software error processing.
The LHR control system is based on a distributed control strategy:
1 Equipment Controller
1 Radio Controller
n Supervisory Unit
Due to the strong interdependency between software of the Radio Controller and of the Supervisory Units,
they are considered as a unique software package. Also the software downloaded by the EC on SABY
FPGA is considered part of the EC software package. So one software object will be created for each of
these software packages.
The commitment of the activated version takes place implicitly together with the activation itself, so that
in case of spontaneous restart events the version used for rebooting is the active version. Since the
standby version is not automatically deleted, the system can be reverted back to the previously active
version by the OS or CT via another switch request.
events logging: to log events and to control of that logging by managing systems
alarm management: to report and to log alarms, to manage alarms severity assignment
alarm synthesis and summarization: to synthesize the current alarms of the NE and to provide visual
local alarm indications
abnormal conditions synthesis: to synthesize non usual conditions of the NE (e.g. manual operations,
loopbacks, slots equipped but not configured).
END OF DOCUMENT
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
258 / 258
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 List of the editions and modified parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
3
4
4
4
2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 MAINTENANCE OF THE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
7
7
7
10
11
13
02
020305
updated
A.FUMAGALLI ITACO
01
020111
validated
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
01A 011109
ED
proposaldraft
DATE
CHANGE NOTE
E.CORRADINI ITACO
M.CORBETTA
M.CORBETTA ITACO
M.CORBETTA ITACO
APPRAISAL AUTHORITY
ORIGINATOR
9600LSY REL.1.0
SWP REG.9600LSY R.1.0
C.T. OPERATORS HANDBOOK
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
1 / 24
FIGURES
Fig. 1. Alarm pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 2. Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 3. Example of Port View alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 4. Example of Board View alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 5. Example of Equipment View alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14
21
22
24
TABLES
Tab. 1. Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 2. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 3. Equipment view alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 4. RACKLHR rack alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 5. SERV unit alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 6. SYSCO unit alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 7. Optical STM1 module alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 8. MD module alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 9. RRA / RRA S / HKDEV modules alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 10. FANS unit alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 11. TRI module alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 12. MEMDEV module alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 13. RX / LO module alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 14. PSU unit alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 15. PSF unit alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 16. TPHDEV / IF1W1COIF0W0CO / IF1W1XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 17. Alarm Surveillance information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 18. General issues of the alarm meanings and their respective maintenance actions . . . . . . .
Tab. 19. Board alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
11
15
15
15
15
16
16
16
16
17
17
17
17
18
18
19
20
23
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
2 / 24
1 DOCUMENT GUIDE
1.1 Scope
1.1.1 Document scope
The LHR Maintenance Manual mainly describes the NE troubleshooting based on the use of the Craft
Terminal.
It applies to LHR SWP in the Version 1.0.
1.1.2 Target audience
The Maintenance Manual is intended for all users.
The documents that should be read before starting this document are:
The sections of this Handbook that should be read before starting are:
SECTION 1: Introduction
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Handbook Guide.
1.2.2 Glossary of terms
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
3 / 24
= new part
= modified part
= part unchanged
DOCUMENT EDITION
ED
01
02
m
Document guide
Maintenance introduction
Maintenance of the PC
02
03
04
05
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
4 / 24
2 MAINTENANCE INTRODUCTION
Problems with the Craft Terminal PC (shutdown and restart ). See Chapter 4 on page 5.
3 MAINTENANCE OF THE PC
With regard to maintenance PC, refer to the constructors documentation.
4.2 Procedure
In order to shut down the PC execute the command :
Start > Shut down
A window (Windows NT Security user dialog) is displayed. It permits to shut down the computer or restart
it.
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
N.B.
In the case this procedure is unsuccesful, carry out the checks indicated in paragraph
Problems with the Craft Terminal in section MAINTENANCE of the 9600LSY/LHR Technical
Handbook (N.B.).
N.B.
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
5 / 24
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
6 / 24
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The following interfaces are present on the equipment for troubleshooting purposes:
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.
WARNING:
The Power Supply Unit ( PSU ) and Power Supply Filter ( PSF ), must be always turnoff before
to begin the maintenance operation of Equipment
ED
on site.
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
7 / 24
Remote craft terminal: the operator, connected to a local NE, can remotely manage and troubleshoot
a network composed of max 32 NEs, including itself. This handbook applies.
Station supervisory center: the maintenance technician shall refer to the Remote Alarms received from
the equipment in a centralized office of the station i.e. :
T URGENT (MAJOR and CRITICAL), T NOT URGENT (MINOR): remote alarms pertaining to the
urgent, not urgent alarm type.
TAND: remote alarms of the both Battery voltages ( Battery 1 and Battery 2 ).
IND: Indeterminate alarm synthesis. Indicates a synthesis of the alarms not associated with other
severities. Not implemented in this case.
TORC: remote alarms of the Power Supply Filter Card Fail ( PSF 1 or PSF 2 ).
TANC: remote alarms of the both Power Supply Filter Card Fail ( PSF 1 and PSF 2 ).
Depending on the organization of the supervisory center, it is possible to locate the faulty equipment and
to detect the fault type and source.
On site : the operator is on site in case :
1)
2)
the equipment is not reachable by the remote manager (TMN or RCT) and therefore is isolated
3)
4)
In cases 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal and of rack
LED indications and station buzzers.
WARNING:
After having identified a unit to be replaced, in order to carry out correctly the replacement,
please refer to paragraph Unit Replacement Procedures in section MAINTENANCE of the
9600LSY Technical Handbook (N.B.).
N.B.
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
8 / 24
TMN network management center: by means of the TMN, the maintenance technician can see the
alarms sent by each equipment of the managed network (see the relevant TMN handbooks).
Yellow LED: detection of an ABNORMAL operating condition. Type: active loopbacks, forcing
the unit into service, laser forced ON or OFF, restoral attempt after ALS
The analysis of these LEDs allows to detect the alarm type (Urgent Not Urgent Indication) and its
relevant condition (Abnormal, Attended).
In the case of an URGENT or NOT URGENT alarm,after locating the alarmed equipment, the alarm
condition can be attended by pressing its respective the relevant alarm storing push button on the
SRBB11.
This condition causes:
On the rack:
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 cordconnected to the relative connector on the Subrack unit (SRBB11) front
coverplate (F interface).
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault
location and subsequent removal as indicated in para. 5.3 on page 10.
To correctly execute the troubleshooting operations the technician must know the exact
equipment configuration (see Equipment Configuration applications on the Craft Terminal).
The 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
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
9 / 24
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
Surveillance data.
The troubleshooting procedure is the following.
a)
Look at the active alarms on the Severity Alarm Synthesis, Domain Alarm Synthesis and
Management States Control Panel always present on the window (which summarizes all NE
alarms).Tab. 2. on page 11 describes the meanings of these alarms/statuses and its respective
maintenance actions.
b)
c)
It is possible to analyze the detailed alarms present on the TPs of the individual ports of the NE by
following the indication of para 5.3.2.1.1 on page 21.
d)
It is also possible to check the alarms statuses in the Board view and in the Equipment view are
also supplied following the indications of para 5.3.2.1.2 on page 22 and para 5.3.2.1.3 on page 24.
e)
These paragraphs describe the general issues of the alarms and their respective maintenance
actions to be done,based on the information given in the applications.
URGENT alarm indicates a severe alarm that could affect on the current traffic (interrupt or
degrade). Hence, a prompt intervention is necessary to restore the regular operating
condition of the equipment.
A message under the mouse facility provides the alarm or status complete name. A message appears in
the message area in the bottom left corner of the view.
An Automatic Laser Shutdown (ALS) feature is used to protect the operators working on the optical fibers.
When the ALS is active, it may be difficult to detect the link failed.
To locate it, it is necessary to force the ALS on, thus enabling the optical power transmission on the
opposite direction of the failed link.
During this phase the operator has to pay attention when working with fibers and connectors.
The ABNORMAL indication informs the operator that an ALS condition is forcedly set.
After completing the maintenance operation, reenable the ALS feature.
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
10 / 24
The following troubleshooting tables pertain to the alarm and status synthesis given in all the screens.
Tab. 2. Alarm Synthesis indication
Mnemonic
Critical alarm
MAJ
MIN
Warning alarm
Indeterminate alarm
EXTP
External Point
(Housekeeping alarm)
EQP
Equipment alarm
Transmission alarm
Supervision state
NE reachable/unreachable
Operation System
Manager level
IND
TRNS
SUP
COM
O. S.
MGR
Maintenance
CRI
WNG
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
11 / 24
NTP
AC
NB1:
ED
Maintenance
Abnormal Condition
Alarm Severity Assignment Profile can modify the assignment of each alarm root to the various
synthesis.
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
12 / 24
Mnemonic
If alarms are present, access the Alarm Surveillance (AS) for troubleshooting. For this purpose
select the Diagnosis pull down menu. With the Alarm pull down menu ( see Fig. 1. ). It is possible to
show all NE Alarms or filter the alarms report, for example only to display the alarms of a specific
domain (e.g. only the alarms of the Synchronization domain). This filtering feature is not currently
implemented, always all data is displayed).
In the synthesis list, it is possible to filter the data to show with the detailed view by double clicking the
selected line of the sublist of Fig. 2. on page 14.
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
13 / 24
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
14 / 24
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The information provided helps the operator during troubleshooting operations is presented in the
following tables.
Tab. 3. Equipment view alarms.
ALARM
LABEL
PROBABLE CAUSE
Backplane Failure
BKF
Battery Fail
BF
Battery Failure
ABF
LABEL
Backplane Failure
BKF
PROBABLE CAUSE
Wrong setting of the dipswitch
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Software Mismatch
VM
Version Mismatch
LAN alarm
LAN
Lan Failure
RC unreachable
ICP
SEP
Equipment Mismatch
RUTM
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
15 / 24
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
Unconfigured Equipment
UEP
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
Unconfigured Equipment
UEP
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
Unconfigured Equipment
UEP
ALARM
LABEL
PROBABLE CAUSE
Fan Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
Unconfigured Equipment
UEP
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
16 / 24
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
Unconfigured Equipment
UEP
ALARM
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
ALARM
LABEL
PROBABLE CAUSE
Card Fail
POP
Power Problem
Card Missing
RUM
Equipment Mismatch
RUTM
Unconfigured Equipment
UEP
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
17 / 24
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
BF
ALARM
Battery failure
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
Unconfigured Equipment
UEP
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
18 / 24
The following tables summarize the main information obtained in the AS view, starting from the left column:
TITLE
DESCRIPTION
Perceived Severity
Indicates the severity assigned to the alarm with its respective color,
e.g.: MAJOR, MINOR, WARNING.
Friendly Name
Identifies the rack, subrack, board, port, and TP in which the alarm is detected,
e.g.: / r01sr2b05/#port01EIS.
Event Type
Indicates the family type of the alarm as subdivided in the ASAP list, e.g.:
EQUIPMENT, COMMUNICATION.
Probable Cause
Indicates the fault/problem e.g.: loss of signal, transmitter degraded, replaceable unit missing,resource isolated.
Reservation Status
Clearing status
Acknowledge status
Indicates whether the alarm has been acknowledged (ACK) through the button on the Subrack unit or not ( SRBB11 ).
Correlated notification
Not used.
flag
Repetition counter
Not used.
The information supplied helps the operator during the troubleshooting operations.
Tab. 18. on page 20 supplies general information on the alarm meanings and on the respective
maintenance actions to be done bases on the information given in the applications.
The maintenance action must take account of the board where the alarm is detected.
The alarms of Tab. 19. on page 23 are also presented in the AS view.
The External Points 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
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
19 / 24
PROBABLE CAUSE
DISPLAYED ALARM
NAME AND/OR ACRONYM
Loss of signal
Transmitter Signal
Tab. 18. General issues of the alarm meanings and their respective maintenance actions
MAINTENANCE
Check line
Replace unit
Transmitter degraded
Loss of frame
AIS
Excessive BER
Degraded Signal
Loss of Pointer
Check line
Loss of multiframe
Check line
Configuration error
Frequency offset
Resource Isolation
Communication Subsystem
Failure
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
20 / 24
ED
OFF
ACTIVE
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
21 / 24
Alarm and status indications can be obtained at Board level, following the indication of chapter Board View
in the previous Section of this Handbook.
The Fig. 4. displays a typical Board view.
The alarm and status indications depend on the unit type; for example, the SDH units are organized into
two levels of presentation (in the first one of the available ports is selected) and each view contains
dedicated information.
The view comprises the Administrative State information;which is either in service or out of service.
Tab. 19. on page 23 lists the alarm indications possibly displayed on the Boards.
In the view, EPS indications can also be present.
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
22 / 24
DISPLAYED ALARM
NAME AND/OR ACRONYM
MAINTENANCE
Insert the right unit (unit inserted into a slot set with another
type of unit)
VM Version mismatch
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
23 / 24
Alarm indications can be obtained at the Equipment level, following the indication of the chapter
Equipment View in the previous Section of this Handbook.
Fig. 5. shows an Equipment view, with the alarm indications.
These alarms can be observed at the OS level.
END OF DOCUMENT
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
24 / 24
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 List of the editions and modified parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
3
4
4
4
2 SIBDL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Purpose of this procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Remote Access Service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Serial Cable Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
7
7
7
02
020305
updated
A.FUMAGALLI ITACO
01
020111
validated
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
01A 011109
ED
proposaldraft
DATE
CHANGE NOTE
E.CORRADINI ITACO
M.CORBETTA
M.CORBETTA ITACO
M.CORBETTA ITACO
APPRAISAL AUTHORITY
ORIGINATOR
9600LSY REL.1.0
SWP REG.9600LSY R.1.0
C.T. OPERATORS HANDBOOK
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
1 / 10
FIGURES
...............................................
...............................................
...............................................
...............................................
...............................................
8
8
9
9
10
TABLES
Tab. 1. Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
2 / 10
1 DOCUMENT GUIDE
1.1 Scope
1.1.1 Document scope
The SIBDL Manual describes the SIBDL application, used to download the NE software via Q or F
interface.
The need for the usage of this application is summedup in section INTRODUCTION of this handbook.
The SIBDL (Standard Image Binary DownLoad) procedure contains the following operative descriptions:
Configuration for SIBDL. Configurations to be performed for SIBDL operation are described. See
Chapter 2 on page 5.
Download with SIBDL. The complete procedure is indicated. See Chapter 3 on page 7
The sections of this Handbook that should be read before starting this document are:
SECTION 1: Introduction.
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Handbook Guide.
1.2.2 Glossary of terms
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
3 / 10
= new part
= modified part
= part unchanged
DOCUMENT EDITION
ED
01
02
m
Document guide
SIBDL configuration
02
03
04
05
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
4 / 10
2 SIBDL CONFIGURATION
2.1 Purpose of this procedure
This chapter describes the configurations to be performed for SIBDL operation.
2.1.1 Remote Access Service configuration
To install a new modem, the user should own the administrator privileges and need the installation
CDROM of Windows NT, then he should proceed as follows:
Double click the My computer icon on the PC desktop and double click the Control panel icon;
double click on Network icon;
select the Services folder in the Network window and push the Add button: start the Select
Network Service window;
In the dialogue box, select Remote Access Service (RAS) ;
follow the instructions.
To install a new modem, the user should own the administrator privileges, then:
Double click the My computer icon on the PC desktop and double click the Control panel icon;
push the Install Modem button in the Add RAS Device window: start the Install New Modem
window;
put a tick against Dont detect my modem; I will select him from a list and push the Next > button;
push the Have disk... button: start the Install from disk window;
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
5 / 10
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
6 / 10
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Maintenance phase, when replacing the System Controller card with a spare, and the spare one
unit doesnt contain software.
WARNING:
A download based on the SIBDL program puts the unit in exam out of service;
It must not be executed when upgrading an in service unit or when downloading a spare unit
that contains software; in this case use the EMLUSM Download option presented in the
previous section.
The SIBDL tool allows to download the software towards the NE using the Q interface (Ethernet
connection) or the RS232 (serial line) F interface of the NE (not implemented).
When using the Q interface, the time necessary to perform the operation is in the order of some minute.
WARNING: In a Windows NT environment, before using the SIBDL it should have configured:
The TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NT Administrator.
The RAS (Remote Access Service) and Serial Cable Modem presented at chapter 2 on page
5.
The download procedure based on the use of the SIBDL tool comprises the following steps:
1)
2)
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
7 / 10
In the screen that appears (see Fig. 1. ) with the command menu, select the automatic mode
command by typing 8 and then ENTER.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3)
In the field source file at the bottom, enter the path name of the NE descriptor file (see Fig. 2. ).
The path name has typically the following format (see an example in the figure):
<directory>/<NE name and release number>/<file descriptor>
5)
ED
Press ENTER.
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
8 / 10
6)
This step (see Fig. 3. ) asks for the entry of the IP Address .
If using Q interface:
7)
Press ENTER. The screen shows the progress state of the automatic download, with a final
message indicating that the download is completed(see Fig. 4. ).
Otherwise, repeat the procedure.
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
9 / 10
Press ENTER.
9)
8)
END OF DOCUMENT
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
10 / 10