9400AWY User Manual Rel2 1 1

AlcatelLucent 9400AWY
7813151823252838 GHz
shorthaul low/medium capacity digital microwave radio links
9400AWY Rel.2.1
SWP 9400AWY R.2.1 V2.1.1
User Manual
3DB 16142 EAAA
Ed.02
Navigation principles
This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific
9400AWY Customer Documentation CDROM: for a comfortable navigation, two hyperlink types are
present:
those inside the text window, marked by a blue rectangle around any crossreference 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 online
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.
WARNING:
the bookmark window is not visible if you use Acrobat reader in fullscreen modality.
For further information, refer to Acrobat reader help online.
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
1
2
3
4
5
SECTION 1 : SYSTEM DESCRIPTION

SECTION 2 : NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
SECTION 3 : INSTALLATION AND COMMISSIONING
SECTION 4 : MAINTENANCE AND UPGRADE
SECTION 5 : APPENDICES
The standard Customer Documentation for 9400AWY Rel.2.1 SWP version V2.1.1 is in the English
language and is distributed to Customers only by the following CDROM:
CDROM TITLE
DCP 9400AWY 2.1 V2.1.1 CDROM
Technical Code
3DB 16142 ACAA
It contains, in electronic format (ADOBE ACROBAT pdf files), the following main documents:
Document Title
Document
Technical Code
9400AWY Rel.2.1 Installation Handbook
3DB 16142 BAAA
9400AWY Rel.2.1 Installation Guide
3DB 16142 FAAA
9400AWY Rel.2.1 V2.1.1 User Manual
3DB 16142 EAAA
9400AWY Rel.2.1 TRS and SAT
3DB 16142 DAAA
Notes
this manual
For further information and additional documents, please refer to Appendix G Documentation
guide on page 567
2 / 592
3DB 16142 EAAA Ed.02
All rights reserved. Passing on and copying of this

document, use and communication of its contents not
permitted without written authorization from AlcatelLucent
QUICK GUIDE
9400AWY Rel.2.1 V2.1.1 USER MANUAL
Tab. 1. below allows to access immediately the most frequently needed operative pieces of information
contained in this manual and in other related handbooks.
To find any other kind of information not listed in this 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.
Tab. 1. Quick guide
If you need immediate operative information on following matters:
have a short description of the
system
read pages 37 to 53
know changes of this issue
read para.11.4 on page 34
know new features of the SWP

version this handbook refers to
GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE

read page 4
INSTALLATION AND COMMISSIONING
read page 4
MAINTENANCE
read page 5
TCO SUITE
read page 5
ECT (EQUIPMENT CRAFT TERMINAL): GENERAL AND LOGIN & LOGOFF
read page 5
ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING
read page 6
EQUIPMENT PROVISIONING AND ITEM PART NUMBERS
read page 6
SYSTEM UPGRADE
read page 7
EQUIPMENT TECHNICAL CHARACTERISTICS
read page 7
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

3 / 592
a)
GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE
get information on safety, EMC,

EMF, ESD norms and equipment
labelling
read Appendix A on page 501
acknowledge cautions to avoid

equipment damage
have the description of equipment

interconnections, according to the
configurations

for:
get operative information regarding

the units in IDU (connectors, leds,
buttons)
IDU Main unit: read para.13.3 on page 70
IDU Extension unit: read para.13.4 on page 77
E1 Protection box: read para.13.5 on page 79
Services Protection box: read para.13.6 on page 84
Flash Card: read para.13.7 on page 93
Cables and Distributor subracks: refer to the

Installation Handbook
read chapter 14 on page 97 , in particular:

get operative information regarding
ODU
carry out antenna fine alignment

b)
para.14.7 on page 119
and para.14.7.4 on page 123
carry out installation and

commissioning of equipment as
delivered from AlcatelLucent
factory
proceed as specified in para.12.6.1 on page 59
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
4 / 592
USER MANUAL
FRONT MATTER

Tab. 1. Quick guide


Tab. 1. Quick guide

c)
MAINTENANCE
know the consequences of unit

extraction in IDU shelf
set and use the EOW functions of

the equipment
read chapter 42 on page 413
provision and manage spare parts
carry out First Level maintenance

(system state display)
proceed as specified in chapter 44 on page 421
carry out preventive maintenance
proceed as specified in para.45.3 on page 431
carry out corrective maintenance

(troubleshooting and repair)
d)
TCO SUITE
know and use TCO functions

e)
ECT: GENERAL AND LOGIN & LOGOFF
know ECT and RECT characteristics
have the functional description of

User Profile management
read para.23.6.1 on page 214
login
logoff
close the 1320CT application
change own password (for all users)
manage usernames and passwords

of all users (for administrator only)
setup a remote connection

between CT and equipment, through
a switched telephone line of the
standard Public Telephone Network.
proceed as specified in Appendix E on page 553
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

5 / 592
f)
ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING
have an overview on menu tree

structure
open SECTION 2 NE MANAGEMENT on page 139 and
then search the information according to the listed topics
manage equipment configuration

setup parameters for maintenance
use functions for SW management
proceed as specified in:

troubleshoot by ECT
g)
EQUIPMENT PROVISIONING AND ITEM PART NUMBERS

for provisioning and P/Ns of:
do provisioning & know P/Ns at IDU

level (except installation materials
and cables)
IDU shelves, read para.13.1 on page 68
Flash Cards & Software Labels, read para.13.7.1 on

page 93
equipment accessories, read para.13.8 on page 96
upgrade kits, refer to Tab. 71. on page 469
do provisioning & know P/Ns at IDU

level for installation materials and
cables
read paragraph IDU installation components of the

do provisioning at ODU level

(transceivers only)
do provisioning & know P/Ns at

ODU level for installation materials,
antennas and related matters
read suitable tables (according to configuration and

frequency bands) in paragraph Full Integrated or Not
Integrated antenna installation components of the
do provisioning of software products
read para.21.1.2 on page 141
do provisioning of cables for

PCtoNE local connection
read para.22.1 point b ) on page 144
do provisioning for system

documentation
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
6 / 592
USER MANUAL
FRONT MATTER

Tab. 1. Quick guide


Tab. 1. Quick guide

h)
SYSTEM UPGRADE
install a plugin 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

version
upgrade only ECT with a newer

SWP version
upgrade both ECT and NE with a

newer SWP version
i)
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
know Ethernet port characteristics
read Appendix D on page 547
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

7 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
8 / 592
USER MANUAL
FRONT MATTER

TABLE OF CONTENTS
QUICK GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
SECTION 1: SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
11 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 Preliminary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 New features with respect to SWP Version V2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Notes on present edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 SafetyEMCEMFESD norms and equipment labelling . . . . . . . . . . . . . . . . . . . . . . .
11.6 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
32
33
34
35
36
12 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 Equipment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 Splitmount architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2 IDU (Indoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.3 ODU (Outdoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.4 IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.1 1+0 Unprotected configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.2 1+1 Protected Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 Equipment Craft Terminal and TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4.1 ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4.2 RECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4.3 TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5 Flash Card types and content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6 General on equipment installation and SWP installation and management . . . . . .
12.6.1 Main phases for 9400AWY HW and SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.2 First SWP installation in PC and NE environments . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.3 How to check ECT and NE versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.4 Common situations requiring ECT and/or NE upgrade . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.5 Flash Card related special procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.6 Craft Terminal related special procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.7 NE configuration data change and save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.8 NE data save after commissioning completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6.9 NE data compatibility between SWP 2.1.x versions . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
37
39
39
42
46
49
50
50
51
54
54
54
55
56
58
59
60
62
64
64
64
65
65
65
13 IDU PROVISIONING AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.1 Provisioning of IDU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Labels affixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3 Description of IDU Main unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.1 IDU Main Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.2 Power Supply connector pinout (MAIN and EXTENSION units) . . . . . . . . . . . . . . . .
13.3.3 ECT RS232 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.4 OS (or ECT) 10/100BaseT connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.5 Ethernet tributaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Description of IDU Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.1 IDU Extension Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5 Description of E1 Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.1 E1 Protection box: connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
68
69
70
73
74
75
75
76
77
78
79
80
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

9 / 592
84
85
88
89
90
93
93
94
96
14 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . .

14.1 ODU mechanical design and identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 Labels affixed on the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.4 ODU provisioning and layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.4.1 Provisioning of ODU (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.4.2 Provisioning, layouts and connections of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5 ODU part lists and characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.1 Part lists of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.2 Part lists of ODUs with embedded diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6 Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.1 1+0 configuration with full integrated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.2 1+1 HSB configuration with coupler and full integrated antenna (1338 GHz) . . . . .
14.6.3 1+1 HSB configuration with coupler and full integrated antenna (78 GHz) . . . . . . .
14.6.4 Configuration with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7 ODU operative information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7.1 Operative information on ODUs with embedded or external diplexer . . . . . . . . . . . . .
14.7.2 ODU hardware settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7.3 ODU identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7.4 Additional operative information on ODUs with external diplexer . . . . . . . . . . . . . . . .
97
98
99
100
101
101
101
104
105
108
113
114
116
117
117
119
119
122
122
123
15 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 Reference system standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.2 RF channelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.3 Transmitted power at antenna port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.4 99% power channel bandwidth and Emission Designator . . . . . . . . . . . . . . . . . . . . . .
15.1.5 ETSI System Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.6 Protection switching system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Tributary interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4 Maximum capacity and Modulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5 IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.6 Manmachine interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.8 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.9 Mechanical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.10 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.10.1 Operating environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.10.2 Electromagnetic compatibility/safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.10.3 Waste from Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . . . . . . .
15.11 Dismantling & Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
128
129
129
130
131
132
134
135
135
135
135
136
136
136
136
137
137
137
137
138
SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL . .
139
21 SWP 9400AWY R.2.1 V2.1.1 DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

21.1 SWP 9400AWY R.2.1 V2.1.1 general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
FRONT MATTER
10 / 592

13.6 Description of Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.1 Alarms Housekeeping (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.2 NMS V.11 Audio 1 (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.3 NMS G.703 Audio 2 (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.4 User service channels (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.7 Provisioning and identification of Flash Cards & Software Labels . . . . . . . . . . . . . .
13.7.1 Provisioning of Flash Cards & Software Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.7.2 Description of Flash Cards & Software Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.8 Provisioning and description of equipment accessories . . . . . . . . . . . . . . . . . . . . . . .

21.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2 SWP 9400AWY R.2.1 V2.1.1 specific information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.2 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.3 SWP version specific data and Reference Information Models . . . . . . . . . . . . . . . . . .
141
141
142
142
142
142
22 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . .

22.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2 TCO Suite description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.1 TCO Suite scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.3 TCO Suite startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.4 TCO Suite Main Menu functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.5 TCO Suite Advanced Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.6 Note: Direct And Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2.7 Warning about interface customization carried out by the Direct Connection . . . . . .
22.3 TCO Suite Alarms & Settings functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.1 TCO Suite Alarms & Settings startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.2 Date & Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.3 Configuration Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.4 Configuration Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.5 Get Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.6 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.7 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.8 Licence Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.9 Modem Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3.10 NAT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4 PCNE physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4.1 Physical interfaces for the NE management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4.2 Local connection of the Craft Terminal to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.5 Craft Terminal: NE supervision, login, logoff and switch off . . . . . . . . . . . . . . . . . . . .
22.5.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.5.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.5.3 NE Logoff or switch off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.5.4 Closing the 1320CT application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.6 9400AWY view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.6.2 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.6.3 Button Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.6.4 Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7 Introduction to the CT menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.1 Menu organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.2 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.3 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.4 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.5 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.7.6 SW Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
144
146
146
147
148
149
151
154
155
156
156
159
160
161
164
165
166
166
167
168
170
170
171
172
172
173
180
180
181
181
182
183
183
184
184
185
186
186
187
187
23 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2.2 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2.3 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2.4 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
190
191
192
193
195
196
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

11 / 592
204
205
207
210
210
212
213
213
214
214
216
217
218
24 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.2 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.3 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.2 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.3 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.3.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.3.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219
221
221
222
222
223
224
224
225
225
25 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.1.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
228
228
228
26 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.2.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.3 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.4 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.4.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.4.2 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.5 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.5.1 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26.6 BER measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233
234
234
234
234
234
235
238
239
240
241
244
246
27 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

27.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
27.2 Output External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
28 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . .
28.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . .
28.2 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3 MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28.3.3 Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
12 / 592
251
251
251
252
252
253
254
255
255
USER MANUAL
FRONT MATTER

23.2.5 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4.1 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4.2 Link Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4.3 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.5 Quick Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.6 Profiles management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.6.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.6.2 Change Password procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.6.3 Users Management procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.7 Log Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28.3.4 Remove file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

28.4 SW key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
29 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1 Equipment Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.1.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.2.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.3 HSB Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29.4 Rx Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257
258
258
259
260
260
261
262
262
263
264
210 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.1 Hardware implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.1.1 IDU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.1.2 ODU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.2 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.3 Loopback domain views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.4 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210.5 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267
267
267
268
269
272
275
276
211 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.1.1 Counter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.1.2 Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.2 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.2.1 Alarm and Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.2.2 Software Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.3.2 Remote Inventory display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.4 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.5 Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211.6 Current Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
277
278
278
278
279
280
281
282
282
283
284
285
288
212 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

212.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . .
212.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.5 Threshold tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.5.1 How to change a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.5.2 How to create a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212.5.3 Threshold table association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
289
289
290
292
292
293
294
294
295
295
296
296
213 SW
213.1
213.2
213.3
297
297
298
299
DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Init SW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

13 / 592
SECTION 3: INSTALLATION AND COMMISSIONING . . . . . . . . . . . . . . . . . . . . .
301
301
302
302
302
304
306
307
31 SWP INSTALLATION IN PC ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.1.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.1.2 Operator skills and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.2 Reference Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.3 Choice of the procedure and summary of SWP installation phases . . . . . . . . . . . . .
31.4 Preliminary: installation of different SWPs in the same PC . . . . . . . . . . . . . . . . . . . . .
31.5 1320CT Package Installation (installation of SWP components from the SWP
CDROM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.5.1 Important warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.5.2 Operations sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.5.3 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.6 Local copy in PC environment of the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.6.1 Operations sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.6.2 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.7 End of SW installation from SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.8 NE software downloading preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.9 CT initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.9.1 Craft Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.9.2 Craft Terminal local connection to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31.10 EML construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
309
309
309
310
310
311
312
32 LINEUP AND COMMISSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.1.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.1.3 Summary of the commissioning phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.1.4 SafetyEMCEMFESD norms and Cautions to avoid equipment damage . . . . . . .
32.2 Description of equipment interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.2.1 Configurations with 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.2.2 Configurations with 16E1 + Audio and User Service Channel plugin . . . . . . . . . . . .
32.2.3 Configurations with 16E1 + Enhanced Ethernet plugin . . . . . . . . . . . . . . . . . . . . . . .
32.2.4 Configurations with 16E1 + Enhanced Ethernet plugin + Audio and User
Service Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.2.5 Configurations with 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.2.6 Configurations with 32E1 + Audio and User Service Channel plugin . . . . . . . . . . .
32.3 Commissioning of STATION A phase 1 (Turn up) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.1 Turnon preliminary operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.2 Powering up the IDU(s) with ODU(s) connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.3 Switching off the IDU(s), and ODU(s) disconnection . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.4 Powering up the IDU(s) with ODU(s) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.5 NE login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.6 General on Quick Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.7 Online creation, modification and save of the NE configuration (interactive) . . . . .
32.3.8 TCO Suite PreProvisioning Tool: offline creation, modification and save of a
provisioning file (not interactive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
329
329
329
329
330
330
331
332
333
334
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
14 / 592
314
314
315
317
318
318
320
320
321
326
326
326
327
335
336
337
338
338
339
339
340
340
341
343
344
USER MANUAL
FRONT MATTER

214 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

214.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214.2 MIB management at Network Element Synthesis level and examples . . . . . . . . . .
214.2.1 MIB backup on ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214.2.2 MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214.2.3 MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214.2.4 MIB restore from ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32.3.9 TCO Suite SetUp Tool: online recover, modification and application of a
provisioning file (not interactive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.10 Quick Configuration Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.11 Powering UP the IDU(s) with the ODU(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.4 Commissioning of STATION B phase 1 (Turn up) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5 End of commissioning phase 1 (Turn up) in STATION A . . . . . . . . . . . . . . . . . . . . . . .
32.5.1 Remote NE (station B) acquisition on craft terminal . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.5.2 Testing configurations for hop quality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6 Commissioning station A phase 2 (acceptance test) . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.1 System Installation and cabling visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.2 Local configuration control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.3 Channel 1 functionality tests (1+0 and 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.4 Channel 0 functionality tests (1+1 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.5 Hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.6.6 NE integration tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.7 Commissioning station B Phase 2 (Acceptance Test) . . . . . . . . . . . . . . . . . . . . . . . .
32.8 Final operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.9 Annex A: fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.10 Annex B: light service kit cable operative information . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 4: MAINTENANCE AND UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . .

41 MAINTENANCE POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.1 Classification of maintenance levels and operators . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.2 First Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.3 Second Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41.4 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
346
369
373
374
374
376
377
377
377
382
394
396
397
403
403
404
405
407
409
409
410
410
410
42 USE OF EOW FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

42.1 Setting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
42.2 Call Setup/End by Telephone handset connected to the IDU Main unit . . . . . . . . . 414
43 MAINTENANCE TOOLS AND SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.2 Instruments and accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.2.1 Software tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.2.2 Maintenance, Installation and Station Tool Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3 Set of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3.1 Types of Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3.2 ODU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3.3 IDU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3.4 Number of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43.3.5 General rules on spare parts management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
415
415
415
415
416
418
418
418
418
419
419
44 FIRST LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.2 System state display by visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.2.1 LED test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.2.2 Alarm LEDs on the IDU MAIN unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.2.3 Alarm LEDs on the Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.3 TCO Suite and Craft Terminal commonly used functions for system status
display and checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.3.1 Viewing the NE alarms by TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44.3.2 Viewing the NE status by Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
421
421
421
421
421
421
423
423
423
45 SECOND LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

45.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

15 / 592
430
430
430
430
431
431
432
433
434
434
434
435
436
436
437
441
441
441
441
441
441
442
442
446
446
446
447
447
447
447
448
449
450
451
452
456
460
463
463
463
46 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES . . . . . . . . .

46.1 Spare Flash Card management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46.2 Flash Card replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46.2.2 Execution of the Flash Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
465
465
466
466
467
47 SYSTEM HARDWARE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47.1 Installation of plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.1.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.2 Upgrade from 1+0 to 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.2.1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.3 Flash Card upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
469
469
469
470
476
476
477
479
479
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
16 / 592
USER MANUAL
FRONT MATTER

45.2 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.2.1 EMC norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.2.2 Safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.2.3 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.3 Routine (preventive) Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.3.1 Routine (preventive) Maintenance every year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.4 Consequences of unit extraction in the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.5 Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.6 Alarm acknowledgment and attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.6.1 Alarm acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.6.2 Alarm Attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.7 Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8 Troubleshooting via Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.1 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.2 Alarm surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.4 Operators Controls of the protection switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.5 Tx mute function (local and remote) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.6 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.7 BER measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.8.8 Commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9 Hints on the troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.1 Problems with the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.2 Analog measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.3 NMS 64 kbit/s V.11 and G.703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.4 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.5 Empty USM icon in NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.6 Remote NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.7 Configuration change from 4 QAM to 16 QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.8 Quick configuration menu correct use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.9 Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.10 Tx Mute functionality for interferences investigation . . . . . . . . . . . . . . . . . . . . . . . . . .
45.9.11 Tributaries 17 to 32 visible in 16E1+Ethernet configuration . . . . . . . . . . . . . . . . . .
45.10 IDU unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.10.1 IDU MAIN unit replacement procedure (CH1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.10.2 IDU EXTENSION unit replacement procedure (CH0) . . . . . . . . . . . . . . . . . . . . . . . . .
45.11 ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.12 Faulty unit repair and Repair Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.12.1 Faulty unit sending back to repair center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45.12.2 Repair Form filling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47.3.2
47.3.3
47.3.4
47.3.5
Summary procedure for both stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 . . . . . . . . . . . . . . . . . . . . . .
480
481
482
483
48 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.1.1 Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.1.2 NE state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.1.3 Operator skills and profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.2 Summary of the SWP download phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.3 CT startup, NE login and initial checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.4 SW download to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.5 Activation of the new Software Package on the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.6 Additional operations for upgrade from V2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48.7 MIB save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
485
485
485
485
485
486
486
487
492
494
494
49 ECT & NE UPGRADE FROM V2.1.0 TO V2.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

410 SWP DEINSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51 APPENDIX A: SAFETYEMCEMFESD NORMS AND EQUIPMENT LABELLING . . . . .
51.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.2 Compliance with International Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3 Safety Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.1 General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.2 Labels Indicating Danger, Forbiddance, Command . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.3 Dangerous Electrical Voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.4 Risks of Explosions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.5 Moving Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.6 Equipment connection to earth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.7 Heatradiating Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.8 Microwave radiations (EMF norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.3.9 Specific safety rules in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.4 Electromagnetic Compatibility (EMC norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.4.1 EMC General Norms Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.4.2 EMC General Norms Turnon, Tests & Operation . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.4.3 EMC General Norms Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.5 Equipment protection against electrostatic discharges . . . . . . . . . . . . . . . . . . . . . . . .
51.6 Suggestions, notes and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51.7 Labels affixed to the 9400AWY equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
499
501
501
501
502
502
503
504
505
505
506
506
507
508
509
509
509
509
510
510
510
52 APPENDIX B: TCO SUITE STARTUP SPECIAL CONDITIONS . . . . . . . . . . . . . . . . . . . . . . 511

53 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NE MANAGEMENT
THROUGH THE NES ECT SERIAL PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
53.1 Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
53.2 Installation of LLMAN from the SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
53.2.1 Operations sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
53.2.2 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
53.3 Installation and configuration of Alcatel Virtual Network Card for Lower Layers . 522
53.3.1 Important warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
53.3.2 Choice of the procedure, according to Windows platform . . . . . . . . . . . . . . . . . . . . . . 522
53.3.3 Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
53.3.4 Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
USER MANUAL
FRONT MATTER
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

17 / 592
54 APPENDIX D: GENERAL ON ETHERNET PORT CHARACTERISTICS AND

MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.1 Ethernet Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.2 MDI/MDIX crossover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.3 Frame size, Rx checksum and FCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.4 Ethernet capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.5 Ethernet flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.6 Ethernet interface management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54.7 Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
547
547
547
547
547
548
548
549
55 APPENDIX E: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.2 Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.3 Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.4 Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . .
55.4.2 TD32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.5 PC laptop Dell Latitude setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.6 Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.7 Changing the ECTequipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.7.2 Configuration at NE side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55.7.3 Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
553
553
554
555
556
556
558
559
560
561
561
561
562
56 APPENDIX F: PART LISTS OF TOOL KITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56.1 Installation Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56.2 Maintenance Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56.3 Station Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
563
563
564
565
57 APPENDIX G: DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

57.1 Guide to this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.1.1 Applicability of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.1.2 Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.2 Documentation set description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.2.1 9400AWY 2.1.1 Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.2.2 Product Release Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.2.3 Additional documentation for 1320CT platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57.3 General on AlcatelLucent Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . .
57.3.1 CustomerIndependent Standard Customer Documentation . . . . . . . . . . . . . . . . . . .
57.3.2 Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . . . . . . .
567
567
567
568
569
569
571
571
572
572
573
58 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS . . .

58.1 List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58.2 List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58.3 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
575
575
575
585
59 APPENDIX I: CUSTOMER DOCUMENTATION FEEDBACK . . . . . . . . . . . . . . . . . . . . . . . . . . 589
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
18 / 592
USER MANUAL
FRONT MATTER

53.3.5 Windows XP (Professional Edition only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

53.3.6 Check for the Network Connections order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

FIGURES
Fig. 1. Antistatic protection device kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 2. 9400AWY radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 3. 9400AWY R.2.1 splitmount system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 4. Possible configurations of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 5. E1 Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 6. Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 9. ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 10. 9400AWY (1+0) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 11. 9400AWY (1+1 HSB SD) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 12. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . .
Fig. 13. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . .
Fig. 14. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . .
Fig. 15. Flash Card content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 16. Main phases for 9400AWY HW and SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 17. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 18. How to check ECT version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 19. How to check NE SW version (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 20. Label affixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 21. IDU Main Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 22. LEDs on the IDU Main Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 23. IDU Extension Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 24. LEDs on the IDU Extension Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 25. E1 Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . . . . . . .
Fig. 26. Services Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . .
Fig. 27. Equipment outputs (summarizing and housekeeping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 28. Equipment inputs relay scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 29. Equipment inputs open collector scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 30. User service channel: V11 codirectional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 31. User service channel: V11 contradirectional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 32. User service channel: G.703 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 33. User service channel: V24/V28 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 34. FLASH CARD profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 35. Flash Card identification labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 36. ODU types, identification, dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 37. Label affixed on the ODU and ODUs TRANSCEIVER box . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 38. Station layout of ODU (1+1) HSBSD or FDDA AP with two antennas . . . . . . . . . . . . . . .
Fig. 39. Station layout of ODU (1+1) HSB with one antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 40. Station layout of ODU (1+1) FDAP with one double polar external antenna . . . . . . . . . .
Fig. 41. View of ODU with full integrated antenna (V polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 42. View of ODU with full integrated antenna (H polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 43. Coupler (1338 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 44. Coupler (78 GHz) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 45. Nose adapters for ODU with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 46. Views of ODUs with embedded diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 47. Views of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 48. ODU LEMO connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 49. Composition of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 50. ODUs TRANSCEIVER and BRANCHING boxes coupling surfaces . . . . . . . . . . . . . . . . . .
USER MANUAL
FRONT MATTER
36
37
40
41
43
43
44
45
47
50
52
52
53
53
56
59
60
62
63
69
70
73
77
78
79
84
86
87
87
91
91
92
92
94
95
98
99
101
102
103
114
115
116
117
117
120
121
122
123
124
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

19 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
20 / 592
125
126
148
148
149
149
151
152
154
154
155
156
157
157
159
160
161
164
165
165
166
166
167
168
168
170
174
175
175
176
176
177
177
179
179
180
181
183
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
206
207
USER MANUAL
FRONT MATTER

Fig. 51. 78 GHz ODUs BRANCHING box mistakeproofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 52. Label affixed inside the ODU BRANCHING box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 53. Java installation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 54. JRE installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 55. TCO Suite Start.html page (CDROM version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 56. TCO Suite Start.html page (Local version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 57. TCO Suite AS.html page (Advanced Settings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 58. Internet Explorer: .exe files management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 59. ECTNE Direct and Remote connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 60. Network Adapter selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 61. Network Adapter details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 62. Direct or Remote connection by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 63. NE login by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 64. TCO Suites Alarms & Settings Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 65. TCO Suites Alarms & Settings Date & Time Configuration page . . . . . . . . . . . . . . . . . . .
Fig. 66. TCO Suites Alarms & Settings Configuration Setting page . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 67. TCO Suites Alarms & Settings Get Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 68. TCO Suites Alarms & Settings Get Configuration Request . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 69. TCO Suites Alarms & Settings Active Alarms: Static Page . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 70. TCO Suites Alarms & Settings Active Alarms: Automatic Page . . . . . . . . . . . . . . . . . . . .
Fig. 71. TCO Suites Alarms & Settings Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 72. TCO Suites Alarms & Settings Reading Software License . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 73. TCO Suites Alarms & Settings Changing FInterface Speed . . . . . . . . . . . . . . . . . . . . . .
Fig. 74. TCO Suites Alarms & Settings NAT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 75. NAT router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 76. MAIN Unit front side: interfaces for equipment control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 77. Choice of Serial or Ethernet interface for PCNE physical connection . . . . . . . . . . . . . . . .
Fig. 78. Network Element Synthesis screen (NE locally connected) . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 79. Network Element Synthesis screen (empty map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 80. SNMP NE creation in the Network Element Synthesis map . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 81. Network Element Synthesis screen after SNMP NE creation . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 82. Start supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 83. NE in supervised state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 84. Show Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 85. Login screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 86. NE Stop Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 87. 9400AWY Main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 88. Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 89. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 90. Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 91. Local Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 92. NTP Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 93. Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 94. Ethernet Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 95. IP configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 96. IP static routing configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 97. Create Static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 98. Point To Point Interface Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 99. OSPF Area configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 100. Create New OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 101. IP Address configuration of PointToPoint Interfaces screen . . . . . . . . . . . . . . . . . . . . . .
Fig. 102. IP Address and Timeslot configuration of PointToPoint InFrame E1 TMN . . . . . . . . .
Fig. 103. Routing information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 104. Alarm Severities Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 105. Name of a cloned alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 106. Clone of an Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 107. Selection of a new severity in the Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 108. Selection of a new severity in the No Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 109. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 110. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 111. USM closing warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 112. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 113. Overhead Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 114. Profile Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 115. Changing Password screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 116. Users Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 117. Users Management help screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 118. Log Switch screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 119. 1+0 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 120. 1+1 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 121. 1+0 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 122. 1+1 IDU/MAIN Ch#1 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 123. 1+1 IDU Ch#0 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 124. ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 125. Alarm tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 126. Configuration tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 127. Remote Inventory tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 128. Line Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 129. Line Interface View: E1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 130. Line Interface View: NMS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 131. Line Interface View: Data Tributary Port QoS Configuration tab panel . . . . . . . . . . . . . . .
Fig. 132. Line Interface View: Data Tributary Port PM counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 133. Line Interface View: individual Data Tributary Port Configuration tab panel . . . . . . . . . . .
Fig. 134. Radio Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 135. RadioConfiguration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 136. Radio Frequency Functions with Shifter and Rx Freq enabled . . . . . . . . . . . . . . . . . . . . . .
Fig. 137. Radio Frequency Functions with Rx Freq disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 138. Radio Frequency Functions with shifter disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 139. Not standard frequency arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 140. RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 141. Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 142. Power Measurement Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 143. Power Meas Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 144. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 145. Example of Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 146. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . .
Fig. 147. BER Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 148. Input External Point View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 149. Output External Points: CP01 ... CP04 (Manual activation) . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 150. Output External Points: CP01 ... CP04 (Automatic activation) . . . . . . . . . . . . . . . . . . . . . .
Fig. 151. Output External Points View: FAIL IDU, FAIL ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 152. Configuration of the Craft access state from the Equipment NE view in the OS mode . .
Fig. 153. Restart NE call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 154. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 155. MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 156. Backup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 157. Restore screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 158. Activate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 159. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 160. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USER MANUAL
FRONT MATTER
207
208
209
210
211
211
212
213
216
216
217
217
218
220
220
221
222
222
223
224
225
225
227
228
230
231
231
232
233
234
235
235
236
237
238
241
242
243
244
244
245
246
247
248
249
250
251
252
252
253
254
255
255
256
257
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

21 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
22 / 592
258
259
260
261
262
263
264
264
265
267
267
268
268
268
269
270
271
272
273
273
274
275
276
278
279
279
280
280
281
281
283
284
286
286
287
287
288
289
290
291
292
294
295
296
297
298
299
300
301
301
302
302
303
USER MANUAL
FRONT MATTER

Fig. 161. Mux Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 162. Mux Protection Switch (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 163. Radio Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 164. Radio Protection Switch (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 165. Transmission Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 166. HSB Tx Protection Commands (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . .
Fig. 167. Rx Static Delay menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 168. Rx Static Delay panel Warning message for fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 169. Rx Static Delay in auto mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 170. Near end IDU cable loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 171. Far end IDU tributary loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 172. Near end tributary loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 173. Near end ODU cable loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 174. Near end RF loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 175. Available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 176. 1+0 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 177. 1+1 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 178. Loopback View for PDH Tributaries (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 179. Loopback View for PDH Tributaries (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 180. Loopback View for Radio PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 181. Loopback CABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 182. Loopback activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 183. Loopback removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 184. Alarm Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 185. Alarm Sublist Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 186. Log Browsing Sub Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 187. Alarm Log Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 188. Event Log Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 189. Transfer Information Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 190. SW Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 191. Remote Inventory screen (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 192. Abnormal Condition List screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports . . . . . . . . . . .
Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports . . . . . . . . .
Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1ETH with Audio/User
Service Channel PlugIn (Lockout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service
Channel PlugIn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 197. Current Configuration view screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 198. Radio sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 199. Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 200. Threshold table association screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 201. Current Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 202. History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 203. Threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 204. Thresholds Table creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 205. Server access configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 206. Init Software Download screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 207. SW Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 208. SW Unit Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 209. Allowed MIB management tasks at NE loggedin level . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 210. Allowed MIB management tasks at Network Element Synthesis level . . . . . . . . . . . . . .
Fig. 211. Launch of MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 212. MIB save to disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 213. MIB save to disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 214. Correspondence between MIB saved folder and MIB saved name . . . . . . . . . . . . . . . . . .
Fig. 215. Launch of MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 216. MIB load from disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 217. MIB load from disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 218. Common components of different SWPs (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 219. CDROM TCO Suite Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 220. CDROM TCO Suite Advanced Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 221. SWP component selection screen and installation start . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 222. SWP component installation end, and installation report . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 223. Check of installed Alcatel SWP components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 224. Local Copy of TCO Suite location choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 225. Local Copy of TCO Suite progress and end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 226. Copy cancelled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 227. Shortcut to the TCO Suite Start icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 228. Selecting SWP Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 229. SWP Administrator screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 230. Directory selection for the descriptor file .DSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 231. SWP available for download to NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 232. Relative positions of stations A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 233. Equipment interconnections for configurations with 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 234. Equipment interconnections for configurations with 16E1 + Audio and User Service
Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 235. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin
Fig. 236. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet
plugin + Audio and User Service Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 237. Equipment interconnections for configurations with 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 238. Equipment interconnections for configurations with 32E1 + Audio and User Service
Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 239. PreProvisioning Tool splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 240. PreProvisioning Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 241. PreProvisioning Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 242. SetUp Tool splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 243. SetUp Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 244. SetUp Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 245. Quick Configuration Procedure: main NE parameter configuration (Step A) . . . . . . . . . .
Fig. 246. Quick Configuration Procedure Step B: PDH Tributary configuration . . . . . . . . . . . . . . . .
Fig. 247. Quick Configuration Procedure Step B: Ethernet GPort configuration . . . . . . . . . . . . . . . .
Fig. 248. Quick Configuration Procedure Step B: Ethernet GPort QoS configuration . . . . . . . . . . .
Fig. 249. Quick Configuration Procedure: Channels Configuration (Step C) . . . . . . . . . . . . . . . . . . .
Fig. 250. Frequency Data Help: choice of ODU type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 251. Frequency Data Help: frequency data of chosen ODU type (example) . . . . . . . . . . . . . . .
Fig. 252. Example of Frequency Data manual setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 253. RTPC setting with ATPC disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 254. Setting of enabled ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 255. ATPC and RTPC Configuration for both channels (1+1 HSB) . . . . . . . . . . . . . . . . . . . . . . .
Fig. 256. Quick Configuration Procedure: Link Identifier configuration (Step D) . . . . . . . . . . . . . . . .
Fig. 257. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E) . .
Fig. 258. Quick Configuration Procedure: OSPF Area Configuration (Step F) . . . . . . . . . . . . . . . . .
Fig. 259. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration
(Step G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 260. Quick Configuration Procedure: Configuration of TMNRF, TMNV11 and TMNG703
channels (Step H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 261. Quick Configuration Procedure: Configuration of TMN inframe (Step H) . . . . . . . . . . .
Fig. 262. Quick Configuration Procedure: IP Static Routes Configuration (Step I) . . . . . . . . . . . . . .
Fig. 263. Quick Configuration Procedure: Default Gateway Routing configuration (Step I) . . . . . .
USER MANUAL
FRONT MATTER
303
304
305
306
313
315
316
316
317
317
318
319
319
320
321
321
323
325
329
332
333
334
335
336
337
344
344
344
345
345
346
347
349
351
352
353
355
355
356
356
357
357
358
359
360
361
362
363
364
365
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

23 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
24 / 592
366
367
368
369
370
371
372
374
375
375
376
376
383
383
384
385
386
387
388
389
390
391
393
394
396
397
398
398
399
400
405
416
417
421
422
424
424
425
426
426
427
433
435
437
439
444
448
449
450
452
456
464
470
471
USER MANUAL
FRONT MATTER

Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J) . . .
Fig. 265. Quick Configuration Procedure: External Input and Output Points configuration (Step K)
Fig. 266. Quick Configuration Procedure: Summary (Step L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 267. ODU(s) alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 268. Transmit power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 269. Received power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 270. Received power details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 271. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 272. Create NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 273. NMS Radio side Remote NE acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 274. Test bench for tributary quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 275. Test bench for User service channel quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 276. 1+0 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 277. 1+1 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 278. Channel 0 lockout mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 279. Near End loopbacks points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 280. Loopback control in the CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 281. Far End loopback point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 282. Test bench for tributary functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 283. Tributary alarm status monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 284. Test bench for User Service Channel functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit
Ethernet plugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 286. Engineering order wire organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 287. Channel 1 forced mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 288. Test bench for hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 289. Test bench for NMS Line side acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 290. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 291. Create NMS Line side NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 292. NMS Line side NE monitoring in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 293. Test bench for EOW line side functionality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 294. Light service kit cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 295. Special extractor to remove the coaxial cables 1.0/2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 296. Lever for ODU mounting/dismounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes . . . . . . . . . . . . .
Fig. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes . . . . . . . . . . . . . . . . .
Fig. 299. Checks on Radio domain : Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 300. Checks on Radio domain : Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 301. Checks on Radio domain : Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 302. Checks on Radio domain : RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 303. Checks on Radio domain : nonintrusive BER measurement . . . . . . . . . . . . . . . . . . . . . . .
Fig. 304. Checks on Radio domain : Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 305. Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 306. Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 307. Alarm and status synthesis indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 308. Active alarm screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 309. Lower Layers Manager screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 310. Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 311. Tx Mute functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 312. Tributaries 17 to 32 visible in 16E1+ Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . .
Fig. 313. Details for IDU MAIN unit or FLASH CARD replacement . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 314. Details for IDU EXTENSION unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 315. Repair form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 316. Dismounting the fixing brackets and cover unfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 317. Release and sliding out the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 318. Removing the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 319. Dismounting the metal plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 320. Connectors and columns for plugin fixing by screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 321. Plugin insertion and fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 322. Server Access Configuration start up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 323. Server Access Configuration setup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 324. Init SW Download startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 325. Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 326. SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 327. Stand by SW activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 328. Forced Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 329. Security Questions: Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 330. Secure Questions: Allow Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 331. Execution confirmation (Security Warning) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 332. Security Warning (English browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 333. Security Warning (Italian browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 334. Security Warning (Java 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 335. Wrong Security Warning (Java 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 336. Firefox browser: no JRE installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 337. Firefox plugin search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 338. Firefox plugin installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 339. CDROM TCO Suite Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 340. CDROM TCO Suite Advanced Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 341. Alcatel Lower Layers Manager splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 342. Alcatel Lower layers Manager language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 343. Alcatel Lower Layers Manager Installation screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 344. Alcatel Lower Layers Manager setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 345. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 348. Windows NT configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 354. Windows 2000 installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 359. Windows 2000 configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 362. Windows XP installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 367. Windows XP configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 371. Check for the Network Connections order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 372. ECTEquipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . .
USER MANUAL
FRONT MATTER
472
472
473
474
487
488
489
490
492
492
494
511
512
512
513
513
514
514
515
515
516
517
518
519
519
520
521
523
524
524
525
526
526
527
528
528
529
530
531
531
532
533
534
535
538
539
540
540
541
542
543
544
545
546
553
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

25 / 592
555
555
558
562
574
TABLES
Tab. 1. Quick guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 2. Main additional features with respect to SWP version V2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 3. Tributaries and modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 4. 13 to 38 GHz 4/16 QAM configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 5. Bit rate of the IDUODU signal on the cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 6. IDU shelf provisioning for 1+0 and 1+1 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 7. IDU Main Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 8. Power supply connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 9. ECT connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 10. OS (or ECT) connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 11. RJ45 connectors leds for Ethernet user data interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 12. IDU Extension Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 13. Equipment Side and Line Side connectors of E1 Protection box . . . . . . . . . . . . . . . . . . . . .
Tab. 14. E1 tributaries (1 to 8) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 15. E1 tributaries (9 to 16) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 16. E1 tributaries (17 to 24) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 17. E1 tributaries (25 to 32) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 18. Equipment Side and Line Side connectors of Services Protection box . . . . . . . . . . . . . . . .
Tab. 19. Alarms Housekeeping connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 20. NMSV.11 + Audio 1 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 21. NMSG.703 + Audio 2 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 22. User service channel connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 23. Flash Cards provisioning and associated & Software Labels . . . . . . . . . . . . . . . . . . . . . . .
Tab. 24. Equipment accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 25. ODU dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 26. ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 27. 7 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 28. Branching assemblies for 7 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 29. 8 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 30. Branching assemblies for 8 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 31. 13 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 34. 18 GHz ODU (VARIABLESHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 36. 23 GHz ODU (VARIABLESHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 40. Pole Mounting versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 41. Available couplers (1338 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 42. Available couplers (78 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 43. ODU Output flanges with external antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 44. ODU external interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 45. RF interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 46. 9400 AWY family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 47. ETSI System Characteristics 32E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 48. ETSI System Characteristics 16E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 49. ETSI System Characteristics 8E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
32
38
48
49
68
70
74
75
75
76
77
79
80
81
82
83
84
85
88
89
90
93
96
98
100
106
106
107
107
108
109
110
110
111
111
112
112
112
113
116
117
118
119
119
127
132
132
133
133
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
26 / 592
USER MANUAL
FRONT MATTER

Fig. 373. ECTLocal external Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 374. F InterfaceRemote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 375. TD32 AC modem dipswitch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 376. Alcatel Lower Layers utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 377. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . .


Tab. 52. Reference documentation for dismantling and recycling detail for 9400AWY R.2
equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 53. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 54. Typical AlcatelLucent Ethernet cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login
profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 56. ATPC Range Rx Threshold for ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 57. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 60. Available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 61. Remote Inventory AlcatelLucent standard format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 62. Remote Inventory mnemonic field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 63. Test and commissioning instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 64. Radio application: Capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 65. Allowed number of PDH tributaries with Ethernet port(s) enabled . . . . . . . . . . . . . . . . . . . .
Tab. 66. Special items of the Tool Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 67. Alarm Synthesis indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 68. Alarm information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 69. General issues of the alarm meanings and their respective maintenance actions . . . . . .
Tab. 70. IDU unit replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 71. Available plugin upgrade kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 72. Flash card upgrade carried out by one operator only for both stations . . . . . . . . . . . . . . . .
Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna: . . . . . . . . .
Tab. 74. QoS based on IEEE std. 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 75. QoS based on DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 76. 9400AWY Rel.2.1.1 Documentation CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 77. Handbooks contained in the 9400AWY R.2.1.1 documentation CDROM . . . . . . . . . . . . .
Tab. 78. Documentation common to AlcatelLucent Network Elements using 1320CT platform . .
Tab. 79. List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tab. 80. List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USER MANUAL
FRONT MATTER
134
138
141
144
158
239
259
261
263
269
282
282
330
348
350
416
438
439
440
451
469
480
508
551
552
569
570
571
575
575
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

27 / 592
a)
28 / 592
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
FRONT MATTER

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 11 About this manual

It deals with:
Preliminary information
New features with respect to SWP Version V2.1.0
Structure of this manual
Notes on present edition
SafetyEMCEMFESD norms and equipment labelling (summary)
Cautions to avoid equipment damage
31
Chapter 12 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
for 9400AWY HW and SW installation, and those regarding the software
management, with particular emphasis on SWP release and versions upgrading
situations.
37
Chapter 13 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
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
67
Chapter 14 ODU provisioning, characteristics and description

It describes in detail the ODU physical configurations, relevant provisioning and
operative information for installation, commissioning and maintenance purposes
97
Chapter 15 Technical specifications

It describes the technical characteristics of the 9400AWY Rel.2.1.
127
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

29 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
30 / 592
USER MANUAL
SYSTEM DESCRIPTION

11 ABOUT THIS MANUAL
11.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.
AlcatelLucent 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. AlcatelLucent 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 AlcatelLucent.
c)
Copyright Notification
The technical information of this manual is the property of AlcatelLucent 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.51.3 on pages 502.
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. 57.2.1 on page 569
is considered as not enough.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

31 / 592
This manual describes the 9400AWY Rel.2.1 equipment running with SWP version V2.1.1.
This table sumsup the main additional features (mainly related to new HW items and new SW features
affecting the Graphical User Interface) of SWP version V2.1.1 with respect to previous version V2.1.0:
Tab. 2. Main additional features with respect to SWP version V2.1.0
Replacement of optional Data plugin (with 2 Fast Ethernet ports) with the new optional Enhanced Data
plugin (with 4 Gbit Ethernet ports):
System & HW on pages: 42 , 44 , 45 , 68 , Tab. 7. from page 70 , 76 , 282 , 331 , 334 ,

335 , 378 , 391 , 469 , 474
SW management on pages:
210 , from 231 to 232 , from 347 to 351
fully new Appendix D from page 547

New Power Measurement screen in TCO Suite Alarms & Settings functions: para.22.3 on pages
156 to 158 , 166
New possible definition of the E1#1 Timeslot number for the TMN inframe, on pages 89 , 203 and
363
For additional information, refer to the Product Release Note (see para.57.2.2 on page 571 )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
32 / 592
USER MANUAL
SYSTEM DESCRIPTION

11.2 New features with respect to SWP Version V2.1.0

11.3 Structure of this manual

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
b)
SECTION 1: SYSTEM DESCRIPTION on page 29

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 307

This section provides the whole operative instructions for the equipment HW and SW installation and
commissioning.
e)
SECTION 4: MAINTENANCE AND UPGRADE on page 407

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 499

In this section some additional information and instructions are given:
Appendix A SafetyEMCEMFESD norms and equipment labelling
Appendix B TCO suite startup special conditions
Appendix C Additional SW installation operations for NE management through the

NES ECT serial port
Appendix D General on Ethernet port characteristics and management
Appendix E ECTEquipment connection via public switched telephone network
Appendix F Part lists of tool kits
Appendix G Documentation guide
Appendix H List of symbols and abbreviations, Glossary of terms
Appendix I Customer documentation feedback
g)
Handbook print and assembly instructions This part (after handbook last page 592 ):
is not present in the handbook paper copy, if supplied by AlcatelLucent factory.
is present in the pdf file. Customer can use it to print and assembly the handbook in the same
way that is done by AlcatelLucent factory.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

33 / 592
ED.02 is the first validated and released edition associated to SWP 9400AWY R.2.1 V2.1.1 final Version
V2.1.1 , and fully annuls and replaces previous ED.01 (same P/N), that was issued in association with
prerelease V2.1.1*.
WARNING:
If you have a SWP version different from final V2.1.1, use neither this manual nor
the CDROM containing it, but those specific for such a version (refer to
AlcatelLucent).
For detailed information regarding the applicability and purpose of this manual, please refer to para.57.1
on page 567
WARNING:
Ed.02 of this manual is validated in conjunction with SWP final version V2.1.1 only.
Information relevant to SWP versions different from V2.1.1 , if any, must be
considered preliminary, subject to change and without any obligation on the part
of AlcatelLucent.
Following information can be useful for users owing the previous edition of this manual. Other users can
simply ignore it.
This edition has been made for the following major changes:
elimination of information regarding the oldtype Data plugin (2 Fast Ethernet ports), throughout
the whole manual
updated information regarding the Flash Cards on pages 93 to 95
updated information regarding the Graphical User Interface, throughout the whole manual,
according to final Version V2.1.1
improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495
appendix Documentation Guide from page 567 updated for new CDROM and handbooks
INFORMATION FOR ALCATELLUCENT INTERNAL USE ONLY

ED
DATE
CHANGE NOTE
(yymmdd)
(ECO)
02
080125
00000 57267
APPRAISAL AUTHORITY
ORIGINATOR
M.Nosari, C.Van Kerrebroeck
E.Corradini
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
34 / 592
USER MANUAL
SYSTEM DESCRIPTION

11.4 Notes on present edition

11.5 SafetyEMCEMFESD norms and equipment labelling

a)
Please refer to Appendix A on page 501 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
Heatradiating 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
b)
Electromagnetic Compatibility (EMC norms)
Other Labels affixed to the Equipment
Identical or similar information on Personal Computer, WorkStation etc., other than

AlcatelLucents, loaded with software applications described in this or other Handbooks, is
supplied in the Constructors technical documentation.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

35 / 592
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 AlcatelLucent as it is and must never be disassembled , with the exception of
operations described in para.47.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 EMIEMC performance.
The screw tightening torque must be:
2.8 kg x cm (0.28 Newton x m) " 10 %

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

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

To connect the CT cable (at IDU Main Units 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 Units 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 Units F or OS Ethernet interface and/or PC side):
perform the logoff, exiting from the CT applications (details in para.22.5.3 and 22.5.4 on page
180)
close all other running applications, if any
switch off the PC
now the cable can be safely disconnected.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
36 / 592
USER MANUAL
SYSTEM DESCRIPTION

11.6 Cautions to avoid equipment damage

12 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 39
System configurations, on page 50
Equipment Craft Terminal and TCO Suite, on page 54
Flash Card types and content, on page 56
General on equipment installation and SWP installation and management, on page 58
12.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 (max length specified in para.15.5 on
page 135 ) 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 networks NE specific data.
9400AWY
ULS NE A
9400AWY
ULS NE B
ETSI RADIO
ODU
ODU
ETSI PDH
ETHERNET
SERVICE CH.
ETSI PDH
ETHERNET
SERVICE CH.
IDU
SUPERVISION
NETWORK
IDU
Fig. 2. 9400AWY radio link

N.B.
With the exception of Chapter 32 LineUp and Commissioning on page 329, this Manual
deals with the description of a single 9400AWY Network Element.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

37 / 592
up to 32 E1
and up to four Gigabit Ethernet (GE) Tributaries (10/100/1000BT)
with different radio modulation formats, according to the following Tab. 3. :

Tab. 3. Tributaries and modulations
Market
ETSI
Max PDH Tributaries
Max Ethernet
Tributaries
Radio Modulation
2xE1
4 x GE
4QAM
4xE1
4 x GE
4QAM / 16QAM
8xE1
4 x GE
4QAM / 16QAM
16xE1
4 x GE
4QAM / 16QAM
32xE1
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 channelassociated failures
for both hardware failures and temporary signals degradation or losses due to propagation effects
(e.g. rain) according to equipment configuration.
Radio Physical Interface (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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
38 / 592
USER MANUAL
SYSTEM DESCRIPTION

ULS NE has the aim to multiplexer/demultiplexer the main tributaries:

12.2 Equipment architecture

12.2.1 Splitmount architecture
The 9400AWY system has been designed in a split mount architecture. As shown in Fig. 3. on page 40, it
consists of three main parts.
Indoor Unit (IDU)
details in paragraph 12.2.2 on page 42
Outdoor Unit (ODU)
IDUODU cable(s)
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, each one with a solar shield)
incorporates the complete RF transceiver and can be associated with an integrated or separate
antenna.
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 fullindoor configuration (obviously without antenna) is also available; its physical
implementation is described in the Installation Handbook.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

39 / 592
ODU Ch#1
Antenna
ODU
IDUODU cable
NE
ULS
DISTRIBUTOR SHELF (optional)
IDU
IDU MAIN UNIT Ch#1
9400AWY R.2.1 (1+1) SPLITMOUNT SYSTEM

for possible ODU (1+1)
configurations
see Fig. 4. on page 41
ODU
IDUODU cables
NE
ULS
DISTRIBUTOR SHELF (optional)
D
IDU
B
A
Legend:
D
SERVICE CHANNELS PROTECTION BOX
C
E1 PROTECTION BOX
B
IDU MAIN UNIT Ch#1
A
IDU EXTENSION UNIT Ch#0
Fig. 3. 9400AWY R.2.1 splitmount system
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
40 / 592
USER MANUAL
SYSTEM DESCRIPTION

9400AWY R.2.1 (1+0) SPLITMOUNT SYSTEM

Antenna CH 0
Antenna CH 1
ODU CH 1
ODU CH 0
to IDU EXTENSION UNIT
to IDU MAIN UNIT
ODU (1+1) HSBSD or FDDA AP with two antennas
COUPLER
ANTENNA
ODU CH 0
ODU CH 1
to IDU MAIN UNIT
ODU (1+1) HSB with one antenna

N.B.
this drawing is an example referred to the coupler used in

1338 GHz configurations.
Couplers used in 78 GHz configurations are shown in
Fig. 44. on page 117.
Double Polar Antenna
ODU CH 0
ODU CH 1
to IDU MAIN UNIT
ODU (1+1) FDAP with one double polar external antenna
Fig. 4. Possible configurations of ODU (1+1)
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

41 / 592
The IDU incorporates the baseband processing and offers tributaries interfaces as well as service
channel and supervision.
The IDU is frequencyindependent, but capacitydependent.
As shown in Fig. 3. on page 40, 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
up to two optional IDU Distributor Shelves
and necessary interconnection cables.

Fig. 7. on page 44 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 (only if the optional AUDIO + USER SERVICE
CHANNEL plugin is equipped)
up to two optional IDU Distributor Shelves
and necessary interconnection cables.

Fig. 8. on page 45 shows the block diagram.
In 1+0 and 1+1 configuration:
both the Main and the Extension IDU units, if not equipped with plugsin, are physically able
to support up to 16xE1 interfaces. Such capacity can be reduced according to the Software
Label employed.
it is possible to accommodate different types of tributary plugin alternative to each other,

exploiting the same mechanical space on the front panel:
1732xE1 plugin , allowing to support the extension to 32xE1 interfaces, to be plugged

onto both Main and Extension units
Enhanced DATA plugin , implementing Ethernet functionalities, and supporting 4 x

10/100/1000 baseT ports. This plugin is plugged onto the Main IDU unit only.
independently from the tributary plugins listed above, another optional plugin, to be plugged
onto the Main IDU unit only, allows the AUDIO + USER SERVICE CHANNEL functionality.
In 1+1 configuration:
the Main and Extension units are interconnected by means of an auxiliary flat cable (100wires
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 , provided that the AUDIO + USER SERVICE CHANNEL plugin is equipped.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
42 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.2.2 IDU (Indoor Unit)

[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.13.3 on page 70 .
[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 (4860) VDC nom. 20%

N.B.
No Fans Unit are foreseen inside the 9400AWY IDU units.
[4]
Flash Card and Software Label

A Flash Card (containing the system software, the Software Label, and the NE configuration, even
if this configuration is almost empty ) is always plugged onto the Main unit. The Software Label 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 45 .
equipment side
User line side

Fig. 5. E1 Protection box
equipment side
User line 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.13.5 on page 79 (E1 Protection Box) and to para.13.6 on page 84
(Service Channels Protection Box).
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

43 / 592
Distribution shelves
For the physical connection at station DDF 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 AlcatelLucent;
usage of AlcatelLucent distributor subracks, to be housed in the same rack where 9400AWY
IDU shelves are installed.
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 plugin
16xE1 + 4 x 10/100/1000 BaseT Ethernet plugin
16xE1 + AUDIO & USER SERVICE CHANNEL plugin + 4 x 10/100/1000 BaseT Ethernet
plugin
32xE1 configurations:
32xE1
32xE1 + AUDIO & USER SERVICE CHANNEL plugin.
All subequipped configurations delivered from factory can be upgraded later by means of the
specific upgrade kits, as described in chapter 47 on page 469.
[8]
Block diagrams
Main board
(JBIDUM)
4 x 10/100/1000 BaseT
1732E1
Main IDU
Ethernetdata
plugin
Ethernet
plugin
E3/DS3plugin
16 E1/DS1plugin
1732E1
plugin
(JAIDUE1)
EPS
MUX/DEMUX
ODU
116E1
NMS_V11
NMS_G703
IDUODU
IDU
ODU
interface
Audio channels
Service Channel (64Kbit/s)
Audiochannels
+ +ServiceChannel
V11 + G703
Plugin
(JAIDUSC)
Plugin
PSU
PSU
uPuP
EC
/ RC
Alarms& housekeepings
RS232
10/100 BaseT
ECT
N.B.
OS (or ECT)
Ethernet and 1732E1 plugins are in alternative.

Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
44 / 592
USER MANUAL
SYSTEM DESCRIPTION

[6]
N.B.
On Main IDU unit, Ethernet and 1732E1 plugins are in alternative.

Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
45 / 592
(64Kbit/s)
Service Channels
SERVICE CHANNELS
PROTECTION BOX
116E1
116E1
Alarms & housekeepings
Audio channels
116E1
NMS_V11
NMS_G703
1732E1
4 x 10/100/1000 BaseT
1732E1
1732E1
E1 PROTECTION BOX
Audio channels
+ +Service
Channel
V11 + G703
Plug in
(JAIDUSC)
Plugin
16 E1/DS1 plug in
1732E1 plugin
(JAIDUE1)
Ethernet data
plug in
Ethernet plugin
data
Ethernet
plug
E3/DS3
pluginin
16
E1/DS1
161732E1
E1/DS1 Plug
plug
in
plugin
(JAIDUE1)
E3/DS3 plug in
ECT
RS232
EPS & RPS
IDUODU
interface
OS (or ECT)
10/100 BaseT
IDUODU
interface
EPS
Interconnection cable
uPuP/ RC
EC
MUX/DEMUX
Main board
(JBIDUM)
MUX/DEMUX
Extension board
(JBIDUE)
PSU
Main IDU
PSU
Extension IDU
ODU
ODU

a)
ODU type:
In 9400AWY R.2.1.1, only the 64Mb V1 ETSI ODU types can be used.
Note for 9400AWY R.2.0 Customers only:
Neither the 32Mb ODU types (V1 and V2) nor the 64Mb V2 ODU types (used in 9400AWY R.2.0,
from V2.0.5) can be used in 9400AWY Rel.2.1.1 environment.
b)
Air interface compatibility: frame arrangement

The Air frame is the AWY format respecting the bandwidth partitioning between traffic and dedicated
service channels.
c)
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 full integrated antenna (30 cm or
60 cm diameter) or a waveguide for not integrated antenna connection can be connected.
The ODU consists of subunits which carry out the following main functions (see Fig. 9. on page 47):
[1]
Modem: It consists of a baseband part and an IF part. The main functions are:
[2]
FrontEnd. The main functions are:
N.B.
Cable interface: DC splitting, echo cancellation, clock recovery

HDB3 coding/decoding
Modulation and demodulation
Digital to analog conversion
Analogue filtering
Upconversion in Tx side in the frequency range of 1 GHz to 2.1 GHz
Downconversion in Rx side from 675 MHz to base band
Control function for hardware configuration and dialog with the IDU.
AGC IF amplification
Upconversion to the RF Tx channel frequency
Transmit power control range of 30 dB
RF loopback (N.B.)
Double mixers at Rx side (the frequency of the signal sent to the modem board is 675 MHz
whatever the frequency band and shifter).
RF loopback is optional and provided only with specific configurations
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
46 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.2.3 ODU (Outdoor Unit)

[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 bandpass 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. 9. ODU block diagram

d)
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
01924.1). It assumes that the protection of the solar shield is 15 0C.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

47 / 592
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. 4. below depicts the corresponding radio configurations.

Tab. 4. 13 to 38 GHz 4/16 QAM configurations
Configuration
ODU cabinet
RF channeling
Coupler
Antenna
1+0
NO
1+1 HSB
1/10 dB asymmetric
1+1 HSB SD
NO
1+1 FD AP
NO
1
(nonintegrated
only)
1+1 FD DA
NO
OR
Legend:
AP = Alternate polar
DA = Dual antenna
f)
ODU Coupler
The ODU coupler (shown in Fig. 43. on page 116 for 1338 GHz bands, and in Fig. 44. on page 117
for 78 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
48 / 592
USER MANUAL
SYSTEM DESCRIPTION

e)

12.2.4 IDUODU cable

The connection between the IDU and the ODU is realized with a single coaxial cable and N50 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 IDUODU
service channels.
The bit rate of the aggregate signal is listed in the following table.
Tab. 5. Bit rate of the IDUODU signal on the cable
ETSI (2 to 16xE1) AWY configuration
39.168 Mbit/s
ETSI (17 to 32xE1) AWY configuration
78.336 Mbit/s
The IDUODU cable is a standard coaxial cable whose characteristics are specified in para.15.5 on page
135.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

49 / 592
The configurations available are:
Unprotected configurations (1+0)

described in para.12.3.1 herebelow
Protected configurations (1+1)

described in para.12.3.2 on page 51.
N.B.
for the detailed description of station layouts and equipment interconnections, refer to
para.32.2 from page 331 onwards.
12.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 capacityindependent.
one Indoor Unit (MAIN IDU unit) incorporating the baseband processing and offering tributaries
interfacing as well as service channel and supervision.
The IDU is frequencyindependent.
one optional E1 Protection Box
one optional Service Channels Protection Box
one/two optional IDU Distributor Shelf/ves
one IDUODU coaxial cable
Fig. 10. below shows the IDU+ODU block diagram.

IDU 1+0
1 x ODU
DISTRIBUTOR SHELF
interconnections
IDUODU cable
IDU MAIN UNIT
RT
Fig. 10. 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 44, and and Tab. 6. on page 68)
and the employed Software Label (see Tab. 23. on page 93)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
50 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.3 System configurations

12.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.12.3.2.1 below:
para.12.3.2.2 on page 52 :
IDU (1+1) configurations

ODU (1+1) configurations
12.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 plugin 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 44, and Tab. 6. on page 68)
and the employed Software Label (see Tab. 23. on page 93)
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

51 / 592
According to the ODU configurations introduced in Tab. 4. on page 48, at radio level the following system
implementations are available:
1+1 Hot Stand By (HSB):
with Space Diversity (SD)
or without space diversity
see Fig. 11. herebelow

see Fig. 12. herebelow
1+1 with Frequency Diversity (FD):
FD double antenna AP
FD one antenna AP

N.B.
The radio configurations are independent from the IDU (1+1) configurations described in
previous para.12.3.2.1 on page 51.
IDU 1+1
interconnections
DISTRIBUTOR SHELF
ODU CH 1
HDB3
MODEM
IF
E1 PROTEC. SERV.CHAN.
BOX
PROTEC.BOX
RF
only one RT
transmits
IDU MAIN UNIT
ODU CH 0
IDU EXTENSION UNIT

HDB3
MODEM
IF
RF
Fig. 11. 9400AWY (1+1 HSB SD) IDU + ODU block diagram
interconnections
IDU 1+1
DISTRIBUTOR SHELF
ODU CH 1
HDB3
MODEM
IF
BOX
PROTEC.BOX
Coupler
RF
only one RT
transmits
IDU MAIN UNIT
1:1
0
ODU CH 0
IDU EXTENSION UNIT

HDB3
MODEM
IF
RF
Fig. 12. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
52 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.3.2.2 ODU (1+1) Configurations
interconnections
DISTRIBUTOR SHELF
ODU CH 1
HDB3
MODEM
IF
BOX
PROTEC.BOX
RF
both RTs
transmit
IDU MAIN UNIT
AP
ODU CH 0
IDU EXTENSION UNIT

HDB3
MODEM
IF
RF
Fig. 13. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram
IDU 1+1
ODU CH 1
HDB3
interconnections

IDU 1+1
DISTRIBUTOR SHELF
MODEM
IF
BOX
PROTEC.BOX
RF
both RTs
transmit
IDU MAIN UNIT

ODU CH 0
IDU EXTENSION UNIT

HDB3
MODEM
IF
RF
Fig. 14. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

53 / 592
The Local Operator can manage the Equipment software programs and most configuration data through
the Equipment Craft Terminal 1320CT connected to the Equipments F or Ethernet interface.
The Craft Terminal characteristics (computer configuration) are listed in para.31.1.1 on page 309.
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 50 Network elements is possible obtaining a remote Craft Terminal
application.
The general information on the Craft Terminal is presented in the:
1320CT Basic Craft Terminal Operators Handbook (see Tab. 78. on page 571)
that the operator has to read before this Handbook.

In this Handbook is given the general description regarding use, navigation, rules, etc., common to
all the NE using the same Craft Terminal.
Furthermore, the same handbook contains the detailed description of common operations as
Installation and common screens as Network Element Synthesis view.
The Network Element Synthesis view is the first view presented to the operator entering the
application.
Starting from this view it is possible to login to the NE and then to enter the EMLULS views, which
directly allow to manage the Network Element.
A detailed description of the 9400AWY EMLULS screens is given in the dedicated Section of this
handbook:
SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139
12.4.1 ECT
AlcatelLucent 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 AlcatelLucent proprietary SWP (SoftWare Package) is employed, which
depends on the productrelease and the NE (Network Element) associated to the specific configuration.
12.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 interarea
communication is possible from networking viewpoint).
Of course, due to the limitation of the physical resources in the Equipment Controller of the NE, some
network design constraints must be taken into account as the total number of managed NEs (50).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
54 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.4 Equipment Craft Terminal and TCO Suite

The following limitations must be taken into account, too:

a)
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.
b)
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 will refuse
the incoming association issued by a RECT and the ECT displays only local information.
c)
only three RECTs can 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.
12.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 CDROM).
TCO Suite works through web pages with simple operations available with a single mouse click.
Please refer to para.22.2 on page 146 for details.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

55 / 592
Whole Equipment configuration data and programs are contained in the Flash Card, as shown in
Fig. 15. below:
SOFTWARE LABEL
Fixed Data
SW
COMMIT
VERSION
(ACTIVE)
SW instances
SW
STANDBY
VERSION
(not active)
MIB
NE Data
NE network
routing data
Fig. 15. Flash Card content

[1]
Fixed Data
The Software Label stored in the Flash Card (plugged into the IDU Main board as shown in
Fig. 21. on page 70 and Fig. 34. on page 94) allows flexibility in choosing user interfaces and
modulation as shown in Tab. 23. on page 93
The Software Label is strictly associated to the Flash Card Logistical Item, and cannot be
changeable, but with Flash Card upgrade (see para.47.3 on page 479).
[2]
SW instances
The SW COMMIT VERSION is that used by the system.
The SW STANDBY VERSION instance is created the first time a SW download from ECT to the NE
is carried out.
A new SWP download is envisaged whenever a new SWP package version or release (new with
respect to that presently loaded in the system) is supplied to Customer (*).
(*) for the meaning of SWP package version and release refer to para.57.3.2 on page 573.
As supplied by AlcatelLucent factory, unless differently required by Customer, the SWPversion
downloaded in Factory is the most recently released at the date of Flash Card delivery to the
Customer, so that the SW instances present in the flash card are:
the SW COMMIT VERSION
the SW STANDBY, loaded with the SW version immediately previous (if any) with respect to
the COMMIT one
The management of these SW instances is described in Chapter 213 Software Management

on page 297.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
56 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.5 Flash Card types and content

[3]
NE data
N.B.
as shown in Fig. 15. on page 56, differently from SW instances, NE data are present as
single instances in the Flash Card.
a)
Base configuration
It is defined by Flash Card Logistical Item.
It is not changeable, but with Flash Card upgrade (see para.47.3 on page 479).
b)
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.
As supplied by AlcatelLucent factory, the 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 214 MIB Management on page 301.
c)
NE network routing data

Defined by Craft Terminal or by TCO Suite SetUp Tool, they are:
1.
2.
3.
4.
Local configuration Systems local address

NTP server configuration
Interface configuration
NMS configuration
Ethernet configuration
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.32.3.6 on page 341). Such a file contains (besides other
data) the NE network routing data defined above.
As supplied by AlcatelLucent factory, the NE network routing data are set to default values.
[4]
System restart and system startup

The system restart (reloading of all RAMs present in the system with information stored in the Flash
Card) is carried out:
after the activation of a new SWP
after EC/OC reset (manual of after new SWP activation)
after power off/on , with 2 to 5 minutes necessary for system startup after the power on.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

57 / 592
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 Flash Card types and content
(para.12.5 on page 56 ).
N.B.
Please refer to para.57.3.2 on page 573 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 59
First SWP installation in PC and NE environments
on page 60
How to check ECT and NE SWP versions
on page 62
Common situations requiring ECT and/or NE upgrade
on page 64
Flash Card related special procedures
on page 64
Craft Terminal related special procedures
on page 64
NE configuration data change and save
on page 65
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
58 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.6 General on equipment installation and SWP installation and

management

12.6.1 Main phases for 9400AWY HW and SW installation

The summary procedure depicted in Fig. 16. below presumes that the SWP version loaded in factory
inside the NEs Flash Card corresponds to that of the SWP CDROM delivered to Customer with the
equipment.
N.B.
The documents with symbol

are included in the same CDROM containing this manual.
For Installation Handbook or Installation Guide choice, read the specific note in Tab. 77.
on page 570
ECT INSTALLATION
described in:
HW INSTALLATION
described in:
9400AWY
or
Installation Guide
Chapter 31 SWP installation in PC

environment on page 309
EQUIPMENT POWERON AND COMMISSIONING

described in:
Chapter 32 LineUp and Commissioning
on page 329
and reporting test results in document:
TRS & SAT
CREATION OF NE OPERATOR PROFILES

described in
NE DATA SAVE
described in
para.12.6.8 on page 65
Fig. 16. Main phases for 9400AWY HW and SW installation
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

59 / 592
Fig. 17. depicts the main phases for SW management, when it is loaded the first time in PC and NE
environments.
SWP
CDROM
1)
SWP LOADING IN PC ENVIRONMENT
CRAFT TERMINAL
2)
NEW SWP
INSTALLATION
6) MIB
BACKUP
3)
NE SWP LOADING
INTO EQUIPMENT
CONTROLLER
(if necessary)
DURATION (about):
30 minutes with
interface F
15 minutes with
Ethernet interface
4)
5) NE CONFIG.
DATA MNGT
7) MIB
RESTORE
AUTOMATIC SW
DOWNLOAD TO
SUPERVISOR UNITS
(if necessary)
DURATION:
some minutes
Fig. 17. Software management main phases
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
60 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.6.2 First SWP installation in PC and NE environments

The SW management can be distinguished into:
program management, i.e.:
(1) and (2) : SWP loading from CDROM to the Personal Computer, after which the PC
becomes and can be used as the Equipment Craft Terminal (abbreviated as ECT or CT)
(3) NE SWP downloading from ECT toward the NetworkElements Equipment Controller (EC),
if necessary (it is necessary if the NE SWversion is lower than that of the ECT)
N.B.
in general, firsttime system installation is carried out with the NEs flash card loaded
in factory with the same SWPversion 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 SWversions present in the Peripheral Units are lower than those
available in the ECTs SW components)
NE configuration data management:
(5) NE configuration data definition and equipment lineup and commissioning
(6) NE configuration data save in Equipment Craft Terminal (MIB backup)
(7) NE configuration data restore from Equipment Craft Terminal (MIB restore, if necessary)
The firsttime 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 31 on page 309
SWP download toward NE, if necessary

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

that includes task (5) mentioned above.
At the end of the firsttime 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.
NE
ECT
ECT release = NE release
A.B.c
A.B.c
ECT version = NE version
This is the typical situation of new installations: the Network Element SW configuration matches
the available Craft Terminal SWP version, so that the NE can be loggedin and the Operator
can carry out the required operations, without any incompatibility problems.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

61 / 592
[1]

12.6.3 How to check ECT and NE versions

How to check ECT version
This check can be done with ECT not connected to any NE
(2)
(1)
(3)
(4) read version
Fig. 18. How to check ECT version

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
62 / 592
USER MANUAL
SYSTEM DESCRIPTION

[2]
How to check NE version

Proceed as follows:
1)
Carry out NE Login (as described in para.22.5.2 on page 173)
2)
From the Menu Bar of the 9400AWY Main view that opens after NE Login (Fig. 87. on page
181), perform SW Download SW Status
V02.01.01
version committed
(active)
V02.01.00
N.B.
version standby
(not active)
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.1.1)
that standby is the immediately previous SW version (e.g. V2.1.0)

Fig. 19. How to check NE SW version (example)
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

63 / 592
The following situations require CT and/or NE upgrading, in order to reach the standard situation defined
in point 1 ) on page 61:
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)
NE
ECT
running release = SWP release

A.B.c
A.B.c
running version < SWP version
SWP
CDROM
A.B.d
This could be the typical situation of installations already running with A.B SWP package
(e.g.2.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 49 on page 495.
After that, the situation is equal to that of point 1 ) on page 61.
2)
Network Element already configured with the more recent SWP version, but the Craft
Terminal is not available or has a version older with respect to that of the Network
Element(s).
NE
ECT
ECT release = NE release
A.B.d
A.B.c
ECT version < NE version
In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter
31 on page 309. After that, the situation is equal to that of point 1 ) on page 61.
12.6.5 Flash Card related special procedures

Taking into account the information contained in the Flash Card (see para.12.5 on page 56 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.47.3 on page 479.
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 46 Spare Flash Card management and replacement
procedures on page 465
12.6.6 Craft Terminal related special procedures

If you need to:
5)
deinstall AlcatelLucent SW from the PC used as Craft terminal, refer to chapter 410 on
page 497.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
64 / 592
USER MANUAL
SYSTEM DESCRIPTION

12.6.4 Common situations requiring ECT and/or NE upgrade

12.6.7 NE configuration data change and save

It must be emphasized that , every time you change the equipment configuration data (see para.12.5 on
page 56), you must always save the relevant data:
a)
data present in Flash Cards MIB bank [see point b ) on page 57]
Data present in Flash Cards MIB bank can be saved in a MIB backup file as described in Chapter
214 on page 301.
The same chapter explains how to recover MIB data from the MIB backup file.
The procedures in this handbook make often reference to the MIB data restore from the MIB backup
file. WARNING: read carefully para.12.6.9 below.
If you change the equipment configuration data without carrying out the MIB backup 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 backup file [see point c ) on page 57]
Only NE network routing data are not saved in the MIB backup file.
Nevertheless, it is possible to create, save and recover configuration files having the .qcml
extension (for details refer to para.32.3.6 on page 341). Such a file contains (besides other data)
the NE network routing data. WARNING: read carefully para.12.6.9 below.
Procedure for .qcml file backup:
1)
2)
3)
4)
launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345
in the screen of Fig. 244. on page 346 , click on button Get configuration from NE
the window in Fig. 245. on page 347 will appear. This window is the first step of the Quick
Configuration Procedure (interactive)
clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 and
click on Save As button: configuration data are saved in a configuration_name.qcml file
(provide a mnemonic name)
12.6.8 NE data save after commissioning completion

For the NE, create a folder containing the following files:
the MIB backup file [point a ) above]
the .qcml configuration file [point b ) above]
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.
12.6.9 NE data compatibility between SWP 2.1.x versions
[1]
MIB backup file

A MIB backup file created while system was running with any SWP version < 2.1.1 can be reused
on a system running with the SWP version 2.1.1.
A MIB backup file created while system is running with the SWP version 2.1.1 cannot be reused
on a system running with any SWP version < 2.1.1.
[2]
.qcml configuration file

A .qcml configuration file created while system was running with any SWP version < 2.1.1 can be
reused on a system running with the SWP version 2.1.1.
A .qcml configuration file created while system is running with the SWP version 2.1.1 cannot be
reused on a system running with any SWP version < 2.1.1.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

65 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
66 / 592
USER MANUAL
SYSTEM DESCRIPTION

13 IDU PROVISIONING AND DESCRIPTION

This chapter gives detailed operative information regarding the IDU shelfs 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 68
Labels affixed on the IDU
on page 69
Description of IDU Main unit

on page 70
IDU Main Unit LEDs summary

on page 73
Power Supply connector pinout

on page 74
ECT RS232 connector pinout

on page 75
OS (or ECT) 10/100BaseT connector pinout

on page 75
Ethernet tributaries
on page 76
Description of IDU Extension unit
IDU Extension Unit LEDs summary
Description of E1 Protection box

on page 79
E1 Protection box: connector pinout

on page 80
Description of Services Protection box

on page 84
Alarms Housekeeping (pinout and description)
NMS V.11 Audio 1 (pinout and description)
NMS G.703 Audio 2 (pinout and description)
User service channels (pinout and description)
on page 77
on page 78
on page 85
on page 88
on page 89
on page 90
Provisioning and identification of Flash Cards & Software Labels
on page 93
Provisioning and description of equipment accessories on page 96
Note for all provisioning tables:
the Logistical Item corresponds to the Logistical Item code you can read on the IDUs label (see
Fig. 20. on page 69 )
please refer to the Installation Handbook for the provisioning of cables and other items that depend
on the installation choices.

Carefully observe statements specified in para.11.6 on page 36
N.B.
For detailed operative information regarding the:
description of equipment interconnections, please refer to para.32.2 on page 331
equipment installation, please refer to the Installation Handbook
equipment commissioning, please refer to Chapter 32 on page 329
equipment maintenance, please refer to section 4 MAINTENANCE on page 407.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

67 / 592
Tab. 6. IDU shelf provisioning for 1+0 and 1+1 configurations

CONFIGURATION
16E1
Logistical Item &
Description
16E1
16E1 +
AUDIO &
USC
32E1
16E1 +
4 ETH
16E1+
4 ETH +
AUDIO &
USC
32E1
32E1 +
AUDIO &
USC
ETSI IDU MAIN UNITS

(48/60V POWER SUPPLY)
For 1+0 and 1+1 configurations
3DB16040ABXX
1 0 IDU 16E1 48/60V PSU
3DB16058ABXX
1 0 IDU 16E1 48/60V PSU AUDIO USC
3DB16160AAXX
1 0 IDU 16E1 ENH DATA 48/60V PSU
3DB16162AAXX
X
1 0 IDU 16E1 ENH DATA 48/60V PSU AUDIO

USC
3DB16041ABXX
1 0 IDU 32E1 48/60V PSU
3DB16059ABXX
1 0 IDU 32E1 48/60V PSU AUDIO USC
ETSI IDU EXTENSION UNITS

(48/60V POWER SUPPLY)
Only for 1+1 configurations
3DB16044ABXX
EXT IDU 16E1 48/60V PSU
3DB16045ABXX
EXT IDU 32E1 48/60V PSU
PROTECTION BOXES
Only for 1+1 configurations
3DB16102AAXX
E1 Protection (SCSI 68 / Dsub 37)
3DB16103AAXX
X
X
Services Protection (Dsub44 / Dsub15)
Equipment interconnection diagrams

(page)
332
333
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
68 / 592
X
X
334
335
336
337
USER MANUAL
SYSTEM DESCRIPTION

13.1 Provisioning of IDU shelves

13.2 Labels affixed on the IDU

This label is affixed on the back side of:
the IDU MAIN unit [position (C) in Fig. 21. on page 70 ]
the IDU EXTENSION unit [position (C) in Fig. 23. on page 77 ]
this label is just an example

SYMBOL OR WRITING
MEANING
9400AWY
Equipment Acronym & Alcatel or AlcatelLucent Logo
CE
European Community logo
12345 (example)
Notified body
Not harmonized frequency logo

2002/96/EC WEEE (Waste Electrical and Electronic
Equipment) Logo (see para.15.10.3 on page 137)
Electrostatic Device Logo
Logistical item 3DB 05620 AAXX (example)
Logistical item for Customer
Logistical item for Customer, bar code 128
P/N ICS 3DB 05620 AAAA 01 (example)
Factory Technical Code + ICS
Factory Technical Code + ICS, bar code 128
SERIAL N CW052402145 (example)

SERIAL N CW052402141 (example)
Factory serial number
Factory serial number bar code 128
24 V 20%, 2.2 A max (example)
Power Supply Version 24 V
4860 V 20%, 1.10.7 A (example)
Power Supply Version 48/60 V
2460 V 20%, 2.20.7 A (example)
Power Supply Version Full Range

Feeding to Continuous Current
Fig. 20. Label affixed on the IDU
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

69 / 592
10
11
12
13
14
15
16
17
18
Fig. 21. IDU Main Unit front and rear views
Tab. 7. IDU Main Unit: external interfaces list
Ref.
Fig. 21.
Connector or item detail
Interface / Explanation
Details
Station Battery input
para.13.3.2
on page 74
Basic Interfaces (without optional plugsin)

(1)
SubD 3 Male
(2)
ON/OFF switch: general

power supply switch
(IDU Main + its ODU)
(3)
RJ45
OS (or ECT) 10/100BaseT
para.13.3.4
on page 75
(4)
Debug RJ45
For
Factory use only
For IDUODU cable
(N.B.2)
(9)
Acknowledgement: Alarm
attending pushbutton; this
pushbutton turns OFF LEDs
MAJ/MIN and turns ON
yellow LED ATTD
para.45.6.2
on page 434
(10)
Equipment Controller
Reset pushbutton
possible use inside

corrective
maintenance
(11)
Lamp Test pushbutton: it

allows to HW test the LEDs
of the unit
para.44.2.1
on page 421
(8)
N 50 ohm Female
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
70 / 592
I
O
ON
OFF
USER MANUAL
SYSTEM DESCRIPTION

13.3 Description of IDU Main unit

Ref.
Fig. 21.
Details
(12)
SubD 9
RS232 connector for NECT

serial cable
para.13.3.3
on page 75
(13)
SCSI 68 pin Female
116E1 64 wires
(N.B.1)
(14)
SCSI 100 pin Female
connector for 100 pin SCSI

flat cable (used only in 1+1
configurations)
interconnection with
Extension Unit,
no pin usage by
Customer
(15)
SubD 44 Female
connector for Alarms

Housekeeping NMS
(N.B.1)
(16)
9 LEDs
para.13.3.1
on page 73
Flash Card
para.13.7
on page 93
(17) + (18)
+ (A)
(B)
label
Data Matrix codification
for factory use
(C)
label
unit identification
Fig. 20.
on page 69
Optional Interfaces (with optional plugsin)

Connectors according to the equipped plugin (if any) (N.B.3) :
(5)
SCSI 68 pin Female
4 x RJ45 Ethernet user data,

when
Enhanced Ethernet plugin
is equipped
para.13.3.5
on page 76
1732 E1 64 wires,
when the 1732 E1 plugin
is equipped
(N.B.1)
Connectors present only when the Audio + User Service Channel plugin is
equipped (N.B.3) :
SubD 44 Female
(6) + (7)
Audio1/2 + G703_V11 User

Service Channel
(N.B.1)
RJ11 Female for

EOW telephone
chapter 42
on page 413
Notes on next page
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

71 / 592
(N.B.1)
(N.B.2)
(N.B.3)
For connector pinout, refer to the Installation Handbook

ATTENTION
(caution to avoid equipment damage)
The Ntype connector carries +48 DC voltage for ODU power supply.
Do not connect measuring instruments directly.
When no plugin equipped, the slot is closed by a metal plate (inside the panel rear
side).
Metal plate is mandatory to ensure EMIEMC performance
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
72 / 592
USER MANUAL
SYSTEM DESCRIPTION

Notes to Tab. 7.

13.3.1 IDU Main Unit LEDs summary

Nine LEDs are present on the front panel of the IDU Main Unit [position (16) in Fig. 21. on page 70 ]:
1) ON
2) RDI
3) MIN
4) EOW
5) ODU W
6) ATTD
7) MAJ
8) LDI
9) ANT
GREEN
RED
GREEN
RED
GREEN
RED
YELLOW
RED
YELLOW
= Power ON (green)
= Remote Defect Indication (red)
= Minor Alarm (red)
= Engineering Order Wire (bicolor: yellow if busy; green if free)
= ODU Working (green)
= Attended (yellow)
= Major Alarm (red)
= Local Defect Indication (red)
= Not operative in current SWP version
Fig. 22. 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 plugin failure (Card Fail and Card Missing)
1732xE1 plugin failure (Card Fail and Card Missing)
Loss of Signal from Tributaries
Loss of cable from ODU (IDUODU 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 42 on page 413 for details.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

73 / 592
ODUW The ODUW led ON identifies the TX activity of the ODU connected to the MAIN unit.
It is OFF in case of:
IDUODU Cable Loss alarm
Mute function activated
ODU switchingoff command activated in 1+1 HSB configuration
[6]
ATTD The attended LED is ON when the acknowledgement button [position (9) in Fig. 21. on page
70 ] 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 plugin failure (Card Fail and Card Missing)
1732xE1 plugin failure (Card Fail and Card Missing)
Loss of Signal from Tributaries
Loss of cable from ODU (IDUODU 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. 21. on page 70 ] allows the HW test of all LEDs.
13.3.2 Power Supply connector pinout (MAIN and EXTENSION units)
Tab. 8. Power supply connections
Pin
Function
A1
+ BATTERY
A2
GROUND
A3
BATTERY
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
74 / 592
USER MANUAL
SYSTEM DESCRIPTION

[5]

13.3.3 ECT RS232 connector pinout

Tab. 9. ECT connections
pin 1
RS 232
RS 232
(IDU MAIN side)
(PC side)
13.3.4 OS (or ECT) 10/100BaseT connector pinout

Tab. 10. OS (or ECT) connections
N.B.
Leds are not operative

RJ45
RJ45
Signal
Color used
Tx +
White/Orange
Tx
Orange
Rx +
White/Green
Not used
Blue
Not used
White/Blue
Rx
Green
Not used
White/Brown
Not used
Brown
(IDU MAIN side)
USER MANUAL
SYSTEM DESCRIPTION
(OS side)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

75 / 592
Present on the front panel of the IDU Main Unit [position (5) in Fig. 21. on page 70 ] when the Enhanced
Ethernet plugin is equipped.
For the Ethernet user data interfaces the following table summarizes the meaning of the LEDs integrated
in the RJ45 connectors:
Tab. 11. RJ45 connectors leds for Ethernet user data interfaces
Color
Display
Function
Ledoff
Ledon
Led blinking
LEFT LED
Green
Link and
activity status
Link down
Link up
RIGHT LED
Yellow
activity
No TX/RX
activity
detected
TX/RX activity
detected
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
76 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.3.5 Ethernet tributaries

13.4 Description of IDU Extension unit

9
Fig. 23. IDU Extension Unit front and rear views
Tab. 12. IDU Extension Unit: external interfaces list

Ref.
Fig. 23.
Details
Station Battery input
para.13.3.2
on page 74
Basic Interfaces (without optional plugsin)

(1)
SubD 3 Male
(2)
ON/OFF switch: general

power supply switch
(IDU Extension + its ODU)
(3)
Lamp Test pushbutton: it

allows to HW test the LEDs
of the unit
para.44.2.1
on page 421
SCSI 68 pin Female
116E1 64 wires
(N.B.1)
(5)
SCSI 100 pin Female
connector for 100 pin SCSI

flat cable
interconnection with
Main Unit,
no pin usage by
Customer
(6)
SubD 44 Female
Audio1/2 + G703_V11 User

Service Channel
(N.B.1)
(7)
3 LEDs
para.13.4.1
on page 78
(8)
N 50 ohm Female
For IDUODU cable
(N.B.2)
(B)
label
Data Matrix codification
for factory use
(C)
label
unit identification
Fig. 20.
on page 69
(4)
I
O
ON
OFF
Optional Interfaces (with optional plugin)

Connector present only when the 1732 E1 plugin is equipped (N.B.3) :
(9)
SCSI 68 pin Female
USER MANUAL
SYSTEM DESCRIPTION
1732 E1 64 wires
(N.B.1)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

77 / 592
Details
Notes
(N.B.1)

ATTENTION
The Ntype connector carries +48 DC voltage for ODU power supply.
Do not connect measuring instruments directly.
(N.B.2)
(N.B.3)
When no plugin equipped, the slot is closed by a metal plate (inside the panel rear
side).
Metal plate is mandatory to ensure EMIEMC performance
13.4.1 IDU Extension Unit LEDs summary

Three LEDs are present on the front panel of the IDU Extension Unit [position (7) in Fig. 23. on page 77 ]:
GREEN
1) ON
2) ODU W
3) ANT
GREEN
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.
=
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:
IDUODU Cable Loss alarm
Mute function activated
ODU switchingoff command activated in 1+1 HSB configuration

= Not operative in current SWP version
Fig. 24. LEDs on the IDU Extension Unit front panel
The lamp test pushbutton [position (3) in Fig. 23. on page 77 ] allows the HW test of all LEDs.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
78 / 592
USER MANUAL
SYSTEM DESCRIPTION

Ref.
Fig. 23.

13.5 Description of E1 Protection box

3
Line Side
Equipment Side
Fig. 25. E1 Protection box: views of Equipment Side and Line Side connectors
Tab. 13. Equipment Side and Line Side connectors of E1 Protection box
Ref.
Fig. 25.
Connector
Interface
To be connected to
Line side
(1)
18 E1
(2)
(3)
916 E1
SubD 37 Female
(4)
see para.13.5.1 on page 80
1724 E1
2532 E1
Equipment side
(5)
116 E1
samename connector of IDU Main unit

[ (13) in Fig. 21. on page 70 ]
(6)
116 E1
samename connector of IDU Extension unit

[ (4) in Fig. 23. on page 77 ]
1732 E1

[ (5) in Fig. 21. on page 70 ]
1732 E1

[ (9) in Fig. 23. on page 77 ]
(7)
SCSI 68 pin Female

N.B.
(8)
N.B.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

79 / 592
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 40 )
Tab. 14. E1 tributaries (1 to 8) connector pinout
pin 1
Description
Pin #
Pin #
Description
Not Used
20
Not Used
IN+
Trib.
21
IN
Trib.
IN+
Trib.
22
IN
Trib.
IN+
Trib.
23
IN
Trib.
IN+
Trib.
24
IN
Trib.
IN+
Trib.
25
IN
Trib.
IN+
Trib.
26
IN
Trib.
IN+
Trib.
27
IN
Trib.
IN+
Trib.
28
IN
Trib.
GND
10
Not Used
11
29
Not Used
Out+
Trib.
12
30
Out
Trib.
Out+
Trib.
13
31
Out
Trib.
Out+
Trib.
14
32
Out
Trib.
Out+
Trib.
15
33
Out
Trib.
Out+
Trib.
16
34
Out
Trib.
Out+
Trib.
17
35
Out
Trib.
Out+
Trib.
18
36
Out
Trib.
Out+
Trib.
19
37
Out
Trib.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
80 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.5.1 E1 Protection box: connector pinout


pin 1
Description
Pin #
Pin #
Description
Not Used
20
Not Used
IN+
Trib.
21
IN
Trib.
IN+
Trib.
10
22
IN
Trib.
10
IN+
Trib.
11
23
IN
Trib.
11
IN+
Trib.
12
24
IN
Trib.
12
IN+
Trib.
13
25
IN
Trib.
13
IN+
Trib.
14
26
IN
Trib.
14
IN+
Trib.
15
27
IN
Trib.
15
IN+
Trib.
16
28
IN
Trib.
16
GND
10
Not Used
11
29
Not Used
Out+
Trib.
12
30
Out
Trib.
Out+
Trib.
10
13
31
Out
Trib.
10
Out+
Trib.
11
14
32
Out
Trib.
11
Out+
Trib.
12
15
33
Out
Trib.
12
Out+
Trib.
13
16
34
Out
Trib.
13
Out+
Trib.
14
17
35
Out
Trib.
14
Out+
Trib.
15
18
36
Out
Trib.
15
Out+
Trib.
16
19
37
Out
Trib.
16
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

81 / 592
pin 1
Description
Pin #
Pin #
Description
Not Used
20
Not Used
IN+
Trib.
17
21
IN
Trib.
17
IN+
Trib.
18
22
IN
Trib.
18
IN+
Trib.
19
23
IN
Trib.
19
IN+
Trib.
20
24
IN
Trib.
20
IN+
Trib.
21
25
IN
Trib.
21
IN+
Trib.
22
26
IN
Trib.
22
IN+
Trib.
23
27
IN
Trib.
23
IN+
Trib.
24
28
IN
Trib.
24
GND
10
Not Used
11
29
Not Used
Out+
Trib.
17
12
30
Out
Trib.
17
Out+
Trib.
18
13
31
Out
Trib.
18
Out+
Trib.
19
14
32
Out
Trib.
19
Out+
Trib.
20
15
33
Out
Trib.
20
Out+
Trib.
21
16
34
Out
Trib.
21
Out+
Trib.
22
17
35
Out
Trib.
22
Out+
Trib.
23
18
36
Out
Trib.
23
Out+
Trib.
24
19
37
Out
Trib.
24
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
82 / 592
USER MANUAL
SYSTEM DESCRIPTION



pin 1
Description
Pin #
Pin #
Description
Not Used
20
Not Used
IN+
Trib.
25
21
IN
Trib.
25
IN+
Trib.
26
22
IN
Trib.
26
IN+
Trib.
27
23
IN
Trib.
27
IN+
Trib.
28
24
IN
Trib.
28
IN+
Trib.
29
25
IN
Trib.
29
IN+
Trib.
30
26
IN
Trib.
30
IN+
Trib.
31
27
IN
Trib.
31
IN+
Trib.
32
28
IN
Trib.
32
GND
10
Not Used
11
29
Not Used
Out+
Trib.
25
12
30
Out
Trib.
25
Out+
Trib.
26
13
31
Out
Trib.
26
Out+
Trib.
27
14
32
Out
Trib.
27
Out+
Trib.
28
15
33
Out
Trib.
28
Out+
Trib.
29
16
34
Out
Trib.
29
Out+
Trib.
30
17
35
Out
Trib.
30
Out+
Trib.
31
18
36
Out
Trib.
31
Out+
Trib.
32
19
37
Out
Trib.
32
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

83 / 592
Line Side
Equipment Side
Fig. 26. Services Protection box: views of Equipment Side and Line Side connectors
Tab. 18. Equipment Side and Line Side connectors of Services Protection box
Ref.
Fig. 25.
Connector
Interface
To be connected to
(1)
Alarms +
Housekeeping
station DDF for Alarms + Housekeeping;

(2)
NMS V.11 +
Audio 1
station DDF for NMS V.11 + Audio 1;

(3)
NMS G.703 +
Audio 2
station DDF for NMS G.703 + Audio 2;

(3)
User Service
Channels
station DDF for User Service Channels;

Audio1/2 +
G703_V11 User
Service Channel

[ (6) in Fig. 23. on page 77 ]
Audio1/2 +
G703_V11 User
Service Channel

[ (6) in Fig. 21. on page 70 ]
Alarms
Housekeeping
NMS

[ (15) in Fig. 21. on page 70 ]
Line side
SubD 15 Female
Equipment side
(5)
(6)
(7)
N.B.
SubD 44 Female
N.B.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
84 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.6 Description of Services Protection box

13.6.1 Alarms Housekeeping (pinout and description)

The AlarmsHousekeeping SubD15 connector (pinout in following Tab. 19. ) 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 86
6 housekeeping alarms equipment inputs (HK_I1 to HK_I6; see point [4] on page 87
1 common wire (COM)
1 ground (GND).
N.B.
the SW User Label depicted in Tab. 19. below represents the name by which each signal is
identified by the External Points Management (see chapter 27 on page 247), and Quick
Configuration Procedure External Input and Output Points configuration on page 367.
Tab. 19. Alarms Housekeeping connector pinout
pin 1
[1]
Pin
Signal
Direction
SW User Label
HK_I1
INPUT
CPI1
13
HK_I2
INPUT
CPI2
HK_I3
INPUT
CPI3
14
HK_I4
INPUT
CPI4
HK_I5
INPUT
CPI5
15
HK_I6
INPUT
CPI6
HK_O1
OUTPUT
CPO1
11
HK_O2
OUTPUT
CPO2
HK_O3
OUTPUT
CPO3
12
HK_O4
OUTPUT
CPO4
COM
A_1
OUTPUT
FAIL IDU
A_2
OUTPUT
FAIL ODU CH#1
A_3
OUTPUT
FAIL ODU CH#0
10
GND
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
IDUODU 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 86.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

85 / 592
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 IDUODU
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. 27. 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 hasnt
yet initialized the HW), all the relays of the outputs of the alarms/housekeeping are in the open state
(HW default condition).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
86 / 592
USER MANUAL
SYSTEM DESCRIPTION

[2]

[4]
EQUIPMENT INPUTS
The IDU is able to detect the status of commands coming from customers circuits.
A common (in) signal is supplied by the customers 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
customer
in n
ooo
I3
ooo
out
in 1
V4
V3
common (in)
customer
ground
Fig. 28. Equipment inputs relay scheme
alarm present the customer relay is closed: 2V V3 0V, |I3| 10mA

This means that the customers 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 customers circuit is 0.2mA.
Case 2 (open collector)
IDU
customer
in n
ooo
I3
ooo
V4
in 1
V3
common (in)
customer
ground
Fig. 29. Equipment inputs open collector scheme

The IDU supplies a suitable negative voltage to the customers circuit:
alarm present the customer transistor conduces (= closed): 2V V4 0V, |I3| 10mA.
alarm not present the customer transistor doesnt conduce (=open): |I3| 0.2mA.
This limits the max current that the customers circuit can drain.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

87 / 592
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.
Expected/transmitted Clock falling edge is in the middle of the data.

Audio1 outputs can be squelched by CT/OS selection.
Tab. 20. NMSV.11 + Audio 1 connector pinout
pin 1
Description
Pin #
Pin #
Description
RS422 data in (+)
RS422 data in ()
RS422 clock in (+)
10
RS422 clock in ()
RS422 data out (+)
11
RS422 data out ()
RS422 clock out (+)
12
RS422 clock out ()
GND NMS
13
Audio1 signal from user ()
Audio1 signal from user (+)
14
Audio1 signal to user ()
Audio1 signal to user (+)
15
Not used
GND Audio
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
88 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.6.2 NMS V.11 Audio 1 (pinout and description)

13.6.3 NMS G.703 Audio 2 (pinout 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),
Inframe: this configuration both disables the NMS_G703 interface and enables the
insertion/extraction into/from the first E1 of the 64Kbit/s channel comingfrom/towards the uP.
The insertion/extraction is relative to any slot of the first tributary.
This setting is not applicable with unframed E1.
Moreover, it is also necessary that the farend E1 is enabled and successfully provisioned.
Audio2 outputs can be squelched by CT/OS selection.

Tab. 21. NMSG.703 + Audio 2 connector pinout
pin 1
Description
Pin #
Pin #
Description
G703 data in (+)
G703 data in ()
Not used
10
Not used
G703 data out (+)
11
G703 data out ()
Not used
12
Not used
GND NMS
13
Audio2 signal from user ()
Audio2 signal from user (+)
14
Audio2 signal to user ()
Audio2 signal to user (+)
15
Not used
GND Audio
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

89 / 592
User service channel can be used in one of the following modes (selectable by CT/OS):
64Kb/s V11 codirectional (data+clock);

64Kb/s codirectional G.703 asynchronous (i.e. TX and RX data are not necessarily synchronous.
This mode includes DCE behavior);
64Kb/s V11 contradirectional (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. 22. User service channel connector pinout
pin 1
N.B.
Pin #
Signal
Direction
COD_RX +
INPUT
COD_RX
INPUT
COD_TX +
OUTPUT
10
COD_TX
OUTPUT
RX_ASY
INPUT
11
TX_ASY
OUTPUT
CC_RX +
INPUT
12
CC_RX
INPUT
RX_CK +
BID
13
RX_CK
BID
CC_TX +
OUTPUT
14
CC_TX
OUTPUT
CC_TCK +
OUTPUT
15
CC_TCK
OUTPUT
GND
The use of signals is depicted in following figures Fig. 30. to Fig. 33.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
90 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.6.4 User service channels (pinout and description)

For V11 codirectional mode, refer to Fig. 30. for the interface description vs pinout.
USER SERVICE CHANNEL V11 CODIR
< USER
RADIO >
IDU AWY
USER EQUIPMENT
DATA
CC_RX +
CC_RX
CLOCK
RX_CK +
RX_CK
CC_TX +
CC_TX
DATA
CC_TCK +
CC_TCK
CLOCK
Fig. 30. User service channel: V11 codirectional interface

For V11 contradirectional DCE mode, refer to Fig. 31. for the interface description vs pinout. Note that
V11 contradirectional DTE mode (as the userequipment interface) is not supported.
USER SERVICE CHANNEL V11 CONTRADIR DCE
< USER
RADIO >
IDU AWY
USER SUBORDINATE
EQUIPMENT (DTE)
DCE
DATA
CC_RX +
CC_RX
CLOCK
RX_CK +
RX_CK
CC_TX +
CC_TX
CC_TCK +
CC_TCK
DATA
CLOCK
Fig. 31. User service channel: V11 contradirectional interface
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

91 / 592
USER SERVICE CHANNEL G.703

< USER
RADIO >
IDU AWY
USER EQUIPMENT
COD_RX+
COD_RX
DATA&CLOCK
COD_TX+
COD_TX
DATA&CLOCK
Fig. 32. User service channel: G.703 interface

For V24/V28 mode, refer to Fig. 33. for the interface description vs pinout.
USER SERVICE CHANNEL V28
< USER
RADIO >
USER EQUIPMENT
DATA&CLOCK
IDU AWY
RX_ASY
TX_ASY
DATA&CLOCK
Fig. 33. User service channel: V24/V28 interface
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
92 / 592
USER MANUAL
SYSTEM DESCRIPTION

For G.703 mode, refer to Fig. 32. for the interface description vs pinout.

13.7 Provisioning and identification of Flash Cards & Software Labels

13.7.1 Provisioning of Flash Cards & Software Labels
A Software Label (stored on the Flash Card plugged in the IDU Main board) allows flexibility in choosing
user interfaces and modulation as in the following Tab. 23. :
Tab. 23. Flash Cards provisioning and associated & Software Labels
Supported configuration
Logistical Item, Description & Software Label
3DB16079ABXX :
Int.N# & type
Modulation
2E1, 4E1
4QAM
2E1
4QAM
4E1
4QAM or 16QAM
2E1, 4E1, 8E1
4QAM
2E1
4QAM
4E1, 8E1
4QAM or 16QAM
2E1, 4E1, 8E1,

16E1
4QAM
2E1
4QAM
4E1, 8E1, 16E1
4QAM or 16QAM
2E1
4QAM
4E1, 8E1, 16E1
4QAM or 16QAM
32E1
16QAM
8Mb 4 QAM FLASH CARD
Software Label: 8Mb 4 QAM
3DB16080ABXX :
8Mb 4/16 QAM FLASH CARD
Software Label: 8Mb 4/16 QAM

3DB16081ABXX :
3DB16082ABXX :

3DB16083ABXX :
3DB16084ABXX :
3DB16085ABXX :
The limitations introduced by the Software Label 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 Label value and NE
Configuration type are independent.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

93 / 592
13.7.2.1 General
The Flash Card is housed inside the IDU Main Unit shelf [see position (17) in Fig. 21. on page 70 ].
Fig. 34. herebelow shows the FLASH CARD profile and insertion direction
CONNECTOR SIDE
INSERTION
BOTTOM SIDE
Fig. 34. FLASH CARD profile and insertion direction

ATTENTION
Whenever you have to handle flash card(s), wear always the Antistatic protection device kit (see
Fig. 1. on page 36) 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. 21. on page 70, a suitable metal cover, fixed to the IDU Main Unit shelf
by three screws, is envisaged to ensure equipment EMIEMC performance and to avoid item detachment:
13.7.2.2 Flash Card identification

The Logistical Items for the possible Flash Card types are specified in Tab. 23. on page 93 , which
indicates, for each P/N, also its Software Label . Flash Card labelling is described in Fig. 35. on page
95:
a)
the Flash Card Logistical Item and Software Label are reported on the label affixed on it;
b)
moreover, the Software Label is affixed on the label present on the front panel of the IDU Main Unit
(position (A) in Fig. 21. on page 70):
flash card Software Label
For this purpose, the Flash Card plastic bag contains another selfadhesive label, equal to that
affixed on the Flash Card itself, that can be cut as shown below, to obtain the label to be affixed on
the front panel of the IDU Main Unit
flash card Software Label
c)
moreover, the Software Label can be verified by Operators Commands: see Fig. 159. on page 256
and Fig. 72. on page 166
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
94 / 592
USER MANUAL
SYSTEM DESCRIPTION

13.7.2 Description of Flash Cards & Software Labels

LABEL AFFIXED ON THE PLASTIC BAG

FOR FLASH CARD SHIPMENT
A
B
C
D
LABEL AFFIXED ON
THE FLASH CARD
E
H
A
F
G
H
FIELD
A
WRITING (EXAMPLES)
3DB16084ABXX
Logistical item for Customer
B
C
MEANING
N.B.
n.b.1
Logistical item for Customer, bar code 39

BS0731UW055
Factory serial number
Factory serial number, bar code 39
32Mb 4/16 QAM
Software Label
3DB16084ABAA 01
V2.1.0/V2.1.1
Software versions loaded in the Flash

Card banks by AlcatelLucent factory
n.b.1
n.b.2
Data matrix (for AlcatelLucent internal

purpose)
H
n.b.1
according to Tab. 23. on page 93
n.b.2
see point [2] on page 56 , and point [2] on page 63

Fig. 35. Flash Card identification labels
13.7.2.3 Flash Card upgrade

To replace a Flash Card with a different type, for system upgrade purpose, please refer to para.47.3
Flash Card upgrade on page 479.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

95 / 592
Tab. 24. Equipment accessories

Ref.[x] is used in other parts of this handbook to refer to the item
Ref.
Logistical Item
Technical Description
[1]
3CC07946AAXX
Telephone Handset
[2]
3DB01398AAXX
Maintenance Tool Kit
[3]
3DB01397AAXX
Installation Kit Tool
[4]
3DB01399AAXX
Station Kit Tool
See chapter 42 on page 413
See para.43.2.2 on page 416
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
96 / 592
N.B.
a
b
USER MANUAL
SYSTEM DESCRIPTION

13.8 Provisioning and description of equipment accessories

14 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 c ) on page 46
ODU mechanical design and identification
on page 98
Labels affixed on the ODU
on page 99
ODU configurations
on page 100
ODU provisioning and layouts
on page 101
ODU part lists and characteristics
on page 104
Part lists of ODUs with external diplexer
on page 105
Part lists of ODUs with embedded diplexer
on page 108
Antenna configurations
on page 113
ODU operative information
on page 119
For the Light service kit cable, please refer to para.32.10 on page 405.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

97 / 592
The ODU consists of one or two cabinets including the modem + transceiver + branching of a channel.
Two mechanical solutions are adopted:
one with external diplexer, where the branching (diplexer) is internal to the ODU cabinet; each of this
type of ODU is identified by one Logistical Item only
another with embedded diplexer, 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 Logistical Items, 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. 25. ODU dimensions and weights

embedded diplexer
Type with ..
Dimensions
Weight
external diplexer
TRANSCEIVER
+ BRANCHING
TRANSCEIVER
BRANCHING
TRANSCEIVER
+ BRANCHING
235 x 235 x 72 mm
(9.25 x 9.25 x 2.8in)
248 x 257 x 93 mm
(9.76 x 10.1 x 3.7in)
235 x 235 x 73.5 mm

(9.25 x 9.25 x 2.9in)
248 x 257 x 156.5 mm

(9.76 x 10.1 x 6.6in)
3.9 kg (8.58 lb)
4.2 kg (9.24 lb)
3.2 kg (7.04 lb)
7.4 kg (16.28 lb)
WITH EMBEDDED DIPLEXER
WITH EXTERNAL DIPLEXER
BRANCHING
BRANCHING
IDENTIFICATION LABEL
(INSIDE)
(see Fig. 52. on page 126)
TRANSCEIVER
+
BRANCHING
ODU IDENTIFICATION LABEL
TRANSCEIVER
TRANSCEIVER
IDENTIFICATION LABEL
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.14.6.4 on page 117)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
98 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.1 ODU mechanical design and identification

14.2 Labels affixed on the ODU

a)
the following label is affixed externally to all types of ODU and ODUs TRANSCEIVER boxes (see
Fig. 46. on page 120 and Fig. 47. on page 121):
A
B
this label is just an example

SYMBOL OR WRITING
MEANING
A9400
Equipment Acronym & Alcatel or AlcatelLucent Logo
CE

55
1.5A
Power supply (Feeding to Continuous Current)
Logistical Item (shown numbers as examples) Logistical Item for Customer

A
Logistical Item for Customer, bar code 128
Serial no (shown numbers as examples)
Factory Serial number
Factory Serial number bar code 128
TX Frequency MHz (shown numbers as

Working frequency range
examples)
Shifter MHz (shown numbers as examples)
Shifter
TX Subband (shown numbers as examples)
TX Subband
Initial SW/ICS (shown numbers as examples)
P/N and ICS of the software loaded in factory
PN/ICS (shown numbers as examples)
Factory P/N + ICS
Factory P/N + ICS bar code 128

Fig. 37. Label affixed on the ODU and ODUs TRANSCEIVER box
b)
only for ODUs with external diplexers, an additional label is placed on the branching assembly (for
details refer to Fig. 50. and Fig. 52. on pages 124126).
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

99 / 592
The available outdoor configurations are listed in Tab. 26. herebelow:

Tab. 26. ODU configurations
Outdoor
configuration
1+0
ODU
ODU coupler
1 x ODU
APPLICATIONS AND
ADVANTAGES
ANTENNA
NO
1 x antenna single polar
Nonprotected
1/10 dB
asymmetric
1 x antenna single polar
Protection against
failures
2 x ODUs at
1+1 HSB SD same
frequency
NO
2 x antennas single polar
1+1 FD AP
2 x ODUs at
different
frequencies
NO
1 x antenna double polar
1+1 FD DA
2 x ODUs at
different
frequencies
NO
2 x antennas single polar

in AP configuration (same
or crossed polarization)
1+1 HSB
N.B.
2 x ODUs at
same
frequency
Protection against
failures.
Improvement of
performances
versus multipath
propagation
For explanatory diagrams, refer to para.12.3 on page 50 System configurations.
Legend:
AP:
DA:
FD:
HSB:
SD:
Alternate Polar
Double Antenna
Frequency diversity
Hot Stand By
Space Diversity
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
100 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.3 ODU configurations

14.4 ODU provisioning and layouts

14.4.1 Provisioning of ODU (1+0)
a)
ODU transceiver: see para.14.5 on page 104
b)
Antenna: see paragraphs:
c)
14.6.1 on page 114 (1+0 configuration with full integrated antenna)

or
14.6.4 on page 117 (Configuration with separated antenna)
Part list of full integrated antennas, ODU accessories and installation materials: refer to
14.4.2 Provisioning, layouts and connections of ODU (1+1)

14.4.2.1 ODU (1+1) HSBSD or FDDA AP with two antennas
Antenna (1)
Antenna (2)
ODU CH 1
ODU CH 0
N.B.
to IDU MAIN UNIT
Figure shows the solution with full integrated antennas; antennas can be also external (see
point b ) herebelow)
Fig. 38. Station layout of ODU (1+1) HSBSD or FDDA AP with two antennas
Equipment provisioning:
a)
ODU transceiver (x2): see para.14.5 on page 104
b)
Antenna (x2): see paragraphs:
c)
14.6.1 on page 114 (1+0 configuration with full integrated antenna)

or
14.6.4 on page 117 (Configuration with separated antenna)
Part list of full integrated antennas, ODU accessories and installation materials (x2): refer to
ODU Equipment block diagram: see:
Fig. 11. on page 52 (1+1 HSBSD)
Fig. 13. on page 53 (1+1 FDDA AP)
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

101 / 592
COUPLER
ANTENNA
ODU CH 0
ODU CH 1
to IDU MAIN UNIT

N.B.
this drawing is an example referred to the coupler used in 1338 GHz configurations.
Couplers used in 78 GHz configurations are shown in Fig. 44. on page 117.
Fig. 39. Station layout of ODU (1+1) HSB with one antenna
a)
ODU transceiver (x2): see para.14.5.2 on page 108
b)
Antenna and coupler: see paragraphs:
c)
14.6.2 on page 116

[1+1 HSB configuration with coupler and full integrated antenna (1338 GHz)]
14.6.3 on page 117

[1+1 HSB configuration with coupler and full integrated antenna (78 GHz)]
Part list of full integrated antennas, ODU accessories and installation materials: refer to
ODU Equipment block diagram: see:
Fig. 12. on page 52 (1+1 HSB)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
102 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.4.2.2 ODU (1+1) HSB or with one antenna

14.4.2.3 ODU (1+1) FDAP with one double polar external antenna
Double Polar Antenna
ODU CH 0
ODU CH 1
to IDU MAIN UNIT
Fig. 40. Station layout of ODU (1+1) FDAP with one double polar external antenna
a)
ODU transceiver (x2): see para.14.5 on page 104
b)
Connection of Double Polar External Antenna: see para.14.6.4 on page 117 (Configuration
with separated antenna)
c)
Part list of ODU accessories and installation materials: refer to the Installation Handbook
ODU Equipment block diagram: see Fig. 14. on page 53
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

103 / 592
Notes for all tables:

ODU Type
Hardware implementation can be:
with external diplexer
with embedded diplexer

Capacity can be:
64Mb = 32E1 capacity ODU
Logistical Item
Corresponds to the Logistical Item code you can read on the ODUs
label (see Fig. 37. on page 99 )
(if any) Technical Description of the item.
Note: The ODU Logistical Items listed in the following tables include always the solar shield.
For:
ODUs with external diplexer, refer to para.14.5.1 on page 105
ODUs with embedded diplexer, refer to para.14.5.2 on page 108
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
104 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.5 ODU part lists and characteristics

14.5.1 Part lists of ODUs with external diplexer

14.5.1.1 General
The diplexer included in the available BRANCHING assemblies refers to ITUR F.385, 386 and RF special
CUSTOMERS channelling with Tx/Rx separation specified in following Tab. 28. and Tab. 30.
Each diplexer is a three port passive device with two bandpass filters as described hereafter (physical
arrangement is shown in Fig. 50. on page 124):
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 AAXX
1_1p
3DB xxxxx ABXX
2_2p
The arrangement between each filters on the same branching device is described below:
f1
foL
f2
f3
foH
f4
frequencies
2.5 dB
70 dB
attenuation
WARNING:
fr SHIFTER
f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channel
frequencies and not to the cutoff frequencies of the filters.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

105 / 592
Tab. 27. 7 GHz Transceiver assemblies

ODU Type
ODU 64Mb
Logistical Item
3DB 06691ABXX
ODU 64MB 9470 7.1 7.75 GHz LHB
3DB 06692ABXX
ODU 64MB 9470 7.25 7.9 GHz UHB
Tab. 28. Branching assemblies for 7 GHz ODU

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

USER MANUAL
SYSTEM DESCRIPTION

14.5.1.2 Part list of 7 GHz ODUs with external diplexer

14.5.1.3 Part list of 8 GHz ODUs with external diplexer

Tab. 29. 8 GHz Transceiver assemblies
ODU Type
ODU 64Mb
Logistical Item
3DB 06693ABXX
ODU 64MB 9470 7.7 8.4 GHz LHB
3DB 06694ABXX
ODU 64MB 9470 8.0 8.5 GHz UHB
Tab. 30. Branching assemblies for 8 GHz ODU

N.B.
Shifter
MHz
119
Central
Freq.
MHz
8366.5
Filter 1 MHz
(Lower Band)
Filter 2 MHz
(Upper Band)
Low
Limit
f1
High
Limit
f2
Low
Limit
f3
High
Limit
f4
8286.0
8328.0
8405.0
8447.0
BRANCHING ASSEMBLY
Logistical Item
BRANCHING 8GHZ ...
3DB 06789 AAXX

126
8366.5
8282.5
8324.5
8408.5
8450.5
119
8408.5
8328.0
8370.0
8447.0
8489.0

3DB 06789ABXX
126
8408.5
8324.5
8366.5
8450.5
8492.5
151.610
8315.010
8204.217
8274.189
8355.831
8425.803
3DB 06787 AAXX
151.610
8384.982
8274.189
8344.161
8425.803
8495.775
3DB 06787ABXX
208
8217.0
8064.0
8162.0
8272.0
8370.0
3DB 10073 AAXX
208
8301.0
8148.0
8246.0
8356.0
8454.0
3DB 10073ABXX
266
8097.5
7905.0
8024.0
8171.0
8290.0
3DB 06788 AAXX
266
8209.5
8017.0
8136.0
8283.0
8402.0
3DB 06788ABXX
3DB 06786 AAXX
... CH11P
P.SH.294/305/311 MHZ
3DB 06786ABXX
... CH22P
P.SH.294/305/311 MHZ
3DB 10103 AAXX
... CH11P P.SH. 213.5 MHZ
294.440
305.560
7749.755
7947.835
311.320
311.320
7738.635
8145.915
7851.475
294.440
7851.475
7862.965
305.560
8162.795
8281.395
8264.515
7970.075
8157.405
7851.845
8147.0
8157.035
8162.795
8063.740
213.5
8044.195
7732.875
8066.435
8035.0
USER MANUAL
SYSTEM DESCRIPTION
8275.635
8046.0
8248.0
8259.0
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

107 / 592
The following tables report the Logistical Items of the available ODUs (with embedded diplexer) with the
following information from left to right:
Column 1:
Column 1bis :
Column 2 & 3:
Column 4 to 7:
Shifter (MHz)
Central Frequency (MHz)
Tx and Rx subbands
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
14.5.2.1 Part list of 13 GHz ODU with embedded diplexer

Tab. 31. 13 GHz ODU (FIXEDSHIFTER)
RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
12807.5
1p
12750
12865
13016
13131
3CC13688ABXX
12920.5
2p
12861
12980
13127
13246
3CC13689ABXX
13073.5
1p
13016
13131
12750
12865
3CC13690ABXX
13186.5
2p
13127
13246
12861
12980
3CC13691ABXX
Logistical Item
266
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
108 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.5.2 Part lists of ODUs with embedded diplexer


RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
14698
1p
14630
14766
14945
15081
3CC13692ABXX
14829,5
2p
14760
14899
15075
15214
3CC13693ABXX
15013
1p
14945
15081
14630
14766
3CC13694ABXX
15144,5
2p
15075
15214
14760
14899
3CC13695ABXX
14612
1p
14500
14724
14920
15144
3CC13696ABXX
14825,5
2p
14710
14941
15130
15361
3CC13697ABXX
15032
1p
14920
15144
14500
14724
3CC13698ABXX
15245,5
2p
15130
15361
14710
14941
3CC13699ABXX
14517,5
1p
14400
14635
14890
15125
3CC13704ABXX
14742,5
2p
14625
14860
15115
15350
3CC13705ABXX
15007,5
1p
14890
15125
14400
14635
3CC13706ABXX
15232,5
2p
15115
15350
14625
14860
3CC13707ABXX
14600
1p
14500
14700
15144
15344
3CC13709ABXX
15244
1p
15144
15344
14500
14700
3CC13711ABXX
14560
1p
14500
14620
15228
15348
3CC13712ABXX
15288
1p
15228
15348
14500
14620
3CC13713ABXX
Logistical Item
315
420
490
644
728
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

109 / 592

RF interface (MHz)
1
Shifter
1bis
RF Tx
max
RF Rx
min
RF Rx
max
Logistical Item
CF
Tx
Rx
RF Tx
min
18640,5
1p
18581
18700
18921
19040
3CC13714ABXX
18760,5
2p
18701
18820
19041
19160
3CC13715ABXX
18980
1p
18920
19040
18580
18700
3CC13716ABXX
19100
2p
19040
19160
18700
18820
3CC13717ABXX
17920
1p
17700
18140
19260
19700
3CC12995ABXX
19480
1p
19260
19700
17700
18140
3CC12996ABXX
340
1560
ETSI
Tab. 34. 18 GHz ODU (VARIABLESHIFTER)

N.B.

RF interface (MHz)
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
1008
17951,5
17703
18200
18711
19208
1p
17700
18201
18710
19211
18182
18679
19190
19687
18180
18690
19190
19700
18711
19208
17703
18200
18710
19211
17700
18201
19190
19687
18182
18679
19190
19700
18180
18690
1010
17950,5
1008
18430,5
2
1010
18435
1008
18959,5
1p
1010
18960,5
1008
19438,5
2p
1010
19445
3CC14780ABXX
2p
3CC14781ABXX
3CC14782ABXX
3CC14783ABXX
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
110 / 592
Logistical Item
USER MANUAL
SYSTEM DESCRIPTION

14.5.2.3 Part lists of 18 GHz ODU with embedded diplexer

14.5.2.4 Part lists of 23 GHz ODU with embedded diplexer

RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
22157,5
1p
22000
22315
23008
23323
3CC13718ABXX
22450
2p
22300
22600
23308
23608
3CC13719ABXX
23165,5
1p
23008
23323
22000
22315
3CC13720ABXX
23458
2p
23308
23608
22300
22600
3CC13721ABXX
Logistical Item
1008
Tab. 36. 23 GHz ODU (VARIABLESHIFTER)

N.B.

RF interface (MHz)
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
1200
21509,5
21200
21819
22400
23019
1p
3CC14776ABXX
1232
21492,5
21198
21787
22430
23019
1050
22306
22252
22360
23302
23410
1200
22090,5
21781
22400
22981
23600
1232
22074,5
21781
22368
23013
23600
1200
22709,5
22400
23019
21200
21819
1p
2p
22724,5
22400
23019
21200
21819
1050
23356
23302
23410
22252
22360
1200
23290,5
22981
23600
21781
22400
1232
23306,5
23013
23600
21781
22368
USER MANUAL
SYSTEM DESCRIPTION
3CC14777ABXX
3CC14778ABXX
1232
2p
Logistical Item
3CC14779ABXX
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

111 / 592

RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
24768,5
1p
24540
24997
25548
26005
3CC13734ABXX
25221
2p
24994
25448
26002
26456
3CC13735ABXX
25776,5
1p
25548
26005
24540
24997
3CC13736ABXX
26229
2p
26002
26456
24994
25448
3CC13737ABXX
Logistical Item
1008

RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
27767
1p
27540
27994
28548
29002
3CC13738ABXX
28221
2p
27994
28448
29002
29456
3CC13739ABXX
28775
1p
28548
29002
27540
27994
3CC13740ABXX
29229
2p
29002
29456
27994
28448
3CC13741ABXX
Logistical Item
1008

RF interface (MHz)
1
1bis
Shifter
CF
Tx
Rx
RF Tx
min
RF Tx
max
RF Rx
min
RF Rx
max
37335
1p
37050
37620
38310
38880
3CC12987ABXX
37899,5
2p
37619
38180
38879
39440
3CC12988ABXX
38595
1p
38310
38880
37050
37620
3CC12989ABXX
39159,5
2p
38879
39440
37619
38180
3CC12990ABXX
Logistical Item
1260
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
112 / 592
USER MANUAL
SYSTEM DESCRIPTION


14.6 Antenna configurations

The ODU can be connected to:
a full integrated antenna of 30 cm (1FT) or 60 cm (2FT) or 90 cm (3FT) or 120 cm (4FT) or 180 cm

(6FT) diameter, in Full Integrated configuration (pole mounting is delivered with the antenna).
N.B.
For the list of full integrated antennas (types, P/Ns and related information), please refer
to the Installation Handbook.
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 standby path.
without coupler and 1 dual polarization antenna: this configuration allows a polarization
diversity, minimizes the antenna and avoids coupler losses on the standby path.
The pole mounting versions are given in the following Tab. 40. for each configuration:
Tab. 40. Pole Mounting versions
Version
see para
1+0 with full integrated antenna
14.6.1 page 114
1+1 HSB configuration with coupler and full integrated antenna (1338 GHz)
14.6.2 page 116
1+1 HSB configuration with coupler and full integrated antenna (78 GHz)
14.6.3 page 117
Configuration with separated antenna
14.6.4 page 117
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

113 / 592
The following Fig. 41. and Fig. 42. 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.
antenna
N connector
for IDUODU cable

antenna
360 mm
(14.17 in)
390 mm
(15.35 in)
N connector
for IDUODU cable
WARNING:
in some ODU mechanical arrangements, the N connector (for IDUODU cable insertion)
can be in the opposite position with respect to that depicted in figure above. In any case,
this N connector is always positioned on the 450 side of ODU assembly.
Fig. 41. View of ODU with full integrated antenna (V polarization)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
114 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.6.1 1+0 configuration with full integrated antenna

antenna
N connector
for IDUODU cable

antenna
measures as Fig. 41.

WARNING:
N connector
for IDUODU cable
Fig. 42. View of ODU with full integrated antenna (H polarization)
Please refer to the Installation Handbook, for the P/N of full integrated antenna pole mounting, and
for detailed assembly drawings.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

115 / 592
See Fig. 43. 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. 41. herebelow:
Tab. 41. Available couplers (1338 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.
Frequency band
Coupler type
Waveguide
(3 ports)
Coupling loss
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
antenna
Coupler
360 mm
(14.17 in)
535 mm
(21.83 in)
620 mm
(24.41 in)
COUPLER VIEW
COUPLER WEIGHT = 4.3 Kg about

Fig. 43. Coupler (1338 GHz)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
116 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.6.2 1+1 HSB configuration with coupler and full integrated antenna (1338 GHz)

14.6.3 1+1 HSB configuration with coupler and full integrated antenna (78 GHz)
Tab. 42. Available couplers (78 GHz)
N.B.
For coupler P/N and assembly drawings of ODUs + coupler, please refer to the Installation
Handbook
Frequency band
Coupler type
Waveguide (3 ports)
Coupling loss
78 GHz
10 dB
WR 112
1 dB / 10 dB
521
235
max 126
COUPLER WEIGHT = 6 Kg about

Fig. 44. Coupler (78 GHz) example
14.6.4 Configuration with separated antenna
The ODU is fixed on a dedicated pole mounting for separated antenna. A nose adapter (different Logistical
Items depending on the waveguide dimension) is used to connect the ODU and the flextwist.
(under)
NOSE
ADAPTER
NOT INTEGRATED
ANTENNA
POLE MOUNTING
Fig. 45. 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.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

117 / 592
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.
Tab. 43. ODU Output flanges with external antenna
N.B.
This list is given for general information purpose.

For flextwist P/Ns and possible additional and related information, please refer to the
Installation Handbook.
Equipment
and Range
(GHz)
ODU Output
Flange
A
UDR84
Suggested
Antenna
Flange
FLEXTWIST
C.E.I.
E.I.A.
R84
WR112
9470 AWY
78
B
PDR84
UBR84
PBR84
or:
UBR84
R84
WR112
PBR84
UBR84
PBR84
9413 AWY
12.7 13.3
UBR120
R120
WR75
PBR120
UBR120
PBR120
9415 AWY
14.2 15.4
UBR140
R140
WR62
PBR140
UBR140
PBR140
UBR220
R220
WR42
PBR220
UBR220
PBR220
UBR320
R320
WR28
PBR320
UBR320
PBR320
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 78 GHz

L=600 mm for 1338 GHz
N.B.
If the flextwist is not provided by AlcatelLucent, the user must carefully choose the type of
the connection guide in order to limit as much as possible galvanic couples between
antenna/flextwist and flextwist/ODU contact surfaces that can induce rust. For this purpose
please note that the surfaces are:
chromiumplated at ODUs output flange side
tinplated at flextwists flange side
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
118 / 592
USER MANUAL
SYSTEM DESCRIPTION

Concerning the interface between the ODU output flange and the suggested antenna flange, the following
Tab. 43. details for each product the standard wave guide to be used and the suggested flange for the
external antenna.

14.7 ODU operative information

This paragraph gives operative information, for installation, commissioning and maintenance purposes
regarding:
ODUs with embedded or external diplexer
herebelow
ODUs with external diplexer (additional information)
on page 123
For the Light service kit cable, please refer to para.32.10 on page 405.
14.7.1 Operative information on ODUs with embedded or external diplexer
14.7.1.1 General, views and access points
Fig. 46. (for ODUs with embedded diplexer) and Fig. 47. (for ODUs with external diplexer) on pages
120121 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
Fig. 46.
and Fig. 47.
Interface
Connector
Further
information
(1)
RF interface for connection of antenna or coupler
waveguide
Tab. 45.
herebelow
(2)
Connector for IDU/ODU cable
(3)
Connector for Light service kit cable
male N 50 ohm
12pin LEMO
(Fig. 48.
on page 122)
para.32.10
on page 405
Tab. 45. RF interface

FREQUENCY GHz
Waveguide type
N.B.
N.B.
78
1315
1825
2838
WR112
WR62
WR42
WR28
for further information, refer to para.14.6 on page 113
For detailed operative information regarding:
equipment installation, please refer to the Installation Handbook
equipment commissioning, please refer to chapter 32 on page 329
equipment maintenance, please refer to section 4 on page 407.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

119 / 592
TRANSCEIVER
+
BRANCHING
SOLAR SHIELD
(1)
(A)
(A)
(A)
(3)
(A)
(2)
(A) Levers (4) to fix/unfix ODU assembly to antenna or coupler

(1)
(2)
(3)
(4)
ODU identification label (see Fig. 37. on page 99)
WARNING:
Fig. 46. Views of ODUs with embedded diplexer
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
120 / 592
USER MANUAL
SYSTEM DESCRIPTION

(4)

BRANCHING
(4)
TRANSCEIVER
(B)
SOLAR SHIELD
(A)
(1)
(B)
(A)
(A)
(B)
(3)
(2)
(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)
(2)
(3)
(4)
TRANSCEIVER identification label (see Fig. 37. on page 99)
WARNING:
Fig. 47. Views of ODUs with external diplexer
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

121 / 592
12
11
10
3
KEY
Fig. 48. ODU LEMO connector pinout

14.7.2 ODU hardware settings
No hardware settings are envisaged on ODUs with embedded diplexer, while on ODUs with external
diplexer a setting allows to choose the halfband (LOW or HIGH) for TX (see para.14.7.4 on page 123
for details).
14.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 ODUs with external diplexer, the BRANCHING
identification label (Fig. 52. on page 126) can be viewed only separating the TRANSCEIVER from the
BRANCHING.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
122 / 592
USER MANUAL
SYSTEM DESCRIPTION


14.7.4 Additional operative information on ODUs with external diplexer

14.7.4.1 ODU composition
As shown in Fig. 49. 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 ORING present in the TRANSCEIVER box guarantees the ODU assembly pressurization.
N.B.
This is a conductive ORING and must be left dry. Do not wet it with silicon grease (silicon
grease must be used only on Oring between ODU and antenna).
BRANCHING
TRANSCEIVER
ORING
Fig. 49. Composition of ODUs with external diplexer

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
121.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

123 / 592
Fig. 50. below shows the TRANSCEIVER and BRANCHING boxes coupling surfaces:
(A) BRANCHING box label informative content

described in Fig. 52. on page 126
(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 (1800rotated with
respect to each other):
BRANCHING boxs (B) (HIGH FREQ) coupled to TRANSCEIVER boxs (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. 52. on page 126); obviously the RX part of the transceiver uses the
corresponding LOW frequency range;
BRANCHING boxs (C) (LOW FREQ) coupled to TRANSCEIVER boxs (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. 52. on page 126); obviously the RX part of the transceiver uses the
corresponding HIGH frequency range.
(D)
BRANCHING
TRANSCEIVER
(A)
(B)
(C)
(E)
Fig. 50. ODUs TRANSCEIVER and BRANCHING boxes coupling surfaces
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
124 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.7.4.2 TRANSCEIVER and BRANCHING boxes coupling

N.B.
There is only one possible way to couple the BRANCHING box and the TRANSCEIVER box:
there is a mistakeproofing put by the factory on the TRANSCEIVER box, whose position
depends on the type of transceiver (low or high band, as shown in Fig. 51. below) to ensure that
the association with the BRANCHING box is always the right one. Notice that this feature was
not available at the very beginning of the 7/8 GHz introduction.
mistakeproofing
mistakeproofing
Fig. 51. 78 GHz ODUs BRANCHING box mistakeproofing
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

125 / 592
3DB 06775 AAAA 01
3DB 06775 AAXX
B
C
154_B
LOW
HIGH
160
LOW
HIGH
7442
7596
7442.5
7602.5
7526
7680
7512.5
7673.5
SYMBOL OR WRITING
A9400
MEANING
Equipment Acronym & Alcatel Logo
ALCATEL
CE
12345 (example)
Notified body
!

PN/ICS 3DB 06775 AAAA 01 (example)
Factory Technical Code + ICS, bar code 128
Logistical Item 3DB 06775 AAXX (example)
Logistical Item for Customer
Logistical Item for Customer, bar code 128
S/N CW 050609001 (example)
Factory Serial number
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 237 for
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.14.7.4.2 on page
124
D (shown numbers as examples)
Fig. 52. Label affixed inside the ODU BRANCHING box
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
126 / 592
USER MANUAL
SYSTEM DESCRIPTION

14.7.4.3 Label affixed inside the ODU BRANCHING box

15 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
78
9413AWY
13
9415AWY
15
9418AWY
18
9423AWY
23
9425AWY
25
9428AWY
28
9438AWY
38
This chapter is organized as follows:
General Characteristics
on page 128, including:
Reference system standards

on page 129
RF channeling
on page 129
Transmitted Power at antenna port

on page 130
99% power channel bandwidth and Emission Designator on page 131
ETSI System Characteristics

on page 132
Switching system
on page 134
Tributary interfaces
on page 135
Modem
on page 135
Maximum capacity and Modulation type
on page 135
IDUODU cable
on page 135
Manmachine interface
on page 136
Alarms
on page 136
Power supply
on page 136
Mechanical characteristics
on page 136
Environmental conditions
on page 137
Electromagnetic compatibility / safety
on page 137
Dismantling & Recycling
on page 138
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

127 / 592
Version
SPLIT MOUNT (IDU+ODU)
Station type
Terminal
Configuration
1+0 / 1+1 HSB / 1+1 FD
Reference standard
(system)
Transmission capacity
Refer to para. 15.1.1 page 129

ETSI: 2xE1, 4xE1, 8xE1, 16xE1, 32xE1
RF channel spacing
Tunability
Transmitted power
99% power channel

bandwidth and Emission
Designator
ATPC range
RTPC range
20 dB (Pmax / Pmax20 dB)
Tx level with Tx mute ON
ETSI mask compliance till Pmax :

20dB for 4QAM modulation
18dB for 16QAM modulation up to 32Mbps
15dB for 16QAM modulation at 64Mbps
< 30 dBm
$ 10 ppm
RF frequency stability
Synthesizer step
250 kHz
RF spectrum masks
Compliant with the relevant ETSI standards
Spurious
emissions
Compliant with the relevant ETSI standards

Compliant with ERC Rec. 7401
BER receiver threshold
Refer to para. 15.1.5 page 132 (ETSI)
System gain
Rx max input level
20 dBm (for a BER of 103)
Switching system
User service channels
SC #1 DATA CHANNEL
1x64 Kb/s data channel configurable alternatively as one of the

following modes:
G.703 asynchronous codirectional
V11 codirectional
V11 contradirectional
4.8/9.6 Kbps V11
4.8/9.6 Kbps V24/V28 asynchronous
1x64 Kbps V11 codirectional 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) + 4wire party line (2
ways)
NMS channels
NMSV.11: 1x64 kbit/s V.11 codirectional for TMN (port 1)

NMSG.703: 1x64 kbit/s G.703 codirectional for TMN (port 2)
NMSRF: 1x64 kbit/s radio channel for TMN (internal to the radio
frame)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
128 / 592
USER MANUAL
SYSTEM DESCRIPTION

15.1 General Characteristics

15.1.1 Reference system standards
Equipment
ETSI standard
Frequency
range
Channeling
(GHz)
Frequency
band
(GHz)
7
9470 AWY
4&16 QAM
9413 AWY 4QAM
9413 AWY16QAM
7.117.9
ITUR F.385
ITUR F.386
7.7259.5
13 GHz
12.7513.25
15 GHz
14.415.35
18 GHz
17.719.7
23 GHz
21.223.6
9415 AWY 4QAM

9415 AWY 16QAM
9418 AWY 4QAM
9418 AWY 16QAM
9423 AWY 4QAM
25 GHz
266
315
728
420, 490, 644
1008, 1010
340, 1560
1092.5
1008, 1050,
1200,1232
1200
ITUR Rec 637
24.526.5
9428 AWY 4QAM
ERC 1302
ITUR Rec. 748
1008
28 GHz
27.529.5
ERC 1302
ITUR Rec. 748
1008
38 GHz
3739.5
ERC 1201
ITUR Rec 749
1260
9428 AWY 16QAM

9438 AWY 4QAM
9438 AWY16QAM
ERC 1202
ITUR Rec 497
MEXICO
ERC 1207
ITUR Rec 636
ERC 1203
ITUR Rec 595
CHINA
ERC 1302 annex A
9423 AWY 16QAM

9425 AWY 4QAM
9425 AWY 16QAM
Standard Tx/Rx
separation
(MHz)
150, 154, 160, 161, 168,
182, 196, 245
119, 126, 151.614, 208,
266, 294.44, 305.56,
311.32
For all frequency bands, the ETSI reference standard is the harmonized standard EN 302 217. In this
stardard , 4QAM is class 2 and 16QAM is class 4.
15.1.2 RF channelling
ETSI RF CHANNELING
Capacity (Mbit/s)
2x2
4x2
8x2
16x2
32x2
RF Channeling with 4 QAM (MHz)
3.5
14
28
RF Channeling with 16 QAM (MHz)
3.5
14
28
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

129 / 592
Tolerance:
2.0 dB in temperature range 33C to +55C for 0 to 20dB RTPC range
Equipment
Output power
dBm
(Note 1)
9470 AWY 4QAM
25
9470 AWY 16QAM
21
9413 AWY 4QAM
24
9413 AWY 16QAM
20
9415 AWY 4QAM
24
9415 AWY16QAM
20
9418 AWY 4QAM
22
9418 AWY 16 QAM
19
9423 AWY 4QAM
19
9423 AWY 16QAM
16
9425 AWY 4QAM
17
9425 AWY 16QAM
14
9428 AWY 4QAM
16
9428 AWY 16QAM
13
9438 AWY 4QAM
16
9438 AWY 16QAM
13
Tx/Rx separation
MHz
For 7 GHz ODUs, refer to shifters in Tab. 28. on

page 106
For 8 GHz ODUs, refer to shifters in Tab. 30. on
page 107
Refer to shifters in Tab. 31. on page 108

Refer to shifters in:
Tab. 33. on page 110 (fixed shifters)
Tab. 34. on page 110 (variable shifters)

Refer to shifters in:
Tab. 35. on page 111 (fixed shifters)
Tab. 36. on page 111 (variable shifters)


Note 1: Output power at antenna port.
Output power setting (dBm):
ATPC/RTPC range with 1dB step
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
130 / 592
USER MANUAL
SYSTEM DESCRIPTION

15.1.3 Transmitted power at antenna port

15.1.4 99% power channel bandwidth and Emission Designator
99% Power Channel

Bandwidth [MHz]
ITUR/CEPT Rec.
Channel Bandwidth
[MHz]
Emission
Designator
9400 AWY 4QAM 2E1
2,8
3,5
3M5D7W
9400 AWY 4QAM 4E1
5,5
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
7M0D7W
9400 AWY 16QAM 16E1
10,9
14
14M0D7W
9400 AWY 16QAM 32E1
21,7
28
28M0D7W
Radio Type
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

131 / 592
Data is split into following Tab. 47. to Tab. 51. according to capacity.
Note for all tables: Transmitted PTX tolerance:
2dB @ ODU Operating temperature range 33C + 55C
Tab. 47. ETSI System Characteristics 32E1 (typical values)
32E1
Frequency
7/8 GHz
External
Diplexer
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
TX Output Power
@ Antenna Port
16
21
20
20
19
16
14
13
13
103 BER Threshold

@ Antenna Port
16
81
79
79
78
78
77
76
74
106 BER Threshold

@ Antenna Port
16
80
78
78
77
77
76
75
73
Net System Gain dB @

103 BER Threshold
16
102
99
99
97
94
91
89
87

106 BER Threshold
16
101
98
98
96
93
90
88
86
System Characteristics
QAM

16E1
Frequency
7/8 GHz
External
Diplexer
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
25
24
24
22
19
17
16
16
16
21
20
20
19
16
14
13
13
88
86
86
85
85
84
83
81
16
84
82
82
81
81
80
79
77
87
85
85
84
84
83
82
80
16
83
81
81
80
80
79
78
76
113
110
110
107
104
101
99
97
16
105
102
102
100
97
94
92
90
112
109
109
106
103
100
98
96
16
104
101
101
99
96
93
91
89
QAM
TX Output Power
@ Antenna Port
103 BER Threshold
@ Antenna Port
106 BER Threshold
@ Antenna Port
103 BER Thr
106 BER Thr
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
132 / 592
USER MANUAL
SYSTEM DESCRIPTION

15.1.5 ETSI System Characteristics


8E1
Frequency
7/8 GHz
External
Diplexer
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
25
24
24
22
19
17
16
16
16
21
20
20
19
16
14
13
13
91
89
89
88
88
87
86
84
16
87
85
85
84
84
83
82
80
90
88
88
87
87
86
85
83
16
86
84
84
83
83
82
81
79
116
113
113
110
107
104
102
100
16
108
105
105
103
100
97
95
93
115
112
112
109
106
103
101
99
16
107
104
104
102
99
96
94
92
QAM
TX Output Power
@ Antenna Port
103 BER Threshold
@ Antenna Port
106 BER Threshold
@ Antenna Port
Net System Gain dB
@ 103 BER Thr
Net System Gain dB
@ 106 BER Thr

4E1
Frequency
7/8 GHz
External
Diplexer
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
25
24
24
22
19
17
16
16
16
21
20
20
19
16
14
13
13
94
92
92
91
91
90
89
87
16
90
88
88
87
87
86
85
83
93
91
91
90
90
89
88
86
16
89
87
87
86
86
85
84
82
119
116
116
113
110
107
105
103
16
111
108
108
106
103
100
98
96
118
115
115
112
109
106
104
102
16
110
107
107
105
102
99
97
95
QAM
TX Output Power
@ Antenna Port
103 BER Threshold
@ Antenna Port
106 BER Threshold
@ Antenna Port
Net System Gain dB
@ 103 BER Thr
Net System Gain dB
@ 106 BER Thr
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

133 / 592
2E1
Frequency
7/8 GHz
External
Diplexer
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
TX Output Power
@Antenna Port
25
24
24
22
19
17
16
16
103 BER Threshold

@Antenna Port
97
95
95
94
94
93
92
90
106 BER Threshold

@Antenna Port
96
94
94
93
93
92
91
89
Net System Gain dB

@103 BER Thr
122
119
119
116
113
110
108
106
Net System Gain dB

@106 BER Thr
121
118
118
115
112
109
107
105
QAM
15.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
Tx EPS
Rx EPS
ODU switch
(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
Switch vs. Configuration
[2]
Configuration
Tx EPS
Rx EPS
ODU switch
1+1 FD
YES
YES
NO
1+1 HSB
YES
YES
YES
RPS (Radio Protection System)

RPS, hitlessswitch type, is equipped to provide protection against radio propagation problems.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
134 / 592
USER MANUAL
SYSTEM DESCRIPTION


15.2 Tributary interfaces

E1
Input / output
electrical interface
ITUT G.703
Code
HDB3
Impedance
75 unbal
120 bal
Jitter Generation
ITUT G.823
Jitter Tolerance
ITUT G.823
Jitter Transfer
ITUT G.736
ITUT G.742
15.3 Modem
Modulation
4/16 QAM
Demodulation
Coherent
Equalizer type
19tap FSE
Channel coding
Reed Solomon (255,239)
Spectrum shaping
Raised cosine
15.4 Maximum capacity and Modulation type

The employed Software Label (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. 23. on page 93.
15.5 IDUODU cable

Coax. connector
N (50 ohm)
Coax. cable type (single)
Coaxial single type, 50 W, dielectric foam and braid

(n.b.1)
Guaranteed cable maximum length
Depends on:
cable type employed
bit rate ( 16E1 or > 16E1)

(n.b.1)
Signals on the cable
DC Voltage/HDB3 Tx/HDB3 Rx (n.b.2)
Gross bit rate on the cable:
ETSI (2 to 16xE1)
ETSI (17 to 32xE1)
39.168 Mbit/s
78.336 Mbit/s
n.b.1
n.b.2
for details on cables that can be employed and relevant cable maximum length, refer to the
Installation handbook.
the HDB3 signal contains the main signal, auxiliary signal and IDUODU service channel.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

135 / 592
Visual (LEDs)
9 (on IDU Main unit) +3 (on IDU Extension unit)
Other
F interface for Personal Computer (WindowsTM) RS232C

TMN interface Ethernet 10/100 BaseT
TMN Data channel 64kbit/s interface RS422/G703
Interface for Telephone Service Channel
15.7 Alarms
Equipment alarms
3 outputs (IDU HW Failure alarm, ODU Main Failure alarm, ODU Spare
Failure alarm)
Housekeeping alarms
6 inputs / 4 outputs
15.8 Power supply

DC nominal voltage (primary)
$ 48 to $ 60 Vdc $20%
Polarity
+ or floating (isolated ground)
Max Power Consumption
1+0 : v 50W
1+1 : v 100W
15.9 Mechanical characteristics
1+0 IDU
Dimensions (H x W x D)
Weight
43 x 210 x 443 mm
1.7 x 8.3 x 17.4 in
1U
< 2.5 kg
< 5.5 lb
2U
< 5 kg
< 11 lb
86 x 210 x 443 mm
1+1 IDU
3.4 x 8.3 x 17.4 in
ODU
see Tab. 25. on page 98
Antenna
Integrated with max diameter depending on frequency (refer to the

Installation Handbook for details)
or:
Separated for larger diameters
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
136 / 592
USER MANUAL
SYSTEM DESCRIPTION

15.6 Manmachine interface

15.10 Environmental conditions

Main environmental aspects of AlcatelLucent 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
15.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: 5C to +55C (23F to 131F)
Operation
EN 300 019 class 4.1, IP 67
ODU
Temperature range: 33C to +55C (27.4F to 131F)
15.10.2 Electromagnetic compatibility/safety

EMC
EN 300 385 class B grade B/FCC Part 15 subpart Bclass A
Safety
EN 60 950
Power supply
EN 300 132
ElectroStatic
discharge
EN 55022 class B
Symmetric protection implemented in ODU & IDU
Lightning protection
$ 5kV on cable ground according to IEC 100045 with 2 wave types:

1.2/50 s and 10/700 s
15.10.3 Waste from Electrical and Electronic Equipment (WEEE)

This product must be selectively collected and treated. Treatment applied at end of life of the product in
these countries shall comply with the applicable national laws implementing directive 2002/96EC on
waste electrical and electronic equipment (WEEE).
The use of the crossedout wheeled bin symbol
indicates that the product is subject to separate
collection and is not to be treated as general household waste (only for B2C equipment)
Separate collection and recycling of waste equipment at the time of disposal contribute to avoid possible
negative effects on the environment and on human health.
USER MANUAL
SYSTEM DESCRIPTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

137 / 592
AlcatelLucent Reference documentation for dismantling and recycling detail is the document:
Ecodeclaration
As far as 9400AWY Rel.2 equipment is concerned, reference documentation for dismantling and recycling
detail is the document:
Tab. 52. Reference documentation for dismantling and recycling detail for 9400AWY R.2 equipment
Product
Code
DOC.
TYPE
(N.B.)
AWY/S
8BW036840000
EUZZA
N.B.
Denomination
9400AWY SCALABLE RADIO SYSTEM ECODECLARATION
DOC. TYPE for AlcatelLucent internal use only
Such a document is available on specific request to your AlcatelLucent local dealer.

NOTE FOR AlcatelLucent INTERNAL USE
cited document, in Adobe Acrobat pdf format, can be retrieved from PDM archive. Get highest
available edition.
a)
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
138 / 592
USER MANUAL
SYSTEM DESCRIPTION

15.11 Dismantling & Recycling

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL

SECTION CONTENT
PAGE
Chapter 21 SWP 9400AWY R.2.1 V2.1.1 description

It gives general information on the SWP version.
141
Chapter 22 Introduction on TCO Suite and CT views and menus

It 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 sumsup the
organization of the 9400AWY NE Craft Terminal, presented after the NE login.
143
EQUIPMENT CONFIGURATION MANAGEMENT

Chapter 23 Configuration
It describes the configuration relevant to the equipment management.
189
Chapter 24 Equipment
It deals with the presentation of the N.E. and the structure of the hierarchical tree,
and the types of subracks and boards, that comprise the Network Element.
219
Chapter 25 Line Interface

It describes the operations necessary for the configuration setting and verification
of each tributary.
227
Chapter 26 Radio
It deals with the management of the Radio transmission features.
233
Chapter 27 External input and output points

It describes how to display and set the input/output environmental alarms
(housekeeping alarms).
247
FUNCTIONS FOR MAINTENANCE

Chapter 28 Supervision
It describes how to manage the NE access from OS or local ECT and how to restart
the NE.
251
Chapter 29 Protection schemes

It deals with the management of the Radio protections.
257
Chapter 210 Loopbacks

It describes the commands for loopback management, for commissioning or
maintenance purposes.
267
Chapter 211 Diagnosis

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

It deals with the use of the Performance Monitoring functionalities.
289
TABLE CONTINUES
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
139 / 592
PAGE
SOFTWARE MANAGEMENT
Chapter 213 Software Management
It deals with the management of the functions related to the software
verification/download.
297
Chapter 214 MIB Management

It deals with the management of the functions related to the backup and restore
of equipment configuration data.
301
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
140 / 592

SECTION CONTENT

21 SWP 9400AWY R.2.1 V2.1.1 DESCRIPTION

This chapter gives general information regarding the Software Package this manual refers to.
21.1 SWP 9400AWY R.2.1 V2.1.1 general description

21.1.1 General
The software products are distributed by AlcatelLucent in a CDROM.
In this CDROM are contained:
Software packages for NE management by means of the craft terminal
Software package of the NE, to be installed in the NE or update the NE (by means of download
function)
The software package used for management allows the dialogue between craft terminal and NE, to
realize all the functions of the NE and EMLULS ).
The software package used for updating the NE must be installed on the PC and then downloaded on
the NE, thus following product evolution.
21.1.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 CDROM with the same identifiers, listed on the following table:
Tab. 53. Software products part numbers
REF
[a]
SWP 9400AWY R.2.1 V2.1.1
Technical Code
3DB16131ABAA
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
141 / 592
21.2.1 PC characteristics
Refer to para.31.1.1 on page 309
21.2.2 NE MIB Compatibility
NE MIB structure is automatically converted from previous release 2.1.0, using the procedure described
in Chapter 49 on page 495
V2.1.1 NE MIB structure is not backward compatible with those of previous release 2.1.0 (see point
[1]6 )WARNING on page 495
NE MIB structure is not compatible with any releases 1.0.x and 2.0.x
21.2.3 SWP version specific data and Reference Information Models
Make reference to the Product Release Note (see para.57.2.2 on page 571 )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
142 / 592

21.2 SWP 9400AWY R.2.1 V2.1.1 specific information

22 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 sumsup 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 156
PCNE physical connections
Physical interfaces for the NE management
Local connection of the Craft Terminal to the NE
Craft Terminal: NE supervision, login, logoff and switch off
on page 172
9400AWY view organization
on page 181
Introduction to the CT menu options
on page 184

on page 170
on page 171
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
143 / 592
a)
PC characteristics
The PC used for TCO Suite application and/or employed as Craft Terminal must meet all
specifications pointed out in para.31.1.1 on page 309.
b)
Cables necessary for PCtoNE 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 NEs Finterface 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 AlcatelLucent (P/N 1AF11294AA**).
for the local direct connection between PC and NE Ethernet ports, one crossconnect Ethernet
cable is necessary.
Otherwise the connection can be done by a normal Ethernet cable through a LAN.
For explanatory drawing, see Fig. 59. on page 154.
Typical AlcatelLucent Ethernet cables are:
Tab. 54. Typical AlcatelLucent Ethernet cables
Length
6m
2m
N.B.
c)
Type
P/N
normal
3DB 14050 AA**
crossconnect
3DB 14051 AA**
normal
3DB 05020 AA**
crossconnect
3DB 05021 AA**
The TCO Suite applications can use the Ethernet interface only.
The Craft Terminal application can use both the Ethernet and the RS232 interfaces.
Craft Terminal
If the Craft Terminal application must be used, the SWP installation must have been already carried
out, as specified in chapter 31 on page 309.
d)
NE state
the SWP (NEspecific components) must be already present in the NEs flash card and its
active version (see point [2] on page 63 to do this check) must be equal to that of the:
SWP CDROM this manual refers to (in case of TCO Suite application run directly from
the CDROM itself)
SWP installed in the Craft Terminal (see point [1] on page 62 to do this check).
Solve different situations, if any, according to instructions given in para.12.6.4 on page 64.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
144 / 592

22.1 Requirements

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.23.6 on page 214.
f)
Operator skills
g)
the Operator shall be familiar with the use of personal computers in WINDOWSNT /
WINDOWS2000 / WINDOWSXP (professional version only) environment, internally to
which the Network Elements 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).
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 G on page 567.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
145 / 592
This paragraph is organized as follows:
TCO Suite scopes
below
Summary
on page 147
TCO Suite startup
on page 148
TCO Suite Main Menu functions
PreProvisioning Tool
SetUp Tool
Alarms & Settings
Advanced Settings

on page 150
on page 150
on page 150
on page 150
TCO Suite Advanced Settings Page

Java JRE Package Installation

on page 152
Serial F Interface Driver Installation

on page 153
1320CT Package Installation

on page 153
1320CT Package DeInstallation

on page 153
Local Copy of TCO Suite

on page 153
Note: Direct and Remote Connections
Warning about interface customization carried out by the Direct Connection on page 155
on page 154
22.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
CDROM).
Moreover, after having installed the SWP components and the TCO Suite local copy in the PC environment
(as described in chapter 31 on page 309), most of TCO Suite functionalities are available also after
having removed the SWP CDROM from the PC CDROM unit.
TCO Suite works through web pages with simple operations available with a single mouse click.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
146 / 592

22.2 TCO Suite description

22.2.2 Summary
After having started up the TCO Suite (para.22.2.3 on page 148), the TCO Suite Main Menu becomes
available (Fig. 55. on page 149) with the following main tools:
This is a fulllocal application.
SetUp 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 your PC for these applications:
N.B.
the CTNE connection can be:
physically and logically local, through a crossconnect 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.
The SetUp Tool and Alarms & Settings applications cannot be used through the
PCNE 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 NEs TCP/IP address
Operational & Maintenance

This application corresponds to the 1320CT application. Refer to para.172 on page 22.5 for details.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
147 / 592
Standard behavior
The Suite autoruns itself (if this feature is enabled on users PC) as soon as CDROM is read by PC.
If autorun does not start, user must run (doubleclick with mouse on) the Start.exe file, available on
CDROM 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 autorun 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 users PC or if there is a JRE installed on users 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 CDROM (Fig. 53. below).
Fig. 53. Java installation request

In both cases:
if user denies authorization to install the suitable JRE, TCO Suite wont be executed at all
if user gives authorization to install the suitable JRE, after some minutes the installation message
appears:
Fig. 54. JRE installation completion

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
148 / 592

22.2.3 TCO Suite startup

After, the default browser (configured as for user preferences) opens the TCO Suite Start.html page
(Fig. 55. below).
Special conditions
For any special condition which may occur during the TCO Suite startup and the countermeasures to
take, refer to the Appendix B TCO suite startup special conditions on page 511
22.2.4 TCO Suite Main Menu functions
Fig. 55. and Fig. 56. on page 149 show the layouts of the TCO Suite Main Page as described from the
internal version of AS.html file, respectively for the CDROM version and the Local version.
N.B.
The TCO Suite Local version must be explicitly created as described in para.22.2.5.5 on page
153
This page shows the main TCO Suite menu with the following functions:
SetUp 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.
Fig. 55. TCO Suite Start.html page (CDROM version)
Fig. 56. TCO Suite Start.html page (Local version)

Detailed functions and differences between CDROM and Local TCO Suites will be described in following
subparagraphs.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
149 / 592
This button is a oneclick execution for the PreProvisioning Tool.

This tool allows the offline 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.32.3.6 point [2] on page 341.
22.2.4.2 SetUp Tool
This button is a oneclick execution for the SetUp Tool.
This tool allows to access a NE, recover a configuration file previously created (e.g. through the TCO Suite
PreProvisioning Tool) or get configuration data from the NE, and check/modify/apply such a configuration
to the NE.
For procedure execution, refer to para.32.3.6 point [3] on page 341.
22.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 NEs
parameters.
For procedure execution, refer to para.22.3 on page 156.
22.2.4.4 Operational & Maintenance
This function runs the 1320CT software application.
This function has two different behaviors, one for CDROM 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
CDROM TCO Suite will perform a complete 1320CT installation, if needed (if such software is not
available).
If 1320CT is available on users system, the behavior is common between Local and CDROM TCO
Suites:
[1]
CDROM 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.31.5 (Installation of SWP components
from the SWP CDROM) from step 5 ) on page 316
[2]
Local TCO Suite

If users 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 174.

22.2.4.5 Advanced Settings
This button will show to user the related HTML page: this function is available through CDROM TCO Suite
only. All functions related to this page are described in following para.22.2.5 on page 151.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
150 / 592

22.2.4.1 PreProvisioning Tool

22.2.5 TCO Suite Advanced Settings Page

This page is opened clicking the Advanced Settings button of the CDROM TCO Suite Main Menu
(Fig. 55. on page 149). Such page is shown in Fig. 57. below and contains:
Java JRE Package Installation
Serial F Interface Driver Installation
1320CT Package Installation
1320CT Package DeInstallation
Local Copy of TCO Suite
Back : go back to Main Menu of Fig. 55. on page 149
Fig. 57. TCO Suite AS.html page (Advanced Settings)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
151 / 592
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. 58. below):
Fig. 58. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
152 / 592

22.2.5.1 Java JRE Package Installation

22.2.5.2 Serial F Interface Driver Installation

This button starts the installation (from the SWP CDROM) in PC environment of the LLMAN (Alcatel
Lower Layer MANager), necessary when communication with NEs ECT serial port is required.
For procedure execution, refer to para.53.2.1 on page 519.
22.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.31.5 on page 314.
22.2.5.4 1320CT Package DeInstallation
This function is a singleclick complete deinstallation for the 1320CT package. This function wont
remove neither possible JRE installed nor Alcatel Lower Layers Manager software.
Sequence of screens shown to user depend on speed and performance of users PC since all the
procedure is automatic and all the deinstallations needed are performed at the same time without the
need for interaction by the user.
22.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.31.6.1 on page 318.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
153 / 592
The difference between Direct or Remote connection, asked to user as in Fig. 62. on page 156, is
depicted in Fig. 59. 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 users PC so no Ethernet configuration is needed and the SetUp Tool or Alarms & Settings
function is executed.
in case of Direct connection, users PC is considered as directly connected to NE via a

crossconnection Ethernet cable so a Ethernet modification is needed on users PC since both
functions (SetUp 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
Direct
crossconnect Ethernet cable
Fig. 59. ECTNE Direct and Remote connections

For this reason, the TCO Suite will perform a search on users 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. 60. :
Fig. 60. Network Adapter selection

Such figure is an example created to show the possible layout. Actually, if users 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 wont see the dialog box shown in Fig. 60. above.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
154 / 592

22.2.6 Note: Direct And Remote Connections

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. 61. :
Fig. 61. Network Adapter details

When the user clicks on Apply the selected network adapter is modified in order to allow users 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 users personal directory usually located inside
Documents And Settings directory on system disk.
22.2.7 Warning about interface customization carried out by the Direct Connection
When the Direct connection (described in previous para.22.2.6 on page 154) is set up, the system
carries out an interface customization that makes any subsequent attempt to start the Craft Terminal using
the Finterface impossible, even after the logging off from the TCO Suite application and independently
from the settings explained in para.22.4.2 on page 171.
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 Finterface becomes again possible.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
155 / 592
TCO Suite Alarms & Settings startup

Date & Time Setting
Configuration Setting
Configuration Info
Get Configuration File
Active Alarms
Power Measurement
Licence Info
Modem Speed
below
on page 159
on page 160
on page 161
on page 164
on page 165
on page 166
on page 166
on page 167
22.3.1 TCO Suite Alarms & Settings startup

To launch this application, click on the button Alarms & Settings of the TCO Suite Main Page (see
Fig. 55. and Fig. 56. on page 149).
Then, User is asked to distinguish between Direct or Remote connection (Fig. 62. below) and he/she
will be asked to fill the IP address field used to connect to NE.
Fig. 62. Direct or Remote connection by the TCO Suite

The difference between Direct or Remote connection is described in para.22.2.6 on page 154.
WARNING 1: In case you choose the Direct connection, read carefully para.22.2.7 on page 155
(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 SWPversion 2.0.4.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
156 / 592

22.3 TCO Suite Alarms & Settings functions

Then (Fig. 63. below), User is asked to provide the Username and Password [same rules as in point 3 )
on page 179]. In case of remote connection, the NEs IP address entered in previous screen (Fig. 62. )
is displayed.
Fig. 63. NE login by the TCO Suite

As soon as the connection with the NE is established, the Alarms & Settings Main Menu screen appears
(Fig. 64. below).
Fig. 64. TCO Suites Alarms & Settings Main Menu screen
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
157 / 592
Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login profile
Login profile
Function
Administrator, Craftperson
and Operator
Viewer
Date & Time Setting

(para.22.3.2 on page 159)
YES
read only
Configuration Setting
YES
NO
Configuration Info
YES
YES
Get Configuration File

YES
YES
Active Alarms
YES
YES
Power Measurement
YES
read only
Licence Info
YES
YES
Modem Speed
YES
read only
NAT Option
(para.22.3.10 on page 168)
YES
NO
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 subparagraphs.
Logout button gives the user the possibility to clear its authentication parameters and reload the initial page
(Fig. 64. on page 157) for starting a new session.
The links between pages are available by following standard procedures and correct navigation steps.
If the user will follow nonauthorized 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.
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 sandglass 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).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
158 / 592

Operations allowed according to the Login profile (refer to para.23.6 on page 214 for details) are:

22.3.2 Date & Time Setting

For authorized users, this function allows to modify NE internal time so that it can be automatically aligned
with users 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 backup).
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. 65. 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 users PC is configured as located in central Europe (CET or CEST time zones) and it
shows 20060825 11:40:00, by clicking Apply button NE web server will receive 20060825 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. 65. TCO Suites 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 wont allow to modify NE time and date
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
159 / 592
The set configuration process allows the allowed operator for sending to NE the operators desired
configuration.
Fig. 66. TCO Suites 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 PreProvisioning Tool, N.B.), and then click on Apply
Configuration button.
N.B.
refer to para.32.3.6 on page 341 for details.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
160 / 592

22.3.3 Configuration Setting

22.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. 67. 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 textreading application (e.g.
WORD PAD) to open and read correctly the file.
Fig. 67. TCO Suites 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/DS1ETH (PSU4860)

Market: ETSI
Frame Structure: 8E1
Modulation: 16QAM
Impedance: Unbalanced 75 Ohm
TRIBUTARIES CONFIGURATION
E1 Tributary 1: Signal
Mode:
Mode:
Mode:
Mode:
Mode:
Mode:
Mode:
Mode:
Unframed
Disabled
Disabled
Disabled
Framed
Disabled
Disabled
Framed
DATA CONFIGURATION
[Ethernet Port 1]
Status: Disabled
Auto Negotiation: Disabled
Speed Without Autonegotiation: 100 Mbit/s
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
161 / 592
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
[Input Point 2]
User Label:CPI2
Polarity: Active
[Input Point 3]
User Label:CPI3
Polarity: Active
[Input Point 4]
User Label:CPI4
Polarity: Active
[Input Point 5]
User Label:CPI5
Polarity: Active
[Input Point 6]
User Label:CPI6
Polarity: Active
Closed
Closed
Closed
Closed
Closed
Closed
[Output Point 1]
User Label:CPO1
Polarity: Active Closed
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
162 / 592

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

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
[TMNRF]
Status: Disabled
[TMNV11]
Status: Disabled
Interface Mode: Not Used
[TMNG703]
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
163 / 592
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 humanreadable text format, the configuration file is described
in QCML format and it can be used by Quick Configuration by Text File or by PreProvisioning and SetUp
Tools. Selecting (by click) this function from main menu will show the user a Save File screen
(Fig. 68. 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 textreading application (e.g.

WORD PAD) to open and read correctly the file.
Fig. 68. TCO Suites Alarms & Settings Get Configuration Request
This file is an XML standardbased set of configuration information that PreProvisioning and SetUp Tool
can preview in a humanreadable 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
164 / 592

22.3.5 Get Configuration File

22.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, wont 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. 69. TCO Suites 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. 70. below).
Fig. 70. TCO Suites 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.
WARNING:
For autorefreshed pages, a longer timeout is foreseen. This is set to 90 refresh cycles
of 10 seconds each, for a total of 15 minutes. After this timeout, the connection expiration
page is shown.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
165 / 592
This page (Fig. 71. below) allows user to read power measurement result.
Refresh Interval filed allow the operator to set the time duration of the measurement for automatic
refreshing. The choice is among 5,10,30 sec. Otherwise operator can click refresh button directly to
refresh the result of power measurement.
Fig. 71. TCO Suites Alarms & Settings Power Measurement
22.3.8 Licence Info

This page allows user to read license so that he can retrieve data needed by AlcatelLucent to produce
a new Software License (Fig. 72. below).
Fig. 72. TCO Suites Alarms & Settings Reading Software License
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
166 / 592

22.3.7 Power Measurement

22.3.9 Modem Speed

This function (Fig. 73. below) allows the authorized user for reading the current FInterface speed value
and for modifying it through a simple combo box.
Fig. 73. TCO Suites Alarms & Settings Changing FInterface Speed
In case of login by viewer profile, the button and combobox elements are not shown and the page just
displays the current modem speed.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
167 / 592
Fig. 74. TCO Suites Alarms & Settings NAT option

[1]
NAT router
In the following the scenario, when the NAT router is used in the network, is analyzed, providing a
list of warnings and the relevant countermeasures. The scenario is represented by a remote
manager that wants to access the radio network; in between one or more NAT router could be
present. WTD suggests not using this device because of the consequences that are hereunder
described.
[2]
What is the NAT router

The Network Address Translation allows a single device, such as a router, to act as agent between
the Internet (or public network) and a local (or private) network. This means that only a single
unique IP address is required to represent an entire group of computers to anything outside their
network. The shortage of IP addresses is the main reason to use NAT.
Fig. 75. NAT router

The NAT function cannot by itself support all applications transparently and often must coexist with
application level gateways (ALGs) for this reason. People looking to deploy NAT based solutions
need to determine their application requirements first and assess the NAT extensions (i.e., ALGs)
necessary to provide application transparency for their environment. NAT devices are application
unaware in that the translations are limited to IP/TCP/UDP/ICMP headers and ICMP error messages
only. NAT devices do not change the payload of the packets, as payloads tend to be application
specific. NAT devices (without the inclusion of ALGs) do not examine or modify transport payload.
For this reason, NAT devices are transparent to applications in many cases.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
168 / 592

22.3.10 NAT option

[3]
What are the NAT router limitations

As stated on the RFC 2663
IP Network Address Translator (NAT) Terminology and Considerations
there are three main areas where NAT devices often cause difficulties:
1)
2)
3)
when an application payload includes an IP address,

the FTP application unless to operate dedicated setting and
when endtoend security is needed (ex. IPSec transport mode or the TCP MD5 Signature
Option)
About 1 ) , SNMP is one such application with address content in payload. NAT routers would not
translate IP addresses within SNMP payloads. It is not uncommon for an SNMP specific ALG to
reside on a NAT router to perform SNMP MIB translations proprietary to the private network, but for
sure it is expensive and NAT device depending.
[4]
How the WTD equipments SNMP based are impacted

1)
About the Manager IP Address Access Control Security

This feature allows the control of the IP manager forbidding the access for any manager that
is not registered. For the 9400AWY family, the Start Supervision operation/sequence is
completed successful only if IP packets coming from the manager have the same IP source
address than the one contained in the Registration table (retrieved by the SNMP message); this
means, in case of NAT usage, no way to access the equipment.
2)
Disabling the Manager IP Access Control

Obviously the case of NAT presence has been overcame with some modification, considering
it as exceptional case.
For example for both products can be enabled the No registration or NAT presence option
that skips the previous check.
In this case some drawbacks can be observed, compared to the standard behavior.
9400AWY case
3)
No registration
Standard Access Control
NE Reset
NOK
OK
Loopback commands
NOK
OK
Shifter management
NOK
OK
About the FTP application

One of the most popular internet applications FTP could not work in presence of the NAT,
unless specific implementations are provided.
Generally the TCP checksum and the TCP sequence and acknowledge numbers must be
updated to reflect the change in length of FTP control data portion: detailed explanation can be
found on the RFC 2663.
Consequently some applications can be impacted as:
Software Download
Backup and Restore
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
169 / 592
22.4.1 Physical interfaces for the NE management

See Fig. 76. 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.12.4.1 on page 54), through the suitable RS232 cable
supplied with the equipment
physically remote but logically local (ECT function, as above) through an ECTequipment
connection via the public switched telephone network, as explained in Appendix E on page 553
N.B.
as shown in Fig. 59. on page 154, the Ethernet interface can be used for the:
the F interface usage requires LLMAN installation [see choice b ) on page 311]
local connection, through a crossconnect Ethernet cable, or through a HUB), to the PC:
configured as Craft Terminal
or running the TCO Suite directly from the SWP CDROM
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. AlcatelLucent 1353NM)
the PC running the TCO Suite directly from the SWP CDROM
by the Radio interface:
the NE can be reached:
from remote Craft Terminals (RECT function, explained in para.12.4.2 on page 54)
or from the TMN OS or from the PC running the TCO Suite directly from the SWP
CDROM, when the NEs 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. 76. MAIN Unit front side: interfaces for equipment control
N.B.
As delivered from AlcatelLucent Factory, the NEs:
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
170 / 592

22.4 PCNE physical connections

22.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 22.4.2.1 and 22.4.2.2 below describe how to switch from one to the other interface (this
setting is at PC side only).
This setting is necessary only in case you start the CT by Start Alcatel 1320CT [see step
e )2 ) on page 174].
In case you start the CT clicking the button Operational & Maintenance of the TCO Suite Main
Menu (see step e )1 ) on page 174], you do not need to carry out this setting, because proper
setting is automatically setup answering the question of Fig. 77. on page 174.
N.B.
22.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. 53.3 on page 522).
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 recustomization by entering the following
command:
Start Programs Alcatel SNMPCTKADDON v3.x.x SNMP AddOn Customization

N.B.
If the connection through Ethernet Network Port has been activated, to activate again the
connection through the Serial Port enter the following command:
Start Programs Alcatel SNMPCTKADDON v3.x.x NE Connection Serial Port
22.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
Operators Handbook.
2)
Enter the NE and enable the Ethernet port on the NE (refer to para. 23.2.3 on page 195).
3)
Quit the NE and close the Network Element Synthesis application.
4)
Activate the CT Connection through the Ethernet Port by the following command:
StartProgramsAlcatelSNMPCTKADDON v3.x.xNE ConnectionEthernet Port

N.B.
If the IP Address configured on the Ethernet port has been changed, it is necessary to perform
a recustomization by entering the following commands:
Start Programs Alcatel CTK v3.x.x Customization
Start Programs Alcatel SNMPCTKADDON v3.x.x NE ConnectionEthernet Port
Start Programs Alcatel SNMPCTKADDON v3.x.x SNMP AddOn Customization
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
171 / 592
NE management states
NE Login
NE Logoff or switch off
Closing the 1320CT application
below
on page 173
on page 180
on page 180
22.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
Operators Handbook (see Tab. 78. on page 571).
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.22.5.2 on page 173.
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.22.5.3 on page
180.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
172 / 592

22.5 Craft Terminal: NE supervision, login, logoff and switch off

22.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:
b)
the CTNE 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 ECTequipment connection via the public
switched telephone network, as explained in Appendix E on page 553
physically and logically local, through a crossconnect 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 NEs TCP/IP address
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 36, through the suitable cable connect the ECT
to the F interface or to the Ethernet interface of the MAIN unit (refer to Fig. 76. on page 170).
To activate on the CT the connection through the Serial Port or through the Ethernet Port refer
to para. 22.4.2 on page 171.
2)
Connection of the PC to the TCP/IP network

N.B.
3)
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.
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 32 on page 329.
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 NEs TCP/IP address.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
173 / 592
Power on the PC and wait for its startup (if not yet done)
d)
Only in case of CTNE connection via public switched telephone network:

set up the connection on the public switched telephone network, as described in para.55.6 on page
560
e)
Craft Terminal startup

There are two ways to start the CT; they are not equivalent (note):
(note)
1)
in case no NE is locally connected to the PC, these modes are equivalent (no CTNE
connection setup)
Preferred mode to start the CT to login a NE: click the button Operational & Maintenance
of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149). Refer to para.22.2.4.4
on page 150 for possible additional details.
Notice that this choice in independent from the setting (at PC side) of the CTNE local
connection on the Serial or Ethernet interface (explained in para.22.4.2 on page 171). 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 users system, user is asked to
select between serial or Ethernet port connection by following screen:
Yes
Fig. 77. Choice of Serial or Ethernet interface for PCNE 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 users 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. 62. on page 156.
After a while, the Network Element Synthesis screen opens [step f ) on page 175].
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.22.4.2 on
page 171.
After a while, the Network Element Synthesis screen opens [step f ) on page 175].
WARNING:
In case you use the Serial interface and the Network Element Synthesis does
not open, read carefully para.22.2.7 on page 155 (Warning about interface
customization carried out by the Direct Connection)
N.B.
Only in case of Finterface 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).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
174 / 592

c)

f)
Network Element Synthesis screen

There are two cases:
the PC is locally connected to the NE; screen appears as follows:
Fig. 78. Network Element Synthesis screen (NE locally connected)
the symbol
symbol is not present if the connection has been established through the Ethernet
interface.
the symbol ? means they NE is not supervised.
indicates the NECT local connection by serial cable (Finterface). Such
Now:
if you have to operate on the NE locally connected, proceed to step h ) on page 177.
if you have to operate on a remote NE, proceed to step g ) on page 176.
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. 79. 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 ) .
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
175 / 592
SNMP NE creation
N.B.
This is a simplified description. For complete instructions, please refer to the 1320CT
Basic Craft Terminal Operators Handbook, section EML CONSTRUCTION.
To create a SNMP NE in the Network Element Synthesis map:
you must know the NEs TCP/IP addresses. Note: the NE has always two addresses that can
be equal or different:
the Local Configuration address, see para.23.2.1 on page 192
the Ethernet Configuration address, see para.23.2.3 on page 195
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.
Note: in case the Local Configuration and Ethernet Configuration addresses are different
from each other, perform this check for both.
then, proceed as shown in Fig. 80. below, inserting in (2) the NEs own TCP/IP address.
Note: in case the Local Configuration and Ethernet Configuration addresses are different
from each other, you must insert the Local Configuration 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. 80. SNMP NE creation in the Network Element Synthesis map
After such creation, the empty map of previous Fig. 79. becomes populated as in Fig. 81. below
(the symbol ? means the NE is not supervised).
Fig. 81. 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 )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
176 / 592

g)

h)
Start supervision on a selected Network Element

From a populated Network Element Synthesis map (e.g. Fig. 78. on page 175 and Fig. 81. 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. 82. below). In alternative, while NE selected, with left
mouse button choose Supervision Start
Fig. 82. 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. 83. on page 177

N.B.
In order to know the possible color meaning , refer to the:

1320CT Basic Craft Terminal Rel.3.x Operators Handbook:
chapter SOFTWARE INSTALLATION
paragraph Craft Terminal Configuration,
subparagraph Communication with NE
Fig. 83. 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:
\ ? : * < >|.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
177 / 592
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 dont click on the name of the map.
This operation causes the lock of the CT and the CT must be closed and opened again.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
178 / 592

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

i)
Network Element login

From screen Network Element Synthesis with NE in supervised state (e.g. Fig. 83. on page 177):
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. 84. below). In alternative, while NE selected, with left
mouse button choose Supervision Show Equipment
Fig. 84. Show Equipment

3)
after a while, the Login screen appears (Fig. 85. below), that must be filled in with suitable
values.
Fig. 85. 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. 23.6 on page 214.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
179 / 592
and, after a while, the 9400AWY Main view opens (Fig. 87. on page 181)
After the 9400AWY Main view has opened, all the available menus are introduced in para.22.6 on
page 181.
22.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. 87. on page 181) clicking
then, in the Network Element Synthesis Window (Fig. 86. 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. 86. NE Stop Supervision
NE will go to not supervised state.
22.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. 86. below) clicking
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
180 / 592

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

22.6 9400AWY view organization

22.6.1 Introduction
The 9400AWY view (see Fig. 87. below for the 1+1 configuration) contains the following fields, which
provide the operator with the information needed to manage the NE:
View title
View area
Main tool bar see para.22.6.4 on page 183
Menu bar
Severity alarm synthesis (N.B.)
Domain alarm synthesis (N.B.)
Management state control panel (N.B.)
Message/state area.
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.45.8.2.1 on page
437.
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.
Main tool bar
Severity alarm synthesis
Domain alarm synthesis
View title
Menu bar
Tab panel
View
area
RESOURCE
TREE AREA
RESOURCE LIST AREA
RESOURCE DETAIL AREA

Management state control panel
Fig. 87. 9400AWY Main view organization
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
181 / 592
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
Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ).
Each tabpanel (e.g. functionalities area) consists of four areas:
ResourceTree Area: displays all the available resources of the Radio NE.
ResourceList Area: may be represented by: Tabular View (e.g., Line Interface Domain) or
Graphical View (e.g., Equipment Domain).
Tabular View: displays a tabular representation of the selected resource. As default, no tabular
element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no

tabular element is shown.
ResourceDetail Area: displays detailed information of a selected item in the Resource List area.
As a default, no entry view is displayed as a consequence of the default behavior of the Resource
List area.
22.6.2.1 Resource Tree Area and Selection Criteria

The Resource Area displays all the available resources in a tree structure like the protocol stack
hierarchy.
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.
22.6.2.2 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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
182 / 592

22.6.2 View Area

22.6.3 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.
22.6.4 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
screen
next
screen
Summary Block Diagram view
not operative
Quick Configuration
Fig. 88. Main tool bar
N.B.
previous screen and next screen buttons are enabled according to the context.
Shortcuts available are:
Quick Configuration: details in para.32.3.7 on page 343
Summary Block Diagram view: details in para.211.5 on page 285
Current Configuration view: details in para.211.6 on page 288
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
183 / 592
Menu organization
Views menu introduction
Configuration menu introduction
Diagnosis menu introduction
Supervision menu introduction
SW Download menu introduction
below
on page 185
on page 186
on page 186
on page 187
on page 187
22.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 23 on page 189 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).
To navigate among the views and to set the TMN parameters.
Configuration
(second column).
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
Diagnosis
(third column).
To get information on the NE (alarms, performance monitoring, remote inventory).
Supervision
(fourth column).
To set the supervision states (i.e. Craft Terminal enabling).
SW Download
(fifth column).
See para. 22.7.6 on page 187
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
184 / 592

22.7 Introduction to the CT menu options

22.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 24 on page 219
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.

See Chapter 29 on page 257.
Loopback:
N.B.
Allows to manage the loopbacks available with the equipment.

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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
185 / 592
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. 23.1 on page 190
Network configuration:
Alarm Severities:
Manages the Alarm Severity Assignment Profile.

System setting:
Allows the system configuration, providing the setting of all the parameters
for the NE setup.
Quick configuration:
Allows a full system configuration through a guided procedure.

Profiles management:
Allows the CT user profile management.

Log Switch:
Inhibits/allows the event and alarm store in the Log

22.7.4 Diagnosis menu introduction

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

Log Browsing:
Manages the alarms and events stored in the NE.

Remote inventory: Displays the equipment Remote inventory information.

Abnormal
condition list:
Summary Block
Diagram View:
Displays the manually operations active in the NE.

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).
Current configuration
View:
Displays the current configuration of the NE.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
186 / 592

22.7.3 Configuration menu introduction

22.7.5 Supervision menu introduction

This menu allows to set the supervision states of the NE, by means of the following entries (see chapter
28 on page 251) :
Access State:
Manages the supervision access to the NE, via CT or OS.

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.

22.7.6 SW Download menu introduction

This menu allows to manage the NE software, by means of the following entries (see chapter 213 on page
297) :
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
187 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
188 / 592


23 CONFIGURATION
This chapter describes the following Configuration menus:
NE Time
on page 190
Network Configuration
on page 191
Local Configuration
NTP Configuration
Ethernet Configuration
IP Configuration
on page 192
on page 193
on page 195
on page 196
IP static routing configuration

OSPF Area configuration
IP Address configuration of PointToPoint Interfaces
Routing information
on page 204
Alarm Severities
on page 205
System Settings
on page 210
NE Configuration
Link Identifier
Overhead
on page 210
on page 212
on page 213
Quick Configuration
on page 213
Profiles management
on page 214
Functional description
Change Password procedure
Users Management procedure
Log Switch
on page 196
on page 200
on page 202
on page 214
on page 216
on page 217
on page 218
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
189 / 592
The NE local time can be displayed and/or realigned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which you can set the local NE time.
Fig. 89. NE Time dialogue box

The NE Time dialogue box displays the current NE time and the current OS time.
To realign the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The NTP status field is a readonly screen, which shows the configuration regarding the Network Time
Protocol performed in the menu Configuration > Network Configuration > NTP Configuration.
The Refresh pushbutton causes the refresh of the screen.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
190 / 592

23.1 NE Time

23.2 Network Configuration

To get access the Network Configuration option select the Configuration pull down menu, as shown
in the following figure.
Fig. 90. Network Configuration menu
The Network Configuration allows to perform the following operations:

Local Configuration:
defines the local NE addresses
NTP Configuration:
allows to enable/disable the Network Time Protocol
Ethernet Configuration:
defines the configuration parameters necessary to manage

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

protocol
shows a summary of the information relevant to the routing
which has been configured.
The options are described in next paragraphs.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
191 / 592
N.B.
This function is equivalent to that of Quick Configuration Procedures Step G on page 361
WARNING:
read carefully Rules for the definition of the NEs Local IP and Ethernet IP
addresses on page 361
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. 91. on page 192 ) 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. 91. Local Configuration dialogue box
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
192 / 592

23.2.1 Local Configuration

23.2.2 NTP Configuration

N.B.
By selecting NTP Configuration the dialogbox in Fig. 92. opens, which allows to enable the Network
Time Protocol.
Fig. 92. 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.
WARNING:
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
193 / 592
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. 93.
NE1
NE2
NE3
NE4
Fig. 93. Map

As example NE1 must be set as Master:
disable the NTP protocol.
NE2 is set as Slave:
enable the NTP protocol;

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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
194 / 592

23.2.2.1 How to configure the NTP in a network

23.2.3 Ethernet Configuration

N.B.
WARNING:
read carefully Rules for the definition of the NEs Local IP and Ethernet IP
addresses on page 361
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. 94. on page 195 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 choose 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. 94. Ethernet Configuration dialogue box
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
195 / 592
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the IP Configuration option ( see Fig. 95. on page 196).
Fig. 95. IP configuration screen
23.2.4.1 IP static routing configuration

N.B.
This function is equivalent to that of Quick Configuration Procedures Step I on page 364
The dialogbox opens ( see Fig. 96. on page 197 ) 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
196 / 592

23.2.4 IP Configuration

Fig. 96. IP static routing configuration screen

By pressing Create pushbutton the screen in Fig. 97. on page 198 opens.
In the Host or Network Address Choice field select:
Host to address to a single IP address;
Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select:
Default Gateway IP Address for the Ethernet interface;
Point to Point Interface Index for the NMS channels (NMSRF, NMSV11, NMSG703)
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
197 / 592

Fig. 97. Create Static routing
If in the screen of Fig. 97. 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. 97. above has been selected the Point To Point Interface Index check box, the screen
in Fig. 98. on page 199 opens.
N.B.
It is also possible to define a Default Gateway Routing (refer to para.23.2.4.2 on page 199 for
details).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
198 / 592

Fig. 98. Point To Point Interface Choice

In this screen one of the 3 NMS channels (NMSRF, NMSV11, NMSG703) can be selected.
23.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. 97. on page 198
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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
199 / 592
N.B.
This function is equivalent to that of Quick Configuration Procedures Step F on page 360
The dialogbox opens ( see Fig. 99. on page 200 ) and allows to configure the parameters for OSPF
(Open Shortest Path First) Area Table Configuration.
Id
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.
The Id identifier is used when configuring the PPP interface or the ETH/OS OSPF parameter.
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. 99. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
200 / 592

23.2.4.3 OSPF Area configuration

By pressing Create pushbutton the screen in Fig. 100. below opens.

N.B.
3 areas max. can be created.
Fig. 100. Create New OSPF Area
In the screen write the IP address, the IP mask and select the flag (True/False).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
201 / 592
N.B.
This function is equivalent to that of Quick Configuration Procedures Step I , point [4] on
page 364
The dialogbox opens ( see Fig. 101. below) and allows to Enable or Disable the three NMS channels,
which use the PPP protocol.
Fig. 101. IP Address configuration of PointToPoint Interfaces screen

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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
202 / 592

23.2.4.4 IP Address configuration of PointToPoint Interfaces

In alternative to the G703 NMS, the TMN inframe E1 can be defined.

With this TMN inframe feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS
131) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmit
remotely this type of information along the E1#1 route; this selection is alternative to the local availability
of TMNG703 (the mutual exclusion is automatic).
It is also necessary that the farend E1#1 tributary is enabled and successfully provisioned.
To activate the TMN inframe feature, in TMN G703 field (see Fig. 102. below) :
set Mode to InFrame E1
define the required E1#1 Timeslot number (default is 1)
Fig. 102. IP Address and Timeslot configuration of PointToPoint InFrame E1 TMN

Apply button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
203 / 592
Select the Configuration pull down menu. Select the Network Configuration and then from the
cascading menu, the Routing information option.
The dialogbox in Fig. 103. on page 204 opens.
Fig. 103. Routing information screen
This screen is a readonly screen and displays the routing parameters currently active on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
204 / 592

23.2.5 Routing information

23.3 Alarm Severities

By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 104. on page
206 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 doesnt affects the
service (with the exception of HighBER alarm, which MINOR alarm severity is defined, even if
it is service affecting).
Profile No Remote Alarms. This profile enables the emission of the primary alarms plus EW and
LBER alarm. This profile uses the following rules to define the alarms severity:
MAJOR: the alarm affects the service (it is service affecting);
MINOR: the alarm is potentially service affecting but a protection has recovered the service;
WARNING: the alarm cannot affect the service (independently from any protection).
Profile All Alarms. This profile enables the emission of all the alarms (included AIS and RDI). This
profile uses the same severity of the Primary alarm profile, the only difference is that EW, LBER,
AIS and RDI alarms are emitted.
The rules used to define the alarm severity are the same of the Primary alarm profile.
N.B.
In case of alarms affecting a protection different severities are used for SA and NSA. The same
severity is used both for SA and NSA in case of service independent alarms.
N.B.
The rules used to define the profile alarms severity described above, are not applied to the
housekeeping alarms. In this case, in order to enhance the flexibility, a different severity is
assigned to each alarm profile (WAR, MIN and MAJ).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
205 / 592

Fig. 104. Alarm Severities Profile

In the screen of Fig. 104. on page 206 are available 2 buttons:
N.B.
Close: to close the screen.

Clone: to create a new Alarm Severity Profile. To create a clone refer to para. 23.3.1 on page 207.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
206 / 592

23.3.1 How to create a new Alarm Severity Profile
Select in the screen of Fig. 104. on page 206 the Alarm Profile to be cloned.
Click the Clone pushbutton.
The screen of Fig. 105. on page 207 appears.
Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 105. 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. 106. on page 207).
Fig. 106. Clone of an Alarm Severity Profile

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
207 / 592
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. 107. on page 208).
Fig. 107. Selection of a new severity in the Service Affecting field
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
208 / 592


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. 108. on page 209).
Fig. 108. 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. 108. on page 209).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
209 / 592
This menu is used to change the configuration of a system already commissioned.

WARNING:
this menu must not be used for the firsttime NE setup. Setting of all parameters for the
firsttime NE setup must be done in the commissioning phase, as explained in Chapter
32 LineUp and Commissioning from page 341
The main window provides tabbedpanels, one for each type of function to be managed:
NE configuration
Link Identifier
Overhead
WARNING:
At the first configuration (i.e. with a flash card with an empty MIB) at the end of the
configuration the Restart NE must be performed (refer to para. 28.2 on page 252).
WARNING:
Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of
PSU2460), 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.
23.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. 109. below will appear.
The fields of this screen are practically equal to those of Quick Configuration Procedures Step A
screen described on page 347. Please refer to it for details not given in this paragraph.
DO NOT USE THIS CHOICE !
Fig. 109. System Settings: NE configuration
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
210 / 592

23.4 System Settings

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.
The Capacity can be modified by selecting a different type according to Tab. 64. on page 348 and then
selecting the Apply button to send the new value.
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 tributary (unbalanced 75 ohm or balanced 120 ohm).
The impedance value will be applied by clicking on the related Apply button.
N.B.
After a change in the Type or Capacity or Modulation field the explicit confirmation shown
in Fig. 110. is requested.
Fig. 110. Confirmation message

N.B.
Only one change can be performed in this screen.

When the user confirms the change in the Type 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 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:
Fig. 111. USM closing warning message
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
211 / 592
The user can view and define the Link Identifier by selecting the Link Identifier tabbed panel.
The window displayed in Fig. 112. below will appear.
The fields of this screen are practically equal to those of Quick Configuration Procedures Step D
screen described on page 358. Please refer to it for details.
If changed, the new parameter values will be sent to NE by clicking on the related Apply button.
Fig. 112. System Settings: NE configuration
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
212 / 592

23.4.2 Link Identifier

23.4.3 Overhead
The Overhead tabbed panel (Fig. 113. below) is present only if the Audio/User Service Channels
plugin is configured and identifies the parameters for the management of the phone number (EOW
function) and auxiliary channel interface:
The fields Order Wire Configuration and Type in the Auxiliary Interface Configuration area
of this screen are practically equal to those of Quick Configuration Procedures Step J screen
described on page 366. Please refer to it for details.
If changed, the new parameter values will be sent to NE by clicking on the related Apply button.
Fig. 113. Overhead Configuration
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. 23.3.1
on page 207). 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.
23.5 Quick Configuration

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.32.3.6 on page 341.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
213 / 592
23.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 cleartext 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
Twentyfive (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. 117. on page 217.
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).
Constructor (only for OS interface)

This Operator can do everything on the NE also to access to the Manager List bypassing 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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
214 / 592

23.6 Profiles management

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 online information is available in the Users Management help screen of Fig. 117. on page
217.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
215 / 592
This procedure is available for all Operator Profiles, after the login (see para.22.5.2 on page 173)
1)
Configuration Profiles Management Change Password
Fig. 114. 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 214. New password will be active at next login (after
having logged out).
1
2
3
4
Fig. 115. Changing Password screen
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
216 / 592

23.6.2 Change Password procedure

23.6.3 Users Management procedure

This procedure is available to users with the Administrator profile only.
1)
Configuration Profiles Management Users Management (see Fig. 114. on page 216)
2)
Following screen appears. Click on Help
Fig. 116. Users Management screen

3)
Following screen appears. Click inside to explore matters and carry out the desired action.
Fig. 117. Users Management help screen
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
217 / 592
This screen (Fig. 118. below) of the configuration menu sets the inhibition or allowing of the the event and
alarm store in the Event Log and Alarm Log (for their browsing, refer to para.211.2 on page 279 ).
The Lock setting corresponds to the store inhibition state.
Fig. 118. Log Switch screen
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
218 / 592

23.7 Log Switch

24 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. 119. on page 220 for 1+0 configuration
Fig. 120. on page 220 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: 16xE1 with or without the Ethernet
ports, or 32xE1.
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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
219 / 592
ODU
ODU Status
IDU Status
IDU
Fig. 119. 1+0 Equipment view

Equipment Status
ODU
Ch#0
ODU
Ch#1
ODU
Status
IDU/EXT Ch #1
IDU/MAIN Ch #0
IDU Status
Fig. 120. 1+1 Equipment view
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
220 / 592

Equipment Status

24.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.
24.1.1 1+0 configuration
The screen in Fig. 121. below will appear.
IDU Status
IDU
MAIN BOARD
Status
Fig. 121. 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 4 Ethernet ports
IDU/MAIN/16xE1 Ch#1 with the second group of 16xE1 tributaries to implement the 32xE1
configuration
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
221 / 592
The screen in Fig. 122. below will appear for the Ch#1 and the screen in Fig. 123. below will appear for
the Ch#0.
IDU Status
IDU
MAIN BOARD
Status
Fig. 122. 1+1 IDU/MAIN Ch#1 view
IDU Status
IDU
EXTENSION BOARD
Status
Fig. 123. 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 4 Ethernet ports (this board receives the power supply from the Main
IDU only).
IDU/MAIN/16xE1 Ch#1 with the second group of 16xE1 tributaries to implement the 32xE1
configuration
The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration type
IDU/EXT/16xE1 Ch#0 with the second group of 16xE1 tributaries to implement the 32xE1
configuration
24.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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
222 / 592

24.1.2 1+1 configuration

24.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. 124. below will appear.
Fig. 124. ODU view
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
223 / 592
24.3.1 Alarms
The Alarms tab panel provides the fault management, which checks the current state of alarms related
to the selected object (Fig. 125. below).
Fig. 125. Alarm tab panel for a selected object

The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are
highlighted. When the alarm disappears it is automatically cleared in the screen.
By putting a tick in the Include alarms from subnodes box the alarms currently active in the subnodes
of the object will also appear.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
224 / 592

24.3 Tab panels in the Resource Detail Area

24.3.2 Configuration
The User Label field (Fig. 126. 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. 23.3.1 on page 207). To
associate a different Alarm Profile click on the selection button and make the selection among the available
Alarm Profiles.
N.B.
Fig. 126. Configuration tab panel for a selected object
24.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. 127. below):
Fig. 127. Remote Inventory tab panel for a selected object

For detailed information on Remote Inventory, refer to para.211.3.1 on page 282
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
225 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
226 / 592


25 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. 128. 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. 128. Line Interface View

In the Resource List Area is given the information related to the tributaries:
Interface Type (E1, Ethernet, NMS channels)
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 tributaries
according to the capacity selected in the System Setting menu (see para.23.4.1 on page 210)
or in Quick Configuration Procedures Step A screen (described on page 347 ).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
227 / 592
25.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. 24.3.1 on page 224.
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.
25.1.2 Configuration
There are different tab panels according to the type of interface:
PDH interface (para. 25.1.2.1 on page 228)

NMS interface (para. 25.1.2.2 on page 230)
Ethernet interface (para. 25.1.2.3 on page 231)
25.1.2.1 Tributaries PDH Configuration tab panel

25.1.2.1.1 ETSI Market
The window, shown in Fig. 129. below for E1 tributaries, performs all the available functions for a PDH
tributary port.
Fig. 129. Line Interface View: E1 Tributary Port

In Fig. 129. above the following fields are readonly fields:
Interface Type (E1)

Port Number: identifies the ports for a given channel and type of port
Channel Number
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
228 / 592

25.1 Tab panels in the Resource Detail Area

The fields, which can be changed, are:
Signal Mode
Line RAI Insertion
Radio RAI Insertion
Alarm Profile
Signal Mode (for E1 tributary)

[1]
Signal Mode
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:
[2]
In case of configuration with two Ethernet ports, some E1 ports must be disabled in
order to allow the transmission of the Ethernet data.
Refer to Tab. 65. on page 350 and to the relevant explanations in the same page.
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.
[3]
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.
[4]
Alarm Profile
The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default
alarm profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page
207). 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
229 / 592
Fig. 130. Line Interface View: NMS interface

For the NMS channels (RF, V11 and G703) 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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
230 / 592

25.1.2.2 NMS interfaces Configuration tab panel

25.1.2.3 Data Tributaries Configuration tab panel

N.B.
For whole information on Ethernet port characteristics and management, refer to the Appendix
D on page 547
The Data Tributaries Configuration tab panels described in following points [1] and [2] are available only
if the Enhanced Ethernet plugin is installed and has been defined by choice 16E1GData in the
Configuration % System Settings screen of Fig. 109. on page 210
[1]
Tab panels relevant to all Data Tributaries ports as a whole

QoS (Quality of Service) information and choices in Fig. 131. below is fully equal to that described
in Quick Configuration Procedures Step B point [2] QoS configuration screen described on
page 352 . Please refer to it for details not given here.
Fig. 131. Line Interface View: Data Tributary Port QoS Configuration tab panel
Fig. 132. below shows Performance Monitoring counters of all Data Tributary Ports
Fig. 132. Line Interface View: Data Tributary Port PM counters

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
231 / 592
Tab panels relevant to each Data Tributary port

The windows shown in Fig. 133. below and performs all available functions for one of four selectable
Data tributary port.
Fig. 133. Line Interface View: individual Data Tributary Port Configuration tab panel
a)
Except the field Alarm Profile and the button Restart , information related to a data port
Configuration panel is practically equal to that described in Quick Configuration Procedures Step
B point [2] Ethernet GPort configuration screen described on page 351 . Please refer to it for
details not given here.
b)
The field Alarm Profile allows to associate a particular Alarm Profile to the interface alarms: 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
c)
The Restart button allows forcing autonegotiation to begin link renegotiation.
If changed, to confirm the new configuration click on Apply.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
232 / 592

[2]

26 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. 134. on page 233):
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. 134. Radio Domain View

The following tab panels are present in the Resource Detail Area:
Alarms: show the active alarms (para. 26.1 on page 234 )

Configuration: configures some radio parameters (para. 26.2 on page 234 )
Frequency: sets the Radio Frequency (para. 26.3 on page 235 )
RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (para.
26.4 on page 238 )
Power Meas: performs the Tx and Rx power measurements (para. 26.5 on page 241 )
BER: performs the BER measurement (para. 26.6 on page 246 )
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
233 / 592
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. 24.3.1 on page 224.
26.2 Configuration
The window shown in Fig. 135. below controls some 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. 135. RadioConfiguration menu

26.2.1 Local or Remote Transmitter Mute
The information related to the transmitter status is shown in the Tx Mute field. To change the transmitter
status choose the desired value (ON for Tx Squelched and OFF for Tx not Squelched) and press the
related Apply button.
WARNING:
The Tx Remote Mute automatically works (on and then off) only if performed on the
local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed,
the EC changes the channel in monodirectional way, in order to have the possibility to
send the command to remove the mute. If the Network Element has been restarted after
a MUTE, there is no more possibility to setup the channel, because the remote address
is not known, and, in any case, to setup the channel a bidirectional communication is
needed. The only way to remove the MUTE command is with local CT or from a remote
CT which can reach the Network Element through another supervisory interface.
26.2.2 ODU service kit

This field is a readonly field, which displays the state (connected or not to the ODU) of the light service
kit cable (see para.32.10 on page 405 )
26.2.3 Alarm Profile
The field Alarm Profile allows to associate a particular Alarm Profile to the object alarms: a default alarm
profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page 207). To
associate a different Alarm Profile click on the selection button and select among the available Alarm
Profile. This panel belongs to TX Squelch one.
N.B.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
234 / 592

26.1 Alarms

26.3 Frequency
The Frequency menu allows to read and, if necessary, to set the frequency parameters.
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.14.5 from
page 104 onwards.
Fig. 136. Radio Frequency Functions with Shifter and Rx Freq enabled
Fig. 137. Radio Frequency Functions with Rx Freq disabled
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
235 / 592

Fig. 138. Radio Frequency Functions with shifter disabled

WARNING:
Since frequency setting could impact on traffic and requires a lot of time, following
messages are shown in sequence:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
236 / 592

[1]
ODU with one Shifter only

If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).
In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the
Frequency Range field on the right side) and press pushbutton Apply (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
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 pushbutton Apply.
In the Shifter field select the suitable shifter and press pushbutton Apply (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
Now the Rx frequency can be changed in order to implement a suitable new shifter. Insert the new
value in the Rx frequency field and press pushbutton Apply.
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 shown in figure below is written on the Frequency screen.
Fig. 139. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
237 / 592
This menu (Fig. 140. 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

ATPC Rx Threshold
Dynamic value of the Tx power
(20 dB range)
Fig. 140. RTPC & ATPC

WARNING:
When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa) the Tx
power (in case of operation with RTPC) and the ATPC range (in case of operation with
ATPC) of the new modulation scheme must be in the correct range. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
238 / 592

26.4 RTPC & ATPC

26.4.1 ATPC
The ATPC can be Enabled or Disabled.
The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the
ATPC Range and ATPC Rx Threshold fields must be filled.
WARNING:
[1]
In 1+1 Configuration (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.
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 levels can be changed by writing the new values in the fields.
WARNING:
Obviously, you must set Max TX Power value > Min TX Power value.
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).
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 could be (but not necessarily is) active.
WARNING:
It is recommended to use the following Tab. 56. in order to set the ATPC threshold.
The ATPC shape is calculated using the max capacity.
Tab. 56. ATPC Range Rx Threshold for ETSI
4
QAM
16
QAM
TH
7/8 GHz
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
Min
Value
73
74
74
72
72
71
71
70
Max Value
60
60
60
60
55
50
50
50
Min
Value
69
70
70
68
68
67
67
66
Max Value
60
60
60
60
55
50
50
50
The applied rule is:

Frequency Band
ATPC Rx threshold setting

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
PRxth: Received power level correspondent to BER

payload and ETSI standard
50 dBm
106
according to modulation scheme,
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
239 / 592
[1]
Nominal Power
The Nominal Value field in the RTPC area is a readonly field and shows the nominal value of the
transmitted power (expressed in dBm).
[2]
Tx Power
The Tx Power field in the RTPC area shows the current value of Tx power (expressed in dBm), when
the ATPC is disabled. In this case, it is possible to modify this value ERROR FREE in ATPC Range
(Pnom 20 dB) with 2 dB max step allowed, by writing the new value and by pressing the related
Apply button
N.B.
During the command setting the CT is frozen. Waiting time: < 15.
The new value must be within the allowed transmitted power range. This range is shown in the Power
Value label of RTPC area.
If the ATPC is enabled, the Tx power value cannot be modified.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
240 / 592

26.4.2 RTPC

26.5 Power Measurement

The Power Measurements capability is performed through the Power Meas tabbed panel in the resource
detail view (Fig. 141. below).
BER
Fig. 141. Power Measurements

The Measurement screen allows the operator to set initial parameters for the required measurement.
Measurement interval fields allow the operator to set the timeduration of the measurement. The
default is Days: 7, Hours: 0, Minutes: 0. A 7day measurement interval is also the maximum allowed
interval.
Sample time field is the period between two consecutive measurement samples. The choice is among
6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and name for this file is displayed to the
operator. The file is stored in the ALCATEL/CTKv3.x.x 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. 141. on
page 241).
The Power Measurement Graphic is available only if the CT is connected to the NE.
The screen in Fig. 142. 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).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
241 / 592
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. 142. Power Measurement Graphic

By clicking on Show details box, on the left side of the Power Measurement Graphic (see Fig. 142. on
page 242), a new table appears (Fig. 143. on page 243); 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
242 / 592

The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the
Rx curves (local and remote). Note that the colors represent the linked endpoint of the two NE; for
example, if the local TX is blue, the remote receiver will also have the same color.

Tx Far End
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
N.B.
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.
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.
PTx and PRx levels software readings tolerance is:
PTx = Real Value 2dB @ ODU Operating temperature range 33C + 55C on 020dB
RTPC range
PRx = Real Value with 3 dB accuracy from 41 dBm down to 69 dBm included (nominal
received levels)
PRx = Real Value with 4 dB accuracy from 30 dBm down to 40 dBm included and from
70 dBm down to threshold included
Fig. 143. Power Meas Details

WARNING:
If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
243 / 592
Click on Read File field and press on the Select File button. The directory of the CT automatically opens
to navigate and get the power measurement file.
N.B.
as default, the measurement files are stored in the ALCATEL/CTKv3.x.x directory and have
extension .txt.
Fig. 144. Name of File ( Log File ) selected screen

Select the desired file and click the Start button in Fig. 141. on page 241 to open the file.
Fig. 145. 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 pushbutton to open .txt file with a text editor (e.g.
WordPad) and to see the power information in tabular mode (see Fig. 146. on page 245).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
244 / 592

26.5.1 How to read a Power Measurement file

Fig. 146. Example of Power Measurement File Reading (with WordPad)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
245 / 592
This paragraph describes the nonintrusive BER function, by means of which it is possible to start/stop
and read the BER measure (Fig. 147. below).
Fig. 147. BER Features

[1]
Start and stop BER Measure

The BER measure function can be started (Start button) or stopped (Stop button)
[2]
Request BER Measure data

The information of BER Measure is not automatically updated in the Measure part. If the user wants
to see the current information of BER Measure, with the Refresh button, the information is updated.
The following parameters are provided:
elapsed time
BER measurement (see point [3] below)
suspect measurement indication. The measurement is marked as suspect if the NE was not
able to collect all the violations in the observation period (card missing, card fail).
[3]
BER Measurement calculation

The BER calculation formula is the following:
Pbit_out . (CNT_ERR_1SEC/ T)
where:
Pbit_out is BER measurement
assumes the following values:
= 4.6E07 (32E1)
= 9.2E07 (16E1)
= 1.8E06 (8E1)
= 3.7E06 (4E1)
= 7.4E06 (2E1)
CNT_ERR_1SEC (number of violations) is the HW counter which accumulates the errors in

the 1 sec. window and after each reading, it resets itself and restarts (the software collects the
counter value each second and to count the T period)
T (elapsed time) is the difference between the start time and the stop time of the
measurement.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
246 / 592

26.6 BER measure

27 EXTERNAL POINTS
This chapter describes the types of functions offered to the user for External Points Management (please
refer to para.13.6.1 on page 85 for physical implementation).
There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Fig. 148. 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. 148. below.
27.1 Input External Points

An input external point is described by the following parameters (Fig. 148. below):
Id: identification number

UserLabel: associates a userfriendly name to an external point
Polarity: describes the polarity (Active Closed/ Active Opened)
External State: describes the state (on /off)
Alarm Profile: describes the associated Alarm Profile
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. 148. Input External Point View
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
247 / 592
Seven output external points are available:

The first four external points (CPO#1, 2, 3, 4) (Fig. 149. below) are described by the following
parameters:
UserLabel: a userfriendly name can be associated to an external point
Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
Criteria: Manual or Automatic. The output can be activated manually by the CT by selecting Manual
(Fig. 149. below) or automatically by selecting Automatic (Fig. 150. on page 249). 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. 149. Output External Points: CP01 ... CP04 (Manual activation)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
248 / 592

27.2 Output External Points

Fig. 150. Output External Points: CP01 ... CP04 (Automatic activation)
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 151. on page 250)
are described by the following parameters:
UserLabel: a userfriendly name can be associated to an external point
Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external
point can be changed.
N.B.
These three output external points are automatically activated when the relevant equipment
summarizing alarm is active.
The operator choices will be sent to NE by clicking on the Apply button.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
249 / 592

Fig. 151. Output External Points View: FAIL IDU, FAIL ODU
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
250 / 592

28 SUPERVISION
28.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:
switching from the OS to the Craft Terminal access state
switching from the Craft Terminal access state back to the OS access state
28.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. 152. Configuration of the Craft access state from the Equipment NE view in the OS mode
From the confirmation dialogue box that opens, you can confirm or cancel the Craft access operation
using the Yes or No pushbutton. The request is sent up to the OS which accepts or refuses it.
If the OS doesnt answer in a predefined time, it is assumed that the NE is in the Craft access state
and can be managed by a Craft Terminal.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
251 / 592
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).
28.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. 153. Restart NE call

The following dialogue box opens.
Fig. 154. 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
pushbutton) the LLM icon is frozen and the supervision of the local NE and the remote
NE is lost.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
252 / 592

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

28.3 MIB Management

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

OSPF Area configuration
IP Address configuration of point to point configuration
1.
Local configuration
2.
NTP server configuration
3.
4.
Fig. 155. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
253 / 592
This menu (Fig. 156. 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. 156. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
254 / 592

28.3.1 Backup

28.3.2 Restore
This menu (Fig. 157. below) allows to download to the NE a previously created backup.
Fig. 157. Restore screen

Select one of the backups to be downloaded in the upper part and press Confirm Restore.
(By pressing the Reset pushbutton the previous selection is cancelled and a new selection can be made).
Confirm the restore operation to start the operation.
To activate the new configuration enter command MIB Management > Activate.
28.3.3 Activate
This command (Fig. 158. below) allows to activate the configuration just downloaded with the restore.
Fig. 158. Activate command
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
255 / 592
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.
28.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. 159. SW key screen
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
256 / 592

28.3.4 Remove file

29 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. 160. below, the tree will be expanded according to protection
schemes supported.
Fig. 160. 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
Fig. 161. on page 258 .
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
HSB protection: Hot Standby protection
To see the current position of the switches enter the menu Diagnosis > Summary Block Diagram View
(refer to para. 211.5 on page 285):
Mux/Demux Protection corresponds to the Switch Tx and the Rx output switch in Fig. 195. on page
287
the Radio protection corresponds to the Switch RPS HS in Fig. 195. on page 287
the HSB protection is implemented in the ODU: one Transmitter is connected to the antenna (active),
the other transmitter is in standby. Refer to Fig. 195. on page 287 . The HSB protection is available
only if the HSB configuration has been selected.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
257 / 592
The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.
The following window (Fig. 161. 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. 161. Mux Protection
29.1.1 Schema Parameters

The window Schema Parameters displays the parameters that can be modified.
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).
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.
The operator choice for Operation Type will be applied by clicking on Apply button.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
258 / 592

29.1 Equipment Protection Management

29.1.2 Commands
To enter the Commands menu, click, in the Tree view (Fig. 162. below), on the Spare #0 element or on
the Main #1 element
Fig. 162. Mux Protection Switch (example for Main #1 selected)

The operator can modify the state of the switch through commands Lockout, Forced and Manual.
Tab. 57. Command priority list
Command
Priority
Lockout
Forced
Automatic switch
Manual
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel)
for both EPS and RPS and disables the hitless function, 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.
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.
N.B.
to release a previously activated command select None and click on Apply.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
259 / 592
The Radio Protection Management is performed by selecting the Radio Protection element tree.
The following window (Fig. 163. below) allows a complete view of all NE resource involved in a RPS
protection:
Schema Parameters
Channels Parameters
Protection Command Status NOT Automatically Updated
Fig. 163. Radio Protection View

The window Schema Parameters displays the parameters that can be modify.
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).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
260 / 592

29.2 Radio Protection Management

29.2.2 Commands
the Main #1 element
Fig. 164. Radio Protection Switch (example for Main #1 selected)

WARNING:
whenever EPS lockout is set (see para.29.1.2 on page 259 ), RPS is switched on CH1,
and these commands are not available (greyed).
Command
Priority
Lockout
Forced
Automatic switch
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.
signaling ABN.
Note :
N.B.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
261 / 592
The Transmission Protection Management is performed selecting Transmission Protection element tree.
The following windows (Fig. 165. below) allows a complete view of all NE resource involved in a TPS
protection:
Schema Parameters
Channels Parameters
Fig. 165. Transmission Protection View

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
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
262 / 592

29.3 HSB Transmission Protection Management

29.3.2 Commands
the Main #1 element
Protection Command Status NOT Automatically Updated

Fig. 166. HSB Tx Protection Commands (example for Main #1 selected)
Command
Priority
Lockout
Forced
Automatic switch
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.
signaling ABN.
Note :
N.B.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
263 / 592
Fig. 167. Rx Static Delay menu

The Rx Static Delay must be compensated during the commissioning. Two compensating modes are
possible:
Automatic
Manual
These two modes are alternative.
To activate the Automatic mode click on the Align pushbutton (the compensation procedure is
automatically done).
To activate the Manual mode:
[1]
click on the Start pushbutton;
[2]
write the values in the Channel 0/1 fields (N.B.);
[3]
click on the Apply pushbutton to send the value to the NE.
N.B.
Write in one field the suitable value (in range 031) and in the other field write 0.
At the end of automatic procedure, a warning message will be displayed to explain the result of procedure.
For example, if procedure failed the following message is shown:
Fig. 168. Rx Static Delay panel Warning message for fail

If procedure is correctly ended, a similar warning message will be displayed. When the manual procedure
is started, the status of buttons change to allow the available procedure: Stop manual procedure Align of
values during manual procedure as shown in Fig. 169. . The automatic procedure is disabled during
manual operation.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
264 / 592

29.4 Rx Static Delay

Fig. 169. Rx Static Delay in auto mode

When the user stops the manual procedure by clicking on the Stop button, the status of the buttons will
turn on the initial one.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
265 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
266 / 592


210 LOOPBACKS
The functions described in this section allow to perform the test operations by loopbacks.
210.1 Hardware implementation

The loopbacks can be performed at different levels:
2 near end and 1 far end loopbacks are embedded in the IDU
2 near end loopbacks are embedded in the ODU
Some loopbacks are declared local only; this means that, when the NE receives a loopback request, the
NE executes the request only if it is arriving from the local ECT. This restriction has been introduced to
avoid the risk of a permanent disconnection from the NMS of a remote NE.
210.1.1 IDU loopbacks
[1]
Near end IDU cable loopback internal local only

Near end
IDU
Near end
ODU
Far end
ODU
Far end
IDU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
FRAME
16E1/E3
LIU
Fig. 170. Near end IDU cable loopback

[2]
Far end IDU tributary loopback internal

This loop can be activated separately on each tributary (example: in 16 E1 mode the ith trib. can
be looped independently from the others).
Assuming that an ECT is connected to the station A, the NE A uses the dedicated link connection
to activate/deactivate this loop on the remote station B. In this way, from station A, it is possible to
activate/deactivate this loop without accessing the NE B through a RECT.
It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.
Near end
IDU
Near end
ODU
Far end
ODU
Far end
IDU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
Station A
MODEM
FRAME
LIU
16E1/E3
Station B
Fig. 171. Far end IDU tributary loopback
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
267 / 592
Near end tributary loopback line

It can be activated separately on each tributary (example: in 16 E1 mode the ith trib. can be looped
independently from the others).
It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.
Nearend
IDU
Nearend
ODU
Far end
ODU
Far end
IDU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
Station A
FRAME
LIU
16E1/E3
Station B
Fig. 172. Near end tributary loopback
210.1.2 ODU loopbacks

[1]
Near end ODU cable loopback internal local only

Near end
IDU
Near end
ODU
Far end
ODU
Far end
IDU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
FRAME
LIU
16E1/E3
Fig. 173. Near end ODU cable loopback

It is executed by the NE only if it sent by the local ECT.
[2]
Near end RF loopback internal local only (N.B.)

Taking into account the HW implementation of the RF loopback, it is not necessary to switch off the
remote transmitter during a local RF loopback.
Nearend
IDU
Nearend
ODU
Far end
ODU
Far end
IDU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
FRAME
LIU
16E1/E3
Fig. 174. Near end RF loopback

N.B.
The RF loopback is executed by the NE only by the local ECT.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
268 / 592

[3]

210.2 Available Loopbacks
N.B.
The loopbacks can be activated on the local NE only.
N.B.
The DATA block in Fig. 175. is present with the Ethernet port option only.
CT
IDU
IDU
ODU
ODU
DATA
DATA
MUX/
DEMUX
MODEM
RF
RF
MODEM
MUX/
DEMUX
TRIB
TRIB
Fig. 175. Available loopbacks
Tab. 60. Available loopbacks

N.B.
Refer to:
Fig. 176. on page 270 (1+0 configurations)
Fig. 177. on page 271 (1+1 configurations)
No.
Loopback
name
CT selection in
the Resource
Tree Area
Location
E1
Port#xx
Tributaries
Near End
E1
Port#xx
Tributaries
Near End
Internal
Loopback toward the

station at tributary level.
Not available.
E1
Port#xx
Tributaries
Far End
Internal
Loopback in the remote station at

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

aggregate level.
ODU
cable
Channel 1
Near End
External line
Loopback at the ODU input at

aggregate level.
RF
Channel 1
Near End
External line
RF local loopback.
(N.B.)
WARNING:
Loopback
type
Note
External line Input loopback at tributary level.

remote
loopbacks on disabled tributaries are not applied (even if no messages are displayed when
the command is sent)
N.B.

Before activating the RF loopback, the Remote Tx must be muted (Menu Radio >
Configuration)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
269 / 592
Tributaries
(External Line)
IDU
CABLE
ODU
CABLE
Radio port
(RF loopback)
2 Channel
(External Line)
Fig. 176. 1+0 Loopback types
An active loopback is indicated by a yellow letter:
Switching status are displayed through different dynamic drawings:
If any indication does not correspond to the expected one, press Refresh to actualize the view.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
270 / 592

In Fig. 176. below is given the association of all the possible loopbacks in 1+0 configurations and their
positions in the block diagram of the equipment provided by the Summary Block Diagram View option,
available in the Diagnosis menu.

In Fig. 177. below is given the association of all the possible loopbacks in 1+1 configurations 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
5 ODU
CABLE
CABLE
Radio port
6 (RF loopback)
Tributaries
(External Line)
Channel
(External Line)
Fig. 177. 1+1 Loopback types
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
271 / 592
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.
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)
Clicking on tree root displayed in Fig. 178. below, the tree will be expanded according to NE configuration.
Fig. 178. Loopback View for PDH Tributaries (1+0)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
272 / 592

210.3 Loopback domain views

Fig. 179. Loopback View for PDH Tributaries (1+1)
Fig. 180. Loopback View for Radio PDH
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
273 / 592
Fig. 181. Loopback CABLE
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
274 / 592


210.4 How to activate a loopback

WARNING:
N.B.
loopbacks on disabled tributaries are not applied (even if no messages are displayed when
the command is sent)
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. 182. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 182. 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, it is recommended to wait 120 to 160 seconds minimum.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
275 / 592
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. 183. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 183. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
276 / 592

210.5 How to remove a loopback

211 DIAGNOSIS
This chapter describes the Diagnosis menus:
Alarms
on page 278
Log Browsing
on page 279
Remote Inventory
on page 282
Abnormal Condition List
on page 284
Summary Block Diagram View
on page 285
Current Configuration view
on page 288
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
277 / 592
This item menu allows navigation to the external tool: Alarm Surveillance.
The Alarm Surveillance application is dedicated to receive, store, display and manage, in real time, the
alarms raised by different sources (current alarms). This facilitates the overall alarm surveillance and
improves the reaction time of the network operators in case of anomalies in the network. It also provides
the possibility to archive and retrieve the alarms (historical alarms), allowing postanalysis of anomalies
in the network.
Taking into account the number of alarms that are usually emitted in a network, the Alarm Surveillance
offers the operator a systematic approach for the alarm visualization.
211.1.1 Counter Summary
This is a main window (Fig. 184. below) used to display statistics on alarms. It shows alarm counters,
according to severity levels or statuses of the alarms (critical, major, minor, warning, indeterminate,
cleared, acknowledged, incoming). In the counter summary, alarms may be grouped according to filtering
criteria in several sublists. For each sublist, each of the counters may be shown or not.
Fig. 184. Alarm Counter Summary Window
211.1.2 Alarm Sublist

The sublist is a basic working window (Fig. 185. on page 279 ). It regroups alarms according to filtering
criteria defined by the operator, allowing work on a limited subset of alarms. The sublist can also be sorted
according to criteria defined by the operator. It makes the management of current alarms easier, and
allows information classification before a possible export to a file or a printer.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
278 / 592

211.1 Alarms

Fig. 185. Alarm Sublist Window

For additional information, refer to the AS Operators Handbook (REF.[H] on page 571 of this manual).
N.B.
The list of alarms displayed by AS (both current and historical) is not easy to read and
understand, mainly due to the way in which units and functional entities are indicated in the
Friendly Name.
211.2 Log Browsing

In the Diagnosis pulldown menu, select the Log Browsing option:
Fig. 186. Log Browsing Sub Menu

The proposed options are:
select the Alarm Log option to access the Alarm Log file (N.B.)
The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.
select the Event Log option to access the Event Log file (N.B.)
The Event Log windows opens, permitting to analyze all the events stored in the NE.
select the Software Trace Log option: see para.211.2.2 on page 281
N.B.
The event and alarm store in the Event Log and Alarm Log can be inhibited or allowed by the
Log Switch function (see para.23.7 on page 218 )
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
279 / 592
By selection of Alarm Log or Event Log item, the specific Event Log Browsing Application will be
started. This application is integrated function of JEMLUSM Core.
This tool collects and shows the alarm log items (Fig. 187. below) and the event log items
(Fig. 188. below). Selecting Set Filter menu item of main menu bar, it is possible to define a filter that
can be applied to search of item.
Fig. 187. Alarm Log Display
Fig. 188. Event Log Display

For additional information, refer to the ELB Operators Handbook (REF.[I] on page 571 of this manual).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
280 / 592

211.2.1 Alarm and Event Log

211.2.2 Software Trace Log

N.B.
The use of the Software Trace Log option is reserved to the AlcatelLucent technicians.
Selecting the Software Trace Log custom item of menu displayed in the Fig. 186. on page 279 , the
application will try to download the trace log file from NE, showing a temporary information box:
Fig. 189. Transfer Information Box

If successfully, the file content will be displayed in a new window (Fig. 190. below), from which it is possible
to save or print the file.
Fig. 190. SW Trace Log
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
281 / 592
211.3.1 General
The Remote Inventory feature allows to store and retrieve the information useful to identify the
components of the product. It is also used to identify the actual equipment type and then, eventually, to
provide an equipment mismatch alarm, if the equipment type read from remote inventory data is different
from the equipment expected provided by the managers.
The AlcatelLucent factory labelling with an electronic inventory data of each replaceable hardware unit
is provided according to the AlcatelLucent standard format:
Tab. 61. Remote Inventory AlcatelLucent standard format
Information field name
Location
Length (Byte)
Encoding
Format identifier
ASCII 22
Company identifier
12
ASCII
Mnemonic (see Tab. 62. below)
36
ASCII
CLEI code
711
10
ASCII
Unit Part Number + ICS
1218
14
ASCII
Software/Firmware PN + ICS
1925
14
ASCII
Factory identifier
2627
ASCII
Serial Number
2835
16
ASCII
Date Identifier
36
ASCII 00
Date
3739
ASCII
Customer field
4062
46
ASCII
Checksum
63
Bin
Format identifier field gives information about the structure and length of the inventory data block.
The chosen identifier format is 22 (this field is not visualized to the operator).
The checksum is not visualized to the operator.
The Remote Inventory data is provided for the following equipment components:
Tab. 62. Remote Inventory mnemonic field
UNIT TYPE
MNEMONIC
IDU Main Unit
M486032
IDU Extension Unit
E486032
4xGigabit Ethernet plugin
P4DATASW
PDH Tributary optional plugsin
P16E1DS1
Audio channels, Service Channel plugin
PACSC
ODU unit
ODU32E
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
282 / 592

211.3 Remote Inventory

211.3.2 Remote Inventory display

Selecting the Remote Inventory item of Diagnosis menu, a summary screen will be displayed.
This screen is a readonly screen, which shows the remote inventory for all configured equipment.
If it is not possible to read the Remote Inventory information, a Card Fail alarm is declared.
Fig. 191. Remote Inventory screen (example)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
283 / 592
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
Fig. 192. Abnormal Condition List screen
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
284 / 592

211.4 Abnormal Condition List

211.5 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. 88. on page 183).
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
1+1 HSB with or without the Ethernet ports
1+1 FD with or without the Ethernet ports
Some examples are shown in Fig. 193. to Fig. 196. on pages 286 to 287
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.
By pressing the Refresh button the refresh of the screen takes place (active loopback and performance
and position of the switch).
N.B.
N.B.
Loopback indicator: yellow letter L means active loop.

Performance indicator: yellow letter P means active performance.
In the 1+1 configuration the current position of the switches is also shown.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
285 / 592

Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports
Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
286 / 592

Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1ETH with Audio/User Service
Channel PlugIn (Lockout)
Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service Channel
PlugIn
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
287 / 592
This screen is a readonly screen, which shows the current configuration of the NE.
Clicking on the Current Configuration view icon of the Main tool bar (see Fig. 88. on page 183) or
selecting Current Configuration view from the Diagnosis menu, the following readonly screen is
opened:
Fig. 197. Current Configuration view screen

By File Save As, screen content can be saved as text file
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
288 / 592

211.6 Current Configuration view

212 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.
212.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, ) can be derived from the quality of the aggregate
signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
The radio section monitored is:
Radio Hop Section: the section between two radio stations inside the protection section
Radio Link Section: the section identifying the protected section.
PROPR.
FRAMING
FEC
ENCODE
MODEM
RF
MODEM
RF
FEC
DECODE
PROPR.
FRAMING
Radio Hop (before the switch)

Radio Link (after the switch)
Fig. 198. Radio sections
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
289 / 592
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. 199. Performance View

The performance reports can be of 2 different types:
N.B.
15 minutes
24 hours
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.
Considering one section (see Fig. 198. on page 289), 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.
The counters supported are the following:
N.B.
Errored Seconds
Severely Errored Seconds (N.B.)
Background Block Error
Unavailable Seconds
According to ITUT G.826 a second is declared Severely Errored Second if it is a second period
with more than 30 % of errored blocks or at least one defect.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
290 / 592

212.2 Performance menu

With reference to Fig. 200. below, 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. 200. on page 291 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. 200.
Fig. 200. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
291 / 592
The window displayed in Fig. 201. below allows to start and to read the 15min PM report and 24h PM
report.
Fig. 201. Current Data View
212.3.1 CD parameters
The fields displayed in the upper part of Fig. 201. on page 292 allow the operator to check and manage
the parameter of the current data collection.
Suspect interval shows whether the current data are suspect or not.
Elapsed Time field (readonly) displays the elapsed time in the current interval of monitoring.
End Period: display time of the PM in the graphical description and in the tabular description in
the upper part of the screen. By pressing the Refresh button this time changes.
Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History
because they dont have errors.
Num. Interval supp.: number of intervals (reports) suppressed in the History because they dont
have errors.
N.B.
An interval is defined as suspect if at least one of the following conditions occurs in the
collection period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the PM data in the equipment
performance counters have been reset during the interval.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
292 / 592

212.3 CD (Current Data)

212.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 201. on page 292 (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:
N.B.
BBE (Errored block)

ES (Errored second)
SES (Severely Errored Second)
UAS (Unavailable second)
These values refer to the last refresh performed by pressing the Refresh button.
In the right part of Fig. 201. on page 292, 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
293 / 592
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.
212.4.1 HD Parameters
The table displayed on the following window (Fig. 202. below) collects the history data for a related PM
report.
Fig. 202. 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).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
294 / 592

212.4 HD (History Data)

212.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. 212.5.3 Threshold table
association.
212.5.1 How to change a threshold table
Fig. 203. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
295 / 592

212.5.2 How to create a threshold table
Fig. 204. 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.
212.5.3 Threshold table association

To each PM can be associated a Threshold Table.
To associate a Threshold Table click on HOPChannel#0 (or Channel#1) or on LINK in the Resource
Tree Area. The 15min&24h tab panel will appear.
In the Counter Thresholds field select the threshold to be associated and click on Apply.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
296 / 592

213 SW DOWNLOAD
213.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 48 SWP
download toward NE on page 485.
Fig. 205. 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:
N.B.
User Id: ftp

Password: ftp
Address: IP address of the F interface or IP address of the Ethernet interface, if present.
Port: 15,000
the System Default can be changed by writing different values in the fields and then by clicking
on button OK.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
297 / 592
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. 206. 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 2530 min. approx.
At 50% of this time starts the download to the first ODU, which lasts 1520 min. approx.
At the end of this time interval starts the download of the second ODU, if present, which
lasts 1520 min.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
298 / 592

213.2 Init SW Download

213.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. 207. below opens, giving additional
information on the software package.
Fig. 207. SW Status screen
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
299 / 592
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)
the other labels give the 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. 208. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
300 / 592

The following information is displayed on the screen:

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

From operative point of view, this management is described in para.28.3 on page 253.
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. 210. below (it depicts save/load using
floppydisk, but the operation can be done through any available read/write computer resource):
Save to
disk
Load from
disk
ECT
ECT
Fig. 210. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
301 / 592
214.2.1 MIB backup on ECT

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

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

1
2
Fig. 212. MIB save to disk phase 1

3)
The following screen appears:
a table showing the MIBs stored in the PC directory is shown
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
302 / 592

214.2 MIB management at Network Element Synthesis level and examples

select the MIB you want to save (3)

click on OK (4)
the usual window to choose a save target directory appears (5); select it and start the save
at save end, a confirmation message is shown (6) indicating also the name of the saved
folder; see N.B. on next page.
3
4
6
5
Fig. 213. 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. 214. Correspondence between MIB saved folder and MIB saved name
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
303 / 592
This operation, carried out by ECT through the Network Element Synthesis screen, allows to load a MIB
previously saved on a floppy disk into ECTs MIB area.
N.B.
This example depicts the Load from disk by using the floppydisk, but the operation can be
done through any available read/write computer resource.
1)
Launch the task as follows:
Fig. 215. Launch of MIB load from disk
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
304 / 592

214.2.3 MIB load from disk

2)
After launch of MIB load from disk, proceed as follows:
in the screen that opens, click on Browse button (1)
select the device from which carry out the load operation (2) and open it (3)
in the opened directory (4) , select the MIB folder to load (5) , then click Open (6)
Fig. 216. MIB load from disk phase 1

3)
... procedure continues
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
305 / 592

N.B.
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) .
the MIB name corresponds to that you had previously saved.
10
Fig. 217. MIB load from disk phase 2
214.2.4 MIB restore from ECT

This operation, carried out by ECT with the NE loggedin, allows to restore the MIB from ECT to NE (see
MIB restore in para. 28.3.2 on page 255).
a)
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
306 / 592


SECTION 3: INSTALLATION AND COMMISSIONING

This section provides the whole operative instructions for the equipment HW and SW installation and
commissioning.
Please read para.12.6.1 on page 59 for an introduction to the procedures of

this section.
SECTION CONTENT
PAGE
Chapter 31 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.
309
Chapter 32 LineUp and Commissioning

This chapter details all phases necessary for the equipment lineup and
commissioning.
329
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
307 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
308 / 592
USER MANUAL


31 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.12.6 on page
58.
N.B.
Procedures described in this chapter are carried out with the PC disconnected from the NE.
31.1 Requirements
31.1.1 PC characteristics
For this SWP version, correct ECT installation requires a PC with the requirements hereafter
described:
1)
HW Configuration
2)
CPU:
Pentium III 850 MHz
RAM:
512 Mbytes
Hard Disk space: 4 Gbytes
Display Resolution: 1024x768 pixel
CDROM Drive:
24X
Primary Interface: Serial Port RS232C 9.6 to 57.6 Kbits/sec.
Communication Interfaces:
Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication with

NEs 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 NEs ECT serial port
(Finterface) is required.
N.B.
In alternative, for the usage of the NEs Finterface 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 AlcatelLucent
(P/N 1AF11294AA**).
Windows Versions
Windows 2000 till SP4
Windows XP (Professional Edition only) till SP2: It is mandatory deactivate the Firewall
installed.
Windows NT partially supported: CTK 3.3 and related Q3/SNMP addon deliveries can
be run on Windows NT but you have to take in account some restrictions in Almap PC 6.5
and PC 7.0 components. They must be considered as Craft Terminal platform restrictions
in Windows NT environment.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
309 / 592
Additional SW requirements
Java Runtime Environment (JRE) version 1.4.212 or higher (the necessary version is
included in the SWP CDROM)
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 SetUp Tool and Alarms & Settings (web server) functions;
otherwise, the IP connection from the PCs web server to the NE cannot take place.
Used browser window should be at least as larger as 1024x768
In users Windows system desktop folder, files with the following names must not be
present:
Default_211.qcml
QCML_211.xsd
QCML_211.xsl
Through systems Display Properties, Settings tab, clicking on Advanced button, the
Display DPI setting should be set to Normal Size (96 DPI);
31.1.2 Operator skills and privileges

a)
The operator shall be familiar with the use of personal computers in WINDOWSNT / WINDOWS
2000 / WINDOWS XP (Professional Edition only) environment, internally to which the Network
Elements application software operates.
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) (ITUT Recommendations).
c)
For the installation of SW packages, the Operators 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 Operators Handbook (see Tab. 78. on page 571 ):
section INTRODUCTION
section GETTING STARTED
31.2 Reference Information Model

Make reference to the Product Release Note (see para.57.2.2 on page 571 )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
310 / 592
USER MANUAL

3)

31.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.1 through Ethernet interface (by CT and TCO Suite).
In this case you must carry out the following main phases:
b)
1)
1320CT Package Installation (installation of SWP components from the SWP CDROM):
2)
Local copy in PC environment of the TCO Suite:

3)
End of SW installation from SWP CDROM:

4)
NE software downloading preparation:

5)
CT initial configuration:
6)
EML construction:
Only SNMP management of 9400AWY V2.1.1 through Ethernet interface (by CT and TCO Suite),
as point a ) above, with the additional possibility of management through the NEs ECT serial port
(by CT)
In this case you must carry out the procedure described in Appendix C Additional SW installation
operations for NE management through the NEs ECT serial port on page 517
c)
N.B.
Management of SNMP 9400AWY V2.1.1 [as case a ) or b ) above] and of other SWPs for different
NEs (e.g. AlcatelLucent 9600USY, 9600LSY)
In this case, before doing anything, read carefully para.31.4 on page 312
Chapter 410 on page 497 describes how to to deinstall the Software Package from the PC.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
311 / 592
If you like to install different AlcatelLucent SWPs (1320CTbased) 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 AddOn (EMLIM)] : highest version
Craft Terminal Base Platform SNMP AddOn (EMLIM) : highest version
Craft Terminal Base Platform Help OnLine AddOn : highest version
Craft Terminal NE Type & Release Configuration AddOn: highest version

Just as an example, Fig. 218. on page 313 shows the SW components and points out the common SW
components of:
SWP 9600LSY V2.0.4
SWP 9400AWY R.2.1 V2.1.1 (which this handbook refers to)

(screens are those appearing after the SWP installation startup, as in step 5 ) on page 316).
N.B.
as far as the SWP 9400AWY R.2.1 V2.1.1 is concerned, JRE and Alcatel Lower Layers
Manager do not appear in the SWP CDROM startup screen because:
JRE is automatically installed, if necessary, according to rules explained in para.22.2.3

on page 148;
Alcatel Lower Layers Manager is installed, if necessary, on Operator explicit request only,
as explained in para.53.2 on page 519.
To make the comparison between the versions of the common SW components, please refer to the
Product Release Notes (see para.57.2.2 on page 571 ) associated to the SWPs you want to install.
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)
2)
3)
4)
5)
6)
7)
compare the PC characteristics and verify that your PC meets the highest requirements (as far
as the SWP 9400AWY R.2.1 V2.1.1 is concerned, refer to para.31.1.1 on pages 309310
uninstall all AlcatelLucent products (the clean situation simplifies the following operations)
carry out the installation of LLMAN from the SWP 9400AWY R.2.1 V2.1.1 CDROM as
described in para.53.2 on page 519, because its version is higher than that of the SWP
9600LSY V2.0.4
install the SWP 9400AWY R.2.1 V2.1.1 , as described in para.31.5 on page 314, selecting all
components, because its common SW components have versions higher than those of the
SWP 9600LSY V2.0.4
complete the SWP 9400AWY R.2.1 V2.1.1 installation as described in steps 2 ) to 6 ) of point
a ) on page 311
using the CT installation Product Guided, start the installation of the SWP 9600LSY V2.0.4,
deselecting (see following Fig. 218. ) the components JRE V1.3 , Alcatel Lower Layers
Manager V3.4.0 , CTK v3.2.0 and HOLCTKADDON v1.1.0, because already installed
(with higher versions) by the SWP 9400AWY R.2.1 V2.1.1 installation
complete the SWP 9600LSY V2.0.4 installation as described in relevant documentation.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
312 / 592
USER MANUAL

31.4 Preliminary: installation of different SWPs in the same PC

common
components
Fig. 218. Common components of different SWPs (example)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
313 / 592
N.B.
Please read carefully para.31.3 on page 311, 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.
31.5.1 Important warnings

N.B.
Windows versions supported are just those listed in point 2 ) on page 309 (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 310 (other versions
are not supported).
N.B.
Warning about Windows XP till SP2 Professional Edition:
It is mandatory to deactivate the Firewall installed.

N.B.
Windows NT is partially supported: CTK 3.3 and related Q3/SNMP addon 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 Q3CTKAddOn component.
In particular, if LLMAN component is not installed because you want to manage AWY NEs only
by Ethernet interface, also Q3CTKAddOn component has not to be installed (or has to be
explicitly deinstalled 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 Q3CTKAddOn
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.x 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 deinstall them from PC.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
314 / 592
USER MANUAL

31.5 1320CT Package Installation (installation of SWP components from the

SWP CDROM)

31.5.2 Operations sequence

Step 1. Initial checks
1)
Verify that the PC characteristics meet all HW and SW requirements specified in para.31.1.1
on page 309
2)
Verify you do have the SWP CDROM P/N REF.[a] in Tab. 53. (page 141)
3)
WARNING : whenever you have already installed a previousversion SWP V2.1.1 including the
TCO Suite, delete the existing shortcut to the Start_html icon as well as the TCOSuite folder
(see Fig. 227. on page 320). Note: it is not necessary to delete shortcut to the Start_html icon
relevant to previous SWP V2.0.x.
Step 2. Installation startup

1)
Insert the SWP CDROM in the PCs CDROM unit
2)
The TCO Suite startup begins. Please refer to para.22.2.3 for the procedure execution and
the management of special conditions that could occur
3)
At the end of the TCO Suite startup, the CDROM TCO Suite Main Menu screen appears
(Fig. 219. below); click on Advanced Settings button
Fig. 219. CDROM TCO Suite Main Menu screen
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
315 / 592
After a while, the CDROM TCO Suite Advanced Settings screen appears (Fig. 220. ); click on
1320CT Package Installation button
Fig. 220. CDROM TCO Suite Advanced Settings screen

5)
After a while, the SWP component selection screen appears (Fig. 221. ); leave all components
selected (or click on Select All button), then click on Next button
Fig. 221. SWP component selection screen and installation start
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
316 / 592
USER MANUAL

4)

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. 222. SWP component installation end, and installation report

N.B.
At any time, you can also check the components installed (Fig. 223. ) carrying out,
in Windows environment:
Start Settings Control Panel Add/Remove Programs
Fig. 223. Check of installed Alcatel SWP components

31.5.3 Next step
You have now completed the installation of the SWP components. Leave the:
SWP CDROM in the PCs CDROM unit,
and the CDROM TCO Suite Advanced Settings screen open,

and proceed with the Local copy in PC environment of the TCO Suite, para.31.6 on page 318.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
317 / 592
N.B.
Please read carefully para.31.3 on page 311, for the position of this step inside the whole
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 CDROM from the
PCs CDROM unit.
1)
In the CDROM TCO Suite Advanced Settings screen (Fig. 220. on page 316) click on Local
Copy of TCO Suite button
2)
Fig. 224. 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. 224. below shows the:
TCOSuite.206 folder, that was created installing the SWP 9400AWY R.2.0.4
TCOSuite.217 folder, that was created installing the SWP 9400AWY R.2.1.0
It is not necessary to delete them, because the Local Copy of TCO Suite from this
SWP 9400AWY R.2.1 V2.1.1 CDROM will create another folder (see Fig. 227. on
page 320).
WARNING: If you delete them, you will loose the TCO functionalities associated
respectively to the SWP 9400AWY R.2.0.4 and SWP 9400AWY R.2.1.0
Fig. 224. Local Copy of TCO Suite location choice
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
318 / 592
USER MANUAL

31.6 Local copy in PC environment of the TCO Suite

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 CDROM. The copy will proceed with a clear show
of the progress (Fig. 225. below).
Fig. 225. 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. 226. below).
Fig. 226. Copy cancelled

4)
Since Java is not systemspecific, 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. 227. ): open the TCO Suite folder [from the
location established in previous step 2 ) ], and create a shortcut to the Start.html icon on the PCs
desktop.
N.B.
Following the example of Fig. 224. on page 318, 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 preexisting SWP.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
319 / 592
New folder
(SWP V2.1.1)
OPEN
LINK
PC DESKTOP
shortcut to
TCO 2.1.1
Fig. 227. Shortcut to the TCO Suite Start icon

31.6.2 Next step
You have now completed the Local copy in PC environment of the TCO Suite. Leave the:
SWP CDROM in the PCs CDROM unit,
and the CDROM TCO Suite Advanced Settings screen open,

and proceed to the next installation step (para.31.3 on page 311), according to the case a ) or b ) you
want to achieve.
31.7 End of SW installation from SWP CDROM

Having reached this phase, you have finished the Software transfer from SWP CDROM into the PC
environment. Now, you can extract the SWP CDROM from the PCs CDROM unit.
Now proceed with NE software downloading preparation, para.31.8 below.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
320 / 592
USER MANUAL

Preexisting folders
(SWP V2.0.4 & V2.1.0)

31.8 NE software downloading preparation

N.B.
This description is retrieved from 1320CT Basic Operators 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 NEs equipment controller and the peripheral
units (such a downloading is explained in Chapter 48 on page 485).
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 174
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. 228. herebelow.
Fig. 228. Selecting SWP Administration

3)
In the screen that opens (Fig. 229. below) click on Install
Fig. 229. SWP Administrator screen
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
321 / 592
In the screen that opens (Fig. 230. on page 323 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.
WARNING:
The NE software package can also be selected from the CDROM used for the
installation of the NE software. In this case, after inserting the CDROM in the driver,
choose the following:
ect / swdw / <equipment name> / <version> / <descriptor file>
in case you have still installed in your PC one or more previous AlcatelLucent SWP, in
step [2] of Fig. 230. on page 323, 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
JUSMw2.4.7 is associated to SWP 9400AWY 2.1.1 [you can check the JUSM version
comparing it with the report produced at installation end (see Fig. 222. on page
317 )].
In any case, whenever the version to be selected in step [6] of Fig. 230. on page 323 is
not that you wanted, you can go backward to step [2] to explore the correct JUSM folder.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
322 / 592
USER MANUAL

4)

CONTINUES
Fig. 230. Directory selection for the descriptor file .DSC
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
323 / 592

End of Fig. 230. Directory selection for the descriptor file .DSC
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
324 / 592
USER MANUAL

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 48 on page 485).
Such availability can be verified (as shown in Fig. 231. herebelow) operating in the Network
Element Synthesis screen (Fig. 228. on page 321), selecting, from the Supervision pull down
menu, the File Administration and then the Software Administration option.
Fig. 231. SWP available for download to NEs

Now proceed with CT initial configuration, para.31.9 on page 326.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
325 / 592
N.B.
Procedures described in the following are carried out with the PC disconnected from the NE.
31.9.1 Craft Terminal configuration

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

1320CT Basic Craft Terminal Operators Handbook ,
chapter SOFTWARE INSTALLATION, paragraph Craft Terminal Configuration
31.9.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.22.4.2 on page 171 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
326 / 592
USER MANUAL

31.9 CT initial configuration

31.10 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. 228. on page 321).
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
SWPreleaseversion (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 Operators Handbook (see Tab. 78. on page 571)
section EML CONSTRUCTION.

An example of NE creation in the map is given in point g ) on page 176.
end of SWP INSTALLATION IN PC ENVIRONMENT procedure
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
327 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
328 / 592
USER MANUAL


32 LINEUP AND COMMISSIONING

32.1 Introduction
32.1.1 General
This chapter details all phases necessary for the equipment lineup and commissioning, providing the
user with the information needed to connect, power on, and perform a minimum turnup of an equipment
of the 9400AWY family running with the SWP 9400AWY R.2.1 V2.1.1 .
It is assumed that the mechanical installation of the INDOOR and OUTDOOR units is completed and the
antennas are installed and prepositioned. 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. 63. on page 330) are supposed
to be available.
The AlcatelLucent Software package SWP 9400AWY R.2.1 V2.1.1 must have already been installed
in the PC used as the Craft Terminal (CT) and the same software already downloaded in the equipment.
32.1.2 Conventions
To simplify the description of actions, the following symbols are in use:
Symbol used
Meaning
Manual action
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
ODU
STATION B
ODU
IDU
IDU
Network
(Supervision Side)
Network
Fig. 232. Relative positions of stations A and B
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
329 / 592
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. 63. Test and commissioning instruments

INSTRUMENT
QTY
CHARACTERISTICS
Laptop computer running the

supervisory software
The PC must have been already configured as Craft

Terminal for 9400AWY Rel.2.1.1.
If necessary, please refer to the Chapter 31 SWP
installation in PC environment on page 309 for any
related information and installation instructions you may
need.
PDH Analyzer Pattern Generator
See System configuration
V.11 G.703 Data Analyzer
See System configuration
Ethernet Data Analyzer
Optional See System configuration
Multimeter
Voltmeter AC and DC Loop tester
Light service kit cable for ODU Rx

power monitoring
see para.32.10 on page 405
TRS and SAT
Test Result Sheet and Site Acceptance Test protocol,

available as separate document
(REF.[D] on page 570)
32.1.4 SafetyEMCEMFESD norms and Cautions to avoid equipment damage

Read carefully SafetyEMCEMFESD norms in Appendix A on page 501, and Cautions to avoid
equipment damage in para.11.6 on page 36.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
330 / 592
USER MANUAL

32.1.3 Summary of the commissioning phases

32.2 Description of equipment interconnections

Following sets of drawings show the equipment interconnections at IDU level in the 1+0 (N.B.) and
1+1 configurations, according to the IDU equipment provisioning specified in Tab. 6. on page 68 :
IDU configuration
drawings on page
16E1 without plugins
332
16E1 + Audio and User Service Channel plugin
333
16E1 + Enhanced Ethernet plugin
334
16E1 + Enhanced Ethernet plugin + Audio and User Service

Channel plugin
335
32E1 without plugins
336
32E1 + Audio and User Service Channel plugin
337
N.B.
As far as the 1+0 configurations are concerned, two interconnection drawings are depicted:
one without protection boxes (the standard and cheapest solution)
the other with the protection box(es), which allows the easy expansion to the
corresponding 1+1 configuration just installing and cabling the IDU Extension unit
without altering the User line connections already existing on the IDU Main unit.
For the layouts at ODU level, refer to para.14.4 on page 101 .

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
connector pinout at User line side, in the case the protection boxes are not used. When they are used,
you can find the User line side connector pinout in this manual:
E1 Protection box
from page 79
Services Protection box
from page 84
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
331 / 592
WARNING: for 1+0 configurations, read carefully N.B. on page 331

1+0 CONFIGURATION WITHOUT PROTECTION BOXES
Alarms & Housekeepings & NMS interface cable
E1 lineside user interface cable
ODU CH1
Main
PS
1+0 CONFIGURATION WITH E1 PROTECTION BOX

E1 lineside user interface
connectors
Main
ODU CH1
PS
1+1 CONFIGURATION
connectors
Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 233. Equipment interconnections for configurations with 16E1
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
332 / 592
USER MANUAL

32.2.1 Configurations with 16E1

32.2.2 Configurations with 16E1 + Audio and User Service Channel plugin
E1 interface cable
Audio & Service channels interface cable
ODU CH1
Main
PS
1+0 CONFIGURATION WITH PROTECTION BOXES

Alarms & Housekeepings & NMS &
Audio & Service channels lineside
connectors
user interface connectors
Main
ODU CH1
PS

connectors
1+1 CONFIGURATION
Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 234. Equipment interconnections for configurations with 16E1 + Audio and User Service Channel
plugin
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
333 / 592

E1 interface cable
4 x Ethernet cables
ODU CH1
Main
PS

connectors
4 x Ethernet
cables
Alarms & Housekeepings

& NMS interface cable
Main
ODU CH1
PS
1+1 CONFIGURATION
connectors
4 x Ethernet
cables
Alarms & Housekeepings
& NMS interface cable
Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 235. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
334 / 592
USER MANUAL

32.2.3 Configurations with 16E1 + Enhanced Ethernet plugin

32.2.4 Configurations with 16E1 + Enhanced Ethernet plugin + Audio and User Service
Channel plugin
E1 interface cable

4 x Ethernet cables
ODU CH1
PS
Main

connectors
4 x Ethernet
cables
Main
ODU CH1
PS

connectors
1+1 CONFIGURATION
4 x Ethernet
cables
Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 236. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin +
Audio and User Service Channel plugin
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
335 / 592

E1 interface cables
ODU CH1
Main
PS

connectors
Main
ODU CH1
PS
1+1 CONFIGURATION
connectors
Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 237. Equipment interconnections for configurations with 32E1
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
336 / 592
USER MANUAL

32.2.5 Configurations with 32E1

32.2.6 Configurations with 32E1 + Audio and User Service Channel plugin
E1 interface cables

Main
ODU CH1
PS

connectors
Main
ODU CH1
PS
1+1 CONFIGURATION
connectors

Main
ODU CH1
PS
ODU CH0
PS
Extension
Fig. 238. Equipment interconnections for configurations with 32E1 + Audio and User Service Channel
plugin
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
337 / 592
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.
32.3.1 Turnon 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).
The hardware configuration of the equipment corresponds to the expected one.
Make visual inspection for units installation and cabling:
The IDU(s) subrack allocation according to the station layout
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 IDUODU cables ground kit connections
The ODU(s) ground connections (In the case of a nonintegrated 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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
338 / 592
USER MANUAL

32.3 Commissioning of STATION A phase 1 (Turn up)

32.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 NEs 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.22.5.2 on page 173):
1)
Connect the crossconnect Ethernet cable between the Ethernet port of the PC and the
Ethernet interface on the Main IDU (see Fig. 76. on page 170).
In alternative connect the RS232 cable between the serial port of the PC and the F interface
(ECT) on the Main IDU (see Fig. 76. on page 170).
2)
Power on the PC and wait for its startup
3)
Startup 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. 83. on page 177)
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.22.6 on page 181)
c)
Check that CT and NE versions are both V2.1.1 (for details, refer to para.12.6.3 on page 62).
If NOT, proceed as specified in Chapter 49 on page 495.
d)
Start the Quick Configuration Procedure clicking on Main Tool Bars icon Quick Configuration
(see Fig. 88. on page 183), or select Configuration Quick Configuration from the Menu bar.
The window in Fig. 245. on page 347 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 353 (Channel configuration) and confirm the Frequency Values fields.
Then, clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 and
click on Finish button. In this way the Frequency Values fields are saved in the NEs data base, and
will be available even if the ODU(s) is/are disconnected.
32.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.22.5.3 on page 180). 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).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
339 / 592
N.B.
Make sure that IDUODU 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, poweron the Main IDU then the Extension IDU if any
via the front panel power supplies switches.
The green ON LEDs on both IDUs come on.
On the IDU Main, wait 1 minute for:

n
The green EOW LED is on.
The red LDI LED is on.
The red RDI LED is on.
Always on the IDU Main, wait another 1 minute for:

n
The red MIN LED is on
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.
32.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.32.3.7 on page 343

N.B.
This is the Quick Configuration (interactive). If you want to use another modality, please
read para.32.3.6 on page 341, and proceed according to the configuration procedure you
like.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
340 / 592
USER MANUAL

32.3.4 Powering up the IDU(s) with ODU(s) disconnected

32.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.
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]
Online creation, modification and save of the NE configuration (interactive)

This is done by Craft Terminal (e.g. by Quick Configuration shortcut icon), after having logging
in the NE. For the execution of this procedure, refer to para.32.3.7 on page 343.
Quick Configuration shortcut icon

[2]
TCO Suite PreProvisioning Tool: offline 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.
For the execution of this procedure, refer to para.32.3.8 on page 344.
[3]
TCO Suite SetUp Tool: online 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 PreProvisioning Tool), or get configuration data from the NE
c ) check/modify the configuration,
d ) apply the configuration to the target NE.
For the execution of this procedure, refer to para.32.3.9 on page 345.
WARNING:
the execution of the TCO Suite SetUp Tool is denied to the Viewer operator
profile
N.B.
In alternative, through the TCO Suites Alarms & Settings function (see para.22.3 on page
156), it is possible:
to send a configuration_name.qcml configuration file to a NE (Configuration Setting,

see para.22.3.3 on page 160)
to get from a NE its own configuration_name.qcml configuration file (Get Configuration

File , see para.22.3.5 on page 164)
to get from a NE its own configuration text Report (Configuration Info , see para.22.3.4
on page 161).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
341 / 592
The bottom buttons available in the screens depend on the configuration tool started, and are
contextspecific, 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 SUITEs 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 is cancelled
Help: by clicking on this button the operator calls the helpon line
WARNING: the Help button is operative in the CT environment only. It is not operative in the TCO
SUITE environment.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
342 / 592
USER MANUAL

32.3.6.1 Note on the use of the bottom buttons available in the screens

32.3.7 Online creation, modification and save of the NE configuration (interactive)

This job can be done by Craft Terminal, after having logged in the NE.
To start this application, click on Main Tool Bars icon Quick Configuration (see Fig. 88. on page 183),
or select Configuration Quick Configuration from the Menu bar.
The window in Fig. 245. on page 347 will appear. This window is the first step of the procedure. Proceed
as specified in para.32.3.10 on page 346.
N.B.
With the Quick Configuration (interactive), 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 368.
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
343 / 592
To launch this application, click on the button PreProvisioning Tool of the TCO Suite Main Page (see
Fig. 55. and Fig. 56. on page 149).
This button is a oneclick execution for the PreProvisioning Tool. User could see a socalled splash
screen (Fig. 239. below), a temporary message that will disappear after 10 seconds or by clicking on it
with the mouse.
Fig. 239. PreProvisioning Tool splash screen

Another screen could be shown, in order to give user some details on current execution.
This screen (Fig. 240. below) is a textbased console with detailed information on execution in progress.
This window wont disappear and cant be closed by clicking on topright X button or PreProvisioning
Tool will be closed too. The window can be minimized by clicking on topright button.
Fig. 240. PreProvisioning Tool console

As soon as the PreProvisioning Tool is ready, the following screen appears:
Fig. 241. PreProvisioning 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. 245. on page 347 will appear. This window is the first step of the
procedure. Proceed as specified in para.32.3.10 on page 346, checking and modifying data as
necessary. The last step is Step L on page 368. 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).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
344 / 592
USER MANUAL

32.3.8 TCO Suite PreProvisioning Tool: offline creation, modification and save of a
provisioning file (not interactive)

32.3.9 TCO Suite SetUp Tool: online recover, modification and application of a provisioning
file (not interactive)
To launch this application, click on the button SetUp Tool of the TCO Suite Main Page (see Fig. 55. and
Fig. 56. on page 149).
User could see a socalled splash screen (Fig. 242. below), a temporary message that will disappear
after 10 seconds or by clicking on it with the mouse.
Fig. 242. SetUp Tool splash screen

Another screen could be shown, in order to give user some details on current execution.
This screen (Fig. 243. below) is a textbased console with detailed information on execution in progress.
This window wont disappear and cant be closed by clicking on topright X button or PreProvisioning
Tool will be closed too. The window can be minimized by clicking on topright button.
Fig. 243. SetUp Tool console

Then, User is asked to distinguish between Direct or Remote connection (Fig. 62. on page 156) 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.22.2.6 on page 154.
Then (Fig. 63. on page 157), User is asked to provide the Username and Password [same rules as in point
3 ) on page 179]. In case of remote connection, the NEs IP address entered in previous screen
(Fig. 62. on page 156) is displayed.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
345 / 592
Fig. 244. SetUp Tool start screen

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 Quick Configuration
(interactive)
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. 245. on page 347 will appear. This window is the first step of the procedure.
Proceed as specified in para.32.3.10 on page 346, checking and modifying data as necessary.
The last step is Step L on page 368. 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.
32.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.32.3.6.1 on page 342.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
346 / 592
USER MANUAL

As soon as the SetUp Tool is ready, the following screen appears:

Step A (Main NE parameter configuration)

Fig. 245. below appears as first window of the procedure:
DO NOT USE THIS CHOICE !
Fig. 245. Quick Configuration Procedure: main NE parameter configuration (Step A)

REMIND:
in interactive modality, this screen is set with values taken from NEs 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:
Area Site:
a)
Site name and location
Area NE Parameters Configuration

b)
Protection Type; choose between:
1+0:
unprotected configuration
1+1 HSB:
Hot Standby protected configuration
1+1 FD:
Frequency Diversity protected configuration
c)
Tributary; choose between:
16E1:
max 16xE1 without Ethernet plugin
16E1FData: DO NEVER SELECT THIS CHOICE !
16E1GData: max 16xE1 with Enhanced Ethernet plugin
32E1:
max 32xE1
N.B.
the number of actually usable tributaries depends on the employed Software Label
(see Tab. 23. on page 93 )
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
347 / 592
Power Supply Unit: in this SWP version, only PSU4860 choice is meaningful
N.B.
choices PSUVAC and PSU2460 are relevant to hardware items not presently available
e)
if equipped, click on Audio/User Service Channels plugin
f)
Market : in this SWP version, only ETSI choice is possible
Area Structure:
g)
Structure of the Radio Frame configuration : fields (Radio) Capacity and (Radio) Modulation.
The capacity implies the choice of modulation; for example, if the tributary structure is 2E1, only
4QAM modulation scheme is supported.
The association between Radio Capacity and Radio Modulation is shown in Tab. 64. below:
Tab. 64. Radio application: Capacity and modulation
N.B.
Radio Modulation
2xE1
4QAM
4xE1
4QAM / 16QAM
8xE1
4QAM / 16QAM
16xE1
4QAM / 16QAM
32xE1
16QAM
the actually usable Radio Capacity and Modulation types depend on the employed
Software Label (see Tab. 23. on page 93 )
WARNING:
N.B.
Radio Capacity
When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa)
the Tx power (in case of operation with RTPC) and the ATPC range (in case of
operation with ATPC) of the new modulation scheme must be in the correct range
(refer to para. 26.4 on page 238). 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.
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. 23.4.1 on page 210).
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. 28.2 on page 160).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
348 / 592
USER MANUAL

d)

Step B (Tributary configuration)

REMIND:

This Step B has one or two substeps:
one PDH tributary port configuration screen, see point [1] below
and four Ethernet port configuration screens (only if Enhanced Ethernet plugin installed and
configured), see point [2] on page 351
N.B.
[1]
summary information on Ethernet port characteristics and management is given in Appendix

D on page 547
PDH tributary port configuration screen
The screen shown in Fig. 246. 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. 246. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
349 / 592
In order to allow the actual configuration and transmission of the Ethernet data streams, it is
mandatory that, except the case of 32xE1 Radio Capacity:
at least one (*) PDH tributary port is disabled
and that the position (according to Fig. 246. on page 349 ) of such disabled PDH tributary port
is one of first four.
N.B.
If such operation is not done, the following error message is raised by the system
when you click on button Next to go to the next step:
so that, to go on with the procedure, you must click OK and go back to the screen of
Fig. 246. on page 349 to disable one PDH tributary port.
(*)
the allowed number of tributaries is as follows:

Tab. 65. Allowed number of PDH tributaries with Ethernet port(s) enabled
Radio Capacity
(n.b.1)
Number of allowed
PDH (E1) Tributaries
2xE1
E1 1
4xE1
E1 3
8xE1
E1 7
16xE1
E1 15
32xE1
E1 16
Number of allowed
Ethernet Ports with
Enhanced Ethernet
plugin (n.b.2)
Ethernet
Bandwidth
[N x (E1capacity)]
N2
GE 4
(10/100/1000BT)
N4
N8
N 16
16 N 32
n.b.1
the actually usable Radio Capacity depends on the employed Software Label (see
Tab. 23. on page 93 )
n.b.2
in any combination.
In the screen displayed in Fig. 246. on page 349 (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. 245. on page 347) you have defined 16E1GData, proceed to next substep [2]
on page 351
Otherwise:
to go to the next step click on button Next.
to go back to the previous step click on button Back.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
350 / 592
USER MANUAL

HOW TO OPERATE IN CASE OF CONFIGURATION WITH ETHERNET PORTS (I.E. WHEN

ENHANCED ETHERNET PLUGIN IS EQUIPPED)

[2]
Ethernet port configuration screen (with Enhanced Ethernet plugin installed)

Following configuration screens ( Fig. 247. below and Fig. 248. on page 352 ) appear only if in
Step A (Fig. 245. on page 347 ) you have defined 16E1GData.
N.B.
For whole information on Ethernet port characteristics and management, refer to the
Appendix D on page 547
Fig. 247. Quick Configuration Procedure Step B: Ethernet GPort configuration

WARNING:
for correct system initialization, it is necessary to define a value in both fields:
Speed with autonegotiation OFF

and
Capability Advertised
for all Ethernet Ports #33 , #34 , #35 and #36 , even if one or more are disabled (i.e. with Port
Status field not Enabled).
If this setting is not done, the following error message is raised by the system when you click
on button Next to go to the next step:
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
351 / 592
For detailed information on QoS configuration, refer to point [8] on page 551
To go to the next step click on button Next.
To go back to the previous step click on button Back.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
352 / 592
USER MANUAL

Fig. 248. Quick Configuration Procedure Step B: Ethernet GPort QoS configuration

Step C (Channel configuration)

REMIND:
in interactive modality, this screen is set with values taken from NEs 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.32.3.2 on page 339 ]
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. 249. :
1+0
1+1 HSB
1+1 FD
Fig. 249. Quick Configuration Procedure: Channels Configuration (Step C)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
353 / 592
[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.14.5 from page 104 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 pushbutton 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 pushbutton 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 237 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 substep [2] on page
356). (Note: if you have gone to following Step F, go back to this Step C).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
354 / 592
USER MANUAL

By this screen, you must set two types of configuration data: frequency data (substep [1] on page 354),
and ATPC data (substep [2] on page 356), 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.

2)
Non interactive mode

In the screen of Fig. 249. on page 353, click the Frequency Data Help button. The screen of
following Fig. 250. opens.
Fig. 250. Frequency Data Help: choice of ODU type

According to the ODU system to be configured, click on relevant line. The screen of following
Fig. 251. opens.
values used in
example of
Fig. 252. below
Fig. 251. 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.14.5.1 from page 105 (Part lists of ODUs with external diplexer)
para.14.5.2 from page 108 (Part lists of ODUs with embedded diplexer)
Thus, in non interactive mode, use values retrieved from such helponline tables to fill the
Frequency Values fields of screens of Fig. 249. on page 353.
Following Fig. 252. shows an example of Frequency Data manual setting with values taken
from the table of Fig. 251. above.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
355 / 592

Fig. 252. Example of Frequency Data manual setting

[2]
ATPC data setting

In the Channel Configuration area of Fig. 249. on page 353, 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 following Fig. 253. )
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 following Fig. 254. ):
strictly following rules stated in para. 26.4 on pages 238 to 240
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. 253. RTPC setting with ATPC disabled
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
356 / 592
USER MANUAL

Fig. 254. Setting of enabled ATPC

In case of 1+1 FD, two tabbed panes (as previous Fig. 253. and Fig. 254. ) are proposed for channel
0 and for channel 1 with the same choices applied.The ATPC/RTPC parameters condition for a channel
implies the same configuration for the other one.
In case of 1+1 HSB, choices will be applied to both channels (Fig. 255. below).
Fig. 255. ATPC and RTPC Configuration for both channels (1+1 HSB)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
357 / 592
The amount of microwave links, especially in urban areas, puts the problem of possible interferences
during installation and turnon 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. 256. below
or disabled deselecting 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 = A
STATION A
sent identifier = B
received identifier = 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. 256. Quick Configuration Procedure: Link Identifier configuration (Step D)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
358 / 592
USER MANUAL

Step D (Link Identifier configuration)

Step E (Automatic restoration criteria configuration)

REMIND:

This step (Fig. 257. 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 RPSHitless Switch)
Mux/Demux Protection (Tx/Rx EPS)
HSB Tx Protection (RF Hot Standby)
Fig. 257. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E)
To go to the next step click on button Next .
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
359 / 592
REMIND:

WARNING FOR NOT INTERACTIVE MODALITY:
if OSPF data are already defined in the NEs data base, when the file is downloaded to the NE,
OSPF data defined in this procedure do not overwrite those present in the NEs data base. The
only way to change such data is to use the interactive modality.
This step (Fig. 258. below) allows to configure one or more OSPF Areas (3 areas max.).
Fig. 258. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
360 / 592
USER MANUAL

Step F (OSPF area configuration)

Step G (Configuration of Local IP address, Ethernet and Network Time Protocol)

REMIND:
Fig. 259. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step G)
This step (Fig. 259. above) allows to configure:
with reference to Fig. 76. on page 170:
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 NEs Local IP and Ethernet IP addresses:
as delivered from AlcatelLucent Factory, the NEs 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
361 / 592
REMIND:
Fig. 260. Quick Configuration Procedure: Configuration of TMNRF, TMNV11 and TMNG703
channels (Step H)
This step (Fig. 260. above) allows to configure the following TMN channels:
the TMNRF interface is a communication interface based on the use of an inframe 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 TMNV11 or the TMNG703 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 TMNV11 and TMNG703 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.
Codirectional mode:
to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
362 / 592
USER MANUAL

Step H (Configuration of TMNRF, TMNV11 and TMNG703 channels)

In alternative to the TMNG703, the TMN inframe can be defined.

With this TMN inframe feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS
131) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmit
remotely this type of information along the E1#1 route; this selection is alternative to the local availability
of TMNG703 (the mutual exclusion is automatic).
It is also necessary that the farend E1#1 tributary is enabled and successfully provisioned.
To activate the TMN inframe feature, in TMN G703 field (see Fig. 261. below) :
set Mode to InFrame E1
define the required E1#1 Timeslot number (default is 1)
Fig. 261. Quick Configuration Procedure: Configuration of TMN inframe (Step H)

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
363 / 592
REMIND:

This step (Fig. 262. below) configures one or more Static Routers.
Fig. 262. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
364 / 592
USER MANUAL

Step I (IP Static Routes Configuration)

N.B.
Default Gateway Routing configuration

It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 262. on page
364 select Network Address. The screen changes to following Fig. 263. :
REMIND:
Fig. 263. 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

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
365 / 592
REMIND:
in not interactive modality, fields of this screen are with default values
This step (Fig. 264. below) appears only if the Audio/User Service Channels plugin configuration has
been defined in step A. It allows the operator to choose:
the field Phone Number in the Order Wire Configuration area allows the operator to read and
write the station number associated to the Engineering Order Wire to be used in the selective call.
Possible values are: 1099 (see chapter 42 on page 413 for details)
N.B.
Number 00 is the value associated to the general call.
the field Type in the Auxiliary Interface Configuration area allows the operator to change the
interface of the auxiliary channels (see para.13.6.4 on page 90 for details)
Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
366 / 592
USER MANUAL

Step J (EOW and Auxiliary Interface Configuration)

Step K (External Input and Output Points Configuration)

REMIND:

This step (Fig. 265. below) configures the external points (please refer to para.13.6.1 on page 85 for
physical implementation).
Fig. 265. 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

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
367 / 592
This is the last step (Fig. 266. below). The screen shown summarizes all the parameters configured during
this procedure and some relevant parameters with default values.
Fig. 266. 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 354 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.32.3.11.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
368 / 592
USER MANUAL

Step L (Summary)

32.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 reestablish the
IDUODU(s) connections.
Then, switch on the IDU(s), log in the NE and proceed to the following checks:
32.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
In the lower right window, verify in the alarms list that there is no TX failure.
Repeat for Ch#0 if any (1+1)
Fig. 267. ODU(s) alarm status
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
369 / 592
Purpose:
Verify via CT the ODU(s) transmitted power output.
Procedure:
Connect CT to IDU
. 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)
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. 268. Transmit power check
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
370 / 592
USER MANUAL

32.3.11.2 Transmitter power output check

32.3.11.3 Received power measurement

Purpose:
Verify via CT the received power to detect any interference
Procedure:
Connect CT to IDU
. 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. 269. Received power check
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
371 / 592

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. 270. Received power details
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
transmitter is in standby).
If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field
the information in dBm is 99, probably the supervision has been lost. The confirmation of the loss
of the supervision is given by a broken red icon in NES screen.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
372 / 592
USER MANUAL

32.4 Commissioning of STATION B phase 1 (Turn up)
To commission station B, perform the same operations carried on at station APhase 1 (para.32.3
on page 338).
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.32.3.11.3 on page 371, 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
404).
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 (in 1+1 configurations) to the lineside connectors of the E1
Protection box and of the Services Protection box (when the Audio and User Service
Channel plugin is equipped). When protection boxes are not employed, Station DDF is
connected directly to the IDU MAIN unit connectors.
Station DDF is not detailed in the drawings: refer to your own plant documentation for details.
For detailed information:
2)
3)
on the description of equipment interconnections (in all 1+0 and 1+1 configurations),
please refer to para.32.2 on page 331 , making reference to the equipment
interconnection diagram corresponding to your actual system layout.
in case of 1+1 configurations, regarding the description of connector pinout of:
E1 Protection box, please refer to para.13.5 on page 79
Services Protection box, please refer to para.13.6 on page 84
regarding the description of IDU MAIN unit connector pinout, in case of 1+0
configurations, where protection boxes are usually not employed, please refer to the
the Craft Terminal (CT) is always necessary.

The connection between CT and NE can be done in two alternative ways (see Fig. 76. on page
170):
trough a crossconnect 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.
the additional material for (1+1) configurations is drawn in dotted line.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
373 / 592
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.32.3.11.3
on page 371, 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 404).
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.32.5.1) in order to verify in the both stations:
n
Received level complies with hop calculation
No alarm showing (except unloaded tributaries)
32.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.
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. 271. NES window local NE
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
374 / 592
USER MANUAL

32.5 End of commissioning phase 1 (Turn up) in STATION A

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. 272. 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. 273. NMS Radio side Remote NE acquisition

N.B.
The above remote NE acquisition is described assuming that the TMNRF access have been
enabled in both Stations during Quick Configuration Procedure step H on page 362. On
the contrary, the TMNRF channel can be enabled directly through the CT menu:
CT Configuration Network Configuration IP configuration IP point to point configuration.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
375 / 592
Interfacing with the E1 Protection box, set up the following testing configuration and run on one tributary,
a minimum of one hour BER test free of error.
Remote station
ODU
ODU
IDU MAIN
IDU MAIN
E1
ERROR
ANALYZER
E1
ERROR
ANALYZER
Fig. 274. 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
ESC loopback
DATA
ANALYZER
G.703 or V11
Fig. 275. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
376 / 592
USER MANUAL

32.5.2 Testing configurations for hop quality check

32.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. 63. on
page 330). Operator will be invited to do so each time it is required by the following sentence: Report
into the TRS.

32.6.1 System Installation and cabling visual inspection
32.6.1.1 Indoor System installation and cabling inspection
See and fill the indoor inspection check list in the TRS.
32.6.1.2 Outdoor System installation and cabling inspection
See and fill the indoor inspection check list in the TRS.
32.6.2 Local configuration control
Purpose:
Verify via CT the Local Station configuration.
Procedure:
Connect CT to IDU
32.6.2.1 Check software key (Software Label) code

. CT Supervision SW key
The screen of Fig. 159. on page 256 opens.
Report the SW Key number and code into the TRS

Close.
32.6.2.2 Check/set the NE parameters and frame Configuration
. CT Configuration System Settings
The screen of Fig. 109. on page 210 opens.
If it is necessary to change any parameter, refer to para.23.4.1 on page 210
Report the Type, Market, Capacity, Modulation and Impedance into the TRS
Close.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
377 / 592
Reference screen: Fig. 129. on page 228 :

. CT Views Line Interface
In the left window
E1 port# 1
In the lower right window Configuration Tab panel.

Repeat for each E1 port#
If it is necessary to change any parameter, refer to para.25.1.2.1.1 on page 228
32.6.2.4 Check/set User Enhanced Ethernet interface parameters (Optional)

In the left window
Ethernet Port#33 or Ethernet Port#34 or Ethernet Port#35

or Ethernet Port#36
In the lower right window Configuration Tab panel.

If it is necessary to change any parameter, refer to point [2] on page 232
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
378 / 592
USER MANUAL

32.6.2.3 Check/set E1 tributaries configuration

32.6.2.5 Check/set the automatic restoration criteria (only 1+1)

32.6.2.5.1 Radio Protection
. CT Views Protection Schemes
In the left window
Radio Protection (RPS)
In the lower right window Schema Parameters Tab panel Protection Type 1+1
If required, change Operation type (Revertive or Not Revertive) then Apply
For additional information, refer to para.29.2 on page 260
Report the Operation Type into the TRS

32.6.2.5.2 Mux/Demux Protection
In the left window
Mux/Demux Protection

32.6.2.5.3 HSB Transmission Protection
In the left window
HSB Tx Protection

32.6.2.6 Check/set the Rx static delay configuration for radio protection (1+1 only)
In the left window
Radio Protection
In the lower right window Rx Static Delay Tab panel press Auto (default value)
If required, change to Manual Operation set suitable values for channel 0 and 1 then Start
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
379 / 592
Reference screen: Fig. 136. to Fig. 138. on pages 235 to 236 :

. CT Views Radio
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

If required, change the Tx frequency then Apply. Rx Freq. will be automatically adjusted
For additional information and warnings, refer to para.26.3 on page 235
32.6.2.8 Check/set TX power (ATPC Off ) or Tx range and Rx threshold (ATPC On)
ATPC Disabled:
. CT Views Radio
In the left window
Channel #1
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:
. CT Views Radio
In the left window
Channel #1
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
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then Apply
For additional information and warnings, refer to para.26.4 on page 238
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
380 / 592
USER MANUAL

32.6.2.7 Check/set TX and RX frequencies

32.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
For additional information and parameter change, refer to para.23.4.3 on page 213 , or to Quick
Configuration Procedures Step J screen described on page 366
32.6.2.10 Check/set the local NE IP address

. CT Configuration Network Configuration Local Configuration
Report the local IP Address in the TRS

Configuration Procedures Step G screen described on page 361
32.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
For additional information and parameter change, refer to para.23.2.4.3 on page 200 , or to Quick
Configuration Procedures Step F screen described on page 360
32.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
Configuration Procedures Step I , point [4] described on page 364
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
381 / 592

. CT Configuration Network Configuration Ethernet Configuration
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area into the TRS
Configuration Procedures Step G described on page 361
32.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
Configuration Procedures Step I described on page 364
32.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
Procedure:
Connect CT to IDU
. CT Diagnosis Summary Block Diagram View
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
382 / 592
USER MANUAL

32.6.2.13 Check/set the Ethernet access (OS) configuration

Fig. 276. 1+0 Summary block diagram view
Fig. 277. 1+1 Summary block diagram view
By clicking on a specific object of the drawing, the operator can navigate to the relevant CT menu view.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
383 / 592
Purpose:
lockout the channel 0 for all the duration of the channel 1 testing
Procedure:
Connect CT to IDU
. 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. 278. Channel 0 lockout mode

For additional information and parameter change, refer to chapter 29 on page 257
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
384 / 592
USER MANUAL

32.6.3.1 Channel protection switching configuration (1+1 only)

32.6.3.2 Near End Loop back functionality

Purpose:
Verify via CT the near end loopback functionality
PC with Craft Terminal software and E1 Data Analyzer
Procedure:
Connect CT to IDU
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.32.6.2.3 on page 378 for more
details about tributaries configuration)
Ensure that the local transmitter is not muted. (see para.45.9.10 on page 449 for more details about
TX Mute functionality)
IDU
MUX
DEMUX
TRIB
E1
ODU
MODEM
2
RF
4
A
N
T
E
N
N
(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 (N.B.)
N.B.

Fig. 279. Near End loopbacks points
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
385 / 592
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
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. 280. Loopback control in the CT

. CT Views Loopback
In the left window Channel #1 IDU Cable
n

Repeat for Near End IDU Cable and Near End ODU Cable
Report about the near end IDU Cable and ODU Cable loopback functionality into the
TRS
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
386 / 592
USER MANUAL

. CT Views Loopback

32.6.3.3 Far End Loop back functionality

Purpose:
Verify via CT the Far end loopback functionality
Procedure:
Connect CT to IDU
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
A
N
T
E
N
N
A
E1
A
N
T
E
N
N
A
RF
IDU
MUX
DEMUX
MODEM
STATION A
TRIB
E1
STATION B
Fig. 281. Far End loopback point

. CT Views Loopback
In the left window Tributaries TX port# FE (select the same tributary # that the one which is locally
connected to the data analyzer)
n

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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
387 / 592
Purpose:
Verify the point to point Tributaries quality

Verify the tributaries alarm status monitoring functionality
Required Instruments: PC with Craft Terminal software and E1 Data Analyzer

Procedure:
Connect CT to IDU
Connect Data analyzer on Tributary Access (At the Station DDF)
ODU
Remote station
ODU
ODU
ODU
IDU EXTENSION
IDU EXTENSION
IDU MAIN
IDU MAIN
N.B.
N.B.
Tributary loopback
E1
ERROR ANALYZER
PATTERN GENERATOR
N.B.
the diagram indicates the loopback (at remote station) and the connection (at local station)
for the first 16 E1 tributaries. To check the other ones, change connections.
Fig. 282. Test bench for tributary functionality check
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
388 / 592
USER MANUAL

32.6.3.4 Tributary functionality test

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
Verify that the analyzer detects no error.
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. 283. Tributary alarm status monitoring
Report about the Tributary BER test and alarm CT monitoring into the TRS.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
389 / 592
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
Procedure:
Connect CT to IDU
Connect Data analyzer on the service channel Access (At the Station DDF)
ODU
Remote station
ODU
ODU
ODU
IDU EXTENSION
IDU EXTENSION
IDU MAIN
ESC
IDU MAIN
ESC
ESC loopback
DATA
ANALYZER
64kbit/s (G.703 or V11)
Fig. 284. 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.
Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRS
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
390 / 592
USER MANUAL

32.6.3.5 Service data channel functionality test

32.6.3.6 Ethernet Data channel (optional) functionality test

Purpose:
Verify the point to point Ethernet Data Channels quality
PC with Craft Terminal software and 2 Ethernet Data Analyzers
Procedure:
Connect CT to IDU
Connect Data analyzer on Main IDU Ethernet Access.
Test bench for Enhanced Ethernet plugin (4xGigabit Ethernet plugin) equipped: Fig. 285. below
Perform 10 minutes of BER test on both Optional Ethernet access.
Verify that the Data analyzer detects no error.
Report about the Ethernet Data Channels BER test into the TRS.
ODU
Remote station
ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
IDU EXTENSION
ETHERNET DATA
ANALYZER
ETHERNET DATA
ANALYZER
Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit Ethernet plugin)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
391 / 592
Purpose:
Verify via CT the Transmitted (Ptx) and received (Prx) power
Required Instruments: PC with Craft Terminal software

Procedure:
Connect CT to IDU

. 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
Pressing Start will prompt a graphic monitoring view of the transmitted and received levels (see Fig. 142.
on page 242 ):
Ticking the box show details in the lower left corner will call a summary view of the TX an Rx levels
(see Fig. 143. on page 243 )
Report the Current Tx Local End (Ptx) and the current Rx Local End (Prx) into the TRS.
For additional information, PTx and PRx levels software readings tolerance and warnings, refer to
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
392 / 592
USER MANUAL

32.6.3.7 Ptx and Prx measurement

32.6.3.8 Inside hop Engineering Order Wire functionality test (optional)

ODU
Remote Station
ODU
ODU
EXTENSION
ODU
MAIN
EXTENSION
MAIN
TPH
OFF ON
EOW
1
4
7
2
5
8
0
3
6
9
OFF ON
Fig. 286. 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 twodigit 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
393 / 592
32.6.4.1 Channel protection switching configuration

Purpose:
Forced the channel 1 for all the duration of the channel 0 testing
Required Instruments: PC with Craft Terminal software

Procedure:
Connect CT to IDU
. CT Diagnosis Protection Schemes

In the left window
Radio Protection Main#1
In the lower right window Command scroll list Forced Apply

n
Check in the summary block diagram that the full channel 0 (Tx and Rx) path is in service.
Repeat for:
the Mux/Demux Protection (see para.29.1 on page 258 )
and, only for HSB systems, the HSB TX Protection (see para.29.3 on page 262 )
Report about the Channel 0 protection Switching functionality into the TRS
Fig. 287. Channel 1 forced mode

Note :
0. In both cases, the result is that the relevant channel protection path is forced to standby
status.
For additional information and parameter change, refer to chapter 29 on page 257
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
394 / 592
USER MANUAL

32.6.4 Channel 0 functionality tests (1+1 only)

32.6.4.2 Near End Loop back functionality

Repeat the same test already performed for channel 1.
Report the results into the TRS.
32.6.4.3 Far End Loop back functionality

32.6.4.4 Tributary functionality test

32.6.4.5 Service data channel functionality test

32.6.4.6 Ethernet Data channel (optional) functionality test

32.6.4.7 Ptx and Prx measurement

32.6.4.8 Inside hop Engineering Order Wire functionality test

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
395 / 592
Purpose:
Verify the Hop stability
Procedure:
Connect CT to IDU
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)
Via the CT, let only one active tributary in both station
In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).
In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the Tributary
Alarm Loss disappears.
Verify in both stations that there are no active software loopbacks or switching requests
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 EXTENSION
IDU MAIN
IDU MAIN
Tributary loopback
E1
ERROR ANALYZER
PATTERN GENERATOR
Fig. 288. Test bench for hop stability test
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
396 / 592
USER MANUAL

32.6.5 Hop stability test

32.6.6
NE integration tests
32.6.6.1 NMS Radio side acquisition

Purpose:
Procedure:
Verify Via CT the remote NE RF side acquisition

Connect CT to IDU
NE Radio side acquisition has been already performed during the Turn Up (commissioning phase 1).
Refer to para.32.5.1 on page 374 for more details.
32.6.6.2 NMS Line side acquisition (if foreseen in the plant documentation)
Purpose:
Procedure:
Verify Via CT the remote NE line side acquisition

Connect CT to IDU
Toward station B
ODU
Direction 2
ODU
Local Station (Station A)
IDU MAIN facing station B
V11
or
G703
IDU MAIN Direction 2
Fig. 289. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
397 / 592
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. 290. NES window local NE
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. 291. 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
398 / 592
USER MANUAL


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. 292. 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
399 / 592
Direction 1
ODU
Direction 2
ODU
Local Station
OFF ON
AUDIO 1
or
AUDIO 2

OFF ON
Fig. 293. 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 twodigit 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
400 / 592
USER MANUAL

32.6.6.3 EOW line side call (if foreseen in the plant documentation)

32.6.6.4 Housekeeping alarms setting and testing (if foreseen in the plant documentation)
N.B.
For additional information not given here, refer to chapter 27 on page 247
32.6.6.4.1 External alarm inputs

Note: These tests should be performed only in specific sites requested by the Customer.
Purpose:
Procedure:
Configure and test Via CT the housekeeping external alarm inputs

Connect CT to IDU
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)
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.13.6.1 on page 85.
Verify in the CT External points view that CPI 1 is showing an alarm.
Repeat with CPI 2 to 6.
Report about the House keeping input alarms acquisition into the TRS.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
401 / 592
Purpose:
Configure and test the housekeeping equipment alarms outputs
Required Instruments: PC with Craft Terminal software and Multimeter (loop tester)
Procedure:
Connect CT to IDU
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
External State On Apply
Then, to activate the remote control
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
Testing a remote control alarm Output:
z
Connect a multimeter (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.13.6.1 on page 85.
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).
Repeat with CPO 2 to 4.
Report about the House keeping Output alarms detection into the TRS.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
402 / 592
USER MANUAL

32.6.6.4.2 Alarms outputs

32.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
32.8 Final operations

As introduced in para.12.6.1 on page 59, complete the commissioning of each NE, creating the NE
operator profiles and saving its data.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
403 / 592
Safety rules for Microwave radiations (EMF norms):

read carefully para.51.3.8 on pages 507 onwards
Antenna prepointing should have been done during equipment hardware installation described in the
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.32.10 on page 405)
d)
proceed with Vertical alignment, then with Horizontal alignment, as described in the Installation
Handbook (N.B.)
e)
in configurations with two antennas, repeat the procedure for the second antenna.
N.B.
procedures for Vertical and Horizontal alignment depend on the type of integrated pole
mounting employed. All integrated pole mounting types are described in the Installation
Handbook.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
404 / 592
USER MANUAL

32.9 Annex A: fine antenna alignment

32.10 Annex B: light service kit cable operative information

Fig. 294. herebelow shows this optional cable (P/N 3CC 13477 AA**):
10
10
11
11
12
12
Black
B
D
Red
7
12
8
7
12
8
4
10
1
9
2
1
9
11
5
View following F
6
11
5
3
View following G
4
10
LEMO wire 6 = ground

Fig. 294. Light service kit cable
Connector usage:
(A) LEMO connector, to be plugged into LEMO connector on ODU (see Fig. 46. on page 120 and
Fig. 47. on page 121)
(B) LEMO connector, for AlcatelLucent internal use only.
banana plugs (C) and (D) : output is a 0 to +3V DC voltage proportional to the radio Rx field. During
equipment lineup, through a multimeter 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.26.5 on page 241).
(E) RS232 connector, for AlcatelLucent internal use only.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
405 / 592

a)
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
406 / 592
USER MANUAL

SECTION 4: MAINTENANCE AND UPGRADE

This section contains the whole logical and operative information for the equipment maintenance and
system SW and HW upgrade.
SECTION CONTENT
PAGE
MAINTENANCE
Chapter 41 Maintenance Policy
It introduces the basic concepts for the equipment maintenance.
409
Chapter 42 Set and use of EOW functions

It explains how to configure and use the Engineering OrderWire functions of the
equipment.
413
Chapter 43 Maintenance Tools and Spare Parts

It describes the instruments, accessories and the equipment spare parts that are
envisaged to carry out the routine and corrective maintenance of the equipment.
415
Chapter 44 First Level Maintenance

It describes the First Level Maintenance (system state display) of the equipment.
421
Chapter 45 Second Level Maintenance

It describes the preventive and corrective maintenance of the equipment.
429
Chapter 46 Spare Flash Card management and replacement procedures

This chapter describes how to manage the spare Flash Card and how to replace
it, in case of problems.
465
UPGRADE
Chapter 47 System hardware upgrade
This chapter details all phases necessary to install tributary plugins, or to upgrade
9400AWY system from (1+0) to (1+1) configuration, or to replace the Flash Card
to improve system capacity.
469
Chapter 48 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 NEs Flash Card.
485
Chapter 49 ECT & NE upgrade from V2.1.0 to V2.1.1

This chapter details all phases necessary to install a new SWP version in the PC
environment as well as in the equipment environment, in both stations A and B of
the radio link.
495
Chapter 410 SWP deinstallation

This chapter describes how to deinstall from the PC the Craft Terminal Software
Package components.
497
USER MANUAL
MAINTENANCE AND UPGRADE
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

407 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
408 / 592
USER MANUAL

41 MAINTENANCE POLICY
This chapter introduces the basic concepts for the equipment maintenance.
41.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 43 on page 415.
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 44 on page 421.
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 45 on page 429.
With regard to the access to the Craft Terminal functionalities as well as to the TCO Suite
NEinteractive 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 twostation 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 42 on page 413.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

409 / 592
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.
41.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.57.2.1 on page 569 is usually not enough to properly maintain equipment.
41.4 Troubleshooting organization

[1]
[2]
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 (backpanel, connectors, etc.)
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 NEinteractive functionalities
F interface for the Craft Terminal (Local or Remote)
LEDs located on the NEs units.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
410 / 592
USER MANUAL

41.2 First Level Maintenance Personnel skill

[3]
Usually, maintenance is firstly done via software (TMN or Local/Remote Craft Terminal or the TCO
Suite NEinteractive 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)
b)
c)
d)
the equipment is not managed by a TMN or by a Remote Craft terminal (RCT).

the equipment is not reachable by the remote manager (TMN or RCT) and therefore is
isolated.
link problems are present.
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:
[5]
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.
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. 45.8 on page 436.
To correctly execute the troubleshooting operations the technician must know the
equipment configuration (see Equipment applications on the Craft Terminal).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

411 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
412 / 592
USER MANUAL

42 USE OF EOW FUNCTIONS

Please refer to chapter 41 on page 409 for an introduction to the basic concepts of equipment
maintenance.
This chapter explains how to configure and use the EOW (Engineering OrderWire) function of the
equipment.
42.1 Setting information

The EOW functions are possible only in the IDU MAIN unit configurations equipped with the AUDIO +
USER SERVICE CHANNEL plugin.
The telephone handset (P/N REF.[1] in Tab. 24. on page 96) allows to carry out EOW in/out calls at IDU
side. It uses DTMF (tone) dialling.
a)
Connection diagram
1
4
7
*
2
5
8
0
3
6
9
#
OFF ON
STATION A
STATION B
ODU
ODU
IDU
IDU
MAIN UNIT
MAIN UNIT
1
4
7
2
5
8
0
OFF ON
Telephone handset
Telephone handset
N.B.
3
6
9
#
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 handsets RJ11 plug to TPH connector on the IDU
MAIN unit [ (7) in Fig. 21. on page 70 ].
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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

413 / 592
Telephone handset phone number display/setting

Display/setting is done:
by Quick Configuration Procedure (see Step J on page 366 )
or by Craft Terminal with the following menus (refer to para.23.4.3 on page 213 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:
f)
SELECTIVE:
OMNIBUS:
a connection between two users (dial a number: 10 to 99)

a unidirectional connection with all the users (dial digits 00)
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
RED
RED
GREEN
YELLOW
YELLOW
42.2 Call Setup/End by Telephone handset connected to the IDU Main unit
a)
To Call from Handset:

1)
2)
3)
4)
5)
6)
b)
To Answer Call at Handset:

1)
2)
c)
Check that line is free (EOWfree green LED on the MAIN unit is on)
Set Handset ON/OFF switch to ON
On keypad, press # to engage line
Check that EOWbusy yellow LED on the MAIN unit is on
On keypad, dial twodigit number of station to be called (or 00 for omnibus call)
Ring tone is audible in the handset, wait for answer
EOWbusy yellow LED on the MAIN unit flashes and audible tone is present
If not connected, connect handset to IDU, set ON/OFF switch to ON, press # on keypad, speak
To End Call from Handset:

1)
2)
On keypad, press *
Move handset ON/OFF switch to OFF
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
414 / 592
USER MANUAL

d)

43 MAINTENANCE TOOLS AND SPARE PARTS
43.1 Introduction
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 Tool Kits

on page 416
Set of spare parts
Types of Spare Parts
Number of Spare Parts
General rules on spare parts management

on page 418
on page 419
on page 419
43.2 Instruments and accessories

43.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 summedup in para.45.8 on
page 436.
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.22.4.1 on page 170 for an overview on the physical interfaces for the NE
management.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

415 / 592
For the P/Ns of these Tool Kits, please see REF.[2] , [3] and [4] in Tab. 24. on page 96 .
a)
The Installation Tool Kit 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 Tool Kit is practically equal to the Station Tool Kit, with the addition of the
Antistatic wristband.
c)
The Station Tool Kit is a bag additionally containing various types of cables and cable adapters.
The detailed item list of these Tool Kits is given in Appendix F from page 563 :
N.B.
Installation Tool Kit part list,
MaintenanceTool Kit part list, para.56.2 on page 564
StationTool Kit part list,
These Tool Kits are standardized kits for the use with all AlcatelLucent 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 Tool Kits
SPECIAL ITEM
DESCRIPTION
COMPONENTS OF ANTISTATIC WRISTBAND

Antistatic wristband
Antistatic applications cord
Fig. 1. on page 36
Plug with crocodile pliers

Female button termination
SPECIAL EXTRACTORS
Unhook tool for 1.0/2.3 coax
Fig. 295. below

SPECIAL TOOLS AND ITEMS FOR ODU
Lever for ODU mounting/dismounting
Fig. 296. on page 417
Fig. 295. Special extractor to remove the coaxial cables 1.0/2.3
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
416 / 592
USER MANUAL

43.2.2 Maintenance, Installation and Station Tool Kits

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.
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. 296. Lever for ODU mounting/dismounting

USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

417 / 592
43.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 sparepart stock correspond
exactly to the plugin replaceable units that are equipped in the system (i.e. with the same Part Number).
43.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 ODUs with embedded diplexer: the complete ODU.

For the P/Ns refer to para. 14.5.2 on page 108.
for ODUs with external diplexer: the TRANSCEIVER assembly. For the P/Ns refer to:
Tab. 27. on page 106 (7 GHz)
Tab. 29. on page 107 (8 GHz)
As a matter of fact, all other ODUrelated items listed in Chapter 14 on page 97 (but whose P/Ns are
given in the Installation Handbook) can be considered items to be provisioned as spare parts.
43.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.13.1 on page 68.
N.B.
b)
In case a terminal has IDU Main and/or Extension units equipped with plugin(s), and you
order as spare parts such units separately from the plugin(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 plugin must be installed, at last box must be closed.
Spare parts for Flash Card

There are various possible types of Flash Cards. For details refer to para.13.7 on page 93 .
For the sparepartstock, 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 64Mb 16 QAM could be provisioned instead.
N.B.
Read important information regarding the spare Flash Card management in para.46.1
on page 465.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
418 / 592
USER MANUAL

43.3 Set of spare parts

43.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.
43.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 antistatic 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

419 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
420 / 592
USER MANUAL

44 FIRST LEVEL MAINTENANCE

44.1 Introduction
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 423
44.2 System state display by visual indications

44.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. 298. on page 422: 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. 297. below: while pushed, all leds of EXTENSION unit should be turned on.
44.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. 298. on page
422.
44.2.3 Alarm LEDs on the Extension unit
(3) LED test
GREEN
(2) ON/OFF switch
LED
ON (green)
Normal status
ON (if the ON/OFF switch is on)
Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

421 / 592

(3) Ethernet (or

OS) interface
for Craft Terminal
GREEN
RED
RED
RED
RED
YELLOW
(2) ON/OFF switch
(10) Reset
(11) LED test
(9) Alarm attending
(12) F interface for

Craft Terminal
LED on
Meaning
Action
Green LED ON
If off (and if the ON/OFF switch is on) there is a problem in the station
battery or in the MAIN unit
Red LED LDI
There is a failure in the equipment
Red LED RDI
There is a failure in the remote station
Red LED MAJ
Detection of an URGENT alarm: it means that there is at least one

alarm (internal and/or external) for which traffic is affected.
Red LED MIN
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.
something is wrong, but the traffic is recovered by an automatic
protection switch).
Yellow LED ATTD
Alarm condition ATTENDED: it means that an Operator (by pushbutton

(8) or by Craft Terminal) has attended the alarm (for details, see para.
45.6.2 on page 434).
ACTION:
A
The immediate intervention of a Second Level Maintenance Operator is required.
The immediate intervention of a Second Level Maintenance Operator is not required

Fig. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
422 / 592
USER MANUAL

44.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 NEs IP address.
44.3.1 Viewing the NE alarms by TCO Suite

Proceed as follows:
1)
startup the TCO Suite Alarms & Settings function as explained in para.22.3.1 on page 156,
using:
the NEs 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. 64. on page 157), click on button
Active Alarms
3)
refer to para.22.3.6 on page 165 for the alarm screen interpretation.
4)
at the end, close the TCO Suite Alarms & Settings Active Alarms screen.
44.3.2 Viewing the NE status by Craft Terminal

Proceed as follows:
1)
login the NE as explained in para.22.5.2 on page 173, using:
the NEs IP address (if remote NE)
the Username and Password

communicated by the Station Manager.
2)
the 9400AWY Main view opens (see Fig. 87. on page 181).
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
181183)
for screen interpretation, refer to para.211.5 on page 285.
USER MANUAL
in the Main tool bar (see Fig. 87. and Fig. 88. on pages
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

423 / 592
3)
Checks on Radio domain

Various checks are possible selecting the specific matters of the Menu bar, as shown in
following Fig. 299. to Fig. 304.
For screen interpretation, click on their relevant HELP button and/or refer to chapter 26
on page 233.
at the end:
first, carry out the NE Logoff as explained in para.22.5.3 on page 180
then, close the 1320CT application as explained in para.22.5.4 on page 180.
RADIO MENU BAR
Fig. 299. Checks on Radio domain : Alarms
Fig. 300. Checks on Radio domain : Configuration
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
424 / 592
USER MANUAL

b)
Fig. 301. Checks on Radio domain : Frequency
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
425 / 592

Fig. 303. Checks on Radio domain : nonintrusive BER measurement
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
426 / 592
USER MANUAL

Fig. 302. Checks on Radio domain : RTPC & ATPC
Fig. 304. Checks on Radio domain : Power Measurement
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
427 / 592

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
428 / 592
USER MANUAL

45 SECOND LEVEL MAINTENANCE

45.1 Introduction
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
EMC norms
Safety rules

Routine (preventive) Maintenance
Consequences of unit extraction in the IDU
Corrective Maintenance general flowchart
Alarm acknowledgment and attending
TroubleShooting starting with visual indications
TroubleShooting via Craft Terminal
Alarm and status synthesis indications
Details on alarms / statuses
Description of alarms and of probable causes

Hints on the troubleshooting
IDU Unit replacement
ODU replacement
Faulty unit repair and Repair Form
on page 431
on page 432
on page 433
on page 434
on page 435
on page 436
on page 437
on page 439
on page 440
on page 442
on page 451
on page 460
on page 463
The handbook parts that should be read (or known) before starting this chapter are:
chapter 12 on page 37
USER MANUAL
System overview
IDU provisioning and description
ODU provisioning, characteristics and description
Maintenance Policy
Maintenance Tools and Spare Parts
First Level Maintenance
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

429 / 592
45.2.1 EMC norms
ATTENTION
EMC NORMS
WHEN CARRYING OUT THE GIVEN OPERATIONS OBSERVE THE NORMS STATED IN PARA.
51.4.3 ON PAGE 509
45.2.2 Safety rules
The Safety Rules stated in para.51.3 on page 502 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 frontpanel warning labels prior to working on optical
connections while the equipment is inservice.
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, lowvoltage,
lowimpedance, 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.
45.2.3 Cautions to avoid equipment damage
Read carefully para.11.6 on page 36.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
430 / 592
USER MANUAL

45.2 Warnings

45.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. 45.8.4 on page 441, allows this function.
45.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.51.3.6
on page 506).
[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, lowvoltage,
lowimpedance, 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.44.2
on page 421.
Checks by Craft Terminal
some suggested checks are indicated in para.44.3 on page 423
the commissioning tests, described in Chapter 32 on page 329, can be useful to carry
out equipment functional checks as a whole, in particular as far as checks on radio hop
are concerned.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

431 / 592
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:
b)
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.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
432 / 592
USER MANUAL

45.4 Consequences of unit extraction in the IDU

45.5 Corrective Maintenance general flowchart

START
Alarm acknowledgment and attending
(para.45.6 page 434)
TroubleShooting starting with visual indications

(para.45.7 page 435)
TroubleShooting starting via Craft Terminal
(para.45.8 page 436).
Identification of a unit to be replaced.
IDU unit replacement

(para.45.10 page 451)
ODU replacement
(para.45.11 page 460)
System check via Craft Terminal

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

Repair Form compiled (para.45.12 on page 463)
END
Fig. 305. Corrective Maintenance general flowchart
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

433 / 592
45.6.1 Alarm acknowledgment

Refer to Fig. 305. on page 433, for the position of this step inside the corrective maintenance general
flowchart.
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. 45.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.
45.6.2 Alarm Attending

See Fig. 298. on page 422:
the detected alarm condition can be stored through the Alarm attending pushbutton 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
434 / 592
USER MANUAL

45.6 Alarm acknowledgment and attending

45.7 Troubleshooting starting with visual indications

flowchart.
Some problems may be localized through the LEDs indicated in para. 44.2 on page 421.
In any case, the inspection through the Craft Terminal is recommended before any unit replacement.
Flowchart of Fig. 306. indicates LEDs on the MAIN unit that should be considered first.
START
N
END
MAJOR, MINOR,
LDI or RDI LED
on the MAIN unit
is ON
Y
Try login NE by Craft Terminal
Y
Login successful ?
Carry out procedure in
para.45.8 page 436
Carry out procedure in

para.45.9.1 page 442
Fig. 306. Troubleshooting starting with visual indications
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

435 / 592
flowchart.
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.45.8.1 below
Alarm surveillance
Loopbacks
para. 45.8.3 on page 441
Operators Controls of the protection switches
Tx mute functions
Performance Monitoring
BER measurement
Commissioning tests
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.45.10 on page 451
for IDU, or to para.45.11 page 460 for ODU).
45.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 AlcatelLucent
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 211 on page 277.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
436 / 592
USER MANUAL

45.8 Troubleshooting via Craft Terminal

45.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 438 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 45.8.2.2 on page 439 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.
45.8.2.1 Alarm and status synthesis indications

The following Tab. 67. pertains to the alarm and status synthesis given in all the screens, pointed out in
this Fig. 307. :
Fig. 307. Alarm and status synthesis indications
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

437 / 592
Mnemonic
Alarm / Status Description
Maintenance
CRI
Critical alarm
Synthesis of alarms that needs immediate

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

can be decided. (N.B.)
WNG
Warning alarm
Synthesis of alarms due to failure of other NE in the

network. (N.B.)
IND
Indeterminate alarm
Synthesis of alarms not associated with the previous

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

input housekeeping indication.
EQP
Equipment alarm
Synthesis of alarms of the Equipment domain.
TRS
Transmission alarm
Synthesis of alarms of the Transmission domain.
Local Access state

(see para.211.2 on page 279)
GREEN LED: Indicates that the Craft Terminal has

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

state of the connection between NE and Craft Terminal
( SDH service link up ).
RED LED: Identified the Disable operational state
of the connection between NE and Craft Terminal
( service link down ).
SUP
Supervision state
GREEN LED: NE is under supervision.

BROWN LED: NE is not under supervision.
Used in the OS.
ALI
Alignment
Alignment status of the SH MIB respect to the

equipment MIB.
OS
Operation System
(see para.211.2 on page 279)
GREEN LED: Indicates that the N.E. is not managed by

the 1353NM/SH.
CYAN LED: Indicates that the N.E. is managed by the
1353NM/SH.
Network Time Protocol
GREEN LED: NTP protocol enabled and both NTP

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

CYAN LED: Detection of an ABNORMAL operative
condition. Type: switch forcing.
NTP
AC
N.B.
that
needs
immediate
The Alarm Profile can modify the assignment of each alarm root to the various synthesis.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
438 / 592
USER MANUAL

Tab. 67. Alarm Synthesis indications

45.8.2.2 Details on alarms / statuses

The troubleshooting proceeds by checking the detailed information on the NE active alarms using the Craft
Terminal as in Fig. 308. 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 subnode) in the Resource Tree Area to check if some alarms are active.
[3]
Select the Alarm tab panel in the Resource Detail Area.
[4]
If the node has subnodes put a tick in the Include alarms from subnodes field to display the
alarms active also in the subnodes.
[1]
[2]
[3]
[4]
Fig. 308. Active alarm screen

Detailed information of some alarms are supplied.
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 440 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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

439 / 592
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
AIS detection on the tributary in Tx Check the

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

(propagation problem)
Dem fail
Demodulator failure affecting the

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

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

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

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

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

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

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

signal)
LOF of the Rx aggregate signal
Check the link (errors)
Loss Of Signal
LOS at the Tx tributary input
Check the line
Low BER
Low BER at the Rx side
Check the
problem)
Mod fail
Internal modulator failure affecting

Replace the ODU
the modulated signal
Mod LOS
No signal at the modulator input
Investigate by using the loopback

facilities with the CT.
Remote Defect Indication
Alarm active in the remote station
Check the remote station
Replaceable Unit Problem
Problem on a replaceable unit
Replace the unit
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
440 / 592
tributary
link
connected
(propagation
Replace the ODU; if the alarm is still

active replace the cable.
link
connected
(propagation
USER MANUAL

45.8.2.3 Description of alarms and of probable causes

Tab. 69. General issues of the alarm meanings and their respective maintenance actions
ALARM
Replaceable Unit Type
Mismatch
MEANING
MAINTENANCE ACTION
Mismatch between the installed unit Change the unit configuration or

and the sw configured unit
change the unit
Replaceable Unit Type Missing No unit in a configured slot
Install the unit
Rx Fail (Radio alarm)
No RF received signal
Check the
problem)
Threshold Cross
Performance threshold has been

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

Download the software version
between CT software and
equipment software
Housekeeping
Active input housekeeping
link
(propagation
Replace the ODU
Check the housekeeping
45.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. The loopbacks are explained in Chapter 210 on page
267.
45.8.4 Operators Controls of the protection switches
In certain troubleshooting conditions, changing the state of the protection switches can be useful to fix
problems.
45.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.
45.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 212 on page 289.
45.8.7 BER measurement
The BER measurement (noonintrusive) can be carried out as described in para.26.6 on page 246
45.8.8 Commissioning tests
In some cases, the commissioning tests, described in Chapter 32 on page 329, can be useful to carry out
equipment functional checks as a whole, in particular as far as checks on radio hop are concerned.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

441 / 592
This paragraph gives hints on following matters:
Problems with the Craft Terminal

below
PC restart
Craft Terminal not working on NEs local Ethernet interface
Craft Terminal not working on NEs Finterface
Craft Terminal blocked
Checks before MAIN unit or FLASH CARD replacement
Analog measurements
NMS 64 kbit/s V.11 and G.703
Loopbacks
Empty USM icon in NES
Remote NE unreachable
Configuration change from 4 QAM to 16 QAM
Quick configuration menu correct use
Abnormal condition list
Tx Mute functionality for interferences investigation
Tributaries 17 to 32 visible in 16E1+Ethernet configuration
on page 443
on page 444
on page 445
on page 445
on page 446
on page 447
on page 447
on page 449
on page 450
45.9.1 Problems with the Craft Terminal

With regard to the PC maintenance, refer to the constructors documentation.
45.9.1.1 PC restart
Should the Craft Terminal Software Product not be working properly or not responding to the operators
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 45.9.1.2 (Ethernet interface usage) or 45.9.1.3 (F interface
usage), till paragraph 45.9.1.5 on page 445.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
442 / 592
USER MANUAL

45.9 Hints on the troubleshooting

45.9.1.2 Craft Terminal not working on NEs local Ethernet interface

Proceed with the following checks:
Verify that the CT Ethernet port is effectively that connected by a crossconnect cable to the MAIN
UNIT Ethernet interface on the left (see Fig. 76. on page 170; 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. 55. and Fig. 56. on page 149),
and answer to question of Fig. 77. on page 174 specifying Ethernet interface usage.
Disconnect and then reconnect, at PC side, the Ethernet cable; this message should arise at
reconnection:
Otherwise:
the cable could not be the required crossconnect 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 AlcatelLucent equipment. If the problem still persists, solve the problem.
Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in
para.45.9.1.5 on page 445.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

443 / 592
Proceed with the following checks:
Verify that the CT serial port is effectively that connected by cable to equipments 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 PCNE Finterface usage) has not been carried out: refer to Appendix C on
page 517 to know what to do.
Check for the Network Connections order (para.53.3.6 on page 546).
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. 55. and Fig. 56. on page 149),
and answer to question of Fig. 77. on page 174 specifying F interface usage.
Check that speed is the same:
at PC side (see para.55.7.3 on page 562)
at NE side through the TCO Suite Alarms & Settings function (see para.22.3.1 on page 156,
and para.22.3.9 on page 167).
With the Craft Terminal connected to the equipment Finterface, open the Alcatel Lower Layer
in the MSWindows
Manager screen (by clicking with the mouse pointer on the Alcatel symbol
menu bar, or by Start Programs Alcatel Lower Layers Lower Layers Manager, and
interpret the various fields of the screen that opens (Fig. 309. below) as described in the 1320CT
Basic Craft Terminal Operators Handbook (see Tab. 78. on page 571), chapter Software
Installation, paragraph Communication with NE.
Link led
Fig. 309. 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 Finterface 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 AlcatelLucent equipment. If the problem still persists, solve the problem.
Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in
para.45.9.1.5 on page 445.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
444 / 592
USER MANUAL

45.9.1.3 Craft Terminal not working on NEs Finterface

45.9.1.4 Craft Terminal blocked

In some situations, the CT is blocked (not temporarily) and, even if 1320CT application is closed by
TaskManager and then relaunched 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 relaunch 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)
loggingout and then reloggingin 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
TaskManager. 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 !
45.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.45.10.1 on page 452.
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.46.2 on page 466.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

445 / 592
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 B
IDU
Station A
IDU
45.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 Procedures Step H on page 362
45.9.4 Loopbacks
For a correct activation of every loopback (Loopback menu):
the relevant tributary must be enabled (Quick Configuration Procedures Step H point [1] on page
349 )
the local transmitter must be not muted (CT Menu Radio Configuration)
Note 1: The loopback will become active after 67 sec. approx. (24 sec. approx. for the RF loopback).
Note 2: The time for a new set is 10 to 25 sec. approx.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
446 / 592
USER MANUAL

45.9.2 Analog measurements

45.9.5 Empty USM icon in NES

Enter Windows Task Manager and stop the process relevant to the empty USM.
45.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.
45.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.
45.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 viceversa for the E1 signal both in the Local and Remote NE).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

447 / 592
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. 310. Abnormal condition list
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
448 / 592
USER MANUAL

45.9.9 Abnormal condition list

45.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. 311. 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 setup the channel, because the remote address is
not known, and, any case, to setup the channel a bidirectional communication is needed.
The only way to remove the MUTE command is with local CT or from a remote CT which
can reach the Network Element through another supervisory interface.
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.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

449 / 592
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. 312. Tributaries 17 to 32 visible in 16E1+ Ethernet configuration
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
450 / 592
USER MANUAL

45.9.11 Tributaries 17 to 32 visible in 16E1+Ethernet configuration

45.10 IDU unit replacement

In general, an IDU unit can be replaced:
a)
for spare part stock management:
b)
to check periodically the functionality of spare parts present in the spare part stock
or, during corrective maintenance:
to replace a faulty (or suspected faulty) unit with the correspondent spare part
Please refer to Fig. 305. on page 433 , for the position of this step inside the corrective maintenance
general flowchart.
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)
45.10.1
452
IDU EXTENSION unit (CH0)
45.10.2
456
Chapter 46
465
FLASH CARD (housed on MAIN unit)
N.B.
All these procedures are based, for both 1+0 and 1+1 configurations, on the equipment
interconnection diagrams depicted in para.32.2 on pages 331 to 337 .
Please make reference to the equipment interconnection diagram corresponding to your
system actual layout.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

451 / 592

45.10.1 IDU MAIN unit replacement procedure (CH1)
ON/OFF switch
Flash Card label
Reset pushbutton
Flash Card cover
Flash Card
possible additional
identification label
of the upgrade kit
(see point [14]
on page 475)
Identification label
Fig. 313. 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 reinstall the IDU MAIN unit
from/in the shelf, wall or desk assembly, please refer to the instructions given in the Installation
Handbook.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
452 / 592
USER MANUAL

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):
substep
operation by CT
[1]A
enable Force on CH0 Extensions RPS switch

if set as Revertive, set RPS protection scheme as
No Revertive
[1]B
enable Force on CH0 Extensions TPS switch

if set as Revertive, set TPS protection scheme as
No Revertive
[1]C
N.B.
results on main traffic

and services
in general, no
alarms/errors on both
NEs (N.B.)
enable Force on CH0 Extensions EPS switch

if set as Revertive, set EPS protection scheme as
No Revertive
(N.B.)
in case Data plugin 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. 313. on page 452) read the unit
Logistical Item (read also notes in point [14] on page 475, for the possible additional identification
label of the upgrade kit)
[4]
Get a spare unit with the same Logistical Item (see para.43.3.5 on page 419 for general cautions).
N.B.
If, according to the spare part policy described in para.43.3.3 point a ) on page 418 :
the unit to be replaced is equipped with optional plugin(s) (1732xE1 plugin, or

Audio + User Service Channel plugin, or Data plugin)
and the spare unit is not equipped with such plugin(s), that are instead available as
separate upgrade kits
you must at first install the spare plugin(s) into the spare IDU Main unit basic, as
described in para.47.1 on page 469 (obviously the described unit deinstallation and
reinstallation 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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

453 / 592
Turn off the front panel power switch (position O, see Fig. 313. on page 452):
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:
IDUODU 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 TNV2
(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. 313. on page 452):
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. 313. on page 452):
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
454 / 592
USER MANUAL

[6]

[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
IDUODU cable
power supply cable
CTNE cable
N.B.
SAFETY RULES: see previous point [8]
[16] if switched off in step [7] on page 454, 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. 313. on page 452)
[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
disable Force on CH0 Extensions RPS switch
Note:
results on main traffic and services

no alarms/errors on both NEs
the commands Force on Extensions TPS and EPS switches [set in previous steps [1]B
and [1]C on page 453] 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.13.7.2.2 on page 94.
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 selfadhesive sticker).
End of IDU MAIN unit replacement procedure
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

455 / 592
ON/OFF switch
possible additional identification label

of the upgrade kit (see point [14] on page 475)
Identification label
Fig. 314. 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 reinstall the IDU EXTENSION
unit from/in the shelf, wall or desk assembly, please refer to the instructions given in the
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
456 / 592
USER MANUAL

45.10.2 IDU EXTENSION unit replacement procedure (CH0)

Procedure:
[1]
Preliminary operations:
Before removing the IDU EXTENSION defective unit, by Craft Terminal carry out following
operations:
substep
operation by CT
results on services
[1]A
Enable Lockout on CH1

Mains RPS switch
no alarms/errors on both
NEs
NEs
[1]B

Mains TPS switch
NEs
NEs
[1]C

Mains EPS switch
no alarms/errors on
remote NE
12 sec alarm/AIS
Sync Loss on local
NE
no alarms/errors on
remote NE
1 sec Slip or AIS on
local NE
[2]
On the unit identification label present at unit rear side (see Fig. 314. on page 456) read the unit
Logistical Item (read also notes in point [14] on page 475, for the possible additional identification
label of the upgrade kit)
[3]
Get a spare unit with the same Logistical Item (see para.43.3.5 on page 419 for general cautions).
N.B.
If, according to the spare part policy described in para.43.3.3 point a ) on page 418 :
the unit to be replaced is equipped with the optional 1732xE1 plugin
and the spare unit is not equipped with such a plugin, that is instead available as
separate upgrade kit
you must at first install the spare plugin into the spare IDU Extension unit basic, as
described in para.47.1 on page 469 (obviously the described unit deinstallation and
reinstallation 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. 314. on page 456):
of the IDU EXTENSION unit to be replaced
of the IDU EXTENSION spare unit
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

457 / 592
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:
IDUODU cable
SCSI 1+1 interconnection cable between IDU Main and Extension units
power supply cable

Note: before removing cables ensure they are labeled
SAFETY RULES
If operation indicated in previous point [6] has not been carried out, a TNV2
(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
IDUODU cable
power supply cable

N.B.
SAFETY RULES: see previous point [7]
[11] if switched off in step [6] on page 458, 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. 314. on page 456)
[13] Wait for the unit configuration (about 2 minutes)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
458 / 592
USER MANUAL

[6]

[14] Carry out following operations:

substep
operation by CT
no alarms/errors on
remote NE
12 sec
alarm/AISSync
Loss on local NE
results on services
no alarms/errors on
remote NE
1 sec Slip or AIS on
local NE
[14]A
Disable Lockout on CH1

Mains EPS switch
[14]B

Mains RPS switch
NEs
NEs
[14]C

Mains 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
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

459 / 592
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
Please refer to Fig. 305. on page 433 , for the position of this step inside the corrective maintenance
general flowchart.
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.51.3.8 on page 507 . 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 508
Procedure:
[1]
Get a spare ODU unit or, in case of ODU with external diplexer, a spare TRANSCEIVER box:
with the same Frequency Band and the same Frequency Shifter
and with the same or compatible Logistical Item

of the ODU unit or TRANSCEIVER box 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:
[3]
CH1 (ODU connected to IDU MAIN unit), carry out steps [1]A to [1]C on page 453
CH0 (ODU connected to IDU EXTENSION unit), carry out steps [1]A to [1]C on page 457
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. 313. on page 452 )
for channel 0, operate on EXTENSION unit (position O, see Fig. 314. on page 456 )
WARNING:
this avoids a possible unrecoverable unknown condition of the spare ODU, when
ODU will be switched on in next step [9]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
460 / 592
USER MANUAL

45.11 ODU replacement

[4]
If present, remove the solar shield (see Fig. 46. on page 120 and Fig. 47. on page 121)
[5]
Disconnect the IDUODU cable at ODU side
[6]
Change the ODU. NOTES:
in case of ODU configurations 1+1 with coupler, use lever shown in Fig. 296. on page 417;
in case of 78 GHz ODUs:

a)
b)
remove the faulty TRANSCEIVER box in the following way (refer to Fig. 47. on page 121):
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.14.7.4.2 on page 124), i.e. if the TRANSCEIVER boxs (D) (TX) is coupled to
the:
BRANCHING boxs (B) (HIGH FREQ)
or BRANCHING boxs (C) (LOW FREQ)
install the spare TRANSCEIVER box in the following way:

4)
verify the presence and correct positioning of the ORING on the spare
TRANSCEIVER box (see Fig. 49. on page 123)
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 121)
[7]
Reconnect the IDUODU 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] .
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

461 / 592
CH1 (ODU connected to IDU MAIN unit), carry out following operations:
substep
results on main traffic and

services
operation by CT
[10]A
disable Force on CH0 Extensions RPS switch
[10]B
disable Force on CH0 Extensions TPS switch
[10]C
disable Force on CH0 Extensions EPS switch
CH0 (ODU connected to IDU EXTENSION unit), carry out steps [14]A to [14]C on page
459
[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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
462 / 592
USER MANUAL

[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:

45.12 Faulty unit repair and Repair Form

flowchart.
45.12.1 Faulty unit sending back to repair center
The complete faulty unit (complete ODU assembly, or TRANSCEIVER box in case of 78 GHz
ODU, or IDU Main or Extension Unit including plugin, if any) must be sent back to the
AlcatelLucent repair center.
Faulty unit repair must be done by authorized repair centers only.
45.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 filledin with as much data as possible and returned to AlcatelLucent
together with the faulty unit.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

463 / 592

REPAIR FORM
Fill in this form and affix it to the faulty unit to be returned to AlcatelLucent
CUSTOMER NAME
ORDER NUMBER/CONTRACT NUMBER
SITE
BRANCH/UNIT/COUNTRY
SYSTEM/EQUIPMENT
PRODUCT RELEASE
TO BE FILLED IN BY THE SENDER
STATION/RACK
EQUIPMENT SOFTWARE PART NUMBER
SUBRACK
SLOT
MNEMONIC
ALCATEL PART NUMBER
SERIAL NUMBER
FAULTY UNIT SOFTWARE VERSION
FAULT PHASE
REASON FOR REPAIR
PRESUMED CAUSE
INSTALLATION /
TURN ON
CLEAR FAULT
DROP IN PERFORMANCE
OPERATION
INTERMITTENT FAULT
UPGRADE/QUALITY ALERT
INTERNAL
LIGHTNING
EXTERNAL
MAINTENANCE
AIR COND.
TEMPERATURE FAULT
OTHER
DATE
NAME OF SENDER
FAULT STILL PRESENT

AFTER REPAIR
TO BE FILLED IN BY THE REPAIR OPERATOR
COMMENTS
PROCESSING
NO FAULTS FOUND
FAULTS DETECTED
UPGRADE
SOLDERING /
WIRING
A
STANDARD REPAIRING
NOT REPAIRABLE
(REJECTED)
ADJUSTMENT
I
MECHANICAL
M
BD
COMPONENT
FL
PRINTED
CIRCUIT BOARD
V1
P
DIRT
V1
V2
SUBSTITUTED
QUALITY ALERT
CORROSION
I
SX
OTHER
V3
NOTE : LETTERS ARE FOR FACTORY USE
COMMENTS
DATE
REPAIRING NUMBER
REPAIRING CENTRE
NAME OF REPAIR OPERATOR
Fig. 315. Repair form
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
464 / 592
USER MANUAL

46 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.47.3 Flash Card upgrade on page 479.
46.1 Spare Flash Card management

Please refer to para.13.7 on page 93 for detailed information on Flash Card position, types and
identification.
With reference to the Flash Card content description given in para.12.5 on page 56 , 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 AlcatelLucent 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 backup information is always available for each
specific NE:
[1]
the MIB backup file

To know how to create a MIB backup file, refer to Chapter 214 on page 301.
[2]
the .qcml configuration file

To know how to create a .qcml configuration backup file, refer to the Procedure for .qcml
file backup on page 65 .
Please, refer to para.12.6.7 on page 65 for details.

SUGGESTION
Use one IDU Main unit of the sparepartstock as an offline service station (non connected to the
network) to manage the content of Flash Cards, before using them as spare parts.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

465 / 592
46.2.1 Introduction
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.12.5 on page 56). Many types are envisaged: its
identification is described in para.13.7.2.2 on page 94.
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 Systems 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.46.2.2, depend on
the choice adopted by the Customer with reference to the type of spare flash card stored in the
sparepartstock (refer to the Spare Flash Card management policy described in para.46.1 on page
465):
a)
NEspecific 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 offline service station).
b)
generic spare part that cannot be inserted it as it is in any NE.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
466 / 592
USER MANUAL

46.2 Flash Card replacement procedure

46.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. 76. on page
170) and according to it, retrieve the Flash Card Logistical Item through Tab. 23. on page 93 .
If CT works, you can verify the Flash Card Software Label by Supervision SW Key (example
in Fig. 159. on page 256 )
[2]
Get the spare Flash Card with the same Logistical Item; 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. 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.
[4]
Before to isolate the system from the supervision network, inform the supervision
center: if (from the supervision point of view), there are other NEs
cascadeconnected to it (and without supervision ring network) they will be isolated,
too.
Wear the antistatic protection armlet [see point b ) on page 36] and connect its termination to a
grounded structure
ATTENTION
[5]
Remove the Flash Card cover (see Fig. 313. on page 452 ). 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. 34. on page 94 for Flash Card profile
and insertion direction)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

467 / 592
[8]
After two minutes, login the NE by CT.

Now, if you have inserted:
a generic spare Flash Card, proceed with following step [8]
a NEspecific spare Flash Card, proceed with following step [9]
If you have inserted a generic spare Flash Card, carry out following checks and operations by CT:
1)
verify the SW COMMITTED and STANDBY versions in the Flash Card, as described in point
[2] on page 63 :
if the SW COMMITTED version is equal to that previously present with the replaced flash
card, proceed with substeps 2 ) and 3 ) below
if the SW COMMITTED version is not equal to that previously present with the replaced
flash card, but the STANDBY version is equal, proceed with the swap between the SW
COMMITTED and STANDBY versions, as described in para.48.5 on page 492 .
Then, proceed with substeps 2 ) and 3 ) below.
if neither the SW COMMITTED nor the STANDBY versions are equal to that previously
present with the replaced flash card, proceed with downloading and activation of the target
SWP version, as described in chapter 48 on page 485 .
Then, proceed with substeps 2 ) and 3 ) below.
2)
launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345
In the screen of Fig. 244. on page 346 , click on button Open Configuration .
When the file selection window opens requiring a configuration_name.qcml file to be opened,
specify the NEs specific file [mentioned in point [2] on page 465 ].
The window in Fig. 245. on page 347 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 368 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 NEs specific MIB backup file mentioned in
point [1] on page 465 ] as shown in MIB Restore in Fig. 209. on page 301 (from operative
point of view, refer to para.28.3.2 and 28.3.3 on page 255). In alternative to activation by
SW, carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN
Unit (see Fig. 76. on page 170).
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
468 / 592
USER MANUAL

[7]

47 SYSTEM HARDWARE UPGRADE

This chapter details all phases necessary to carry out the following hardware upgrades:
Installation of plugins, para.47.1 below
upgrade 9400AWY system from 1+0 to 1+1 configuration, para.47.2 on page 476
install a new Flash Card to improve system capacity, para.47.3 on page 479
47.1 Installation of plugins

47.1.1 Introduction
When Customer orders a 9400AWY equipment, usually , if plugins are included in the order, IDU Main
unit and IDU Extension unit are delivered with the required plugins 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 plugin equipped,
Customer needs to upgrade it adding plugins.
Tab. 71. below lists the plugins presently available.
Tab. 71. Available plugin upgrade kits
Logistical Item
Description
Notes
3DB16086AAXX 32E1 ON SITE UPGRADE KIT

3DB16130AAXX
DATA ENHANCED ON SITE UPGRADE KIT

(4 x 10/100/1000 baseT ports)
in alternative
3DB16089AAXX AUDIO + USER SERVICE CHANNEL UPGRADE KIT
Notice that:
in 1+0 configuration, you can equip any of the plugin 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 1732 E1 PLUGIN into both
the:
IDU Main unit
IDU Extension unit
upgrade to Ethernet tributaries: you must install the DATA ENHANCED ON SITE UPGRADE
KIT into the IDU Main unit only
upgrade for AUDIO + USER SERVICE CHANNEL functionalities: you must install the AUDIO
+ USER SERVICE CHANNEL UPGRADE KIT into the IDU Main unit only.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

469 / 592
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 reinstallation
In all described operations, when it is necessary to uninstall or reinstall 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 36] and disconnect all
cables.
[2]
Uninstall the unit and place it on a workbench
[3]
Fig. 316. :
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
B
D
Fig. 316. Dismounting the fixing brackets and cover unfix
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
470 / 592
USER MANUAL

47.1.2 Procedure

[4]
Rotating the removed fixing brackets into both the suitable covers side holes, slide the box cover
out from the box base, as shown in Fig. 317. :
use of fixing bracket to release the cover
sliding out the cover
Fig. 317. Release and sliding out the cover

[5]
Wear the antistatic protection armlet and connect its termination to a grounded structure (see
ATTENTION
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

471 / 592
Now, you can remove the cover (Fig. 318. ):

[6]
Fig. 318. Removing the cover

[7]
Fig. 319. : according to the plugin to be installed, dismount the metal plate (fixed by two screws)
which closes the plugin devoted hole. Take the two removed screws for their fixing.
plate to remove for
AUDIO + USER SERVICE
CHANNEL plugin
plate to remove for

TRIBUTARY plugin
Fig. 319. Dismounting the metal plate
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
472 / 592
USER MANUAL
Fig. 320. shows in details the connectors and columns for plugin fixing by screws

[8]
2 columns for plugin

fixing by screws
3 columns for plugin

fixing by screws
connectors for plugin

connector
for plugin
Fig. 320. Connectors and columns for plugin fixing by screws
[9]
Insert the plugin in its connector(s) depicted in previous Fig. 320. , and fix it:
on the PCB using the 2 or 3 screws on the suitable columns depicted in previous Fig. 320.
to the front panel by the 2 screws or the screw columns
The result must be as shown in following Fig. 321.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

473 / 592
Details of Enhanced Ethernet plugin installed
Details of Audio + User Service Channel plugin installed

Fig. 321. Plugin insertion and fix
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
474 / 592
USER MANUAL

Details of 1632 E1 plugin installed

[10] Reinsert the cover

(reverse operation of Fig. 318. on page 472)
[11] Slide in the cover
(reverse operation of Fig. 317. on page 471. The fixing brackets use is not necessary)
[13] Fix the cover and, if they were present, mount both fixing brackets
(reverse operation of Fig. 316. on page 470)
[14] Upgrade kit identification label
After this upgrading, the Unit identification label placed on the box rear side [position (C) in Fig. 21. on
page 70 for the IDU Main Unit, and in Fig. 23. on page 77 for the IDU Extension Unit] is no longer
right to correctly identify the assembly as a whole.
This could impact on sparepartstock management and maintenance.
For this reason:
if the upgrade kit is supplied with a suitable selfadhesive label (under study), stick it just on side
of that already existing
otherwise create a label writing the upgrade kit P/N on a selfadhesive sticker, and stick it just
on side of that already existing.
additional
of the upgrade kit
existing
of the basic unit
[15] Reinstall 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 redefinition (it is different from that previous to upgrading), carrying out Quick
Configuration procedure by Craft Terminal (details in para.32.3.7 on page 343).
commissioning procedure, to check the new interface, (details in Chapter 32

Commissioning on page 329).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

475 / 592
47.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 lineup.
a)
First case: 1+0 already equipped with the Protection boxes

This procedure is based on the equipment interconnection diagrams depicted in para.32.2 on
pages 331 to 337 . 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.32.2 on pages 331 to 337 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:
SAFETY RULES
When operating on the antenna pole, strictly follow cautions stated in
para.51.3.8 on page 507 . 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 508
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
476 / 592
USER MANUAL

47.2 Upgrade from 1+0 to 1+1 configuration

47.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.13.1 on page 68 (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.22.5.2 on page 173) 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.22.5.2 on page 173)
[4]
Using the instructions given in the Installation Handbook , install the second ODU; for general
information, make reference to Fig. 4. on page 41). Warning: in case of 1+1 ODU configuration:
[5]
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.26.4.1 on page
239
2)
carry out NE logoff (details in para.22.5.3 on page 180)
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.26.4.1 on page 239
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]
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

477 / 592
Connect the 100pin cable to both IDU MAIN and EXTENSION units, using the instructions given
in the Installation Handbook
[7]
Connect the IDUODU 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:
[9]
1)
Configuration System Setting NE Configuration 1+1 Configuration: see para.23.4.1

on page 210
2)
This configuration change causes the JUSM loss, so that you must login again the NE (details
in para.22.5.2 from page 173)
3)
Set EPS (Mux/Demux Protection) Lockout: see para.29.1 subpara.29.1.2 on page 259
WARNING: this operation is not error free
4)
Set CH0 Tx Power as follows: with reference to Fig. 140. on page 238 :
select Channel #0 click on RTPC & ATPC insert value in Tx Power(dBm) field Apply
WARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]4 ) below
5)
Note: this step is not necessary in HSB configuration, where frequency is set automatically:
Set CH0 Tx Frequency as follows: with reference to Fig. 136. on page 235 :
select Channel #0 click on Frequency insert value in Tx Frequency(kHz) field Apply
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. 136. on page 235 :
select Channel #0 insert value in Shifter field Apply
2)
Note: this step is necessary in FD configuration only:

Set again CH0 Frequency as follows: with reference to Fig. 136. on page 235 :
select Channel #0 click on Frequency insert value in Tx Frequency(kHz) field Apply
WARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]4 ) below
3)
Remove EPS (Mux/Demux Protection) Lockout: see para.29.1 subpara.29.1.2 on page 259
WARNING: this operation is not error free
4)
Restart NE: see para. 28.2 on page 252

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 32 on page 329.
PHASE [D] : NE DATA SAVE
[14] Save data of both NEs as explained in para.12.6.8 on page 65.

End of procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
478 / 592
USER MANUAL

[6]

47.3 Flash Card upgrade

47.3.1 Introduction
Please refer to para.13.7 on page 93 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.46.2 Flash Card replacement procedures on page 466.
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 32Mb 4/16 QAM FLASH CARD with the 64Mb 16 QAM FLASH
CARD
corresponding to the change of the:
Software Label from 32Mb 4/16 QAM to 64Mb 16 QAM
This paragraph explains how to do this operation.
and install (if not yet present) the 1732xE1 PLUGIN 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.47.1
Installation of plugins on page 469.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

479 / 592
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
(in series to step1)
STEP 1 IN STATION B
Current configuration Backup
idem
Flash card replacement. This requires, in

typical condition (rack installation), to
switch the IDU off and disconnect cables;
otherwise, if the installation condition
allows to replace the flash card without
disconnecting cables, the NE supports an
hot replacement
idem
IDU switchon (after recabling) or NE

Restart (in case of hot replacement), Start
Supervision & Open USM (empty due to
the nonpreconfigured flash card)
idem
Check that the SW Key is the new one
idem
MIB Restore / Activation, Start Supervision

& Open USM
idem
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
is modified to 32E1 and the Tributary
config is set again to 16E1 (not to 32E1
as desired)
idem
notes
Reopening 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
the traffic is
CAPACITY
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
480 / 592
USER MANUAL

47.3.2 Summary procedure for both stations

47.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. 23. on page 93 ,
and preferably, already set by AlcatelLucent Factory:
N.B.
with the same SWPversion present in the 9400AWY system to be upgraded, already present
in the FlashCards 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 NEs .qcml configuration file on
floppydisk as explained in the Procedure for .qcml file backup on page 65 , and give it to
AlcatelLucent Factory). N.B.
with the same MIB of the system to be upgraded (for this purpose, Customer can save the MIB
on floppydisk as explained in chapter 214 on page 301 and give it to AlcatelLucent Factory).
N.B.
these options could be subject to possible special contractual terms.
To install a new Flash Card fully configured in factory carry out operations in para.47.3.4 on page 482.
To install a new Flash Card not configured in factory carry out operations in para.47.3.5 on page 483.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

481 / 592
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.47.3.3 on page 481 .
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 36 ] and connect its termination to a
grounded structure
ATTENTION
[3]
remove the Flash Card cover (see Fig. 313. on page 452 ). 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. 34. on page
94 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. 313. on page 452 ).
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 Quick Configuration procedure (interactive) by Craft Terminal [details in para.32.3.7
on page 343 ], to change the system capacity
[10] carry out functional checks by Craft Terminal

[11] save NE data as explained in para.12.6.8 on page 65 ( creation of MIB backup file and .qcml
backup file )
[12] as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Software
Label, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, remove
the older selfadhesive label before sticking the newer).
End of procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
482 / 592
USER MANUAL

47.3.4 Installation of a new Flash Card fully configured in factory

47.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 Quick Configuration procedure (interactive) by Craft Terminal [details in para.32.3.7
on page 343 ]. In the last screen (Step L on page 368) 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. 209. on page 301 (from operative point of
view, refer to para.28.3.1 on page 254)
[4]
carry out NE logoff
[5]
isolate the NE from the supervision network

N.B.
[6]
Before to isolate the system from the supervision network, inform the supervision center:
if (from the supervision point of view), there are other NEs cascadeconnected to it (and
without supervision ring network) they will be isolated, too.
wear the antistatic protection armlet [see point b ) on page 36 ] and connect its termination to a
grounded structure
ATTENTION
[7]
remove the Flash Card cover (see Fig. 313. on page 452 ). 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. 34. on page
94 for Flash Card profile and insertion direction)
[9]
restore the Flash Card cover removed in step [7] above (screw tightening torque as specified above)
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

483 / 592
[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 63.
If not V2.1.0, proceed with V2.1.0 downloading and activation, as described in chapter 48 on
page 485.
2)
launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345.
In the screen of Fig. 244. on page 346 , click on button Open Configuration .
When the file selection window opens requiring a configuration_name.qcml file to be opened,
specify the NEs specific file you have saved in previous step [3]1 ) on page 483.
The window in Fig. 245. on page 347 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 368 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 NEs specific MIB backup file you have saved
in previous step [3]2 ) on page 483] as shown in MIB Restore in Fig. 209. on page 301 (from
operative point of view, refer to para.28.3.2 and 28.3.3 on page 255). In alternative to
activation by SW, carry out the Equipment Controller HW Reset, pushing the suitable button
on IDU MAIN Unit (see Fig. 76. on page 170).
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 Quick Configuration procedure (interactive) by Craft Terminal [details in para.32.3.7
on page 343 ], 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.12.6.8 on page 65.
[16] as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Software
Label, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, remove
the older selfadhesive label before sticking the newer).
N.B.
In alternative, if an offline IDU MAIN unit is available at Customer premises, the Flash Card
can be prepared on it, and then installed on the target system as described in previous
para.47.3.4 on page 482.
End of procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
484 / 592
USER MANUAL

[10] now you can take off the antistatic protection armlet

48 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 NEs Flash Card.
N.B.
Before starting this procedure, it is suggested to give a look to para.12.6 on page 58.
N.B.
Procedures described in this chapter are carried out with the PC connected to the NE.
48.1 Requirements
48.1.1 Craft Terminal
The PC, already loaded with the SWP to be downloaded toward the NE (as explained in previous chapter
31 on page 309) must be available as CT (Craft Terminal).
48.1.2 NE state
[1]
[2]
Equipment state
equipment must have been previously installed, cabled, powered on and commissioned as
described in para.12.6.1 on page 59
the SWPversion present inside the NEs Flash Card must be lower than that of the ECT (refer
to para.12.6.3 on page 62 to know how to compare them).
Equipment HW constraints
None
48.1.3 Operator skills and profile

a)
In addition to skills stated in para.31.1.2 on page 310, the Operator must be familiar with all the
equipment functionalities.
b)
The Operators profile must be Administrator or craftPerson (see para.23.6 on page 214).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

485 / 592
WARNING:
this procedure describes the operations to be done on a single NE. You must be aware
that they must be done on both stations A and B of the radio link. For this purpose, make
reference to Chapter 49 on page 495
The installation phases are:

a)
CT startup, NE login and initial checks
para.48.3 herebelow
b)
SW download to the NE,
c)
Activation of the new Software Package on the NE
d)
Additional operations for upgrade from V2.1.0
e)
MIB save
48.3 CT startup, NE login and initial checks

Step 1.
Step 2.
Carry out following operations (for details refer to para.22.5.2 on page 173):
a)
Power on the PC and wait for its startup
b)
Startup the Craft Terminal and wait for the Network Element Synthesis screen
c)
Carry out Start supervision and Show Equipment on the Network Element that must be
affected by this download operation
d)
Login the Network Element, using the Administrator or craftPerson UserName &
Password
e)
Wait for the main Equipment view (CT) to appear
Check SWP versions 2.1.x present in the NE MIB banks, as explained in point [2] on page 63.
You must be aware that the SWP download, carried out in the following, will overwrite the current
Standby version. In the case you want to maintain such a version, and overwriting the other (i.e.
that presently Committed), activate the current Standby version as described in para.48.5 on
page 492.
Step 3.
Check the SWP version 2.1.y (y > x) availability for download to the NE, as explained in step
6 ) on page 325.
If not available, carry out completely the procedure described in para.31.8 on page 321.
Verify also that the version to be downloaded is greater than those present in both the NE MIB
current Standby and Committed banks.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
486 / 592
USER MANUAL

48.2 Summary of the SWP download phases

48.4 SW download to the NE

Step 1.
Setup Server Access Configuration

a)
Carry out SW Download Server Access Configuration (Fig. 322. below)
Fig. 322. Server Access Configuration start up

b)
The following confirmation box appears. Press OK to close it.
c)
The screen of Fig. 323. on page 488 appears, with empty fields. Click on Use System
Default button.
In this way the systems sets automatically the Address and Port fields, that depend on
how the login to the NE has been done:
by F interface: IP address of the LLMAN to download in interface F mode is set
by LAN interface: IP address of the PC to download the software in LAN mode is set
N.B.
The UserId and Password present in this screen are relevant to the ftp login, are
set automatically with the Use System Default button and have no relationship
with those necessary for the NE login.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

487 / 592

Fig. 323. Server Access Configuration setup screen

d)
Press OK to confirm values and close the window.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
488 / 592
USER MANUAL

Step 2.
SW Download
a)
Carry out SW Download Init SW Download (Fig. 322. below)
Fig. 324. Init SW Download startup

b)
Wait List Sw Package creation ...

When action is completed, press Enter to close message window.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

489 / 592
Now select a specific SWP to download on the NE, and press Init download to start it.
c)
2_1_
1
Fig. 325. Init download

d)
Confirm the start of software downloading:
2_1_1
e)
The software downloading in progress is shown by a specific window:
f)
When the download is over the following window is shown:
N.B.
The software download lasts about 1/2 hour if performed through the F interface, and
few minutes if the Ethernet interface is used.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
490 / 592
USER MANUAL

g)
After the software download completion, by SW Download SW Status (see

Fig. 326. on page 492), you can verify that the downloaded SW is present as Stand by
version; moreover, clicking on the Software Unit Status button, it is possible to see its
components and their version.
V02.01.01
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

491 / 592
After the software download (explained in previous para.48.4 on page 487), two software packages are
present in the NE: one Committed and the other Stand by.
The Activation of the new Software Package on the NE means to make the Stand by SWP become the
Committed one (and viceversa).
Step 1.
Stand by SW activation
a)
Carry out SW Download SW Status
Fig. 326. SW Status

b)
Fig. 327. below: select the Standby SW (1), set Activation (2) in the Software
Management Action field, then Apply Action (3)
(1)
V02.01.01
(2)
V02.01.01
(3)
Fig. 327. Stand by SW activation
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
492 / 592
USER MANUAL

48.5 Activation of the new Software Package on the NE

c)
Confirm the selected action:
d)
This message appears (click OK to close) ...
e)
... and the NE restarts with the new software package.

N.B.
Step 2.
The JUSM becomes unavailable (the following message appears (click OK to

close)
Logoff and ReLogin

a)
Logoff the NE
b)
Login the NE and verify, by SW Download SW Status (see Fig. 326. on page 492), that
the SW banks have changed their Current Status.
WARNING:
once you have downloaded and made active the new SWP in NE environment, do not
make the mistake of trying to switch the previos version back to COMMITTED status (for
details, read WARNING on page 495 ).
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

493 / 592
Proceed as follows:
After having carrying out for the first time:
the V2.1.1 SW download to the NE (para.48.4 on page 487)
and the activation of the V2.1.1 on the NE (para.48.5 on page 492)

carry out for the second time:
the V2.1.1 SW download to the NE (para.48.4 on page 487), but, in phase c ) on page 490,
setting Forced before clicking on Init download (Fig. 328. below)
2_1_1
(1)
(2)
Fig. 328. Forced Init download
N.B.
and the activation of the Stand by V2.1.1 on the NE (para.48.5 on page 492)
Obviously, at the end of this procedure, you will have both SW banks with V2.1.1 SWP, and the
V2.1.0 SWP has been lost.
Why are there operations required?

Starting from AWY V2.1.1, one new SW component has been added (with respect to V2.1.0) in
Software Package: for this reason, if the active bank is V2.1.0, the download of SWP in the flash card
must be executed in two steps:
with the first step (normal download procedure) all SW components known by previous SWP
version are downloaded on flash card;
new SWP component is known ONLY by SWP 2.1.1, so after the activation of package SWP
2.1.1, it is necessary to download SWP 2.1.1 again (IN FORCED MODE), to transfer the new
SW component image onto flash card.
48.7 MIB save

At the end, create a new MIB backup copy (associated to the new SWPversion), as described in chapter
214 on page 301.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
494 / 592
USER MANUAL

48.6 Additional operations for upgrade from V2.1.0

49 ECT & NE UPGRADE FROM V2.1.0 TO V2.1.1

This chapter details all phases necessary to install a new SWP version in the PC environment as well
as in the equipment environment in both stations A and B of the radio link, i.e. in the following case:
both ECT and equipment (in both stations A and B) are presently running with version V2.1.0
the new SWP V2.1.1 is delivered to Customer by means of the specific SWP CDROM.
Procedure:
[1]
Preliminary checks and actions on both stations

1)
if the former version of 2xFast Ethernet plugin is equipped, it must be removed, and, if
envisaged, the new version of 4xGbit Ethernet plugin must be installed; for this purpose, carry
out these operations on both stations:
a)
using the instructions given in the 9400AWY V2.1.0 User Manual:
remove traffic on Fast Ethernet ports
disable both Fast Ethernet ports
unconfigure the 2xFast Ethernet plugin
b)
phisically disinstall the 2xFast Ethernet plugin
c)
and, if envisaged, install the DATA ENHANCED ON SITE UPGRADE KIT, making
reference to para.47.1 on page 469 of this manual
N.B.
ignore the unespected equipment alarm that arises after the installation of the
4xGbit Ethernet plugin (it is not supported by SWP version V2.1.0)
2)
check that no hardware or radio transmission problems are present (with exception of the
unespected equipment alarm stated above). Otherwise, solve them before starting upgrade
3)
close all Performance Monitoring, analog measurement and BER measurement processes, if
any
4)
remove all loopbacks as well as all lockout, forced and manual commands on protection
schemes, if any
5)
do not use functions stated above, or any other action not strictly necessary for the upgrade,
until you have completed the SW upgrade of both stations, i.e. not before step [5] on page
496 of this procedure.
6)
WARNING:
you must be aware that, once you have downloaded and made active the new SWP V2.1.1 in
NE environment (at the end of step [3] for station A , and at the end of step [4] for station B),
you cannot switch them back to V2.1.0, because there is no backward compatibility between
V2.1.1 and V2.1.0 NE data base structures.
In case you think you could need to go back to V2.1.0, before next step [2] , i.e. with SWP 2.1.0
running both in PC and NE, prepare a spare Flash Card containing:
the SWP 2.1.0 as COMMITTED bank
the associated MIB data

Restoring this Flash Card in the system is the only way to make downgrade.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

495 / 592
Operations on local PC (station A)

1)
Requirements: see para.31.1 on page 309 and para.48.1 on page 485.
2)
on local PC, carry out the installation of the new SWP version in the ECT environment and the
V2.1.1 NE software downloading preparation, as indicated in Chapter 31 from page 309 to
page 325
N.B.
[3]
The Craft Terminal configuration (para.31.9.1 on page 326 ) and the EML
construction (para.31.10 on page 327 ) are not considered necessary because
relevant data should have already been defined during the CT installation made with
SWP 2.1.0.
V2.1.1 software download and activation on station A

3)
connect the CT to the local NE (station A) by the suitable crossconnct Ethernet cable, launch
the V2.1.1 Craft Terminal and login the local NE (station A) by:
TCO Suite Main Menu Operational & Maintenance
4)
[4]
SW download to the NE, para.48.4 on page 487
activation of the new Software Package on the NE, para.48.5 on page 492
additional operations for upgrade from V2.1.0, para.48.6 on page 494
V2.1.1 software download and activation on station B

5)
[5]
carry out the download (from the CT) and the activation of the new SWP version in the NE
environment, executing in sequence the operations described in:
by RECT functionality, login the remote NE (station B) and carry out same operations made
for station A
Carry out functional checks on radio link

E.g. Performance Monitoring, analog measurement, BER measurement, operations on protection
schemes, loopbacks, etc.
[6]
Operations on remote PC (station B)

Do not forget to update also the PC(s) present in station B, as done in step [2]2 ) above.
End of procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
496 / 592
USER MANUAL

[2]
410 SWP DEINSTALLATION

This chapter describes how to deinstall 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 deinstall the following procedures can be followed:
automatically, using the CDROM containing the installed Softwareversion product.
manually, with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CDROM
containing the relevant Software product is not available.
Practically, the manual deinstallation 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 subprocesses) are
active; in case of doubts, restart the PC (switch it off / on).
From Control Panel select Add/Remove Programs and deinstall the components in the following
order:
1)
CTNEConfUpd (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 Q3CTKADDONvX.Y.Z (1320CT)
6)
ALCATEL SNMPCTKADDONvX.Y.Z (1320CT)
7)
ALCATEL HOLCTKADDONvX.Y.Z (1320CT)
8)
ALCATEL CTKvX.Y.Z (1320CT)
9)
Alcatel Lower Layers Manager & Tiny Tools
10 ) Java 2 Runtime Environment. SE vX.Y.Z_KJ
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

497 / 592
a)
END OF SECTION 4
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
498 / 592
USER MANUAL

SECTION 5: APPENDICES
SECTION CONTENT
PAGE
Appendix A SafetyEMCEMFESD norms and equipment labelling

It describes the equipment labelling and the norms mandatory or suggested that must
be considered to avoid injuries on persons and/or damage to the equipment.
Moreover the labels affixed to the IDU and ODU equipment are described.
501
Appendix B TCO suite startup special conditions

This Appendix describes some special conditions that may occur during the TCO
Suite startup and the countermeasures to take.
511
Appendix C Additional SW installation operations for NE management

through the NEs ECT serial port
This Appendix explains the operations necessary to allow the NE management
through the NEs ECT serial port. Such operations are not necessary if you use TCO
Suite and Craft Terminal accessing the NE through its Ethernet interface only.
517
Appendix D General on Ethernet port characteristics and management

This Appendix gives summary information that can be useful for the configuration of
Ethernet ports.
547
Appendix E ECTEquipment connection via public switched telephone

network
This Appendix explains the operations necessary to allow the remote connection to
the FInterface, from a local PC configurated as ECT, through a switched telephone
line of the standard Public Telephone Network.
553
Appendix F Part lists of tool kits
563
Appendix G Documentation guide

It contains all information regarding this handbook (purpose, applicability, history) and
the Customer Documentation set it belongs to, in particular the list of the handbooks
the Operators should have in order to carry out the required operations.
567
Appendix H List of symbols and abbreviations, Glossary of terms
575
Appendix I Customer documentation feedback
589
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

499 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
500 / 592
USER MANUAL
APPENDICES

51 APPENDIX A: SAFETYEMCEMFESD NORMS AND

EQUIPMENT LABELLING
51.1 Introduction
This appendix describes the equipment labelling and the norms mandatory or suggested (see also point
d ) on page 31) 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.57.2.1 on page 569.
Compliance with International Standards
herebelow
Safety Rules
on page 502 including:
General Rules
Labels Indicating Danger, Forbiddance, Command
Dangerous Electrical Voltages
Risks of Explosions
Moving Mechanical Parts
Equipment connection to earth
Heatradiating Mechanical Parts
Specific safety rules in this handbook
Electromagnetic Compatibility (EMC norms)
on page 502
on page 503
on page 504
on page 505
on page 505
on page 506
on page 506
on page 507
on page 508
on page 509 including:
EMC General Norms Installation

EMC General Norms Turnon, Tests & Operation
EMC General Norms Maintenance
on page 509
on page 509
on page 509
Equipment protection against electrostatic discharges
on page 510
Suggestions, notes and cautions
on page 510
Labels affixed to the 9400AWY equipment
on page 510
51.2 Compliance with International Standards

Refer to chapter 15 on page 127.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

501 / 592
51.3.1 General Rules
Before carrying out any installation, turnon, tests & operation and maintenance operations
carefully read the related parts of this Manual or other Handbooks, in particular:
Installation: 9400AWY Installation Handbook
Commissioning: Chapter 32 on page 329
Maintenance: Section 4: Maintenance and Upgrade on page 407
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
502 / 592
USER MANUAL
APPENDICES

51.3 Safety Rules

51.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 38461984. The symbols or statements are
enclosed in geometric shapes: ISO 38641984.
CONTAINS A SYMBOL STATEMENT

INDICATES FORBIDDANCE (WHITE BACKGROUND
WHIT RED RIMBLACK SYMBOL OR STATEMENT)
IT IS A COMMAND (BLUE BACKGROUNDWHITE
SYMBOL OR STATEMENT).
CONTAINS A SYMBOL
INDICATES WARNING OR DANGER (YELLOW
BACKGROUNDBLACK SYMBOL AND RIM)
CONTAINS A STATEMENT PROVIDING INFORMATION

OR INSTRUCTION.
(YELLOW BACKGROUNDBLACK STATEMENT AND RIM)
The labels have been affixed to indicate a dangerous condition. They may contain any standardknown
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
heatradiating Mechanical Parts
microwave radiations
Pay attention to the information stated in the following, and proceed as instructed
The symbols presented in para.51.3.3 through 51.3.8 are all the possible symbols that
could be present on AlcatelLucent equipment, but are not all necessarily present on the
equipment this handbook refers to.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

503 / 592
51.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.
51.3.3.2 Electrical safety: general rules
DANGER! Possibility of personal injury:
carefully observe the specific

procedures for installation / turnup and commissioning / maintenance of equipment parts where D.C..
power is present, described in the relevant installation / turnup 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
504 / 592
USER MANUAL
APPENDICES

51.3.3 Dangerous Electrical Voltages

51.3.4 Risks of Explosions

51.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
(batteryemitted hydrogen). A 417IEC5641 Norm. compliant label is affixed next to it indicating that the
openings must not be covered up.
51.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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

505 / 592
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.
51.3.7 Heatradiating Mechanical Parts

The presence of heatradiating 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 / turnup and commissioning / maintenance of equipment parts where
heatradiating mechanical parts are present, described in the relevant installation / turnup 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
506 / 592
USER MANUAL
APPENDICES

51.3.6 Equipment connection to earth

51.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 switchoff 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
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
installation)
On the antenna (rear side)
USER MANUAL
APPENDICES
EMF emission warning sign, placed on the antenna.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

507 / 592
Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna:
B
System
Modulation
Worst Configuration
A (m)
B (m)
9413 AWY Rel 2.0
4 QAM
1+0 with integrated antenna

(13 GHz 1ft. SP integrated antenna)
0,4
2,63
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
51.3.9 Specific safety rules in this Manual
Specific safety rules are specified in the following parts:
chapter 32 para.32.9 on page 404
chapter 45 :
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
508 / 592
USER MANUAL
APPENDICES

Compliance boundaries:

51.4 Electromagnetic Compatibility (EMC norms)

The equipments 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, turnon, tests & operation and maintenance operations
carefully read the related parts of this Manual or other Handbooks, in particular:
Installation: Installation Handbook

Commissioning: Chapter 32 on page 329
Maintenance: Section 4: Maintenance and Upgrade on page 407
The norms set down to guarantee EMC compatibility, are distinguished inside this handbook
by the symbol and term:
ATTENTION
EMC NORMS
51.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 CustomersInstallation 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.
51.4.2 EMC General Norms Turnon, 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
51.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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

509 / 592
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 36):
an elasticized band worn around the wrist
a coiled cord connected to the elasticized band and to the stud on the subrack.
51.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....
51.7 Labels affixed to the 9400AWY equipment

Following paragraphs indicates the positions and the information contained on the identification labels
affixed to the equipment, with the exception of those already mentioned in para.51.3.2 ( page 503 ) to
51.5 ( page 510 ):
Labels affixed on the IDU:
Flash Card identification labels: Fig. 35. on page 95
Labels affixed on the ODU:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
510 / 592
USER MANUAL
APPENDICES

51.5 Equipment protection against electrostatic discharges

52 APPENDIX B: TCO SUITE STARTUP SPECIAL CONDITIONS

This Appendix describes some special conditions that may occur during the TCO Suite startup
(para.22.2.3 on page 148 ) and the countermeasures to take.
Depending on selected browser, on browser configuration and preferences and on users choices some
security questions could be made to the user, like:
Active content may potentially harm your computer or disclose personal information. Are you
sure to allow the CD for the execution of active content on the computer?
To proceed, you must answer YES.
In case of specific users browser configuration, the browser could ask some questions about secure or
blocked content (Fig. 329. below) 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 and allow
the browser to manage this information (Fig. 330. on page 512).
click
Fig. 329. 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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

511 / 592
Fig. 330. Secure Questions: Allow Secure Content

Usually, the user has to click with the mouse on such yellow bar and a popup menu will appear to ask
user if he/she allows running this special content (Fig. 330. above). In some cases another confirmation
is requested to the user (Fig. 331. below).
Fig. 331. Execution confirmation (Security Warning)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
512 / 592
USER MANUAL
APPENDICES

click

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. 332. and Fig. 333. show a
couple of examples of this warnings: as wrote before, things can differ with respect to language or graphics
and so on.
Fig. 332. Security Warning (English browser on Italian System)
Fig. 333. Security Warning (Italian browser on Italian System)
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

513 / 592
Fig. 334. Security Warning (Java 1.4)

Following Fig. 335. shows a wrong security warning with a Java version lower than 1.4. In this case the
TCO Suite wont work:
Fig. 335. Wrong Security Warning (Java 1.3)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
514 / 592
USER MANUAL
APPENDICES

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
(AlcatelLucent 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. 334. below,
usually with JREs with version number 1.4:

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. 336. 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 plugin so the browser asks the user to automatically install needed plugin by searching it on
the Internet.
Fig. 336. Firefox browser: no JRE installed

If user allows to search for related plugin, a specific operation could be started (Fig. 337. below).
Fig. 337. Firefox plugin search

And if the user agrees, the browser could automatically install the correct plugin (see following Fig. 338. ).
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

515 / 592
Fig. 338. Firefox plugin 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. 55. on page 149.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
516 / 592
USER MANUAL
APPENDICES

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.

53 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NE

MANAGEMENT THROUGH THE NES ECT SERIAL PORT
53.1 Foreword
This procedure is referenced to by case b ) on page 311 , and is necessary only when you need to use
the NEs ECT serial port to manage the NE itself by the Craft Terminal functions.
N.B.
Carrying out this procedure is not necessary if you want to use TCO Suite and Craft Terminal
functions, accessing the NE through its Ethernet interface only.
WARNING:
the LLMAN installation (step [3] on page 518 ) must always be performed before the
1320CT Package Installation (step [4] on page 518 ) . Installing the 1320CT Package
before the LLMAN may result in unproper working. If you have installed the 1320CT
Package without having installed before LLMAN, and after you want to install LLMAN, you
must:
uninstall the1320CT application (see Chapter 410 on page 497 )
install LLMAN and, after, the 1320CT Package, as described in this Appendix.
Procedure:
[1]
Installation startup
1)
Insert the SWP CDROM in the PCs CDROM unit
2)
The TCO Suite startup begins. Please refer to para.22.2.3 on page 148 for the procedure
execution (in particular for JRE Package automatic installation) and the management of special
conditions that could occur
3)
At the end of the TCO Suite startup, the CDROM TCO Suite Main Menu screen appears
(Fig. 339. below); click on Advanced Settings button
Fig. 339. CDROM TCO Suite Main Menu screen
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

517 / 592
After a while, the CDROM TCO Suite Advanced Settings screen appears (Fig. 340. below)
4)
Fig. 340. CDROM TCO Suite Advanced Settings screen

[2]
In the CDROM TCO Suite Advanced Settings screen (Fig. 340. on page 518 ) click on button Java
JRE Package Installation . Please refer to para.22.2.5.1 on page 152 for details.
N.B.
as a matter of fact, the JRE Package Installation should have already been done in step
[1] 2 ) on page 517
[3]
Install LLMAN (Alcatel Lower Layers Manager), as described in para.53.2 from page 519
[4]
Carry out the 1320CT Package Installation (installation in PC of SWP components from the SWP
CDROM): see para.31.5 on page 314 , taking into account that , when you reach para.31.5.3
on page 317 (Next step) you must come back here to execute steps from [5] below
[5]
Install and configure Alcatel Virtual Network Card for Lower Layers, as described in para.53.3
from page 522 (different subprocedures, according to the PC Operating System)
[6]
Complete the Craft Terminal setup carrying out the following phases:
1)
Local copy in PC environment of the TCO Suite:

2)
End of SW installation from SWP CDROM:

3)
NE software downloading preparation:

4)
CT initial configuration:
5)
EML construction:
END OF PROCEDURE
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
518 / 592
USER MANUAL
APPENDICES

53.2 Installation of LLMAN from the SWP CDROM

1)
In the CDROM TCO Suite Advanced Settings screen (Fig. 340. on page 518) click on button
SerialFInterface 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. 341. below) and the installation begins.
Fig. 341. Alcatel Lower Layers Manager splash screen

2)
User is asked to select installation and application language (Fig. 342. below).
Fig. 342. Alcatel Lower layers Manager language selection
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

519 / 592
Then the installation is carried out automatically after a simple confirmation by the user
(Fig. 343. below).
Fig. 343. Alcatel Lower Layers Manager Installation screens

4)
Select Configure Lower Layer and press FINISH button to open next screen (following
Fig. 344. )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
520 / 592
USER MANUAL
APPENDICES

3)

Fig. 344. Alcatel Lower Layers Manager setting screen

5)
In screen of Fig. 344. above, complete the configuration and press OK button.
N.B.
6)
If a network adapter is not running in the PC, you can set the System identifierfield
with a sequence of 12 0. The following window will be displayed.
Press YES button to confirm.
53.2.2 Next step

You have now completed the Installation of LLMAN from the SWP CDROM.
Now, you must proceed with step [4] on page 518
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

521 / 592
At first SWP installation on ECT, after the installation of Alcatel Lower Layer Manager (carried out in
previous para.53.2 on page 519), 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.
53.3.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.53.3.6 on page 546 for details.
53.3.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)
53.3.3
523
Windows 2000 till SP2
53.3.4
529
Windows XP till SP2 (Professional Edition only)
53.3.5
537
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
522 / 592
USER MANUAL
APPENDICES

53.3 Installation and configuration of Alcatel Virtual Network Card for Lower
Layers

53.3.3 Windows NT 4.0

53.3.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. 345. Windows NT installation step 1
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

523 / 592
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. 347. 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.53.3.3.2 on page
525.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
524 / 592
USER MANUAL
APPENDICES


53.3.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. 349. NT configuration step 2) or a dialog box (Fig. 350. NT configuration step 3) may appear.
Follow the instructions until the dialog box (Fig. 351. NT configuration step 4) will appear.
2
3
4
Fig. 348. Windows NT configuration step 1
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

525 / 592
Click Yes to save changes.

Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
526 / 592
USER MANUAL
APPENDICES

Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for Lower
Layers and push OK.
3
4
*** WARNING ***

If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is
necessary, for a correct ECT functionality, to perform an explicit ECT recustomization by executing the
following command:
Start Programs Alcatel SNMPCTKADDON v... SNMP AddOn Customization
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

527 / 592
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.

53.3.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.53.3.6 on page 546.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
528 / 592
USER MANUAL
APPENDICES

53.3.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).
53.3.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. 354. Windows 2000 installation step 1

USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

529 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
530 / 592
USER MANUAL
APPENDICES
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:\WinNT\System32\Drivers\LLmanNIC; type echo %systemroot% from a Command
Prompt window to discover the right location of the WinNT folder) and click OK.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

531 / 592
Click Next in the Start Hardware Installation dialog box.


533.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
532 / 592
USER MANUAL
APPENDICES

53.3.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 Dialup connections
applet from the Control Panel.
Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP
protocol (please refer to Windows 2000 Help).
the Control Panel.
Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the
Network and Dialup connections applet.
Fig. 359. Windows 2000 configuration step 1
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

533 / 592
Uncheck any unneeded component in the Properties dialog box General tab (1). Check and select
the Internet Protocol (TCP/IP) component (2) and click Properties (3).
1
2
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
534 / 592
USER MANUAL
APPENDICES


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 screens Interface Metric field, write 50 (4) and push OK (5)
Having come back to the first screen, push OK (6)
1
2
3
6
5
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

535 / 592
*** WARNING ***

following command:
53.3.4.3 Next step (Windows 2000)

Layers in Windows 2000 environment. Now proceed with the Check for the Network Connections
order, para.53.3.6 on page 546.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
536 / 592
USER MANUAL
APPENDICES

Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Manager
to use it.

53.3.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).
53.3.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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

537 / 592
Fig. 362. Windows XP installation step 1
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
538 / 592
USER MANUAL
APPENDICES
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
539 / 592

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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
540 / 592
USER MANUAL
APPENDICES
Click Next in the The wizard is ready to install your hardware dialog box.


542.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

541 / 592
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 Dialup connections applet.
Fig. 367. Windows XP configuration step 1
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
542 / 592
USER MANUAL
APPENDICES

53.3.5.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows XP
Professional Edition)

Uncheck any unneeded component (disable always the QoS Packet Scheduler 1 ) in the
Properties dialog box General tab. Check and select the Internet Protocol (TCP/IP) component (2)
and click Properties (3).
1
2
3
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

543 / 592
Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK
(4).
1
2
3
4
*** WARNING ***

following command:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
544 / 592
USER MANUAL
APPENDICES


Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOS
over TCP/IP (2) and then push OK (3).

Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers
Manager to use it.
53.3.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.53.3.6 on page 546.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

545 / 592
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. 371. below) verify that it is the first in the list. If necessary, move its
position, using suitable arrows.
Fig. 371. 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 step [6] on page 518
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
546 / 592
USER MANUAL
APPENDICES

53.3.6 Check for the Network Connections order

54 APPENDIX D: GENERAL ON ETHERNET PORT CHARACTERISTICS

AND MANAGEMENT
This Appendix gives summary information that can be useful for the configuration of Ethernet ports.
54.1 Ethernet Physical Interface

The Enhanced Ethernet plugin provides 4 Electrical Gigabit Ethernet ports. Each port performs all
physical layer interface functions and is capable to interface 10/100/1000 Mb/s link partners.
Each Ethernet port can be declared as used (enabled) or unused (disabled default):
when unused, the ethernet physical interface is turned off and all associated communication
alarms are not reported; the associated LEDs are both off.
when used, the ethernet physical interface must be configured and, depending on this
information, the correct management is applied.
54.2 MDI/MDIX crossover

Allows two Ethernet interfaces to be connected directly, without the need to differentiate the cables
as straight or crossover. This feature allows the use of only one type of ethernet cable in field and
does not require ECT/NM management.
54.3 Frame size, Rx checksum and FCS

The Ethernet interfaces support a maximum frame size of 1536 bytes for ports set up as 10/100 Mbit/s
and 9728 bytes (jumbo frame) for ports at 1 Gbit/s.
FCS field, inside each ethernet frame, is checked; if the check is wrong, the packet is discarded.
FCS is always enabled.
54.4 Ethernet capacity

With the 100/1000 BaseT Ethernet interfaces, the PDH transport capability is always less than the
maximum input bit rate, whereas in case of 10BaseT, 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 available frame structure configuration (i.e. 16xE1). Given a gross bit rate, the
combinations of E1 tributaries and data tributaries that can be realized are defined in Tab. 65. on
page 350 .
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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

547 / 592
The total radio capacity allocated for global Ethernet traffic is shared between all enabled Ethernet
ports. The modality of division of the bandwidth among the ports Ethernet enabled is defined from
the mechanism of QoS configured (see point [8] on page 551 ).
When the traffic data bandwidth requested is bigger than available radio capacity two actions are
possible:
if the flow control is enabled, the pause packet is sent to the port that create the congestion in
order to do not loss packets.
Note: it is only applicable to the direction from line to radio transmission where there could be
the traffic congestion, but not to the direction from radio to line transmission.
if the flow control is disabled, the packets according to priority classes will be discarded when
the buffer is full.
The supported pause function is symmetric and asymmetric. The pause function (enable/disable)
is independent of the autonegotiation: in fact, the autonegotiation could be enabled or disabled, but,
in any case, the capability is always fullduplex.
54.6 Ethernet interface management

In terms of Ethernet interface management, the ULS supports the following functional layers:
Ethernet Physical Interface Layer
Ethernet Port Layer
[1]
Ethernet Physical Interface Layer

The Ethernet interfaces can be configured according to two different modalities: manual mode
(or default type, autonegotiation is disabled) or automatic mode (autonegotiation is enabled):
these two modalities are valid always for Fast Ethernet signals, only automatic mode for Gigabit
Ethernet signals. In automatic mode a mechanism of autosensing (the autonegotiation) of
the parameters involved is activated, these parameters are negotiated with the remote Ethernet
interface.
Autonegotiation on a link is exchanged when:
link is initially connected
device at either end of the link is powered up
device is reset or initialized
the management system requires an autonegotiation restart

During autonegotiation, each port automatically chooses its mode of operation by advertising
its abilities and comparing them with those received from its link partner.
The parameters that can be advertise during autonegotiation from each port must be selected
between the following:
Speed: 10 Mbit/s or/and 100 Mbit/s or/and 1000 Mbit/s (all combinations are possible)
Capability: full and/or half duplex (note 1)
Flow control (802.3x): pause disable or pause enable (note 2)

note 1
when the rate is 1000 Mb/s, then the supported capability is always full duplex.
note 2
in half duplex, the back pressure is not supported.
If the remote end has the ports in manual mode and the link partner has the autonegotiation
enabled, the link could be established with 10 or 100 Mbit/s speed and halfduplex capability
(as defined by the standard 802.3).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
548 / 592
USER MANUAL
APPENDICES

54.5 Ethernet flow control

The following items resume the features supported by ULS in terms of Gigabit Ethernet
Physical interface management:
autonegotiation is always enabled only in case of Gigabit Ethernet signal;
the operator can plan one or a set of rates (10 and/or 100 and/or 1000 Mb/s), and allow
to autonegotiate them;
the directionality can be half or fullduplex (when the 10 and/or 100 Mb/s rates are chosen,
the directionality can be half or full duplex, when the 1000 Mb/s rate is chosen, the
directionality is always fullduplex);
when the autonegotiation process fails or when the autonegotiation parameters are
changed, the autonegotiation restart command has to be performed in order to have new
configured parameters effective.
[2]
Ethernet Port Layer

The following items resume the features supported by ULS in terms of Gigabit Ethernet Port
layer management:
the Pause function is allowed only when the capability is fullduplex;
the Pause function can be supported in automatic or manual mode;
the Ethernet Flow Control (EFC) can be enabled or disabled; when it is enabled, PAUSE
function can be symmetric and asymmetric (IEEE 802.3x); the supported asymmetric case
is related to allowed Pause at transmission side, no allowed Pause at receiver side;
in case of remote peer MAC layer without EFC feature, the overflow of the input queues
causes to discard any further received MAC frames: a correct frame received and
discarded because of an input queues overflow, is not counted as a received frame;
total transparency towards the IEEE 802.1Q (VLAN management is presently not
supported);
Ethernet corrupted frames (Tx and Rx side independently) can be discarded or forwarded
to the addressed destination, according to the related SNMP manager request.
54.7 Ethernet Switch

The fundamental component of Enhanced data plugin is the Ethernet switch, which provides the
switching, grooming and queuing functions between the user data ports and radio link.
The Switch is a level 2+ switch able to operate at frame level. The switches are data link layer devices
that enable multiple physical ethernet LAN segments to be interconnected into a single larger
network.
The switch supports the following function:
[1]
MAC Switching
The switch is capable of evaluate the destination address of each frame received and to
transmit the individual frames to the correct egress port in according to information contained
in a database address resolution table and associated to destination address. If switch does
not know on which port to forward the frame (destination address is not present in address
resolution table), it sends the packet on all ports (flooding). The switch must perform half
transparent bridge functionality thats to filter the frames which destination is on the segment
(port) where it was received.
Always enabled by default, no ECT/NM management is necessary.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

549 / 592
MAC Learning
The entry in a database, the address resolution table is written learned the source address
from received unicast packets. The switch supports also static writing of the address resolution
table, these entries are created and updated via programming interface. Up to 4096 entries
(MAC address port mapping) can be stored in the database.
It is always enabled.
[3]
MAC Ageing
In current SWP version, only default values are defined (typical value is 300 seconds, it is an
indicative value, the real range is 300 600 seconds)
The aging process periodically removes dynamically learned addresses from the address
resolution table.
The address aging process is used to ensure that if a node is disconnected from the network
segment, or it become inactive, its entry is removed from address database. Aging makes room
for new active addresses.
[4]
At least four output queues with flexible scheduler

In current SWP version, only default values are defined (typical default configuration is: DWRR
algorithm with weight respectively of 8, 4, 2, 1 for the four queues on each port).
Each egress port can support up to four transmit queues; frames are assigned to each queue
according to their priority. Algorithms type Deficit Weighted Round Robin (DWRR) and High
Queue Preempt (HQP) are used to schedule each transmit queue.
The deficit weighted roundrobin algorithm allows each queue to be serviced in turn, sending
a set amount of packets before moving to the next queue. For every round are sent 8 packets
from queue with highest priority and respectively 4, 2, 1 packets from the queues with lower
priority.
[5]
Frame types
The switch is able to treat Ethernet frames of the following types: Ethernet v2, 802.3, 802.1Q.
No ECT/NM management is necessary.
[6]
IEEE 802.1Q (VLAN management)

In current SWP version, the traffic type IEEE 802.1Q tag is managed in transparent mode (the
switch does not look the tag).
The IEEE 802.1Q tag VLAN feature is enabled including between the other the stripping or
adding of the TAG and VLAN lookups in addition to MAC lookups (this feature can be useful to
logically break a physical LAN into a few smaller logical LAN and prevent data to flow between
the subLAN).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
550 / 592
USER MANUAL
APPENDICES

[2]

[7]
IEEE 802.3x Flow Control

In case of incoming Ethernet traffic leading to exhaustion of buffers on input queues, PAUSE
frames are transmitted in order to slow down remote peer MAC layer.
When the flow control is activated any packets shall not be lost.
The flow control management is foreseen only for the four user ports and not for the port linked
to the FPGA.
[8]
QoS management (IEEE 802.1p, IPV4 ToS & DiffServ, Port based)
The Ethernet switch provides a Quality of Service mechanism to control all streams. The QoS
feature, referred to the four ports (line side) Gigabit Ethernet, provides up to four internal queues
per port (four user ports and one radio) to support four different traffic priorities. These priorities
can be programmed in such a way that highpriority traffic in the switch experiences less delay
than lowerpriority traffic under congested conditions.
For Ethernet flows in the switch, it is possible by CT/NMS (see Fig. 131. on page 231 , and
Fig. 248. on page 352 ) to choose how assign the priority to each packet according to the
information in:
a)
IEEE std 802.1p
The packet is examined for the presence of a valid 802.1P userpriority tag. If the tag is
present the correspondent priority is assigned to the packet.
When 802.1p QoS mechanism is adopted the reference is the standard IEEE
802.1D2004 Annex G User priorities and traffic classes that defines 7 traffic types and
the corresponding user priority values.
Considering that the switch has four egress queues for each port, the mapping 802.1p
value to queue is the following:
Tab. 74. QoS based on IEEE std. 802.1p
802.1P priority
Queue
111,110
Queue 4 (higher priority)
101,100
Queue 3
011,000
Queue 2
010,001
Queue 1 (lower priority)
When an incoming packet is not 802.1p it is assigned to the lowest priority queue.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

551 / 592
DiffServ
When DiffServ QoS mechanism is adopted the classification uses the DS field of the IP
packet header.
Each packet is classified based on DSCP field in the IP header to determine the priority.
Considering that for the switch has four egress queues for each port the mapping DSCP
value (6 bits) to queue is the following:
Tab. 75. QoS based on DiffServ
DiffServ priority
Queue
111000, 110000, 101110, 101000
Queue 4 (higher priority)
100110, 100100, 100010, 100000, 011110,

011100, 011010, 011000
Queue 3
010110, 010100, 010010, 010000, 001110,

001100, 001010, 001000, 000000
Queue 2
all the remaining values
Queue 1 (lower priority)
When an incoming packet has not DiffServ valid value, it is assigned to the lowest priority
queue.
[9]
Link aggregation
In current SWP version, the default corresponds to disabled link aggregation.
The link aggregation (or trunking) feature allows bundling several physical ports together to
form a single logical channel. In this way provides a more resilient end to end connection, and
enables load balancing.
The switch supports:
automatic failover: if one of multiple ports aggregate in a logical link fails, traffic network
is dynamically redirected to remaining good ports in the link.
Mac based trunking: the load balancing traffic depends of the dynamics of MAC address
distribution
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
552 / 592
USER MANUAL
APPENDICES

b)

55 APPENDIX E: ECTEQUIPMENT CONNECTION VIA PUBLIC

SWITCHED TELEPHONE NETWORK
55.1 Introduction
This chapter explains the operations necessary to allow the remote connection to the FInterface, from
a local PC (with external or internal modem) configured as ECT, through a switched telephone line of the
standard Public Telephone Network, as shown in Fig. 372. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.
local side
(ECT side)
remote side
(equipment side)
F Interface
Port COM
Telephone network
PC/ECT
Remote
Modem
Local
Modem
PCLAPTOP/ECT
with internal modem
Fig. 372. ECTEquipment connection via Public Switched Telephone Network
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

553 / 592
The connection has been successfully tested:

a)
b)
c)
with the following types of modems:

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

1)
with external modem:

characteristics as in para.31.1.1 on page 309
2)
with internal modem:

PC laptop Dell Latitude:
Processor equipped:
Operating system:
RAM equipped:
Hard disk equipped:
Internal Modem:
PENTIUM III
Microsoft Windows 2000 v. 5.00.2195 service pack 2
128 Mbytes
10 Gbytes
3COM 56K v.90 Mini PCI MODEM
and with the following local/remote combinations:

Local Modem
Remote Modem
Sportster Flash
Sportster Flash
TD 32 AC
3Com 56K Faxmodem
TD 32 AC
TD 32 AC
Sportster Flash
3Com 56K Faxmodem
TD 32 AC
PC laptop Dell Latitude as in

Sportster Flash
point b ) 2 ) above
3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customers charge.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
554 / 592
USER MANUAL
APPENDICES

55.2 Certified equipment

55.3 Connection cables

In the following figures, the cables for the connections are described:
PC/ECT (DTE)
Cannon 9 pins female
Local Modem (DCE)

Cannon 25 pins male
DCD
DCD
TD
TD
RD
RD
DTR
RTS
DSR
CTS
RTS
DSR
CTS
20
DTR
GND
GND
Fig. 373. ECTLocal external Modem cable
Remote Modem (DCE)
F Interface (DCE)
Cannon 25 pins male
Cannon 9 pins male
TD 2
RD
RD
RTS
RTS
CTS
CTS
DSR
DSR
CTS
20
DTR
GND
GND
TD
Fig. 374. F InterfaceRemote Modem cable
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

555 / 592
55.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. 372. on page 553 for
the distinction between local and remote), relevant to the autoanswer option that must be set in the
remote modem and not set in the local modem.
LOCAL MODEM SETTING
To set the local modem, proceed as follows:
1)
Only for external modem: connect the local modem to the PC/ECT with the cable of Fig. 373. on
page 555.
2)
Only for external modem: Power and switch on the local modem.
3)
On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Bits per second: 38400
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
4)
Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return>
ATT<Return>
ATX3<Return>
AT&W0<Return>
5)
(Best PC default configuration recall)

(Tone Dialling instead than Pulse Dialling)
(Second Signal disabling, avoids problems with PABX)
(Configuration store in NVRAM 0)
Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
556 / 592
USER MANUAL
APPENDICES

55.4 Modem setting

N.B.
For confirmation, the modem configuration can be checked writing the command
ATI4<Return> in the HyperTerminal program window.
Information displayed should be as follows:
ATI4
U.S. Robotics Sportster Flash 56000 Settings...
B0 E1 F1 L2 M1 Q0 V1 X3 Y0
BAUD=38400 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE CID=0
&A3
&M4
&B1
&N0
S00=000
S07=060
S15=000
S25=005
S33=000
S41=004
&C1
&P0
&D2
&R2
S01=000
S08=002
S16=000
S27=001
S34=000
S42=000
&H1
&S0
S02=043
S09=006
S18=000
S28=008
S35=000
&I0
&T5
&K1
&U0
S03=013
S10=014
S19=000
S29=020
S36=014
&Y1
S04=010
S11=072
S21=010
S30=000
S38=000
S05=008
S12=050
S22=017
S31=128
S39=012
S06=004
S13=000
S23=019
S32=002
S40=000
LAST DIALED #:
REMOTE MODEM SETTING
To set the remote modem, proceed as follows:
a)
carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting
b)
execute and store the modem setup, writing in the HyperTerminal program window the same
commands described in step 4 ) for the local modem setting, and adding the following command:
ATS=1<Return>
c)
(Autoanswering setting)
now, setting has been completed. Modem can be switched off and disconnected, if necessary.
N.B.
S00=001
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:
S01=000
USER MANUAL
APPENDICES
S02=043
S03=013
S04=010
S05=008
S06=004
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

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

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

(DTE/DCE flow control disabling)
(Automatic Answer enabling > Only on Remote modem and
wait the message NO CARRIER)
(Configuration store in NVRAM 0)
(Configuration Set to load at switchon: NVRAM 0)
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
558 / 592
USER MANUAL
APPENDICES

55.4.2 TD32 AC Modem setting

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

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

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

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

The following setting must be done:
Control Panel > Alcatel Lower Layer > Serial port > COM3 and Serial port selected
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

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

Finterface and telephone line, operations set up by steps 1 ) thru 4 ) , it is possible to access
the equipment in any moment.
In order to access the equipment by local ECT, proceed as specified in steps 5 ) thru 14 ) .
1)
Connect the remote modem to equipments F interface with the cable of Fig. 374. on page 555.
2)
Connect the remote modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipments F
interface and signed with the wall symbol).
3)
Power and switch on the remote modem.
4)
Be sure remote equipment is switched on and correctly working.
5)
Connect the local modem to the PC/ECT (with the cable of Fig. 373. on page 555.) on the serial
port assigned for the connection with F interface (usually COM1).
6)
Connect the local modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipments F
interface).
7)
Power and switch on the local modem.
8)
On the PC, activate program HyperTerminal and configure the PCLocal Modem serial line with
the following parameters:
* Data Bits:
8
* Parity:
None
* Stop Bit:
1
* Flow control:
None
9)
For PC laptop Dell Latitude only, type the following command inside HyperTerminal program:
AT&C0&D0&R1
N.B.
this command must be typed every time the Hyper terminal session is opened (this
command is not stored in the modem NV RAM).
10 ) Execute the telephone call from the PC writing the following command in the HyperTerminal
program window:
ATDnnn<Return>
where nnn is the telephone network number associated to the remote telephone line (that
which the remote modem is connected to).
11 ) Wait the message indicating the successful connection between local and remote modems.
N.B.
The message text depends on the modem type, as follows:

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

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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
560 / 592
USER MANUAL
APPENDICES

55.6 Setting up the connection

55.7 Changing the ECTequipment connection speed

55.7.1 Introduction
This feature is meant to use modems with speed different from that documented in previous paragraphs,
giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,
56000) with automatic management of modem setup and phone call at ECT startup.
To make change operative, the following operations are necessary:
at equipment side, the configuration must be setup as explained in the para.55.7.2 below,
at PC side, the configuration must be setup as explained in the following para.55.7.3 on page 562,
as far as the modem is concerned, please refer to the constructor documentation.
55.7.2 Configuration at NE side

1)
Login the NE through the TCO Suite Alarms & Settings function (see para.22.3.1 on page
156) using a login profile allowing the Modem Speed change (see Tab. 55. on page 158),
2)
enter the Modem Speed screen and set the required speed (see para.22.3.9 on page 167).
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

561 / 592
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. 376. opens.
Fig. 376. Alcatel Lower Layers utility

In the Subnetwork Type field select Modem.
In the Modem field select the suitable Modem type.
In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK.
In the Phone Number field enter the phone number, which will be automatically called at the ECT startup.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
562 / 592
USER MANUAL
APPENDICES

55.7.3 Configuration at PC side

56 APPENDIX F: PART LISTS OF TOOL KITS

This appendix supplies information referenced to by para.43.2.2 on page 416
These part lists are given for general information purpose. The parts listed in each tool kit could differ from
those actually delivered inside the kit (make reference to the part list accompanying the kit).
56.1 Installation Tool Kit part list

P/N
Description
1AD035000002
HAND TOOL MALE WRENCHE
1AD035000003
870952129
CHIAVE FISSA I6XI7
870952131
CHIAVE FISSA I7XI9
870952417
CHIAVE PIEGATA COMB.ESAG.17
870952706
CHIAVE X ESAG.INCASSATO 6
870959166
CACCIAVITE 5,5X200
879010249
TOOL KEY 5,5 MM
879010250
TOOL KEY 7 MM
8BE815010002
8X10 FIXED SPANNER
8BE815010070
TORQUE WRENCH
8BE815010080
ALLEN WRENCH
8BE815020020
3XIOO SCREWDRIVER
8BE815020021
3.5X100 SCREWDRIVER
8BE815020040
3X60 CROSSHEAD SCREWDRIVER
8BE815020041
4.5X80 CROSSHEAD SCREWDRIVER
8BE815020042
8BE815030000
TOOL KIT
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

563 / 592
P/N
Description
41172010
INSULATED PLUG WITH PLIERS
41172011
ANTISTATIC WRIST BAND
41911001
CORDONE X APPLICAZIONI A
248501099
FEMALE BUTTON TERMINATION
870952129
CHIAVE FISSA I6XI7
870952131
CHIAVE FISSA I7XI9
870952417
870952706
870959166
CACCIAVITE 5,5X200
879010249
TOOL KEY 5,5 MM
879010250
TOOL KEY 7 MM
1AD024120002
UNHOOK TOOL
1AD035000002
1AD035000003
3AL79115AAAA
EXTRACTOR
3DB00489AAAA
COASSIAL CABLE
3DB01229AAAA
CABLE
3DB01400AAAA
COAXIAL CORD PLUG
3DB02519AAAA
CORD
3DB03884AAAA
LEVER
3DB05021AAAA
CORD
3DB06439AAAA
COAXIAL CORD
8BE815010002
8X10 FIXED SPANNER
8BE815010070
TORQUE WRENCH
8BE815010080
ALLEN WRENCH
8BE815020020
3XIOO SCREWDRIVER
8BE815020021
3.5X100 SCREWDRIVER
8BE815020040
8BE815020041
8BE815020042
8BE815030000
TOOL KIT
8BE815030001
TOOL KIT
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
564 / 592

56.2 Maintenance Tool Kit part list
USER MANUAL
APPENDICES

56.3 Station Tool Kit part list

P/N
Description
41172010
INSULATED PLUG WITH PLIERS
41172011
ANTISTATIC WRIST BAND
41911001
CORDONE X APPLICAZIONI A
248501099
FEMALE BUTTON TERMINATION
870952129
CHIAVE FISSA I6XI7
870952131
CHIAVE FISSA I7XI9
870952417
870952706
870959166
CACCIAVITE 5,5X200
879010249
TOOL KEY 5,5 MM
879010250
TOOL KEY 7 MM
1AB026470031
PROTECTION*BIPOLAR
1AB026470031
PROTECTION*BIPOLAR
1AD024120002
UNHOOK TOOL
1AD035000002
1AD035000003
3AL79115AAAA
EXTRACTOR
3DB01229AAAA
CABLE
3DB03884AAAA
LEVER
8BE815010002
8X10 FIXED SPANNER
8BE815010070
TORQUE WRENCH
8BE815010080
ALLEN WRENCH
8BE815020020
3XIOO SCREWDRIVER
8BE815020021
3.5X100 SCREWDRIVER
8BE815020040
8BE815020041
8BE815020042
8BE815030000
TOOL KIT
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

565 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
566 / 592
USER MANUAL
APPENDICES

57 APPENDIX G: DOCUMENTATION GUIDE

This
appendix contains all information regarding:

this Manual, herebelow
the Customer Documentation set this Manual belongs to,
general on AlcatelLucent Customer Documentation,
on page 569
on page 572
57.1 Guide to this Manual

This paragraph contains all information regarding this Manual and is structured as follows:
Applicability of this Manual

Purpose of this Manual
herebelow
on page 568
57.1.1 Applicability of this Manual

a)
Productrelease 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 127.
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 systems equipment, configurations and
features associated to the following SWP versions:
N.B.
SWP Technical Description
SWP Technical Code
SWP Version
(N.B.)
SWP 9400AWY R.2.1 V2.1.1
REF.[a] in Tab. 53. on page 141
V2.1.1
For the meaning of SWP Release and Version, please refer to para.57.3.2 on page 573.
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 manmachine interface, or even in the presence of minor
changes that do not affect negatively the understandability of the procedures described
therein (e.g. a button moved internally to a screen);
b)
furthermore, if the screens contained in this Manual show the versionrelease of the
productrelease, then they are not replaced in the subsequent versions of Manual if their
contents remains unchanged.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

567 / 592
This Manual belongs to the Customer Documentation set envisaged for the equipment specified in
para.57.1.1 on page 567.
Refer to para.57.2 on page 569 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. 57.1.1 point c ) on page 567 ].
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 Operators 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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
568 / 592
USER MANUAL
APPENDICES

57.1.2 Purpose of this Manual

57.2 Documentation set description

This paragraph contains all information regarding the 9400AWY Rel.2.1.1 Customer Documentation and
is organized as follows:
9400AWY Rel.2.1.1 Customer Documentation

herebelow
Product Release Note

on page 571
Additional documentation for 1320CT platform

on page 571
WARNING:
this Documentation set is relevant to 9400AWY Rel.2.1 final version V2.1.1 only.
The Documentation set relevant to 9400AWY Rel.2.1 previous version V2.1.0 and
prerelease version V2.1.1* is contained in the CDROM P/N 3DB16142ABAA.
57.2.1 9400AWY 2.1.1 Customer Documentation

This paragraph lists and briefly describes the documentation set envisaged for 9400AWY Rel.2.1.1.
Please refer to following para.57.3 on page 572 for a general description of AlcatelLucent 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 AlcatelLucent to update it in this Handbook.
The standard Customer Documentation for 9400AWY Rel.2.1.1 is in the English language and is
distributed to Customers only by the following CDROM:
Tab. 76. 9400AWY Rel.2.1.1 Documentation CDROM
REF
DCP 9400AWY 2.1 V2.1.1 CD_ROM
[A]
Technical Code
3DB 16142 ACAA
This CDROM contains, in electronic format (ADOBE ACROBAT pdf files), all handbooks
listed in Tab. 77. on page 570
N.B.
a)
Standard supply
One copy of the 9400AWY Rel.2.1.1 CDROM is automatically delivered to Customer together with
the equipment it refers to (one copy for each terminal).
As 9400AWY Rel.2.1.1 CDROM is a standard commercial item, additional copies can be ordered
and delivered as any other AlcatelLucent 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)
Productdocumentation consistency
Equipment description and layout are always general, i.e. they never describe the actual
composition of the equipment supplied to Customer (this task is entrusted to plantdependent
documentation).
Detailed hardware documentation concerns actually supplied units and is coherent with the
production issue of such units.
Softwareassociated handbooks are coherent with the supplied SWP release.
Copies of the CDROMs regarding a specific productrelease previously delivered can be required
specifying P/N and edition.
c)
Copyright notification
The technical information of the handbooks and CDROMs supplied to Customers is the property
of AlcatelLucent and must not be copied, reproduced or disclosed to a third party without written
consent.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

569 / 592
N.B.
The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a )
on page 569, they do not represent Commercial item P/Ns.
REF
HANDBOOKT NAME
HANDBOOK P/N
HANDBOOKS FOR HARDWARE INSTALLATION (n.b.1)

9400AWY Rel.2.1 Installation Handbook
3DB 16142 BAAA
9400AWY Rel.2.1 Installation Guide
3DB 16142 FAAA
[B]
USER MANUAL (n.b.2)
[C]
9400AWY Rel.2.1 V2.1.1 User Manual

this manual
3DB 16142 EAAA
TRS & SAT DOCUMENT (n.b.3)

[D]
9400AWY Rel.2.1 TRS and SAT
3DB 16142 DAAA
ADDITIONAL DOCUMENTATION
[E]
n.b.1
Interference investigation procedure

n.b.4
3DB 04165 EAAA
These handbooks provide information regarding equipment hardware installation, according

to AlcatelLucent WTD LAB. rules. Moreover, they give the P/Ns of all installation materials
that are not given in this User Manual.
As shown, two versions are available:
the Installation Handbook provides detailed descriptions and instructions, and is mainly
addressed to technicians who have never installed a 9400AWY system before
the Installation Guide provides same information in a more concise way, and is mainly
addressed to technicians who have already installed a 9400AWY system
This User Manual makes reference to the Installation Handbook; using it or the Installation
Guide is on Customer choice.
n.b.2
n.b.3
Contains the Test Report Sheets and the Site Acceptance Test protocol, according to
AlcatelLucent WTD LAB. rules. The source file of this document (MSWord 2000) is also
distributed in the Documentation CDROM.
n.b.4
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
570 / 592
USER MANUAL
APPENDICES

Tab. 77. Handbooks contained in the 9400AWY R.2.1.1 documentation CDROM

57.2.2 Product Release Note

The Product Release Note contains information not strictly necessary for Customers (like the SW Package
Identification data, the list of SW Package Components, the list of ECT SW SubComponents, the
description of new features and modifications, restrictions and known problems, etc.)
The Product Release Note is neither contained in the Documentation CDROM nor automatically
delivered to Customers.
The Product Release Note is available only on specific request to your AlcatelLucent local dealer,
specifying the SWPs Technical Code and ICS (edition) printed on the SWP CDROM itself.
57.2.3 Additional documentation for 1320CT platform
Tab. 78. Documentation common to AlcatelLucent Network Elements using 1320CT platform
REF
CTK
Version
(N.B.)
q 3.0.1
[F]
3AL 79552 AAAA
1320CT Rel.3.x Basic Operators Handbook
3AL 79551 AAAA
Provides general information and operational procedures common to all 1320CT (Craft
terminal) of AlcatelLucent InfoModel Network Elements.
q 3.0.1
[H]
DCP 1320 CT 3.x CD_ROM EN
P/N
Contains, in electronic format, the 1320 CT Operators Handbook REF.[G] to [I]

q 3.0.1
[G]
ITEM
AS Rel.6.5 Operators Handbook
3AL 88876 AAAA
Provides detailed information and operational procedures regarding the alarm Surveillance
software embedded in the 1320CT software package.
q 3.0.1
ELB Rel.2.x Operators Handbook
3AL 88877 AAAA
[I]
Provides detailed information and operational procedures regarding the Event Log Browser
software embedded in the 1320CT software package.
N.B.
The CT Version is displayed when, on the PC, you select the 1320CT application for its
launch.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

571 / 592
This paragraph describes in general the AlcatelLucent 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 AlcatelLucent WTD
(Wireless Transmission Division) only.
57.3.1 CustomerIndependent Standard Customer Documentation
a)
Definition
Standard Customer Documentation, referred to hereafter, must be always meant as
plantindependent and is always independent of any Customization.
Plantdependent and/or Customized documentation, if envisaged by the contract, is subjected to
commercial criteria as far as contents, formats and supply conditions are concerned
N.B.
b)
Plantdependent and Customized documentation is not described here.
Aims of standard Customer Documentation

Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and
maintaining the equipment according to AlcatelLucent Laboratory design and Installation Dept.
choices. In particular:
the contents of the handbooks associated to the software applications focus on the explanation
of the manmachine interface and of the operating procedures allowed by it;
maintenance is described down to faulty PCB location and replacement.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
572 / 592
USER MANUAL
APPENDICES

57.3 General on AlcatelLucent Customer Documentation

57.3.2 Product levels and associated Customer Documentation

See Fig. 377. on page 574.
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 productreleases, which are the real products marketed
for their delivery at a certain productrelease availability date. A certain productrelease performs
more functionalities than the previous one.
E.g. Rel.1.0, Rel.2.0 and Rel.2.1 are three successive productreleases of the same product.
A productrelease comprehends a set of hardware components and at least one Software
Package (SWP); as a whole, they identify the possible network applications and the equipment
performances that the specific productrelease has been designed, engineered, and marketed for.
c)
Configurations and Network Elements

In some cases, a productrelease includes different possible configurations which are
distinguished from one another by different Network Element (NE) types and, from the
management point of view, by different SWPs.
d)
SWP Releases and Versions

This description is 9400AWYspecific:
A 9400AWY SWP is identified by its Denomination, Part Number and Change Status, that
are printed on the CDROMs label.
The SWP Denomination versions first and second digits (e.g. 2.1) correspond to the HW
productrelease 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 bugfixing purposes
and/or minor additional features.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

573 / 592
Customer Documentation
A productrelease(configuration) has its own set of standard Customer Documentation, usually
formed of several handbooks, i.e., in general:
System and Hardware documentation:
one (or more) Technical Handbook(s)
an Installation Handbook
a Commissioning Handbook or LineUp Guide
Software documentation:
a Craft Terminal Operators Handbook, associated to the specific SWPRelease
other Operators Handbooks (typically those associated to the SW platform embedded

in the SWP)
In other cases (e.g. this Manual), above pieces of information are collected in a single document.
PRODUCT
evolution
PRODUCTRELEASE 1.0
PRODUCTRELEASE 2.1
ALTERNATIVE CONFIGURATIONS
CONFIG.A
SWP REL.1.0
PRODUCT
LEVELS
CONFIG.B
evolution
SWP REL.1.1
DOCUMENTATION
CONFIG.A
System & HW
Documentation
SWP REL.1.0
SW
Documentation
SWP REL.1.1
SW
Documentation
Fig. 377. Example of Product levels and associated Customer Documentation
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
574 / 592
USER MANUAL
APPENDICES

e)

58 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS,

GLOSSARY OF TERMS
58.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:
POLARIZATION can be assumed as either horizontal

SYMBOLS
Once you have decided a polarization (e.g.
or vertical
H
)
)
the opposite direction symbol will be opposite polarization (e.g.

V
58.2 List of abbreviations

Tab. 80. List of abbreviations
ABBREVIATION
MEANING
STARTING WITH NUMBERS
9400AWY
Shorthaul 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
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

575 / 592

ABBREVIATION
ALR
Automatic Laser Restart
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

MEANING
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
CoChannel Dual Polarized (Frequency reuse)
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
576 / 592
USER MANUAL
APPENDICES


ABBREVIATION
MEANING
CMISE
Common Management Information Service Element
CMISS
Card Missing
CO
Central Office
COAX
Coaxial
CP
Copolar
CPE
Customer premises equipment
CPI
Incoming parallel contacts
CPO
Outgoing parallel contacts
CPU
Central Processor Unit
CRCn
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
ECC
Embedded Communication Channel
ECS
External Communication Service
ECT
Equipment Craft Terminal
EE
Equipment Engineering
EF
Equipment Failure
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

577 / 592

ABBREVIATION
EFD
Event Forwarding Discriminator
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
EXCBER
Excessive BER

MEANING
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
Horizontal (polarization)
HBER
High Bit Error Rate
HCS
Higher order Connection Supervision
HD
History Data
HDBK
Handbook
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
578 / 592
USER MANUAL
APPENDICES


ABBREVIATION
MEANING
HDB3
High Density Binary 3
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
IJ
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
ITUR (*)
International Telecommunication Union Radiocommunication
ITUT (*)
International Telecommunication Union Telecommunication
JRE
Java Runtime Environment

L
LAC
Local Access Control
LAN
Local Area Network
LAPD
Link Access Procedure on Dchannel
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
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

579 / 592

ABBREVIATION
LOM
Loss Of Multiframe
LOS
Loss Of Signal
LS
Low Speed

MEANING
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
Nearend Defect Second
NA
Not Applicable
NE
Network Element
NES
Network Element Synthesis
NEBC
Nearend 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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
580 / 592
USER MANUAL
APPENDICES


ABBREVIATION
MEANING
ODU
OutDoor Unit
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
ORing 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
USER MANUAL
APPENDICES
Quadrature Amplitude Modulation

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
581 / 592

ABBREVIATION

QOS
MEANING
Quality Of Service
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
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
582 / 592
USER MANUAL
APPENDICES


ABBREVIATION
MEANING
STBY
Standby
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
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
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

583 / 592

ABBREVIATION
USY
Urban Haul Synchronous split mount Radio System
UT
Unavailability Time
UTRAN
Universal Terrestrial Radio Access Network

MEANING
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 ITUR and ITUT,
respectively.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
584 / 592
USER MANUAL
APPENDICES

58.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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

585 / 592
Kilobits per second:

Unit that correspond to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Megabits per second:
Unit that corresponds to the transmission of 106 bits every second.
Network Access Domain:
Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user
can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.
Network Management Level:
Designates the management functions performed on networks elements assembled in a network.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Operator:
The enduser of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Physical Interface:
Electrical or Electrical/Optical transformers that decouple the line signals and adapt the form of signal for
further transmission. This functional block also manages clock extraction, signal loss monitoring and
loopback functions.
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.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
586 / 592
USER MANUAL
APPENDICES

International Telegraph and Telephone Consultative Committee:

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

Telecommunication Management Network:

Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching
supports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
User Profile:
Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the
administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles
installed with Craft Terminal.
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.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

587 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
588 / 592
USER MANUAL
APPENDICES

59 APPENDIX I: CUSTOMER DOCUMENTATION FEEDBACK

The meaning of this appendix is to collect customer feedback about this handbook.
Scope of this activity is the improvement and innovation of customer documentation through the
understanding of customer needs.
Your comments are welcome.
Please send your comment also if you appreciate the handbook.
You can send them to your Local Alcatel Technical Assistance Center.
They will be addressed to the team in charge of the relevant manual.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
How to send feedback:
copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
using the same form (if available) as a file in the relevant documentation CDROM, saving,
filling and sending it by email to your Local Alcatel Technical Assistance Center.
creating a dedicated form on paper or file and sending it to your Local Alcatel Technical
Assistance Center.
We will take into account of your suggestion.

We reserve to modify consequently the handbook according to the correctness and congruence of the
suggestion and requests.
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

589 / 592
Handbook data
Product release, version: 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
Handbook type: USER MANUAL
Handbook part number and edition: 3DB 16142 EAAA Ed.02
General evaluation
SUBJECT
5 (max.)
1 (min.)
1 (min.)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Section evaluation
SECTION
5 (max.)
Front matter
1 : System description
2 : NE management BY TCO Suite and CT
3 : Installation and commissioning
4 : Maintenance and upgrade
5 : Appendices
Your comments (strictly necessary when value is less than 3)
Suggestion for improvements
Which subject to deepen:
How to deepen:
Subject to eliminate or reduce:
Other comments/suggestions:
Error identified
Reader Info
Name:
Date;
Company:
Job:
Address:
Email:
Phone:
Fax:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
590 / 592
USER MANUAL
APPENDICES

CUSTOMER DOCUMENTATION FEEDBACK
USER MANUAL
APPENDICES
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
591 / 592

All rights reserved

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel Lucent.
www.alcatellucent.com
THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK

QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
COD.MANUALE HDBK P/N:
HANDBOOK PRINT AND ASSEMBLY INSTRUCTIONS

ISTRUZIONI DI STAMPA ED ASSIEMAGGIO DEL MANUALE
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 5 SEPARATORI NUMERATI DA 1 A 5
5 SEPARATORS NUMBERED FROM 1 TO 5 ARE NECESSARY
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
fase
step
TARGHETTE - LABELS
Fig. 1. pg. 594
PARTE INIZIALE - FRONT MATTER
INSERIRE SEPARATORE 1 - INSERT SEPARATOR 1
SECTION 2: NE MANAGEMENT BY TCO SUITE AND

CRAFT TERMINAL
10
11
12
USER MANUAL
Handbook print & assembly
numerate
numbered
No pagine
(facciate)
No pages
da from
a to
1/592
28/592
29/592
138/592
139/592
306/592
307/592
406/592
407/592
498/592
499/592
592/592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

593 / 592
9400AWY Rel.2.1
7813151823252838 GHz
SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz
SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links
SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links
SWP 9400AWY R.2.1 V2.1.1

USER MANUAL
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz
SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
VOL.1/1
Fig. 1.
END OF PRINT INSTRUCTIONS FINE DELLE ISTRUZIONI DI STAMPA

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
594 / 592
USER MANUAL
Handbook print & assembly
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY

HANDBOOK EDITORIAL INFORMATION

(not inserted in the CDROM)
PART FOR ALCATELLUCENT INTERNAL USE ONLY
Note for Customers: this part contains editorial information for Alcatellucent internal use only,
and should have not be given to you. Nevertheless, in case you receive it, take into account that
it does not contain information useful for you, so that you can simply ignore it.

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
USER MANUAL
COD.MANUALE HDBK P/N:
1 PUBLISHING NOTES FOR THIS MANUAL
Labels on page 594 are done according to A-Italy binder format.

Source files and printable files of this manual are archived in PDM:
Printable file without revision bars: used for official distribution to Customers (and inserted
in CDROM without this part)
PDF file must be opened with ACROBAT Reader Version 5.0 at least.
(N.B. : it has been created with ACROBAT DISTILLER 7.0)
Source file with revision bars:

SOURCE FORMAT
SIZE Mbytes
TOTAL N.PAGES
PDM ARCHIVE
METHOD
QUICKSILVER 1.5.3
633
600
IDU WINZIP
WARNING: the source file folder contains also the pdf file with revision bars
Notes on revision bars: revision bars point out changes with respect to the previous edition
archived in PDM
N.B.
page numbers specified in table on page 593 are automatic and obtained by
autoreference to tags of:
section first page
section last page, marked by the special component endofsection. WARNING:

components endofsection have white color, to avoid their printing. DO NOT
REMOVE THEM, otherwise table on page 593 will have NO TAGs.
handbook last page, marked by the special component efme.

N.B.
component efme correspond to writing www.alcatellucent.com
on page 592 . DO NOT REMOVE IT, otherwise all pages will have
NO TAGs in footer.
N.B.
additional information (source file) in first catalog.
USER MANUAL
Handbook editorial information
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

595 / 592

2 HANDBOOK HISTORY
ED
DATE
CHANGE NOTE
(yymmdd)
(ECO)
01
070802
02
080125
APPRAISAL AUTHORITY
ORIGINATOR
B.Gabbrielli, V.Fossati, C.Van Kerrebroeck
E.Corradini
M.Nosari, C.Van Kerrebroeck
E.Corradini
00000 57267
2.1 List of the editions and modified parts

The following Tab. 81. indicates the Manual parts new and modified with respect to the previous edition.
Legend: n = new part
m = modified part
blank= part unchanged
Tab. 81. History of this Manual

MANUAL EDITION
01
02
QUICK GUIDE
11
About this manual
12
System overview
13
IDU provisioning and description
14
ODU provisioning, characteristics and description
15
Technical specifications
SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT

TERMINAL
21
SWP 9400AWY R.2.1 description
22
Introduction on TCO Suite and CT views and menus
23
Configuration
24
Equipment
25
Line Interface
26
Radio
27
External points
28
Supervision
29
Protection schemes
210 Loopbacks
211
Diagnosis
212 Performance Monitoring
213 Software Download
214 MIB Management
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
596 / 592
03
04
05
USER MANUAL

Tab. 81. History of this Manual
MANUAL EDITION
01
02
03
04
05
31
SWP installation in PC environment
32
LineUp and Commissioning

41
Maintenance Policy
42
Set and use of EOW functions
43
Maintenance Tools and Spare Parts
44
First Level Maintenance
45
Second Level Maintenance
46
Spare Flash Card management and replacement procedures
47
System hardware upgrade
48
SWP download toward NE
49
ECT & NE upgrade from V2.1.0 to V2.1.1
410 SWP deinstallation
m
m
SafetyEMCEMFESD norms and equipment labelling
TCO suite startup special conditions
Additional SW installation operations for NE management

through the NES ECT serial port
General on Ethernet port characteristics and management
ECTEquipment connection via public switched telephone

network
Part lists of tool kits
Documentation guide
List of symbols and abbreviations, Glossary of terms
Customer documentation feedback
n
m
2.2 Notes on ED.01

ED.01 created on August 2nd, 2007 is the first validated and released edition, associated to SWP
9400AWY R.2.1 V2.1.1 Version V2.1.1* , corresponding to the prerelease version V2.1.1h.
SWP 9400AWY R.2.1 V2.1.1 V2.1.1* is a V2.1.1 not fullfeatures prereleased version distributed to
selected Customers only, and is conceived to support just the management of the new Enhanced Data
plugin (with 4 Gbit Ethernet ports) in addition to the Data plugin (with 2 Fast Ethernet ports).
For additional information, refer to this same part of handbook ED.01 archived in PDM.
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

597 / 592

2.3 Notes on ED.02 draft and released editions
a)
Draft editions neither validated nor officially released issue, for AlcatelLucent internal purposes:
1)
2)
ED.02ADRAFT created on December 19th, 2007

ED.02BDRAFT created on January 22nd, 2008
First draft edition associated to SWP final version V2.1.1 . It has been created starting from the
ED.01 archived in PDM, and introducing the following modifications:
changes for V2.1.1 :
general information in para.11.2 on page 32 and chapter 21 from page 141
changes for elimination of oldtype Data plugin (2 Fast Ethernet ports):
System & HW on pages: 38 , 42 , 44 , 45 , 68 , Tab. 7. from page 70 , 76,

282 , 331 (moreover eliminated two pages after page 333 ), 378 , 391 ,
469 , 474 , and whole Appendix D from page 547
SW management on pages: 210 , 231 , 347 , 349 to 351
updating of Enhanced Ethernet port characteristics and management from

prerelease V2.1.1* to final V2.1.1: modified Appendix D point [8] on pages 551
and 552
other changes for GUI modifications from prerelease V2.1.1* to final V2.1.1 on
pages: 156 to 158 , 166 , 203 , 231 and 232 , 351 and 352 , 363
changes for RF Loopback on pages 46 , 268 , 269 , 385 ; 386 (removed test and
report regarding RF loopback, done also in TRS document ED.03)
changes for RTPC on pages 128 , 238
changes for Transmitted power at antenna port on page 130
changes for Power Measurement on page 243
changes for Flash Cards:
updated P/Ns, denominations and software labels in Tab. 23. on page 93
inserted new identification labels on pages 94 and 95
updated description of documentation set on pages 59 , 567 , 569 and 570
corrections and improvements:
improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495
(and associated WARNINGs on pages 486 and 493 )
elimination of enclosed documents (same information put in new Appendix F on

page 563 )
new appendix Customer documentation feedback on page 589
new standardized template look

continues..
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
598 / 592
USER MANUAL

..continues
corrections submitted for 9400AWY 2.0.6 User Manual ED.01ADRAFT, considered

applicable also to this 9400AWY 2.1.1 User Manual:
submitted by P.Garofoli:
throughout the handbook: integrated antenna replaced by full integrated

antenna
Fig. 41. , Fig. 42. , Fig. 43. and Fig. 44. on pages 114 to 117
submitted by Y.Y.Lebret: ETSI reference standard in para.15.1.1 on page 129
submitted by B.Magnan:
new para.12.6.9 on page 65 ; new N.B. in Tab. 22. on page 90 ;
new WARNING in para.23.4 on page 210 ; one line deleted on page 230
Sample time on page 241 ; directory on pages 241 and 244 ;
EPS Lockout description on page 259 ;
new WARNING in para.29.2.2 on page 261
simplified description of Available loopbacks in para.210.2 on pages 269 to

271
Errors found in previous edition have been corrected.
Revision bars point out major (listed above) and minor (not listed above) modifications of
ED.02ADRAFT and ED.02BDRAFT with respect to ED.01.
Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated
or shifted in other places of the handbook
Tab. 81. from page 596 shows all parts modified (for major and minor changes).
N.B.
NO TAG markers will be replaced by correct values in final edition
USER MANUAL
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

599 / 592

3)
b)
Results of peer review held on January 25 , 2008

Main additional changes with respect to ED.02BDRAFT:
corrections submitted by E.Carpine:
on page 88 : removed this mode includes DCE behavior from CODIR description
on page 89 : Inframe description corrected. Moreover line It is also necessary

that the farend E1#1 tributary is enabled and successfully provisioned added also
on pages 203 and 363
corrections submitted by A.Goncalves:
in Appendix D General on Ethernet port characteristics and management :

removed all warnings on pages 549 , 550 , 552
eliminated the RF loopback detailed scheme, that was present on page following 268
corrections submitted by C.Van Kerrebroeck:
throughout the handbook: SWP 9400AWY IDU32 V2.1.1 replaced by SWP

9400AWY R.2.1 V2.1.1
on page 349 : and two Ethernet port configuration screens replaced by and
four Ethernet port configuration screens
in Tab. 23. on page 93 : eliminated Software Key P/Ns. Moreover, throughout the
handbook: Software Key replaced by Software Label
in Product Release Note on page 571 : removed the lists of DDTs
additional corrections for harmonization with AWY 2.0.6 User Manual ED.01:
corrected para.12.6.9 on page 65
in Tab. 32. on page 109 : 14700 instead of 15988 for 3CC13711ABXX
in para.23.2.3 on page 195 :

.. if in IP Routing Protocol the OSPF protocol has been selected, it is possible to
create OSPF areas
replaced by:
.. if in IP Routing Protocol the OSPF protocol has been selected, it is possible to
choose OSPF areas
in para.23.2.4.3 on page 200 , added Id description
Validated and released edition:

ED.02 created on January 25th, 2008 is the first validated and released edition associated to SWP
9400AWY R.2.1 V2.1.1 final Version V2.1.1 , and fully annuls and replaces previous ED.01 (same
P/N).
Errors found in previous edition have been corrected.
Revision bars point out all modifications of final ED.02 with respect to ED.01. Revision bars in
correspondence of empty lines or empty table rows, point out parts eliminated or shifted in other
places of the handbook. N.B.
Tab. 81. from page 596 shows all parts modified (for major and minor changes).
N.B.
The handbook officially distributed to Customers (as pdf file inside the specific Customer
Documentation CDROM) contains neither revision bars nor this part (handbook editorial
information). Source and pdf files of final ED.02 with revision bars are archived in PDM as
specified in chapter 1 on page 595
END OF INTERNAL DOCUMENT FINE DEL DOCUMENTO INTERNO
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
600 / 592
USER MANUAL

9400AWY User Manual Rel2 1 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9400AWY User Manual Rel2 1 1

Uploaded by

Copyright:

Available Formats

AlcatelLucent 9400AWY

SECTION 1 : SYSTEM DESCRIPTION

9400AWY Rel.2.1 Installation Handbook

3DB 16142 BAAA

9400AWY Rel.2.1 Installation Guide

3DB 16142 FAAA

9400AWY Rel.2.1 V2.1.1 User Manual

3DB 16142 EAAA

9400AWY Rel.2.1 TRS and SAT

3DB 16142 DAAA

3DB 16142 EAAA Ed.02

All rights reserved. Passing on and copying of this

know changes of this issue

read para.11.4 on page 34

know new features of the SWP

read para.11.2 on page 32

GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE

get information on safety, EMC,

read Appendix A on page 501

acknowledge cautions to avoid

read para.11.6 on page 36

have the description of equipment

read para.32.2 on page 331

get operative information regarding

IDU Main unit: read para.13.3 on page 70

IDU Extension unit: read para.13.4 on page 77

E1 Protection box: read para.13.5 on page 79

Services Protection box: read para.13.6 on page 84

Flash Card: read para.13.7 on page 93

Cables and Distributor subracks: refer to the

read chapter 14 on page 97 , in particular:

carry out antenna fine alignment

para.14.7 on page 119

and para.14.7.4 on page 123

read para.32.9 on page 404

INSTALLATION AND COMMISSIONING

carry out installation and

proceed as specified in para.12.6.1 on page 59

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

3DB 16142 EAAA Ed.02

All rights reserved. Passing on and copying of this

Tab. 1. Quick guide

All rights reserved. Passing on and copying of this

Tab. 1. Quick guide

know the consequences of unit

read para.45.4 on page 432

set and use the EOW functions of

read chapter 42 on page 413

provision and manage spare parts

read para.43.3 on page 418

carry out First Level maintenance

proceed as specified in chapter 44 on page 421

carry out preventive maintenance

proceed as specified in para.45.3 on page 431

carry out corrective maintenance

proceed as specified in para.45.5 on page 433

know and use TCO functions

read para.22.2 on page 146

ECT: GENERAL AND LOGIN & LOGOFF

know ECT and RECT characteristics

read para.12.4 on page 54