AWY User Manual V210 01ADRAFT PDF

User Manual
Alcatel–Lucent 9400AWY
7–8–13–15–18–23–25–28–38 GHz
short–haul low/medium capacity digital microwave radio links
9400AWY Rel.2.1
SWP 9400AWY IDU32
Version V2.1.0
WARNING
This issue is a DRAFT and still IN PREPARATION edition.
Before accessing and use any information herein contained
read carefully
Notes on ED.01A–DRAFT–IN PREPARATION
on page 554
3DB 16142 CAAA Ed.01A–DRAFT 1 / 576

Navigation principles
This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific
9400AWY Customer Documentation CD–ROM: for a comfortable navigation, two hyperlink types are
present:
– those inside the text window, marked by a blue rectangle around any cross–reference to a figure,
table, part, section, chapter, paragraph, numbered list, and page: by clicking such a blue rectangle,
you are led to the referenced component
– the bookmarks, present on the left side of the text window. Most of them represent the on–line
handbook “table of contents”. Bookmarks can be expanded (clicking on [+] ) or reduced (clicking on
[–] ). By clicking on one bookmark, you are led to the referenced part.
Moreover, at the bookmark window bottom, there are some red bookmarks: clicking one of them
opens the relevant enclosed document file.
WARNING: the bookmark window is not visible if you use Acrobat reader in “full–screen” modality.
For further information, refer to Acrobat reader help on–line.
If printed on paper by Users, it is suggested to divide this manual by numbered separators, for an easier
access to the information herein contained:
CONTENTS SEPARATOR
QUICK GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES
SECTION 1 : SYSTEM DESCRIPTION 1
SECTION 2 : NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 2
SECTION 3 : INSTALLATION AND COMMISSIONING 3
SECTION 4 : MAINTENANCE AND UPGRADE 4
SECTION 5 : APPENDICES 5
SECTION 6 : ENCLOSED DOCUMENTS 6
The standard Customer Documentation for 9400AWY Rel.2.1 SWP version V2.1.0 is in the English
language and is distributed to Customers only by the following CD–ROM:
CD–ROM TITLE Technical Code

DCP 9400AWY 2.1 CD_ROM 3DB 16142 AAAA
It contains, in electronic format (ADOBE ACROBAT pdf files), the following documents:
Document
Document Title Notes
Technical Code
9400AWY Rel.2.1 V2.1.0 User Manual 3DB 16142 CAAA this manual
9400AWY Rel.2.1 Installation Handbook 3DB 16142 BAAA
9400AWY Rel.2.1 TRS and SAT 3DB 16142 DAAA
Interference investigation procedure 3DB 04165 EAAA
For further information, please refer to Appendix C – Documentation guide on page 551
2 / 576 3DB 16142 CAAA Ed.01A–DRAFT

QUICK GUIDE
9400AWY Rel.2.1 V2.1.0 USER MANUAL
permitted without written authorization from Alcatel–Lucent
document, use and communication of its contents not
All rights reserved. Passing on and copying of this
Tab. 1. Quick guide

If you need immediate operative information on how to:
GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE
have a short description of the
read pages 33 to 49
system
get information on safety, EMC,
EMF, ESD norms and equipment read Appendix A on page 529
labelling
acknowledge cautions to avoid
read para.1–1.5 on page 32
equipment damage
have the description of equipment
interconnections, according to the read para.3–2.2 on page 363
configurations
for:
– IDU Main unit: read para.1–3.2 on page 67
– IDU Extension unit: read para.1–3.3 on page 73
get operative information regarding – E1 Protection box: read para.1–3.4 on page 75

the units in IDU (connectors, leds,
buttons) – Services Protection box: read para.1–3.5 on page 80
– Flash Card: read para.1–3.6 on page 89
– Distributor subracks: refer to the Installation

Handbook
read chapter 1–4 on page 93 , in particular:

get operative information regarding
– para.1–4.7 on page 118
ODU
– and para.1–4.8 on page 121
carry out antenna fine alignment read para.3–2.9 on page 443
INSTALLATION AND COMMISSIONING

carry out installation and
commissioning of equipment as
proceed as specified in para.1–2.6.1 on page 58
delivered from Alcatel–Lucent
factory

Tab. 1. Quick guide

MAINTENANCE

know the consequences of unit
extraction in IDU shelf
set and use the EOW functions of
read chapter 4–2 on page 453
the equipment
provision and manage spare parts read para.4–3.3 on page 458
carry out First Level maintenance

proceed as specified in chapter 4–4 on pag e 461
(system state display)
carry out preventive maintenance proceed as specified in para.4–5.3 on page 469
carry out corrective maintenance

proceed as specified in para.4–5.5 on page 471
(troubleshooting and repair)
TCO SUITE
know and use TCO functions read para.2–2.2 on page 146
ECT: GENERAL AND LOGIN & LOGOFF
know ECT and RECT characteristics read para.1–2.4 on page 50
have the functional description of

read para.2–3.6.1 on page 218
User Profile management
login proceed as specified in para.2–2.5.2 on page 177
logoff proceed as specified in para.2–2.5.3 on page 184
close the 1320CT application proceed as specified in para.2–2.5.4 on page 184
change own password (for all users) proceed as specified in para.2–3.6.2 on page 220
manage usernames and passwords

proceed as specified in para.2–3.6.3 on page 221
of all users (for administrator only)
set–up a remote connection
between CT and equipment, through
proceed as specified in Appendix B on page 541
a switched telephone line of the
standard Public Telephone Network.

Tab. 1. Quick guide
ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING

have an overview on menu tree

structure
manage equipment configuration open SECTION 2 – NE MANAGEMENT on page 139 and
then search the information according to the listed topics
set–up parameters for maintenance
use functions for SW management
proceed as specified in:

troubleshoot by ECT
EQUIPMENT PROVISIONING AND ITEM PART NUMBERS

for provisioning and P/Ns of:
– IDU shelves, read para.1–3.1 on page 66
do provisioning & know P/Ns at IDU – Flash Cards & Software Keys, read para.1–3.6.1 on
level (except installation materials page 89
and cables)
– equipment accessories, read para.1–3.7 on page 91
– upgrade kits, refer to Tab. 71. on page 509
do provisioning & know P/Ns at IDU

read paragraph IDU installation components of the
level for installation materials and
Installation Handbook
cables
do provisioning at ODU level

(transceivers only)
read suitable tables (according to configuration and

do provisioning & know P/Ns at
frequency bands) in paragraph Integrated or Not
ODU level for installation materials,
Integrated antenna installation components of the
antennas and related matters
do provisioning of software products read para.2–1.2.2 on page 141
do provisioning of cables for

read para.2–2.1 point b ) on page 144
PC–to–NE local connection
do provisioning for system
read para.C.2 on page 555
documentation

Tab. 1. Quick guide

SYSTEM UPGRADE

install a plug–in on IDU Main and/or
Extension unit
upgrade system configuration from

(1+0) to (1+1)
replace Flash Card to improve

system capacity
upgrade only NE with a newer SWP

proceed as specified in chapter 4–8 on page 525
version
upgrade only ECT with a newer

SWP version
upgrade both ECT and NE with a

newer SWP version
EQUIPMENT TECHNICAL CHARACTERISTICS
know system technical
specifications
know ODU P/Ns and related
frequency bands and frequency
shifters, antenna characteristics and
other ODU related matters
To find any other kind of information not listed in the above table, please refer to the TABLE OF
CONTENTS of this handbook, or, if you are using the pdf file of it, use the Acrobat Reader “Find” function.

TABLE OF CONTENTS
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SECTION 1: SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1–1 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1–1.1 Preliminary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1–1.2 History, applicability and purpose of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1–1.3 Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1–1.4 Safety–EMC–EMF–ESD norms and equipment labelling . . . . . . . . . . . . . . . . . . . . . . . 31
1–1.5 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1–2 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1–2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1–2.2 Equipment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1–2.2.1 Split–mount architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1–2.2.2 IDU (Indoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1–2.2.3 ODU (Outdoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1–2.2.4 IDU–ODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1–2.3 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1–2.3.1 1+0 Unprotected configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1–2.3.2 1+1 Protected Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1–2.4 Equipment Craft Terminal and TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1–2.4.1 ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1–2.4.2 RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1–2.4.3 TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
1–2.5 SW allocation and Flash Card contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1–2.5.1 Allocation of equipment and craft terminal software . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1–2.5.2 Flash Card types and content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1–2.6 General on equipment installation and SWP installation and management . . . . . . 57
1–2.6.1 Main phases for 9400AWY HW and SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1–2.6.2 First SWP installation in PC and NE environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1–2.6.3 How to check ECT and NE versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1–2.6.4 Common situations requiring ECT and/or NE upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 63
1–2.6.5 Flash Card related special procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1–2.6.6 Craft Terminal related special procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1–2.6.7 NE configuration data change and save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
1–2.6.8 NE data save after commissioning completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
1–3 IDU PROVISIONING AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

1–3.1 Provisioning of IDU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1–3.2 Description of IDU Main unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
1–3.2.1 IDU Main Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1–3.2.2 Power Supply connector pin–out (MAIN and EXTENSION units) . . . . . . . . . . . . . . . . 70
1–3.2.3 ECT RS232 connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
1–3.2.4 OS (or ECT) 10/100BaseT connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
1–3.2.5 Ethernet tributaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1–3.3 Description of IDU Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
1–3.3.1 IDU Extension Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
1–3.4 Description of E1 Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1–3.4.1 E1 Protection box: connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1–3.5 Description of Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
1–3.5.1 Alarms Housekeeping (pin–out and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
1–3.5.2 NMS V.11 – Audio 1 (pin–out and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

1–3.5.3 NMS G.703 – Audio 2 (pin–out and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
1–3.5.4 User service channels (pin–out and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

1–3.6 Provisioning and identification of Flash Cards & Software Keys . . . . . . . . . . . . . . . 89

1–3.6.1 Provisioning of Flash Cards & Software Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

1–3.6.2 Description of Flash Cards & Software Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
1–3.7 Provisioning and description of equipment accessories . . . . . . . . . . . . . . . . . . . . . . . 91
1–4 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . 93

1–4.1 ODU mechanical design and identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1–4.2 ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
1–4.3 ODU provisioning and layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
1–4.3.1 Provisioning of ODU (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
1–4.3.2 Provisioning, layouts and connections of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . 96
1–4.4 ODU part lists and characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
1–4.4.1 7–8 GHz ODU part lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
1–4.4.2 13–38 GHz ODU part lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
1–4.5 Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
1–4.5.1 1+0 configuration with integrated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
1–4.5.2 1+1 HSB configuration with coupler and integrated antenna (13–38 GHz) . . . . . . . . 112
1–4.5.3 1+1 HSB configuration with coupler and integrated antenna (7–8 GHz) . . . . . . . . . . 113
1–4.5.4 Configuration with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
1–4.6 Integrated antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
1–4.7 ODU operative information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
1–4.7.1 General, views and access points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
1–4.7.2 ODU hardware settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1–4.7.3 ODU identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1–4.8 7–8 GHz ODU additional operative information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
1–4.8.1 7–8 GHz ODU composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
1–4.8.2 7–8 GHz ODU’s TRANSCEIVER and BRANCHING boxes coupling . . . . . . . . . . . . 122
1–4.8.3 Label affixed inside the 7–8 GHz ODU BRANCHING box . . . . . . . . . . . . . . . . . . . . . . 123
1–5 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

1–5.1 General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1–5.1.1 Reference system standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
1–5.1.2 RF channelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
1–5.1.3 Transmitted power at antenna port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
1–5.1.4 99% power channel bandwidth and Emission Designator . . . . . . . . . . . . . . . . . . . . . . 129
1–5.1.5 ETSI System Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
1–5.1.6 Protection switching system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
1–5.2 Tributary interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
1–5.3 Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
1–5.4 Maximum capacity and Modulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
1–5.5 IDU–ODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
1–5.6 Man–machine interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1–5.7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1–5.8 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1–5.9 Mechanical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1–5.10 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
1–5.10.1 Operating environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
1–5.10.2 Electro–magnetic compatibility/safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
1–5.10.3 Waste from Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . . . . . . . 136
1–5.11 Dismantling & Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
1–5.11.1 WEEE general information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
1–5.11.2 Reference documentation for dismantling and recycling . . . . . . . . . . . . . . . . . . . . . . 137

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL . . 139
2–1 SWP 9400AWY IDU32 DESCRIPTION AND VERSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
2–1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

2–1.2 SWP 9400AWY IDU32 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

2–1.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
2–1.2.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
2–1.3 SWP 9400AWY IDU32 V2.1.0 specific information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–1.3.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–1.3.2 Reference Information Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–1.3.3 Equipment hardware constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–1.3.4 SWP version specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–1.3.5 Restrictions and known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
2–2 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . 143

2–2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2–2.2 TCO Suite description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–2.2.1 TCO Suite scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2–2.2.2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2–2.2.3 TCO Suite start–up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
2–2.2.4 TCO Suite Main Menu functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
2–2.2.5 TCO Suite Advanced Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2–2.2.6 Note: “Direct” And “Remote” Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
2–2.2.7 Warning about interface customization carried out by the Direct Connection . . . . . . 161
2–2.3 TCO Suite Alarms & Settings functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
2–2.3.1 TCO Suite Alarms & Settings start–up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
2–2.3.2 Date & Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
2–2.3.3 Configuration Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
2–2.3.4 Configuration Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
2–2.3.5 Get Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
2–2.3.6 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
2–2.3.7 Licence Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
2–2.3.8 Modem Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
2–2.3.9 NAT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
2–2.4 PC–NE physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
2–2.4.1 Physical interfaces for the NE management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
2–2.4.2 Local connection of the Craft Terminal to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
2–2.5 Craft Terminal: NE supervision, login, logoff and switch off . . . . . . . . . . . . . . . . . . . . 176
2–2.5.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
2–2.5.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
2–2.5.3 NE Logoff or switch off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
2–2.5.4 Closing the 1320CT application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
2–2.6 9400AWY view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
2–2.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
2–2.6.2 Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
2–2.6.3 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
2–2.6.4 Resource Tree Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
2–2.6.5 Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
2–2.6.6 Button Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
2–2.7 Introduction to the CT menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
2–2.7.1 Menu organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
2–2.7.2 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
2–2.7.3 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
2–2.7.4 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
2–2.7.5 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

2–2.7.6 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
2–3 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

2–3.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

2–3.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
2–3.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
2–3.2.2 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
2–3.2.3 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
2–3.2.4 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
2–3.2.5 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
2–3.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
2–3.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
2–3.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
2–3.4.1 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
2–3.4.2 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
2–3.5 Quick Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
2–3.6 Profiles management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
2–3.6.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
2–3.6.2 Change Password procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
2–3.6.3 Users Management procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
2–3.7 Current Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
2–4 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

2–4.1 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
2–4.1.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
2–4.1.2 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
2–4.1.3 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
2–4.2 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
2–4.3 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
2–4.3.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
2–4.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
2–4.3.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
2–5 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

2–5.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
2–5.1.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
2–5.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
2–6 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

2–6.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
2–6.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
2–6.2.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
2–6.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
2–6.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
2–6.3 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
2–6.4 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
2–6.4.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
2–6.4.2 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
2–6.5 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
2–6.5.1 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
2–7 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

2–7.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
2–7.2 Output External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
2–8 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
10 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–8.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
2–8.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . 257
2–8.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . 258
2–8.2 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

2–8.3 MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

2–8.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
2–8.3.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
2–8.3.3 Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
2–8.3.4 Remove file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
2–8.4 SW key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
2–9 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

2–9.1 Mux/Demux Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
2–9.1.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
2–9.1.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
2–9.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
2–9.2.1 Rx Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
2–9.2.3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
2–9.3 HST Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
2–9.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
2–10 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

2–10.1 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
2–10.1.1 1+0 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
2–10.1.2 1+1 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
2–10.2 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
2–10.3 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
2–11 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

2–11.1 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
2–11.2 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
2–11.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
2–11.4 Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
2–11.5 Current Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
2–12 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

2–12.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . . 291
2–12.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
2–12.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
2–12.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
2–12.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
2–12.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
2–12.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
2–12.5 Threshold tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
2–12.5.1 How to change a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
2–12.5.2 How to create a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
2–12.5.3 Threshold table association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
2–13 SW DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

2–13.1 Server Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
2–13.2 Init SW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
2–13.3 SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
2–14 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
3DB 16142 CAAA Ed.01A–DRAFT 11 / 576

2–14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
2–14.2 MIB management at Network Element Synthesis level and examples . . . . . . . . . . 306

2–14.2.1 MIB back–up on ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

2–14.2.2 MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

2–14.2.3 MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
2–14.2.4 MIB restore from ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
SECTION 3: INSTALLATION AND COMMISSIONING . . . . . . . . . . . . . . . . . . . . . 311
3–1 SWP INSTALLATION IN PC ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
3–1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
3–1.1.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
3–1.1.2 Operator skills and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
3–1.2 Reference Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
3–1.3 Choice of the procedure and summary of SWP installation phases . . . . . . . . . . . . . 315
3–1.4 Preliminary: installation of different SWPs in the same PC . . . . . . . . . . . . . . . . . . . . . 316
3–1.5 Installation of SWP components from the SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . . 318
3–1.5.1 Important warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
3–1.5.2 Operations sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
3–1.5.3 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
3–1.6 Local copy in PC environment of the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
3–1.6.2 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
3–1.7 Installation of LLMAN from the SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
3–1.7.2 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
3–1.8 Installation and configuration of Alcatel Virtual Network Card for Lower Layers . 327
3–1.8.1 Important warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
3–1.8.2 Choice of the procedure, according to Windows platform . . . . . . . . . . . . . . . . . . . . . . 327
3–1.8.3 Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
3–1.8.4 Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
3–1.8.5 Windows XP (Professional Edition only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
3–1.8.6 Check for the “Network Connections” order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
3–1.9 End of SW installation from SWP CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
3–1.10 NE software downloading preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
3–1.11 CT initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
3–1.11.1 Craft Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
3–1.11.2 Craft Terminal local connection to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
3–1.12 EML construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
3–2 LINE–UP AND COMMISSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

3–2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
3–2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
3–2.1.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
3–2.1.3 Summary of the commissioning phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
3–2.1.4 Hardware (HW) Presetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
3–2.1.5 Safety–EMC–EMF–ESD norms and Cautions to avoid equipment damage . . . . . . . 362
3–2.2 Description of equipment interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
3–2.2.1 Configurations with 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
3–2.2.2 Configurations with 16E1 + Audio and User Service Channel plug–in . . . . . . . . . . . . 365
3–2.2.3 Configurations with 16E1 + Ethernet plug–in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
3–2.2.4 Configurations with 16E1 + Ethernet plug–in + Audio and User Service Channel
plug–in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
3–2.2.5 Configurations with 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
3–2.2.6 Configurations with 32E1 + Audio and User Service Channel plug–in . . . . . . . . . . . 369
12 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3 Commissioning of STATION A – phase 1 (Turn up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
3–2.3.1 Turn–on preliminary operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
3–2.3.2 Powering up the IDU(s) with ODU(s) connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

3–2.3.3 Switching off the IDU(s), and ODU(s) disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . 371

3–2.3.4 Powering up the IDU(s) with ODU(s) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

3–2.3.5 NE login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
3–2.3.6 General on Quick Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
3–2.3.7 On–line creation, modification and save of the NE configuration . . . . . . . . . . . . . . . . 375
3–2.3.8 TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of a
provisioning file (not interactive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
3–2.3.9 TCO Suite Set–Up Tool: on–line recover, modification and application of a
provisioning file (not interactive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
3–2.3.10 Quick Configuration Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
3–2.3.11 Powering UP the IDU(s) with the ODU(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
3–2.4 Commissioning of STATION B – phase 1 (Turn up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
3–2.5 End of commissioning phase 1 (Turn up) in STATION A . . . . . . . . . . . . . . . . . . . . . . . 403
3–2.5.1 Remote NE (station B) acquisition on craft terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
3–2.5.2 Testing configurations for hop quality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
3–2.6 Commissioning station A – phase 2 (acceptance test) . . . . . . . . . . . . . . . . . . . . . . . . . 406
3–2.6.1 System Installation and cabling visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
3–2.6.2 Local configuration control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
3–2.6.3 Channel 1 functionality tests (1+0 and 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
3–2.6.4 Channel 0 functionality tests (1+1 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
3–2.6.5 Hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
3–2.6.6 NE integration tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
3–2.7 Commissioning station B – Phase 2 (Acceptance Test) . . . . . . . . . . . . . . . . . . . . . . . . 442
3–2.8 Final operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
3–2.9 Annex A: fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
3–2.9.1 Vertical alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
3–2.9.2 Horizontal alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
3–2.10 Annex B: light service kit cable operative information . . . . . . . . . . . . . . . . . . . . . . . . 446
SECTION 4: MAINTENANCE AND UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
4–1 MAINTENANCE POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
4–1.1 Classification of maintenance levels and operators . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
4–1.2 First Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4–1.3 Second Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4–1.4 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4–2 USE OF EOW FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

4–2.1 Setting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
4–2.2 Call Set–up/End by Telephone handset connected to the IDU Main unit . . . . . . . . . 454
4–3 MAINTENANCE TOOLS AND SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

4–3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
4–3.2 Instruments and accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
4–3.2.1 Software tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
4–3.2.2 Maintenance, Installation and Station Kit Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
4–3.3 Set of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
4–3.3.1 Types of Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
4–3.3.2 ODU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
4–3.3.3 IDU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
4–3.3.4 Number of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
4–3.3.5 General rules on spare parts management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
3DB 16142 CAAA Ed.01A–DRAFT 13 / 576

4–4 FIRST LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
4–4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

4–4.2 System state display by visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

4–4.2.1 LED test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

4–4.2.2 Alarm LEDs on the IDU MAIN unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
4–4.2.3 Alarm LEDs on the Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
4–4.3 TCO Suite and Craft Terminal commonly used functions for system status
display and checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
4–4.3.1 Viewing the NE alarms by TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
4–4.3.2 Viewing the NE status by Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
4–5 SECOND LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

4–5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
4–5.2 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
4–5.2.1 EMC norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
4–5.2.2 Safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
4–5.2.3 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
4–5.3 Routine (preventive) Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
4–5.3.1 Routine (preventive) Maintenance every year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
4–5.4 Consequences of unit extraction in the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
4–5.5 Corrective Maintenance general flow–chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
4–5.6 Alarm acknowledgment and attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
4–5.6.1 Alarm acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
4–5.6.2 Alarm Attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
4–5.7 Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
4–5.8 Troubleshooting via Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
4–5.8.1 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
4–5.8.2 Alarm surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
4–5.8.3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
4–5.8.4 Operator’s Controls of the protection switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
4–5.8.5 Tx mute function (local and remote) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
4–5.8.6 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
4–5.8.7 Commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
4–5.9 Hints on the troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
4–5.9.1 Problems with the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
4–5.9.2 Analog measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
4–5.9.3 NMS 64 kbit/s V.11 and G.703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
4–5.9.4 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
4–5.9.5 Empty USM icon in NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
4–5.9.6 Remote NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
4–5.9.7 Configuration change from 4 QAM to 16 QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
4–5.9.8 Quick configuration menu correct use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
4–5.9.9 Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
4–5.9.10 Tx Mute functionality for interferences investigation . . . . . . . . . . . . . . . . . . . . . . . . . . 488
4–5.9.11 Tributaries 17 to 32 visible in “16E1+Ethernet” configuration . . . . . . . . . . . . . . . . . . 489
4–5.10 IDU unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
4–5.10.1 IDU MAIN unit replacement procedure (CH1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
4–5.10.2 IDU EXTENSION unit replacement procedure (CH0) . . . . . . . . . . . . . . . . . . . . . . . . . 495
4–5.11 ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
4–5.12 Faulty unit repair and Repair Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
4–5.12.1 Faulty unit sending back to repair center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
4–5.12.2 Repair Form filling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
14 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–6 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES . . . . . . . . . 505
4–6.1 Spare Flash Card management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
4–6.2 Flash Card replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

4–6.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

4–6.2.2 Execution of the Flash Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
4–7 SYSTEM HARDWARE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

4–7.1 Installation of plug–ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
4–7.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
4–7.1.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
4–7.2 Upgrade from 1+0 to 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
4–7.2.1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
4–7.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
4–7.3 Flash Card upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
4–7.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
4–7.3.2 Summary procedure for both stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
4–7.3.3 Ordering the new Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
4–7.3.4 Installation of a new Flash Card fully configured in factory . . . . . . . . . . . . . . . . . . . . . 521
4–7.3.5 Installation of a new Flash Card not configured in factory . . . . . . . . . . . . . . . . . . . . . . 522
4–8 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
4–9 ECT & NE UPGRADE TO A NEW SWP ’VERSION’ (SAME NE ’RELEASE’) . . . . . . . . . . . 525
4–10 SWP DE–INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
APPENDIX A: SAFETY–EMC–EMF–ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . 529
A.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
A.2 : Compliance with International Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
A.3 : Safety Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
A.3.1 : General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
A.3.2 : Labels Indicating Danger, Forbiddance, Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
A.3.3 : Dangerous Electrical Voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
A.3.4 : Risks of Explosions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
A.3.5 : Moving Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
A.3.6 : Equipment connection to earth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
A.3.7 : Heat–radiating Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
A.3.8 : Microwave radiations (EMF norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
A.3.9 : Specific safety rules in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
A.4 : Electromagnetic Compatibility (EMC norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
A.4.1 : EMC General Norms – Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
A.4.2 : EMC General Norms – Turn–on, Tests & Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
A.4.3 : EMC General Norms – Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
A.5 : Equipment protection against electrostatic discharges . . . . . . . . . . . . . . . . . . . . . . . . . 538
A.6 : Suggestions, notes and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
A.7 : Labels affixed to the 9400AWY equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
A.7.1 : Labels affixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
A.7.2 : Labels affixed on the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
APPENDIX B: ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
B.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
B.2 : Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
B.3 : Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
B.4 : Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
3DB 16142 CAAA Ed.01A–DRAFT 15 / 576

B.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . . . 544
B.4.2 : TD–32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

B.5 : PC laptop “Dell Latitude” setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

B.6 : Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

B.7 : Changing the ECT–equipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
B.7.1 : Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
B.7.2 : Configuration at NE side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
B.7.3 : Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
APPENDIX C: DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551

C.1 : Guide to this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
C.1.1 : Applicability of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
C.1.2 : Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
C.1.3 : History of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
C.2 : Documentation set description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
C.2.1 : 9400AWY Rel.2.1 Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
C.2.2 : Additional documentation for 1320CT platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
C.3 : General on Alcatel–Lucent Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
C.3.1 : Customer–Independent Standard Customer Documentation . . . . . . . . . . . . . . . . . . . . . 558
C.3.2 : Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . 559
APPENDIX D: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS . . . . . . . 561

D.1 : List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
D.2 : List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
D.3 : Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
SECTION 6: ENCLOSED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
16 / 576 3DB 16142 CAAA Ed.01A–DRAFT

LIST OF FIGURES AND TABLES
FIGURES
Fig. 1. Antistatic protection device kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Fig. 2. 9400AWY radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 3. 9400AWY R.2.1 split–mount system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fig. 4. Possible configurations of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Fig. 5. E1 Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Fig. 6. Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Fig. 9. ODU air interface compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Fig. 10. ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fig. 11. 9400AWY (1+0) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fig. 12. 9400AWY (1+1 HSB SD) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Fig. 13. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . 48
Fig. 14. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . 49
Fig. 15. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . 49
Fig. 16. Equipment main parts containing local SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Fig. 17. Flash Card content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Fig. 18. Main phases for 9400AWY HW and SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Fig. 19. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Fig. 20. How to check ECT version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Fig. 21. How to check NE SW version (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Fig. 22. IDU Main Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Fig. 23. LEDs on the IDU Main Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Fig. 24. IDU Extension Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Fig. 25. LEDs on the IDU Extension Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Fig. 26. E1 Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . . . . . . . 75
Fig. 27. Services Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . . 80
Fig. 28. Equipment outputs (summarizing and housekeeping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Fig. 29. Equipment inputs – relay scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Fig. 30. Equipment inputs – open collector scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Fig. 31. User service channel: V11 co–directional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fig. 32. User service channel: V11 contra–directional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fig. 33. User service channel: G.703 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Fig. 34. User service channel: V24/V28 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Fig. 35. FLASH CARD profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Fig. 36. ODU types, identification, dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Fig. 37. Station layout of ODU (1+1) HSB–SD or FD–DA AP with two antennas . . . . . . . . . . . . . . . 96
Fig. 38. Station layout of ODU (1+1) HSB with one antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Fig. 39. Station layout of ODU (1+1) FD–AP with one double polar external antenna . . . . . . . . . . 98
Fig. 40. View of ODU with integrated antenna (V polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Fig. 41. View of ODU with integrated antenna (H polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Fig. 42. Coupler (13–38 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Fig. 43. Coupler (7–8 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Fig. 44. Nose adapters for ODU with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Fig. 45. ODU LEMO connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Fig. 46. ODU views (13–38 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Fig. 47. ODU views (7–8 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Fig. 48. 7–8 GHz ODU composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Fig. 49. 7–8 GHz ODU’s TRANSCEIVER and BRANCHING boxes coupling surfaces . . . . . . . . . . 122
Fig. 50. Label affixed inside the 7–8 GHz ODU BRANCHING box . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Fig. 51. Java installation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
3DB 16142 CAAA Ed.01A–DRAFT 17 / 576

Fig. 52. JRE installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Fig. 53. Browser loading warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Fig. 54. Security Questions: Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Fig. 55. Secure Questions: Allow Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Fig. 56. Execution confirmation (Security Warning) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Fig. 57. Security Warning (English browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Fig. 58. Security Warning (Italian browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Fig. 59. Security Warning (Java 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Fig. 60. Wrong Security Warning (Java 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Fig. 61. Firefox browser: no JRE installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Fig. 62. Firefox plug–in search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Fig. 63. Firefox plug–in installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Fig. 64. TCO Suite Start.html page (CD–ROM version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Fig. 65. TCO Suite Start.html page (Local version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Fig. 66. TCO Suite AS.html page (Advanced Settings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Fig. 67. Internet Explorer: .exe files management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Fig. 68. ECT–NE “Direct” and “Remote” connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Fig. 69. Network Adapter selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Fig. 70. Network Adapter details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Fig. 71. Direct or Remote connection by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Fig. 72. NE login by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Fig. 73. TCO Suite’s Alarms & Settings Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Fig. 74. TCO Suite’s Alarms & Settings “Date & Time Configuration” page . . . . . . . . . . . . . . . . . . . 165
Fig. 75. TCO Suite’s Alarms & Settings “Configuration Setting” page . . . . . . . . . . . . . . . . . . . . . . . . 166
Fig. 76. TCO Suite’s Alarms & Settings “Get Report Request” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Fig. 77. TCO Suite’s Alarms & Settings “Get Configuration” Request . . . . . . . . . . . . . . . . . . . . . . . . 170
Fig. 78. TCO Suite’s Alarms & Settings “Active Alarms: Static Page” . . . . . . . . . . . . . . . . . . . . . . . . 171
Fig. 79. TCO Suite’s Alarms & Settings “Active Alarms: Automatic Page” . . . . . . . . . . . . . . . . . . . . 171
Fig. 80. TCO Suite’s Alarms & Settings “Reading Software License” . . . . . . . . . . . . . . . . . . . . . . . . . 172
Fig. 81. TCO Suite’s Alarms & Settings “Changing F–Interface Speed” . . . . . . . . . . . . . . . . . . . . . . 172
Fig. 82. TCO Suite’s Alarms & Settings “NAT option” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Fig. 83. MAIN Unit front side: interfaces for equipment control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Fig. 84. Choice of Serial or Ethernet interface for PC–NE physical connection . . . . . . . . . . . . . . . . 178
Fig. 85. Network Element Synthesis screen (NE locally connected) . . . . . . . . . . . . . . . . . . . . . . . . . 179
Fig. 86. Network Element Synthesis screen (empty map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Fig. 87. SNMP NE creation in the Network Element Synthesis map . . . . . . . . . . . . . . . . . . . . . . . . . 180
Fig. 88. Network Element Synthesis screen after SNMP NE creation . . . . . . . . . . . . . . . . . . . . . . . . 180
Fig. 89. Start supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Fig. 90. NE in supervised state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Fig. 91. Show Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Fig. 92. Login screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Fig. 93. NE Stop Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Fig. 94. 9400AWY Main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Fig. 95. Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Fig. 96. View Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Fig. 97. Resource tree area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Fig. 98. Tab panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Fig. 99. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Fig. 100. Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Fig. 101. Local Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Fig. 102. NTP Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Fig. 103. Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Fig. 104. Ethernet Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Fig. 105. IP configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Fig. 106. IP static routing configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
18 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 107. Create Static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Fig. 108. Point To Point Interface Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Fig. 109. OSPF Area configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Fig. 110. Create New OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Fig. 111. IP Address configuration of Point–To–Point Interfaces screen . . . . . . . . . . . . . . . . . . . . . . 208

Fig. 112. Routing information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Fig. 113. Alarm Severities Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fig. 114. Name of a cloned alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fig. 115. Clone of an Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fig. 116. Selection of a new severity in the Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Fig. 117. Selection of a new severity in the No Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . 214
Fig. 118. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Fig. 119. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Fig. 120. USM closing warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Fig. 121. Overhead Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Fig. 122. Profile Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Fig. 123. Changing Password screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Fig. 124. Users Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Fig. 125. Users Management help screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Fig. 126. Current Configuration view screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Fig. 127. 1+0 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Fig. 128. 1+1 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Fig. 129. 1+0 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Fig. 130. 1+1 IDU/MAIN Ch#1 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Fig. 131. 1+1 IDU Ch#0 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Fig. 132. Main board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Fig. 133. ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Fig. 134. Alarm tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Fig. 135. Configuration tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Fig. 136. Remote Inventory tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Fig. 137. Line Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Fig. 138. Line Interface View: E1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Fig. 139. Line Interface View: E3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Fig. 140. Line Interface View: DS1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Fig. 141. Line Interface View: DS3 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Fig. 142. Line Interface View: NMS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Fig. 143. Line Interface View: Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Fig. 144. Line Interface View: Ethernet Port auto–negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Fig. 145. Radio Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Fig. 146. Radio Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Fig. 147. Rtpc & Atpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Fig. 148. Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Fig. 149. Power Measurement Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Fig. 150. Power Meas Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Fig. 151. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Fig. 152. Example of “Power Measurement File Reading“ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Fig. 153. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . . 252
Fig. 154. Input External Point View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Fig. 155. Output External Points: CP01 ... CP04 (Manual activation) . . . . . . . . . . . . . . . . . . . . . . . . 254
Fig. 156. Output External Points: CP01 ... CP04 (Automatic activation) . . . . . . . . . . . . . . . . . . . . . . 255
Fig. 157. Output External Points View: FAIL IDU, FAIL ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Fig. 158. Configuration of the Craft access state from the Equipment NE view in the OS mode . . 257
Fig. 159. Restart NE call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Fig. 160. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Fig. 161. MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
3DB 16142 CAAA Ed.01A–DRAFT 19 / 576

Fig. 162. Backup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Fig. 163. Restore screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Fig. 164. Activate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Fig. 165. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Fig. 166. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Fig. 167. Mux Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Fig. 168. Mux Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Fig. 169. Mux Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Fig. 170. Radio Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Fig. 171. Rx Static Delay menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Fig. 172. Radio Protection Switch (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Fig. 173. Radio Protection Switch (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Fig. 174. Transmission Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Fig. 175. Tx Protection Commands (Spare #0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Fig. 176. Tx Protection Commands (Main #1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Fig. 177. 1+0 available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Fig. 178. Channel 1 Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Fig. 179. Tributaries Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Fig. 180. 1+0 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Fig. 181. 1+1 available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Fig. 182. Channel 1 Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Fig. 183. Tributaries Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Fig. 184. 1+1 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Fig. 185. Loopback activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Fig. 186. Loopback removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Fig. 187. Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Fig. 188. Summary Block Diagram View: 1+0 without Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . 287
Fig. 189. Summary Block Diagram View: 1+0 with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Fig. 190. Summary Block Diagram View: 1+1 HST without Ethernet ports . . . . . . . . . . . . . . . . . . . . 288
Fig. 191. Summary Block Diagram View: 1+1 HST with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . 288
Fig. 192. Summary Block Diagram View: 1+1 FD without Ethernet ports . . . . . . . . . . . . . . . . . . . . . 289
Fig. 193. Summary Block Diagram View: 1+1 FD with Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . 289
Fig. 194. Radio sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Fig. 195. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826 . . . . . . . . . 292
Fig. 196. Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Fig. 197. Threshold table association screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Fig. 198. Current Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Fig. 199. History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Fig. 200. Threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Fig. 201. Thresholds Table creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Fig. 202. Server access configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Fig. 203. Init Software Download screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Fig. 204. SW Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Fig. 205. SW Unit Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Fig. 206. Allowed MIB management tasks at “NE logged–in” level . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Fig. 207. Allowed MIB management tasks at “Network Element Synthesis” level . . . . . . . . . . . . . . 305
Fig. 208. Launch of MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Fig. 209. MIB save to disk – phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Fig. 210. MIB save to disk – phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Fig. 211. Correspondence between MIB saved folder and MIB saved name . . . . . . . . . . . . . . . . . . 307
Fig. 212. Launch of MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Fig. 213. MIB load from disk – phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Fig. 214. MIB load from disk – phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Fig. 215. Common components of different SWPs (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Fig. 216. CD–ROM TCO Suite Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
20 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 217. CD–ROM TCO Suite Advanced Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Fig. 218. SWP component selection screen and installation start . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Fig. 219. SWP component installation end, and installation report . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Fig. 220. Check of installed Alcatel SWP components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Fig. 221. Local Copy of TCO Suite location choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Fig. 222. Local Copy of TCO Suite progress and end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Fig. 223. Copy cancelled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Fig. 224. Shortcut to the TCO Suite Start icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Fig. 225. Alcatel Lower Layers Manager ”splash screen” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Fig. 226. Alcatel Lower layers Manager language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Fig. 227. Alcatel Lower Layers Manager Installation screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Fig. 228. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Fig. 231. Windows NT configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Fig. 237. Windows 2000 installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Fig. 242. Windows 2000 configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Fig. 245. Windows XP installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Fig. 250. Windows XP configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Fig. 254. Check for the “Network Connections” order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Fig. 255. Selecting SWP Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Fig. 256. SWP Administrator screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Fig. 257. Directory selection for the descriptor file “.DSC” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Fig. 258. SWP available for download to NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Fig. 259. Relative positions of stations A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Fig. 260. Equipment interconnections for configurations with 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Fig. 261. Equipment interconnections for configurations with 16E1 + Audio and User Service
Channel plug–in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Fig. 262. Equipment interconnections for configurations with 16E1 + Ethernet plug–in . . . . . . . . . 366
Fig. 263. Equipment interconnections for configurations with 16E1 + Ethernet plug–in + Audio
and User Service Channel plug–in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Fig. 264. Equipment interconnections for configurations with 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Fig. 265. Equipment interconnections for configurations with 32E1 + Audio and User Service
Channel plug–in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Fig. 266. Pre–Provisioning Tool ”splash screen” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Fig. 267. Pre–Provisioning Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Fig. 268. Pre–Provisioning Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
3DB 16142 CAAA Ed.01A–DRAFT 21 / 576

Fig. 269. Set–Up Tool ”splash screen” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Fig. 270. Set–Up Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Fig. 271. Set–Up Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Fig. 272. Quick Configuration Procedure: main NE parameter configuration (Step A) . . . . . . . . . . 379

Fig. 273. Quick Configuration Procedure Step B: PDH Tributary configuration . . . . . . . . . . . . . . . . 381
Fig. 274. Quick Configuration Procedure Step B: Ethernet port configuration – basic information 383
Fig. 275. Quick Configuration Procedure Step B: Ethernet port configuration – discard frames
information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Fig. 276. Quick Configuration Procedure: Channels Configuration (Step C) . . . . . . . . . . . . . . . . . . . 384
Fig. 277. Frequency Data Help: choice of ODU type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Fig. 278. Frequency Data Help: frequency data of chosen ODU type (example) . . . . . . . . . . . . . . . 386
Fig. 279. Example of Frequency Data manual setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Fig. 280. RTPC setting with ATPC disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Fig. 281. Setting of enabled ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Fig. 282. Quick Configuration Procedure: Link Identifier configuration (Step D) . . . . . . . . . . . . . . . . 388
Fig. 283. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E) . . 389
Fig. 284. Quick Configuration Procedure: OSPF Area Configuration (Step F) . . . . . . . . . . . . . . . . . 390
Fig. 285. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration
(Step G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Fig. 286. Quick Configuration Procedure: Configuration of TMN–RF, TMN–V11 and TMN–G703
channels (Step H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Fig. 287. Quick Configuration Procedure: IP Static Routes Configuration (Step I) . . . . . . . . . . . . . . 393
Fig. 288. Quick Configuration Procedure: Default Gateway Routing configuration (Step I) . . . . . . 394
Fig. 289. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J) . . . 395
Fig. 290. Quick Configuration Procedure: External Input and Output Points configuration (Step K) 396
Fig. 291. Quick Configuration Procedure: Summary (Step L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Fig. 292. ODU(s) alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Fig. 293. Transmit power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Fig. 294. Received power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Fig. 295. Received power details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Fig. 296. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Fig. 297. Create NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Fig. 298. NMS Radio side Remote NE acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Fig. 299. Test bench for tributary quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Fig. 300. Test bench for User service channel quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Fig. 301. Software Key code view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Fig. 302. NE parameters and Frame configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Fig. 303. E1 tributary configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Fig. 304. Automatic restoration criteria configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Fig. 305. Automatic restoration criteria configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Fig. 306. Rx Static delay configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Fig. 307. Tx and Rx frequencies configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Fig. 308. Not standard frequency arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Fig. 309. ATPC mode configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Fig. 310. Overhead configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Fig. 311. Local IP address configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Fig. 312. OSPF configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Fig. 313. NMS IP point to point configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Fig. 314. (OS) Ethernet access configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Fig. 315. IP static routing configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Fig. 316. 1+0 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Fig. 317. 1+1 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Fig. 318. Channel 0 lockout mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Fig. 319. Near End loopbacks points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Fig. 320. Loopback control in the CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
22 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 321. Far End loopback point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Fig. 322. Test bench for tributary functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Fig. 323. Tributary alarm status monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Fig. 324. Test bench for User Service Channel functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Fig. 325. Test bench for Optional Ethernet Data Channel functionality . . . . . . . . . . . . . . . . . . . . . . . 429
Fig. 326. Power measurement view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Fig. 327. TX and RX power details view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Fig. 328. Engineering order wire organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Fig. 329. Channel 1 forced mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Fig. 330. Test bench for hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Fig. 331. Test bench for NMS Line side acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Fig. 332. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Fig. 333. Create NMS Line side NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Fig. 334. NMS Line side NE monitoring in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Fig. 335. Test bench for EOW line side functionality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Fig. 336. Input housekeeping external alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Fig. 337. Output housekeeping equipment alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Fig. 338. Integrated pole mounting screws for Vertical alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Fig. 339. Stretching screw (3CC14292AAAA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Fig. 340. Integrated pole mounting screws for Horizontal alignment . . . . . . . . . . . . . . . . . . . . . . . . . 445
Fig. 341. Light service kit cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Fig. 342. Special extractor to remove the coaxial cables 1.0/2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Fig. 343. Lever for ODU mounting/dismounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Fig. 344. LEDs and pushbutton on IDU Extension unit for maintenance purposes . . . . . . . . . . . . . 461
Fig. 345. LEDs and pushbutton on IDU MAIN unit for maintenance purposes . . . . . . . . . . . . . . . . . 462
Fig. 346. Checks on Radio domain – Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Fig. 347. Checks on Radio domain – Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Fig. 348. Checks on Radio domain – Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Fig. 349. Checks on Radio domain – RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Fig. 350. Checks on Radio domain – Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Fig. 351. Corrective Maintenance general flow–chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Fig. 352. Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Fig. 353. Active alarm screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Fig. 354. Lower Layers Manager screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Fig. 355. Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Fig. 356. Tx Mute functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Fig. 357. Tributaries 17 to 32 visible in “16E1+ Ethernet” configuration . . . . . . . . . . . . . . . . . . . . . . . 489
Fig. 358. Details for IDU MAIN unit or FLASH CARD replacement . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Fig. 359. Details for IDU EXTENSION unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Fig. 360. Repair form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Fig. 361. Dismounting the fixing brackets and cover unfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Fig. 362. Release and sliding out the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Fig. 363. Removing the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Fig. 364. Dismounting the metal plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Fig. 365. Connectors and columns for plug–in fixing by screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Fig. 366. Plug–in insertion and fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Fig. 367. Label affixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Fig. 368. Label affixed on the ODU and ODU’s TRANSCEIVER box . . . . . . . . . . . . . . . . . . . . . . . . . 540
Fig. 369. ECT–Equipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . . 541
Fig. 370. ECT–Local external Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Fig. 371. F Interface–Remote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Fig. 372. TD–32 AC modem dip–switch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Fig. 373. Alcatel Lower Layers utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Fig. 374. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . 560
3DB 16142 CAAA Ed.01A–DRAFT 23 / 576

TABLES
Tab. 1. Quick guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tab. 2. Tributaries and modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Tab. 3. 13 to 38 GHz 4/16 QAM configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Tab. 4. Bit rate of the IDU–ODU signal on the cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Tab. 5. IDU shelf provisioning for 1+0 and 1+1 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Tab. 6. IDU Main Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Tab. 7. Power supply connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Tab. 8. ECT connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Tab. 9. OS (or ECT) connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Tab. 10. RJ45 connectors leds for Ethernet user data interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Tab. 11. IDU Extension Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Tab. 12. Equipment Side and Line Side connectors of E1 Protection box . . . . . . . . . . . . . . . . . . . . . 75
Tab. 13. E1 tributaries (1 to 8) connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Tab. 14. E1 tributaries (9 to 16) connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Tab. 15. E1 tributaries (17 to 24) connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Tab. 16. E1 tributaries (25 to 32) connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Tab. 17. Equipment Side and Line Side connectors of Services Protection box . . . . . . . . . . . . . . . . 80
Tab. 18. Alarms Housekeeping connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Tab. 19. NMS–V.11 + Audio 1 connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Tab. 20. NMS–G.703 + Audio 2 connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Tab. 21. User service channel connector pin–out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Tab. 22. Flash Cards & Software Keys provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Tab. 23. Equipment accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Tab. 21. ODU dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Tab. 22. ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Tab. 23. 7 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Tab. 24. Branching assemblies for 7 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Tab. 25. 8 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Tab. 26. Branching assemblies for 8 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Tab. 27. 13 GHz ODU (FIXED–SHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Tab. 30. 18 GHz ODU (VARIABLE–SHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Tab. 32. 23 GHz ODU (VARIABLE–SHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Tab. 36. Pole Mounting versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Tab. 37. Available couplers (13–38 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Tab. 38. Available couplers (7–8 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Tab. 39. ODU Output flanges with external antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Tab. 40. Available integrated antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Tab. 41. ODU external interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Tab. 42. RF interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Tab. 43. 9400 AWY family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Tab. 44. ETSI System Characteristics 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Tab. 45. ETSI System Characteristics 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Tab. 46. ETSI System Characteristics 8E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Tab. 49. Reference documentation for dismantling and recycling detail for 9400AWY equipment 137
Tab. 53. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Tab. 54. Typical Alcatel–Lucent Ethernet cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login
profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
24 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Tab. 53. ATPC Range Rx Threshold for ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Tab. 54. ATPC Range Rx Threshold for ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Tab. 55. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266



Tab. 58. 1+0 loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Tab. 59. 1+1 loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Tab. 60. SES Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Tab. 64. Test and commissioning instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Tab. 65. Radio application: Market, capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Tab. 63. Special items of the Kit Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Tab. 64. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Tab. 65. Alarm information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Tab. 66. General issues of the alarm meanings and their respective maintenance actions . . . . . . 479
Tab. 67. IDU unit replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Tab. 68. Available plug–in upgrade kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Tab. 69. Flash card upgrade carried out by one operator only for both stations . . . . . . . . . . . . . . . . 519
Tab. 70. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna: . . . . . . . . . 536
Tab. 74. History of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Tab. 75. 9400AWY Rel.2.1 Documentation CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Tab. 76. Handbooks independent from SWP version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Tab. 77. Handbooks dependent from SWP version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Tab. 78. Documentation common to Alcatel–Lucent Network Elements using 1320CT platform . . 557
Tab. 76. List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Tab. 77. List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Tab. 78. List of enclosed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
3DB 16142 CAAA Ed.01A–DRAFT 25 / 576

a)
26 / 576
END OF FRONT MATTER
3DB 16142 CAAA Ed.01A–DRAFT

SECTION 1: SYSTEM DESCRIPTION
This section provides general warnings, the equipment description (at system, IDU and ODU levels),
introduces the basic information regarding the 9400AWY Rel.2.1 HW and SW installation and
commissioning and those regarding the software management, and gives its technical characteristics.
SECTION CONTENT PAGE
Chapter 1–1 – About this manual

It deals with:
– Preliminary information
– History, applicability and purpose of this manual (summary) 29
– Structure of this manual
– Safety–EMC–EMF–ESD norms and equipment labelling (summary)
– Cautions to avoid equipment damage
Chapter 1–2 – System overview

It gives the 1st level description of the equipment architecture, system configurations
of the 9400AWY Rel.2.1. Moreover, it gives the basic information regarding the
Equipment Craft Terminal and TCO Suite, as well those concerning the main phases 33
for 9400AWY HW and SW installation, and those regarding the software
management, with particular emphasis on SWP release and versions upgrading
situations.
Chapter 1–3 – IDU provisioning and description

It contains the whole logical and operative information on:
– provisioning of equipment items (P/Ns, equipping rules)
– their physical and logical position in the system
65
– unit assembly/subassembly and front panel drawings, with the description on
the access point usage (connectors, visual indicators, buttons)
– pinout description of connectors for Customer implementation
– summary and operative information on characteristics of external interfaces
Chapter 1–4 – ODU provisioning, characteristics and description

It describes in detail the ODU physical configurations, relevant provisioning and 93
operative information for installation, commissioning and maintenance purposes
Chapter 1–5 – Technical specifications

125
It describes the technical characteristics of the 9400AWY Rel.2.1.
3DB 16142 CAAA Ed.01A–DRAFT 27 / 576

28 / 576
1–1 ABOUT THIS MANUAL
1–1.1 Preliminary information

a) Warranty
Any warranty must be referred exclusively to the terms of the contract of sale of the equipment to
which this handbook refers to.
Alcatel–Lucent 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–Lucent 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–Lucent.
c) Copyright Notification
The technical information of this manual is the property of Alcatel–Lucent and must not be copied,
reproduced or disclosed to a third party without written consent.
d) Safety recommendations
The safety recommendations here below must be considered to avoid injuries on persons and/or
damage to the equipment:
1) Service Personnel
Installation and service must be carried out by authorized persons having appropriate technical
training and experience necessary to be aware of hazardous operations during installation and
service, so as to prevent any personal injury or danger to other persons, as well as prevent
damaging the equipment.
2) Access to the Equipment
Access to the Equipment in use must be restricted to Service Personnel only.
3) Safety Rules
Recommended safety rules are indicated in para.A.3 on pages 530.
Local safety regulations must be used if mandatory. Safety instructions in this handbook should
be used in addition to the local safety regulations. In case of conflict between safety instructions
stated in this manual and those indicated in local regulations, mandatory local norms will prevail.
Should not local regulations be mandatory, then safety rules stated in this manual will prevail.
e) Service Personnel skill

Service Personnel must have an adequate technical background on telecommunications and in
particular on the equipment subject of this handbook.
An adequate background is required to properly install, operate and maintain equipment. The fact of
merely reading this handbook and the associated handbooks indicated in para. C.2.1 on page 555 is
considered as not enough.
3DB 16142 CAAA Ed.01A–DRAFT 29 / 576

1–1.2 History, applicability and purpose of this manual

DATE CHANGE NOTE

ED APPRAISAL AUTHORITY ORIGINATOR

(yymmdd) (ECO)
01A 070126 DRAFT IN PREPARATION E.Corradini
For detailed information regarding the applicability, purpose and history of this manual, please refer to
para.C.1 on page 551.
1–1.3 Structure of this manual

This manual is composed by a ’main part’ and ’enclosed documents’.
MAIN PART
Information in this manual is divided into the following parts:
a) FRONT MATTER
• FRONT PAGE
• QUICK GUIDE
The Quick guide allows to access immediately the most frequently needed operative pieces
of information contained in this manual and in other related handbooks.
• TABLE OF CONTENTS
• LIST OF FIGURES AND TABLES
b) SECTION 1: SYSTEM DESCRIPTION on page 27
This section provides general warnings, the equipment description, introduces the basic information
regarding the 9400AWY Rel.2.1 HW and SW installation and commissioning, and those regarding
the software management, and gives its technical characteristics.
Moreover, it contains the whole logical and operative information on:
• provisioning of equipment items (P/Ns, equipping rules)
• their physical and logical position in the system
• unit assembly/subassembly and front panel drawings, with the description on the access point
usage (connectors, visual indicators, buttons)
c) SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139
In this section, the description of the TCO suite, and the NE functionalities available in the Craft
Terminal are given.
d) SECTION 3: INSTALLATION AND COMMISSIONING on page 311
This section provides the whole operative instructions for the equipment HW and SW installation and
commissioning.
e) SECTION 4: MAINTENANCE AND UPGRADE on page 447
This section contains the whole logical and operative information for the equipment maintenance and
system SW and HW upgrade.
f) SECTION 5: APPENDICES on page 527
In this section some additional information and instructions are given:
• Appendix A – Safety–EMC–EMF–ESD norms and equipment labelling
• Appendix B – ECT–Equipment connection via public switched telephone network
• Appendix C – Documentation guide
• Appendix D – List of symbols and abbreviations, Glossary of terms
g) SECTION 6: ENCLOSED DOCUMENTS on page 575
This section lists and contains the documents enclosed to this manual. Each of them has its own P/N,
different from that of this main part and different from one another.
ENCLOSED DOCUMENTS
30 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–1.4 Safety–EMC–EMF–ESD norms and equipment labelling
a) Please refer to Appendix A on page 529 to obtain details regarding following information:
• Safety rules:
TOPIC WARNING LABEL ON EQUIPMENT

General rules
Dangerous Electrical Voltages
Equipment connection to earth
Risk of explosion
Moving mechanical parts
Heat–radiating mechanical parts
Equipment emitting RF power (EMF norms)
• Other labels:
TOPIC WARNING LABEL ON EQUIPMENT
Device sensitive to electrostatic discharges
2002/96/EC WEEE (Waste Electrical and

Electronic Equipment) Logo
• Electromagnetic Compatibility (EMC norms)
• Other Labels affixed to the Equipment
b) Identical or similar information on Personal Computer, Work–Station etc., other than

Alcatel–Lucent’s, loaded with software applications described in this or other Handbooks, is
supplied in the Constructor’s technical documentation.
3DB 16142 CAAA Ed.01A–DRAFT 31 / 576

1–1.5 Cautions to avoid equipment damage

a) Unit assemblies

Each of the IDU MAIN UNIT and IDU EXTENSION UNIT is assembled inside its own box and must
be considered an unique item from the service and maintenance points of view. Such an assembly
is supplied by Alcatel–Lucent “as it is” and must never be disassembled , with the exception of
operations described in para.4–7.1, that must be carried out exactly as described.
b) Antistatic protection device kit

Whenever is necessary to handle spare parts and boards out of their own box, this kit (Fig. 1. below)
must be always warn and its termination must be connected to a grounded structure, to avoid the
possible damage of the electronic devices for electrostatic discharges.
ELASTICIZED BAND
COILED CORD
Fig. 1. Antistatic protection device kit
c) Screw fixing
In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) must be always
tightened to avoid item detachment and to ensure the equipment EMI–EMC performance.
The screw tightening torque must be:
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Exceeding this value may result in screw breaking.
d) IDU–ODU cable disconnection / connection

Before to disconnect or connect the IDU–ODU cable (at IDU or ODU side) switch off the
corresponding IDU Main Unit or IDU Extension Unit.
e) Craft Terminal connection

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

To disconnect the CT cable (at IDU Main Unit’s F or OS Ethernet interface and/or PC side):
• perform the logoff, exiting from the CT applications (details in para.2–2.5.3 and 2–2.5.4 on page
184)
• close all other running applications, if any
• switch off the PC
• now the cable can be safely disconnected.
32 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2 SYSTEM OVERVIEW
This chapter gives the 1st level description of the equipment architecture and system configurations of the
9400AWY Rel.2.1; it includes the following main parts:

– Introduction, herebelow
– Equipment architecture, on page 35
– System configurations, on page 46
– Equipment Craft Terminal and TCO Suite, on page 50
– SW allocation and Flash Card contents, on page 52
– General on equipment installation and SWP installation and management, on page 57
1–2.1 Introduction
The 9400AWY is a family of digital Point to Point microwave PDH and Ethernet radio systems covering
the frequency range from 7 GHz to 38 GHz, consisting of an Indoor Unit (IDU) providing the baseband
processing and tributaries interfaces as well as service channel and supervision, and an Outdoor Unit
(ODU).
IDU and ODU are connected with a single standard coaxial cable (up to 150 meters / 492 ft) carrying the
main traffic, the remote power supply voltage for the ODU and auxiliary information.
As shown in Fig. 2. below, one 9400AWY radio link is composed by two 9400AWY Network Elements
(ULS NE), having the same hardware and software configurations, with the exception of the go and return
channel frequencies (complementary to each other), and the supervision network’s NE specific data.
9400AWY 9400AWY
ULS NE “A” ULS NE “B”
ETSI RADIO
ODU ODU
max 150 m max 150 m

ETSI PDH ETSI PDH
ETHERNET ETHERNET
SERVICE CH. SERVICE CH.
IDU SUPERVISION IDU
NETWORK
Fig. 2. 9400AWY radio link
N.B. With the exception of Chapter 3–2 – Line–Up and Commissioning on page 361, this Manual
deals with the description of a single 9400AWY Network Element.
3DB 16142 CAAA Ed.01A–DRAFT 33 / 576

ULS NE has the aim to multiplexer/demultiplexer the main tributaries (up to 32 E1 and up to two 10/100BT
Ethernet Tributaries with different modulation formats, according to the following Tab. 2. :

Tab. 2. Tributaries and modulations

Max Ethernet
Market Max PDH Tributaries Modulation
Tributaries
2xE1 2 4QAM
4xE1 2 4QAM / 16QAM
ETSI 8xE1 2 4QAM / 16QAM
16xE1 2 4QAM / 16QAM
32xE1 0 16QAM
The main functions performed by ULS NE are the following:
– Multiplexer/Demultiplexer
The multiplexer function receives main tributaries and generates a PDH frame.
The demultiplexer function receives a PDH frame and generates main tributaries.
– Signal Protection switch (if any)

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

The function converts a radio frequency signal into an internal logic level signal, and vice versa
(RPPI). Specifically, the following functions are performed:
• Modulation and Tx functions in the transmit side
• Demodulation and Rx functions in the receive side
ULS NE can be composed by:
– one radio channel (1+0 configurations);
– two radio channels (1+1 configurations).
The 2+0 configuration is not supported.
34 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.2 Equipment architecture
1–2.2.1 Split–mount architecture

The 9400AWY system has been designed in a split mount architecture. As shown in Fig. 3. on page 36, it
consists of three main parts.
– Indoor Unit (IDU) details in paragraph 1–2.2.2 on page 38
– Outdoor Unit (ODU) details in paragraph 1–2.2.3 on page 45
– IDU–ODU cable(s) details in paragraph 1–2.2.4 on page 42
IDU and ODU are connected with a single standard coaxial cable carrying the main traffic, the remote
power supply voltage for the ODU and auxiliary information.
– IDU
The mechanical structure adopted comply with ETSI/19” standard practice.
IDU units can be also inserted in a standard ETSI rack, or placed on a desk, or mounted on a wall.
– ODU
The ODU can be installed on standard poles, wall or pedestal mount, with an appropriate fastening
system, which guarantees the coarse and fine pointing, even when a faulty ODU has to be replaced.
The ODU (one or two depending on the configuration 1+0 or 1+1) incorporates the complete RF
transceiver and can be associated with an integrated 30 cm, 60 cm, 90 cm or 120 cm (1, 2, 3 or 4
ft) antenna or separate antenna, if a larger diameter is needed. The ODU is capacity–independent
and consists of a single cabinet (size and weight independent on frequency) with a solar shield.
The cabinet is a very compact and robust weatherproof (IP 67) container, designed to be compatible
with hot and very sunny climatic zones.
The ODU can be rapidly installed on standard poles with an appropriate fastening system. The pole
mounting is the same for 1+0 or 1+1 configurations from 7 to 38 GHz.
The ODU is fixed by means of quick latches. This system allows to change the ODU without altering
antenna pointing.
N.B. An IDU+ODU full–indoor configuration (obviously without antenna) is also available; its physical
implementation is described in the Installation Handbook.
3DB 16142 CAAA Ed.01A–DRAFT 35 / 576

9400AWY R.2.1 (1+0) SPLIT–MOUNT SYSTEM
ODU Ch#1

Antenna
ODU
IDU–ODU cable
NE
16xE1 DISTRIBUTOR SHELF (75W example) ULS
IDU
IDU MAIN UNIT Ch#1
9400AWY R.2.1 (1+1) SPLIT–MOUNT SYSTEM
for possible ODU (1+1)

configurations
see Fig. 4. on page 37
ODU
IDU–ODU cables
NE
ULS
E
C D
IDU
B
Legend:
E 32xE1 DISTRIBUTOR SHELF (120W example)
D SERVICE CHANNELS PROTECTION BOX
C E1 PROTECTION BOX
B IDU EXTENSION UNIT Ch#0
A IDU MAIN UNIT Ch#1
Fig. 3. 9400AWY R.2.1 split–mount system
36 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Antenna CH 0 Antenna CH 1
ODU CH 0 ODU CH 1
to IDU EXTENSION UNIT to IDU MAIN UNIT
ODU (1+1) HSB–SD or FD–DA AP with two antennas
COUPLER
ANTENNA
ODU CH 0
ODU CH 1
ODU (1+1) HSB with one antenna
N.B. this drawing is an example referred to the coupler used in

13–38 GHz configurations.
Couplers used in 7–8 GHz configurations are shown in
Fig. 43. on page 113.
Double Polar Antenna
ODU CH 0 ODU CH 1
ODU (1+1) FD–AP with one double polar external antenna
Fig. 4. Possible configurations of ODU (1+1)
3DB 16142 CAAA Ed.01A–DRAFT 37 / 576

1–2.2.2 IDU (Indoor Unit)

The IDU incorporates the base–band processing and offers tributaries interfaces as well as service

channel and supervision.

The IDU is frequency–independent, but capacity–dependent.
As shown in Fig. 3. on page 36, up to 2 active subracks (the Main IDU unit and the Extension IDU unit)
and some additional passive boxes are used as basic elements to build the following configurations:
– 1+0: this configuration includes:

• one Main IDU unit
• one/two optional IDU Distributor Shelf/ves
• one optional E1 Protection Box
• one optional Service Channels Protection Box
• and necessary interconnection cables.
Fig. 7. on page 40 shows the block diagram.
– 1+1: this configuration includes:

• one Main IDU unit
• one Extension IDU unit
• one E1 Protection Box
• one Service Channels Protection Box
• one/two optional IDU Distributor Shelf/ves
• and necessary interconnection cables.
Fig. 8. on page 41 shows the block diagram.
In 1+1 configuration:
– the Main and Extension units are interconnected by means of an auxiliary flat cable (100–wires SCSI
front panel connector)
– the protection of E1 signals at line side is achieved by the E1 Protection Box
– the protection of Service Channels signals at line side is achieved by the Service Channels
Protection Box
Both the main and the extension IDU units, if not equipped with plugs–in, are physically able to support
up to 16xE1 interfaces. Such capacity can be reduced according to the Software Key employed.
It is possible to accommodate two different types of plug–in alternative to each other, exploiting the same
mechanical space on the front panel:
– “17–32xE1 plug–in” , allowing to support the extension to 32xE1 interfaces, to be plugged onto both
Main and Extension units
– “DATA plug–in” , implementing Ethernet functionalities. This plug–in is plugged onto the Main IDU
unit only.
An optional plug–in, to be plugged onto the Main IDU unit only, allows the AUDIO + USER SERVICE
CHANNEL functionality.
38 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[1] Main IDU unit
This is a common item for 1+0 and 1+1 systems. It includes the Mux/Demux and the cable interface
functions for the main channel.

Onto the main unit is plugged the microprocessor unit implementing the EC (Equipment Controller)
functionalities.
For details, refer to para.1–3.2 on page 67 .
[2] Extension IDU unit
This is an item specific for 1+1 systems. It includes the Mux/Demux and the cable interface functions
for the spare channel.
The Hitless Switch functionality (RPS RX) is embedded.
[3] Power supply
One PSU is integrated in each of the Main and Extension units; the main characteristics are:
• Floating (48–60) VDC nom. ± 20%
N.B. No Fans Unit are foreseen inside the 9400AWY IDU units.
[4] Flash Card and Software Key
A Flash Card (containing the system software and a Software Key) is always plugged onto the Main
unit. The Software Key allows flexibility in choosing user interfaces and modulation.
[5] Protection Boxes
The E1 Protection Box and Service Channels Protection Box, used in 1+1 configurations, are
shown in Fig. 5. and Fig. 6. below. They are passive components exploiting the splitting functions
of relevant signals from/to the Main IDU and Extension IDU units and from/to the User lines, as
shown in Fig. 8. on page 41 . Their use is recommended also in 1+0 systems.
User line side equipment side
Fig. 5. E1 Protection box
User line side equipment side
Fig. 6. Services Protection box
Such boxes have been designed in order to have the connectors present at User line side exactly
equal to those of the 9400AWY Rel.2.0 IDU Main and Extension units.
In this way, Customers wishing to replace the 9400AWY Rel.2.0 IDU platform with the 9400AWY
Rel.2.1 IDU platform can do it without refurbishing the existing station cabling and DDF wiring.
For details, refer to para.1–3.4 on page 75 (E1 Protection Box) and to para.1–3.5 on page 80
(Service Channels Protection Box).
3DB 16142 CAAA Ed.01A–DRAFT 39 / 576

[6] Distribution shelves

For the physical connection of the User signal cables to the main tributaries connectors of the IDU

Main and Extension units, two main solutions are envisaged:

• usage of the Customer Plant Distributor racks, connected to the IDU main tributaries
connectors by means of Customer own cables or cables supplied by Alcatel–Lucent;
• usage of Alcatel–Lucent distributor subracks, to be housed in the same rack where 9400AWY
IDU shelves are installed. Fig. 3. on page 36 shows two examples of the possible types of
Alcatel–Lucent distributor shelves optionally available for this purpose.
For details, please refer to the Installation Handbook.
[7] IDU configurations from factory
Different IDU configurations (unprotected 1+0 or protected 1+1) are available from factory:
• 16xE1 configurations:
– 16xE1 (base configuration)
– 16xE1 + AUDIO & USER SERVICE CHANNEL plug–in
– 16xE1 + 2 x Ethernet plug–in
– 16xE1 + AUDIO & USER SERVICE CHANNEL plug–in + 2 x Ethernet plug–in
• 32xE1 configurations:
– 32xE1
– 32xE1 + AUDIO & USER SERVICE CHANNEL plug–in.
All sub–equipped configurations delivered from factory can be upgraded later by means of the
specific upgrade kits, as described in chapter 4–7 on page 509.
[8] Block diagrams
Main board Main IDU

(JBIDUM)
Ethernetdata
2 x 10/100 BaseT plug–in
Ethernet plug–in EPS
E3/DS3plug–in
17–32E1 16 E1/DS1plug–in MUX/DEMUX

17–32E1 plug–in
(JAIDUE1) ODU
1–16E1 IDU –ODU
IDU–ODU
NMS_V11
NMS_G703
interface
Audiochannels
Audiochannels
Audiochannels
+ +ServiceChannel
V11 + G703 PSU
ServiceChannel(64Kbit/s) Plug–in (JAIDUSC)
Plug–in
uPuP
EC / RC
Alarms& housekeepings
RS–232 10/100 BaseT
ECT OS (or ECT)
N.B. Ethernet and 17–32E1 plug–ins are in alternative.
Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram
40 / 576 3DB 16142 CAAA Ed.01A–DRAFT

N.B.
Extension IDU
Extension board ODU
(JBIDUE)
E1 PROTECTION BOX IDU–ODU
E3/DS3 plug –in
interface
16 E1/DS1
E1/DS1 Plug
1617–32E1 plug –in
–
17–32E1 17–32E1 plug–in
(JAIDUE1) MUX/DEMUX
1–16E1 1–16E1
PSU
EPS & RPS
Service Channel (64Kbit/s)

Interconnection cable
Main board Main IDU

Ethernet data (JBIDUM)
plug –in
2 x 10/100 BaseT Ethernet data
Ethernet plug–in
plug
E3/DS3 plugin–in
EPS
17–32E1 16 E1/DS1 plug –in

17–32E1 plug–in MUX/DEMUX
(JAIDUE1)
ODU
1–16E1 IDU–ODU
NMS_V11 interface
NMS_G703
Audio channels
Audio channels
Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram

Service Channels + +Service Channel
V11 + G703 PSU
Service Channel (64Kbit/s)
Plug –in (JAIDUSC)
Plug–in
On Main IDU unit, Ethernet and 17–32E1 plug–ins are in alternative.

(64Kbit/s) EC
uPuP/ RC
SERVICE CHANNELS
PROTECTION BOX Alarms & housekeepings
RS–232 10/100 BaseT
ECT OS (or ECT)
41 / 576
1–2.2.3 ODU (Outdoor Unit)

The ODU is capacity–independent, but frequency–dependent.

a) ODU types:
In 9400AWY R.2.1, only the 32E1 ODU types can be used.
N.B. The 16E1 ETSI and 16DS1 ANSI–FCC ODU types (used in 9400AWY R.1.0 and R.2.0)
cannot be used in 9400AWY Rel.2.1 environment.
b) ODU air interface compatibility:
ODU 32E1 ODU 32E1
IDU ETSI IDU ETSI
SW2.1.0 SW2.1.0
Fig. 9. ODU air interface compatibility
c) Air interface compatibility: frame arrangement

The Air frame is the AWY format respecting the bandwidth partitioning between traffic and dedicated
service channels.
d) ODU unit
The ODU consists of a cabinet including the modem + transceiver of a channel. The mechanical
structure utilizes an outdoor IP67 cabinet.
Two mechanical solutions are adopted:
• one for all frequency bands from 13 to 38 GHz, where the branching (diplexer) is internal to the
ODU cabinet; the only differences among the frequency bands are related to the diplexer and
the RF section;
• another for all frequency bands from 7 to 8 GHz, where ODU is composed by two independent
units: the branching (diplexer) and the RF section (transceiver).
All configurations are available for each frequency band.
The ODU presents one output port at which a single polarization integrated antenna (30 cm or 60
cm diameter) or a waveguide for not integrated antenna connection can be connected.
The ODU is capacity–independent.
The ODU consists of subunits which carry out the following main functions (see Fig. 10. on page 43):
[1] Modem: It consists of a base–band part and an IF part. The main functions are:
– Cable interface: DC splitting, echo cancellation, clock recovery

– HDB3 coding/decoding
– Modulation and demodulation
– Digital to analog conversion
– Analogue filtering
– Up–conversion in Tx side in the frequency range of 1 GHz to 2.1 GHz
– Down–conversion in Rx side from 675 MHz to base band
– Control function for hardware configuration and dialog with the IDU.
42 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[2] Front–End. The main functions are:
– AGC IF amplification
– Up–conversion to the RF Tx channel frequency

– Transmit power control range of 30 dB

– RF loop–back
– Double mixers at Rx side (the frequency of the signal sent to the modem board is 675 MHz
whatever the frequency band and shifter).
[3] Synthesizer unit
– The RF LO in the overall frequency range of 3.8 GHz to 5.7 GHz

– The IF LO in the frequency range of 1.0 GHz to 2.1 GHz
[4] Power Supply Unit: it is screwed on the Front End box
[5] Microwave Diplexer: it is inserted between the front end and the antenna. Its scope is to filter
all interfering signals and harmonics. It consists of two band–pass filters: one for the Rx and one
for the Tx. The rejection between these two parts is more than 70 dB. The insertion losses are
less than 2 dB.
Fig. 10. ODU block diagram
e) Solar shield
Even if the ODU has been designed to work without solar shield, this one is always delivered with
each ODU.
N.B. Note : the ODU is qualified for a room temperature of +55 0C maximum. In case of solar
radiation (1120 W/m2), the maximum room temperature is reduced to +40 0C (ETS 300
019–2–4.1). It assumes that the protection of the solar shield is 15 0C.
3DB 16142 CAAA Ed.01A–DRAFT 43 / 576

f) ODU configurations

The ODU configurations available are:

• for the employment in 1+0 unprotected systems:
– 1+0
• for the employment in 1+1 protected systems:

– 1+1 HSB
– 1+1 HSB SD
– 1+1 FD AP
– 1+1 FD DA
Tab. 3. below depicts the corresponding radio configurations.
Tab. 3. 13 to 38 GHz 4/16 QAM configurations
Configuration ODU cabinet RF channeling Coupler Antenna
1+0 1 NO 1
1+1 HSB 2 1/10 dB asymmetric 1
1+1 HSB SD 2 NO 2
1
1+1 FD AP 2 NO (non–integrated
only)
1+1 FD DA 2 OR NO 2
Legend:
AP = Alternate polar
DA = Dual antenna
g) ODU Coupler
The ODU coupler (shown in Fig. 42. on page 112 for 13–38 GHz bands, and in Fig. 43. on page 113
for 7–8 GHz bands) is used in the 1+1 HSB configuration.
The 1+0 configuration is comprised of a simple diplexer inside the cabinet while the protected
configurations (1+1) are always comprised of two cabinets and one 1/10 dB asymmetric coupler for
HSB configuration.
The couplers are connected between the cabinets and the antenna.
44 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.2.4 IDU–ODU cable
The connection between the IDU and the ODU is realized with a single coaxial cable and N–50 ohm
connectors (2 cables in 1+1 configurations).

On this cable the following signals are present:
– DC voltage to the remote power supply of the ODU;

– HDB3 Tx signal;
– HDB3 Rx signal.
The HDB3 signal is an aggregate signal including the main signal, auxiliary signal and the IDU–ODU
service channels.
The bit rate of the aggregate signal is listed in the following table.
Tab. 4. Bit rate of the IDU–ODU signal on the cable
ETSI (2 to 16xE1) AWY configuration 39.168 Mbit/s
ETSI (2 to 16xE1) UX configuration 39.437 Mbit/s
ETSI (17 to 32xE1) AWY configuration 78.336 Mbit/s
The IDU–ODU cable is a standard coaxial cable whose characteristics are specified in para.1–5.5 on page
134.
3DB 16142 CAAA Ed.01A–DRAFT 45 / 576

1–2.3 System configurations

The configurations available are:

– Unprotected configurations (1+0)
described in para.1–2.3.1 herebelow
– Protected configurations (1+1)

described in para.1–2.3.2 on page 47.
1–2.3.1 1+0 Unprotected configurations
The 1+0 unprotected terminal is made up of the following elements:
– one Outdoor Unit (ODU) incorporating the complete RF transceiver (modem, RF units, branching
filter) and an integrated or separated antenna.
The ODU is capacity–independent.
– one Indoor Unit (MAIN IDU unit) incorporating the base–band processing and offering tributaries
interfacing as well as service channel and supervision.
The IDU is frequency–independent.
– one optional E1 Protection Box
– one optional Service Channels Protection Box
– one/two optional IDU Distributor Shelf/ves
– one IDU–ODU coaxial cable
Fig. 11. below shows the IDU+ODU block diagram.
IDU 1+0 1 x ODU

DISTRIBUTOR SHELF
interconnections IDU–ODU cable RT
IDU MAIN UNIT
Fig. 11. 9400AWY (1+0) IDU + ODU block diagram
The possible capacities and modulations depend on:
– the (1+0) IDU equipment provisioning (see point [7] on page 40, and and Tab. 5. on page 66)
– and the employed Software Key (see Tab. 22. on page 89)
46 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.3.2 1+1 Protected Configurations
The protected configurations allow to protect the most critical transmission paths.
The 1+1 configurations include an EPS protection (in Tx and Rx side) and an Hitless Switch (at Rx side)
as standard features.
In the protected configuration the main traffic and service channels are automatically protected.
In the following, IDU and ODU protected configurations are described in:
– para.1–2.3.2.1 below: IDU (1+1) configurations

– para.1–2.3.2.2 on page 48 : ODU (1+1) configurations
1–2.3.2.1 IDU (1+1) configurations
The IDU (1+1) system is implemented by:
– one Main IDU Unit (mandatory)
– one Extension IDU Unit (mandatory)
– one E1 Protection Box (mandatory)
– one optional Service Channels Protection Box (mandatory if the AUDIO + USER SERVICE
CHANNELS plug–in is equipped)
– one/two optional IDU Distributor Shelf/ves
– cables interconnecting IDU units, protection boxes, and Distributor Shelf/ves.
The possible capacities and modulations depend on:
– the (1+1) IDU equipment provisioning (see point [7] on page 40, and Tab. 5. on page 66)
– and the employed Software Key (see Tab. 22. on page 89)
3DB 16142 CAAA Ed.01A–DRAFT 47 / 576

1–2.3.2.2 ODU (1+1) Configurations

According to the ODU configurations introduced in Tab. 3. on page 44, at radio level the following system

implementations are available:

– 1+1 Hot Stand By (HSB):
• with Space Diversity (SD) see Fig. 12. herebelow
• or without space diversity see Fig. 13. herebelow
– 1+1 with Frequency Diversity (FD):

• FD double antenna AP see Fig. 14. on page 49
• FD one antenna AP see Fig. 15. on page 49
N.B. The radio configurations are independent from the IDU (1+1) configurations described in
previous para.1–2.3.2.1 on page 47.
IDU 1+1 ODU CH 0

HDB3
DISTRIBUTOR SHELF MODEM IF RF
interconnections
E1 PROTEC. SERV.CHAN.
BOX PROTEC.BOX only one RT
transmits
IDU EXTENSION UNIT
ODU CH 1
IDU MAIN UNIT
HDB3
MODEM IF RF
Fig. 12. 9400AWY (1+1 HSB SD) IDU + ODU block diagram
IDU 1+1 ODU CH 0 Coupler
HDB3
interconnections
BOX PROTEC.BOX only one RT 1:10
transmits
IDU EXTENSION UNIT
ODU CH 1
IDU MAIN UNIT
HDB3
MODEM IF RF
Fig. 13. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram
48 / 576 3DB 16142 CAAA Ed.01A–DRAFT

IDU 1+1 ODU CH 0
HDB3
interconnections
BOX PROTEC.BOX both RTs AP
IDU EXTENSION UNIT transmit
ODU CH 1
IDU MAIN UNIT
HDB3
MODEM IF RF
Fig. 14. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram
IDU 1+1 ODU CH 0

HDB3
interconnections
BOX PROTEC.BOX both RTs
transmit
IDU EXTENSION UNIT
ODU CH 1
IDU MAIN UNIT
HDB3
MODEM IF RF
Fig. 15. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram
3DB 16142 CAAA Ed.01A–DRAFT 49 / 576

1–2.4 Equipment Craft Terminal and TCO Suite

The Local Operator can manage the Equipment software programs and most configuration data through

the Equipment Craft Terminal 1320CT connected to the Equipment’s F or Ethernet interface.

The Craft Terminal characteristics (computer configuration) are listed in para.3–1.1.1 on page 313.
The Craft Terminal is a project in charge of the local management of single network elements, providing
ITU– compliant Information Model Interface to the Network Element.
Multiple NE management up to 128 Network elements is possible obtaining a remote Craft Terminal
application.
The general information on the Craft Terminal is presented in the:
• 1320CT Basic Craft Terminal Operator’s Handbook (see Tab. 78. on page 557)
that the operator has to read before this Handbook.

In this Handbook is given the general description regarding use, navigation, rules, etc., common to all the
NE using the same Craft Terminal.
Furthermore, the same handbook contains the detailed description of common operations as “Installation”
and common screens as “Network Element Synthesis view”.
The Network Element Synthesis view is the first view presented to the operator entering the application.
Starting from this view it is possible to login to the NE and then to enter the EML–ULS views, which directly
allow to manage the Network Element.
A detailed description of the 9400AWY EML–ULS screens is given in the dedicated Section of this
handbook:
• SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139
1–2.4.1 ECT
Alcatel–Lucent TMN management products 1320 CT called Craft Terminals (CT) consists of a compatible
personal computer and application software specially developed for monitoring transmission equipment.
The CT designed to monitor a single transmission equipment is called Equipment Craft Terminal (ECT)
or 1320CT.
For each 9400AWY station an Alcatel–Lucent proprietary SWP (SoftWare Package) is employed, which
depends on the product–release and the NE (Network Element) associated to the specific configuration.
1–2.4.2 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 or Ethernet interface of the NE, to zoom and
perform a complete set of management operations on all the reachable NEs in the network.
The Remote NE can be physically reached through the NMS channels or Ethernet LAN.
RECT can be connected to any NE pertaining to the same area of the local NE and to any NE pertaining
to different areas (assuming that the DCN network has been correctly designed and hence inter–area
communication is possible from networking viewpoint).
Of course, due to the limitation of the physical resources in the Equipment Controller of the NE, some
network design constraints must be taken into account as the total number of managed NEs (128).
50 / 576 3DB 16142 CAAA Ed.01A–DRAFT

The RECT features and limitations are briefly the following:
1) The RECT function provides a remote login facility similar to those offered by an OS to manage
several configured NEs, included the local one.

2) The contemporaneous presence of the RECT function and an OS is possible. The access
disable flag avoids access conflict between the OS and both RECT and ECT on some
operations as configuration modification and remote control with access filtering.
3) The NE which may be remotely controlled by a RECT must be configured and must be loaded
with the same SW version supporting the RECT function. A NE not supporting RECT function
shall refuse the incoming association issued by a RECT and the ECT displays only local
information.
4) Only three RECTs shall be active at a time over one NE. The coexistence of ECTs and RECTs
in the whole network is guaranteed since the conflict in configuring the NEs is solved locally by
the NE itself.
5) The operator, through the RECT function, is able to see the alarm synthesis of the whole
network .
6) In a network the maximum number of NEs equipped with the RECT function are 128. This value
identifies what it is understood as ”small network” for which the RECT function may replace the
Element Manager.
1–2.4.3 TCO Suite
The TCO Suite is a feature that mainly allows the operator to access and configure the NE from his/her
PC without the need for software installation in PC environment (i.e. running the TCO Suite directly from
the SWP CD–ROM).
TCO Suite works through web pages with simple operations available with a single mouse click.
Please refer to para.2–2.2 on page 146 for details.
3DB 16142 CAAA Ed.01A–DRAFT 51 / 576

1–2.5 SW allocation and Flash Card contents

1–2.5.1 Allocation of equipment and craft terminal software

Fig. 16. herebelow roughly depicts the NE main parts containing the local SW and the interfaces with the
Operator (Extension Unit and RT–0 are present in 1+1 configuration and are not equipped in 1+0
configuration).
MAIN UNIT
JBIDUM SUBUNIT
FLASH
F CARD
EQUIPMENT
Ethernet
CONTROLLER
RAM
EXTENSION UNIT
JBIDUE
SUBUNIT
RT–0
FLASH
EPROM
ODU
CONTROLLER
RAM
RT–1
FLASH
EPROM
ODU
CONTROLLER
RAM
Fig. 16. Equipment main parts containing local SW
52 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Once the system has been configured and activated (as explained in Section 3 Installation and
Commissioning on page 311), Equipment and Craft Terminal must not necessarily be left connected,
because equipment contains all the software necessary for its working.
This equipment local software comprises programs and configuration data. Programs and data are
managed differently from each other:
a) SW resident in Equipment Controller and Flash Card
Whole Equipment SW (programs and configuration data) is contained in the Flash Card housed in
MAIN unit (the Flash Card contains also the software (programs and configuration data) relevant to
the peripheral units, i.e., RTs in Fig. 16. on page 52).
This flash card is removable (i.e. replaceable), and the programs can be overwritten by a SW
download from CT (through F or Ethernet interface interface) or Network Management Operation
System (through Ethernet interface) to the MAIN unit.
More precisely, as shown in Fig. 17. on page 54, the Flash Card contains two independent instances
of the Equipment SW programs (one active, the other stand–by), so that the above cited SW
download is actually done toward the stand–by instance, while equipment goes on working with the
SW programs of the active instance. Swapping between the two instances is done only under
Operator’s request.
b) SW resident in Peripheral Units
The Peripheral units (RTs) contain their own local SW (programs and configuration data), housed in
a local Flash Eprom (physically not removable). The programs in this local Flash Eprom can be
overwritten by means of a SW download from the Equipment Controller with the same
active–standby duplication described before for the Equipment Controller.
c) Equipment Configuration Data
The whole equipment configuration data (together with programs) are stored in the MAIN unit Flash
Card. Refer to point 1–2.5.2 on page 54 for details.
3DB 16142 CAAA Ed.01A–DRAFT 53 / 576

1–2.5.2 Flash Card types and content

Whole Equipment configuration data and programs are contained in the Flash Card, as shown in

Fig. 17. below:

Fixed Data SOFTWARE KEY
SW SW
SW instances COMMIT STAND–BY
VERSION VERSION
(ACTIVE) (not active)
MIB
NE Data
NE network
routing data
Fig. 17. Flash Card content
[1] Fixed Data
The Software Key allows flexibility in choosing user interfaces and modulation as shown in
Tab. 22. on page 89.
It is strictly associated to the Flash Card Technical Code, and cannot be changeable, but with Flash
Card upgrade (see para.4–7.3 on page 518).
[2] SW instances
The SW COMMIT VERSION is that used by the system.
The SW STAND–BY VERSION instance is created the first time a SW download from ECT to the NE
is carried out.
A new SWP download is envisaged whenever a new SWP package version or release (new with
respect to that presently loaded in the system) is supplied to Customer (*).
(*) for the meaning of SWP package version and release refer to para.C.3.2 on page 559.
As supplied by Alcatel–Lucent factory:
• usually only the SW COMMIT VERSION is present; in other cases the SW STAND–BY instance
is loaded with the SW version immediately previous (if any) with respect to the COMMIT one
• unless differently required by Customer, the SWP–version downloaded in Factory is the most
recently released at the date of Flash Card delivery to the Customer.
The management of these SW instances is described in Chapter 2–13 – Software Management

on page 301.
54 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[3] NE data
N.B. as shown in Fig. 17. on page 54, differently from SW instances, NE data are present as
single instances in the Flash Card.

a) MIB
Most (but not all) configuration data set is named MIB (Management Information Base).
Such data are defined by Craft Terminal and can be changed only within the limits (Base
configuration) implicitly defined by the employed Flash Card type.
– if the Flash card is supplied together with 9400AWY equipment, NE configuration data are
consistent with the actual HW configuration
– if the Flash card is supplied alone, usually and unless differently required by Customer,
NE configuration data are set to default values
MIB can be saved as a file in the Craft Terminal (or OS) environment, as well can be restored
in the Flash Card retrieving this file from the Craft Terminal (or OS), as described in detail in
Chapter 2–14 – MIB Management on page 305.
b) NE network routing data

Defined by Craft Terminal or by TCO Suite Set–Up Tool, they are:
1. Local configuration ⇒ System’s local address

2. NTP server configuration
3. Interface configuration ⇒ NMS configuration
⇒ Ethernet configuration
4. IP configuration ⇒ IP Static Routing configuration
⇒ OSPF AREA configuration
Presently, all those listed parameter are NOT stored into the MIB file.
Nevertheless, it is possible to create, save and recover configuration files having the “.qcml”
extension (for details refer to para.3–2.3.6 on page 373). Such a file contains (besides other
data) the NE network routing data defined above.
– if, before delivery, Customer communicates the NE network routing data values, they are
stored in the supplied Flash card by Factory
– otherwise, the NE network routing data are set to default values.
3DB 16142 CAAA Ed.01A–DRAFT 55 / 576

[4] System restart

The system restart (reloading of all RAMs present in the system with information stored in the Flash

Card) is without traffic interruption and is carried out:

• after the activation of a new SWP
• after power off/on
• after EC/OC reset (manual of after new SWP activation)
• after plug–in insertion
[5] FPGA download
As a whole, the correct performance of a certain SWP is granted if the system software works
together with the FPGAs’ SW versions specifically required by the SWP itself. When a new SWP is
loaded into the NE, the SW versions present in the equipped FPGA may not be consistent with those
expected, so FPGA upgrade could be necessary.
When a new SWP is loaded from ECT into the ULS NE, also the SW images of FPGAs are loaded
into the PQ/ECRC. Each of these SW images is downloaded automatically toward the relevant FPGA
only in case the FPGA version currently running is lower than that made available by the new SWP.
The FPGA version comparison and the possible FPGA download are without traffic interruption and
are launched every time a system restart is carried out.
56 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.6 General on equipment installation and SWP installation and
management
This paragraph introduces the basic information regarding the main phases for 9400AWY HW and SW
installation, and those regarding the software management, with particular emphasis on SWP release and
versions upgrading situations.
N.B. Before reading this paragraph, it is suggested to read SW allocation and Flash Card contents
(para.1–2.5 on page 52).
N.B. Please refer to para.C.3.2 on page 559 for the meaning of SWP Release, Version and Patch
Level.
Information given in the following is:
– Main phases for 9400AWY HW and SW installation on page 58
– First SWP installation in PC and NE environments on page 59
– How to check ECT and NE SWP versions on page 61
– Common situations requiring ECT and/or NE upgrade on page 63
– Flash Card related special procedures on page 63
– Craft Terminal related special procedures on page 63
– NE configuration data change and save on page 64
3DB 16142 CAAA Ed.01A–DRAFT 57 / 576

1–2.6.1 Main phases for 9400AWY HW and SW installation

The summary procedure depicted in Fig. 18. below presumes that the SWP version loaded in factory

inside the NE’s Flash Card corresponds to that of the SWP CD–ROM delivered to Customer with the

equipment.
HW INSTALLATION ECT INSTALLATION

described in: described in:
9400AWY Chapter 3–1 – SWP installation in PC

Installation Handbook environment on page 313
EQUIPMENT POWER–ON AND COMMISSIONING

described in:
Chapter 3–2 – Line–Up and Commissioning
on page 361
CREATION OF NE OPERATOR PROFILES

described in
para.2–3.6 on page 218
NE DATA SAVE
described in
para.1–2.6.8 on page 64
Fig. 18. Main phases for 9400AWY HW and SW installation
58 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.6.2 First SWP installation in PC and NE environments
Fig. 19. depicts the main phases for SW management, when it is loaded the first time in PC and NE
environments.
SWP
CD–ROM
1) SWP LOADING IN PC ENVIRONMENT
CRAFT TERMINAL
2) NEW SWP
INSTALLATION
6) MIB
BACK–UP
3) NE SWP LOADING
INTO EQUIPMENT
CONTROLLER
(if necessary)
DURATION:
– 1/2 hour with
interface F
– some minutes with
Ethernet interface
4) AUTOMATIC SW
5) NE CONFIG. DOWNLOAD TO
DATA MNGT SUPERVISOR UNITS
7) MIB (if necessary)
RESTORE
DURATION:
some minutes
Fig. 19. Software management main phases
3DB 16142 CAAA Ed.01A–DRAFT 59 / 576

The SW management can be distinguished into:

– program management, i.e.:

• (1) and (2) : SWP loading from CD–ROM to the Personal Computer, after which the PC
becomes and can be used as the Equipment Craft Terminal (abbreviated as ECT or CT)
• (3) NE SWP downloading from ECT toward the Network–Element’s Equipment Controller (EC),
if necessary (it is necessary if the NE SW–version is lower than that of the ECT)
N.B. in general, first–time system installation is carried out with the NE’s flash card loaded
in factory with the same SWP–version of the ECT, so that this phase is usually not
necessary
• (4) SW downloading from EC toward the Peripheral Units, always automatic (this phase is
carried out only whenever the SW–versions present in the Peripheral Units are lower than those
available in the ECT’s SW components)
– NE configuration data management:
• (5) NE configuration data definition and equipment line–up and commissioning
• (6) NE configuration data save in Equipment Craft Terminal (MIB back–up)
• (7) NE configuration data restore from Equipment Craft Terminal (MIB restore, if necessary)
The first–time installation can be distinguished in two main procedures:
– SWP installation in PC environment

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

that includes tasks (3) to (4) mentioned above.
– NE configuration data definition and equipment line–up and commissioning

that includes task (5) mentioned above.
At the end of the first–time installation, the CT and NE situation is the standard one:
1) Network Element already configured with the more recent SWP version and Craft
Terminal already available.
ECT NE
ECT release = NE release
A.B.c ECT version = NE version A.B.c
This is the typical situation of new installations: the Network Element SW configuration matches
the available Craft Terminal SWP version, so that the NE can be logged–in and the Operator
can carry out the required operations, without any incompatibility problems.
60 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.6.3 How to check ECT and NE versions
[1] How to check ECT version

This check can be done with ECT not connected to any NE

(2)
(1)
(3)
(4) read version
Fig. 20. How to check ECT version
3DB 16142 CAAA Ed.01A–DRAFT 61 / 576

[2] How to check NE version
Proceed as follows:

1) Carry out NE Login (as described in para.2–2.5.2 on page 177)

2) From the Menu Bar of the 9400AWY Main view that opens after NE Login (Fig. 94. on page
185), perform SW Download ⇒ SW Status
version committed
(active)
version stand–by
(not active)
N.B. When the equipment is shipped from factory, two SW versions are present in the flash card:
– that committed is the actual SW version defined by the SWP name (e.g. V2.0.4)
– that stand–by is the immediately previous SW version (e.g. V2.0.3)
Fig. 21. How to check NE SW version (example)
WARNING FOR V.2.1.0 Fig. 21. above is just an example ! For the SWP this manual refers to, only one
SW version is present and enabled (V2.1.0) in the flash card delivered from
factory. The other SW bank does not exist.
62 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–2.6.4 Common situations requiring ECT and/or NE upgrade
The following situations require CT and/or NE upgrading, in order to reach the standard situation defined
in point 1 ) on page 60:

1) Both Network Element and Craft Terminal already configured with a SWP version older
than that made available by the a new SWP version (SAME RELEASE)
ECT NE
running release = SWP release SWP
CD–ROM
A.B.c = A.B.c running version < SWP version
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.2.1.0), in the case a newer version of the same A.B SWP package has to be installed
(e.g.2.1.1).
In this case, you must upgrade both ECT and NE as described in Chapter 4–9 on page 525.
After that, the situation is equal to that of point 1 ) on page 60.
2) Network Element already configured with the more recent SWP version, but the Craft
Terminal is not available or has a version older with respect to that of the Network
Element(s).
ECT NE
ECT release = NE release
A.B.c ECT version < NE version A.B.d
In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter
3–1 on page 313. After that, the situation is equal to that of point 1 ) on page 60.
1–2.6.5 Flash Card related special procedures
Taking into account the information contained in the Flash Card (see para.1–2.5.2 on page 54 for
explanations, if necessary), you could need to:
3) for system upgrade purposes, replace the flash card currently in use with a different type
Flash Card
In this case, please refer to para.4–7.3 on page 518.
4) for corrective maintenance purposes, replace the faulty flash card currently in use with a
spare Flash Card
In this case, please refer to Chapter 4–6 Spare Flash Card management and replacement
procedures on page 505
1–2.6.6 Craft Terminal related special procedures
If you need to:
5) de–install Alcatel–Lucent SW from the PC used as Craft terminal, refer to chapter 4–10 on
page 526.
3DB 16142 CAAA Ed.01A–DRAFT 63 / 576

1–2.6.7 NE configuration data change and save

It must be emphasized that , every time you change the equipment configuration data (see para.1–2.5.2

on page 54), you must always save the relevant data:

a) data present in Flash Card’s MIB bank [see point a ) on page 55]
Data present in Flash Card’s MIB bank can be saved in a MIB back–up file as described in Chapter
2–14 on page 305.
The same paragraph explains how to recover MIB data from the MIB back–up file.
The procedures in this handbook make often reference to the MIB data restore from the MIB back–up
file.
If you change the equipment configuration data without carrying out the MIB back–up save, in case
of troubles you will have to create again the NE configuration data by means of a lot of individual ECT
commands, wasting time and with high probability of errors.
b) data that are not saved in the MIB back–up file [see point b ) on page 55]
Only NE network routing data are not saved in the MIB back–up file.
Nevertheless, it is possible to create, save and recover configuration files having the “.qcml”
extension (for details refer to para.3–2.3.6 on page 373). Such a file contains (besides other data)
the NE network routing data.
1–2.6.8 NE data save after commissioning completion
For the NE, create a folder containing the following files:

– the MIB back–up file [point a ) above]
– the “.qcml” configuration file [point b ) above]
– the “text” configuration file. For this purpose you can use:
• the Configuration Info of the TCO Suite Alarms & Settings function (see para.2–2.3.4 on
page 167)
• the Current Configuration view by Craft Terminal (see para.2–3.7 on page 222)
– the TRS & SAT MSWord file. This can be used, in the future, to compare system performance to that
verified at the commissioning phase.
Maintain this folder updated whenever you make changes on the NE.
64 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3 IDU PROVISIONING AND DESCRIPTION
This chapter gives detailed operative information regarding the IDU shelf’s units available with the
equipment version this handbook issue is relevant to, for provisioning, installation, commissioning and
maintenance purposes. Information given is relevant to assembly/subassembly and front panel drawings,
as well as the usage description of the access points (connectors, visual indicators, buttons). This chapter
is organized as follows:
– Provisioning of IDU shelves on page 66
– Description of IDU Main unit on page 67

• IDU Main Unit LEDs summary on page 69
• Power Supply connector pin–out on page 70
• ECT RS232 connector pin–out on page 71
• OS (or ECT) 10/100BaseT connector pin–out on page 71
• Ethernet tributaries on page 72
– Description of IDU Extension unit on page 73

• IDU Extension Unit LEDs summary on page 74
– Description of E1 Protection box on page 75

• E1 Protection box: connector pin–out on page 76
– Description of Services Protection box on page 80

• Alarms Housekeeping (pin–out and description) on page 81
• NMS V.11 – Audio 1 (pin–out and description) on page 84
• NMS G.703 – Audio 2 (pin–out and description) on page 85
• User service channels (pin–out and description) on page 86
– Provisioning and identification of Flash Cards & Software Keys on page 89
– Provisioning and description of equipment accessories on page 91
Note for all provisioning tables:
– the Technical Code is the technical part number of the item.

N.B. The last two Technical Code letters stand for a ”feasible alternative”, they might
differentiate two items even though still functionally compatible. For this reason the
indicated Technical Code does not include the last two letters (replaced by **).
– please refer to the Installation Handbook for the provisioning of cables and other items that depend
on the installation choices.
Cautions to avoid equipment damage

Carefully observe statements specified in para.1–1.5 on page 32
N.B. For detailed operative information regarding the:
– description of equipment interconnections, please refer to para.3–2.2 on page 363
– equipment installation, please refer to the Installation Handbook
– equipment commissioning, please refer to Chapter 3–2 on page 361
– equipment maintenance, please refer to section 4 – MAINTENANCE on page 447.
3DB 16142 CAAA Ed.01A–DRAFT 65 / 576

1–3.1 Provisioning of IDU shelves

Tab. 5. IDU shelf provisioning for 1+0 and 1+1 configurations

CONFIGURATION
16E1 32E1
Technical Code & 16E1+
16E1 + 32E1 +
Description 2 ETH +
AUDIO 16E1 + AUDIO
16E1 AUDIO 32E1
& 2 ETH &
&
USC USC
USC
3DB16040AB**
X
1 0 IDU 16E1 48/60V PSU
3DB16058AB**
PPLY)
X
NITS
1 0 IDU 16E1 48/60V PSU AUDIO USC

WER SUPP
MA UNIT
3DB16043AB**
X
TSI IDU MAIN
1 0 IDU 16E1 DATA 48/60V PSU

/60V POWE
3DB16061AB**
X
1 0 IDU 16E1 DATA 48/60V PSU AUDIO USC
(48/60V
ETSI
3DB16041AB**
X
1 0 IDU 32E1 48/60V PSU
3DB16059AB**
X
1 0 IDU 32E1 48/60V PSU AUDIO USC
ONFIGURATIONS)
ENSION UNITS
3DB16044AB**
ER SUPPLY)
X X X X
EXT IDU 16E1 48/60V PSU
ETSI IDU EXTENS
(48/60V POWER
(ONLY FOR 1+1 CON
3DB16045AB**
X X
EXT IDU 32E1 48/60V PSU
ION BOXES
3DB16102AA**
X X X X X X
E1 Protection (SCSI 68 / D–sub 37)
PROTECTION
N.B.1
.B.1
3DB16103AA** (X) (X) (X)

X X X
Services Protection (D–sub44 / D–sub15) N.B.2 N.B.2 N.B.2
Equipment interconnection diagram (page) ⇒ 364 365 366 367 368 369
N.B.1 in 1+0 configurations, equipping of protection boxes is optional, but highly recommended.
N.B.2 In 1+1 configurations without Audio + User Service Channel plug–in, equipping of services
protection box is optional, but highly recommended.
66 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.2 Description of IDU Main unit
1 2 A 3 4 5 6 7 8
9 10 11 12 13 14 15 16
17 B C
18
Fig. 22. IDU Main Unit front and rear views
Tab. 6. IDU Main Unit: external interfaces list

Ref.
Connector or item detail Interface / Explanation Details
Fig. 22.
Basic Interfaces (without optional plugs–in)
para.1–3.2.2
(1) SubD 3 Male Station Battery input
on page 70
ON/OFF switch: general
I ⇒ ON
(2) power supply switch
O ⇒ OFF
(IDU Main + its ODU)
RJ45 para.1–3.2.4
(3)
OS (or ECT) 10/100BaseT on page 71
For
(4) Debug RJ45
Factory use only
(8) N 50 ohm Female For IDU–ODU cable (N.B.2)

Acknowledgement: Alarm
attending pushbutton; this
para.4–5.6.2
(9) pushbutton turns OFF LEDs
on page 472
MAJ/MIN and turns ON
yellow LED ATTD
possible use inside

Equipment Controller
(10) corrective
Reset pushbutton
maintenance
Lamp Test pushbutton: it

para.4–4.2.1
(11) allows to HW test the LEDs
on page 461
of the unit
3DB 16142 CAAA Ed.01A–DRAFT 67 / 576

Ref.
Fig. 22.

RS232 connector for NE–CT para.1–3.2.3
(12) SubD 9

serial cable on page 71
(13) SCSI 68 pin Female 1–16E1 – 64 wires (N.B.1)
interconnection with
connector for 100 pin SCSI
Extension Unit,
(14) SCSI 100 pin Female flat cable (used only in 1+1
no pin usage by
configurations)
Customer
connector for Alarms –
(15) SubD 44 Female (N.B.1)
Housekeeping – NMS
para.1–3.2.1
(16) – 9 LEDs
on page 69
(17) + (18) para.1–3.6
Flash Card
+ (A) on page 89
(B) label Data Matrix codification for factory use
Fig. 367.
(C) label unit identification
on page 539
Optional Interfaces (with optional plugs–in)
Connectors according to the equipped plug–in (if any) (N.B.3) :
2 x RJ45 Ethernet user data,
para.1–3.2.5
when Ethernet plug–in
on page 72
(5) is equipped
17–32 E1 – 64 wires,
SCSI 68 pin Female when the 17–32 E1 plug–in (N.B.1)
is equipped
Connectors present only when the Audio + User Service Channel plug–in is
equipped (N.B.3) :
Audio1/2 + G703_V11 User
SubD 44 Female (N.B.1)
Service Channel
(6) + (7)
RJ11 Female for chapter 4–2

EOW telephone on page 453
Notes
(N.B.1) For connector pinout, refer to the Installation Handbook
ATTENTION
(N.B.2) (caution to avoid equipment damage)
The N–type connector carries +48 DC voltage for ODU power supply.
Do not connect measuring instruments directly.
When no plug–in equipped, the slot is closed by a metal plate (inside the panel rear
(N.B.3)
side).
Á ÁÁ
Metal plate is mandatory to ensure EMI–EMC performance
68 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.2.1 IDU Main Unit LEDs summary
Nine LEDs are present on the front panel of the IDU Main Unit [position (16) in Fig. 22. on page 67 ]:
GREEN RED GREEN

RED
YELLOW
GREEN RED RED YELLOW
1) ON = Power ON (green)
2) RDI = Remote Defect Indication (red)
3) MIN = Minor Alarm (red)
4) EOW = Engineering Order Wire (bicolor: yellow if busy; green if free)
5) ODU W = ODU Working (green)
6) ATTD = Attended (yellow)
7) MAJ = Major Alarm (red)
8) LDI = Local Defect Indication (red)
9) ANT = Not operative in current SWP version
Fig. 23. LEDs on the IDU Main Unit front panel
[1] ON – This green LED is ON when the Station Battery is connected, the ON/OFF switch is ON, and
the internal DC/DC is working properly.
[2] RDI – The Remote Defect Indication is a local indication of the Remote Equipment Failure alarms
requiring consequent operator intervention. It is transmitted from the remote station to the local via
the aggregate radio frame. RDI is formed in the remote station by the following roots:
• Main Unit failure (Card Fail)

• Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations)
• Data plug–in failure (Card Fail and Card Missing)
• 17–32xE1 plug–in failure (Card Fail and Card Missing)
• Loss of Signal from Tributaries
• Loss of cable from ODU (IDU–ODU cable loss)
• ODU transmitted/received power alarm (TX Fail/RX Fail)
• ODU incompatible TX power alarm
• ODU incompatible TX frequency alarm (only in 1+1 configurations)
• ODU incompatible shifter
• ODU failure (Card Fail)
[3] MIN – Minor Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, a
MINOR severity.
[4] EOW – This LED refers to the use of the EOW. Refer to chapter 4–2 on page 453 for details.
3DB 16142 CAAA Ed.01A–DRAFT 69 / 576

[5] ODUW – The ODUW led ON identifies the TX activity of the ODU connected to the MAIN unit.
It is OFF in case of:

• IDU–ODU Cable Loss alarm

• Mute function activated

• ODU switching–off command activated in 1+1 HSB configuration
[6] ATTD – The attended LED is ON when the acknowledgement button [position (9) in Fig. 22. on page
67 ] has been pushed
[7] MAJ – Major Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, a high
severity (MAJOR or CRITICAL).
[8] LDI – The Local Defect Indication (LDI) has the purpose to show Local Equipment Failure requiring
consequent actions by operators. The LDI roots are:
• Main Unit failure (Card Fail)

• Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations)
• Data plug–in failure (Card Fail and Card Missing)
• 17–32xE1 plug–in failure (Card Fail and Card Missing)
• Loss of Signal from Tributaries
• Loss of cable from ODU (IDU–ODU cable loss)
• ODU transmitted/received power alarm (TX Fail/RX Fail)
• ODU incompatible TX power alarm
• ODU incompatible TX frequency alarm
• ODU incompatible shifter
• ODU failure (Card Fail)
The lamp test pushbutton [position (11) in Fig. 22. on page 67 ] allows the HW test of all LEDs.
1–3.2.2 Power Supply connector pin–out (MAIN and EXTENSION units)
Tab. 7. Power supply connections
Pin Function
A1 + BATTERY
A2 GROUND
A3 – BATTERY
70 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.2.3 ECT RS232 connector pin–out
Tab. 8. ECT connections

pin 1
RS 232 RS 232
(IDU MAIN side) (PC side)
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
1–3.2.4 OS (or ECT) 10/100BaseT connector pin–out
Tab. 9. OS (or ECT) connections
N.B. Leds are not operative

RJ45 RJ45
Signal Color used
(IDU MAIN side) (OS side)
1 Tx + White/Orange 1
2 Tx – Orange 2
3 Rx + White/Green 3
4 Not used Blue 4
5 Not used White/Blue 5
6 Rx – Green 6
7 Not used White/Brown 7
8 Not used Brown 8
3DB 16142 CAAA Ed.01A–DRAFT 71 / 576

1–3.2.5 Ethernet tributaries

Present on the front panel of the IDU Main Unit [position (5) in Fig. 22. on page 67 ] when the Ethernet

plug–in is equipped.

For the Ethernet user data interfaces the following table summarizes the meaning of the LEDs integrated
in the RJ45 connectors:
Tab. 10. RJ45 connectors leds for Ethernet user data interfaces
Display
Color Led–off Led–on Led blinking
Function
Link and
LEFT LED Green Link down Link up –
activity status
No TX/RX
TX/RX activity
RIGHT LED Yellow activity activity –
detected
detected
72 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.3 Description of IDU Extension unit
9 8
4 5 6 7
1 2 3
B C
Fig. 24. IDU Extension Unit front and rear views
Tab. 11. IDU Extension Unit: external interfaces list

Ref.
Fig. 24.
Basic Interfaces (without optional plugs–in)
para.1–3.2.2
(1) SubD 3 Male Station Battery input
on page 70
ON/OFF switch: general
I ⇒ ON
(2) power supply switch
O ⇒ OFF
(IDU Extension + its ODU)
Lamp Test pushbutton: it

para.4–4.2.1
(3) allows to HW test the LEDs
on page 461
of the unit
(4) SCSI 68 pin Female 1–16E1 – 64 wires (N.B.1)
interconnection with
connector for 100 pin SCSI Main Unit,
(5) SCSI 100 pin Female
flat cable no pin usage by
Customer
Audio1/2 + G703_V11 User
(6) SubD 44 Female (N.B.1)
Service Channel
para.1–3.3.1
(7) – 3 LEDs
on page 74
(8) N 50 ohm Female For IDU–ODU cable (N.B.2)
(B) label Data Matrix codification for factory use
Fig. 367.
(C) label unit identification
on page 539
Optional Interfaces (with optional plug–in)
Connector present only when the 17–32 E1 plug–in is equipped (N.B.3) :
(9)
SCSI 68 pin Female 17–32 E1 – 64 wires (N.B.1)
3DB 16142 CAAA Ed.01A–DRAFT 73 / 576

Ref.
Fig. 24.

Notes

(N.B.1) For connector pinout, refer to the Installation Handbook
ATTENTION
(N.B.2) (caution to avoid equipment damage)
The N–type connector carries +48 DC voltage for ODU power supply.
Do not connect measuring instruments directly.
Á ÁÁ
When no plug–in equipped, the slot is closed by a metal plate (inside the panel rear
side).
(N.B.3)
Metal plate is mandatory to ensure EMI–EMC performance
1–3.3.1 IDU Extension Unit LEDs summary
Three LEDs are present on the front panel of the IDU Extension Unit [position (7) in Fig. 24. on page 73 ]:
GREEN GREEN
1) ON = Power ON (green)
This green LED is ON when the Station Battery is connected, the ON/OFF switch is
ON, and the internal DC/DC is working properly.
2) ODU W = ODU Working (green).
The ODUW led ON identifies the TX activity of the ODU connected to the
EXTENSION unit.
It is OFF in case of:
– IDU–ODU Cable Loss alarm
– Mute function activated
– ODU switching–off command activated in 1+1 HSB configuration
3) ANT = Not operative in current SWP version
Fig. 25. LEDs on the IDU Extension Unit front panel
The lamp test pushbutton [position (3) in Fig. 24. on page 73 ] allows the HW test of all LEDs.
74 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.4 Description of E1 Protection box
3 1
Line Side
4 2
6 8
Equipment Side
5 7
Fig. 26. E1 Protection box: views of Equipment Side and Line Side connectors
Tab. 12. Equipment Side and Line Side connectors of E1 Protection box
Ref.
Connector Interface To be connected to
Fig. 26.
Line side
(1) 1–8 E1
(2) 9–16 E1
SubD 37 Female see para.1–3.4.1 on page 76
(3) 17–24 E1
(4) 25–32 E1
Equipment side
same–name connector of IDU Main unit
(5) 1–16 E1
[ (13) in Fig. 22. on page 67 ]
same–name connector of IDU Extension unit
(6) 1–16 E1
SCSI 68 pin Female [ (4) in Fig. 24. on page 73 ]
N.B. same–name connector of IDU Main unit
(7) 17–32 E1
[ (5) in Fig. 22. on page 67 ]
(8) 17–32 E1
[ (9) in Fig. 24. on page 73 ]
N.B. For connector pinout, refer to the Installation Handbook
3DB 16142 CAAA Ed.01A–DRAFT 75 / 576

1–3.4.1 E1 Protection box: connector pin–out

Notes for all tables:

– for E1 tributaries the same input and output wires are used for 120 ohm (balanced) and 75 ohm
(unbalanced); the selection between the two options is possible with CT/OS
– in 75 ohm unbalanced configuration ”Out– Trib.n” is the ground of ”Trib.n”
– pins must be connected to the station DDF, directly or through distribution shelves (see Fig. 3. on
page 36 )
Tab. 13. E1 tributaries (1 to 8) connector pin–out
pin 1
Description Pin # Pin # Description
Not Used 1 20 Not Used
IN+ Trib. 1 2 21 IN– Trib. 1
GND 10
29 Not Used
Not Used 11
Out+ Trib. 1 12 30 Out– Trib. 1
76 / 576 3DB 16142 CAAA Ed.01A–DRAFT

pin 1
GND 10
29 Not Used
Not Used 11
3DB 16142 CAAA Ed.01A–DRAFT 77 / 576


pin 1

GND 10
29 Not Used
Not Used 11
78 / 576 3DB 16142 CAAA Ed.01A–DRAFT

pin 1
GND 10
29 Not Used
Not Used 11
3DB 16142 CAAA Ed.01A–DRAFT 79 / 576

1–3.5 Description of Services Protection box

1 2 3 4

Line Side

5 6 7
Equipment Side
Fig. 27. Services Protection box: views of Equipment Side and Line Side connectors
Tab. 17. Equipment Side and Line Side connectors of Services Protection box
Ref.
Connector Interface To be connected to
Fig. 26.
Line side
Alarms + station DDF for Alarms + Housekeeping;
(1)
Housekeeping see para.1–3.5.1 on page 81
NMS V.11 + station DDF for NMS V.11 + Audio 1;
(2)
Audio 1 see para.1–3.5.2 on page 84
SubD 15 Female
NMS G.703 + station DDF for NMS G.703 + Audio 2;
(3)
Audio 2 see para.1–3.5.3 on page 85
User Service station DDF for User Service Channels;
(3)
Channels see para.1–3.5.4 on page 86
Equipment side
Audio1/2 +
(5) G703_V11 User
[ (6) in Fig. 24. on page 73 ]
Service Channel
Audio1/2 +
SubD 44 Female same–name connector of IDU Main unit
(6) G703_V11 User
N.B. [ (6) in Fig. 22. on page 67 ]
Service Channel
Alarms –
same–name connector of IDU Main unit
(7) Housekeeping –
[ (15) in Fig. 22. on page 67 ]
NMS
N.B. For connector pinout, refer to the Installation Handbook
80 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.5.1 Alarms Housekeeping (pin–out and description)
The “Alarms–Housekeeping” SubD15 connector (pinout in following Tab. 18. ) is divided in:
– 3 summarizing discrete alarms – equipment outputs (A_1 to A_3); see point [1] below
– 4 housekeeping controls – equipment outputs (HK_O1 to HK_O4); see point [2] on page 82
– 6 housekeeping alarms – equipment inputs (HK_I1 to HK_I6; see point [4] on page 83
– 1 common wire (COM)
– 1 ground (GND).
N.B. the SW User Label depicted in Tab. 18. below represents the name by which each signal is
identified by the External Points Management (see chapter 2–7 on page 253), and Quick
Configuration Procedure External Input and Output Points configuration on page 396.
Tab. 18. Alarms Housekeeping connector pin–out
pin 1
Pin Signal Direction SW User Label

6 HK_I1 INPUT CPI1
13 HK_I2 INPUT CPI2
7 HK_I3 INPUT CPI3
14 HK_I4 INPUT CPI4
8 HK_I5 INPUT CPI5
15 HK_I6 INPUT CPI6
4 HK_O1 OUTPUT CPO1
11 HK_O2 OUTPUT CPO2
5 HK_O3 OUTPUT CPO3
12 HK_O4 OUTPUT CPO4
9 COM
1 A_1 OUTPUT FAIL IDU
2 A_2 OUTPUT FAIL ODU CH#1
3 A_3 OUTPUT FAIL ODU CH#0
10 GND /
[1] SUMMARIZING DISCRETE ALARMS
The 3 summarizing discrete alarms (equipment outputs) are defined as follows:
A_1 IDU HW Failure alarm ( = IDU Main (or Extension unit) Card fail/missing + Loss of
IDU–ODU cable + Loss of Tributaries)
A_2 ODU Main Failure alarm ( = ODU Tx Failure + ODU Rx Failure)
A_3 ODU Spare Failure alarm
For electrical characteristics refer to point [3] on page 82.
3DB 16142 CAAA Ed.01A–DRAFT 81 / 576

[2] HOUSEKEEPING CONTROLS

For the 4 housekeeping controls (equipment outputs), it is possible to choose through CT not only

the manual setting of each one of them, but also the association to one of the system alarms available

in the CT menu lists (including: Major Alarm, Minor Alarm, Loss of Tributaries, Loss of IDU–ODU
cable, Remote Defect Indication, Local Defect Indication, ODU alarm, Service Affecting Alarm,
Signal Failure Alarm).
For electrical characteristics refer to point [3] herebelow.
[3] SUMMARIZING DISCRETE ALARMS & HOUSEKEEPING CONTROLS ELECTRICAL

CHARACTERISTICS
The presence of an active output alarm corresponds to a closed relay contact with a common wire.
The relay is compliant with the following electrical specification:
• alarm present ⇒ the relay is ”closed”: |V2| ≤ 2V, |I2| ≤ 50mA (the limit on the current defines
the maximum current supported by the IDU circuit)
• alarm not present ⇒ the relay is ”open”: |I2| ≤ 0.2mA, |V2| ≤ 60V
The limit on the voltage means that the customer is not allowed to force in this condition too large
V2.
IDU
OUTn
ooo ooo
OUT2
I1
OUT1
V1
OUTCommon
Fig. 28. Equipment outputs (summarizing and housekeeping)
Note 1: logic can be independently changed for each input and output (the relay is ”closed” when
the alarm is not present and is ”opened” when the alarm is present) through CT configuration while
for Summarizing outputs the default configuration is the only possibility.
Note 2: when the power supply is down (and also when the power supply is on, but the SW hasn’t
yet initialized the HW), all the relays of the outputs of the alarms/housekeeping are in the ”open” state
(HW default condition).
82 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[4] EQUIPMENT INPUTS
The IDU is able to detect the status of ”commands” coming from customer’s circuits.
A common (in) signal is supplied by the customer’s circuit, and this signal is different from the one
defined for equipment outputs.

The customer can use two different schemes to provide the command:
[case 1] relay
[case 2] open collector
Case 1 (relay)
IDU in n
customer
ooo ooo
I3
in 1 out
V4
V3
common (in)
customer
ground
Fig. 29. Equipment inputs – relay scheme
• alarm present ⇒ the customer relay is ”closed”: –2V ≤ V3 ≤ 0V, |I3| ≤ 10mA
This means that the customer’s circuit guarantees that |V3| ≤ 2V and is allowed to drain from
the IDU a 10mA max current;
• alarm not present ⇒ the customer relay is ”open”: |I3| ≤ 0.2mA. This means that the maximum
current drained by the customer’s circuit is 0.2mA.
Case 2 (open collector)
IDU in n
customer
ooo ooo
I3 in 1 V4
V3
common (in)
customer
ground
Fig. 30. Equipment inputs – open collector scheme
The IDU supplies a suitable negative voltage to the customer’s circuit:

• alarm present ⇒ the customer transistor conduces (= ”closed”): –2V ≤ V4 ≤ 0V, |I3| ≤ 10mA.
• alarm not present ⇒ the customer transistor doesn’t conduce (=”open”): |I3| ≤ 0.2mA.
This limits the max current that the customer’s circuit can drain.
3DB 16142 CAAA Ed.01A–DRAFT 83 / 576

1–3.5.2 NMS V.11 – Audio 1 (pin–out and description)

The “(NMS_V11+Audio1)” interface has 9 pins dedicated to NMS and 6 pins dedicated to EOW analog

party line.

The NMS_V11 channel is a 64Kb/s; its working mode can be selected between:
– DTE: the data in and data out have to be synchronous, data out being the slave,
– CODIR (asynchronous): TX and RX are totally asynchronous (this mode includes DCE behavior).
Expected/transmitted Clock falling edge is in the middle of the data.
Audio1 outputs can be squelched by CT/OS selection.
Tab. 19. NMS–V.11 + Audio 1 connector pin–out
pin 1
RS422 data in (+) 1 9 RS422 data in (–)
RS422 clock in (+) 2 10 RS422 clock in (–)
RS422 data out (+) 3 11 RS422 data out (–)
RS422 clock out (+) 4 12 RS422 clock out (–)
GND NMS 5 13 Audio1 signal from user (–)
Audio1 signal from user (+) 6 14 Audio1 signal to user (–)
Audio1 signal to user (+) 7 15 Not used
GND Audio 8
84 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.5.3 NMS G.703 – Audio 2 (pin–out and description)
The “(NMS_G703+Audio2)” interface has 5 pins dedicated to NMS and 6 pins dedicated to EOW analog
party line.
The NMS_G703 channel is a 64Kb/s; its working mode can be selected between:
– DTE: G703 data in and G703 data out have to be synchronous, G703 data out being the slave,
– CODIR (asynchronous): G703 data in and G703 data out are totally asynchronous (this mode
includes DCE behavior),
– “In–frame”: this configuration both disables the NMS_G703 interface and enables the
insertion/extraction into/from the first E1 of the 64Kbit/s channel coming–from/towards the uP. The
insertion/extraction is relative to the first slot of the first tributary even if there is the possibility in the
IDU ASIC to configure the desired slot. This setting is not applicable with unframed E1.
Audio2 outputs can be squelched by CT/OS selection.
Tab. 20. NMS–G.703 + Audio 2 connector pin–out
pin 1
G703 data in (+) 1 9 G703 data in (–)
Not used 2 10 Not used
G703 data out (+) 3 11 G703 data out (–)
Not used 4 12 Not used
GND NMS 5 13 Audio2 signal from user (–)
Audio2 signal from user (+) 6 14 Audio2 signal to user (–)
Audio2 signal to user (+) 7 15 Not used
GND Audio 8
3DB 16142 CAAA Ed.01A–DRAFT 85 / 576

1–3.5.4 User service channels (pin–out and description)

User service channel can be used in one of the following modes (selectable by CT/OS):

– 64Kb/s V11 co–directional – (data+clock);
– 64Kb/s co–directional – G.703 asynchronous (i.e. TX and RX data are not necessarily synchronous.
This mode includes DCE behavior);
– 64Kb/s V11 contra–directional (data+clock);
– 9.6Kb/s asynchronous V24/V28;
– 4.8Kb/s asynchronous V24/V28;
– 9.6Kb/s V11;
– 4.8Kb/s V11.
The pin function is shown in the table below.
Tab. 21. User service channel connector pin–out
pin 1
Pin # Signal Direction
2 COD_RX + INPUT
9 COD_RX – INPUT
3 COD_TX + OUTPUT
10 COD_TX – OUTPUT
4 RX_ASY INPUT
11 TX_ASY OUTPUT
5 CC_RX + INPUT
12 CC_RX – INPUT
6 RX_CK + BID
13 RX_CK – BID
7 CC_TX + OUTPUT
14 CC_TX – OUTPUT
8 CC_TCK + OUTPUT
15 CC_TCK – OUTPUT
1 GND /
86 / 576 3DB 16142 CAAA Ed.01A–DRAFT

For V11 co–directional mode, refer to Fig. 31. for the interface description vs pin–out.
USER SERVICE CHANNEL V11 CO–DIR

< USER RADIO >
USER EQUIPMENT IDU AWY
CC_RX +
DATA CC_RX –
RX_CK +
CLOCK RX_CK –
CC_TX +
CC_TX – DATA
CC_TCK +
CC_TCK – CLOCK
Fig. 31. User service channel: V11 co–directional interface
For V11 contra–directional DCE mode, refer to Fig. 32. for the interface description vs pin–out. Note that
V11 contra–directional DTE mode (as the user–equipment interface) is not supported.
USER SERVICE CHANNEL V11 CONTRA–DIR – DCE
< USER RADIO >
USER SUBORDINATE IDU AWY

EQUIPMENT (DTE)
DCE
CC_RX +
DATA CC_RX–
RX_CK +
CLOCK RX_CK–
CC_TX +
CC_TX– DATA
CC_TCK +
CC_TCK– CLOCK
Fig. 32. User service channel: V11 contra–directional interface
3DB 16142 CAAA Ed.01A–DRAFT 87 / 576

For G.703 mode, refer to Fig. 33. for the interface description vs pin–out.

USER SERVICE CHANNEL G.703

< USER RADIO >
COD_RX+
COD_RX–
DATA&CLOCK
COD_TX+
DATA&CLOCK
COD_TX–
Fig. 33. User service channel: G.703 interface
For V24/V28 mode, refer to Fig. 34. for the interface description vs pin–out.
USER SERVICE CHANNEL V28
< USER RADIO >
RX_ASY
DATA&CLOCK
TX_ASY DATA&CLOCK
Fig. 34. User service channel: V24/V28 interface
88 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.6 Provisioning and identification of Flash Cards & Software Keys
1–3.6.1 Provisioning of Flash Cards & Software Keys

A Software Key (stored on the Flash Card plugged in the IDU Main board) allows flexibility in choosing user
interfaces and modulation as in the following Tab. 22. :
Tab. 22. Flash Cards & Software Keys provisioning

Supported configuration
Technical Code, Description & Software Label Int.N#
Modulation
& type
3DB16079AA** : 4E1/8Mbps DATA 4QAM
3DB16114AA** : 4E1/8Mbps Data 4QAM SW KEY 2E1, 4E1 4QAM
Software Label: 4E1DS1 4QAM
3DB16080AA** : 4E1/8Mbps DATA 4/16QAM 2E1 4QAM

3DB16115AA**: 4E1/8Mbps Data 4/16QAM SW KEY
Software Label: 4E1DS1 4/16QAM 4E1 4QAM or 16QAM

3DB16116AA** : 8E1/16Mbps Data 4QAM SW KEY 2E1, 4E1, 8E1 4QAM
Software Label: 8E1DS1 4QAM

3DB16117AA** : 8E1/16Mbps Data 4/16QAM SW KEY
Software Label: 8E1DS1 4/16QAM 4E1, 8E1 4QAM or 16QAM

2E1, 4E1, 8E1,
3DB16118AA** : 16E1/32Mbps Data 4QAM SW KEY 4QAM
16E1
Software Label: 16E1DS1E3DS3 4QAM

3DB16119AA** : 16E1/32Mbps Data 4/16QAM SW KEY
Software Label: 16E1DS1E3DS3 4/16QAM 4E1, 8E1, 16E1 4QAM or 16QAM
2E1 4QAM
3DB16085AA** : 32E1/64Mbps DATA 4/16QAM
3DB16120AA** : 32E1/64Mbps Data 4/16QAM SW KEY 4E1, 8E1, 16E1 4QAM or 16QAM
Software Label: 32E1DS1 4/16QAM 32E1 16QAM
The limitations introduced by the Software key are related only to frame structure and modulation
configuration.
There are no limits related to the NE Configuration type (1+0 or 1+1) . Software key value and NE
Configuration type are independent.
3DB 16142 CAAA Ed.01A–DRAFT 89 / 576

1–3.6.2 Description of Flash Cards & Software Keys

1–3.6.2.1 General

The Flash Card is housed inside the IDU Main Unit shelf [see position (17) in Fig. 22. on page 67 ].
Fig. 35. herebelow shows the FLASH CARD profile and insertion direction
CONNECTOR SIDE
INSERTION BOTTOM SIDE
Fig. 35. FLASH CARD profile and insertion direction
ATTENTION
(caution to avoid equipment damage)

Whenever you have to handle flash card(s), wear always the Antistatic protection device kit (see
Fig. 1. on page 32) and connect its termination to a grounded structure, to avoid the possible damage
of the flash card contents for electrostatic discharges.
As shown in position (18) in Fig. 22. on page 67, a suitable metal cover, fixed to the IDU Main Unit shelf
by three screws, is envisaged to ensure equipment EMI–EMC performance and to avoid item detachment:
1–3.6.2.2 Flash Card identification
The Technical Codes for the possible Flash Card types are specified in Tab. 22. on page 89 , which
indicates, for each P/N, also its Software Label :
a) the Flash Card Technical Code is reported on the label affixed on it;
b) the Software Label is affixed on the label present on the front panel of the IDU Main Unit (position
(A) in Fig. 22. on page 67):
flash card Software Label
c) moreover, the Software Label can be verified by Operator’s Commands: see Fig. 165. on page 262
and Fig. 80. on page 172
1–3.6.2.3 Flash Card upgrade
To replace a Flash Card with a different type, for system upgrade purpose, please refer to para.4–7.3
Flash Card upgrade on page 518.
90 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–3.7 Provisioning and description of equipment accessories
Tab. 23. Equipment accessories

Ref.[x] is used in other parts of this handbook to refer to the item

Ref. Technical Code Technical Description N.B.
[1] 3CC07946AA** Telephone Handset a
[2] 3DB01398AA** Maintenance Tool Kit
[3] 3DB01397AA** Installation Kit Tool b
[4] 3DB01399AA** Station Kit Tool
a See chapter 4–2 on page 453
b See para.4–3.2.2 on page 456
3DB 16142 CAAA Ed.01A–DRAFT 91 / 576

92 / 576
1–4 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION
This chapter describes the ODU configurations, relevant provisioning and operative information for
installation, commissioning and maintenance purposes:

– ODU general description: refer to point d ) on page 42
– ODU mechanical design and identification on page 94
– ODU configurations on page 95
– ODU provisioning and layouts on page 96
– ODU part lists and characteristics on page 99
• 7–8 GHz ODU part lists on page 100
• 13–38 GHz ODU part lists on page 103
– Antenna configurations on page 109
– Integrated antennas on page 116
– ODU operative information on page 118
– 7–8 GHz ODU additional information on page 121
For the Light service kit cable, please refer to para.3–2.10 on page 446.
3DB 16142 CAAA Ed.01A–DRAFT 93 / 576

1–4.1 ODU mechanical design and identification

The ODU consists of one or two cabinets including the modem + transceiver + branching of a channel.

Two mechanical solutions are adopted:

– one for all frequency bands from 13 to 38 GHz, where the branching (diplexer) is internal to the ODU
cabinet; each of this type of ODU is identified by one Technical Code only
– another for all frequency bands from 7 to 8 GHz, where ODU is composed by two independent units:
the BRANCHING assembly (containing the diplexer) and the TRANSCEIVER assembly (containing
the RF section); each of this type of ODU is identified by two Technical Codes, one for the
BRANCHING assembly and another for the TRANSCEIVER assembly. To read the BRANCHING
assembly identification label it is necessary to separate the BRANCHING assembly from the
TRANSCEIVER assembly.
Tab. 24. ODU dimensions and weights

13…38 GHz 7–8 GHz
Frequency TRANSCEIVER TRANSCEIVER
TRANSCEIVER BRANCHING
+ BRANCHING + BRANCHING
235 x 235 x 72 mm 248 x 257 x 93 mm 235 x 235 x 73.5 mm 248 x 257 x 156.5 mm
Dimensions
(9.25 x 9.25 x 2.8in) (9.76 x 10.1 x 3.7in) (9.25 x 9.25 x 2.9in) (9.76 x 10.1 x 6.6in)
Weight 3.9 kg (8.58 lb) 4.2 kg (9.24 lb) 3.2 kg (7.04 lb) 7.4 kg (16.28 lb)
13 ... 38 GHz 7–8 GHz
BRANCHING
BRANCHING
IDENTIFICATION LABEL
(INSIDE)
(see Fig. 50. on page 123)
TRANSCEIVER TRANSCEIVER
+
BRANCHING
TRANSCEIVER
ODU IDENTIFICATION LABEL IDENTIFICATION LABEL
(see Fig. 368. on page 540) (see Fig. 368. on page 540)
Fig. 36. ODU types, identification, dimensions and weights
The ODUs are delivered with the “nose” adapter in case of configurations with the separated antenna (for
details, see para.1–4.5.4 on page 114)
94 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.2 ODU configurations
The available outdoor configurations are listed in Tab. 25. herebelow:

Tab. 25. ODU configurations
Outdoor APPLICATIONS AND

ODU ODU coupler ANTENNA
configuration ADVANTAGES
1+0 1 x ODU NO 1 x antenna single polar Non–protected
2 x ODUs at
1/10 dB Protection against
1+1 HSB same 1 x antenna single polar
asymmetric failures
frequency
2 x ODUs at
1+1 HSB SD same NO 2 x antennas single polar
frequency Protection against
failures.
2 x ODUs at
Improvement of
1+1 FD AP different NO 1 x antenna double polar
performances
frequencies
versus multipath
2 x ODUs at 2 x antennas single polar propagation
1+1 FD DA different NO in AP configuration (same
frequencies or crossed polarization)
N.B. For explanatory diagrams, refer to para.1–2.3 on page 46 System configurations.
Legend:
AP: Alternate Polar
DA: Double Antenna
FD: Frequency diversity
HSB: Hot Stand By
SD: Space Diversity
3DB 16142 CAAA Ed.01A–DRAFT 95 / 576

1–4.3 ODU provisioning and layouts

1–4.3.1 Provisioning of ODU (1+0)

a) ODU transceiver: see para.1–4.4 on page 99
b) Antenna: see paragraphs:
– 1–4.5.1 on page 110 (1+0 configuration with integrated antenna)
– 1–4.6 on page 116 (Integrated antennas)
or
– 1–4.5.4 on page 114 (Configuration with separated antenna)
c) Part list of ODU accessories and installation materials: refer to the Installation Handbook
1–4.3.2 Provisioning, layouts and connections of ODU (1+1)
1–4.3.2.1 ODU (1+1) HSB–SD or FD–DA AP with two antennas
Antenna (2) Antenna (1)
ODU CH 0 ODU CH 1
N.B. Figure shows the solution with integrated antennas; antennas can be also external (see point
b ) herebelow)
Fig. 37. Station layout of ODU (1+1) HSB–SD or FD–DA AP with two antennas
– Equipment provisioning:
a) ODU transceiver (x2): see para.1–4.4 on page 99
b) Antenna (x2): see paragraphs:
– 1–4.5.1 on page 110 (1+0 configuration with integrated antenna)

or
– 1–4.5.4 on page 114 (Configuration with separated antenna)
c) Part list of ODU accessories and installation materials (x2): refer to the Installation Handbook
– ODU Equipment block diagram: see:
• Fig. 12. on page 48 (1+1 HSB–SD)
• Fig. 14. on page 49 (1+1 FD–DA AP)
96 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.3.2.2 ODU (1+1) HSB or with one antenna
COUPLER
ANTENNA
ODU CH 0
ODU CH 1
N.B. this drawing is an example referred to the coupler used in 13–38 GHz configurations.
Couplers used in 7–8 GHz configurations are shown in Fig. 43. on page 113.
Fig. 38. Station layout of ODU (1+1) HSB with one antenna
a) ODU transceiver (x2): see para.1–4.4.2 on page 103
b) Antenna and coupler: see paragraphs:
– 1–4.5.2 on page 112

[1+1 HSB configuration with coupler and integrated antenna (13–38 GHz)]
– 1–4.5.3 on page 113

[1+1 HSB configuration with coupler and integrated antenna (7–8 GHz)]
– ODU Equipment block diagram: see:
• Fig. 13. on page 48 (1+1 HSB)
3DB 16142 CAAA Ed.01A–DRAFT 97 / 576

1–4.3.2.3 ODU (1+1) FD–AP with one double polar external antenna

Double Polar Antenna

ODU CH 0 ODU CH 1
Fig. 39. Station layout of ODU (1+1) FD–AP with one double polar external antenna
a) ODU transceiver (x2): see para.1–4.4 on page 99
b) Connection of Double Polar External Antenna: see para.1–4.5.4 on page 114 (Configuration
with separated antenna)
– ODU Equipment block diagram: see Fig. 15. on page 49
98 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.4 ODU part lists and characteristics
Notes for all tables:

ODU Type In 9400AWY R.2.1, only 32E1 ODU types can be used.
N.B. The 16E1/DS1 ODU types (used in 9400AWY R.1.0 and
R.2.0) cannot be used in 9400AWY Rel.2.1.
Technical Code Technical part number of the item.

N.B. The last two Technical Code letters stand for a ”feasible
alternative”, they might differentiate two items even though
still functionally compatible. For this reason the indicated
Technical Code does not include the last two letters
(replaced by **).
Note: The ODU Technical Codes listed in the following tables include always the solar shield.
For:
– 7–8 GHz ODU, refer to para.1–4.4.1 on page 100
– 13–38 GHz ODU, refer to para.1–4.4.2 on page 103
3DB 16142 CAAA Ed.01A–DRAFT 99 / 576

1–4.4.1 7–8 GHz ODU part lists

1–4.4.1.1 General

The 7/8 GHz diplexer included in the available BRANCHING assemblies refers to ITU–R F.385, 386 and
RF special CUSTOMERS channelling with Tx/Rx separation specified in following Tab. 27. and Tab. 29.
Each diplexer is a three port passive device with two band–pass filters as described hereafter (physical
arrangement is shown in Fig. 49. on page 122):
Port A
Port C
Port B
Each BRANCHING assembly has two different variants by duplex spacing, depending on the RF_Tx
output frequency band as described on the table below :
3DB Variant Channel

3DB xxxxx AA** 1_1p
3DB xxxxx AB** 2_2p
The arrangement between each filters on the same branching device is described below:
foL foH
f1 f2 f3 f4
frequencies
2.5 dB
70 dB
attenuation fr SHIFTER
WARNING: f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channel
frequencies and not to the cut–off frequencies of the filters.
100 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.4.1.2 7 GHz ODU part list
Tab. 26. 7 GHz Transceiver assemblies

ODU Type Technical Code Technical Description

3DB 06691 AB** ODU 32E1 9470 7.1 – 7.75 GHz LHB
32E1
3DB 06692 AB** ODU 32E1 9470 7.25 – 7.9 GHz UHB
Tab. 27. Branching assemblies for 7 GHz ODU

N.B. shifter value choice to be done by Craft Terminal
Filter 1 MHz Filter 2 MHz
(Lower Band) (Upper Band)
BRANCHING ASSEMBLY
Central
Shifter
Freq. Low High Low High
MHz Technical Description
MHz Limit Limit Limit Limit Technical Code
f1 f2 f3 f4 BRANCHING 7GHZ ...
154 7212,0 7107,0 7163,0 7261,0 7317,0 3DB 10060 AA** ... CH1–1P P.SH. 154_C MHz
154 7547,0 7428,0 7512,0 7582,0 7666,0 3DB 06774 AA** ... CH1–1P P.SH. 154_A MHz
154 7603,0 7484,0 7568,0 7638,0 7722,0 3DB 06774 AB** ... CH2–2P P.SH. 154_A MHz
154 7561,0 7442,0 7526,0 7596,0 7680,0 ... CH1–1P P.SH.154_B MHz
3DB 06775 AA**
160 7561,0 7442,0 7520,0 7602,0 7680,0 ... CH1–1P P.SH.160 MHz
154 7617,0 7498,0 7582,0 7652,0 7736,0 ... CH2–2P P.SH.154_B MHz
3DB 06775 AB**
160 7617,0 7498,0 7576,0 7658,0 7736,0 ... CH2–2P P.SH.160 MHz
161 7240,0 7124,5 7194,5 7285,5 7355,5 3DB 06780 AA** ... CH1–1P P.SH.161_A MHz
161 7310,0 7194,5 7264,5 7355,5 7425,5 3DB 06780 AB** ... CH2–2P P.SH.161_A MHz
161 7365,0 7249,5 7319,5 7410,5 7480,5 3DB 06781 AA** ... CH1–1P P.SH.161_B MHz
161 7435,0 7319,5 7389,5 7480,5 7550,5 3DB 06781 AB** ... CH2–2P P.SH.161_B MHz
161 7390,0 7274,5 7344,5 7435,5 7505,5 3DB 06782 AA** ... CH1–1P P.SH.161_C MHz
161 7460,0 7344,5 7414,5 7505,5 7575,5 3DB 06782 AB** ... CH2–2P P.SH.161_C MHz
161 7540,0 7424,5 7494,5 7585,5 7655,5 3DB 06783 AA** ... CH1–1P P.SH.161_D MHz
161 7610,0 7494,5 7564,5 7655,5 7725,5 3DB 06783 AB** ... CH2–2P P.SH.161_D MHz
161 7665,0 7549,5 7619,5 7710,5 7780,5 3DB 06784 AA** ... CH1–1P P.SH.161_E MHz
161 7735,0 7619,5 7689,5 7780,5 7850,5 3DB 06784 AB** ... CH2–2P P.SH.161_E MHz
161 7690,0 7574,5 7644,5 7735,5 7805,5 3DB 06785 AA** ... CH1–1P P.SH.161_F MHz
161 7760,0 7644,5 7714,5 7805,5 7875,5 3DB 06785 AB** ... CH2–2P P.SH.161_F MHz
168 7299,0 7187,0 7243,0 7355,0 7411,0 3DB 10059 AA** ... CH1–1P P.SH.168_B MHZ
168 7569,0 7443,0 7527,0 7611,0 7695,0 3DB 06776 AA** ... CH1–1P P.SH.168 MHZ
168 7625,0 7499,0 7583,0 7667,0 7751,0 3DB 06776 AB** ... CH2–2P P.SH.168 MHZ
182 7547,0 7414,0 7498,0 7596,0 7680,0 3DB 06777 AA** ... CH1–1P P.SH.182 MHZ
182 7603,0 7470,0 7554,0 7652,0 7736,0 3DB 06777 AB** ... CH2–2P P.SH.182 MHZ
196 7247,0 7107,0 7191,0 7303,0 7387,0 3DB 06778 AA** ... CH1–1P P.SH.196 MHZ
196 7303,0 7163,0 7247,0 7359,0 7443,0 3DB 06778 AB** ... CH2–2P P.SH.196 MHZ
245 7606,5 7428,0 7540,0 7673,0 7785,0 3DB 06779 AA** ... CH1–1P P.SH.245 MHZ
245 7718,5 7540,0 7652,0 7785,0 7897,0 3DB 06779 AB** ... CH2–2P P.SH.245 MHZ
3DB 16142 CAAA Ed.01A–DRAFT 101 / 576


Tab. 28. 8 GHz Transceiver assemblies

ODU Type Technical Code Technical Description
3DB 06693 AB** ODU 32E1 9470 7.7 – 8.4 GHz LHB
32E1
3DB 06694 AB** ODU 32E1 9470 8.0 – 8.5 GHz UHB
Tab. 29. Branching assemblies for 8 GHz ODU

Filter 1 MHz Filter 2 MHz

(Lower Band) (Upper Band)
BRANCHING ASSEMBLY
Central
Shifter
Freq. Low High Low High
MHz Technical Technical Description
MHz Limit Limit Limit Limit
f1 f2 f3 f4 Code BRANCHING 8GHZ ...
119 8366.5 8286.0 8328.0 8405.0 8447.0 ... CH1–1P P.SH.119 MHz
3DB 06789 AA**
126 8366.5 8282.5 8324.5 8408.5 8450.5 ... CH1–1P P.SH.126 MHz
119 8408.5 8328.0 8370.0 8447.0 8489.0 ... CH2–2P P.SH.119 MHz
3DB 06789 AB**
126 8408.5 8324.5 8366.5 8450.5 8492.5 ... CH2–2P P.SH.126 MHz
151.610 8315.010 8204.217 8274.189 8355.831 8425.803 3DB 06787 AA** ... CH1–1P P.SH.151 MHz
151.610 8384.982 8274.189 8344.161 8425.803 8495.775 3DB 06787 AB** ... CH2–2P P.SH.151 MHz
208 8217.0 8064.0 8162.0 8272.0 8370.0 3DB 10073 AA** ... CH1–1P P.SH.208 MHZ
208 8301.0 8148.0 8246.0 8356.0 8454.0 3DB 10073 AB** ... CH2–2P P.SH.208 MHZ
266 8097.5 7905.0 8024.0 8171.0 8290.0 3DB 06788 AA** ... CH1–1P P.SH.266 MHZ
266 8209.5 8017.0 8136.0 8283.0 8402.0 3DB 06788 AB** ... CH2–2P P.SH.266 MHZ
294.440 7749.755 8145.915
305.560 7738.635 8157.035 ... CH1–1P

7947.835 7851.475 8044.195 3DB 06786 AA**
P.SH.294/305/311 MHZ
311.320 7732.875 8162.795
311.320 8066.435 7851.475 8162.795 8281.395

... CH2–2P
294.440 7862.965 7970.075 8264.515 3DB 06786 AB**
P.SH.294/305/311 MHZ
8063.740 8157.405
305.560 7851.845 8275.635
213.5 8147.0 8035.0 8046.0 8248.0 8259.0 3DB 10103 AA** ... CH1–1P P.SH. 213.5 MHZ
102 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.4.2 13–38 GHz ODU part lists
The following tables report the Technical Code of the available 13–38 GHz ODUs with the following
information from left to right:

Column 1: Shifter (MHz)

Column 1bis : Central Frequency (MHz)
Column 2 & 3: Tx and Rx sub–bands
Column 4 to 7: Tx & Rx frequency ranges at RF interface (MHz)
For some frequency ranges, two types of ODU are envisaged:
– ODU with fixed shifter
– ODU with variable shifter: the shifter value can be set by Craft Terminal
Tab. 30. 13 GHz ODU (FIXED–SHIFTER)
RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
RF Tx RF Tx RF Rx RF Rx
Shifter CF Tx Rx
min max min max
12807.5 1 1p 12750 12865 13016 13131 3CC 13688 AB**
12920.5 2 2p 12861 12980 13127 13246 3CC 13689 AB**

266 32E1
13073.5 1p 1 13016 13131 12750 12865 3CC 13690 AB**
13186.5 2p 2 13127 13246 12861 12980 3CC 13691 AB**
3DB 16142 CAAA Ed.01A–DRAFT 103 / 576



RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
Shifter CF Tx Rx
min max min max
14698 1 1p 14630 14766 14945 15081 3CC 13692 AB**
14829,5 2 2p 14760 14899 15075 15214 3CC 13693 AB**

315
15013 1p 1 14945 15081 14630 14766 3CC 13694 AB**
15144,5 2p 2 15075 15214 14760 14899 3CC 13695 AB**
14612 1 1p 14500 14724 14920 15144 3CC 13696 AB**
14825,5 2 2p 14710 14941 15130 15361 3CC 13697 AB**

420
15032 1p 1 14920 15144 14500 14724 3CC 13698 AB**
15245,5 2p 2 15130 15361 14710 14941 3CC 13699 AB**

32E1
14517,5 1 1p 14400 14635 14890 15125 3CC 13704 AB**
14742,5 2 2p 14625 14860 15115 15350 3CC 13705 AB**

490
15007,5 1p 1 14890 15125 14400 14635 3CC 13706 AB**
15232,5 2p 2 15115 15350 14625 14860 3CC 13707 AB**
14600 1 1p 14500 14700 15144 15344 3CC 13709 AB**

644
15244 1p 1 15144 15344 14500 15988 3CC 13711 AB**
14560 1 1p 14500 14620 15228 15348 3CC 13712 AB**

728
15288 1p 1 15228 15348 14500 14620 3CC 13713 AB**
104 / 576 3DB 16142 CAAA Ed.01A–DRAFT


RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
Shifter CF Tx Rx
min max min max
18640,5 1 1p 18581 18700 18921 19040 3CC 13714 AB**
18760,5 2 2p 18701 18820 19041 19160 3CC 13715 AB**

340
18980 1p 1 18920 19040 18580 18700 3CC 13716 AB**
32E1
19100 2p 2 19040 19160 18700 18820 3CC 13717 AB**
1560 17920 1 1p 17700 18140 19260 19700 3CC 12995 AB**

ETSI 19480 1p 1 19260 19700 17700 18140 3CC 12996 AB**
Tab. 33. 18 GHz ODU (VARIABLE–SHIFTER)

RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical Code
type
Shifter CF Tx Rx
min max min max
1008 17951,5 17703 18200 18711 19208

1 1p 3CC 14780 AB**
1010 17950,5 17700 18201 18710 19211
1008 18430,5 18182 18679 19190 19687

2 2p 3CC 14781 AB**
1010 18435 18180 18690 19190 19700
32E1
1008 18959,5 18711 19208 17703 18200
1p 1 3CC 14782 AB**
1010 18960,5 18710 19211 17700 18201
1008 19438,5 19190 19687 18182 18679

2p 2 3CC 14783 AB**
1010 19445 19190 19700 18180 18690
3DB 16142 CAAA Ed.01A–DRAFT 105 / 576


RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical Code
type
Shifter CF Tx Rx
min max min max
22157,5 1 1p 22000 22315 23008 23323 3CC 13718 AB**
22450 2 2p 22300 22600 23308 23608 3CC 13719 AB**

1008 32E1
23165,5 1p 1 23008 23323 22000 22315 3CC 13720 AB**
23458 2p 2 23308 23608 22300 22600 3CC 13721 AB**
Tab. 35. 23 GHz ODU (VARIABLE–SHIFTER)

RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical Code
type
Shifter CF Tx Rx
min max min max
1200 21509,5 21200 21819 22400 23019

1 1p 3CC 14776 AB**
1232 21492,5 21198 21787 22430 23019
1050 22306 22252 22360 23302 23410
1200 22090,5 2 2p 21781 22400 22981 23600 3CC 14777 AB**
1232 22074,5 21781 22368 23013 23600

32E1
1200 22709,5 22400 23019 21200 21819
1p 1 3CC 14778 AB**
1232 22724,5 22400 23019 21200 21819
1050 23356 23302 23410 22252 22360
1200 23290,5 2p 2 22981 23600 21781 22400 3CC 14779 AB**
1232 23306,5 23013 23600 21781 22368
106 / 576 3DB 16142 CAAA Ed.01A–DRAFT


RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
Shifter CF Tx Rx
min max min max
24768,5 1 1p 24540 24997 25548 26005 3CC 13734 AB**
25221 2 2p 24994 25448 26002 26456 3CC 13735 AB**

1008 32E1
25776,5 1p 1 25548 26005 24540 24997 3CC 13736 AB**
26229 2p 2 26002 26456 24994 25448 3CC 13737 AB**
RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
Shifter CF Tx Rx
min max min max
27767 1 1p 27540 27994 28548 29002 3CC 13738 AB**
28221 2 2p 27994 28448 29002 29456 3CC 13739 AB**

1008 32E1
28775 1p 1 28548 29002 27540 27994 3CC 13740 AB**
29229 2p 2 29002 29456 27994 28448 3CC 13741 AB**
3DB 16142 CAAA Ed.01A–DRAFT 107 / 576



RF interface (MHz)
1 1bis 2 3 4 5 6 7 ODU
Technical code
type
Shifter CF Tx Rx
min max min max
37335 1 1p 37050 37620 38310 38880 3CC 12987 AB**
37899,5 2 2p 37619 38180 38879 39440 3CC 12988 AB**

1260 32E1
38595 1p 1 38310 38880 37050 37620 3CC 12989 AB**
39159,5 2p 2 38879 39440 37619 38180 3CC 12990 AB**
108 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.5 Antenna configurations
The ODU can be connected to:

– an integrated antenna of 30 cm (1FT) or 60 cm (2FT) or 90 cm (3FT) or 120 cm (4FT) diameter.
– a separated antenna, if larger diameters are necessary. In this case, the antenna is interconnected
by a flextwist directly to the ODU, or the coupler, depending on the protection used.
For the outdoor section the following 1+1 configuration are presently implemented:
• HSB configuration is available with a 1 dB/10 dB asymmetrical coupler and 1 antenna: this
configuration optimizes the infrastructure using only one antenna, a 10 dB coupling has been
chosen to minimize the losses on the normal path (1 dB only).
• without coupler and 2 antennas: this configuration adds a natural Space Diversity and improves
the link budget avoiding coupler losses on the stand–by path.
• without coupler and 1 dual polarization antenna: this configuration allows a polarization
diversity, minimizes the antenna and avoids coupler losses on the stand–by path.
The pole mounting versions are given in the following Tab. 39. for each configuration:
Tab. 39. Pole Mounting versions
Version see para
1+0 with integrated antenna 1–4.5.1 page 110
1+1 HSB configuration with coupler and integrated antenna (13–38 GHz) 1–4.5.2 page 112
1+1 HSB configuration with coupler and integrated antenna (7–8 GHz) 1–4.5.3 page 113
Configuration with separated antenna 1–4.5.4 page 114
3DB 16142 CAAA Ed.01A–DRAFT 109 / 576

1–4.5.1 1+0 configuration with integrated antenna

The following Fig. 40. and Fig. 41. show the 1+0 configuration with a 30 cm (1FT) antenna in both vertical

and horizontal configurations. The modification of the polarization is obtained by rotating the ODU and the

nose of the antenna.
7–8 GHz
antenna
IDU connector
INTEGRATED
ANTENNA
POLE MOUNTING
13 ... 38 GHz
antenna
360 mm
(14.17 in)
IDU connector
390 mm
(15.35 in)
620 mm
(24.41 in)
Fig. 40. View of ODU with integrated antenna (V polarization)
110 / 576 3DB 16142 CAAA Ed.01A–DRAFT

7–8 GHz
antenna
IDU connector
INTEGRATED
ANTENNA
POLE MOUNTING
13 ... 38 GHz
antenna
IDU connector
measures as Fig. 40.
Fig. 41. View of ODU with integrated antenna (H polarization)
Please refer to the Installation Handbook, for the P/N of “integrated antenna pole mounting“, and for
detailed assembly drawings.
3DB 16142 CAAA Ed.01A–DRAFT 111 / 576

1–4.5.2 1+1 HSB configuration with coupler and integrated antenna (13–38 GHz)

– See Fig. 42. below. The 2 ODUs are interconnected through a 1 dB /10 dB coupler. The coupler is

fixed on the 1+0 pole mounting with 4 catches. The 2 ODUs are connected to the coupler with their

catches.
– The modification of the polarization is done on the coupler by rotating rings at antenna port and on
the antenna by rotating the nose (the ODUs are always in the same position).
– Different couplers are available, as shown in Tab. 40. herebelow:
Tab. 40. Available couplers (13–38 GHz)

N.B. This list is given for general information purpose.
For P/Ns and possible additional and related information, please refer to the Installation
Handbook.
Waveguide
Frequency band Coupler type Coupling loss
(3 ports)
13, 15 GHz 10 dB WR 62 1 dB / 10 dB
18, 23, 25 GHz 10 dB WR 42 1 dB / 10 dB
28, 38 GHz 10 dB WR 28 1 dB / 10 dB
Coupler antenna
360 mm
(14.17 in)
535 mm
(21.83 in)
620 mm COUPLER VIEW
(24.41 in)
COUPLER WEIGHT = 4.3 Kg about
Fig. 42. Coupler (13–38 GHz)
112 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.5.3 1+1 HSB configuration with coupler and integrated antenna (7–8 GHz)
Two alternative couplers are available, as shown in Tab. 41. and Fig. 43. herebelow:
Tab. 41. Available couplers (7–8 GHz)

Frequency band Coupler type Waveguide (3 ports) Coupling loss
7–8 GHz 10 dB WR 112 1 dB / 10 dB
For coupler P/Ns and assembly drawings of ODUs + coupler, please refer to the Installation Handbook.
weight 6 Kg about
(both versions)
Fig. 43. Coupler (7–8 GHz)
3DB 16142 CAAA Ed.01A–DRAFT 113 / 576

1–4.5.4 Configuration with separated antenna

The ODU is fixed on a dedicated pole mounting for separated antenna. A nose adapter (different Technical

Codes depending on the waveguide dimension) is used to connect the ODU and the flextwist.

7–8 GHz 13 ... 38 GHz
NOSE (under)
ADAPTER
NOT INTEGRATED
ANTENNA
POLE MOUNTING
Fig. 44. Nose adapters for ODU with separated antenna
Please refer to the Installation Handbook, for the P/Ns of “nose adapters” and “not integrated antenna
pole mounting“, and for detailed assembly drawings.
Concerning the interface between the ODU output flange and the suggested antenna flange, the following
Tab. 42. details for each product the standard wave guide to be used and the suggested flange for the
external antenna.
Please note that the use of 600 mm flex twist is not suggested for antennas bigger than 3ft (90 cm
diameter), due to mechanical reasons. The suggested way to make the RF connection is to use the
elliptical wave guide fitted with flanged connectors.
114 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Tab. 42. ODU Output flanges with external antenna

For flextwist P/Ns and possible additional and related information, please refer to the
Installation Handbook.
Equipment Suggested
ODU Output
and Range FLEXTWIST Antenna
Flange
(GHz) Flange
A C.E.I. E.I.A. B C D
UDR84 R84 WR112 PDR84 UBR84 PBR84

9470 AWY
or:
7–8
UBR84 R84 WR112 PBR84 UBR84 PBR84
9413 AWY
12.7 – 13.3
9415 AWY
14.2 – 15.4
9418 AWY
17.7 – 19.7
9423 AWY
21.2 – 23.6
9425 AWY
24.5 – 26.5
9428 AWY
27.3 – 31.3
9438 AWY
37.0 – 40.0
L=1000 mm for 7–8 GHz

L=600 mm for 13–38 GHz
N.B. If the flex–twist is not provided by Alcatel–Lucent, the user must carefully choose the type of
the connection guide in order to limit as much as possible galvanic couples between
antenna/flex–twist and flex–twist/ODU contact surfaces that can induce rust. For this purpose
please note that the surfaces are:
– chromium–plated at ODU’s output flange side
– tin–plated at flex–twist’s flange side
3DB 16142 CAAA Ed.01A–DRAFT 115 / 576

1–4.6 Integrated antennas

Tab. 43. Available integrated antennas

For P/Ns and possible additional antenna types and related information, please refer to the
Installation Handbook.
Frequency
∅ Technical Description
(GHz)
7 2FT 7GHZ 2FT SP INTEGRATED ANTENNA
8 2FT 8GHZ 2FT SP INTEGRATED ANTENNA
3FT INT. ANT. COMPACT LINE 3FT 7.1/8.5GHZ SP

7&8
1FT 13GHZ 1FT SP INTEGR. ANTENNA ANDREW
13GHZ 2FT SP INTEGR. ANTENNA RFS

2FT
13 13GHZ 2FT SP INTEGR. ANTENNA ANDREW

1FT
15GHZ 1FT SP INTEGR. ANTENNA ANDREW

15 2FT

1FT

18 2FT
3FT INT. ANT. COMPACT LINE 3FT 17.7/19,7GHZ SP
116 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Frequency
(GHz)
∅ Technical Description

1FT

23 2FT

1FT

25 2FT
1FT 28GHZ 1FT SP INTEGRATED ANTENNA

28
2FT 28GHZ 2FT SP INTEGRATED ANTENNA

1FT
38
2FT
3DB 16142 CAAA Ed.01A–DRAFT 117 / 576

1–4.7 ODU operative information

1–4.7.1 General, views and access points

Fig. 46. (for 13–38 GHz) and Fig. 47. (for 7–8 GHz) on pages 119–120 show ODU views and access
points.
The external interfaces are listed in Tab. 44. below, with the corresponding connector.
Tab. 44. ODU external interfaces

Ref. in
Further
Fig. 46. Interface Connector
information
and Fig. 47.
Tab. 45.
(1) RF interface for connection of antenna or coupler waveguide
herebelow
(2) Connector for IDU/ODU cable male N 50 ohm
12–pin LEMO
para.3–2.10
(3) Connector for Light service kit cable (Fig. 45.
on page 446
on page 118)
Tab. 45. RF interface

FREQUENCY GHz ⇒ 7–8 13–15 18–25 28–38
Waveguide type ⇒ WR112 WR62 WR42 WR28
N.B. for further information, refer to para.1–4.5 on page 109
N.B. For detailed operative information regarding:
– equipment installation, please refer to the Installation Handbook
– equipment commissioning, please refer to chapter 3–2 on page 361
– equipment maintenance, please refer to section 4 on page 447.
7 6
8 12 11 5
1 9 10 4
2 3
KEY
Fig. 45. ODU LEMO connector pinout
118 / 576 3DB 16142 CAAA Ed.01A–DRAFT

(4)
TRANSCEIVER
+
BRANCHING
SOLAR SHIELD
(1)
(A)
(A)
(A)
(3) (A)
(2)
(A) Levers (4) to fix/unfix ODU assembly to antenna or coupler
(1) RF interface for connection of antenna or coupler
(2) Connector for IDU/ODU cable
(3) Connector for Light service kit cable
(4) ODU identification label (see Fig. 368. on page 540)
Fig. 46. ODU views (13–38 GHz)
3DB 16142 CAAA Ed.01A–DRAFT 119 / 576

BRANCHING
(4)
TRANSCEIVER
SOLAR SHIELD
(B) (A)
(1)
(B)
(A)
(A)
(B)
(2)
(3)
(A) (B)
(A) 4 levers to fix/unfix branching assembly (diplexer) to transceiver
(B) 4 levers to fix/unfix branching assembly (diplexer) to antenna or coupler
(1) RF interface for connection of antenna or coupler
(2) Connector for IDU/ODU cable
(3) Connector for Light service kit cable
(4) TRANSCEIVER identification label (see Fig. 368. on page 540)
Fig. 47. ODU views (7–8 GHz)
1–4.7.2 ODU hardware settings
No hardware settings are envisaged on 13–38 GHz ODUs, while on 7–8 GHz ODUs a setting allows to
choose the half–band (LOW or HIGH) for TX (see para.1–4.8 on page 121 for details).
1–4.7.3 ODU identification
Through the Solar Shield window are visible the ODU or TRANSCEIVER identification label and the
Vertical or Horizontal polarization mounting. In case of 7–8 GHz ODU, the BRANCHING identification label
(Fig. 50. on page 123) can be viewed only separating the TRANSCEIVER from the BRANCHING.
120 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.8 7–8 GHz ODU additional operative information
1–4.8.1 7–8 GHz ODU composition

The 9400AWY in 7 and 8 GHz bands (9470AWY) is provided with a new ODU mechanical arrangement
in order to minimize the parts number required.
As shown in Fig. 48. below, the 9470AWY ODU assembly is composed, unlike the existing ones in the
other frequency bands, by two boxes, one for diplexer system (BRANCHING) and the other for the all other
active functions (TRANSCEIVER) connected together to form the ODU.
An O–RING present in the TRANSCEIVER box guarantees the ODU assembly pressurization.
N.B. This is a conductive O–RING and must be left dry. Do not wet it with silicon grease (silicon
grease must be used only on O–ring between ODU and antenna).
BRANCHING
TRANSCEIVER
O–RING
Fig. 48. 7–8 GHz ODU composition
The TRANSCEIVER box is very similar to the existing ones 9400AWY ODU used in the other frequency
bands, but without the diplexer system.
The BRANCHING box provides the interface between the pole mounting/antenna and the
TRANSCEIVER.
The favorite solution foresees the possibility to change in field a spare part TRANSCEIVER without
disconnecting the BRANCHING box from the pole mounting/antenna. The TRANSCEIVER and
BRANCHING boxes fixing and unfixing are obtained through the four levers (A) shown in Fig. 47. on page
120.
3DB 16142 CAAA Ed.01A–DRAFT 121 / 576

1–4.8.2 7–8 GHz ODU’s TRANSCEIVER and BRANCHING boxes coupling

Fig. 49. below shows the TRANSCEIVER and BRANCHING boxes coupling surfaces:

– (A) BRANCHING box label informative content
described in Fig. 50. on page 123
– (B) (HIGH FREQ) and (C) (LOW FREQ) RF interfaces on BRANCHING box
– (D) (TX) and (E) (RX) RF interfaces on TRANSCEIVER box

The TRANSCEIVER and BRANCHING boxes can be coupled in two alternative ways (1800–rotated with
respect to each other):
– BRANCHING box’s (B) (HIGH FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the HIGH frequency range of the Shifter set by Craft
Terminal (see field D in Fig. 50. on page 123); obviously the RX part of the transceiver uses the
corresponding LOW frequency range;
– BRANCHING box’s (C) (LOW FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the LOW frequency range of the Shifter set by Craft
Terminal (see field D in Fig. 50. on page 123); obviously the RX part of the transceiver uses the
corresponding HIGH frequency range.
TRANSCEIVER BRANCHING
(D)
(A) (B)
(C)
(E)
Fig. 49. 7–8 GHz ODU’s TRANSCEIVER and BRANCHING boxes coupling surfaces
122 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–4.8.3 Label affixed inside the 7–8 GHz ODU BRANCHING box
3DB 06775 AAAA 01 A

3DB 06775 AAXX B
C
154_B LOW 7442 7526

HIGH 7596 7680
160 LOW 7442.5 7512.5 D
HIGH 7602.5 7673.5
SYMBOL OR WRITING MEANING
A9400 Equipment Acronym & Alcatel Logo

ALCATEL
CE European Community logo

12345 (example) Notified body
! Not harmonized frequency logo
2002/96/EC WEEE (Waste Electrical and Electronic
Equipment) Logo (see para.1–5.10.3 on page 136)
PN/ICS 3DB 06775 AAAA 01 (example) Factory Technical Code + ICS
A Factory Technical Code + ICS, bar code 128
Logistical Item 3DB 06775 AAXX (example) Technical Code for Customer
B Technical Code for Customer, bar code 128
S/N CW 050609001 (example) Factory Serial number
C Factory Serial number bar code 128
– the field “Shifter MHz” indicates the possible
frequency bands that can be used with this
branching assembly.
The choice between different shifters is done by
Craft Terminal (refer to point [2] on page 413 for
D (shown numbers as examples) details).
– for each “Shifter MHz”, the TX “LOW” and

“HIGH” rows indicate the frequency range
assumed by transceiver TX section, according to
the TRANSCEIVER and BRANCHING boxes
coupling described in para.1–4.8.2 on page 122
Fig. 50. Label affixed inside the 7–8 GHz ODU BRANCHING box
3DB 16142 CAAA Ed.01A–DRAFT 123 / 576

124 / 576
1–5 TECHNICAL SPECIFICATIONS
Data indicated in this manual must be considered as typical values

The guaranteed values are only those indicated in the contract.

This chapter describes the technical characteristics of the 9400AWY Rel.2.1 in the following RF band
configurations:
Tab. 46. 9400 AWY family

SYSTEM BAND (GHz)
9470AWY 7–8
9413AWY 13
9415AWY 15
9418AWY 18
9423AWY 23
9425AWY 25
9428AWY 28
9438AWY 38
This chapter is organized as follows:

– General Characteristics on page 126, including:
• Reference system standards on page 127
• RF channeling on page 128
• Transmitted Power at antenna port (ETSI & ANSI) on page 128
• 99% power channel bandwidth and Emission Designator on page 129
• ETSI System Characteristics on page 130
• Switching system on page 133
– Tributary interfaces on page 134
– Modem on page 134
– Maximum capacity and Modulation type on page 134
– IDU–ODU cable on page 134
– Man–machine interface on page 135
– Alarms on page 135
– Power supply on page 135
– Mechanical characteristics on page 135
– Environmental conditions on page 136
– Electro–magnetic compatibility / safety on page 136
– Dismantling & Recycling on page 137
3DB 16142 CAAA Ed.01A–DRAFT 125 / 576

1–5.1 General Characteristics

Version SPLIT MOUNT (IDU+ODU)

Station type Terminal
Configuration 1+0 / 1+1 HSB / 1+1 FD
Reference standard
Refer to para. 1–5.1.1 page 127
(system)
Transmission capacity ETSI: 2xE1, 4xE1, 8xE1, 16xE1, 32xE1
RF channel spacing Refer to para. 1–5.1.2 page 128
Tunability Refer to para. 1–5.1.3 page 128
Transmitted power Refer to para. 1–5.1.3 page 128
99% power channel
bandwidth and Emission Refer to para. 1–5.1.4 page 129
Designator
ATPC range 20 dB (Pmax / Pmax–20 dB)
RTPC range 30 dB (Pmax / Pmax–30 dB) (ETSI mask compliance till Pmax–20 dB)
Tx level with Tx mute ON < –30 dBm
RF frequency stability 10 ppm
Synthesizer step 250 kHz
RF spectrum masks Compliant with the relevant ETSI standards
Spurious Compliant with the relevant ETSI standards
emissions Compliant with ERC Rec. 74–01
BER receiver threshold
Refer to para. 1–5.1.5 page 130 (ETSI)
System gain
Rx max input level –20 dBm (for a BER of 10–3)
Switching system Refer to para. 1–5.1.6 page 133
SC #1 – DATA CHANNEL
– 1x64 Kb/s data channel configurable alternatively as one of the
following modes:
• G.703 asynchronous co–directional
• V11 co–directional
• V11 contra–directional
User service channels • 4.8/9.6 Kbps V11
• 4.8/9.6 Kbps V24/V28 asynchronous
– 1x64 Kbps V11 co–directional or G703 (DTE or codirectional)
[also embedded in E1 slot for TMN ( first tributary, first slot) ]
SC #2 – EOW
Omnibus voice channel 64 kbit/s DTMF (Q.23) + 4–wire party line (2
ways)
– NMS–V.11: 1x64 kbit/s V.11 co–directional for TMN (port 1)
– NMS–G.703: 1x64 kbit/s G.703 co–directional for TMN (port 2)
NMS channels
– NMS–RF: 1x64 kbit/s radio channel for TMN (internal to the radio
frame)
126 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–5.1.1 Reference system standards
ETSI standard
Standard
Frequency Frequency
ETSI reference Tx/Rx
Equipment band range Channeling
standard separation
(GHz) (GHz)
(MHz)
150,154,160,
7 7.11–7.9 161,168,182,
196,245
9470 AWY ITU–R F.385 119, 126,

EN 301 216 151.614,
4&16 QAM ITU–R F.386
208,266,
8 7.725–9.5
294.44,
305.56,
311.32
EN 301 128
9413 AWY 4QAM
Class 1 ERC 12–02
13 GHz 12.75–13.25 266
9413 AWY16QAM EN 301 128 ITU–R Rec 497
Class 2
EN 301 128
9415 AWY 4QAM MEXICO 315
Class 1
15 GHz 14.4–15.35 ERC 12–07 728
EN 301 128 ITU–R Rec 636 420,490,644
9415 AWY 16QAM
Class 2
9418 AWY 4QAM ERC 12–03 1008,1010
EN 301 128
18 GHz 17.7–19.7 ITU–R Rec 595 340,1560
9418 AWY 16QAM Class 1
CHINA 1092.5
EN 300 198
9423 AWY 4QAM 1008, 1050,
Class 2 ERC 13–02 annex A
23 GHz 21.2–23.6 1200,1232
EN 300 198 ITU–R Rec 637
9423 AWY 16QAM 1200
Class 4
EN 300 431
9425 AWY 4QAM
Class 2 24.5–26.5 ERC 13–02
25 GHz 1008
EN 300 431 ITU–R Rec. 748
9425 AWY 16QAM
Class 4
EN 300 431
9428 AWY 4QAM
Class 2 ERC 13–02
28 GHz 27.5–29.5 1008
EN 300 431 ITU–R Rec. 748
9428 AWY 16QAM
Class 4
EN 300 197
9438 AWY 4QAM
Class 2 ERC 12–01
38 GHz 37–39.5 1260
EN 300 197 ITU–R Rec 749
9438 AWY16QAM
Class 4
3DB 16142 CAAA Ed.01A–DRAFT 127 / 576

1–5.1.2 RF channelling

ETSI RF CHANNELING

Capacity (Mbit/s) 2x2 4x2 8x2 16x2 32x2
RF Channeling with 4 QAM (MHz) 3.5 7 14 28 –
RF Channeling with 16 QAM (MHz) – 3.5 7 14 28
1–5.1.3 Transmitted power at antenna port
Tolerance:
– ± 2.0 dB in temperature range –33°C to +55°C
Output Output power setting (dBm)

Tx/Rx
power
Equipment separation
(dBm) N.B. ATPC range = 20 dBm
(MHz) RTPC range = 30 dBm
(Note 1)
7GHz: 150, 154, 160, 161, ATPC : +25 to +5 dBm

9470 AWY 4QAM 168, 182, 196, 245 25
RTPC : +25 to –5 dBm with 1 dB step
8GHz: 119, 126, 151.614,

ATPC : +21 to +1 dBm
9470 AWY 16QAM 208, 213.5, 266, 294.44, 21
305.56, 311.32
9413 AWY 4QAM 24
266
9413 AWY 16QAM 20
24
9415 AWY 4QAM 728, 315, 420, 490, 475
(*) , 644 ATPC : +21 to +1 dBm
21
(*) values for 475 referred ATPC : +21 to +1 dBm
to the High Power version 21
9415 AWY16QAM (see Tab. 31. on page 104)
20
9418 AWY 4QAM 22
1008,1010,340, RTPC : +22 to –8 dBm with 1 dB step
1560, 1092.5 ATPC : +19 to –1 dBm
9418 AWY 16 QAM 19
ATPC : +19 to –1 dBm
9423 AWY 4QAM 19
1008,1200, RTPC : +19 to –11 dBm with 1 dB step
1232 ATPC : +16 to –4 dBm
9423 AWY 16QAM 16
128 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Output Output power setting (dBm)
Tx/Rx
power
Equipment separation
(dBm) N.B. ATPC range = 20 dBm
(MHz)
(Note 1) RTPC range = 30 dBm

9425 AWY 4QAM 17
1008
9425 AWY 16QAM 14
9428 AWY 4QAM 16
1008
9428 AWY 16QAM 13
9438 AWY 4QAM 1260 16
9438 AWY 16QAM 1260 13
Note 1: Output power at antenna port.
1–5.1.4 99% power channel bandwidth and Emission Designator
ITU–R/CEPT Rec.
99% Power Channel Emission
Radio Type Channel Bandwidth
Bandwidth [MHz] Designator
[MHz]
9400 AWY 4QAM 2E1 2,8 3,5 3M5D7W
9400 AWY 4QAM 4E1 5,5 7 7M0D7W
9400 AWY 4QAM 8E1 10,9 14 14M0D7W
9400 AWY 4QAM 16E1 21,7 28 28M0D7W
9400 AWY 16QAM 4E1 2,8 3,5 3M5D7W
9400 AWY 16QAM 8E1 5,5 7 7M0D7W
9400 AWY 16QAM 16E1 10,9 14 14M0D7W
9400 AWY 16QAM 32E1 21,7 28 28M0D7W
3DB 16142 CAAA Ed.01A–DRAFT 129 / 576

1–5.1.5 ETSI System Characteristics

Data is split into following Tab. 47. to Tab. 51. according to capacity.

Note for all tables: Transmitted PTX tolerance:
– ±0,5dB @ Ambient Temperature
– ±2dB @ ODU Operating temperature range – 33°C ÷ + 55°C
Tab. 47. ETSI System Characteristics 32E1

GHz ⇒ 7/8 13 15 18 23 25 28 38
QAM
Typ. Guar Typ. Guar Typ. Guar Typ. Guar Typ. Guar Typ. Guar Typ. Guar Typ. Guar
⇓
TX Output
Power @ 16 21 20 20 19 16 14 13 13
Antenna Port
10–3 BER
Threshold @ 16 –79 –76 –80 –77 –80 –77 –78 –75 –78 –75 –77 –74 –77 –74 –76 –73
Antenna Port
10–6 BER
Threshold @ 16 –78 –75 –78 –76 –78 –76 –76 –74 –76 –74 –75 –73 –75 –73 –74 –72
Antenna Port
Net System
Gain dB @
16 100 100 100 87 94 91 90 89
10–3 BER
Threshold
Net System
Gain dB @
16 99 98 98 95 92 89 88 87
10–6 BER
Threshold
GHz ⇒ 7/8 13 15 18 23 25 28 38
QAM
⇓
TX Output 4 25 24 24 22 19 17 16 16
Power @
Antenna Port 16 21 20 20 19 16 14 13 13
10–3 BER 4 –86 –83 –86 –84 –86 –84 –84 –82 –84 –82 –83 –81 –83 –81 –82 –80
Threshold @
Antenna Port 16 –82 –79 –82 –80 –82 –80 –80 –78 –80 –78 –79 –77 –79 –77 –78 –76
10–6 BER 4 –85 –82 –85 –83 –85 –83 –83 –81 –83 –81 –82 –80 –82 –80 –81 –79
Threshold @
Antenna Port 16 –81 –78 –81 –79 –81 –79 –79 –77 –79 –77 –78 –76 –78 –76 –77 –75
Net System 4 111 110 110 106 103 100 99 98

Gain dB @
10–3 BER
Threshold 16 103 102 102 99 96 93 92 91
Net System 4 110 109 109 105 102 99 98 97

Gain dB @
10–6 BER
Threshold 16 102 101 101 98 95 92 91 90
130 / 576 3DB 16142 CAAA Ed.01A–DRAFT

GHz ⇒ 7/8 13 15 18 23 25 28 38
QAM
Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar.
⇓
TX Output 4 25 24 24 22 19 17 16 16
Power @
Antenna Port 16 21 20 20 19 16 14 13 13
10–3 BER 4 –89 –86 –89 –87 –89 –87 –87 –85 –87 –85 –86 –84 –86 –84 –85 –83
Threshold @
Antenna Port 16 –85 –82 –85 –83 –85 –83 –83 –81 –83 –81 –82 –80 –81 –79 –80 –78
10–6 BER 4 –88 –85 –88 –86 –88 –86 –86 –84 –86 –84 –85 –83 –85 –83 –84 –82
Threshold @
Antenna Port 16 –84 –81 –84 –82 –84 –82 –82 –80 –82 –80 –81 –79 –80 –78 –79 –77
Net System 4 114 113 113 109 106 103 102 101
Gain dB @
10–3 BER
Threshold 16 106 105 105 102 99 96 94 93
Net System 4 113 112 112 108 105 102 101 100
Gain dB @
10–6 BER
Threshold 16 105 104 104 101 98 95 93 92
GHz ⇒ 7/8 13 15 18 23 25 28 38
QAM
Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar. Typ. Guar.
⇓
TX Output 4 25 24 24 22 19 17 16 16
Power @
Antenna Port 16 21 20 20 19 16 14 13 13
10–3 BER 4 –92 –89 –92 –90 –92 –90 –90 –88 –90 –88 –89 –87 –89 –87 –88 –86
Threshold @
Antenna Port 16 –88 –85 –88 –86 –88 –86 –86 –84 –86 –84 –84 –82 –83 –81 –81 –79
10–6 BER 4 –91 –88 –91 –89 –91 –89 –89 –87 –89 –87 –88 –86 –88 –86 –87 –85
Threshold @
Antenna Port 16 –87 –84 –87 –85 –87 –85 –85 –83 –85 –83 –83 –81 –82 –80 –80 –78
Net System 4 117 116 116 112 109 106 105 104
Gain dB @
10–3 BER
Threshold 16 109 108 108 105 102 98 96 94
Net System 4 116 115 115 111 108 105 104 103
Gain dB @
10–6 BER
Threshold 16 108 107 107 104 101 97 95 93
3DB 16142 CAAA Ed.01A–DRAFT 131 / 576


GHz ⇒ 7/8 13 15 18 23 25 28 38

QAM
⇓
TX Output 4 25 24 24 22 19 17 16 16
Power @
Antenna Port 16 na na na na na na na na
10–3 BER 4 –95 –92 –95 –93 –95 –93 –93 –91 –93 –91 –92 –90 –92 –90 –91 –89
Threshold @
Antenna Port 16 na na na na na na na na na na na na na na na na
10–6 BER 4 –94 –91 –94 –92 –94 –92 –92 –90 –92 –90 –91 –89 –91 –89 –90 –88
Threshold @
Antenna Port 16 na na na na na na na na na na na na na na na na
Net System 4 120 119 119 115 112 109 108 107
Gain dB @
10–3 BER
Threshold 16 na na na na na na na na
Net System 4 119 118 118 114 111 108 107 106
Gain dB @
10–6 BER
Threshold 16 na na na na na na na na
132 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–5.1.6 Protection switching system
[1] EPS (Equipment Protection System)

In 1+1 configurations, the system can support 3 levels of protection against hardware problems.
All the switches are independent and have its own switching criteria.
Available switches
ODU switch
Tx EPS Rx EPS
(HSB)
Select the IDU unit in Tx Select the IDU unit in Rx Select the ODU on line
Not hitless Not hitless Not hitless
Non revertive/Revertive Non revertive/Revertive Non revertive/Revertive
Switch vs. Configuration
Configuration Tx EPS Rx EPS ODU switch
1+1 FD YES YES NO
1+1HSB YES YES YES
[2] RPS (Radio Protection System)
RPS, hitless–switch type, is equipped to provide protection against radio propagation problems.
3DB 16142 CAAA Ed.01A–DRAFT 133 / 576

1–5.2 Tributary interfaces

E1

Input / output
ITU–T G.703
electrical interface
Code
75Ω unbal
Impedance
120Ω bal
Jitter Generation ITU–T G.823
Jitter Tolerance ITU–T G.823
ITU–T G.736
Jitter Transfer
ITU–T G.742
1–5.3 Modem
Modulation 4/16 QAM

Demodulation Coherent
Equalizer type 19–tap FSE
Channel coding Reed Solomon (255,239)
Spectrum shaping Raised cosine
1–5.4 Maximum capacity and Modulation type
The employed SOFTWARE KEY (stored in the FLASH CARD plugged into the IDU Main unit) gives the
maximum capacity for the tributaries and the Modulation Type.
For details please refer to Tab. 22. on page 89.
1–5.5 IDU–ODU cable
Coax. cable type (single) Filotex ET 390998 or equivalent

Coax. connector N (50 ohm)
Guaranteed maximum distance between Up to 150 m (492 feet).
IDU and ODU For details, refer to the Installation handbook.
Lightening protection ITU–T K17 (current 333 A)
Signals on the cable DC Voltage/HDB3 Tx/HDB3 Rx (Note 1)
Gross bit rate on the cable:
– ETSI (2 to 16xE1) 39.168 Mbit/s
– ETSI (17 to 32xE1) 78.336 Mbit/s
Note 1: The HDB3 signal contains the main signal, auxiliary signal and IDU–ODU service channel.
134 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–5.6 Man–machine interface
Visual (LEDs) 9 (on IDU Main unit) +3 (on IDU Extension unit)
– F interface for Personal Computer (WindowsTM) RS232C

– TMN interface Ethernet 10/100 Base–T
Other
– TMN Data channel 64kbit/s interface RS422/G703
– Interface for Telephone Service Channel
1–5.7 Alarms
3 outputs (IDU HW Failure alarm, ODU Main Failure alarm, ODU Spare
Equipment alarms
Failure alarm)
Housekeeping alarms 7 inputs / 4 outputs
1–5.8 Power supply
DC nominal voltage (primary) 48 to 60 Vdc 20%

Polarity + or – floating (isolated ground)
1+0 : 50W
Max Power Consumption
1+1 : 100W
1–5.9 Mechanical characteristics
Dimensions (H x W x D) H Weight
43 x 210 x 443 mm < 2.5 kg
1+0 IDU 1U
1.7 x 8.3 x 17.4 in < 5.5 lb
86 x 210 x 443 mm < 5 kg
1+1 IDU 2U
3.4 x 8.3 x 17.4 in < 11 lb
ODU see Tab. 24. on page 94
– Integrated with 30, 60, 90, 120 cm (1FT, 2FT, 3FT, 4FT) diameter;
availability according to frequency (refer to Tab. 43. on page 116 for de-
Antenna tails)
– Separated with larger diameters
3DB 16142 CAAA Ed.01A–DRAFT 135 / 576

1–5.10 Environmental conditions

Main environmental aspects of Alcatel–Lucent products are:

– Energy consumption during manufacturing and use
– Materials harmfulness and recyclability
– Emission to air, water or soil related to the manufacturing and the use of the product
– Electromagnetic (EM) emissions
– Value recovery at the product end of life
1–5.10.1 Operating environmental conditions
Storage EN 300 019 class 1.3

Transport EN 300 019 class 2.3
EN 300 019 class 3.2
IDU
Temperature range: –5°C to +55°C (23°F to 131°F)
Operation
EN 300 019 class 4.1, IP 67
ODU
Temperature range: –33°C to +55°C (–27.4°F to 131°F)
1–5.10.2 Electro–magnetic compatibility/safety
EMC EN 300 385 class B grade B/FCC Part 15 subpart B–class A

Safety EN 60 950
Power supply EN 300 132
Electro–Static
EN 55022 class B
discharge
Symmetric protection implemented in ODU & IDU
Lightning protection 5kV on cable ground according to IEC 1000–4–5 with 2 wave types:
1.2/50 μs and 10/700 μs
1–5.10.3 Waste from Electrical and Electronic Equipment (WEEE)
WEEE management for Alcatel–Lucent products is in compliance with the Directive 2002/96/EC On Waste
of Electrical and Electronic Equipment.
The starting date coming into force for the European directive is 13th August 2005
In the different countries the European directive is effective once transposed in the specific country
legislation
All Alcatel–Lucent products fall under in Category 3 of Annex 1A of the WEEE directive (Directive
2002/96/EC) i.e. “ IT and Telecommunication equipment “ under item “ other products transmitting sound,
images or other information by telecommunications. “
Alcatel–Lucent products fall under WEEE directive name: “ Other product or equipment of transmitting
sound, images or other information by telecommunications “ in Annex 1B.
The marking printed on the product denotes compliancy with the above Directive
(see para.A.7 on page 539).

This mark will not cause any responsibility as all responsibilities will be defined by contract.
136 / 576 3DB 16142 CAAA Ed.01A–DRAFT

1–5.11 Dismantling & Recycling
1–5.11.1 WEEE general information

A new European directive was published on the 13th of February 2003 on Wastes of Electrical and
Electronic Equipment ( WEEE ) identified as EU Directive 2002/96/EC.
EU Directive 2002/96/EC sets rules for the collection and treatment of electrical and electronic equipment
in Europe coming into force from August 13th 2005.
Two regimes have been defined :

– Waste of household equipment
– Waste of professional equipment
As a consequence this paragraph of this handbook focuses on professional equipment regime.
There are two e–waste stream to be considered :

– Historical e–waste or waste of equipment put on the market before August 13th 2005
– Future waste or waste of equipment put on the market after 13th August 2005
The European directive introduce possible different responsibilities in the two cases, responsibilities that
are anyway specified in the contract between customer and supplier in agreement with the transposition
of the Directive in the Local Legislation.
1–5.11.2 Reference documentation for dismantling and recycling
Alcatel–Lucent Reference documentation for dismantling and recycling detail are the documents:
– Environmental guide
– Ecodeclaration
As far as 9400AWY equipment is concerned, reference documentation for dismantling and recycling detail
are the documents:
Tab. 52. Reference documentation for dismantling and recycling detail for 9400AWY equipment
DOC.
Product Code TYPE Denomination
(N.B.)
AWY/S 8BW036860000 BFZZA 9400 AWY/S ENVIRONMENTAL GUIDE
AWY/S 8BW036840000 EUZZA 9400AWY SCALABLE RADIO SYSTEM ECODECLARATION
N.B. DOC. TYPE for Alcatel–Lucent internal use only
Such documents are available on specific request to your Alcatel–Lucent local dealer.
NOTE FOR Alcatel–Lucent INTERNAL USE
cited documents, in Adobe Acrobat pdf format, can be retrieved from PDM archive. Get highest
available edition.
3DB 16142 CAAA Ed.01A–DRAFT 137 / 576

a)
138 / 576
END OF SECTION 1

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL

Chapter 2–1 – SWP 9400AWY IDU32 description and versions

141
It gives general information both independent and dependent on the SWP version.
Chapter 2–2 – Introduction on TCO Suite and CT views and menus
It describes the functions of the TCO Suite, describes how to start and close the 143
Craft Terminal application, how to login and logout the NE, and sums–up the
organization of the 9400AWY NE Craft Terminal, presented after the NE login.
EQUIPMENT CONFIGURATION MANAGEMENT
Chapter 2–3 – Configuration
195
It describes the configuration relevant to the equipment management.
Chapter 2–4 – Equipment
It deals with the presentation of the N.E. and the structure of the hierarchical tree, 223
and the types of subracks and boards, that comprise the Network Element.
Chapter 2–5 – Line Interface
It describes the operations necessary for the configuration setting and verification 233
of each tributary.
Chapter 2–6 – Radio
243
It deals with the management of the Radio transmission features.
Chapter 2–7 – External input and output points
It describes how to display and set the input/output environmental alarms 253
(housekeeping alarms).
FUNCTIONS FOR MAINTENANCE
Chapter 2–8 – Supervision
It describes how to manage the NE access from OS or local ECT and how to restart 257
the NE.
Chapter 2–9 – Protection schemes
263
It deals with the management of the Radio protections.
Chapter 2–10 – Loopbacks
It describes the commands for loopback management, for commissioning or 275
maintenance purposes.
Chapter 2–11 – Diagnosis
It describes how to access the Alarm and Event Log files and explains the
Summary Block Diagram View menu. 285
N.B. The chapter does not describe the Log Browser. Reference must be
done to the specific “ELB Operator’s Handbook”.
Chapter 2–12 – Performance Monitoring
291
It deals with the use of the Performance Monitoring functionalities.
SOFTWARE MANAGEMENT
Chapter 2–13 – Software Management
It deals with the management of the functions related to the software 301
verification/download.
Chapter 2–14 – MIB Management
It deals with the management of the functions related to the back–up and restore 305
of equipment configuration data.
3DB 16142 CAAA Ed.01A–DRAFT 139 / 576

140 / 576
2–1 SWP 9400AWY IDU32 DESCRIPTION AND VERSIONS
This chapter gives :
– information regarding the Software Packages this manual refers to, that is independent of the specific
SWP Version: commercial information (SWP and Software Licences P/Ns): para.2–1.2 below;
– operative information regarding the Software Packages Version 2.1.x, starting from version V2.1.0:
requirements (PC and equipment Firmware), Reference Information Model, SW Package
Identification, SW Package Components, ECT SW Sub–Component, NE MIB Compatibility, new
features (only for versions > V2.1.0), restrictions and known problems:
• SWP 9400AWY IDU32 V2.1.0 specific information, para.2–1.3 on page 142
2–1.2 SWP 9400AWY IDU32 description
2–1.2.1 General
The software products are distributed by Alcatel–Lucent in a CD–ROM.
In this CD–ROM are contained:
• Software packages for NE management by means of the craft terminal
• Software package of the NE, to be installed in the NE or update the NE (by means of download
function)
The software package used for management allows the dialogue between craft terminal and NE, to
realize all the functions of the NE and EML–ULS ).
The software package used for updating the NE must be installed on the PC and then downloaded on
the NE, thus following product evolution.
Alcatel–Lucent typically offers several software licences on the software product.
They are referred both to the Network Element software features and to the Craft Terminal software
features.
2–1.2.2 Software product list and part numbers
Every Software Product is identified by a Technical Code and a Technical Description and is distributed
by a CD–ROM with the same identifiers, listed on the following table:
Tab. 53. Software products part numbers
REF Technical Description Technical Code
[a] SWP 9400AWY IDU32 3DB16131AA**
[b] SWP OPTICS–IM WTD SNMP V3.01 3DB16145AA**
3DB 16142 CAAA Ed.01A–DRAFT 141 / 576

2–1.3 SWP 9400AWY IDU32 V2.1.0 specific information

N.B. This paragraph has to be completed, after final SWP release document

availability.
N.B. With reference to the Versions stated in this chapter, please read carefully the
N.B. on page 551.
2–1.3.1 PC characteristics
Refer to para.3–1.1.1 on page 313
2–1.3.2 Reference Information Models
– Reference SNMP–IM version with ECT Platform: 3.03
– Reference SNMP–IM version with NE: 3.01 (SGPA 3.5.0)

Related SWP: REF.[b] in Tab. 53. on page 141.
2–1.3.3 Equipment hardware constraints

t.b.d.
2–1.3.4 SWP version specific data

t.b.d.
2–1.3.4.1 SW Package Identification

t.b.d.
2–1.3.4.2 SW Package Components

t.b.d.
2–1.3.4.3 ECT SW Sub–Components

t.b.d.
2–1.3.4.4 NE MIB Compatibility
NE MIB is not compatible with any releases 1.0.x and 2.0.x.
2–1.3.5 Restrictions and known problems

t.b.d.
142 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS
This chapter describes the functions of the TCO Suite, describes how to start and close the Craft Terminal
application, how to login and logout the NE, and sums–up the organization of the 9400AWY NE Craft
Terminal, presented after the NE login.
– Requirements on page 144
– TCO Suite description on page 146
– TCO Suite Alarms & Settings functions on page 162
– PC–NE physical connections on page 174, including:

• Physical interfaces for the NE management on page 174
• Local connection of the Craft Terminal to the NE on page 175
– Craft Terminal: NE supervision, login, logoff and switch off on page 176
– 9400AWY view organization on page 185
– Introduction to the CT menu options on page 190
3DB 16142 CAAA Ed.01A–DRAFT 143 / 576

2–2.1 Requirements

a) PC characteristics

The PC used for TCO Suite application and/or employed as Craft Terminal must meet all
specifications pointed out in para.3–1.1.1 on page 313.
b) Cables necessary for PC–to–NE local connection
• for the local connection between PC and NE RS232 serial ports, one RS232 cable is necessary
(P/N 1AB054120027)
N.B. In alternative, for the usage of the NE’s F–interface with any PC having no RS232
serial port (but obviously with USB ports available) it is possible to employ the “USB
TO RS232 ADAPTER” , ordering it to Alcatel–Lucent (P/N 1AF11294AA**).
• for the local direct connection between PC and NE Ethernet ports, one cross–connect Ethernet
cable is necessary.
Otherwise the connection can be done by a normal Ethernet cable through a LAN.
For explanatory drawing, see Fig. 68. on page 160.
Typical Alcatel–Lucent Ethernet cables are:
Tab. 54. Typical Alcatel–Lucent Ethernet cables

Length Type P/N
normal 3DB 14050 AA**
6m
cross–connect 3DB 14051 AA**
normal 3DB 05020 AA**
2m
cross–connect 3DB 05021 AA**
N.B. The TCO Suite applications can use the Ethernet interface only.
The Craft Terminal application can use both the Ethernet and the RS232 interfaces.
c) Craft Terminal
If the Craft Terminal application must be used, the SWP installation must have been already carried
out, as specified in chapter 3–1 on page 313.
d) NE state
• the SWP (NE–specific components) must be already present in the NE’s flash card and its
active version (see point [2] on page 62 to do this check) must be equal to that of the:
– SWP CD–ROM this manual refers to (in case of TCO Suite application run directly from
the CD–ROM itself)
– SWP installed in the Craft Terminal (see point [1] on page 61 to do this check).
Solve different situations, if any, according to instructions given in para.1–2.6.4 on page 63.
• if the NE must be accessed in remote way (by TCO Suite application or by RECT application)
it must have already a valid TCP/IP address, and such address must be known by the Operator.
144 / 576 3DB 16142 CAAA Ed.01A–DRAFT

e) Operator profiles and allowed operations
The menu options described in this section are all available logging in the system with the
Administrator profile username and password. Logging the system with other operator
profiles result in some functionality access limitations. For further information please refer
to Profiles management , para.2–3.6 on page 218.
f) Operator skills
• the Operator shall be familiar with the use of personal computers in WINDOWS–NT /
WINDOWS–2000 / WINDOWS–XP (professional version only) environment, internally to
which the Network Element’s application software operates.
• the Operator must be familiar with all the functionalities of this equipment.
• 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).
g) Documentation
Besides this manual, all the documentation set this manual belongs to must be available to the
Operator, to retrieve pieces of information not contained in this manual. The documentation set is
described in Appendix C on page 551.
3DB 16142 CAAA Ed.01A–DRAFT 145 / 576

2–2.2 TCO Suite description

This paragraph is organized as follows:

– TCO Suite scopes below
– Summary on page 147
– TCO Suite start–up on page 148
– TCO Suite Main Menu functions on page 154, including:

• Pre–Provisioning Tool on page 155
• Set–Up Tool on page 155
• Alarms & Settings on page 156
• Advanced Settings on page 156
– TCO Suite Advanced Settings Page on page 157, including:

• Java JRE Package Installation on page 158
• Serial –F– Interface Driver Installation on page 159
• 1320CT Package Installation on page 159
• 1320CT Package De–Installation on page 159
• Local Copy of TCO Suite on page 159
– Note: Direct and Remote Connections on page 160
– Warning about interface customization carried out by the Direct Connection on page 161
2–2.2.1 TCO Suite scopes
The TCO Suite is a feature that allows the operator to access and configure the NE from his/her PC without
the need for software installation in PC environment (i.e. running the TCO Suite directly from the SWP
CD–ROM).
Moreover, after having installed the SWP components and the TCO Suite local copy in the PC environment
(as described in chapter 3–1 on page 313), most of TCO Suite functionalities are available also after
having removed the SWP CD–ROM from the PC CDROM unit.
TCO Suite works through web pages with simple operations available with a single mouse click.
146 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.2.2 Summary
After having started up the TCO Suite (para.2–2.2.3 on page 148), the TCO Suite Main Menu becomes
available (Fig. 64. on page 155) with the following main tools:
– Pre–Provisioning Tool
This is a full–local application.
– Set–Up Tool and Alarms & Settings

These applications require the access and the login to a 9400AWY NE from your PC.
To access and login a 9400AWY NE from you PC for these applications:
• the CT–NE connection can be:
– physically and logically local, through a cross–connect Ethernet cable for the local direct
connection between PC and NE Ethernet ports
– physically local but logically remote, by a normal Ethernet cable through a LAN for the
– physically and logically remote, by a connection between PC Ethernet port and the NE
through the RECT function or the TCP/IP network.
N.B. The Set–Up Tool and Alarms & Settings applications cannot be used through the
PC–NE local connection by RS232 serial F interface
• you must have a UserName and password set
• in case of logically remote connection, you must know the NE’s TCP/IP address
– Operational & Maintenance

This application corresponds to the 1320CT application. Refer to para.176 on page 2–2.5 for details.
3DB 16142 CAAA Ed.01A–DRAFT 147 / 576

2–2.2.3 TCO Suite start–up

The Suite auto–runs itself (if this feature is enabled on user’s PC) as soon as CD–ROM is read by PC.

If auto–run does not start, user must run (double–click with mouse on) the Start.exe file, available on

CD–ROM root in order to launch TCO Suite.
Since this TCO Suite works using Java™ software, it is mandatory to have a Java Runtime Environment
(JRE) installed on the system. Allowed JREs are Sun only, with version number higher or equal than
1.4.2_12. The first operation performed by auto–run procedure is the check for JRE.
All HTML pages used for TCO Suite are XHTML 1.1 and CSS 2.0 standards compliant with respect to W3C
(WWW Consortium) specifications.
Minimal screen resolution allowed to use TCO Suite is 1024x768 pixels
If there is no JRE on user’s PC or if there is a JRE installed on user’s PC but its version number if lower
than 1.4.2_12, user will be asked to install the Sun Java Runtime Environment version 1.4.2_12 available
on TCO Suite CD–ROM (Fig. 51. below).
Fig. 51. Java installation request
In both cases:
– if user denies authorization to install the suitable JRE, TCO Suite won’t be executed at all
– if user gives authorization to install the suitable JRE, after some minutes the installation message
appears:
Fig. 52. JRE installation completion
148 / 576 3DB 16142 CAAA Ed.01A–DRAFT

After, the default browser (configured as for user preferences) opens the TCO Suite Start.html page
(Fig. 64. on page 155).
Special conditions
Depending on selected browser, on browser configuration and preferences and on user’s choices some
security questions could be made to the user. Fig. 53. below shows an example of the first warning user
could see.
Fig. 53. Browser loading warning
In case of specific user’s browser configuration, the browser could ask some questions about “secure” or
“blocked” content (Fig. 54. on page 149) and before operating on TCO Suite pages user must click on this
information box (usually shown in a pale yellow background on top of the browser HTML page, see
(Fig. 54. on page 149) and allow the browser to manage this information (Fig. 55. on page 150).
click
Fig. 54. Security Questions: Secure Content
As stated before, the layout and graphical representation for this question (if asked) could be different from
browser to browser and, with respect to the same browser, language and information could vary too.
3DB 16142 CAAA Ed.01A–DRAFT 149 / 576

click
Fig. 55. Secure Questions: Allow Secure Content
Usually, the user has to click with the mouse on such yellow bar and a pop–up menu will appear to ask
user if he/she allows running this special content (Fig. 55. above). In some cases another confirmation
is requested to the user (Fig. 56. on page 150).
Fig. 56. Execution confirmation (Security Warning)
Generally speaking, as soon as the browser is allowed to execute Java applets inside the HTML page,
a specific dialog will appear when browser recognizes that Java applets are inside the page.
As usual, both language and graphical layout could vary with respect to browser, operating system
version, operating system and browser languages and so on. Following Fig. 57. and Fig. 58. show a
couple of examples of this warnings: as wrote before, things can differ with respect to language or graphics
and so on.
150 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 57. Security Warning (English browser on Italian System)
Fig. 58. Security Warning (Italian browser on Italian System)
This request is necessarily shown because TCO Suite applets needs specific parameters and permissions
in order to perform requested operations (reading and writing of files, for example). Applets used are
authenticated and a certificate is used to sign applets in order to tell user (and browser) that someone
(Alcatel–Lucent Italia SpA, WTD R&D Software CC, in this case) guarantees about the safety in loading
those applets inside a browser. Other examples could be more similar to the one shown in Fig. 59. below,
usually with JREs with version number 1.4:
3DB 16142 CAAA Ed.01A–DRAFT 151 / 576

Fig. 59. Security Warning (Java 1.4)
Following Fig. 60. shows a wrong security warning with a Java version lower than 1.4. In this case the
TCO Suite won’t work:
Fig. 60. Wrong Security Warning (Java 1.3)
Another difference that user could perceive is related to a missing JRE but, even in this case, the graphical
layout will differ from system and browser.
If user opens the Start.html page even without a JRE installed shown page would differ from browser
and system versions. Following Fig. 61. shows a Mozilla Firefox browser with no JRE installed. On top of
browser a yellow alert bar can be seen: in this case the browser detected a special content for which it
has no plug–in so the browser asks the user to automatically install needed plug–in by searching it on the
Internet.
152 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 61. Firefox browser: no JRE installed
If user allows to search for related plug–in, a specific operation could be started (Fig. 62. below).
Fig. 62. Firefox plug–in search
And if the user agrees, the browser could automatically install the correct plug–in (see following Fig. 63. ).
Since this operations is specifically related to Mozilla Firefox browser, some details could be different with
respect to used version. Anyway, since this operation is automatically managed by the browser no control
can be made through TCO Suite. Using this procedure will usually install the latest JRE version available
as Mozilla Firefox plugin that is usually newer than the JRE 1.4.2_12 available within the TCO Suite.
3DB 16142 CAAA Ed.01A–DRAFT 153 / 576

Fig. 63. Firefox plug–in installation
As stated before, graphical layout, language, information, alert boxes and everything shown by a browser
would differ from each browser and operating system version or release.
Then, when Java applets and the Start.html page finally goes for a complete execution, the user will
see the content shown in Fig. 64. on page 155.
2–2.2.4 TCO Suite Main Menu functions
Fig. 64. and Fig. 65. on page 155 show the layouts of the “TCO Suite Main Page” as described from the
internal version of AS.html file, respectively for the “CD–ROM version” and the “Local version”.
N.B. The TCO Suite Local version must be explicitly created as described in para.2–2.2.5.5 on page
159
This page shows the main TCO Suite menu with the following functions:
– Pre–Provisioning Tool
– Set–Up Tool
– Alarms & Settings
– Operational & Maintenance
– Advanced Settings (N.B.)
N.B. The “Advanced Settings” button is not available in the local version of the “TCO Suite Main
Page”.
154 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 64. TCO Suite Start.html page (CD–ROM version)
Fig. 65. TCO Suite Start.html page (Local version)

Detailed functions and differences between CD–ROM and Local TCO Suites will be described in following
sub–paragraphs.
2–2.2.4.1 Pre–Provisioning Tool
This button is a one–click execution for the Pre–Provisioning Tool.

This tool allows the off–line creation and modification of a provisioning file, without accessing any NE.
This file will be after used to configure the NE (after having logged it) with a simple load command.
For procedure execution, refer to para.3–2.3.6 point [2] on page 373.
2–2.2.4.2 Set–Up Tool
This button is a one–click execution for the Set–Up Tool.

This tool allows to access a NE, recover a configuration file previously created (e.g. through the TCO Suite
Pre–Provisioning Tool) or get configuration data from the NE, and check/modify/apply such a configuration
to the NE.
For procedure execution, refer to para.3–2.3.6 point [3] on page 373.
3DB 16142 CAAA Ed.01A–DRAFT 155 / 576

2–2.2.4.3 Alarms & Settings

The “Alarms & Settings” function allows the user to login a NE through the use of the NE web server via

a generic Internet browser, in order to monitor the status of NE alarms and to get and/or set some NE’s

parameters.
For procedure execution, refer to para.2–2.3 on page 162.
2–2.2.4.4 Operational & Maintenance
This function runs the 1320CT software application.
This function has two different behaviors, one for “CD–ROM” TCO Suite and one for “Local” TCO Suite.
The main difference is related to 1320CT software installation:
– “Local” TCO Suite does not install 1320CT in any case
– “CD–ROM” TCO Suite will perform a complete 1320CT installation, if needed (if such software is not
available).
If 1320CT is available on user’s system, the behavior is common between “Local” and “CD–ROM” TCO
Suites:
[1] CD–ROM TCO Suite

In this case, if the 1320CT platform is not installed, the user will be asked to perform the installation
and, if the user agrees, the installation will be started.
The 1320CT platform installation is described in para.3–1.5 (Installation of SWP components
from the SWP CD–ROM) from step 5 ) on page 320
[2] Local TCO Suite

If user’s PC does not have a 1320CT platform installed, no installation is performed and an error
message is shown to user.
For procedure execution, refer to point e )–1 ) on page 178.
2–2.2.4.5 Advanced Settings
This button will show to user the related HTML page: this function is available through CD–ROM TCO Suite
only. All functions related to this page are described in following para.2–2.2.5 on page 157.
156 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.2.5 TCO Suite Advanced Settings Page
This page is opened clicking the “Advanced Settings” button of the CD–ROM TCO Suite Main Menu
(Fig. 64. on page 155). Such page is shown in Fig. 66. below and contains:
– Java JRE Package Installation
– Serial –F– Interface Driver Installation
– 1320CT Package Installation
– 1320CT Package De–Installation
– Local Copy of TCO Suite
Fig. 66. TCO Suite AS.html page (Advanced Settings)
3DB 16142 CAAA Ed.01A–DRAFT 157 / 576

2–2.2.5.1 Java JRE Package Installation

This button connects to the installation file for the Java Runtime Environment, version 1.4.2_12. The

behavior of this button depends on browser configuration. The usual behavior is:

– Internet Explorer asks the user to “Open” or “Save” the file (Fig. 67. below):
Fig. 67. Internet Explorer: .exe files management
– Mozilla Firefox automatically saves the file, the first time (or every time, depends on configuration)
asking the user where to place it;
– Mozilla browser automatically saves the file, the first time (or every time, depends on configuration)
asking the user where to place it;
In any case, for most browsers the default behavior can be changed but this strictly depends on browser
configuration and user choices.
158 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.2.5.2 Serial –F– Interface Driver Installation
This button starts the installation (from the SWP CD–ROM) in PC environment of the LLMAN (Alcatel
Lower Layer MANager), necessary when communication with NE’s ECT serial port is required.
For procedure execution, refer to para.3–1.7.1 on page 325.
2–2.2.5.3 1320CT Package Installation
This function will automatically perform the complete installation of the existing 1320CT platform without
installing a needed JRE (that is anyway installed if this function can be performed) and without installing
the “Alcatel Lower Layers Manager” software.
For procedure execution, refer to para.3–1.5 on page 318.
2–2.2.5.4 1320CT Package De–Installation
This function is a single–click complete de–installation for the 1320CT package. This function won’t
remove neither possible JRE installed nor “Alcatel Lower Layers Manager” software.
Sequence of screens shown to user depend on speed and performance of user’s PC since all the
procedure is automatic and all the de–installations needed are performed at the same time without the
need for interaction by the user.
2–2.2.5.5 Local Copy of TCO Suite
This function, written as part of the TCO Suite Java applet, allows the user to create the “Local” TCO Suite
by copying the content of the TcoSuite directory on a location specified by user.
For procedure execution, refer to para.3–1.6.1 on page 322.
3DB 16142 CAAA Ed.01A–DRAFT 159 / 576

2–2.2.6 Note: “Direct” And “Remote” Connections

The difference between “Direct” or “Remote” connection, asked to user as in Fig. 71. on page 162, is

depicted in Fig. 68. below, and reflects the working mode for JUSM application:

– in case of “Remote” connection the NE is considered as reachable through the network connected
to user’s PC so no Ethernet configuration is needed and the “Set–Up Tool” or “Alarms & Settings”
function is executed.
– in case of “Direct” connection, user’s PC is considered as directly connected to NE via a

cross–connection Ethernet cable so a Ethernet modification is needed on user’s PC since both
functions (“Set–Up Tool” and “Alarms & Settings”) have to be sure about PC connection with NE in
order to be performed.
IP NETWORK
“Remote”
PC Ethernet interface
HUB
cross–connect Ethernet cable

“Direct”
Fig. 68. ECT–NE “Direct” and “Remote” connections
For this reason, the TCO Suite will perform a search on user’s computer resources in order to find all
network adapters related to active (enabled) network connections. Then, if more than one network adapter
is found, the user must select the one to modify in order to connect his/her PC to the NE. This selection
box is shown in Fig. 69. :
Fig. 69. Network Adapter selection
Such figure is an example created to show the possible layout. Actually, if user’s PC owns one network
adapter only and the “Alcatel Virtual Network Card for Lower Layers”, the selection is automatically done
without bothering the user, which won’t see the dialog box shown in Fig. 69. above.
160 / 576 3DB 16142 CAAA Ed.01A–DRAFT

In order to let the user knows more information about adapters details, by clicking the “Details” toggle
button some supplemental information are shown as in Fig. 70. :
Fig. 70. Network Adapter details
When the user clicks on “Apply” the selected network adapter is modified in order to allow user’s PC
connecting with specified NE.
Network adapters configuration is saved in XML format using the NAML (Network Adapter Markup
Language) format in the NAML directory inside user’s personal directory usually located inside
“Documents And Settings” directory on system disk.
2–2.2.7 Warning about interface customization carried out by the Direct Connection
When the “Direct” connection (described in previous para.2–2.2.6 on page 160) is set up, the system
carries out an interface customization that makes any subsequent attempt to start the Craft Terminal using
the F–interface impossible, even after the logging off from the TCO Suite application and independently
from the settings explained in para.2–2.4.2 on page 175.
These are the simplest alternative ways to solve this situation:
– launch the TCO Suite Alarms & Settings defining the “Remote” connection, then close the TCO
Suite application
or:
– perform the PC shut down.
Any of these operations resets the interface customization said above, so that the start of the Craft
Terminal using the F–interface becomes again possible.
3DB 16142 CAAA Ed.01A–DRAFT 161 / 576

2–2.3 TCO Suite Alarms & Settings functions


– TCO Suite Alarms & Settings start–up below
– Date & Time Setting on page 165
– Configuration Setting on page 166
– Configuration Info on page 167
– Get Configuration File on page 170
– Active Alarms on page 171
– Licence Info on page 172
– Modem Speed on page 172
2–2.3.1 TCO Suite Alarms & Settings start–up
To launch this application, click on the button Alarms & Settings of the “TCO Suite Main Page” (see
Fig. 64. and Fig. 65. on page 155).
Then, User is asked to distinguish between “Direct” or “Remote” connection (Fig. 71. below) and he/she
will be asked to fill the IP address field used to connect to NE.
Fig. 71. Direct or Remote connection by the TCO Suite
The difference between “Direct” or “Remote” connection is described in para.2–2.2.6 on page 160.
WARNING 1: In case you choose the “Direct” connection, read carefully para.2–2.2.7 on page 161
(Warning about interface customization carried out by the Direct Connection)
WARNING 2: In case you have in your network some 9400AWY NEs with SWP 2.0.x (N.B.) and others
with SWP 2.1.x you must be aware that:
• by TCO Suite of SWP 2.0.x you can access only 9400AWY NEs with SWP 2.0.x
• by TCO Suite of SWP 2.1.x you can access only 9400AWY NEs with SWP 2.1.x
The other combinations do not work properly!
N.B. in 9400AWY Rel.2.0, TCO Suite is available starting from SWP–version 2.0.4.
162 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Then (Fig. 72. below), User is asked to provide the Username and Password [same rules as in point 3 )
on page 183]. In case of remote connection, the NE’s IP address entered in previous screen (Fig. 71. )
is displayed.
Fig. 72. NE login by the TCO Suite
As soon as the connection with the NE is established, the Alarms & Settings Main Menu screen appears
(Fig. 73. on page 164).
Operations allowed according to the Login profile (refer to para.2–3.6 on page 218 for details) are:
Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login profile
Login profile
Function Administrator, Craftperson
Viewer
and Operator
Date & Time Setting
YES read only
(para.2–2.3.2 on page 165)
Configuration Setting
YES NO
(para.2–2.3.3 on page 166)
Configuration Info
YES YES
(para.2–2.3.4 on page 167)
Get Configuration File
YES YES
(para.2–2.3.5 on page 170)
Active Alarms
YES YES
(para.2–2.3.6 on page 171)
Licence Info
YES YES
(para.2–2.3.7 on page 172)
Modem Speed
YES read only
(para.2–2.3.8 on page 172)
NAT Option
FOR ALCATEL–LUCENT INTERNAL USE ONLY
(para.2–2.3.9 on page 173)
User can perform desired operations by clicking on proper label in proposed menu. The behavior of the
Web Server for each of menu entry is detailed in the following sub–paragraphs.
Logout button gives the user the possibility to clear its authentication parameters and reload the initial page
(Fig. 73. on page 164) for starting a new session.
The links between pages are available by following standard procedures and correct “navigation” steps.
If the user will follow non–authorized processes or will try to search for other pages, a “404” error will show
the “Page Not Found” result. In this case, the user will be allowed to get back to initial login page and he
has to redo the whole login process.
3DB 16142 CAAA Ed.01A–DRAFT 163 / 576

Fig. 73. TCO Suite’s Alarms & Settings Main Menu screen
WARNING: if, during the usage of the TCO Suite Alarms & Settings functions, the connected NE
becomes unavailable (e.g. for network problems, or after having loaded NE data which
modify the NE IP address), the sand–glass symbol appears and no operations are longer
possible. In this case, close the TCO Suite Alarms & Settings session, then verify the NE
reachability (e.g. by PING function).
164 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.3.2 Date & Time Setting
For authorized users, this function allows to modify NE internal time so that it can be automatically aligned
with user’s PC internal time or the user can set its preferred time and date on NE. Also, it is possible, for
the user, to verify the status of NTP configuration for automatic synchronization using a couple of NTP
server (main and back–up).
There are two functions available to authorized users:
1. NE Time Setting with OS time;
2. GMT Time Manual Setting.
In the first situation (Fig. 74. below) the user will see his/hers PC internal time and by clicking on apply,
NE will receive UTC time based on PC configuration.
For example: if user’s PC is configured as located in central Europe (CET or CEST time zones) and it
shows 2006–08–25 11:40:00, by clicking “Apply” button NE web server will receive 2006–08–25 09:40 due
to Daylight Saving (summer) Time one hour difference with respect to normal time and to one hour time
difference between CET time zone and GMT time zone.
Fig. 74. TCO Suite’s Alarms & Settings “Date & Time Configuration” page
The other function allows user to directly send a specific date and time information to NE without bothering
on time zones but simply specifying all the information needed.
In both cases there could be some short delays (few seconds) between applied time shown after the
operation and current time or selected time.
In case of enabled NTP, this page won’t allow to modify NE time and date
3DB 16142 CAAA Ed.01A–DRAFT 165 / 576

2–2.3.3 Configuration Setting

The set configuration process allows the allowed operator for sending to NE the operator’s desired

configuration.

Fig. 75. TCO Suite’s Alarms & Settings “Configuration Setting” page
To carry out this operation, you must browse from your PC a configuration file “configuration_name.qcml”
previously created (e.g. through the TCO Suite Pre–Provisioning Tool, N.B.), and then click on Apply
Configuration button.
N.B. refer to para.3–2.3.6 on page 373 for details.
166 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.3.4 Configuration Info
The Get Configuration Report function allows the user to download the full NE system report. Selecting
(by click) this function from main menu will show the user a “Save File” screen (Fig. 76. below) that gives
the user the capability to browse its system in order to select the path where to save the full report file.
N.B. With some browsers (e.g. Mozilla), it is necessary to specify a text–reading application (e.g.
WORD PAD) to open and read correctly the file.
Fig. 76. TCO Suite’s Alarms & Settings “Get Report Request”
This screen content, shape, graphics and layout all depend on operating system version and language
and on used browser too. The report file is a text file that describes the configuration of the NE. It contains
all the information once added to the quick configuration report or in the current configuration view used
in the former versions. An example of this file content is shown below:
⋅NE CONFIGURATION
––––––––––––––––
NE Configuration Type:1+0 16E1/DS1–ETH (PSU4860)
Market: ETSI
Frame Structure: 8E1
Modulation: 16QAM
Impedance: Unbalanced 75 Ohm
TRIBUTARIES CONFIGURATION
–––––––––––––––––––––––––
E1 Tributary 1: Signal Mode: Unframed
E1 Tributary 2: Signal Mode: Disabled
E1 Tributary 5: Signal Mode: Framed
E1 Tributary 8: Signal Mode: Framed
DATA CONFIGURATION
––––––––––––––––––
[Ethernet Port 1]
Status: Disabled
Auto Negotiation: Disabled
Speed Without Autonegotiation: 100 Mbit/s
3DB 16142 CAAA Ed.01A–DRAFT 167 / 576

Advertised Capability for AutoNegotiation: 10 Mbit/s
[Ethernet Port 2]

Status: Disabled

Auto Negotiation: Disabled

Speed Without Autonegotiation: 100 Mbit/s
Advertised Capability for AutoNegotiation: 10 Mbit/s
RADIO CONFIGURATION
–––––––––––––––––––
[Channel 1]
Tx Frequency: 0 kHz
Tx Range: [5000000 , 40000000] kHz
Rx Frequency: 0 kHz
Rx Range: [5000000 , 40000000] kHz
Current Tx Power: 30 dBm
Atpc Status: Disabled
Shifter Settings: Unconfigured
EXTERNAL POINTS STATUS

––––––––––––––––––––––
[Input Point 1]
User Label:CPI1
Polarity: Active Closed
[Input Point 2]
User Label:CPI2
[Input Point 3]
User Label:CPI3
[Input Point 4]
User Label:CPI4
[Input Point 5]
User Label:CPI5
[Input Point 6]
User Label:CPI6
[Output Point 1]
User Label:CPO1
Switching Criteria: Manual
External State: Off
[Output Point 2]
User Label:CPO2
External State: Off
[Output Point 3]
User Label:CPO3
External State: Off
[Output Point 4]
User Label:CPO4
External State: Off
NETWORK INFORMATION
–––––––––––––––––––
[Ospf Area 1]
IP Address: 0.0.0.0
168 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Stub Flag: FALSE
[Ospf Area 2]
IP Address: 10.0.1.0
Stub Flag: FALSE

Local IP Address: 10.0.1.2

LAN IP Address: 151.98.141.77
Ethernet Status: Enabled
Mask: 192.0.0.0
MAC Address: 00:20:60:00:03:5e
Routing Protocol: None
[Static Route: 1]
IP Address: 151.98.70.0
IP Mask: 255.255.254.0
Point to Point Interface: RF
[Static Route: 2]
IP Address: 151.98.170.0
IP Mask: 255.255.254.0
[Static Route: 3]
IP Address: 172.24.168.0
IP Mask: 255.255.255.0
[TMN–RF]
Status: Disabled
[TMN–V11]
Status: Disabled
Interface Mode: Not Used
[TMN–G703]
Status: Disabled
Interface Mode: Not Used
NTP CONFIGURATION
–––––––––––––––––
Status: Enabled
Main Server IP Address: 100.5.4.75
Spare Server IP Address: 100.5.5.5
INSTALLED SOFTWARE
––––––––––––––––––
[Active SW Package: R94A – V02.01.00]
Status: Committed
Operational State: Enabled
SW Units:
EC – V03.00.03 – Size(Bytes): 1769472
OC_R – V02.01.01 – Size(Bytes): 215469
The content above describe a sample configuration report in text format.
3DB 16142 CAAA Ed.01A–DRAFT 169 / 576

2–2.3.5 Get Configuration File

Just like the Get Configuration Info function, the Get Configuration File allows the user to download the

full NE system report. Instead of being in “human–readable” text format, the configuration file is described

in QCML format and it can be used by Quick Configuration by Text File or by Pre–Provisioning and Set–Up
Tools. Selecting (by click) this function from main menu will show the user a “Save File” screen
(Fig. 77. below) that gives the user the capability to browse its system in order to select the path where
to save the full report file.
N.B. With some browsers (e.g.Mozilla), it is necessary to specify a text–reading application (e.g.
WORD PAD) to open and read correctly the file.
Fig. 77. TCO Suite’s Alarms & Settings “Get Configuration” Request
This file is an XML standard–based set of configuration information that Pre–Provisioning and Set–Up Tool
can preview in a human–readable HTML layout and allow the user to modify such configuration using a
set of wizard/simplified steps just like the Quick Configuration by Text File do.
170 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.3.6 Active Alarms
Alarms monitoring is represented by a simple colored table that will shows an updated list of active alarms.
Older alarms, anyway, won’t be removed but in order to be more comprehensible, activated alarms table
will be updated by recreating the whole table each time, so showing only all active alarms in any moment.
Fig. 78. TCO Suite’s Alarms & Settings “Active Alarms: Static Page”
This table can be presented into two ways: the first one shown when user chooses “Active Alarms” function
is a simple page that will show to user alarms active at the moment of its selection.
To give user a better control on this status table, a “Refresh” button is provided. This button will redo the
request to NE and updates shown HTML page anytime is pressed.
The “Enable Automatic Refresh” button allows the user to forget about doing a refresh by providing an
automatic refresh process (Fig. 79. below).
Fig. 79. TCO Suite’s Alarms & Settings “Active Alarms: Automatic Page”
This page will do a periodic automatic refresh of its content and anyway allows the user to get back to the
manual refresh page.
3DB 16142 CAAA Ed.01A–DRAFT 171 / 576

2–2.3.7 Licence Info

This page allows user to read license so that he can retrieve data needed by Alcatel–Lucent to produce

a new Software License (Fig. 80. below).

Fig. 80. TCO Suite’s Alarms & Settings “Reading Software License”
2–2.3.8 Modem Speed
This function (Fig. 81. below) allows the authorized user for reading the current F–Interface speed value
and for modifying it through a simple combo box.
Fig. 81. TCO Suite’s Alarms & Settings “Changing F–Interface Speed”
In case of login by viewer profile, the button and combo–box elements are not shown and the page just
displays the current modem speed.
172 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.3.9 NAT option
This function (Fig. 82. below) is for Alcatel–Lucent internal use only.
N.B. please leave always the default option NO set!
Fig. 82. TCO Suite’s Alarms & Settings “NAT option”
3DB 16142 CAAA Ed.01A–DRAFT 173 / 576

2–2.4 PC–NE physical connections

2–2.4.1 Physical interfaces for the NE management

See Fig. 83. below:
– the F interface (RS232 serial interface) is used for the connection with the PC configured as Craft
Terminal. This connection can be:
• local (ECT function, as explained in para.1–2.4.1 on page 50), through the suitable RS232 cable
supplied with the equipment
• physically remote but logically local (ECT function, as above) through an ECT–equipment
connection via the public switched telephone network, as explained in Appendix B on page 541
N.B. the F interface usage requires LLMAN installation [see choice b ) on page 315]
– as shown in Fig. 68. on page 160, the Ethernet interface can be used for the:
• local connection, through a cross–connect Ethernet cable, or through a HUB), to the PC:
– configured as Craft Terminal
– or running the TCO Suite directly from the SWP CD–ROM
• connection to the TCP/IP network (provided that the NE has a valid TCP/IP address).
Notice that by means of this connection, the NE can be reached by:
– the TMN OS (e.g. Alcatel–Lucent 1353NM)
– the PC running the TCO Suite directly from the SWP CD–ROM
– by the Radio interface:
– the NE can be reached:
• from remote Craft Terminals (RECT function, explained in para.1–2.4.2 on page 50)
• or from the TMN OS or from the PC running the TCO Suite directly from the SWP
CD–ROM, when the NE’s Ethernet interface is not connected (but the NE is defined
in the Supervision Network)
– the local Craft Terminal, connected to the F interface or the local Ethernet interface, can
reach other NEs by means of the RECT function
Ethernet Interface F Interface Radio Interface
Fig. 83. MAIN Unit front side: interfaces for equipment control
N.B. As delivered from Alcatel–Lucent Factory, the NE’s:

– local IP address (associated to the F interface)
– and Ethernet TCP/IP address (associated to the Ethernet interface)
are both set at default value “10.0.1.2”.
Obviously, these values can be maintained only until the NE remains disconnected from the
TCP/IP network and from any other NE, and must be changed as soon as possible.
174 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.4.2 Local connection of the Craft Terminal to the NE
The CT can be locally connected to the NE through the Serial Port or through the Ethernet Network Port.
Only one connection can be active at a time.

Paragraphs 2–2.4.2.1 and 2–2.4.2.2 below describe how to switch from one to the other interface (this
setting is at PC side only).
N.B. This setting is necessary only in case you start the CT by Start ⇒ Alcatel 1320CT [see step
e )–2 ) on page 178].
In case you start the CT clicking the button Operational & Maintenance of the TCO Suite Main
Menu (see step e )–1 ) on page 178], you do not need to carry out this setting, because proper
setting is automatically set–up answering the question of Fig. 84. on page 178.
2–2.4.2.1 Connection through the Serial Port
Remind that, to connect the CT to the NE through the Serial Port, the Alcatel Virtual Network Card for
Lower Layers Software has to be installed on the PC (refer to para. 3–1.8 on page 327).
N.B. If the IP Address configured for the Alcatel Virtual Card has been changed after the 1320CT
Platform installation, it is necessary to perform a re–customization by entering the following
command:
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → SNMP Add–On Customization
N.B. If the connection through Ethernet Network Port has been activated, to activate again the
connection through the Serial Port enter the following command:
Start → Programs → Alcatel→ SNMPCT–K–ADD–ON v3.x.x → NE Connection → Serial Port
2–2.4.2.2 Connection through the Ethernet Network Port
1) Configure the Network Card on the CT as explained in the 1320CT Basic Craft Terminal
Operator’s Handbook.
2) Enter the NE and enable the Ethernet port on the NE (refer to para. 2–3.2.3 on page 201).
3) Quit the NE and close the Network Element Synthesis application.
4) Activate the CT Connection through the Ethernet Port by the following command:
Start→Programs→Alcatel→SNMPCT–K–ADD–ON v3.x.x→NE Connection→Ethernet Port
N.B. If the IP Address configured on the Ethernet port has been changed, it is necessary to perform
a re–customization by entering the following commands:
Start → Programs → Alcatel → CT–K– v3.x.x → Customization
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → NE Connection→Ethernet Port
Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → SNMP Add–On Customization
3DB 16142 CAAA Ed.01A–DRAFT 175 / 576

2–2.5 Craft Terminal: NE supervision, login, logoff and switch off


– NE management states below
– NE Login on page 177
– NE Logoff or switch off on page 184
– Closing the 1320CT application on page 184
2–2.5.1 NE management states
The elementary building blocks of any telecommunication network are called Network Elements (NEs).
The 9400AWY NE type is ULS.
When operating with the Craft Terminal or the TCO Suite, 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 ULS view level.
All information relevant to the management states are described in the 1320CT Basic Craft Terminal
Operator’s Handbook (see Tab. 78. on page 557).
The Network Element Synthesis views enable to get access to the views described in this section.
– NE supervision and login
The Network Element Synthesis view enables to work on local or remote NE ULS, selecting them
and activating Supervision and Login, as described in para.2–2.5.2 on page 177.
– NE logoff and switch off
In order to logoff the NE, or before disconnecting the F interface cable, or before switching off the
NE, close the NE JUSM window and stop the NE supervision as described in para.2–2.5.3 on page
184.
176 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.5.2 NE supervision and login
a) Summary
To access and login a 9400AWY NE from you PC for the use of the Craft Terminal functionalities:
• the CT–NE connection can be:

– physically and logically local, through the RS232 serial cable for its connection to the
equipment F interface
– physically remote but logically local through an ECT–equipment connection via the public
switched telephone network, as explained in Appendix B on page 541
– physically and logically local, through a cross–connect Ethernet cable for the local direct
– physically local but logically remote, by a normal Ethernet cable through a LAN for the
– physically and logically remote, by a connection between PC Ethernet port and the NE
through the RECT function or the TCP/IP network.
• you must have a UserName and password set
• in case of logically remote connection, you must know the NE’s TCP/IP address
b) Cable and network connections (if not yet done)
1) Local connection between the PC and the NE
N.B. This operation has to be done whenever you have to access the NE locally; it is highly
recommended when commissioning and maintenance tasks must be carried out.
For other operations, consider that any NE reachable through the TCP/IP network
[see point 3 ) below] can be accessed by the PC connected to the TCP/IP network
[see point 2 ) below]
Following cautions stated in point e ) on page 32, through the suitable cable connect the ECT
to the F interface or to the Ethernet interface of the MAIN unit (refer to Fig. 83. on page 174).
To activate on the CT the connection through the Serial Port or through the Ethernet Port refer
to para. 2–2.4.2 on page 175.
2) Connection of the PC to the TCP/IP network
N.B. Just from NE management point of view, this operation has to be done whenever:
– you have no local access to any NE;
– or, even though you have local access to a NE, other NEs (you want to access
in remote way) are not accessible from the local NE.
3) Connection of the NE to the TCP/IP network
N.B. Please take into account that this connection must not be done until the network
routing data of the NE have been correctly defined. This definition is carried out
during the Configuration Procedure described in chapter 3–2 on page 361.
If, in the following, you want to access the NE through the TCP/IP network (provided that it has
already inserted correctly inside it from both physical and logical points of view), you must know
the NE’s TCP/IP address.
3DB 16142 CAAA Ed.01A–DRAFT 177 / 576

c) Power on the PC and wait for its start–up (if not yet done)

d) Only in case of CT–NE connection via public switched telephone network:

set up the connection on the public switched telephone network, as described in para.B.6 on page

548
e) Craft Terminal start–up

There are two ways to start the CT; they are not equivalent (note):
(note) in case no NE is locally connected to the PC, these modes are equivalent (no CT–NE
connection set–up)
1) Preferred mode to start the CT to login a NE: click the button Operational & Maintenance
of the TCO Suite Main Menu (see Fig. 64. and Fig. 65. on page 155). Refer to para.2–2.2.4.4
on page 156 for possible additional details.
Notice that this choice in independent from the setting (at PC side) of the CT–NE local
connection on the Serial or Ethernet interface (explained in para.2–2.4.2 on page 175). This is
the reason for preferring this simpler modality to start the CT to login a NE.
– if LLMAN (Alcatel Lower Layers Manager) is available on user’s system, user is asked to
select between serial or Ethernet port connection by following screen:
Yes
Fig. 84. Choice of Serial or Ethernet interface for PC–NE physical connection
• in case of serial connection (YES answer), no other request is asked to user and
1320CT platform is automatically started with the related Serial port connection
customization;
• in case of Ethernet connection (NO answer), no other request is asked to user and
1320CT platform is automatically started with the related Ethernet port connection
customization;
– if LLMAN is not available on user’s system, the 1320CT will be run with the Ethernet
connection customization and the user will be asked the same “Direct”/”Remote” request
shown in Fig. 71. on page 162.
After a while, the “Network Element Synthesis” screen opens [step f ) on page 179].
2) Alternative (not preferred) mode: in Windows: Start ⇒ Alcatel 1320CT

With this modality, you must know in advance if the local connection of the Craft Terminal to
the NE is set (at PC side):
– on the Serial interface
– or on the Ethernet interface
and consequently switch to one another, according to needs, as explained in para.2–2.4.2 on
page 175.
After a while, the “Network Element Synthesis” screen opens [step f ) on page 179].
WARNING: In case you use the Serial interface and the “Network Element Synthesis” does
not open, read carefully para.2–2.2.7 on page 161 (Warning about interface
customization carried out by the Direct Connection)
N.B. Only in case of F–interface employment, for a correct operation, and only on some PCs
with Windows 2000 or XP, it is necessary to start the Lower Layers Manager (Start →
Programs → Alcatel → Lower Layers → Lower Layers Manager) before starting the ECT
Platform (Alcatel 1320CT).
178 / 576 3DB 16142 CAAA Ed.01A–DRAFT

f) Network Element Synthesis screen
There are two cases:

• the PC is locally connected to the NE; screen appears as follows:
Fig. 85. Network Element Synthesis screen (NE locally connected)
– the symbol indicates the NE–CT local connection by serial cable (F–interface). Such
symbol is not present if the connection has been established through the Ethernet
interface.
– the symbol “?” means they NE is not supervised.
Now:
– if you have to operate on the NE locally connected, proceed to step h ) on page 181.
– if you have to operate on a remote NE, proceed to step g ) on page 180.
• the PC is not locally connected to any NE; the screen (the first time you have launched 1320CT
after its installation) is as follows (empty map):
Fig. 86. Network Element Synthesis screen (empty map)
In this case you must create on this empty map the SNMP NE(s) you want to access, as
described in following step g ) .
3DB 16142 CAAA Ed.01A–DRAFT 179 / 576

g) SNMP NE creation

N.B. This is a simplified description. For complete instructions, please refer to the 1320CT

Basic Craft Terminal Operator’s Handbook, section “EML CONSTRUCTION”.

To create a SNMP NE in the Network Element Synthesis map:
• you must know the NE’s TCP/IP address,
• and you must be sure that the NE is reachable from your PC. To make this check, open the
Windows Command Prompt application and execute the command:
ping <space> –t <space> TCP/IP_address
Leave this command run some minutes, verifying the connection is and remains established
without interruptions, then close the command window.
• then, proceed as shown in Fig. 87. below, inserting in (2) the NE’s own TCP/IP address.
N.B. During the creation of the SNMP NE, if not set automatically, insert the number “161”
in the TCP/IP Port field.
(2)
(1)
(3)
Fig. 87. SNMP NE creation in the Network Element Synthesis map
After such creation, the empty map of previous Fig. 86. becomes populated as in Fig. 88. below
(the symbol “?” means the NE is not supervised).
Fig. 88. Network Element Synthesis screen after SNMP NE creation
• If necessary, create the other SNMP NEs you may need.
• At the end, save the map (Map ⇒ Save). In this way, when you start again 1320CT, you will find
the same NEs you have created in this phase.
• If you need to start supervision and, after, to login any NE present in the map, proceed to next
step h )
180 / 576 3DB 16142 CAAA Ed.01A–DRAFT

h) Start supervision on a selected Network Element
From a populated “Network Element Synthesis” map (e.g. Fig. 85. on page 179 and Fig. 88. above)
:
1) select the interested Network Element clicking once left mouse button on it;
2) while NE selected, with right mouse button choose Start Supervision and with left mouse
button execute it, clicking once (Fig. 89. below). In alternative, while NE selected, with left
mouse button choose Supervision ⇒ Start
Fig. 89. Start supervision

Wait until the symbol “?” becomes at first (under exploration) and then colored “•” (it
means “NE in supervised state” N.B.), as shown in Fig. 90. on page 181
N.B. In order to know the possible “color” meaning , refer to the:

• 1320CT Basic Craft Terminal Rel.3.x Operator’s Handbook:
– chapter “SOFTWARE INSTALLATION”
• paragraph “Craft Terminal Configuration”,
• sub–paragraph “Communication with NE”
Fig. 90. NE in supervised state
N.B. If you want to change the User Label of the NE (select it ⇒ Description ), take into
account that it must not include the following characters:
\ ? : * “ < >|.
3DB 16142 CAAA Ed.01A–DRAFT 181 / 576

WARNING: Due to a deep fading, the radio remote NE can be unreachable. In this condition in the
USM will appear the following message:

In this case, operate as follows:
• The JUSM must be closed.
In the NE will appear a broken icon and a red bullet.
• Wait for the automatic restarting of the Supervision (at the end of the fading conditions).
The icon in NE will become whole and the bullet will take the color relevant to the alarms (if any)
active in the NE.
• If the Supervision does not start, close and open again the CT.
• If the Supervision does not start, switch off and switch on the PC.
WARNING: When the supervision of a NE has been started don’t click on the name of the map.
This operation causes the lock of the CT and the CT must be closed and opened again.
182 / 576 3DB 16142 CAAA Ed.01A–DRAFT

i) Network Element login
From screen “Network Element Synthesis” with NE in supervised state (e.g. Fig. 90. on page 181):
1) select the interested Network Element (NE) clicking once right mouse button on it;
2) while NE selected, with right mouse button choose Show Equipment and with left mouse
button execute it, clicking once (Fig. 91. below). In alternative, while NE selected, with left
mouse button choose Supervision ⇒ Show Equipment
Fig. 91. Show Equipment
3) after a while, the Login screen appears (Fig. 92. below), that must be filled in with suitable
values.
Fig. 92. Login screen
At first installation time, one default Administrator user is available only, with (lower case):
• UserName= initial
• Password = initialing
Otherwise, use the Login information the Administrator has assigned you.
WARNING: The change of the password of this Administrator user is strongly suggested, to be done
at the end of all commissioning phases. Further this initial user, the Administrator is
allowed to create/delete users belonging to the predefined profiles.
For the Administrator to make such operations, please refer to para. 2–3.6 on page 218.
3DB 16142 CAAA Ed.01A–DRAFT 183 / 576

If the Login values are correct, NE data are loaded:

and, after a while, the 9400AWY Main view opens (Fig. 94. on page 185)
After the 9400AWY Main view has opened, all the available menus are introduced in para.2–2.6 on
page 185.
2–2.5.3 NE Logoff or switch off
Before disconnecting the F interface cable or before switching off the NE:
– close the NE JUSM window (Fig. 94. on page 185) clicking
– then, in the Network Element Synthesis Window (Fig. 93. below), stop the NE supervision as follows:
• select NE with mouse left button
• holding it selected, select Stop supervision with mouse right button. In alternative, while NE
selected, with left mouse button choose Supervision ⇒ Stop
Fig. 93. NE Stop Supervision
• NE will go to not supervised state.
2–2.5.4 Closing the 1320CT application
– Verify that all NEs in the Network Element Synthesis map are in not supervised state
– Now you can close the Network Element Synthesis Window (Fig. 93. below) clicking
184 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.6 9400AWY view organization

– Introduction below
– View Area on page 187

– Resource Tree Area on page 188
– Resource Detail Area on page 189
– Button Policy on page 189
2–2.6.1 Introduction
The 9400AWY view (see Fig. 94. below) contains the following fields, which provide the operator with the
information needed to manage the NE:
– Severity alarm synthesis,
– Domain alarm synthesis,
– Management status control panel,
– View title,
– View area,
– Message/state area.
The Menu bar , Main Tool bar and the View area contained in the same NE view permit to perform all
configuration and supervision operations and the display of the specific selected item.
The view organization is detailed in the 1320CT Basic Craft Terminal Operator Handbook to which refer
for the description.
N.B. Fig. 94. below shows the 9400AWY in 1+1 configuration.
Severity alarm synthesis Domain alarm synthesis

Menu
bar
Main tool
bar
View
area
Management state control panel

Fig. 94. 9400AWY Main view organization
N.B. For the meaning of the icons in the Severity alarm synthesis, Domain alarm synthesis and the
Management state control panel refer to Alarm synthesis indication para.4–5.8.2.1 on page
476.
3DB 16142 CAAA Ed.01A–DRAFT 185 / 576

2–2.6.2 Main tool bar

Besides navigation buttons, it contains some shortcut icons for specific tools or views (most of them are

accessible also through the Menu Bar).

Current Configuration view
previous next
screen Summary Block Diagram view
screen
not operative Quick Configuration by text file
Interactive Quick Configuration
Fig. 95. Main tool bar
N.B. previous screen and next screen buttons are enabled according to the context.
Shortcuts available starting from SWP 9400AWY IDU32 are:
– Interactive Quick Configuration: details in para.3–2.3.7 point a ) on page 375
– Quick Configuration by text file: details in para.3–2.3.7 point b ) on page 375
– Summary Block Diagram view: details in para.2–11.4 on page 286
– Current Configuration view: details in para.2–3.7 on page 222
186 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.6.3 View Area
The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g.
many windows placed one upon another. Each window is selectable (placing it on top of the others) with
a tab shown on the top.

Each panel represents a set of functions. The area consist of the following sets:
– Equipment
– External Points
– Line Interface
– Performance
– Radio
– Protection Schemes (in 1+1 configuration only)
– Loopback
– Sw Download
The following figure shows the tabbed panel organization.
Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ).
RESOURCE
TREE AREA
RESOURCE LIST AREA
RESOURCE DETAIL AREA
Fig. 96. View Areas
3DB 16142 CAAA Ed.01A–DRAFT 187 / 576

Each tab–panel (e.g. functionalities area) consists of four areas:

– Resource–Tree Area: displays all the available resources of the Radio NE.

– Resource–List Area: may be represented by: Tabular View (e.g., Line Interface Domain) or
Graphical View (e.g., Equipment Domain).
• Tabular View: displays a tabular representation of the selected resource. As default, no tabular
element is shown.
• Graphical View: displays a graphical representation of the selected resource. As default, no

tabular element is shown.
– Resource–Detail Area: displays detailed information of a selected item in the Resource List area.
As a default, no entry view is displayed as a consequence of the default behavior of the Resource
List area.
2–2.6.4 Resource Tree Area
The “Resource Area” displays all the available resources in a tree structure like the protocol stack
hierarchy. The below figure shows an example of the resource tree instance (for the Line Interface
functions):
Fig. 97. Resource tree area
188 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.6.4.1 Selection Criteria
Each tree node consists of two symbols. The first symbol indicates the state of the structure e.g., if the
symbol is ”+” the tree can be expanded to a lower level. The tree structure can be collapsed if the symbol
is “–“. Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphical
representation of the resource.
The user must select the resource by clicking with the mouse to carry out an action that depends on the
type of click.
Each resource listed above may be selected by using the mouse by a:
– Single left click;

– Double left click
Single left click:

By a single left click the resource is highlighted. This selection causes the activation of the
resource list area, e.g., every time the user selects a resource in the resource tree area the
corresponding Tabular or Graphical representation is displayed in the ”Resource list area” .
Double left click:

Using this type of selection on the items of the resource tree, the user can expand the tree
structure and activate the “Resource list area” displaying the same information described
above. When the tree node is expanded a double click will collapse the tree node showing the
same information in the “Resource list area”.
2–2.6.5 Resource Detail Area
This area displays the detailed information of the selected object in the Resource list area. It also provides
the types of operations available
2–2.6.6 Button Policy
The possible buttons for selection are the following:
– Apply this button activates the “modify”, but it does not close the window.
– Cancel this button closes the window without modifying the parameters displayed in the window.
– OK this button activates the modify and closes the window
– Close this button closes the window
– Help this button provides the help management for the functions of the supporting window.
Critical configuration choices generate a warning message for user confirmation before to be activated.
3DB 16142 CAAA Ed.01A–DRAFT 189 / 576

2–2.7 Introduction to the CT menu options


– Menu organization below

– Views menu introduction on page 191
– Configuration menu introduction on page 193
– Diagnosis menu introduction on page 193
– Supervision menu introduction on page 194
– Download menu introduction on page 194
2–2.7.1 Menu organization

The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph lists all menu options and then provides more details on the respective contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where they are detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
From Chapter 2–3 on page 195 details and operating information on all views are given.
In the menu bar, a number of permanent menu items are always displayed. Starting from the left, the
menus are:
– Permanent Menus
• Views (first column). See para.2–2.7.2 on page 191.
To navigate among the views and to set the TMN parameters.
• Configuration (second column). See para.2–2.7.3 on page 193.
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
• Diagnosis (third column). See para.2–2.7.4 on page 193.
To get information on the NE (alarms, performance monitoring, remote inventory).
• Supervision (fourth column). See para.2–2.7.5 on page 194.
To set the supervision states (i.e. Craft Terminal enabling).
• SW Download (fifth column). See para. 2–2.7.6 on page 194.
To manage the NE software (download, MIB management).
• Help (last column).
To activate the help on line.
The menu bar also comprises other menus, presented only when a specific option is selected.
– Other Menus
• Equipment
This menu is present only when the Equipment menu (selected in the View menu or in the
Equipment tab panel) is active. It allows to go back to the supporting equipment of the displayed
object.
190 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.7.2 Views menu introduction
The menu on the left side of the screen, allows to navigate among the views and to set some parameters,
by means of the following entries:

– Previous: Goes back to the previous screen of the application.
– Open Object: Not active.
– Open in New
Window: Not active.
– Duplicate View in
New Window: Not active.
– Equipment: Opens the Equipment view.

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

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

– Radio: Allows to manage all the functions relevant to the radio channels.
– Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.

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

3DB 16142 CAAA Ed.01A–DRAFT 191 / 576

N.B. It is possible to enter directly menus Equipment, External Points, Line Interface, Performance,
Radio, Protection Scheme, Loopback by clicking on the relevant tab panel above the view area.

Refer to Fig. 98. on page 192.

Tab panel
Fig. 98. Tab panels
192 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–2.7.3 Configuration menu introduction
This menu allows to set the general configuration of the NE and to show or modify some parameters, by
means of the following entries:

– NE Time: Displays and set the NE local time. See para. 2–3.1 on page 196.
– Network configuration: See para. 2–3.2 on page 197.
– Alarm Severities: Manages the Alarm Severity Assignment Profile.

See para. 2–3.3 on page 210.
– System setting: Allows the system configuration, providing the setting of all the parameters
for the NE setup. See para. 2–3.4 on page 215.
– Quick configuration: Allows a full system configuration through a guided procedure.

– Profiles management: Allows the CT user profile management.

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

Opens the following menu options:
• Alarm log
• Event log
• Software Trace log
– Current configuration
View: Displays the current configuration of the NE.
– Summary Block
Diagram View: Displays a global logical view (strictly related to the physical implementation)
highlighting a synthesis of all the alarms and statuses present in the system
(ODU+IDU).
– Abnormal
condition list: Displays the manually operations active in the NE.
3DB 16142 CAAA Ed.01A–DRAFT 193 / 576

2–2.7.5 Supervision menu introduction

This menu allows to set the supervision states of the NE, by means of the following entries (see chapter

2–8 on page 257) :

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

– MIB Management: Allows to perform backup and restore operations of the MIB.
– SW key: Displays the type of the key stored in the flash card.
2–2.7.6 Download menu introduction
This menu allows to manage the NE software, by means of the following entries (see chapter 2–13 on page
301) :
– Server Access
Configuration: Manages the configuration of the FTP server to be used for the software
download to the NE.
– Init SW download: Manages the software download to the NE.

– SW status: Shows and manages the status of the software packages installed in the NE
memory banks.
194 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3 CONFIGURATION
This chapter describes the following Configuration menus:

– NE Time on page 196
– Network Configuration on page 197
• Local Configuration on page 198
• NTP Configuration on page 199
• Ethernet Configuration on page 201
• IP Configuration on page 202
– IP static routing configuration on page 202
– OSPF Area configuration on page 206
– IP Address configuration of Point–To–Point Interfaces on page 208
• Routing information on page 209
– Alarm Severities on page 210
– System Settings on page 215
• NE Configuration on page 215
• Overhead on page 217
– Quick Configuration Procedure on page 218
– Profiles management on page 218
• Functional description on page 218
• Change Password procedure on page 220
• Users Management procedure on page 221
3DB 16142 CAAA Ed.01A–DRAFT 195 / 576

2–3.1 NE Time

The NE local time can be displayed and/or re–aligned to the OS time basis.

From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which you can set the local NE time.
Fig. 99. NE Time dialogue box
The NE Time dialogue box displays the current NE time and the current OS time.
To re–align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The NTP status field is a read–only screen, which shows the configuration regarding the Network Time
Protocol performed in the menu Configuration –> Network Configuration –> NTP Configuration.
The Refresh pushbutton causes the refresh of the screen.
196 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.2 Network Configuration
To get access the Network Configuration option select the Configuration pull down menu, as shown
in the following figure.

Fig. 100. Network Configuration menu
The Network Configuration allows to perform the following operations:
Local Configuration: defines the local NE addresses
NTP Configuration: allows to enable/disable the Network Time Protocol
Ethernet Configuration: defines the configuration parameters necessary to manage

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

which has been configured.
The options are described in next paragraphs.
3DB 16142 CAAA Ed.01A–DRAFT 197 / 576

2–3.2.1 Local Configuration

Select the Configuration pull down menu.

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

2–3.2.2 NTP Configuration
By selecting NTP Configuration the dialog–box in Fig. 102. opens, which allows to enable the Network
Time Protocol.
Fig. 102. NTP Configuration dialogue box
To enable the NTP put a tick in the check box of the Enabling NTP protocol field.
If the NTP has been enabled in the Main Server address field write the IP address of the Server, which
distributes the NTP and in the Spare Server address field write the IP address of the Spare Server, if any,
which will distribute the NTP in case of failure in the Main Server.
It is mandatory to define both the Main Server address and the Spare Server address.
In case a Spare Server is not available, fill its address field with the same
value of the Main Server.
To configure the setting click on Apply.
The Refresh pushbutton causes the refresh of the screen.
3DB 16142 CAAA Ed.01A–DRAFT 199 / 576

2–3.2.2.1 How to configure the NTP in a network

When the NTP is enabled, one of the NE must be MASTER and all the other NEs must be SLAVEs.

An example is shown in Fig. 103.

NE1
NE2
NE3
NE4
Fig. 103. Map
As example NE1 must be set as Master:
– enable the NTP protocol;

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

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


All the other NEs must be set as NE4.
200 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.2.3 Ethernet Configuration
Select the Configuration pull down menu.

Select the Network Configuration option and then, from the cascading menu, the Ethernet
Configuration option.
The dialogue box in Fig. 104. on page 201 opens, which allows to define the parameters necessary to
configure the Ethernet interface.
The following areas are present:
– IP Section which comprises:
• IP Address to be assigned to the N.E.

• IP Mask relevant to the IP address
• IP Routing Protocol default is “none” state. If “OSPF” choice is selected, the “Associated OSPF
Area “ must be set.
WARNING: please do never use the RIP choice present in the IP Routing Protocol field!
• OSPF Area pointer: if in “IP Routing Protocol” the OSPF protocol has been selected, it is
possible to create OSPF areas.
– Enable which comprises two selections to Enable or Disable the Ethernet interface.
Refresh button refresh the information written in the upper port.

Apply button performs a configuration change of the data.
Close button closes the dialog without changes of the data.
Fig. 104. Ethernet Configuration dialogue box
3DB 16142 CAAA Ed.01A–DRAFT 201 / 576

2–3.2.4 IP Configuration

Select the Configuration pull down menu. Select the Network Configuration and then from the

cascading menu, the IP Configuration option ( see Fig. 105. on page 202).

Fig. 105. IP configuration screen
2–3.2.4.1 IP static routing configuration
The dialog–box opens ( see Fig. 106. on page 203 ) and allows to configure the parameters for IP Static
Routing Configuration.
The following fields and data are present:
[1] IP Address: allows to define the IP address necessary to reach a

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

Fig. 106. IP static routing configuration screen
By pressing Create pushbutton the screen in Fig. 107. on page 204 opens.
In the Host or Network Address Choice field select:
– Host to address to a single IP address;
– Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select:
– Default Gateway IP Address for the Ethernet interface;
– Point to Point Interface Index for the NMS channels (NMS–RF, NMS–V11, NMS–G703)
WARNING: No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.
3DB 16142 CAAA Ed.01A–DRAFT 203 / 576

Fig. 107. Create Static routing
If in the screen of Fig. 107. above the Default Gateway IP Address check box has been selected, write
in the Default Gateway IP Address field below the relevant IP address.
If in screen in Fig. 107. above has been selected the Point To Point Interface Index check box, the
screen in Fig. 108. on page 205 opens.
N.B. It is also possible to define a Default Gateway Routing (refer to para.2–3.2.4.2 on page 205 for
details).
204 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 108. Point To Point Interface Choice
In this screen one of the 3 NMS channels (NMS–RF, NMS–V11, NMS–G703) can be selected.
2–3.2.4.2 Default Gateway Routing configuration
It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 107. on page 204
operate as follows:
a) select Network
b) in IP Address field, write 0.0.0.0
c) in IP Mask field, write 0.0.0.0
d) in Default Gateway IP Address field, write the required destination
e) click OK
3DB 16142 CAAA Ed.01A–DRAFT 205 / 576

2–3.2.4.3 OSPF Area configuration

The dialog–box opens ( see Fig. 109. on page 206 ) and allows to configure the parameters for OSPF

(Open Shortest Path First) Area Table Configuration.

– OSPF Area IP Address

– OSPF Area Stub
The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network)
in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
Fig. 109. OSPF Area configuration screen
WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0
WARNING: When the area is a Stub area, all interfaces inside the same Stub Area (NMS and
Ethernet) must be defined “Stub”.
206 / 576 3DB 16142 CAAA Ed.01A–DRAFT

By pressing Create pushbutton the screen in Fig. 110. below opens.
N.B. 3 areas max. can be created.

Fig. 110. Create New OSPF Area
In the screen write the IP address, the IP mask and select the flag (True/False).
3DB 16142 CAAA Ed.01A–DRAFT 207 / 576

2–3.2.4.4 IP Address configuration of Point–To–Point Interfaces

The dialog–box opens ( see Fig. 111. on page 208 ) and allows to Enable or Disable the three NMS

channels, which use the PPP protocol.

OK button is used to perform a configuration change of the data contained in the dialog–box and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Fig. 111. IP Address configuration of Point–To–Point Interfaces screen
208 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.2.5 Routing information
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the Routing information option.

The dialog–box in Fig. 112. on page 209 opens.
Fig. 112. Routing information screen
This screen is a read–only screen and displays the routing parameters currently active on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.
3DB 16142 CAAA Ed.01A–DRAFT 209 / 576

2–3.3 Alarm Severities

By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 113. on page

211 appears.

In this screen in the Profile Name field are listed the 4 default Alarm Severity Profiles:
– Profile “No Alarms”. With this profile all alarms are disabled.
– Profile “Primary Alarms”. This profile enables the emission of the primary alarms. General rules
used to define the alarms severity:
• MAJOR: the alarm affects the service (it is service affecting);
• MINOR or WARNING (according to the impact of the alarm): the alarm doesn’t affects the
service (with the exception of HighBER alarm, which MINOR alarm severity is defined, even if
it is service affecting).
– Profile “No Remote Alarms”. This profile enables the emission of the primary alarms plus EW and
LBER alarm. This profile uses the following rules to define the alarms severity:
• MAJOR: the alarm affects the service (it is service affecting);
• MINOR: the alarm is potentially service affecting but a protection has recovered the service;
• WARNING: the alarm cannot affect the service (independently from any protection).
– Profile “All Alarms”. This profile enables the emission of all the alarms (included AIS and RDI). This
profile uses the same severity of the “Primary alarm” profile, the only difference is that EW, LBER,
AIS and RDI alarms are emitted.
The rules used to define the alarm severity are the same of the “Primary alarm” profile.
N.B. In case of alarms affecting a protection different severities are used for SA and NSA. The same
severity is used both for SA and NSA in case of service independent alarms.
N.B. The rules used to define the profile alarms severity described above, are not applied to the
housekeeping alarms. In this case, in order to enhance the flexibility, a different severity is
assigned to each alarm profile (WAR, MIN and MAJ).
210 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 113. Alarm Severities Profile
In the screen of Fig. 113. on page 211 are available 2 buttons:
– Close: to close the screen.

– Clone: to create a new Alarm Severity Profile. To create a clone refer to para. 2–3.3.1 on page 212.
N.B. Only 2 new profiles can be created.
An Alarm Profile is the complete set of the equipment alarms with their severity in case of Service
Affecting situation and No Service Affecting situation.
Each alarm has its Service Affecting and No Service Affecting attribute, which can differ according to the
Alarm Severity Profile.
N.B. To some objects in the equipment (overhead alarm, input housekeeping alarm, tributaries etc.)
can be assigned an Alarm Profile.
To do this association:
– select the tab panel (Equipment, Line Interface, FSO etc.) in which is present the object
to be associated to a specific Alarm Severity Profile;
– select the object;
– select the Configuration menu in the relevant Resource Detail Area;
– select in the Alarm Profile field the Alarm Profile to be associated.
3DB 16142 CAAA Ed.01A–DRAFT 211 / 576

2–3.3.1 How to create a new Alarm Severity Profile

– Select in the screen of Fig. 113. on page 211 the Alarm Profile to be cloned.

– Click the Clone pushbutton.
– The screen of Fig. 114. on page 212 appears.
– Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 114. Name of a cloned alarm profile
– Select again the Alarm Severity option from the Configuration menu.
– Select the just created Alarm Profile (Link 1 in the example of Fig. 115. on page 212).
Fig. 115. Clone of an Alarm Severity Profile
212 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– In this screen are available 4 buttons:
•
Close: to close the screen without any change

• Rename: to change the name of the Alarm Severity Profile
• Modify: to modify the Alarm Severity Profile
• Delete: to delete the Alarm Severity Profile.
– Click on the Modify button.
– To modify the severity of an alarm click on the Service Affecting field click on the suitable alarm and
select a new severity (see Fig. 116. on page 213).
Fig. 116. Selection of a new severity in the Service Affecting field
3DB 16142 CAAA Ed.01A–DRAFT 213 / 576

– To modify the severity of an alarm click on the No Service Affecting field click on the suitable alarm
and select a new severity (see Fig. 117. on page 214).

Fig. 117. Selection of a new severity in the No Service Affecting field
– To save the changes in the Alarm Severity Profile click on Apply. (By clicking on Cancel you quit the
Alarm Severity Profile screen without any change) (see Fig. 117. on page 214).
214 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.4 System Settings
This menu allows the system configuration, providing the setting of all the parameters for the NE setup.
The main window provides 3 tabbed–panels, one for each type of function to be managed:
– NE configuration
– Overhead
WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of the
configuration the “Restart NE” must be performed (refer to para. 2–8.2 on page 258).
WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of
PSU24), to insert the correct type enter the System Settings menu → NE configuration
tab panel; select the correct type; click on Apply and then restart the EC by entering
menu Supervision and by activating command ”Restart NE”.
2–3.4.1 NE Configuration
The user can view and define the NE configuration by selecting the “NE Parameters” tabbed panel.
The window displayed in Fig. 118. on page 215 will appear.
The field “Type” contains all the allowed configurations supported for the NE. The operator choice will be
applied by selecting the related “Apply” button.
The “Structure” area displays the market, capacity and modulation and, if needed, the ability to change
it, according to NE market configured in the previous screen.
The field ”Market” contains the market type: ETSI or ANSI (refer to Tab. 65. on page 380). The operator
choice will be applied by clicking the related “Apply” button.
Fig. 118. System Settings: NE configuration
3DB 16142 CAAA Ed.01A–DRAFT 215 / 576

The information related to the modulation type is shown in the “Modulation” field. The possible values are
”4QAM” or ”16QAM”. The operator choice will be applied by clicking the related “Apply” button.

WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or vice–versa) the Tx

power (in case of operation with RTPC) and the ATPC range (in case of operation with
ATPC) of the new modulation scheme must be in the correct range (refer to para. 2–6.4
on page 245). If the value is out of range the relevant field in the RTPC & ATPC screen
appears empty (automatically is associated a default value, but this value is not displayed).
Fill the field with the suitable value.
The Capacity can be modified by selecting a different type according to Tab. 65. and then selecting the
”Apply” button to send the new value.
N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field the explicit
confirmation shown in Fig. 119. is requested.
Fig. 119. Confirmation message
N.B. Only one change can be performed in this screen.

When the user confirms the change in the “Type” or “Market” or “Capacity” or “Modulation” field
all the other fields are disabled. To perform another change close the screen and enter again.
N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field (for the “Modulation”
only for the remote NE configuration) at the completion of the operation the CT forces the JUSM
closing with the following warning message (see Fig. 120. ).
Fig. 120. USM closing warning message
The “Tributary Port Configuration” area is in the lower part of the window. The “Impedance” field allows
the operator to configure the impedance of the E1/DS1 tributary (unbalanced 75 ohm or balanced 120ohm
for E1 tributary; balanced 100 ohm for DS1 tributary).
The impedance value will be applied by clicking on the related ”Apply” button.
216 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.4.2 Overhead
The ”Overhead” tabbed panel identifies the parameters for the management of the phone number and
auxiliary interface (Fig. 121. on page 217).

Fig. 121. Overhead Configuration
The field ”Phone Number” in the ”Order Wire Configuration” area allows the operator to read and write
the station number associated to the Engineering Order Wire to be used in the selective call. Possible
values are: 10–99.
N.B. Number 00 is the value associated to the general call.
The parameter will be sent to NE by clicking on the related “Apply” button.
The field ”Type” in the ”Auxiliary Interface Configuration” area allows the operator to change the
interface of the auxiliary channels.
The parameter will be sent to NE by clicking on the related “Apply” button.
The field Alarm Profile allows to associate to the Overhead alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1 on page 212).
To associate a different Alarm Profile click on the selection button and make the selection among the
available Alarm Profiles.
N.B. the default associated Alarm Profile is the Primary Alarm profile.
3DB 16142 CAAA Ed.01A–DRAFT 217 / 576

2–3.5 Quick Configuration Procedure

This procedure allows a full system configuration through a guided process, based on a reduced set of

screens. The related windows will be displayed by a “Wizard Tool” according to a specific order.

For the procedure execution, please refer to para.3–2.3.6 on page 373.
2–3.6 Profiles management
2–3.6.1 Functional description
[1] Username and Password
An user is identified by a username and password with the following characteristics:
• Username length: the length must not be more than 20 characters.
• Password length: the length must not be less than six (6) characters under any circumstances
and must not be less than eight (8) characters for administrator user profile. Moreover the
password length must not be more than 20 characters.
• Password composition: the password must be composed of full ASCII characters set
(UPPER/lower case, numeric and special characters).
The CT provides User login procedures (with the Show Equipment action) with the username
displayed on the screen and the clear–text password not displayed on the screen. After 3 number
of consecutive unsuccessful NE login attempts, the CT interface closes the login procedure. To
access to the NE, a new Show Equipment action must be performed.
Each user is associated to a predefined profile.
[2] User number
Twenty–five (25) users at most can be created.
[3] User predefined profiles
The list of supported features for each user profile is shown clicking on Appendix Craft Terminal
Access Control in the Users Management help screen of Fig. 125. on page 221.
For each functionality on user profile: Full indicates that the related screen is visible both for SET
and GET operation; Read Only indicates that the related screen is visible, but only for GET
operations (to see the MIB objects); Not Supported indicates that the related screen is not visible.
The predefined profile are:
• Administrator (both for OS interface and CT/MibBrowser interface)

This Operator can do everything on the NE.
This Operator can manage security features (to add/remove users or to change own password
and of all users).
218 / 576 3DB 16142 CAAA Ed.01A–DRAFT

• Constructor (only for OS interface)
This Operator can do everything on the NE also to access to the Manager List by–passing the
RM checks, but for this Operator some administration functions are disabled: for example the
Constructor cannot add or remove operators, and cannot do backup and restore.
This user profile is related only to OS system and so not stored on MIB NE. To manage NE, the
suitable menu items are enabled/disabled according to tables that can be viewed clicking on
Appendix Craft Terminal Access Control in the Users Management help screen of
• Operator (both for OS interface and CT/MibBrowser interface)

This Operator has in charge the operation at network level, not at radio site.
This Operator cannot add or remove users, but can change her/his own user password.
This Operator cannot manage network configuration, only for NTP Configuration, due to
dangerous isolation of NE.
This Operator cannot either do quick configuration, or backup/restore, or restart NE. Also the
provisioning of equipment is not supported, as well the operations requiring the operator
presence on the radio site.
• craftPerson (only for CT/MibBrowser interface)

This Operator has in charge the installation and the maintenance at radio site.
This Operator can do everything on NE system, but cannot add or remove users. This Operator
can change only own user password.
• viewer (both for OS interface and CT/MibBrowser interface)

This Operator can only explore the NE.
This Operator cannot add or remove users. This Operator can change own user password
All user predefined profiles can be connected to NE by a F interface (local serial interface) or by a
remote interface.
[4] NE scratch behavior
At installation time (NE scratch), a default Administrator user is created with (lower case):
• UserName= initial
• Password = initialing
The change of the password of this Administrator user is strongly suggested.
Further this initial user, the Administrator is allowed to create/delete users belonging to the
predefined profiles. The manager is prohibited from creating a user with username that already
exists.
The Administrator is allowed also to change user passwords (own or of all user by administrator).
[5] Reset NE behavior
All the security information sets (username/password/profile for each user) are stored on NE
database (MIB data base). After the NE reset, these information sets are not lost and are recreated
as before the NE reset.
Complete on–line information is available in the Users Management help screen of Fig. 125. on page
221.
3DB 16142 CAAA Ed.01A–DRAFT 219 / 576

2–3.6.2 Change Password procedure

This procedure is available for all Operator Profiles, after the log–in (see para.2–2.5.2 on page 177)

1) Configuration ⇒ Profiles Management ⇒ Change Password
Fig. 122. Profile Management options
2) Following screen appears; fill it with old and new passwords, taking into account password
characteristics listed in point [1] on page 218. New password will be active at next login (after
having logged out).
Fig. 123. Changing Password screen
220 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–3.6.3 Users Management procedure
This procedure is available to users with the Administrator profile only.

1) Configuration ⇒ Profiles Management ⇒ Users Management (see Fig. 122. on page 220)
2) Following screen appears. Click on Help
Fig. 124. Users Management screen
3) Following screen appears. Click inside to explore matters and carry out the desired action.
Fig. 125. Users Management help screen
3DB 16142 CAAA Ed.01A–DRAFT 221 / 576

2–3.7 Current Configuration view

Clicking on the Current Configuration view icon of the Main tool bar (see Fig. 95. on page 186) the

following screen is opened:

Fig. 126. Current Configuration view screen
By File ⇒ Save As, screen content can be saved as text file
222 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–4 EQUIPMENT
This chapter describes the types of functions offered to the user for Equipment Management.
The equipment domain deals with the management of the NE as a whole and its physical components
(subrack, boards,..)
The main screen of the Equipment tab panel differs according to the configuration:
– Fig. 127. on page 224 for 1+0 configuration
– Fig. 128. on page 224 for 1+1 configuration.
In the Resource List Area is shown a graphical representation of the Equipment, which consists of one
IDU and one ODU in 1+0 configuration and two IDUs and two ODUs in 1+1 configuration.
The IDU consists of different boards according to the configuration: 8xE1/DS1, 16xE1/DS1, E3/DS3 with
or without the Ethernet ports.
A colored ball gives information on the status of the associated object (Equipment, ODU, IDU, IDU board).
The color differs according to the severity of the alarms:
– Green: no alarm
– White: indetermination alarm active (not operative)
– Cyan: warning alarm active
– Yellow: minor alarm active
– Brown: major alarm active
– Red: critical alarm active
3DB 16142 CAAA Ed.01A–DRAFT 223 / 576

Equipment Status
ODU
ODU Status
IDU
IDU Status
Fig. 127. 1+0 Equipment view
Equipment Status
ODU
Ch#
ODU 0
Ch#
1 ODU
Status
IDU/EXT Ch #1
IDU/MAIN Ch #0
IDU Status
Fig. 128. 1+1 Equipment view
224 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–4.1 IDU level
To enter the IDU level click on the IDU object in the Resource Tree Area or double click on the IDU image
in the Resource Detail Area.

2–4.1.1 1+0 configuration
The screen in Fig. 129. below will appear.
IDU Status
IDU
MAIN
BOARD
Status
Fig. 129. 1+0 IDU view
One IDU is present:
– IDU channel#1: the Main IDU.
The IDU channel#1 includes the IDU/Main Ch#1 object, which includes according to the configuration type
the following options:
– IDU/MAIN/DATA Ch#1 with the 2 Ethernet ports
– IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
– IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries interface.
3DB 16142 CAAA Ed.01A–DRAFT 225 / 576

2–4.1.2 1+1 configuration

The screen in Fig. 130. below will appear for the Ch#1 and the screen in Fig. 131. on page 227 will appear

for the Ch#0.

IDU Status
IDU
MAIN
BOARD
Status
Fig. 130. 1+1 IDU/MAIN Ch#1 view
226 / 576 3DB 16142 CAAA Ed.01A–DRAFT

IDU Status
IDU
Fig. 131. 1+1 IDU Ch#0 view
Two IDUs are present:
– IDU channel#1: the Main IDU
– IDU channel#0: the Extension IDU
The IDU channel#1 includes the IDU/Main Ch#1 object which includes according to the configuration type
– IDU/MAIN/DATA Ch#1 with the 2 Ethernet ports (this board receives the power supply from the Main
IDU only).
– IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
– IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries interface.
The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration type
– IDU/EXT/8xE1/DS1 Ch#0 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1
configuration
– IDU/EXT/1xE3/DS3 Ch#0 with the E3/DS3 tributaries interface.
3DB 16142 CAAA Ed.01A–DRAFT 227 / 576

2–4.1.3 Board level

To enter a board click on the object in the Resource Tree Area or double click on the board image in the

Resource Detail Area.

As example in Fig. 132. below is shown the screen of the MAIN IDU board.
BOARD Status
Fig. 132. Main board view
228 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–4.2 ODU level
To enter the ODU level click on the ODU object in the Resource Tree Area or double click on the ODU
image in the Resource Detail Area.

The screen in Fig. 133. below will appear.
Fig. 133. ODU view
3DB 16142 CAAA Ed.01A–DRAFT 229 / 576

2–4.3 Tab panels in the Resource Detail Area

2–4.3.1 Alarms

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

2–4.3.2 Configuration
The “User Label” field (Fig. 135. below) only display the label associated to the selected node in the tree.
The field Alarm Profile allows to associate to the object alarms a particular Alarm Profile: a default alarm
profile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1 on page 212). To
associate a different Alarm Profile click on the selection button and make the selection among the available
Alarm Profiles.
Fig. 135. Configuration tab panel for a selected object
2–4.3.3 Remote Inventory
The information about the unit can be read in the Remote Inventory panel in the Resource Detail Area
as the following window shows (Fig. 136. below):
Fig. 136. Remote Inventory tab panel for a selected object
3DB 16142 CAAA Ed.01A–DRAFT 231 / 576

232 / 576
2–5 LINE INTERFACE
This chapter describes the type of functions available for Line Interface Management.
The Line Interface domain deals with the management of the aggregate frame and tributary ports (line
side).
The Line Interface menu allows the user to manage the resources of the line interfaces: PDH tributary,
NMS channel and Ethernet port, if has been configured.
This domain view consists of the following areas (Fig. 137. below):
– Resource Tree Area: displays the tributary ports sorted by the channel number and the NMS
interfaces.
– Resource List Area: displays tabular information about the selected resource in the tree area.
– Resource Detail Area: displays, through tabbed windows, the selected object’ s properties in list
area. This area performs the available functions for involved resource.
Fig. 137. Line Interface View
In the Resource List Area is given the information related to the tributaries or to the NMS channels:
– Type Interface (E1/DS1 or E3/DS3, Ethernet, NMS 64 kbit/s channel)
– Port Number: the port for a given channel and type of port
– Channel Number: the number of a channel
– Rate/Modulation: the bit rate of the tributary
– Signal Mode: the type of frame (Unframed/Framed/Disabled)
To configure a line interface select the interface in the Resource Tree Area and configure the Configuration
tab panel in the Resource Detail Area.
N.B. In the Resource Tree Area below the Tributary PDH line are shown all the E1/DS1 tributaries
according to the capacity selected in the System Setting menu or in Quick Configuration menu.
3DB 16142 CAAA Ed.01A–DRAFT 233 / 576

2–5.1 Tab panels in the Resource Detail Area

2–5.1.1 Alarm

The fault management checks the current state of alarms related to the selected tributary.
It is provided by the alarm panel like the one explained in para. 2–4.3.1 on page 230.
WARNING: The GFP alarm (alarm present in the Ethernet data interface) if active is shown not in this
tab panel, but in the Alarm tab panel of the Radio menu.
2–5.1.2 Configuration
There are different tab panels according to the type of interface:
– PDH interface (para. 2–5.1.2.1 on page 234)

– NMS interface (para. 2–5.1.2.2 on page 239)
– Ethernet interface (para. 2–5.1.2.3 on page 239)
2–5.1.2.1 Tributaries PDH Configuration tab panel
2–5.1.2.1.1 ETSI Market
The window, shown in Fig. 138. below for E1 tributary and Fig. 139. below for E3 tributary, performs all
the available functions for a PDH tributary port.
Fig. 138. Line Interface View: E1 Tributary Port
Fig. 139. Line Interface View: E3 Tributary Port
In Fig. 138. on page 234 and Fig. 139. on page 234 the following fields are read–only fields:
234 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– Interface Type (E1, E3)
– Port Number: identifies the ports for a given channel and type of port
– Channel Number
The fields, which can be changed, are:
– Signal Mode
– Line RAI Insertion
– Radio RAI Insertion
– Alarm Profile
Signal Mode (for E1 tributary)
The possible values are:
– Framed for the framed received signal

– Unframed for the unframed received signal
– Disabled
The current state can be modified selecting a different signal mode value and then click on the ”Apply”
button to send the new value to NE.
WARNING: In case of the configuration with the two Ethernet ports some E1 ports must be at least
disabled in order to allow the transmission of the Ethernet data.
Refer to the following Table.
Capacity Number of disabled E1 tributaries

2xE1 1
4xE1 1
8xE1 1
16xE1 8
Signal Mode (for E3 tributary)
– Framed G.751 for the framed received signal

– Framed G.753 for the framed received signal (not applicable)
– Disabled
3DB 16142 CAAA Ed.01A–DRAFT 235 / 576

Line RAI Insertion (for E1 tributary only)

This feature is available for framed signals only.

This field refers to the insertion of the RAI signal in Tx side. The possible alternative values are:
– Forced: the RAI insertion is performed

– Enabled: the RAI insertion is possible.
Radio RAI Insertion (for E1 tributary only)
This feature is available for framed signals only.
This field refers to the insertion of the RAI signal in Rx side. The possible alternative values are:
– Forced: the RAI insertion is performed

– Enabled: the RAI insertion is possible.
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm
Alarm Profile.
N.B. the default associated Alarm Profile is the No Alarm profile.
236 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–5.1.2.1.2 ANSI Market
The window, shown in Fig. 140. below for DS1 tributary and Fig. 141. below for DS3 tributary, performs
all the available functions for a tributary port.

Fig. 140. Line Interface View: DS1 Tributary Port
Fig. 141. Line Interface View: DS3 Tributary Port
In Fig. 140. and Fig. 141. above the following fields are read–only fields:
– Interface Type (DS1, DS3)

– Port Number: identifies the ports for a given channel and type of port
– Channel Number
The fields, which can be changed, are:
– Signal Mode
– Line Coding (AMI/B8ZS : for DS1 tributary only)
– Line length (0–133, 133–266, 266–399, 399–533, 533–655 : for DS1 tributary only)
– Alarm Profile
Signal Mode (for DS1 tributary)
– Framed SF for the Super Framed received signal

– Framed ESF for the Extended Super Framed received signal
– Disabled
3DB 16142 CAAA Ed.01A–DRAFT 237 / 576

WARNING: In case of the configuration with the two Ethernet ports some tributary ports must be at
least disabled in order to allow the transmission of the Ethernet data.


Capacity Number of disabled DS1 tributaries
4xDS1 1
8xDS1 1
16xDS1 8
Signal Mode (for DS3 tributary)
– Framed for the framed received signal

– Disabled
Line Coding (for DS1 tributary only)
This field refers to the coding relevant to the tributary signal. The possible values are:
– B8ZS
– AMI
Line Length (for DS1 tributary only)
This field refers to the length of the connected line. The possible values are:
– 0–133
– 133–266
– 266–399
– 399–533
– 533–655
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm
Alarm Profile.
N.B. the default associated Alarm Profile is the No Alarm profile.
238 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–5.1.2.2 NMS interfaces Configuration tab panel
Fig. 142. Line Interface View: NMS interface
For the NMS 64 kbit/s channels only the Alarm Profile can be associated.
The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator in menu Configuration –> Alarm
Severities. To associate a different Alarm Profile click on the selection button and make the selection
among the available Alarm Profile.
N.B. The default associated Alarm Profile is the No Alarm profile.
2–5.1.2.3 Tributaries Data Configuration tab panel
The Ethernet interfaces can be configured according to two different modalities: manual (or default type)
mode (auto–negotiation is disabled) or automatic mode (auto–negotiation is enabled). In automatic mode
a mechanism of auto–sensing (the auto–negotiation) of the parameters involved is activated. These
parameters are negotiated with the remote Ethernet interface.
The following items resume the features supported:
– the rate (10 or 100 Mb/s) is always configurable independently of the modality (manual or automatic);
– the directionality is always full–duplex (no carrier control mechanism is implemented to use
the half–duplex mode);
– when the auto–negotiation process fails or when the auto–negotiation parameters are changed, the
auto–negotiation restart command has to be performed in order to have new configured parameters
effective.
3DB 16142 CAAA Ed.01A–DRAFT 239 / 576

1 – Configuration menu

Fig. 143. Line Interface View: Ethernet Port
In this menu the Ethernet port can be Enabled or Disabled and the Errored Frames can be discarded in
Tx side and in Rx side. To each Ethernet port can also be associated an Alarm Profile.
The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator in menu Configuration –> Alarm
Severities. To associate a different Alarm Profile click on the selection button and make the selection
among the available Alarm Profile.
WARNING: In case of the configuration with the two Ethernet ports some tributary ports must be at
least disabled in order to allow the transmission of the Ethernet data.
Market Capacity Number of disabled tributaries
2xE1 1
4xE1 1
ETSI
8xE1 1
16xE1 8
4xDS1 1
ANSI 8xDS1 1
16xDS1 8
N.B. The default associated Alarm Profile is the No Alarm profile.
To confirm the new configuration click on Apply.
240 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2 – Auto–negotiation
Fig. 144. Line Interface View: Ethernet Port auto–negotiation
In this menu the Auto–negotiation protocol regarding the Ethernet port can be Enabled or Disabled.
To confirm the new configuration click on Apply.
3DB 16142 CAAA Ed.01A–DRAFT 241 / 576

242 / 576
2–6 RADIO
The Radio domain view allows the user to manage the resources of the radio transmission channel.
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio ports
etc).
This domain view consists of the following areas (Fig. 145. on page 243):
– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource List Area: displays tabular information about the selected resource in tree area.
– Resource Detail Area: displays, through tabbed windows, the object’ s properties selected in the
list area. This area enables to execute the available functions for involved resource.
Fig. 145. Radio Domain View
Five tab panels are present in the Resource Detail Area:
– Alarms: shows the active alarms (refer to para. 2–6.1 on page 244)
– Configuration: configures some radio parameters (refer to para. 2–6.2 on page 244)
– Frequency: sets the Tx RF frequency (refer to para. 2–6.3 on page 245)
– RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (refer
to para. 2–6.4 on page 245)
– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–6.5 on page 248).
3DB 16142 CAAA Ed.01A–DRAFT 243 / 576

2–6.1 Alarm

The fault management allows to check the current state of alarms related to the selected object.

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

2–6.2 Configuration
The window shown in Fig. 146. on page 244 performs all the available functions for a Radio channel.
To define the involved port, first select the port/channel in the tabular view: this selection enables the
“Resource Detail list” to show the available functions for the single resource.
Fig. 146. Radio Configuration menu
2–6.2.1 Local or Remote Transmitter Mute
The information related to the transmitter status is shown in the “Tx Mute” field. To change the transmitter
status choose the desired value (ON for Tx Squelched and OFF for Tx not Squelched) and press the
related “Apply” button.
WARNING: The Tx Remote Mute automatically works (”on” and then “off”) only if performed on the
local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed,
the EC changes the channel in mono–directional way, in order to have the possibility to
send the command to remove the mute. If the Network Element has been restarted after
a MUTE, there is no more possibility to set–up the channel, because the remote address
is not known, and, in any case, to set–up the channel a bidirectional communication is
needed. The only way to remove the MUTE command is with local CT or from a remote
CT which can reach the Network Element through another supervisory interface.
2–6.2.2 ODU service kit
This field is a read–only field, which displays the state of the Portable Service Kit (connected or not to the
ODU).
2–6.2.3 Alarm Profile
The field Alarm Profile allows to associate a particular Alarm Profile to the object alarms: a default alarm
associate a different Alarm Profile click on the selection button and select among the available Alarm
Profile.
244 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–6.3 Frequency
The Frequency menu allows to read and, if necessary, to set the frequency parameters.
For operative information and relevant screens, refer to para.3–2.6.2.7 on page 412.
2–6.4 RTPC & ATPC
This menu (Fig. 147. below) allows to read and, if necessary, to set the Tx power parameters.
The shown information is related to the channel selected in the Resource Tabular View.
Static value of the Tx power

(30 dB range)
Dynamic value of the Tx power
ATPC Rx Threshold
(20 dB range)
Fig. 147. Rtpc & Atpc
WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or vice–versa) the Tx
power (in case of operation with RTPC) and the ATPC range (in case of operation with
ATPC) of the new modulation scheme must be in the correct range. If the value is out of
range the relevant field in the RTPC & ATPC screen appears empty (automatically is
associated a default value, but this value is not displayed).
Fill the field with the suitable value.
3DB 16142 CAAA Ed.01A–DRAFT 245 / 576

2–6.4.1 ATPC

The ATPC can be Enabled or Disabled.

The new value will be applied when the ”Apply” button is pressed. If the ATPC has been enabled, the
ATPC Range and ATPC Rx Threshold fields must be filled.
WARNING: In 1+1 Configuration (HST or FD) the ATPC information, sent back from the Rx side to Tx
side, is the information relevant to the channel (protecting or protected) currently active
in the EPS protection scheme. The two transmitters are, therefore, driven by the same
ATPC control signal.
[1] ATPC Range
The Min Value and Max Value, for Tx Range in the ATPC management, are shown in the Atpc
Range area. The min and max level can be changed by writing the new value in the field.
When the Apply button is pressed the new values will be applied.
[2] ATPC Rx Threshold
The value of the power low threshold can be changed by writing the new value in the field.
When the Apply button is pressed the new values will be applied.
WARNING: During the reconfiguration phase or during the activation of a new software the alarm
“ATPC loop” is active.
It is recommended to use the following Tab. 56. (for ETSI) and Tab. 57. (for ANSI) in order
to set the ATPC threshold. The ATPC shape is calculated using the following max capacity:
• E3 for ETSI
• DS3 for ANSI
Tab. 56. ATPC Range Rx Threshold for ETSI

TH 7/8 GHz 13 GHz 15 GHz 18 GHz 23 GHz 25 GHz 28 GHz 38 GHz
Min
–73 –74 –74 –72 –72 –71 –71 –70
4 Value
QAM Max
–60 –60 –60 –60 –55 –50 –50 –50
Value
Min
–69 –70 –70 –68 –68 –67 –67 –66
16 Value
QAM Max
–60 –60 –60 –60 –55 –50 –50 –50
Value
246 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Tab. 57. ATPC Range Rx Threshold for ANSI
15 18 23 38
TH
GHz GHz GHz GHz

Min
–72 –70 –70 –66
4 Value
QAM Max
–60 –60 –55 –50
Value
Min
–68 –66 –66 –62
16 Value
QAM Max
–60 –59 –55 –50
Value
The applied rule is:
ATPC Rx threshold setting

Frequency Band
Min Value Max Value
7/8, 13, 15 & 18 GHz PRxth + 8 dB –60 dBm
23 GHz PRxth + 8 dB –55 dBm
25 & 38 GHz PRxth + 8 dB –50 dBm
PRxth: Received power level correspondent to BER 10–6 according to modulation scheme,
payload and ETSI/FCC standard
2–6.4.2 RTPC
[1] Nominal Power
The Nominal Value field in the “RTPC” area is a read–only field and shows the nominal value of the
transmitted power (expressed in dBm).
[2] Tx Power
The Tx Power field in the RTPC area shows the current value of Tx power (expressed in dBm), when
the ATPC is disabled. In this case, it is possible to modify this value ERROR FREE in ATPC Range
(Pnom –20 dB) with 2 dB max step allowed, by writing the new value and by pressing the related
Apply button
N.B. During the command setting the CT is frozen. Waiting time: < 15’.
The new value must be within the allowed transmitted power range. This range is shown in the Power
Value label of RTPC area.
If the ATPC is enabled, the Tx power value cannot be modified.
3DB 16142 CAAA Ed.01A–DRAFT 247 / 576

2–6.5 Power Measurement

The Power Measurements capability is performed through the “Power Meas” tabbed panel in the resource

detail view (Fig. 148. below).

Fig. 148. Power Measurements
The Measurement screen allows the operator to set initial parameters for the required measurement.
“Measurement interval” fields allow the operator to set the time–duration of the measurement. The
default is Days: 7, Hours: 0, Minutes: 0. A 7–day measurement interval is also the maximum allowed
interval.
“Sample time” field is the period between two consecutive measurement samples. The choice is among
2, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and name for this file is displayed to the
operator. The file is stored in the ALCATEL/CT–Kv3.0.1 directory.
N.B. The file name must not include the following characters: \ ? : * “ < > |.
The log file contains the sample value and records the measurement up to a maximum dimension ( 7 days
for a 2 s sample time).
By clicking on the ”Start“ button the screen “ Power Measurement Graphic “ appears (see Fig. 148. on
page 248).
The Power Measurement Graphic is available only if the CT is connected to the NE.
248 / 576 3DB 16142 CAAA Ed.01A–DRAFT

The screen in Fig. 149. shows the Tx and Rx measurements related to the local NE.
Through this screen the operator can see, in real time, the power transmitted by the local and remote
transmitter (Tx) and the power received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the
Rx curves (local and remote). Note that the colors represent the linked end–point of the two NE; for
example, if the local TX is blue, the remote receiver will also have the same color.
The top of the screen offers all the characteristics present in the current measurement:
– Radio port: gives the symbolic name associated to the radio channel being analyzed;
– Sample time: indicates the frequency used to send the measurement requests to NE;
– Start time: is the first request time;
– Stop time: is the interval time selected in the previous parameters window, added to the start time;
– Time: is the current response time;
– Log File: is the complete pathname of the file where the received values are stored.
Fig. 149. Power Measurement Graphic
By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 149. on
page 249), a new table appears (Fig. 150. on page 250); this table shows the following relevant values
of the received and transmitted power:
– Tx Local End
• max TX local value and date when this value was received for the first time.
• min. TX local value and its current date when this value was received for the first time.
• current TX local value and its current date.
3DB 16142 CAAA Ed.01A–DRAFT 249 / 576

– Tx Far End
• max TX remote value and date when this value was received for the first time.

• min. TX remote value and its current date when this value was received for the first time.

•

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

– PTx = Real Value ± 3dB
– PRx = Real Value ± 5dB
Fig. 150. Power Meas Details
WARNING:
– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HST Configuration the
transmitter is in standby).
– If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field
the information in dBm is –99, probably the supervision has been lost. The confirmation of the loss
of the supervision is given by a broken red icon in Network Element Synthesis screen.
250 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–6.5.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button. The directory of the CT automatically opens
to navigate and get the power measurement file.

N.B. as default, the measurement files are stored in the ALCATEL/CT–Kv3.0.1 directory and have
extension .txt.
Fig. 151. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 148. on page 248 to open the file.
Fig. 152. Example of “Power Measurement File Reading“
The button in the lower part of the window allow to flow the graph within the measurement interval.
Select the .txt file and click with the mouse right push–button to open .txt file with a text editor (e.g.
WordPad) and to see the power information in tabular mode (see Fig. 153. on page 252).
3DB 16142 CAAA Ed.01A–DRAFT 251 / 576

252 / 576
Fig. 153. Example of Power Measurement File Reading (with WordPad)

2–7 EXTERNAL POINTS
This chapter describes the types of functions offered to the user for External Points Management (please
refer to para.1–3.5.1 on page 81 for physical implementation).

There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Fig. 154. below, the tree will be expanded according to the
equipment configuration.
A single left click selection of a tree element causes the activation of the corresponding Tabular
representation displayed in the ”Resource list area”. A click on a row in the Resource list area opens the
Configuration menu in the Resource Detail Area. An example of this mechanism is displayed in the
Fig. 154. below.
2–7.1 Input External Points
An input external point is described by the following parameters (Fig. 154. below):
– Id: identification number

– UserLabel: associates a user–friendly name to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened)
– External State: describes the state (on /off)
– Alarm Profile: describes the associated Alarm Profile
The lower part provides the possible parameters, which can be modified; after a row selection, the user
can modify the User Label, the Polarity and can associate a different Alarm Profile by clicking on the
Selection button.
The operator choices will be sent to NE after selecting the “Apply” button.
Fig. 154. Input External Point View
3DB 16142 CAAA Ed.01A–DRAFT 253 / 576

2–7.2 Output External Points

Seven output external points are available:

The first four external points (CPO#1, 2, 3, 4) (Fig. 155. below) are described by the following
parameters:
– UserLabel: a user–friendly name can be associated to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
– Criteria: Manual or Automatic. The output can be activated manually by the CT by selecting Manual
(Fig. 155. below) or automatically by selecting Automatic (Fig. 156. on page 255). In this case a
new field appears (Event) in which it is possible to select the alarm, the generation of which will cause
the activation of the external point output.
– External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The operator choices will be sent to NE by clicking on the “Apply” button.
Fig. 155. Output External Points: CP01 ... CP04 (Manual activation)
254 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 156. Output External Points: CP01 ... CP04 (Automatic activation)
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 157. on page 256)
are described by the following parameters:
– UserLabel: a user–friendly name can be associated to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
N.B. These three output external points are automatically activated when the relevant equipment
summarizing alarm is active.
The operator choices will be sent to NE by clicking on the “Apply” button.
3DB 16142 CAAA Ed.01A–DRAFT 255 / 576

256 / 576
Fig. 157. Output External Points View: FAIL IDU, FAIL ODU

2–8 SUPERVISION
2–8.1 Access state (allow or inhibit NE Craft access)

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

2–8.1.2 Switching from the Craft Terminal access state back to the OS access state

Select the Supervision pull down menu. Then from the Access State cascading menu select the OS

option.

From the confirmation dialogue box that opens, you can confirm or cancel the ”OS access” operation.
The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view indicates whether the NE is
managed by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the
NE. When the communication with the NE is lost, the OS automatically recovers the
communication and forces the state existing before the loss of communication (therefore, Craft
Terminal access can be denied or granted).
2–8.2 Restart NE
The RESTART operation is a software reset and can be executed in normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
Fig. 159. Restart NE call
The following dialogue box opens.
Fig. 160. Restart NE confirmation
Click the OK button to confirm the restart N.E. operation
Click the Cancel button to abort the restart N.E. operation.
WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset
push–button) the LLM icon is frozen and the supervision of the local NE and the remote
NE is lost.
258 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–8.3 MIB Management
This menu (Fig. 161. below) refers to the management of the MIB (Management Information Base). The
MIB includes all the system configuration data, except the routing configuration data:
1. Local configuration ⇒ System’s local address
2. NTP server configuration
3. Interface configuration ⇒ NMS configuration

⇒ Ethernet configuration
4. IP configuration ⇒ IP Static Routing configuration

⇒ OSPF Area configuration
⇒ IP Address configuration of point to point configuration
Fig. 161. MIB Management
The routing configuration data are NOT stored into the MIB file, because considered unique to a particular
system in a network and are NOT meant to be reproduced on other systems in the same network, because
will cause conflicts in the supervision network centre.
3DB 16142 CAAA Ed.01A–DRAFT 259 / 576

2–8.3.1 Backup

This menu (Fig. 162. below) allows to save on the CT the NE configuration. To backup the configuration

write the filename in the Backup field (Lower part) and press Confirm Backup.

WARNING: The backup file name must not include the following characters: space, &, /.
Fig. 162. Backup screen
Confirm the backup operation to start the operation.
In the upper part appears the list of the previously created backups.
By pressing Refresh the list is updated with the insertion of the just created backup.
260 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–8.3.2 Restore
This menu (Fig. 163. below) allows to download to the NE a previously created backup.
Fig. 163. Restore screen
Select one of the backups to be downloaded in the upper part and press Confirm Restore.
(By pressing the Reset push–button the previous selection is cancelled and a new selection can be made).
Confirm the restore operation to start the operation.
To activate the new configuration enter command MIB Management ––> Activate.
2–8.3.3 Activate
This command (Fig. 164. below) allows to activate the configuration just downloaded with the restore.
Fig. 164. Activate command
3DB 16142 CAAA Ed.01A–DRAFT 261 / 576

2–8.3.4 Remove file

This menu allows to remove from the list of the backups one particular backup.

To remove a backup select the backup file in the upper part and press Confirm Remove.
Confirm the operation to start the operation.
By pressing Refresh the list of backups in the upper part of the screen is updated.
2–8.4 SW key
From the Supervision cascading menu, select the SW key option.
In this screen the type of the key (stored in the flash card installed in the Main IDU unit) is shown.
Fig. 165. SW key screen
262 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–9 PROTECTION SCHEMES
This domain is present in 1+1 configuration only.

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

– Radio protection: RPS Hitless Switch in Rx side
– HST protection: Hot Stand–by protection
3DB 16142 CAAA Ed.01A–DRAFT 263 / 576

To see the current position of the switches enter the menu Diagnosis –> Summary Block Diagram View
(refer to para. 2–11.4 on page 286).

– Mux/Demux protection corresponds to the Switch Tx and the Rx output switch in Fig. 191. on page

288 or Fig. 193. on page 289
– The Radio protection corresponds to the Switch RPS HS in Fig. 191. on page 288 or Fig. 193. on
page 289
– The HST protection is implemented in the ODU: one Transmitter is connected to the antenna
(active), the other transmitter is in stand–by. Refer to Fig. 191. on page 288. The HST protection
is available only if the HST configuration has been selected.
2–9.1 Mux/Demux Protection Management
The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.
The following window (Fig. 167. below) allows a complete view of all NE resource involved in the EPS
protection:
– Schema Parameters
– Channels Parameters
To read the
correct
indication
on the switch
status press
here to
refresh the
screen
Fig. 167. Mux Protection
264 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–9.1.1 Schema Parameters
The window “Schema Parameters” displays the parameters that can be modify.
The Schema parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported type
is: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare).
– Operation type: it defines if automatic restoration from protecting to protected channel is allowed
(revertive mode) or inhibited (not revertive mode).
The operator choice for “Operation Type” will be applied by clicking on “Apply” button.
2–9.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 168. below) or on the
Main #1 element (Fig. 169. on page 266).
Fig. 168. Mux Protection Switch (Spare #0)
3DB 16142 CAAA Ed.01A–DRAFT 265 / 576

Fig. 169. Mux Protection Switch (Main #1)
The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced
and Manual.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),
independently of the possible active alarms. This command activates signaling ABN.
WARNING: the EPS Lockout command is not error free, even if it is raised when traffic is not on the
spare channel.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of the switch depends on the commands
generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic
switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does not activate signaling ABN.
Tab. 58. Command priority list

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
N.B. to release a previously activated command select None and click on Apply.
266 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–9.2 Radio Protection Management
The Radio Protection Management is performed by selecting the Radio Protection element tree.
The following window (Fig. 170. below) allows a complete view of all NE resource involved in a RPS
protection:
– Rx Static Delay
To read the
correct
indication
on the switch
status press
here to
refresh the
screen
Fig. 170. Radio Protection View
3DB 16142 CAAA Ed.01A–DRAFT 267 / 576

2–9.2.1 Rx Static Delay

Fig. 171. Rx Static Delay menu
The Rx Static Delay must be compensated during the installation.
Two compensating modes are possible:
– Automatic
– Manual
The two modes are alternative.
To activate the Automatic mode click on the Align push–button (the compensation procedure is
automatically done).
To activate the Manual mode:
[1] click on the Start push–button;
[2] write the values in the Channel 0/1 fields (N.B.);
[3] click on the Apply push–button to send the value to the NE.
N.B. Write in one field the suitable value (in range 0–31) and in the other field write 0.
268 / 576 3DB 16142 CAAA Ed.01A–DRAFT

The Schema Parameters are:
– ”Protection Type” field: defines the protection schema architecture: 1+1 Hitless;
– ”Operation Type” field: the possible values are revertive (automatic restoration allowed) or
notRevertive (automatic restoration Inhibited).
2–9.2.3 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 172. below) or on the
Main #1 element (Fig. 173. on page 270).
Fig. 172. Radio Protection Switch (Spare #0)
3DB 16142 CAAA Ed.01A–DRAFT 269 / 576

Fig. 173. Radio Protection Switch (Main #1)
and Manual.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),
independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
270 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–9.3 HST Transmission Protection Management
The Transmission Protection Management is performed selecting Transmission Protection element tree.
The following windows (Fig. 174. below) allows a complete view of all NE resource involved in a TPS
protection:
To read the
correct
indication
on the switch
status,
press here
to refresh the
screen
Fig. 174. Transmission Protection View
The Schema parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported type
are: 1+1 (onePlusOne) ,e.g. a working element is protected by one protecting unit.
– Operation type: it defines if automatic restoration from protecting to protected unit is allowed
(revertive mode) or inhibited (not revertive mode).
The operator choice for “Operation Type” will be applied clicking on “Apply” button.
3DB 16142 CAAA Ed.01A–DRAFT 271 / 576

2–9.3.2 Commands

To enter the Commands menu click on the Spare #0 element (Fig. 175. below) or on the Main #1 element

(Fig. 176. below) in the Tree view.

Fig. 175. Tx Protection Commands (Spare #0)
Fig. 176. Tx Protection Commands (Main #1)
272 / 576 3DB 16142 CAAA Ed.01A–DRAFT

and Manual.
Lockout has higher priority than Forced: the activation connects to the antenna Transmitter 1 (default
transmitter), independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command connects to the
antenna Transmitter 0, independently of the possible active alarms. This command activates signaling
ABN.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
3DB 16142 CAAA Ed.01A–DRAFT 273 / 576

274 / 576
2–10 LOOPBACKS
The functions described in this section allow to perform the test operations.
This domain view consists of the following areas:
– Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by
number.
– Resource List Area: displays tabular information about the loopback supported by the resource
selected in tree area.
– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enables to perform the available functions for involved resource.
3DB 16142 CAAA Ed.01A–DRAFT 275 / 576

2–10.1 Available Loopbacks

2–10.1.1 1+0 Loopbacks

N.B. The loopbacks can be activated on the local NE only.
N.B. The DATA block in Fig. 177. is present with the Ethernet port option only.
CT
IDU ODU ODU IDU
DATA DATA
MUX/ MODEM RF RF MODEM MUX/
DEMUX DEMUX
TRIB TRIB
2 4 5 6 3
1
Fig. 177. 1+0 available loopbacks
Tab. 61. 1+0 loopbacks
Loop- CT selection in
Ref. to Loopback
No. back the Resource Location Note
Fig. type
name Tree Area
E1/DS1
1 Port#xx or Tributaries Fig. 180. Near End External line Input loopback at tributary level.
E3/DS3
E1/DS1 Loopback toward the remote

2 Port#xx or Tributaries Fig. 180. Near End Internal station at tributary level.
E3/DS3 Not available.
E1/DS1
Loopback in the remote station
3 Port#xx or Tributaries Fig. 180. Far End Internal
at tributary level.
E3/DS3
Loopback at the IDU output at

4 IDU cable Channel 1 Fig. 180. Near End External line
aggregate level.
ODU Loopback at the ODU input at

5 Channel 1 Fig. 180. Near End External line
cable aggregate level.
RF local loopback.
6 RF Channel 1 Fig. 180. Near End External line
(Note 1)
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration)
276 / 576 3DB 16142 CAAA Ed.01A–DRAFT


Fig. 178. Channel 1 Loopback View
Fig. 179. Tributaries Loopback View
277 / 576
In the Resource List Area are listed all the loopbacks which can be performed.

In this area the following information is given:

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

(External CABLE port
Line) (RF
loop)
2 Channel
(External Line)
Fig. 180. 1+0 Loopback types
278 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–10.1.2 1+1 Loopbacks
N.B. The loopbacks can be activated on the local NE only.

N.B. The DATA block in Fig. 181. is present with the Ethernet port option only.
CT
IDU ODU ODU IDU
DATA DATA
MUX/ MODEM RF RF MODEM MUX/
DEMUX DEMUX
TRIB TRIB
2 4 5 6 3
1
Fig. 181. 1+1 available loopbacks
Tab. 62. 1+1 loopbacks
Loop- CT selection in
Ref. to Loopback
No. back the Resource Location Note
Fig. type
name Tree Area
E1/DS1
1 Port#xx or Tributaries Fig. 184. Near End External line Input loopback at tributary level.
E3/DS3
E1/DS1 Loopback toward the remote

2 Port#xx or Tributaries Fig. 184. Near End Internal station at tributary level.
E3/DS3 Not available.
E1/DS1
Loopback in the remote station
3 Port#xx or Tributaries Fig. 184. Far End Internal
at tributary level.
E3/DS3
Loopback at the IDU output at

4 IDU cable Channel 0 or 1 Fig. 184. Near End External line
aggregate level.
ODU Loopback at the ODU input at

5 Channel 0 or 1 Fig. 184. Near End External line
cable aggregate level.
RF local loopback.
6 RF Channel 0 or 1 Fig. 184. Near End External line
(Note 1)
Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration).
3DB 16142 CAAA Ed.01A–DRAFT 279 / 576

280 / 576
Fig. 182. Channel 1 Loopback View
Fig. 183. Tributaries Loopback View

In the Resource List Area are listed all the loopbacks which can be performed.
In this area the following information is given:

– Channel: the number of the channel (channel 1 only)
– Type Interface: the type of interface in which a loopback can be performed.
– Location: the station in which the loopback is performed (Near End/Far End)
– Type: the type of the loopback (Internal/Internal IF/External Line)
– Modality: the type of the loopback (Loop and Continue only)
– Activation: the activation status of a loopback (Active/Not Active)
In Fig. 184. below is given the association of all the possible loopbacks and their positions in the block
diagram of the equipment provided by the Summary Block Diagram View option, available in the
Diagnosis menu.
4 IDU Radio
5 ODU 6 port
CABLE CABLE
(RF loop)
1 Tributaries
(External Line)
2
Channel
(External Line)
Fig. 184. 1+1 Loopback types
3DB 16142 CAAA Ed.01A–DRAFT 281 / 576

2–10.2 How to activate a loopback

N.B. For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to the

related Channel; for the Tributaries loopbacks must only be forced to the radio switch to Channel

0 or lockout to Channel 1.
To activate a loopback:
[1] Select the suitable loopback to be activated by clicking on the relevant object in the Resource Tree
Area or by selecting the relevant row in the Resource List Area.
[2] The screen in Fig. 185. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 185. Loopback activation
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the relevant
loopback will change from Not Active to Active).
WARNING:
When the Loopback commands start the Craft Terminal is not “frozen”. Before to set another command
is recommended to wait 120 to 160 seconds minimum.
282 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–10.3 How to remove a loopback
To deactivate loopbacks use the following steps:

[1] Select the suitable loopback to be removed by clicking on the relevant object in the Resource Tree
Area or by selecting the relevant row in the Resource List Area.
[2] The screen in Fig. 186. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 186. Loopback removing
[3] Select Not Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the
relevant loopback will change from Active to Not Active).
WARNING:
When the Loopback commands start the Craft Terminal is not “frozen”. Before to set another command
is recommended to wait 10 to 25 seconds.
3DB 16142 CAAA Ed.01A–DRAFT 283 / 576

284 / 576
2–11 DIAGNOSIS
The options available in the Diagnosis menu are shown in Fig. 187.
Fig. 187. Diagnosis menu
2–11.1 Log Browsing
In the Diagnosis pull–down menu, select the Log Browsing option.
The proposed options:
– Select the Alarm Log option to access the Alarm Log file.
The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.
Refer to the “ELB Operator’s Handbook”.
– Select the Event Log option to access the Event Log file.
The Event Log windows opens, permitting to analyze all the events stored in the NE.
Refer to the “ELB Operator’s Handbook”.
– Software Trace Log option is reserved to the Alcatel–Lucent technicians.
2–11.2 Remote Inventory
This screen is a read–only screen, which shows all the information on the equipment.
3DB 16142 CAAA Ed.01A–DRAFT 285 / 576

2–11.3 Abnormal Condition List

The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions (i.e.

the manual operations) currently active in the NE.

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

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

– 1+0 with or without the Ethernet ports (see Fig. 188. on page 287, Fig. 189. on page 287)
– 1+1 HST with or without the Ethernet ports (see Fig. 190. on page 288, Fig. 191. on page 288)
– 1+1 FD with or without the Ethernet ports (see Fig. 192. on page 289, Fig. 193. on page 289)
In detail, it is possible to:
– navigate from Alarm indicator to related “Alarm Synthesis”;

– navigate from External Point indicator to “External Point” view;
– navigate from Switch indicator to related “Protection Scheme” view;
– navigate from Loopback indicator to specific “Loopback” view; for example, by clicking on (L)
indicator of main board (Ch#1) the operator can navigate to loopback view for PDH tributaries;
– navigate from Performance indicator to specific “Performance” view; for example, by clicking on
(P) indicator (line side) the operator can navigate to “Current Data” view;
– navigate from ODU box to the ”radio view” with automatic selection of the related channel.
To refresh the screen press the Refresh button.
N.B.
• Loopback indicator: yellow letter L means active loop.
• Performance indicator: yellow letter P means active performance.
N.B. In the 1+1 configuration the current position of the switches is also shown.
286 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 188. Summary Block Diagram View: 1+0 without Ethernet ports
Fig. 189. Summary Block Diagram View: 1+0 with Ethernet ports
3DB 16142 CAAA Ed.01A–DRAFT 287 / 576

Fig. 190. Summary Block Diagram View: 1+1 HST without Ethernet ports
Fig. 191. Summary Block Diagram View: 1+1 HST with Ethernet ports
288 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 192. Summary Block Diagram View: 1+1 FD without Ethernet ports
Fig. 193. Summary Block Diagram View: 1+1 FD with Ethernet ports
3DB 16142 CAAA Ed.01A–DRAFT 289 / 576

By pressing the Refresh button the refresh of the screen takes place (active loopback and performance
and position of the switch).

2–11.5 Current Configuration View
This screen is a read–only screen, which shows the current configuration of the NE.
290 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–12 PERFORMANCE MONITORING
This chapter describes the functions to provide Performance Monitoring management. It explains the
procedures that the operator must perform in order to activate a PM process.

2–12.1 General information on the performance monitoring process
The performance monitoring (PM) gives indication on the quality of the service.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, DS1, …) can be derived from the quality of the
aggregate signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
Considering one section (see below), one current register is for 15 min report and one for 24 h report; 96
history data can be stored for 15 min report and 8 history data for 24 h report.
N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errors
have been occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
The radio section monitored is:
– Radio Hop Section: the section between two radio stations inside the protection section
– Radio Link Section: the section identifying the protected section.
PROPR. FEC MODEM MODEM FEC PROPR.

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

E3 16E1 8E1 4E1 2E1 DS3 16DS1 8DS1 4DS1
Gross bit rate [MHz] 39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140
RS Blocks number/sec. 19200 19200 9600 4800 2400 28000 14000 7000 3500
SES Threshold (Note 1) 5760 5760 2880 1440 720 8400 4200 2100 1050
(Note 1) Note that according to ITU–T G.826 a second is declared Severely Errored Second if it is a
second period with more than 30 % of errored blocks or at least one defect.
3DB 16142 CAAA Ed.01A–DRAFT 291 / 576

The flow chart shown below illustrates the recognition of anomalies, defects, errored blocks, ES and SES
according to ITU–T G.826 (12/2002).

Monitored
second
Yes
Defects?
No
No
Anomalies?
Yes
Yes
%EB ≥ 30? SES
(and therefore an ES)
ES
(but not a SES) No
Path in Path in N
No
available available
State? State?
Yes Yes
cES = cES + 1 cES = cES + 1
cBBE = cBBE + EB(s) cSES = cSES + 1
T1313790–98
End
Fig. 195. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826
292 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–12.2 Performance menu
The performance view allows the user to activate and monitor the PM process on the selected object.
– Resource Tree Area: displays the threshold for measurement and the object monitoring sorted by
channel number.
– Resource List Area: displays the PM management for the selected resource in the tree area.
Fig. 196. Performance View
The performance reports can be of 2 different types:
– 15 minutes
– 24 hours
The following description explains the functions to provide the PM process with a granularity period of 15
min. The same functions are provided for 24h PM process.
The PM are of HOP or LINK type. The current report can be seen (and configured) and the history PM log
can be seen.
3DB 16142 CAAA Ed.01A–DRAFT 293 / 576

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

[1] click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click

on LINK to see the LINK report

[2] click on the desired granularity (15 m or 24 h)
[3] click on CD (Current Data).
With reference to Fig. 197. on page 294 to see an history log:
[1] click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click
on LINK to see the LINK report
[2] click on the desired granularity (15 m or 24 h)
[3] click on the desired HD (History Data).
To each PM can be associated a threshold table. To associate a threshold table click on HOP or LINK in
the Resource Tree Area in Fig. 197.
Fig. 197. Threshold table association screen
In the Counter Thresholds field select the threshold to be associated and click on Apply.
To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select
one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
294 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–12.3 CD (Current Data)
The window displayed in Fig. 198. below allows to start and to read the 15min PM report and 24h PM
report.
Fig. 198. Current Data View
3DB 16142 CAAA Ed.01A–DRAFT 295 / 576

2–12.3.1 CD parameters

The fields displayed in the upper part of Fig. 198. on page 295 allow the operator to check and manage

the parameter of the current data collection.

– “Suspect interval” shows whether the current data are suspect or not.
– “Elapsed Time” field (read–only) displays the elapsed time in the current interval of monitoring.
– “End Period”: display time of the PM in the graphical description and in the tabular description in
the upper part of the screen. By pressing the Refresh button this time changes.
– “Max Interval supp.”: max. number of intervals (reports) which can be suppressed in the History
because they don’t have errors.
– “Num. Interval supp.”: number of intervals (reports) suppressed in the History because they don’t
have errors.
N.B. An interval is defined as “suspect“ if at least one of the following conditions occurs in the
collection period:
– the elapsed time deviates more than 10 seconds of the nominal time
– loss of the PM data in the equipment
– performance counters have been reset during the interval.
2–12.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 198. on page 295 (Counters Area) allow the
management of performance events.
In the left part of Counters Area, there is a graphical description of the event counter value:
– BBE (Errored block)

– ES (Errored second)
– SES (Severely Errored Second)
– UAS (Unavailable second)
N.B. These values refer to the last refresh performed by pressing the Refresh button.
In the right part of Fig. 198. on page 295, there are button choice to perform action on the current data
collection:
– “Reset” button resets the data collection and related counters.
– “Start” button starts the counters for the data collection, when the CD has been stopped.
– ”Refresh” button makes a refresh of the counters.
– “Stop” button stops the counters for the data collection, when the CD has been started.
296 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–12.4 HD (History Data)
The PM process monitors the parameters during a specified interval (i.e. 15min) and stores their values
in history data. A History Data collection is created automatically at the end of each time interval of Current
Data and deleted when the relative CD is deleted.
2–12.4.1 HD Parameters
The table displayed on the following window (Fig. 199. below) collects the history data for a related PM
report.
Fig. 199. History Data
The table columns hold the value of following parameters:
– End Period: End period of the relevant report
– Elapsed time: elapsed time in the related interval
– Suspect interval: this field describes whether the History Data is suspect or not.
– Counters: the last columns hold the counters value (BBE, ES, SES, UAS).
3DB 16142 CAAA Ed.01A–DRAFT 297 / 576

2–12.5 Threshold tables

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

There are threshold tables for the HOP and for the LINK.
There are two default tables: threshold 1 and 2.
To view the available threshold for PM process, the operator must select the Thresholds Tables node
tree in the Resource Tree Area of the Performance View.
N.B. For the association of the threshold tables to the PM refer to para. 2–12.5.3 “Threshold table
association”.
2–12.5.1 How to change a threshold table
Fig. 200. Threshold table
Click on the threshold in the Resource Tree Area in the Resource List Area: the threshold screen will
appear.
In the upper part of the screen, the Name field displays the name assigned to the threshold table.
In the lower part of the screen, low and high threshold for each counter is shown. To change them, the
operator must edit the new values in the table fields and click on the Apply button.
298 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–12.5.2 How to create a threshold table
Fig. 201. Thresholds Table creation
Click on Threshold Tables HOP (or LINK) node tree in the Resource Tree Area of the Performance view.
The Threshold Data Creation screen will appear.
In the upper part write the name of the new table.
In the lower part write the values for the Low and High thresholds.
To create the new table click on Create.
2–12.5.3 Threshold table association
To each PM can be associated a Threshold Table.
To associate a Threshold Table click on HOP–Channel#0 (or Channel#1) or on LINK in the Resource
Tree Area. The 15min&24h tab panel will appear.
In the Counter Thresholds field select the threshold to be associated and click on Apply.
To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select
one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
3DB 16142 CAAA Ed.01A–DRAFT 299 / 576

300 / 576
2–13 SW DOWNLOAD
2–13.1 Server Access Configuration

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

– Password: ftp
– Address: IP address of the F interface or IP address of the Ethernet interface, if present.
– Port: 15,000
N.B. the System Default can be changed by writing different values in the fields and then by clicking
on button OK.
3DB 16142 CAAA Ed.01A–DRAFT 301 / 576

2–13.2 Init SW Download

Through this menu software is downloaded to the NE in order to upgrade the NE software version.

To start download select the desired software version and click on the Init download button.
N.B. This screen displays the software packages previously stored through the menu Supervision
–> Files Administration –> Software Administration available in the NES menu.
The Forced check box can be used to force download (i.e. the complete description file is downloaded
to the NE).
If the Forced download is not selected, the system shall first proceed to compare the software to be
downloaded with the software present in the NE. Then only the differences are downloaded.
Fig. 203. Init Software Download screen
Recommended operation: Before to start the software download it is recommended to disable the
ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.
When the SW download starts a screen, showing the in progress operation of the download, appears.
Download is aborted when the Abort button is pressed.
WARNING: The download time from the CT to the NE flash is 25–30 min. approx.
At 50% of this time starts the download to the first ODU, which lasts 15–20 min. approx.
At the end of this time interval starts the download of the second ODU, if present, which
lasts 15–20 min.
302 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–13.3 SW Status
This menu allows to display the information of the software installed in the NE.
The following information is displayed:
– Name: software name
– Version: software version
– Operational state: enabled or disabled
– Current status: committed or standby. The committed status refers to the software currently in use.
By clicking on the Software Units Status button the screen of Fig. 204. below opens, giving additional
information on the software package.
Fig. 204. SW Status screen
3DB 16142 CAAA Ed.01A–DRAFT 303 / 576

The following information is displayed on the screen:

– EC: software on the Equipment Controller

– OC_R: software on the ODU Controller (Radio) (The total download time of the ODU software is 17
to 20 min approx. with some SES after 15 seconds from the activation) (Note 1)
– FFENI, FGAIA, FGAEX, FMEDU, FPONT: FPGA firmware version (Note 1)
Note 1: during the download of the ODU and FPGA software arises the alarm “Firmware Download On
Going”. This alarm disappears when the download is over. The download lasts 2 minutes for
every FPGA starting from the activation of the alarm.
Fig. 205. SW Unit Status screen
The Flash card, which stores the NE software, contains 2 banks.
The 2 banks can store 2 different software versions. One bank will be committed (active) and the other
bank will be standby.
N.B. The second bank will appear when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is enabled
(this means that download took place without errors) select Activation or Forced Activation in the
Software Management Action field and click on the Apply Action button.
By selecting Forced Activation the bank to be activated is forced to restart.
By selecting Activation the bank to be activated restarts only if the content of the two banks differ.
304 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–14 MIB MANAGEMENT
This function allows the backup and/or restore of the MIB and is carried out at two levels:
– the first is available at NE logged–in level, and allows operations depicted in Fig. 206. below:
NE XXX Flash Card NE XXX Flash Card

MIB MIB
MIB BackUp MIB Restore
NE AAA MIB back–up file NE AAA MIB back–up file MIB delete
NE XXX MIB back–up file NE XXX MIB back–up file
NE ZZZ MIB back–up file NE ZZZ MIB back–up file
ECT ECT
Fig. 206. Allowed MIB management tasks at “NE logged–in” level
From operative point of view, this management is described in para.2–8.3 on page 259.
– the second is available at “Network Element Synthesis level” (independently of whether or not the
NE is logged in), and allows operations shown in Fig. 207. below (it depicts save/load using
floppy–disk, but the operation can be done through any available read/write computer resource):
NE AAA MIB back–up file NE AAA MIB back–up file
NE XXX MIB back–up file NE XXX MIB back–up file
Save to NE ZZZ MIB back–up file

Load from NE ZZZ MIB back–up file
disk disk
ECT ECT
Fig. 207. Allowed MIB management tasks at “Network Element Synthesis” level
From operative point of view, this management and whole applicative examples are described in the
following paragraphs.
3DB 16142 CAAA Ed.01A–DRAFT 305 / 576

2–14.2 MIB management at Network Element Synthesis level and examples

2–14.2.1 MIB back–up on ECT

This operation, carried out by ECT with the NE logged–in, allows to save the MIB from NE to ECT (see
MIB back–up in 2–8.3.1 on page 260).
2–14.2.2 MIB save to disk
This operation, carried out by ECT through the Network Element Synthesis screen, allows to save MIB
from ECT to a floppy disk.
N.B. This example depicts the “Save to disk” by using the floppy–disk, but the operation can be done
through any available read/write computer resource.
1) Launch the task as follows:
Fig. 208. Launch of MIB save to disk
2) The following screen appears:

– in field “Look in” (1) the PC directory where MIBs are stored is shown
– click on Find Now button (2)
Fig. 209. MIB save to disk – phase 1
3) The following screen appears:

– a table showing the MIBs stored in the PC directory is shown
306 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– select the MIB you want to save (3)
– click on OK (4)
– the usual window to choose a save target directory appears (5); select it and start the save
– at save end, a confirmation message is shown (6) indicating also the name of the saved
folder; see N.B. on next page.
Fig. 210. MIB save to disk – phase 2
N.B. The saved MIB folder name acronym does not correspond to the name of the MIB that you have
selected to be saved. In order to know such a correspondence open the saved folder: in the
“userlbl.txt” you can find such name.
Fig. 211. Correspondence between MIB saved folder and MIB saved name
3DB 16142 CAAA Ed.01A–DRAFT 307 / 576

2–14.2.3 MIB load from disk

This operation, carried out by ECT through the Network Element Synthesis screen, allows to load a MIB

previously saved on a floppy disk into ECT’s MIB area.

N.B. This example depicts the “Load from disk” by using the floppy–disk, but the operation can be
done through any available read/write computer resource.
1) Launch the task as follows:
Fig. 212. Launch of MIB load from disk
308 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2) After launch of MIB load from disk, proceed as follows:
– in the screen that opens, click on Browse button (1)
– select the device from which carry out the load operation (2) and open it (3)
– in the opened directory (4) , select the MIB folder to load (5) , then click Open (6)
Fig. 213. MIB load from disk – phase 1
3) ... procedure continues
3DB 16142 CAAA Ed.01A–DRAFT 309 / 576

– in the screen that opens, click on Find Now button (7)
– in the subsequent screen, select the MIB (N.B.) that must be loaded (8), then click on OK

button (9)

– at load end, a confirmation message is shown (10) .

N.B. the MIB name corresponds to that you had previously saved.
10
Fig. 214. MIB load from disk – phase 2
2–14.2.4 MIB restore from ECT
This operation, carried out by ECT with the NE logged–in, allows to restore the MIB from ECT to NE (see
MIB restore in para. 2–8.3.2 on page 261).
a) END OF SECTION 2
310 / 576 3DB 16142 CAAA Ed.01A–DRAFT

SECTION 3: INSTALLATION AND COMMISSIONING
This section provides the whole operative instructions for the equipment HW and SW installation and
commissioning.
Please read para.1–2.6.1 on page 58 for an introduction to the procedures of

this section.
Chapter 3–1 – SWP installation in PC environment

This chapter details all phases necessary to install for the first time the SWP this 313
manual refers to, in the PC environment.
Chapter 3–2 – Line–Up and Commissioning

This chapter details all phases necessary for the equipment line–up and 361
commissioning.
3DB 16142 CAAA Ed.01A–DRAFT 311 / 576

312 / 576
3–1 SWP INSTALLATION IN PC ENVIRONMENT
This chapter details all phases necessary to install for the first time the SWP this manual refers to, in the
PC environment.
N.B. Before starting this installation procedure, it is suggested to give a look to para.1–2.6 on page
57.
N.B. Procedures described in this chapter are carried out with the PC disconnected from the NE.
3–1.1 Requirements
3–1.1.1 PC characteristics
For this SWP version, correct ECT installation requires a PC with the requirements hereafter
described:
1) HW Configuration
– CPU: Pentium III 850 MHz

– RAM: 256 Mbytes (512 Mbytes suggested for Windows XP)
– Hard Disk space: 4 Gbytes
– Display Resolution: 1024x768 pixel
– CD–ROM Drive: 24X
– Primary Interface: Serial Port RS–232–C 9.6 to 57.6 Kbits/sec.
– Communication Interfaces:
• Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication with

NE’s Ethernet port or TCP/IP network is required (if both connections are required
contemporarily, two Ethernet Cards are needed)
• RS232 serial port is mandatory, if local communication with NE’s ECT serial port
(F–interface) is required.
N.B. In alternative, for the usage of the NE’s F–interface with any PC having no
RS232 serial port (but obviously with USB ports available) it is possible to
employ the “USB TO RS232 ADAPTER” , ordering it to Alcatel–Lucent
(P/N 1AF11294AA**).
2) Windows Versions
– Windows 2000 till SP4
– Windows XP (Professional Edition only) till SP2: It is mandatory de–activate the Firewall
installed.
– Windows NT partially supported: CT–K 3.3 and related Q3/SNMP add–on deliveries can
be run on Windows NT but you have to take in account some restrictions in Almap PC 6.5
and PC 7.0 components. They must be considered as Craft Terminal platform restrictions
in Windows NT environment.
3DB 16142 CAAA Ed.01A–DRAFT 313 / 576

3) Additional SW requirements

– Java Runtime Environment (JRE) version 1.4.2–12 or higher (version 1.4.2–12 is included

in the SWP CD–ROM)

– Browser:
• System default browser that correctly supports XHTML 1.1 and CSS 2.1 standards:
– Microsoft Internet Explorer 5.5 or higher
– Mozilla Firefox 1.5 or higher
– Netscape Communicator 6 or higher
N.B. Opera browser is not supported in any version.
• It is mandatory to manually disable system and browser proxy configurations prior
to use both TCO Suite ”Set–Up Tool” and ”Alarms & Settings” (web server) functions;
otherwise, the IP connection from the PC’s web server to the NE cannot take place.
• Used browser window should be at least as larger as 1024x768
– In user’s Windows system desktop folder, files with the following names must not be
present:
• Default_210.qcml
• QCML_210.xsd
• QCML_210.xsl
– Through system’s Display Properties, ‘Settings’ tab, clicking on ‘Advanced’ button, the
Display – ‘DPI setting’ should be set to ‘Normal Size (96 DPI)’;
3–1.1.2 Operator skills and privileges
a) The operator shall be familiar with the use of personal computers in WINDOWS–NT / WINDOWS
2000 / WINDOWS XP (Professional Edition only) environment, internally to which the Network
Element’s application software operates.
b) Furthermore, for a number of configuration applications, the operator shall be aware of some
specifications of the International Standard Organization (ISO) and of the standards applied to the
Plesiochronous Digital Hierarchy (PDH) (ITU–T Recommendations).
c) For the installation of SW packages, the Operator’s PC privilege and skill must be those of “System
Administrator”.
d) The Operator shall be familiar with the use of Alcatel 1320CT functionalities. If necessary, a good
approach to the related matters is to read and understand the following sections of the 1320CT Basic
Craft Terminal Operator’s Handbook (see Tab. 78. on page 557):
• section INTRODUCTION
• section GETTING STARTED
3–1.2 Reference Information Model
For version refer to paragraph on page

V 2.1.0 2–1.3.2 142
314 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.3 Choice of the procedure and summary of SWP installation phases
The procedure and main phases to carry out depend on the ECT environment you want achieve:
a) Only SNMP management of 9400AWY V2.1.0 through Ethernet interface (by CT and TCO Suite).
In this case you must carry out the following main phases:
1) Installation of SWP components from the SWP CD–ROM:

2) Local copy in PC environment of the TCO Suite:
3) End of SW installation from SWP CD–ROM:
4) NE software downloading preparation:
5) CT initial configuration:
6) EML construction:
b) Only SNMP management of 9400AWY V2.1.0 through Ethernet interface (by CT and TCO Suite),
as point a ) above, with the additional possibility of management through the NE’s ECT serial port
(by CT)
In this case you must carry out the following main phases:
1) Installation of SWP components from the SWP CD–ROM [as step 1 ) of case a ) above]:
2) Local copy in PC environment of the TCO Suite [as step 2 ) of case a ) above]:
3) Installation of LLMAN (Alcatel Lower Layer MANager) from the SWP CD–ROM:
4) Installation and configuration of Alcatel Virtual Network Card for Lower Layers:
5) End of SW installation from SWP CD–ROM [as step 3 ) of case a ) above]:
6) NE software downloading preparation [as step 4 ) of case a ) above]:
7) CT initial configuration [as step 5 ) of case a ) above]:
8) EML construction [as step 6 ) of case a ) above]:
c) Management of SNMP 9400AWY V2.1.0 [as case a ) or b ) above] and of other SWPs for different
NEs (e.g. Alcatel–Lucent 9600USY, 9600LSY)
In this case, before doing anything, read carefully para.3–1.4 on page 316
N.B. Chapter 4–10 on page 526 describes how to to de–install the Software Package from the PC.
3DB 16142 CAAA Ed.01A–DRAFT 315 / 576

3–1.4 Preliminary: installation of different SWPs in the same PC

If you like to install different Alcatel–Lucent SWPs (1320CT–based) in the same PC, you must be aware

that there are some SW components to be installed which are common to such SWPs.

The basic principle is that, due the ascendant compatibility, for such common components you must take
and install, from each SWP, the highest version components, e.g.:
– Java Run Time Environment : highest version
– Lower Layers Manager : highest version
– Craft Terminal Base Platform [Craft Terminal Base Platform Q3 Add–On (EML–IM)] : highest version
– Craft Terminal Base Platform SNMP Add–On (EML–IM) : highest version
– Craft Terminal Base Platform Help On–Line Add–On : highest version
– Craft Terminal NE Type & Release Configuration Add–On: highest version
Just as an example, Fig. 215. on page 317 shows the SW components and points out the common SW
components of:
– SWP 9600LSY V2.0.4
– SWP 9400AWY IDU32 (which this handbook refers to)
(screens are those appearing after the SWP installation start–up, as in step 5 ) on page 320).
N.B. as far as the SWP 9400AWY IDU32 is concerned, JRE and Alcatel Lower Layers Manager do
not appear in the SWP CD–ROM start–up screen because:
– JRE is automatically installed, if necessary, according to rules explained in para.2–2.2.3
on page 148;
– Alcatel Lower Layers Manager is installed, if necessary, on Operator explicit request only,
as explained in para.3–1.7 on page 325.
To make the comparison between the versions of the common SW components, please refer to the
Product Release Notes associated to the SWPs you want to install. As far as the SWP 9400AWY IDU32
is concerned, refer to the version–specific paragraph listed in para.2–1.1 on page 141.
In term of method to install:
– use CT installation Product Guided and select component depending of the rule before;
– install at first the SWP with the common SW components highest versions, and after the other SWPs
leaving unselected the common SW components already installed.
Please extend these considerations to the need of installing more than two different SWPs.
Procedure example (referred to the two SWP cited above):
1) compare the PC characteristics and verify that your PC meets the highest requirements (as far
as the SWP 9400AWY IDU32 is concerned, refer to para.3–1.1.1 on pages 313–314
2) uninstall all Alcatel–Lucent products (the “clean” situation simplifies the following operations)
3) install the SWP 9400AWY IDU32 , as described in para.3–1.5 on page 318, selecting all
components, because its common SW components have versions higher than those of the
SWP 9600LSY V2.0.4
4) carry out the local copy in PC environment of the TCO Suite, as described in para.3–1.6 on page
322
5) carry out the installation of LLMAN from the SWP 9400AWY IDU32 CD–ROM as described in
para.3–1.7 on page 325, because its version is higher than that of the SWP 9600LSY V2.0.4
6) complete the SWP 9400AWY IDU32 installation as described in steps 4 ) to 8 ) of point b ) on
page 315
7) using the CT installation Product Guided, start the installation of the SWP 9600LSY V2.0.4,
de–selecting (see Fig. 215. below) the components JRE V1.3 , Alcatel Lower Layers Manager
V3.4.0 , CT–K v3.2.0 and HOLCT–K–ADD–ON v1.1.0, because already installed (with higher
versions) by the SWP 9400AWY IDU32 installation
8) complete the SWP 9600LSY V2.0.4 installation as described in relevant documentation.
316 / 576 3DB 16142 CAAA Ed.01A–DRAFT


Fig. 215. Common components of different SWPs (example)
common
components
317 / 576
3–1.5 Installation of SWP components from the SWP CD–ROM

N.B. Please read carefully para.3–1.3 on page 315, for the position of this step inside the whole

installation procedure.

N.B. Procedures described in the following are carried out with the PC disconnected from the NE.
3–1.5.1 Important warnings
N.B. Windows versions supported are just those listed in point 2 ) on page 313 (e.g. Windows XP
Home Edition, Windows 95, 98, ME, etc. are not supported).
N.B. System browser versions supported are just those listed in point 3 ) on page 314 (other versions
are not supported).
N.B. Warning about Windows XP till SP2 – Professional Edition:

It is mandatory to de–activate the Firewall installed.
N.B. Windows NT is partially supported: CT–K 3.3 and related Q3/SNMP add–on deliveries can be
run on Windows NT with some restrictions.
N.B. These operations must be performed by the Administrator of the PC.
WARNING: During the installation an ALCATEL directory is automatically created, if not already
present.
If ALCATEL directory is already present on the PC, for a correct operation of the FTP
server, this directory must have all upper case characters (i.e. “ALCATEL”).
N.B. Note for Users having previously used SWP 9400AWY versions up to V2.0.3:
This behavior takes place from V2.0.4: the 1320CT installation of this SWP does not include
anymore the Q3CT–K–Add–On component.
In particular, if LLMAN component is not installed because you want to manage AWY NEs only
by Ethernet interface, also Q3CT–K–Add–On component has not to be installed (or has to be
explicitly de–installed if previously installed) in order to have a correct behavior on 1320CT
usage.
Obviously, as also applied to previous SW releases, it is mandatory to install LLMAN component
in order to be able to manage AWY NEs by Serial F interface and in this case Q3CT–K–Add–On
component can be installed to enable the possibility to manage also Q3 NEs with the same
1320CT installation.
N.B. Notes for Users having previously used any SWP 9400AWY previous versions:
When installing this SWP on a PC where are already installed the previous:
– SWP 2.0.3, 2.0.4 or 2.1.0x versions, it is mandatory select all the components in the
installation procedure
– any 1.0.x and 2.0.x versions, it is not necessary to de–install them from PC.
318 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.5.2 Operations sequence
Step 1. Initial checks

1) Verify that the PC characteristics meet all HW and SW requirements specified in para.3–1.1.1
on page 313
2) Verify you do have the SWP CD–ROM P/N REF.[a] in Tab. 53. (page 141)
3) WARNING : whenever you have already installed a previous–version SWP V2.1.x including the
TCO Suite, delete the existing shortcut to the Start_html icon as well as the TCOSuite folder
(see Fig. 224. on page 324). Note: it is not necessary to delete shortcut to the Start_html icon
relevant to previous SWP V2.0.x.
Step 2. Installation start–up
1) Insert the SWP CD–ROM in the PC’s CD–ROM unit
2) The TCO Suite start–up begins. Please refer to para.2–2.2.3 for the procedure execution and
the management of special conditions that could occur
3) At the end of the TCO Suite start–up, the CD–ROM TCO Suite Main Menu screen appears
(Fig. 216. below); click on Advanced Settings button
Fig. 216. CD–ROM TCO Suite Main Menu screen
3DB 16142 CAAA Ed.01A–DRAFT 319 / 576

4) After a while, the CD–ROM TCO Suite Advanced Settings screen appears (Fig. 217. ); click on
1320CT Package Installation button

Fig. 217. CD–ROM TCO Suite Advanced Settings screen
5) After a while, the SWP component selection screen appears (Fig. 218. ); leave all components
selected (or click on Select All button), then click on Next button
Fig. 218. SWP component selection screen and installation start
320 / 576 3DB 16142 CAAA Ed.01A–DRAFT

6) The installation process begins. After its completion (time depends on PC performance), the
following screen appears; clicking on confirmation button (YES / SÌ), the installation report is
produced
Fig. 219. SWP component installation end, and installation report
N.B. At any time, you can also check the components installed (Fig. 220. ) carrying out,
in Windows environment:
Start ⇒ Settings ⇒ Control Panel ⇒ Add/Remove Programs
Fig. 220. Check of installed Alcatel SWP components
3–1.5.3 Next step
You have now completed the installation of the SWP components. Leave the:
– SWP CD–ROM in the PC’s CD–ROM unit,
– and the CD–ROM TCO Suite Advanced Settings screen open,
and proceed with the Local copy in PC environment of the TCO Suite, para.3–1.6 on page 322.
3DB 16142 CAAA Ed.01A–DRAFT 321 / 576

3–1.6 Local copy in PC environment of the TCO Suite


installation procedure.

This step is mandatory to have all TCO Suite functionalities (with exception of those related to the SWP
installation in PC environment) available from the PC after the extraction of the SWP CD–ROM from the
PC’s CD–ROM unit.
1) In the CD–ROM TCO Suite Advanced Settings screen (Fig. 217. on page 320) click on Local
Copy of TCO Suite button
2) Fig. 221. below: user is asked to choose the location where save must be done; such a location
could be on the local PC or on a USB “Key”, Flash Memory Card, etc. Confirm or change it, and
proceed
N.B. As an example, Fig. 221. below shows the TCOSuite.206 folder, that was created
installing the SWP 9400AWY R.2.0.4. It is not necessary to delete it, because the
Local Copy of TCO Suite from this SWP 9400AWY IDU32 CD–ROM will create
another folder (see Fig. 224. on page 324). If you delete it, you will loose the TCO
functionalities associated to the SWP 9400AWY R.2.0.4.
Fig. 221. Local Copy of TCO Suite location choice
322 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3) Where the user selects to put the TCO Suite, will be created a “TCOSuite” directory with the
content of the same TCO Suite located on CD–ROM. The copy will proceed with a clear show
of the progress (Fig. 222. below).

Fig. 222. Local Copy of TCO Suite progress and end
N.B. The user can also cancel the copy operation and all the files copied will be removed
(Fig. 223. below).
Fig. 223. Copy cancelled
4) Since Java is not system–specific, neither shortcut to local TCO Suite Start.html page, nor
Microsoft Windows “Start” menu entry for TCO Suite can be created automatically. User should
provide to create them as follows (see following Fig. 224. ): open the TCO Suite folder [from the
location established in previous step 2 ) ], and create a shortcut to the Start.html icon on the PC’s
desktop.
N.B. Following the example of Fig. 221. on page 322, in order to create the shortcut, pay
attention to open the new folder that has been created now, and to give it a mnemonic
name different from the shortcut associated to the pre–existing SWP.
3DB 16142 CAAA Ed.01A–DRAFT 323 / 576

Pre–existing folder New folder
(SWP V2.0.4) (SWP V2.1.x)

OPEN
PC DESKTOP
LINK
Fig. 224. Shortcut to the TCO Suite Start icon
3–1.6.2 Next step
You have now completed the Local copy in PC environment of the TCO Suite. Leave the:
– SWP CD–ROM in the PC’s CD–ROM unit,
– and the CD–ROM TCO Suite Advanced Settings screen open,
and proceed to the next installation step (para.3–1.3 on page 315), according to the case a ) or b ) you
want to achieve.
324 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.7 Installation of LLMAN from the SWP CD–ROM
installation procedure. In particular, take into account that this step is necessary only in case
b ) (additional possibility of management of 9400AWY V2.1.0 through the NE’s ECT serial port).
1) In the CD–ROM TCO Suite Advanced Settings screen (Fig. 217. on page 320) click on button
Serial–F–Interface Driver Installation
This function performs the installation for the “Alcatel Lower Layers Manager” together with the
drivers needed for the “Alcatel Virtual Network Card for Lower Layers”. A splash screen will
appear as soon as the button applet is clicked (Fig. 225. below) and the installation begins.
Fig. 225. Alcatel Lower Layers Manager ”splash screen”
2) User is asked to select installation and application language (Fig. 226. below).
Fig. 226. Alcatel Lower layers Manager language selection
3) Then the installation is carried out automatically after a simple confirmation by the user
(Fig. 227. on page 326).
3DB 16142 CAAA Ed.01A–DRAFT 325 / 576

Fig. 227. Alcatel Lower Layers Manager Installation screens
3–1.7.2 Next step
You have now completed the Installation of LLMAN from the SWP CD–ROM.
Now, you must carry out the Installation and configuration of Alcatel Virtual Network Card for Lower
Layers (para.3–1.8 on page 327).
326 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.8 Installation and configuration of Alcatel Virtual Network Card for Lower
Layers
installation procedure. In particular, take into account that this step is necessary only in case
b ) (additional possibility of management of 9400AWY V2.1.0 through the NE’s ECT serial port).
At first SWP installation on ECT, after the installation of Alcatel Lower Layer Manager (carried out in
previous para.3–1.7 on page 325), it is necessary, for NE connection using TCP/IP through serial port, to
configure a Virtual Network Card.
Alcatel Virtual Network Card for Lower Layers is a software component used by Alcatel Lower Layers
Manager to manage TCP/IP packets through the serial port.
Follow this guide to install and configure Alcatel Virtual Network Card for Lower Layers using the
Control Panel.
3–1.8.1 Important warning
Whenever, after the completion of this step, you must install a new network card, always verify
that the Alcatel Virtual Network Card for Lower Layers is always the first
one in the “Network Connections” list. Refer to para.3–1.8.6 on page 353 for details.
3–1.8.2 Choice of the procedure, according to Windows platform
for installation and configuration on refer to paragraph on page
Windows NT 4.0 (partially supported) 3–1.8.3 328
Windows 2000 till SP2 3–1.8.4 334
Windows XP till SP2 (Professional Edition only) 3–1.8.5 343
3DB 16142 CAAA Ed.01A–DRAFT 327 / 576

3–1.8.3 Windows NT 4.0

3–1.8.3.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0)

To install the Alcatel Virtual Network Card for Lower Layers select the Adapters tab in the Network Control
Panel applet.
After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following the
instruction of the Windows NT 4.0: Configuring Alcatel Virtual Network Card for Lower Layers section.
Before installing Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please
refer to Windows NT Help).
– Click the Add... button in the Adapter tab of the Network Control Panel applet.
Fig. 228. Windows NT installation step 1
328 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– In the Insert Disk dialog box, type the source path of the driver files copied during installation phase
(e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command Prompt
window to discover the right location of the WinNT folder) and click OK.
– If the dialog box in Fig. 230. appears, the driver is already installed.
Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP
parameters before use it in with Alcatel Lower Layers Manager. Proceed with para.3–1.8.3.2 on page
330.
3DB 16142 CAAA Ed.01A–DRAFT 329 / 576

3–1.8.3.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0)

To configure the Alcatel Virtual Network Card for Lower Layers use both the Bindings and the Protocols

tabs in the Network Control Panel applet.

Before configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol
(please refer to Windows NT Help).
This operation must be performs at Administrator of the PC, because it subsequently could be to
set IP address .
To install the Alcatel Virtual Network Card for Lower Layers run the Network Control Panel applet from
the Control Panel.
– Select the bindings of Alcatel Virtual Network Card for Lower Layers in the Bindings tab (1), (2) of
the Network Control Panel applet.
– Disable any unneeded component (3), (4).
– Selecting the Protocols tab (5) of the Network Control Panel applet, the either a message box
(Fig. 232. NT configuration step 2) or a dialog box (Fig. 233. NT configuration step 3) may appear.
– Follow the instructions until the dialog box (Fig. 234. NT configuration step 4) will appear.
Fig. 231. Windows NT configuration step 1
330 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– Click Yes to save changes.
– Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).
3DB 16142 CAAA Ed.01A–DRAFT 331 / 576

– Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for Lower
Layers and push OK.

1
*** WARNING ***
If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is
necessary, for a correct ECT functionality, to perform an explicit ECT re–customization by executing the
following command:
– Start → Programs → Alcatel → SNMPCT–K–ADD–ON v... → SNMP Add–On Customization
332 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– Click Close in the Protocols tab of the Network Control Panel applet.
– The new configuration of Alcatel Virtual Network Card for Lower Layers will be used at the next restart
of the computer.
– If you are configuring or installing the Alcatel Virtual Network Card for Lower Layers you can click Yes.
If you are installing some other component you should click No and restart the computer later.
3–1.8.3.3 Next step (Windows NT 4.0)
You have now completed the installation and configuration of the Alcatel Virtual Network Card for Lower
Layers in Windows NT 4.0 environment. Now proceed with the Check for the “Network Connections”
order, para.3–1.8.6 on page 353.
3DB 16142 CAAA Ed.01A–DRAFT 333 / 576

3–1.8.4 Windows 2000

The System Standby function in the Power Option menu of the Control Panel must be always

disabled (select in the Power Schemes tab panel in the Power schemes field “Always On”).

3–1.8.4.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows 2000)
To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard from
the Control Panel.
Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP
protocol (please refer to Windows 2000 Help).
Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:
Alcatel Virtual Network Card for Lower Layers has to be installed only once.
instruction of the Windows 2000: Configuring Alcatel Virtual Network Card for Lower Layers section.
– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
Fig. 237. Windows 2000 installation step 1
334 / 576 3DB 16142 CAAA Ed.01A–DRAFT


Click the Have Disk... button in the Select Network Adapter dialog box.
335 / 576
336 / 576

– In the Install From Disk dialog box, type the source path of the driver files copied during installation
phase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command
Prompt window to discover the right location of the WinNT folder) and click OK.
3DB 16142 CAAA Ed.01A–DRAFT 337 / 576

– Click Next in the Start Hardware Installation dialog box.

339.
338 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.8.4.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows 2000)
This operation must be performs at Administrator of the PC, because it subsequently could be to
set IP address .
To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dial–up connections
applet from the Control Panel.
Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP
protocol (please refer to Windows 2000 Help).
the Control Panel.
– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the
Network and Dial–up connections applet.
Fig. 242. Windows 2000 configuration step 1
3DB 16142 CAAA Ed.01A–DRAFT 339 / 576

– Uncheck any unneeded component in the Properties dialog box General tab (1). Check and select
the Internet Protocol (TCP/IP) component (2) and click Properties (3).

1
340 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– Configure the IP Address (1) and the Subnet Mask (2) and push Advanced (3) to open the relevant
Advanced TC/IP Settings screen
– In the Advanced TC/IP Settings screen’s Interface Metric field, write 50 (4) and push OK (5)
– Having come back to the first screen, push OK (6)
1
2
3DB 16142 CAAA Ed.01A–DRAFT 341 / 576

Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Manager
to use it.

*** WARNING ***

following command:
3–1.8.4.3 Next step (Windows 2000)
Layers in Windows 2000 environment. Now proceed with the Check for the “Network Connections”
order, para.3–1.8.6 on page 353.
342 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.8.5 Windows XP (Professional Edition only)
The System Standby function in the Power Option menu of the Control Panel must be always
disabled (select in the Power Schemes tab panel in the Power schemes field “Always On”).
3–1.8.5.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows XP
Professional Edition)
To install the Alcatel Virtual Network Card for Lower Layers run the Add Hardware Wizard from the Control
Panel.
instruction of the Windows XP: Configuring Alcatel Virtual Network Card for Lower Layers section.
Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:
Alcatel Virtual Network Card for Lower Layers has to be installed only once.
– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
3DB 16142 CAAA Ed.01A–DRAFT 343 / 576

344 / 576
Fig. 245. Windows XP installation step 1


345 / 576
–
346 / 576
Click the Have Disk... button in the Select Network Adapter dialog box.

– In the Install From Disk dialog box, type the source path of the driver files copied during installation
phase (e.g. C:\Windows\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a
Command Prompt window to discover the right location of the Windows folder) and click OK.
C:\Windows\System32\Drivers\LLmanNIC
3DB 16142 CAAA Ed.01A–DRAFT 347 / 576

– Click Next in the The wizard is ready to install your hardware dialog box.

349.
348 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.8.5.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows XP
Professional Edition)
This operation must be performed by the Administrator of the PC, because it subsequently
could be to set IP address .
To configure the Alcatel Virtual Network Card for Lower Layers run the Network connections applet from
the Control Panel.
the Control Panel.
– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the
Network and Dial–up connections applet.
Fig. 250. Windows XP configuration step 1
3DB 16142 CAAA Ed.01A–DRAFT 349 / 576

– Uncheck any unneeded component (disable always the QoS Packet Scheduler – 1 –) in the
Properties dialog box General tab. Check and select the Internet Protocol (TCP/IP) component (2)

and click Properties (3).

1
2
350 / 576 3DB 16142 CAAA Ed.01A–DRAFT

– Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK
(4).
1
2
*** WARNING ***
following command:
3DB 16142 CAAA Ed.01A–DRAFT 351 / 576

– Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOS
over TCP/IP (2) and then push OK (3).

1
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers
Manager to use it.
3–1.8.5.3 Next step (Windows XP Professional Edition)
Layers in Windows XP (Professional Edition only) environment. Now proceed with the Check for the
“Network Connections” order, para.3–1.8.6 on page 353.
352 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.8.6 Check for the “Network Connections” order
For the SWP to operate correctly, it is necessary that the Alcatel Virtual Network Card for Lower Layers
is always the first one in the “Network Connections” list.

To carry out this check, operate as follows:
1) Start → Control Panel → Network Connections
2) in the field “LAN or High Speed Internet”, select the Device Name “Alcatel Virtual Network
Card for Lower Layers”
3) from “Advanced” menu, select “Advanced Settings”
4) in the relevant screen (Fig. 254. below) verify that it is the first in the list. If necessary, move its
position, using suitable arrows.
Fig. 254. Check for the “Network Connections” order
Whenever, after the installation of this SWP, you must install a new network card, always verify
that the Alcatel Virtual Network Card for Lower Layers is always the first one in the “Network
Connections” list.
You have now completed the installation, configuration and check of the Alcatel Virtual Network Card for
Lower Layers. Now proceed with the End of SW installation from SWP CD–ROM, para.3–1.9 on page
354.
3DB 16142 CAAA Ed.01A–DRAFT 353 / 576

3–1.9 End of SW installation from SWP CD–ROM

Having reached this phase, you have finished the Software transfer from SWP CD–ROM into the PC

environment. Now, you can extract the SWP CD–ROM from the PC’s CD–ROM unit.

Now proceed with NE software downloading preparation, para.3–1.10 below.
3–1.10 NE software downloading preparation
N.B. This description is retrieved from 1320CT Basic Operator’s Handbook 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 NE’s equipment controller and the peripheral
units (such a downloading is explained in Chapter 4–8 on page 525).
This operation is independent from the NE management state and must be executed with the following
procedure:
1) Launch the CT by:
– TCO Suite Main Menu ⇒ Operational & Maintenance
or:
– Start ⇒ 1320CT
For details, refer to point e ) on page 178
2) On NES (Network Element Synthesis) screen that opens, from the Supervision pull down
menu select the File Administration and then the Software Administration option, as shown
in Fig. 255. herebelow.
Fig. 255. Selecting SWP Administration

3) In the screen that opens (Fig. 256. below) click on Install
Fig. 256. SWP Administrator screen
354 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4) In the screen that opens (Fig. 257. on page 356 is an example) select the directory where the
NE software package is installed:
Alcatel / JUSMw V.x.x.x / ect / swdw / <equipment name> / <version> / <descriptor file> (*)
(*) the 9400AWY equipment name is “R94AWY” ;

the version is that you want;
the descriptor file has always the extension “.DSC”.
N.B. The NE software package can also be selected from the CD–ROM used for the
installation of the NE software. In this case, after inserting the CD–ROM in the driver,
choose the following:
ect / swdw / <equipment name> / <version> / <descriptor file>
WARNING: in case you have still installed in your PC one or more previous Alcatel–Lucent SWP, in
step [2] of Fig. 257. on page 356, you must be sure to open the JUSM folder relevant to
the SWP you have installed now. In such an example:
• JUSMw2.2.16 is associated to SWP 9400AWY 2.0.4
• JUSMw2.3.11 is associated to SWP 9400AWY 2.1.0 [you can check the JUSM
version comparing it with the report produced at installation end (see Fig. 219. on
page 321 )].
In any case, whenever the version to be selected in step [6] of Fig. 257. on page 356 is
not that you wanted, you can go backward to step [2] to explore the correct JUSM folder.
3DB 16142 CAAA Ed.01A–DRAFT 355 / 576

356 / 576
1
5
3
Fig. 257. Directory selection for the descriptor file “.DSC”

6
2

5) On last screen (containing the “.DSC” file), click on Open to activate the installation of the
selected“.DSC” file. At the end of the process, a confirmation message is displayed:
6) At this point the NE Software Package is installed and available to be downloaded on the
Network Elements (as described in chapter 4–8 on page 525).
Such availability can be verified (as shown in Fig. 258. herebelow) operating in the Network
Element Synthesis screen (Fig. 255. on page 354), selecting, from the Supervision pull down
menu, the File Administration and then the Software Administration option.
Fig. 258. SWP available for download to NEs
Now proceed with CT initial configuration, para.3–1.11 on page 358.
3DB 16142 CAAA Ed.01A–DRAFT 357 / 576

3–1.11 CT initial configuration

N.B. Procedures described in the following are carried out with the PC disconnected from the NE.

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

chapter “SOFTWARE INSTALLATION”, paragraph “Craft Terminal Configuration”
3–1.11.2 Craft Terminal local connection to the NE
The CT can be locally connected to the NE preferably through the Ethernet Network Port, or through the
Serial Port.
Only one connection can be active at a time.
Please refer to para.2–2.4.2 on page 175 to change from Ethernet Network Port to Serial port or viceversa.
N.B. this setting operation is not necessary if you login the local NE through the Operational &
Maintenance button of the TCO Suite Main Menu.
358 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–1.12 EML construction
After having activated the 1320CT application (by TCO Suite Main Menu ⇒ Operational & Maintenance
or Start ⇒ 1320CT) the “Network Element Synthesis screen” appears (example in Fig. 255. on page 354).
This NE map specifies the NEs that can be reached by the ECT. This map must be built by the Operator.
N.B. This map is empty in the case of first installation of ECT on a PC.
The map content is usually not affected when you install a new SWP or upgrade the
SWP–release–”version” (e.g. from V2.1.x to V2.1.y).
The set of procedures necessary to configure the ECT in order to manage the Network Elements (which
include the management of Maps, Submaps and Network Elements, like creation, deletion, saving,
opening, etc) is named EML construction .
In order to carry out these procedures, refer to the:

– 1320CT Basic Craft Terminal Rel.3.x Operator’s Handbook (see Tab. 78. on page 557)
• section “EML CONSTRUCTION”.
An example of NE creation in the map is given in point g ) on page 180.
end of SWP INSTALLATION IN PC ENVIRONMENT procedure
3DB 16142 CAAA Ed.01A–DRAFT 359 / 576

360 / 576
3–2 LINE–UP AND COMMISSIONING
3–2.1.1 General
This chapter details all phases necessary for the equipment line–up and commissioning, providing the
user with the information needed to connect, power on, and perform a minimum turn–up of an equipment
of the 9400AWY family running with the SWP 9400AWY IDU32 .
It is assumed that the mechanical installation of the INDOOR and OUTDOOR units is completed and the
antennas are installed and pre–positioned. Moreover, the IF cable has been allocated but not connected
to the IDU. Any information needed to complete the above mentioned operations are out of the scope of
this chapter. For this purpose refer to the Installation Handbook.
All the cables and measurement kits as described in the following (Tab. 64. on page 362) are supposed
to be available.
The Alcatel–Lucent Software package SWP 9400AWY IDU32 must have already been installed in the
PC used as the Craft Terminal (CT) and the same software already downloaded in the equipment.
3–2.1.2 Conventions
To simplify the description of actions, the following symbols are in use:
Symbol used Meaning

. Manual action
n Check/Verify
CT⇒ On Craft terminal Select
⇒ Select a Menu item
→ Sub Menu item
The commissioning operations described in this document are for a link between a station A and a station
B.
If the network includes supervision, station A is the one located between the supervisory station and
station B (see figure below). Installation and commissioning begin at station A.
STATION A STATION B
ODU ODU
IDU IDU
Network
(Supervision Side) Network
Fig. 259. Relative positions of stations A and B
3DB 16142 CAAA Ed.01A–DRAFT 361 / 576

3–2.1.3 Summary of the commissioning phases

Before proceeding with this operation ensure that you have the equipment and accessories required for

that purpose. All these materials should be present in the service bag.

The commissioning procedure is summarized as follows:
– Turn up (phase 1)
• Station A, roughly point the antenna towards station B

• Commission station A (phase 1)
• Commission station B (phase 1)
• Station B, fine align the antenna towards station A
• Station A, fine align the antenna towards station B
– Site acceptance tests (phase 2)
• Station A, carry out all the commissioning checks and tests – Report the results in the TRS
• Station B, carry out all the commissioning checks and tests – Report the results in the TRS
Tab. 64. Test and commissioning instruments

INSTRUMENT QTY CHARACTERISTICS
The PC must have been already configured as Craft
Terminal for 9400AWY Rel.2.1.0.
Laptop computer running the If necessary, please refer to the Chapter 3–1 – SWP
1
supervisory software installation in PC environment on page 313 for any
related information and installation instructions you may
need.
PDH Analyzer –Pattern Generator 1 See System configuration
V.11 – G.703 Data Analyzer 1 See System configuration
Ethernet Data Analyzer 1 Optional – See System configuration
Multi–meter 1 Voltmeter AC and DC – Loop tester
Light service kit cable for ODU Rx
1 see para.3–2.10 on page 446
power monitoring
Test Result Sheet and Site Acceptance Test protocol,
TRS and SAT 1 available as separate document
(REF.[C] on page 556)
3–2.1.4 Hardware (HW) Presetting
Every unit is factory preset, so setting is not required.

In case of doubt verify that the equipment is preset according to plant requirements.
3–2.1.5 Safety–EMC–EMF–ESD norms and Cautions to avoid equipment damage
Read carefully Safety–EMC–EMF–ESD norms in Appendix A on page 529, and Cautions to avoid
equipment damage in para.1–1.5 on page 32.
362 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.2 Description of equipment interconnections
Following drawings show the equipment interconnections at IDU level in the “1+0” and “1+1”
configurations, according to the IDU equipment provisioning specified in Tab. 5. on page 66 :

IDU configuration drawings on page
16E1 without plug–ins 364
16E1 + Audio and User Service Channel plug–in 365
16E1 + Ethernet plug–in 366
16E1 + Ethernet plug–in + Audio and User Service Channel plug–in 367
32E1 without plug–ins 368
32E1 + Audio and User Service Channel plug–in 369
As depicted in the drawings, the usage of the protection boxes also in the “1+0” configurations allows the
easy expansion to the corresponding “1+1” configurations just installing and cabling the IDU Extension
unit without altering the connections already existing on the IDU Main unit.
For the layouts at ODU level, refer to para.1–4.3 on page 96 .
For additional and more detailed information, please refer to the Installation Handbook, in particular for:
– P/Ns of cables to use
– exact shelves layout for cable route optimization
– equipment interconnections in the “1+0” configurations and connector pinout at User line side, in the
case the protection boxes are not used.
3DB 16142 CAAA Ed.01A–DRAFT 363 / 576

3–2.2.1 Configurations with 16E1

1+0 CONFIGURATION

E1 line–side user interface Audio & Service channels line–side
connectors user interface connectors
ODU CH1
PS
Main
1+1 CONFIGURATION

Extension ODU CH0
PS
ODU CH1
PS
Main
Fig. 260. Equipment interconnections for configurations with 16E1
364 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.2.2 Configurations with 16E1 + Audio and User Service Channel plug–in
1+0 CONFIGURATION

ODU CH1
PS
Main
1+1 CONFIGURATION

Extension ODU CH0
PS
ODU CH1
PS
Main
Fig. 261. Equipment interconnections for configurations with 16E1 + Audio and User Service Channel
plug–in
3DB 16142 CAAA Ed.01A–DRAFT 365 / 576

3–2.2.3 Configurations with 16E1 + Ethernet plug–in

1+0 CONFIGURATION

2 x Ethernet
ODU CH1
PS
Main
1+1 CONFIGURATION

2 x Ethernet
Extension ODU CH0
PS
ODU CH1
PS
Main
Fig. 262. Equipment interconnections for configurations with 16E1 + Ethernet plug–in
366 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.2.4 Configurations with 16E1 + Ethernet plug–in + Audio and User Service Channel plug–in
1+0 CONFIGURATION

2 x Ethernet
ODU CH1
PS
Main
1+1 CONFIGURATION

2 x Ethernet
Extension ODU CH0
PS
ODU CH1
PS
Main
Fig. 263. Equipment interconnections for configurations with 16E1 + Ethernet plug–in + Audio and
User Service Channel plug–in
3DB 16142 CAAA Ed.01A–DRAFT 367 / 576

3–2.2.5 Configurations with 32E1

1+0 CONFIGURATION

ODU CH1
PS
Main
1+1 CONFIGURATION

ODU CH0
Extension
PS
ODU CH1
PS
Main
Fig. 264. Equipment interconnections for configurations with 32E1
368 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.2.6 Configurations with 32E1 + Audio and User Service Channel plug–in
1+0 CONFIGURATION

ODU CH1
PS
Main
1+1 CONFIGURATION

Extension ODU CH0
PS
ODU CH1
PS
Main
Fig. 265. Equipment interconnections for configurations with 32E1 + Audio and User Service Channel
plug–in
3DB 16142 CAAA Ed.01A–DRAFT 369 / 576

3–2.3 Commissioning of STATION A – phase 1 (Turn up)

– Where necessary, switch OFF the power supply before disconnecting the earth
connection,
– Do not connect instruments directly to the IDU/ODU cable connector since the
connector carries 48v DC used to supply the ODU.
– Do not connect the IF cable between IDU and ODU while the IDU is powered up.
3–2.3.1 Turn–on preliminary operations
ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF.
n The antenna of station A is pointed towards station B the best as possible (use compass if
necessary).
n The hardware configuration of the equipment corresponds to the expected one.
n Make visual inspection for units’ installation and cabling:
• The IDU(s) subrack allocation according to the station lay–out
• The IDU(s) subrack and units ground connections
• The power supply voltage is present (48, 60 V DC) with the correct polarity at the IDU power
supply input
• In 1+1 configuration, check the connections between main and extension IDU(s)
• Tributaries and service channel access are cabled on the station DDF
• The IDU–ODU cables ground kit connections
• The ODU(s) ground connections (In the case of a non–integrated antenna, the antenna and the
ODU(s) must be ground connected)
• The IDU(s) / ODU(s) cables are connected to IDU(s) and ODU(s)
• The ODU(s) cables connectors waterproofing
370 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.2 Powering up the IDU(s) with ODU(s) connected
This operation has the following scopes:

– verify the SWP present both in CT and NE
– make the Central Frequency and Shifter values of ODUs be acquired by IDU (so that they are
retained in the NE’s data base).
Proceed as follows:
a) Switch on IDU (MAIN and, if equipped, EXTENSION)
b) Start the Craft Terminal and carry out the NE login

Proceed as follows (for details refer to para.2–2.5.2 on page 177):
1) Connect the cross–connect Ethernet cable between the Ethernet port of the PC and the
Ethernet interface on the Main IDU (see Fig. 83. on page 174).
In alternative connect the RS232 cable between the serial port of the PC and the “F” interface
(ECT) on the Main IDU (see Fig. 83. on page 174).
2) Power on the PC and wait for its start–up
3) Start–up the Craft Terminal and wait for the Network Element Synthesis screen
4) Give the NE icon a mnemonic name (e.g. STAZ A as in Fig. 90. on page 181)
5) Start supervision on the local Network Element
6) Login the local Network Element, using the Administrator UserName & Password
7) Wait for the main Equipment view (CT) to appear (for details, refer to para.2–2.6 on page 185)
c) Check that CT and NE versions are both V2.1.0 (for details, refer to para.1–2.6.3 on page 61).
If NOT, proceed as specified in Chapter 4–9 on page 525.
d) Start the Interactive Quick Configuration Procedure clicking on Main Tool Bar’s icon Interactive
Quick Configuration (see Fig. 95. on page 186), or select Configuration ⇒ Quick Configuration
⇒ Interactive mode from the Menu bar.
The window in Fig. 272. on page 379 will appear. This window is the first step of the Interactive
Quick Configuration Procedure. Clicking repeatedly on Next button (without any other actions),
reach Step C on page 383 (Channel configuration) and confirm the Frequency Values fields.
Then, clicking repeatedly on Next buttons (without any other actions), reach Step L on page 397 and
click on Finish button. In this way the Frequency Values fields are saved in the NE’s data base, and
will be available even if the ODU(s) is/are disconnected.
3–2.3.3 Switching off the IDU(s), and ODU(s) disconnection
Proceed as follows:
a) Close JUSM and stop Supervision on the NE (for details, refer to para.2–2.5.3 on page 184). Leave
PC and CT ready for next operations
b) Switch off IDU (MAIN and, if equipped, EXTENSION)
c) Disconnect the IDU(s) / ODU(s) cables from IDU(s).
3DB 16142 CAAA Ed.01A–DRAFT 371 / 576

3–2.3.4 Powering up the IDU(s) with ODU(s) disconnected

N.B. Make sure that IDU–ODU cable is disconnected from the IDU(s) in order to verify via CT

the System PTx Power and Frequency Tx settings as foreseen by Plant documentation

before powering up the ODU(s).
Since the IDU(s)–ODU(s) connection is not established, when powering up the IDU(s),
the ODU(s) will not be operating and then the IDU(s) will display the relative Alarms.
. After switching on the wall circuit breakers, power–on the Main IDU then the Extension IDU if any
via the front panel power supplies switches.
n The green ”ON” LEDs on both IDUs come on.
On the IDU Main, wait 1 minute for:
n The green “EOW” LED is on.
n The red “LDI” LED is on.
n The red “RDI” LED is on.
Always on the IDU Main, wait another 1 minute for:
n The red “MIN” LED is on
n The red “MAJ” LED is on
WARNING: With a new Flash only LED “ON” is on.
Finally perform a “Lamp Test” by pressing the “LT” pushbutton on IDU(s) in order to verify if the remaining
LEDs are operational.
3–2.3.5 NE login
a) Login again the local Network Element, using the Administrator UserName & Password.
b) Wait for the main Equipment view (CT) to appear.

Note: Since the ODU(s) cables are disconnected, relevant communication alarm is shown.
c) Proceed as described in para.3–2.3.7 point a ) on page 375.

N.B. This is the Interactive Quick Configuration. If you want to use another modality, please
read para.3–2.3.6 on page 373, and proceed according to the configuration procedure you
like.
372 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.6 General on Quick Configuration Procedure
This procedure allows a full system configuration through a guided process, based on a reduced set of
screens. The related windows will be displayed by a “Wizard Tool” according to a specific order.
Notice that:
– it is possible to create, save and recover configuration files having the “.qcml” extension
– to manage configurations (and configuration files) the following options are available:
[1] On–line creation, modification and save of the NE configuration (interactive or not
interactive)
This is done by Craft Terminal, after having logging in the NE.
For the execution of this procedure, refer to para.3–2.3.7 on page 375.
[2] TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of a
provisioning file (not interactive)
By this modality, you do not need to login any NE; its main steps are:
a ) launch the application,
b ) create and check the NE configuration,
c ) save the configuration file ( format is “configuration_name.qcml” ).
This file will be after used to configure the NE (after having logged it) with a simple load
command.
[3] TCO Suite Set–Up Tool: on–line recover, modification and application of a provisioning
file (not interactive)
By this modality, you access one NE, not using the Craft Terminal application, but the TCO Suite
web server; its main steps are:
a ) launch the application and the connection with the target NE,
b ) recover a configuration file “configuration_name.qcml” previously created (e.g. through
the TCO Suite Pre–Provisioning Tool), or get configuration data from the NE
c ) check/modify the configuration,
d ) apply the configuration to the target NE.
WARNING: the execution of the TCO Suite Set–Up Tool is denied to the Viewer operator
profile
N.B. In alternative, through the “TCO Suite’s Alarms & Settings” function (see para.2–2.3 on page
162), it is possible:
– to send a “configuration_name.qcml” configuration file to a NE (Configuration Setting,

see para.2–2.3.3 on page 166)
– to get from a NE its own “configuration_name.qcml” configuration file (Get Configuration

File , see para.2–2.3.5 on page 170)
– to get from a NE its own configuration text Report (Configuration Info , see para.2–2.3.4
on page 167).
3DB 16142 CAAA Ed.01A–DRAFT 373 / 576

3–2.3.6.1 Note on the use of the bottom buttons available in the screens

The bottom buttons available in the screens depend on the configuration tool started, and are

context–specific, e.g.:

– Back: by clicking on this button the procedure goes back to the previous step
– Next: by clicking on this button the procedure goes on the next step
– Finish or Apply to the NE : this button is active only in the last step. By clicking on this button the
operator confirms the configuration and the new parameters are sent to the equipment
– Save As: by clicking on this button, the configuration can be saved as a “configuration_name.qcml”
file (provide a mnemonic name)
– Save & Apply: by clicking on this button, two operations are carried out:
• Save: the configuration and the new parameters are temporarily saved on the system disc N.B.
and then:
• Apply: they are sent to the equipment
N.B. the file is saved under the user “home” directory, inside the TCO SUITE’s temporary file
folder. For example, in Windows XP it is:
[system disc]:\Documents and Settings\[username]\temp_tcosuite.2[xx]\[timestamp]\temp.qcml
Example: D:\Documents and Settings\berenice\temp_tcosuite.217\1164279978890\temp.qcml
– Cancel: by clicking on this button, the procedure goes back to the first screen
– Help: by clicking on this button the operator calls the help–on line
WARNING: the Help button is operative in the CT environment only. It is not operative in the TCO
SUITE environment.
374 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.7 On–line creation, modification and save of the NE configuration
This job can be done by Craft Terminal, after having logging in the NE.
There are two ways to start this application:
a) Interactive mode. To start this application, click on Main Tool Bar’s icon Interactive Quick
Configuration (see Fig. 95. on page 186), or select Configuration ⇒ Quick Configuration ⇒
Interactive mode from the Menu bar.
The window in Fig. 272. on page 379 will appear. This window is the first step of the procedure.
Proceed as specified in para.3–2.3.10 on page 379.
N.B. With this Interactive Quick Configuration, the configurations parameters displayed in
the various steps are taken from those actually stored in the NE data base. You can check
them and modify (if necessary), then go to the following step. The last step is Step L on
page 397. In such a step you can:
• click on Save As button: configuration data are saved in a
“configuration_name.qcml” file (provide a mnemonic name)
• and / or click on Finish button: configuration data are stored in the NE data base.
b) By text file (not interactive)

To start this application, click on Main Tool Bar’s icon Quick Configuration by text file (see
Fig. 95. on page 186), or select Configuration ⇒ Quick Configuration ⇒ By text file from the
Menu bar.
A file selection window opens, requiring a “configuration_name.qcml” file to be opened.
After having selected such a file, the window in Fig. 272. on page 379 will appear. This window is the
first step of the procedure. Proceed as specified in para.3–2.3.10 on page 379.
N.B. With this Quick Configuration by text file, the configurations parameters displayed in the
various steps are not taken from those actually stored in the NE data base. You can check
them and modify (if necessary), then go to the following step. The last step is Step L on
page 397. In such a step you can:
• click on Save As button: configuration data are saved in a
“configuration_name.qcml” file (provide a mnemonic name)
• and / or click on Finish button: configuration data are stored in the NE data base.
3DB 16142 CAAA Ed.01A–DRAFT 375 / 576

3–2.3.8 TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of a
provisioning file (not interactive)

To launch this application, click on the button Pre–Provisioning Tool of the “TCO Suite Main Page” (see

Fig. 64. and Fig. 65. on page 155).
This button is a one–click execution for the Pre–Provisioning Tool. User could see a so–called “splash
screen” (Fig. 266. below), a temporary message that will disappear after 10 seconds or by clicking on it
with the mouse.
Fig. 266. Pre–Provisioning Tool ”splash screen”
Another screen could be shown, in order to give user some details on current execution.
This screen (Fig. 267. below) is a text–based console with detailed information on execution in progress.
This window won’t disappear and can’t be closed by clicking on top–right “X” button or Pre–Provisioning
Tool will be closed too. The window can be minimized by clicking on top–right “–“ button.
Fig. 267. Pre–Provisioning Tool console
As soon as the Pre–Provisioning Tool is ready, the following screen appears:
Fig. 268. Pre–Provisioning Tool start screen
In this screen you can click on button:

– Open configuration : a file selection window opens, requiring a “configuration_name.qcml” file to
be opened. In this case, the configuration process starts from data you have recovered;
– or Create configuration : in this case, the configuration process starts from default data.
In both cases, the window in Fig. 272. on page 379 will appear. This window is the first step of the
procedure. Proceed as specified in para.3–2.3.10 on page 379, checking and modifying data as
necessary. The last step is Step L on page 397. In such a step you can only click on Save As button:
configuration data are saved in a “configuration_name.qcml” file (provide a mnemonic name).
376 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.9 TCO Suite Set–Up Tool: on–line recover, modification and application of a provisioning
file (not interactive)
To launch this application, click on the button Set–Up Tool of the “TCO Suite Main Page” (see Fig. 64. and
Fig. 65. on page 155).
User could see a so–called “splash screen” (Fig. 269. below), a temporary message that will disappear
after 10 seconds or by clicking on it with the mouse.
Fig. 269. Set–Up Tool ”splash screen”
Another screen could be shown, in order to give user some details on current execution.
This screen (Fig. 270. below) is a text–based console with detailed information on execution in progress.
This window won’t disappear and can’t be closed by clicking on top–right “X” button or Pre–Provisioning
Tool will be closed too. The window can be minimized by clicking on top–right “–“ button.
Fig. 270. Set–Up Tool console
Then, User is asked to distinguish between “Direct” or “Remote” connection (Fig. 71. on page 162) and
he/she will be asked to fill the IP address field used to connect to NE.
The difference between “Direct” or “Remote” connection is described in para.2–2.2.6 on page 160.
Then (Fig. 72. on page 163), User is asked to provide the Username and Password [same rules as in point
3 ) on page 183]. In case of remote connection, the NE’s IP address entered in previous screen
(Fig. 71. on page 162) is displayed.
As soon as the Set–Up Tool is ready, the following screen appears:
Fig. 271. Set–Up Tool start screen
3DB 16142 CAAA Ed.01A–DRAFT 377 / 576

In this screen you can click on button:

– Get configuration from NE : in this case, the configuration process starts with data taken from the

NE; this modality is exactly the same you can do by Craft Terminal through the Interactive Quick

Configuration
– or Open configuration : a file selection window opens, requiring a “configuration_name.qcml” file

to be opened. In this case, the configuration process starts from data you have recovered;
– or Create configuration : in this case, the configuration process starts from default data.
In all cases, the window in Fig. 272. on page 379 will appear. This window is the first step of the procedure.
Proceed as specified in para.3–2.3.10 on page 379, checking and modifying data as necessary.
The last step is Step L on page 397. In such a step you can:
– click on Save As button: configuration data are saved in a “configuration_name.qcml” file (provide
a mnemonic name)
– and / or click on Apply to NE button: configuration data are stored in the NE data base.
378 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.10 Quick Configuration Procedure steps
N.B. Following screens do not show the bottom buttons, that depend on the tool by which the
configuration procedure has been started and by the context. For their use please refer to
para.3–2.3.6.1 on page 374.
Step A (Main NE parameter configuration)
Fig. 272. Quick Configuration Procedure: main NE parameter configuration (Step A)
REMIND:
– in interactive modality, this screen is set with values taken from NE’s data base
– in not interactive modality, this screen is set with default values
This step provides a screen to configure the following main NE parameters:
– Site : give mnemonic names for User Label and Location
– NE Parameters Configuration:
• Protection Type : choose between:

– 1+0: unprotected configuration
– 1+1 HSB: Hot Standby protected configuration
– 1+1 FD: Frequency Diversity protected configuration
• Tributary : choose between:

– 16E1: max 16xE1 without Ethernet plug–in
– 16E1–Data: max 16xE1 with Ethernet plug–in
– 32E1: max 32xE1
N.B. the number of actually usable tributaries depends on the employed Software Key
(see Tab. 22. on page 89 )
3DB 16142 CAAA Ed.01A–DRAFT 379 / 576

• if equipped, click on Audio/User Service Channels plug–in

Market : in this SWP version, only ETSI choice is possible

– Structure of the Frame configuration (fields Capacity and Modulation).
The capacity implies the choice of modulation; for example, if the tributary structure is 2E1, only
4QAM modulation scheme is supported.
N.B. The association between Capacity and Modulation is shown in Tab. 65. below:
Tab. 65. Radio application: Market, capacity and modulation
Market Capacity Modulation

2xE1 4QAM
4xE1 4QAM / 16QAM
ETSI 8xE1 4QAM / 16QAM
16xE1 4QAM / 16QAM
32xE1 16QAM
N.B. the actually usable capacity and modulation types depend on the employed Software
Key (see Tab. 22. on page 89 )
N.B. For the Remote NE, parameters belonging to this step cannot be modified.
To modify them the System Settings menu must be used (refer to para. 2–3.4.1 on page 215).
To go to next step click on button “Next”.
WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of the
configuration the “Restart NE” must be performed (refer to para. 2–8.2 on page 160).
380 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step B (Tributary configuration)
REMIND:
This Step B has two sub–steps:

– PDH tributary port configuration, see point [1] below
– Ethernet port configuration, see point [2] on page 383
[1] PDH tributary port configuration

The screen shown in Fig. 273. below provides the fields to set the signal mode (unframed, framed
or disabled) of each E1 port.
Moreover, the Impedance for the E1 tributary also must be selected in the Tributary Port
Configuration (unbalanced 75 ohm or balanced 120 ohm).
Fig. 273. Quick Configuration Procedure Step B: PDH Tributary configuration
By clicking on the one facility button (“All Framed”, “All Unframed” and “All Disabled”), the operator
can configure all the tributaries with the same values; otherwise he can apply all configuration for
each tributary by selecting the related value from the relevant scroll list.
N.B. This procedure can be used also after the first configuration to perform multiple changes
in the configuration both in the local and in the remote NE.
WARNING: Frame Structure (Capacity) Configuration with Ethernet Interfaces

With the Fast Ethernet interfaces (100BASE–T), the PDH transport capability is
always less than the maximum input bit rate, then a compression mechanism is
supported by ULS NE; with the 10BASE–T interface, the PDH transport capability
can be larger or smaller than the maximum input bit rate, according to the number
of tributaries to be transported.
Also when Ethernet signals have to be transported the gross bit rate at the output of
the Mux is defined by the frame structure configuration (capacity).
Obviously, the maximum compression of the data signals is reached when the space
of only one tributary is reserved, the compression decreases if the space or more
tributaries is reserved.
3DB 16142 CAAA Ed.01A–DRAFT 381 / 576

HOW TO OPERATE IN CASE OF CONFIGURATION WITH TWO ETHERNET PORTS (I.E. WHEN
ETHERNET PLUG–IN IS EQUIPPED):

In order to allow the actual configuration and transmission of the Ethernet data streams, it is

mandatory that:
• at least one (*) tributary port is disabled
• and that the position (according to Fig. 273. on page 381) of such disabled tributary port is one
of first four.
N.B. If such operation is not done, no error message is raised by the system (with
exception of “time–out expired”), but the configuration (or the configuration change)
does not correctly take place, and Ethernet data streams are neither configured nor
transmitted.
(*) the allowed number of tributaries is as follows:

Market
– Frame structure configuration: 2 E1
• Number of FE (100BASE–T): ≤2
• Number of PDH (E1) Tributaries: ≤ 1
Example: possible combinations:
• 1 FE, 1 E1 ⇒ 1 FE is compressed in 1 E1 equivalent bandwith;
• 1 FE, 0 E1 ⇒ 1 FE is compressed in 2 E1 equivalent bandwith;
• 2 FE, 1 E1 ⇒ 2 FE are compressed in 1 E1 equivalent bandwith;
• 2 FE, 0 E1 ⇒ 2 FE are compressed in 2 E1 equivalent bandwith.

ETSI • Number of PDH (E1) Tributaries: ≤3

• Number of PDH (E1) Tributaries: ≤7


In the screen displayed in Fig. 273. on page 381 (and in the following Steps), the “Back” button is enabled
also. It allows the operator to turn back and change the parameters configured in the previous screen.
Now, if in Step A (Fig. 272. on page 379) you have defined 16E1–Data, proceed to next sub–step [2] on
page 383. Otherwise:
– to go to the next step click on button “Next”.
– to go back to the previous step click on button “Back”.
382 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[2] Ethernet port configuration
Configuration screens of following Fig. 274. and Fig. 275. appear only if in Step A (Fig. 272. on page
379) you have defined 16E1–Data.

WARNING:
• in screen of Fig. 274. , you can configure the characteristics of each Ethernet port differently
from those of the other one
• in screen of Fig. 275. , you must configure the characteristics of each Ethernet port exactly as
those of the other one; i.e. for Ethernet Ports 1 & 2:
– “Tx–FCS Discard Error Frames” must be both enabled or both disabled
– “Rx–FCS Discard Error Frames” must be both enabled or both disabled
Fig. 274. Quick Configuration Procedure Step B: Ethernet port configuration – basic information
Fig. 275. Quick Configuration Procedure Step B: Ethernet port configuration – discard frames
information
To go to the next step click on button “Next”.

To go back to the previous step click on button “Back”.
Step C (Channel configuration)
REMIND:
– in interactive modality, this screen is set with values taken from NE’s data base [if you are executing
this step inside the commissioning procedure, ODU(s) is/are disconnected, but the relevant
frequency values have been acquired by IDU during operations of para.3–2.3.2 on page 371]
– in not interactive modality, fields of this screen are all empty
This step allows the operator to define the basic parameters for each configured channel. The related
screen (according to the Protection Type set in Step A) is shown in following Fig. 276. :
3DB 16142 CAAA Ed.01A–DRAFT 383 / 576

1+0
1+1 HSB
1+1 FD
Fig. 276. Quick Configuration Procedure: Channels Configuration (Step C)
By this screen, you must set two types of configuration data: frequency data (sub–step [1] on page 385),
and ATPC data (sub–step [2] on page 387), taking into account that, in case of:
– “1+0” and “1+1 HSB” configurations, you must set data for one frequency only
– “1+1 FD” configuration, you must set data for two channels.
384 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[1] Frequency data setting
The system can operate with different types of ODU according to the RF band and to the channel
arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several
predefined shifters (flexible shifter). For details, according to ODU type employed, please refer to
para.1–4.4 from page 99 onwards.
1) Interactive mode
a) ODU with one Shifter only

If the ODU can manage only one shifter the Shifter field in the menu is not available (it is
grey).
In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written
in the Frequency Range field on the right side) and press push–button Next (the Rx
frequency is automatically calculated by using the inserted Tx frequency and the shifter).
b) ODU with different available Shifters

1 ) In the Tx frequency field insert the suitable Tx frequency ...
2 ) ... then, in the Shifter field select the suitable shifter and press push–button Next (the
Rx frequency is automatically calculated by using the inserted Tx frequency and the
shifter).
WARNING: In case of troubles, please refer to point [2] on page 413 for additional
information.
N.B. If necessary, you can exploit the “Frequency Data Help”, described below, in
Interactive mode too.
Note: During the command setting, the CT is frozen. Waiting time: max 30’.
After having set the frequency data, carry out ATPC data setting (next sub–step [2] on page
387). (Note: if you have gone to following Step F, go back to this Step C).
2) Non interactive mode

In the screen of Fig. 276. on page 384, click the “Frequency Data Help” button. The screen of
following Fig. 277. opens.
Fig. 277. Frequency Data Help: choice of ODU type
According to the ODU system to be configured, click on relevant line. The screen of following
Fig. 278. opens.
3DB 16142 CAAA Ed.01A–DRAFT 385 / 576

values used in
example of
Fig. 279. below
Fig. 278. Frequency Data Help: frequency data of chosen ODU type (example)
N.B. The content of these tables is the same of the tables present in:
– para.1–4.4.1 from page 100 (7–8 GHz ODU part lists)
– para.1–4.4.2 from page 103 (13–38 GHz ODU part lists)
Thus, in non interactive mode, use values retrieved from such help–on–line tables to fill the
“Frequency Values” fields of screens of Fig. 276. on page 384.
Fig. 279. below shows an example of Frequency Data manual setting with values taken from
the table of Fig. 278. above.
Fig. 279. Example of Frequency Data manual setting
386 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[2] ATPC data setting
In the Channel Configuration area of Fig. 276. on page 384, the ATPC can be Disabled or
Enabled:
•
if ATPC is disabled, the power (constantly transmitted) can be selected by writing the suitable
value in the Tx power field in the RTPC area (see Fig. 280. below)
• if ATPC is enabled, the RTPC field is greyed (cannot be selected), and the other ATPC
parameters (Max TX Power value, Min TX Power value, and Low Rx Power threshold value)
must be configured in the ATPC area fields (see Fig. 281. below):
– strictly following rules stated in para. 2–6.4 on page 245
– and obviously setting “Max TX Power value” > “Min TX Power value”.
WARNING: if you want to set the minimum value of the range greater than the current
maximum value, you must at first change the maximum value, then change the
minimum value (obviously setting it smaller than maximum)
Fig. 280. RTPC setting with ATPC disabled
Fig. 281. Setting of enabled ATPC

3DB 16142 CAAA Ed.01A–DRAFT 387 / 576

Step D (Link Identifier configuration)

The amount of microwave links, especially in urban areas, puts the problem of possible interferences

during installation and turn–on phase.

The digital frame incorporates link identity coding capabilities to prevent the capture of an unwanted signal.
Link identifier management can be:
– enabled selecting the choice Mismatch Detection in the screen of Fig. 282. below
– or disabled de–selecting it.
In case of enabled Link identifier management, it is necessary to provide the NEs with the suitable sent
and expected link identifiers values. The NE originating the section inserts the sent identifier. The NE
terminating the section extracts the received identifier and compares this value to the expected one.
received identifier = B ⇐ ⇐ sent identifier = B

sent identifier = A ⇒ ⇒ received identifier = A
STATION A STATION B
When the mismatch detection is enabled and the value of the incoming identifier is different from the
expected one, a Link Identifier Mismatch (LIM) is notified and an AIS signal will be inserted down stream.
Link identifier functionality is managed per NE: in case of 1+1 radio configurations the same link identifier
code is used on both the radio channels.
Link identifier functionality is performed by 5 bits link code, then 32 values link code are allowed.
Fig. 282. Quick Configuration Procedure: Link Identifier configuration (Step D)
388 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step E (Automatic restoration criteria configuration)
REMIND:
This step (Fig. 283. below) appears only if any 1+1 configuration has been defined in step A. It allows the
operator to choose the restoration criteria (revertive or not revertive) for the 3 possible protections
available in the 1+1 configuration:
– Radio Protection (Rx RPS–Hitless Switch)
– Mux/Demux Protection (Tx/Rx EPS)
– HSB Tx Protection (RF Hot Stand–by)
Fig. 283. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E)
To go to the next step click on button “Next” .
3DB 16142 CAAA Ed.01A–DRAFT 389 / 576

Step F (OSPF area configuration)

REMIND:


WARNING FOR NOT INTERACTIVE MODALITY:
if OSPF data are already defined in the NE’s data base, when the file is downloaded to the NE,
OSPF data defined in this procedure do not overwrite those present in the NE’s data base. The
only way to change such data is to use the interactive modality.
This step (Fig. 284. below) allows to configure one or more OSPF Areas (3 areas max.).
Fig. 284. Quick Configuration Procedure: OSPF Area Configuration (Step F)
WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0
To create a new area write a number in the Area Id field, in the IP address field write the address and click
on Add button.
If the OSPF area must be a stub area, make the selection in the Stub Area check box.
WARNING: When the area is a Stub area, all interfaces inside the same Stub Area (NMS and
Ethernet) must be defined “Stub”.
In the upper part of the screen the new OSPF area will appear.
To remove or change an OSPF Area Configuration select the Area in the upper part and click on Remove
or Change button.
390 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step G (Configuration of Local IP address, Ethernet and Network Time Protocol)
REMIND:
Fig. 285. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step G)
This step (Fig. 285. above) allows to configure:

– with reference to Fig. 83. on page 174:
• the Local IP address associated to the F interface of the NE. This address is that used to identify
the NE as far as the RECT function is concerned.
• the Ethernet interface: it can be Enabled or Disabled by ticking the TMN Ethernet field (default
is Enabled). If enabled, enter in the relevant fields the IP address, the IP mask and select the
Routing protocol. If the selected routing protocol is OSPF, select also the area number in the
associated OSPF Area field.
WARNING: please do never use the RIP choice present in the Routing Protocol field!
Rules for the definition of the NE’s Local IP and Ethernet IP addresses:
– as delivered from Alcatel–Lucent Factory, the NE’s Local IP and Ethernet IP addresses
are both set at default value “10.0.1.2” ;
– obviously, these values must be changed to have them different from each other and from
those of the other NEs present in the accessible network. In particular such two addresses
must not belong to the same subnetwork (i.e. the third digit must be different. Examples:
• wrong definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.1.3
• correct definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.2.3
with IP Mask = 255.255.255.0
– the Network Time Protocol (NTP). To enable the NTP put a tick in the check box of the NTP field.
If the NTP has been enabled, write in the Main Server field the IP address of the Server, which
distributes the NTP, and write in the Spare Server field the IP address of the Spare Server, if any,
which will distribute the NTP in case of failure in the Main Server.
N.B. It is mandatory to define both the Main Server address and the Spare Server address.
In case a Spare Server is not available, fill its address field with the
same value of the Main Server.
3DB 16142 CAAA Ed.01A–DRAFT 391 / 576

Step H (Configuration of TMN–RF, TMN–V11 and TMN–G703 channels)

REMIND:


Fig. 286. Quick Configuration Procedure: Configuration of TMN–RF, TMN–V11 and TMN–G703
channels (Step H)
This step (Fig. 286. above) allows to configure the following TMN channels:
– the “TMN–RF” interface is a communication interface based on the use of an in–frame RF proprietary
64 kbit/s channel. Through this interface the NE can exchange management messages with a remote
OS (or Craft Terminal) station.
– through the “TMN–V11” or the “TMN–G703” interface the NE can exchange management messages
with an OS (or Craft Terminal) in the same station.
Each TMN channel can be Enabled or Disabled by selection in its own Enable field.
If enabled, in the Remote Address field will appear the IP address of the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the
associated OSPF area.
In the Mode field of the “TMN–V11” and “TMN–G703” interfaces the following selections can be made:
– DTE mode:
to interface an SDH service channel, where DCE mode is not available because of the common
synchronization of the SDH network.
– Co–directional mode:
to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.

392 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step I (IP Static Routes Configuration)
REMIND:
This step (Fig. 287. below) configures one or more Static Routers.
Fig. 287. Quick Configuration Procedure: IP Static Routes Configuration (Step I)
[1] Host Address: allows to define the IP address necessary to reach a specific Host.
[2] Network Address: it is in alternative to the Host Address; allows to define the IP Mask to reach
a network.
[3] Gateway Address: allows to define the address of the next hop gateway.
[4] PPP: it allows to use the point to point interfaces (the 3 NMS channels) available
with the NE.
WARNING: No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.
3DB 16142 CAAA Ed.01A–DRAFT 393 / 576

N.B. Default Gateway Routing configuration

It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 287. on page

393 select Network Address. The screen changes to following Fig. 288. :

REMIND:
• in interactive modality, this screen is set with values taken from NE’s data base
• in not interactive modality, fields of this screen are all empty
Fig. 288. Quick Configuration Procedure: Default Gateway Routing configuration (Step I)
In this screen operate as follows:
a) in IP Address field, write 0.0.0.0
b) in IP Mask field, write 0.0.0.0
c) in Default Gateway IP Address field, write the required destination
d) click Add
394 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step J (EOW and Auxiliary Interface Configuration)
REMIND:
– in not interactive modality, fields of this screen are with default values
This step (Fig. 289. below) appears only if the Audio/User Service Channels plug–in configuration has
been defined in step A. It allows the operator to choose:
– the Phone Number for the EOW function (see chapter 4–2 on page 453 for details)
– the Auxiliary Interface Type
Fig. 289. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J)
3DB 16142 CAAA Ed.01A–DRAFT 395 / 576

Step K (External Input and Output Points Configuration)

REMIND:


This step (Fig. 290. below) configures the external points (please refer to para.1–3.5.1 on page 81 for
physical implementation).
Fig. 290. Quick Configuration Procedure: External Input and Output Points configuration (Step K)
For:
– both Inputs and Outputs:

• clicking in the Polarity field, Active Closed or Active Opened can be chosen
– Outputs only:
• clicking in the Working Mode field, Manual or Automatic can be chosen;
if Manual is chosen, you can select the Associated Event clicking in the relevant field
396 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Step L (Summary)
This is the last step (Fig. 291. below). The screen shown summarizes all the parameters configured during
this procedure and some relevant parameters with default values.

Fig. 291. Quick Configuration Procedure: Summary (Step L)
All the parameters can still be changed by clicking on the “Back” button. The operator can navigate back
to the desired screen and set the new values.
According to the configuration tool started, at the end the operator can:
– click on Save As button: configuration data are saved in a “configuration_name.qcml” file (provide
a mnemonic name)
– and/or confirm the selections by pressing the Finish or Apply to NE or Save & Apply button. All the
parameters are stored and sent to the NE.
At the end of the NE updating, a summary of the values of all the parameters are shown to the
operator with the indication of the result of each request of change (OK or error message).
An indication of the parameters remained unchanged is provided too.
WARNING: in case of problems regarding the Shifter Value and/or the Central Frequency , that
could result in one of the following error message:
– Shifter Value KO OK
– Central Frequency OK KO
you must go back to point [1] (Frequency data setting) on page 385 and check and
correct both values, not only that declared KO.
– or do none of such operations, clicking on Cancel.
If you are inside the commissioning procedure, obviously you must have defined a correct configuration.
In this case proceed with next para.3–2.3.11.
3DB 16142 CAAA Ed.01A–DRAFT 397 / 576

3–2.3.11 Powering UP the IDU(s) with the ODU(s)

After the completion of the configuration step, switch Off the IDU(s) in order to re–establish the

IDU–ODU(s) connections.

Then, switch on the IDU(s), log in the NE and proceed to the following checks:
3–2.3.11.1 Verify ODU(s) alarm status
Purpose: Verify no abnormal communication alarm between IDU(s) and ODU(s)
Required Instruments: PC with Craft Terminal software
Procedure: Connect CT to IDU
. CT ⇒ Views ⇒ Equipment
→ In the left window, select ODU ch#1
n In the lower right window, verify in the alarms list for that there is no internal communication failure
n In the lower right window, verify in the alarms list that that there is no TX failure.
z Repeat for Ch#0 if any (1+1)
Fig. 292. ODU(s) alarm status
398 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.3.11.2 Transmitter power output check
Purpose: Verify via CT the ODU(s) transmitted power output.

. CT ⇒ Views ⇒ Radio
→ From the left window → select Channel #1
→ From the lower right window → select RTPC & ATPC tab panel
n Verify that ATPC is ”Disabled” as already set during the quick step procedure
(If required, change the ATPC status to disable in the ATPC field then → Apply)
n Verify that Tx Power value complies with the suitable value already set via the quick step procedure.
(If required, change the Tx Power in the RTPC field then → Apply)
Fig. 293. Transmit power check
3DB 16142 CAAA Ed.01A–DRAFT 399 / 576

3–2.3.11.3 Received power measurement

Purpose: Verify via CT the received power to detect any interference

→ From the lower right window → select “Power Meas” tab panel
→ In the Sample time (sec), write the suitable measurement poling time then press → Start
Fig. 294. Received power check
400 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels:
Ticking the box “show details” in the lower left corner will call a summary view of the TX an Rx levels:
Fig. 295. Received power details
n Verify that the current Rx local End received level is < –95 dBm (no interferences)
WARNING:
– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the
of the supervision is given by a broken red icon in NES screen.
3DB 16142 CAAA Ed.01A–DRAFT 401 / 576

3–2.4 Commissioning of STATION B – phase 1 (Turn up)

– To commission station B, perform the same operations carried on at station A–Phase 1 (para.3–2.3

on page 370).

– When Station B is fully configured and operational, and assuming that the antenna in station A has
been previously correctly pointed, you should receive some field from station A. In this case, proceed
to a fine tuning of the antenna to improve as much as possible the received level.
To monitor the received level during alignment, use the Craft Terminal received power measurement
facility described in para.3–2.3.11.3 on page 400, or the Light service kit cable for ODU Rx power
monitoring in addition to a voltmeter (see description in Annex A: antenna alignment on page
443).
– For near future tests, establish on the Station DDF hardware loops on every tributary as well as on
the User service channel.
READ THIS GENERAL INFORMATION ABOUT TEST BENCH DRAWINGS
In the test bench drawings depicted in the following, take always account that:
1) the standard equipment interfaces for access points are in most cases considered at Station
DDF, in turn connected to the line–side connectors of the E1 Protection box and of the
Services Protection box.
Station DDF is not detailed in the drawings: refer to your own plant documentation for details.
For detailed information on the:
– description of equipment interconnections (between such protection boxes and the IDU
Main and Extension units), please refer to para.3–2.2 on page 363 , making reference to
the equipment interconnection diagram corresponding to your actual system layout.
– description of connector pin–out of the:
• E1 Protection box, please refer to para.1–3.4 on page 75
• Services Protection box, please refer to para.1–3.5 on page 80
2) the Craft Terminal (CT) is always necessary.

The connection between CT and NE can be done in two alternative ways (see Fig. 83. on page
174):
– trough a cross–connect Ethernet cable between the Ethernet port of the PC and the
Ethernet interface on the Main IDU
– or trough a RS232 cable between the serial port of the PC and the “F” interface (ECT) on
the Main IDU.
3) the additional material for (1+1) configurations is drawn in dotted line.
402 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.5 End of commissioning phase 1 (Turn up) in STATION A
– In Station A, proceed to a final fine alignment of the antenna. To monitor the received level during
alignment, use the Craft Terminal received power measurement facility described in para.3–2.3.11.3
on page 400, or the Light service kit cable for ODU Rx power monitoring in addition to a voltmeter
(see description in Annex A: antenna alignment on page 443).
Verify in the hop calculation that the calculated received level has been reached.
– Proceed to the remote NE (station B) acquisition in the Craft Terminal map (described in following
para.3–2.5.1) in order to verify in the both stations:
n Received level complies with hop calculation
n No alarm showing (except unloaded tributaries)
3–2.5.1 Remote NE (station B) acquisition on craft terminal
. Connect the cable between the serial port of the PC and the “F” interface (ECT) on the Main IDU.
. Start the “1320 CT” application.
n Wait until the NES window appears, for the LLMAN to connect and the “Map” indicator to turn grey.
Right click on Station A NE icon and select “Start supervision”, or ⇒ Supervision → Start
n The question mark in the NE icon disappears while the alarm status of the NE appears.
Fig. 296. NES window local NE
3DB 16142 CAAA Ed.01A–DRAFT 403 / 576

z Right click on the first line “Map “sample”” (or click on “Map sample” and select “NE Directory”) and
choose “create SNMP NE”. The following window will prompt

Fig. 297. Create NE in the CT map
→ Write the local IP address of Station B in the TCP/IP Address field and the port number in the
TCP/IP Port field (typically: 161), then click OK.
The newly created NE will appear in the CT map as shown below.
. Right click on Station B NE icon and select “Start supervision”, or ⇒ Supervision → Start
Fig. 298. NMS Radio side Remote NE acquisition
N.B. The above remote NE acquisition is described assuming that the TMN–RF access have been
enabled in both Stations during Quick Configuration Procedure – step H on page 392. On
the contrary, the TMN–RF channel can be enabled directly through the CT menu:
. CT ⇒ Configuration ⇒ Network Configuration → IP configuration → IP point to point configuration.
404 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.5.2 Testing configurations for hop quality check
Interfacing with the E1 Protection box, set up the following testing configuration and run on one tributary,
through the hardware loopback previously established in station B, a minimum of one hour BER test free
of error.
Remote station ODU
ODU
IDU MAIN
IDU MAIN
“Tributary loopback”
E1
ERROR
ANALYZER
Fig. 299. Test bench for tributary quality test

Interfacing with the Services Protection box, set up the following testing configuration and run on the
User service channel, through the hardware loopback previously established in station B, a minimum of
10 minutes BER test free of error.
Remote station ODU
ODU
IDU MAIN
ESC
IDU MAIN
“ESC loopback” ESC
DATA
ANALYZER
G.703 or V11
Fig. 300. Test bench for User service channel quality test
N.B. In case of V.11 the loopback on the remote station cannot be performed. In this case two data
analyzer must be used.
3DB 16142 CAAA Ed.01A–DRAFT 405 / 576

3–2.6 Commissioning station A – phase 2 (acceptance test)

Commissioning phase 2 is a site acceptance test procedure made up of the required tests to ensure that

the equipment is fully operational.

This phase describes first of all the way to check and to change (if necessary) via the Craft Terminal menu
the different configuration parameters already set, for most of them, during the Quick Configuration
Procedure in phase 1, followed by various tests.
Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet ; see Tab. 64. on
page 362). Operator will be invited to do so each time it is required by the following sentence: “Report
… into the TRS.”
3–2.6.1 System Installation and cabling visual inspection
3–2.6.1.1 Indoor System installation and cabling inspection
See and fill the indoor inspection check list in the TRS.
3–2.6.1.2 Outdoor System installation and cabling inspection
See and fill the indoor inspection check list in the TRS.
3–2.6.2 Local configuration control
Purpose: Verify via CT the Local Station configuration.
3–2.6.2.1 Check software key code
. CT ⇒ Supervision ⇒ SW key
Fig. 301. Software Key code view
Report the SW Key number and code into the TRS

→ Close.
406 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.2.2 Check/set the NE parameters and frame Configuration
. CT ⇒ Configuration ⇒ System Settings

Report the Type, Market, Capacity, Modulation and Impedance into the TRS
→ Close.
Fig. 302. NE parameters and Frame configuration view
N.B. If required, change each parameter in the relevant scroll list then → Apply.
For any change concerning Type, Market, Capacity and modulation, operator will be invited to
confirm or deny his choice in the warning window shown below:
“Impedance” change will be applied without any warning.
3DB 16142 CAAA Ed.01A–DRAFT 407 / 576

3–2.6.2.3 Check/set E1 tributaries configuration
. CT ⇒ Views ⇒ Line Interface

In the left window → E1 port# 1
In the lower right window → “Configuration” Tab panel.
Repeat for each E1 port#
N.B. If required, change each parameter in the relevant scroll list then → Apply
RAI insertion feature is operating only in “framed” signal mode. “Enabled” is the automatic mode
(default value), “forced” the manual insertion mode.
Fig. 303. E1 tributary configuration view
408 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.2.4 Check/set User Ethernet interface parameters (Optional)

In the left window → Ethernet Port#17 or Ethernet Port#18
In the lower right window → “Configuration” Tab panel.
N.B. If required change any parameters then → Apply
In the lower right window → “Auto–Negotiation” Tab panel.
Fig. 304. Automatic restoration criteria configuration view
3DB 16142 CAAA Ed.01A–DRAFT 409 / 576

3–2.6.2.5 Check/set the automatic restoration criteria (only 1+1)
. CT ⇒ Views ⇒ Protection Schemes

In the left window → Radio Protection (RPS)
In the lower right window → Schema Parameters Tab panel → Protection Type 1+1
Repeat for HSB TX Protection and Mux/Demux Protection.
Report the Operation Type for each protection level into the TRS
N.B. If required, change Operation type (Revertive or Not Revertive) then → Apply
In “Revertive” Operation, after an abnormal condition such fading, hardware problem or maintenance
action, the relevant protection will automatically switch back to channel #1 as a default state.
To read the correct indication on the switch status

press here to refresh the screen
Fig. 305. Automatic restoration criteria configuration view
410 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.2.6 Check/set the Rx static delay configuration for radio protection (1+1 only)
. CT ⇒ Views ⇒ Protection Schemes

In the left window → Radio Protection
In the lower right window → “Rx Static Delay” Tab panel → press Auto (default value)
N.B. If required, change to Manual Operation → set suitable values for channel 0 and 1 then → Start
The Rx static delay adjustment function is to recover the delay that may exist between the two channels
frames due to a cable length difference. Manual operation range is 0 to 31 bits.
Fig. 306. Rx Static delay configuration view
3DB 16142 CAAA Ed.01A–DRAFT 411 / 576

3–2.6.2.7 Check/set TX and RX frequencies

In the left window → Channel #1
In the lower right window → “Frequency” Tab Panel
Repeat for Channel 0 (only in 1+1)
Report the TX and the RX frequencies into the TRS

N.B. If required, change the Tx frequency then → Apply. Rx Freq. will be automatically adjusted.
Fig. 307. Tx and Rx frequencies configuration view
The system can operate with different types of ODU according to the RF band and to the channel
arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefined
shifters (flexible shifter).
412 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[1] ODU with one Shifter only
If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).
In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the
Frequency Range field on the right side) and press push–button Apply (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
Note: During the command setting the CT is frozen. Waiting time: max 30’.
[2] ODU with different available Shifters

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

To restore a ”Standard Shifter” configuration, the operator has only to apply again the selected (or
another one) Shifter value or to apply again the Tx frequency.
As result, the normal Frequency screen is restored removing both red color as background of the
Shifter field and the specific warning message.
Note: During the command setting the CT is frozen. Waiting time: max 30’.
3DB 16142 CAAA Ed.01A–DRAFT 413 / 576

3–2.6.2.8 Check/set TX power (ATPC Off ) or Tx range and Rx threshold (ATPC On)

ATPC Disabled:


In the lower right window → “RTPC&ATPC” Tab Panel
n ATPC “Disabled”
Report the ATPC “Disabled” status, Tx nominal Power and Tx Power setting into the TRS
ATPC Enabled:
In the lower right window → RTPC&ATPC Tab Panel
n ATPC “Enabled”
Report the ATPC “Enabled” status, ATPC Range and ATPC RX Threshold setting into the
TRS
N.B. If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then → Apply
Static delay of the Tx power Dynamic value of the Tx power

(30 dB range) (20 dB range
Fig. 309. ATPC mode configuration view
414 / 576 3DB 16142 CAAA Ed.01A–DRAFT

WARNING: In 1+1 Configuration (HSB or FD) the ATPC information, sent back from the Rx side to Tx
side, is the information relevant to the channel (protecting or protected) currently active in the EPS
protection scheme. The two transmitters are, therefore, driven by the same ATPC control signal.
WARNING: During the reconfiguration phase or during the activation of a new software the
alarm“ATPC loop” is active.
3–2.6.2.9 Check/set the User data channel type and the station phone number
. CT ⇒ Configuration ⇒ System Setting → “Overhead” Tab Panel
Report the auxiliary interface type and the Phone number into the TRS
→ Close
N.B. If required, Change Phone Number (between 10 and 99) or Auxiliary interface type then →
Apply
Fig. 310. Overhead configuration view
3DB 16142 CAAA Ed.01A–DRAFT 415 / 576

3–2.6.2.10 Check/set the local NE IP address
. CT ⇒ Configuration ⇒ Network Configuration → Local Configuration

Report the local IP Address in the TRS
Fig. 311. Local IP address configuration view
N.B. If required, change the local IP Address then → Apply
3–2.6.2.11 Check/set OSPF Area Configuration
. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → OSPF Area Configuration
Report the Id, IP Address, IP Mask and Stub flag into the TRS
N.B. If required, Add a new OSPF Area by → create → OK or to remove an existing one, select it
in the upper list then → Delete → Yes
Fig. 312. OSPF configuration view
416 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.2.12 Check/set the NMS IP point to point interface configuration
. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Point to Point Configuration

Report the mode, IP Routing, OSPF Area and Remote Address for Enabled connection into the
TRS
Fig. 313. NMS IP point to point configuration view
N.B. If required, enable or disable RF, V11 or G703 NMS access then → Apply. Then, wait for the
following confirmation window:
→ Click OK to close the window.
3DB 16142 CAAA Ed.01A–DRAFT 417 / 576

3–2.6.2.13 Check/set the Ethernet access (OS) configuration

The Ethernet interface (OS) can be used to connect a Craft terminal as an alternative to the “F” interface

(ESC), or more generally to connect the NE to any IP Network.

. CT ⇒ Configuration ⇒ Network Configuration → Ethernet Configuration
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area into the TRS
N.B. If required, Enable or Disable the Ethernet connection or change any parameter then → Apply
By default, use the same IP address as the one used for the NE local IP address.
Fig. 314. (OS) Ethernet access configuration view
418 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.2.14 Check/set IP static routing configuration
. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Static Routing Configuration

Report the IP Address, IP Mask and Default gateway IP Address or interface type into the TRS
N.B. If required, add a new static route by → create → write the different parameters then → OK or
to remove an existing route, select it in the upper list then → Delete → Yes.
Fig. 315. IP static routing configuration view
3DB 16142 CAAA Ed.01A–DRAFT 419 / 576

3–2.6.3 Channel 1 functionality tests (1+0 and 1+1)

Open the “summary Block diagram view” for all the duration of Channel 1 functionality tests in order to

visualize at any time the Switching and Loopback status of the microwave:

Purpose: Display the summary block diagram
. CT ⇒ Diagnosis ⇒ Summary Block Diagram View
Fig. 316. 1+0 Summary block diagram view
420 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Fig. 317. 1+1 Summary block diagram view
– An active loopback is indicated by a yellow letter:

L
– Switching status are displayed through different dynamic drawings:
If any indication does not correspond to the expected one, press “Refresh” to actualize the view.
By clicking on a specific object of the drawing, the operator can navigate to the relevant CT menu view.
3DB 16142 CAAA Ed.01A–DRAFT 421 / 576

3–2.6.3.1 Channel protection switching configuration (1+1 only)

Purpose: lockout the channel 0 for all the duration of the channel 1 testing

. CT ⇒ Diagnosis ⇒ Protection Schemes
In the left window → Radio Protection → Spare #0
In the lower right window → Commands scroll list → Lockout → Apply
Repeat for HSB Tx Protection and Mux/Demux Protection
n Check in the summary block diagram that the full channel 1 (TX and RX) path is in service.
Report about the Channel 1 protection switching functionality into the TRS
Fig. 318. Channel 0 lockout mode
422 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.3.2 Near End Loop back functionality
Purpose: Verify via CT the near end loopback functionality

Required Instruments: PC with Craft Terminal software and E1 Data Analyzer

Connect Data analyzer on one Tributary Access (At the Station DDF)
– Four different near end Loopbacks have to be performed one by one. Remove previous loopback
before proceeding with the next one. A delay up to 10 seconds may be observed for each
activation/deactivation.
– Ensure that the local tributary access (used to control via the data analyzer the continuity and the
quality of every loopback) is active (framed or unframed) (see para.3–2.6.2.3 on page 408 for more
details about tributaries configuration)
– Ensure that the local transmitter is not muted. (see para.4–5.9.10 on page 488 for more details about
TX Mute functionality)
IDU ODU
A
N
MUX T
TRIB DEMUX MODEM RF E
E1 1 2 3 4 N
N
A
(1) Near End Tributary Loopback Point
(2) Near End IDU Cable Loopback Point
(3) Near End ODU Cable Loopback Point
(4) Near End RF Loopback Point
Fig. 319. Near End loopbacks points
3DB 16142 CAAA Ed.01A–DRAFT 423 / 576

. CT ⇒ Views ⇒ Loopback
In the left window →Tributaries → TX port# NE (select tributary on which the Data Analyzer is connected)

In the lower right window → Activate → Apply

n Data analyzer showing no errors
n Loopback showing in the summary block diagram view
In the lower right window → Deactivate → Apply
Report about the near end Tributary loopback functionality into the TRS
Fig. 320. Loopback control in the CT

In the left window → Channel #1 → IDU Cable
Repeat for ODU Cable and RF
Report about the near end IDU Cable, ODU Cable and RF loopback functionality into
the TRS
424 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.3.3 Far End Loop back functionality
Purpose: Verify via CT the Far end loopback functionality


– One Far end loopback has to be performed under the same condition as the near end loopbacks.
Moreover, ensure that the remote transmitter like the local transmitter is not muted.
IDU ODU ODU IDU

A A
N N
T T MUX
E E RF MODEM DEMUX TRIB
E1 N N
1 E1
N N
A A
STATION A STATION B
Fig. 321. Far End loopback point
In the left window → Tributaries → TX port# FE (select the same tributary # that the one which is locally
connected to the data analyzer)
WARNING: A far end loopback can be removed only from the NE that activated it.
Report about the Far end Tributary loopback functionality into the TRS
3DB 16142 CAAA Ed.01A–DRAFT 425 / 576

3–2.6.3.4 Tributary functionality test

Purpose: Verify the point to point Tributaries quality

Verify the tributaries alarm status monitoring functionality


Connect Data analyzer on Tributary Access (At the Station DDF)
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN IDU EXTENSION
N.B. IDU MAIN
“Tributary loopback” N.B.

E1
ERROR ANALYZER
PATTERN GENERATOR
N.B. the diagram indicates the “loopback” (at remote station) and the connection (at local station)
for the first 8 E1 tributaries. To check the other ones chenge connections.
Fig. 322. Test bench for tributary functionality check
426 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Assuming that all the tributaries have been enabled (Unframed status) via CT in both stations and that
every tributary are looped at the DDF in the remote station:
z Perform one minute of BER test on each E1 tributary

n Verify that the analyzer detects no error.
n Verify on CT “Line Interface” view the tributary alarm status:
In the lower right “Alarms list”, verify that while the data analyzer is connected, the “AlarmLossSignal” on
the relevant tributary goes off.
Note: Check also the framed tributaries (if required).
Fig. 323. Tributary alarm status monitoring
Report about the Tributary BER test and alarm CT monitoring into the TRS.
3DB 16142 CAAA Ed.01A–DRAFT 427 / 576

3–2.6.3.5 Service data channel functionality test

Purpose: Verify the point to point Service Data Channel quality

Required Instruments: PC with Craft Terminal software and G703 / V11 64 Kbit/s Data Analyzer

Connect Data analyzer on the service channel Access (At the Station DDF)
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
ESC
IDU MAIN
ESC
“ESC loopback”
DATA
ANALYZER
64kbit/s (G.703 or V11)
Fig. 324. Test bench for User Service Channel functionality check
Assuming that the User service Channel is looped at the DDF in the remote station:
z Perform 10 minutes of BER test.
n Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRS
428 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.3.6 Ethernet Data channel (optional) functionality test
Purpose: Verify the point to point Ethernet Data Channels quality

Required Instruments: PC with Craft Terminal software and Ethernet Data Analyzer

Connect Data analyzer on Main IDU Ethernet Access.
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
IDU EXTENSION
“Ethernet loopback”
ETHERNET DATA
ANALYZER
Fig. 325. Test bench for Optional Ethernet Data Channel functionality
Assuming that the Two Ethernet Data Channels are looped in the remote station:
z Perform 10 minutes of BER test on both Optional Ethernet access.
n Verify that the Data analyzer detects no error.
Report about the Ethernet Data Channels BER test into the TRS.
3DB 16142 CAAA Ed.01A–DRAFT 429 / 576

3–2.6.3.7 Ptx and Prx measurement

Purpose: Verify via CT the Transmitted (Ptx) and received (Prx) power

. CT ⇒ Views → Radio
→ From the lower right window → select “Power Meas” tab panel
→ In the Sample time (sec), write the suitable measurement poling time then press → Start
Fig. 326. Power measurement view
Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels:
430 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Ticking the box “show details” in the lower left corner will call a summary view of the TX an Rx levels:
Fig. 327. TX and RX power details view
Report the Current Tx Local End (Ptx) and the current Rx Local End (Prx) into the TRS.
WARNING:
– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the
of the supervision is given by a broken red icon in NES screen.
3DB 16142 CAAA Ed.01A–DRAFT 431 / 576

3–2.6.3.8 Inside hop Engineering Order Wire functionality test (optional)

ODU

Remote Station
ODU ODU
EXTENSION
MAIN ODU
EXTENSION
MAIN TPH
OFF ON
EOW
1 2 3
4 5 6
7 8 9
* 0 #
OFF ON
Fig. 328. Engineering order wire organization
Make a call from local station:

1. Check that the line is free (green EOW LED is on).
2. Handset OFF/ON switch to ON.
3. On keypad, press # to engage line.
4. Check that yellow EOW LED on MAIN IDU is on (as well as in the remote station)
5. On keypad, dial the two–digit remote station number or 00 for general call.
6. Ring tone is audible in the handset.
In the remote station:

7. Yellow EOW LED is flashing and the IDU is emitting a ring tone.
8. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.
Switch off the handsets in both stations to finish the call.
Report about the Order wire functionality into the TRS.
432 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.4 Channel 0 functionality tests (1+1 only)
3–2.6.4.1 Channel protection switching configuration

Purpose: Forced the channel 1 for all the duration of the channel 0 testing
. CT ⇒ Diagnosis ⇒ Protection Schemes
In the left window → Radio Protection → Main#1
In the lower right window → Command scroll list → Forced → Apply
Repeat for HSB Tx Protection and Mux/Demux protection
n Check in the summary block diagram that the full channel 0 (Tx and Rx) path is in service.
Report about the Channel 0 protection Switching functionality into the TRS
Fig. 329. Channel 1 forced mode
Note : The “Forced” command for channel 1 is equivalent to the “Lockout “ command for the channel
0. In both case, the result is that the relevant channel protection path is forced to standby status.
3DB 16142 CAAA Ed.01A–DRAFT 433 / 576

3–2.6.4.2 Near End Loop back functionality

Repeat the same test already performed for channel 1. Report the results into the TRS.

3–2.6.4.3 Far End Loop back functionality
3–2.6.4.4 Tributary functionality test
3–2.6.4.5 Service data channel functionality test
3–2.6.4.6 Ethernet Data channel (optional) functionality test
3–2.6.4.7 Ptx and Prx measurement
3–2.6.4.8 Inside hop Engineering Order Wire functionality test
434 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.5 Hop stability test
Purpose: Verify the Hop stability


– The Hop stability test is performed during two consecutive hours, one time, on one Tributary, in real
working condition whatever the protection configuration (1+ 0 or 1+1).
– The two hours stability test must be free of error in normal propagation conditions (out of fading
period)
z Via the CT, let only one active tributary in both station
z In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).
z In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the “Tributary
Alarm Loss” disappears.
n Verify in both stations that there are no active software loopbacks or switching requests
n Verify in both stations that none alarm is showing.
Report the two hours free of error test result into the TRS.
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
“Tributary loopback”
E1
ERROR ANALYZER
PATTERN GENERATOR
Fig. 330. Test bench for hop stability test
3DB 16142 CAAA Ed.01A–DRAFT 435 / 576

3–2.6.6 NE integration tests

3–2.6.6.1 NMS Radio side acquisition

Purpose: Verify Via CT the remote NE RF side acquisition
NE Radio side acquisition has been already performed during the Turn Up (commissioning – phase 1).
Refer to para.3–2.5.1 on page 403 for more details.
3–2.6.6.2 NMS Line side acquisition (if foreseen in the plant documentation)
Purpose: Verify Via CT the remote NE line side acquisition

Toward station B Direction 2
ODU ODU
Local Station (Station A)
IDU MAIN – facing station B
V11 or G703
IDU MAIN – Direction 2
Fig. 331. Test bench for NMS Line side acquisition
N.B. A transfer cable must be placed between the G703 or V11 connectors of the two Services
Protection boxes.
On both IDUs, the NMS line side access must be enabled:
. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Point to Point Configuration
→ Select V11 interface or G703 interface (depending of the transfer cable used) and the required routing.
→ Select enable → Apply
The IP address of the line side remote NE should appear in the remote address field.
436 / 576 3DB 16142 CAAA Ed.01A–DRAFT

z Connect the CT to the IDU facing Station B
. Start the “1320 CT” application.

. Right click on each NE icon and select “Start supervision”, or ⇒ Supervision → Start
Since the NMS RF side NE acquisition has already been performed, both local and remote NE of the hop
currently under commissioning are visible.
Fig. 332. NES window local NE
z Right click on the first line “Map “sample”” (or click on “Map sample” and select “NE Directory”) and
choose “create SNMP NE”. The following window will prompt
Fig. 333. Create NMS Line side NE in the CT map
→ Write the local IP address of Main IDU direction 2 in the TCP/IP Address field and the port number
in the TCP/IP Port field (typically: 161), then click OK.
3DB 16142 CAAA Ed.01A–DRAFT 437 / 576

The newly created NE (direction 2) will appear in the CT map as shown below.
Right click on “direction 2” NE icon and select “Start supervision”, or ⇒ Supervision → Start

.

Fig. 334. NMS Line side NE monitoring in the CT map
Check that “Direction 2” NE responds correctly to supervision:
. Right click on the NE icon and select “Show equipment”, or ⇒ Supervision → Show equipment
Report about the NE line side acquisition functionality into the TRS.
438 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.6.6.3 EOW line side call (if foreseen in the plant documentation)
Direction 1 Direction 2
ODU ODU
Local Station
OFF ON
AUDIO 1 or AUDIO 2
OFF ON
Fig. 335. Test bench for EOW line side functionality test
Make a call from IDU direction 1 to IDU direction 2 or any remote station in Direction 2:
A transfer cable must be placed between the Audio 1 or Audio 2 connectors of the two Services
Protection boxes.
Check that the line is free on both Main IDU(s) (green EOW LED is on).
On IDU direction 1:
1. Check that the line is free (green EOW LED is on).
2. Handset OFF/ON switch to ON.
3. On keypad, press # to engage line.
4. Check that the EOW LEDs turn to yellow (as well as on the IDU direction 2)
5. On keypad, dial the two–digit number of the IDU direction 2 or any remote station in direction 2.
6. Ring tone is audible in the handset.
On IDU direction 2 (or in the remote station in direction 2 which is called):

7. Yellow EOW LED is flashing and the IDU is emitting a ring tone.
8. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.
Switch off the handsets to finish the call.
Report about the Order wire Line side functionality into the TRS.
3DB 16142 CAAA Ed.01A–DRAFT 439 / 576

3–2.6.6.4 Housekeeping alarms setting and testing (if foreseen in the plant documentation)

Note: These tests should be performed only in specific sites requested by the Customer.

Purpose: Configure and test Via CT the housekeeping external alarm inputs
Six alarm inputs are available to monitor either Relay contact or open collector type external alarms.
. CT ⇒ Views ⇒ External Points
In the left window → INPUT → CPI 1 to CPI 6
In the lower right window → User Label → Write the suitable name for the current alarm.
→ Polarity → Configure if the alarm must show when closed or opened
→ Alarm Profile → Primary Alarms (by default)
Fig. 336. Input housekeeping external alarm configuration
Testing the external alarms monitoring:
Assuming that CPI 1 is configured in “Active Closed” polarity:
z Place a hardware loop on the station DDF between CPI 1 access point (Sub D – pin 6) and GND point
(Sub D – Pin 10). See connection point description in para.1–3.5.1 on page 81.
n Verify in the CT External points view that CPI 1 is showing an alarm.
z Repeat with CPI 2 to 6.
Report about the House keeping input alarms acquisition into the TRS.
440 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Purpose: Configure and test the housekeeping equipment alarms outputs
Required Instruments: PC with Craft Terminal software and Multi–meter (loop tester)

– Three alarm outputs are dedicated to fixed equipment general alarms: IDU, ODU 1 and SPARE ODU.
– Four alarm outputs CPO 1 to 4 can be configured either as equipment alarm or manual remote
control:
. CT ⇒ Views ⇒ External points
In the left window → OUTPUT → CPO 1 to CPI 4
In the lower right window → User Label → Write a name for the current equipment or
remote control alarm
→ Polarity → Configure if the contact must be closed or
opened when active
To use the relevant Alarm output as a manual remote control:
→ Criteria → Manual → Apply
Then, to activate the remote control → External State → “On” → Apply
To use the relevant Alarm output as an automatic equipment alarm:
→ Criteria → Automatic
→ Select in the “Event” scroll list the equipment alarm to be associated
→ Apply
Fig. 337. Output housekeeping equipment alarm configuration
3DB 16142 CAAA Ed.01A–DRAFT 441 / 576

Testing a remote control alarm Output:

z Connect a multi–meter (loop tester mode) between CPO 1 access point (Sub D – pin 4) and the

Common wire point (Sub D – pin 9). See connection point description in para.1–3.5.1 on page 81.

. CT ⇒ Views ⇒ External points
In the left window → OUTPUT → CPO 1
In the lower right window → Polarity → Active Closed.
→ Criteria→ Manual → Apply
→ External State → On → Apply
n Loop tester must detect a loop (close circuit).
In the lower right window → External State → Off → Apply
n Loop tester does not detect anymore loop (open circuit).
z Repeat with CPO 2 to 4.
Report about the House keeping Output alarms detection into the TRS.
3–2.7 Commissioning station B – Phase 2 (Acceptance Test)
Repeat in Station B all the tests performed in Station A except the Hop Stability Test that has to be run only
one time for the full hop.
Fill a second Test Result Sheet for Station B
END OF COMMISSIONING ACCEPTANCE TEST
3–2.8 Final operations
As introduced in para.1–2.6.1 on page 58, complete the commissioning of each NE, creating the NE
operator profiles and saving its data.
442 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.9 Annex A: fine antenna alignment
Safety rules for Microwave radiations (EMF norms):

read carefully para.A.3.8 on pages 535 onwards
Antenna pre–pointing should have been done during equipment hardware installation described in the
9400AWY Installation Handbook. This annex explains how to carry out the antenna fine alignment.
To do that:
a) the radio link must be up

b) in general, fine alignment should be done only on one station of the radio link
c) connect a voltmeter to the ODU of such a station, through the light service kit cable (see
para.3–2.10 on page 446)
d) proceed with Vertical alignment, then with Horizontal alignment, as described in following
para.3–2.9.1 and 3–2.9.2
e) in configurations with two antennas, repeat the procedure for the second antenna.
3–2.9.1 Vertical alignment
F1
F2
B F3
A
– A Vertical position rotational axis

– B Vertical fine alignment nut movement (stretching screw)
– F1–F2–F3 Vertical position coarse alignment movement tighten screws
Fig. 338. Integrated pole mounting screws for Vertical alignment
3DB 16142 CAAA Ed.01A–DRAFT 443 / 576

Fig. 339. Stretching screw (3CC14292AAAA)
Vertical tuning:
The vertical (or elevation) fine tuning system offers a maximum range of ± 25 degrees.
+ 25°
0°
– 25°
Only two screws among F1, F2 and F3 are placed depending on the suitable final elevation angle:
• For a final elevation angle between – 5 degrees and + 5 degrees, put the screws F1 and F3.
• For a final elevation angle between + 5 degrees and + 25 degrees, put the screws F1 and F2.
• For a final elevation angle between – 5 degrees and – 25 degrees, put the screws F2 and F3.
In any of the three cases above, proceed the following to fine tune the antenna in elevation:
1) Insert the tool of Fig. 339. above (Stretching screw) for fine pointing in position (B)
2) Loosen the axis screw (A), release the two locking screws (F), and then tune the turnbuckle (B) with
the appropriate spanner while monitoring the received level.
3) When the maximum received level has been reached, tight the locking screws (F), then the axis
screw (A).
4) Remove the tool (B)
Advice: to proceed to a ± 25° wide range tuning:
1) Put only the locking screw F2.
2) Loosen the axis screw (A), release the locking screw F2, then tune the turnbuckle (B) with the
appropriate spanner while monitoring the received level.
3) When the maximum received level has been reached, look what holes are visible and establish the
relevant screws configuration F1 + F3 or F1 + F2 or F2 + F3.
4) Tight everything.
Proceed to the horizontal tuning.
444 / 576 3DB 16142 CAAA Ed.01A–DRAFT

3–2.9.2 Horizontal alignment
E
C1
under
under
C2
D2
D1
– C1–C2 Horizontal position rotational axis screws

– D1–D2 Horizontal position coarse alignment movement tighten screws
– E Pole mounting bolts (2)
Fig. 340. Integrated pole mounting screws for Horizontal alignment
Horizontal tuning:
1) Pre–pointing (if necessary): loosen the two “U bolts” (E) just enough to permit the pole
mounting to turn around the pipe. Align the best as possible the pole mounting in the direction
of the remote station with the help of a compass if the remote station is not visible, at sight if the
remote station is visible. Fix the two “U bolts” (E).
2) Fine alignment: loosen the two screws C1–C2 and the two screws D1–D2 just enough to
permit the pole mounting to turn around the rotational axis C1–C2.
With the link up, optimize the pointing by monitoring the received level with the voltmeter.
When the maximum received level has been reached, tight the C1–C2 and D1–D2 screws.
N.B. After the alignment completion, the final tightening torque for the M10 screws :
– A, F1, F2, F3 in Fig. 338. on page 443
– C1, C2, D1, D2 in Fig. 340. above
must be 30 Nm.
3DB 16142 CAAA Ed.01A–DRAFT 445 / 576

3–2.10 Annex B: light service kit cable operative information

Fig. 341. herebelow shows this optional cable (P/N 3CC 13477 AA**):

E
A B
F G
1 1
3
2
3
Black
4 4
5 5
A 6 6 B
7 7 D
8
9
8
9
C
10 10 Red
11 11
12 12
1
E
C D
6 7 7 6
12 12 11
11 5
5 8 8
4 1 4
9 1
10 9 10
3 2 3
2
View following F View following G
LEMO wire 6 = ground

Fig. 341. Light service kit cable
Connector usage:
– (A) LEMO connector, to be plugged into LEMO connector on ODU (see Fig. 46. on page 119 and
Fig. 47. on page 120)
– (B) LEMO connector, for Alcatel–Lucent internal use only.
– banana plugs (C) and (D) : output is a 0 to +3V DC voltage proportional to the radio Rx field. During
equipment line–up, through a multi–meter it is possible to easily point the antenna until the measured
voltage is the maximum, corresponding to the maximum radio Rx field. Actual Rx field value can be
measured by means of the Craft Terminal (see para.2–6.5 on page 248).
– (E) RS232 connector, for Alcatel–Lucent internal use only.
a) END OF SECTION 3
446 / 576 3DB 16142 CAAA Ed.01A–DRAFT

SECTION 4: MAINTENANCE AND UPGRADE
This section contains the whole logical and operative information for the equipment maintenance and
system SW and HW upgrade.
MAINTENANCE
Chapter 4–1 – Maintenance Policy

449
It introduces the basic concepts for the equipment maintenance.
Chapter 4–2 – Set and use of EOW functions

It explains how to configure and use the Engineering Order–Wire functions of the 453
equipment.
Chapter 4–3 – Maintenance Tools and Spare Parts

It describes the instruments, accessories and the equipment spare parts that are 455
envisaged to carry out the routine and corrective maintenance of the equipment.
Chapter 4–4 – First Level Maintenance

461
It describes the First Level Maintenance (system state display) of the equipment.
Chapter 4–5 – Second Level Maintenance

467
It describes the preventive and corrective maintenance of the equipment.
Chapter 4–6 – Spare Flash Card management and replacement procedures

This chapter describes how to manage the spare Flash Card and how to replace 505
it, in case of problems.
UPGRADE
Chapter 4–7 – System hardware upgrade

This chapter details all phases necessary to install tributary plug–ins, or to upgrade
509
9400AWY system from (1+0) to (1+1) configuration, or to replace the Flash Card
to improve system capacity.
Chapter 4–8 – SWP download toward NE

This chapter details all phases necessary to download inside the NE equipment
525
environment, and then activate, a SWP having a version greater than that presently
loaded in the NE’s Flash Card.
Chapter 4–9 – CT & NE Upgrade to a new SWP “version”

(same NE “release”)
525
This chapter details all phases necessary to install a new SWP ’version’ in the PC
environment as well as in the equipment environment.
Chapter 4–10 – SWP de–installation

This chapter describes how to de–install from the PC the Craft Terminal Software 526
Package components.
3DB 16142 CAAA Ed.01A–DRAFT 447 / 576

448 / 576
4–1 MAINTENANCE POLICY
This chapter introduces the basic concepts for the equipment maintenance.
4–1.1 Classification of maintenance levels and operators
The maintenance procedures described in the following chapters are based on the following
considerations:
– The possibility of carrying out routine and corrective maintenance is based on the availability of:
• a suitable set of instruments and accessories
• a suitable set of spare parts
These matters are described in chapter 4–3 on page 455.
– Maintenance can be classified as:
• First Level Maintenance:
– ROUTINE (system state check)
• Second Level Maintenance:
– PREVENTIVE (periodic set of measurements and checks)

– CORRECTIVE (troubleshooting and repair)
First level maintenance consists of a set of simple operations by means of which a First Level
Maintenance Operator can acknowledge the state of the system and decide whether or not the
intervention of a Second Level Maintenance Operator is required in order to bring back the assembly
to optimum operating conditions by troubleshooting and unit replacement, if necessary. In this
philosophy:
• First Level Maintenance Operator should not be authorized to change the equipment status;
he should be only authorized to display it or to make some simple tests through the Craft
Terminal, if expressly authorized by the Station Manager.
These actions are described in chapter 4–4 on page 461.
• Second Level Maintenance Operator is authorized to make all actions necessary to repair
the system; moreover he should only be authorized to carry out routine maintenance.
These actions are described in chapter 4–5 on page 467.
With regard to the access to the Craft Terminal functionalities as well as to the TCO Suite
NE–interactive functionalities, notice that it is possible to use the following operator profiles:
• viewer for the First Level Maintenance Operator

• craftPerson for the Second Level Maintenance Operator.
– The two–station layout typical of a radio link requires often that different operators can communicate
with each other to solve problems. The EOW functions of this equipment give a simple way for this
communication need.
This matter is described in chapter 4–2 on page 453.
3DB 16142 CAAA Ed.01A–DRAFT 449 / 576

4–1.2 First Level Maintenance Personnel skill

First Level Maintenance Personnel must have received:

– an adequate technical background on telecommunications. Experience in first level maintenance
activities is a must;
– an adequate presentation on the equipment this handbook refers to;
– detailed instructions on “what to do” and/or “who must be contacted” in the case should he find the
equipment not in its normal conditions.
4–1.3 Second Level Maintenance Personnel skill
Second Level Maintenance Personnel must have received an adequate technical background on
telecommunications. Experience in maintenance activities is a must.
In particular, Second Level Maintenance Personnel must be familiar:
– with the equipment this handbook refers to
– and with the use of the Craft Terminal applications of the equipment this handbook refers to.
Without these prerequisites, reading this handbook and the associated handbooks indicated in para.C.2.1
on page 555 is usually not enough to properly maintain equipment.
4–1.4 Troubleshooting organization
[1] The troubleshooting procedure is carried out with the help of information reported in following
chapters. Anyway this method does not deal with the following issues (which are to be dealt with
otherwise):
• faulty electronic alarm indication, processing and detection circuits
• faulty wiring (back–panel, connectors, etc.)
[2] The following interfaces are present on the equipment for troubleshooting purposes:
• Ethernet interface for:

– the Telecommunication Management Network ( TMN )
– the Craft Terminal (Local or Remote)
– the TCO Suite NE–interactive functionalities
• F interface for the Craft Terminal (Local or Remote)
• LEDs located on the NE’s units.
450 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[3] Usually, maintenance is firstly done via software (TMN or Local/Remote Craft Terminal or the TCO
Suite NE–interactive functionalities) to locate the faulty equipment and the faulty unit or the faulty
path and then on site to physically correct the trouble.

Maintenance can be done:

• from a TMN network management center.

By means of the TMN, the maintenance technician can see the alarms generated by each
equipment of the managed network (see the relevant TMN handbooks).
• from a Remote Craft Terminal (RCT) management center.

The operator, connected to a local NE, can remotely manage and troubleshoot a network
composed of max 128 NEs, including itself. This handbook applies to this function.
• on site.
The operator is on site in case:
a) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT).

b) the equipment is not reachable by the remote manager (TMN or RCT) and therefore is
isolated.
c) link problems are present.
d) the trouble has been located and a physical replacement is necessary.
In cases a ) , b ), c ), the alarmed equipment is checked by means of the local Craft Terminal.
[4] The NE is provided with LEDs which indicate Centralized Equipment Alarms.
All alarms detected on the units are collected by the IDU MAIN unit, which delivers centralized
indications (by means of LEDs on the front coverplate). Specifically:
• Red LED: detection of a MAJOR (URGENT) alarm.

• Red LED: detection of a MINOR (NOT URGENT) alarm.
• Yellow LED: alarm condition ATTENDED.
• Red LED: detection of a LDI (problem in the local equipment).
• Red LED: detection of an RDI (problem in the remote equipment).
– In the case of a MAJOR or MINOR alarm, after locating the alarmed unit, the alarm condition can
be ”attended” by pressing the alarm storing push button on the front panel of the IDU MAIN unit.
This condition causes on the front coverplate:
• yellow LED ATTENDED to light up
• red LEDs MINOR and MAJOR to turn off (free to accept other alarms)
If both LEDs are on, the Attend command should be given twice : one to attend the MINOR
alarm and one to attend the MAJOR alarm.
[5] The troubleshooting operation is done by means of the Craft Terminal, and of the optical indicators
(LEDs) present on the NE.
The Craft Terminal is connected to the relative connector (F or Ethernet interface) on the front
coverplate of the IDU MAIN unit.
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault
location and subsequent removal as indicated in para. 4–5.8 on page 474.
To correctly execute the troubleshooting operations the technician must know the
equipment configuration (see Equipment applications on the Craft Terminal).
3DB 16142 CAAA Ed.01A–DRAFT 451 / 576

452 / 576
4–2 USE OF EOW FUNCTIONS
Please refer to chapter 4–1 on page 449 for an introduction to the basic concepts of equipment
maintenance.
This chapter explains how to configure and use the EOW (Engineering Order–Wire) function of the
equipment.
4–2.1 Setting information
The EOW functions are possible only in the IDU MAIN unit configurations equipped with the AUDIO +
USER SERVICE CHANNEL plug–in.
The telephone handset (P/N REF.[1] in Tab. 23. on page 91) allows to carry out EOW in/out calls at IDU
side. It uses DTMF (tone) dialling.
a) Connection diagram
STATION A STATION B
ODU ODU
1 2 3 3 1 2
4
7
5
8
6
9
IDU IDU 6 4 5
9 7 8
0 # # 0
* *
OFF ON MAIN UNIT MAIN UNIT OFF ON
Telephone handset Telephone handset
N.B. each Telephone handset has its own phone number. Phone number can be in the 10 to
99 range. Telephone handsets must have different phone numbers.
Physical connection on IDU: connect Telephone handset’s RJ11 plug to TPH connector on the IDU
MAIN unit [ (7) in Fig. 22. on page 67 ].
b) Telephone handset view
Caution: to operate, set the handset switch to “FV”.
Set switch to “FV”
ON/OFF switch
RJ 11 connector
c) Telephone handset keyboard
KEY MEANING
* Force unlocking of the line
# Engage line
3DB 16142 CAAA Ed.01A–DRAFT 453 / 576

d) Telephone handset phone number display/setting
Display/setting is done:

• by Quick Configuration Procedure (see Step J on page 395 )

•

or by Craft Terminal with the following menus (refer to para.2–3.4.2 on page 217 for details):
– display: Configuration ⇒ System Settings ⇒ Overhead ⇒ Phone Parameter
– setting: Configuration ⇒ System Settings ⇒ Overhead ⇒ Phone Parameter ⇒ ’phone
number’ ⇒ Apply
e) Ways of Calling : two different ways of calling are possible:

• SELECTIVE: a connection between two users (dial a number: 10 to 99)
• OMNIBUS: a unidirectional connection with all the users (dial digits 00)
f) LEDs indication:
• EOW (GREEN): free line
• EOW (YELLOW): busy line
• Flashing YELLOW: received and recognized call
N.B. position of green/yellow LED on IDU MAIN unit:
EOW
GREEN
GREEN RED RED
YELLOW
GREEN RED RED YELLOW
4–2.2 Call Set–up/End by Telephone handset connected to the IDU Main unit
a) To Call from Handset:
1) Check that line is free (EOW–free green LED on the MAIN unit is on)
2) Set Handset ON/OFF switch to “ON”
3) On keypad, press # to engage line
4) Check that EOW–busy yellow LED on the MAIN unit is on
5) On keypad, dial two–digit number of station to be called (or 00 for omnibus call)
6) Ring tone is audible in the handset, wait for answer
b) To Answer Call at Handset:
1) EOW–busy yellow LED on the MAIN unit flashes and audible tone is present
2) If not connected, connect handset to IDU, set ON/OFF switch to “ON”, press # on keypad, speak
c) To End Call from Handset:
1) On keypad, press *
2) Move handset ON/OFF switch to “OFF”
454 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–3 MAINTENANCE TOOLS AND SPARE PARTS
maintenance.
This chapter describes the instruments, accessories and the equipment spare parts that are envisaged
to carry out the routine and corrective maintenance of the equipment, and and is organized as follows:
– Instruments and accessories herebelow, including:

• Software tools herebelow
• Maintenance, Installation and Station Kit Tools on page 456
– Set of spare parts on page 458, including:

• Types of Spare Parts on page 458
• Number of Spare Parts on page 459
• General rules on spare parts management on page 460
4–3.2 Instruments and accessories
4–3.2.1 Software tools
There is a local Craft Terminal (PC) which permits to display all the alarms and which manages the
Equipment. Its whole implementation is described in the SECTION 2 (NE MANAGEMENT BY TCO SUITE
AND CRAFT TERMINAL) on page 139, while its use for troubleshooting is summed–up in para.4–5.8 on
page 474.
When a TMN is implemented, an Operation System will display alarms and manage all the connected
Equipment of the network. Refer to the relevant handbooks.
Please refer to para.2–2.4.1 on page 174 for an overview on the physical interfaces for the NE
management.
3DB 16142 CAAA Ed.01A–DRAFT 455 / 576

4–3.2.2 Maintenance, Installation and Station Kit Tools

For the P/Ns of these Kit Tools, please see REF.[2], [3] and [4] in Tab. 23. on page 91 .

a) The Installation Kit Tool includes various types of common usage fixed spanners, standard and
crosshead screwdrivers, polygon spanners, polygon tube spanners, special fixed spanners, a torque
wrench, etc.
b) The Maintenance Kit Tool is practically equal to the Station Kit Tool, with the addition of the
Antistatic wrist–band.
c) The Station Kit Tool is a bag additionally containing various types of cables and cable adapters.
The detailed item list of these Kit Tools is given in the documents enclosed to this handbook:
• Installation Kit Tool part list, REF.[A] in Tab. 81. on page 575
• Maintenance Kit Tool part list, REF.[B] in Tab. 81. on page 575
• Station Kit Tool part list, REF.[C] in Tab. 81. on page 575
N.B. These Kit Tools are standardized kits for the use with all Alcatel–Lucent WTD equipment types:
they contain also items that are not used in 9400AWY environment (they are not described in
this manual).
Some special items are listed in Tab. 66. below, which gives also reference to figures where they are
depicted.
Tab. 66. Special items of the Kit Tools

SPECIAL ITEM DESCRIPTION
COMPONENTS OF ANTISTATIC WRIST–BAND
Antistatic wrist–band
Antistatic applications cord
para.A.5 on page 538
Plug with crocodile pliers
Female button termination
SPECIAL EXTRACTORS
Unhook tool for 1.0/2.3 coax Fig. 342. below
SPECIAL TOOLS AND ITEMS FOR ODU
Lever for ODU mounting/dismounting Fig. 343. on page 457
Fig. 342. Special extractor to remove the coaxial cables 1.0/2.3
456 / 576 3DB 16142 CAAA Ed.01A–DRAFT

When, in ODU configurations 1+1 with coupler, you must dismount and then mount one of the
two ODUs for maintenance purposes, the following operations:

UNBLOCK BEFORE DISMOUNT

One at a time, unblock the four ODU blocking levers (A) pushing up the restraint spring
(B) and, contemporarily, turning down the lever (C).
BLOCK AFTER MOUNT
Block the four ODU blocking levers (A)
may produce vibrations that could cause synch loss or other electrical disturbances to the other
ODU still working.
A B
Using the special lever:
allows to do the same unblock/block operations without producing vibrations.

The following photographs should clarify the correct lever handling and usage.
Fig. 343. Lever for ODU mounting/dismounting
3DB 16142 CAAA Ed.01A–DRAFT 457 / 576

4–3.3 Set of spare parts

4–3.3.1 Types of Spare Parts

The unit replacement procedures described in paragraph Corrective Maintenance of chapter Second
Level Maintenance in this section presume that the units present in the spare–part stock correspond
exactly to the plug–in replaceable units that are equipped in the system (i.e. with the same Part Number).
4–3.3.2 ODU Spare Parts
The suggested spare parts should be at least those containing electronic parts; in general the spare part
types are:
– for 13 to 38 GHz: the complete ODU. For the P/Ns refer to para. 1–4.4.2 on page 103.
– for 7–8 GHz: the TRANSCEIVER assembly. For the P/Ns refer to:
• Tab. 26. on page 101 (7 GHz)
• Tab. 28. on page 102 (8 GHz)
As a matter of fact, all other ODU–related items listed in Chapter 1–4 on page 93 (but whose P/Ns are
given in the Installation Handbook) can be considered items to be provisioned as spare parts.
458 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–3.3.3 IDU Spare Parts
The set of spare parts for the IDU is inclusive of a minimum number of spares for each type of replaceable
units. The suggested spare parts should be at least those containing electronic parts; in general the spare
part types are:
– IDU Main unit, for both (1+0) and (1+1) systems
– IDU Extension unit, for (1+1) systems only
– Flash card, for both (1+0) and (1+1) systems
As a matter of fact, also passive items (whose P/Ns are given in the Installation Handbook) can be
considered items to be provisioned as spare parts.
a) Spare parts for IDU Main and Extension units
For P/Ns, refer to para.1–3.1 on page 66.
N.B. In case a terminal has IDU Main and/or Extension units equipped with plug–in(s), and you
order as spare parts such units separately from the plug–in(s), take into account that, when
the IDU Main or Extension faulty unit must be replaced, the spare part box has first to be
opened, then the plug–in must be installed, at last box must be closed.
b) Spare parts for Flash Card
There are various possible types of Flash Cards. For details refer to para.1–3.6 on page 89 .
For the spare–part–stock, Customer should provision at least one Flash Card for each type (P/N) of
Flash Card equipped in systems in service. For cost saving, as alternative to provision the various
types, that with Software Label “32E1DS1 4/16QAM” could be provisioned instead.
N.B. Read important information regarding the spare Flash Card management in para.4–6.1
on page 505.
4–3.3.4 Number of spare parts
The overall number of spares depends on Customer requirements, and should be based on the average
amount of transmission circuits available to be accounted for not only during MTBF (Mean Time Between
Failures) but also during MTTR (Mean Time To Repair); the latter depending on the amount of spare parts
available.
3DB 16142 CAAA Ed.01A–DRAFT 459 / 576

4–3.3.5 General rules on spare parts management

Before storing the spare units make sure that they are working by inserting them in an operating

equipment.

It is suggested to periodically check those spare units that have not been utilized for over a year.
If the spare parts and the equipment are stored in the same environment, make sure that the spare parts
are placed in cabinets to safeguard them from dust and damp.
Moreover, they should also be well grounded to avoid electrostatic discharges.
If the spare parts are stored in another room, or have to be moved from another place, building or site,
make sure that the following is observed:
– the spare parts must be wrapped in anti–static and padded envelopes;
– the spare parts must not touch wet surfaces or chemical agents that might damage them (e.g. gas);
– if during transportation the temperature is lower than that of the room where they had been kept,
make sure that before using them they pass a certain period in a climatic chamber to prevent thermal
shocks and/or the possibility of steaming up.
460 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–4 FIRST LEVEL MAINTENANCE
maintenance.
This chapter describes the First Level Maintenance of the equipment and is organized as follows:
– System state display by visual indications, below
– TCO Suite and Craft Terminal commonly used functions for system status display and
checks, on page 463
4–4.2 System state display by visual indications
4–4.2.1 LED test
To be sure to have correct indications, carry out the LED test of IDU MAIN unit, pushing pushbutton (9)
in Fig. 345. on page 462: while pushed, all leds of the MAIN unit should be turned on.
In 1+1 system, perform the same test also on the IDU Extension Unit, pushing pushbutton (6) in
Fig. 344. below: while pushed, all leds of EXTENSION unit should be turned on.
4–4.2.2 Alarm LEDs on the IDU MAIN unit
All the alarms detected on the units are collected and processed by the IDU MAIN unit which gives
centralized optical indications by means of LEDs on its front coverplate, as shown in Fig. 345. on page
462.
4–4.2.3 Alarm LEDs on the Extension unit
(3) LED test GREEN
(2) ON/OFF switch
LED Normal status

ON (green) ON (if the ON/OFF switch is on)
Fig. 344. LEDs and pushbutton on IDU Extension unit for maintenance purposes
3DB 16142 CAAA Ed.01A–DRAFT 461 / 576

(3) Ethernet (or

OS) interface

for Craft Terminal
GREEN RED RED
RED RED YELLOW
(2) ON/OFF switch
(10) Reset
(9) Alarm attending (11) LED test

(12) F interface for
Craft Terminal
LED on Meaning Action
If off (and if the ON/OFF switch is on) there is a problem in the station
Green LED ON A
battery or in the MAIN unit
Red LED LDI There is a failure in the equipment A
Red LED RDI There is a failure in the remote station A
Detection of an URGENT alarm: it means that there is at least one

Red LED MAJ A
alarm (internal and/or external) for which traffic is affected.
Detection of a NOT URGENT alarm: it means that there is at least one

alarm (internal and/or external) for which traffic is not affected (e.g.
Red LED MIN B
something is wrong, but the traffic is recovered by an automatic
protection switch).
Alarm condition ATTENDED: it means that an Operator (by pushbutton

Yellow LED ATTD (8) or by Craft Terminal) has attended the alarm (for details, see para. B
4–5.6.2 on page 472).
ACTION:
A The immediate intervention of a Second Level Maintenance Operator is required.
B The immediate intervention of a Second Level Maintenance Operator is not required
Fig. 345. LEDs and pushbutton on IDU MAIN unit for maintenance purposes
462 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–4.3 TCO Suite and Craft Terminal commonly used functions for system
status display and checks
This paragraph sums up how to use the TCO Suite and Craft Terminal functions for system status display
and checks to be carried out by a First Level Maintenance Operator.
N.B. These operations should be done by the First Level Maintenance Operator only if expressly
authorized by the Station Manager, who, in his turn, for each 9400AWY NE that should be
accessible by the First Level Maintenance Operator must:
– assign him a Username/Password set
– in case of remote NE, communicate him the NE’s IP address.
4–4.3.1 Viewing the NE alarms by TCO Suite
Proceed as follows:
1) start–up the TCO Suite Alarms & Settings function as explained in para.2–2.3.1 on page 162,
using:
– the NE’s IP address (if remote NE)
– the Username and Password
communicated by the Station Manager
2) in the Alarms & Settings Main Menu screen that appears (Fig. 73. on page 164), click on button
Active Alarms
3) refer to para.2–2.3.6 on page 171 for the alarm screen interpretation.
4) at the end, close the TCO Suite Alarms & Settings – Active Alarms screen.
4–4.3.2 Viewing the NE status by Craft Terminal
Proceed as follows:
1) login the NE as explained in para.2–2.5.2 on page 177, using:

– the NE’s IP address (if remote NE)
– the Username and Password
communicated by the Station Manager.
2) the 9400AWY Main view opens (see Fig. 94. on page 185).
From this screen, according to the user profile assigned through the entered
Username/Password set, you can navigate to make some checks. Suggested checks are:
a) Summary Block Diagram view

Proceed as follows:
• Click on button in the Main tool bar (see Fig. 94. and Fig. 95. on pages
185–186)
• for screen interpretation, refer to para.2–11.4 on page 286.
3DB 16142 CAAA Ed.01A–DRAFT 463 / 576

b) Checks on Radio domain
Various checks are possible selecting the specific matters of the Menu bar, as shown in

following Fig. 346. to Fig. 350.

For screen interpretation, click on their relevant HELP button and/or refer to chapter 2–6

on page 243.
3) at the end:
– first, carry out the NE Logoff as explained in para.2–2.5.3 on page 184
– then, close the 1320CT application as explained in para.2–2.5.4 on page 184.
RADIO MENU BAR
Fig. 346. Checks on Radio domain – Alarms
Fig. 347. Checks on Radio domain – Configuration
464 / 576 3DB 16142 CAAA Ed.01A–DRAFT


Fig. 348. Checks on Radio domain – Frequency
Fig. 349. Checks on Radio domain – RTPC & ATPC
465 / 576
466 / 576
Fig. 350. Checks on Radio domain – Power Measurement

4–5 SECOND LEVEL MAINTENANCE
maintenance.
Second level maintenance consists of a set of operations which maintain or bring back the assembly to
optimum operating conditions in a very short time, with the aim of obtaining maximum operational
availability.
Second level maintenance is classified as:
– ROUTINE or PREVENTIVE (periodic set of measurements and checks, independently of troubles)
– CORRECTIVE (troubleshooting and repair, in case of troubles)
This chapter describes the routine and corrective maintenance operations and is organized as follows:
– Warnings on page 468, including:

• EMC norms
• Safety rules
• Cautions to avoid equipment damage
– Routine (preventive) Maintenance on page 469
– Consequences of unit extraction in the IDU on page 470
– Corrective Maintenance general flow–chart on page 471
– Alarm acknowledgment and attending on page 472
– Trouble–Shooting starting with visual indications on page 473
– Trouble–Shooting via Craft Terminal on page 474
• Alarm synthesis indication on page 476
• Details on alarms / statuses on page 477
• Description of alarms and of probable causes on page 479
– Hints on the troubleshooting on page 481
– IDU Unit replacement on page 490
– ODU replacement on page 499
– Faulty unit repair and Repair Form on page 502
The handbook parts that should be read (or known) before starting this chapter are:
– chapter 1–2 on page 33 System overview

– chapter 1–3 on page 65 IDU provisioning and description
– chapter 1–4 on page 93 ODU provisioning, characteristics and description
– chapter 4–1 on page 449 Maintenance Policy
– chapter 4–3 on page 455 Maintenance Tools and Spare Parts
– chapter 4–4 on page 461 First Level Maintenance
3DB 16142 CAAA Ed.01A–DRAFT 467 / 576

4–5.2 Warnings

4–5.2.1 EMC norms

ATTENTION EMC NORMS
WHEN CARRYING OUT THE GIVEN OPERATIONS OBSERVE THE NORMS STATED IN PARA.
A.4.3 ON PAGE 537
4–5.2.2 Safety rules
The Safety Rules stated in para.A.3 on page 530 describe the operations and/or precautions to observe
to safeguard operating personnel during the working phases and to guarantee equipment safety.
Please read them carefully before starting each action on the equipment.
SAFETY RULES
General
Carefully observe the front–panel warning labels prior to working on optical

connections while the equipment is in–service.
Should it be necessary to cut off power during the maintenance phase, proceed
to switch off the power supply units as well as cut off power station upstream
(rack or station distribution frame)
Electrical safety
DANGER: Possibility of personal injury. Personal injury can be caused by

–48 V DC.
DANGER: Possibility of personal injury. Short circuiting, low–voltage,

low–impedance, DC circuits can cause severe arcing that can result in burns
and/or eye damage. Remove rings, watches, and other metal jewelry before
working with primary circuits. Exercise caution to avoid shorting power input
terminals.
4–5.2.3 Cautions to avoid equipment damage
Read carefully para.1–1.5 on page 32.
468 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.3 Routine (preventive) Maintenance
Routine maintenance is a periodic set of measurements and checks. This maintenance discovers those
devices whose function has deteriorated with time and therefore need adjustment or replacement.
Typically, digital equipment requires no routine maintenance.

The equipment allows to assess the quality of the connection links or counting the errored events and
obtaining performance data.
The Performance Monitoring Application, described in para. 4–5.8.4 on page 480, allows this function.
4–5.3.1 Routine (preventive) Maintenance every year
It is suggested to carry out the following operations yearly:
[1] Mechanical checks

Check that:
• the units,
• the cables,
• the mounting fixtures
are inserted and connected correctly.
[2] Grounding check

Check that the racks, subracks, and modules are grounded (for 9400AWY shelves, see para.A.3.6
on page 534).
[3] Power cables check
SAFETY RULES
DANGER: Possibility of personal injury. Personal injury can be caused by

–48 V DC.
DANGER: Possibility of personal injury. Short circuiting, low–voltage,

low–impedance, DC circuits can cause severe arcing that can result in burns
terminals.
Make these operations:
• Check that the power cable is perfectly safety grounded.
• Make sure that the subrack has been tightly fastened to the rack with screws, to guarantee
grounding (the rack is connected to the station ground).
[4] Operative checks
• Visual check:
– During the normal operation, check the led normal condition, as specified in para.4–4.2
on page 461.
• Checks by Craft Terminal

– some suggested checks are indicated in para.4–4.3 on page 463
– the commissioning tests, described in Chapter 3–2 on page 361, can be useful to carry
out equipment functional checks as a whole, in particular as far as checks on radio hop
are concerned.
3DB 16142 CAAA Ed.01A–DRAFT 469 / 576

4–5.4 Consequences of unit extraction in the IDU

Generally, a unit can be extracted from the system for the following reasons:

– to replace it with a spare part during corrective maintenance
– to check a spare part taken from the spare part stock
– to restore the suspected faulty unit (after its successful replacement with a spare unit during
corrective maintenance) to verify that it is really faulty.
The extraction of a unit has always some consequences on system behavior and performance that the
Maintenance Operator must know in advance:
a) Consequences of the MAIN unit extraction
The time taken to extract the MAIN unit must be short and should be limited to the time strictly
necessary for operation and maintenance purposes; it causes:
• interruption of the traffic on channel 1
• in (1+1) configurations, all protections are lost
• the NE not to be supervised because the Equipment controller is installed in this unit.
Note for (1+1) configurations:
• before extracting the unit make sure that the traffic is transmitted over channel 0 (on the
Extension unit). Otherwise, force with the CT the traffic onto channel 0.
b) Consequences of the Extension unit extraction
The time taken to extract the Extension unit must be short and should be limited to the time strictly
necessary for operation and maintenance purposes; it causes:
• interruption of the traffic on channel 0
• all protections lost
Note:
• before extracting the unit make sure that the traffic is transmitted over channel 1 (on the MAIN
unit). Otherwise, force with the CT the traffic onto channel 1.
470 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.5 Corrective Maintenance general flow–chart
START
Alarm acknowledgment and attending

(para.4–5.6 page 472)
Trouble–Shooting starting with visual indications

(para.4–5.7 page 473)
Trouble–Shooting starting via Craft Terminal

(para.4–5.8 page 474).
Identification of a unit to be replaced.
IDU unit replacement ODU replacement

(para.4–5.10 page 490) (para.4–5.11 page 499)
System check via Craft Terminal
Try again with N

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

Repair Form compiled (para.4–5.12 on page 502)
END
Fig. 351. Corrective Maintenance general flow–chart
3DB 16142 CAAA Ed.01A–DRAFT 471 / 576

4–5.6 Alarm acknowledgment and attending

4–5.6.1 Alarm acknowledgment

Refer to Fig. 351. on page 471, for the position of this step inside the corrective maintenance general
flow–chart.
The need for Operator intervention is notified:
– locally (on the front of the equipment or in the station):
• when one of the alarm LEDs MAJ – MIN on the MAIN unit front plate lights up.
– remotely (in a TMN maintenance center) when the OS acknowledges the presence of problems in
the station.
When the local Operator decides to manage the problem, he should carry out the alarm attending
operation (see para. 4–5.6.2 below). This operation has the scope of notifying locally in the station and
remotely to the TMN maintenance center that a local operator is attending the problem.
4–5.6.2 Alarm Attending
See Fig. 345. on page 462:
– the detected alarm condition can be stored through the Alarm attending push–button on the MAIN
unit.
This operation will turn OFF the LEDs MAJ / MIN and will light up the yellow LED ATTD on the MAIN
unit (Attended). The local Operator could also attend the alarm via the craft terminal.
– a possible new alarm condition (following the Attending) will turn on the LEDs MAJ / MIN.
– when the fault has been repaired, the yellow LED (if the alarm had been attended) or the red ones
(if the alarm had not been attended and no further alarms have occurred in the mean time) will turn
off.
472 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.7 Troubleshooting starting with visual indications
flow–chart.
Some problems may be localized through the LEDs indicated in para. 4–4.2 on page 461.
In any case, the inspection through the Craft Terminal is recommended before any unit replacement.
Flow–chart of Fig. 352. indicates LEDs on the MAIN unit that should be considered first.
START
N MAJOR, MINOR,
LDI or RDI LED
END
on the MAIN unit
is “ON”
Try login NE by Craft Terminal
N Y
Login successful ?
Carry out procedure in Carry out procedure in

para.4–5.9.1 page 481 para.4–5.8 page 474
Fig. 352. Troubleshooting starting with visual indications
3DB 16142 CAAA Ed.01A–DRAFT 473 / 576

4–5.8 Troubleshooting via Craft Terminal


flow–chart.

The ECT/RECT application includes several types of functions for system maintenance (used in
commissioning operations, too), as depicted in the following table:
FUNCTION FUNCTION DESCRIPTION
Diagnosis para.4–5.8.1 below
Alarm surveillance para.4–5.8.2 on page 475
Loopbacks para. 4–5.8.3 on page 480
Operator’s Controls of the protection switches para. 4–5.8.4 on page 480
Tx mute functions para. 4–5.8.5 on page 480
Performance Monitoring para. 4–5.8.6 on page 480
Commissioning tests para. 4–5.8.7 on page 480
The operating instructions make it possible to identify the faulty unit.

Having located the suspected faulty unit, replace it with a spare one (refer to para.4–5.10 on page 490
for IDU, or to para.4–5.11 page 499 for ODU).
4–5.8.1 Diagnosis
The options available in the Diagnosis menu are:
– Current Configuration View

– Summary Block Diagram View: displays a global logical view (strictly related to the physical
implementation) highlighting a synthesis of all the alarms and statuses present in the system
(ODU+IDU).
– Abnormal Condition List
– Remote Inventory
– Event Log
The generic events occurred and discriminated by the NE are stored in one or more Event Log files.
The ELB (Event Log Browsing) application embedded in the 9400AWY SWP allows the Operator to
read such log files, in order to have historical data that can be useful to troubleshoot the equipment
or the link or the PDH network, in case of multiple alarm conditions or intermittent alarms.
N.B. The event log file examination is quite complex; it is reserved to Alcatel–Lucent
skilled personnel as a debug tool (only using filters on the not meaningful events,
it is possible to understand the meaning of the stored data).
For further information and operative procedures, refer to the Chapter 2–11 on page 285.
474 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.8.2 Alarm surveillance
The Alarm surveillance available with the CT allow the Operator to examine the alarms currently present in
the equipment or in the link or in the PDH network.

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

Para 4–5.8.2.2 on page 477 explains how to see the alarms.
MAJOR alarm indicates a severe alarm that could affect the current traffic (interrupt or
degrade). Hence, a prompt intervention is necessary to restore the regular operating
condition of the equipment.
3DB 16142 CAAA Ed.01A–DRAFT 475 / 576

4–5.8.2.1 Alarm synthesis indication

The following troubleshooting table pertains to the alarm and status synthesis given in all the screens.

Tab. 67. Alarm Synthesis indication
Mnemonic Alarm / Status Description Maintenance
Synthesis of alarms that needs immediate

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

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

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

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

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

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

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

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

ALI Alignment
equipment MIB.
NB1: The Alarm Profile can modify the assignment of each alarm root to the various synthesis.
476 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.8.2.2 Details on alarms / statuses
The troubleshooting proceed by checking the detailed information on the NE alarm by using the Craft
Terminal.
To display the active alarms (refer to Fig. 353. below):
It is also possible to analyze the detailed alarms present on each TP of the Port views of the NE.
[1] Select the Equipment tab panel.
[2] Select one node (or sub–node) in the Resource Tree Area to check if some alarms are active.
[3] Select the Alarm tab panel in the Resource Detail Area.
[4] If the node has sub–nodes put a tick in the Include alarms from sub–nodes field to display the
alarms active also in the sub–nodes.
[1]
[2]
[3]
[4]
Fig. 353. Active alarm screen
Detailed information of some alarms are supplied.
3DB 16142 CAAA Ed.01A–DRAFT 477 / 576

The following table summarizes the information obtained in the Alarm view, starting from the left column.

Tab. 68. Alarm information, general description

TITLE DESCRIPTION
Severity severity associated to the alarm and assigned in the Alarm Profile
Event time time of the generation of the alarm
Entity entity involved in the alarm
Probable Cause probable cause of the alarm
Managed Object Class class of the alarm
The information supplied helps the operator during the troubleshooting operations.
Tab. 69. on page 479 supplies general information on the alarm meanings and on the respective
maintenance actions to be done bases on the information given in the applications.
The maintenance action must take account of the board where the alarm is detected.
The Housekeeping alarms are referred to the input external point relevant to the Housekeeping signals.
They are available to the customer by connecting them to a dedicated subrack connector.
478 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.8.2.3 Description of alarms and of probable causes
The information provided helps the operator during troubleshooting operations.

Tab. 69. General issues of the alarm meanings and their respective maintenance actions
ALARM MEANING MAINTENANCE ACTION

AIS detection on the tributary in Tx Check the tributary connected
AIS
side or Rx side equipment
ATPC loop problem Problem on the ATPC loop Communication problem
Battery fail Problem on the Station Battery Check the Station Battery
Excessive errors. Check the link
High BER Excessive BER
(propagation problem)
Demodulator failure affecting the
Dem fail Replace the ODU
demodulated signal
Loss of the incoming signal at the Check the link (propagation
Dem LOS
demodulator input problem)
Replace the ODU; if the alarm is still
Cable LOS Problem on the cable or on the ODU
active replace the cable.
Frequency setting incompatible with Change the frequency or change the
Incompatible Frequency
the ODU P/N ODU
Incompatible PTX Output power out of the limits Replace the ODU
Press the Reset pushbutton on the
Internal Communication
ODU not responding MAIN unit. If the alarm is still active,
Problem
replace the ODU
Check the LAN connection or
LAN failure LAN problem
replace the MAIN unit
Check the correct connection of the
cable between the IDU and the
Link Identifier Mismatch Mismatch on the link identifier relevant ODU. If the connection is
correct, check the link (propagation
problem)
LOF at the Tx tributary input or at Rx
tributary output (with framed Check the tributary connected
Loss Of Frame
tributary) or LOF of the Rx equipment or the line
aggregate signal
Loss Of Frame (Aggregate
LOF of the Rx aggregate signal Check the link (errors)
signal)
Loss Of Signal LOS at the Tx tributary input Check the line
Check the link (propagation
Low BER Low BER at the Rx side
problem)
Internal modulator failure affecting
Mod fail Replace the ODU
the modulated signal
Investigate by using the loopback
Mod LOS No signal at the modulator input
facilities with the CT.
Remote Defect Indication Alarm active in the remote station Check the remote station
Replaceable Unit Problem Problem on a replaceable unit Replace the unit
3DB 16142 CAAA Ed.01A–DRAFT 479 / 576

Tab. 69. General issues of the alarm meanings and their respective maintenance actions

ALARM MEANING MAINTENANCE ACTION

Replaceable Unit Type Mismatch between the installed unit Change the unit configuration or
Mismatch and the sw configured unit change the unit
Replaceable Unit Type Missing No unit in a configured slot Install the unit
Check the link (propagation
Rx Fail (Radio alarm) No RF received signal
problem)
Performance threshold has been
Threshold Cross Errors on the link
crossed
Tx Fail (Radio alarm) Transmitter failure Replace the ODU
Unconfigured Equipment
Unit present in an unconfigured slot Configure the unit
Present
Mismatch on the software version
Version Mismatch between CT software and Download the software version
equipment software
Housekeeping Active input housekeeping Check the housekeeping
4–5.8.3 Loopbacks
The loopbacks (settable by CT) give the possibility to perform some functional tests, thus making the fault
location and maintenance tests faster and easier. To implement the loopbacks, refer to the Chapter 2–10
on page 275.
4–5.8.4 Operator’s Controls of the protection switches
In certain troubleshooting conditions, changing the state of the protection switches can be useful to fix
problems.
For operative procedures, refer to the Chapter 2–9 on page 263.
4–5.8.5 Tx mute function (local and remote)
This facility allows to switch off the transmitter. This facility can be useful during commissioning to avoid
producing interference if the frequency is not yet properly set.
For further information and operative procedures, refer to the Chapter 2–6 on page 243.
4–5.8.6 Performance Monitoring
The Performance Monitoring is responsible for quality events counting and reporting.
For further information and operative procedures, please refer to the Chapter 2–12 on page 291.
4–5.8.7 Commissioning tests
In some cases, the commissioning tests, described in Chapter 3–2 on page 361, can be useful to carry out
equipment functional checks as a whole, in particular as far as checks on radio hop are concerned.
480 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.9 Hints on the troubleshooting
This paragraph gives hints on following matters:

– Problems with the Craft Terminal below

• PC restart
• Craft Terminal not working on NE’s local Ethernet interface on page 482
• Craft Terminal not working on NE’s F–interface on page 483
• Craft Terminal blocked on page 484
• Checks before MAIN unit or FLASH CARD replacement on page 484
– Analog measurements on page 485
– NMS 64 kbit/s V.11 and G.703
– Loopbacks
– Empty USM icon in NES on page 486
– Remote NE unreachable
– Configuration change from 4 QAM to 16 QAM
– Quick configuration menu correct use on page 486
– Abnormal condition list
– Tx Mute functionality for interferences investigation on page 488
– Tributaries 17 to 32 visible in “16E1+Ethernet” configuration on page 489
4–5.9.1 Problems with the Craft Terminal
With regard to the PC maintenance, refer to the constructor’s documentation.
4–5.9.1.1 PC restart
Should the Craft Terminal Software Product not be working properly or not responding to the operator’s
commands, to shutdown and restart the PC , proceed as follows:
– if possible, close the 1320CT application, after having verified that all NEs in the Network Element
Synthesis map are in not supervised state
– in order to shutdown the PC execute the command :
Start > Shutdown
A window (Windows NT Security user dialog) is displayed. It permits to shutdown the computer or
restart it.
The same window is displayed pressing the keys <Ctrl> + <Alt> + <Del> simultaneously.
N.B. In the case this procedure is unsuccessful for successive NE login, carry out the checks
indicated in following paragraphs 4–5.9.1.2 (Ethernet interface usage) or 4–5.9.1.3 (F interface
usage), till paragraph 4–5.9.1.5 on page 484.
3DB 16142 CAAA Ed.01A–DRAFT 481 / 576

4–5.9.1.2 Craft Terminal not working on NE’s local Ethernet interface

Proceed with the following checks:

– Verify that the CT Ethernet port is effectively that connected by a cross–connect cable to the MAIN
UNIT Ethernet interface on the left (see Fig. 83. on page 174; that on the right is not for CT interface).
– Restart the Craft Terminal (NE logout, PC switch off/on, NE login).

N.B. To carry out NE login, do not use Start ⇒ Alcatel 1320CT, but click the button Operational
& Maintenance of the TCO Suite Main Menu (see Fig. 64. and Fig. 65. on page 155),
and answer to question of Fig. 84. on page 178 specifying Ethernet interface usage.
– Disconnect and then reconnect, at PC side, the Ethernet cable; this message should arise at
re–connection:
Otherwise:
• the cable could not be the required cross–connect type (see Tab. 54. on page 144), or it could
be broken
• PC Ethernet port faulty
• MAIN unit Ethernet port faulty
If possible, verify the correct working of the Craft Terminal and of the Ethernet cable using them with
another Alcatel–Lucent equipment. If the problem still persists, solve the problem.
Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in
para.4–5.9.1.5 on page 484.
482 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.9.1.3 Craft Terminal not working on NE’s F–interface
Proceed with the following checks:

– Verify that the CT serial port is effectively that connected by cable to equipment’s F interface and that
cable is correctly connected.
– In Windows, verify that the possible selection Start ⇒ Programs ⇒ Alcatel ⇒ Lower Layers does
exist; if not, the installation and configuration of LLMAN and Alcatel Virtual Network Card for Lower
Layers (necessary for PC–NE F–interface usage) has not been carried out: refer to point b ) on page
315 to know what to do.
– Check for the “Network Connections” order (para.3–1.8.6 on page 353).
– Restart the Craft Terminal (NE logout, PC switch off/on, NE login).

N.B. To carry out NE login, do not use Start ⇒ Alcatel 1320CT, but click the button Operational
& Maintenance of the TCO Suite Main Menu (see Fig. 64. and Fig. 65. on page 155),
and answer to question of Fig. 84. on page 178 specifying F interface usage.
– Check that speed is the same:

• at PC side (see para.B.7.3 on page 550)
• at NE side through the TCO Suite Alarms & Settings function (see para.2–2.3.1 on page 162,
and para.2–2.3.8 on page 172).
– With the Craft Terminal connected to the equipment F–interface, open the ’Alcatel Lower Layer
Manager’ screen (by clicking with the mouse pointer on the Alcatel symbol in the MS–Windows
menu bar, or by Start ⇒ Programs ⇒ Alcatel ⇒ Lower Layers ⇒ Lower Layers Manager, and
interpret the various fields of the screen that opens (Fig. 354. below) as described in the 1320CT
Basic Craft Terminal Operator’s Handbook (see Tab. 78. on page 557), chapter Software
Installation, paragraph Communication with NE.
Link led
Fig. 354. Lower Layers Manager screen
– If the ’Link led’ is red (i.e. OFF), the problem can be due to:
• PC serial physical port faulty
• MAIN unit F–interface port faulty
• the cable
• FLASH CARD missing on MAIN unit (verify) or FLASH CARD/MAIN faulty
If possible, verify the correct working of the Craft Terminal and of the serial cable using them with
another Alcatel–Lucent equipment. If the problem still persists, solve the problem.
Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in
para.4–5.9.1.5 on page 484.
3DB 16142 CAAA Ed.01A–DRAFT 483 / 576

4–5.9.1.4 Craft Terminal blocked

In some situations, the CT is blocked (not temporarily) and, even if 1320CT application is closed by

Task–Manager and then re–launched again, the following message could arise:

Another instance of the system probably running . Do you really to continue setting?
Answering yes, you enter in Network Element Synthesis, but in this case continuos Autorestart trouble
/ Cannot autorestart program are received and the successive start of supervision fails.
If you decide to close again the CT in correct way and re–launch again the 1320CT application, no
signaling of errors are present but the condition does not change (CT is still blocked)
In this situation, there are two solutions:
a) logging–out and then relogging–in Windows session, thus terminating all active applications
b) or, if you do not want to close all applications, terminating manually all CT single processes by
Task–Manager. The list of processes to be terminated is:
• acdbm.exe
• FTclient.exe
• FTserver.exe
• java.exe
• LLman.exe
• lss.exe
• nesim.exe
• nspd.exe
• secim.exe
• admctemlimosi.exe
• dxcctemlimosi.exe
• tsdsnmpemlim.exe
N.B. pay attention not to terminate other processes !
4–5.9.1.5 Checks before MAIN unit or FLASH CARD replacement
If the Craft Terminal application does not respond (login unsuccessful):
1) push the RESET button on the MAIN unit and wait 10 minutes;
2) if, after 10 minutes, the Craft Terminal application responds, open the ”Alarm status” procedure
and proceed investigating the system state;
3) if, after 10 minutes, the Craft Terminal application does not respond, replace the MAIN unit, as
indicated in para.4–5.10.1 on page 491.
4) if the problem still persists after the MAIN unit has been replaced, the failure or content
corruption of the FLASH CARD must be suspected (a very extraordinary event); proceed with
its replacement, as indicated in para.4–6.2 on page 506.
484 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.9.2 Analog measurements
In case of two CT connected to the NE, as shown in the figure below, and at the same time both open on
the menu Radio → Power Meas, the analog measurements relevant to the PTx rem (Tx power of the
Remote NE) and the PRx rem (Rx power of the Remote NE) could have some instabilities (i.e. an
intermittent +99 dBm is reported for the PTx rem and –99 dBm is reported for the PRx rem).
ODU ODU
Station A Station B
IDU IDU
4–5.9.3 NMS 64 kbit/s V.11 and G.703
For a correct operation the NMS channel has to be configured in one station as ”DTE” and in the other
station as ”Codirectional”.
This selection can be done in the Quick Configuration Procedure in Step 10 (for NMS V.11 channel) and
in Step 11 (for NMS G.703 channel) or in the Menu Configuration → Network Configuration → IP
Configuration → IP Point to Point Configuration.
4–5.9.4 Loopbacks
For a correct activation of every loopback (Loopback menu):
– the relevant tributary must be enabled (Quick Configuration Procedure → Step 3)
– the local transmitter must be not muted (Menu Radio → Configuration)
Note 1: The loopback will become active after 6–7 sec. approx. (24 sec. approx. for the RF loopback).
Note 2: The time for a new set is 10 to 25 sec. approx.
3DB 16142 CAAA Ed.01A–DRAFT 485 / 576

4–5.9.5 Empty USM icon in NES

Enter Windows Task Manager and stop the process relevant to the empty USM.

4–5.9.6 Remote NE unreachable
Due to a deep fading the radio remote NE can be unreachable. In this condition in the USM will appear
the following message:
– The USM must be closed.
In the NES will appear a broken icon and a red bullet:
– Wait for the automatic restarting of the Supervision (at the end of the fading conditions). The icon in
NES will become whole and the bullet will take the color relevant to the alarms (if any) active in the
NE.
– If the Supervision does not start, close and open again the CT.
– If the Supervision does not start, switch off and switch on the PC.
4–5.9.7 Configuration change from 4 QAM to 16 QAM
With 16 QAM the max. Tx power must be typically 3 dB below the max Tx power of the 4 QAM.
4–5.9.8 Quick configuration menu correct use
The Quick Configuration menu must be used during the first installation to configure completely the NE
and also if some multiple configuration changes must be done (i.e. change of all the tributaries from
”Framed” to ”Unframed” or vice–versa for the E1 signal both in the Local and Remote NE).
486 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.9.9 Abnormal condition list
The abnormal condition list is a summary of the abnormal conditions currently active in the NE due to
manual operations such channel protection switching commands (Radio, HST Tx or Mux/Demux), Tx
muting, or any loopback (tributary, IDU, ODU).
Most of the manual operations listed in the abnormal conditions list may affect the traffic and the normal
working condition of the equipment
By CT ⇒ Diagnosis ⇒ Abnormal condition list
Press “Refresh” to actualize the list each time it is required.
Fig. 355. Abnormal condition list
3DB 16142 CAAA Ed.01A–DRAFT 487 / 576

4–5.9.10 Tx Mute functionality for interferences investigation
The local and the remote transceiver(s) can be muted by the following procedure:

By CT ⇒ Views ⇒ Radio

→ From the left window → select Channel #1 or #0
To mute the local transceivers:
→ From the lower right window → select “on” in the “Tx Local Mute field” → apply
To mute the remote station transceivers:
→ From the lower right window → select “on” in the “Tx Remote Mute” field → apply
N.B. In 1+1 configuration, Tx mute applied either on channel 1 or channel 0 will mute the two
channels transceivers at the same time.
Fig. 356. Tx Mute functionality
WARNING: The Tx Remote Mute automatically works («on» and then «off») only if performed on the
local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed,
the EC changes the channel in monodirectional way, in order to have the possibility to send
the command to remove the mute. If the Network Element has been restarted after a
MUTE, there is no more possibility to set–up the channel, because the remote address is
not known, and, any case, to set–up the channel a bidirectional communication is needed.
The only way to remove the MUTE command is with local CT or from a remote CT which
can reach the Network Element through another supervisory interface.
Interferences investigation:
In order to verify that the local equipment is not receiving a foreign signal as a frequency interference,
“Tx mute” the remote station transceivers and check that the local current received level is < –95
dBm.
For additional information refer to the handbook Interference investigation procedure, which describes
in detail how to test the radio hop in order to find possible interferences.
488 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.9.11 Tributaries 17 to 32 visible in “16E1+Ethernet” configuration
In an “16E1+ Ethernet” type configuration, operator may choose a 32 E1 frame structure capacity. In this
case, the relevant 17 to 32 tributaries bandwidth will be dedicated to the two User Ethernet ports
Nevertheless, tributaries 17 to 32 might show in the “line interface” CT view as well as in the “Loopback
view”. Since they do not physically exist, operator must ignore the lines dedicated to tributaries 17 to 32,
in the “line interface” view as well as in the “loopback view”.
Fig. 357. Tributaries 17 to 32 visible in “16E1+ Ethernet” configuration
3DB 16142 CAAA Ed.01A–DRAFT 489 / 576

4–5.10 IDU unit replacement

In general, an IDU unit can be replaced:

a) for spare part stock management:
• to check periodically the functionality of spare parts present in the spare part stock
b) or, during corrective maintenance:
• to replace a faulty (or suspected faulty) unit with the correspondent spare part
• to restore the suspected faulty unit (after its successful replacement with a spare unit during
Please refer to Fig. 351. on page 471 , for the position of this step inside the corrective maintenance
general flow–chart.
Tab. 70. herebelow lists the specific procedures, according to the unit type. These procedures are
particularly detailed in order to:
– avoid injuries to personnel (electric safety)
– avoid damages to the equipment and the spare parts
– avoid, as far as possible, traffic interruptions or degrade.
Tab. 70. IDU unit replacement procedures
UNIT PARAGRAPH PAGE
IDU MAIN unit (CH1) 4–5.10.1 491
IDU EXTENSION unit (CH0) 4–5.10.2 495
FLASH CARD (housed on MAIN unit) Chapter 4–6 505
N.B. All these procedures are based, for both “1+0” and “1+1” configurations, on the equipment
interconnection diagrams depicted in para.3–2.2 on pages 363 to 369 .
Please make reference to the equipment interconnection diagram corresponding to your
system actual layout.
490 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.10.1 IDU MAIN unit replacement procedure (CH1)
ON/OFF switch
Flash Card label
Equipment Controller
Reset pushbutton
Flash Card Flash Card cover possible additional

Identification label
identification label
of the upgrade kit
(see point [14]
on page 514)
Fig. 358. Details for IDU MAIN unit or FLASH CARD replacement
General warnings:
Screw fixing
In all described operations, the screw tightening torque must be:
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Unit uninstallation and installation
In all described operations, when it is necessary to uninstall or re–install the IDU MAIN unit
from/in the shelf, wall or desk assembly, please refer to the instructions given in the Installation
Handbook.
3DB 16142 CAAA Ed.01A–DRAFT 491 / 576

Procedure:

[1] Preliminary operations for 1+1 configurations:

Before removing the defective IDU MAIN unit, carry out following operations (operations by Craft

Terminal possible if CT working):
results on main traffic

sub–step operation by CT
and services
– enable Force on CH0 Extension’s RPS switch

[1]–A – if set as Revertive, set RPS protection scheme as
No Revertive
– enable Force on CH0 Extension’s TPS switch

in general, no
[1]–B – if set as Revertive, set TPS protection scheme as
alarms/errors on both
No Revertive
NEs (N.B.)
– enable Force on CH0 Extension’s EPS switch
– if set as Revertive, set EPS protection scheme as
[1]–C
No Revertive
(N.B.)
N.B. in case Data plug–in is present, this implies the loss of tributary Ethernet traffic on both
NEs, that cannot be avoided
[2] If the local Craft Terminal is connected, perform the logoff, then switch it off
[3] On the unit identification label present at unit rear side (see Fig. 358. on page 491) read the unit
Technical Code (read also notes in point [14] on page 514, for the possible additional identification
label of the upgrade kit)
[4] Get a spare unit with the same Technical Code (see para.4–3.3.5 on page 460 for general cautions).
N.B. If, according to the spare part policy described in para.4–3.3.3 point a ) on page 459 :
• the unit to be replaced is equipped with optional plug–in(s) (17–32xE1 plug–in, or
Audio + User Service Channel plug–in, or Data plug–in)
• and the spare unit is not equipped with such plug–in(s), that are instead available as
separate upgrade kits
you must at first install the spare plug–in(s) into the spare IDU Main unit basic, as
described in para.4–7.1 on page 509 (obviously the described unit de–installation and
re–installation steps do not apply).
[5] Disconnect following cables from the front panel of the IDU MAIN unit to be replaced, in the
recommended order:
• tributaries cables
• services cables
Notes:
• before removing cables ensure they are labeled
• in (1+1) configurations, do not remove cables on the IDU EXTENSION unit.
In this way, the tributary and user service channels traffic interruption is avoided (it continues
on channel “0” through the IDU EXTENSION unit), with exception of tributary Ethernet traffic,
if any
492 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[6] Turn off the front panel power switch (position “O”, see Fig. 358. on page 491):
• of the IDU MAIN unit to be replaced
• of the IDU MAIN spare unit

[7] if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDU
MAIN unit to be replaced.
[8] Disconnect all remaining cables from the front panel of the IDU MAIN unit to be replaced, in the
recommended order:
• IDU–ODU cable
• only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and
Extension units
• power supply cable
• all other remaining cables, if any
Note: before removing cables ensure they are labeled
SAFETY RULES
If operation indicated in previous point [7] has not been carried out, a TNV–2
(battery) voltage could be present on Station Battery input (cable side); do not
touch the pins when unplugged.
DANGER: Possibility of personal injury. Short circuiting, low-voltage,
low-impedance, DC circuits can cause severe arcing that can result in burns
terminals.
[9] Uninstall the IDU MAIN unit to be replaced and place it on the workbench
[10] Wear the antistatic protection armlet and connect its termination to a grounded structure (see
ATTENTION

this avoids the possible damage of the electronic devices for electrostatic discharges
[11] Carry out the following operations on the IDU MAIN defective unit (see Fig. 358. on page 491):
• remove the Flash Card cover

• extract the Flash Card (it will be mounted in the spare IDU Main unit)
• restore the Flash Card cover
[12] Carry out the following operations on the IDU MAIN spare unit (see Fig. 358. on page 491):
• remove the Flash Card cover

• insert the Flash Card you have extracted from the IDU MAIN defective unit in previous step [11]
• restore the Flash Card cover
[13] Now you can take off the antistatic protection armlet
[14] Install the IDU MAIN spare unit
3DB 16142 CAAA Ed.01A–DRAFT 493 / 576

[15] Reconnect following cables to the front panel of the new IDU MAIN unit, exactly as they were
connected before the faulty unit was extracted, in the following order:

• only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and

Extension units

• IDU–ODU cable
• CT–NE cable
N.B. SAFETY RULES: see previous point [8]
[16] if switched off in step [7] on page 493, switch on the circuit breaker giving power supply to the cable
connected to the new IDU MAIN unit
[17] Turn on power on the new IDU MAIN unit (position “I”, see Fig. 358. on page 491)
[18] Wait for the unit configuration (about 2 minutes)
[19] Switch on CT, start 1320CT, login and enter NE supervision
[20] Additional operation for 1+1 configurations:
operation by CT results on main traffic and services
disable Force on CH0 Extension’s RPS switch no alarms/errors on both NEs
Note: the commands Force on Extension’s TPS and EPS switches [set in previous steps [1]–B
and [1]–C on page 492] are lost due to the EC reset for IDU MAIN unit switch off/on
[21] Reconnect tributaries and services cables exactly as they were connected before the faulty unit was
extracted
[22] Check the system status using LED visual inspection and through the Craft Terminal
[23] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protection
scheme setting to Revertive is not error free.
[24] Flash Card identifier label affixing
Please read para.1–3.6.2.2 on page 90.

If the inserted IDU MAIN spare unit has no Flash Card identifier label sticked on it or the label does
not match the flash card effectively inserted, put a label with the correct information (if not available,
create a label writing the information on a self–adhesive sticker).
End of IDU MAIN unit replacement procedure
494 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.10.2 IDU EXTENSION unit replacement procedure (CH0)
ON/OFF switch
possible additional identification label Identification label

of the upgrade kit (see point [14] on page 514)
Fig. 359. Details for IDU EXTENSION unit replacement
General warnings:
Screw fixing
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Unit uninstallation and installation
In all described operations, when it is necessary to uninstall or re–install the IDU EXTENSION
unit from/in the shelf, wall or desk assembly, please refer to the instructions given in the
3DB 16142 CAAA Ed.01A–DRAFT 495 / 576

Procedure:

[1] Preliminary operations:

Before removing the IDU EXTENSION defective unit, by Craft Terminal carry out following

operations:
sub–step operation by CT results on main traffic results on services
Enable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[1]–A
Main’s RPS switch NEs NEs
Enable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[1]–B
Main’s TPS switch NEs NEs
– no alarms/errors on
remote NE
Enable Lockout on CH1 remote NE
[1]–C – 1–2 sec alarm/AIS–
Main’s EPS switch – 1 sec Slip or AIS on
Sync Loss on local
local NE
NE
[2] On the unit identification label present at unit rear side (see Fig. 359. on page 495) read the unit
Technical Code (read also notes in point [14] on page 514, for the possible additional identification
label of the upgrade kit)
[3] Get a spare unit with the same Technical Code (see para.4–3.3.5 on page 460 for general cautions).
N.B. If, according to the spare part policy described in para.4–3.3.3 point a ) on page 459 :
• the unit to be replaced is equipped with the optional 17–32xE1 plug–in
• and the spare unit is not equipped with such a plug–in, that is instead available as
separate upgrade kit
you must at first install the spare plug–in into the spare IDU Extension unit basic, as
described in para.4–7.1 on page 509 (obviously the described unit de–installation and
re–installation steps do not apply).
[4] Disconnect following cables from the front panel of the IDU EXTENSION unit to be replaced in the
recommended order:
• tributaries cables
• services cables
Notes:
• before removing cables ensure they are labeled
• do not remove cables on the IDU MAIN unit.
In this way, the tributary and user service channels traffic interruption is avoided (it continues
on channel “1” through the IDU MAIN unit)
[5] Turn off the front panel power switch (position “O”, see Fig. 359. on page 495):
• of the IDU EXTENSION unit to be replaced
• of the IDU EXTENSION spare unit
496 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[6] if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDU
EXTENSION unit to be replaced.
[7] Disconnect all remaining cables from the front panel of the IDU EXTENSION unit to be replaced, in
the recommended order:

• IDU–ODU cable
• SCSI 1+1 interconnection cable between IDU Main and Extension units
Note: before removing cables ensure they are labeled
SAFETY RULES
If operation indicated in previous point [6] has not been carried out, a TNV–2
(battery) voltage could be present on Station Battery input (cable side); do not
touch the pins when unplugged.
DANGER: Possibility of personal injury. Short circuiting, low-voltage,
low-impedance, DC circuits can cause severe arcing that can result in burns
terminals.
[8] Uninstall the IDU EXTENSION unit to be replaced
[9] Install the IDU EXTENSION spare unit
[10] Reconnect the following cables to the front panel of the new IDU EXTENSION unit, exactly as they
were connected before the faulty unit was extracted, in the recommended order:
• SCSI 1+1 interconnection cable between IDU Main and Extension units
• IDU–ODU cable
N.B. SAFETY RULES: see previous point [7]
[11] if switched off in step [6] on page 497, switch on the circuit breaker giving power supply to the cable
connected to the new IDU EXTENSION unit.
[12] Turn on power on the new IDU EXTENSION unit (position “I”, see Fig. 359. on page 495)
[13] Wait for the unit configuration (about 2 minutes)
3DB 16142 CAAA Ed.01A–DRAFT 497 / 576

[14] Carry out following operations:

sub–step operation by CT results on main traffic results on services

remote NE
Disable Lockout on CH1 remote NE
[14]–A – 1–2 sec
Main’s EPS switch – 1 sec Slip or AIS on
alarm/AIS–Sync
local NE
Loss on local NE
Disable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[14]–B
Main’s RPS switch NEs NEs
Disable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[14]–C
Main’s TPS switch NEs NEs
[15] Reconnect tributaries and services cables exactly as they were connected before the faulty unit was
extracted
[16] Check the system status through LED visual inspection and through the Craft Terminal
End of IDU EXTENSION unit replacement procedure
498 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–5.11 ODU replacement
In general, an ODU unit can be replaced:

a) for spare part stock management:

to check periodically the functionality of spare parts present in the spare part stock
b) or, during corrective maintenance:

to replace a faulty (or suspected faulty) unit with the correspondent spare part
to restore the suspected faulty unit (after its successful replacement with a spare unit during
Please refer to Fig. 351. on page 471 , for the position of this step inside the corrective maintenance
general flow–chart.
This procedure is particularly detailed in order to:

– avoid injuries to personnel (EMF safety)
– avoid damages to the equipment and the spare parts
General warnings:
ODU unit uninstallation and installation
In all described operations, when it is necessary to uninstall the faulty ODU and install the spare
ODU, please refer to possible additional instructions given in the Installation Handbook.
Microwave radiations (EMF norms)
SAFETY RULES
When operating on the antenna pole, strictly follow cautions stated in
para.A.3.8 on page 535 . In particular, if ODU is powered on from IDU, do not
stand on the antenna axis and be aware of the compliance boundaries
stated in Tab. 73. on page 536
Procedure:
[1] Get a spare ODU unit or, in case of 7–8 GHz ODU, a spare TRANSCEIVER box with the same
Technical Code of that to be replaced
[2] Preliminary operations for 1+1 configurations:

Before replacing the ODU, make sure that the traffic is transmitted over the other channel.
To do that, if ODU to be replaced is that of:
• CH1 (ODU connected to IDU MAIN unit), carry out steps [1]–A to [1]–C on page 492
• CH0 (ODU connected to IDU EXTENSION unit), carry out steps [1]–A to [1]–C on page 496
[3] Switch off the ODU by using the ON/OFF switch of the relevant IDU unit:
• for channel 1, operate on MAIN unit (position “O”, see Fig. 358. on page 491 )
• for channel 0, operate on EXTENSION unit (position “O”, see Fig. 359. on page 495 )
WARNING: this avoids a possible unrecoverable unknown condition of the spare ODU, when
ODU will be switched on in next step [9]
3DB 16142 CAAA Ed.01A–DRAFT 499 / 576

[4] If present, remove the solar shield (see Fig. 46. on page 119 and Fig. 47. on page 120)

[5] Disconnect the IDU–ODU cable at ODU side

[6] Change the ODU. NOTES:
• in case of ODU configurations 1+1 with coupler, use lever shown in Fig. 343. on page 457;
• in case of 7–8 GHz ODUs:
a) remove the faulty TRANSCEIVER box in the following way (refer to Fig. 47. on page 120):
1) leave the BRANCHING box attached to antenna or coupler, i.e. do not open
levers (B)
2) unblock the four levers (A) and separate gently the faulty TRANSCEIVER box from
the BRANCHING box
3) verify the coupling between TRANSCEIVER and BRANCHING boxes (see

para.1–4.8.2 on page 122), i.e. if the TRANSCEIVER box’s (D) (TX) is coupled to
the:
– BRANCHING box’s (B) (HIGH FREQ)
– or BRANCHING box’s (C) (LOW FREQ)
b) install the spare TRANSCEIVER box in the following way:

4) verify the presence and correct positioning of the O–RING on the spare
TRANSCEIVER box (see Fig. 48. on page 121)
5) gently couple the spare TRANSCEIVER box on the BRANCHING box in the same
position you have verified in step 3 ) above
6) fix the spare TRANSCEIVER box to the BRANCHING box using the four levers (A)
(refer to Fig. 47. on page 120)
[7] Reconnect the IDU–ODU cable at ODU side
[8] If was present, mount the solar shield that was removed in previous step [4]
[9] Switch on the ODU by using the ON/OFF switch (position “I” of the relevant IDU unit (MAIN or
EXTENSION unit) that has been switched off in previous step [3] .
500 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[10] Additional operations for (1+1) configurations:
by CT, remove forced traffic condition set in previous step [2]
To do that, if replaced ODU is that of:

• CH1 (ODU connected to IDU MAIN unit), carry out following operations:
results on main traffic and

sub–step operation by CT
services
[10]–A – disable Force on CH0 Extension’s RPS switch no alarms/errors on both NEs
[10]–B – disable Force on CH0 Extension’s TPS switch no alarms/errors on both NEs
[10]–C – disable Force on CH0 Extension’s EPS switch no alarms/errors on both NEs
• CH0 (ODU connected to IDU EXTENSION unit), carry out steps [14]–A to [14]–C on page
498
[11] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protection
scheme setting to Revertive is not error free.
[12] Check the system status through LED visual inspection and through the Craft Terminal.
End of ODU replacement procedure
3DB 16142 CAAA Ed.01A–DRAFT 501 / 576

4–5.12 Faulty unit repair and Repair Form


flow–chart.

4–5.12.1 Faulty unit sending back to repair center
The complete faulty unit (complete ODU assembly, or TRANSCEIVER box in case of 7–8 GHz
ODU, or IDU Main or Extension Unit including plug–in, if any) must be sent back to the
Alcatel–Lucent repair center.
Faulty unit repair must be done by authorized repair centers only.
4–5.12.2 Repair Form filling
To facilitate repair operation, data on the faulty unit must be reported on the form shown in
The repair form must be filled–in with as much data as possible and returned to Alcatel–Lucent
together with the faulty unit.
502 / 576 3DB 16142 CAAA Ed.01A–DRAFT

REPAIR FORM
Fill in this form and affix it to the faulty unit to be returned to Alcatel–Lucent
CUSTOMER NAME ORDER NUMBER/CONTRACT NUMBER
SITE BRANCH/UNIT/COUNTRY
SYSTEM/EQUIPMENT PRODUCT RELEASE EQUIPMENT SOFTWARE PART NUMBER
STATION/RACK SUBRACK SLOT

TO BE FILLED IN BY THE SENDER
MNEMONIC ALCATEL PART NUMBER
SERIAL NUMBER FAULTY UNIT SOFTWARE VERSION
FAULT PHASE REASON FOR REPAIR PRESUMED CAUSE
INSTALLATION / CLEAR FAULT DROP IN PERFORMANCE INTERNAL

TURN ON
LIGHTNING
OPERATION INTERMITTENT FAULT UPGRADE/QUALITY ALERT
EXTERNAL AIR COND.
MAINTENANCE TEMPERATURE FAULT OTHER
DATE NAME OF SENDER

FAULT STILL PRESENT
AFTER REPAIR
COMMENTS
PROCESSING FAULTS DETECTED

TO BE FILLED IN BY THE REPAIR OPERATOR
NO FAULTS FOUND UPGRADE SOLDERING / COMPONENT ADJUSTMENT

WIRING
A I C F–L P
STANDARD REPAIRING NOT REPAIRABLE MECHANICAL PRINTED DIRT

(REJECTED) CIRCUIT BOARD
B–D M V1 V1 V2
SUBSTITUTED
QUALITY ALERT CORROSION OTHER
I S–X V3
NOTE : LETTERS ARE FOR FACTORY USE
COMMENTS
DATE REPAIRING NUMBER REPAIRING CENTRE NAME OF REPAIR OPERATOR
Fig. 360. Repair form
3DB 16142 CAAA Ed.01A–DRAFT 503 / 576

504 / 576
4–6 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES
This chapter, for maintenance purpose, describes how to manage the spare Flash Card and how to
replace it, in case of problems.

N.B. To replace a Flash Card with a different type, for system upgrade purpose, please refer to
para.4–7.3 Flash Card upgrade on page 518.
4–6.1 Spare Flash Card management
Please refer to:
– para.1–2.5 on page 52 for detailed information on Flash Card content
– para.1–3.6 on page 89 for detailed information on Flash Card position, types and identification
A spare Flash Card:
a) usable as “specific” spare part for a certain NE must contain the same SW information stored in the
Flash Card present in the NE:
• SW committed version
• “.qcml” configuration data
• and MIB data.
In this case, such a “specific” spare Flash Card can be used at any time only to replace that existing
in that “specific” NE, provided that no change is made on the NE SW information by Craft Terminal,
TCO Suite or by TMN system.
b) supplied as “generic” spare part, contains default SW information, stored by Alcatel–Lucent factory
for testing purposes before delivery to Customer. In this case you cannot insert it “as it is” in any NE,
without making specific operations by Craft Terminal. The same warning applies also for a Flash Card
supplied as “specific” spare part for a certain NE [see point a ) above], whenever the NE SW
information has been changed by Craft Terminal or by TMN system after the system installation
phase.
In both cases, it is expected that in the plant, the following back–up information is always available for each
specific NE:
[1] the MIB back–up file
[2] the “.qcml” configuration file
[3] the “text” configuration file.
Please, refer to para.1–2.6.7 on page 64 for details.
SUGGESTION
Use one IDU Main unit of the spare–part–stock as an off–line service station (non connected to the
network) to manage the content of Flash Cards, before using them as spare parts.
3DB 16142 CAAA Ed.01A–DRAFT 505 / 576

4–6.2 Flash Card replacement procedure


The need for this replacement is for corrective maintenance purposes, whenever the failure or content
corruption of the Flash Card must be suspected
The Flash Card contains the system software (see para.1–2.5.2 on page 54). Many types are envisaged:
its identification is described in para.1–3.6.2.2 on page 90.
ATTENTION
(caution to avoid complete traffic loss)

Do not insert in the system a Flash Card the content of which you do not well know!
You must be aware that if a Flash Card with SW information different from that running in the system
is inserted “as it is”, the software download will be automatically carried out from the Flash Card
toward the System’s EC and RCs and Supervisory Units, thus causing a complete system crash.
The steps of the Flash Card replacement procedure to use, detailed in following para.4–6.2.2, depend on
the choice adopted by the Customer with reference to the type of spare flash card stored in the
spare–part–stock (refer to the Spare Flash Card management policy described in para.4–6.1 on page
505):
a) “NE–specific” spare part for a certain NE (each NE has its own “specific” spare Flash Card, kept
aligned to SW changes made on the NE in service, through an off–line service station).
b) “generic” spare part that cannot be inserted it “as it is” in any NE.
506 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–6.2.2 Execution of the Flash Card replacement
General warnings:
Screw fixing
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Procedure:
[1] Read the Flash Card Software Label on the label affixed on IDU MAIN unit (see Fig. 83. on page
174) and according to it, retrieve the Flash Card Technical Code through Tab. 22. on page 89 .
If CT works, you can verify the Flash Card Software Label by Supervision ⇒ SW Key (example
in Fig. 165. on page 262 )
[2] Get the spare Flash Card with the same Technical Code; leave it in its protective envelope until you
have worn the antistatic protection armlet
[3] Verify if the spare Flash Card is:
• really “specific” for the NE where it must be inserted, by suitable documentation that should be
together with it [the “text” configuration file mentioned in point b ) on page 505 ].
Proceed to next step [4]
• or “generic”; in this case, before proceeding to next step [4] , isolate the NE from the supervision
network.
N.B. Before to isolate the system from the supervision network, inform the supervision
center: if (from the supervision point of view), there are other NEs
cascade–connected to it (and without supervision ring network) they will be isolated,
too.
[4] Wear the antistatic protection armlet [see point b ) on page 32] and connect its termination to a
grounded structure
ATTENTION

[5] Remove the Flash Card cover (see Fig. 358. on page 491 ). Store tidily cover and screws for their
successive mount
[6] Extract the faulty Flash Card from the IDU Main Unit, verify again that its type is equal to that of the
spare Flash Card and insert the spare Flash Card (refer to Fig. 35. on page 90 for Flash Card profile
and insertion direction)
3DB 16142 CAAA Ed.01A–DRAFT 507 / 576

[7] After two minutes, login the NE by CT.
Now, if you have inserted:

• a “generic” spare Flash Card, proceed with following step [8]

• a “NE–specific” spare Flash Card, proceed with following step [9]
[8] If you have inserted a “generic” spare Flash Card, carry out following checks and operations by CT:
• verify the SW COMMITTED version in the Flash Card, as described in point [2] on page 62.
If not V2.1.0, proceed with V2.1.0 downloading and activation, as described in chapter 4–8 on
page 525.
• run the Quick Configuration by text file, as described in point b ) on page 375. When the file
selection window opens requiring a “configuration_name.qcml” file to be opened, specify the
NE’s specific file [mentioned in point b ) on page 505 ]. The window in Fig. 272. on page 379
will appear. Then, clicking repeatedly on Next buttons (without any other actions, or just
checking configuration screens, if you like), reach Step L on page 397 and click on Finish
button.
In this way the “.qcml” configuration data are loaded in the Flash Card data base.
• carry out MIB data restore and activation [using NE’s specific MIB back–up file mentioned in
point b ) on page 505 ] as shown in MIB Restore in Fig. 206. on page 305 (from operative point
of view, refer to para.2–8.3.2 and 2–8.3.3 on page 261). In alternative to activation by SW,
carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit
(see Fig. 358. on page 491 ).
In this way the MIB configuration data are loaded in the Flash Card data base.
About two minutes are necessary for the supervision process to get data from the new flash
card.
• now, you can reconnect the NE to the supervision network, and proceed with following step [9]
[9] Restore the Flash Card cover removed in previous step [5]
[11] Carry out functional checks by Craft Terminal.
End of procedure
508 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–7 SYSTEM HARDWARE UPGRADE
This chapter details all phases necessary to carry out the following hardware upgrades:
– Installation of plug–ins, para.4–7.1 below
– upgrade 9400AWY system from 1+0 to 1+1 configuration, para.4–7.2 on page 515
– install a new Flash Card to improve system capacity, para.4–7.3 on page 518
4–7.1 Installation of plug–ins
When Customer orders a 9400AWY equipment, usually , if plug–ins are included in the order, IDU Main
unit and IDU Extension unit are delivered with the required plug–ins already mounted. In such a case, this
procedure has no use.
This procedure is used whenever, after the installation of a 9400AWY equipment with no plug–in equipped,
Customer needs to upgrade it adding plug–ins.
Tab. 71. below lists the plug–ins presently available.
Tab. 71. Available plug–in upgrade kits
Notes
Technical Code Description
3DB16086AA** 32E1 ON SITE UPGRADE KIT

in alternative
3DB06610AA** 10/100BT UPGRADE KIT
3DB16089AA** AUDIO + USER SERVICE CHANNEL UPGRADE KIT
Notice that:
– in 1+0 configuration, you can equip any of the plug–in types into the IDU Main unit
– in 1+1 configuration, you can upgrade the system in one of the following ways:
• upgrade from max 16 to max 32 E1 tributaries: you must install the 17–32 E1 PLUG–IN into both
the:
– IDU Main unit
– IDU Extension unit
• upgrade to Ethernet tributaries: you must install the ETHERNET PLUG–IN into the IDU Main
unit only
• upgrade for AUDIO + USER SERVICE CHANNEL functionalities: you must install the AUDIO
+ USER SERVICE CHANNEL PLUG–IN into the IDU Main unit only.
3DB 16142 CAAA Ed.01A–DRAFT 509 / 576

4–7.1.2 Procedure

Drawings used to show operations are relevant to the IDU Main unit. Operations to be carried

out for IDU Extension unit are exactly the same.

Screw fixing
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Unit uninstallation and re–installation
In all described operations, when it is necessary to uninstall or re–install the IDU unit (MAIN or
EXTENSION) from/in the shelf, wall or desk assembly, please refer to the instructions given in
the:
– Installation Handbook
The following operations concern the IDU unit (MAIN or EXTENSION) to be upgraded:
[1] Isolate the power supply, disconnect Craft Terminal [see point f ) on page 32] and disconnect all
cables.
[2] Uninstall the unit and place it on a workbench
[3] Fig. 361. :
• if present, dismount both fixing brackets (A and B), there are two screws for each (C)
• undo the side screws D (three on each side) for cover unfix
Fig. 361. Dismounting the fixing brackets and cover unfix
510 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[4] Rotating the removed fixing brackets into both the suitable cover’s side holes, slide the box cover
out from the box base, as shown in Fig. 362. :
use of fixing bracket to sliding out the cover

release the cover
Fig. 362. Release and sliding out the cover
[5] Wear the antistatic protection armlet and connect its termination to a grounded structure (see
ATTENTION

[6] Now, you can remove the cover (Fig. 363. ):
Fig. 363. Removing the cover
3DB 16142 CAAA Ed.01A–DRAFT 511 / 576

[7] Fig. 364. : according to the plug–in to be installed, dismount the metal plate (fixed by two screws)
which closes the plug–in devoted hole. Take the two removed screws for their fixing.

plate to remove for plate to remove for

AUDIO + USER SERVICE TRIBUTARY plug–in
CHANNEL plug–in
Fig. 364. Dismounting the metal plate
[8] Fig. 365. shows in details the connectors and columns for plug–in fixing by screws
2 columns for plug–in

fixing by screws 3 columns for plug–in
fixing by screws
connectors for plug–in
connector
for plug–in
Fig. 365. Connectors and columns for plug–in fixing by screws
512 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[9] Insert the plug–in in its connector(s) depicted in previous Fig. 365. , and fix it:
• on the PCB using the 2 or 3 screws on the suitable columns depicted in previous Fig. 365.
• to the front panel by the 2 screws or the screw columns

The result must be as shown in Fig. 366. below:

Details of 16–32 E1 plug–in installed
Details of Ethernet plug–in installed
Details of Audio + User Service Channel plug–in installed
Fig. 366. Plug–in insertion and fix
3DB 16142 CAAA Ed.01A–DRAFT 513 / 576

[10] Reinsert the cover
(reverse operation of Fig. 363. on page 511)

[11] Slide in the cover

(reverse operation of Fig. 362. on page 511. The fixing brackets use is not necessary)
[13] Fix the cover and, if they were present, mount both fixing brackets
(reverse operation of Fig. 361. on page 510)
[14] Upgrade kit identification label

After this upgrading, the Unit identification label placed on the box rear side [position (C) in Fig. 22. on
page 67 for the IDU Main Unit, and in Fig. 24. on page 73 for the IDU Extension Unit] is no longer
right to correctly identify the assembly as a whole.
This could impact on spare–part–stock management and maintenance.

For this reason:
• if the upgrade kit is supplied with a suitable self–adhesive label (under study), stick it just on side
of that already existing
• otherwise create a label writing the upgrade kit P/N on a self–adhesive sticker, and stick it just
on side of that already existing.
ÉÉÉÉ
ÉÉÉÉ
additional existing
identification label identification label
of the upgrade kit of the basic unit
[15] Re–install the unit
[16] Complete upgrade operations with:
• system cabling (it is different from that previous to upgrading). Refer to the Installation
Handbook, according to the new hardware configuration
• system data re–definition (it is different from that previous to upgrading), carrying out Quick
Configuration procedure by Craft Terminal (details in para.3–2.3.7 on page 375).
• commissioning procedure, to check the new interface, (details in Chapter 3–2 –

Commissioning on page 361).
514 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–7.2 Upgrade from 1+0 to 1+1 configuration
4–7.2.1 Preface
This upgrade must be done on both stations of the radio link, first on one, then on the other, or at the same
time by two different service teams. A third phase is necessary for the radio link line–up.
a) First case: “1+0” already equipped with the Protection boxes

This procedure is based on the equipment interconnection diagrams depicted in para.3–2.2 on
pages 363 to 369 . In such diagrams you can see:
• the “1+0” configuration (”starting configuration”), already equipped with the E1 Protection box
and the Services Protection box . Please make reference to the equipment interconnection
diagram corresponding to your actual system layout.
• the corresponding “1+1” configuration (”target configuration”)
In this case the upgrade to the corresponding “1+1” configuration can be done with a small traffic
interruption time. Nevertheless, the full link unavailability must be planned for the phase [C] .
b) Second case: “1+0” not equipped with the Protection boxes

Due to full hardware changes, station DDF refurbishing, cable extraction/insertion and system switch
off/on need, much more link unavailability time must be foreseen for the upgrade, with respect to case
a ) above.
In this case, too, you must use one of the “1+1” equipment interconnection diagrams depicted in
para.3–2.2 on pages 363 to 369 as ”target configuration”.
N.B. Operations by Craft Terminal on each station must be done by local ECT through ’F’ or Ethernet
interface only, while the use of RECT is not admitted.
This procedure is particularly detailed in order to:

– avoid injuries to personnel (EMF safety)
– avoid damages to the equipment
General warnings:
Microwave radiations (EMF norms)
SAFETY RULES
When operating on the antenna pole, strictly follow cautions stated in
para.A.3.8 on page 535 . In particular, if ODU is powered on from IDU, do not
stand on the antenna axis and be aware of the compliance boundaries
stated in Tab. 73. on page 536
3DB 16142 CAAA Ed.01A–DRAFT 515 / 576

4–7.2.2 Procedure
[1] For both stations, ascertain to have all materials necessary for the HW upgrade, at IDU and ODU

levels, as well as necessary installation materials.

For materials necessary for hardware upgrade, please refer to the:
• para.1–3.1 on page 66 (standard materials for IDU)
• Installation Handbook (ODU provisioning and additional installation materials for IDU and
ODU)
PHASE [A] : OPERATIONS ON FIRST STATION
[2] Preliminary operations to be done only in case of “1+0” system not equipped with the Protection
boxes:
a) switch off the IDU MAIN unit and disconnect all tributary (with the exception of Ethernet, if any)
and services cables from its front panel
b) using the instructions given in the Installation Handbook:
– install the E1 Protection box and the Services Protection box
– install the IDU EXTENSION unit
N.B. connect its power supply plug to the station battery, but ascertain that its
ON/OFF switch is in OFF position and leave it in OFF position till step [9]
– connect the IDU MAIN and EXTENSION units to the E1 Protection box and the Services
Protection box
– connect the E1 Protection box and the Services Protection box to the station DDF
c) switch on the IDU MAIN unit, connect the Craft Terminal, switch it on, start 1320CT and login
the NE (details in para.2–2.5.2 on page 177) and verify the link functionality
[3] If not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details in
para.2–2.5.2 on page 177)
[4] Using the instructions given in the Installation Handbook , install the second ODU; for general
information, make reference to Fig. 4. on page 37). Warning: in case of 1+1 ODU configuration:
a) with two antennas, install the second ODU with its own antenna
b) with 1+1 coupler:
– if the coupler is already installed, fix the second ODU to the coupler, then go to step [5]
– if the coupler is not installed, carry out following operations (full link unavailability from
substep 3 ) till substep 6 ):
1) by Craft Terminal, disable ATPC on CH1 (if enabled): see para.2–6.4.1 on page
246
2) carry out NE logoff (details in para.2–2.5.3 on page 184)
3) switch off IDU MAIN unit (CH1)
4) disconnect ODU CH1 from antenna, connect the 1+1 coupler to the antenna, and
connect the ODU CH1 to the 1+1 coupler
5) switch on IDU MAIN unit (CH1)
6) wait until system restart completion, then start 1320CT and login the NE (details in
7) by Craft Terminal, enable ATPC on CH1 (if necessary): see para.2–6.4.1 on page 246
516 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[5] Only in case of “1+0” system already equipped with the Protection boxes: install the CH0 IDU
EXTENSION unit and connect it to the E1 Protection box and the Services Protection box, using
the instructions given in the Installation Handbook

N.B. connect its power supply plug to the station battery, but ascertain that its ON/OFF switch
is in OFF position and leave it in OFF position till step [9]
[6] Connect the 100–pin cable to both IDU MAIN and EXTENSION units, using the instructions given
in the Installation Handbook
[7] Connect the IDU–ODU cable (between the “CH0 Extension IDU” and the second ODU), using the
instructions given in the Installation Handbook
[8] By Craft Terminal carry out the following operations:

1) System Setting ⇒ NE Configuration ⇒ 1+1 Configuration: see para.2–3.4.1 on page 215
2) Set EPS (Mux/Demux Protection) Lockout: see para.2–9.1 subpara.2–9.1.2 on page 265.
WARNING: this operation is not error free
3) Set HST Lockout: see para.2–9.3 subpara.2–9.3.2 on page 272
4) Set CH0 Tx Power as follows: with reference to Fig. 147. on page 245:
select Channel #0 ⇒ click on “RTPC & ATPC” ⇒ insert value in “Tx Power(dBm)” field ⇒ Apply
5) Set CH0 Tx Frequency as follows: with reference to Fig. 307. on page 412:
select Channel #0 ⇒ click on “Frequency” ⇒ insert value in “Tx Frequency(kHz)” field ⇒ Apply
[9] Switch on the CH0 Extension IDU by its ON/OFF switch
[10] By Craft Terminal carry out the following operations:

1) Set CH0 Frequency Shifter as follows: with reference to Fig. 307. on page 412:
select Channel #0 ⇒ insert value in “Shifter” field ⇒ Apply
2) Remove HST Lockout: see para.2–9.3 subpara.2–9.3.2 on page 272
3) Remove EPS (Mux/Demux Protection) Lockout: see para.2–9.1 subpara.2–9.1.2 on page 265.
WARNING: this operation is not error free
4) Restart NE: see para. 2–8.2 on page 258
PHASE [B] : OPERATIONS ON SECOND STATION
[11] Repeat the previous steps in the other station of the radio link
PHASE [C] : OPERATIONS ON THE LINK
N.B. These operations are meant for the radio link as a whole, and imply full link unavailability.
[12] In case of ODU configuration with two antennas, carry out the alignment of the second ODU antenna
(N.B.)
[13] Carry out the CH0 functionality test (N.B.).
N.B. For details on commissioning procedures, please refer to the Chapter 3–2 on page 361.
PHASE [D] : NE DATA SAVE
[14] Save data of both NEs as explained in para.1–2.6.8 on page 64.
End of procedure
3DB 16142 CAAA Ed.01A–DRAFT 517 / 576

4–7.3 Flash Card upgrade


Please refer to:
– para.1–2.5 on page 52 for detailed information on Flash Card content
– para.1–3.6 on page 89 for detailed information on Flash Card position, types and identification
N.B. To replace a Flash Card with the same type, for maintenance purpose, please refer to
para.4–6.2 – Flash Card replacement procedures on page 506.
In general, the Flash Card upgrade must be done together with HW changes, e.g. changing the system
capacity from “16xE1” to “32xE1” requires to:
– change:
• the existing Flash Card “16E1/32Mbps DATA 4/16QAM” with the “32E1DS1 4/16QAM”
corresponding to the change of the:
• Software Key Label from “16E1DS1E3DS3 4/16QAM” to “32E1DS1 4/16QAM”
This chapter explains how to do this operation.
– and install (if not yet present) the 17–32xE1 PLUG–IN in the IDU MAIN UNIT, as well in the IDU
EXTENSION UNIT in case of 1+1 systems; to carry out this operation, please refer to para.4–7.1 –
Installation of plug–ins on page 509.
518 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–7.3.2 Summary procedure for both stations
This example is for changing the existing Flash Card “16E1/32Mbps DATA 4/16QAM” with the “32E1DS1
4/16QAM”. Adapt it to the actual change you must do.

Tab. 72. Flash card upgrade carried out by one operator only for both stations
STEP 2 IN STATION A
STEP 1 IN STATION B notes
(in series to step1)
Current configuration Back–up idem
Flash card replacement. This requires, in
typical condition (rack installation), to
switch the IDU off and disconnect cables;
otherwise, if the installation condition idem
allows to replace the flash card without
disconnecting cables, the NE supports an
hot replacement
IDU switch–on (after re–cabling) or NE
Restart (in case of hot replacement), Start
idem
Supervision & Open USM (empty due to
the non–preconfigured flash card)
Check that the SW Key is the new one idem
MIB Restore / Activation, Start Supervision
idem
& Open USM
Quick configuration. In this case
(=dialogue with ODU already established),
the shifter and TX frequency are allowed to
be set also by Quick config. The NE type idem
is modified to 32E1 and the Tributary
config is set again to 16E1 (not to 32E1
as desired)
Re–opening USM
Go to STATION A and carry out operations
detailed in column STEP 2
Open Local and Remote USM
CHANGE REMOTE CONFIG BY
SYSTEM SETTING FROM 16E1 TO 32E1
CAPACITY the traffic is
impacted for
CHANGE LOCAL CONFIG BY SYSTEM about 1 min
SETTING FROM 16E1 TO 32E1
CAPACITY
Following paragraphs are given just for Operators who need to know what to do in detail for:
– Ordering the new Flash Card
– Installation of a new Flash Card fully configured in factory
– Installation of a new Flash Card not configured in factory
3DB 16142 CAAA Ed.01A–DRAFT 519 / 576

4–7.3.3 Ordering the new Flash Card

Whenever the Base configuration of the 9400AWY NE must be upgraded, Customer must order a new

Flash Card:

– of the type consistent with the equipment configuration he wants: see Tab. 22. on page 89 ,
– and preferably, already set by Alcatel–Lucent Factory:
• with the same SWP–version (V2.1.0) present in the 9400AWY system to be upgraded, already
present in the Flash–Card’s SW committed version bank
• with the same NE network routing data (and other configuration data) of the system to be
upgraded (for this purpose, Customer can save the NE’s “.qcml” configuration file on
floppy–disk as explained in chapter 3–2.3.6 on page 373 and give it to Alcatel–Lucent Factory).
• with the same MIB of the system to be upgraded (for this purpose, Customer can save the MIB
on floppy–disk as explained in chapter 2–14 on page 305 and give it to Alcatel–Lucent Factory).
To install a new Flash Card fully configured in factory carry out operations in para.4–7.3.4 on page 521.
To install a new Flash Card not configured in factory carry out operations in para.4–7.3.5 on page 522.
520 / 576 3DB 16142 CAAA Ed.01A–DRAFT

4–7.3.4 Installation of a new Flash Card fully configured in factory
General warnings:
Screw fixing
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Use of this procedure
This procedure can be carried out only if the new Flash Card is delivered with SW and data as
specified in para.4–7.3.3 on page 520 .
Procedure:
After having got the new Flash Card, the phases for the Flash Card upgrading are:
[1] get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protection
armlet
[2] wear the antistatic protection armlet [see point b ) on page 32 ] and connect its termination to a
grounded structure
ATTENTION

[3] remove the Flash Card cover (see Fig. 358. on page 491 ). Store tidily cover and screws for their
successive mount
[4] extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 35. on page
90 for Flash Card profile and insertion direction)
[5] carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit (see
Fig. 358. on page 491 ).
About two minutes are necessary for the supervision process to get data from the new flash card.
[6] restore the Flash Card cover removed in step [3] above (screw tightening torque as specified above)
[7] now you can take off the antistatic protection armlet
[8] if not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details in
[9] carry out the Interactive Quick Configuration procedure by Craft Terminal [details in para.3–2.3.7
point a ) on page 375], to change the system capacity
[10] carry out functional checks by Craft Terminal
[11] save NE data as explained in para.1–2.6.8 on page 64.

[12] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card Software
Label, get and stick it over the older one [see (A) in Fig. 22. on page 67 ); (N.B. if possible, remove
the older self–adhesive label before sticking the newer).
End of procedure
3DB 16142 CAAA Ed.01A–DRAFT 521 / 576

4–7.3.5 Installation of a new Flash Card not configured in factory

General warnings:

Screw fixing
2.8 kg x cm (0.28 Newton x m) 10 %

2.4317 in lb (0.2026 ft lb) 10 %
Use of this procedure
With this procedure, the system is isolated from the supervision network.
In fact, the insertion in a 9400AWY system connected to the network of a Flash Card with:
– “default” or “unknown“ NE network routing data
– SW Commit Version “unknown“ or lower than that present on the system
must be absolutely avoided.
Procedure:
After having got the new Flash Card, the phases for the Flash Card upgrading are:
[1] get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protection
armlet
[2] if not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details in
[3] by Craft Terminal:
1) run the Interactive Quick Configuration procedure by Craft Terminal [details in para.3–2.3.7
point a ) on page 375]. In the last screen (Step L on page 397) click on Save As button:
configuration data are saved in a “configuration_name.qcml” file
2) save the MIB data as shown in MIB BackUp in Fig. 206. on page 305 (from operative point of
view, refer to para.2–8.3.1 on page 260)
[4] carry out NE logoff
[5] isolate the NE from the supervision network

N.B. Before to isolate the system from the supervision network, inform the supervision center:
if (from the supervision point of view), there are other NEs cascade–connected to it (and
without supervision ring network) they will be isolated, too.
[6] wear the antistatic protection armlet [see point b ) on page 32 ] and connect its termination to a
grounded structure
ATTENTION

[7] remove the Flash Card cover (see Fig. 358. on page 491 ). Store tidily cover and screws for their
successive mount
[8] extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 35. on page
90 for Flash Card profile and insertion direction)
[9] restore the Flash Card cover removed in step [7] above (screw tightening torque as specified above)
522 / 576 3DB 16142 CAAA Ed.01A–DRAFT

[10] now you can take off the antistatic protection armlet
[11] login the NE and, by Craft Terminal, perform following operations:

1) verify the SW COMMITTED version in the Flash Card, as described in point [2] on page 62.
If not V2.1.0, proceed with V2.1.0 downloading and activation, as described in chapter 4–8 on
page 525.
2) run the Quick Configuration by text file, as described in point b ) on page 375. When the file
selection window opens requiring a “configuration_name.qcml” file to be opened, specify the
NE’s specific file you have saved in previous step [3]–1 ) on page 522. The window in
Fig. 272. on page 379 will appear. Then, clicking repeatedly on Next buttons (without any other
actions, or just checking configuration screens, if you like), reach Step L on page 397 and click
on Finish button.
In this way the “.qcml” configuration data are loaded in the Flash Card data base.
3) carry out MIB data restore and activation [using NE’s specific MIB back–up file you have saved
in previous step [3]–2 ) on page 522] as shown in MIB Restore in Fig. 206. on page 305 (from
operative point of view, refer to para.2–8.3.2 and 2–8.3.3 on page 261). In alternative to
activation by SW, carry out the Equipment Controller HW Reset, pushing the suitable button
on IDU MAIN Unit (see Fig. 83. on page 174).
In this way the MIB configuration data are loaded in the Flash Card data base.
About two minutes are necessary for the supervision process to get data from the new flash
card.
[12] carry out the Interactive Quick Configuration procedure by Craft Terminal [details in para.3–2.3.7
point a ) on page 375], to change the system capacity
[13] connect the system to the supervision network
[14] carry out functional checks by Craft Terminal
[15] save NE data as explained in para.1–2.6.8 on page 64.
[16] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card Software
Label, get and stick it over the older one [see (A) in Fig. 22. on page 67 ); (N.B. if possible, remove
the older self–adhesive label before sticking the newer).
N.B. In alternative, if an off–line IDU MAIN unit is available at Customer premises, the Flash Card
can be prepared on it, and then installed on the target system as described in previous
para.4–7.3.4 on page 521.
End of procedure
3DB 16142 CAAA Ed.01A–DRAFT 523 / 576

524 / 576
4–8 SWP DOWNLOAD TOWARD NE
This chapter details all phases necessary to download inside the NE equipment environment, and then
activate, a SWP having a version greater than that presently loaded in the NE’s Flash Card.
As this manual deals with the first version V2.1.0 of the SWP 2.1, carrying out this
procedure is not necessary because the flash cards delivered with the equipment
are loaded with SWP version V2.1.0, and there is no need to update them by SWP
download.
4–9 ECT & NE UPGRADE TO A NEW SWP ’VERSION’ (SAME NE ’RELEASE’)

This chapter details all phases necessary to install a new SWP ’version’ in the PC environment as well
as in the equipment environment.
This procedure can be used only in the case depicted in point 1 ) on page 63, i.e.:
– ECT and equipment are both running with a generic version ’A.B.c’ (’A.B’ is the NE release, ’c’ is the
SWP version)
– a new version of SWP ’A.B.d’ (d > c), is delivered to Customer.
As this manual deals with the first version V2.1.0 of the SWP 2.1, carrying out this
procedure is not necessary.
3DB 16142 CAAA Ed.01A–DRAFT 525 / 576

4–10 SWP DE–INSTALLATION

This chapter describes how to de–install from the PC the Craft Terminal Software Package components.

This can be useful, for example, when a version of the software package is no more updated.

To de–install the following procedures can be followed:
– automatically, using the CD–ROM containing the installed Software–version product.
– manually, with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CD–ROM
containing the relevant Software product is not available.
Practically, the manual de–installation of the installed SW components must be done in the opposite
sequence by which they were installed by the automatic installation process.
Manual procedure
N.B. Before starting this procedure, check that no SW components (or sub–processes) are
active; in case of doubts, restart the PC (switch it off / on).
From Control Panel select Add/Remove Programs and de–install the components in the following
order:
1) CT–NE–ConfUpd (if present)
2) ALCATEL JUSM Help On Line (for all versions you like to remove)
3) ALCATEL SW Package REG.9400AWY (for all versions you like to remove)
4) ALCATEL Radio Common JUSM (for all versions you like to remove)
5) ALCATEL Q3CT–K–ADD–ONvX.Y.Z (1320CT)
6) ALCATEL SNMPCT–K–ADD–ONvX.Y.Z (1320CT)
7) ALCATEL HOLCT–K–ADD–ONvX.Y.Z (1320CT)
8) ALCATEL CT–KvX.Y.Z (1320CT)
9) Alcatel Lower Layers Manager & Tiny Tools
10 ) Java 2 Runtime Environment. SE vX.Y.Z_KJ
a) END OF SECTION 4
526 / 576 3DB 16142 CAAA Ed.01A–DRAFT

SECTION 5: APPENDICES

Appendix A – Safety–EMC–EMF–ESD norms and equipment labelling

It describes the equipment labelling and the norms mandatory or suggested that must
529
be considered to avoid injuries on persons and/or damage to the equipment.
Moreover the labels affixed to the IDU and ODU equipment are described.
Appendix B – ECT–Equipment connection via public switched telephone

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

It contains all information regarding this handbook (purpose, applicability, history) and
551
the Customer Documentation set it belongs to, in particular the list of the handbooks
the Operators should have in order to carry out the required operations.
Appendix D – List of symbols and abbreviations, Glossary of terms 561
3DB 16142 CAAA Ed.01A–DRAFT 527 / 576

528 / 576
APPENDIX A: SAFETY–EMC–EMF–ESD NORMS AND EQUIPMENT LABELLING
A.1 : Introduction
This appendix describes the equipment labelling and the norms mandatory or suggested (see also point
d ) on page 29) that must be considered to avoid injuries on persons and/or damage to the equipment.
The stated norms apply both to the operations described in this manual and to those described in the
related manuals listed in para.C.2.1 on page 555.
– Compliance with International Standards herebelow
– Safety Rules on page 530 including:
• General Rules on page 530

• Labels Indicating Danger, Forbiddance, Command on page 531
• Dangerous Electrical Voltages on page 532
• Risks of Explosions on page 533
• Moving Mechanical Parts on page 533
• Equipment connection to earth on page 534
• Heat–radiating Mechanical Parts on page 534
• Microwave radiations (EMF norms) on page 535
• Specific safety rules in this handbook on page 536
– Electromagnetic Compatibility (EMC norms) on page 537 including:
• EMC General Norms – Installation on page 537

• EMC General Norms – Turn–on, Tests & Operation on page 537
• EMC General Norms – Maintenance on page 537
– Equipment protection against electrostatic discharges on page 538
– Suggestions, notes and cautions on page 538
– Labels affixed to the 9400AWY equipment on page 539
A.2 : Compliance with International Standards
Refer to chapter 1–5 on page 125.
3DB 16142 CAAA Ed.01A–DRAFT 529 / 576

A.3 : Safety Rules

A.3.1 : General Rules

• Before carrying out any installation, turn–on, tests & operation and maintenance operations
carefully read the related parts of this Manual or other Handbooks, in particular:
– Installation: 9400AWY Installation Handbook
– Commissioning: Chapter 3–2 on page 361
– Maintenance: Section 4: Maintenance and Upgrade on page 447
• Observe safety rules
– When equipment is operating nobody is allowed to have access inside on the equipment
parts which are protected with Cover Plate Shields removable with tools
– In case of absolute need to have access inside, on the equipment parts when it is operating
this is allowed exclusively to service personnel, where for Service Personnel or Technical
assistance is meant :
”personnel which has adequate Technical Knowledge and experience necessary to be

aware of the danger that he might find in carrying out an operation and of the necessary
measurements to reduce danger to minimum for him and for others”.
The Service Personnel can only replace the faulty units with spare parts.
The Service Personnel is not allowed to repair: hence the access to the parts no specified
is not permitted.
The keys and/or the tools used to open doors, hinged covers to remove parts which give
access to compartments in which are present high dangerous voltages must belong
exclusively to the service personnel.
– For the eventual cleaning of the external parts of the equipment, absolutely do not use any
inflammable substance or substances which in some way may alter the markings,
inscriptions ect.
– It is recommended to use a slightly wet cleaning cloth.
• The Safety Rules stated in the handbook describe the operations and/or precautions to observe
to safeguard service personnel during the working phases and to guarantee equipment safety,
i.e., not exposing persons, animals, things to the risk of being injured/damaged.
• Whenever the safety protection features have been impaired, REMOVE POWER.
To cut off power proceed to switch off the power supply units as well as cut off power station
upstream (rack or station distribution frame).
• The safety rules described in this handbook are distinguished by the following symbol and
statement:
SAFETY RULES
530 / 576 3DB 16142 CAAA Ed.01A–DRAFT

A.3.2 : Labels Indicating Danger, Forbiddance, Command
It is of utmost importance to follow the instructions printed on the labels affixed to the units and assemblies.
The labels are fully compliant with International Norms ISO 3846–1984. The symbols or statements are
enclosed in geometric shapes: ISO 3864–1984.
CONTAINS A SYMBOL STATEMENT

INDICATES FORBIDDANCE (WHITE BACKGROUND
WHIT RED RIM–BLACK SYMBOL OR STATEMENT)
IT IS A COMMAND (BLUE BACKGROUND–WHITE
SYMBOL OR STATEMENT).
CONTAINS A SYMBOL
INDICATES WARNING OR DANGER (YELLOW
BACKGROUND–BLACK SYMBOL AND RIM)
CONTAINS A STATEMENT PROVIDING INFORMATION

OR INSTRUCTION.
(YELLOW BACKGROUND–BLACK STATEMENT AND RIM)
The labels have been affixed to indicate a dangerous condition. They may contain any standard–known
symbol or any statement necessary to safeguard users and service personnel against the most common
ones, specifically:
• dangerous electrical voltages
• harmful optical signals
• risk of explosion
• moving mechanical parts
• heat–radiating Mechanical Parts
• microwave radiations
Pay attention to the information stated in the following, and proceed as instructed
The symbols presented in para.A.3.3 through A.3.8 are all the possible symbols that
could be present on Alcatel–Lucent equipment, but are not all necessarily present on the
equipment this handbook refers to.
3DB 16142 CAAA Ed.01A–DRAFT 531 / 576

A.3.3 : Dangerous Electrical Voltages

A.3.3.1: Electrical safety: Labelling

The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 Vdc).
If it is a Class 1 equipment connected to mains, then the label associated to it will state that the equipment
will have to be grounded before connecting it to the power supply voltage, e.g.:
WARNING !
Ground protect the equipment before
connecting it to the mains
Make sure that power has been cut off
before disconnecting ground protection.
A.3.3.2: Electrical safety: general rules
DANGER! Possibility of personal injury: carefully observe the specific

procedures for installation / turn–up and commissioning / maintenance of equipment parts where D.C..
power is present, described in the relevant installation / turn–up and commissioning / maintenance
documents and the following general rules:
a) Personal injury can be caused by –48 V DC. Avoid touching powered terminals with any exposed
part of your body.
b) Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result in
burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with
primary circuits. Exercise caution to avoid shorting power input terminals.
532 / 576 3DB 16142 CAAA Ed.01A–DRAFT

A.3.4 : Risks of Explosions
A.3.4.1: Labelling and safety instructions

This risk is present when batteries are used, and it is signalled by the following label:
Therefore, slits or apertures are made to let air circulate freely and allow dangerous gasses to down flow
(battery–emitted hydrogen). A 417–IEC–5641 Norm. compliant label is affixed next to it indicating that the
openings must not be covered up.
A.3.5 : Moving Mechanical Parts
The following warning label is affixed next to fans or other moving mechanical parts:
Before carrying out any maintenance operation see that all the moving mechanical parts have been
stopped.
3DB 16142 CAAA Ed.01A–DRAFT 533 / 576

A.3.6 : Equipment connection to earth

Terminals for equipment connection to earth , to be done according to international safety standards, are

pointed out by the suitable symbol:

terminal
symbol
The position of earth connection terminals is specified in the equipment Installation Handbook.
A.3.7 : Heat–radiating Mechanical Parts
The presence of heat–radiating mechanical parts is indicated by the following warning label in compliancy
with IEC 417 Norm, Fig.5041:
DANGER! Possibility of personal injury: carefully observe the specific

procedures for installation / turn–up and commissioning / maintenance of equipment parts where
heat–radiating mechanical parts are present, described in the relevant installation / turn–up and
commissioning / maintenance documents and the following general rule:
a) Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part of
your body.
534 / 576 3DB 16142 CAAA Ed.01A–DRAFT

A.3.8 : Microwave radiations (EMF norms)
Equipment emitting RF power (Reminder from site preparation procedure):

– The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.
– The following rules should be strictly applied by Customer:
• Non authorized persons should not enter the compliance boundaries, if any, for the general
public.
• Compliance RF boundaries, if any, related to Electro Magnetic Field exposure must be marked.
• Workers should be allowed to switch–off the power if they have to operate inside compliance
boundaries.
• Assure good cable connection.
• Install the antenna as high as possible from floor or area with public access ( if possible the
cylinder delimitating the compliance boundaries, if any, or the cylinder corresponding to the
transmission area directly in front of antenna with the same diameter as the antenna, more than
2 meters high).
• Install the antenna as far as possible from other existing equipment emitting RF power.
– Anyway remind that someone standing in front of the 9400AWY antenna may cause traffic
shutdown.
Place the relevant stickers:
On the site when applicable (when people can cross the compliance
boundaries and/or the transmission area of the antenna, i.e. roof top
installation)
– Warning label “Do not stand on the antenna axis”
On the mast (front side)

– EMF emission warning sign (Yellow and black) to be placed at bottom of
antenna, visible by someone moving in front of the antenna (roof top
EMF emission
installation)
warning sign
On the antenna (rear side)

– EMF emission warning sign, placed on the antenna.
3DB 16142 CAAA Ed.01A–DRAFT 535 / 576

Compliance boundaries:

Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna:

B
System Modulation Worst Configuration A (m) B (m)
1+0 with integrated antenna

9413 AWY Rel 2.0 4 QAM 0,4 2,63
(13 GHz 1ft. SP integrated antenna)

9415 AWY Rel 2.0 4 QAM 0,4 0,55

9418 AWY Rel 2.0 4 QAM 0,4 0,71
Antenna configurations:
a ) 1+0 with 1ft. integrated antenna
b ) 1+1 HSB with coupler and 1ft. integrated antenna
c ) Configuration with separated 1ft. antenna
A.3.9 : Specific safety rules in this Manual
Specific safety rules are specified in the following parts:

– chapter 3–2 para.3–2.9 on page 443
– chapter 4–5 :
• para.4–5.2.2 on page 468
• para.4–5.3.1 on page 469
• para.4–5.10.1 on page 493
• para.4–5.10.2 on page 497
• para.4–5.11 on page 499
536 / 576 3DB 16142 CAAA Ed.01A–DRAFT

A.4 : Electromagnetic Compatibility (EMC norms)
The equipment’s EMC norms depend on the type of installation being carried out (cable termination,
grounding etc.,) and on the operating conditions (equipment, setting options of the electrical/electronic
units, presence of dummy covers, etc.).
• Before carrying out any installation, turn–on, tests & operation and maintenance operations
carefully read the related parts of this Manual or other Handbooks, in particular:
– Installation: 9400AWY Installation Handbook

– Commissioning: Chapter 3–2 on page 361
– Maintenance: Section 4: Maintenance and Upgrade on page 447
• The norms set down to guarantee EMC compatibility, are distinguished inside this handbook
by the symbol and term:
ATTENTION EMC NORMS
A.4.1 : EMC General Norms – Installation
• All connections (towards the external source of the equipment) made with shielded cables use
only cables and connectors suggested in this Manual or in the relevant Plant Documentation,
or those specified in the Customer’s”Installation Norms.” (or similar documents)
• Shielded cables must be suitably terminated
• Install filters outside the equipment as required
• Ground connect the equipment utilizing a conductor with proper dia. and impedance
• Mount shields (if utilized), previously positioned during the installation phase, but not before
having cleaned and decrease it.
• Before inserting the shielded unit proceed to clean and decrease all peripheral surfaces
(contact springs and connection points, etc.)
• Screw fasten the units to the subrack.
• To correctly install EMC compatible equipment follow the instructions given.
A.4.2 : EMC General Norms – Turn–on, Tests & Operation
• Preset the electrical units as required to guarantee EMC compatibility

• Check that the equipment is operating with all the shields properly positioned (dummy covers,
ESD connector protections, etc.)
• To properly use EMC compatible equipment observe the information given
A.4.3 : EMC General Norms – Maintenance
• Before inserting the shielded unit, which will replace the faulty or modified unit, proceed to clean
and decrease all peripheral surfaces (contact springs and connection points, etc.)
• Clean the dummy covers of the spare units as well.
• Screw fasten the units to the subrack.
3DB 16142 CAAA Ed.01A–DRAFT 537 / 576

A.5 : Equipment protection against electrostatic discharges

Before removing the ESD protections from the monitors, connectors etc., observe the precautionary

measures stated. Make sure that the ESD protections have been replaced and after having terminated

the maintenance and monitoring operations.
Most electronic devices are sensitive to electrostatic discharges, to this concern the following warning
labels have been affixed:
Observe the precautionary measures stated when having to touch the electronic parts during the
installation/maintenance phases.
Workers are supplied with antistatic protection devices consisting of (see Fig. 1. on page 32):
• an elasticized band worn around the wrist
• a coiled cord connected to the elasticized band and to the stud on the subrack.
A.6 : Suggestions, notes and cautions
Suggestions and special notes in this handbook are marked by the following symbol:
Suggestion or note....
Cautions to avoid possible equipment damage are marked by the following symbol:
TITLE...

statement....
538 / 576 3DB 16142 CAAA Ed.01A–DRAFT

A.7 : Labels affixed to the 9400AWY equipment
This paragraph indicates the positions and the information contained on the identification labels affixed
to the equipment, with the exception of those already mentioned in para.A.3.2 (page 531) thru’ A.5 (page
538).
A.7.1 : Labels affixed on the IDU
This label is affixed on the back side of:
– the IDU MAIN unit [position (C) in Fig. 22. on page 67 ]
– the IDU EXTENSION unit [position (C) in Fig. 24. on page 73 ]
A C
B
this label is just an example
Alcatel Logo
ALCATEL
9400AWY Equipment Acronym

12345 (example) Notified body
N.B. this symbol is present only on equipment
supplied by Alcatel–Lucent from August 13th,
2005
Electrostatic Device Logo
Logistical item 3DB 05620 AAXX (example) Technical Code for Customer
A Technical Code for Customer, bar code 128
P/N ICS 3DB 05620 AAAA 01 (example) Factory Technical Code + ICS
B Factory Technical Code + ICS, bar code 128
SERIAL N CW052402145 (example)
Factory serial number
SERIAL N CW052402141 (example)
C Factory serial number bar code 128
24 V ± 20%, 2.2 A max (example) Power Supply Version 24 V
48–60 V ± 20%, 1.1–0.7 A (example) Power Supply Version 48/60 V
24–60 V ± 20%, 2.2–0.7 A (example) Power Supply Version Full Range
Feeding to Continuous Current
Fig. 367. Label affixed on the IDU
3DB 16142 CAAA Ed.01A–DRAFT 539 / 576

A.7.2 : Labels affixed on the ODU

a) the following label is affixed externally to all types of ODU and ODU’s TRANSCEIVER boxes (see

Fig. 46. on page 119 and Fig. 47. on page 120):

A
A9400 Equipment Acronym & Alcatel Logo

ALCATEL

N.B. this symbol is present only on equipment
supplied by Alcatel–Lucent from August 13th,
2005
55 1.5A Power supply (Feeding to Continuous Current)
Logistical Item 3CC13007AAXX (example) Technical Code for Customer
A Technical Code for Customer, bar code 128
Serial no LM0348T05EJ (example) Factory Serial number
B Factory Serial number bar code 128
TX Frequency MHz 38319,75–38876,25
Working frequency range
(example)
Shifter 1260 MHz (example) Shifter
TX Sub–band 2 – 2P (example) TX Sub–band
Initial SW/ICS 3CC13007AAAA 02 (example) ANV P/N and ICS of the software loaded in factory
PN/ICS 3CC12988AAAA 01 (example) ANV P/N + ICS
C ANV P/N + ICS bar code 128
Fig. 368. Label affixed on the ODU and ODU’s TRANSCEIVER box
b) only for 7–8 GHz ODUs, an additional label is placed on the branching assembly (for details refer to
Fig. 49. and Fig. 50. on pages 122–123).
540 / 576 3DB 16142 CAAA Ed.01A–DRAFT

APPENDIX B: ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED
TELEPHONE NETWORK
B.1 : Introduction
This chapter explains the operations necessary to allow the remote connection to the F–Interface, from
a local PC (with external or internal modem) configured as ECT, through a switched telephone line of the
standard Public Telephone Network, as shown in Fig. 369. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.
local side remote side

(ECT side) (equipment side)
F Interface
Port COM
Telephone
network
Local Remote
PC/ECT Modem
Modem
PC–LAPTOP/ECT
with internal modem
Fig. 369. ECT–Equipment connection via Public Switched Telephone Network
3DB 16142 CAAA Ed.01A–DRAFT 541 / 576

B.2 : Certified equipment

The connection has been successfully tested:

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

characteristics as in para.3–1.1.1 on page 313
2) with internal modem:

PC laptop Dell Latitude:
– Processor equipped: PENTIUM III
– Operating system: Microsoft Windows 2000 v. 5.00.2195 service pack 2
– RAM equipped: 128 Mbytes
– Hard disk equipped: 10 Gbytes
– Internal Modem: 3COM 56K v.90 Mini PCI MODEM
c) and with the following local/remote combinations:
Local Modem Remote Modem
Sportster Flash
Sportster Flash TD 32 AC
3Com 56K Faxmodem
TD 32 AC
TD 32 AC Sportster Flash
3Com 56K Faxmodem
TD 32 AC
PC laptop Dell Latitude as in
Sportster Flash
point b ) 2 ) above
3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customer’s charge.
542 / 576 3DB 16142 CAAA Ed.01A–DRAFT

B.3 : Connection cables
In the following figures, the cables for the connections are described:
PC/ECT (DTE) Local Modem (DCE)

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

Cannon 25 pins male Cannon 9 pins male
TD 2 3 TD
RD 3 2 RD
RTS 4 7 RTS
CTS 5 8 CTS
DSR 6 6 DSR
CTS 20 4 DTR
GND 7 5 GND
Fig. 371. F Interface–Remote Modem cable
3DB 16142 CAAA Ed.01A–DRAFT 543 / 576

B.4 : Modem setting

B.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem

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

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

ATT<Return> (Tone Dialling instead than Pulse Dialling)
ATX3<Return> (Second Signal disabling, avoids problems with PABX)
AT&W0<Return> (Configuration store in NVRAM 0)
5) Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.
544 / 576 3DB 16142 CAAA Ed.01A–DRAFT

N.B. For confirmation, the modem configuration can be checked writing the command
“ATI4<Return>” in the HyperTerminal program window.
Information displayed should be as follows:

ATI4
U.S. Robotics Sportster Flash 56000 Settings...
B0 E1 F1 L2 M1 Q0 V1 X3 Y0
BAUD=38400 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE CID=0
&A3 &B1 &C1 &D2 &H1 &I0 &K1

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

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

B.4.2 : TD–32 AC Modem setting

This modem requires an initial HW set–up via dip–switches and a SW setting via serial port.

To set the modem, both local and remote, proceed as follows:
1) The initial HW set–up via dip–switches is indicated in Fig. 372. 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. 372. TD–32 AC modem dip–switch setting
2) Connect the local modem to the PC/ECT with the cable of Fig. 370. on page 543.
3) Power on the local modem (there is no an ON/OFF switch).
4) On the PC, activate program HyperTerminal and configure the PC–Modem serial line with the
following parameters:

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

AT&K0<Return> (DTE/DCE flow control disabling)
ATA<Return> (Automatic Answer enabling ––> Only on Remote modem and
wait the message “NO CARRIER”)
AT&W0<Return> (Configuration store in NVRAM 0)
AT&Y0<Return> (Configuration Set to load at switch–on: NVRAM 0)
6) Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
546 / 576 3DB 16142 CAAA Ed.01A–DRAFT

“AT\S<Return>” in the HyperTerminal program window.
Information displayed should be as follows:

AT\S
CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION

––– –––––––––––––––––––– ––– –––––––––––––––––––– ––– ––––––––––––––––––––
COUNTRY...........IT &A CHR ABORT OPT.....NO *H NEG. SPEED......HIGH
DTE BPS........38400 &B DTR DIAL OPTION...NO S0 RINGS TO ANS.....002
DTE PARITY.....8NONE &C DCD OPTION........ON S1 RING COUNT.......000
LINE SPEED......NONE &D DTR OPTION.........0 S2 <ESC> CHAR.......043
B BELL MODE........OFF &G GUARD TONE......NONE S3 <CR> CHAR........013
E CMD ECHO..........ON &K FLOW CONTROL....NONE S4 <LF> CHAR........010
F LINE MODE.......AUTO &L NETWORK.........PSTN S5 <BS> CHAR........008
L SPKR VOLUME......LOW &Q ASYNC/SYNC.........5 S7 CONNECT TIME.....060
M SPKR CONTROL....CALL &R RTS/CTS.........AUTO S8 PAUSE TIME.......002
N AUTO MODE.........ON &S DSR OPT............0 S12 ESC GUARD TIME...050
Q QUIET............OFF &T ENABLE RDL........NO S30 CONNECT INACT....000
V RESULT FORM.....LONG &X SYNC CLOCK.......INT S32 XON CHAR.........017
W EC MSG.............0 &Y PROFILE........NVM.0 S33 XOFF CHAR........019
X EXT RESULTS........4 \A MAX BLK SIZE.....192 S36 FALLBACK ACTION..007
Y LONG SPACE DISC...NO \G REMOTE FLOW......OFF S37 MODE SELECT......000
%C COMPRESSION.....BOTH \K BRK OPT............5 S48 V42 NEG CTRL.....007
–K EXT. SERVICES......0 \N ECL MODE........AUTO S95 RES. CODE........000
B.5 : PC laptop “Dell Latitude” setting
The following setting must be done:
Control Panel –> Alcatel Lower Layer –> Serial port –> COM3 and Serial port selected
3DB 16142 CAAA Ed.01A–DRAFT 547 / 576

B.6 : Setting up the connection
In order to activate the connection and operate the ECT in remote way, proceed as specified herebelow.

Refer to Fig. 369. on page 541 for the distinction between “local” and “remote” modems.

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

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

“CONNECT 38400” (TD 32 AC)
12 ) Close HyperTerminal program.
13 ) Activate the ECT applicative SW as usual.
14 ) At the end of the job, after having logged out from the ECT applicative SW, close the connection
between local and remote modems, switching off the local modem or physically disconnecting
the cable connecting it to the PC.
548 / 576 3DB 16142 CAAA Ed.01A–DRAFT

B.7 : Changing the ECT–equipment connection speed
B.7.1 : Introduction
This feature is meant to use modems with speed different from that documented in previous paragraphs,
giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,
56000) with automatic management of modem set–up and phone call at ECT start–up.
To make change operative, the following operations are necessary:
– at equipment side, the configuration must be set–up as explained in the para.B.7.2 below,
– at PC side, the configuration must be set–up as explained in the following para.B.7.3 on page 550,
– as far as the modem is concerned, please refer to the constructor documentation.
B.7.2 : Configuration at NE side
1) Login the NE through the TCO Suite Alarms & Settings function (see para.2–2.3.1 on page
162) using a login profile allowing the Modem Speed change (see Tab. 55. on page 163),
2) enter the Modem Speed screen and set the required speed (see para.2–2.3.8 on page 172).
3DB 16142 CAAA Ed.01A–DRAFT 549 / 576

B.7.3 : Configuration at PC side

To configure the modem with the relevant speed, enter the menu Settings –> Control Panel of the

Operating System and open the Alcatel Lower Layers utility. The menu of Fig. 373. opens.

Fig. 373. Alcatel Lower Layers utility
In the Sub–network Type field select Modem.

In the Modem field select the suitable Modem type.
In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK.
In the Phone Number field enter the phone number, which will be automatically called at the ECT start–up.
550 / 576 3DB 16142 CAAA Ed.01A–DRAFT

APPENDIX C: DOCUMENTATION GUIDE
This appendix contains all information regarding:

– this Manual, herebelow

– the Customer Documentation set this Manual belongs to, on page 555
– general on Alcatel–Lucent Customer Documentation, on page 558
C.1 : Guide to this Manual
This paragraph contains all information regarding this Manual and is structured as follows:
– Applicability of this Manual herebelow

– Purpose of this Manual on page 552
– History of this Manual on page 552
C.1.1 : Applicability of this Manual
a) Product–release applicability
The current edition of this Manual applies to the 9400AWY Rel.2.1 in the RF band configurations
listed in Tab. 46. on page 125.
b) NE applicability
The current edition of this Manual applies to the following Network Elements (NE): ULS
c) SWP and Version applicability

The current edition of this Manual applies to the set of system’s equipment, configurations and
features associated to the following SWP versions:
SWP Version
SWP Technical Description SWP Technical Code
(N.B.)
SWP 9400AWY IDU32 REF.[a] in Tab. 53. on page 141 V2.1.0
N.B. For the meaning of SWP Release and Version, please refer to para.C.3.2 on page 559.
The indication of the Versions in this Manual has the following meaning:
this Manual applies starting from the Versions stated in this table, but it could also apply to
subsequent Versions for the following reasons:
a) this Manual is not modified, unless the new version distributed to the Customers
comprises changes to the man–machine interface, or even in the presence of minor
changes that do not affect negatively the understandability of the procedures described
therein (e.g. a ”button” moved internally to a screen);
b) furthermore, if the screens contained in this Manual show the ”version–release” of the
”product–release”, then they are not replaced in the subsequent versions of Manual if their
contents remains unchanged.
3DB 16142 CAAA Ed.01A–DRAFT 551 / 576

C.1.2 : Purpose of this Manual

This Manual belongs to the Customer Documentation set envisaged for the equipment specified in

para.C.1.1 on page 551.

Refer to para.C.2 on page 555 in order to have the list and description of the Customer Documentation set.
Taking into account that the system consists of an InDoor Unit (IDU), an OutDoor Unit (ODU), and a
Software Package (SWP), this Manual provides the following information:
– system description at different detail levels, with regard to system, hardware and software
– system technical specifications
– IDU and ODU item Part Numbers and equipping rules (provisioning)
– unit operative hardware description: access point description (usage of LED, pushbuttons, switches
and connectors for Customer use), connection rules, hardware setting options
– operation and maintenance activities the operators can carry out according to the specific software
application(s) referred to in this Manual [see para. C.1.1 point c ) on page 551].
– spare parts provisioning
– routine maintenance procedures
– corrective maintenance and unit replacement procedures
– SWP installation
– equipment and radio link commissioning procedure.
Reading the following Manual:
– 1320CT Basic Operator’s Handbook V3.0.1
is not strictly necessary before starting this document, but its knowledge is necessary for operating the
procedures introduced by this document and detailed in the other sections of this Manual.
C.1.3 : History of this Manual
C.1.3.1: List of the editions and modified parts
The following Tab. 74. indicates the Manual parts new and modified with respect to the previous edition.
552 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Legend: n = new part m = modified part blank= part unchanged
Tab. 74. History of this Manual

MANUAL EDITION ⇒ 01 02 03 04 05
QUICK GUIDE n
SECTION 1: SYSTEM DESCRIPTION n
1–1 About this manual n
1–2 System overview n
1–3 IDU provisioning and description n
1–4 ODU provisioning, characteristics and description n
1–5 Technical specifications n
SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT
n
TERMINAL
2–1 SWP 9400AWY R.2.1 description and versions n
2–2 Introduction on TCO Suite and CT views and menus n
2–3 Configuration n
2–4 Equipment n
2–5 Line Interface n
2–6 Radio n
2–7 External points n
2–8 Supervision n
2–9 Protection schemes n
2–10 Loopbacks n
2–11 Diagnosis n
2–12 Performance Monitoring n
2–13 Software Download n
2–14 MIB Management n
SECTION 3: INSTALLATION AND COMMISSIONING n
3–1 SWP installation in PC environment n
3–2 Line–Up and Commissioning n
SECTION 4: MAINTENANCE AND UPGRADE n
4–1 Maintenance Policy n
4–2 Set and use of EOW functions n
4–3 Maintenance Tools and Spare Parts n
4–4 First Level Maintenance n
4–5 Second Level Maintenance n
4–6 Spare Flash Card management and replacement procedures n
4–7 System hardware upgrade n
4–8 SWP download toward NE n
CT & NE Upgrade to a newer SWP ’version’ (same SWP
4–9 n
’release’)
4–10 SWP de–installation n
3DB 16142 CAAA Ed.01A–DRAFT 553 / 576

Tab. 74. History of this Manual
MANUAL EDITION ⇒ 01 02 03 04 05

SECTION 5: APPENDICES n

A Safety–EMC–EMF–ESD norms and equipment labelling n
ECT–Equipment connection via public switched telephone
B n
network
C Documentation guide n
D List of symbols and abbreviations, Glossary of terms n
SECTION 6: ENCLOSED DOCUMENTS n
C.1.3.2: Notes on ED.01A–DRAFT–IN PREPARATION
– Draft edition neither validated nor officially released issue, for Alcatel–Lucent internal purposes or
for selected Customer usage:
• ED.01A–DRAFT–IN PREPARATION created on January 26th, 2007
First Draft edition associated to SWP version V2.1.0 . Its status is as follows:
– Parts that can be considered fully consistent with the Rel.2.1 SWP version V2.1.0 are:
• whole SECTION 1: SYSTEM DESCRIPTION from page 3 to page 138
• whole SECTION 4: MAINTENANCE AND UPGRADE from page 447 to page 526,
with the exception of some CT screens, that are those of SWP Version V2.0.4
• whole SECTION 5: APPENDICES and SECTION 6: ENCLOSED DOCUMENTS
from page 527 to page 576
– Parts that must be considered partially consistent with the Rel.2.1 SWP version V2.1.0 are:
• in SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL :
– chapter 2–1 – SWP 9400AWY R.2.1 description and versions is fully
consistent, but para.2–1.3 (from page 142) will be completed in the final ED.01,
after final V2.1.0 SWP release document availability
– chapter 2–2 – Introduction on TCO Suite and CT views and menus can be
considered consistent from page 143 to page 162
– chapter 2–2 from page 163 and all other section’s chapters (in particular
those related to the equipment management) till page 310 must not be
considered consistent with SWP version V2.1.0 (they are relevant to SWP
Version V2.0.4)
• in SECTION 3: INSTALLATION AND COMMISSIONING :
– chapter 3–1 – SWP installation in PC environment is fully consistent
– in chapter 3–2 – Line–Up and Commissioning :
• pages from 361 to 397 are fully consistent
• pages from 398 to 442 can be considered consistent, with the exception
of the CT screens, that are those of SWP Version V2.0.4
• remaining pages from 443 to 446 are fully consistent
N.B. At any rate, also parts that are stated as fully consistent with the Rel.2.1 SWP
version V2.1.0 have not been validated, and are subject to change in next edition(s).
554 / 576 3DB 16142 CAAA Ed.01A–DRAFT

C.2 : Documentation set description
This paragraph contains all information regarding the 9400AWY Rel.2.1 Customer Documentation and
is organized as follows:
– 9400AWY Rel.2.1 Customer Documentation herebelow

– Additional documentation for 1320CT platform on page 557
C.2.1 : 9400AWY Rel.2.1 Customer Documentation
This paragraph lists and briefly describes the documentation set envisaged for 9400AWY Rel.2.1.
Please refer to following para.C.3 on page 558 for a general description of Alcatel–Lucent 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–Lucent to update it in this Handbook.
The standard Customer Documentation for 9400AWY Rel.2.1 is in the English language and is distributed
to Customers only by the following CD–ROM:
Tab. 75. 9400AWY Rel.2.1 Documentation CD–ROM
REF Technical Description Technical Code NOTES
DCP 9400AWY 2.1 CD_ROM 3DB 16142 AAAA
From Ed.05 of the CD–ROM, it contains, in electronic format (ADOBE ACROBAT pdf files),
[A] all handbooks listed in:
– Tab. 76. on page 556 (Handbooks independent from SWP version)
– Tab. 77. on page 556 (Handbooks dependent from SWP version)
N.B.
a) Standard supply
One copy of the 9400AWY Rel.2.1 CD–ROM is automatically delivered to Customer together with
the equipment it refers to (one copy for each terminal).
As 9400AWY Rel.2.1 CD–ROM is a standard commercial item, additional copies can be ordered and
delivered as any other Alcatel–Lucent commercial item.
Supply to Customers of paper copies of the handbooks is not envisaged.
Supply to Customers of Customer Documentation source files is not envisaged.
b) Product–documentation consistency
Equipment description and lay–out are always general, i.e. they never describe the actual
composition of the equipment supplied to Customer (this task is entrusted to plant–dependent
documentation).
Detailed hardware documentation concerns actually supplied units and is coherent with the
production issue of such units.
Software–associated handbooks are coherent with the supplied SWP release.
Copies of the CD–ROMs regarding a specific product–release previously delivered can be required
specifying P/N and edition.
c) Copyright notification
The technical information of the handbooks and CD–ROMs supplied to Customers is the property
of Alcatel–Lucent and must not be copied, reproduced or disclosed to a third party without written
consent.
3DB 16142 CAAA Ed.01A–DRAFT 555 / 576

Tab. 76. Handbooks independent from SWP version

N.B. The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a )

on page 555, they do not represent Commercial item P/Ns.

REF HANDBOOK DOCUMENT P/N NOTES
9400AWY Rel.2.1 Installation Handbook 3DB 16142 BAAA
[B] Provides information regarding Equipment Hardware installation, according to Alcatel–Lucent

WTD LAB. rules.
9400AWY Rel.2.1 TRS and SAT 3DB 16142 DAAA
[C] Contains the Test Report Sheets and the Site Acceptance Test protocol, according to Alcatel
WTD LAB. rules. The source file of this document (MSWORD 2000) is also distributed in the
Documentation CD–ROM.
Interference investigation procedure 3DB 04165 EAAA
[D] Describes the measurement procedure for the interference searching in the various RF bands
used by Alcatel Radio Transmission products. It is common to all Alcatel Radio Transmission
products.
Tab. 77. Handbooks dependent from SWP version

They provide information regarding 9400AWY Rel.2.1:
– equipment description and composition, station layouts and hardware setting documentation and
maintenance
– SWP screens and operational procedures for Equipment SW management and maintenance
– equipment commissioning, according to Alcatel WTD LAB. rules.
N.B. The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a )
on page 555, they do not represent Commercial item P/Ns.
REF HANDBOOK DOCUMENT P/N NOTES
9400AWY Rel.2.1 V2.1.0 User Manual 3DB 16142 CAAA this handbook
[E]
To be used in association with SWP specified in point c ) on page 551
556 / 576 3DB 16142 CAAA Ed.01A–DRAFT

C.2.2 : Additional documentation for 1320CT platform
Tab. 78. Documentation common to Alcatel–Lucent Network Elements using 1320CT platform
CT–K
REF Version ITEM P/N
(N.B.)
3.0.1 DCP 1320 CT 3.x CD_ROM EN 3AL 79552 AAAA
[F]
Contains, in electronic format, the 1320 CT Operator’s Handbook REF.[G] to [I]
3.0.1 1320CT Rel.3.x Basic Operator’s Handbook 3AL 79551 AAAA
[G] Provides general information and operational procedures common to all 1320CT (Craft
terminal) of Alcatel–Lucent InfoModel Network Elements.
3.0.1 AS Rel.6.5 Operator’s Handbook 3AL 88876 AAAA
[H] Provides detailed information and operational procedures regarding the alarm Surveillance
software embedded in the 1320CT software package.
3.0.1 ELB Rel.2.x Operator’s Handbook 3AL 88877 AAAA
[I] Provides detailed information and operational procedures regarding the Event Log Browser
software embedded in the 1320CT software package.
N.B. The CT Version is displayed when, on the PC, you select the 1320CT application for its
launch.
3DB 16142 CAAA Ed.01A–DRAFT 557 / 576

C.3 : General on Alcatel–Lucent Customer Documentation

This paragraph describes in general the Alcatel–Lucent 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–Lucent WTD
(Wireless Transmission Division) only.
C.3.1 : Customer–Independent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as

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

commercial criteria as far as contents, formats and supply conditions are concerned
N.B. Plant–dependent and Customized documentation is not described here.
b) Aims of standard Customer Documentation
Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and
maintaining the equipment according to Alcatel–Lucent Laboratory design and Installation Dept.
choices. In particular:
• the contents of the handbooks associated to the software applications focus on the explanation
of the man–machine interface and of the operating procedures allowed by it;
• maintenance is described down to faulty PCB location and replacement.
N.B. No supply to Customers of design documentation (like PCB hardware design and
production documents and files, software source programs, programming tools, etc.) is
envisaged.
558 / 576 3DB 16142 CAAA Ed.01A–DRAFT

C.3.2 : Product levels and associated Customer Documentation
See Fig. 374. on page 560.

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

In some cases, a ”product–release” includes different possible “configurations” which are
distinguished from one another by different “Network Element” (NE) types and, from the
management point of view, by different SWPs.
d) SWP Releases and Versions
This description is 9400AWY–specific:
• A 9400AWY SWP is identified by its “Denomination”, “Part Number” and “Change Status”, that
are printed on the CD–ROM’s label.
• The SWP Denomination version’s first and second digits (e.g. 2.1) correspond to the “HW
product–release” number first and second digits; third digit of the SWP version identifies the
Version Level of the SWP.
• A 9400AWY SWP with new “Denomination” and “Part Number” represents a fully new SWP
having main features in addition to those of the previous SWP.
• A 9400AWY SWP with same “Denomination” and “Part Number” , but with new “Change
Status” corresponds to a new version of such SWP, usually developed for bug–fixing purposes
and/or minor additional features.
3DB 16142 CAAA Ed.01A–DRAFT 559 / 576

e) Customer Documentation

A ”product–release–(configuration)” has its own set of standard Customer Documentation, usually

formed of several handbooks, i.e., in general:

• System and Hardware documentation:
– one (or more) Technical Handbook(s)
– an Installation Handbook
– a Commissioning Handbook or Line–Up Guide
• Software documentation:
– a Craft Terminal Operator’s Handbook, associated to the specific SWP–Release
– other Operator’s Handbooks (typically those associated to the SW platform embedded
in the SWP)
In other cases (e.g. this Manual), above pieces of information are collected in a single document.
PRODUCT
evolution
PRODUCT–RELEASE 1.0 PRODUCT–RELEASE 2.1
ALTERNATIVE CONFIGURATIONS
CONFIG.A CONFIG.B
evolution
PRODUCT SWP REL.1.0 SWP REL.1.1
LEVELS
DOCUMENTATION
CONFIG.A SWP REL.1.0 SWP REL.1.1

System & HW SW SW
Documentation Documentation Documentation
Fig. 374. Example of Product levels and associated Customer Documentation
560 / 576 3DB 16142 CAAA Ed.01A–DRAFT

APPENDIX D: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS
D.1 : List of symbols

Tab. 79. List of symbols

N.B. This table lists some symbols whose interpretation could be doubtful.
SYMBOL MEANING AND COMMENTS

In this handbook it is not the division symbol. It means ’from .. to ..’.
E.g.:
<value1> <value2>
means:
from <value1> (included) to <value2> (included)
A polarization symbol like this:
H V
POLARIZATION can be assumed as either horizontal or vertical
SYMBOLS H
Once you have decided a polarization (e.g. )
the opposite direction symbol will be opposite polarization (e.g. )
V
D.2 : List of abbreviations
Tab. 80. List of abbreviations

ABBREVIATION MEANING
STARTING WITH NUMBERS
9400AWY Short–haul low/medium capacity digital microwave radio links
9400FSO PDH Low/Medium Capacity Free Space Optic System
9600FSO SDH/SONET High Capacity Free Space Optics System
9600LSY STM 1/0 Long Haul Digital Radio Relay System
9600USY Urban Haul Synchronous split mount Radio System
A
ABIL Enabling
ABN Abnormal
AC Alternate Current
ACD Access Control Domain
ACSE Association Control Service Element
ADC – A/D Analog to Digital Converter
AE Access Enable
AF Atomic Function
ADM Add and Drop Multiplexer
AGC Automatic Gain Control
AIS Alarm indication Signal
ALR Automatic Laser Restart
3DB 16142 CAAA Ed.01A–DRAFT 561 / 576


ALS Automatic Laser Shutdown

AMI Alternate Mark Inversion
AND Alarm on both station batteries
ANSI American National Standard Institute
AP Alternate Polarization
API Access Point Identifier
APS Automatic Protection Switching
APT Active Problem Table
AS Alarm Surveillance
ASAP Alarm Severity Assignment Profile
ASE Application Service Element
ASIC Application Specific Integrated Circuit
AT Attended Alarm
ATL Far Terminal Alarm
ATM Asynchronous transfer Mode
ATPC Automatic Transmit Power Control
ATTD ATTendeD (alarm storing)
AUX AUXiliary
AVC Attribute Value Change
B
BATT Battery
BB Base Band
BBE Background Block Error
BCA Common Battery Dial Pulsing (Telephone Set)
BER Bit Error Rate
BIP Bit Interleaved Parity
BKPV Back Plane Version
BNC Bayonet Not Coupling
BSC Base Station Controller
BTS Base Transceiver Station
C
CAND All power supply units are faulty
CCDP Co–Channel Dual Polarized (Frequency re–use)
CCITT International Telephone and Telegraph Consultative Committee
CD Current Data
CE European Conformity
CFA Carrier Failure Alarm
C/I Carrier to Interference ratio
CK Clock
CLA Common Loss Alarm
CLEC Competitive Local Exchange Carrier
CMISE Common Management Information Service Element
562 / 576 3DB 16142 CAAA Ed.01A–DRAFT

CMISS Card Missing

CO Central Office
COAX Coaxial
CP Co–polar
CPE Customer premises equipment
CPI Incoming parallel contacts
CPO Outgoing parallel contacts
CPU Central Processor Unit
CRC–n Cyclic Redundancy Check – n
CS (Item) Change Status
CT Craft Terminal
CTP Connection Termination Point
D
DA Distant Alarm
DAV Distinguishing Attribute Value
D/A Digital to Analog (converter/conversion)
DC Direct Current
DCC Data Communication Channel
DCE Data Circuit Terminating Equipment
DCN Data Communication Network
DDF Digital Distribution Frame
DEFEC FEC Decoder
DEM Demodulator
DEMUX Demodulator
DF Dialog Failure
DIV Diversity
DM Degraded Minute
DRRS Digital Radio Relay System
DTE Data Terminal Equipment
DTI Department of Trade and Industry
DTMF Dual Tone Multi Frequency
E
EB Errored Block
EBC Errored Block Count
EBU European Broadcasting Union
EC Equipment Controller
ECC Embedded Communication Channel
ECS External Communication Service
ECT Equipment Craft Terminal
EE Equipment Engineering
EF Equipment Failure
EFD Event Forwarding Discriminator
3DB 16142 CAAA Ed.01A–DRAFT 563 / 576


EIA Electronic Industries Association

EIRP Equivalent Isotropically Radiated Power
ELB Event Log Browsing
EMC ElectroMagnetic Compatibility
EMI Electromagnetic interference
EML Element Management Layer
EOW Engineering Order Wire
EPS Equipment Protection Switching
ES Errored Second
ESD Electrostatic discharges
ETH ETHernet
ETR European Telecommunication Report
ETS European Telecommunication Standard
ETSI European Telecommunication Standard Institute
EW Early Warning
EWH Early Warning High
EWL Early Warning Low
EXC–BER Excessive BER
F
F Interface F (for Craft Terminal) or Fuse
FAD Functional Access Domain
FCC Federal Communications Commission
FCS Frame Check Sequence
FD Frequency Diversity
FE Front End – Fast Ethernet
FEC Forward Error Correction (Code)
FIT Failure Unit
FPGA Field Programmable Gate Array
FR ’Failure Rate’ or ’Frequency Reuse’
FSO Free Space Optics
FTP File Transfer Protocol
G
GA General Alarm or Gate Array
GND Ground
GNE Gateway Network Element
H
H Horizontal (polarization)
HBER High Bit Error Rate
HCS Higher order Connection Supervision
HD History Data
HDBK Handbook
HDB3 High Density Binary 3
564 / 576 3DB 16142 CAAA Ed.01A–DRAFT

HDLC High level Data Link Control

HET HETerofrequency
HEW High Early Warning
HK HouseKeeping
HSB or HST Hot Standby
HMI Human Machine Interface
HS High Speed – Hitless Switch
HW Hardware
HWP Hardware Protection
I–J
ICS Item Change Status
ID IDentifier
IDU InDoor Unit
IEC International Electro technical Commission
IEEE Institute of Electrical and Electronic Engineering
IF Intermediate Frequency
IM Information Manager – Information Model
IN Input
IND Indicative alarm
INT Internal Local Alarms
I/O Input/Output
IP Internet Protocol
IRC International Radiotechnical Commission
ISO International Standards Organization
ITU–R (*) International Telecommunication Union – Radiocommunication
ITU–T (*) International Telecommunication Union – Telecommunication
JRE Java Run–time Environment
L
LAC Local Access Control
LAN Local Area Network
LAPD Link Access Procedure on D–channel
LBER Low Bit Error Rate
LC Loss of Configuration
LCS Lower Order Connection Supervision
LDI Local Defect Indication
LED Light Emission Diode
LEW Low Early Warning
LIM Link Identifier Mismatch
LLMAN Alcatel Lower Layer MANager
LO Local Oscillator
LOF Loss Of Frame
LOM Loss Of Multiframe
3DB 16142 CAAA Ed.01A–DRAFT 565 / 576


LOS Loss Of Signal

LS Low Speed
M
MAC Media Access Control
MAJ Major (alarm)
MAU Medium Attachment Unit
MCF Message Communication Function
MDT Mean Dawn Time
MEM Memorization
MIB Management Information Base
MIN Minor (alarm)
MLR Manual Laser Restart
MOC Managed Object Class
MOD Modulator
MSOH Multiplex Section OverHead
MSp Manual Switch to protecting channel
MSw Manual Switch to working channel
MTBF Mean Time Between Failures
MTTR Mean Time To Repair
MUX Multiplexer
N
NBF Narrow Band Filter
NDS Near–end Defect Second
NA Not Applicable
NE Network Element
NES Network Element Synthesis
NEBC Near–end Errored Block Count
NF Noise Figure
NFD Net Filter Discrimination
NG Not Urgent
NML Network Management Layer
NMS Network Management System
NRZ Non Return to Zero
NSA Not Service Affecting
NTP Network Time Protocol
NURG Not urgent alarm
O
OBPS On Board Power Supply
OC_R ODU Controller_Radio
OCT Office Craft Terminal
ODF Optical Distribution Frame
ODU OutDoor Unit
566 / 576 3DB 16142 CAAA Ed.01A–DRAFT

ODUC ODU Controller

OFS Out of Frame Second

OH OverHead
O&M Operation and Maintenance
OIRT Russian Regulatory Body
OOF Out Of Frame
OOS Out Of Service
OR Logic sum/Loss of only one station battery
ORALIM OR’ing of station power supply alarm
OS Operation System
OSI Open Systems Interconnection
OSPF Open Shortest Path First
OUT Output
OVF Overflow
OW Order Wire
P
PABX Private Automatic Branch Exchange
PBX Private Branch Exchange
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PFAIL Power supply failure
PI Physical Interface
PLL Phase Locked Loop
PLM PayLoad Mismatch
PM Performance Monitoring
PPI Plesiochronous Physical interface
ppm parts per million
PPP Point to Point Protocol
PRx Received power
PRBS Pseudo Random Binary Signal
P/S Parallel/Serial converter
PS Power Supply
PSA Protection Switch Actual
PSA C Protection Switch Count
PSA D Protection Switch Actual Duration
PSK Portable Service Kit
PSR Protection Switch Request
PSU Power Supply Unit
PTx Transmitted power
Q
QAM Quadrature Amplitude Modulation
QOS Quality Of Service
3DB 16142 CAAA Ed.01A–DRAFT 567 / 576


R

RAI Remote Alarm Indication
RAM Random Access Memory
RAPS Radio Automatic Protection Switch
RC Radio Controller
RCK Received clock
RCIM Radio Channel Identifier Mismatch
RDI Remote Defect Indication
RECC Recommendation
RECT Remote Equipment Craft Terminal
REI Remote Error Indication
REF Reference
REL Release
RF Radio Frequency
RFC Remote Frequency Control
RI Remote Inventory
RL Received Level
RLTS Received Level Threshold Second
RMS Root Mean Square
RNURG Not urgent Alarm command. Lights up the relative rack red LED
RPI Radio Physical Interface
RPS Radio Protection Switching
RSOH Regenerator Section OverHead
RSPI Radio Synchronous Physical Interface
RT Transceiver
RTF Remote Terminal Failure
RTPC Remote Transmit Power Control
RURG Urgent Alarm command. Lights up the relative rack red LED
Rx Receiver/Received
S
SA Service Affecting or Service Alarm
SC Service Channel or System Controller
SD Space Diversity
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
SF Signal Fail
SNMP Simple Network Management Protocol
SP Splitter
SQ Squelch
S/P Serial to Parallel
SSF Server Signal Fail
STBY Standby
568 / 576 3DB 16142 CAAA Ed.01A–DRAFT

SU Supervisory Unit
SW ”Switch” or ”Software”
SWP Software Package
T
TA Remote Alarm
TCO Total Cost of Owner
TCP Transmission Control Protocol
TD Layout drawing
TDM Time Division Multiplexer
TEM Transversal Electric Mode
TIM Trace Identifier Mismatch
TL Transmitted Level
TLTS Transmitted Level Threshold Second
TM Transmission and Multiplexing
TMN Telecommunication Management Network
TN Telecommunications Network
TPH Telephone
TP Termination Point
TPS Tx Protection Switching
TR TRansceiver – Technical Report
TRCF Total Received Correct Frames
TRCO Total Received Correct Octets
TRIB Tributary
TRSEF Total Received Service Errored Frames
TS Time Slot
TRU Top Rack Unit
TTF Total Transmitted Frames
TTO Total Transmitted Octets
TTP Trail Termination Point
Tx Transmitter/Transmitted
U
U Unavailability
UAS UnAvailable Second
UAT UnAvailable Time
UDR Unpressurized Rectangular Waveguide Type
UG Urgent Alarm
UMTS Universal Mobile Telecommunications System
URG Urgent
URU Underlying Resource Unavailable
USC User Service Channel
USM User Service Manager
USY Urban Haul Synchronous split mount Radio System
3DB 16142 CAAA Ed.01A–DRAFT 569 / 576


UT Unavailability Time

UTRAN Universal Terrestrial Radio Access Network
V
V Vertical (polarization)
VCO Voltage Controller Oscillator
VF Voice Frequency
VLAN Virtual Local Area Network
VSWR Voltage Standing Wave Ratio
W
WAN Wide Access Network
WBF Wide Band Filter
WIP Wireless IP
WLT Wireless Line Terminal
WS Work Station
X
XPD Cross Polar Discrimination
XPIC Cross Polar Interference Canceller
XPI Cross Polar Interference
XPIF Cross Polar Improvement Factor
XPOL Cross Polar/Polarization
NOTES:
(*) Owing to change of name, all documents issued by the two ITU committees (CCIR ND
CCITT) in 1992 (and in some cases even before then) are classified as ITU–R and ITU–T,
respectively.
570 / 576 3DB 16142 CAAA Ed.01A–DRAFT

D.3 : Glossary of terms
Acknowledgment:
When an alarm is taken into account by the application, the operator has to acknowledge it to point out
that he has seen it and that he will react in the right way. During alarm configuration it is possible to set
a maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear
has to be acknowledged.
Administrator:
A user who has access rights to all the Management Domains of the Craft Terminal product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end.
Alarm Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Compact Disk Read Only Memory:

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

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

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

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

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

It is the graphical user interface application through which the operators interact with the system.
History Report:
This function enables operators to get information concerning performances, security or alarms on entities
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
3DB 16142 CAAA Ed.01A–DRAFT 571 / 576

International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITU–T (International Telecommunication

Union).

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

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

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

Designates the management functions performed on networks elements assembled in a network.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Operator:
The end–user of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Physical Interface:
Electrical or Electrical/Optical transformers that decouple the line signals and adapt the form of signal for
further transmission. This functional block also manages clock extraction, signal loss monitoring and
loopback functions.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
572 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Telecommunication Management Network:
Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching
supports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
User Profile:
Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the
administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles
installed with Craft Terminal.
User Service Manager:

These are presentation processes used by the Craft Terminal to manage the Human Machine Interface
and facilitate the interaction with the product.
3DB 16142 CAAA Ed.01A–DRAFT 573 / 576

a)
574 / 576
END OF SECTION 5

SECTION 6: ENCLOSED DOCUMENTS
This section lists and contains the documents enclosed to this handbook.
The enclosed documents are listed in following Tab. 81. ; each of them has its own P/N, different from that
of this main handbook and different from one another.
Tab. 81. List of enclosed documents
REF [x] is used in other parts of this handbook to refer to the item.
N.B. The edition of the documents (listed in this table) that are physically enclosed in the handbook
is the highest available when this handbook is assembled or the master documentation CD–
ROM is created. The edition of enclosed documents is not specified in this table.
Documents listed and enclosed by P/N
REF DOCUMENT P/N DOCUMENT CONTENT
[A] 3DB 01397 AAAA MSZZQ Installation Kit Tool part list
[B] 3DB 01398 AAAA MSZZQ Maintenance Kit Tool part list n.b.1
[C] 3DB 01399 AAAA MSZZQ Station Kit Tool part list
n.b.1 referenced to by para.4–3.2.2 on page 456.
3DB 16142 CAAA Ed.01A–DRAFT 575 / 576

576 / 576
END OF DOCUMENT

QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK
COD.MANUALE HDBK P/N: 3DB 16142 CAAA Ed.01A–DRAFT

9400AWY Rel.2.1
USER MANUAL SWP 9400AWY IDU32
ISTRUZIONI PER LA STAMPA ED ASSIEMAGGIO DI QUESTO MANUALE –

INSTRUCTIONS FOR PRINT AND ASSEMBLY OF THIS MANUAL
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 6 SEPARATORI NUMERATI DA 1 A 6

6 SEPARATORS NUMBERED FROM 1 TO 6 ARE NECESSARY
– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
1 TARGHETTE - LABELS
2 PARTE INIZIALE - FRONT MATTER ⇒ 1/576 26/576
3 INSERIRE SEPARATORE ’1’ - INSERT SEPARATOR ’1’
4 SECTION 1: SYSTEM DESCRIPTION ⇒ 27/576 138/576
SECTION 2: NE MANAGEMENT BY TCO SUITE AND

6 ⇒ 139/576 310/576
CRAFT TERMINAL
8 SECTION 3: INSTALLATION AND COMMISSIONING ⇒ 311/576 446/576
10 SECTION 4: MAINTENANCE AND UPGRADE ⇒ 447/576 526/576
12 SECTION 5: APPENDICES ⇒ 527/576 574/576
CONTINUA – CONTINUES
3DB 16142 CAAA Ed.01A–DRAFT 577 / 576

QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK
CONTINUA – CONTINUES
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
14 SECTION 6: ENCLOSED DOCUMENTS ⇒ 575/576 576/576
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 576
– STAMPARE I SEGUENTI DOCUMENTI FRONTE/RETRO ED INSERIRLI DOPO LA PAG.576

– PRINT FOLLOWING DOCUMENTS RECTO-VERSO AND INSERT THEM AFTER PAGE 576
• I seguenti documenti sono archiviati individualmente in PDM; prendere l’edizione più alta
disponibile (formato pdf).
• The following documents are individually archived in PDM; get the highest edition available (pdf
format).
15 INSERIRE DOCUMENTO – INSERT DOCUMENT 3DB 01397 AAAA MSZZQ

fine istruzioni assemblaggio – end of assembly instructions
578 / 576 3DB 16142 CAAA Ed.01A–DRAFT

9400AWY Rel.2.1
7–8–13–15–18–23–25–28–38 GHz
SWP 9400AWY IDU32

USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7–8–13–15–18–23–25–28–38 GHz
SWP 9400AWY IDU32

USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7–8–13–15–18–23–25–28–38 GHz short–haul low/medium capacity digital microwave radio links
SWP 9400AWY IDU32
3DB 16142 CAAA Ed.01A–DRAFT USER MANUAL VOL.1/1
9400AWY Rel.2.1
7–8–13–15–18–23–25–28–38 GHz short–haul low/medium capacity digital microwave radio links
SWP 9400AWY IDU32
9400AWY Rel.2.1
7–8–13–15–18–23–25–28–38 GHz
SWP 9400AWY IDU32
3DB 16142 CAAA Ed.01A–DRAFT 579 / 576

FINE DELLE ISTRUZIONI DI STAMPA – END OF PRINT INSTRUCTIONS
580 / 576 3DB 16142 CAAA Ed.01A–DRAFT

AWY User Manual V210 01ADRAFT PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

AWY User Manual V210 01ADRAFT PDF

Caricato da

Copyright:

Formati disponibili

User Manual

SWP 9400AWY IDU32

3DB 16142 CAAA Ed.01A–DRAFT 1 / 576

CD–ROM TITLE Technical Code

2 / 576 3DB 16142 CAAA Ed.01A–DRAFT

Tab. 1. Quick guide

– IDU Main unit: read para.1–3.2 on page 67

– IDU Extension unit: read para.1–3.3 on page 73

get operative information regarding – E1 Protection box: read para.1–3.4 on page 75

– Flash Card: read para.1–3.6 on page 89

– Distributor subracks: refer to the Installation

read chapter 1–4 on page 93 , in particular:

carry out antenna fine alignment read para.3–2.9 on page 443

INSTALLATION AND COMMISSIONING

3DB 16142 CAAA Ed.01A–DRAFT 3 / 576

permitted without written authorization from Alcatel–Lucent

All rights reserved. Passing on and copying of this

provision and manage spare parts read para.4–3.3 on page 458

carry out First Level maintenance

carry out preventive maintenance proceed as specified in para.4–5.3 on page 469

carry out corrective maintenance

know and use TCO functions read para.2–2.2 on page 146

ECT: GENERAL AND LOGIN & LOGOFF

know ECT and RECT characteristics read para.1–2.4 on page 50

have the functional description of

login proceed as specified in para.2–2.5.2 on page 177

logoff proceed as specified in para.2–2.5.3 on page 184

close the 1320CT application proceed as specified in para.2–2.5.4 on page 184

manage usernames and passwords

4 / 576 3DB 16142 CAAA Ed.01A–DRAFT

ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING

have an overview on menu tree

– para.4–5.8 on page 474

EQUIPMENT PROVISIONING AND ITEM PART NUMBERS

– IDU shelves, read para.1–3.1 on page 66

– upgrade kits, refer to Tab. 71. on page 509

do provisioning & know P/Ns at IDU

do provisioning at ODU level

read suitable tables (according to configuration and

do provisioning of software products read para.2–1.2.2 on page 141

do provisioning of cables for

3DB 16142 CAAA Ed.01A–DRAFT 5 / 576

permitted without written authorization from Alcatel–Lucent

All rights reserved. Passing on and copying of this

upgrade system configuration from

replace Flash Card to improve

upgrade only NE with a newer SWP

upgrade only ECT with a newer

upgrade both ECT and NE with a

6 / 576 3DB 16142 CAAA Ed.01A–DRAFT

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1–2 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1–3 IDU PROVISIONING AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3DB 16142 CAAA Ed.01A–DRAFT 7 / 576

permitted without written authorization from Alcatel–Lucent

document, use and communication of its contents not

All rights reserved. Passing on and copying of this

1–4 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . 93

1–5 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

8 / 576 3DB 16142 CAAA Ed.01A–DRAFT

2–1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

2–1.2 SWP 9400AWY IDU32 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

2–2 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . 143