LSY Operator Rel.01 Ed04

QUESTA PAGINA NON VA INSERITA NEL MANUALE
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 957.207.022
A Ed.04 3DB 02838 AAAA Ed.04
9600LSY Rel.1.0
SWP REG.9600LSY R.1.0
C.T. OPERATORS HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 396 + 4

DIMENSIONE BINDER SORGENTE (du ks): 386.951 Mbyte
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 4 SEPARATORI NUMERATI DA 1 A 4
4 REGISTERS NUMBERED FROM 1 TO 4 ARE NECESSARY
No pagine
(facciate)
No pages
1AA 00014 0004 (9007) A4 ALICE 04.10
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
GENERAL TABLE OF CONTENTS ED.04
INSERIRE SEPARATORE 1 - INSERT REGISTER 1
SC.1: INTRODUCTION ED.04
SC.2: LHR NE MANAGEMENT ED.04
SC.3: LHR NE MAINTENANCE ED.02
10
11
SC.4: SIBDL ED.02
10
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
396
TOTALE FOGLI A4 TOTAL A4 SHEETS:
198
04
numerate
numbered
RELEASED
957.207.022 TQZZA
3DB 02838 AAAA TQZZA

4
1/ 4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
Site
CONCOREZZO

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
WTD
Originators
M.CORBETTA
E.CORRADINI
C.NAVA
9600LSY REL.1.0
SWP REG.9600LSY R1.0
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
9600LSY REL.1.0 C.T. OPERATORS HANDBOOK

Internal :
External
:
Approvals
Name
App.
G.CONSONNI
A.FUMAGALLI
Name
App.
WARNING FOR A-UNITS OTHER THAN A-ITALY
Labels are done according to A-Italy binder format.

Source files:ALICE 6.10 ARCHIVED BY GAPI 3.9.1
PDF file retrieved from PD1 must be opened with ACROBAT Reader Version 4.0 at least.
957.207.022 A
3DB 02838 AAAA
Ed.04
9600LSY Rel.1.0
STM 1/0 Long Haul Digital Radio Relay System
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
RELEASED
957.207.022 TQZZA

4
2/ 4
9600LSY Rel.1.0


957.207.022 A Ed.04
3DB 02838 AAAA Ed.04
VOL.1/1
9600LSY Rel.1.0
957.207.022 A Ed.04
VOL.1/1
9600LSY Rel.1.0
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
1AA 00014 0004 (9007) A4 ALICE 04.10
957.207.022 A Ed.04
ED
04
VOL.1/1
RELEASED
957.207.022 TQZZA

4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
04
RELEASED
957.207.022 TQZZA
4/ 4
Craft Terminal Operators Handbook
Alcatel 9600LSY
STM1/0 Long Haul Digital Radio Relay System
9600LSY Rel.1.0
SWP REG. 9600LSY R.1.0
957.207.022 A Ed.04
Documentation set for 9600LSY/LHR Rel.1.0

ANV P/N
Factory P/N
Handbook
9600LSY/LHR Rel.1.0 & 2.0 Technical Handbook
3DB 02839 AAAA

955.203.292 Q
9600LSY/LHR Rel.1.0 & 2.0 Installation Handbook
3DB 02840 AAAA

955.203.302 S
9600LSY/LHR Rel.1.0 & 2.0 Lineup Guide
3DB 02841 AAAA

955.203.312 K
Interference investigation procedure
3DB 04165 EAAA

955.203.374 Z
9600LSY Rel.1.0 CT Operators Handbook SWP 1.0
3DB 02838 AAAA

957.207.022 A
1320CT Version 1.3.x Basic Operators Handbook
3AL 79186 AAAA

957.130.542 E
1330AS Rel.5.0 Operators Handbook
3AL 71079 AAAA

957.130.442 A
ELM Rel.5.0 Operators Handbook
3AL 71081 AAAA

957.130.462 E
this
Handbook
When supplied on paper, this handbook is divided by registers, for an easier access to the information
herein contained:
CONTENTS
REGISTER
GENERAL TABLE OF CONTENTS

SECTION 1: INTRODUCTION
SECTION 2: LHR NE MANAGEMENT
SECTION 3: LHR NE MAINTENANCE
SECTION 4: SIBDL
957.207.022 A Ed.04


This handbook is composed by several sections.
At the beginning of each section numbering of pages, chapters, figures and tables restarts from
1.
Cross references (ex. see figure 3 on page 45) are always inside the section where you are,
and are referred to the section pages.
This General Table Of Contents is relevant to the whole handbook. At the beginning of each
section, you can find:
a more detailed Table Of Contents, specific for the section
the List of Figures and Tables, specific for the section.
SECTION 1: INTRODUCTION
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAFETYEMCESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
2 ALCATEL SOFTWARE PRODUCTS AND LICENCES DELIVERED TO THE CUSTOMER . . .

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
04
020722
S402071501
03
020524
S402040401
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
04
957.207.022 A
3DB 02838 AA AA
6
1/ 6
1AA 00014 0004 (9007) A4 ALICE 04.10
31
32
3 SWP ADDITIONAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 SWP REG. 9600LSY R.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
5 ALLOCATION OF EQUIPMENT AND CRAFT TERMINAL SOFTWARE . . . . . . . . . . . . . . . . . . .

5.1 EquipmentOperator interfaces and local software allocation . . . . . . . . . . . . . . . . . . . . .
5.2 OperatorEquipment Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
57
6 GENERAL ON SOFTWARE INSTALLATION AND MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . .

6.1 Common situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Troubleshooting situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 SW download with MIB reset on the Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
61
62
63
7 HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
8 SWP INSTALLATION ON A NEW SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 PC hardware characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Operator skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Summary of SW installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 SWP loading in PC WINDOWSNT environment (offline mode) . . . . . . . . . . . . . . . . . . .
8.5 SW download toward NE (online mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 Configuration data definition and save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
65
65
65
66
69
70
70
9 NEW SWP VERSION INSTALLATION (SAME SWP RELEASE) . . . . . . . . . . . . . . . . . . . . . . . .
71
10 SWP UPGRADING FROM A PREVIOUS SWP RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
11 ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK . . . .

11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Certified modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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

2.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Software licence list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10


1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
12
14
2 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 LHR view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Introduction to the LHR menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
17
3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
27
4 NE MANAGEMENT GENERAL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 NE Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
29
31
33
5 COMMUNICATION AND ROUTING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Overview on Communication and Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Communication and routing views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Reachable Address Prefixes Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9 Manual ES Adjacencies table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
9 RADIO PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Overall RPS structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
101
10 WAY SIDE TRAFFIC AND SERVICE CHANNELS PROTECTION MANAGEMENT . . . . . . . .

10.1 Overall structure of WST and Service Channels protection . . . . . . . . . . . . . . . . . . . . . .
10.2 RFCOH Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115
115
116
ED
04
957.207.022 A
3DB 02838 AA AA
6
3/ 6
1AA 00014 0004 (9007) A4 ALICE 04.10
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
14 EXTERNAL INPUT AND OUTPUT POINT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Displaying external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 External Point configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
183
186
15 ALARMS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
189
194
196
16 EVENT LOG MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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

10.3 RFCOH Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.4 RFCOH Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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
19 SYSTEM SOFTWARE OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3 Channels and relation between boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4 Functional partitioning of the management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 Equipment management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6 Transmission management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.7 Radio management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.9 Radio Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.10 Overhead management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.11 Radio Overhead management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.12 Connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.13 Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.14 Communication and Routing management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.15 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.16 Support management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.17 Test management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
225
226
227
227
228
229
248
249
251
252
253
256
257
258
258
258
258
258
1AA 00014 0004 (9007) A4 ALICE 04.10

1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
4
4
2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 MAINTENANCE OF THE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 PROBLEMS WITH CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Purpose of this procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Troubleshooting by means of the Craft Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
4
4
2 SIBDL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 DOWNLOAD WITH SIBDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
04
957.207.022 A
3DB 02838 AA AA
6
6/ 6

SECTION 4: SIBDL

TABLE OF CONTENTS
HANDBOOK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAFETYEMCESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.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
2 ALCATEL SOFTWARE PRODUCTS AND LICENCES DELIVERED TO THE CUSTOMER . . .

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Software licence list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
31
32
3 SWP ADDITIONAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 SWP REG. 9600LSY R.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
33
33
04
020722
S402071501
03
020524
S402040401
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
1 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
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
5 ALLOCATION OF EQUIPMENT AND CRAFT TERMINAL SOFTWARE . . . . . . . . . . . . . . . . . . .

5.1 EquipmentOperator interfaces and local software allocation . . . . . . . . . . . . . . . . . . . . .
5.1.1 LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 OperatorEquipment Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 WMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
53
57
58
6 GENERAL ON SOFTWARE INSTALLATION AND MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . .

6.1 Common situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Troubleshooting situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 SW download with MIB reset on the Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
61
62
63
7 HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
8 SWP INSTALLATION ON A NEW SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 PC hardware characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Operator skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Summary of SW installation phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 SWP loading in PC WINDOWSNT environment (offline mode) . . . . . . . . . . . . . . . . . . .
8.4.1 Installation of 1320CT + NE software from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Installation of SIBDL program from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.3 End of SW installation from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4 Craft Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.5 NE Profile management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.6 NE software downloading preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 SW download toward NE (online mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.1 Dipswitch check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.2 Warning about ANTP (Alcatel Network Time Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.3 LHR SW download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 Configuration data definition and save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
65
65
65
66
66
67
67
67
67
68
69
69
69
69
70
70
9 NEW SWP VERSION INSTALLATION (SAME SWP RELEASE) . . . . . . . . . . . . . . . . . . . . . . . .
71
10 SWP UPGRADING FROM A PREVIOUS SWP RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
11 ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK . . . .

11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Certified modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
1AA 00014 0004 (9007) A4 ALICE 04.10

11.4 Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.4.1 Sportster Flash Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4.2 TD32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10
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

LIST OF FIGURES AND TABLES

HANDBOOK GUIDE
1AA 00014 0004 (9007) A4 ALICE 04.10
SECTION CONTENT
ED
PAGE
PRELIMINARY INFORMATION
QUICK GUIDE
SAFETYEMCESD NORMS AND EQUIPMENT LABELLING
Chapter 1 Document 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
ED
1)
Service Personnel
Installation and service must be carried out by authorized people having appropriate technical
training and experience necessary to be aware of hazardous operations during installation and
service and of measures to avoid any danger to them, to any other people and to the equipment.
2)
Access to the Equipment

Access to the Equipment in use must be restricted to Service Personnel only.
3)
Safety norms
Recommended safety norms are not indicated in this manual, but in 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.
Service Personnel skill

Service Personnel must have been an adequate technical training on telecommunications and in
particular on the equipment this handbook refers to.
Reading this handbook and the associated handbooks indicated in chapter 12 on page 83 is usually
not enough to properly install, operate and maintain equipment.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
6 / 96

a)
QUICK GUIDE
N.B.
In the documentation on CDROM, this table represent hyperlinks to the referenced parts.
Tab. 1. Quick guide

If you need immediate operative information on how to:
GENERAL TOPICS
get information on system
documentation
read chapter 12 on page 83 of this handbook
have a very short description of the

system from the hardware point of
view
read pages 40 thru 44 of this section
have the description of the system

from the software point of view
read chapter System Software overview in SECTION 2

LHR MANAGEMENT
logically configure a station (or

change its configuration) and
logically setup connections
get LHR Technical Handbook (Ref.[A] on page 84) and read

its QUICK GUIDE (same topic) (N.B.1)
logically provision equipment boards
read pages 45 thru 50 of this section
getting item P/Ns

GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE

get information on safety, EMC,
ESD norms and equipment labelling
get operative information regarding
the units in IDU shelf (connectors,
leds, buttons)
read page 9 of this section

carry out units hardware setting
1AA 00014 0004 (9007) A4 ALICE 04.10
INSTALLATION AND COMMISSIONING

physically install and cable the
equipment hardware
get LHR Installation Handbook (Ref.[B] on page 84) and

proceed as specified by it
install SWP (first time) on ECT and

equipment
proceed as specified in chapter 8 on page 65 of this section
commission equipment
get LHR Lineup Guide (Ref.[C] on page 84) and proceed as

specified by it
update ECT and equipment with a

newer SWP version (same SWP
release)
update ECT and equipment with a

newer SWP release
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:
ECT SOFTWARE USAGE FOR EQUIPMENT SW MANAGEMENT

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

read its paragraph Document Structure, and then search the
information according to the listed topics.
access the Events Log file

use of the Performance Monitoring
functionalities
set/modify the operator profiles
(username + password)
read para.8.4.5 on page 67 of this section

MAINTENANCE
provision and manage spare parts

carry out routine maintenance

get LHR Technical Handbook (Ref.[A] on page 84) , go to its
section
MAINTENANCE,
paragraph
Corrective
Maintenance and proceed as specified; in any case, such
paragraph will usually lead to the SECTION 3 NE
MAINTENANCE of this handbook.
carry out corrective maintenance

Alternatively, access directly SECTION 3 NE
MAINTENANCE of this handbook and proceed as specified;
if a board must be replaced, you will be led to the use of
paragraph Unit Replacement Procedures of LHR
Technical Handbook for the correct replacing procedures.
(N.B.2)
1AA 00014 0004 (9007) A4 ALICE 04.10
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
Paragraph Unit Replacement Procedures in LHR Technical Handbook is available starting

from its ED.02.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
8 / 96
SAFETYEMCESD NORMS AND EQUIPMENT LABELLING

a)
Please refer to 9600LSY/LHR Technical Handbook to obtain details regarding following information:
Compliance with European norms
Safety rules:
TOPIC
WARNING LABEL ON EQUIPMENT
General rules
Dangerous Electrical Voltages
Harmful optical signals
Risk of explosion
Moving mechanical parts
Heatradiating mechanical parts

Microwave radiations
Equipment protection against electrostatic discharges:

TOPIC
WARNING LABEL ON EQUIPMENT
Device sensitive to electrostatic discharges
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
ED
Electromagnetic Compatibility (EMC norms)
Other Labels affixed to the Equipment
Identical or similar information on Personal Computer, WorkStation etc., other than ALCATELs,
loaded with software applications described in this Handbook, is supplied in the Constructors
technical documentation.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
9 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
10 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10

1 DOCUMENT GUIDE
1.1 Introduction
This chapter contains all information regarding this handbook is organized as follows:
Handbook applicability
on page 12
Purpose of the handbook
on page 13
Handbook structure
on page 14
Handbook history
on page 16
Document history
on page 18
Acronyms and abbreviations
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
3DB 00581 AAAA
522.171.110
9647LSY
(4.7 GHz)
1.00.00
3DB 00584 AAAA
522.171.210
9662LSY
(6.2 GHz)
1.00.00
3DB 00587 AAAA
522.171.310
9667LSY
(6.7 GHz)
1.00.00
3DB 00590 AAAA
522.171.410
9674LSY
(7 GHz)
1.00.00
3DB 00593 AAAA
522.171.510
9681LSY
(8 GHz)
1.00.00
3DB 00596 AAAA
522.171.610
9610LSY
(10 GHz)
1.00.00
3DB 03936 AAAA
522.171.910
9611LSY
(11 GHz)
1.00.00
3DB 00599 AAAA
522.171.710
9613LSY
(13 GHz)
1.00.00
3DB 02270 AAAA
522.171.810
SWP Release
NE
SWP ANV &

FACTORY P/N
SWP Version
(N.B.)
LHR
3DB 03179 AAAA

415.201.006 E
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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

1.2 Handbook applicability

1.3 Purpose of the handbook

This handbook belongs to the Customer Documentation set envisaged for the equipment specified in para.
1.2 on page 12.
Please refer to chapter 12 on page 83 to have the list and description of such Customer Documentation
set.
This handbook describes the operation and maintenance activities the operators can carry out according
the specific software application(s) referred to in this handbook (see para. 1.2 on page 12).
This handbook must be used together with the associated Technical Handbook and does not replicate
information contained into it.
In particular, all cautions relevant to safety on rules for EMC and ESD, as well as warnings regarding
operations that may cause damages to the equipment, are not duplicated here, but must be retrieved from
the Technical Handbook.
When using this handbook, it is assumed that the Operators know:
the structure (hardware composition) and all the possible operating modes of the equipment
(product-release) that this handbook refers to.
how to use a PC and the Windows environment applications
Before accessing other sections of this handbook, read completely this section in order to have information
on:
SWP P/Ns and composition
how to access the other sections of this handbook according to the SWP type (if more than one
envisaged)
how to manage Craft Terminal SW and Equipment SW for new installations or for upgrading previous
installation to the new SW version.
how to make ECTequipment remote connection on Public Switched Telephone Network.
The document that should be read before starting this document is:
9600LSY/LHR Rel. 1.0 & 2.0 Technical Handbook

N.B.
In any case, the Technical Handbook must be always available to the Operator in charge
of the equipment software management, as it contains information and documents that are
used in the procedures described in this manual (e.g. the hardware setting documents, the
unit replacement procedures (N.B.), etc.).
N.B.
Paragraph Unit Replacement Procedures is available starting from ED.02 of
9600LSY/LHR Technical Handbook.
Reading the following manual:
1AA 00014 0004 (9007) A4 ALICE 04.10
1320CT Basic Operators 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
1.4 Handbook structure
SECTION 1: INTRODUCTION (this section)

This section comprehends the following parts:
HANDBOOK GUIDE (this part)

It contains all information regarding this handbook
This part includes the following parts:
1AA 00014 0004 (9007) A4 ALICE 04.10
Quick Guide
It allows to access immediately the most frequently needed operative pieces of information
contained in this handbook and in other related handbooks.
Chapter 1 Document guide (this chapter)

This chapter contains all information regarding this handbook (purpose, applicability,
history, abbreviation list, glossary).
SWP DESCRIPTION
This part lists and describes the Software Packages this Handbook refers to, and includes the
following chapters:
ED
Chapter 2 Alcatel Software Products and Licences delivered to Customer

This chapter gives commercial information regarding the Software Packages this
handbook refers to, i.e. the SWP and Software Licences P/Ns.
Chapter 3 SWP additional information

This chapter gives operative information regarding the Software Packages this handbook
refers to: requirements (PC and equipment Firmware), SW Package Identification, SW
Package Components, ECT SW SubComponents, NE MIB Compatibility and
Softwaredependent DipSwitches setting.
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
Chapter 4 System overview

This chapter replicates some information still present in the 9600LSY Technical
Handbook, that can be useful as refresh for the Operator in charge of the equipment
software management.
Chapter 5 Allocation of equipment and Craft Terminal Software

This chapter presents the Equipment from a software point of view, not dealing with the
detailed equipment software functionalities (that are entrusted to the other sections of this
handbook or to other associated manuals), but pointing out the software allocation and the
general software management rules (installation, download, equipment data backup and
restore), that the Operator should always mind when operates on the equipment software.
Chapter 6 General on Software installation and management

This chapter introduces the basic information regarding the software management, with
particular emphasis on SWP version and release upgrading situations and special
troubleshooting situations.
Chapter 7 Hardware installation

A reference to the specific handbook.
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
14 / 96

Information in this handbook is divided into the following main sections:
1AA 00014 0004 (9007) A4 ALICE 04.10

Chapter 8 SWP installation of a new system

This chapter details all phases necessary to install for the first time a SWP in the PC
environment as well as in the equipment environment.
Chapter 9 Upgrading to a newer SWP version (same SWP release)

This chapter details all phases necessary to install a new SWP version in the PC
Chapter 10 SWP upgrading from a previous SWP release

This chapter details all phases necessary to install a new SWP release in the PC
APPENDICES
In this part some additional information and instructions are given.
This part includes the following chapters:
Chapter 11 Remote connection via public switched telephone network

This chapter explains the operations necessary to allow the remote connection to the
FInterface, from a local PC configurated as ECT, through a switched telephone line of the
standard Public Telephone Network.
Chapter 12 Documentation guide

This chapter contains all information regarding the Customer Documentation, in particular
the list of the handbooks the Operators should have in order to carry out the required
operations.

In this section, the description of the menu structure and of all the LHR NE functionalities available
in the Craft Terminal is given. This section is organized in several chapters grouped according to the
following scheme:
General information
Equipment configuration management
Setting of parameters for maintenance
Events Log and Performance Monitoring management
Software management
Appendices
Please read chapter Document guide at beginning of SECTION 2: LHR NE MANAGEMENT for a
more detailed guide.

In this section the description of the LHR NE troubleshooting based on the use of the Craft Terminal
is given.
Please read chapter Document guide at beginning of SECTION 3: LHR NE MAINTENANCE for
a more detailed guide.
SECTION 4: SIBDL MANUAL

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 explained in part INSTALLATION of this section.
Please read chapter Document guide at beginning of SECTION 4: SIBDL MANUAL MANUAL 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
REGISTER AND SECTION TITLE
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
1.5.1 Notes on Ed.01Aproposal

Ed.01A issued on November 9, 2001 is the first neither released nor validated version of the handbook.
1.5.2 Notes on Ed.01
Ed.01 issued on January 11, 2002 is the first officially released and validated version of the handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 System overview in Section 1 INTRODUCTION
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

1.5 Handbook history


Ed.03 issued on May 24, 2002 has been done to align the handbook to the SWP Version 1.0.9. New
features and specific modifications introduced by this Version are the following:
Compatibility with Windows 2000 (see para.3.1.1 on page 33 in this section)
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
1.6.1 List of the editions and modified parts

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. 3. indicates the handbook parts new and modified with respect to the previous edition.
Legend
n
m
blank
= new part
= modified part
= part unchanged
Tab. 3. Document history

DOCUMENT EDITION
HANDBOOK GUIDE
1
02
03
04
Document guide
SWP DESCRIPTION
Alcatel software products and licences delivered to the Customer
SWP additional information
System overview
Allocation of equipment and Craft Terminal software
General on software installation and management
Hardware installation
SWP installation on a new system
New SWP version installation (same SWP release)
10 SWP upgrading from a previous SWP release
APPENDICES
11
ED
ECTEquipment connection via public switched telephone

network
12 Documentation guide
04
05
INSTALLATION
1AA 00014 0004 (9007) A4 ALICE 04.10
01
m
m
m
n
n
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
18 / 96

1.6 Document history
1.7 Acronyms and abbreviations

ACD: Access Control Domain

ADM: Add/Drop Multiplexer
AIS: Alarm Indication Signal
ALR: Automatic Laser Restart
ALS: Automatic Laser Shutdown
ANTP: Alcatel Network Time Protocol
APS: Automatic Protection Switching
ASAP: Alarm Severity Assignment Profile
ATM: Asynchronous Transfer Mode
ATPC: Automatic Transmit Power Control
AU: Administrative Unit
AUG: Administrative Unit Group
AVC: Attribute Value Change
BBE: Background Block Error
BER: Bit Error Rate
BIP: Bit Interleaved Parity
CMI: Coded Mark Inversion
CRC: Cyclic Redundancy Check
CRU: Clock Reference Unit
CSES: Consecutive Severely Errored Second
CTP: Connection Termination Point
CDROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee
CT: Craft Terminal
DCC: Data Communication Channel
DCN: Data Communications Network
1AA 00014 0004 (9007) A4 ALICE 04.10
DEM: DEModulator
EB: Errored Block
EC: Equipment Controller
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
19 / 96
ECT: Equipment Craft Terminal

EFD: Event Forwarding Discriminator

ECC: Embedded Communication Channels
EML: Element Management Layer
EOW: Engineering Order Wire
EPS: Equipment Protection Switching
ES: Errored Second
ES: End System
ETSI: European Telecommunication Standard Institute
EW: Early Warning
FAD: Functional Access Domain
GA: General Alarm
FEBBE: Far End Background Block Error
FEBE: Far End Block Error
FEES: Far End Errored Second
FESES: Far End Severely Errored Second
FERF: Far End Receive Failure
Gbit/s: Gigabits per second
GNE: Gateway Network Element
HCS: Higher order Connection Supervision
HBER: High Bit Error Rate
HMI: Human Machine Interface
HO: Higher Order
HOA: Higher Order Assembler
HOI: Higher Order Interface
HP: High Power
HPA: Higher Order Path Adaption
1AA 00014 0004 (9007) A4 ALICE 04.10
HPC: Higher Order Path Connection

HPOM: Higher Order Path Overhead Monitor
HPT: Higher Order Path Termination
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
20 / 96
HS: High Speed

HSUT: Higher Order Supervisory Unequipped Termination

HTCA: Higher Order Tandem Connection Adaption
HTCM: Higher Order Tandem Connection Monitor
HTCT: Higher Order Tandem Connection Termination
HUG: Higher Order Path Unequipped Generator
HST: Hot STandby
ID: Identifier
IDU: InDoor Unit
ISO: International Standards Organization
IEEE: Institute of Electrical and Electronics Engineers
IM: Information Manager
IP: Input Port
IS: Intermediate System
Kbit/s: Kilobits per second
LAN: Local Area Network
LAPD: Link Access Procedure on Dchannel
LBER: Low Bit Error Rate
LCS: Lower Order Connection Supervision
LHR: Long Haul Regenerator
LO: Local Oscillator
LOF: Loss Of Frame
LOI: Lower Order Interface
LOP: Loss Of Pointer
LOS: Loss Of Signal
LPA: Lower Order Path Adaptation
LPC: Lower Order Path Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
LPOM: Lower Order Path Overhead Monitor

LPT: Lower Order Path Termination
LSUT: Lower Order Supervisory Unequipped Termination
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
21 / 96
LTCA: Lower Order Tandem Connection Adaption

LTCM: Lower Order Tandem Connection Monitor

LTCT: Lower Order Tandem Connection Termination
LVC: Lower Order Virtual Container
LS: Low Speed
LUG: Lower Order Unequipped Generator
LVDS: Low Voltage Differential Signals
MAC: Media Access Control
MESA: Manual ES Adjacencies
Mbit/s: Megabits per seconds
MIB: Management Information Base
MOD: Modulator
MS: Multiplex Section
MSA: Multiplex Section Adaption
MSOH: Multiplex Section OverHead
MSP: Multiplex Section Protection
MST: Multiplex Section Termination
MSp: Manual Switch to protecting channel
MSw: Manual Switch to working channel
NAD: Network Access Domain
NAP: Network Access Point
NE: Network Element
NML: Network Management Layer
NTP: Network Time Protocol
OBPS: On Board Power Supply
ODU: OutDoor Unit
OH: OverHead
1AA 00014 0004 (9007) A4 ALICE 04.10
OHA: OverHead Access

OP: Output Port
OS: Operation System
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
22 / 96
PDH: Plesiochronous Digital Hierarchy

PI: Physical Interface

PJE: Pointer Justification Events
PLL: Phase Locked Loop
POH: Path OverHead
PPI: PDH Physical Interface
PPS:Path Protection Switch
PSU: Power Supply Unit
QOS: Quality Of Service
RAP: Reachable Address Prefixes
RC: Radio Controller
RDI: Remote Defect Indication
RECT: Remote Equipment Craft Terminal
REI: Remote Error Indication
RPS: Radio Protection Switching
RRA: Radio Regenerator Adaptation
RMD: Radio Regenerator adaptation MoDem
RPS: Radio Protection Switching
RS: Regenerator Section
RSOH: Regenerator Section OverHead
RSPI: Radio Synchronous Physical Interface
RST: Regenerator Section Termination
SAM: Service Auxiliary Management
SC: Service Channel
SD: Signal Degrade
SDH: Synchronous Digital Hierarchy
SEC: SDH Equipment Clock
1AA 00014 0004 (9007) A4 ALICE 04.10
SES: Severely Errored Second

SF: Signal Fail
SNCP: Sub Network Connection Protection
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
23 / 96
SOH: Section OverHead

SPI: SDH Physical Interface

SSF: Server Signal Fail
SSU: Synchronization Supply Unit
STM1: Synchronous Transport Module 1
SWP: Software Package
TCA: Threshold Crossing Alarm
TM: Terminal Multiplexer
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
TPH: TelePHone
TSF: Trail Server Failure
TTF: Transport Terminal Function
TTP: Trail Termination Point
UAS: UnAvailable Second
UAT: UnAvailable Time
UHM: Urban Haul split mount terminal Multiplexer
UHMC: Urban Haul split mount terminal Multiplexer Compact
UHR: Urban Haul split mount terminal Regenerator
UHRC: Urban Haul split mount terminal Regenerator Compact
UPA: UnAvailable Path Alarm
URU: Underlying Resource UnAvailable
USM: User Service Manager
VCn: Virtual Container n
VCO: Voltage Controlled Oscillator
XPIC: Cross Polar Interference Canceller
1AA 00014 0004 (9007) A4 ALICE 04.10
XC: CrossConnection
WST: Way Side Traffic
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
24 / 96

1.8 Glossary of terms

Acknowledgment:
When an alarm is taken into account by the application, the operator has to acknowledge it to point out
that he has seen it and that he will react in the right way. During alarm configuration it is possible to set
a maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear
has to be acknowledged.
Administrator:
A user who has access rights to all the Management Domains of the Craft Terminal product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end.
Alarm Severity Assignment Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Compact Disk Read Only Memory:
Data saving support from which the information can only be read. Is useful for stocking data due to its
available memory space.
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Crossconnection
CrossConnections provide the network with the Routing Capabilities, this is the possibility of routing one
signal to a particular destination.
Digital Communication network:
Communication Network in which the transmission of data is done in a digitized format.
Embedded Communication Channel:
Communication channel used in conjunction with packet commuting networks (X25) to manage distant
SDH networks. These communication channels are related to the QECC* protocols.
Element Management Layer:
This application is responsible for the configuration and management of Network Elements.
1AA 00014 0004 (9007) A4 ALICE 04.10
Equipment Protection Switching:

Used to provide protection for cards within an equipment to protect traffic in the event of card failure.
Filter:
They are related to the alarms or events generated on an NE or internally within the OS itself. They can
be configured by an operator to reject specified types of notifications and limit the processing that is applied
to them.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
25 / 96
Functional Access Domain:

It defines the range of functions which are available to a specified user.
Gigabits per second:
Unit that corresponds to the transmission of 109 bits every second.
Gateway Network Element:
It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface.
To do this it uses a QB3* interface and performs the conversion QB3* QECC*.
Human Machine Interface:
It is the graphical user interface application through which the operators interact with the system.
History Report:
This function enables operators to get information concerning performances, security or alarms on entities
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITUT (International Telecommunication
Union).
Kilobits per second:
Unit that correspond to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Media Access Control Address:
Represents the Level 2 address for Local Area Networks.
Megabits per second:
Unit that corresponds to the transmission of 106 bits every second.
1AA 00014 0004 (9007) A4 ALICE 04.10
Network Access Domain:

Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user
can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.
Network Management Level:
Designates the management functions performed on networks elements assembled in a network.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
User Service Manager:

These are presentation processes used by the Craft Terminal to manage the Human Machine Interface
and facilitate the interaction with the product.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file
is full.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
27 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
28 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10
SWP DESCRIPTION
ED
SECTION CONTENT
PAGE
Chapter 2 Alcatel software products and licences delivered to the Customer
31
Chapter 3 SWP additional information
33
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
29 / 96
The symbol
Handbook.
points out references to Other Handbooks or to other sections of this same
In the documentation on CDROM they represent hyperlinks to the handbooks referenced to.
1AA 00014 0004 (9007) A4 ALICE 04.10
Referenced handbook P/Ns are given in chapter 12 on page 83.
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 ALCATEL SOFTWARE PRODUCTS AND LICENCES DELIVERED TO THE

CUSTOMER
This chapter gives commercial information regarding the Software Packages this handbook refers to, i.e.
the SWP and Software Licences P/Ns.
2.1 General
The software products are distributed by Alcatel in a CDROM.
In this CDROM are contained:
Software packages for NE management by means of the craft terminal
Software package of the NE, to be installed in the NE or update the NE (by means of download
function)
The software package used for management allows the dialogue between craft terminal and NE, to
realize all the functions of the NE and 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.
2.2 Software product list and part numbers

Every Software Product is identified by a denomination and a part number and is distributed by a CDROM
with the same identifiers, listed on the following table:
Tab. 4. Software products part numbers
Name
SWP REG. 9600LSY R.1.0
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
04
ANV Part Number
Factory
Part Number
N.B.
3DB 03179 AAAA
415.201.006 E
Software Package associated to LCT or RCT SW Licence ( For LHR NEs).

See para.2.3 on page 32 for additional information.
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
31 / 96
2.3 Software licence list and part numbers
Tab. 5. Software licence part numbers
ANV Part Number
Factory
Part Number
SWLA LHR Rel. 1.0 LICENCE FEE
3DB 03027 AAAA
700.500.008 J
SWLB LHR Rel. 1.0 LICENCE FEE
3DB 03028 AAAA
700.500.009 K
SWLC LHR Rel. 1.0 LICENCE FEE
3DB 03029 AAAA
700.500.0010 F
SWLA LHM Rel. 1.0 LICENCE FEE
3DB 03030 AAAA
700.500.011 U
SWLB LHM Rel. 1.0 LICENCE FEE
3DB 03031 AAAA
700.500.012 V
SWLC LHM Rel. 1.0 LICENCE FEE
3DB 03032 AAAA
700.500.013 W
SWLLCT ( Local Craft Terminal )

9600LSY Rel. 1.0 LICENCE FEE
3DB 03033 AAAA
700.500.014 X
Name
N.B.
3
SWLRCT ( Remote Craft Terminal )
9600LSY Rel 1.0 LICENCE FEE
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
04
3DB 03034 AAAA
700.500.015 Y
Licence alternative for Network Element software features:
SWLA: software licence A type for regenerator configuration
SWLB: software licence B type for regenerator configuration
SWLC: software licence C type for regenerator configuration
Licence alternative for Network Element software features:
SWLA: software licence A type for WMSN configuration
SWLB: software licence B type for WMSN configuration
SWLC: software licence C type for WMSN configuration
Licence alternative for Craft Terminal software features:
SWLLCT: local Craft Terminal functionality
SWLRCT: remote Craft Terminal functionality.
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.

3 SWP ADDITIONAL INFORMATION

This chapter gives operative information regarding the Software Packages this handbook refers to:
requirements (PC and equipment Firmware), SW Package Identification, SW Package Components, ECT
SW SubComponents, NE MIB Compatibility and Softwaredependent DipSwitches setting.
Please refer to para.12.2.2 on page 88 for the meaning of SWP Release, Version and Patch Level.
With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 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.
3.1 SWP REG. 9600LSY R.1.0

3.1.1 Requirements
For ECT installation it is necessary a PC with the requirement hereafter described.
Basic requirements:
CPU
RAM
Hard Disk
Display size
Display resolution
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
3.1.2 SW Package Identification

Identification
Version
Date
SWP REG. 9600LSY R1.0
V1.0.10
July 18th, 2002
3.1.3 SW Package Components

Name
Description
Version
SW Package for 2G Radio Regenerator Long Haul

Equipments
V1.0.10
SWCECT9600LSY_V20
Equipment Craft Terminal SW Component
V2.0.21
SWCEC9600LSY_V20
Equipment Controller SW Component
V2.0.14
SWCRC9600LSY_V20
Radio Controller SW Component
V2.0.22
SWCFD9600LSY_V10
File Descriptor for SW Download Component
V1.0.10
SWP REG. 9600LSY R1.0
3.1.4 ECT SW SubComponents

Name
JRE
Version
V1.3
Description
Java 2 Run Time Environment
Q3CTP
V1.5.1.6
Equipment Craft Terminal Base Platform
LLMAN
V1.2.1
Lower Layers Manager
USMMWCOMMON
V2.0.21
User Service Manager Common Part for all Q3 MW Nes
USMMWREGLSY
V1.0.10
User Service Manager Specific Part for REG. LSY Nes
3.1.5 NE MIB Compatibility
1AA 00014 0004 (9007) A4 ALICE 04.10
NE MIB on EC is compatible with previous version V1.0.8 and 1.0.9.
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.

3.1.6 DipSwitches setting

On main board System Controller units main board (see Fig. 13. on page 56) are present two
dipswitches, I1 and I4, used to identify the main HW characteristics and equipment type.
For the position of these dipswitches, see section:
UNIT HW PRESETTING of
9600LSY/LHR Technical Handbook
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
LHRC Long Haul indoor terminal Regenerator Compact
LHR Long Haul indoor terminal Regenerator
LHRR Long Haul indoor terminal Regenerator Repeater
1AA 00014 0004 (9007) A4 ALICE 04.10
DipSwitch I4 /45678 must be set to 1 (Open or Off).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
35 / 96
3.1.6.3 SLOTID field for LHR

According to following Tab. 7.

Tab. 7. ESC DipSwitch Bank I1 setting
SLOTID
I1 switches
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
1AA 00014 0004 (9007) A4 ALICE 04.10
DipSwitch I1 /78 must be set to 1 (Open or Off).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
36 / 96

INSTALLATION
1AA 00014 0004 (9007) A4 ALICE 04.10
SECTION CONTENT
ED
PAGE
Chapter 4 System overview
39
Chapter 5 Allocation of equipment and Craft Terminal software
53
Chapter 6 General on software installation and management
59
Chapter 7 Hardware installation
64
Chapter 8 SWP installation on a new system
65
Chapter 9 Upgrading to a newer SWP version (same SWP release)
71
Chapter 10 SWP upgrading from a previous SWP release
71
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
37 / 96
The symbol
Handbook.
points out references to Other Handbooks or to other sections of this same
In the documentation on CDROM they represent hyperlinks to the handbooks referenced to.
1AA 00014 0004 (9007) A4 ALICE 04.10
Referenced handbook P/Ns are given in chapter 12 on page 83.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
38 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10

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:
LHR System Configurations
on page 40
LHR system layout and equipping rules

including:
on page 41
System layout and hardware components
on page 41
Equipment provisioning
on page 45
ECT and RECT
on page 51
For further details, please refer to 9600LSY/LHR Technical Handbook.
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
In N+0 configurations, channels are without protection.

In N+1 configurations, channel 0 is always the standby channel.
In N+1 & Occasional configurations (also known as 1:N protection architecture), channel 0 carries the
occasional traffic, that is cut off whenever it becomes the recovery channel for any (faulty) of the protected
channels.
As indicated in Tab. 8. above, the WST configuration is independent from N+0 / N + 1 / 1:N system
configuration. 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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

4.1 LHR System Configurations

4.2 LHR system layout and equipping rules

4.2.1 System layout and hardware components
Fig. 1. herebelow shows the OPTINEX rack layout respectively in Regenerator and WMSN
configurations.
In the following, only information regarding Regenerator configuration is refreshed, in particular as far as
Base Band shelf, Transceiver shelf and Fans for RRA/MODEM shelf are concerned.
For further or other information, please refer to 9600USY/LHR Technical Handbook.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 1. Regenerator and WMSN station rack configuration
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
1AA 00014 0004 (9007) A4 ALICE 04.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

The functions performed in Base Band shelf are:

a)
RRA
Performs the following main functions :
STM1 bidirectional interface, electrical or optical selectable by means of interchangeable

plugins
Extraction/Insertion RSOH line side to/from Aux. Service Board
Hitless Switch functionality.

Just one unit has been developed for utilization with both STM1 and STM0 capacity.
Each RRA unit is equipped with an embedded STM1 electrical interface. As an option, a S 1.1
STM1 optical interface can be used instead. This optical interface is realized by a plugin unit that
can be installed in the RRA through the front panel.
b)
RRA Standby board

It is equipped only in slot 3 (see Fig. 2. on page 42) in N+1 (1:N )configurations.
The unit performs the same functionalities of RRA board but, moreover, the hitless switch circuits
(Tx/Rx distributors and a switching logic unit) are is installed on board and dedicated to the radio
section protection.
The protection supplied is N+1 type and it is also utilized in 1+1 configuration .
Only one RRA STBY has been developed for utilization with both STM1 and STM0 capacity.
c)
MD Modem unit
Performs the following main functions:
Terminal modulator
Terminal demodulator
XPIC
Baseband signal combiner

Two different 128 QAM modems have been developed, according to the two capacities that can be
transmitted:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED
SERV Service Unit

The Service board provides an external access to the auxiliary service channels, utilizing SUBD
connectors in the subrack connector area. Moreover the unit manages the ATPC functionality.
Service unit consents the terminal to transmit one WST 2 Mb/s service stream in Radio Frame
Complementary OverHead in protected way on channels x and y (that can be choosen among the
couples specified in Tab. 9. on page 40), and contains the logic switching unit. The WST interface
is present on the unit front panel. The accesses to the other WST service streams that can be
transmitted one for each channel in nonprotected way are in the connector area.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
43 / 96
SYSCO System Controller

The S.C. is devoted to the equipment management. It exchanges alarms, commands and
management information with the other units of the equipment and provides the following interfaces
for local and remote management:
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
QECC interface for remote management through DCC channels.
f)
Additional Housekeeping unit

This optional unit (equipped as depicted in Fig. 1. on page 41) increases by 18 the number of
Housekeeping inputs available with SYSCO board.
g)
PSU Power Supply

PSU units are grouped in 2units groups (i.e. PSU0+PSU1, PSU2+PSU3, ...). Each PSU pair
converts and then distributes, through the backpanel, power supply to the correspondent pair of
RRA, whereas each PSU board supplies only the associated MODEM board (i.e. PSU0 supplies only
MODEM0 board, etc) If not utilized, the P.S. slots are provided with a front plate cover.
Each P.S. gets the primary voltage from both batteries, connected in parallel.
The P. S. units supply the secondary power voltage to all the units starting from the primary voltage:
48 to 60 Vdc ( 20%);
The system can also be powered by batteries with different voltage: 24 Vdc ( 20%). In this case,
onpurpose designed DC/DC converters (in preparation) will have to be installed in the lower area
of the rack.
h)
PSF Battery filter

Two battery filters, located in the lower side positions of the subrack, supply the DC power to the
common units (System Controller, Service) in 1+1 protected way.
The functions performed in Transceiver shelf are:
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
4.2.2 Equipment provisioning

General equipping rules

According to Fig. 2. and Fig. 3. on page 42:
a)
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)
BASE BAND SHELF
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
Fig. 4. Layout of max 8 channels in single polarization configurations
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
Fig. 5. Layout of max 8 channels in double polarization configurations
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
Channel provisioning/expansion guideline

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
H (V)
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
(adding 1 RT on V pol)
(adding 1 RT on H pol)
2 4
V V
H
2
2
1
4
1
4
5
1AA 00014 0004 (9007) A4 ALICE 04.10
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 RT on H pol and
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.
1 3
4 2
3 1
V V
H H
H H
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 9. Expansion procedure with reused channels
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 RRA/MODEM is mandatory in all configurations
FAN shelf for 1650SMC is mandatory whenever the 1650SMC shelf is equipped.
FANS ASSEMBLED provisioning

The FANS SHELF contains one or two independent FANS ASSEMBLED units, as depicted in
following Fig. 10. :
FANSL
A
FANSL
B
Fig. 10. Fan shelf (slot numbering and board types)

The equipping rules for FANS assembled unit in Basebandshelf are depicted in Tab. 10. below:
Tab. 10. Equipping rules for FANS assembled unit in Basebandshelf
E=
NE =
equipped
not equipped
POLARIZATION
single polarization
(see Fig. 6. on page 47)
two antenna polarizations
CONFIGURATION
FANSLA
FANSLB
up to
2+1 / 3+0
NE
3+1 / 4+0
all
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
4.3 ECT and RECT

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:
SWP REG. 9600LSY for the Regenerator station
and, additionally, SWP 1650SMC for the WMSN station.

The Equipment Craft Terminal, connected to the F interface of the Equipment Controller, enable an
operator to perform locally the following Element Management functions:
Equipment Management
Transmission Management
Test management
External points management
Alarm (fault) management
Synchronization management
Radio Management
Performance Monitoring Management
Event log manager
Overhead Management
Connection Management
Software Management
Communication and Routing Management
Security Management
Support Management
1AA 00014 0004 (9007) A4 ALICE 04.10
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 features and limitations are briefly the following:

1)
The RECT function provides a remote login facility similar to those offered by an OS to manage
several configured NEs, included the local one.
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)
1AA 00014 0004 (9007) A4 ALICE 04.10
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.

5 ALLOCATION OF EQUIPMENT AND CRAFT TERMINAL SOFTWARE

5.1 EquipmentOperator interfaces and local software allocation
5.1.1 LHR
Following Fig. 11. , taken from 9600LSY/LHR Technical Handbook (as well as Fig. 15. page 58), sums
up main EquipmentOperator interfaces:
CMI 9
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 11. LHR system (N+1 / N+0)
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)
Local software allocation

Once the system has been configured and activated (as explained in following chapters), Equipment
and Craft Terminal must not necessarily be left connected, because equipment contains all the
software necessary for its working.
This equipments local software comprises programs and configuration data. Programs and data are
managed differently from each other:
1)
ESC: Equipment Controller SYSCO

Whole Equipment SW (programs and configuration data) is contained in the Flash Card housed
in SYSCO boards ESCON subunit (the Flash Card contains also the software (programs and
configuration data) relevant to the peripheral units, i.e., in the figure, SERVICE, RRAs,
MODEMs and RTs). See Fig. 13. and Fig. 14. on page 56.
This flash card is removable (i.e. replaceable), and the programs can be overwritten by a SW
download from CT (through F interface) or Network Management Operation System (through
Q interface) to SYSCO.
More precisely, the Flash Card contains two independent instances of the Equipment SW
programs (one active, the other standby) so that the above cited SW download is actually done
toward the standby instance, while equipment goes on working with the SW programs of the
active instance. Swapping between the two instances is done only under Operators request.
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)
Equipment Configuration Data
1AA 00014 0004 (9007) A4 ALICE 04.10
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
1AA 00014 0004 (9007) A4 ALICE 04.10
RT
SUPERVISOR UNIT
FLASH
EPROM
Fig. 12. Equipment main parts containing local SW (LHR)
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
55 / 96

Fig. 13. herebelow shows the System Controller assembly view

Fig. 14. herebelow shows the FLASH CARD profile and insertion direction
Subunit
ESCON
Flash Card
F INTERFACE
System Controller
main board
Fig. 13. System Controller assembly
TOP SIDE
INSERTION
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 14. FLASH CARD profile and insertion direction
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
56 / 96
5.2 OperatorEquipment Interaction

Local Operator can manage Equipment software programs and most configuration data
through the Equipment Craft Terminal 1320CT attached to F interface (see Fig. 12. on page
55 and Fig. 13. on page 56).
The Craft Terminal characteristics (computer configuration) are listed in chapter 3 on page 33.
The Craft Terminal is a project in charge of the local management of single network elements,
providing ITU compliant Information Model Interface to the Network Element.
Multiple NE management up to 32 Network element is possible obtaining a remote Craft
Terminal application.

1)
The general information of the Craft Terminal are presented in the:

1320CT Basic Craft Terminal Operators Handbook
that the operator have to read before this Handbook.
In this Handbook are described all the general description of use, navigation, rules, etc.,
common to all the NE using the same Craft Terminal.
Furthermore, the same handbook contains the detailed description of common operations as
Installation and common screens as Network Element Synthesis view.
The Network Element Synthesis view is the first view presented to the operator entering the
application.
Starting from this view it is possible login the NE and than enter the EMLUSM views.
This Operators Handbook deals with the EMLUSM views of the Craft Terminal, which directly
allows to manage the Network Element.
A detailed description of the LHRs EMLUSM screens is given in the dedicated Section of this
handbook:
LHR Ne Management
2)
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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

Fig. 15. sums up main EquipmentOperator interfaces in the WMSN configuration.

TR
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
Fig. 15. WMSN system (N+1 / N+0)

From the Infomodel point of view and consequently in any equipment operation and maintenance
operation, in all WMSN configurations takes always into account that LHR and 1650SMC are two different
Network Elements.
As depicted in Fig. 15. , in any WMSN configuration the standard Q and F interfaces (as well as those of
the service channels) are those provided by MUXs Equipment Controller. The dialogue between
Equipment Controllers of MUX and LHR (allowing regenerator SW management from OS or ECT attached
to MUXs Equipment Controller) is performed through the DCC channel of STM1 link existing between
MUX and LHR.
This is true for Equipment Craft Terminal standard applications, as well as for SIBDL application.
1AA 00014 0004 (9007) A4 ALICE 04.10
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

6 GENERAL ON SOFTWARE INSTALLATION AND MANAGEMENT

This chapter introduces the basic information regarding the software management, with particular
emphasis on SWP versions and release upgrading situations and special troubleshooting situations.
N.B.
Before reading this chapter, it is suggested to read (if not yet done) previous chapter 5 on page
53.
Fig. 16. depicts the main phases for SW management.

SWP
CDROM
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
1AA 00014 0004 (9007) A4 ALICE 04.10
RESTORE
Fig. 16. Software management main phases
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:
program management, i.e.:
(1) and (2) : SWP loading from CDROM to the Personal Computer, after which the PC
becomes and can be used as the Equipment Craft Terminal
(3) NE SWP downloading from ECT toward the NetworkElements Equipment Controller (EC)
(4) SW downloading from EC toward peripheral Supervisor Units (SU).
NE configuration data management:
(5) NE configuration data definition
(6) NE configuration data save in Equipment Craft Terminal (MIB backup)
(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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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

6.1 Common situations

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
running release < SWP release

A.B.c
A.B.c
patch levels unmeaningful
SWP
CDROM
D.E.f

5)
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
running release = SWP release
1AA 00014 0004 (9007) A4 ALICE 04.10
A.B.c
A.B.c
running version < SWP version
SWP
CDROM
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.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).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
61 / 96
6.2 Troubleshooting situations

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

or:
2)
NE not infactory configured
use the SW download through SIBDL program (refer to the specific section in this handbook):
SIBDL
b)
In the following situation:

3)
there are symptoms of MIB data corruption in the NE Flash Card
1AA 00014 0004 (9007) A4 ALICE 04.10
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)

6.3 SW download with MIB reset on the Flash Card

This is a special procedure that can be referred to by other parts of this handbook. Use it only if
specifically referenced.
a)
Perform a SW download as explained in chapter Software Management of section LHR Ne

Management in this manual, i.e. , after having loggedin the NE, according to the Craft Terminal
Men:
Download Init download
then, after about 2 hours, Commit , to select the version to be written on the Flash Card
b)
Extract the Equipment controller card SYSCO.

On SYSCOs subunit ESCON (see Fig. 13. on page 56) there is one 4switch DIPSwitch bank, all
normally set in off position. The switch 2 allows the reset of MIB.
For the position of these dipswitches, see section:
UNIT HW PRESETTING of
9600LSY/LHR Technical Handbook
c)
Set switch 2 to ON position.
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)
Configure the equipment data:
by Craft Terminal, with individual commands
or, always by Craft Terminal:
restoring MIB data base previously saved, as indicated in dedicated sections of this
handbook:
LHR Ne Management , chapter MIB management
1AA 00014 0004 (9007) A4 ALICE 04.10
and manually reconfiguring network configuration data not saved in MIB (ref. point 3 ) on
page 54).
h)
Switch off and (after 10 seconds) switch on equipment.
i)
Perform all necessary checks.
j)
Save Equipment Configuration Data as explained in para.8.7 point 2 ) on page 70.
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
63 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
9600LSY/LHR Installation Handbook
ED
04
957.207.022 A
7 HARDWARE INSTALLATION
Hardware installation must be done according to:
SC.1:INTRODUCTION
3DB 02838 AA AA
96
64 / 96

8 SWP INSTALLATION ON A NEW SYSTEM

This chapter details all phases necessary to install for the first time a SWP in the PC environment as well
as in the equipment environment.
N.B.
Before starting the installation procedures, it is suggested to give a look to previous chapters
5 on page 53 and 6 on page 59.
8.1 PC hardware characteristics

Refer to SWP DESCRIPTION (para.3.1.1 on page 33).
8.2 Operator skills

The operator shall be familiar with the use of personal computers in WINDOWSNT or WINDOWS 2000
environment, internally to which the Network Elements application software operates.
Furthermore, for a number of configuration applications, the operator shall be aware of some
specifications of the International Standard Organization (ISO) and of the standards applied to the
Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).
8.3 Summary of SW installation phases

The sequence of installation phases are as follows:
a)
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
SWP loading in PC WINDOWSNT environment (PC is disconnected from Equipment Controller):

1)
installation of 1320CT + NE software from SWP CDROM
2)
installation of SIBDL program from SWP CDROM
3)
end of SW installation from SWP CDROM
4)
Craft Terminal configuration
5)
NE Profile management
6)
NE software downloading preparation
SW download toward NE (PC is connected to Equipment Controller):

7)
dipswitch check
8)
warning about ANTP (Alcatel Network Time Protocol)
9)
LHR SW download
c)
Commissioning
d)
Configuration data definition and save
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
65 / 96
8.4.1 Installation of 1320CT + NE software from SWP CDROM

1)
Insert the SWP CDROM in the PCs CDROM unit:

a)
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)
the autoinstallation process continues with the installation of NE own Software

Package(s):
1)
d)
SWP REG. 9600LSY

that includes:
LHR Equipment Controller SW Components
LHR Radio Controller SW Components
LHR File Descriptor (for SW Download).
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)
when so requested by the installation procedure, confirm all default values.
1AA 00014 0004 (9007) A4 ALICE 04.10
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

8.4 SWP loading in PC WINDOWSNT environment (offline mode)

8.4.2 Installation of SIBDL program from SWP CDROM

Refer to chapter 5 for general information on SIBDL program (in particular point 5.2 2 ) on page 57 and
point 6.2 2 ) on page 62).
The SIBDL program is not automatically installed by the autoinstallation process described in para.8.4.1
(page 66).
The installation of SIBDL is detailed in the dedicated Section of this handbook:
SIBDL
N.B.
It is not mandatory to install SIBDL in this phase. You can postpone it when necessary (take into
account that you will need the SWP CDROM).
8.4.3 End of SW installation from SWP CDROM

Having reached this phase, you have finished the Software transfer from SWP CDROM to the PC
environment. Now, you can extract the SWP CDROM from the PCs CDROM unit.
8.4.4 Craft Terminal configuration

This procedure is necessary to configure the PC in order to manage the Network Elements and includes
the following types of configuration:
PC hostname
CT configuration
Communication Protocol (TCP/IP):
TCP/IP without a network card
TCP/IP with a network card
Switching between the two configurations
Serial Communication with the NE
Screen settings
In order to setup these configurations, refer to:
section INSTALLATION, chapter Craft Terminal Configuration
8.4.5 NE Profile management

This management allows to define the operator profiles (username + password) in order to access all the
Craft Terminal functionality or only limited parts of it.
In order to setup these configurations, refer to:
1AA 00014 0004 (9007) A4 ALICE 04.10

section GETTING STARTED, chapter Access to the main functionalities,
paragraph NE Profile management
N.B.
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.
Fig. 17. Selecting Software Administration
1AA 00014 0004 (9007) A4 ALICE 04.10
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>.
Fig. 18. Directory selection
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
68 / 96

8.4.6 NE software downloading preparation

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.
8.5 SW download toward NE (online mode)

8.5.1 Dipswitch check
If not yet done, verify that the setting of dipswitches is consistent with the equipment configuration. See
para.3.1.6 on page 35.
8.5.2 Warning about ANTP (Alcatel Network Time Protocol)

For ANTP description refer to:
1320CT Basic Craft Terminal Operators Handbook,
section EML Construction, chapter Using Craft Terminal Environment ,
paragraph ANTP Configuration
The ANTP default state is Enable Client. In this situation, when you connect the PC to the equipments
Finterface, start 1320CT program and execute the log in, the PC gets the time information from the
equipment. If this time information is incorrect, WindowsNT (that accepts years only in the range
19802023), could go into unexpected states.
In order to avoid problems, if you are not sure of the NE Network Time, it is suggested to disable the ANTP
function with the following operations, with the PC disconnected from the NE Network:
1)
activate ECT (1320CT x.x.x)
2)
activate ANTP configuration window ( CT Environment ANTP configuration )
3)
select option NOT Managed
4)
Confirm with Save and OK
After having connected to the NE Network, the Operator should decide what to do with ANTP (disabled,
Client, Server).
8.5.3 LHR SW download

1)
Through the suitable cable, connect the PC to F interface of SYSCO board
2)
Activate ECT (1320CT x.x.x)
3)
Execute the Login of LHR NE
4)
Perform the SW download, as explained in this manual:

LHR Ne Management, chapter Software Management
1AA 00014 0004 (9007) A4 ALICE 04.10
i.e. , after having loggedin the NE, according to the Craft Terminal Men:
ED
04
a)
Download Init download (selecting the NEversion to be downloaded)
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
9600LSY/LHR Line Up Guide
8.7 Configuration data definition and save

The instructions given in the handbook cited in para.8.6 do not include the definition of all the Equipment
configuration data that could be necessary.
1)
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:
through the MIB backup, as described in this handbook in section:

LHR Ne Management , chapter Software Management,
para. MIB management
1AA 00014 0004 (9007) A4 ALICE 04.10
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

The commissioning instructions are given in:

9 NEW SWP VERSION INSTALLATION (SAME SWP RELEASE)

This chapter details all phases necessary to install a new SWP version in the PC environment as well
This procedure can be used only in the case depicted in point 5 ) on page 61, i.e.:
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.
DO NOT USE THIS PROCEDURE TO UPDATE

FROM OLDER TO NEW SWP RELEASE
Procedure:
1)
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)
new MIB structure compatible with old MIB structure

Perform a SW download as explained in chapter Software Management of section LHR
Ne Management in this manual, i.e. , after having loggedin the NE, according to the Craft
Terminal Men:
Download Init download (selecting the version to be downloaded)
then, after about 2 hours, Download Unit Info Activate to swap between
the older and the newer versions.
The result is to have the Equipment working with the new SWP version nevertheless
maintaining the old configuration data.
b)
new MIB structure not compatible with old MIB structure

Proceed as specified on para.6.3 on page 63, taking into account that in step g ) equipment
data configuration must be carried out by individual commands only.
10 SWP UPGRADING FROM A PREVIOUS SWP RELEASE

This chapter details all phases necessary to install a new SWP release in the PC environment as well
This procedure must be used only in the case depicted in point 4 ) on page 61.
1AA 00014 0004 (9007) A4 ALICE 04.10
Procedure not presently envisaged (this is the first SWP release).
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
71 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
72 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10
APPENDICES
ED
SECTION CONTENT
PAGE
Chapter 11 ECTEquipment connection via public switched telephone

network
75
Chapter 12 Documentation guide
83
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
73 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
74 / 96

11 ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK
11.1 Introduction
This chapter explains the operations necessary to allow the remote connection to the FInterface, from
a local PC configurated as ECT, through a switched telephone line of the standard Public Telephone
Network, as shown in Fig. 19. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork (reachable
from the main equipment through DCC and/or LAN).

F Interface
Port COM

Remote
Modem
Local
Modem
Fig. 19. ECTEquipment connection via Public Switched Telephone Network
11.2 Certified modems

The connection has been successfully tested with the following types of modems:
a)
Modem Sportster Flash (US Robotics)
b)
Modem TD32 AC (Westermo Teleindustri AB)
and with the following local/remote combinations:

Local Modem
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
11.3 Connection cables
PC/ECT (DTE)
Local Modem (DCE)
Cannon 9 pins female
DCD
TD
RD
DTR
DSR
RTS
CTS
GND

In the following figures, the cables for the connections are described:
Cannon 25 pins male
8
3
2
DCD
TD
RD
4 RTS
5 CTS
6 DSR
20 DTR
7 GND
1
2
3
4
6
7
8
5
Fig. 20. ECTLocal Modem cable
Remote Modem (DCE)
F Interface (DCE)
Cannon 25 pins male
Cannon 9 pins male
TD
RD
RTS
CTS
DSR
CTS
GND
2
3
4
5
6
3
2
7
8
6
20
7
4
5
TD
RD
RTS
CTS
DSR
DTR
GND
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 21. F InterfaceRemote Modem cable
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
76 / 96

11.4 Modem setting

11.4.1 Sportster Flash Modem setting
This modem requires only a SW setting via serial port.
There is a little difference between local and remote modems setting (refer to Fig. 19. on page 75 for the
distinction between local and remote), relevant to the autoanswer option that must be set in the remote
modem and not set in the local modem.
LOCAL MODEM SETTING
To set the local modem, proceed as follows:
1)
Connect the local modem to the PC/ECT with the cable of Fig. 20. on page 76.
2)
Power and switch on the local modem.
3)
On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Bits per second: 38400
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
4)
Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return>
ATT<Return>
ATX3<Return>
AT&W0<Return>
1AA 00014 0004 (9007) A4 ALICE 04.10
5)
ED
(Best PC default configuration recall)

(Tone Dialling instead than Pulse Dialling)
(Second Signal disabling, avoids problems with PABX)
(Configuration store in NVRAM 0)
Now, setting has been completed. 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:
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)
carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting
b)
execute and store the modem setup, writing in the HyperTerminal program window the same
commands described in step 4 ) for the local modem setting, and adding the following command:
ATS=1<Return>
c)
now, setting has been completed. Modem can be switched off and disconnected, if necessary.
N.B.
ATI4<Return> in the HyperTerminal program window.
Information displayed should be equal to that displayed for the local modem, with only the
difference for field S00:
1AA 00014 0004 (9007) A4 ALICE 04.10
S00=001
ED
(Autoanswering setting)
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
11.4.2 TD32 AC Modem setting

This modem requires an initial HW setup via dipswitches and a SW setting via serial port.
To set the modem, both local and remote, proceed as follows:
1)
The initial HW setup via dipswitches is indicated in Fig. 22. herebelow:
ON
ON
ON
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 2 3 4
SW3
SW2
SW1
ON
ON
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
SW5
SW4
Fig. 22. TD32 AC modem dipswitch setting

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

(DTE/DCE flow control disabling)
(Automatic Answer enabling > Only on Remote modem and
wait the message NO CARRIER)
(Configuration store in NVRAM 0)
(Configuration Set to load at switchon: NVRAM 0)
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
79 / 96
AT\S<Return> in the HyperTerminal program window.
Information displayed should be as follows:
AT\S
1AA 00014 0004 (9007) A4 ALICE 04.10
CMD DESCRIPTION / OPTION

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

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

*H NEG. SPEED......HIGH
S0 RINGS TO ANS.....002
S1 RING COUNT.......000
S2 <ESC> CHAR.......043
S3 <CR> CHAR........013
S4 <LF> CHAR........010
S5 <BS> CHAR........008
S7 CONNECT TIME.....060
S8 PAUSE TIME.......002
S12 ESC GUARD TIME...050
S30 CONNECT INACT....000
S32 XON CHAR.........017
S33 XOFF CHAR........019
S36 FALLBACK ACTION..007
S37 MODE SELECT......000
S48 V42 NEG CTRL.....007
S95 RES. CODE........000
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
80 / 96

N.B.

11.5 Setting up the connection

In order to activate the connection and operate the ECT in remote way, proceed as specified herebelow.
Refer to Fig. 19. on page 75 for the distinction between local and remote modems.
N.B.
Leaving the remote modem permanently switched on and permanently connected to

Finterface and telephone line, operations set up by steps 1 ) thru 4 ) , it is possible to access
the equipment in any moment.
In order to access the equipment by local ECT, proceed as specified in steps 5 ) thru 13 ) .
1)
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)
Power and switch on the remote modem.
4)
Be sure remote equipment is switched on and correctly working.
5)
Connect the local modem to the PC/ECT (with the cable of Fig. 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)
Power and switch on the local modem.
8)
On the PC, activate program HyperTerminal and configure the PCLocal Modem serial line with
the following parameters:
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
9)
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.
The message text depends on the modem type, as follows:

CONNECT 14400/ARQ/V32/LAPM/V42BIS
CONNECT 38400
(Sportster Flash)
(TD 32 AC)
11 ) Close HyperTerminal program.

12 ) Activate the ECT applicative SW as usual.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
82 / 96
12 DOCUMENTATION GUIDE
1AA 00014 0004 (9007) A4 ALICE 04.10

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.
INFORMATION REGARDING CUSTOMER DOCUMENTATION IN GENERAL
ED
General on Alcatel Customer Documentation

including:
on page 87
CustomerIndependent Standard Customer Documentation
on page 87
Product levels and associated Customer Documentation
on page 88
Typical contents of Technical & Craft Terminal Operators Handbooks on page 90
Documentation on paper
on page 92
Documentation on CDROM
on page 94
Handbook and CDROM supply to Customers
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.
12.1.1 Specific equipment handbooks and CDROMs

The standard Customer Documentation in the English language for the equipment whose
product-release-version is stated in para.1.2 on page 12 consists of the following handbooks:
Tab. 11. Handbooks related to the specific product hardware
REF
HANDBOOK
9600LSY/LHR Rel.1.0 & 2.0

Technical Handbook
[A]
ANV Part No.
FACTORY
Part No.
3DB 02839 AAAA
955.203.292 Q
THIS
HDBK
or NOTE
Provides information regarding Equipment description and composition,

Hardware setting documentation, and Maintenance (together with handbook
REF.[D] )
9600LSY/LHR Rel.1.0 & 2.0
Installation Handbook
3DB 02840 AAAA
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
3DB 02841 AAAA
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
1AA 00014 0004 (9007) A4 ALICE 04.10
REF
HANDBOOK
9600LSY Rel.1.0
CT Operators Handbook SWP 1.0
ANV Part No.
FACTORY
Part No.
3DB 02838 AAAA
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

12.1 Productreleaseversion handbooks

Tab. 13. Handbooks common to all Alcatel Radio Transmission products
REF
[E]
HANDBOOK
ANV Part No.
FACTORY
Part No.
Interference investigation procedure
3DB 04165 EAAA
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
ANV Part No.
FACTORY
Part No.
3AL 79186 AAAA
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
3AL 71079 AAAA
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]
3AL 71081 AAAA
957.130.462 E
Provide detailed information and operational procedures regarding the Event Log
Management software embedded in the 1320CT software package.
Tab. 15. Documentation on CDROM

CDROM TITLE
REF
DCP 9600LSY 1.0 CDROM
1AA 00014 0004 (9007) A4 ALICE 04.10
[I]
ED
ANV Part No.
FACTORY Part No.
3DB 02831 AAAA
417.200.017 D
Contains, in electronic format, all handbooks: REF.[A] to [H]

Envisaged after the release of all handbooks
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
85 / 96
12.1.2 Related equipment handbooks and CDROMs
Tab. 16. Handbooks related to the products hardware
REF
HANDBOOK
[J]
Optinex Racks Rel.3.0.0 Technical Handbook
ANV Part No.
FACTORY
Part No.
3AL 37953 AAAA
955.100.922 C
Tab. 17. Documentation on CDROM

CDROM TITLE
ANV Part No.
FACTORY Part No.
Optinex Racks Rel.3.0 CDROMDOC EN
3AL 37954 AAAA
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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

12.1.2.1 Handbooks and CDROMs of OPTINEX Rack

12.2 General on Alcatel Customer Documentation

This paragraph describes in general the Alcatel Customer Documentation system, details the association
between the product levels and the associated documentation, and explains Customer Documentation
characteristics as well as the policies for its delivery and updating.
This paragraph is fully applicable to the 2nd generation Radio Product families of Alcatel WTD (Wireless
Transmission Division) only.
The documentation typical contents described in para.12.2.3 on page 90, apply to handbooks issued after
February 2002.
12.2.1 CustomerIndependent Standard Customer Documentation
a)
Definition
Standard Customer Documentation, referred to hereafter, must be always meant as
plantindependent and is always independent of any Customization.
Plantdependent and/or Customized documentation, if envisaged by the contract, is subjected to
commercial criteria as far as contents, formats and supply conditions are concerned
N.B.
b)
Plantdependent and Customized documentation is not described here.
Aims of standard Customer Documentation

Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and
maintaining the equipment according to Alcatel Laboratory design and Installation Dept. choices. In
particular:
the contents of the handbooks associated to the software applications focus on the explanation
of the manmachine interface and of the operating procedures allowed by it;
maintenance is described down to faulty PCB location and replacement.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
04
No supply to Customers of design documentation (like PCB hardware design and

production documents and files, software source programs, programming tools, etc.) is
envisaged.
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
87 / 96
12.2.2 Product levels and associated Customer Documentation
a)
Products
A product is defined by the network hierarchical level where it can be inserted and by the whole
of performances and services that it is meant for.
E.g. 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)
Configurations and Network Elements

In some cases, a product-release includes different possible configurations which are
distinguished from one another by different Network Element (NE) types and, from the
management point of view, by different SWPs.
E.g. 9600USY Rel.1.0 includes various configurations with various NE types (Regenerator
1+0/1+1/2+0 with NE types UHR/UHRC; Regenerator 3+1/4+0 with NE type UHRN; WMSN with
NE types UHR/UHRC/UHM/UHMC) each of which has its own specific SWP.
d)
SWP Releases and Versions

See Fig. 23. herebelow.
A SWP is identified by the configuration name and by the version number (tree digits).
The versions first digit corresponds to the productrelease number first digit; the second digit
identifies, together with the first, the SWP release.
The third digit of the SWP version identifies the Patch Level of the SWP Release.
SWP version
SWP Release
Product
Releases
first digit
SWP evolution for bug fixing purposes
(same SWP Release within same ProductRelease)
SWP evolution for additional features
(new SWP Release within same ProductRelease)
(N.B. see next page)
1AA 00014 0004 (9007) A4 ALICE 04.10
SWP evolution for additional features

(new SWP Release of a new ProductRelease)
Patch Level
1.
0.
1.
0.
1.
0.
1.
1.
1.
0.
2.
0.
Fig. 23. Example of SWP Release and Version numbering
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
88 / 96

See Fig. 24. on page 89.

N.B.
e)
Sometimes, different SWP Releases (within the same ProductRelease) are commercially
distinguished by different names, e.g. :
SWP version
SWPRelease commercial name
1.0.x
1.0
1.1.x
1.0B
1.2.x
1.0C
Customer Documentation
A product-release(configuration) has its own set of standard Customer Documentation, usually
formed of several handbooks, i.e., in general:
System and Hardware documentation:
one (or more) Technical Handbook(s) (see page 90 for details)
an Installation Handbook
a Commissioning Handbook or LineUp Guide
Software documentation:
a Craft Terminal Operators Handbook, associated to the specific SWPRelease (see

page 91 for details)
other Operators Handbooks (typically those associated to the SW platform embedded

in the SWP)
PRODUCT
evolution
PRODUCTRELEASE 1.0
PRODUCTRELEASE 2.0
ALTERNATIVE CONFIGURATIONS
CONFIG.A
SWP REL.1.0
PRODUCT
LEVELS
CONFIG.B
evolution
SWP REL.1.1
DOCUMENTATION
1AA 00014 0004 (9007) A4 ALICE 04.10
CONFIG.A
System & HW
Documentation
SWP REL.1.0
SW
Documentation
SWP REL.1.1
SW
Documentation
Fig. 24. Example of Product levels and associated Customer 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
Documentation Guide : contains general information on the Customer Documentation

set envisaged for the equipment and detailed information regarding the specific
handbook, like handbook structure/history and abbreviation list.
SafetyEMCESD norms and equipment labelling : describes the equipment labelling

and the norms mandatory or suggested that must be considered to avoid injuries on
persons and/or damage to the equipment.
INFORMATIVE LEVEL
1AA 00014 0004 (9007) A4 ALICE 04.10
System Description : gives the firstlevel description of equipment in the specific

configuration the handbook is meant for. The information given is enough to understand
the equipment composition and operation and to read the operative level chapters.
Functional Description : gives the secondlevel description of equipment in the specific

configuration the handbook is meant for. Reading this chapter is not necessary to carry
out standard installation commissioning and maintenance activities.
Technical Specifications : supplies in detail the equipment technical characteristics.
OPERATIVE LEVEL
Physical Configuration : gives detailed operative information regarding:
the equipments items (P/Ns, equipping rules, labels for remote inventory)
their physical and logical position in the system
the unit assembly/subassembly and front panel drawings, with the usage description
of the access points (connectors, visual indicators, buttons)
hardware setting description
pinout description of connectors for Customer usage
summary and operative information on characteristics of external interfaces
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.
Maintenance : describes the equipment routine and corrective maintenance procedures

as well as those for the unit replacement with spare parts.
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

12.2.3 Typical contents of Technical & Craft Terminal Operators Handbooks

b)
Craft Terminal Operators Handbook

It is usually composed by various sections. Each section is an independent document that can evolve
independently from the others. The sections always present are:
SECTION 1: INTRODUCTION containing the following main parts (not necessarily in this
sequence):
Documentation Guide and SafetyEMCESD norms and equipment labelling, as

Technical Handbook
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).
ECTequipment remote connections : gives instructions to allow the remote connection

between ECT and the equipment.
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
Equipment configuration management
Setting of parameters for maintenance
Events Log and Performance Monitoring management
Software management
SECTION 3: NE MAINTENANCE : gives the description of the NE troubleshooting based on

the use of the Craft Terminal.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
12.2.4 Documentation on paper

Handbook format
Handbooks are supplied on A4sized papers for text and general drawings, and, when necessary,
A3sized papers for detailed drawings, in four ring solid/plasticcovered binders.
b)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Each handbook is identified by:
ED
the name of the product-release,
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 name,
the handbook part number,
the handbook edition:
first draft edition=01A
second draft edition=01B
.....
first validated edition=01
second validated edition=02
nnth validated edition=nn
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)
Changes introduced in the same product-release (same handbook P/N)

In case of handbook updating for its technical contents:
the edition, hence the date, is increased;
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)
Changes due to a new product-release
1AA 00014 0004 (9007) A4 ALICE 04.10
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
12.2.5 Documentation on CDROM

Contents
A CustomerDocumentation CDROM is conceived to contain in readonly electronic format the
handbooks of all the product-release(configurations) of one productrelease.
The first edition of a CDROM is created only when all the handbooks of the first released
product-releaseconfiguration of one productrelease have been issued as first validated editions.
If envisaged, the handbooks relevant to other product-releaseconfigurations of the same
productrelease are added in a further CDROM edition, when they are all completed and validated.
No additional information is added to each handbook, so that the documentation present in the
CDROM is exactly the same the Customer would receive on paper (with the same handbook
editions).
b)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Each CDROM is identified:
ED
1)
by the following external identifiers, that are printed both on the booklet and the CDROM upper
surface:
the name of the productrelease,
a writing indicating the language(s),
the CDROM P/N (Factory P/N and ANV P/N),
the CDROM edition (first edition=01)
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)
The list of source handbook/document P/Nseditions indicated in previous para.c ) point 2 ), in

association with the CDROMs own P/Nedition, is also loaded in the AlcatelInformationSystem
as a structured list.

1AA 00014 0004 (9007) A4 ALICE 04.10
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
12.2.6 Handbook and CDROM supply to Customers

Standard supply
Handbooks and CDROMs are standard commercial items and are ordered and delivered as any
other Alcatel commercial item.
Handbooks and CDROMs are not automatically delivered together with the equipment they refer
to.
The number of handbooks or CDROMs per type to be supplied must be decided at contract level.
b)
Productdocumentation consistency
Equipment description and layout are always general, i.e. they never describe the actual
composition of the equipment supplied to Customer (this task is entrusted to plantdependent
documentation).
Detailed hardware documentation concerns actually supplied units and is coherent with the
production issue of such units.
Softwareassociated handbooks are coherent with the supplied SWP release.
Copies of the handbooks regarding a specific productrelease previously delivered can be required
specifying P/N and edition.
c)
Inadvance supply
Whenever handbooks or CDROMs are delivered before the relevant equipment delivery, there is
the risk that their contents might not agree with the characteristics of the equipment which will be
delivered: the more they are in advance the less are they likely to agree.
d)
Supplying updated handbooks and CDROMs to Customers

Supplying updated handbooks or CDROMs to Customers who have already received previous
issues is subject to commercial criteria.
By updated handbook delivery, we mean the supply of a complete copy of a new issue of the
handbook (supplying erratacorrige sheets is not envisaged).
e)
Copyright notification
The technical information of the handbooks and CDROMs supplied to Customers is the property
of ALCATEL and must not be copied, reproduced or disclosed to a third party without written consent.
f)
Supply to Customers of Customer Documentation source files

Presently not envisaged.
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
04
SC.1:INTRODUCTION
957.207.022 A
3DB 02838 AA AA
96
96 / 96

a)

TABLE OF CONTENTS
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
11
11
11
11
12
14
14
2 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 LHR view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Introduction to the LHR menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.6 Radio menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.7 Equipment menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.8 Board menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.9 Port menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.10 External Points menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.11 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
4 NE MANAGEMENT GENERAL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . . . .
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
1AA 00014 0004 (9007) A4 ALICE 04.10
01A 011109
ED
DATE
C.NAVA ITACO
E.CORRADINI
C.NAVA ITACO
E.CORRADINI
M.CORBETTA ITACO
ORIGINATOR
9600LSY REL.1.0
ED
04
SC.2:LHR NE MANAGEMENT
957.207.022 A
3DB 02838 AA AA
258
1 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
31
33
5 COMMUNICATION AND ROUTING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Overview on Communication and Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Partitioning into Routing Subdomains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Partitioning into separate Routing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Communication and routing views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Reachable Address Prefixes Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9 Manual ES Adjacencies table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
9 RADIO PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Overall RPS structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Information on RPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 RPS Configure Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 RPS Configure Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 RPS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6 Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.7 RPS Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.8 RPS Extra Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
101
101
102
103
105
107
109
111
113
ED
04
957.207.022 A
3DB 02838 AA AA
258
2 / 258

4.2 NE Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

10 WAY SIDE TRAFFIC AND SERVICE CHANNELS PROTECTION MANAGEMENT . . . . . . . .

10.1 Overall structure of WST and Service Channels protection . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Information on WST and Service Channels protection . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 RFCOH Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 RFCOH Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 RFCOH Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
14 EXTERNAL INPUT AND OUTPUT POINT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Displaying external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.1 Expanding or reducing the External Points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 External Point configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
183
185
186
ED
04
957.207.022 A
3DB 02838 AA AA
258
3 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
189
189
189
193
194
196
16 EVENT LOG MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
19 SYSTEM SOFTWARE OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3 Channels and relation between boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4 Functional partitioning of the management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 Equipment management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.1 Base band shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.2 Fans shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.3 Transceiver shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.4 Physical Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.5 Allowed and default equipment configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.6 Equipment protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.7 Compatible boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.8 Power Supply Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.9 External Points management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.10 Remote Inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6 Transmission management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.7 Radio management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.9 Radio Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.10 Overhead management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
225
226
227
227
228
229
230
234
235
236
237
245
245
245
246
247
248
249
251
252
253
ED
04
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

19.10.1 RSOH bytes terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.10.2 RFCOH bytes terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.10.3 RSOHRFCOH bytes crossconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.10.4 Phonic parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.11 Radio Overhead management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.12 Connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.13 Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.14 Communication and Routing management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.15 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.16 Support management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.17 Test management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
04
255
255
255
255
256
257
258
258
258
258
258
957.207.022 A
3DB 02838 AA AA
258
5 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
6 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Fig. 51. Remote Inventory (file saved) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 52. Remote Inventory screen at Board Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 53. Equipment Overview Subrack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 54. An example of a Board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 55. An example of Port identification and alarm synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 56. Board menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 57. After Port Access selection ( example ) of LHR N.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 58. Subrack level view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 59. Port view SDH ( on the left ) and PDH ( on the right ) option menu . . . . . . . . . . . . . . . . . . . .
Fig. 60. LAPD Configuration option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 61. LAPD Configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 62. Visualizing a port optical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 63. Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 64. Automatic Laser Shutdown Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 65. ALS current state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 66. Ber Not Intrusive window (Start button) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 67. BER Not Intrusive window (Refresh/Stop button) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 68. BER Not Intrusive window (Overflow condition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 69. Refresh option offered by the PORT menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 70. RPS Configure (Schema) option offered by the RADIO menu bar . . . . . . . . . . . . . . . . . . . .
Fig. 71. RPS Configure Schema Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 72. RPS Configure (Units) option offered by the RADIO menu bar . . . . . . . . . . . . . . . . . . . . . . .
Fig. 73. RPS Configure Units Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 74. RPS Switch option offered by the RADIO menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 75. RPS Commands Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 76. Static Delay option offered by the RADIO menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 77. Static Delay Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 78. Row Selected Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 79. RPS Synthesis option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 80. RPS Synthesis dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 81. RPS Extra Traffic screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 82. RPS Extra Traffic dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 83. RFCOH Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 84. RFCOH Configure Dialog Box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 85. Search RFCOH Protection Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 86. RFCOH Configure with WST parameters (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 87. RFCOH Configure with Service Channels parameters (example) . . . . . . . . . . . . . . . . . . . . .
Fig. 88. RFCOH Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 89. RFCOH Switch Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 90. RFCOH Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 91. RFCOH Synthesis Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 92. Search RFCOH Protection Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 93. RFCOH Synthesis Dialog Box (with parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 94. ATPC option offered by the RADIO menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 95. ATPC Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 96. ATPC Configure screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 97. Power Setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 98. Manual Power Setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 99. ATPC Identifier option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 100. ATPC Single Direction Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 101. Gain option offered by the RADIO menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 102. Channel Radio Port Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 103. Gain Management Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 104. Hop Trace option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
957.207.022 A
3DB 02838 AA AA
258
7 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
8 / 258

Fig. 105. Hop Trace Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 106. Squelch option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 107. Squelch Management Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 108. Radio Abnormal Condition List option offered by the Radio menu . . . . . . . . . . . . . . . . . . .
Fig. 109. Radio Abnormal Condition List Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 110. Frequency Reuse option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 111. Frequency Reuse Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 112. Equalization Delay option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 113. Equalization Delay screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 114. Frequency Agility option offered by the Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 115. Frequency screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 116. Voltage Control Oscillator option offered by Radio menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 117. Voltage Control Oscillator screen (only read) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 118. Power Measurement option offered by the RADIO menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 119. Power Measurement Parameters screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 120. Power Measurement Graphic Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 121. Details Dialog screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 122. Power Measurements File Reading option offered by Radio menu . . . . . . . . . . . . . . . . . . .
Fig. 123. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 124. Example of Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 125. Overhead options offered by the Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 126. OH TP creation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 127. Search OH Tp to be created Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 128. OH TP insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 129. CrossConnection Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 130. CrossConnection Management dialogue box ( After Search ) . . . . . . . . . . . . . . . . . . . . . .
Fig. 131. Main CrossConnection dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 132. Search for OverHead CrossConnection Input screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 133. Selection of Search OH Tp Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 134. OH TP deleting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 135. OH TP delete (selection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 136. Phone Parameters screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 137. Print to Printer Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 138. Print to File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 139. Loopback A: RRA line loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 140. Loopback B: RRA internal loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 141. Loopback C: RFCOH Internal loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 142. DCC structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 143. EC position with respect to loopback points and consequent unavailability by RECT
(CHx/y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 144. Allowed and not allowed loopbacks by RECT (CHx/y) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 145. Port Loopback Configuration option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 146. Port Loopbacks Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 147. Loopback Create (Loopback on RST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 148. Loopback Create Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 149. Loopback Create Choose Tp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 150. Loopback Create Tp search screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 151. Loopback Create Tp selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 152. Loopback Create Loopbacks selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 153. Loopback Create (see RST block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 154. Loopback Delete Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 155. Loopback Management Delete TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 156. Loopback Management (Configuration menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 157. Loopback Management Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

Fig. 158. Loopback Configuration Dialog Box (Port level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 159. Loopback Management Search Termination Point (TP) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 160. Loopback Management Termination Point selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 161. Loopback Management Termination Point List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 162. Loopback Management (Configuration Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 163. Loopback Management Delete Termination Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 164. Opening the External Points view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 165. External Points view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 166. Expanding or reducing the External Points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 167. Configuring external points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 168. External Input Point Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 169. External Output Point Configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 170. External Points view with flag symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 171. Configuring the Alarm Severity Assignment Profile (ASAP). . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 172. ASAPs Management dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 173. ASAP Edition dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 174. Set ASAP dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 175. Inhibit alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 176. Allow alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 177. N.E. Alarms option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 178. Alarm Surveillance screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 179. Abnormal Condition List menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 180. Abnormal Condition List screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 181. Log Browsing option in the Network Element context view . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 182. An example to access to the Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 183. PM Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 184. Current PM Data dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 185. PM History Data dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 186. PM Threshold Table Select dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 187. PM Threshold Table Modify dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 188. Software Download general principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 189. Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 190. Download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 191. SW downloading initiate dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 192. Software download in progress dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 193. Software packages information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 194. Software units details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 195. Software packages information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 196. NE MIB management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 197. Restart NE confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 198. Radio system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 199. Base Band shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 200. STM1 access module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 201. Transceiver shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 202. SDH and Radio Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 203. Radio functional block diagram for LHR NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 204. Details of Radio Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 205. Overhead management functional view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 206. Overhead containment and connection relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
957.207.022 A
3DB 02838 AA AA
258
9 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
14
51
151
151
152
152
153
213
238
240
241
243
243
244
244
244
250
250
257
957.207.022 A
3DB 02838 AA AA
258
10 / 258

TABLES
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:
9600LSY/LHR Rel.1.0&2.0 Technical Handbook
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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
11 / 258
1.3 Document structure
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
GENERAL INFORMATION

It contains general information on this document, like document scope, structure and history.
Chapter 2 General introduction on views and menus

This chapter describes the organization of the LHR N.E., presented after the NE login.
Chapter 3 NE management supervision

This chapter is dedicated to the N.E. states and N.E. access.
EQUIPMENT CONFIGURATION MANAGEMENT
Chapter 4 NE management general configuration

This chapter describes the configuration relevant to the general equipment management (Craft
Terminal access, N.E. Time, etc. ).
Chapter 5 Communication and Routing management

This chapter describes how to set the configuration parameters concerning the communication
protocols for the local N.E., the OS and each other related N.E. in order to provide global
communication capabilities inside the network.
Chapter 6 Equipment management

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.
Chapter 7 Board view

This chapter describes the Board View function, allowing to show the physical port available in
a specific board and to access the Port view.
Chapter 8 Port view

This chapter describes the operations necessary for the configuration setting and verification
of each port.
Chapter 9 Radio protection management

This chapter deals with the management of the Radio protections.
Chapter 10 Way Side Traffic and Service Channels Protection Management

This chapter deals with the management of the Way Side Traffic and Service Channels
Protection.
Chapter 11 Radio parameters

This chapter deals with the management of the Radio transmission features.
Chapter 12 Overhead management

This chapter describes how to manage the Overhead ( OH ) bytes of the N.E.
04
957.207.022 A
3DB 02838 AA AA
258
12 / 258

Information in this document is organized as follows:

SETTING OF PARAMETERS FOR MAINTENANCE
Chapter 13 Loopback management

This chapter describes the commands for the management of loopbacks, for commissioning
or maintenance purposes.
Chapter 14 External input and output point management

This chapter describes how to display and set the input/output environmental alarms
(housekeeping alarms).
Chapter 15 Alarms management

This chapter describes how to configure the Alarms Management and access the Alarm
Surveillance and show the alarm condition.
N.B.
The chapter does not describe the Alarm Surveillance system. Reference must be
done to the specific 1330AS Operators Handbook.
EVENTS LOG AND PERFORMANCE MONITORING MANAGEMENT
Chapter 16 Event Log Manager

This chapter describes how to access the Event Log file.
N.B.
The chapter does not describe the Event Log Manager. Reference must be done to
the specific ELM Operators Handbook.
Chapter 17 Performance Monitoring

This chapter deals with the use of the Performance Monitoring functionalities.
SOFTWARE MANAGEMENT
Chapter 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.
APPENDICES
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Chapter 19 System Software overview

This chapter presents the system from the management software point of view.
04
957.207.022 A
3DB 02838 AA AA
258
13 / 258
Legend
n
m
blank
= new part
= modified part
= part unchanged

DOCUMENT EDITION
02
03
04
Document guide
General introduction on views and menus
NE management supervision
NE management general configuration
Communication and Routing management
Equipment management
Board view
Port view
Radio protection management
11
Radio parameters
12 Overhead management
10 Way Side Traffic and Service Channels Protection Management
14 External input and output point management
15 Alarms management
16 Event Log Manager
17 Performance Monitoring
19 System Software overview
ED
04
13 Loopback management
18 Software Management
1AA 00014 0004 (9007) A4 ALICE 04.10
01
05
m
n
m
m
m
m
957.207.022 A
3DB 02838 AA AA
258
14 / 258

2 GENERAL INTRODUCTION ON VIEWS AND MENUS

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.
2.1 LHR view organization

The LHR view ( see Fig. 1. on page 16 ) contains the following fields, which provide you with the
information needed to manage the NE:
Severity alarm synthesis,

Domain alarm synthesis,
Management status control panel,
View title,
View area,
Message/state area.
The Menu bar and the View area contained in the same NE view permit to perform all configuration and
supervision operations and the display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for the
description.
This document only comprises the information on the fields that differ according to the NE type:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Domain alarm synthesis

The different alarm domain types in to which the NE can be subdivided are: External Point,
Equipment, Transmission.
04
957.207.022 A
3DB 02838 AA AA
258
15 / 258
Domain alarm synthesis
Severity alarms
synthesis

Menu bar
View title
View area
Message/state
area
Management
state control panel
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 1. LHR Main view organization.
ED
04
957.207.022 A
3DB 02838 AA AA
258
16 / 258
2.2 Introduction to the LHR menu options

The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph lists all menu options and then provides more details on the respective contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where they are detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
From Chapter 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).
See para.2.2.1 on page 19 .
To navigate among the views and to set the TMN parameters.
Configuration
(second column).
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
Diagnosis
(third column).
To get information on the NE (alarms, performance monitoring, remote inventory).
Supervision
(fourth column).
To set the supervision states (i.e. Craft Terminal enabling).
Download
(fifth column).
See para. 2.2.5 on page 22 .
To manage the NE software (download, MIB management).
Radio
See para. 2.2.6 on page 23.
To show information about the functions and features of the radio Equipment (ATPC, Switch ,
Gain ).
Help
(last column).
1AA 00014 0004 (9007) A4 ALICE 04.10
To activate the help.
ED
04
957.207.022 A
3DB 02838 AA AA
258
17 / 258
Other Menus
Equipment
See para. 2.2.7 on page 24
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
See para 2.2.9 on page 25.
To set and show (detailed alarm view) the transmission resources referred to the Port.
External Points
1AA 00014 0004 (9007) A4 ALICE 04.10
To show and modify the housekeeping (environmental) alarms.
ED
04
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.
1AA 00014 0004 (9007) A4 ALICE 04.10

2.2.1 Views menu introduction

The menu on the left side of the screen, allows to navigate among the views and to set some parameters
( see Fig. 18. on page 53 ), by means of the following entries:
Backward:
Displays the previous screen of the same application.
Forward:
Displays the next screen of the same application.
Equipment:
Opens the Equipment view.

Then the Equipment menu is available on the menu bar.
External Points:
Displays and sets the input/output environmental alarm.
Refresh:
Allows to show a complete overview of Equipment.
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:
Allows to navigates and shows the contents of the selected object.

The current view doesnt change, but a new windows opened with a new view.
Close:
Close the EMLUSM view, without stopping the supervision of the NE.
ED
04
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:
Manages the Alarm Severity Assignment Profile.
Set Alarm severities:
Sends the Alarm Severity Assignment Profile to the selected boards.
Set SdhNe Alarm severities: Sends the Alarm Severity Assignment Profile to the equipment level.
NE Time:
Displays and set the NE local time.
Performance:
Manages the Performance Monitoring domain.

Used to set the PM parameters, opening the following menu options:
Threshold table
1AA 00014 0004 (9007) A4 ALICE 04.10
Loopback Management: Manages the allowed Loopback types ( internal or line ).
Comm/Routing:
Enters the Communication and Routing management.

Used to set the parameters for NE and OS in the TMN, opening the following
menu options:
Local configuration
OS Configuration
NTP Server Configuration
Interfaces Config. =>LAPD Configuration

=>Ethernet Configuration
OSI Routing Config.=>RAP Configuration

=>MESA Configuration
Overhead:
Handles the operation on the Overhead bytes

Used to set the parameters in the following menu options:
OH Cross Connection
OH Phone Parameters
OH Tp Creation
OH Tp Deleting
ED
04
957.207.022 A
3DB 02838 AA AA
258
20 / 258

2.2.2 Configuration menu introduction
2.2.3 Diagnosis menu introduction
1AA 00014 0004 (9007) A4 ALICE 04.10

This menu allows to get information on the NE, by means of the following entries:
Alarms:
Displays the Alarms Surveillance information of the NE.

See para. 15.2 on page 194.
Opens the following menu options:
NE alarms
Object alarms
Subtree alarms
Equipment alarms
Transmission alarms
External Points alarms
Performance data:
Not implemented
Log Browsing:
Manages the events stored in the NE.

( logld.1 )
( logld.2 )
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
957.207.022 A
3DB 02838 AA AA
258
21 / 258
2.2.4 Supervision menu introduction
Access State:
Manages the supervision access to the NE, via CT or OS.

OS
Requested
Manages the alarm supervision of the NE.

Resynchronize
Allow Notifs
Inhibit Notifs
Alarms:
Upload Remote Inventory:Stores the Remote Inventory data in the Craft Terminal.
Set Manager List:
Not implemented yet.
Restart NE:
Reset the NE software.

This menu allows to set the supervision states of the NE, by means of the following entries:
2.2.5 Download menu introduction
1AA 00014 0004 (9007) A4 ALICE 04.10
This menu allows to manage the NE software, by means of the following entries:
Initial download:
Manages the software download,and upgrades the NE.
Units info:
Show the status of the software package installed in the NE memory banks.
Mib management
Used to back up the NE software configuration and restore of backupped file.
ED
04
957.207.022 A
3DB 02838 AA AA
258
22 / 258

2.2.6 Radio menu introduction

This menu is used to protect the STM1/subSTM1 signals by means the manage the NE software and
of the following entries:
RPS:
Displays the Radio features of the LHR NE.

Configure
=>Schema
=>Units
Static Delay
=> Rx Side
Switch
Synthesis
Extra Traffic
RFCOH:
Displays the Radio features of the LHR NE.

Configure
Switch
Synthesis
Frequency:
This function displays the TX/RX frequency values of a N.E. station.
Power Measurement:
1AA 00014 0004 (9007) A4 ALICE 04.10
The purpose of this function is to set the power measurement in a Link of

N.E.
Graphic Power Measurement
File Reading
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.
Power and Threshold Setting
ATPC Identifier
Squelch:
Displays the possible Squelch actions ( Main, Diversity and Reused ).
Gain:
Set the Gain levels on the Receiver side in manual mode.
Hop Trace:
This function allows the operator to verify one hop section trace of Equipment.
Radio Abnormal Condition List:
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.
Voltage Control Oscillator Status:
ED
04
Displays the list of operation manual in Tx and Rx sections.
This function displays the Equipment V.C.O. domain.
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:
Adds or changes the board type.
Modify:
Changes the board type without previously remove it.
Remove:
Removes the board.
Set in service:
Inserts a lock symbol in the board.
Set out of service
Deletes the lock symbol in the board, enabling changes.
Reset:
Not implemented yet.
Software description:
Shows information on the software of the board.
Remote Inventory:
Shows the Remote Inventory data inserted in the equipment.

Subrack level
Board level
Show supporting equipment: Allows to navigates to the upper equipment level.
Show Supported Port:
Allows to navigates to the Subracks/Boards/Ports level of Equipment.
2.2.8 Board menu introduction
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
Access the Port view. See para.7.2.1 on page 86.
Change Physical Interface
.Not implemented
Show supporting equipment: Allows to navigate to the upper subrack level. See para.7.2.2 on
page 87.
ED
04
957.207.022 A
3DB 02838 AA AA
258
24 / 258

2.2.7 Equipment menu introduction

2.2.9 Port menu introduction

This menu allows to set and show the transmission resources (TP) referred to the Port, by means of the
entries indicated in the following list.
The Port view is reached by means of the Equipment menu and Board view to check the detailed
alarms presented, but the available menu permits to configure the port .
In these views only the TPs specific to the port are presented.
The Port view is presented when, a TP is selected and than confirmed .
TP configuration:
Set the parameters for the Section Trace.
AU4 Concatenation:
Not implemented yet. Only for SDH port views.
Performance:
Set and show Performance Monitoring parameters and data.

See chapter 17 on page 199.
It opens the following menu options:
Configure Monitoring
Display Current Data
Display History Data
1AA 00014 0004 (9007) A4 ALICE 04.10
Loopback:
Allows to manage the Loopback Commands.
Port Loopback Configuration

Loopback Management
Manages the physical setting

See para.8.2 on page 90.
ALS Management
Show Optical Configuration
TX Quality Configuration
Single Fiber Configuration
LAPD Configuration
MS Configuration
Physical Media:
of
the
TP
of
the
ports.
Show supporting board: Allows to navigate to the upper board level.
Refresh:
Allows to show a complete overview on the signal flow, opening all TPs
Ber Not Intrusive:
Allows to start/stop BER measurement data and to display them
ED
04
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:
Set the input/output housekeeping alarms.

See para. 14.2 on page 186. As default nothing is set.
Display:
Shows the list of the input/output housekeeping alarms.

See para. 14.1 on page 183.
Show external Input Points
Show external Output Points
Show all external Points
2.2.11 Help
1AA 00014 0004 (9007) A4 ALICE 04.10
Not implemented
ED
04
957.207.022 A
3DB 02838 AA AA
258
26 / 258

2.2.10 External Points menu introduction
3 NE MANAGEMENT SUPERVISION

This chapter is dedicated to the NE states and NE access.
3.1 NE management states

The elementary building blocks of any telecommunication network are called Network Elements (NEs).
When operating with a Craft Terminal, the NE can present different management states according to the
condition of the connection (supervision, local access, connection state, etc.). Also general Alarm states
are presented.
Management states are present at the Network Element Synthesis view level and at the LHR view level.
All information relevant to the management states are included in the Basic Craft Terminal Operators
Handbook.
Any message in the communication link between the CT and the NE results in updating of the management
states when the CT detects the communication failure.
3.2 NE supervision and login

The Network Element Synthesis views enable to get access to the current view described in this handbook.
The Network Element Synthesis views enable to work on local or remote NE LHR, selecting them and
activating Supervision and Login, as described in the Basic Craft Terminal Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
The LHR Main views are shown in the following figures ( see Fig. 2. on page 28 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
27 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 2. NE LHR Main view
ED
04
957.207.022 A
3DB 02838 AA AA
258
28 / 258

4 NE MANAGEMENT GENERAL CONFIGURATION

This chapter describes the general configuration relevant to the equipment management (Craft Terminal
access, NE Time, etc.).
4.1 Access state (allow or inhibit NE Craft access)

The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and the
CT, a Local Access Control (LAC) is available.
If the LAC is access denied, it means the OS manages the NE and the CT is not allowed to modify the
NE configuration (it can only read). In the view, the icon with a key symbol has a circular shape.
If the LAC is granted, it means the CT is allowed to manage the NE. In the view, the icon with a key symbol
has a rectangular shape.
If the LAC is requested, it means the CT has requested a permission from the OS and is waiting for a
replay.
However, the OS does continue to provide a certain number of services. These services include:
Alarm reception and processing,

Performance processing on TPs,
Switching back to the OS access state.
The access state of an NE can be modified from two types of views:

4.1.1 Switching from the OS to the Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the Access State
cascading menu as shown in the following figure.
Fig. 3. Configuration of the Craft access state from the Equipment NE view in the OS mode.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
29 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
4.2 NE Time management

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
Fig. 4. Getting and/or setting the local NE time.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following dialogue box opens, from which you can get and/or set the local NE time.
Fig. 5. NE Time dialogue box.
ED
04
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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.

4.3 Set Manager list

This option is referred to Security management and allows the user to set the Manager List and the Access
Control Domain of the NE.
From the Supervision pull down menu, select the Set Manager List option.
The dialogue box contains the following fields:
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.
OK button is used to validate the selection made.

Cancel button closes the dialogue without changing of the data.
Help button provides some useful information on the dialogue.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 6. Set Manager List dialogue box
ED
04
957.207.022 A
3DB 02838 AA AA
258
33 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
34 / 258

5 COMMUNICATION AND ROUTING MANAGEMENT

5.1 Overview on Communication and Routing Domain
The purpose of the communication and routing domain is to set the configuration parameters concerning
the communication protocols for the local NE, the OS and each other related NE in order to provide global
communication capabilities inside the network.
A brief description Follows of basic concepts and terms involved in the communication and routing
domain.
During the TMN design process, a network is partitioned into domains; each domain can consist of a
collection of two types of nodes:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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:
routing domain A resides in a level 1 subdomain with area address a
routing domain B resides in a level 1 subdomain with area address b
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
36 / 258

5.1.2 Partitioning into separate Routing Domains
5.2 Communication and routing views

The Communication and Routing views allow to perform the following operations:
Local Configuration:
defining the local NE addresses
OS Configuration:
addressing the main and spare OSs connected to the local NE
NTP Server Configuration:
addressing the main and spare NTP servers connected to the

local NE
Interfaces Config.
which comprises:
LAPD Configuration:
Ethernet Configuration:
OSI Routing Config.
defining the LAPD port parameters for each LAPD channel in

the local NE
defining the configuration parameters necessary to manage
the local NE providing a LAN Ethernet interface
which comprises:
RAP Configuration:
MESA Configuration:
configuring the parameters necessary to address the NE

connected by Reachable Address Prefixes in a domain different
from the one of the local NEs one. This information is stored in
a RAP table.
configuring the parameters necessary to address a non SIS
NE in the same domain as the local NEs one. This information
is stored in a MESA table.
To get access in the Configuration pull down menu, as shown in the following figure select the
Comm/Routing option from.
1AA 00014 0004 (9007) A4 ALICE 04.10
The options are described in next paragraphs.
ED
04
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 Local Address section contain the following graphical objects:
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:
System Id: identifies an NE in an area uniquely and is 12 characters long
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.
End System section is not available.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
04
957.207.022 A
3DB 02838 AA AA
258
38 / 258

5.3 Local Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 7. Local Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
39 / 258

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.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 8. OS Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
40 / 258

5.4 OS Configuration

5.5 NTP Server Configuration

cascading menu, the NTP Server Configuration option.
The dialogue box opens ( see Fig. 9. ) allows to configure the addresses of the Main and Spare NTP
(Network Protocol synchronization Time) Servers connected to the local NE, used for time distribution in
the network.
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.
Help button provides some useful information about the dialogue.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 9. NTP Server Configuration dialogue box.
ED
04
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 10. LAPD Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
42 / 258

5.6 LAPD Configuration

5.7 Ethernet Configuration

Select the Configuration pull down menu. Select the Comm/Routing=>Interfaces Configuration
option and then, from the cascading menu, the Ethernet Configuration option.
The dialogue box opens ( see Fig. 11. on page 44 ) allows to define the parameters necessary to manage
an NE and provide a LAN Ethernet interface .
The following fields and data are present:
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.
OSI Section which comprises:
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 ) .
IP Section which comprises:
IP Address to be assigned to the N.E.
IP Mask relevant to the IP address
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.
Apply button performs a configuration change of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Close button closes the dialog without changes of the data.
ED
04
957.207.022 A
3DB 02838 AA AA
258
43 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 11. Ethernet Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
44 / 258

5.8 Reachable Address Prefixes Configuration

Select the Configuration pull down menu. Select the Comm/Routing=>OSI Routing Configuration
option and then, from the cascading menu, the RAP option.
The dialogue box opens ( see Fig. 12. ) allows to configure the Reachable Address Prefix table.
Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate
domain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, then
the LAN port will be used.
pointing device (upper part of the figure); each page represents a specific element of the RAP table and
its respective pointing device displays the element counter.
Physical Interface button
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 12. RAP Configuration dialogue box.
ED
04
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.
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.
Physical Interface button
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.
System Id section represents the System Id of the ES element.
MAC Address section allows to address the elements in the Ethernet LAN; this field is managed as
a simple string of 12 digits.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 13. MESA Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
46 / 258

5.9 Manual ES Adjacencies table Configuration

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.
6.1 Introduction and navigation

This section mainly deals with setting and changing the boards present on the Equipment and undertaking
board protection operations.
To use the menu options, from the View pull down menu select the Equipment option.
The first level of the Equipment Overview representation will be displayed directly into the current window
( see Fig. 14. on page 47 ).
The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 ).
Fig. 14. Equipment Overview NE level
ED
04
957.207.022 A
3DB 02838 AA AA
258
47 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 15. Equipment Overview Rack Level
Fig. 16. Equipment Overview Subrack level ( example )
ED
04
957.207.022 A
3DB 02838 AA AA
258
48 / 258

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.
Fig. 17. Equipment menu
1AA 00014 0004 (9007) A4 ALICE 04.10
Equipment setting operations are defined according the following sequences:
configuration of a new board
Configure the board by using the Set option
change of a board type
Set out of service the board
Configure the board by using the Set option
removal of a board
Set out of service the board
Remove the board.
ED
04
957.207.022 A
3DB 02838 AA AA
258
49 / 258
6.1.1 Equipment configurations
The LHR NE can be equipped up to 8 radio channels:
N + 1 Configuration ( where N is minor of 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
channel.
1 + 1 Configuration. The protected Channel is transmitted on the Spare channel ( protecting )

by Hitless switch function; the extra traffic cannot be supported.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The LHR NE contains the following Equipment:
ED
Base Band Subrack
Transceiver Subrack
Fans Subracks
04
957.207.022 A
3DB 02838 AA AA
258
50 / 258

This section provides information on the equipment types configurations of the LHR NE.

6.1.1.1 Allowed Equipment Configurations

In the following there are a short description and the related screens of the Equipment Composition of LHR
NE.
Tab. 2. LHR N.E. Composition.
COMPOSITION
RACK
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 )
TRI 128 ( Slot 1 to 10 )

( Transceiver card )
RX
( Daughter 4 )
( Receiver module S. D. )
1AA 00014 0004 (9007) A4 ALICE 04.10
LO ( Daughter 12 )
( Local Oscillator module )
SRFANS
( Fan Subrack 3)
ED
04
FANSL ( Slot 12 )
( Fan card )
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:
Transceiver card standard TRI 128
These Transceiver cards are in alternative between them.

6.1.1.1.3 Fans
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Rack of LHR N.E. are present two Fan Subracks:
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
957.207.022 A
3DB 02838 AA AA
258
52 / 258

6.1.1.1.1 Base Band

Fig. 18. Selecting the Equipment ( Rack ) to display ( Open Object )
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
53 / 258

Fig. 19. Rack screen
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
By clicking twice on the selected module the next screen opens ( see Fig. 21. on page 56 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
55 / 258

Fig. 21. SYStem COntroller card ( SYSCO ) screen
1AA 00014 0004 (9007) A4 ALICE 04.10
Starting from the Unit screen the operator can get access to all the circuit parts ( Daughters ) consists of.
ED
04
957.207.022 A
3DB 02838 AA AA
258
56 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 22. SERVice card ( SERV ) screen
Fig. 23. Allowed Boards Equipment Types Screen
ED
04
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 24. MoDemodulator card ( MD 128 1W1 ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
58 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 25. RRA card ( RRA 1W1 ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
59 / 258


Fig. 26. Selectable modules view
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
60 / 258

Fig. 27. Board view MD 128 1W1 Screen
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
61 / 258

Fig. 28. Board view RRA 1 ( Electrical Interface ) screen
Clicking twice on the below square in the left of the screen, the SDH Port view screen it opens ( see
1AA 00014 0004 (9007) A4 ALICE 04.10
In the same way in the upper square, the PDH Port view screen it opens ( see Fig. 30. on page 63 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
62 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 29. SDH Port view Electrical Interface ( RRA ) screen
Fig. 30. PDH Port view ( RRA ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
63 / 258


Fig. 31. Selectable Optical STM1 module view
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
64 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 32. Board view Optical module STM1 ( IS11 ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
65 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 33. SDH Port view Optical Interface ( Optical module STM1 ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
66 / 258

Fig. 34. Board view SERV screen

The screen above shows the external connector ( Auxiliary Service Channels ) relatives to the SERVice
card.
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking twice on the connectors symbol ( AUX ), the PDH Port view screen it opens ( see Fig. 35. on
page 68 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
67 / 258

Fig. 35. PDH Port view ( SERVICE ) screen
1AA 00014 0004 (9007) A4 ALICE 04.10
The screen above shows the Plesiochronous Physical Interface with the relevant alarms ( LOS and URU,
refer to Chapter Maintenance ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
68 / 258

Fig. 36. Power Supply Filter ( PSF 12 ) Board screen
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
69 / 258

Fig. 37. Subrack Transceiver ( SRTRI 1 ) screen

The screen above shows the Subrack SRTRI with two transceiver. Clicking twice one of the two
transceivers checked with the padlock symbol the screen it opens ( see Fig. 38. on page 71 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking twice one of the two transceivers checked with the padlock symbol the screen it open (see
Fig. 38. on page 71).
ED
04
957.207.022 A
3DB 02838 AA AA
258
70 / 258

Fig. 38. Transceiver card ( TRI 128 ) screen
1AA 00014 0004 (9007) A4 ALICE 04.10
In the screen above the operator can select the Four modules which the Transceiver is composed:
Receiver module 128 QAM ( Daughter 3 ).
Receiver module 128 QAM Space Diversity ( Daughter 4 ).
Local Oscillator module ( Daughter 1 ) related to the Rx side.
Local Oscillator module ( Daughter 2 ) related to the Tx side.
ED
04
957.207.022 A
3DB 02838 AA AA
258
71 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 39. Board view ( TRI 128 ) screen
Fig. 40. SDH Board view ( Rx ) screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
72 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 41. SDH Port view Rad_S ( Rx ) screen
Fig. 42. SRFANS Subrack Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
73 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 43. Fans card Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
74 / 258
6.2 Set and change or remove board

The boards can be set, changed, or removed by using the menu options of the Equipment view.
a)
Setting or changing a board
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.
Fig. 44. List of different boards relevant to an NE slot
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
This procedure can be done to replace an existing board with another type without
previously remove it.
Select the Modify option of the Equipment pull down menu.
A dialog box containing a list of different types of modules selectable is displayed.
Fig. 45. Example of boards change with a Lock representation
ED
04
957.207.022 A
3DB 02838 AA AA
258
76 / 258

b)
6.3 Board administrative state

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.
6.3.1 Setting a board in service
In the Equipment NE view, click on the board in order to select it.

In the Equipment pull down menu of Fig. 17. on page 49, select the Set in service option
A lock representation appears over the boards.
6.3.2 Setting a board out of service
In the Equipment NE view, click the board in order to select it.

In the Equipment pull down menu of Fig. 17. on page 49, select the Set out of service option. In
the confirmation window which appears, select the Ok pushbutton
A lock representation disappears over the boards.
6.3.3 Consulting a Boards Administrative state
1AA 00014 0004 (9007) A4 ALICE 04.10
The boards administrative (in service or out of service) state is indicated on the Board view as shown
in the following figure.
Fig. 46. Getting a boards administrative state
ED
04
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
The Soft 0 is RC Software and Soft 1 is EC Software.
The following window opens.
Fig. 47. Software Description dialogue box

The dialogue box contains as many folder sheets as the softwares in the selected board.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Close pushbutton to close the dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
78 / 258

6.4 Software description

6.5 Remote Inventory

This command is used to display the remote inventory data present in the NE and in a board.
In the Equipment pull down menu, select the Remote Inventory option
Two options are available ( see the following figure ):
Subrack level: Remote Inventory of the board inside Subrack

Board level: shows the remote inventory data for the selected board
6.5.1 Remote Inventory Subrack Level

This command allows to display the remote inventory of the Subrack
In the Equipment pull down menu, select the Remote Inventory => Subrack Level
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 48. Remote Inventory screen at Subrack Level
ED
04
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.
Fig. 49. Update Remote Inventory

If its OK is possible to select the Output Destination
Printer Destination
Printer
File (see Fig. 51. on page 80)
Output Format
Postscript
ASCII
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 50. Remote Inventory Output Destination
Fig. 51. Remote Inventory (file saved)
ED
04
957.207.022 A
3DB 02838 AA AA
258
80 / 258
6.5.2 Remote Inventory Board Level

This command allows to display the remote inventory of the Subrack

In the Equipment pull down menu, select the Remote Inventory => Board Level
A dialogue similar to that of Fig. 52. appears.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 52. Remote Inventory screen at Board Level

In the screen above are stored all the information relatives to an Equipment Board. When it isnt possible
to read the Remote Inventory information a RUTM (Replaceable Unit Type Mismatch) alarm is declared.
ED
04
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 53. Equipment Overview Subrack level
ED
04
957.207.022 A
3DB 02838 AA AA
258
82 / 258

6.6 Show supporting equipment

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 54. An example of a Board view
ED
04
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. ).
Fig. 55. An example of Port identification and alarm synthesis

The following information is provided:
port type (name)

port type (alarm status synthesis)
port symbol
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
By doubleclicking a Board view, it is also possible open its corresponding Port view ( see Fig. 57. on page
86 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
84 / 258

7.2 Board View Menu

By selecting the Board option in the menu bar ( see Fig. 54. on page 83 ), the complete Board pull down
menu is presented ( see Fig. 56. ):
Port Access:
Access the Port view. See para.7.2.1 on page 86 .
Change Physical Interface:
Not implemented
Show supporting equipment: Navigate to the upper subrack level.

See para.7.2.2 on page 87.
Fig. 56. Board menu options
1AA 00014 0004 (9007) A4 ALICE 04.10
These options are described in the next paragraphs.
ED
04
957.207.022 A
3DB 02838 AA AA
258
85 / 258
7.2.1 Port Access
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 57. After Port Access selection ( example ) of LHR N.E.
ED
04
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.

7.2.2 Show Supporting equipment

In the Board menu ( see Fig. 56. on page85 ), click the Show Supporting Equipment option to navigate
to the subrack that supports the selected Port view ( see Fig. 58. on page 87 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 58. Subrack level view
ED
04
957.207.022 A
3DB 02838 AA AA
258
87 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
88 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10

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
957.207.022 A
3DB 02838 AA AA
258
89 / 258
8.2 Port View Menu

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:
Set and show Performance Monitoring parameters and data.

See chapter 17 on page 199.
all TPs.
Physical Media:
Manage the physical setting of the TP of the port.

ALS Management
Show Optical Configuration
TX Quality Configuration
Single Fiber Configuration
LAPD Configuration ( see para 8.2.1 on page 91 )
MS Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Show supporting board: Navigate to the upper board level

It is described in this chapter, see para.7.2.2 on page 87
Refresh:
Set a request to the NE to upgrade the functional states.

See Fig. 69. on page 102
Ber Not Intrusive:
Manage the BER measurement data.
ED
04
957.207.022 A
3DB 02838 AA AA
258
90 / 258

8.2.1 Physical Media option menu

Selecting the Physical Media option by means Port menu bar ( see Fig. 60. on page 91 ) and then
selecting Lapd Configuration option, the LAPD Configuration screen of N.E. it opens ( see
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 60. LAPD Configuration option menu
ED
04
957.207.022 A
3DB 02838 AA AA
258
91 / 258

Fig. 61. LAPD Configuration screen

The screen above displays the LAPD configuration parameters of a selected RS TTP.
The selected TP is indicated in the left at the top of the screen.
1AA 00014 0004 (9007) A4 ALICE 04.10
For the description of the LAPD configuration refer to the para 5.6 on page 42 of this handbook.
ED
04
957.207.022 A
3DB 02838 AA AA
258
92 / 258
8.2.2 Optical Laser Parameters

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.
Fig. 62. Visualizing a port optical parameters

The laser ports are identified by three major characteristics:
STM Level: describes the input/output optical interface types: STM1
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
93 / 258
8.2.3 Automatic Laser Shutdown Configuration
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 63. Automatic Laser Shutdown Configuration
ED
04
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.

Fig. 64. Automatic Laser Shutdown Management

The dialogue box enables the following actions:
a)
Allow Automatic Laser Shutdown.

To allow the automatic laser shutdown functionality, select the ALS Enabled option of the ALS
Function: option button.
b)
Forcing the Laser to start or stop.
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
Force laser ON.

To carry out a laser forced ON, select the Laser Forced ON option of the ALS Function: option
button.
From the confirmation dialogue box that opens you can confirm or cancel the operation using
the Apply or Close push buttons.
2)
Force laser OFF.

To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function: option
button.
From the confirmation dialogue box that opens you can confirm or cancel the operation using
the Apply or Close push buttons.
c)
Delete / create the ALS management
d)
Enabling or Disabling Automatic / Manual Laser Restart.

To enable (disable) an automatic laser restart following an automatic laser shutdown (restart), select
the Enabled (Disabled) option of the ALS Auto Restart. The same procedure is applicable for the
ALS Manual restart : the manual restart permits to perform a laser restart for a single time period.
ED
04
957.207.022 A
3DB 02838 AA AA
258
95 / 258
Wait to restart time

The Wait To Restart Time: field indicating the delay period in seconds, occurring before an
automatic laser restart is launched (following an automatic shutdown). If the feature is supported,
this delay can be edited in the relative field (secs.). The restart time period for this equipment is fixed
to 70 secs.
f)
Als Manual restart

When the Als Manual Restart is Enable it is possible to enter two different commands: Manual or
Test Restart. If the feature is supported, the manual command immediately activates a single laser
restart: this command overrides the wait to restart time. The test restart is similar to the manual
restart but the laser remains ON for a longer time in order to make a measurement of the received
optical power.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 65. ALS current state
ED
04
957.207.022 A
3DB 02838 AA AA
258
96 / 258

e)

8.2.4 BER Not Intrusive

The management of not intrusive BER measurement capability is performed by means of the following
Port menu item, and is available only if a RST block is selected and the feature is supported by the NE.
Fig. 66. Ber Not Intrusive window (Start button)

The window allows the operator to start/stop collecting BER measurement data and to display them. The
field TP Name contains the user label of the RsTTP bidirectional under measurement.
The operator have to use START button to start the BER measurement Data collection.
When the window opens, the START button is compliant with the current situation about BER
measurement:
sensitive if the BER measurement data collection is still active
1AA 00014 0004 (9007) A4 ALICE 04.10
not sensitive if no BER measurement data collection is active
ED
04
957.207.022 A
3DB 02838 AA AA
258
97 / 258

Fig. 67. BER Not Intrusive window (Refresh/Stop button)

The REFRESH button allows the operator to retrieve update data. It is sensitive only if a BER
measurement is in progress.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
98 / 258

Fig. 68. BER Not Intrusive window (Overflow condition)

The information displayed is:
the number of violations detected till the moment of the request of the data (from start time)
the BER measurement from the start time and the elapsed time (duration of the current measurement
period where the period starts from start time)
The elapsed time is the period which the violations and the BER are related
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 68. shows the Overflow condition when the violations and the elapsed time exceed threshold defined
(32 bit).
ED
04
957.207.022 A
3DB 02838 AA AA
258
99 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
100 / 258
9 RADIO PROTECTION MANAGEMENT

Deals with the management of the Radio protections.
9.1 Overall RPS structure

9.1.1 Menu
The RPS parameters are displayed in the Radio menu of the menu bar ( see Fig. 70. on page 103 ),
providing access to:
Configure
Static Delay (Rx side)
Switch
Synthesis
Extra traffic
1AA 00014 0004 (9007) A4 ALICE 04.10
The first two entries are always available and display a secondary window.
ED
04
957.207.022 A
3DB 02838 AA AA
258
101 / 258
9.1.2 Information on RPS
RPS Protection Role (protected or protecting). .
RPS Protection Status (active, standby).

The label changes according to the state and the icon lights (red color) on when the state is active.
RPS Switch Type ( NoRequest, Forced ..).

The label changes according to the state.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 69. Refresh option offered by the PORT menu bar
ED
04
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:

9.1.3 RPS Configure Schema

Selecting the RPS => Configure option in the Radio menu ( see Fig. 70. ) and then, from the cascading
menu, the Schema option, a dialogue box appears ( see Fig. 71. on page 103 ).
Fig. 70. RPS Configure (Schema) option offered by the RADIO menu bar
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 71. RPS Configure Schema Dialog Box
ED
04
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:
the protection status of the protecting and/or protected ports
the configuration parameters for the selected RPS schema:
switching type ( single ended )
operation type ( not revertive/revertive )
RPS protection schema
Far end Mismatch ( alarm )
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Help button provides some useful information on the dialogue capabilities.
ED
04
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.

9.1.4 RPS Configure Units

This command is used to select the channel of highest priority when different channels have the same
switch request. The priority is from 0 to 9.
The management system may have the possibility to declare at most one channels, among the n protected
channels, as privileged. A privileged channel is maintained permanently bridged in TX direction to a
predefined channel when no switch request is active. In absence of other switch requests coming from
the remote end, the protecting section in the TX direction carries the privileged signal.
Selecting the RPS => Configure option in the Radio menu ( see Fig. 72. ) and then, from the cascading
menu, the Units option, a dialogue box appears ( see Fig. 73. on page 106 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 72. RPS Configure (Units) option offered by the RADIO menu bar
ED
04
957.207.022 A
3DB 02838 AA AA
258
105 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 73. RPS Configure Units Dialog Box
ED
04
957.207.022 A
3DB 02838 AA AA
258
106 / 258

9.1.5 RPS Switch

Selecting the RPS => Switch option in the Radio menu ( see Fig. 74. ) a dialogue box appears ( see
Fig. 75. on page 107 ).
Fig. 74. RPS Switch option offered by the RADIO menu bar
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 75. RPS Commands Dialog Box

This dialogue ( see Fig. 75. on page 107 ) allows to start protection commands on RPS protected ports.
It is subdivided into two parts.
ED
04
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Cancel button removes the dialogue.
ED
04
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.

9.1.6 Static Delay

The static delay alignment is necessary in order to have the hitless switching of the channel from direct
way to indirect way. The operation allowed is:
Automatic delay alignment (Rx side) both for direct way and indirect way
The alignment can be done on one channel at a time.

If one channel is not aligned, the automatic switching function is inhibited (only EWLBER).
The management Static Delay is performed by means of the following Radio menu option:
Fig. 76. Static Delay option offered by the RADIO menu

By selecting the RPS=>Static Delay option in the Radio menu ( see Fig. 76. ) and then, from the
cascading menu, the Rx Side option, a dialogue box appears ( see Fig. 77. on page 110 ), with four
columns scrolled matrix:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The operator may select an item of the scrolled matrix, that makes the entire row selected ( see Fig. 78. on
page 110 ).
ED
04
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 .
Fig. 77. Static Delay Screen

By selecting a channel and by entering Manual it is possible to insert manually the Static Delay in the
Direct Way and in the Indirect Way (Range 0255).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 78. Row Selected Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
110 / 258

Set button changed in sensitive when a field is selected .
9.1.7 RPS Synthesis

Selecting the RPS => Synthesis option in the Radio menu a dialogue box appears
Fig. 79. RPS Synthesis option offered by the Radio menu
Fig. 80. RPS Synthesis dialogue box
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
111 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Radio channel number
Port involved in a RPS Protection Schema
Protection role of the current port ( protecting, protected )
Status of the current port ( standby, active )
Switch Type (last operator command) (NoRequest, ManualSwitch, ForcedSwitch, Lockout,

HwForcing).
Automatic Switch (NoOne, WaitToRestore, EarlyWarning, LowBer, HighBer, SignalFail).
ED
04
957.207.022 A
3DB 02838 AA AA
258
112 / 258

Information shown in the screen:
9.1.8 RPS Extra Traffic

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
Fig. 81. RPS Extra Traffic screen
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 82. RPS Extra Traffic dialog box

The channel used for this operation is Channel 0. The operator can select this buttons:
Enable: Extra Traffic function is Enabled
Disable: Extra Traffic function is Disabled
ED
04
957.207.022 A
3DB 02838 AA AA
258
113 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
114 / 258

10 WAY SIDE TRAFFIC AND SERVICE CHANNELS PROTECTION

MANAGEMENT
10.1 Overall structure of WST and Service Channels protection

The WST protection management part is visible from any view.
A special menu (WST/Service Channel Protection) is displayed in the Radio menu of the menu bar,
providing access to:
Configure WST/Service Channels Protection
Switch
Synthesis
10.1.1 Information on WST and Service Channels protection
1AA 00014 0004 (9007) A4 ALICE 04.10
The configuration parameters for the WST and Service Channels protection are:
switching type
operation type
protection scheme
Signal switching conditions
external commands
ED
04
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)
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 83. RFCOH Configure
ED
04
957.207.022 A
3DB 02838 AA AA
258
116 / 258

10.2 RFCOH Configure

1:n
Fig. 84. RFCOH Configure Dialog Box (example)
Fig. 85. Search RFCOH Protection Schema

This windows is displayed clicking on Choose Schema button in Fig. 84.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
117 / 258

1:n
Fig. 86. RFCOH Configure with WST parameters (example)
1:n
Fig. 87. RFCOH Configure with Service Channels parameters (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
This dialog box allow to display for WST/Channels protection.

In the upper part of the windows there is a tree list providing all existing schemas with protecting elements
as root nodes and protected port (the protected port is not mandatory to choose a WST/Service Channels
protection schema). This operation fills the protecting and/or protected elements text fields with the
selected ports, the configuration parameters of the schema and starts the request to NE for the protection
status of the selected ports; a wait cursor is presented.
ED
04
957.207.022 A
3DB 02838 AA AA
258
118 / 258

The following information are displayed in this box to the user:
the protection status of the protecting and/or protected ports
the configuration parameters for the selected WST/Service Channels protection schema:
Switching type (Single ended)
Operation type (NoRevertive)
Protection schema (1+n)
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Help button provides some useful information about the capabilities of the dialog
ED
04
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 88. RFCOH Switch
ED
04
957.207.022 A
3DB 02838 AA AA
258
120 / 258

10.3 RFCOH Switch

Fig. 89. RFCOH Switch Dialog Box

This dialogue allow to start protection on WST/Service Channels protected ports.
This window is divided into two parts.
In the upper part there is a tree list providing all existing schemas with protecting elements as root nodes
and protected ones 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 determined when
protected port is chosen)
This operation fills the protecting and/or protected elements text fields with the selected ports.
The lower part provides the possible protection commands on the selected ports.
For each command the related release command i provided. Each set of commands (Lockout, Force to)
is available according the NE setting present in the resource file.
The OK button is enable when the ports involved and the protection command are selected. Otherwise
the OK button is disabled (grayed)
When an OK is clicked the operation is started and wait cursor is presented; at the end of the request the
dialog will disappear.
If some errors arise during the request, an error dialog is presented.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Help button provides some useful information about capabilities of the dialog.
ED
04
957.207.022 A
3DB 02838 AA AA
258
121 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10

10.4 RFCOH Synthesis
Selecting the RFCOH => Synthesis option in the Radio menu a dialogue box appears.
Fig. 90. RFCOH Synthesis
ED
04
957.207.022 A
3DB 02838 AA AA
258
122 / 258

Fig. 91. RFCOH Synthesis Dialog Box
Fig. 92. Search RFCOH Protection Schema

This windows is displayed clicking on Choose Schema button in Fig. 91.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
123 / 258

Fig. 93. RFCOH Synthesis Dialog Box (with parameters)

It is possible to have a complete view of all NE resources involved in a WST/Service Channels Protection
Schema.
It is possible by a dialog box containing a matrix to collect all the WST/Service Channels
protected/protecting TPs information.
These information are:
TPs involved in a RFCOH protection schema
Protection role of the current port: protecting, protected
Status of the current port: standby, active
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
1AA 00014 0004 (9007) A4 ALICE 04.10
The Help button provides some useful information about the capabilities of the dialog.
ED
04
957.207.022 A
3DB 02838 AA AA
258
124 / 258
11 RADIO PARAMETERS
1AA 00014 0004 (9007) A4 ALICE 04.10

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
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:
Fig. 94. ATPC option offered by the RADIO menu

By selecting the ATPC option in the Radio menu ( see Fig. 94. ), a dialogue box appears ( see Fig. 95. on
page 127 ) with four column scrolled matrix:
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
126 / 258

11.1 ATPC/Power and Threshold Setting

Fig. 95. ATPC Management screen

The operator may select an item of the scrolled matrix, that makes the entire row selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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.
Fig. 96. ATPC Configure screen
1AA 00014 0004 (9007) A4 ALICE 04.10
NB:
the HPTH is always greatier 3 dbm than LPTH
the EPTH is always greatier 3 dbm than ELPT.
ED
04
957.207.022 A
3DB 02838 AA AA
258
128 / 258

11.2 ATPC Configure

11.3 Power Setting

This function modifies the TX power level when Manual Operations are Not Active and ATPC Disable.
It is accessible across Set button ( see Fig. 95. on page 127 ) that opens the new screen ( see Fig. 97. on
page 129 ).
Fig. 97. Power Setting screen

Initially all modifiable fields shows the current value for the Tp selected in the previous screens. In the
screen above it is possible to modify Pout level ( Pout Value ) by uparrows and downarrows with step
of 0.1 dBm or by writing directly in the field. The new value is considered when Apply button is pressed;
value must be inside the range values visible in the screen otherwise an error message box appears.
Before the operation is performed, an explicit confirm is required by means of a confirmation box. The
capture of the Attribute Value Change message allows to update the fields of ATPC Configure screen.
11.4 Manual operation
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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 ).
Fig. 98. Manual Power Setting screen

Initially the TX Power Setting screen shows the current TX power for the Tp selected in previous window.
In this screen it is possible to modify TX power level ( Pout Value ) by uparrows and downarrows (with
step of 0.1 dBm) or by writing directly in the field. The new value is considered when Apply button is
pressed; value must be inside the range values visible in the screen otherwise an error message box
appears. No confirm box is shown.
The four automatic apply buttons are make for more quickly operations because when pressed, the PTx
value is incremented or decremented and immediately send to NE. However value must be inside the
range values visible in window otherwise an error message box appears.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Stop Manual button closes the Manual Operation Session.
ED
04
957.207.022 A
3DB 02838 AA AA
258
130 / 258

11.5 Power Setting in Manual Mode

11.6 ATPC Identifier

The ATPC Identifier item is always available, and it is sensitive only if the feature is supported by the
NE.
The Management of ATPC capability is performed by means of the following Radio menu:
Fig. 99. ATPC Identifier option offered by the Radio menu

Selecting the ATPC Identifier option in the Radio menu a dialog box appears ( see Fig. 100. on page
131 ).
The box contain the ATPC Single direction identifier that is sent ( Sent Identifier ).The Operator may
change the number by means uparrows and down arrows.
The value 0 corresponds at No Define that is equal whichever value.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 100. ATPC Single Direction Identifier
ED
04
957.207.022 A
3DB 02838 AA AA
258
131 / 258
11.7 Gain Management

The RX Gain level Management is performed by means of the following radio menu item:
Fig. 101. Gain option offered by the RADIO menu

By selecting the Gain option in the Radio menu ( see Fig. 101. ) a dialogue box appears ( see Fig. 103. on
page 133 ).
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.
If a manual operation is active, Stop Manual button is enabled and the toggle Manual operation in
progress is checked.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
132 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 102. Channel Radio Port Screen
Fig. 103. Gain Management Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
133 / 258

11.8 HOP Section Trace Management

The management of Hop section trace is performed by means of the following Radio menu item.
Fig. 104. Hop Trace option offered by the Radio menu

By selecting the Hop Trace option in the Radio menu ( see Fig. 104. ) a dialogue box appears ( see
Fig. 105. on page 135 )
Both fields Expected and Transmitted are modificable by the operator.
The value 0 is non define.
1AA 00014 0004 (9007) A4 ALICE 04.10
On OK button the modification is performed and the window closed.
ED
04
957.207.022 A
3DB 02838 AA AA
258
134 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 105. Hop Trace Management screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
135 / 258

11.9 Squelch Management

The Squelch management is performed by means of the following radio menu item:
Fig. 106. Squelch option offered by the Radio menu

By selecting the Squelch option in the Radio menu ( see Fig. 106. ) a dialogue box appears ( see
Fig. 107. on page 136 ).
By means of this screen the operator can make the squelch action in the MAIN, DIVERSITY, and the
REUSED channel by clicking on the near square.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on OK to confirm the operation.
Fig. 107. Squelch Management Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
136 / 258
11.10 Radio Abnormal Condition List

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 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
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 ).
Fig. 109. Radio Abnormal Condition List Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
137 / 258
11.11 Frequency Reuse Management

The Frequency Reuse Management is performed by means of the following radio menu :
Fig. 110. Frequency Reuse option offered by the Radio menu

This function is enabled only if the N.E. support the frequency reuse.
By selecting the Frequency Reuse option in the Radio menu ( see Fig. 110. ) a dialogue box appears
The screen of Fig. 111. on page 139 displayed the following information about the N.E.:
Radio Port
Carrier Status
Channel
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Associated Channel, NE User Label, Ne Location Name the operator can set the information,
about the Channel Frequency Reused.
ED
04
957.207.022 A
3DB 02838 AA AA
258
138 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 111. Frequency Reuse Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
139 / 258

11.12 Equalization Delay

The equalization delay management is performed by means of the following radio menu item:
Fig. 112. Equalization Delay option offered by the Radio menu

By selecting the Equalization Delay option in the Radio menu ( see Fig. 112. ) a dialogue box appears
By means of this screen the operator can set equalization delays for the main, diversity and the reused
channels either in automatic mode or in manual mode.
The automatic mode is performed by pressing the Auto button, in such a way the values in the fields
Main and Diversity are not taken into account and automatic delays are computed and shown in the
fields at the end of the procedure.
The manual mode is performed by setting the delays in the fields and pressing Set.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
140 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 113. Equalization Delay screen
ED
04
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:
Fig. 114. Frequency Agility option offered by the Radio menu

By selecting the Frequency option in the Radio menu ( see Fig. 114. ) a dialogue box appears ( see
Fig. 115. on page 142 ), with four columns scrolled matrix:
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
1AA 00014 0004 (9007) A4 ALICE 04.10
The screen allows only to Display the values of TX and RX Frequency.
Fig. 115. Frequency screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
142 / 258

11.14 V.C.O. State Management

The Voltage Control Oscillator State Management is performed by means the following Radio menu
option:
Fig. 116. Voltage Control Oscillator option offered by Radio menu

By selecting the Voltage Control Oscillator Status option by the Radio menu ( Fig. 116. ) a dialogue box
appears ( see Fig. 117. on page 143 ),with four columns scrolled matrix:
1AA 00014 0004 (9007) A4 ALICE 04.10
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 .
Fig. 117. Voltage Control Oscillator screen (only read)
ED
04
957.207.022 A
3DB 02838 AA AA
258
143 / 258
11.15 Power Measurement

The Power Measurements capability is performed by means of the following Radio menu option:
Fig. 118. Power Measurement option offered by the RADIO menu
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
144 / 258

11.15.1 Power Measurement Parameters

The Power Measurement Parameters screen ( see Fig. 119. ) allows the operator to set initial parameters
for the required measurement.
The Radio Port: matrix shows all the radio ports not actually set under measurement.
Measurement interval. The default is Days: 0, Hours: 0, Minutes: 0 those means a 7 days
measurement interval which is also the maximum allowed interval.
Sample time field is the period between two samples.
The last section of the dialog is referred to an optional Log file.
For default the log file is always created and a default path and name for this file is presented to the
operator. The default name is derived by the selected Radio Port.
The file name and path can be modified using the default browser started by Select file button.
The log file contains the sample values.
It records the measurement until a maximum dimension ( 7 days for a 2 sec. sample time).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 119. Power Measurement Parameters screen
ED
04
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. ).
Fig. 120. Power Measurement Graphic Screen

The Power Measurement Graphic is available only if the USM is connected to NE.
The screen above shows the current TX and Rx performance related to the two linked NE. Every window
correspond to a single NE channel.
When the screen is showed the operator is able to see the curves following the real time values of power
transmitted by the local and remote transmitters (TX) and moreover, the values of power received by the
remote and locale receivers (Rx).
The top graphic screen size shows the TX curves (local and remote), while the bottom size shows the Rx
curves (local and remote). Note that the colors represent the linked endpoint of the two NE; if the local
TX is blue, for example, the remote receiver has the same color.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 start time item is the first request time;
the stop time item is the interval time selected in the previous parameters window, added to start time;
time item is the current response time;
Log File item is the complete pathname of the file where the received values are stored.
ED
04
957.207.022 A
3DB 02838 AA AA
258
146 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10

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.
current TX local value and his current date.
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.
current TX remote value and his current date.
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.
current Rx local value and his current date.
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.
current Rx remote value and his current date.
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.
current Rx local diversity value and his current date.
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.
current Rx remote diversity value and his current date.
ED
04
957.207.022 A
3DB 02838 AA AA
258
147 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 121. Details Dialog screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
148 / 258
11.16 Power Measurement File Reading

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 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
149 / 258

Fig. 123. Name of File ( Log File ) selected screen

This screen allows only to display the Power Parameters.
In default status the file selected is USMmw2.0.1/_r01sr2sl01.txt .
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 124. Example of Power Measurement File Reading
ED
04
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.
Termination of an OH byte onto an auxiliary port or vocal channel.

There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead of OH
bytes or auxiliary port, depending on the context.
12.2 OH Connection overview

Here are described the possible OH connections
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 )
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
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:
create the OH TP involved in the operation
create the OH byte termination:
select the created OH TP
select the auxiliary port/vocal channel TP involved in the operation

After having deleted an OH byte termination, the involved TP have to be deleted.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
957.207.022 A
3DB 02838 AA AA
258
152 / 258

In Tab. 5. and Tab. 6. are show the RFCOH Termination Bytes.
OH Crossconnection

The operator can crossconnect OH bytes on SERVice and RRA boards.

The possible crossconnection types are:
unprotected bidirectional point to point
The steps an operator has to do in order to perform the crossconnection are the following:
create the OH TPs involved in the operation

create the OH crossconnection:
select type of crossconnection
select first OH TP involved in the operation
select second OH TP involved in the operation
After having deleted an OH crossconnection, the involved TPs have to be deleted.

Tab. 7. RSOHRFCOH Bytes crossconnections
RFCOH
BYTES
1AA 00014 0004 (9007) A4 ALICE 04.10
RSOH BYTES
ED
==>
E1
User Channel
Radio Order Wire
Radio User Channel
E1
rs Order Wire
F1
rs User Channel
Future Use
rs Future Use
National Use
rs National Use
04
957.207.022 A
3DB 02838 AA AA
258
153 / 258
12.3 Overhead views
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 Cross Connection See para.12.5 on page 157
OH TP deleting
OH Phone Parameters See para.12.7 on page 165.
Fig. 125. Overhead options offered by the Configuration menu
1AA 00014 0004 (9007) A4 ALICE 04.10
The options are described in next paragraphs.
ED
04
957.207.022 A
3DB 02838 AA AA
258
154 / 258

The Overhead Views allows to perform the previously presented operations.

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 Equipment field is possible the navigation in rack/subrack/board/port. By

doubleclicking, e.g. on a port, the contents of the port appear on the right side of the screen
( TP list ).
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 ).
OH Tp field displays the label selected on Search OH Tp to be created screen.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 126. OH TP creation Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
155 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 127. Search OH Tp to be created Screen
Fig. 128. OH TP insert
ED
04
957.207.022 A
3DB 02838 AA AA
258
156 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10

12.5 OH Cross Connection

Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH Cross Connection option.
The Cross-Connection Management dialog opens ( see Fig. 129. on page 158 ) and allows to start the
configuration.
In the following is showed a procedure to realize an example of O.H. CrossConnection Bytes:
Click on Create ; a new screen called Main Cross-Connection is opened ( see Fig. 131. on page
161 ).
Select on Type the bidirectional option.
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.
Click on OK ; the Search OH Tp screen is closed.
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.
Click on Search in the Cross-Connection Management screen to see the new

crossconnection created ( Fig. 130. on page 160 ).
ED
04
957.207.022 A
3DB 02838 AA AA
258
157 / 258
12.5.1 Cross-Connection Management dialog

See Fig. 129. on page 158
Fig. 129. CrossConnection Management dialogue box
Supported operations
After choosing one or more crossconnections/terminations, this dialog allows to:
Delete the selected xconnection/termination
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Unlike the normal crossconnections, the OH xconnections are automatically active at the moment of their
creation.
ED
04
957.207.022 A
3DB 02838 AA AA
258
158 / 258
The operation buttons availability follows some rules:

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
Not Supported operation
When used for OH purposes, the Cross-Connection Management dialog doesnt support the following
functionalities:
Protect cross connections/terminations: all the OH cross connections/terminations are

unprotected
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:
Cross Conn. Name

trailname of the 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
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 130. CrossConnection Management dialogue box ( After Search )
ED
04
957.207.022 A
3DB 02838 AA AA
258
160 / 258

N.B.
12.5.2 Main Cross-Connection dialog

See Fig. 131. on page 161 .
Fig. 131. Main CrossConnection dialogue box

According to the philosophy of offering only meaningful operations to the user, and being the OH
crossconnection operations a subset of those applying to the general cross connections (e.g.:protections
are not allowed), some fields of this dialog are disabled.
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
selection of the first TP involved in the crossconnection
selection of the second TP involved in the crossconnection
In order to do that the operator can either type in the involved TPs ID or use the TP Search dialog.
ED
04
957.207.022 A
3DB 02838 AA AA
258
161 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 132. Search for OverHead CrossConnection Input screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
162 / 258
12.5.3 Search OH TP dialog
1AA 00014 0004 (9007) A4 ALICE 04.10

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
Fig. 133. Selection of Search OH Tp Screen
ED
04
957.207.022 A
3DB 02838 AA AA
258
163 / 258
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.
OH Tp field displays the label of the selected OH Tp to be deleted.

Apply button is used to perform a delete request of the tp displayed in the OH Tp field. After having
performed the delete request, the OH Tp field is set to empty.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 134. OH TP deleting screen
Fig. 135. OH TP delete (selection)
ED
04
957.207.022 A
3DB 02838 AA AA
258
164 / 258

12.6 OH TP deleting

12.7 OH Phone Parameters

the OH Phone Parameters option.
The OH Phone Parameters dialog box opens ( see Fig. 136. ).
It allows to set the equipment phone number for the selective call by means of the scroll arrows. The
number is programmable between 10 to 99.
The Operator can to select the omnibus called ( 00 ) by means the handset.
Apply button is used to confirm the choice number.

Fig. 136. Phone Parameters screen
1AA 00014 0004 (9007) A4 ALICE 04.10
The TPHDEV module, related to the SERVice card allows another telephone number is available.
ED
04
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:
Fig. 137. Print to Printer Screen

Note: The facility to print the file by the printer is not available.
1AA 00014 0004 (9007) A4 ALICE 04.10
The dialog changes after clicking on File :
Fig. 138. Print to File Screen
ED
04
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.
13.1 Types of Loopbacks

The following loopbacks can be performed:
Line loopback (RRA)

A Line Loopback is a loopback where the incoming signal to a physical port is looped back onto
the outgoing signal (see Fig. 139. )
Internal loopback (RRA RFCOH)

An Internal Loopback is a loopback where the internal outgoing signal of a port is looped back
onto its internal incoming signal (see Fig. 140. and Fig. 141. )
RST
SPI
RPS
RST
RFCOH
MODEM
RT
RSPI
RRA
MD
TRI
Fig. 139. Loopback A: RRA line loopback
RST
SPI
RST
RPS
RFCOH
MODEM
RT
RSPI
RRA
MD
TRI
Fig. 140. Loopback B: RRA internal loopback
SPI
RST
RST
RPS
MODEM
RFCOH
RT
RSPI
RSPI
1AA 00014 0004 (9007) A4 ALICE 04.10
RRA
MD
TRI
Fig. 141. Loopback C: RFCOH Internal loopback

All of these are loop and continue loopbacks (the signal is sent back and continues its path).
ED
04
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
radio channels x,y
radio channels x,y

D4D12
D4D12
D1D3
RRA
RRA
SEMF
SEMF
D4D12
D1D3
F
MCF
MCF
1320CT
QB3
QB3
ECT for Station A

RECT for Station B
Fig. 142. DCC structure
DCC control channel uses two radio channels, in 1+1 protected configuration.
The couple of radio channels (x,y in Fig. 142. above) which carry the protected service channel (as well
as the WST channels, 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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
168 / 258

13.2 Caution: recoverable and unrecoverable loopbacks (with RECT)

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 other than x&y:

there are no limitations (as these channels are not used for DCC communication purposes):
loopbacks setup by the local or remote Craft Terminal can be always removed by the local or remote
Craft Terminal
loopbacks on channels x&y (used for DCC communication purposes) setup by the local or remote
Craft Terminal:
can be always removed by the Local Craft Terminal
with regard to the remotion possibility by Remote Craft Terminal :

a)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
LOOPBACKS NOT RECOVERABLE BY REMOTE CRAFT TERMINAL

A = RRA (RMD) line loopback (see Fig. 139. on page 167)
B = RRA (RMD) internal loopback (see Fig. 140. on page 167)
C = RFCOH (RMD) Internal loopback (see Fig. 141. on page 167)
Read carefully text to interpret correctly this figure
Fig. 143. EC position with respect to loopback points and consequent unavailability by RECT (CHx/y)
ED
04
957.207.022 A
3DB 02838 AA AA
258
169 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Read carefully text to interpret correctly this figure
Fig. 144. Allowed and not allowed loopbacks by RECT (CHx/y)
ED
04
957.207.022 A
3DB 02838 AA AA
258
170 / 258
EC
EC
BB
1320CT
or OS
RT
STATION 3
RT
NOT ALLOWED LOOPBACKS

(NOT RECOVERABLE BY RECT)
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
A = RRA (RMD) line loopback (see Fig. 139. on page 167)

B = RRA (RMD) internal loopback (see Fig. 140. on page 167)
C = RFCOH (RMD) Internal loopback (see Fig. 141. on page 167)
EC
BB
EC
BB
STATION 1
STATION 2
RT
13.3 Loopback management starting from Port view menu

N.B.
There are two modalities for the loopback management:

a)
starting from Equipment View menu (described in para.13.4 on page 178)
b)
starting from Port View menu (described in this para.13.3)
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:
Port Loopback Configuration
Loopback Management
13.3.1 Port Loopback Configuration

(Select the Rack=>Subrack=>Board)
The first operation is to select an object where will be managed the Loopback. In this example has been
selected the RST block.
Selecting the Loopback option in the Port menu (see Fig. 145. ) a dialogue box appears
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 145. Port Loopback Configuration option.
ED
04
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. )
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 146. Port Loopbacks Configuration Screen.
ED
04
957.207.022 A
3DB 02838 AA AA
258
172 / 258

13.3.2 Loopbacks Configuration

13.3.3 Loopback Management

Before to manage the Loopbacks is necessary to select an object. In this case has been selected a RST
block (see Fig. 147. )
13.3.3.1 Loopback Create
Selecting the Loopback Management (see Fig. 147. ) option in the Port =>Loopback menu a dialogue
box appears (see Fig. 148. )
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 147. Loopback Create (Loopback on RST)
ED
04
957.207.022 A
3DB 02838 AA AA
258
173 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 148. Loopback Create Dialog box
Click the Create button.
Fig. 149. Loopback Create Choose Tp
Click Choose Tp button.
ED
04
957.207.022 A
3DB 02838 AA AA
258
174 / 258

Fig. 150. Loopback Create Tp search screen
1AA 00014 0004 (9007) A4 ALICE 04.10
After the Tp selection click OK button to confirm.
Fig. 151. Loopback Create Tp selected
ED
04
957.207.022 A
3DB 02838 AA AA
258
175 / 258

Click OK button to confirm.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 152. Loopback Create Loopbacks selected
Fig. 153. Loopback Create (see RST block)

When a Loopback has been created, the symbol L appears.
ED
04
957.207.022 A
3DB 02838 AA AA
258
176 / 258

13.3.3.2 Loopback Delete

Selecting Loopback Management in Port=>Loopback menu (see Fig. 154. ) a dialogue box appears
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 154. Loopback Delete Menu
Fig. 155. Loopback Management Delete TP

Select in Current Loopbacks Table field the Loopback to delete and click Delete button to confirm the
operation.
ED
04
957.207.022 A
3DB 02838 AA AA
258
177 / 258
13.4 Loopback management starting from Equipment view

There are two modalities for the loopback management:
a)
starting from Equipment View menu (described in this para.13.4)
b)
starting from Port View menu (described in para.13.3 on page 171)
From the Operators point of view, the modality starting from Port View menu is of easiest
execution.
13.4.1 Loopback Create

Select the Loopback Management option in the Configuration menu (see Fig. 156. ) a dialogue box
appears (see Fig. 157. on page 179)
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 156. Loopback Management (Configuration menu)
ED
04
957.207.022 A
3DB 02838 AA AA
258
178 / 258

N.B.

Fig. 157. Loopback Management Dialog box
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the Create button and new dialog box appears (see Fig. 158. )
Fig. 158. Loopback Configuration Dialog Box (Port level)
ED
04
957.207.022 A
3DB 02838 AA AA
258
179 / 258

Click the Choose Tp button to select a Termination Point (see Fig. 159. )
Fig. 159. Loopback Management Search Termination Point (TP)
1AA 00014 0004 (9007) A4 ALICE 04.10
Click OK button to confirm and the Fig. 160. on page 180 appears.
Fig. 160. Loopback Management Termination Point selected
ED
04
957.207.022 A
3DB 02838 AA AA
258
180 / 258
The TP selected is into Termination Point field.

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. )
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 161. Loopback Management Termination Point List
ED
04
957.207.022 A
3DB 02838 AA AA
258
181 / 258
13.4.2 Loopback Delete

Select the Loopback Management option in the Configuration menu (see Fig. 162. ) a dialogue box
appears (see Fig. 163. on page 182)
Fig. 162. Loopback Management (Configuration Menu)
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Fig. 163. Loopback Management Delete Termination Point
ED
04
957.207.022 A
3DB 02838 AA AA
258
182 / 258

14 EXTERNAL INPUT AND OUTPUT POINT MANAGEMENT

This chapter describes how to display and set the input/output environmental alarms (housekeeping
alarms),
An external input point is an environmental alarm (also called housekeeping alarm).It corresponds to an
external event that is monitored by the NE. A number of relays on the NE are dedicated to monitor any
changes in the environment, for example: fire, flood , etc.
An external output point is used to control an NE contact (i.e. relay) connected to a detector. An external
output point is independent of external input points.
The following operations can be undertaken in this section:
Displaying external points,

Expanding or reducing the external point list,
Configuring input and output external points.
14.1 Displaying external points

From the Views pull down menu, select the External Points option as shown in the following figure.
Fig. 164. Opening the External Points view.
1AA 00014 0004 (9007) A4 ALICE 04.10
After selecting this menu option, the External Points view is displayed in the current window instead of the
current view.
ED
04
957.207.022 A
3DB 02838 AA AA
258
183 / 258

Fig. 165. External Points view.

The External Points view displays a list of all input and output points. The following information is given
for each external point:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
the external point type: Input or Output.

the user label: a userfriendly label associated with the configurable external point (see also
paragraph External points configuration).
the polarity assigned to the external point (see also paragraph External points configuration).
the external state: represents the alarm state. On when the alarm is raised, else Off. If the external
point is active (On), then a little flag is represented near to the status of the concerned point ( see
Fig. 170. on page 188 ).
04
957.207.022 A
3DB 02838 AA AA
258
184 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10

14.1.1 Expanding or reducing the External Points list.

The External Points view displays a complete list of the external points, but can also be restricted to the
input or output points.
To view the input points, the output points, or all external points, select the appropriate option from the
External Points pull down menu as shown in the following figure.
Fig. 166. Expanding or reducing the External Points list.
ED
04
957.207.022 A
3DB 02838 AA AA
258
185 / 258
14.2 External Point configuration
user label configuration

polarity configuration
external state. Can be set for output points (ON or OFF)
change of the associated Output Criteria. Only for External Output points
change of the associated Probable Cause. Only for External Input points (fixed value)
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.
Fig. 167. Configuring external points.

The following dialogue box opens, displaying information on the selected (Input or Output) external point.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 168. External Input Point Configuration dialogue box.
ED
04
957.207.022 A
3DB 02838 AA AA
258
186 / 258

The configuration operations available on external points are:

Fig. 169. External Output Point Configuration dialogue box.

By opening the dialogue, the current state of the selected External Point is shown.
The External Point Configuration dialogue box enables you to give a name to the external point by entering
a userfriendly label in the User Label entry box.
Select the Polarity of the external point (low or high) by using the arrow button. Low is a ground contact
in case of active command, while high is an open contact.
External state can be set for output points and forces the output to the ON (alarm) or OFF value.
The Probable Cause field, used for External Input Points only, is fixed to Housekeeping Alarm .
The Output Criteria option menu presents the criteria to be associated with the External Output Points.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
187 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 170. External Points view with flag symbol.
ED
04
957.207.022 A
3DB 02838 AA AA
258
188 / 258

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.
15.1 Alarm Configuration

The operations described in this chapter, which are mainly related to alarm setting, comprise:
Alarm Severity Assignment Profile management,

Allow/Inhibit alarm notification,
Alarm resynchronization.
15.1.1 Alarm Severity Assignment Profile (ASAP) management

Managed entities yield alarms when they malfunction. This section deals with the configuration of the
ASAPs. An ASAP is a list of alarm probable causes, to which Severity Profiles are assigned, predefined,
or set by the operator.
Three important notions are used:
The Probable Cause of an alarm,

The Severity of an alarm.
The Alarm Type (communication alarm, equipment alarm).
15.1.1.1 Alarm Severities

This option allows to configure and display an ASAP.
1AA 00014 0004 (9007) A4 ALICE 04.10
From the Configuration pull down menu, select the Alarm Severities... option .
Fig. 171. Configuring the Alarm Severity Assignment Profile (ASAP).
ED
04
957.207.022 A
3DB 02838 AA AA
258
189 / 258

The ASAPs Management dialogue box is displayed.
Fig. 172. ASAPs Management dialogue box.

The following default profiles are presented:
Profile All Alarms.With this profile all alarms are enabled .
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).
Profile 10001 can be set by the user.

Each individual alarm can be classified according to a criterion selected by the operator.
A default standard configuration is set.
NOTE: if this profile is not already present in the list, it is necessary to create it, by using the
dialog of Fig. 172. on page 190, selecting one existing profile and then clicking on the Clone
button.
Profile 0 is not used.
1AA 00014 0004 (9007) A4 ALICE 04.10
You can select an ASAP.

For ASAP 10001, it is then possible to choose the Detail, Modify, Clone, or Delete buttons.
For ASAP All Alarms , No Remote Alarms , Primary Alarms and No Alarms , it is only possible
to choose the Detail or Clone buttons.
Clone you can select to create new ASAPs.
By clicking the Detail, Modify, or Clone button, the ASAPs Edition dialogue box is displayed.
ED
04
957.207.022 A
3DB 02838 AA AA
258
190 / 258

Fig. 173. ASAP Edition dialogue box.

The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarm
severities.
The Probable Cause Families check buttons allow to filter the probable causes that will appear in the
Probable Causes Name list.
To find a particular probable cause, enter its name in the Search entry box at the bottom of the screen.
ASAPs are already defined in the system with default values for the assigned severities.
You can modify the severity associated with each probable cause. To do this, select the probable cause
whose severity level you wish to modify.
Then click the option button: Service Affecting (not protected probable cause), then Non Service Affecting
(protected probable cause), and then Service Independent (not used). For each option the severity can
be chosen among Critical, Major, Minor, Warning, Nonalarm, or Not used. A Nonalarm
probable cause corresponds to no alarm issued for this probable cause.
When selecting Details the assigned severity is only shown and can not be modifies.
After finishing configuring ASAP, press the OK button, to confirm the settings and close the dialogue box,
or the Cancel pushbutton to cancel the new settings and close the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
To take a profile modification into account, it is mandatory to perform a resynchronization of

the alarms. During this resynchronization, the severity of each alarm is updated. Otherwise,
the severities are updated only when modified or new alarms are issued by the NE.
ED
04
957.207.022 A
3DB 02838 AA AA
258
191 / 258
15.1.1.2 Set Alarm Severities
Only the alarms relative to the selected object will be set.

To select the object in exam, then select the Set Alarm Severities... option, from the Configuration pull
down menu.
Note: the Set Alarm Severities... option is accessible only if an object has been selected.
The Set ASAP dialogue box is displayed ( see Fig. 174. ). The ASAP operative on the TP is highlighted.
You can select an ASAP. Then it is possible to choose only the Detail button.
By clicking the Detail button, a dialogue box is displayed.
The Alarm Severity Assignment Profile dialogue box displays a list of the probable causes and a list of the
alarm severities.
Click on OK to send the selected ASAP to the TP of the selected Board.
Note: the change of ASAP configuration must be done one by one, for each single object ( for example
for each single TP of one board ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 174. Set ASAP dialogue box.
ED
04
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).
15.1.2 Allow/Inhibit Alarm Notifications

The system provides facilities to allow/inhibit the spontaneous notifications of the incoming alarms.
g)
To inhibit alarm notification,

Select the Supervision pull down menu. Then you can select the Inhibit Notifs option from the
Alarms pull down menu as shown in the following figure.
Fig. 175. Inhibit alarm notification

From the confirmation dialogue box which opens, you can confirm or cancel the operation by using
the Ok or Cancel pushbutton respectively.
The labels of the alarm panel are greyed out to inform the operator that alarms have been inhibited.
N.B.
h)
Inhibiting alarm notification means that alarms are not forwarded to the CT, but are still
generated by the NE.
To allow alarm notification

Select the Supervision pull down menu. Then you can select the Allow Notifs option from the Alarms
pull down menu as shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 176. Allow alarm notifications

From the confirmation dialogue box which opens, you can confirm or cancel the operation by using
the Ok or Cancel pushbutton respectively.
ED
04
957.207.022 A
3DB 02838 AA AA
258
193 / 258
15.2 Alarms surveillance
It is possible to show all alarms or to filter the alarm report.

Select the Diagnosis pull down menu. Then you can select the following options from the Show pull down
menu (see the following figure):
NE Alarms:
all NE alarms are listed in the Alarm Surveillance report that is

activated
Object Alarms:
only the alarms of the selected object are listed in the Alarm Surveillance
report
Subtrees Alarm:
only the alarms of the selected object and of its respective subtrees are
listed in the Alarm Surveillance report
Equipment Alarms:
only the alarms of the equipment management are listed in the Alarm
Surveillance report
Transmission Alarms: only the alarms of the transmission management are listed in the Alarm
Surveillance report
External Points Alarms: only the alarms of the input external point management are listed in the
Alarm Surveillance report
In the current release, all NE alarms are listed also when selecting a filter option.
Fig. 177. N.E. Alarms option.

Selecting the Alarm Surveillance, a report is displayed as typically shown in Fig. 178. on page 195.
1AA 00014 0004 (9007) A4 ALICE 04.10
This view first shows a synthesis of the NE alarms.
ED
04
957.207.022 A
3DB 02838 AA AA
258
194 / 258

This chapter describes the access to the Alarm Surveillance information of the NE.

Fig. 178. Alarm Surveillance screen.

The information supplied help the operator, typically during troubleshooting operation, presented in this
handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
A detailed description is given in the AS Operators Handbook.
ED
04
957.207.022 A
3DB 02838 AA AA
258
195 / 258
15.3 Abnormal Condition List
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.
Fig. 179. Abnormal Condition List menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 180. Abnormal Condition List screen.

The screen above ( Fig. 180. on page 196 ) shows a Type of forcing relative to the Protection Unit ( Named
PU ) of the Protection Group .
ED
04
957.207.022 A
3DB 02838 AA AA
258
196 / 258

This option allows to relieve the abnormal conditions related to the N.E..

16 EVENT LOG MANAGER

From the Network Element context views, perform the following operations to gain access to the Events
Log file:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
For further details, refer to the ELM Rel.5.0 Operators Handbook.
04
957.207.022 A
3DB 02838 AA AA
258
197 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
198 / 258
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 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 182. An example to access to the Performance Monitoring

The Performance Monitoring domain on the NE covers the monitoring of the counter values for trail
termination points and connection termination points.
Examples of these counters are the Errored Seconds (ES) and Severely Errored Seconds (SES) ones.
ED
04
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 counting interval for each performance measurement point.
Collection of the performance data.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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.
17.1.2 Supported Performance Counters

The NE uses performance counters to count the transmission errors.

A set of performance counters is provided according to the Termination Point (TP) where the performance
measurement is made.
The user can start a performance monitoring on one or several subsets of counters for each TP; it is not
possible to start the performance counters individually.
The following performance counters are supported:
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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.
Performance Monitoring can be started at any time.

As soon as a Performance Monitoring is started on the Craft Terminal, the current PM data is collected
on the I/O boards, and increments the performance counters whenever an error is detected.
The performance data counted is evaluated every quarter of an hour or every 24 hours and is stored there
in a history log.
When the user disables the monitoring of a TP within the first 10 minutes of a 15-minute period, the PM
data of the previous monitoring interval night have not been received yet.
Since the PM data is not stored after monitoring is disabled, the PM data of the previous interval would
be lost in this case.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
202 / 258

A monitoring period of a given granularity is associated with each performance counter.

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:
15 min. (explicit clearance):

A TCA is reported once only in the Alarm Manager, even if the same threshold is crossed several
times a day.
The TCAs are automatically cleared by the system after one error-free 15 min. interval.
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 following limitations apply to explicit clearance:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Additionally, an explicit clearance of the TCAs for all granularity periods is done if any of the following
events occurs during the current interval:
the current data instance is deleted,
the counters are reset,
the thresholds are increased above (current values of the counters).
ED
04
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:
NE15, near end 15 minutes page

NE24, near end 24 hours page
1AA 00014 0004 (9007) A4 ALICE 04.10
Each dataset has to be configured independently of the others.
ED
04
957.207.022 A
3DB 02838 AA AA
258
204 / 258

17.2 Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 183. PM Configuration dialogue box
ED
04
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).
Lock Data Collection. Not supported

If Lock is selected, PM remains enabled but data collection is stopped. All history performance
data remains available. All current values are set to zero.
EML OS Monitoring (accessible from SH only)

Not available for Craft Terminal.
Notifications
UAT (available for 24 h granularity only)

For 24 h granularity, UAT (UnAvailable Time) notifications are created, if enabled. This
notification results in an UAT alarm in the Alarm Surveillance.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
206 / 258


17.3 Display Current Data

Select the Port menu option and open the Current PM Data dialogue (see Fig. 184. on page 208) by
clicking the Display Current Data menu option.
This Current PM Data dialogue is used to show the results and status of the Performance
Monitoring counters.
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:
15 min., near end and far end 15 minutes page

24 h, near end and far end 24 hours page
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following items are indicated for each entity:
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
Indicates which threshold table is assigned to the entity.
Current Problem List

Indicates the current UAT (Unavailable) and TCA (ThresholdCrossed) alarms.
ED
04
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.
If no printer is installed,there is no error messages displayed to indicate this.

Press the Refresh button to update the window contents and display the latest data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 184. Current PM Data dialogue box

The screen above displays in the box at the top side the selected TP : r01sr1sl21port#01_RsTTP .
The Current PM data dialogue is possible only in Unidirectional way.
ED
04
957.207.022 A
3DB 02838 AA AA
258
208 / 258

N.B.

17.4 Display History Data

Select the Port menu option and open the PM History Data dialogue (see Fig. 185. on page 210) by
clicking the menu Display History Data menu option.
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.
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:
15 min., near end and far end 15 minutes page

24 h, near end and far end 24 hours page
1AA 00014 0004 (9007) A4 ALICE 04.10
The PM data displayed contain information concerning:
Interval End Time

in the dd.mm.yyyy hh:mm:ss format.
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
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.
If no printer is installed, no error messages one displayed to indicate this situation.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 185. PM History Data dialogue box
ED
04
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.

17.5 PM Threshold Table Selection

The PM Threshold Table Select dialogue (see Fig. 186. on page 212) pops up if the Attach button is
clicked in the PM Configuration dialogue (see Fig. 183. on page 205).
This dialogue can also be accessed by using the Configuration menu:
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.
The dialogue presents the list of the existing threshold tables.

The tables are individually indicated with a number.
Each table is dedicated to a specific entity, as reported in 17.6 on page 213. Each table can be modified
according to the operator selections.
The user can filter the threshold tables according to the filtering criteria granularity period. Select either
15 Minutes or 24 Hours for granularity. Select both granularities to list all threshold tables.
Press Filter to activate the filter criteria. The filtering area can be hidden by clicking Hide Filter.
The user can perform the following actions:
Modify / Display a threshold table.
Delete an existing threshold table

Mark the table in the list and click the Delete button.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
211 / 258
Attach the selected threshold table to a TP entity.

The Create action is not operative.

The user has to close the dialogue explicitly by clicking the button Close.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 186. PM Threshold Table Select dialogue box
ED
04
957.207.022 A
3DB 02838 AA AA
258
212 / 258

17.6 PM Threshold Table Modification or Display

17.6.1 Modification
The PM Threshold Table Modify dialogue (see Fig. 187. on page 214) pops up if a threshold table is
selected in the PM Threshold Table Selection dialogue (see Fig. 186. on page 212) and the Modify
button is clicked.
Carry out the following steps to modify a threshold table:
1)
Modify the upper threshold value (Value Up).

Tab. 8. shows the allowed maximum performance parameter values.
The lower value (Value Down) is fixed to 0 in the current release .

2)
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.
Note that the Name of a threshold table cannot be changed.

4)
Confirm the modifications with Apply.
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).
Explicitly close the dialogue with button Close.

17.6.2 Display
The PM Threshold Table Display dialogue (similar to Fig. 187. on page 214) pops up if a threshold table
is selected in the PM Threshold Table Selection dialogue (see Fig. 186. on page 212) and the Display
button is clicked.
Refer to the previous chapter for a description of the attribute values and types.
Tab. 8. Maximum Performance Parameter Values
Performance Parameter
Max. Value for 15-min. period
BBE, FEBBE on STM-1

boards
2,159,100
207,273,600
536,100
51,753,600
OFS, ES, UAS, FEES,
900
86,400
SES, FESES
810
78,760
BBE, FEBBE on all other

boards
1AA 00014 0004 (9007) A4 ALICE 04.10
Max. Value for 24-h period
ED
04
957.207.022 A
3DB 02838 AA AA
258
213 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 187. PM Threshold Table Modify dialogue box
ED
04
957.207.022 A
3DB 02838 AA AA
258
214 / 258

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.
18.1 General and descriptions

The Craft Terminal provides a set of functions which allow software package manipulation within NEs. A
downloading operation consists of establishing a session between the NE and a software server for file
transfer purposes. Actions can then be performed on the NE software version, including: update, delete,
activation and commit operations; it is also possible to roll back to the previous software version operation.
This way, the NE can follow the product evolution.
A backup/restore can also be done on the MIB of the NE. The MIB can be saved to or restored from the
mass storage of the EMLCORE indeed. The operator can use the NE simulator to prepare a configuration
of the NE MIB. This MIB is then saved in the NE MIB backup area, ready to be downloaded to the NE MIB.
The software download general principle is represented in the following figure.
Software Management
OPERATOR
MANAGER
Download
Control
Event
Report
AGENT
NE
Software Downloading
OPERATOR
Transfer
Request
SERVER
CLIENT
Binary & Data

Files
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 188. Software Download general principle
ED
04
957.207.022 A
3DB 02838 AA AA
258
215 / 258
18.1.1 Naming Conventions
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:
the active version: the software package currently running on the NE
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.
Software Management Function: A Software Management Function offers information on all

current software packages present in an NE. Indicators enable software management (running
package, activated package, etc...).
The following software version states are available:
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:
Software Download Manager function
Software Download Server function

The Software Download Manager function takes the downloading and management requests entered by
the operator and sends them to the NE. Thus, this function enables a download process to be initiated and
monitored by the operator. It manages the NE software releases and initiates software download
operations.
The Software Download Server is only responsible for fulfilling the requests received from the NEs and
performing software package file transfer operations to the NE.
18.1.2 Software Management functions
Usually, the operator will first ask for the present status of the software on a selected NE. Provided that
the status allows a download operation , the operator selects the new software package in the server and
triggers the download process. Afterwards, he will activate the package. If everything works well with the
newly activated package, the operator will do the commit operation. If problems are found with the newly
activated package, he can use the deactivate (revertback) operation to come back to the previous
software package and data.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following operations can be undertaken in this section:
ED
display Software Download information,

set / get the server address (not yet available),
initiate / Abort Software Package Download,
manage Software Packages within NEs.
04
957.207.022 A
3DB 02838 AA AA
258
216 / 258

The naming conventions used for Download Management are the following:
18.2 Software Download Manager menu

All software download operations are carried out from the Software Download Manager.
Fig. 189. Equipment view
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
Fig. 190. Download menu
ED
04
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.
Fig. 191. SW downloading initiate dialogue box

The following fields are available to search a specific package:
Server filter: to enter the selected server name.

Package filter: to enter the selected package name.
1AA 00014 0004 (9007) A4 ALICE 04.10
To display the selection, push on Apply filter(s) button.
ED
04
957.207.022 A
3DB 02838 AA AA
258
218 / 258

18.3 Init download

In the next field the list of the packages is displayed:
Server: the name of the server,

Package: the name of the package,
Version: the version number of the package.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 192. Software download in progress dialogue box

The Software download in progress dialogue box displays the name and type of the NE and the name of
the SW package, the total bytes, the current percentage, and the current file that is being downloaded.
Click the Abort pushbutton to abort the complete download transaction. From the confirmation dialogue
box that opens, you can confirm or cancel the abort operation.
Click the Close pushbutton to close the Software download in progress dialogue box at the end of the
software download.
ED
04
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.
Fig. 193. Software packages information dialogue box

The Software packages information dialogue box displays the name and type of the NE and the respective
package name and status of the committed and of the uncommitted software (if any).
You can select a software package by clicking its name.
The following fields are displayed:
Software package: name, release, version, edition of the package,

Operational state: enabled or disabled,
Activation date: last activation date and time,
Vendor: the supplier of the product,
Current state Action: commit or standby, together with an option button: none/Force/Activate/Delete
The Detail button allows to give more information on a selected software package.
1AA 00014 0004 (9007) A4 ALICE 04.10
By clicking the Detail button, the following window is displayed:
ED
04
957.207.022 A
3DB 02838 AA AA
258
220 / 258

18.4 Units information

Fig. 194. Software units details window

Then click the [+] symbol behind the software package to get more details.
Fig. 195. Software packages information window

Click Close to have the previous view displayed ( Fig. 194. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
In Fig. 193. on page 220 click:
ED
OK pushbutton to close the dialogue box,

Cancel pushbutton to close the Software packages information dialogue box,
Help pushbutton to access help on context.
04
957.207.022 A
3DB 02838 AA AA
258
221 / 258
18.5 MIB management
From the Download pull down menu, select the MIB management option. The following window is displayed:
Fig. 196. NE MIB management dialogue box

The following fields are 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.
Three pushbuttons allow to choose the desired action:
1AA 00014 0004 (9007) A4 ALICE 04.10
Backup: to backup the CT of the MIB present on the NE,

Restore: this function allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at a time on a given NE.
Delete: this action allows to delete a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a given directory of the FT server.
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
957.207.022 A
3DB 02838 AA AA
258
222 / 258

This function allows to backup and/or restore of the MIB.
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.
Fig. 197. Restart NE confirmation box

Click the OK pushbutton to confirm the restart NE operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click the Cancel pushbutton to abort the restart NE operation.
ED
04
957.207.022 A
3DB 02838 AA AA
258
223 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.207.022 A
3DB 02838 AA AA
258
224 / 258
19 SYSTEM SOFTWARE OVERVIEW
1AA 00014 0004 (9007) A4 ALICE 04.10

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
Channels and relation between boards
on page 227
Functional partitioning of the management
on page 228
Equipment management
on page 229
Base band shelf

on page 230
Fans shelf
on page 234
Transceiver shelf
on page 235
Physical Connectors
on page 236
Allowed and default equipment configurations

on page 237
Equipment protection management

on page 245
Compatible boards
on page 245
Power Supply Management

on page 245
External Points management

on page 246
Remote Inventory data

on page 247
Transmission management
on page 248
Radio management
on page 249
Performance Monitoring
on page 251
Radio Performance Monitoring
on page 252
Overhead management
RSOH bytes terminations
RFCOH bytes terminations
RSOHRFCOH bytes crossconnections
Phonic parameters
on page 253
on page 255
on page 255
on page 255
on page 255
Radio Overhead management
on page 256
Connection management
on page 257
Software management
on page 258
Communication and Routing management
on page 258
Security management
on page 258
Support management
on page 258
Test management
on page 258
ED
04
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
regenerator section layer

Fig. 198. shows an example of radio link composed of two Radio Terminal.
Optical fibre
or
Coaxial cable
Optical fibre
or
Coaxial cable
Radio terminal
Radio terminal
Fig. 198. Radio system
1AA 00014 0004 (9007) A4 ALICE 04.10
The main functions performed by the radio systems are the following:
Radio Regenerator Adaptation function (RRA)

It performs the SPI and RST functional blocks for STM1 signals and the RFCOH management.
Radio
The function converts a radio frequency signal into an internal logic level STM1 signal, and vice
versa. Specifically, the following functions are performed:
Modulation and TX functions in the transmit side
Demodulation and RX functions in the receive side
Hitless switch and logic

The function provides 1 protection channel for one of the N main signals against channelassociated
failures for both hardware failures and temporary signals degradation or losses due to propagation
effects (e.g. rain) within a radio section.
ED
04
957.207.022 A
3DB 02838 AA AA
258
226 / 258

19.1 Functional description

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
With and without Frequency Reuse

With and without Space Diversity
N+0 (N=1 .. 8)

N+1 (N=1 .. 7)

All the configurations support an electrical/optical type of line interface.
19.3 Channels and relation between boards

According to the configuration LHR NE can be composed up to 8 radio channels:
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:
the 2 Mbit/s Way Side Traffic (WST) channels

the service channels
1AA 00014 0004 (9007) A4 ALICE 04.10
They are transmitted using the radio frame complementary overhead (RFCOH, an arbitrary and
unstandardized extra SDH frame overhead).
ED
04
957.207.022 A
3DB 02838 AA AA
258
227 / 258
1AA 00014 0004 (9007) A4 ALICE 04.10
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 radio performance management domain : it is responsible of the additional performance

monitoring parameters in the radio physical layer.
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 connection management domain is in charge of the management of the crossconnections.
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 software management domain is responsible for management of downloading operation,

software version, backup and software error processing.
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).
the test management domain is responsible for loopback test.
ED
04
957.207.022 A
3DB 02838 AA AA
258
228 / 258

19.4 Functional partitioning of the management

19.5 Equipment management

The LHR NE is composed by one ETSI rack. It contains the following shelves:
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
Base Band 1+1 Shelf
SRBB11
Base Band N+0 Shelf
SRBBN0
(note 1)
Base Band N+1 Shelf

1+1 HET
Shelf
SRBBN1
(note 1)
Notes
They are logical entities, they correspond to

the same physical shelf: the Base Band shelf.
They are associated to different equipment
configurations, which require a different
configuration of the physical shelf.
Transceiver SRTRI1HET
(note 2)
1+1 HET Transceiver SRTRISD1HET

Shelf with Space Diversity (note 2)
1
N+0 / N+1 Transceiver SRTRIN
Shelf
(note 2)
They are logical entities, they correspond to

the same physical shelf: the Transceiver
shelf.
They are associated to different equipment
configurations, which require a different
configuration of the physical shelf.
N+0 / N+1 Transceiver SRTRISDN

Shelf with Space Diversity (note 2)
up to 2 Fans Shelf
SRFANS
(note 3)
(note 1) N is the number of the main channels (protected):
no spare channel in SRBBN0 configuration, so N minor or equal 8;
1 spare channel (protecting) in SRBBN1 configuration, so N minor or equal 7.

(note 2) In the transceiver with space diversity there are two receivers in each TRI board instead
of one as in the transceiver without space diversity.
1AA 00014 0004 (9007) A4 ALICE 04.10
(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
957.207.022 A
3DB 02838 AA AA
258
229 / 258
19.5.1 Base band shelf
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,
13, 15, 17, 19, 21: RRA (0 to 9) cards
slots
4, 6, 8, 10, 12,
14, 16, 18, 20, 22: MoDem (0 to 9) cards
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
Fig. 199. Base Band shelf

N.B. The number associated to RRA, MD and PSU is related to channel (0 9).
The SYStem COntroller (SYSCO) card (with the equipment and radio controller) contains the memory
device (MEMDEV), the external connectors for the QB3 and F interfaces and it can host a module
(HKDEV) to expand the number of housekeeping (up to 40 input contacts in all).
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
optical access module

(with optical drawer)
Fig. 200. STM1 access module

The MoDem (MD) card types contain the modulator and demodulator function units. Only 128 QAM is
supported in the current release. For each type of MD (supporting STM1 or sub STM1 signal), an IF
module is used in case of space diversity configuration as daughter board of the MD board. The same
physical module is used also in case of frequency reuse configuration, always as a daughter board, but
only for MD supporting STM1 signals. In case of space diversity with frequency reuse configuration with
MD supporting STM1 signals, two of these daughter boards are used.
The PSU boards power the Base Band shelf. Each PSU board supplies one MD and RRA (e.g. PSU0
supplies MD0 and RRA0/RRAS, PSU1 supplies MD1 and RRA1, and so on); moreover, the PSU boards
are connected in a protection scheme (only to RRA cards), so PSU0 protects a PSU1 failure and viceversa,
PSU2 protects a PSU3 failure and viceversa and so on.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
provisioned
provisioned
provisioned
provisioned
service channel and WST protection on channel 0 and 1: CH01SCPWP has to be provisioned
service channel and WST protection on channel 8 and 9: CH89SCPWP has to be provisioned.
1AA 00014 0004 (9007) A4 ALICE 04.10
The equipment types associated to base band shelf and shown at Q/F interfaces are described in the
following table.
ED
04
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
System Controller card
SYSCO
Massmemory device
MEMDEV
This module is contained in SYSCO card
up to 1
Additional
housekeeping device
HKDEV
This module is a daughter board of the SYSCO

card.
SERVICE card
SERV
up to 1 Tph device
Label
TPHDEV
Notes
This module is a daughter board of the

SERVICE card.
Ch. 0, 1 for Serv. Ch.

CH01SCP
prot. module
CH09SCP
prot. module
CH12SCP
prot. module
CH19SCP
prot. module
CH89SCP
prot. module
up to 1
Ch. 0, 1 for Serv. Ch. &
CH01SCPWP
WST prot. module
This is a logical equipment type contained in the

SERV unit.

CH09SCPWP
WST prot. module
CH12SCPWP
WST prot. module
CH19SCPWP
WST prot. module
CH89SCPWP
WST prot. module
RRA 1 WST card
(1xSTM1)
RRA1W1
This is a logical equipment type, it corresponds

to the RRA physical card. It allows to express
the way of working of the card: STM1.
RRA 0 WST card

(1xsubSTM1)
RRA0W0

to the RRA physical card. It allows to express
the way of working of the card: subSTM1.
1AA 00014 0004 (9007) A4 ALICE 04.10
up to 8
ED
04
957.207.022 A
3DB 02838 AA AA
258
233 / 258
Equipment Type
Label
RRA 1 WST standby

RRAS1W1
card (1xSTM1)

to the RRA standby physical card. It allows to
express the way of working of the card: STM1.
RRA 0 WST standby

RRAS0W0
card (1xsubSTM1)

to the RRA standby physical card. It allows to
express the way of working of the card:
subSTM1.
Opt.
STM1
module
This module is contained in RRA and RRA

standby cards.
up to 1
up to 8
Notes
S.1.1
IS1.1
MODEM 128 QAM

MD1281W1
STM1 1xWST card
up to 8
MODEM 128 QAM
MD1280W0
subSTM1 0xWST card
IF STM1 1 WST module

IF1W1CO
with combiner function

MD1281W1 card.
to the IF1W daughter board.
IF subSTM1 0 WST
module with combiner IF0W0CO
function

MD1280W0 card.
IF STM1 1WST module

up to 8
IF1W1XP
with XPIC function

MD1281W1 card.
up to 8
up to 8 PSU 48/60 V
2
Battery filter
PSL4860
PSF
19.5.2 Fans shelf

The Fans shelf contains the following units:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Num.
Equipment Type
up to 2
ED
Fan card
04
Label
FANSL
Notes
It includes four fans.
957.207.022 A
3DB 02838 AA AA
258
234 / 258

Num.

19.5.3 Transceiver shelf

The Transceiver shelf (see Fig. 201. ) contains the following units:
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
Fig. 201. Transceiver shelf

N.B. The number associated to TRI is related to channel (0 9).
Each TRI includes the transmitter and DC/DC converter modules and, as independent replaceable unit,
the receiver/s and the local oscillators (Rx and Tx).
The equipment types associated to these shelves and shown at Q/F interfaces are described in the
following table.
Num.
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.
power TRI128HP (note 1) It includes Tx, DC/DC converter modules.
RX128
up to 16 Local Oscillator TX and RX LO

module
(note 2)
It is included in the related TRI card.
(note 3)
It is included in the related TRI card.
(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.
1AA 00014 0004 (9007) A4 ALICE 04.10
(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
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.
Allowed Equipment Type

Optical module STM1 S1.1
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
RRA card (1xSTM1)

RRA card (1xsubSTM1)
RRAS card (1xSTM1)
RRAS card (1xsubSTM1)
RRA1W1
RRA0W0
RRAS1W1
Transceiver 128 QAM card
1AA 00014 0004 (9007) A4 ALICE 04.10
(note 1) 3 associated to G.703 interfaces, 1 to 2Mbit WST ones only if STM1 signals are
supported.
ED
04
957.207.022 A
3DB 02838 AA AA
258
236 / 258

19.5.4 Physical Connectors

19.5.5 Allowed and default equipment configurations

This paragraph provides information on the allowed equipment types and default configurations for all the
configurations used in LHR NE.
The following table shows the LHR allowed equipment types for racks and shelves at system start up time.
The bold enhanced configuration is the default value. Label column represents the string to be used at
the Q/F interfaces.
Rack.Shelf
position
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
237 / 258
Tab. 9. N+0/N+1 Base Band shelves slots configuration
Slot
Label
Creation/
Deletion
Replaceable
SYSCO
1.1
Massmemory device
MEMDEV
1.2
not provisioned
Housekeeping device
HKDEV
Auxiliary Service card
SERV
2.1
not provisioned
Ch. 0, 1 for Serv. Ch. prot. module
Ch. 0, 1 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Shelf type dependent, see Tab. 10.
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
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
Power Supply Filter

not provisioned
PSF
X=
26..35
not provisioned
48/60 V Power Supply unit
PSL4860
36
Power Supply Filter

not provisioned
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.
type and Space Diversity configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
type and not Space Diversity configuration.
ED
04
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
(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
1AA 00014 0004 (9007) A4 ALICE 04.10
(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
957.207.022 A
3DB 02838 AA AA
258
240 / 258

SRBBN0 / SRBBN1
Tab. 11. Base Band 1+1 shelf slots configuration

SRBB11
Slot
Label
Creation/
Deletion
Replaceable
SYSCO
1.1
Massmemory device
MEMDEV
1.2
not provisioned
Housekeeping device
HKDEV
Auxiliary Service card
SERV
2.1
not provisioned
(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
(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
1AA 00014 0004 (9007) A4 ALICE 04.10
Y=
9,
13,
17,
ED
7,
11,
15,
19
04
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
Power Supply Filter

not provisioned
PSF
X=
26, 27
34, 35
not provisioned
48/60 V Power Supply unit
(note 8)
PSL4860
36
Power Supply Filter

not provisioned
PSF
(note 1) See (note 1) of Tab. 9.

(note 3) Slots 5 and 21 are alternative (only channel 1 or 9 can be provisioned).
1AA 00014 0004 (9007) A4 ALICE 04.10
(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
957.207.022 A
3DB 02838 AA AA
258
242 / 258
Tab. 12. N+1/N+0 Transceiver shelves slots configuration

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
Local Oscillator TX module
LO
X.2
Local Oscillator RX module
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
1AA 00014 0004 (9007) A4 ALICE 04.10
X.4
ED
04
957.207.022 A
3DB 02838 AA AA
258
243 / 258
Tab. 14. 1+1 Transceiver shelves slots configuration
Creation/
Deletion
Replaceable
TRI128
TRI128HP
Y (note 1)
Local Oscillator TX module
LO
X.2
Local Oscillator RX module
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

Tab. 15. 1+1 Transceiver slots configuration shelf type dependent
SRTRI1HET / SRTRISD1HET
Slot
Shelf Type
Label
Creation/
Deletion
Replaceable
SRTRI1HET
not provisioned
SRTRISD1HET
RX module
RX128
X.4
Tab. 16. Fan shelf slot configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
SRFANS
ED
Slot
Label
Creation/
Deletion
Replaceable
not provisioned
FANSL card
FANSL
not provisioned
FANSL card
FANSL
04
957.207.022 A
3DB 02838 AA AA
258
244 / 258

SRTRI1HET / SRTRISD1HET
19.5.6 Equipment protection management

LHR NE doesnt support any equipment protection schema.

19.5.7 Compatible boards
The only compatible equipment are the transceivers.
to
from
TRI128
TRI128HP
TRI128
TRI128HP
19.5.8 Power Supply Management

Each subrack is powered independently in the following way:
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;
each module of the transceiver subrack is powered by internal DC/DC converter.
1AA 00014 0004 (9007) A4 ALICE 04.10
The equipment protection scheme associated to converters in load sharing is not represented at the Q/F
interfaces.
ED
04
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)
Each input contact can be labelled by the operator

The probableCause used by externalInputPoint is always housekeepingAlarm
Default value of perceived severity is defined in the alarmSeverityAssignmentProfile document
The operator can reassign the associated ASAP
The supportedByObjectList attribute points to the SYSCO sdhEquipmentR object (for
HK_IN_x)
The supportedByObjectList attribute points to the HKDEV (SYSCOs daughter board)
sdhEquipmentR object (for HK_IN_AUX_z)
Default value of locationName attribute is NULL string
Reference
User Label
Default value
Notes
HK_IN_x
CPIx
x = 1..22
HK_IN_AUX_z
CPI_AUXz
z = 23..40
Output Housekeeping (automaticExternalOutputPoint)
Each output contact can be labelled by the operator

Each output contact can be configured only as manual, they are driven by the operator and not
automatically by defined events
The supportedByObjectList attribute points to the SYSCO sdhEquipmentR object
Default value of locationName attribute is NULL string
Reference
User Label
Default value
Notes
HKy
CPOy
y = 1..10
1AA 00014 0004 (9007) A4 ALICE 04.10
The configuration of the input and output housekeeping will be preserved in case of restart.
ED
04
957.207.022 A
3DB 02838 AA AA
258
246 / 258

19.5.9 External Points management
1AA 00014 0004 (9007) A4 ALICE 04.10

19.5.10 Remote Inventory data

The Remote Inventory feature allows to store the information useful to identify all the components of the
product.
Also the information about the equipment type can be read from the remote inventory data (Unit
mnemonic field). All the boards must be provided in its own remote inventory data this type of information.
It is used to identify the actual equipment type and then, eventually, to provide an equipment mismatch
alarm (if the equipment type read from remote inventory data is different from the equipment expected
provided by the ECT/OS).
If it isnt possible to read the Remote Inventory information a Card Fail alarm is declared.
The Remote Inventory data are reported to OS/ECT using the specificPhysicalInstance attribute of the
sdhEquipmentR object. It is implemented as a 128 byte string (two bytes for each position) and its format
is shown in the table below.
Information field name
Position
Length
(Byte)
Encoding
Mandatory /
Optional
Format identifier
ASCII 22
Company identifier
12
ASCII
Unit mnemonic
36
ASCII
CLEI code
711
10
ASCII
Unit part number + ICS
1218
14
ASCII
Software part number + ICS
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
957.207.022 A
3DB 02838 AA AA
258
247 / 258
19.6 Transmission management

The transmission view of LHR NE is composed of the following transport entities:
up to 8 SDH ports
STM1 optical port
STM1 electrical port
up to 8 radio ports
STM1 port
sub STM1 port

The following Fig. 202. indicates the static association between SDH port and radio port.
SDH Port
Radio Port
n=1..8
Fig. 202. SDH and Radio Ports

Fig. 203. provides the supported functional blocks for LHR.

1AA 00014 0004 (9007) A4 ALICE 04.10

Fig. 203. Radio functional block diagram for LHR NE
ED
04
957.207.022 A
3DB 02838 AA AA
258
248 / 258

19.7 Radio management

The radio management domain is in charge of the radio specific part of the transmission. The functional
blocks of the whole NE are provided in para. 19.6.
The following Fig. 204. gives the mapping between the functional blocks of the Radio port and the radio
boards.
RRA
RPS
MD
RFCOH
TRI
Tx
Mod
RSPI
Dem
Rx
Fig. 204. Details of Radio Port
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
Wait to restore time
Not supported (0 sec.)
Signal switching condition
SF, HBER, LBER, EW
Switching time
<= 10 ms
Priority
Applicable
External commands
Manual switch, Force switch, Lockout protected
Tab. 18. 1+1 RPS protection type parameters

Parameter
Values
Architecture type
1+1
Switching type
Single ended
Operation type
Not Revertive
SF, HBER, LBER, EW
Switching time
1 ms
Priority
Not Applicable
External commands
Manual switch,
protecting
Force
switch,
Lockout
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
250 / 258
19.8 Performance Monitoring
1AA 00014 0004 (9007) A4 ALICE 04.10

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:
unidirectional performance monitoring of RS
associated collection periods are 15 minutes and 24 hours.

For each channel both line and radio side performance monitoring are supported in the current release
(in case of N+1 configuration the monitoring of the RRA spare channel is possible only if extra traffic is
supported).
ED
04
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:
the performance monitoring of the RSPI functional block;

the performance monitoring of the RPS functional block;
the monitoring of the RPS criteria; it is used as an estimation of the radio hop quality monitoring.
Performance monitoring of the RSPI functional block

Performance monitoring of the RSPI functional block is not supported by the current release.
Performance monitoring of the RPS functional block
Performance monitoring of the RPS functional block is not supported by the current release.
Monitoring of the RPS criteria
The hop section performance monitoring gives the quality of service of the radio section inside the
protection one. Due to the RPS location in the second generation radio NEs, it is not possible to perform
the monitoring of the hop section by means of standard methodologies. In order to provide the possibility
to compare the performance of the hop section of different radio channels, a RPS Criteria Monitoring is
provided.
This monitoring is based on the following primitives:
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):
Early Warning Second (EWS)

This event is defined as a one second period with at least one occurrence of EW.
Low BER Second (LBERS)

This event is defined as a one second period with at least one occurrence of LBER.
High BER Second (HBERS)

This event is defined as a one second period with at least one occurrence of HBER.
Signal Fail Second (SFS)

This event is defined as a one second period with at least one occurrence of SF.
A second is declared EWS, LBERS, HBERS or SFS according to the occurrence of the primitive with
higher priority (i.e. in contemporary presence in one second of EW, LBER, HBER, SF occurrences only
a SFS event is declared).
Monitoring of the RPS criteria is supported by the current release.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
Performance data collection and history treatment

For each radio specific type of performance monitoring the performance data collection and history
management are performed according to the ITUT Recc. G.784. One current register is required for 15
minutes and one for 24 hours. At least 16 recent registers are required for 15 minutes and one for 24 hours.
ED
04
957.207.022 A
3DB 02838 AA AA
258
252 / 258

19.9 Radio Performance Monitoring

19.10 Overhead management

As far as the LHR is concerned, the TSDIM External Specification Overhead Domain deals with the
management of (see Fig. 205. , it represents both standard overhead and radio specific overhead):
Terminations of RSOH or RFCOH bytes to auxiliary ports:
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 205. Overhead management functional view
ED
04
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 206. Overhead containment and connection relationships
ED
04
957.207.022 A
3DB 02838 AA AA
258
254 / 258

19.10.1 RSOH bytes terminations
Auxiliary interfaces provided by SERVICE card

See Tab. 3. on page 151.
Auxiliary interfaces provided by TPHDEV module

19.10.2 RFCOH bytes terminations
Auxiliary interfaces provided by SERVICE card

Auxiliary interfaces provided by TPHDEV module

19.10.3 RSOHRFCOH bytes crossconnections

19.10.4 Phonic parameters
Phonic extension is provided. It indicates if a channel in the NE is used to extend the phonic connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
255 / 258
19.11 Radio Overhead management
the 2 Mbit/s Way Side Traffic (WST) channels management, they represent a service traffic in
addition to the main one;
the service channels management.
Both the WST and service channels are transmitted using the radio frame complementary overhead
(RFCOH, an arbitrary and unstandardized extra SDH frame overhead).
2 Mbit/s WST channels management

The main features of the 2 Mbit/s WST Channels management are the following:
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.
Service Channels management

As the management of each single radio service channel (i.e. radioOrderWireCTPBid or
radioUserChannelCTPBid) uses the same approach used by the SDH overhead bytes, it is described in
the overhead section. Here after the management of the service channels as a whole and related
protection is covered.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
258
256 / 258

Radio overhead management deals with the following items:
WST and Service Channels protection

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
SF, HBER, LBER, EW for WST

SF, HBER, LBER for Service Channels
Priority
Not Applicable
External commands
Manual switch, Force switch, Lockout protecting
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.
19.12 Connection management
1AA 00014 0004 (9007) A4 ALICE 04.10
As far as LHR is concerned, Connection management is used only to manage Overhead

crossconnections. Only Unprotected Bidirectional PointtoPoint CrossConnections are supported.
ED
04
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.
19.14 Communication and Routing management

The Communication and Routing management is responsible to provide all the means to establish an
association in order to report an event to the managing systems.
For LHR NE the association is always permanent (it remains even if no information exchange exists
between peer application entities) and the reuse of the existing association is not allowed (the NE doesnt
reuse an existing association).
19.15 Security management

The Security Management functions are used by the OS to configure the access rights of the local terminal.
Being the use of these functions limited to the OS and not applicable to the F interface, the following only
shows the level of support at the Q interface.
The NE checks the OS address and verifies if it is in the allowed OS list. Only in this case the connection
with the OS is allowed, otherwise it is refused.
19.16 Support management

The Support management is responsible for the following functionalities:
event reporting: to notify events to the managing systems
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
19.17 Test management

The test management functions are used to control and monitor the Loopbacks. Refer to chapter 13 on
page 167 for details.
END OF DOCUMENT
ED
04
957.207.022 A
3DB 02838 AA AA
258
258 / 258

19.13 Software management

TABLE OF CONTENTS
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
3
4
4
4
2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 MAINTENANCE OF THE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 PROBLEMS WITH CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Troubleshooting by means of the Craft Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Alarm synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Details on alarms / statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
02
SC.3:LHR NE MAINTENANCE
957.207.022 A
3DB 02838 AA AA
24
1 / 24
1AA 00014 0004 (9007) A4 ALICE 04.10
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. 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
957.207.022 A
3DB 02838 AA AA
24
2 / 24


1 DOCUMENT GUIDE
1.1 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.
The Maintenance Manual is intended for all users.
9600LSY/LHR Rel.1.0&2.0 Technical Handbook (in particular its section MAINTENANCE)
The sections of this Handbook that should be read before starting are:
SECTION 1: Introduction
SECTION 2: LHR NE Management manual
1.2 Terminology
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.207.022 A
3DB 02838 AA AA
24
3 / 24

Chapter 2 Maintenance introduction
Chapter 3 Maintenance of the PC
Chapter 4 Problems with Craft Terminal

It indicates what to do if the CTequipment dialogue does not work.
Chapter 5 Corrective Maintenance (troubleshooting)

This chapter describes troubleshooting involving detection, location and correction of the
failures occurred in the equipment and the replacement of the defective parts.
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/LHR Technical Handbook (N.B.).
N.B.
Such paragraph Unit Replacement Procedures is available starting from

ED.02 of 9600LSY/LHR Technical Handbook.

Legend
n
m
blank
= new part
= modified part
= part unchanged
1AA 00014 0004 (9007) A4 ALICE 04.10
DOCUMENT EDITION
ED
01
02
m
Document guide
Maintenance introduction
Maintenance of the PC
Problems with Craft Terminal
Corrective Maintenance (troubleshooting)
02
03
04
05
957.207.022 A
3DB 02838 AA AA
24
4 / 24

2 MAINTENANCE INTRODUCTION

The maintenance procedures consist of the following steps:
PC Maintenance. See Chapter 3 on page 5
Problems with the Craft Terminal PC (shutdown and restart ). See Chapter 4 on page 5.
Equipment Corrective Maintenance (Troubleshooting). See Chapter 5 on page 7.
3 MAINTENANCE OF THE PC
With regard to maintenance PC, refer to the constructors documentation.
4 PROBLEMS WITH CRAFT TERMINAL

4.1 Purpose of the procedure
This procedure describes the Shutdown and restart the PC should the Craft Terminal SoftWare Product
not be working properly or not responding to the operators commands.
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.).
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
02
Such paragraph Unit Replacement Procedures is available starting from ED.02 of

9600LSY/LHR Technical Handbook.
957.207.022 A
3DB 02838 AA AA
24
5 / 24
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.207.022 A
3DB 02838 AA AA
24
6 / 24

5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING)

5.1 Purpose of this procedure
Troubleshooting involves detection, location and correction of the failures occurred in the equipment and
replacement of the defective parts.
5.2 Troubleshooting organization

The troubleshooting procedure is carried out with the help of some tables, reported hereinafter. Anyway
this method does not deal with the following issues (which are to be dealt with otherwise):
faulty electronic alarm indication, processing and detection circuits
faulty wiring (backpanel, connectors, etc.)
The following interfaces are present on the equipment for troubleshooting purposes:
Q3 interface for the Telecommunication Management Network ( TMN )
F interface for the Craft Terminal (Local or Remote)
Remote Alarm for the Supervisory Center
LEDs located on the NEs units.
Usually, maintenance is firstly done via software (TMN or Remote Craft Terminal), to locate the faulty
equipment and the faulty unit or the faulty path and then on site to physically correct the trouble.
WARNING:
The Power Supply Unit ( PSU ) and Power Supply Filter ( PSF ), must be always turnoff before
to begin the maintenance operation of Equipment
1AA 00014 0004 (9007) A4 ALICE 04.10
Maintenance can be done:
ED
from a TMN network management center
from a Remote Craft Terminal (RCT) management center
from a station supervisory center
on site.
02
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.
TOR: remote alarms of the Battery voltages ( Battery 1 or Battery 2 ).
TAND: remote alarms of the both Battery voltages ( Battery 1 and Battery 2 ).
INT: Remote alarm pertaining to the local (internal) alarm type.
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 ).
LOSQ3: Loss of dialog with OS.
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)
the equipment is not managed by a TMN or by a Remote Craft terminal (RCT)
2)
the equipment is not reachable by the remote manager (TMN or RCT) and therefore is isolated
3)
link problems are present
4)
the trouble has been located and a physical replacement is necessary.
In cases 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal 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.).
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
02
Such paragraph Unit Replacement Procedures will be available starting from

ED.02 of 9600LSY Technical Handbook.
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).
The NE is provided with a number of LEDs which indicate:

Centralized Equipment Alarms:

All alarms detected on the units are collected by a BaseBand Subrack ( SRBB11 ), which delivers
centralized optical indications (by means of LEDs on its front coverplate). Specifically, from top down:
Red LED: detection of an URGENT (MAJOR and CRITICAL) alarm
Red LED: detection of a NOT URGENT (MINOR) alarm
Yellow LED: alarm condition ATTENDED
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
Yellow LED: detection of an INDICATION (WARNING) alarm
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 YELLOW LED to light up

the RED LED to go off
On the front coverplate:
yellow LED ATTENDED to light up

red LEDs NOT URGENT (MINOR) and URGENT (MAJOR and CRITICAL) to turn off (free to
accept other alarms)
If both LEDs are on, the Attend command should be given twice : one to attend the NOT
URGENT (MINOR) alarm and one to attend the URGENT (MAJOR) alarm.
The troubleshooting operation is done by means of the Craft Terminal, and of the optical indicators (LEDs)
present on the NE.
The Craft Terminal is 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).
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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)
In case of alarm, access the Alarm Surveillance for troubleshooting.

Para 5.3.2.1 on page 13 describes this view.
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.
Troubleshooting with Automatic Laser Shutdown
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
24
10 / 24

5.3 Troubleshooting by means of the Craft Terminal.
5.3.1 Alarm synthesis indication

The following troubleshooting tables pertain to the alarm and status synthesis given in all the screens.
Tab. 2. Alarm Synthesis indication
Mnemonic
Critical alarm
Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation). NB1.
MAJ
Major (Urgent) alarm
Synthesis of alarms that needs immediate troubleshooting. NB1.
MIN
Minor (Not urgent) alarm
Synthesis of alarms for which a deferred intervent can

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

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

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

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

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

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

of the connection between NE and Craft Terminal
(SDH service link up).
RED LED: Identifies the Disable operational state of
the connection between NE and Craft Terminal (SDH
service link down).
Operation System
GREEN LED: Indicates that the N.E. is not managed

by the 1353 SH.
CYAN LED: Indicates that the N.E. is managed by the
1353 SH.
Manager level
GREEN LED: Indicates that the N.E. is managed by

the 1354 RM.
CYAN LED: Indicates that the N.E. is not managed by
the 1354 RM.
IND
TRNS
SUP
COM
O. S.
MGR
1AA 00014 0004 (9007) A4 ALICE 04.10
Maintenance
CRI
WNG
ED
Alarm / Status Description
02
957.207.022 A
3DB 02838 AA AA
24
11 / 24
NTP
AC
1AA 00014 0004 (9007) A4 ALICE 04.10
NB1:
ED
Alarm / Status Description
Maintenance
Network Time Protocol
GREEN LED: NTP protocol enabled and both NTP

servers ( Main and Spare ) are unreachable.
BROWN LED: NTP protocol disabled.
CYAN LED: NTP protocol enabled and at least one NTP
servers ( Main or Spare ) are reachable.
Abnormal Condition
GREEN LED: normal operating condition.

CYAN LED: detection of an ABNORMAL operative
condition.Type:forcing the unit into service, laser
forced ON or OFF, restoral attempt after an ALS.
Alarm Severity Assignment Profile can modify the assignment of each alarm root to the various
synthesis.
02
957.207.022 A
3DB 02838 AA AA
24
12 / 24

Mnemonic

5.3.2 Details on alarms / statuses

The troubleshooting proceed by checking the detailed information on the NE alarm by using the Craft
Terminal.
This information is obtained through the Alarm Surveillance data.
It is also possible to analyze the detailed alarms present on each TP of the Port views of the NE.
Alarms and statuses are also supplied in the Board view and Equipment view.
The following paragraphs provide more details on these views.
5.3.2.1 Alarm Surveillance
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).
Fig. 1. Alarm pull down menu.

After selection, a list is presented with a synthesis of the Alarm Surveillance and is immediately followed
by the detailed list of the Alarm Surveillance (see Fig. 2. on page 14).
1AA 00014 0004 (9007) A4 ALICE 04.10
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
957.207.022 A
3DB 02838 AA AA
24
13 / 24
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 2. Alarm Surveillance
Detailed information of some alarm are supplied.
ED
02
957.207.022 A
3DB 02838 AA AA
24
14 / 24

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
Wrong setting of the dipswitch
Battery Fail
BF
Battery Failure
And Battery Fail
ABF
Power and/or circuit
Tab. 4. RACKLHR rack alarms.

ALARM
LABEL
Backplane Failure
BKF
PROBABLE CAUSE
Wrong setting of the dipswitch
Tab. 5. SERV unit alarms.

ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Replaceable Unit Problem
Card Missing
RUM
Replaceable Unit Missing
Equipment Mismatch
RUTM
Replaceable Unit Type Mismatch
Firmware download in progress
SEP
Sfwr Environment Problem
Tab. 6. SYSCO unit alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Software Mismatch
VM
Version Mismatch
LAN alarm
LAN
Lan Failure
RC unreachable
ICP
Internal Communication Problem
SEP
Equipment Mismatch
RUTM
Replaceable Type Mismatch
ED
02
957.207.022 A
3DB 02838 AA AA
24
15 / 24
Tab. 7. Optical STM1 module alarms.

LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
Replaceable Type Mismatch
Unconfigured Equipment
UEP
Unconfigured Equipment Present

ALARM
Tab. 8. MD module alarms.

ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
UEP
Tab. 9. RRA / RRA S / HKDEV modules alarms.

ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
UEP
Tab. 10. FANS unit alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
ALARM
LABEL
PROBABLE CAUSE
Fan Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
UEP
ED
02
957.207.022 A
3DB 02838 AA AA
24
16 / 24
Tab. 11. TRI module alarms.

ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
SEP
UEP
Tab. 12. MEMDEV module alarms.

LABEL
ALARM
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Tab. 13. RX / LO module alarms.

ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
Tab. 14. PSU unit alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
ALARM
LABEL
PROBABLE CAUSE
Card Fail
POP
Power Problem
Card Missing
RUM
Equipment Mismatch
RUTM
UEP
ED
02
957.207.022 A
3DB 02838 AA AA
24
17 / 24
Tab. 15. PSF unit alarms.

LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
Battery fail / Missing
BF

ALARM
Battery failure
Tab. 16. TPHDEV / IF1W1COIF0W0CO / IF1W1XP
1AA 00014 0004 (9007) A4 ALICE 04.10
ALARM
LABEL
PROBABLE CAUSE
Card Fail
RUP
Card Missing
RUM
Equipment Mismatch
RUTM
UEP
ED
02
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:

Tab. 17. Alarm Surveillance information, general description
TITLE
DESCRIPTION
Perceived Severity
Indicates the severity assigned to the alarm with its respective color,
e.g.: MAJOR, MINOR, WARNING.
Event date and time
Indicates year, month, day and hours of the alarm.
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
Indicates whether the alarm is reserved (RSV) or not (NRSV),according to the

security management set.
Clearing status
Indicates whether the alarm condition is cleared (CLR) or is still active

(NCLR).
If cleared it has a green background.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
A detailed description of this application can be found in the AS Operators Handbook.
ED
02
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
Replace unit when possible (laser degrade)
Loss of frame
Check line (alignment problems due to line error)
AIS
Check connected equipment
Excessive BER
Check line (excessive line BER)
Degraded Signal
Check line (line signal degrade)
Loss of Pointer
Check line
Loss of multiframe
Check line
Signal label Mismatch
Configuration error
Far End Received Failure
Check farend equipment
Server Signal Failure
Check all the TU path. Alarm indicates AIS signal received on

the TU
Frequency offset
Check reference and connection between it and the equipment
Loss of timing source
Check reference and connection between it and the equipment
Resource Isolation
Check connection between NE and Craft Terminal
Communication Subsystem
Failure
Check Communication configuration (LAPD)
Push the RadioController Reset. If the alarm persists push the

Internal Communication ProbEquipment Controller Reset. If the alarm persists substitute the
lem
System Controller card.
TCA Alarm threshold cross
Check path / line section interested to the indication.
1AA 00014 0004 (9007) A4 ALICE 04.10
URU Underlaying Resource

Insert the board
Unavailable
ED
02
957.207.022 A
3DB 02838 AA AA
24
20 / 24

5.3.2.1.1 Port View alarms

It is also possible to analyze the detailed alarms present on the TPs of each port of the NE, following the
indication of the Port View chapter in the previous Section of this Handbook.
The Fig. 3. displays an example of a Port view.
For each TP of the Port a detail of the relevant alarms is presented.
On the port view the messages displayed on the bottom provide information about MSP protection and
Automatic Laser Shutdown state (if supported).
Fig. 3. Example of Port View alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
ALS state can be:
ED
OFF
ACTIVE
IN TEST ALS forcedly set ON or OFF or automatically every 70 seconds.
02
ALS in active (normal condition)

ALS active (Loss of signal alarm is present)
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 4. Example of Board View alarms and status
ED
02
957.207.022 A
3DB 02838 AA AA
24
22 / 24

5.3.2.1.2 Board view alarms and statuses
1AA 00014 0004 (9007) A4 ALICE 04.10

Tab. 19. Board alarms
DISPLAYED ALARM
NAME AND/OR ACRONYM
MAINTENANCE
RUM Unit missing
Insert the missing unit
RUP Unit Problem
Replace the unit
RUTM Unit type mismatch
Insert the right unit (unit inserted into a slot set with another
type of unit)
VM Version mismatch
Update the software version by downloading it.
POP Power Problem
Replace the board.
LAN LAN problem
Check LAN interconnection or replace the System Controller

card.
Internal dialogue problem in the System Controller card.It indiICP Internal

cates a temporary condition which will be restored. If the conCommunication Problem dition lasts it is due to a unit hardware failure. Try to reset it ; if
unsuccessful replace the System Controller card.
ED
02
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 5. Example of Equipment View alarms and status
END OF DOCUMENT
ED
02
957.207.022 A
3DB 02838 AA AA
24
24 / 24

5.3.2.1.3 Equipment View alarms

TABLE OF CONTENTS
1 DOCUMENT GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
3
4
4
4
2 SIBDL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Remote Access Service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Serial Cable Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
3 DOWNLOAD WITH SIBDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 SIBDL download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
02
020305
updated
A.FUMAGALLI ITACO
01
020111
validated
A.FUMAGALLI ITACO
E.CORRADINI
A.FUMAGALLI ITACO
E.CORRADINI
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
1 / 10
FIGURES
...............................................
...............................................
...............................................
...............................................
...............................................
8
8
9
9
10
TABLES
1AA 00014 0004 (9007) A4 ALICE 04.10
Fig. 1. SIBDL download procedure step 1

ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
2 / 10


1 DOCUMENT GUIDE
1.1 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 SIBDL Manual is intended for all users.
The sections of this Handbook that should be read before starting this document are:
SECTION 1: Introduction.
1.2 Terminology
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
3 / 10

Chapter 2 SIBDL configuration

It describes the configurations to be performed for SIBDL operation.
Chapter 3 Download with SIBDL

It describes how to download a N.E. software by using the SIBDL (Standard Image Binary
DownLoad) program.

Legend
n
m
blank
= new part
= modified part
= part unchanged
1AA 00014 0004 (9007) A4 ALICE 04.10
DOCUMENT EDITION
ED
01
02
m
Document guide
SIBDL configuration
Download with SIBDL
02
03
04
05
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
4 / 10


2 SIBDL CONFIGURATION
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.
2.1.2 Serial Cable Modem configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
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;
double click the Network icon;

select the Services folder in the Network window;
select Remote Access Service and the Properties... push button;
push the add button in the Remote Access Setup window;
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;
push the Browse... button;

search the folder where SIBDL is installed (Alcatel / SIBDL version / SIBDL /)and select the
mdmalca.inf file, then push the Open button;
push the OK button in the Install from disk window;

select the modem named Serial cable in the dialog box of window Install New Modem and push
the Next > button ;
put a tick against Selected ports and select one port only(the port must be available, i.e. not used
by another RAS modem) and push the button Next >;
follow the instructions;
push the OK button in the Add RAS Device window;
push the Continue button in Remote Access Setup window;
push the OK button in the Network window.
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
5 / 10
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
6 / 10

3 DOWNLOAD WITH SIBDL

This procedure describes how to download an NE software by using the SIBDL (Standard Image Binary
DownLoad) program.
3.1.1 SIBDL download procedure

A download based on the use of the SIBDL program is performed in the following operating phases:
Turn on phase, when activating the NE.
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)
Connect the Craft Terminal to the NE:
1AA 00014 0004 (9007) A4 ALICE 04.10
2)
ED
Using the Q interface, always connect both the F and Q interface.
Using the F interface, connect the F interface only.
Start the SIBDL by selecting Start > Program>Alcatel>SIBDLversion>SIBDL
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.
3)

4)
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>
1AA 00014 0004 (9007) A4 ALICE 04.10
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 .

In the NE_IP_address[ PPP TEL NET] field at the bottom:
If using F interface: type PPP and press ENTER
If using Q interface:
first option: type TELNET and press ENTER

In next step that appears, type the IP Address of the Craft Terminal
second option: type the IP Address of the NE
1AA 00014 0004 (9007) A4 ALICE 04.10
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)
In the new screen, type 8 (see Fig. 5. ) and press ENTER.

8)
1AA 00014 0004 (9007) A4 ALICE 04.10
10 ) Extract and reinsert the unit in exam to complete the operation.
END OF DOCUMENT
ED
02
SC.4: SIBDL
957.207.022 A
3DB 02838 AA AA
10
10 / 10

LSY Operator Rel.01 Ed04

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LSY Operator Rel.01 Ed04

Uploaded by

Copyright:

Available Formats

QUESTA PAGINA NON VA INSERITA NEL MANUALE

All rights reserved. Passing on and copying of this

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

A Ed.04 3DB 02838 AAAA Ed.04

No PAGINE TOTALI PER ARCHIVIAZIONE: 396 + 4

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

1AA 00014 0004 (9007) A4 ALICE 04.10

GENERAL TABLE OF CONTENTS ED.04

INSERIRE SEPARATORE 1 - INSERT REGISTER 1

SC.1: INTRODUCTION ED.04

INSERIRE SEPARATORE 2 - INSERT REGISTER 2

SC.2: LHR NE MANAGEMENT ED.04

INSERIRE SEPARATORE 3 - INSERT REGISTER 3

SC.3: LHR NE MAINTENANCE ED.02

INSERIRE SEPARATORE 4 - INSERT REGISTER 4

SC.4: SIBDL ED.02

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:

TOTALE FOGLI A4 TOTAL A4 SHEETS:

3DB 02838 AAAA TQZZA

QUESTA PAGINA NON VA INSERITA NEL MANUALE

All rights reserved. Passing on and copying of this

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

9600LSY REL.1.0 C.T. OPERATORS HANDBOOK

WARNING FOR A-UNITS OTHER THAN A-ITALY

Labels are done according to A-Italy binder format.

1AA 00014 0004 (9007) A4 ALICE 04.10

C.T. OPERATORS HANDBOOK

3DB 02838 AAAA TQZZA

SWP REG.9600LSY R.1.0

C.T. OPERATORS HANDBOOK

3DB 02838 AAAA Ed.04

3DB 02838 AAAA Ed.04

3DB 02838 AAAA Ed.04

C.T. OPERATORS HANDBOOK

SWP REG.9600LSY R.1.0

1AA 00014 0004 (9007) A4 ALICE 04.10

3DB 02838 AAAA Ed.04

C.T. OPERATORS HANDBOOK

3DB 02838 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

3DB 02838 AAAA TQZZA

Craft Terminal Operators Handbook

SWP REG. 9600LSY R.1.0

3DB 02838 AAAA Ed.04

Documentation set for 9600LSY/LHR Rel.1.0

9600LSY/LHR Rel.1.0 & 2.0 Technical Handbook

3DB 02839 AAAA

9600LSY/LHR Rel.1.0 & 2.0 Installation Handbook

3DB 02840 AAAA

9600LSY/LHR Rel.1.0 & 2.0 Lineup Guide

3DB 02841 AAAA

Interference investigation procedure

3DB 04165 EAAA

9600LSY Rel.1.0 CT Operators Handbook SWP 1.0

3DB 02838 AAAA

1320CT Version 1.3.x Basic Operators Handbook

3AL 79186 AAAA

1330AS Rel.5.0 Operators Handbook

3AL 71079 AAAA

ELM Rel.5.0 Operators Handbook

3AL 71081 AAAA