9400AWY User Manual Rel2.1.3

AlcatelLucent 9400AWY
78131518232538 GHz
shorthaul low/medium capacity digital microwave radio links
9400AWY Rel.2.1
SWP 9400AWY V2.1.3
User Manual
3DB 16142 JAAA
Ed.01
i Navigation principles
permitted without written authorization from AlcatelLucent

document, use and communication of its contents not
This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific
All rights reserved. Passing on and copying of this

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. They 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
FRONT MATTER
ii Preliminary information
iii Cautions to avoid equipment damage
iv Documentation set
v Notes on used TCO Suite and associated User Manual
vi Structure of this manual
vii Notes on present edition
VIII Table of contents
PART A : HARDWARE INSTALLATION HANDBOOK 1

SECTION 1 : HARDWARE INSTALLATION before page 23
PART B : TECHNICAL HANDBOOK 2

SECTION 2 : SYSTEM DESCRIPTION before page 359
3
SECTION 3 : NE MANAGEMENT BY SOFTWARE APPLICATIONS
before page 401
4
SECTION 4 : SW INSTALLATION IN THE PC AND COMMISSIONING
before page 665
5
SECTION 5 : MAINTENANCE AND UPGRADE
before page 737
6
SECTION 6 : APPENDICES
before page 827
9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

FRONT MATTER
2 / 866 3DB 16142 JAAA Ed.01
ii 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 Chapter 12 from page 35.
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 point iv on page 5 is
considered as not enough.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

FRONT MATTER
3DB 16142 JAAA Ed.01 3 / 866
iii Cautions to avoid equipment damage

a) Unit assemblies
Each of the IDU MAIN UNIT and IDU EXTENSION UNIT is assembled inside its own box and must
be considered an unique item from the service and maintenance points of view. Such an assembly
is supplied by AlcatelLucent as it is and must never be disassembled , with the exception of
operations described in para.57.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.
COILED CORD
ELASTICIZED BAND
Fig. 1. Antistatic protection device kit
c) Screw tightening torque

In normal operation conditions, all screws (fixing subracks to the rack, fixing cables to connectors,
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 and/or in difficult deinstallation operations, if
necessary.
N.B. This statement is referenced to in many parts of this manual, when necessary.
d) Tightening torque for assembling other equipment parts

To fix other equipment parts, the tightening torque to be used is specified in various parts of the
following chapters:
Chapter 16 (ODU), from page 137
Chapter 17 (IDUODU cable), from page 189
e) 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.
f) Craft Terminal 9400AWY RS232 cable connection / disconnection

If the 9400AWY equipment is switched on, to connect or disconnect the CT RS232 cable (at IDU Main
Units F interface, and/or at PC side), the PC must be switched off.

FRONT MATTER
4 / 866 3DB 16142 JAAA Ed.01
iv Documentation set
a) 9400AWY V2.1.3 Documentation CDROM (mandatory)

The standard Customer Documentation for 9400AWY V2.1.3 is distributed to Customers only by a
specific documentation CDROM, which contains, in electronic format, the following documents:
User Manual : this document
other possible documents. If present, their use is explained in the CDROM menu pages.
b) TCO Suite User Manual (mandatory)
The 9400AWY V2.1.3 NE software management is performed by the SWP TCO Suite, which is
distributed to Customers by a specific SWP TCO Suite CDROM.
The TCO Suite User Manual is contained, in electronic format, in the specific SWP TCO Suite
CDROM. Please, read carefully following point v
c) Plantdependent documentation (mandatory)
The operations for the Hardware Installation (described in the part A of this manual, from page
23 ), and for the LineUp and Commissioning (described in Chapter 42 from page 675 ), must
be done according to specific plantdependent documentation, that can be supplied by
AlcatelLucent, on contract basis.
If such specific plantdependent documentation is not available, Customer must be able to define
relevant data by Himself.
d) Product Release Notes (optional)
Please, refer to point [2] on page 407
v Notes on used TCO Suite and associated User Manual
The SWP TCO SUITE Rel.1.7 is the first TCO Suite version able to manage the 9400AWY V2.1.3
NE,
other successive versions of TCO Suite, able to manage it, may be made available in future,
besides the AWY V2.1.3, the SWP TCO SUITE Rel.1.7 is able to manage other versions of the
9400AWY.
Therefore:
if you use the SWP TCO SUITE Rel.1.7:
almost all information present in the SWP TCO SUITE Rel.1.7 User Manual is contained also
in this 9400AWY V2.1.3 User Manual. Only the following information must be retrieved from
the SWP TCO SUITE Rel.1.7 User Manual:
PC requirements
procedures to install the SWP TCO SUITE in the PC
this 9400AWY V2.1.3 User Manual does not give any information regarding the management,
by the SWP TCO SUITE Rel.1.7 , of the other versions of 9400AWY (i.e. different from V2.1.3).
For such different versions, refer to the SWP TCO SUITE Rel.1.7 User Manual
if you use a SWP TCO Suite with version greater than SWP TCO SUITE Rel.1.7, refer to the User
Manual contained in its SWP TCO Suite CDROM to retrieve information regarding possible new
management features regarding the 9400AWY V2.1.3 NE.
N.B. Information relevant to SWP TCO Suite with version greater than SWP TCO SUITE
Rel.1.7, if any, must be considered preliminary, subject to change and without any
obligation on the part of AlcatelLucent.

FRONT MATTER
3DB 16142 JAAA Ed.01 5 / 866
vi Structure of this manual

Information in this manual is divided into the following parts:

a) Front matter
This part, with general information, warnings, and table of contents.
b) part A: the Hardware Installation Handbook, starting on page 23 , containing the:
SECTION 1: HARDWARE INSTALLATION
This section provides whole information regarding Equipment hardware installation and
network interconnections, according to AlcatelLucent WTD LAB. rules. Moreover, it contains
the whole operative information on:
provisioning of equipment items (P/Ns, equipping rules)
their physical position in the system
unit assembly and front panel drawings, with the description on the access point usage
(connectors, visual indicators, buttons)
cables (drawings and connection tables)
c) part B: the Technical Handbook, starting on page 359 , containing the following sections:
SECTION 2: SYSTEM DESCRIPTION on page 360
This section provides the equipment description (at system, IDU and ODU levels), introduces
the basic information regarding the 9400AWY Rel.2.1 HW architecture, and gives its technical
characteristics.
SECTION 3: NE MANAGEMENT BY SOFTWARE APPLICATIONS on page 401
This section gives the description and use of the SW tools available for the NE management.
SECTION 4: SW INSTALLATION IN THE PC AND COMMISSIONING on page 665
This section provides the whole operative instructions for the preparation of the Craft Terminal
based on the SWP TCO SUITE CDROM and the SWP 9400AWY V2.1.3 CDROM, and for
the LineUp and Commissioning of the two NEs making up the radio link.
SECTION 5: MAINTENANCE AND UPGRADE on page 737
This section contains the whole logical and operative information for the equipment
maintenance and system SW and HW upgrade.
SECTION 6: APPENDICES on page 827
In this section some additional information and instructions are given:
Appendix A General on Ethernet port characteristics and management
Appendix B ECTEquipment connection via public switched telephone network
Appendix C List of symbols and abbreviations, Glossary of terms
Appendix D Customer documentation feedback
d) Handbook print and assembly instructions This part (after handbook last page 866 ):
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.
vii Notes on present edition
ED.01 is the first validated and released edition of this 9400AWY V2.1.3 User Manual, which applies to
the set of systems equipment, configurations and features associated to the SWP 9400AWY V2.1.3 and
to the SWP TCO Suite Rel.1.7. Please, read carefully previous point v

FRONT MATTER
6 / 866 3DB 16142 JAAA Ed.01
viii Table of contents
i Navigation principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ii Preliminary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
iii Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
iv Documentation set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
v Notes on used TCO Suite and associated User Manual . . . . . . . . . . . . . . 5
vi Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
vii Notes on present edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Part A: Hardware Installation Handbook . . . . . . . . . . . . . . . . . . . . . . . 23
SECTION 1: HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

11 INSTALLATION AND COMMISSIONING SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
11.1 Objects of this procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
11.2 Main phases for 9400AWY hardware and software installation . . . . . . . . . . . . . . . . . 26
11.3 Hardware installation rules and suggested phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.3.1 Hardware installation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.3.2 Suggested phases for 9400AWY hardware installation . . . . . . . . . . . . . . . . . . . . . . . . 28
12 SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING . . . . . . . . . . . . . . . . . . . 35

12.1 Summary of labels for safety and warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12.2 Compliance with International Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
12.3 Safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
12.3.1 General safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.3.2 Specific safety rules in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.3.3 List of safety requirements for workers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
12.3.4 Labels Indicating Danger, Forbiddance, Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
12.3.5 Dangerous Electrical Voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
12.3.6 Equipment connection to earth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
12.3.7 EMF safety instructions (microwave radiations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
12.3.8 Risks of Explosions: labelling and safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . 45
12.3.9 Moving Mechanical Parts: labelling and safety instructions . . . . . . . . . . . . . . . . . . . . . 45
12.3.10 Heatradiating Mechanical Parts: labelling and safety instructions . . . . . . . . . . . . . 45
12.4 Electromagnetic Compatibility (EMC norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.4.1 EMC General Norms Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.4.2 EMC General Norms Turnon, Tests & Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.4.3 EMC General Norms Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.5 Equipment protection against electrostatic discharges (ESD norms) . . . . . . . . . . . 47
12.6 Suggestions, notes and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.7 9400AWY equipmentspecific identification labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

FRONT MATTER
3DB 16142 JAAA Ed.01 7 / 866
13 RACK INSTALLATION AND GROUNDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
13.1 Safety rules for rack positioning and fastening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

13.2 ETSI Rack installation and grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

13.2.1 ETSI Rack positioning and fastening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13.2.2 ETSI Rack fixing the rack using expansion bolts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13.2.3 ETSI Rack fixing to floating floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.2.4 ETSI Rack grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.3 Laborack installation and grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
13.3.1 Laborack installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
13.3.2 Laborack grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
13.4 Wall mounting kit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
14 TOP RACK UNIT (TRU) INSTALLATION AND CABLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

14.1 General installation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
14.2 Introduction to Top Rack Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
14.3 Top Rack Unit components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
14.4 Top Rack Unit installation and cabling steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
14.5 Power Supply installation kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
14.5.1 Kit components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
14.5.2 Assembly procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
14.5.3 Steps for the connection to the TRU of the power supply cables . . . . . . . . . . . . . . . . 66
14.6 Types and section of cables for grounding and power supply . . . . . . . . . . . . . . . . . . 67
15 INDOOR UNIT INSTALLATION AND CABLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

15.1 Labels affixed on the IDU Main and Extension units . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
15.2 Installation and cabling of IDU components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
15.2.1 Composition, installation and cabling rules for IDU components . . . . . . . . . . . . . . . . 71
15.2.2 Suggested IDU installation and cabling procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
15.3 IDU configuration types and cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
15.3.1 16E1 IDU 1+0 with/without Audio and User Service Channel plugin, without
Service Protection box and without E1 distributor subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
15.3.2 16E1 IDU 1+0 with Audio and User Service Channel plugin, and with distributor
120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
15.3.4 16E1 IDU 1+0 with Audio and User Service Channel plugin, Enhanced Data
plugin and with distributor 120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
15.3.5 32E1 IDU 1+0 with/without Audio and User Service Channel plugin, without
Service Protection box and without E1 distributor subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
15.3.8 16E1 IDU 1+1 radio protected with Audio and User Service Channel plugin,
and with distributor 75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
and with distributor 120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Enhanced Data plugin, and with distributor 75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . 115
Enhanced Data plugin, and with distributor 120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

FRONT MATTER
8 / 866 3DB 16142 JAAA Ed.01
15.3.14 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin,

Enhanced Data plugin, and with distributor 75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . 125
Enhanced Data plugin, and with distributor 120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
and with distributor 75 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
15.4 IDU horizontal and vertical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
15.4.1 Minimum distances between systems installed horizontally in the rack . . . . . . . . . . . 133
15.4.2 Minimum distances between systems installed vertically in the rack . . . . . . . . . . . . . 135
16 OUTDOOR UNIT INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

16.1 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
16.1.1 Safety, EMC, EMF, and ESD norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
16.1.2 Tutorial information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
16.1.3 P/Ns of installation materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
16.1.4 Installation near a wall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
16.2 ODU types and ODU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
16.2.1 ODU mechanical design and identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
16.2.2 ODU operative information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
16.2.3 Labels affixed on the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
16.3 1+0 ODU installation (full integrated antenna) all frequencies . . . . . . . . . . . . . . . . 150
16.3.1 Typical installation layout of 1+0 ODU full integrated antenna . . . . . . . . . . . . . . . . . . 150
16.3.2 Suggested installation procedure of 1+0 ODU full integrated antenna . . . . . . . . . . . 151
16.4 1+0 ODU installation with non integrated antenna all frequencies . . . . . . . . . . . . 153
16.4.1 Typical installation layout of 1+0 ODU Non integrated antenna . . . . . . . . . . . . . . . . 153
16.4.2 Suggested installation procedure of 1+0 ODU not integrated antenna . . . . . . . . . . 154
16.5 1+1 ODU installation (full integrated antenna, all frequencies) . . . . . . . . . . . . . . . . . . 157
16.5.1 Typical installation layout of 1+1 ODU full integrated antenna . . . . . . . . . . . . . . . . . . 157
16.5.2 Suggested installation procedure of 1+1 ODU full integrated antenna (1338 GHz) 158
16.5.3 Suggested installation procedure of 1+1 ODU full integrated antenna (78 GHz) . 163
16.6 1+1 ODU installation with not integrated antenna all frequencies . . . . . . . . . . . . . 166
16.6.1 Typical installation layout of 1+1 ODU Non integrated antenna . . . . . . . . . . . . . . . . 166
16.6.2 Suggested installation procedure of 1+1 ODU not integrated antenna
(1338 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
16.6.3 Suggested installation procedure of 1+1 ODU not integrated antenna (78 GHz) . 171
16.7 Full Indoor ODU configurations (78 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
16.7.1 7 8 GHz Full Indoor ODU configuration for installation in LABORACK . . . . . . . . . . 176
16.8 ODU system grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
16.9 Installing the Flextwist waveguide (not integrated antenna cases) . . . . . . . . . . . . 183
16.10 Aligning the antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
16.10.1 Antenna prepointing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
16.10.2 Fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
16.11 Solar shield installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
17 IDUODU CABLE INSTALLATION MATERIAL AND INSTALLATION PROCEDURE . . . . 189

17.1 Installation components for IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
FRONT MATTER
3DB 16142 JAAA Ed.01 9 / 866
17.1.1 Maximum length and cable types to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
17.1.2 Nconnector for IDU / ODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

17.1.3 IDU / ODU cable grounding kit assembling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

17.2 Suggested IDUODU cable installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

18 NETWORK INTERCONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
18.1 Introduction on NMS channel and EOW audio continuity . . . . . . . . . . . . . . . . . . . . . . 197
18.1.1 Solutions for NMS channel continuity between two colocated 9400AWY R.2.1
NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
18.1.2 Interconnections between a 9400AWY R.2.1 NE with other AlcatelLucent
colocated radio transmission NE types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
18.2 9400AWY 9400AWY interconnections without the Service Protection Box . . . . . 198
18.2.1 NMS Continuity without the Service Protection Box, through OS Ethernet ports
and ALM_NMS connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
18.2.2 NMS Continuity without the Service Protection Box, through OS Ethernet port
and Ethernet port (of Enhanced Ethernet plugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
18.3 General on interconnections with the Service Protection Box . . . . . . . . . . . . . . . . . . 208
18.3.1 EOW audio continuity and EOW party line structure in 9400AWY R.2.1 . . . . . . . . . . 208
18.3.2 General on NMS channel and EOW audio continuity . . . . . . . . . . . . . . . . . . . . . . . . . . 209
18.3.3 NMS channel and EOW audio continuity with the Service Protection Box . . . . . . . . 210
18.3.4 Available supports for the Service Protection Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
18.4 9400AWY 9400AWY interconnections with the Service Protection Box . . . . . . . . 213
18.4.1 NMS Continuity with the Service Protection Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
18.4.2 AUDIO Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
18.4.3 NMS Ring Protection with Audio Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
18.4.4 ESC Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
18.5 9400AWY MELODIE SNMP interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
18.5.1 NMS Continuity with Audio Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
18.5.2 Service Channel Continuity (MELODIE 1+0 classic) . . . . . . . . . . . . . . . . . . . . . . . . . . 224
18.5.3 Service Channel Continuity (MELODIE 1+0 Light) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
18.5.4 Service Channel Continuity (MELODIE 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
18.5.5 Service Channel Continuity (MELODIE 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
18.6 9400AWY MELODIE RQ2 interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
18.6.1 9400AWY NMS_V11 Transport (MELODIE 1+0 Classic) . . . . . . . . . . . . . . . . . . . . . . . 228
18.6.2 9400AWY NMS_V11 Transport (MELODIE 1+0 Light) . . . . . . . . . . . . . . . . . . . . . . . . . 230
18.6.3 9400AWY NMS_V11 Transport (MELODIE 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
18.6.4 9400AWY NMS_V11 Transport (MELODIE 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
18.6.5 RQ2 9.6 Kb/s Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
18.7 E1 interconnections between 9400AWY and 9500MPRE MSS . . . . . . . . . . . . . . . . . . 237
19 UNPACKING AND WAREHOUSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

19.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
19.2 Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
19.2.1 Preliminary checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
19.2.2 Unpacking phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
19.2.3 Shipping crate content check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
19.3 Warehousing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
110 IDU INSTALLATION COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
111 ODU INSTALLATION COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

111.1 Full integrated or Not Integrated antenna installation components . . . . . . . . . . . . 250
111.1.1 9470 AWY ODU installation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
111.1.2 9413 AWY ODU installation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

FRONT MATTER
10 / 866 3DB 16142 JAAA Ed.01
111.1.3 9415 AWY ODU installation components ................................. 253



111.2 Part lists and characteristics of ODU transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
111.2.1 Part lists of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
111.2.2 Part lists of ODUs with embedded diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
111.3 Types of RF couplers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
111.3.1 RF couplers for 7/8GHz bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
111.3.2 RF couplers for bands from 13 to 38GHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
111.4 Types of Pole Mounting Installation kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
111.4.1 FULL INTEGRATED ANTENNA Pole Mounting Installation kits . . . . . . . . . . . . . . . . 283
111.4.2 NON INTEGRATED ANTENNA Pole Mounting Installation kits . . . . . . . . . . . . . . . . 284
111.5 Types of nose adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
112 VIEWS OF IDU UNITS, CONNECTOR PINOUT, AND SIGNAL DESCRIPTION . . . . . . . 287
112.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
112.2 Description of IDU Main unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
112.2.1 IDU Main Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
112.2.2 ECT RS232 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
112.2.3 OS (or ECT) 10/100BaseT connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
112.2.4 Gbit Ethernet tributaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
112.3 Description of IDU Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
112.3.1 IDU Extension Unit LEDs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
112.4 Description of E1 Protection box (Tributary Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
112.4.1 E1 Protection box: pinout of lineside connectors . . . . . . . . . . . . . . . . . . . . . . . . . . 297
112.5 Description of Services Protection box (Auxiliary Service Panel) . . . . . . . . . . . . . . 301
112.5.1 Services Protection box: pinout of lineside connectors . . . . . . . . . . . . . . . . . . . . . 302
112.6 Power Supply connector pinout (Main and Extension units) . . . . . . . . . . . . . . . . . 306
112.7 Connector for IDUODU cable (Main and Extension units) . . . . . . . . . . . . . . . . . . . . 306
112.8 1/16 E1 I/O SCSI 68pin Female connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
112.9 17/32 E1 I/O SCSI 68pin Female connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
112.10 ALMNMS (G703/V11) SubD 44pin Female connector . . . . . . . . . . . . . . . . . . . . . . 311
112.11 AUDIOUSER SERV SubD 44pin Female connector . . . . . . . . . . . . . . . . . . . . . . . . 313
112.12 USER SERV SubD 44pin Female connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
112.13 Description of user signals with alternative connectors . . . . . . . . . . . . . . . . . . . . . 316
112.13.1 E1 signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
112.13.2 Alarms and Housekeeping signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
112.13.3 Alternative connectors for Audio, NMS, and User Service Channels signals . . . . 321
112.13.4 NMS V11 Audio 1 signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
112.13.5 NMS G703 Audio 2 signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
112.13.6 User service channels signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
113 DESCRIPTION OF INTERCONNECTION AND SIGNAL CABLES . . . . . . . . . . . . . . . . . . . . 327

113.1 Cable 3CC07759ABAA Cable for distributor BNC 8 x 2 Mbit/s (L= 2m) . . . . . . . . 329
113.2 Cable 3CC7885ABAA Cable for distributor 1.6/5.6 8 x 2 Mbit/s (L= 2m) . . . . . . . 330
113.3 Cable 3CC52115ABAA (L= 15m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
113.4 Cable 3CC52116AAAA (L= 0.5m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
113.5 Cable 3CC52117ABAA (L= 15m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
113.6 Cable 3CC52118AAAA (L= 1m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

FRONT MATTER
3DB 16142 JAAA Ed.01 11 / 866
113.7 Cable 3CC52119AAAA (L= 1.6) or 3CC52120AAAA (L= 6.4m) . . . . . . . . . . . . . . . . . . 335
113.8 Cable 3CC52121AAAA (L= 1m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

113.9 Cable 3CC52130AAAA (L= 1.6m) or 3CC52131AAAA (L= 6.4m) . . . . . . . . . . . . . . . . 337

113.10 Cable 3CC52132AAAA (L= 1m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
113.11 Cable 3CC52133AAAA SCSI68 120 Ohm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
113.12 Cable 3CC52134AAAA Cord 120 Ohm SCSI68/DSUB37 2 x 16 pairs . . . . . . . . 341
113.13 RJ45RJ45 Cat.5e Ethernet cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
113.13.1 RJ45RJ45 Cat.5e Direct Ethernet cables 3CC52141Axxx . . . . . . . . . . . . . . . . . . 343
113.13.2 RJ45RJ45 Cat.5e Cross Ethernet cables 3CC52142Axxx . . . . . . . . . . . . . . . . . . 343
113.14 Cable 3CC52143ABAA (L= 1.6m) or 3CC52143ACAA (L= 6.4m) . . . . . . . . . . . . . . . 344
113.15 Cables 3CC52150AAAA (L=1.6 m) and 3CC52150ABAA (L=6.4 m)
SCSI68/SCSI68 M/M CROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
113.16 Cable 3CC52157AAAA 2 SCSI MALE TO 4 TERMINALS MODULES . . . . . . . . . . 346
113.17 Cable 3DB05594AAA SubD 15pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
113.18 Cable 3DB05922AAAA (L= 1.6m) or 3DB05923AAAA (L= 6.4m) . . . . . . . . . . . . . . . 349
113.19 Cable 3DB10063AAAA (L= 1.6) or 3DB10064AAAA (L= 6.4m) . . . . . . . . . . . . . . . . . 350
113.25 Cable 3DB10100AAAA (L= 1m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
113.26 Cable 3DB10101AAAA (Adapter ESC/NMS V1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
113.27 Cable 3DB16126ABAA SCSI100 wire for 1+1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Part B: Technical Handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
SECTION 2: SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

21 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
21.1 Main characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
21.2 Equipment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
21.2.1 Splitmount architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
21.2.2 IDU (Indoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
21.2.3 ODU (Outdoor Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
21.2.4 ODU and antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
21.2.5 IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
21.3 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
21.3.1 Available system configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
21.3.2 1+0 Unprotected configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
21.3.3 1+1 Protected Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
21.3.4 Detailed IDU block diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
21.3.5 IDUODU and station compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
21.4 Provisioning of equipment items (summary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
22 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

22.1 General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
22.1.1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
22.1.2 Reference system standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
22.1.3 RF channelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
FRONT MATTER
12 / 866 3DB 16142 JAAA Ed.01
22.1.4 Transmitted power at antenna port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
22.1.5 99% power channel bandwidth and Emission Designator . . . . . . . . . . . . . . . . . . . . . . 393
22.1.6 ETSI System Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

22.1.7 Protection switching system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

22.2 Tributary interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

22.3 Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
22.4 Maximum capacity and Modulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
22.5 IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
22.6 Manmachine interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
22.7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
22.8 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
22.9 Mechanical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
22.10 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
22.10.1 Operating environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
22.10.2 Electromagnetic compatibility/safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
22.10.3 Waste from Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . . . . . . . 399
22.11 Dismantling & Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
SECTION 3: NE MANAGEMENT BY SOFTWARE APPLICATIONS . . . . . . . . . 401

31 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
31.1 Flash Card description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
31.1.1 Flash Card part numbers and associated Licence Strings . . . . . . . . . . . . . . . . . . . . . 404
31.1.2 Physical description of Flash Cards & Licence Strings . . . . . . . . . . . . . . . . . . . . . . . . . 405
31.2 Description of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs . . . . . . . . . . 407
31.2.1 Part numbers of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs . . . . . . 407
31.2.2 Notes on SWP CDROM identification, and Product Release Note . . . . . . . . . . . . . 407
31.2.3 SWP 9400AWY V2.1.3 CDROM contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
31.2.4 SWP TCO SUITE Rel.1.7 CDROM contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
32 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE, AND SECURITY
POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
32.1 Types of physical access from the PC to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
32.2 PCNE network addressing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
32.2.1 NEs management interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
32.2.2 NEs local IP address and Ethernet Configuration IP address . . . . . . . . . . . . . . . . 414
32.2.3 NE reachability from the CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
32.2.4 Networking scenarios for PC connection to the NEs local IP address . . . . . . . . . . . 416
32.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
32.3.1 Summary of security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
32.3.2 Security by operator profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
32.3.3 Security by community string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
32.3.4 Security by access lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
33 GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

33.1 Preparation of the Craft Terminal based on SWP TCO SUITE . . . . . . . . . . . . . . . . . . . 423
33.2 Equipment SW management by SWP TCO SUITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
33.2.1 Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
33.2.2 Procedures for the management of the NE software . . . . . . . . . . . . . . . . . . . . . . . . . . 426
33.2.3 NE data compatibility between SWP 2.1.x versions . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
33.3 Startup and functions of the TCO SUITE Main Menu screen . . . . . . . . . . . . . . . . . . . 432
33.4 Checks the operator must do before accessing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . 433

FRONT MATTER
3DB 16142 JAAA Ed.01 13 / 866
33.5 Common behavior of NE login, and application logoff, for the NEinteractive
Provisioning Tool and Alarms & Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

33.5.1 Constraints and preliminary checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

33.5.2 NE login procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

33.5.3 Application logoff procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
33.6 Close Current Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
33.7 Operational & Maintenance WebEML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
33.8 Operational & Maintenance 1320CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
34 PROVISIONING TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

34.1 Provisioning Tool overview, and startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
34.2 Full Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
34.2.1 Note on the use of the bottom buttons available in the screens . . . . . . . . . . . . . . . . . 448
34.2.2 Full Configuration Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
35 ALARMS & SETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

35.1 Alarms & Settings overview, startup, and closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
35.2 Alarms & Settings functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
35.2.1 Date & Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
35.2.2 Configuration Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
35.2.3 Configuration Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
35.2.4 Get Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
35.2.5 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
35.2.6 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
35.2.7 Modem Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
35.2.8 Licence Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
35.2.9 NAT Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
36 NETO (NETWORK ELEMENT OVERVIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

36.1 General on NEtO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
36.1.1 NEtO functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
36.1.2 NEtO sessions and constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
36.2 NE access constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
36.3 Summary of actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
36.3.1 Preliminary operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
36.3.2 Operations with NEtO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
36.4 Details on NEtO screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
36.4.1 Supervision Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
36.4.2 Supervision and Alarm Synthesis roundshaped icons . . . . . . . . . . . . . . . . . . . . . . . . 505
36.4.3 NEtO screen minimize and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
36.4.4 NEtO icon in the tray bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
36.4.5 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
36.4.6 Command Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
36.4.7 How to close the NEtO session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
36.5 NE list management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
37 9400AWY WEBEML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

37.1 How to open the 9400AWY NE WebEML main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
37.2 9400AWY main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
37.3 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
37.3.1 Resource Tree Area and Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
37.3.2 Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
37.4 Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

FRONT MATTER
14 / 866 3DB 16142 JAAA Ed.01
37.5 Severity alarm synthesis, and Domain alarm synthesis . . . . . . . . . . . . . . . . . . . . . . . . 517
37.6 Management state control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
37.7 Access state (allow or inhibit NE Craft Terminal access) . . . . . . . . . . . . . . . . . . . . . . . 519

37.7.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . 519
37.7.2 Switching from the Craft Terminal access state back to the OS access state . . . . . 519
37.8 Introduction to the WebEML menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
37.8.1 Security by operator profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
37.8.2 Menu organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
37.8.3 Command button policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
37.8.4 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
37.8.5 Views menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
37.8.6 Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.8.7 Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.8.8 Supervision menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
37.8.9 SW download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
38 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
38.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
38.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
38.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
38.2.2 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
38.2.3 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
38.2.4 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
38.2.5 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.2.6 Vlan Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
38.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
38.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
38.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
38.4.1 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
38.4.2 Link Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
38.4.3 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
39.1 Main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
39.2 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
39.2.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
39.2.2 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
39.2.3 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
39.3 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
39.4 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
39.4.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
39.4.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
39.4.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
310 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

310.1 Areas of the Line Interface domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
310.2 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
310.2.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
310.2.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
310.2.3 Tributaries PDH Configuration tab panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
310.2.4 NMS interfaces Configuration tab panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
310.2.5 Data Tributaries Configuration tab panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568

FRONT MATTER
3DB 16142 JAAA Ed.01 15 / 866
311 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
311.1 Areas of the Radio domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

311.2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

311.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
311.3.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
311.3.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
311.3.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
311.4 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
311.5 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
311.5.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
311.5.2 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
311.6 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
311.6.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
311.6.2 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
311.7 BER measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
312 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

312.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
312.2 Output External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
313 MANAGEMENT OF THE SECURITY FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

313.1 Management of security by operator profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
313.2 Management of security by community string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
313.3 Management of security by access lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
314 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

314.1 Default repository folders of MIB backup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
314.2 Craft Terminal commands for the management of MIB backup files . . . . . . . . . . 600
314.3 How to perform the MIB backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
314.4 How to perform the MIB restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
314.5 How to remove a MIB backup file from the repository folder . . . . . . . . . . . . . . . . . 604
315 ALARMS MONITOR AND EVENT LOG BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

315.1 Log switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
315.2 Alarms Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
315.2.1 Alarms Monitor functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
315.2.2 Alarms Monitor startup for one single NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
315.2.3 Alarms Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
315.2.4 Multiple NE Alarms Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
315.2.5 Filters menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
315.2.6 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
315.2.7 Printing the alarms and logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
315.2.8 Exporting the alarms and logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
315.2.9 Navigate from AM to USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
315.2.10 Navigate from USM to AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
315.2.11 Shortcut icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
315.3 Event Log Browser (ELB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
315.3.1 ELB scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
315.3.2 ELB startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
315.3.3 Event Log Table screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

FRONT MATTER
16 / 866 3DB 16142 JAAA Ed.01
316 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
316.1 Software Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
316.2 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

316.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

316.2.2 Remote Inventory display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
316.3 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
316.4 Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
316.5 Current Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
316.6 Ethernet Port Counters Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
316.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
316.6.2 Monitoring on disabled ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
316.6.3 Displaying modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
317 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

317.1 Possible Resource Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
317.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
317.2.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
317.2.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
317.3 HSB Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
317.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
317.4 Rx Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
317.5 Mux/Demux Protection (EPS) Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
317.5.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
318 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

318.1 General information, and Loopback timeout management . . . . . . . . . . . . . . . . . . . 646
318.2 Hardware implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
318.2.1 IDU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
318.2.2 ODU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
318.3 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
318.4 Loopback domain views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
318.5 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
318.6 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
319 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

319.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . . 657
319.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
319.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
319.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
319.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
319.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
319.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
319.5 Threshold tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
319.5.1 How to change a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
319.5.2 How to create a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
319.5.3 Threshold table association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

FRONT MATTER
3DB 16142 JAAA Ed.01 17 / 866
SECTION 4: SW INSTALLATION IN THE PC, AND COMMISSIONING . . . . . . 665
41 PREPARATION OF THE CRAFT TERMINAL BASED ON THE SWP TCO SUITE AND THE

SWP 9400AWY V2.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

41.1 PC requirements to run and install the SWP TCO SUITE . . . . . . . . . . . . . . . . . . . . . . . 668
41.2 Craft Terminal preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
41.3 Operation sequence for the JRE installation, and to perform the Local copy
of the TCO Suite and of the WebEML (Jusm/CT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
41.4 LLMAN installation and configuration, and use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
41.4.1 LLMAN installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
41.4.2 How to start and use the LLMAN application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
41.4.3 Full information regarding the use of the LLMAN application . . . . . . . . . . . . . . . . . . . 672
41.5 Local Copy of the SWP 9400AWY V2.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
42 LINEUP AND COMMISSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

42.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
42.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
42.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage . . . . . . . 677
42.1.3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
42.1.4 Summary of the lineup, commissioning, and acceptance phases . . . . . . . . . . . . . . 679
42.1.5 General information about test bench drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.2 Phase 1: Commissioning of STATION A (NE turn up and data definition) . . . . . . . . 681
42.2.1 Preliminary operations before IDU power on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
42.2.2 Power on the IDU unit(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
42.2.3 Craft Terminal switch on, and PC IP setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
42.2.4 Check the SWP running in the NEs Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
42.2.5 Define the NE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
42.2.6 New IP setting of the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
42.3 Phase 1: Commissioning of STATION B (NE turn up and data definition) . . . . . . . . 686
42.4 Note on NE login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
42.5 Phase 1: Fine antenna alignment, and preliminary checks (stations A & B) . . . . . . 687
42.5.1 Wait for the possible ODU SW upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
42.5.2 Fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
42.5.3 Preliminary checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
42.6 End of commissioning phase 1 in STATION A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
42.7 Phase 2: Commissioning of station A (acceptance test) . . . . . . . . . . . . . . . . . . . . . . . 693
42.7.1 Start the NEinteractive Acceptance Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
42.7.2 Step 1: Indoor installation visual inspection check . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
42.7.3 Step 2: Outdoor installation visual inspection check, and Antenna data . . . . . . . . . . 695
42.7.4 Step 3: Channel protection switch (for 1+1 configurations only) . . . . . . . . . . . . . . . 695
42.7.5 Step 3: Loopback Tests on channel 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
42.7.6 Step 3: Point to point BER loop tests on E1 Tributaries on Channel 1 . . . . . . . . . . . . 703
42.7.7 Step 3: Point to point BER loop tests on Ethernet Ch. for Radio Channel 1
(optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
42.7.8 Step 3: Rx level (dBm) tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
42.7.9 Step 4: Housekeeping input alarms acquisition (optional) . . . . . . . . . . . . . . . . . . . . . . 710
42.7.10 Step 4: Housekeeping output alarms acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
42.7.11 Step 4: Hop Stability Test on Channel 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
42.7.12 Channel 0 functionality tests (1+1 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
42.7.13 Step 5: Equipment identification, and NE software release . . . . . . . . . . . . . . . . . . . . 716
42.7.14 Step 6: Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
42.7.15 Step 7: Summary readonly tab panels, and TRS save and print . . . . . . . . . . . . . . 717
42.8 Phase 2: Commissioning of station B (acceptance test) . . . . . . . . . . . . . . . . . . . . . . . 717

FRONT MATTER
18 / 866 3DB 16142 JAAA Ed.01
42.9 Phase 3: Final acceptance of the link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
42.10 Phase 4: Final operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
42.11 Annex A: fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719

42.12 Annex B: light service kit cable operative information . . . . . . . . . . . . . . . . . . . . . . . . 720
43 USE OF THE ACCEPTANCE TOOL TO WRITE THE TRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

43.1 Acceptance Tool scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
43.2 Acceptance Tool start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
43.3 Acceptance Tool in NEinteractive modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
43.3.1 Bench setup and startup of the NEinteractive Acceptance Tool . . . . . . . . . . . . . . 726
43.3.2 Main functions of the NEinteractive Acceptance Tool . . . . . . . . . . . . . . . . . . . . . . . . . 728
43.3.3 Create Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
43.3.4 Steps of the Acceptance Tools Create Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
43.4 Acceptance Tool in not NEinteractive modality (offline) . . . . . . . . . . . . . . . . . . . . . . . 736
SECTION 5: MAINTENANCE AND UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

51 MAINTENANCE POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
51.1 Classification of maintenance levels and operators . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
51.2 First Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
51.3 Second Level Maintenance Personnel skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
51.4 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
52 USE OF EOW FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

52.1 Setting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
52.2 Call Setup/End by Telephone handset connected to the IDU Main unit . . . . . . . . . 744
53 MAINTENANCE TOOLS AND SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

53.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
53.2 Instruments and accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
53.2.1 Software tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
53.2.2 Maintenance, Installation and Station Tool Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
53.3 Set of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
53.3.1 Types of Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
53.3.2 ODU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
53.3.3 IDU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
53.3.4 Number of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
53.3.5 General rules on spare parts management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
54 FIRST LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751

54.1 System state display by visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
54.1.1 LED test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
54.1.2 Alarm LEDs on the IDU MAIN unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
54.1.3 Alarm LEDs on the IDU EXTENSION unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
54.2 TCO Suite commonly used functions for system status display and checks . . . . . 753
54.2.1 Viewing the NE alarms by NEtO Supervision, and Alarm Monitor . . . . . . . . . . . . . . . 753
54.2.2 Viewing the NE status by WebEML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
55 SECOND LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

55.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
55.2 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
55.2.1 EMC norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
55.2.2 Safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
FRONT MATTER
3DB 16142 JAAA Ed.01 19 / 866
55.2.3 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
55.3 Routine (preventive) Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

55.3.1 Routine (preventive) Maintenance every year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

55.4 Consequences of unit extraction in the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
55.5 Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
55.6 Alarm acknowledgment and attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
55.6.1 Alarm acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
55.6.2 Alarm Attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
55.7 Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
55.8 Troubleshooting via Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
55.8.1 Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
55.8.2 Alarm Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
55.8.3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.8.4 Operators Controls of the protection switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.8.5 Tx mute function (local and remote) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.8.6 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.8.7 BER measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.8.8 Commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
55.9 Link troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
55.9.1 Main tools available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
55.9.2 Alarms and troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
55.10 Hints on the troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
55.10.1 Problems with the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
55.10.2 Analog measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
55.10.3 NMS 64 kbit/s V.11 and G.703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
55.10.4 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
55.10.5 Remote NE unreachable for deep fading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
55.10.6 Configuration change from 4 QAM to 16 QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
55.10.7 Correct use of Full Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
55.10.8 Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
55.10.9 Tx Mute functionality for interferences investigation . . . . . . . . . . . . . . . . . . . . . . . . . . 777
55.11 IDU unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
55.11.1 IDU MAIN unit replacement procedure (CH1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
55.11.2 IDU EXTENSION unit replacement procedure (CH0) . . . . . . . . . . . . . . . . . . . . . . . . . 783
55.12 ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
55.13 Faulty unit repair and Repair Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
55.13.1 Faulty unit sending back to repair center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
55.13.2 Repair Form filling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
56 SPARE FLASH CARD MANAGEMENT, AND REPLACEMENT PROCEDURE . . . . . . . . . . 793

56.1 Spare Flash Card management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
56.2 Flash Card replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
56.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
56.2.2 Execution of the Flash Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
57 SYSTEM HARDWARE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797

57.1 Installation of plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
57.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
57.1.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
57.2 Upgrade from 1+0 to 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
57.2.1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
57.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805

FRONT MATTER
20 / 866 3DB 16142 JAAA Ed.01
58 PROCEDURE TO CHANGE CAPACITY/MODULATION/FREQUENCY . . . . . . . . . . . . . . . . . 809
59 NE UPGRADE TO V2.1.3 FROM PREVIOUS VERSION V2.1.X . . . . . . . . . . . . . . . . . . . . . . . 811

59.1 Introduction and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812

59.2 How to check the SW versions present in the NEs flash card . . . . . . . . . . . . . . . . . . 813
59.3 How to perform the SWP download to the NE, and its activation . . . . . . . . . . . . . . . 815
59.3.1 Remotion of the 2 x Fast Ethernet plugin, if equipped (stations A and B) . . . . . . 815
59.3.2 CT startup, and check for the availability of the SWP to be downloaded . . . . . . . . 816
59.3.3 NE login and initial operations (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
59.3.4 SW download to the NE (station A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
59.3.5 Activation of the new Software Package on the NE (station A) . . . . . . . . . . . . . . . . . . 822
59.3.6 Additional operations for upgrade from V2.1.0 (station A) . . . . . . . . . . . . . . . . . . . . . . 824
59.3.7 Operations on station B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
59.3.8 Functional checks on the radio link (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . . 824
59.3.9 NE data backup (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
59.4 Notes about NE SW downgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
SECTION 6: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

61 APPENDIX A: GENERAL ON ETHERNET PORT CHARACTERISTICS AND
MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
61.1 Ethernet Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
61.2 MDI/MDIX crossover (AutoMDI/MDIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
61.3 Frame size, Rx checksum and FCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
61.4 Ethernet capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
61.5 Ethernet flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
61.6 Ethernet interface management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
61.7 Auto Link Shutdown (ALiS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
61.8 Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
61.9 VLAN characteristics and management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
62 APPENDIX B: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
62.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
62.2 Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
62.3 Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
62.4 Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
62.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . . 842
62.4.2 TD32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
62.5 PC laptop Dell Latitude setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
62.6 Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
62.7 Changing the ECTequipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
62.7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
62.7.2 Configuration at NE side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
62.7.3 Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
63 APPENDIX C: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS . . . 849

63.1 List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
63.2 List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
63.3 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
64 APPENDIX D: CUSTOMER DOCUMENTATION FEEDBACK . . . . . . . . . . . . . . . . . . . . . . . . . 863

FRONT MATTER
3DB 16142 JAAA Ed.01 21 / 866
a)
22 / 866
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
3DB 16142 JAAA Ed.01

USER MANUAL
FRONT MATTER
Part A: Hardware Installation Handbook
This Hardware Installation Handbook (from this page 23 to page 358 ) is the part A of the whole User
Manual.
In case of paper copy, for its use during equipment installation operations, this part can be extracted from
the whole handbook, but take into account that, inside it, there are information referenced to (i.e.
necessary) by part B (Technical Handbook).
N.B. Cross references to page numbers > 358 are references to the part B (Technical Handbook).
Such references are for scopes (descriptions and maintenance) that are out of the aim of this
Hardware Installation Handbook, so that they can be ignored during the installation phases.
N.B. This section contains also some descriptions concerning the NE management performed by the
SWP TCO Suite. For such parts, please read carefully the point v Notes on used TCO Suite
and associated User Manual on page 5

HARDWARE INSTALLATION
3DB 16142 JAAA Ed.01 23 / 866
SECTION 1: HARDWARE INSTALLATION
SECTION CONTENT PAGE
Installation procedures
Chapter 11 Installation and commissioning summary 25
Chapter 12 Safety, EMC, EMF, ESD norms and equipment labelling 35
Chapter 13 Rack installation and grounding 49
Chapter 14 Top Rack Unit (TRU) installation and cabling 59
Chapter 15 Indoor Unit installation and cabling 69
Chapter 16 Outdoor Unit installation 137
Chapter 17 IDUODU cable installation material and installation

189
procedure
Chapter 18 Network interconnections

This chapter gives the interconnection diagrams and the associated list of cables
for network interconnections regarding the NMS channel continuity, and the EOW 195
audio continuity, and describes the E1 interconnections with the 9500MPRE
Microwave Packet Radio MSS equipment
Installation material
N.B. Installation components for IDUODU cable are described in para.17.1
on page 189
Chapter 19 Unpacking and warehousing 239
Chapter 110 IDU installation components 243
Chapter 111 ODU installation components 249
Additional information for installation, commissioning, and maintenance
Chapter 112 Views of IDU units, connector pinout, and signal description 287
Chapter 113 Description of interconnection and signal cables 327

24 / 866 3DB 16142 JAAA Ed.01
11 INSTALLATION AND COMMISSIONING SUMMARY
This chapter deals with:
Subject On page
Objects of this procedure below
Main phases for 9400AWY hardware and software installation 26
Hardware installation rules and suggested phases 27
11.1 Objects of this procedure
Whenever, before starting installation and commissioning operations described in the following, you like
to have an overview of the system, please refer to:
chapter 21 from page 361 , for descriptions at hardware level
para.33.2 from page 424 , for descriptions at NE software management level
9400AWY RADIO LINK
STATION A STATION B
ETSI RADIO
ODU ODU
CH1 CH1
IDUODU IDUODU
ODU ODU
cable CH1 CH0 CH0 cable CH1
IDUODU IDUODU
ETSI PDH cable CH0 cable CH0 ETSI PDH
ETHERNET ETHERNET
SERVICE CH. SERVICE CH.
IDU SUPERVISION IDU
NETWORK
All procedures for the hardware and software installation, and those for the commissioning of the single
station and of the radio link, are contained in this manual. The procedures for:
the hardware installation, are contained in this Hardware Installation Handbook (from this page
25 to page 236 )
the software installation, and those for the commissioning of the single station and of the radio link,
are contained in the Technical Handbook (from page 359 )
of the whole User Manual. Next para.11.2 specifies where to find such information in this manual.

3DB 16142 JAAA Ed.01 25 / 866
11.2 Main phases for 9400AWY hardware and software installation

The summary procedure depicted below presumes that the NEs Flash Card (for both stations) is as

delivered from AlcatelLucent factory, i.e.:

with SWP version = V2.1.3
with default configuration data.
1) Perform the HW INSTALLATION
Install and cable:
the STATION A
and the STATION B
as described in para.11.3 from page 27
2) Prepare the CRAFT TERMINAL, as described in chapter 41 from page 667
3) Perform the EQUIPMENT POWERON AND COMMISSIONING and the RADIO LINK
COMMISSIONING
as described in chapter 42 from page 675
and reporting the test results in the document TRS, using the Acceptance Tool described in
chapter 43 on page 721
4) Set the SECURITY PARAMETERS
as described in chapter 313 from page 591
5) Perform the NE DATA BACKUP
as described in point [1] on page 427

26 / 866 3DB 16142 JAAA Ed.01
11.3 Hardware installation rules and suggested phases
11.3.1 Hardware installation rules

[1] Specific plant documentation

The 9400AWY equipment should be installed and cabled making reference to the specific plant
documentation. If such documentation is not available, you must be able to create plant installation
data by yourself. You can find some information to create plant installation data in:
Subject Reference
para.22.8 on page 398
Rules for power supply
Rules for Equipment emitting RF power para.12.3.7.1 on page 43
Rules for IDU configuration types and cabling para.15.3 from page 101
Rules for ODU and antenna configurations para.21.2.4 on pages 372 to 375
Rules for installation and cabling of IDU
para.15.2.1 on pages 71 to 74
components
Rules for IDUODU cable para.17.1.1 on page 189
[2] Warning: capacity extension

In the case of successive capacity extensions, pay attention to the following:
IDUODU (Coax Cable 50 ohm)
9400 AWY R.2.1 can be provided with ODUs able to support 32 x E1 capacity even with IDU
subequipped configurations supporting 16 x E1 maximum.
With coax cable, there are limitation in the maximum length; a more performing cable could be
necessary to cover specific cases (see para.17.1.1 on page 189 for details)
IDU installation in Rack
To migrate:
from 1+0 to 1+1 configurations
from configurations without protection boxes to configurations with protection boxes
the IDU requires more room (see Chapter 15 from page 133 for details)
For an easy successive extension, the required additional room needed should be left free.
[3] Installation Tools required
The 9400AWY system is supplied with three Tools Bags: Station Tools Bag, Maintenance Tools Bag,
and Installation Tools Bag. These bags are described in para.53.2.2 on page 746
[4] General installation rules
ATTENTION EMC NORMS
When carrying out the given operations observe the norms states in para.12.4 on page 46
Check that the equipment is operating with all the shields properly positioned (dummy covers,
ESD connector protections, etc.)
In order to reduce the risk of damage the electrostatic sensitive devices, is mandatory to use
the elasticized band (around the wrist) and the coiled cord joined connect with the ground rack
during the touching of the equipment.
All the measures must be done at the MDF/CDF points (MDF= Mini Distributor Frame, CDF=
Customer Distributor Frame).
The equipment may be installed only in RESTRICTED ACCESS LOCATIONS, and be
permanently connected to a PROTECTIVE EARTHING CONDUCTOR as described in this
section.
Equipotential bonding must be applied for all equipments in the location.

3DB 16142 JAAA Ed.01 27 / 866
11.3.2 Suggested phases for 9400AWY hardware installation

[1] Read safety, EMC, EMF, and ESD norms and cautions to avoid equipment damage

SAFETY RULES:

Read chapter 12 from page 35 , and point iii on page 4 , which describe the operations
and/or precautions to be observed to safeguard operating personnel during the working
phases, and to guarantee equipment safety. Read them with accuracy before to start
every action on the equipment.
Perform following steps for STATION A and STATION B, making reference to the specific plant
documentation:
[2] Check the installation material

Unpack the shipping crate(s) and check its/their content for the presence of all installation material
required for the configuration stated in the plant documentation. For details, if necessary, refer to
chapter 19 from page 239
[3] Check the IDUODU distance

Using the plant documentation, and/or making a survey, verify that the distance between IDU and
ODU Nconnectors (actual length of the cable path) comply with that specified in para.17.1.1 on
page 189 , according to the used cable
[4] Perform the rack installation and grounding
Item: rack
(example)
Rack Installation
Operations to do:
Rack grounding
Chapter 13 from page 49
Details in: N.B. the same chapter describes the kit for the installation on the
wall

28 / 866 3DB 16142 JAAA Ed.01
[5] Perform the installation and cabling of the TRU
Item: TRU
+
TRU installation
Operations to do: TRU grounding
Connection of the TRU to the plant power supply
Details in: Chapter 14 on pages 59 to 63
[6] Prepare the power supply cables for IDU unit(s)
Item: Power Supply cable(s) for IDU MAIN (and EXTENSION) units
Cable construction
Operations to do:
Cable connection to the TRU
Details in: Chapter 14 on pages 64 to 66

3DB 16142 JAAA Ed.01 29 / 866
[7] Perform the installation and cabling of Indoor Unit

Item: IDU shelves and cables

(example)
Insertion of the Flash Card in the IDU MAIN unit (rear side)
Installation of the IDU MAIN unit, and of the IDU EXTENSION unit
(if present in the configuration)
Optional grounding of the IDU MAIN unit, and of the IDU
EXTENSION unit (if present in the configuration)
Assembling and installation of the PROTECTION BOXES (if
present in the configuration)
Interconnection of IDU MAIN and EXTENSION units (only for 1+1
Operations to do: systems)
Connection of power supply cable to the IDU MAIN unit, and to the
IDU EXTENSION unit (if present in the configuration)
Preparation of cables for connection of IDU to Customer DDF (if
Installation of the DISTRIBUTOR SUBRACKS (if present in the
configuration)
Positioning and connection of signal cables (according to system
configuration)
Chapter 15 on pages 69 to 100
Details in:
Chapter 18 from page 195 (for network interconnections)
[8] Perform the installation and grounding of Outdoor Unit(s) and Antenna(s)
Read warnings on page 138 ,

then proceed according to the ODU configuration (5 cases):
ODU Antenna Frequency Procedure
full integrated all point a ) on page 31

1+0
not integrated all point b ) on page 31
full integrated all point c ) on page 32

1+1 HSB
one antenna not integrated all point d ) on page 33
1+0 or 1+1
external 78 GHz para.16.7 from page 175
full Indoor ODU

30 / 866 3DB 16142 JAAA Ed.01
a) 1+0 ODU full integrated antenna all frequencies
Item: 1+0 ODU full integrated antenna all frequencies
pole
mounting
full integrated antenna
ODU (1+0)
(example)
Check/Set the coupling between the TRANSCEIVER and

BRANCHING boxes (only for ODU with external diplexer)
Install the Antenna and Pole Mounting
Check or change the polarization on the Antenna nose
Take off the solar shield from the ODU transceiver
Operations to do:
Install the ODU on Antennas nose adapter
Ground the ODU system
Prepoint the antenna
Reinstall the solar shield onto the ODU transceiver
Affix the EMF stickers
Details in: Para.16.3 on pages 150 to 152
b) 1+0 ODU not integrated antenna all frequencies

Item: 1+0 ODU not integrated antenna all frequencies
antenna pole mounting

flextwist not integrated antenna
ODU (1+0)
ODU pole mounting

(example)

BRANCHING boxes (only for ODU with external diplexer)
Install the Nose Adapter on the Pole Mounting for not integrated
antenna
Install the Pole Mounting for not integrated antenna
Take off the solar shield from the ODU transceiver
Install the ODU
Operations to do: Install the external Antenna with its own Pole Mounting
Connect the antenna side (flange) of the Pole Mountings nose
adapter to the external antenna, by means of the Flextwist
waveguide
Reinstall the solar shield onto the ODU transceiver
Details in: Para.16.4 on pages 153 to 156

3DB 16142 JAAA Ed.01 31 / 866
c) 1+1 ODU full integrated antenna all frequencies

Item: 1+1 ODU full integrated antenna all frequencies

1338 GHz 78 GHz
full integrated antenna full integrated antenna
ODU
CH0
ODU
CH1
ODU ODU
CH0 pole pole
RF CH1 RF coupler
mounting mounting
coupler

BRANCHING boxes (only for ODUs with external diplexer)
Install the Antenna and Pole Mounting
Check or change the polarization of the RF coupler
Install the RF coupler on antennas nose adapter
Operations to do: For each ODU transceiver, take off the solar shield
Install the ODU transceivers on the RF coupler
Reinstall the solar shield onto each ODU transceiver
For:
all frequencies: para.16.5.1 on page 157 (typical installation
Details in: layout)
1338 GHz: para.16.5.2 on pages 158 to 162 (procedure)

32 / 866 3DB 16142 JAAA Ed.01
d) 1+1 ODU not integrated antenna all frequencies
Item: 1+1 ODU not integrated antenna all frequencies

antenna pole mounting

ODU (1+1) not integrated
antenna
flextwist waveguide
ODU pole mounting

BRANCHING boxes (only for ODUs with external diplexer)
Install the Nose Adapter on the not integrated antenna Pole
Mounting for ODU
Install the not integrated antenna Pole Mounting for ODU
Install the RF coupler on the nose adapter
For each ODU transceiver, take off the solar shield
Install the ODU transceivers on the RF coupler
Operations to do:
Install the external Antenna with its own Pole Mounting
Connect the antenna side (flange) of the ODU Pole Mountings
nose adapter to the external antenna, by means of the Flextwist
waveguide
Reinstall the solar shield onto each ODU transceiver
For:
all frequencies: para.16.6.1 on page 166 (typical installation
Details in: layout)

3DB 16142 JAAA Ed.01 33 / 866
[9] Perform the installation and cabling of IDUODU cable(s)

Item: IDUODU cable(s)

ODU
CH1
IDUODU
cable CH1 ODU
CH0
IDUODU
cable CH0
IDU
Install the cable in the cable tray

Install the cable in the feed thru plate
Mount the N connectors on the cable
Operations to do: Ground the cable
Label and connect the cable to the ODU
Waterproof the connector on ODU
Label and connect the cable to the IDU
Details in: Chapter 17 from page 189
End of hardware installation procedure

34 / 866 3DB 16142 JAAA Ed.01
12 SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT
LABELLING
This chapter describes the equipment labelling and the norms mandatory or suggested [see also point d )
on page 3 ] 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 point iv on page 5
Subject On page
Summary of labels for safety and warning below
Compliance with International Standards 36
Safety rules 36
Electromagnetic Compatibility (EMC norms) 46
Equipment protection against electrostatic discharges (ESD norms) 47
Suggestions, notes and cautions 47
9400AWY equipmentspecific identification labels 47
12.1 Summary of labels for safety and warning
LABEL ON EQUIPMENT MEANING

Dangerous Electrical Voltages
see para.12.3.5 on page 42
Equipment connection to earth

Equipment emitting RF power (EMF norms)

Risk of explosion
Moving mechanical parts

Heatradiating mechanical parts

Device sensitive to electrostatic discharges

see para.12.5 on page 47
2002/96/EC WEEE (Waste Electrical and Electronic

Equipment) Logo

3DB 16142 JAAA Ed.01 35 / 866
12.2 Compliance with International Standards

Refer to chapter 22 from page 389

12.3 Safety rules
Subject On page
General safety rules 37
Specific safety rules in this Manual 37
List of safety requirements for workers 38
Labels Indicating Danger, Forbiddance, Command 41
Dangerous Electrical Voltages 42
Equipment connection to earth 42
EMF safety instructions (microwave radiations)
Equipment emitting RF power (Reminder from site preparation

43
procedure)
EMF sticker positioning
Compliance boundaries 44
Risks of Explosions: labelling and safety instructions 45
Moving Mechanical Parts: labelling and safety instructions 45
Heatradiating Mechanical Parts: labelling and safety instructions 45

36 / 866 3DB 16142 JAAA Ed.01
12.3.1 General safety rules

Before carrying out any installation, turnon, tests & operation and maintenance operations
carefully read the related parts of this manual or other handbooks.

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).
12.3.2 Specific safety rules in this Manual
The safety rules described in this manual are

SAFETY RULES
distinguished by the following symbol and statement:
They are specified in the following parts:

Part A (Hardware Installation Handbook):
chapter 12 on pages 35 to 45 (this chapter)
chapter 13 on pages 50 , 55 , 57
chapter 14 on pages 60 , 62 , 63 , 66
chapter 15 on pages 75 , 82
Part B (Technical Handbook):
chapter 55 on pages 756 , 757 , 781 , 785 , 787

3DB 16142 JAAA Ed.01 37 / 866
12.3.3 List of safety requirements for workers

Every person on site must respect the safety requirements mentioned below:

Delegation of Power
Safety of the Individual
Safety of the Perimeter of Work
Installation Site
Every technician must regularly check his safety equipment and the deadline of use.
[1] Delegation of Power
Aptitude Required to Work on Site
A medical certificate of aptitude to work at height.
A certificate of aptitude to work on electrical equipment and to work

at height.
In certain cases, a climbing certificate.
any time,
At any time,you
youmust
mustbebe
ableable
to showyour
to show yourpersonal
personal certificates.
certificates.

38 / 866 3DB 16142 JAAA Ed.01
[2] Safety of the Individual
2 operators at least for any work:
at height
on electrical equipment
near live stripped parts
In these three cases, a medical certificate of aptitude

for work is required.
Requirements to Work at Height
A safety harness
2m shockabsorbing lanyards
A tether adjustment
The material to prevent falls when climbing

the pylon
Requirements to Work with Cords
A rope grab
Two semistatic cords
Requirements if a Technician works on the Pylon
A helmet
Safety shoes

3DB 16142 JAAA Ed.01 39 / 866
[3] Safety of the Perimeter of Work

Requirements

Delimit the perimeter of danger area (lifting area) with road stripes.
Cordon off the danger area during the lifting operation.
As soon as a technician works on the pylon, everyone on the

ground has to wear a helmet and safety shoes.
Post up the safety agreement of the site in the technical room.
Caution
Never stay or circulate under the load.
Do not stay below people working at height (risk of fall of objects).
[4] Installation Site
Keep the installation site clean and tidy for the

duration of the work.

40 / 866 3DB 16142 JAAA Ed.01
12.3.4 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 STATEMENT.

INDICATES WARNING OR DANGER (YELLOW
BACKGROUND + BLACK SYMBOL AND RIM)
CONTAINS A STATEMENT PROVIDING INFORMATION OR

INSTRUCTION.
(YELLOW BACKGROUND + BLACK STATEMENT AND RIM)
The labels have been affixed to indicate a dangerous condition. They may contain any standardknown
symbol or any statement necessary to safeguard users and service personnel against the most common
ones, specifically:
labels that are affixed to 9400AWY hardware components:

dangerous electrical voltages
equipment connection to earth
microwave radiations
labels affixed to other equipments that can be found in the same 9400AWY premises:
risk of explosion
harmful optical signals
moving mechanical parts
heatradiating Mechanical Parts
Pay attention to the information stated in the following, and proceed as instructed
The symbols presented in para.12.3.5 through 12.3.10 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.

3DB 16142 JAAA Ed.01 41 / 866
12.3.5 Dangerous Electrical Voltages

[1] Electrical safety: Labelling

This warning label is affixed next to
dangerous voltages (>42.4 Vp; >60 Vdc):
WARNING !
If it is a Class 1 equipment connected to
mains, then the label associated to it states Ground protect the equipment before
that the equipment has to be grounded connecting it to the mains
before connecting it to the power supply Make sure that power has been cut off before
voltage, e.g.: disconnecting ground protection.
[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.
12.3.6 Equipment connection to earth
Terminals for equipment connection to earth , to be

done according to international safety standards, terminal
are pointed out by the suitable symbol: symbol
Information for earth connection terminals is specified in:
Chapter 13 on pages 55 , 57 , 58
Chapter 14 on pages 62
Chapter 15 on page 80
Chapter 16 on pages 150 , 153 , 157 , 166 , 181

42 / 866 3DB 16142 JAAA Ed.01
12.3.7 EMF safety instructions (microwave radiations)
12.3.7.1 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.
12.3.7.2 EMF sticker positioning
Place the relevant stickers:
On the site when applicable (when people can cross the compliance
boundaries and/or the transmission area of the antenna, i.e. roof top
installation)
Warning label Do not stand on the antenna axis
On the mast (front side)

EMF emission warning sign (Yellow and black) to be placed at bottom of
antenna, visible by someone moving in front of the antenna (roof top
EMF emission
installation)
warning sign
On the antenna (rear side)

EMF emission warning sign, placed on the antenna.

3DB 16142 JAAA Ed.01 43 / 866
12.3.7.3 Compliance boundaries

SAFETY RULES
DANGER: Possibility of personal injury for RF power emission.

While working on antenna pole where other antennas are present, do not stand on the
antenna axis, and be aware of the compliance boundaries defined for the systems they
are connected to.
If 9400AWYs ODU is powered on from IDU, do not stand on the antenna axis and be aware of the
specific compliance boundaries defined in Tab. 1. below, valid for following 9400AWY system
configurations:
a) 1+0 with 1ft. integrated antenna

b) 1+1 HSB with coupler and 1ft. integrated antenna
c) configuration with separated 1ft. antenna
N.B. these are the worst cases (lower frequencies, 4QAM, and smallest antenna). Respecting these
boundaries also for other better cases (higher frequencies, 16QAM, and largest antenna)
ensures your safety.
Tab. 1. Compliance boundaries for 9400AWY 1ft (30 cm) antenna:
System Modulation Worst Configuration A (m) B (m)
1+0 with integrated antenna

9413 AWY 4 QAM 0,4 2,63
(13 GHz 1ft. SP integrated antenna)

9415 AWY 4 QAM 0,4 0,55

9418 AWY 4 QAM 0,4 0,71

44 / 866 3DB 16142 JAAA Ed.01
12.3.8 Risks of Explosions: labelling and safety instructions
This risk is usually present when batteries are

used, and it is signalled by the following label:
The openings made in the unit containing the battery must not be covered up to let dangerous gases
flow out in case of heating or burning.
Therefore, slits or apertures are made to let air

circulate freely and allow dangerous gases to
down flow (batteryemitted hydrogen). A
417IEC5641 Norm. compliant label is affixed
next to it indicating that the openings must not be
covered up.
12.3.9 Moving Mechanical Parts: labelling and safety instructions
The following warning label is affixed next to fans

or other moving mechanical parts:
Before carrying out any maintenance operation, verify that all the moving mechanical parts have
been stopped.
12.3.10 Heatradiating Mechanical Parts: labelling and safety instructions
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:
Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part of
your body.

3DB 16142 JAAA Ed.01 45 / 866
12.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 (part A of this User Manual, from page 23 )

Commissioning: Chapter 42 on page 675
Maintenance: Section 5: Maintenance and Upgrade on page 737
The norms set down to guarantee EMC compatibility, are distinguished inside this handbook
by the symbol and term:
ATTENTION EMC NORMS
12.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.
12.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
12.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.

46 / 866 3DB 16142 JAAA Ed.01
12.5 Equipment protection against electrostatic discharges (ESD norms)
Most electronic devices are sensitive to

electrostatic discharges, to this concern the

following warning labels have been affixed:
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.
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 4):
an elasticized band worn around the wrist
a coiled cord connected to the elasticized band and to the stud on the subrack.
12.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...
(caution to avoid equipment damage)

statement....
12.7 9400AWY equipmentspecific identification labels
Following paragraphs indicates the positions and the information contained on the 9400AWY
equipmentspecific identification labels:
Labels affixed on the IDU: para.15.1 on page 70
Labels affixed on the Flash Card: Fig. 179. on page 406
Labels affixed on the ODU: para.16.2.3 on page 148

3DB 16142 JAAA Ed.01 47 / 866
48 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
13 RACK INSTALLATION AND GROUNDING
The IDU components making up one 9400AWY NE can be installed:
in a ETSI (WTD) rack (21) and North American standard rack (19)
in a Laborack (19)
with some equipment limitations, on the wall, through a specific wall mounting kit.
This chapter deals with the procedures for the installation and grounding of the above stated racks and
mounting kit:
Subject On page
Safety rules for rack positioning and fastening 50
ETSI Rack installation and grounding

50
For ETSI (WTD) rack (21), and North American standard rack (19)
Laborack installation and grounding

56
For 19 Laborack
Wall mounting kit description 58
N.B.
missing P/Ns of items described in this chapter are given in point a ) of Tab. 11. on page 243
the procedures for fixing IDU units to the rack are explained in chapter 15 from page 69

3DB 16142 JAAA Ed.01 49 / 866
13.1 Safety rules for rack positioning and fastening

SAFETY RULES
DANGER: Possibility of personal injury. Brace top of rack/subrack during

movement to prevent tipping and to avoid strains that can twist or damage
backplane.
DANGER: Possibility of personal injury. Rack equipment weight exceeds 50 Kg.

Use materialhandling equipment to lift equipment.
13.2 ETSI Rack installation and grounding
Installation has been subdivided into the following phases:
Rack Positioning and Fastening
Fixing the rack to floor using expansion bolts or Fixing to floating floor
Rack grounding.
13.2.1 ETSI Rack positioning and fastening
Proceed as follows:
Refer to the plant documentation to see rack row assignment
Fasten the rack to the station structure according to one of the following procedures:
fixing the rack to floor, proceed with para.13.2.2 below
fixing the rack to floating floor, proceed with para.13.2.3 on page 53.
13.2.2 ETSI Rack fixing the rack using expansion bolts
See Fig. 2. on page 51 and Fig. 3. on page 52
1) Mount the rack in a vertical position in the desired place
2) Mark the baseplate with six holes (1) to be drilled on the floor
3) Temporarily remove the rack and drill the holes at the points drawn on the floor (see Fig. 3.
on page 52 )
4) Place the inserts into the holes
5) Secure the expander bolts to the floor through the baseplate holes.

50 / 866 3DB 16142 JAAA Ed.01
20
EXPANSION ANCHOR M8xM40
NOTES:
All dimensions are in mm
* Fixable max thickness
12** ** Diameter drill
Fig. 2. Fixing the rack using expansion bolts

3DB 16142 JAAA Ed.01 51 / 866
142 mm
30 mm
30 mm
98 mm
149 mm 300 mm 149 mm
DRILL HOLES
Fig. 3. Drill Holes for Anchoring to the Floor (single rack)

52 / 866 3DB 16142 JAAA Ed.01
13.2.3 ETSI Rack fixing to floating floor
The drilling mask is the same used for concrete floor fastening (Fig. 3. on page 52). In this case must be
create a hole for the cables coming from the bottom according to Fig. 4. below. The rack fastening is to
be realized on the concrete floor below using a suitable stud as shown in Fig. 5. on page 54.
Using the row layout drawing, mark out the cable entry areas in the floor tiles and cut out with a jigsaw.
Remember that the beginning of the row will be agreed with the customer.
N.B. Unused or incompletely used cable entry areas should be blocked off with foam rubber.
598
149 300 149
61.25
96.25
CABLE ENTRY 35
AREA
30
130
30 297.25
35
80
106 81
FIBER DUCTS
26
Fig. 4. Floor tile drilling template

3DB 16142 JAAA Ed.01 53 / 866
HEX NUT
LOCKWASHER
FLAT WASHER
BOTTOM
FRAME
STUD
Rack base
FLAT WASHER
LOCKWASHER
HEX NUT
Computer Floor
STUD
HEX NUT
LOCKWASHER Concrete Floor
FLAT WASHER
EXPANSION PLUG
Fig. 5. Example of securing rack assembly to computer floor

54 / 866 3DB 16142 JAAA Ed.01
13.2.4 ETSI Rack grounding
The rack must be grounded by means of a connection to the protection ground terminal of the site electrical
plant. protection ground terminal of the site electrical plant.

SAFETY RULES
The rack must be connected to the protection ground before performing any
other electrical connection.
Fig. 6. shows the connection of the ground on the topside of the ETSI rack.
The rack is grounded to the station through a 16 to 25 mm2 (1 to 2 AWG) section cable (1) terminated
onto the cable terminal lug (2).
Insert and crimp the cable
2 1
Fig. 6. ETSI Rack Ground connections

3DB 16142 JAAA Ed.01 55 / 866
13.3 Laborack installation and grounding

13.3.1 Laborack installation
Fig. 7. Laborack
The Laborack must be fixed to the floor by means the four (4) screws.
(For more information see the manufacturer instructions)
When you have correctly positioned the fixing brackets on the 19 unit, the front panel will hold the
equipment by four screws fitted into the Laborack cage nuts.

56 / 866 3DB 16142 JAAA Ed.01
13.3.2 Laborack grounding
The Laborack must be grounded by means of a connection to the protection ground terminal of the site
electrical plant.
SAFETY RULES
The Laborack must be connected to the protection ground before performing
any other electrical connection.
Fig. 8. shows the connection of the ground on the bottom side of the Laborack.
Fig. 8. Laborack Ground connections

3DB 16142 JAAA Ed.01 57 / 866
13.4 Wall mounting kit description

The mechanical support (kit ref. 3CC09614AAAA) can be used for wall installation and it can support a

maximum of three units.

The kit includes:
Two brackets
Four fixing for the brackets
M6x50 socket cap screws
Onduflex washers
Expansion bolt
The mechanical support can contain a maximum of ONE unit in case of system 1+0 and TWO units in
case of system 1+1, both equipped with mini distributor.
The possible installations are the followings:
1+0 and 1+1 Installation wall with and without mini distributor
1+0 and 1+1 typical wall installation (horizontal and vertical positioning)
The wooden or masonry wall that is selected for the installation should be in a suitable portion of the room.
Preferably it should be near to a safety power outlet, and it should ensure safeguard against accidental
tampering. It is possible to install the apparatus in a horizontal or vertical position
Detail A
Detail A
Grounding
point
The mechanical support must be grounded using the Grounding Kit 3CC13423AAAA
Fig. 9. Fixing the mechanical support to the wall and grounding

58 / 866 3DB 16142 JAAA Ed.01
14 TOP RACK UNIT (TRU) INSTALLATION AND CABLING
SUBJECT ON PAGE
General installation rules 60
Introduction to Top Rack Unit 61
Top Rack Unit components 61
Top Rack Unit installation and cabling steps 62
Power Supply installation kit 64
Types and section of cables for grounding and power supply 67
N.B. missing P/Ns of items described in this chapter are given in Tab. 11. :
point b ) on page 243 (TRU components)
point i ) on page 246 (power supply and grounding cables)

3DB 16142 JAAA Ed.01 59 / 866
14.1 General installation rules

ATTENTION EMC NORMS

SAFETY RULES
If not yet done, read chapter 12 from page 35 , and point iii on page 4 , which describe the
operations and/or precautions to be observed to safeguard operating personnel during the working
phases, and to guarantee equipment safety.
Read them with accuracy before to start every action on the equipment.
After performing the TRU mechanical installation, perform the TRU ground connection.
Before performing any electrical connection operation, make sure that the power supply circuit
breaker at the customer distributor panel is turned OFF.
Before performing any electrical connection operation from TRU to any subrack, make sure that the
correspondent TRU power supply circuit breaker is turned OFF.
In case of expansions, to carry out any new electrical connection from the TRU to a new shelf:
position the TRUtoshelf power supply cables and connect them only to the TRUs
correspondent circuit breaker, without connecting them to the new shelf
turn ON the new circuit breakers and verify the correct polarity and quality connection on it, on
the connector at new shelf side
turn OFF such new circuit breakers
connect the power supply cables to the new NEs connectors, and screw them
power ON the new circuit breakers and check for few minutes if is there any anomalies
condition.

60 / 866 3DB 16142 JAAA Ed.01
14.2 Introduction to Top Rack Unit
The Top Rack Unit (TRU) is positioned on the top of the Rack and it is used to provide the Power Supply
to the equipment.
Rear view (with sliding cover)

Front view (with cover)
Fig. 10. Top Rack Unit views
14.3 Top Rack Unit components
Component description Quantity Particular view
Terminal Block 16mm2 2
Thermal Magnetic Circuit

6
Breaker Unipolar
Bus Bar Supply to 12 Fuse Carrier 1
Screws M6x16 with plastic Washer 4
Natched Clamp Nuts M6 4
Rail + Front 19 1

3DB 16142 JAAA Ed.01 61 / 866
14.4 Top Rack Unit installation and cabling steps

[1] TRU installation

The TRU is fixed to the 19 rack by means of two screws:

Fig. 11. Top Rack Unit installation in the rack
N.B. In case of installation in a 21 rack, use the specific 19 / 21 adapter kit P/N
3CC50042AAAA, which contains two adapters as that shown below, besides mounting
materials:
(3CC5034AAAA)
[2] TRU grounding

As shown in Fig. 12. , the TRU must be grounded by means of a connection to the rack, which, in
turn, is connected to the protection ground terminal of the site electrical plant.
SAFETY RULES
The TRU must be connected to the protection ground before performing any
other electrical connection.
Fig. 12. Top Rack Unit grounding to the rack

62 / 866 3DB 16142 JAAA Ed.01
[3] Connection of the TRU to the plant power supply
SAFETY RULES
Before performing this electrical connection operation, make sure that the
power supply circuit breaker at the customer distributor panel is turned OFF.
N.B. For the section of cables to use, refer to para.14.6 on page 67
POSITIVE (brown) NEGATIVE (blue) ELECTRICAL GROUND

(yellowgreen)
from plant power supply
Fig. 13. Top Rack Unit connection to the plant power supply

3DB 16142 JAAA Ed.01 63 / 866
14.5 Power Supply installation kit

This paragraph describes the Power Supply Kit and the assembly of the connector with / without the EMI

suppression ferrite.

The Power Supply Kit allows to prepare the power supply cables necessary for each IDU MAIN unit, and
for each IDU EXTENSION unit, powered through the TRU.
14.5.1 Kit components
Power Supply Kit code: 3CC52136AAAA
In an antistatic bag there is the following material:
1AB006030115
1AD016580003
1AB040970046
EMI Suppression FERRITE with plastic case , necessary only with full range IDU units (2460 Vdc)
1AB093970004

64 / 866 3DB 16142 JAAA Ed.01
14.5.2 Assembly procedure
For the section of cables to use, refer to para.14.6 on page 67

The cable length must be defined according to the position of the IDU MAIN / EXTENSION unit in the rack.
blue

yellowgreen
connect the cables wires to the connector
brown
+
position the cable into the shell
close the cover of the shell and fix with the screw
Following operations are necessary only with full range IDU units (2460 Vdc)
position the ferrite with plastic case near the shell and
fix the two wrappers
close the ferrite with plastic case

3DB 16142 JAAA Ed.01 65 / 866
14.5.3 Steps for the connection to the TRU of the power supply cables

The cables are used in step [8] of the IDU installation and cabling procedure, on page 82

SAFETY RULES

Before performing this electrical connection operation, make sure that the
power supply circuit breaker at the customer distributor panel is turned OFF.
[1] Cable positioning inside the TRU trail (rear side)
[2] Cable connection to the TRU (front side)
NEGATIVE
POSITIVE Blue wire ELECTRICAL GROUND
Brown wire Yellowgreen wire

66 / 866 3DB 16142 JAAA Ed.01
14.6 Types and section of cables for grounding and power supply
System
AWY 1+0 AWY 1+1
Cable type & section Cable type & section

Cable usage (for cable length (for cable length
up to 20 m) up to 20 m)
Grounding cables
Cable for grounding the RACK to the protection

ground terminal of the site electrical plant.
See: 1 x 16 mm2 1 x 16 mm2
Fig. 6. on page 55
Fig. 8. on page 57
Cable for grounding the TRU to the RACK.

1 x 16 mm2 1 x 16 mm2
See Fig. 12. on page 62
Cable for grounding the IDU MAIN / EXTENSION unit

to the RACK (if necessary). 1 x 3 mm2 1 x 3 mm2
Power supply cables
Cable for TRU power supply from plant power supply.

2 x ( 1 x 16 mm2 ) 2 x ( 1 x 16 mm2 )
Cable for IDU MAIN / EXTENSION units power supply

from TRU.
See para.14.5.2 on page 65
Cable for Power Supply 4860 Vdc 3 x 1.5 mm2 3 x 1.5 mm2
Cable for Power Supply 2460 Vdc 3 x 2.5 mm2 3 x 2.5 mm2

3DB 16142 JAAA Ed.01 67 / 866
68 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
15 INDOOR UNIT INSTALLATION AND CABLING
Subject On page
Labels affixed on the IDU Main and Extension units 70
Installation and cabling of IDU components 71
Composition, installation and cabling rules for IDU components

This paragraph is mainly useful in case you must perform the IDU
71
installation and cabling without having a reference plantdependent
documentation
Suggested IDU installation and cabling procedure

This paragraph describes in detail how to install and cable the IDU 75
components.
IDU configuration types and cabling

This paragraph describes the hardware components (shelves, cables, and
101
how to connect them) of one single 9400AWY NE according to the most
common system configurations envisaged.
IDU horizontal and vertical installation

This paragraph describes the rules for the horizontal or vertical installation of 133
one or more 9400AWY NEs in one rack.

3DB 16142 JAAA Ed.01 69 / 866
15.1 Labels affixed on the IDU Main and Extension units

This label is affixed on the back side of the IDU MAIN and EXTENSION unit:

example IDU MAIN unit
A C
B
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
Equipment) Logo (see para.22.10.3 on page 399)
Electrostatic Device Logo

Logistical item 3DB 05620 AAXX (example) Logistical item for Customer
A Logistical item for Customer, bar code 128
P/N ICS 3DB 05620 AAAA 01 (example) Factory Technical Code + ICS
B Factory Technical Code + ICS, bar code 128
SERIAL N CW052402145 (example)
Factory serial number
SERIAL N CW052402141 (example)
C Factory serial number bar code 128
24 V 20%, 2.2 A max (example) Power Supply Version 24 V
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. 14. Label affixed on the IDU Main and Extension units

70 / 866 3DB 16142 JAAA Ed.01
15.2 Installation and cabling of IDU components
15.2.1 Composition, installation and cabling rules for IDU components

[1] IDU composition according to NE configuration

The IDU components making up one 9400AWY NE are:
one IDU MAIN unit, always present. Before its hardware installation, the Flash Card must be
inserted inside it, and the associated Software Label must be sticked on the IDU MAIN unit front
panel
one IDU EXTENSION unit, present in 1+1 configurations only
one E1 PROTECTION BOX and/or one SERVICE PROTECTION BOX, present or not,
depending on specific configurations. These boxes are installed in the rack by means of a
specific mechanical support
one or two E1 DISTRIBUTOR SHELVES, present or not, depending on specific configurations
signal interconnection cables, connecting IDU components to each other, and to the Customer
DDF and external lines
power supply cables: one for the IDU MAIN unit, and another one for the IDU EXTENSION unit,
if present in the configuration.
The IDU composition, according to NE configuration, is described in para.15.3 from page 101
[2] Terminology and synonyms
Synonym that can be found

Term used in this document
in other related documents
IDU Main (unit) Main (unit)
IDU Extension (unit) Spare (unit)
E1 Protection Box or Service Protection Box Patch Panel
E1 Protection Box Tributary Panel
Service Protection Box Auxiliary Service Panel
[3] IDU installation options

a) Housing rack
The IDU components stated above can be installed:
in an ETSI (WTD) rack (21)
in a Laborack (19)
in a North American standard rack (19)
with some equipment limitations, on the wall, through a specific wall mounting kit.
For each type of installation, special mechanical supporting fixtures are available.
b) Horizontal or vertical installation, and relative position
The IDU components stated above can be installed horizontally or vertically in the rack, as
described in para.15.4 from page 133 . This same paragraph specifies the relative position of
slots to be employed for the IDU MAIN unit, the IDU EXTENSION unit, the PROTECTION
BOXES, and the E1 DISTRIBUTOR SHELVES (DDF).

3DB 16142 JAAA Ed.01 71 / 866
[4] IDU shelf components installation positions and installation sequence

With reference to the IDU shelf components, defined by each one of the various configurations

described in para.15.3 from page 101 , following Fig. 15. (for 1+0 systems) and Fig. 16. (for 1+1

systems) :
depict the exact (mandatory) relative position of shelves
by numbers in brackets [ (1) , (2) , (3) , (4) ] , specify the exact (mandatory) order for the
installation of the IDU shelf components
N.B. for mounting the protection box(es), two types of support kits are available, according to
the configuration, as depicted in Fig. 21. on page 81
Detailed instructions for the shelf installation are given in para.15.2.2 from page 75
N.B. For ease of operation, in case the DISTRIBUTOR SUBRACK(s) is / are present in the
configuration, it is preferable to make its / their final installation after having positioned the
signal cables.
1+0 WITH NEITHER PROTECTION BOX(ES) NOR DISTRIBUTOR SUBRACK(S)
(1) MAIN
1+0 WITHOUT SERVICE PROTECTION BOX & WITH DISTRIBUTOR SUBRACK(S)
Distributor Subrack (1U example) (2)
(1) MAIN
1+0 WITH SERVICE PROTECTION BOX & WITHOUT DISTRIBUTOR SUBRACK(S)
(2) Service Protection Box on support
(1) MAIN
1+0 WITH SERVICE PROTECTION BOX AND DISTRIBUTOR SUBRACK(S)
(1) MAIN
Fig. 15. IDU shelf components installation positions and installation sequence (1+0 systems)

72 / 866 3DB 16142 JAAA Ed.01
1+1 WITH NEITHER PROTECTION BOX(ES) NOR DISTRIBUTOR SUBRACK(S)
(2) MAIN
(1) EXTENSION
1+1 WITHOUT PROTECTION BOX(ES) & WITH DISTRIBUTOR SUBRACK(S)
(2) MAIN
(1) EXTENSION
1+1 WITH SERVICE PROTECTION BOX ONLY, AND WITHOUT DISTRIBUTOR SUBRACK(S)
(2) MAIN
(1) EXTENSION
1+1 WITH SERVICE PROTECTION BOX ONLY, AND WITH DISTRIBUTOR SUBRACK(S)
(2) MAIN
(1) EXTENSION
1+1 WITH E1 & SERVICE PROTECTION BOXES, AND WITHOUT DISTRIBUTOR SUBRACK(S)
(3) Protection Boxes on support
(2) MAIN
(1) EXTENSION
1+1 WITH E1 & SERVICE PROTECTION BOXES, AND WITH DISTRIBUTOR SUBRACK(S)
(3) Protection Boxes on support
(2) MAIN
(1) EXTENSION
Fig. 16. IDU shelf components installation positions and installation sequence (1+1 systems)

3DB 16142 JAAA Ed.01 73 / 866
[5] Cable labelling
For installation, service and maintenance purposes, the following cables must be uniquely identified:

by two labels (with the same identification data) placed at its two ends:
cables for IDU unit grounding to the rack (if done, see step [5] on page 80 )
cables for IDU unit power supply (see step [8] on page 82 )
by various labels (with different identification data):

cables connecting IDU to Customer DDF (see step [9] on page 83 )

74 / 866 3DB 16142 JAAA Ed.01
15.2.2 Suggested IDU installation and cabling procedure
Step summary:
step from page
SAFETY RULES:
If not yet done, read chapter 12 from page 35 , and point iii on
page 4 , which describe the operations and/or precautions to be
observed to safeguard operating personnel during the working
phases, and to guarantee equipment safety. Read them with
accuracy before to start every action on the equipment.
In case you must perform the IDU installation and cabling without
having a reference plantdependent documentation, read
71
Composition, installation and cabling rules for IDU
components, and carefully observe given statements
Checks before starting installation 76
Tightening torque 76
Insertion of the Flash Card in the IDU MAIN unit 77
Installation of the IDU MAIN unit, and of the IDU EXTENSION unit (if present
79
in the configuration)
Optional grounding of the IDU MAIN unit, and of the IDU EXTENSION unit (if
80
Assembling and installation of the PROTECTION BOXES (if present in the

81
configuration)
Interconnection of IDU MAIN and EXTENSION units (only for 1+1 systems) 82
Connection of power supply cable to the IDU MAIN unit, and to the IDU
82
EXTENSION unit (if present in the configuration)
Preparation of cables for connection of IDU to Customer DDF (if present in the
83
configuration)
Installation of the DISTRIBUTOR SUBRACKS (if present in the configuration) 95
Positioning and connection of signal cables (according to system

96
configuration)
N.B. refer to the plant documentation (or any other Customer site plan), for the connection of the
Ethernet cables:
from IDU MAIN units RJ45 OS connector [Ref. (3) in Fig. 143. on page 289 ] to the OS,
(if this connection is envisaged)
from IDU MAIN unit 4 x RJ45 Ethernet user data connectors [Ref. (5) in Fig. 143. on page
289 ], to Ethernet network (only when Enhanced Ethernet plugin is equipped)

3DB 16142 JAAA Ed.01 75 / 866
[1] Checks before starting installation

Before to start the installation of the IDU components, verify:


that the installation and grounding of the rack, or wall mounting kit, have already been
performed: see Chapter 13 from page 49
in case of installation in a rack:
that the installation and cabling of the TRU have already been performed: see Chapter 14
on pages 59 to 63
that the power supply cable(s) for the IDU MAIN (and EXTENSION, if present in the
configuration) unit(s) has (have) already been prepared and connected to the TRU: see
para.14.5 on pages 64 to 66
that in the rack there is the available room for the NE components installation, according
to the NE configuration
that you have all necessary material, according to the NE configuration
that you own plant data to connect the 9400AWY NE IDU to the Customer DDF and external
lines.
[2] Screw tightening torque

In all described operations (fixing subracks to the rack, fixing cables to connectors,
etc.), and unless differently specified, the screw tightening torque must be as stated
in point c ) on page 4

76 / 866 3DB 16142 JAAA Ed.01
[3] Insertion of the Flash Card in the IDU MAIN unit (rear side)
General
The Flash Card shipping packing includes the Flash Card itself, in dedicated packing composed of
two parts (inner and outer clamshell).

The Flash Card, which has an identification label affixed on it, is inside the inner clamshell; these two
parts are inside the outer clamshell, and in this part is present also the booklet shown below, and the
3rd Flash Card label, used in following step 7 ). The label with Logistical item of the Flash Card and
the Flash Card label are affixed in this booklet,
The labels are described in Fig. 179. on page 406 .
Fig. 17. Flash Card booklet with areas for the label
Insertion procedure
1) Remove the Flash Card cover
Flash Card slot
Flash Card cover
2) Wear the antistatic protection armlet [see point b ) on page 4 ] and connect its termination to
a grounded structure
ATTENTION

this avoids the possible damage of the Flash Card for electrostatic discharges
3) Extract the Flash Card from its clamshell

3DB 16142 JAAA Ed.01 77 / 866
4) Insert the Flash Card:

CONNECTOR SIDE

INSERTION BOTTOM SIDE
5) Restore the Flash Card cover
6) Now you can take off the antistatic protection armlet
7) The Flash Card shipping packing contains another selfadhesive label, equal to that affixed on
the Flash Card itself.
As shown below, cut and stick it on the front panel of the IDU Main Unit:
flash card
Licence String

78 / 866 3DB 16142 JAAA Ed.01
[4] Installation of the IDU MAIN unit, and of the IDU EXTENSION unit (if present in the
configuration)
Special mechanical fittings are provided, depending to the width of rack (19 or 21).
The mechanical fittings for installation in in a 19 or 21 ETSI rack are shown in the assembly drawing
of Fig. 18. below
IDU ADAPTER FOR 19 Rack (3DB04834AAAA, default delivery)
IDU ADAPTER FOR 21 Rack (3DB18181AAAA)
Fig. 18. IDU unit with adapter for installation in 19 rack
The installation in in a 19 Laborack is shown in Fig. 19. : fasten the IDU units to the rack by inserting
screws into holes of 19 mechanical adaptors and by screwing them into relevant holes provided with
nut cage situated on rack brackets
Screw hole Nut cage

Fig. 19. IDU unit installation in Laborack

3DB 16142 JAAA Ed.01 79 / 866
[5] Optional grounding of the IDU MAIN unit, and of the IDU EXTENSION unit (if present in the
configuration)

If the installation is made:

in one of the the rack types listed in point a ) on page 243 ,
and by means of the mechanical adapters shown on page 79 ,
there is no need to ground the IDU MAIN / EXTENSION units, because their fastening to the rack
guarantees the connection to the protection ground, in that the rack is wired to the station protection
ground.
In case you use another type of rack or another type of mechanical adapters, for which the subrack
mechanical fastening does not guarantee a good subracktorack electrical contact, it is necessary
to ground each IDU unit to the rack, using the Faston connector present on the rear side of the unit,
as shown in following Fig. 20.
The section of the Yellow/Green cable (wire) to use must be 1 x 3 mm2 (12AWG)
Fig. 20. IDU unit grounding (if necessary)

Label the cable at both ends:
Link ID Main Ground Link ID Extension Ground

80 / 866 3DB 16142 JAAA Ed.01
[6] Assembling and installation of the PROTECTION BOXES (if present in the configuration)
1) Perform assembly as depicted in Fig. 21. : in case of KIT 3DB16151AAAA, notice that the E1
PROTECTION BOX must be on the left, and the SERVICE PROTECTION BOX must be on the
right
CASE OF KIT 3DB16151AAAA
E1 PROTECTION BOX
SERVICE PROTECTION BOX
equipment side connectors line side connectors
Support (belonging to kit P/N 3DB16151AAAA)
CASE OF KIT 3DB16151ABAA

SERVICE PROTECTION BOX SERVICE PROTECTION BOX
line side connectors line side connectors
Support (belonging to kit P/N 3DB16151ABAA)

N.B. The use of two Service Protection Boxes on the same support is explained in para.18.3.4
on page 212
Fig. 21. Assembling the PROTECTION BOXES on the 19 support
2) fix the assembly to the 19 rack.

N.B. In case of installation in a 21 rack, use the specific 19 / 21 adapter kit (P/N
3DB16152AAAA), which contains two adapters as that shown below, besides
mounting materials:
(3DB16144AAA)

3DB 16142 JAAA Ed.01 81 / 866
[7] Interconnection of IDU MAIN and EXTENSION units (only for 1+1 systems)

[8] Connection of power supply cable to the IDU MAIN unit, and to the IDU EXTENSION unit (if
SAFETY RULES
Before performing this cabling operation, make sure that:
the power supply circuit breaker at the customer distributor panel is turned OFF.
the ON/OFF switch of the:
IDU MAIN unit ; Ref. (2) in Fig. 143. on page 289
IDU EXTENSION unit (if present in the configuration); Ref. (2) in Fig. 145.
on page 294
is (are) in OFF position:
0 OFF
The power supply cable should have already been prepared and connected to the TRU, as explained
in para.14.5.3 on page 66 . If not yet done, label the cable at both ends:
Link ID 48V Main Link ID 48V Extension
Now, connect and fix the power supply cables connector on the IDU unit connector:

82 / 866 3DB 16142 JAAA Ed.01
[9] Preparation of cables for connection of IDU to Customer DDF (if present in the configuration)
a) Introduction
Need for this preparation
Typical example station layouts, requiring this preparation for all the connections from IDU
to the Customer DDF are shown on pages 103 and 108
Other station layouts require this preparation only for some connections from IDU to the
Customer DDF, as shown in examples on pages 104 and 118
Cable unsheathing
Cables used to connect IDU to Customer DDF are supplied by AlcatelLucent with one
end unterminated, as in this example:
unterminated end
The unterminated end must be unsheathed by the installer.
Twisted pair identification
Wires to be connected to Customer DDF are twisted pairs uniquely identified by pair of
colors, as in this example:
YellowBlue pair
WhiteBrown pair
To identify the correspondence between twisted pairs colors and the carried signals, you
must use together:
the pinout of the IDU connector, which the cable is connected to (this gives you the
signals present on each pin of the connector)
and, starting from the P/N of the used cable, the specific CONNECTION CABLE
documented in chapter 113 from page 327
Connector labelling, and twisted pair tieing and labelling
For installation, service and maintenance purposes, before connecting the cable to IDU
and to DDF:
at connector side, the cable should be labelled with the IDU connector name
at DDF side, twisted pairs should be grouped, tied, and labelled according to:
the carried signals,
and the DDF structure.

3DB 16142 JAAA Ed.01 83 / 866
Suggested detailed instructions for the preparation of cables are given on following pages:

Cable type On page

From IDU MAIN unit to Customer DDF
116 E1 tributary cable 85
1732 E1 tributary cable 86
ALMNMS cable (note) 87
AUDIOUSER SERV cable 89
From Service Protection Box to Customer DDF (note)
ALM cable 91
NMS V11AUDIO1 cable 92
NMS G703AUDIO2 cable 93
ESC cable 94
note: This description is given for information completion.

Take into account that, in case of network interconnections for NMS channel and
EOW audio continuity, the connections on the connectors:
ALMNMS of the IDU MAIN unit
and of the Service Protection Box
must be done as specified in Chapter 18 from page 195
In each connection table:
P1 .. Px specify the pair number, according to the specific CONNECTION CABLE

documented in chapter 113 from page 327 ,
numbers specify the pin numbers (according to the specific IDU connector used),
and color is the color of the wire.
N.B. Obviously, you must prepare only the cables present in the specific NE configuration.

84 / 866 3DB 16142 JAAA Ed.01
b) Preparation of 116 E1 tributary cable from IDU MAIN to Customer DDF
Example referred to configuration depicted in para.15.3.1 on page 103 :
pinout of IDU connector 116 E1 as in Tab. 63. on page 307

CONNECTION TABLE of cable P/N 3CC52117ABAA as in para.113.5 on page 333

DDF organized in Tx and Rx, by 8 pair groups

Combining this information, the result is:
CABLE N 1 (Tx) Tx 18
Tx 916
Link ID I/O (116) CABLE N 2 (Rx) Rx 18

Rx 916
CABLE N5 1: Tx 1 to 8
P1 P2 P3 P4 P5 P6 P7 P8
2 36 4 38 6 40 8 42 10 44 12 46 14 48 16 50
white blue white orange white green white brown white grey yellow blue yellow orange yellow green
Labelling: Link ID Tx Trib 1 to 8
P9 P10 P11 P12 P13 P14 P15 P16
18 52 20 54 22 56 24 58 26 60 28 62 30 64 32 66
yellow brown yellow grey violet blue violet orange violet green violet brown violet grey black blue
CABLE N5 2: Rx 1 to 8
P1 P2 P3 P4 P5 P6 P7 P8
3 37 5 39 7 41 9 43 11 45 13 47 15 49 17 51
Labelling: Link ID Rx Trib 1 to 8
P9 P10 P11 P12 P13 P14 P15 P16
19 53 21 55 23 57 25 59 27 61 29 63 31 65 33 67

3DB 16142 JAAA Ed.01 85 / 866
c) Preparation of 1732 E1 tributary cable from IDU MAIN to Customer DDF

pinout of IDU connector 1732 E1 as in Tab. 64. on page 309


DDF organized in Tx and Rx, by 8 pair groups
Tx 1724
Tx 2532
CABLE N 1 (Tx)
Link ID I/O (1732)
Rx 1724
Rx 2532
CABLE N 2 (Rx)
P17 P18 P19 P20 P21 P22 P23 P24
2 36 4 38 6 40 8 42 10 44 12 46 14 48 16 50
P25 P25 P27 P28 P29 P30 P31 P32
18 52 20 54 22 56 24 58 26 60 28 62 30 64 32 66
P17 P18 P19 P20 P21 P22 P23 P24
3 37 5 39 7 41 9 43 11 45 13 47 15 49 17 51
P25 P25 P27 P28 P29 P30 P31 P32
19 53 21 55 23 57 25 59 27 61 29 63 31 65 33 67

86 / 866 3DB 16142 JAAA Ed.01
d) Preparation of ALMNMS cable from IDU MAIN to Customer DDF
pinout of IDU connector ALMNMS as in Tab. 65. on page 311

explanations on:
Alarms and Housekeeping signals, from page 317

NMS V11 signals, from page 322
NMS G703 signals, from page 323
AlarmsHousekeeping
NMS V11+G703
Link ID ALMNMS
ALARMSHOUSEKEEPING
P5 P7 P8 P10 P14
9 12 13 14 15 30 10 11 25 26
GND A_1 COM_GND HK_I1 HK_I2 HK_I4 HK_O1 COM HK_O2 HK_O3
whitebl
blue orange yellow orange red orange white green black
ue
P15 P16 P21 P22
27 42 28 29 40 41 43 44
A_2 COM_GND COM_GND HK_I3 HK_O4 A_3 HK_I5 HK_I6
green whiteblue brown white grey white grey yellow
Labelling: Link ID AlarmsHousekeeping

3DB 16142 JAAA Ed.01 87 / 866
NMS V11+G703

NMS V11

P10 P11
17 18 19 20
CC_RXP (V11) CC_RXN (V11) RX_CKN (V11) RX_CKP (V11)
(DATA RX +) (DATA RX ) (CLOCK CK) (CLOCK CK+)
orange whiteblue green white
P17 P18
32 33 34 35
CC_TXP (V11) CC_TXN (V11) CC_TCKP (V11) CC_TCKN (V11)
(DATA TX +) (DATA TX ) (CLOCK TCK+) (CLOCK TCK)
brown yellow brown red
NMS G703
P2 P3
2 3 4 5
COD_TXP (G703) COD_TXN (G703) COD_RXP (G703) COD_RXN (G703)
(G703_64K_TX+) (G703_64K_TX) (G703_64K_RX+) (G703_64K_RX)
blue yellow blue red
Labelling: Link ID NMS V11+G703

88 / 866 3DB 16142 JAAA Ed.01
e) Preparation of AUDIOUSER SERV cable from IDU MAIN to Customer DDF
pinout of IDU connector AUDIOUSER SERV as in Tab. 66. on page 313

explanations on User service channels signals from page 324


User Service Channels Link ID AUDIOUSER SERV
Audio
USER SERVICE CHANNELS
G703
P2 P3
2 3 4 5
COD_TXP (G703) COD_TXN (G703) COD_RXP (G703) COD_RXN (G703)
blue yellow blue red
V11
P10 P11
17 18 19 20
CC_RXP (V11) CC_RXN (V11) RX_CKN (V11) RX_CKP (V11)
orange whiteblue green white
P17 P18
32 33 34 35
CC_TXP (V11) CC_TXN (V11) CC_TCKP (V11) CC_TCKN (V11)
brown yellow brown red
RS232
P4 P12
7 8 22 23
RX_ASY (RS232) GND TX_ASY (RS232) GND
blue black green yellow
Labelling: Link ID User Service Channels

3DB 16142 JAAA Ed.01 89 / 866
AUDIO
N.B. meaningful only if the Audio + User Service Channel plugin is present in IDU MAIN unit

AUDIO 1
P6 P7
10 11 13 14
1WEOW_IN_P 1WEOW_IN_N 1WEOW_OUTP 1WEOW_OUT_N
(from user+) (from user) (to user+) (to user)
orange white orange yellow
AUDIO 2
P21 P22
40 41 43 44
2EEOW_IN_P 2EEOW_IN_N 2EEOW_OUTP 2EEOW_OUT_N
(from user+) (from user) (to user+) (to user)
grey white grey yellow
Labelling: Link ID Audio

90 / 866 3DB 16142 JAAA Ed.01
f) Preparation of ALM cable from Service Protection Box to Customer DDF
pinout of Service Protection Box connector ALM as in Tab. 58. on page 302
explanations on Alarms and Housekeeping signals, from page 317

CONNECTION TABLE of cable P/N 3DB05594AAAA as in para.113.17 on page 348

AlarmsHousekeeping
Link ID ALM
ALARMSHOUSEKEEPING
P1 P2 P3 P4
2 9 3 10 4 1 5 12
A_2 COM A_3 GND HK_O1 A_1 HK_O3 HK_O4
blue white violet turquoise orange white violet turquoise
P5 P6 P7 P8
6 13 7 14 8 15 11 not
HK_I1 HK_I2 HK_I3 HK_I4 HK_I5 HK_I6 HK_O2 connected
green white violet turquoise brown white violet turquoise
Labelling: Link ID AlarmsHousekeeping

3DB 16142 JAAA Ed.01 91 / 866
g) Preparation of NMS V11AUDIO1 cable from Service Protection Box to Customer DDF

pinout of Service Protection Box connector NMS V11AUDIO1 as in Tab. 59. on page

303

explanations on NMS V11 Audio 1 signals, on page 322
NMS V11
Link ID NMS V11AUDIO1

Audio 1
NMS V11
P1 P2 P3
2 9 3 10 4 1
RS422 clock in RS422 data in RS422 data RS422 clock in RS422 clock RS422 data in
(+) () out (+) () out (+) (+)
blue white violet turquoise orange white
P4 P8
5 12 11
not connected
GND NMS RS422 clock out () RS422 data out ()
violet turquoise violet turquoise
Labelling: Link ID NMS V11
AUDIO 1
P5 P6 P7
6 13 7 14 8 15
Audio1 signal Audio1 signal Audio1 signal Audio1 signal
GND Audio Not used
from user (+) from user () to user (+) to user ()
green white violet turquoise brown white
Labelling: Link ID Audio 1

92 / 866 3DB 16142 JAAA Ed.01
h) Preparation of NMS G703AUDIO2 cable from Service Protection Box to Customer DDF
pinout of Service Protection Box connector NMS G703AUDIO2 as in Tab. 60. on page
304
explanations on NMS G703 Audio 2 signals, on page 323

NMS G703
Link ID NMS G703AUDIO2

Audio 2
NMS G703
P1 P2 P3
2 9 3 10 4 1
G703 data in G703 data out G703 data in
Not used Not used Not used
() (+) (+)
blue white violet turquoise orange white
P4 P8
5 12 11
not connected
GND NMS Not used G703 data out ()
violet turquoise violet turquoise
Labelling: Link ID NMS G703
AUDIO 2
P5 P6 P7
6 13 7 14 8 15
Audio2 signal Audio2 signal Audio2 signal Audio2 signal
GND Audio Not used
from user (+) from user () to user (+) to user ()
green white violet turquoise brown white
Labelling: Link ID Audio 2

3DB 16142 JAAA Ed.01 93 / 866
i) Preparation of ESC cable from Service Protection Box to Customer DDF

pinout of Service Protection Box connector ESC as in Tab. 61. on page 305

explanations on User service channels signals from page 324

User Service Channels

Link ID ESC
USER SERVICE CHANNELS

P1 P2 P3 P4
2 9 3 10 4 1 5 12
COD_RX + COD_RX COD_TX + COD_TX RX_ASY GND CC_RX + CC_RX
blue white violet turquoise orange white violet turquoise
P5 P6 P7 P8
6 13 7 14 8 15 11
not
RX_CK + RX_CK CC_TX + CC_TX CC_TCK + CC_TCK TX_ASY connected
green white violet turquoise brown white violet turquoise
Labelling: Link ID User Service Channels

94 / 866 3DB 16142 JAAA Ed.01
[10] Installation of the DISTRIBUTOR SUBRACKS (if present in the configuration)
The DISTRIBUTOR SUBRACKS are all 19 units, some 3U high, other 1U high. They are shown,
together with their P/Ns, in figures of point g ) from page 245

N.B. In case of installation in a 21 rack, use the specific 19 / 21 adapter kit; in case of:
3U high subrack, use the kit P/N 3CC50042AAAA, which contains two adapters as
that shown below, besides mounting materials:
(3CC5034AAAA)
1U high subrack, use the kit P/N 3CC50065AAAA, which contains two adapters as
that shown below, besides mounting materials:
(3CC50066AAAA)
75 W DDF support 120 W DDF support
Suggestion: for ease of cable positioning, in particular with ETSI rack (with unremovable back
cover), make a temporary installation of the DISTRIBUTOR SUBRACK(s), position and connect the
signal cables (as specified in next step [11] ), and, at last, fix the DISTRIBUTOR SUBRACK(s) in
its / their definitive position.

3DB 16142 JAAA Ed.01 95 / 866
[11] Positioning and connection of signal cables (according to system configuration)

General cabling rules

The cables must be positioned in such a way:
caution to avoid equipment damage
to avoid their possible damage (e.g. avoiding excessive bending or connector forcing)
to allow easy extraction of IDU MAIN / EXTENSION units, for service and maintenance purpose
General connection rules
cables terminated by connectors at both sides must be connected to IDU units as depicted in
the connection diagram relevant to the specific NE configuration (*)
cables from IDU to DDF must have already been prepared (see step [9] from page 83 ), and
must be connected:
to IDU units, as depicted in the connection diagram relevant to the specific NE
configuration (*)
at DDF side, according to the specific plant documentation
(*) NE configurations and relevant connection diagrams are described in para.15.3 from
page 101
Positioning and connection examples
In the following, some examples of signal cables positioning and connection are depicted:
Base configuration Protection boxes Distributor subrack(s) on page
1+0 NO NO 97
NO NO 97
YES NO 98
1+1
NO YES 99
YES YES 100

96 / 866 3DB 16142 JAAA Ed.01
a) 1+0 configuration without protection boxes, and with no distributor subrack
b) 1+1 configuration without protection boxes, and with no distributor subrack

3DB 16142 JAAA Ed.01 97 / 866
c) 1+1 configuration with protection boxes, and with no distributor subrack

For easy installation, insert the ALMNMS cable and, if present, the AUDIOUSER

SERV cable, between the MAIN IDU and the right side of the Service Protection Box:

For easy installation, insert the E1 TRIBUTARY cable(s) between the MAIN IDU and the
left side of the E1 Protection Box:
Do not bend these cables

too much

98 / 866 3DB 16142 JAAA Ed.01
d) 1+1 configuration without protection boxes, and with distributor subrack(s)
These example figures show only the cabling of E1 tributaries with 120 W 3U distributor. For
other cables, refer to the other examples.

Full protected configuration with 3CC52157AAAA cords front side
Radio protected configuration with 3CC52157AAAA cords front side
Full protected configuration with 3CC52157AAAA cords rear side

3DB 16142 JAAA Ed.01 99 / 866
e) 1+1 configuration with protection boxes, and with distributor subrack(s)

Cable positioning Front Cable positioning Rear
Cable Positioning Front Cable Positioning Rear

From IDU/EXTENSION From IDU/EXTENSION
To Service protection box SubD44pin/SubD15pin To Service protection box SubD44pin/SubD15pin
Cable Positioning
From IDU/EXTENSION
To E1 protection box SCSI968Male/SCSI68Male
End of IDU installation and cabling procedure

100 / 866 3DB 16142 JAAA Ed.01
15.3 IDU configuration types and cabling
Tab. 2. below lists the P/Ns of main IDU components:
Tab. 2. P/Ns of main IDU components

TRIBUTARY CONFIGURATION
Logistical Item & Description
N.B. the Logistical Item corresponds 16E1 32E1
to the Logistical Item code you 16E1+
16E1 + 32E1 +
16E1 + 4 ETH +
can read on the IDUs label (see 16E1 AUDIO & 32E1 AUDIO &
4 ETH AUDIO &
Fig. 14. on page 70 ) USC USC
USC
ETSI IDU MAIN UNITS (48/60V POWER SUPPLY)
For 1+0 and 1+1 configurations
3DB16040ACXX
X
MAIN IDU 64Mb 16E1 48V
3DB16058ACXX
X
MAIN IDU 64Mb 16E1 48V Audio+USC
3DB16160AAXX
X
MAIN IDU 64Mb 16E1 ENH. DATA 48V
3DB16162AAXX
MAIN IDU 64Mb 16E1 ENHDATA 48V X
Audio+USC
3DB16041ACXX
X
MAIN IDU 64Mb 32E1 48V
3DB16059ACXX
X
MAIN IDU 64Mb 32E1 48V Audio+USC
ETSI IDU EXTENSION UNITS (48/60V POWER SUPPLY)
Only for 1+1 configurations
3DB16044ACXX
X X X X
EXT IDU 64Mb 16E1 48V choice
3DB16045ACXX n.b.1
EXT IDU 64Mb 32E1 48V
PROTECTION BOXES AND SUPPORT KITS
3DB16102AAXX
equipped or not equipped n.b.1
E1 Protection (SCSI 68 / Dsub 37)
3DB16103AAXX
equipped or not equipped n.b.1
Services Protection (Dsub44 / Dsub15)
3DB16151ABAA necessary whenever 1 or 2 Services Protection Box(es) must

DIN Rack Kit for 2 Service protection boxes be used, with no need of the E1 Protection Box n.b.2
3DB16151AAAA necessary whenever the E1 Protection Box must be used,
DIN rack kit distributor panels (with or without the Services Protection Box)
OPTIONAL E1 DISTRIBUTOR SUBRACK (choice)
For employment examples, refer to IDU configurations listed in Tab. 3. on page 102
3CC07810AAAA 3U DISTRIBUTOR SUBRACK FOR 120 W EMC (32E1)
3CC08062AAAA 1U DISTRIBUTOR SUBRACK FOR 120 W non EMC (16E1)
3CC08061AAAA 1U DISTRIBUTOR SUBRACK FOR 75 W 1.6/5.6 (16E1)
3CC08061ABAA 1U DISTRIBUTOR SUBRACK FOR 75 W BNC (16E1)
n.b.1 The general equipping rules are explained:
for 1+0 configurations, in para.21.3.2 on page 377
for 1+1 configurations, in Tab. 76. on page 379
n.b.2 Fig. 118. on page 212 shows an usage example for 2 Services Protection Boxes

3DB 16142 JAAA Ed.01 101 / 866
In the following paragraphs, the most common IDU configurations, included the list of used cables, and
the relative connection diagrams, are described, as listed in Tab. 3. below

Tab. 3. Examples of IDU configurations

Service
Protection
Basic configuration and With E1 Described
box
tributary configuration distributor on page
equipped
(nb1)
1+0
16E1 none N 103
none N 103
16E1 + AUDIO & USC 120 W N 104
75 W 1.6/5.6 or BNC N 105
16E1+ 4 ETH + AUDIO & USC 120 W N 107
32E1 none N 108
none N 108
32E1 + AUDIO & USC 120 W N 109
75 W 1.6/5.6 or BNC N 110
1+1 radio protected (without EPS) (nb2)
75 W 1.6/5.6 or BNC N 112
16E1 + AUDIO & USC
120 W N 114
75 W 1.6/5.6 or BNC N 115
16E1+ 4 ETH + AUDIO & USC
120 W N 117
75 W 1.6/5.6 or BNC N 118
32E1 + AUDIO & USC
120 W N 120
E1
Protection
1+1 fully protected (with EPS) (nb2) : EPS made by: protection
Y cable
box
75 W 1.6/5.6 or BNC Y X 121

16E1 + AUDIO & USC
120 W Y X 123
75 W 1.6/5.6 or BNC Y X 125
16E1+ 4 ETH + AUDIO & USC
120 W Y X 127
75 W 1.6/5.6 or BNC Y X 129
32E1 + AUDIO & USC
120 W Y X 131
(nb1) in case of network interconnections for NMS channel and EOW audio continuity, the Service
Protection box is practically always required, and the connections on IDU ALMNMS
connector must be done as specified in Chapter 18 from page 195
(nb2) for the description of protection types, if necessary, refer to para.21.3.3.1 from page 378
WARNING: in all cabling diagrams, the cables are depicted schematically; for details on each cable
(structure, connectors, and pin connection tables) refer to chapter 113 from page 327

102 / 866 3DB 16142 JAAA Ed.01
15.3.1 16E1 IDU 1+0 with/without Audio and User Service Channel plugin, without Service
Protection box and without E1 distributor subrack
C
B D
A Main
E
Description Code Quantity
MAIN IDU 64Mb 16E1 48V 3DB16040ACXX

or 1
MAIN IDU 64Mb 16E1 48V Audio+USC 3DB16058ACXX
Cable Connection
Ref. Code Description From To
3CC08209AAAA Power supply connection

24V (3x2.5mm2)
A or IDU T.R.U.
Power supply connection
3CC08165AAAA
48V (3X1.5mm2)
Cord IDU DDF

B 3CC52117ABAA
SCSI68Male/SCSI68 free 116E1 CUSTOMER
3CC52115ABAA Cord IDU DDF

C
(N.B.) SubD44Male/free Audio User Service CUSTOMER
Cord IDU DDF

D 3CC52115ABAA
SubD44Male/free ALMNMS CUSTOMER
1AC001100022 Coax cable 50Ohm 10.3 mm

E or IDU ODU
N.B. only with MAIN IDU 64Mb 16E1 48V Audio+USC equipped
Fig. 22. 16E1 IDU 1+0 with/without Audio and User Service Channel plugin, without Service

3DB 16142 JAAA Ed.01 103 / 866
15.3.2 16E1 IDU 1+0 with Audio and User Service Channel plugin, and with distributor 120
Ohm

Distributor 3U subrack 19 inch Modules 120 W
B C
D
A Main E
MAIN IDU 64Mb 16E1 48V Audio+USC 3DB16058ACXX 1
Distributor Subrack 19Inch Modules 120Ohm 3CC07810AAAA 1
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
Distributor 3U
Cable 16XE1 IDU / IDU
B 3CC52133AAAA Subrack 19inch 120
DISTR120Ohm 116E1
Ohm
IDU
DDF
C Audio User
Cord CUSTOMER
3CC52115ABAA Service
SubD44Male / free
IDU DDF
D
ALM NMS CUSTOMER
1AC001100022 Coax cable 50Ohm 10.3
or mm
E IDU ODU
1AC041350001 Coax cable 50Ohm
6.85mm
Fig. 23. 16E1 IDU 1+0 with Audio and User Service Channel plugin, and with distributor 120 Ohm

104 / 866 3DB 16142 JAAA Ed.01
Ohm (1.6/5.6 or BNC)
D Support connectors 1.6/5.6 75 Ohm Panel 1U

or
Distributor subrack for BNC
C
B
E
F
Main G
A
Support connectors 1.6/5.6 75 Ohm Panel 1U 3CC08061AAAA

or 1
Distributor subrack for BNC 3CC08061ABAA

3DB 16142 JAAA Ed.01 105 / 866
Cable Connection


Power supply
3CC08209AAAA connection
24V (3x2.5mm2)
A or IDU T.R.U.
Power supply
48V (3X1.5mm2)
M1 IDU 116E1
Cord 120 Ohm
B 3CC52134AAAA SCSI68/DSUB37 2 x M2 (IN/OUT 18) subD 37 of cable C
16 pairs
M3 (IN/OUT 916) subD 37 of cable D
Cable for distributor Support connectors

3CC07885ABAA
1.6/5.6 (8 x 2 Mbit/s) 1.6/5.6 75 Ohm Panel 1U
C
M2 & M3
& or or
of cable B
D
Cable for distributor Distributor subrack for
3CC07759ABAA
BNC (8 x 2 Mbit/s) BNC
IDU
DDF
E Audio
Cord CUSTOMER
3CC52115ABAA User Service
SubD44Male / free
IDU DDF
F
ALM NMS CUSTOMER
1AC001100022 Coax cable 50 Ohm

or 10.3 mm
G IDU ODU
6.85 mm
(1.6/5.6 or BNC)

106 / 866 3DB 16142 JAAA Ed.01
15.3.4 16E1 IDU 1+0 with Audio and User Service Channel plugin, Enhanced Data plugin
and with distributor 120 Ohm
B
F FF F C
D
A Main E
MAIN IDU 64Mb 16E1 ENHDATA 48V Audio+USC 3DB16162AAXX 1
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
Distributor 3U
Cable 16XE1 IDU / IDU
DISTR120 Ohm 116E1
Ohm
IDU
DDF
C Audio User
Cord CUSTOMER
SubD44Male / free
IDU DDF
D
ALM NMS CUSTOMER
or 10.3 mm
E IDU ODU
6.85mm
F 3CC52141ACAA RJ45 Cat 5 E IDUMAIN CUSTOMER
Fig. 25. 16E1 IDU 1+0 with Audio and User Service Channel plugin, Enhanced Data plugin and with
distributor 120 Ohm

3DB 16142 JAAA Ed.01 107 / 866
15.3.5 32E1 IDU 1+0 with/without Audio and User Service Channel plugin, without Service

F C

B D
Main
A E
MAIN IDU 64Mb 32E1 48V 3DB16041ACXX
or 1
MAIN IDU 64Mb 32E1 48V Audio+USC 3DB16059ACXX
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
Cord IDU DDF
B 3CC52117ABAA
3CC52115ABAA IDU DDF
C
(N.B.) Cord Audio User Service CUSTOMER
SubD44Male/free IDU DDF
D 3CC52115ABAA
ALMNMS CUSTOMER
E or IDU ODU
Cord IDU DDF
F 3CC52117ABAA
N.B. only with MAIN IDU 64Mb 32E1 48V Audio+USC equipped
Fig. 26. 32E1 IDU 1+0 with/without Audio and User Service Channel plugin, without Service

108 / 866 3DB 16142 JAAA Ed.01
Ohm
B B C
D
A Main E
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
IDU Distributor 3U
Cable 16XE1
B 3CC52133AAAA 116E1 Subrack 19inch 120
IDU/DISTR120Ohm
1732E1 Ohm
IDU
DDF
C Audio User
Cord CUSTOMER
SubD44Male / free
IDU DDF
D
ALM NMS CUSTOMER
1AC001100022 Coax cable 50Ohm 10.3
or mm
E IDU ODU
6.85mm

3DB 16142 JAAA Ed.01 109 / 866
Ohm (1.6/5.6 or BNC)

or
C (116 E1)
B
G Support connectors 1.6/5.6 75 Ohm Panel 1U

or
F (1732 E1)
E
H
I
Main J
A

or 2

110 / 866 3DB 16142 JAAA Ed.01
Cable Connection

Power supply
24V (3x2.5mm2)
A or IDU T.R.U.
Power supply
48V (3X1.5mm2)
M1 IDU 116E1
Cord 120 Ohm
16 pairs
M3 (IN/OUT 916) subD 37 of cable D
Support connectors
Cable for distributor
3CC07885ABAA 1.6/5.6 75 Ohm Panel 1U
1.6/5.6 (8 x 2 Mbit/s)
(116E1)
C
M2 & M3
& or or
of cable B
D
Distributor subrack for
3CC07759ABAA BNC
BNC (8 x 2 Mbit/s)
(116E1)
M1 IDU 1732E1
Cord 120 Ohm
E 3CC52134AAAA SCSI68/DSUB37 2 x M2 (IN/OUT 18) subD 37 of cable F
16 pairs
M3 (IN/OUT 916) subD 37 of cable G
Support connectors
1.6/5.6 (8 x 2 Mbit/s)
(1732E1)
F
M2 & M3
& or or
of cable E
G
Distributor subrack for
3CC07759ABAA BNC
BNC (8 x 2 Mbit/s)
(1732E1)
IDU
DDF
H Audio
Cord CUSTOMER
SubD44Male / free
IDU DDF
I
ALM NMS CUSTOMER

or 10.3 mm
J IDU ODU
6.85 mm
(1.6/5.6 or BNC)

3DB 16142 JAAA Ed.01 111 / 866
15.3.8 16E1 IDU 1+1 radio protected with Audio and User Service Channel plugin, and with
distributor 75 Ohm (1.6/5.6 or BNC)

or
C
B
E
F
A Main H
G
A Extension H
EXT IDU 64Mb 16E1 48V 3DB16044ACXX 1
or 1

112 / 866 3DB 16142 JAAA Ed.01
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
M1 IDUMAIN 116E1
Cord 120 Ohm M2 (IN/OUT

subD 37 of cable C
B 3CC52134AAAA SCSI68/DSUB37 2 x 16 18)
pairs
M3 (IN/OUT
subD 37 of cable D
916)

3CC07885ABAA
C
or M2 & M3 or
&
of cable B
D
Cable for distributor BNC Distributor subrack for
3CC07759ABAA
(8 x 2 Mbit/s) BNC
IDUMAIN
DDF
E AUDIO
CUSTOMER
Cord USER SERV
3CC52115ABAA
SubD44Male / Free IDUMAIN
DDF
F AUDIO
CUSTOMER
ALMNMS
G 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION

or 10.3 mm
H IDU ODU
6.85 mm
Fig. 29. 16E1 IDU 1+1 radio protected with distributor subrack for 1.6/5.6 75 Ohm or BNC

3DB 16142 JAAA Ed.01 113 / 866
distributor 120 Ohm

B
C
D
A Main E
F
A Extension E
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
Distributor 3U
Cable 16XE1 IDU / IDUMAIN
DISTR120 Ohm 116E1
Ohm
IDU
DDF
C Audio
Cord CUSTOMER
SubD44Male / free
IDU DDF
D
ALM NMS CUSTOMER
or 10.3 mm
E IDU ODU
6.85 mm
F 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
Fig. 30. 16E1 IDU 1+1 radio protected with Audio and User Service Channel plugin, and with
distributor 120 Ohm

114 / 866 3DB 16142 JAAA Ed.01
Enhanced Data plugin, and with distributor 75 Ohm (1.6/5.6 or BNC)

or
C
B
I I I I E
F
Main H
A G
Extension H
A

or 1

3DB 16142 JAAA Ed.01 115 / 866
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
M1 IDUMAIN 116E1
Cord 120 Ohm M2 (IN/OUT

subD 37 of cable C
B 3CC52134AAAA SCSI68/DSUB37 2 x 16 18)
pairs
M3 (IN/OUT
subD 37 of cable D
916)

3CC07885ABAA
C
or M2 & M3 or
&
of cable B
D
Cable for distributor BNC Distributor subrack for
3CC07759ABAA
(8 x 2 Mbit/s) BNC
IDUMAIN
DDF
E AUDIO
CUSTOMER
Cord USER SERV
3CC52115ABAA
SubD44Male / Free IDUMAIN
DDF
F AUDIO
CUSTOMER
ALMNMS
or 10.3 mm
H IDU ODU
6.85 mm
I 3CC52141ACAA RJ45 Cat 5 E IDUMAIN CUSTOMER
Fig. 31. 16E1 IDU 1+1 radio protected with Audio and User Service Channel plugin, Enhanced Data
plugin and with distributor 75 Ohm (1.6/5.6 or BNC)

116 / 866 3DB 16142 JAAA Ed.01
Enhanced Data plugin, and with distributor 120 Ohm
B F FF F C
D
A Main E
G
A Extension E
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
Distributor 3U
Cable 16XE1 IDU / IDUMAIN
DISTR120 Ohm 116E1
Ohm
IDU Audio User DDF
C
Cord Service CUSTOMER
3CC52115ABAA
SubD44Male / free IDU DDF
D
ALM NMS CUSTOMER
or 10.3 mm
E IDU ODU
6.85 mm
F 3CC52141ACAA RJ45 Cat 5 E IDUMAIN CUSTOMER
Fig. 32. 16E1 IDU 1+1 radio protected with Audio and User Service Channel plugin, Enhanced Data
plugin, and with distributor 120 Ohm

3DB 16142 JAAA Ed.01 117 / 866

or
C (116 E1)
B
G Support connectors 1.6/5.6 75 Ohm Panel 1U

or
F (1732 E1)
E
H
I
Main K
A J
Extension K
A
or 2

118 / 866 3DB 16142 JAAA Ed.01
Cable Connection

Power supply
24V (3x2.5mm2)
A or IDU T.R.U.
Power supply
48V (3X1.5mm2)
M1 IDU 116E1
Cord 120 Ohm
16 pairs M3 (IN/OUT 916) subD 37 of cable D
Support connectors
1.6/5.6 (8 x 2 Mbit/s)
C (116E1)
M2 & M3
& or or
of cable B
D Distributor subrack for
3CC07759ABAA BNC
BNC (8 x 2 Mbit/s)
(116E1)
M1 IDU 1732E1
Cord 120 Ohm
E 3CC52134AAAA SCSI68/DSUB37 2 x M2 (IN/OUT 18) subD 37 of cable F
16 pairs M3 (IN/OUT 916) subD 37 of cable G
Support connectors
1.6/5.6 (8 x 2 Mbit/s)
F (1732E1)
M2 & M3
& or or
of cable E
G Distributor subrack for
3CC07759ABAA BNC
BNC (8 x 2 Mbit/s)
(1732E1)
IDU
DDF
H Audio
Cord CUSTOMER
SubD44Male / free
IDU DDF
I
ALM NMS CUSTOMER
J 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
or 10.3 mm
K IDU ODU
6.85 mm

3DB 16142 JAAA Ed.01 119 / 866
distributor 120 Ohm


C D
E
B
A Main G F
Extension
A F
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
IDUMAIN
B Distributor 3U
Cable 16XE1 IDU / 116E1
3CC52133AAAA Subrack 19inch 120
DISTR120 Ohm IDUMAIN
C Ohm
1732E1
IDU Audio User DDF
D
Cord Service CUSTOMER
3CC52115ABAA
SubD44Male / free IDU DDF
E
ALM NMS CUSTOMER
or 10.3 mm
F IDU ODU
6.85 mm
distributor 120 Ohm

120 / 866 3DB 16142 JAAA Ed.01
15.3.14 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, and with
B
Support Connectors 1.6/5.6 75 W Panel 1U or BNC

B
Line side
L L L L
Line side
Equipment side
D
Equipment side
C
F G
H
A Main E
A Extension E
Services Protection (Dsub44 / Dsub15) 3DB16103AAXX 1
E1 Protection (SCSI 68 / Dsub 37) 3DB16102AAXX 1
Support connectors 1.6/5.6
3CC08061AAAA
75 Ohm Panel 1U
1
or
DIN Rack Kit Distributor Panels 3DB16151AAAA 1

3DB 16142 JAAA Ed.01 121 / 866
Cable Connection

3CC08209AAAA

24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
3CC07885ABAA
1.6/5.6 (8 x 2 Mbit/s) E1 protection box Support connectors
B or SCSI68/SubD 1.6/5.6 75 Ohm
Cable for distributor BNC 37 Panel 1U or BNC
3CC07759ABAA
(8 x 2 Mbit/s)
E1 protection box
IDUMAIN
C SCSI68pin/SubD37pin
116E1
Cord SCSI68SCSI68 E11/16 Main
3CC52118AAAA
L=1m E1 protection box
IDUEXTENSION
D SCSI68pin/SubD37pin
116E1
E11/16 EXT
or 10.3 mm
E IDU ODU
6.85 mm
Service protection box
IDUEXTENSION
F SubD44pin/SubD15pin
USER SERV
USER SERV
Cord IDUMAIN Service protection box
G 3CC52116AAAA SubD44Male/SubD44 AUDIO SubD44pin/SubD15pin
Male USER SERV AUDIO USER SERV
IDUMAIN Service protection box
H AUDIO SubD44pin/SubD15pin
ALMNMS ALMNMS
I 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
Cord Service DDF
L 3DB05594AAAA
SubD15Male / free protection box CUSTOMER
Fig. 35. 16E1 IDU 1+1 fully protected with distributor subrack for 1.6/5.6 75 Ohm or BNC

122 / 866 3DB 16142 JAAA Ed.01
distributor 120 Ohm
SZ1 IN 18
SZ3 IN 916
H H H H
SZ2 OUT 18 Line side
SZ4 OUT 916
B Equipment side
M1 D E
F
A Main C
M2 G
A Extension C
DIN Rack Kit for 2 Service protection boxes 3DB16151ABAA
or or 1
DIN Rack Kit Distributor Panels 3DB16151AAAA

3DB 16142 JAAA Ed.01 123 / 866
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
IDUMAIN
116E1
2 SCSI Male to 4
B 3CC52157AAAA & Distributor 3U 120 Ohm
Terminals Modules
IDUEXTENSION
116E1
or 10.3 mm
C IDU ODU
6.85 mm
IDUEXTENSION
D SubD44pin/SubD15pin
USER SERV
USER SERV
3CC52116AAAA SubD44Male/SubD44
E AUDIO SubD44pin/SubD15pin
(0,5m) Male
USER SERV AUDIO USER SERV
F AUDIO SubD44pin/SubD15pin
ALMNMS ALMNMS
Cord Service DDF
H 3DB05594AAAA
Fig. 36. 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, and with
distributor 120 Ohm

124 / 866 3DB 16142 JAAA Ed.01
15.3.16 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, Enhanced
Data plugin, and with distributor 75 Ohm (1.6/5.6 or BNC)
B

B
Line side
M M M M
Line side
Equipment side
D
Equipment side
C
I I I I F G
H
A Main E
A Extension E
or 1

3DB 16142 JAAA Ed.01 125 / 866
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)

3CC07885ABAA
1.6/5.6 (8 x 2 Mbit/s)
E1 protection box Support connectors
3CC07759ABAA
(8 x 2 Mbit/s)
E1 protection box
IDUMAIN
116E1
3CC52118AAAA
IDUEXTENSION
116E1
E11/16 EXT

or 10.3 mm
E IDU ODU
6.85 mm

IDUEXTENSION
USER SERV
USER SERV

G 3CC52116AAAA SubD44Male/SubD44 AUDIO SubD44pin/SubD15pin
Male USER SERV AUDIO USER SERV

ALMNMS ALMNMS
I 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
L 3CC52141ACAA RJ45 Cat 5 E IDUMAIN CUSTOMER
Cord Service DDF

M 3DB05594AAAA
Fig. 37. 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, Enhanced Data
plugin and with distributor 75 Ohm (1.6/5.6 or BNC)

126 / 866 3DB 16142 JAAA Ed.01
15.3.17 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, Enhanced
Data plugin, and with distributor 120 Ohm
SZ1 IN 18
SZ3 IN 916
H H H H
SZ2 OUT 18 Line side
SZ4 OUT 916
B Equipment side
I I I I
M1 D E
F
A Main C
M2 G
A Extension C
or or 1

3DB 16142 JAAA Ed.01 127 / 866
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
IDUMAIN
116E1
2 SCSI Male to 4
B 3CC52157AAAA & Distributor 3U 120 Ohm
Terminals Modules
IDUEXTENSION
116E1
or 10.3 mm
C IDU ODU
6.85 mm
IDUEXTENSION
D SubD44pin/SubD15pin
USER SERV
USER SERV
E AUDIO SubD44pin/SubD15pin
(0,5m) Male
ALMNMS ALMNMS
Cord Service DDF
H 3DB05594AAAA
I 3CC52141ACAA RJ45 Cat 5 E IDUMAIN CUSTOMER
Fig. 38. 16E1 IDU 1+1 fully protected with Audio and User Service Channel plugin, Enhanced Data
plugin, and with distributor 120 Ohm

128 / 866 3DB 16142 JAAA Ed.01
distributor 75 Ohm
B

B Support Connectors 1.6/5.6 75 W Panel 1U or BNC

B
Line side
N N N N
Line side
Equipment side
D L Equipment side
I F G
H
C
A Main E
Extension E
A
or 2

3DB 16142 JAAA Ed.01 129 / 866
Cable Connection


3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
3CC07885ABAA
1.6/5.6 (8 x 2 Mbit/s)
E1 protection box Support connectors
3CC07759ABAA
(8 x 2 Mbit/s)
E1 protection box
IDUMAIN
116E1
3CC52118AAAA
IDUEXTENSION
116E1
E11/16 EXT
or 10.3 mm
E IDU ODU
6.85 mm
IDUEXTENSION
USER SERV
USER SERV
G 3CC52116AAAA SubD44Male AUDIO SubD44pin/SubD15pin
SubD44Male USER SERV AUDIO USER SERV
ALMNMS ALMNMS
E1 protection box
Cord SCSI68SCSI68 IDUMAIN
I 3CC52118AAAA SCSI68pin/SubD37pin
L=1m 1732 E1
E117/32 Main
SI68Male/Free
E1 protection box
L=15m IDUEXT
L 3CC52118AAAA SCSI68pin/SubD37pin
Cord SCSI68SCSI68 1732 E1
E117/32 EXT
L=1m
M 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
Cord Service DDF
N 3DB05594AAAA
distributor 75 Ohm

130 / 866 3DB 16142 JAAA Ed.01
distributor 120 Ohm
Distributor 3U subrack
19 inch Modules 120 W
SZ1 IN 18
SZ3 IN 916
SZ2 OUT 18 SZ1 IN 1724 (labelled IN 18)
SZ4 OUT 916 SZ3 IN 2532 (labelled IN 916)
SZ2 OUT 1724 (labelled OUT 18)
SZ4 OUT 2532 (labelled OUT 916)
I I I I
Line side
B Equipment side
M1 M1 E F
M2 G
Main
A M2 H D
A Extension D

3DB 16142 JAAA Ed.01 131 / 866


or or 1
Cable Connection
3CC08209AAAA
24V (3x2.5mm2)
A or IDU T.R.U.
3CC08165AAAA
48V (3X1.5mm2)
IDUMAIN
116E1
B &
IDUEXTENSION
2 SCSI Male to 4 116E1
3CC52157AAAA Distributor 3U 120 Ohm
Terminals Modules IDUMAIN
1732E1
C &
IDUEXTENSION
1732E1
or 10.3 mm
D IDU ODU
6.85 mm
IDUEXTENSION
E SubD44pin/SubD15pin
USER SERV
USER SERV
(0,5m) Male
G AUDIO SubD44pin/SubD15pin
ALMNMS ALMNMS
H 3DB16162ABAA 100 wire SCSI cable IDUMAIN IDUEXTENSION
Cord Service DDF
I 3DB05594AAAA
distributor 120 Ohm

132 / 866 3DB 16142 JAAA Ed.01
15.4 IDU horizontal and vertical installation
In following example figures, the 1U space must be left empty, to allow heat dissipation, and positioning
of cables.
Installation type Configuration Figure
1+1 Fig. 41.

horizontal
1+0 Fig. 42.
1+1 Fig. 43.

vertical
1+0 Fig. 44.
15.4.1 Minimum distances between systems installed horizontally in the rack
[1] In 1+1 configurations
without Protection
with Protection Boxes
Boxes
without DDF with DDF with DDF
RACK ETSI RACK ETSI RACK ETSI
1U
Protection Boxes 3U DDF 3U DDF
Main
Extension Protection Boxes 1U
1U Main Main
Protection Boxes Extension Extension
Main 1U 1U
Extension
1U 3U DDF 3U DDF
Protection Boxes
Main Protection Boxes 1U
Extension Main Main
1U Extension Extension
1U 1U 1U
Fig. 41. Horizontal installation in racks of 1+1 systems

3DB 16142 JAAA Ed.01 133 / 866
[2] In 1+0 configurations

without DDF with DDF

RACK ETSI RACK ETSI
1U 1U
Protection Boxes
Main 3U DDF
Protection Boxes
Main Protection Boxes
Protection Boxes Main
Main
Protection Boxes 3U DDF
Main
Protection Boxes Protection Boxes
Main Main
Protection Boxes 1U
Main 1U
1U 1U
without Protection Boxes

without DDF with DDF
first solution second solution
RACK ETSI RACK ETSI RACK ETSI
1U 1U 1U
Main Main DDF
1U Main Main
Main 1U 1U
1U Main DDF
Main Main Main
1U 1U 1U
Main Main DDF
1U Main Main
Main 1U 1U
1U Main DDF
Main Main Main
1U 1U 1U
1U 1U 1U
Fig. 42. Horizontal installation in racks of 1+0 systems

134 / 866 3DB 16142 JAAA Ed.01
1U 1U [1]
USER MANUAL
Extension Main
In 1+1 configuration
1U Extension
Main 1U
Extension Protection Boxes
1U Main
Main Extension

Extension 1U
1U Protection Boxes
Fig. 43. Vertical installation in racks of 1+1 systems

15.4.2 Minimum distances between systems installed vertically in the rack
Main Main
Extension Extension
1U 1U
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
135 / 866
1U 1U [2]
136 / 866
Main Main
In 1+0 configuration
1U 1U
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

Main Main
1U 1U


Main Main
1U 1U
Fig. 44. Vertical installation in racks of 1+0 systems

Main Main
1U 1U
USER MANUAL
16 OUTDOOR UNIT INSTALLATION
This chapter gives whole information for installation of ODUs according to the envisaged system
configurations:
Subject On page
Warnings
Safety, EMC, EMF, and ESD norms
Tutorial information
138
P/Ns of installation materials
Installation near a wall
a) ODU types and ODU description 139
b) 1+0 ODU installation procedures full integrated antenna all frequencies
Typical installation layout 150
Suggested installation procedure 151
c) 1+0 ODU installation procedures not integrated antenna all frequencies
Suggested installation procedure 154
d) 1+1 ODU installation procedures full integrated antenna all frequencies
Suggested installation procedure for (choice):
1338 GHz 158
78 GHz 163
e) 1+1 ODU installation procedures not integrated antenna all frequencies
Suggested installation procedure for (choice):
1338 GHz 167
78 GHz 171
f) Installation procedures for Full Indoor ODU configurations (78 GHz) 175
g) Additional installation operations
These are subprocedures referenced to by the installation procedures stated above
ODU system grounding 181
Installing the Flextwist waveguide (not integrated antenna cases) 183
Aligning the antenna 185
Solar shield installation 186
N.B. for IDU / ODU cable installation, see Chapter 17 on page 189

3DB 16142 JAAA Ed.01 137 / 866
16.1 Warnings

16.1.1 Safety, EMC, EMF, and ESD norms

SAFETY RULES:
If not yet done, read chapter 12 from page 35 , and point iii on page 4 , which
describe the operations and/or precautions to be observed to safeguard operating
personnel during the working phases, and to guarantee equipment safety. Read them
with accuracy before to start every action on the equipment.
16.1.2 Tutorial information
If this is your first installation of 9400AWY Rel.2.1 ODUs, you are suggested to spend some time to read
tutorial information in para.16.2 on following pages 139 to 149 (various types of ODUs, operative
information, and labelling).
Moreover, if you need the description of ODUantenna configurations and relevant applications, refer to
para.21.2.4 on pages 372 375
16.1.3 P/Ns of installation materials
Refer to chapter 111 from page 249
16.1.4 Installation near a wall
In certain pole mounting installation circumstances, due to various reasons such as protrusions from the
wall, it might be useful to mount as shown below in order to easily install ODU module.
POLE
WALL
Fig. 45. Pole mounting near a wall

138 / 866 3DB 16142 JAAA Ed.01
16.2 ODU types and ODU description
This paragraph describes the types of ODUs, and relevant operative information for installation,
commissioning and maintenance purposes:

Subject On page
ODU mechanical design and identification 140
ODU operative information 142
Operative information on ODUs with embedded or external diplexer 142
Additional operative information on ODUs with external diplexer 145
Labels affixed on the ODU 148
For ODU functional description refer to point c ) on page 370
For the Light service kit cable, please refer to para.42.12 on page 720

3DB 16142 JAAA Ed.01 139 / 866
16.2.1 ODU mechanical design and identification

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

Two mechanical solutions are adopted:

one with embedded diplexer, shown in Fig. 46. below (relevant to ODU V1) and in Fig. 48. on page
141 (relevant to ODU V2), 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 external diplexer, shown in Fig. 47. below (relevant to ODU V1) , where ODU is
composed by two independent units: the BRANCHING assembly (containing the diplexer) and the
RF 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 RF TRANSCEIVER
assembly. To read the BRANCHING assembly identification label it is necessary to separate the
BRANCHING assembly from the RF TRANSCEIVER assembly.
TRANSCEIVER + BRANCHING ODU IDENTIFICATION LABEL

(see Fig. 54. on page 148)
Fig. 46. Views of ODU V1 with embedded diplexer
TRANSCEIVER BRANCHING
IDENTIFICATION LABEL IDENTIFICATION LABEL
(see Fig. 54. on page 148) (INSIDE)
(see Fig. 55. on page 149)
Fig. 47. Views of ODU V1 with external diplexer

140 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
Fig. 48. Views of ODU V2 with embedded diplexer
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
141 / 866
16.2.2 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 145
16.2.2.1 Operative information on ODUs with embedded or external diplexer
16.2.2.1.1 General, views and access points
Fig. 49. (for ODUs with embedded diplexer) and Fig. 50. (for ODUs with external diplexer) on pages 143
144 show ODU views and access points.
The external interfaces are listed in Tab. 4. below, with the corresponding connector.
Tab. 4. ODU external interfaces

Ref. in
Further
Fig. 49. Interface Connector
information
and Fig. 50.
Tab. 5.
(1) RF interface for connection of antenna or coupler waveguide
herebelow
(2) Connector for IDU/ODU cable male N 50 ohm
para.42.12
(3) Connector for Light service kit cable 12pin LEMO
on page 720
Tab. 5. RF interface
FREQUENCY GHz 78 1315 1825 38
Waveguide type WR112 WR62 WR42 WR28
N.B. For detailed operative information regarding:
equipment commissioning, please refer to chapter 42 on page 675
equipment maintenance, please refer to section 5 on page 737

142 / 866 3DB 16142 JAAA Ed.01
(4)
TRANSCEIVER
+
BRANCHING
SOLAR SHIELD
ODU V1 ODU V2
(A)
(1)
(A)
(A)
(A)
(A)
(A)
(A)
(2) (A)
(3) (2) (3)
(A) Locking hooks (4) to fix/unfix ODU assembly to antenna or coupler
(1) RF interface for connection of antenna or coupler
WARNING: a waterproofness tape is glued on the waveguide of the ODU. It must never be
removed.
(2) N Connector for IDU/ODU cable
(3) Connector for Light service kit cable (see Fig. 403. on page 720 )
(4) ODU identification label (see Fig. 54. on page 148 )
Fig. 49. Views of ODU with embedded diplexer
NOTE FOR CONNECTORS ON ODU V1 / V2

As shown in Fig. 49. above, the position of the N connector (for IDUODU cable insertion), and
of the connector for Light service kit cable in ODU V2 is opposite with respect to ODU V1.
In any case, this N connector is always positioned on the 450 side of ODU assembly.

3DB 16142 JAAA Ed.01 143 / 866
BRANCHING
(4)
TRANSCEIVER
SOLAR SHIELD
ODU V1 ODU V2
(B) (A) (A)
(B)
(1)
(B) (B)
(A) (A)
(A)
(B)
(B)
(A)
(A)
(A) (B)
(3) (B) (3)
(2) (2)
(A) 4 locking hooks to fix/unfix branching assembly (diplexer) to transceiver

(B) 4 locking hooks to fix/unfix branching assembly (diplexer) to antenna or coupler
(1) RF interface for connection of antenna or coupler
WARNING: a waterproofness tape is glued on the waveguide of the ODU. It must never be
removed.
(2) N Connector for IDU/ODU cable
(3) Connector for Light service kit cable (see Fig. 403. on page 720 )
(4) TRANSCEIVER identification label (see Fig. 54. on page 148 )
Fig. 50. Views of ODU with external diplexer
NOTE FOR CONNECTORS ON ODU V1 / V2

As shown in Fig. 50. above, the position of the N connector (for IDUODU cable insertion), and
of the connector for Light service kit cable in ODU V2 is opposite with respect to ODU V1.
In any case, this N connector is always positioned on the 450 side of ODU assembly.

144 / 866 3DB 16142 JAAA Ed.01
16.2.2.2 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. 55. on page 149) can be viewed only separating the TRANSCEIVER from the
BRANCHING.
16.2.2.3 Additional operative information on ODUs with external diplexer
16.2.2.3.1 ODU composition
As shown in Fig. 51. 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).
TRANSCEIVER
ORING
BRANCHING
Fig. 51. 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. 50. on page
144.

3DB 16142 JAAA Ed.01 145 / 866
16.2.2.3.2 TRANSCEIVER and BRANCHING boxes coupling

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

(A) BRANCHING box label informative content
described in Fig. 55. on page 149
(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. 55. on page 149); 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. 55. on page 149); obviously the RX part of the transceiver uses the
corresponding HIGH frequency range.
(D)
(A) (B)
(C)
(E)
Fig. 52. ODUs TRANSCEIVER and BRANCHING boxes coupling surfaces

146 / 866 3DB 16142 JAAA Ed.01
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. 53. 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. 53. 78 GHz ODUs BRANCHING box mistakeproofing

3DB 16142 JAAA Ed.01 147 / 866
16.2.3 Labels affixed on the ODU

a) the label depicted in Fig. 54. below is affixed externally to all types of ODU and ODUs

TRANSCEIVER boxes (see Fig. 49. on page 143 and Fig. 50. on page 144 ):

b) only for ODUs with external diplexers, an additional label, depicted in Fig. 55. on page 149 , is
placed on the branching assembly (see Fig. 52. on page 146 and Fig. 55. on page 149 ).
this label is just an example

A9400 Equipment Acronym & AlcatelLucent Logo
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
B 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
C Factory P/N + ICS bar code 128
Fig. 54. Label affixed on the ODU and ODUs TRANSCEIVER box

148 / 866 3DB 16142 JAAA Ed.01
3DB 06775 AAAA 01 A

3DB 06775 AAXX B
C
154_B LOW 7442 7526

HIGH 7596 7680
160 LOW 7442.5 7512.5 D
HIGH 7602.5 7673.5

A9400 Equipment Acronym & AlcatelLucent Logo
12345 (example) Notified body
PN/ICS 3DB 06775 AAAA 01 (example) Factory Technical Code + ICS
A Factory Technical Code + ICS, bar code 128
Logistical Item 3DB 06775 AAXX (example) Logistical Item for Customer
B Logistical Item for Customer, bar code 128
S/N CW 050609001 (example) Factory Serial number
C Factory Serial number bar code 128
the field Shifter MHz indicates the possible
frequency bands that can be used with this
branching assembly.
The choice between different shifters is done by
Craft Terminal (refer to point [3] on page 577 for
details).
D (shown numbers as examples)
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.16.2.2.3.2 on page
146
Fig. 55. Label affixed inside the ODU BRANCHING box

3DB 16142 JAAA Ed.01 149 / 866
16.3 1+0 ODU installation (full integrated antenna) all frequencies
16.3.1 Typical installation layout of 1+0 ODU full integrated antenna

TYPE N
CONNECTOR
IDUODU CABLE
POLE
ODU SYSTEM GROUNDING KIT

See NOTE A
Cable ties
IDUODU CABLE GROUNDING KIT

See NOTE C See NOTE B
INDOOR UNIT
Rear side
GROUNDING
Rack, TRU and IDU shelf
See NOTE C
See NOTE C
Fig. 56. Typical installation layout of 1+0 ODU full integrated antenna
NOTE A: ODU SYSTEM GROUNDING KIT (see para.16.8 on page 181 )
1 ) The grounding cable is fixed along the supporting pipe or pole by the normal methods (cable
ties are supplied in the optional consumables kit)
2 ) The grounding cable is connected to the ODU grounding point
NOTE B : IDUODU cable grounding Kit (see step [4] on page 191 )
first in proximity of ODU
second in proximity of building access
in case of cable length over 80 m, the cable grounding kit must be implemented every 40 meter cable
distance.
NOTE C: IDU SYSTEM GROUNDING
For grounding at IDU level, refer to Chapter 13 on pages 55 and 57 58 (installation in rack or
on the wall), Chapter 14 on page 62 (TRU), and Chapter 15 on page 80 (IDU shelf).

150 / 866 3DB 16142 JAAA Ed.01
16.3.2 Suggested installation procedure of 1+0 ODU full integrated antenna
[1] Check/Set the coupling between the TRANSCEIVER and BRANCHING boxes (only for ODU
with external diplexer)

Making reference to para.16.2.2.3.2 on page 146 , set coupling according to the plant
documentation
[2] Install the Antenna and Pole Mounting

This pole mounting is delivered as pole mounting, antenna, and frequencyspecific nose
adapter already assembled. The full integrated antenna is mounted on the pole front.
Antenna and pole mounting must be installed in accordance with the manufacturers instructions.
N.B. Example figures below show pole mountings with ODU already mounted.
RFS Pole mounting (2ft) ANDREW Pole mounting (2ft)
[3] Check or change the polarization on the Antenna nose

To change the polarization, follow the instructions supplied with each antenna. Fig. 57. below shows
an example.
N.B. The antennas are normally supplied with vertical polarization.
Fig. 57. Example of antenna polarization change (1+0 ODU full integrated antenna)

3DB 16142 JAAA Ed.01 151 / 866
[4] Take off the solar shield from the ODU transceiver by unscrewing the two screws placed on the
solar shield back panel

[5] Install the ODU on Antennas nose adapter

N.B. Before to insert the ODU on nose adapter, it is mandatory to put SILICONE grease
on the Oring.
Silicone grease
Fig. 58. Putting silicone grease on Oring before ODU insertion
1) Grasp the ODU module by the handle

2) Open the four looking hooks (1) arranged on the four walls of the ODU unit
3) Rotate the ODU depending to horizontal or vertical polarization, and slide it on the nose adapter
4) Secure the ODU module through the four hooks (1) on the relative brackets (2)
(2) Brackets
(1) Hook
Fig. 59. ODU 1+0 installation for Full Integrated antenna
REMINDER: The ODU/antenna assembly requires no additional seal on the SHF flanges; the two
ends are smooth. The Oring seal around the male nose provides sealing.
[6] Ground the ODU system (see para.16.8 on page 181 )
[7] Prepoint the antenna (see para.16.10.1 on page 185 )
[8] Reinstall the solar shield onto the ODU transceiver by screwing on it the two solar shield screws:
[9] Affix the EMF stickers (see para.12.3.7.2 on page 43 )
End of 1+0 ODU installation procedure (full integrated antenna)

152 / 866 3DB 16142 JAAA Ed.01
16.4 1+0 ODU installation with non integrated antenna all frequencies
16.4.1 Typical installation layout of 1+0 ODU Non integrated antenna
N.B. Not in all 1+0 configuration the external coupler is used. In 1+1HSBSD the coupler is not used,
in this case it is necessary to use the same Flex twist used in 1+0, that is the 1AF119977AAAA
TYPE N
CONNECTORS

See NOTE A
IDUODU CABLE GROUNDING KIT

See NOTE C See NOTE B

See NOTE C
See NOTE C
Fig. 60. Typical installation layout of 1+0 ODU Non integrated antenna
1) The grounding cable is fixed along the supporting pipe or pole by the normal methods (cable
2 ) The grounding cable is connected to the ODU grounding point
NOTE B: IDUODU cable grounding Kit (see step [4] on page 191 )
distance.

3DB 16142 JAAA Ed.01 153 / 866
16.4.2 Suggested installation procedure of 1+0 ODU not integrated antenna

[1] Check/Set the coupling between the TRANSCEIVER and BRANCHING boxes (only for ODU


documentation
[2] Install the Nose Adapter on the Pole Mounting for not integrated antenna
According to the NON INTEGRATED ANTENNA Pole Mounting used, refer to Fig. 140. on page
284 , or to Fig. 142. on page 286
[3] Install the Pole Mounting for not integrated antenna
Pole mounting must be installed in accordance with the manufacturers instructions.
In case of missing instructions, fix the Ubolts with 34 N x m tightening torque.
N.B. Pole mounting can be installed on the Right or Left hand side of the pole.
Ubolts
Ubolts
Fig. 61. Not integrated antenna pole mounting installation

[4] Take off the solar shield from the ODU transceiver by unscrewing the two screws placed on the
[5] Install the ODU
N.B. Before to insert the ODU on nose adapter, it is mandatory to put SILICONE grease
on the Oring.
Silicone grease
Fig. 62. Putting silicone grease on Oring before ODU insertion
For NON INTEGRATED ANTENNA Pole Mounting:

P/N 3DB10137AAAA, refer to Fig. 63. on page 155
P/N 3DB10137AAAB, refer to Fig. 64. on page 155
1 ) Grasp the ODU module by the handle. Open the four looking hooks arranged on the four walls
of the ODU unit
2 ) Position the Pole mounting support on the pole side as shown in the plant documentation
3 ) Position the ODU for desired polarization (horizontal or vertical), and slide it on the nose adapter
4 ) Secure the ODU module through the four hooks onto the relative brackets

154 / 866 3DB 16142 JAAA Ed.01
WARNING: as shown in Fig. 63. on page 155 , on each arm of the pole mounting P/N
3DB10137AAAA there are two grooves (the inner and the outer): it is mandatory to fix the four
looking hooks to the inner grooves (if you use the outer grooves, you could not be able to
unlock and extract the hooks)

REMINDER: The ODU/antenna assembly requires no additional seal on the SHF flanges; the
two ends are smooth. The Oring seal around the male noses provides sealing.
DO NOT USE THIS GROOVE !
Fig. 63. ODU 1+0 installation for not integrated antenna (with pole mounting P/N 3DB10137AAAA)
Fig. 64. ODU 1+0 installation for not integrated antenna (with pole mounting P/N 3DB10137AAAB)

3DB 16142 JAAA Ed.01 155 / 866
[6] Install the external Antenna with its own Pole Mounting
The installation of the antenna and of its own pole mounting, as well as the antenna polarization

check/change, must be done in accordance with the manufacturers instructions.

[7] Connect the antenna side (flange) of the Pole Mountings nose adapter to the external
antenna, by means of the Flextwist waveguide
Refer to para.16.9 on page 183
[10] Reinstall the solar shield onto the ODU transceiver by screwing on it the two solar shield screws:
End of 1+0 ODU installation procedure (not integrated antenna)

156 / 866 3DB 16142 JAAA Ed.01
16.5 1+1 ODU installation (full integrated antenna, all frequencies)
16.5.1 Typical installation layout of 1+1 ODU full integrated antenna
TYPE N CONNECTORS

See NOTE A
See NOTE C IDUODU CABLE GROUNDING KIT

See NOTE B

See NOTE C
See NOTE C
Fig. 65. Typical installation layout of 1+1 ODU full integrated antenna (all frequencies)

1) The grounding cables are fixed along the supporting pipe or pole by the normal methods (cable
2 ) The 2 grounding cables are connected to the grounding point of each ODU
distance.

3DB 16142 JAAA Ed.01 157 / 866
16.5.2 Suggested installation procedure of 1+1 ODU full integrated antenna (1338 GHz)

[1] Check/Set the coupling between the TRANSCEIVER and BRANCHING boxes (only for ODUs


documentation

[3] Check or change the polarization of the RF coupler

The axial adaptation between H polarization to V polarization (and viceversa) is a
mechanical/electrical adjustment. Every mechanical STEP is a 30 adjustment.
2nd Step
1st Step
Fig. 66. Coupler Polarization Change (1338 GHz) 1st Step and 2nd step
The final result must be as shown in Fig. 69. on page 159 (example for V polarization): the
engraved polarization symbols (H or V) must coincide with the reference blind hole.
Change Polarization Procedure
1) 1st Step = internal 30 rotate
Coupler body
1st Step
Rotate 30
Fig. 67. Coupler Polarization Change (1338 GHz) 1st Step execution

158 / 866 3DB 16142 JAAA Ed.01
2) 2nd Step= cover + screws 60( 30+ 30) rotate
Coupler body
2st Step
Rotate 60
Fig. 68. Coupler Polarization Change (1338 GHz) 2nd Step execution
The spigot in the full Integrated Antenna configuration is 30 and complete the change of
polarization (90).
engraved
reference polarization
blind hole symbols
(H and V)
note: shown example is for V polarization

Fig. 69. Coupler Polarization Change (1338 GHz) Screws fixing

3DB 16142 JAAA Ed.01 159 / 866
[4] Install the RF coupler on antennas nose adapter
N.B. Before to insert the RF coupler on antennas nose adapter, it is mandatory to put

SILICONE grease on the Oring.

Silicone grease
Fig. 70. Putting silicone grease on Oring before RF coupler insertion (1338 GHz)
Grasp the coupler by the handle. Fasten the coupler to the support through the four locking hooks
that will be tightened onto the relative fastening brackets on the radio support.
The label corresponds to the side of the pole
ENGRAVED
INDICATION
Fig. 71. Installing the RF coupler to the radio support (1338 GHz)
PIPE
WARNING: verify that the indication , engraved on the coupler, is directed toward the
side pole:
PIPE
(side pole) PIPE

160 / 866 3DB 16142 JAAA Ed.01
[5] For each ODU transceiver, take off the solar shield by unscrewing the two screws placed on the
[6] Install the ODU transceivers on the RF coupler

N.B. Before to insert each ODU on RF couplers nose adapters, it is mandatory to put
SILICONE grease on the Orings.
Silicone grease
Fig. 72. Putting silicone grease on RF couplers Oring before ODU insertion (1338 GHz)
Grasp each ODU by the handle. Fasten the ODU module to the support through the locking hooks
that will be tightened onto the relative fastening bracket on the coupler.
Fastening
Locking
brackets
hooks
Fig. 73. Installing the ODU 1+1 on the RF coupler for full Integrated antenna (1338 GHz)

3DB 16142 JAAA Ed.01 161 / 866
Fig. 74. below shows the final result, and indicates which ODU must be respectively connected to
the IDU MAIN and EXTENSION units, as described in Chapter 17 from page 189

ODU
to be connected
to IDU MAIN unit
ODU
to be connected
to IDU EXTENSION unit
RF coupler
Fig. 74. Views of ODU 1+1 Full integrated antenna after installation (1338 GHz)
[9] Reinstall the solar shield onto each ODU transceiver by screwing on it the two solar shield
screws: see para.16.11 on page 186
End of 1+1 ODU full integrated antenna installation procedure (1338 GHz)

162 / 866 3DB 16142 JAAA Ed.01
16.5.3 Suggested installation procedure of 1+1 ODU full integrated antenna (78 GHz)

documentation

[3] Check or change the polarization of the RF coupler

a) Vertical Polarization to Horizontal Polarization
The point of reference is on the position V (Vertical Polarization).
To change the polarization, perform the following operations:
1 ) unscrew the three screws
2 ) turn the thin twist and to make to coincide the position H to the point of reference A
3 ) screw the screws
b) Horizontal Polarization to Vertical Polarization
The point of reference is on the position H (Horizontal Polarization).
To change the polarization, perform the following operations:
1 ) unscrew the three screws
2 ) turn the thin twist and to make to coincide the position H to the point of reference A
3 ) screw the screws
Detail B Point of Detail A

Point of
reference Screw reference
A A
Screw
TWIST
See Detail B See Detail A
Fig. 75. Coupler Polarization Change (78 GHz)

3DB 16142 JAAA Ed.01 163 / 866
[4] Install the RF coupler on antennas nose adapter
N.B. Before to insert the RF coupler on antennas nose adapter, it is mandatory to put

SILICONE grease on the Oring.

that will be tightened onto the relative fastening brackets on the radio support .
The label corresponds to the side of the pole
Locking
hook
Silicon
grease
Fastening
bracket
MAIN
ACCESS
Fig. 76. Installing the RF coupler to the radio support (78 GHz)

Silicone grease
Fig. 77. Putting silicone grease on Oring before ODU insertion (78 GHz)

164 / 866 3DB 16142 JAAA Ed.01
Grasp the ODU transceiver by the handle, and fasten it to the coupler support through the four locking
hooks that will be tightened onto the relative fastening brackets on coupler.
Locking
hook
Fastening
bracket
ODU
to be connected
ODU
to be connected
to IDU MAIN unit
RF coupler
Fig. 78. Installing the ODU 1+1 on the RF coupler for full Integrated antenna (78 GHz)
End of 1+1 ODU full integrated antenna installation procedure (78 GHz)

3DB 16142 JAAA Ed.01 165 / 866
16.6 1+1 ODU installation with not integrated antenna all frequencies
16.6.1 Typical installation layout of 1+1 ODU Non integrated antenna

ODU SYSTEM
GROUNDING KIT
See NOTE A IDUODU CABLE GROUNDING KIT
See NOTE B
See NOTE C

See NOTE C
See NOTE C
Fig. 79. Typical installation layout of 1+1 ODU Non integrated antenna (all frequencies)

1 ) The grounding cables are fixed along the supporting pipe or pole by the normal methods (cable
2 ) The 2 grounding cables are connected to the grounding point of each ODU
distance.

166 / 866 3DB 16142 JAAA Ed.01
16.6.2 Suggested installation procedure of 1+1 ODU not integrated antenna (1338 GHz)

documentation
[2] Install the Nose Adapter on the not integrated antenna Pole Mounting for ODU
284 , or to Fig. 142. on page 286
[3] Install the not integrated antenna Pole Mounting for ODU
Ubolts
Ubolts
[4] Install the RF coupler on the nose adapter

N.B. Before to insert the RF coupler on nose adapter, it is mandatory to put SILICONE
grease on the Oring.
Silicone grease
Fig. 81. Putting silicone grease on Oring before RF coupler insertion

that will be tightened onto the relative fastening brackets on the Pole Mounting.
looking hooks to the inner grooves (if you use the outer grooves, you could not be able to unlock
and extract the hooks)

3DB 16142 JAAA Ed.01 167 / 866
DO NOT USE THIS GROOVE !
Fig. 82. 1338 GHz RF coupler installation for not integrated antenna (pole mounting P/N
3DB10137AAAA)
Fig. 83. 1338 GHz RF coupler installation for not integrated antenna (with pole mounting P/N
3DB10137AAAB)

168 / 866 3DB 16142 JAAA Ed.01

Silicone grease
Fig. 84. Putting silicone grease on RF couplers Oring before ODU insertion (1338 GHz)
Grasp each ODU by the handle. Fasten the ODU module to the support through the locking hooks
that will be tightened onto the relative fastening bracket on the coupler.
RF coupler
Fastening bracket
Pole mounting
on the coupler
(not integrated
antenna)
ODU
ODU to be connected
to be connected to IDU MAIN unit
Fig. 85. Installation of ODU 1+1 not integrated antenna (1338 GHz)

3DB 16142 JAAA Ed.01 169 / 866


[8] Connect the antenna side (flange) of the ODU Pole Mountings nose adapter to the external
End of 1+1 ODU not integrated antenna installation procedure (1338 GHz)

170 / 866 3DB 16142 JAAA Ed.01
16.6.3 Suggested installation procedure of 1+1 ODU not integrated antenna (78 GHz)

documentation
[2] Install the Nose Adapter on the not integrated antenna Pole Mounting for ODU
284 , or to Fig. 142. on page 286
[3] Install the not integrated antenna Pole Mounting for ODU
Ubolts
Ubolts
[4] Install the RF coupler on the nose adapter

N.B. Before to insert the RF coupler on nose adapter, it is mandatory to put SILICONE
grease on the Oring.
Silicone grease
Fig. 87. Putting silicone grease on Oring before RF coupler insertion

that will be tightened onto the relative fastening brackets on the Pole Mounting.
looking hooks to the inner grooves (if you use the outer grooves, you could not be able to unlock
and extract the hooks)

3DB 16142 JAAA Ed.01 171 / 866
DO NOT USE
THIS GROOVE !
3DB10137AAAA)
3DB10137AAAB)

172 / 866 3DB 16142 JAAA Ed.01

Silicone grease
Silicone grease
Fig. 90. Putting silicone grease on Oring before ODU insertion (78 GHz)
Grasp the ODU transceiver by the handle, and fasten it to the coupler support through the four locking
hooks that will be tightened onto the relative fastening brackets on coupler.
Locking
hook
Fastening
bracket
Fig. 91. Installing the ODU 1+1 on the RF coupler (for not Integrated antenna 78 GHz)

3DB 16142 JAAA Ed.01 173 / 866

ODU ODU

to be connected to be connected
to IDU EXTENSION unit RF coupler to IDU MAIN unit
Pole mounting
(not integrated
antenna)
RF coupler
ODU
to be connected
Pole mounting
(not integrated
ODU antenna)
to be connected
to IDU MAIN unit
Fig. 92. ODU 1+1 installed on the RF coupler (for not Integrated antenna 78 GHz)
[8] Connect the antenna side (flange) of the ODU Pole Mountings nose adapter to the external
End of 1+1 ODU not integrated antenna installation procedure (78 GHz)

174 / 866 3DB 16142 JAAA Ed.01
16.7 Full Indoor ODU configurations (78 GHz)
The Full Indoor ODU configurations presently available are for 7 8 GHz, and are depicted in following
Fig. 93.
2 x (1+1) ODU 1 x (1+1) ODU 2 x (1+0) ODU
Pressure window/inlet
1U UBR84 1U UBR84 1U UBR84
3U 3U 3U
14U
27U 24U
Front view
7U
7U
5U
4U
7U
4U 5U
3U 3U 3U
Fig. 93. 7 8 GHz Full Indoor ODU configurations
The UBR84 pressure window/inlet is connected to the antenna feeder by means of flex wave guide.
The Full Indoor ODU installation is done with the use of specific mounting kits:
Configuration on page
7 8 GHz Full Indoor ODU installation in LABORACK
176
High/Low mount
Kit for low mount 177
Kit for high mount 179

3DB 16142 JAAA Ed.01 175 / 866
16.7.1 7 8 GHz Full Indoor ODU configuration for installation in LABORACK

HIGH MOUNT
LOW MOUNT
Fig. 94. 7 8 GHz Full Indoor ODU configuration for installation in LABORACK (High/Low mount)

176 / 866 3DB 16142 JAAA Ed.01
[1] Kit for low mount
N.B. Waveguide type WR112 with flange type UBR84
Fig. 95. Low mount kit drawing for 7 8 GHz Full Indoor ODU installation in LABORACK

3DB 16142 JAAA Ed.01 177 / 866
Tab. 6. Low mount kit part list for 7 8 GHz Full Indoor ODU installation in LABORACK

REF

ALCATELLUCENT CODE DESCRIPTION Q.TY

Fig. 95.
3CC52135AAAA Support 1 1
3CC58038AAAA Bracket 2 2
1AD009150040 Screw M10X20 4 5
1AD001970097 NUT M10*8.00MM 4 6
Washer plain
1AD00870180 4 7
10.5mmx21mmx2mm/M10
1AD00915001 Screw M6X12mm 10 8
Washer plain
1AD00870136 10 9
6.4mmx12.5mmx1.6mm/M6
1AD002920002 NUT M6*9.5MM 10 10
3CC58037AAAA Double bend e plane 1 11
1AD009150010 Screw M4 4 12
Washer plain
1AD000870153 4 13
4.3mm x 8mm x 800mm/M4
3DB02438AAAA block 1 14

178 / 866 3DB 16142 JAAA Ed.01
[2] Kit for high mount
N.B. Waveguide type WR112 with flange type UBR84
Fig. 96. High mount kit drawing for 7 8 GHz Full Indoor ODU installation in LABORACK

3DB 16142 JAAA Ed.01 179 / 866
Tab. 7. Low mount kit part list for 7 8 GHz Full Indoor ODU installation in LABORACK

REF

ALCATELLUCENT CODE DESCRIPTION Q.TY

Fig. 96.
3CC52135AAAA Support 1 1
1AD009150040 Screw M10X20 4 5
1AD001970097 NUT M10*8.00MM 4 6
Washer plain
1AD00870180 4 7
10.5mmx21mmx2mm/M10
1AD00915001 Screw M6X12mm 10 8
Washer plain
1AD00870136 10 9
6.4mmx12.5mmx1.6mm/M6
1AD002920002 NUT M6*9.5MM 10 10
3CC58036AAA Double bend e plane 1 11
1AD009150010 Screw M4 4 12
Washer plain
1AD000870153 4 13
4.3mm x 8mm x 800 mm/M4
3DB02438AAAA Bock 1 14

180 / 866 3DB 16142 JAAA Ed.01
16.8 ODU system grounding
Each ODU transceiver must be individually grounded.

N.B. neither the RF coupler, nor the antenna(s), integrated or not integrated, must be grounded.
The grounding of ODU transceivers is shown in the following typical installation layouts:
ODU system antenna typical installation layout
full integrated Fig. 56. on page 150

1+0 ODU
not integrated Fig. 60. on page 153

1+1 ODU
The following items are necessary for the individual grounding of each ODU transceiver:
one ODU Grounding Kit (P/N 3CC08166AAAA ).

This kit corresponds to a cable (16mm2 L=15m) that must be cut on site and connected to the terminal
provided on the ODU transceiver, and, on the other side, to the nearest grounding plate.
one Common kit V2 (P/N 3DB21042AAAB ).

This kit includes, besides other mechanical elements, those necessary for fixing the ODU grounding
cable (lugs, screws, washers, etc.)
N.B. these two kits are present in the ODU installation components tables on pages 251 to 257
This example figure shows the grounding cable connected on a 1+0 ODU:
ODU grounding cable to be

connected to the nearest
grounding plate

3DB 16142 JAAA Ed.01 181 / 866
This other example figure shows the grounding cables connected on a 1+1 ODU 1338 GHz:

Grounding cable Grounding cable
for 1st ODU for 2nd ODU
ODU grounding cables to be connected to the nearest grounding plate
Connect all grounding cables to the nearest grounding plate, as shown in this example:
[1]

182 / 866 3DB 16142 JAAA Ed.01
16.9 Installing the Flextwist waveguide (not integrated antenna cases)
Concerning the interface between the ODU output flange and the suggested antenna flange, the following
Tab. 8. details for each product the standard wave guide to be used and the suggested flange for the
external antenna.
Please note that the use of 600 mm flex twist is not suggested for antennas bigger than 3ft (90 cm
diameter), due to mechanical reasons. The suggested way to make the RF connection is to use the
elliptical wave guide fitted with flanged connectors.
Tab. 8. ODU Output flanges with external antenna

Equipment Suggested
ODU Output
and Range FLEXTWIST Antenna
Flange
(GHz) Flange
A C.E.I. E.I.A. B C D
UDR84 R84 WR112 PDR84 UBR84 PBR84

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

L=600 mm for 1338 GHz

3DB 16142 JAAA Ed.01 183 / 866
The long twistable flexible waveguide is supplied complete with gaskets and fasteners. At one end, it has
a smooth square or rectangular flange (to be mounted on the antenna) and at the other end, a grooved

square flange designed to accommodate an Oring seal (mounted at the ODU end).

Tab. 9. 7/8GHz Flextwist waveguide
FLEXIBLE TWISTABLE WAVEGUIDE KIT
Stainless Stainless
Onduflex
Freq. steel steel Stainless HM.
Length springy
Alcatel code Waveguide Band Flanges socket socket Z. flat Hex
mm. crinkle
GHz. cap cap washers nuts
washers
screws screws
12 8 12
1AF11977AAXX WR112 1.000 7,05 10 PDR84 UBR84 12 (B4) 12 (Z4)
(M4x25) (M4x20) (HM4)
3CC08010ABAB 8 8
WR112 1.000 7,05 10 PBR84 UBR84 8 (B4) 8 (Z4) 8 (HM4)
(Note A) (M4x25) (M4x12)
Note A: next introduction in substitution of 1AF11977AAXX
Tab. 10. 13/38GHz Flextwist waveguide
FLEXIBLE TWISTABLE WAVEGUIDE KIT
Stainless Stainless
Onduflex
Freq. steel steel Stainless HM.
Length springy
Alcatel code Waveguide Band Flanges socket socket Z. flat Hex
mm. crinkle
GHz. cap cap washers nuts
washers
screws screws
8 8 12
3CC05751ACAA WR75 600 10 15,0 PBR120 UBR120 8 (B4) 12 (Z4)
(M4x20) (M4x12) (HM4)
8 8
3CC05750ACAA WR62 600 12,4 18 PBR140 UBR140 8 (B4) 8 (Z4) 8 (HM4)
(M4x20) (M4x12)
8 8
3CC05749ACAA WR42 600 18 26,5 PBR220 UBR220 8 (B3) 8 (Z3) 8 (HM3)
(M3x20) (M3x12)
8 8
3DB00682AAAA WR28 600 26,5 40 PBR320 UBR320 8 (B3) 8 (Z3) 8 (HM3)
(M3x20) (M3x12)
N.B. If the FLEXTWIST is not provided by Alcatel, 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

184 / 866 3DB 16142 JAAA Ed.01
16.10 Aligning the antenna
16.10.1 Antenna prepointing

Antenna prepointing alignment involves adjusting the direction of each antenna toward the other antenna
of the radio link.
First horizontal prepointing (azimuth)

Horizontally place the antenna according to the direction set down in the plant documents where,
among the various indication are indicated those concerning the reference points (Position of the
tower or of the building with respect to true north) in order to point the antenna in the set direction.
There are various procedures and technical means to adopt in order to mechanically prepoint the
antenna, and they can be implemented in various ways according to the various configurations and
to the various system conditions.
The standard instrumentation is the compass.
Second vertical prepointing (zenith)

Place the antenna vertically nearest to its operating angle.
The technical and operative procedure adopted to vertically point the antenna is as that previously
implemented to horizontally prepoint.
In configurations with two antennas, repeat the procedure for the second antenna.
Notes:
a) At the end of the prepointing operation, slowly block all the horizontal and vertical regulating system
of the antenna taking care not to modify dish direction
b) Final antenna pointing (or connection) shall be established only after all the Antenna and ODU
system is fully installed.
c) After the fine pointing TIGHTENING TORQUE FOR THE SCREWS OF M10 IS OF 30Nm
16.10.2 Fine antenna alignment
Fine antenna alignment involves adjusting the direction of each antenna until the received signal strength
its maximum level at each and of the link.
The antenna fine alignment is performed in the commissioning phase: refer to para.42.11 on page 719

3DB 16142 JAAA Ed.01 185 / 866
16.11 Solar shield installation

One solar shield (P/N 3CC13476AAAA) is automatically delivered with each supplied ODU.

Figure Fig. 97. below shows the solar shield mounting.
The ARROW shows the polarization.
Solar shield
Screw
ODU
H
H
V
V
Screw
Polarization V Polarization H
Fig. 97. Solar shield installation
In vertical or horizontal polarization, the solar shield remains fixed in the same position and the ODU is
the only part which can rotate 90 degrees when changing the polarization.
N.B. Solar shield has to be installed only after ODU installation.
Fig. 98. on page 187 shows views of installed ODU solar shields.

186 / 866 3DB 16142 JAAA Ed.01
1+0 ODU solar shield view 1+1 ODU solar shields view (13 to 38GHz)
1+1 ODU solar shields view (78GHz)
Fig. 98. ODU solar shields views

3DB 16142 JAAA Ed.01 187 / 866
188 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
17 IDUODU CABLE INSTALLATION MATERIAL AND INSTALLATION
PROCEDURE
Subject On page
Installation components for IDUODU cable below
Suggested IDUODU cable installation procedure 190
17.1 Installation components for IDUODU cable
17.1.1 Maximum length and cable types to use

Max length of IDU/ODU cable ..
.. for capacity .. for capacity Code of cable to use Description
v 16E1 17E1 B 32E1
250 m 150 m 1AC001100022 Coax cable 50 ohm 10.3 mm
120 m 80 m 1AC041350001 Coax cable 50 ohm 6.85 mm
WARNING: the equipment can work with capacity v 16E1 or 17E1 B 32E1. In case of initial
configuration at capacity v 16E1 and a successive extension to capacity 17E1 B 32E1,
the IDU/ODU cable length must be checked according to the above table.
17.1.2 Nconnector for IDU / ODU cable
Hereafter are reported the suggested AlcatelLucent connectors:

Cable Code Code of Connector
Connector Description
(para.17.1.1 above) to use
1AC001100022 1AB095530021 Connector male N 90 50 Ohm (diam. 10.3 mm)
1AC041350001 1AB095530037 Connector male N 90 50 Ohm (diam. 6.85 mm)
17.1.3 IDU / ODU cable grounding kit assembling

Cable Code Code of Grounding
Grounding kit Description
(para.17.1.1 above) kit to use
IDUODU cable grounding kit for coax cable 50 ohm
1AC001100022 1AB128500002
10.3 mm
IDUODU cable grounding kit for coax cable 50 ohm
1AC041350001 1AD040130004
6.85 mm

3DB 16142 JAAA Ed.01 189 / 866
17.2 Suggested IDUODU cable installation procedure

N.B. Quality of the preparation and of the installation is essential to guarantee electrical, mechanical

and waterproof performances.

SAFETY RULES:
If not yet done, read chapter 12 from page 35 , and carefully observe statements for
your safety
[1] Install the cable in the cable tray

Tighten the tie raps in
cross form
Cable must follow the structure with a

minimum curve radius of 1520 cm
[2] Install the cable in the feed thru plate
Internal view
N.B. Waterproof the cables at the entrance of the shelter

190 / 866 3DB 16142 JAAA Ed.01
[3] Mount the N connectors on the cable
Connector P/N as in para.17.1.2 on page 189
In order to assemble the connectors to the coaxial cable, refer to the leaflet enclosed into the supplied
connector bag.
The tightening torque on connector on the cable must be 2.5 Nm
[4] Ground the cable

Grounding kit P/N as in para.17.1.3 on page 189
Use the Blue label spacing
Remove the jacket
Metal contact
Install the
grounding kit

3DB 16142 JAAA Ed.01 191 / 866
Tighten with allen key
8 mm
Coaxial cable grounding kit

connection to the tower grounding
ATTENTION
As specified on pages 150 , 153 , 157 , and 166 :
a) two grounding kits at least must be installed:

first, in proximity of ODU (5m maximum)
second, in under feed thru flat of the building
b) in case of cable length over 80 m, the cable grounding kit must be implemented every 40
meter cable distance.

192 / 866 3DB 16142 JAAA Ed.01
[5] Label and connect the cable to the ODU
Labelling:
Example for cable connected to Example for cable connected to

IDU MAIN unit IDU EXTENSION unit
Link ID RF MAIN POL H or V Link ID RF EXTENSION POL H or V
Connection:
IDUODU cable
The tightening torque on Connector N (Male) on the ODU must

be 3 Nm
[6] Waterproof the connector on ODU
Surround the connector with the auto amalgamate tape

from up to down
Surround the connector with the adhesive tape

from up to down
Put tie raps on the up and the down of the connector

3DB 16142 JAAA Ed.01 193 / 866
[7] Label and connect the cable to the IDU

Labelling:

Example for cable connected to Example for cable connected to

IDU MAIN unit IDU EXTENSION unit
Link ID RF MAIN Link ID RF EXTENSION
Connection:
Before connecting the cable to IDU, verify that the IDU unit
(MAIN and EXTENSION, if present) is switched off
IDUODU Cable for IDU MAIN unit

IDUODU Cable for IDU EXTENSION unit
The tightening torque on Connector N (Male) on the IDU must

be 2 Nm
End of IDUODU cable installation procedure

194 / 866 3DB 16142 JAAA Ed.01
18 NETWORK INTERCONNECTIONS
This chapter:
gives the interconnection diagrams and the associated list of cables for network interconnections
regarding the NMS channel continuity, and the EOW audio continuity
and describes the E1 interconnections with the 9500MPRE Microwave Packet Radio MSS
equipment
Service
Protection
Subject On page
Box
usage
Introduction on NMS channel and EOW audio continuity 197
Solutions for NMS channel continuity between two colocated 9400AWY

197
R.2.1 NEs
Interconnections between a 9400AWY R.2.1 NE with other

197
AlcatelLucent colocated radio transmission NE types
9400AWY 9400AWY interconnections without the Service Protection

N 198
Box
NMS Continuity without the Service Protection Box, through OS Ethernet

N 198
ports and ALM_NMS connectors
NMS Continuity without the Service Protection Box, through OS Ethernet

N 204
port and Ethernet port (of Enhanced Ethernet plugin)
General on interconnections with the Service Protection Box Y 208
EOW audio continuity and EOW party line structure in 9400AWY R.2.1 Y 208
General on NMS channel and EOW audio continuity Y 209
NMS channel and EOW audio continuity with the Service Protection Box Y 210
Available supports for the Service Protection Box Y 212
9400AWY 9400AWY interconnections with the Service Protection

Y 213
Box
NMS Continuity with the Service Protection Box Y 213
AUDIO Connection Y 217
NMS Ring Protection with Audio Continuity Y 219
ESC Continuity Y 221

table continues

3DB 16142 JAAA Ed.01 195 / 866
Service
Protection

Subject On page
Box

usage
9400AWY MELODIE SNMP interconnections Y 222
NMS Continuity with Audio Connection Y 222
Service Channel Continuity (MELODIE 1+0 classic) Y 224
Service Channel Continuity (MELODIE 1+0 Light) Y 225
Service Channel Continuity (MELODIE 1+1) Y 226
Service Channel Continuity (MELODIE 1+1) Y 227
9400AWY MELODIE RQ2 interconnections Y 228
9400AWY NMS_V11 Transport (MELODIE 1+0 Classic) Y 228
9400AWY NMS_V11 Transport (MELODIE 1+0 Light) Y 230
9400AWY NMS_V11 Transport (MELODIE 1+1) Y 232
9400AWY NMS_V11 Transport (MELODIE 1+1) Y 234
RQ2 9.6 Kb/s Transport Y 236
E1 interconnections between 9400AWY and 9500MPRE MSS Y 237

196 / 866 3DB 16142 JAAA Ed.01
18.1 Introduction on NMS channel and EOW audio continuity
In this context, network interconnections are meant as those to allow the remote NE supervision (NMS
channel continuity), as well as the propagation of the EOW (EOW audio continuity).
Fig. 183. on page 413 shows an example of 9400AWY NEs remotely supervised by their Radio interface
and NMS rings and chains.
This chapter deals with the ways to create an interworking network based on different products and to
provide certificated solutions:
focusing on the available product interconnections for the following AlcatelLucentLucent wireless
transmission products:
9400AWY Rel.2.1
Melodie via SNMP or RQ2
integrating in a Telecommunication Management Network (TMN), which can be based on :
a remote Craft Terminal (via F or Ethernet connected);
the AlcatelLucent Network Management System 1352CM PC based where supported;
the AlcatelLucent Network Management System 1353NM WS based;
an external Operations System (OS) provided / developed by the customer.
18.1.1 Solutions for NMS channel continuity between two colocated 9400AWY R.2.1 NEs
Two solutions are possible to interconnect two colocated 9400AWY R.2.1 NEs: without or with the
Service Protection Box:
the solution without the Service Protection Box employes the direct interconnection through their
OS Ethernet ports or their ALM_NMS connectors by a special cable, as described in para.18.2 from
page 198
WARNING: when this interconnection is employed, the housekeeping signals cannot be

accessed on the IDU MAIN unit front panel (see signals HK_xx in Tab. 65. from page
311 )
with the Service Protection Box. In this case, refer to para.18.4 from page 213
18.1.2 Interconnections between a 9400AWY R.2.1 NE with other AlcatelLucent colocated

radio transmission NE types
For interconnections with:
Melodie equipment, the Service Protection Box is always required, as described in para.18.5 from
page 222 , and para.18.6 from page 228
9500MPRE equipment, the Service Protection Box is never used; the E1 signal interconnection,
if necessary, is described in para.18.7 on page 237 ; the NMS channel continuity must be done
connecting the 9400AWY R.2.1 NEs OS Ethernet port to the corresponding port of the 9500MPRE
equipment.

3DB 16142 JAAA Ed.01 197 / 866
18.2 9400AWY 9400AWY interconnections without the Service Protection
Box

18.2.1 NMS Continuity without the Service Protection Box, through OS Ethernet ports and

ALM_NMS connectors
WARNING 1: when this interconnection is employed, the housekeeping signals cannot be accessed on
the IDU MAIN unit front panel (see signals HK_xx in Tab. 65. from page 311 )
WARNING 2: cables are depicted schematically; for details on each cable (structure, connectors, and
pin connection tables) refer to chapter 113 from page 327
[1] Case 1: Management through OS port

Management
Cable B through OS port
Station A Cable A
Station B
Cable C
Cable A
Station C
For cables A:
Cable Code Cable Type From Equipment To Equipment
3CC52143ABAA
(1.6 m)
Sub.D 44 pins / First station Second station
or
Sub.D 44 pins (IDUMAIN) ALM_NMS (IDUMAIN) ALM_NMS
3CC52143ACAA
(6.4 m)
For cable B:
Station A OS (or ECT)
3CC52141Axxx RJ45 Eth Direct Customer
port
For cable C:
Station Bs OS(or ECT) Station Cs OS (or ECT)
3CC52142Axxx RJ45 Eth Cross
port port
Fig. 99. NMS Continuity without the Service Protection Box: case 1

198 / 866 3DB 16142 JAAA Ed.01
Software configuration procedure for case 1 ( Fig. 99. ):
1) Configure OS port on each stations ( Fig. 100. )

Enable all stations OS port and OSPF routing protocol.

N.B. The IP address and OSPF Area Point is just an example. Operator should follow IP
administration policy in each field.
Fig. 100. Configure OS port on each stations
2) Setup PPP link
Select V11 or G703
For station B, in the Mode combox, select DTE ( Fig. 101. ); For Station C, select
Codirectional ( Fig. 102. )
Enable OSPF routing protocol.
N.B. The OSPF area MUST be the same as OSPF area of OS port [ step 1 ) above]

3DB 16142 JAAA Ed.01 199 / 866
Fig. 101. Setup PPP link: DTE
Fig. 102. Setup PPP link: Codirectional

200 / 866 3DB 16142 JAAA Ed.01
[2] Case 2: Management through Microwave link
Management through
Microwave Link
Station A Cable A
Station B
Cable C
Cable A
Station C
For cables A:
3CC52143ABAA
(1.6 m)
Sub.D 44 pins / First station Second station
or
Sub.D 44 pins (IDUMAIN) ALM_NMS (IDUMAIN) ALM_NMS
3CC52143ACAA
(6.4 m)
For cable C:
Station Bs OS(or ECT) Station Cs OS (or ECT)
3CC52142Axxx RJ45 Eth Cross
port port
Fig. 103. NMS Continuity without the Service Protection Box: case 2

3DB 16142 JAAA Ed.01 201 / 866
Software configuration procedure for case 2 ( Fig. 103. ):

1) Configure OS port on each stations, except Station A ( Fig. 104. )

Enable all stations OS port and OSPF routing protocol.

Fig. 104. Configure OS port on each stations
2) Setup PPP link
Select V11 or G703
For station B, in the Mode combox, select DTE ( Fig. 105. ); For Station C, select
Codirectional ( Fig. 106. )
Enable OSPF routing protocol.
N.B. The OSPF area MUST be the same as OSPF area of OS port [ step 1 ) above]
N.B. The OSPF area MUST be the same as OSPF area of RF link.

202 / 866 3DB 16142 JAAA Ed.01
Fig. 105. Setup PPP link: DTE
Fig. 106. Setup PPP link: Codirectional

3DB 16142 JAAA Ed.01 203 / 866
18.2.2 NMS Continuity without the Service Protection Box, through OS Ethernet port and
Ethernet port (of Enhanced Ethernet plugin)

WARNING: the IDU must be equipped with the Enhanced Ethernet plugin, and the VLAN feature is

used
[1] Case 1: NMS continuity in backtoback

204 / 866 3DB 16142 JAAA Ed.01
Fig. 108. Case 1: VLAN configuration for NE A
b) At NE B ( Fig. 109. ):
1. The 2 Ethernet ports which connect to OS port, and NE Bs Ethernet port, must be the
members of a same VLAN.
2. The port which connect to OS port, must be untagged port of the VLAN.
3. In JUSM, Configuration > Network Configuration > Vlan configuration
Fig. 109. Case 1: VLAN configuration for NE B
N.B.
The VLAN ID of NE A and NE B can be the same or not the same.
It is recommended that NE A OS Ethernet IP address, PCs IP address, and NE B OS
Ethernet IP address are in the same subnetwork.

3DB 16142 JAAA Ed.01 205 / 866
[2] Case 2: NMS continuity through RF link

ODU ODU

CH1 CH1

all Ethernet cables
NE A
PC
NE B
Fig. 110. NMS continuity through RF link
In this case, NE A and NE B are not in the same station

We want to use CT to supervise NE A and NE B.
Cable connection ( Fig. 110. ):

NE A Ethernet port 33 connected to NE A OS port
The PC, running CT, connected to NE A Ethernet port 34
NE B Ethernet port 36 connected to NE B OS port
All cables are RJ45RJ45 Cat.5e Ethernet Direct cables (P/N 3CC52141Axxx, refer to
para.113.13.1 on page 113.13.1 for lengths).
N.B. this connection is an example. Operator can use any of the Ethernet ports.
VLAN software configuration procedure for case 2 ( Fig. 110. ):
N.B. The VLAN ID and VLAN names in Fig. 111. and Fig. 112. are examples. Operator should
follow IP administration policy in each field.
a) At NE A ( Fig. 111. ):
1. The 2 Ethernet ports which connect to OS port, Craft terminal, together with the radio
port, must be the members of a VLAN.
2. The port which connect to OS port, must be the members of untagged port of the VLAN.

206 / 866 3DB 16142 JAAA Ed.01
Fig. 111. Case 2: VLAN configuration for NE A
b) At NE B ( Fig. 112. ):
1. The Ethernet port connected to OS port, together with the radio port, must be the
members of a VLAN;
2. The port which connect to OS port, must be the members of untagged port of the VLAN.
Fig. 112. Case 2: VLAN configuration for NE B
N.B.
The VLAN ID of NE A and NE B must be the same.
It is recommended that NE A OS Ethernet IP address, PCs IP address, and NE B OS
Ethernet IP address are in the same subnetwork.

3DB 16142 JAAA Ed.01 207 / 866
18.3 General on interconnections with the Service Protection Box

These matters are taken into consideration, described in the following:

the EOW audio continuity and EOW party line structure in 9400AWY R.2.1
the NMS channel and EOW audio continuity
the NMS channel and EOW audio continuity with the Service Protection Box
the available supports for the Service Protection Box
18.3.1 EOW audio continuity and EOW party line structure in 9400AWY R.2.1
The EOW audio continuity is meaningful only if all connected NEs have the EOW function.
As far as 9400AWY R.2.1 is concerned, this is true only if the Audio + User Service Channel plugin
is equipped.
Fig. 113. below shows the 9400AWY R.2.1 EOW party line structure.
Audio 1 signals, associated to NMSV11

(see Tab. 69. on page 322 )
EOW telephone set NEs

(see chapter 52 EOW party Radio interface
on page 743 ) line
Audio 2 signals, associated to NMSG703

Fig. 113. 9400AWY R.2.1 EOW party line

208 / 866 3DB 16142 JAAA Ed.01
18.3.2 General on NMS channel and EOW audio continuity
The NMS channel continuity between two NEs is obtained, as described in Full Configuration
Procedures Step I on page 472 :

in case of the two 9400AWY R.2.1 NEs of the radio link, by means of the TMNRF channel
in case of two NEs not connected by radio, by means of the:
TMNV11 channel (NMSV11), implemented by wires
or, in alternative to each other:

TMNG703 channel (NMSG703), implemented by wires
or TMN inframe channel (NMSG703 inframe)
Fig. 114. below shows the continuity of NMS channel (and EOW audio, provided that the Audio + User
Service Channel plugin is equipped in 9400AWY R.2.1) for a NENE point to point connection:
NE A NE B
NMSV11 (+ Audio 1 signals) or NMSG703 (+ Audio 2 signals)
Fig. 114. NMS channel and EOW audio continuity in a NENE point to point connection
Fig. 115. below shows the continuity of NMS channel (and EOW audio, provided that the Audio + User
Service Channel plugin is equipped in 9400AWY R.2.1) for a NENE ring connection.
WARNING as shown in Fig. 115. , in a NENE audio ring connection, the audio loop makes the
conversation disturbed. To avoid that, you can:
open the audio loop, not connecting the audio signal wires between two NEs
or perform the audio squelch in only one of the 9400AWY R.2.1 NEs present in the
ring, disabling the party line by the screen of Fig. 228. on page 478 , or by the
screen of Fig. 286. on page 556
WRONG CONFIGURATION CORRECT CONFIGURATION
NMSG703 NE B NMSG703
NMSV11 NE B
(+ Audio 2) (+ Audio 2)
(+ Audio 1) NMSV11
full audio
ring causes NE C audio not
NE A NE A NE C
disturbance connected or
audio squelch
NMSV11 NMSG703 NMSV11 NMSG703
(+ Audio 1) NE D (+ Audio 2) (+ Audio 1) NE D (+ Audio 2)
?*!$&*?
Fig. 115. NMS channel and EOW audio continuity in a NENE ring connection

3DB 16142 JAAA Ed.01 209 / 866
18.3.3 NMS channel and EOW audio continuity with the Service Protection Box

As shown in table on page 195 , in most cases the network interconnections on 9400AWY Rel.2.1

are made on the lineside connectors of the Service Protection Box, that therefore, when present

in the networkrelevant figure of next paragraphs, must be always be present, independently from
1+0 or 1+1 system configuration, and independently from with/without EPS system
configuration.
Following Fig. 116. (for 1+0 configurations) and Fig. 117. (for 1+1 configurations) show the
standard interconnections between IDU and Service Protection Box. Such interconnections are done
through the following cables:
Ref. in Fig. 116. & Fig. 117. Cable code Description

ABC 3CC52116AAAA Cord SubD44Male SubD44Male
In the networkrelevant figures of next paragraphs, it is assumed that this standard interconnection,
between IDU and Service Protection Box, has already been done, so that they are not repeated in
such networkrelevant figures, but denoted by a generic block like this:
Service Protection Box
IDU
For details of the Service Protection Box, see para.112.5 from page 301 ; in particular, for its
connectors:
ESC see point [4] on page 305
NMS_V11 AUDIO1 see point [2] on page 303
NMSG703AUDIO 2 see point [3] on page 304
Moreover, some networkrelevant figure of next paragraphs specifies NMS Ethernet connection,
that must be done on the connector depicted in following Fig. 116. and Fig. 117. , too.
For details on cables used in the various network configurations (listed in the associated tables), see
Tab. 72. from page 327
N.B. GNE = Gateway Network Element

for connectors on Melodie equipment, refer to relevant documentation

210 / 866 3DB 16142 JAAA Ed.01
Connectors to use for
network interconnections
Line side
Equipment side
Connector to use for

NMS Ethernet
network interconnections B
C
Main Unit
Fig. 116. Standard interconnections between IDU and Service Protection Box (1+0 configurations)
Connectors to use for

Line side
Equipment side
Connector to use for

NMS Ethernet
A B
C
Main Unit
Extension Unit
Fig. 117. Standard interconnections between IDU and Service Protection Box (1+1 configurations)

3DB 16142 JAAA Ed.01 211 / 866
18.3.4 Available supports for the Service Protection Box

As depicted in Fig. 21. on page 81 , and in point f ) on page 244 , two types of support kits are

available:

one, allowing to mount two Service Protection Boxes, as shown in Fig. 118. below [example
for the NMS interconnection of two 9400AWY NE (1+1) radio protected].
This is the standard solution when the E1 Protection Box is not needed
NE1
NMS Interconnections between Service Protection

line sides of Service Protection Boxes Box
equipment side (NE2)
Service Protection
Box
equipment side (NE1)
NE2
Fig. 118. Two Service Protection Boxes mounted on one support
the other one is mandatory when also the E1 Protection Box is needed, as shown in Fig. 119.
below [example for the NMS interconnection of two 9400AWY NE (1+1) fully protected].
NMS Interconnections between

line sides of Service Protection Boxes
equipment side
NE1

equipment side
NE2
Fig. 119. E1 & Service Protection Boxes mounted on one support

212 / 866 3DB 16142 JAAA Ed.01
18.4 9400AWY 9400AWY interconnections with the Service Protection Box
18.4.1 NMS Continuity with the Service Protection Box

N.B. For correct interpretation of figures and tables in this paragraph, read carefully, if not yet done,
WARNING: cables are depicted schematically; for details on each cable (structure, connectors, and

3DB05922AA**
(1.6m)
or Sub.D 15 pins (IDU) NMS_V11 Audio1 (IDU) NMS_V11 Audio1
3DB05923AA**
(6.4m)
3DB05922AA**
(1.6m)
or Sub.D 15 pins (IDU) NMS_G703 Audio2 (IDU) NMS_G703 Audio2
3DB05923AA**
(6.4m)
3CC52142AAAA
(1 m)
or RJ45 8 pins cross (IDU) NMS Ethernet IP DCN
3CC52142ABAA
(5 m)
3DB10101AAAA Sub.D 15 pins Adapter Adapter
3DB10095AAAA
(1.6m)
or Sub.D 15 pins (IDU) NMS_V11 Audio1 IP Router (IP DCN)
3DB10096AAAA
(6.4m)

3DB 16142 JAAA Ed.01 213 / 866
214 / 866
NMS_V11 Audio1
NMS_G703 Audio2
Service Service
Service Protection Box Protection Box
Protection Box Service
Protection Box
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

NMS_V11 Audio1
3CC52142AAAA or
3CC52142ABAA

Fig. 120. NMS Continuity
Service
Protection Box
Service NMS_G703 Audio2
Protection Box
USER MANUAL
USER MANUAL
NMS_V11 Audio1
NMS_V11 Audio1
Service Service Service Service NMS_V11 Audio1
Protection Box Protection Box Protection Box Protection Box

Fig. 121. NMS Continuity
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
215 / 866
216 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
GNE
Service Service
ESC NMS_V11 AUDIO2 ESC NMS_V11 AUDIO2
Protection Box Protection Box
IDU
IDU

NMS Ethernet
Fig. 122. NMS Continuity on ESC

3DB10101AAAA + 3DB05952AAxx 3CC52142AAAA
3DB10101AAAA + 3DB05952AAxx
or
3CC52142ABAA
USER MANUAL
18.4.2 AUDIO Connection


3DB05922AA**
(1.6m)
3DB05923AA**
(6.4m)
3DB05922AA**
(1.6m)
3DB05923AA**
(6.4m)

3DB 16142 JAAA Ed.01 217 / 866
218 / 866
NMS_G703 Audio2
NMS_V11 Audio1
Service Service Service
Service Protection Box Protection Box Protection Box
Protection Box
NMS_G703 Audio2
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

Fig. 123. AUDIO Connection
Service NMS_V11 Audio1
Protection Box
Service
Protection Box
USER MANUAL
18.4.3 NMS Ring Protection with Audio Continuity


3DB05922AA**
(1.6m)
3DB05923AA**
(6.4m)
3DB05922AA**
(1.6m)
3DB05923AA**
(6.4m)
3CC52142AAAA
(1 m)
or RJ45 8 pins cross (IDU) NMS Ethernet (IDU) NMS Ethernet
3CC52142ABAA
(5 m)

3DB 16142 JAAA Ed.01 219 / 866
220 / 866
NMS_G703 Audio2
NMS_V11 Audio1
Service
Service Service Protection Box
Service
Protection Box
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

3CC52142AAAA
or
3CC52142ABAA

Fig. 124. NMS Ring protection with audio continuity
NMS_V11 Audio1
Service
Protection Box
Service
Protection Box
USER MANUAL
18.4.4 ESC Continuity


3DB10087AAAA (1.6m)
or Sub.D 15 pins (IDU) ESC (IDU) ESC
3DB10088AAAA (6.4m)
Protection Box
Service
ESC
Protection Box
Service
Protection Box
Service
ESC
Protection Box
Service
Fig. 125. ESC Continuity

3DB 16142 JAAA Ed.01 221 / 866
18.5 9400AWY MELODIE SNMP interconnections

N.B. For complete information on AlcatelLucent Melodie equipment, refer to the relevant

documentation.

18.5.1 NMS Continuity with Audio Connection

3DB05922AA**
(1.6m)
3DB05923AA**
(6.4m)
3DB10063AAAA
(1.6m)
or Y cable sub D 15 AWY (IDU) NMS_V11 Melodie (IDU) NMS_V11
(2x Sub D 9) Audio1 and Audio1
3DB10064AAAA
(6.4m)
3CC52142AAAA
(1 m)
or RJ45 8 pins cross (IDU) NMS Ethernet IP DCN
3CC52142ABAA
(5 m)

222 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
NMS_V11 Audio1
Service Service Service Service
Protection Box Protection Box Protection Box Protection Box
3CC52142AAAA
or
3CC52142ABAA

Fig. 126. NMS continuity with Audio connection
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
223 / 866
18.5.2 Service Channel Continuity (MELODIE 1+0 classic)



3DB10089AAAA (1.6m)
or Sub D 15 Sub D 9 (IDU) ESC (IDU) ESC34
3DB10090AAAA (6.4m)
3DB10100AAAA (1 m) Adapter Sub D 37 (3x Sub D 9)
ESC
Protection Box
Service
Protection Box
Service
Fig. 127. Service Channel continuity (MELODIE 1+0 classic)

224 / 866 3DB 16142 JAAA Ed.01
18.5.3 Service Channel Continuity (MELODIE 1+0 Light)

3CC52130AAAA (1.6m)
or Sub D 15Sub D 9 AWY (IDU) ESC Y cable Sub D 9 ESC3
3CC52131AAAA (6.4m)
Y cable sub D 37
3CC52121AAAA (1 m) Melodie ESC3/Alarm
(Sub D 9 + Sub D 25)
3CC52130AAAA or 3CC52131AAAA
ESC
Protection Box
Service
Protection Box
Service
Fig. 128. Service Channel continuity (MELODIE 1+0 Light)

3DB 16142 JAAA Ed.01 225 / 866
18.5.4 Service Channel Continuity (MELODIE 1+1)


3DB10091AAAA (1.6m)
3DB10092AAAA (6.4m)
Protection Box
Service
ESC
Protection Box
Service
Fig. 129. Service Channel continuity (MELODIE 1+1)

226 / 866 3DB 16142 JAAA Ed.01
18.5.5 Service Channel Continuity (MELODIE 1+1)

3DB10089AAAA (1.6m)
3DB10090AAAA (6.4m)
Protection Box
ESCService
Protection Box
Service
Fig. 130. Service Channel continuity (MELODIE 1+1)

3DB 16142 JAAA Ed.01 227 / 866
18.6 9400AWY MELODIE RQ2 interconnections

N.B. For complete information on AlcatelLucent Melodie equipment, refer to the relevant

documentation.

18.6.1 9400AWY NMS_V11 Transport (MELODIE 1+0 Classic)
3DB10063AAAA
(1.6m)
or Y cable sub D 15
(IDU) NMS_V11 Audio 1 (IDU) ESC345
(2x Sub D 9)
3DB10064AAAA
(6.4m)
3DB10100AAAA Adapter Sub D 37

(1m) (3x Sub D 9)

228 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
NMS_V11 AUDIO1
Service Service

Fig. 131. 9400AWY NMS V11 Transport (MELODIE 1+0 classic)
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
229 / 866
18.6.2 9400AWY NMS_V11 Transport (MELODIE 1+0 Light)



3CC52119AAAA
(1.6m)
or Y cable sub D 15
(IDU) NMS_V11 Audio 1 (IDU) ESC5
(2x Sub D 9)
3CC52120AAAA
(6.4m)
3CC52121AAAA Y cable sub D 37

(1m) (Sub D 9 + Sub D 25)

230 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
NMS_V11 AUDIO1
Service Service

Fig. 132. 9400AWY NMS V11 Transport (MELODIE 1+0 light)
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
231 / 866
18.6.3 9400AWY NMS_V11 Transport (MELODIE 1+1)



3DB10063AAAA
(1.6m)
or Y cable sub D 15 (2x Sub D 9) (IDU) NMS_V11 Audio 1 (IDU) ESC34
3DB10064AAAA
(6.4m)

232 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
NMS_V11 AUDIO1
Service Service

Fig. 133. 9400AWY NMS V11 Transport (MELODIE 1+1)
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
233 / 866
18.6.4 9400AWY NMS_V11 Transport (MELODIE 1+1)



3DB10063AAAA
(1.6m)
or Y cable sub D 15 (2x Sub D 9) (IDU) NMS_V11 Audio 1 (IDU) ESC5
3DB10064AAAA
(6.4m)
3CC52132AAAA
Sub D 25 Sub D 9 (IDU) NMS_V11 Audio 1
(1m)

234 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
NMS_V11 AUDIO1
Service Service

Fig. 134. 9400AWY NMS V11 Transport (MELODIE 1+1)
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
235 / 866
18.6.5 RQ2 9.6 Kb/s Transport



3DB10093AAAA (1.6m)
or Sub D 15 Sub D 9 (IDU) ESC (IDU) NMS1
3DB10094AAAA (6.4m)
ESC
Protection Box
Service
Protection Box
Service
Fig. 135. RQ2 9.6 Kb/s Transport

236 / 866 3DB 16142 JAAA Ed.01
18.7 E1 interconnections between 9400AWY and 9500MPRE MSS
N.B. These examples are referred to the 9500MPRE MSS8 base band. For complete information
on AlcatelLucent 9500MPRE equipment, refer to the relevant documentation.

[1] Allowed configurations

Both 9400AWY and the 32xE1 access card of 9500MPRE must be configured as:
1+0
or 1+1 radio protected (fully protected configurations are not allowed)
[2] Interconnections
Interconnections are the same for the (1+0) and (1+1) configurations.
WARNING: for details on each cable (structure, connectors, and pin connection tables) refer to
Interconnections for 16xE1 (example)

9400AWY 16xE1 IDU Main unit (example)
M1
32xE1 access card (example position)

A
1 2 9
3 4
5 6
7 8
M2
9500MPRE MSS8 (example)
Interconnections for 32xE1 (example)
9400AWY 32xE1 IDU Main unit (example) M1
M1
A 32xE1 access card (example position) B
1 2 9
3 4
5 6
7 8
M2
9500MPRE MSS8 (example) M2
A and B : cable 3CC52150AAAA (L=1.6 m) or 3CC52150ABAA (L=6.4 m)

3DB 16142 JAAA Ed.01 237 / 866
238 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
19 UNPACKING AND WAREHOUSING
19.1 General
The following procedures have been issued and must be observed when unpacking the equipment.
The reciprocal operation must be done for repacking. In such case it is recommended to use the original
packing material.
The following sturdy outer packing material is utilized in order to protect the equipment against mechanical
and climatic stresses to which they are subjected:
wooden crates for transport by ship, air, on road for periods longer than 60 days
plywood crates for transport by ship, air, on road for periods of 30 to 60 days
cardboard boxes for transport by air or on road for periods of less than 30 days
19.2 Unpacking
19.2.1 Preliminary checks
The following information should be printed on the outer crate:
International symbols:
side up
keep dry
fragile
trade mark/address of the manufacturing company;

labels (or templated marks) indicating information on the contract and destination site of the product;
an envelope holding among others the packing list
Upon receipt check:
that the final destination of the crates is that indicated on the label;
that no damage was made to the cases
Report any shipping damages to the Companys representative or the Shipping Agent.

3DB 16142 JAAA Ed.01 239 / 866
19.2.2 Unpacking phases

When having to unpack proceed as follows:

make sure that the packing has been properly positioned, refer to the symbol
open the case;
remove the shockproof material;
remove the goods from the case;
remove prepacking, the polyethylene bag and any other protection;
remove the plastic bags cellotaped to the rack and containing accessories;
remove the dehydrating bags;
ascertain that the goods are not damaged and that they correspond to those indicated on the packing
list enclosed in the envelope. Conversely, contact the agencys representative.
N.B. When unpacking it is advisable to handle the packing material with care; it might be reused for
packing again if it must be reshipped.
No antistatic wearing precaution are required for the unpacking phase.
19.2.3 Shipping crate content check
Check the contents of the shipping crates for the following configurations:
a) 1+0 Full integrated Antenna
IDU BB 1+0 (Telephone Kit if present in site)

ODU RTx & solar shield
Fixing Installation kit material
Antenna (with Pole Mounting)
IDU / ODU Cable & Connectors
Installation kit material
Subrack for BB Wall installation ( if foreseen by Plant Documentation)
Rx Power Monitoring & Light Service Kit Cable
Flash Card & SWP CDROM
b) 1+0 NON Integrated Antenna

ODU RTx & solar shield
Non Integrated Pole Mounting
Antenna Support
Antenna
Flex Twist / Wave guide and Wave Guide Connectors
Subrack for BB Wall installation ( if foreseen by Plant Documentation )

240 / 866 3DB 16142 JAAA Ed.01
c) 1+1 Full integrated Antenna


N2 ODU RTx & solar shield

RF Coupler
Antenna (with Pole Mounting)
Subrack for BB Wall installation ( if foreseen by Plant Documentation )
d) 1+1 NON Integrated Antenna

N2 ODU RTx & solar shield
RF Coupler
Non Integrated Pole Mounting
Antenna Support
Antenna
Flex Twist / Wave guide and Wave Guide Connectors
Subrack for BB Wall Installation ( if foreseen by Plant Documentation )
The 9400 AWY composition catalogue includes the installation components required for the most common
installation cases. The installation parts related to the available system configuration, and the antenna
types are listed in:
IDU installation components:

for all codes, chapter 110 from page 243
for IDU installation components (according to configuration), para.15.3 from page 101
ODU installation components, chapter 111 from page 249
IDUODU cable installation components, para.17.1 on page 189
19.3 Warehousing
If having to store the packed material, the following requirements must be met:
the cardboard boxes must be placed indoors in airy rooms;
the wooden or plywood cases can be placed outdoors, provided they are protected against rain and
direct sunlight.

3DB 16142 JAAA Ed.01 241 / 866
242 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
110 IDU INSTALLATION COMPONENTS
This chapter gives the P/N and the denomination of IDU installation components.
Two IDU boxes (Main / Extension) are foreseen:
(1+0): 44,45 x 443 x 210mm ( 1U) + Minidistributor ( 1U, 2U, or 3U)
(1 Main + Extension): 89,9x443x 210mm ( 2U) + Minidistributor ( 1U, 2U, or 3U)
Indoor units (IDU) of the 9400AWY system can be installed in different ways as described below:
Installation on a special workbench or desk;
Installation on a suitable wooden or masonry wall;
Installation in a 19 Din rack
Installation in a 21 ETSI rack (with Adapters)
Installation in Laborack
For each of the above type of installation special mechanical supporting fixtures are available.
Tab. 11. below gives a list of the installation materials that are included in the catalogue.
Tab. 11. IDU installation components

IDU INSTALLATION COMPONENTS
AlcatelLucent P/N Description
a) RACKS : see Chapter 13 on page 49
1AD114560001 19 Laborack
3DB04657AAAA 21 ETSI RACK H 2000
3DB04656AAAA 21 ETSI RACK H 2200
3CC09614AAAA IDU Wall Mounting Kit 3U
3DB06612AAAA 1+0 Table/ETSI Rack Mounting Kit (not documented in this manual)
b) TRU : see Chapter 14 on page 59
1AB152220001 6 Breakers DC Power Panel
1AD053060001 6 Fuse DC Power Panel
1AB058580014 One circuit breaker
B0177096497 Single fuse holder with fuse
c) 19 / 21 ADAPTER KITS : see Chapter 14 from page 49 , and Chapter 15 from page 69
3CC50042AAAA 21 Rack Adapter Kit for TRU and 3U Distributor Subracks
3CC50065AAAA 21 Rack Adapter Kit for 1U Distributor Subracks
21 Rack Adapter Kit for Support for E1 and Service protection boxes and
3DB16152AAAA
for DIN Rack Kit for 2 Service protection box
3DB18181AAAA 21 Rack Adapter Kit for IDU Main and Extension units

3DB 16142 JAAA Ed.01 243 / 866

d) ETSI IDU MAIN UNIT types

The P/Ns of the various types of IDU MAIN UNITS are given, and their use and installation are
explained, in Chapter 15 from page 69
IDU MAIN UNIT (example)

e) ETSI IDU EXTENSION UNIT types
The P/Ns of the various types of IDU EXTENSION UNITS are given, and their use and installation
are explained, in Chapter 15 from page 69
IDU EXTENSION UNIT (example)

f) PROTECTION BOXES AND SUPPORT KIT
The use and installation of the PROTECTION BOXES are explained in Chapter 15 from page
69
3DB16102AAAA E1 protection box
User line side equipment side
3DB16103AAAA Service protection box
equipment side
User line side
DIN Rack Kit Distributor Panels
It is used to mount one E1 protection box and/or one Service protection
3DB16151AAAA
box, and contains the support shown below, as well as the washers,
screws, and nuts to mount it on the rack.
DIN Rack Kit for 2 Service protection box

It is used to mount one or two Service protection boxes, and contains the
3DB16151ABAA
support shown below, as well as the washers, screws, and nuts to mount
it on the rack.

244 / 866 3DB 16142 JAAA Ed.01
g) DISTRIBUTOR SUBRACKS
The use and installation of the DISTRIBUTOR SUBRACKS are explained in Chapter 15 from
page 69
19 1U DISTRIBUTOR SUBRACK FOR 120 ohm non EMC (16E1)
3CC08062AAAA
N.B. 2 are necessary for 32E1 configurations
3CC07810AAAA 19 3U DISTRIBUTOR SUBRACK FOR 120 ohm EMC (32E1)
3U Support 19 Inch modules 120 Ohm (3CC07810AAAA)

19 DISTRIBUTOR SUBRACK FOR 1.6/5.6 (16E1)
3CC08061AAAA
Support connector 1.6/5.6 75 Ohm Panel 1U (3CC08061AAAA)

3DB 16142 JAAA Ed.01 245 / 866

19 DISTRIBUTOR SUBRACK FOR BNC (16E1)
3CC08061ABAA

2 x Support connector 75 Ohm BNC (3CC08061ABAA)

h) ITEMS FOR IDUODU CABLE
See para.17.1 on page 189
i) ITEMS FOR POWER SUPPLY AND GROUNDING CABLES
See chapter 14 from page 59
1AB093970004 EMI suppression ferrite with plastic case
3CC08211AAAA Connection cable 48V (3x4 mm2) (TDCC / TRU)
3CC08212AAAA Connection cable 24V (3x10 mm2) (TDCC / TRU)
3CC08209AAAA Power supply connection 24V (3x2.5 mm2) (TRU / IDU)
3CC08165AAAA Power supply connection 48V (3x1.5 mm2) (TRU / IDU)
3CC52136AAAA Cable Power Supply with Ferrite
j) SIGNAL CABLES
They are listed and described (drawings and connection tables) in Chapter 113 on page 327

246 / 866 3DB 16142 JAAA Ed.01
k) ACCESSORIES
1AB002130006 Panel coax connector 1.6/5.6

1AB006020076 Panel coax connector BNC 75ohm
1AB006420060 Male coax connector BNC 75 ohm
1AB009790019 Panel coax connector 1.0/2.3
1AB009870002 Male coax connector 1.6/5.6
1AB061220005 Male coax connector 1.0/2.3
1AB074610008 RJ45 8p connector
1AB095530021 CONN.MALE 90 50 OHM
1AC001100013 2MHz 75 OHM cable L=1m (049475400)
1AC001100022 COAX CABLE 50 OHM
1AC011980001 120ohm 8X2 twisted pair cable
1AC016760003 Cable 4 pair shielded
OSA3 insertion and extraction tool (to connect 120ohm pair to
1AD016040001
3CC07917AAAA)
75 OHM COAX CABLE 8XE1/DS1 IDU/DISTR NO CONNECTORS
3DB05588AAAA
L=10M
3CC06503AAXX Consumable set
3CC07917AAAA COMPAX module 10 pairs and covers
3CC52134AAAA SCSI 2xSub D adapter 1m
3DB05850AAXX ADAPT.CABLE 1.0/2.3 MALEBNC.FEMALE
3DB05851AAXX ADAPT.CABLE 1.0/2.3 MALE 1.6/5.6 FEMALE
3DB06371AAAA SUB D37 FW 10m
l) FLASH CARD TYPES
If necessary, see para.31.1 from page 404 , where Flash Card types are listed together with their
characteristics.
The Flash Card is packed (in a ESD protective envelope) separately from the other items, and is
inserted in the system during the hardware installation procedure; see step [3] on page 77
m ) ON SITE UPGRADE KITS
If necessary, see para.57.1 on page 797 , where kits are listed and their installation is described

3DB 16142 JAAA Ed.01 247 / 866

n) TELEPHONE KIT

The Telephone Kit is not used in the hardware installation procedure.
1AF12831AAAA
If necessary, see chapter 52 on page 743
RJ 11 connector

248 / 866 3DB 16142 JAAA Ed.01
111 ODU INSTALLATION COMPONENTS
This chapter gives the P/N and the denomination of ODU installation components, according to the
envisaged system configurations:
Subject On page
a) Full integrated or Not Integrated antenna installation components 250
b) Part lists and characteristics of ODU transceivers 258
c) Types of RF couplers 281
d) Types of Pole Mounting Installation Kits 282
e) Types of nose adapters 286

3DB 16142 JAAA Ed.01 249 / 866
111.1 Full integrated or Not Integrated antenna installation components

The following installation components tables include all the items required for the Full Integrated antenna

or Not Integrated antenna cases; the tables show the item part numbers and the requested quantity related

to the foreseen system:
9470 AWY, on page 251
Such installation components tables do not include the P/N of ODU transceivers, but the reference to
additional and specific ODU tables, which give, for each P/N, also the shifter characteristics. These
specific ODU tables are given in para.111.2 from page 258
Notes:
1In/N (2In/N) = it is possible to use FULL INTEGRATED ANTENNA (In) or NON INTEGRATED
ANTENNA (N)
1In (2In) = it is possible to use FULL INTEGRATED ANTENNA (In) only
1N (2N) = it is possible to use NON INTEGRATED ANTENNA (N) only
Legend:
1+1 HSB 1+1 Hot Standby
1+1 HSB SD 1+1 Hot Standby Space Diversity
1+1 FD AP 1+1 Frequency Diversity Alternate Polar
1+1 FD DA 1+1 Frequency Diversity Dual Antenna

250 / 866 3DB 16142 JAAA Ed.01
111.1.1 9470 AWY ODU installation components
Tab. 12. 9470 AWY ODU Installation materials for Integrated or Non Integrated antenna
9470 AWY ODU INSTALLATION COMPONENTS

AlcatelLucent Quantity / Configuration

Part Description 1+1 1+1 1+1 1+1
1+0
Number HSB HSB SD FD AP FD DA
RF Coupler
3CC14536AAAA
or 7.18.5 GHz 10dB Integrated Coupler 1
3CC14536AAAB
ODU Transceiver
For:
7 GHz ODUs with external diplexer
refer to para. 111.2.1.2 on page 260
7 GHz ODUs with embedded diplexer 1 2 2 2 2
refer to Tab. 24. on page 265
8 GHz ODUs with external diplexer
refer to para. 111.2.1.3 on page 262
Installation Materials
1AF11977AAAA Flex Twist WR112 PDR84/UBR84 L=1m 1N 1N 2N 2N 2N
1AB128510002 Non Integrated Antenna Pole Mounting 1N 1N 2N 2N 2N
3DB01459AAAA Nose adapter WR112 kit for not int antenna 1N 1N 2N 2N 2N
1AB128500002 IDUODU cable grounding kit diam. 10.3 mm
1AC001100022 IDUODU Coax cable 50 ohm diam. 10.3 mm 1 2 2 2 2
1AB095530021 Connector. male N. 90 50 ohm 2 4 4 4 4
3CC08166AAAA Ground connect kit (IDU+ODU)
3DB21042AAAB Common kit V2
1AC041350001 IDUODU Coax cable diam. 6.85mm 1 2 2 2 2
1AB095530037 Connector male N.90 50 ohm 2 4 4 4 4
1AD040130004 IDU/ODU cable grounding kit diam. 6.85mm
ANTENNA TYPE RFS
1AF14302AAAA AWY FULL INTEGRATED 0,6m
1AF11284AAAA AWY FULL INTEGRATED 1,2 m
1AF14290AAAA AWY FULL INTEGRATED 1,8
ANTENNA TYPE ANDREW
To be codified AWY FULL INTEGRATED 0,9m
Note for Quantity / Configuration In = Full Integrated Antenna N= Not Integrated Antenna
NOTE: next introduction in substitution of present configuration
Present
Next introduction Description
Configuration
1AB128510002 3DB10137AAAB POLE MOUNTING NON INTEGRATED ANTENNA
3DB01459AAAA 3DB10135AAAA WR112 ADAPTER KIT
1AF11977AAXX 3CC08010ABAB Flex Twist WR112 PBR84/UBR84 L=1m

3DB 16142 JAAA Ed.01 251 / 866



1+0
RF Coupler
3CC13472ABXX 13/15 GHz 10db Coupler 1
ODU Transceiver
Refer to Tab. 27. on page 267 1 2 2 2 2
1
3CC05751ACAA 13 GHz Flex Twist 600mm 1N
In/N
2N 2 2N
1
1AB146090003 NoseAdapter (Non Integr.Antenna) 1N
In/N
2N 2N 2N

ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
NOTE from 13GHz to 38GHz: next introduction in substitution of present configuration

Present
Configuration

252 / 866 3DB 16142 JAAA Ed.01


1+0
RF Coupler
3CC13472ABXX 13/15 GHz 10db Coupler 1
ODU Transceiver
For:
ODUs with fixed shifters
refer to Tab. 29. on page 269 1 2 2 2 2
ODUs with variable shifters

1
3CC05750ACAA Flex Twist 15 GHz 600mm 1N
In/N
2N 2 2N
1
1AB146090001 NoseAdapter (Non Integrated Antenna) 1N
In/N
2N 2N 2N

ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
Present
Configuration

3DB 16142 JAAA Ed.01 253 / 866



1+0
RF Coupler
3CC13473ABXX 18/23/245 GHz 10db Coupler 1
ODU Transceiver
For:

1
3CC05749ACAA 18/23/25 GHz Flex Twist 1N
In/N
2N 2 2N
1
1AB146090002 18/23/25 NoseAdapter (Non Integr.Antenna) 1N
In/N
2N 2N 2N

ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
Present
Configuration

254 / 866 3DB 16142 JAAA Ed.01


1+0
RF Coupler
ODU Transceiver
For:

1
In/N
2N 2 2N
1
In/N
2N 2N 2N

1AB095530021 Connector male N. 90 50 ohm 2 4 4 4 4
ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
Present
Configuration

3DB 16142 JAAA Ed.01 255 / 866


1+0
RF Coupler
ODU Transceiver
1
In/N
2N 2 2N
1
In/N
2N 2N 2N



ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
Present
Configuration

256 / 866 3DB 16142 JAAA Ed.01

1+0
RF Coupler
3CC13474AB** 28/38 GHz 10db Coupler 1
ODU Transceiver
1
3DB00682AAXX 28/38 GHz Flex.Twist 1N
In/N
2N 2 2N
1
3DB02082AAXX 28/38 NoseAdapter (Non Integr.Antenna) 1N
In/N
2N 2N 2N
FLEXTWIST ARM SUPPORT 2838GHz

3DB00692AAXX 1 1 2 2 2
(Non Integr.Antenna)
3DB03455AAXX Universal Round Collar 1 1 2 2 2



ANTENNA TYPE RFS
ANTENNA TYPE ANDREW
Present
Configuration

3DB 16142 JAAA Ed.01 257 / 866
111.2 Part lists and characteristics of ODU transceivers

Note for all tables:

ODU Type Hardware implementation can be:
with embedded diplexer
with external diplexer
For details, if necessary, see para.16.2.1 on page 140
Capacity can be:
32Mb = the16E1capacity ODU
64Mb = the32E1capacity ODU
Engineering version can be:
ODU V1 = the former ODU version
ODU V2 = the new ODU version
Modulation agility for ODU V1 :

32/64 Mb ODU V1= 4 & 16QAM (if supported by flash card) (*)
Modulation agility for ODU V2 :

32 Mb ODU V2= 4QAM only (independently from employed
flash card) (*)
64 Mb ODU V2= 4 & 16QAM (if supported by flash card) (*)
(*) for flashcard types, and associated supported modulation agility,

see Tab. 85. on page 404
Shifter : for some frequency ranges, two types of ODU are envisaged:
with fixed shifter
with variable shifter: the shifter value must be set by Craft
Terminal
Logistical Item Corresponds to the Logistical Item code you can read on the ODUs
label (see Fig. 54. on page 148 )
Note 1: for the same frequency range and shifter, there can be up to
4 different ODU part number:
ODU 32MbV1
ODU 32MbV2
ODU 64MbV1
ODU 64MbV2
Note 2: in some cases, two Logistical Items are listed for the same
frequency range, shifter and ODU type: such codes are fully
compatible and interchangeable (e.g. 3DB21091AAXX and
3DB21091ABXX in Tab. 39. on page 278 )
Technical Description (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.111.2.1 on page 259
ODUs with embedded diplexer, refer to para.111.2.2 on page 263

258 / 866 3DB 16142 JAAA Ed.01
111.2.1 Part lists of ODUs with external diplexer
111.2.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. 20. and Tab. 22.
Each diplexer is a three port passive device with two bandpass filters as described hereafter (physical
arrangement is shown in Fig. 52. on page 146):
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:
foL foH
f1 f2 f3 f4
frequencies
2.5 dB
70 dB
attenuation fr SHIFTER
WARNING: f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channel
frequencies and not to the cutoff frequencies of the filters.

3DB 16142 JAAA Ed.01 259 / 866
111.2.1.2 Part list of 7 GHz ODUs with external diplexer

Tab. 19. 7 GHz Transceiver assemblies

ODU Type Logistical Item Technical Description
3DB 06691 AAXX ODU 32MB 9470 7.1 7.75 GHz LHB
ODU 32MbV1
3DB 06692 AAXX ODU 32MB 9470 7.25 7.9 GHz UHB
3DB 21495 AAXX ODU 32MB 9470 Ext D 7.1 7.75 GHz LHB
ODU 32MbV2
3DB 21496 AAXX ODU 32MB 9470 Ext D 7.1 7.75 GHz UHB
3DB 06691 ABXX ODU 64MB 9470 7.1 7.75 GHz LHB
ODU 64MbV1
3DB 06692 ABXX ODU 64MB 9470 7.25 7.9 GHz UHB
ODU 64MbV2

260 / 866 3DB 16142 JAAA Ed.01
Tab. 20. Branching assemblies for 7 GHz ODU
N.B. shifter value choice to be done by Craft Terminal
Filter 1 MHz Filter 2 MHz

(Lower Band) (Upper Band)
BRANCHING ASSEMBLY
Central
Shifter
Freq. Low High Low High
MHz Technical Description
MHz Limit Limit Limit Limit Logistical Item
f1 f2 f3 f4 BRANCHING 7GHZ ...
154 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 06774 ABXX ... 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 ... CH11P P.SH.160 MHz
154 7617,0 7498,0 7582,0 7652,0 7736,0 ... CH22P P.SH.154_B MHz
3DB 06775 ABXX
160 7617,0 7498,0 7576,0 7658,0 7736,0 ... CH22P P.SH.160 MHz
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 06780 ABXX ... CH22P P.SH.161_A MHz
161 7365,0 7249,5 7319,5 7410,5 7480,5 3DB 06781 AAXX ... CH11P P.SH.161_B MHz
161 7435,0 7319,5 7389,5 7480,5 7550,5 3DB 06781 ABXX ... CH22P P.SH.161_B MHz
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 06782 ABXX ... 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 06783 ABXX ... 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 06784 ABXX ... 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 06785 ABXX ... 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 06776 ABXX ... CH22P P.SH.168 MHZ

3DB 16142 JAAA Ed.01 261 / 866
111.2.1.3 Part list of 8 GHz ODUs with external diplexer

Tab. 21. 8 GHz Transceiver assemblies

ODU Type Logistical Item Technical Description
3DB 06693 AAXX ODU 32MB 9470 7.7 8.4 GHz LHB
ODU 32MbV1
3DB 06694 AAXX ODU 32MB 9470 8.0 8.5 GHz UHB
ODU 32MbV2
3DB 06693 ABXX ODU 64MB 9470 7.7 8.4 GHz LHB
ODU 64MbV1
3DB 06694 ABXX ODU 64MB 9470 8.0 8.5 GHz UHB
ODU 64MbV2
Tab. 22. Branching assemblies for 8 GHz ODU

Filter 1 MHz Filter 2 MHz

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

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

... CH22P
294.440 7862.965 7970.075 8264.515 3DB 06786 ABXX
P.SH.294/305/311 MHZ
8063.740 8157.405
305.560 7851.845 8275.635
213.5 8147.0 8035.0 8046.0 8248.0 8259.0 3DB 10103 AAXX ... CH11P P.SH. 213.5 MHZ

262 / 866 3DB 16142 JAAA Ed.01
111.2.2 Part lists of ODUs with embedded diplexer
The following tables report the Logistical Items of the available 738 GHz ODUs (with embedded
diplexer) with the following information from left to right:

Column 1: Shifter (MHz)

Column 1bis : Central Frequency (MHz)
Column 2 & 3: Tx and Rx subbands
Column 4 to 7: Tx & Rx frequency ranges at RF interface (MHz)
For some frequency ranges, two types of ODU are available:
ODU with fixed shifter

ODU with variable shifter: the shifter value must be set by Craft Terminal
Summary of ODU tables:
FIXED SHIFTERS VARIABLE SHIFTERS

Frequency Part list of Part list of
(from page) List of fixed List of variable
ODU ODU
shifters shifters
32Mb & 64Mb 32Mb & 64Mb
Tab. 24. page 265

7 GHz
Tab. 23. page 264 and not available
( 264 )
Tab. 25. page 266
8 GHz not available not available
13 GHz
Tab. 26. page 267 Tab. 27. page 267 not available
( 267 )
15 GHz
Tab. 28. page 268 Tab. 29. page 269 Tab. 30. page 271 Tab. 31. page 272
( 268 )
18 GHz
( 273 )
23 GHz
( 276 )
25 GHz
( 279 )
38 GHz
( 280 )

3DB 16142 JAAA Ed.01 263 / 866
111.2.2.1 Shifters and part list of 7 GHz ODU with embedded diplexer

Tab. 23. List of FIXEDSHIFTERs for 7 GHz ODU

RF interface (MHz)
1 1bis 2 3 4 5 6 7
RF Tx RF Tx RF Rx RF Rx
Shifter CF Tx Rx
min max min max
These shifters are used by ODUs listed in Tab. 24. on page 265
7240,0 1 1p 7124,5 7194,5 7285,5 7355.5
7310,0 2 2p 7194,5 7264,5 7355,5 7425,5

161A
7240,0 1p 1 7285,5 7355.5 7124,5 7194,5
7310,0 2p 2 7355,5 7425,5 7194,5 7264,5
7480,5 1 1p 7249,5 7319,5 7410,5 7480.5

161B
7480,5 1p 1 7410,5 7480.5 7249,5 7319,5
7540,0 1 1p 7424,5 7494,5 7585.5 7655.5
7610,0 2 2p 7494,5 7564,5 7655,5 7725,5

161D
7540,0 1p 1 7585.5 7655.5 7424,5 7494,5
7610,0 2p 2 7655,5 7725,5 7494,5 7564,5
These Wide Band shifters are used by ODUs listed in Tab. 25. on page 266
7240 1 1p 7110,5 7208,5 7271,5 7369,5

WB 161A
7310 2 2p 7180,5 7278,5 7341,5 7439,5
WB 161B 7365 1 1p 7235,5 7333,5 7396,5 7494,5
7540 1 1p 7410,5 7508,5 7571,5 7669,5

WB 161D
7610 2 2p 7480,5 7578,5 7641,5 7739,5

264 / 866 3DB 16142 JAAA Ed.01
Tab. 24. Part list of ODU 32Mb & 64Mb 7 GHz 161MHz
Frequency & Shifter ODU type Logistical Item

3DB21044AAXX
ODU 32MbV2
7GHz 161 A 11P 3DB21044ABXX
ODU 64MbV2 3DB21388AAXX
3DB21047AAXX
ODU 32MbV2
7GHz 161 A 1P1 3DB21047ABXX
3DB21051AAXX
ODU 32MbV2
7GHz 161 A 22P 3DB21051ABXX
3DB21052AAXX
ODU 32MbV2
7GHz 161 A 2P2 3DB21052ABXX
3DB21053AAXX
ODU 32MbV2
7GHz 161 B 11P 3DB21053ABXX
3DB21054AAXX
ODU 32MbV2
7GHz 161 B 1P1 3DB21054ABXX
3DB21057AAXX
ODU 32MbV2
7GHz 161 D 11P 3DB21057ABXX
3DB21055AAXX
ODU 32MbV2
7GHz 161 D 1P1 3DB21055ABXX
3DB21058AAXX
ODU 32MbV2
7GHz 161 D 22P 3DB21058ABXX
3DB21056AAXX
ODU 32MbV2
7GHz 161 D 2P2 3DB21056ABXX

3DB 16142 JAAA Ed.01 265 / 866
Tab. 25. Part list of ODU 32Mb & 64Mb 7 GHz Wide Band 161MHz


ODU 32MbV2 3DB21044ACXX
7 GHz WB 161 A 11P
ODU 64MbV2 3DB21388ABXX

7 GHz WB 161 A 1P1

7 GHz WB 161 A 22P

7 GHz WB 161 A 2P2

7 GHz WB 161 B 11P

7 GHz WB 161 B 1P1

7 GHz WB 161 D 11P

7 GHz WB 161 D 1P1

7 GHz WB 161 D 22P

7 GHz WB 161 D 2P2

266 / 866 3DB 16142 JAAA Ed.01

RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
12807.5 1 1p 12750 12865 13016 13131
12920.5 2 2p 12861 12980 13127 13246

266
13073.5 1p 1 13016 13131 12750 12865
13186.5 2p 2 13127 13246 12861 12980
Tab. 27. Part list of ODU 32Mb & 64Mb 13GHz

ODU 32MbV1 3CC13688AAXX
13GHz/266 11P
ODU 64MbV1 3CC13688ABXX
13GHz/266 22P
13GHz/266 1P1
13GHz/266 2P2

3DB 16142 JAAA Ed.01 267 / 866


RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
14698 1 1p 14630 14766 14945 15081
14829,5 2 2p 14760 14899 15075 15214
315
15013 1p 1 14945 15081 14630 14766
15144,5 2p 2 15075 15214 14760 14899
14612 1 1p 14500 14724 14920 15144
14825,5 2 2p 14710 14941 15130 15361
420
15032 1p 1 14920 15144 14500 14724
15245,5 2p 2 15130 15361 14710 14941
14517,5 1 1p 14400 14635 14890 15125
14742,5 2 2p 14625 14860 15115 15350

490
15007,5 1p 1 14890 15125 14400 14635
15232,5 2p 2 15115 15350 14625 14860
14600 1 1p 14500 14700 15144 15344

644
15244 1p 1 15144 15344 14500 14700
14560 1 1p 14500 14620 15228 15348

728
15288 1p 1 15228 15348 14500 14620

268 / 866 3DB 16142 JAAA Ed.01
Tab. 29. Part list of ODU 32Mb & 64Mb 15 GHz with fixed shifters

FIXED SHIFTERs

15GHz/315 11P
15GHz/315 22P
15GHz/315 1P1
15GHz/315 2P2

15GHz/420 11P
15GHz/420 22P
15GHz/420 1P1
15GHz/420 2P2

15GHz/490 11P
15GHz/490 22P

3DB 16142 JAAA Ed.01 269 / 866



15GHz/490 1P1
15GHz/490 2P2

15GHz/644 11P
15GHz/644 1P1

15GHz/728 11P
15GHz/728 1P1

270 / 866 3DB 16142 JAAA Ed.01
Tab. 30. List of VARIABLESHIFTERs for 15 GHz ODU

RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
308 14701,5 14637 14766 14945 15074
315 14698 1 1p 14630 14766 14945 15081
322 14700 14641 14759 14963 15081
308 14832,5 14766 14899 15074 15207
315 14829,5 2 2p 14760 14899 15075 15214
322 14826 14759 14893 15081 15215
308 15009,5 14945 15030 14637 14766
315 15013 1p 1 14945 15081 14630 14766
322 15022 14963 15081 14641 14759
308 15140,5 15074 15207 14766 14899
315 15144,5 2p 2 15075 15214 14760 14899
322 15148 15081 15215 14759 14893
644 14600 14500 14700 15144 15344

1 1p
728 14560 14500 14620 15228 15348
644 15244 15144 15344 14500 14700

1p 1
728 15288 15228 15348 14500 14620

3DB 16142 JAAA Ed.01 271 / 866
Tab. 31. Part list of ODU 32Mb & 64Mb 15 GHz with variable shifters


VARIABLE SHIFTERs

15GHz/308315322 11P

15GHz/308315322 22P

15GHz/308315322 1P1

15GHz/308315322 2P2

15GHz/644728 11P

15GHz/644728 1P1

272 / 866 3DB 16142 JAAA Ed.01

RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
18640,5 1 1p 18581 18700 18921 19040
18760,5 2 2p 18701 18820 19041 19160

340
18980 1p 1 18920 19040 18580 18700
19100 2p 2 19040 19160 18700 18820
17951,5 1 1p 17703 18200 18711 19208
18430,5 2 2p 18182 18679 19190 19687

1008
18959,5 1p 1 18711 19208 17703 18200
19438,5 2p 2 19190 19687 18182 18679
17906,25 1 1p 17727.50 18085.00 18820.00 19177.50
18401,25 2 2p 18222.50 18580.00 19315.00 19672.50

1092.5
18998,75 1p 1 18820.00 19177.50 17727.50 18085.00
19493,75 2p 2 19315.00 19672.50 18222.50 18580.00
17950,5 1 1p 17700 18201 18710 19211
18435 2 2p 18180 18690 19190 19700

1010
18960,5 1p 1 18710 19211 17700 18201
19445 2p 2 19190 19700 18180 18690
17920 1 1p 17700 18140 19260 19700

1560
19480 1p 1 19260 19700 17700 18140

3DB 16142 JAAA Ed.01 273 / 866

FIXED SHIFTERs

18GHz/340 11P
18GHz/340 22P
18GHz/340 1P1
18GHz/340 2P2
18GHz/1008 11P ODU 32MbV1 3CC13468AAXX
18GHz/1008 1P1 ODU 32MbV1 3CC13470AAXX
18GHz/1092.5 11P ODU 32MbV1 3CC14472AAXX
18GHz/1092.5 22P ODU 32MbV1 3CC14473AAXX
18GHz/1092.5 1P1 ODU 32MbV1 3CC14474AAXX
18GHz/1092.5 2P2 ODU 32MbV1 3CC14475AAXX
18GHz/1560 11P
18GHz/1560 1P1

274 / 866 3DB 16142 JAAA Ed.01
RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
1008 17951,5 17703 18200 18711 19208
1 1p
1010 17950,5 17700 18201 18710 19211
1008 18430,5 18182 18679 19190 19687

2 2p
1010 18435 18180 18690 19190 19700
1008 18959,5 18711 19208 17703 18200

1p 1
1010 18960,5 18710 19211 17700 18201
1008 19438,5 19190 19687 18182 18679

2p 2
1010 19445 19190 19700 18180 18690
VARIABLE SHIFTERs
18GHz/10081010 11P
18GHz/10081010 22P
18GHz/10081010 1P1
18GHz/10081010 2P2

3DB 16142 JAAA Ed.01 275 / 866


RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
22157,5 1 1p 22000 22315 23008 23323
22450 2 2p 22300 22600 23308 23608

1008
23165,5 1p 1 23008 23323 22000 22315
23458 2p 2 23308 23608 22300 22600
21509,5 1 1p 21200 21819 22400 23019
22090,5 2 2p 21781 22400 22981 23600

1200
22709,5 1p 1 22400 23019 21200 21819
23290,5 2p 2 22981 23600 21781 22400
21492,5 1 1p 21198 21787 22430 23019
22074,5 2 2p 21781 22368 23013 23600

1232
22724,5 1p 1 22430 23019 21200 21819
23306,5 2p 2 23013 23600 21781 22368

276 / 866 3DB 16142 JAAA Ed.01
FIXED SHIFTERs

3DB21087AAXX
ODU 32MbV2
23GHz/1008 11P 3DB21087ABXX
3DB21088AAXX
ODU 32MbV2
23GHz/1008 22P 3DB21088ABXX
3DB21094AAXX
ODU 32MbV2
23GHz/1008 1P1 3DB21094ABXX
3DB21089AAXX
ODU 32MbV2
23GHz/1008 2P2 3DB21089ABXX


3DB 16142 JAAA Ed.01 277 / 866

RF interface (MHz)

1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
1050 23356 23302 23410 22252 22360

1200 23290,5 2p 2 22981 23600 21781 22400
1232 23306,5 23013 23600 21781 22368
1200 22090,5 21781 22400 22981 23600

2 2p
1232 22074,5 21781 22368 23013 23600
1232 21492,5 1 1p 21198 21787 22430 23019

1232 22724,5 1p 1 22400 23019 21200 21819
VARIABLE SHIFTERs
3DB21091AAXX
ODU 32MbV2
23GHz/105012001232 22P 3DB21091ABXX
3DB21093AAXX
ODU 32MbV2
23GHz/105012001232 2P2 3DB21093ABXX
3DB21090AAXX
ODU 32MbV2
23GHz/12001232 11P 3DB21090ABXX
3DB21092AAXX
ODU 32MbV2
23GHz/12001232 1P1 3DB21092ABXX

278 / 866 3DB 16142 JAAA Ed.01

RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
24768,5 1 1p 24540 24997 25548 26005
25221 2 2p 24994 25448 26002 26456
1008
25776,5 1p 1 25548 26005 24540 24997
26229 2p 2 26002 26456 24994 25448
FIXED SHIFTERs
25GHz/1008 11P
25GHz/1008 22P
25GHz/1008 1P1
25GHz/1008 2P2

3DB 16142 JAAA Ed.01 279 / 866


RF interface (MHz)
1 1bis 2 3 4 5 6 7
Shifter CF Tx Rx
min max min max
37335 1 1p 37050 37620 38310 38880
37899,5 2 2p 37619 38180 38879 39440

1260
38595 1p 1 38310 38880 37050 37620
39159,5 2p 2 38879 39440 37619 38180
FIXED SHIFTERs
38GHz/1260 11P
38GHz/1260 22P
38GHz/1260 1P1
38GHz/1260 2P2

280 / 866 3DB 16142 JAAA Ed.01
111.3 Types of RF couplers
Subject On page
RF couplers for 7/8GHz bands below
RF couplers from 13 to 38GHz 282
111.3.1 RF couplers for 7/8GHz bands
Tab. 44. Codes, characteristics and views of RF couplers for bands from 7 to 8 GHz
Waveguide Coupler Coupling

Code Description
(3 ports) type loss
3CC14536AAAB 7.18.5 GHz 10dB Coupler

WR 112 10 dB 1 dB / 10 dB
3CC14536AAAA 7.18.5 GHz 10dB Coupler
Coupler weight = 6 Kg about
(3CC14536AAAB)
(3CC14536AAAA)
Fig. 136. ODU RF coupler views (Bands 7 8 GHz)

3DB 16142 JAAA Ed.01 281 / 866
111.3.2 RF couplers for bands from 13 to 38GHz

Tab. 45. Codes, characteristics and views of RF couplers for bands from 13 to 38 GHz

Waveguide Coupler Coupling
Code Description
(3 ports) type loss
3CC13472ABxx 13/15 GHz 10dB Coupler WR 62
3CC13473ABxx 18/23/25 GHz 10dB Coupler WR 42 10 dB 1 dB / 10 dB
3CC13474ABxx 38 GHz 10dB Coupler WR 28
Coupler weight = 4.3 Kg about
Fig. 137. ODU RF coupler view (Bands from 13 to 38 GHz)
111.4 Types of Pole Mounting Installation kits
Subject On page
FULL INTEGRATED ANTENNA Pole Mounting Installation kits 283
NON INTEGRATED ANTENNA Pole Mounting Installation kits 284
Types of nose adapters 286

282 / 866 3DB 16142 JAAA Ed.01
111.4.1 FULL INTEGRATED ANTENNA Pole Mounting Installation kits
These Full integrated Antenna Pole Mounting kits are designed for quick mechanical installation, and:
are included inside the chosen antenna kit (antenna kits are listed, according to frequency bands,
in tables of para.111.1 from page 250 ). The pole mounting and the antenna are always delivered
already assembled.
foresee the Fine Tuning for the positioning of the Antenna.
Fig. 138. below shows some examples of these Full integrated Antenna Pole Mounting kits, shown
without antenna.
Fine tuning
RFS (1ft) ANDREW (1&2ft)

Fig. 138. Examples of FULL INTEGRATED ANTENNA Pole Mounting (shown without antenna)
Moreover, as shown in Fig. 139. below, these Full integrated Antenna Pole Mounting kits are supplied
with the frequencyspecific nose adapter for mounting the frequencyspecific ODU transceiver or RF
Coupler.
In general, the nose adapter:
in case of smallest antennas, is already mounted on the antenna
in case of largest antennas, is supplied separately, and must be mounted on the antenna during the
installation procedure
Nose adapter
Fig. 139. Example of FULL INTEGRATED ANTENNA Pole Mounting (with antenna and nose adapter)

3DB 16142 JAAA Ed.01 283 / 866
111.4.2 NON INTEGRATED ANTENNA Pole Mounting Installation kits

These kits are frequency independent, and provide only the mechanical support function. The frequency

specialization is obtained mounting the frequencyspecific nose adapter, see para.111.5 on page 286

All parts shown should be received packed together in the same carton. The steerable support is wrapped
and the remaining hardware is in two plastic bags, the large pieces in a large plastic bag and the smaller
hardware in a small plastic bag within the larger bag.
Presently, two types are foreseen, in alternative:
[1] P/N 3DB10137AAAA
Description Code Ref. in figure Qty

SUPPORT POLE MOUNTING 3DB10138AAAA 1 1
SUPPORT TUBE 3CC13037AAAA 2 1
2G0 9400UXETRIER 3CC06029ABAA 3 2
WASHER*PLAIN (10.5mmx22mmx2mm/M10) 1AD000870185 4 4
WASHER*SCSPG (10.5mmx16.5mmx1.8mm/M10) 1AD011670004 5 8
NUT*HEX*HEXHD (M10*8.4mm) 1AD001970046 6 8
SCREW*HEXHD*HEXHD (M10X40*SS) 1AD002040083 7 4
WASHER*WAVED (4.3mmx9mmx500mm/M4) 1AD002290002 3
SCREW*CHHD*HEXSKT (M4x12mm*SS) 1AD002150063 3
LUG*RING*CRIMP*UNINSUL (4.51mm) 1AB032050033 4
SILICON GREASE [tube 5/8 X 23/16 (1.5cc)] 1AC018650001 1
Fig. 140. NON INTEGRATED ANTENNA Pole Mounting Installation kit (3DB10137AAAA)

284 / 866 3DB 16142 JAAA Ed.01
[2] P/N 3DB10137AAAB
N.B.
N.B. the nose adapter shown is not included in the kit
Description Code Ref. in figure Qty

Support 3CC52135AAAA 1 1
M10 TIEROD 3CC01910AAAA 2 2
NUT M10*8.4MM 1AD001970046 3 4
Washer (10.2mmx18.1mmx2.2mm/M10) 1AD009240006 4 4
Washer plain (10.5mmx22mmx2mm/M10) 1AD000870185 5 4
Silicon grease Tube 5/8x23/16 (1.5cc) 1AC018650001 1
Lug ring crimp 4.51mm 1AB032050033 7 2
NUT M6*5MM 1AD001970018 8 5
Screw M6x25mm 1AD002150018 9 1
Washer plain (6.1mmx11.8mmx1.6mm/M6) 1AD000870134 10 5
Washer (6.1mmx11.8mmx1.6mm/M6) 1AD009240003 11 4
Screw M6X16mm 1AD002150027 12 3
Support 3CC58034AAAA 13 2
Fig. 141. NON INTEGRATED ANTENNA Pole Mounting Installation kit (3DB10137AAAB)

3DB 16142 JAAA Ed.01 285 / 866
111.5 Types of nose adapters

In case of:

Full Integrated Antenna configurations, the nose adapter is delivered inside the chosen antenna kit
(see Fig. 139. on page 283 ); in this case the RF interface is used to attach the frequencyspecific
ODU transceiver or RF Coupler.
Non Integrated Antenna configurations, as shown in Fig. 142. below, the nose adapter is used to
attach:
at one side, the frequencyspecific ODU transceiver or RF Coupler
at the other side, to attach the Flextwist cable toward the antenna.
In these Non Integrated Antenna configurations, the nose adapter is delivered as individual item, and
must be always mounted on the Non Integrated Antenna Pole Mounting, during the installation
procedure.
The P/Ns of nose adapter are listed, according to frequency bands, in tables of para.111.1 from
page 250
Fig. 142. below shows how to mount the nose adapter on the NON INTEGRATED ANTENNA Pole
Mounting of Fig. 140. on page 284 , while Fig. 141. on page 285 shows directly how to mount
the nose adapter. Mounting accessories are delivered with the nose adapter.
ODU or RF coupler Flextwist cable

side (to antenna) side
Fig. 142. Nose adapter mounting (example)

286 / 866 3DB 16142 JAAA Ed.01
112 VIEWS OF IDU UNITS, CONNECTOR PINOUT, AND SIGNAL
DESCRIPTION
This chapter gives detailed operative information regarding the IDU shelfs units available with the
equipment version this handbook issue is relevant to, for 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 and associated signals, visual indicators, buttons).
Subject On page
General 288
Description of IDU Main unit 289
IDU Main Unit LEDs summary 291
ECT RS232 connector pinout 292
OS (or ECT) 10/100BaseT connector pinout 293
Gbit Ethernet tributaries 293
Description of IDU Extension unit 294
IDU Extension Unit LEDs summary 295
Description of E1 Protection box (Tributary Panel) 296
E1 Protection box: pinout of lineside connectors 297
Description of Services Protection box (Auxiliary Service Panel) 301
ALM connector 302
NMSV11AUDIO 1 connector 303
NMSG703AUDIO 2 connector 304
ESC connector 305
Power Supply connector pinout (Main and Extension units) 306
Connector for IDUODU cable (Main and Extension units) 306
1/16 E1 I/O SCSI 68pin Female connector 307
17/32 E1 I/O SCSI 68pin Female connector 309
ALMNMS (G703/V11) SubD 44pin Female connector 311
AUDIOUSER SERV SubD 44pin Female connector 313
USER SERV SubD 44pin Female connector 315
Description of user signals with alternative connectors 316
E1 signals 316
Alarms and Housekeeping signals 317
Alternative connectors for Audio, NMS, and User Service Channels signals 321
NMS V11 Audio 1 signals 322
NMS G703 Audio 2 signals 323
User service channels signals 324

3DB 16142 JAAA Ed.01 287 / 866
112.1 General

This chapter describes the views of IDU units (MAIN, EXTENSION, and Protection Boxes), and describes

the signals present on their connectors, starting from such physical views.

For user convenience, Tab. 46. below indicates where to find same information, starting from the types
of tributary or signal.
Tab. 46. Summary of customeruse signals
Described
Tributary / signal
in paragraph from page
E1 112.13.1 316
Alarms and Housekeeping signals 112.13.2 317
OS (or ECT) 10/100BaseT 112.2.3 293
NMS V11 Audio 1 signals 112.13.4 322
NMS G703 Audio 2 signals 112.13.5 323
Gbit Ethernet (optional) 112.2.4 293
User service channels (optional) 112.13.6 324
N.B. For detailed operative information regarding the:
description of IDU interconnections, please refer to Chapter 15 on page 69 , and to

equipment commissioning, please refer to Chapter 42 on page 675
equipment maintenance, please refer to section 5 MAINTENANCE on page 737
Cautions to avoid equipment damage

Carefully observe statements specified in point iii on page 4

288 / 866 3DB 16142 JAAA Ed.01
112.2 Description of IDU Main unit
1 2 A 3 4 5 6 7 8
9 10 11 12 13 14 15 16
17 B C
18
Fig. 143. IDU Main Unit front and rear views
Tab. 47. IDU Main Unit: external interfaces list

Ref.
Connector or item detail Interface / Explanation Details
Fig. 143.
Basic Interfaces (without optional plugsin)
para.112.6
(1) SubD 3 Male Station Battery input
on page 306
ON/OFF switch: general
I ON
(2) power supply switch
O OFF
(IDU Main + its ODU)
RJ45 para.112.2.3
(3)
OS (or ECT) 10/100BaseT on page 293
For AlcatelLucent
(4) Debug RJ45
personnel use only
para.112.7
(8) N 50 ohm Female For IDUODU cable
on page 306
Acknowledgement: Alarm
attending pushbutton; this
para.55.6.2
(9) pushbutton turns OFF LEDs
on page 760
MAJ/MIN and turns ON
yellow LED ATTD
Equipment Controller performs the system

(10)
Reset pushbutton restart

3DB 16142 JAAA Ed.01 289 / 866
Ref.
Fig. 143.

Lamp Test pushbutton: it

para.54.1.1
(11) allows to HW test the LEDs
on page 751
of the unit
RS232 connector for NECT para.112.2.2
(12) SubD 9
serial cable on page 292
para.112.8
(13) SCSI 68 pin Female 116E1 64 wires
on page 307
interconnection with
connector for 100 pin SCSI
Extension Unit,
(14) SCSI 100 pin Female flat cable (used only in 1+1
no pin usage by
configurations)
Customer
connector for Alarms para.112.10
(15) SubD 44 Female
Housekeeping NMS on page 311
para.112.2.1
(16) 9 LEDs
on page 291
(17) + (18) para.31.1
Flash Card
+ (A) on page 404
(B) label Data Matrix codification for factory use
Fig. 14.
(C) label unit identification
on page 70
Optional Interfaces (with optional plugsin)
Connectors according to the equipped plugin (if any) (N.B.) :
4 x RJ45 Ethernet user data,
when para.112.2.4
Enhanced Ethernet plugin on page 293
(5)
is equipped
1732 E1 64 wires,
para.112.9
SCSI 68 pin Female when the 1732 E1 plugin
on page 309
is equipped
Connectors present only when the Audio + User Service Channel plugin is
equipped (N.B.) :
Audio1/2 + G703_V11 User para.112.11
SubD 44 Female
Service Channel on page 313
(6) + (7)
RJ11 Female for chapter 52

EOW telephone on page 743

When no plugin equipped, the slot is closed by a metal plate (inside the panel rear

side).
(N.B.)
Metal plate is mandatory to ensure EMIEMC performance

290 / 866 3DB 16142 JAAA Ed.01
112.2.1 IDU Main Unit LEDs summary
Nine LEDs are present on the front panel of the IDU Main Unit [position (16) in Fig. 143. on page 289 ]:
GREEN RED GREEN

RED
YELLOW
GREEN RED RED YELLOW
1) ON = Power ON (green)
2) RDI = Remote Defect Indication (red)
3) MIN = Minor Alarm (red)
4) EOW = Engineering Order Wire (bicolor: yellow if busy; green if free)
5) ODU W = ODU Working (green)
6) ATTD = Attended (yellow)
7) MAJ = Major Alarm (red)
8) LDI = Local Defect Indication (red)
9) ANT = Not operative in current SWP version
Fig. 144. 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 52 on page 743 for details.

3DB 16142 JAAA Ed.01 291 / 866
[5] 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. 143. on page
289 ] 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. 143. on page 289 ] allows the HW test of all LEDs.
112.2.2 ECT RS232 connector pinout
Connector present on the front panel of the IDU Main Unit [position (12) in Fig. 143. on page 289 ]
Tab. 48. ECT connections
pin 1
CONNECTION TABLE OF ECTPC cable (1AB054120027)

RS 232 (IDU MAIN side) RS 232 (PC side)
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9

292 / 866 3DB 16142 JAAA Ed.01
112.2.3 OS (or ECT) 10/100BaseT connector pinout
Connector present on the front panel of the IDU Main Unit [position (3) in Fig. 143. on page 289 ]
Tab. 49. OS (or ECT) connections
N.B. Leds are not operative

RJ45 RJ45
Signal Color used
(IDU MAIN side) (OS side)
1 Tx + White/Orange 1
2 Tx Orange 2
3 Rx + White/Green 3
4 Not used Blue 4
5 Not used White/Blue 5
6 Rx Green 6
7 Not used White/Brown 7
8 Not used Brown 8
112.2.4 Gbit Ethernet tributaries
Present on the front panel of the IDU Main Unit [position (5) in Fig. 143. on page 289 ] 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. 50. RJ45 connectors leds for Ethernet user data interfaces
Display
Color Ledoff Ledon Led blinking
Function
Link and
LEFT LED Green Link down Link up
activity status
No TX/RX
TX/RX activity
RIGHT LED Yellow activity activity
detected
detected

3DB 16142 JAAA Ed.01 293 / 866
112.3 Description of IDU Extension unit

9 8

4 5 6 7
1 2 3
B C
Fig. 145. IDU Extension Unit front and rear views
Tab. 51. IDU Extension Unit: external interfaces list

Ref.
Fig. 145.
Basic Interfaces (without optional plugsin)
para.112.6
(1) SubD 3 Male Station Battery input
on page 306
ON/OFF switch: general
I ON
(2) power supply switch
O OFF
(IDU Extension + its ODU)
Lamp Test pushbutton: it

para.54.1.1
(3) allows to HW test the LEDs
on page 751
of the unit
para.112.8
(4) SCSI 68 pin Female 116E1 64 wires
on page 307
interconnection with
connector for 100 pin SCSI Main Unit,
(5) SCSI 100 pin Female
flat cable no pin usage by
Customer
Audio1/2 + G703_V11 User para.112.11
(6) SubD 44 Female
Service Channel on page 313
para.112.3.1
(7) 3 LEDs
on page 295
para.112.7
(8) N 50 ohm Female For IDUODU cable
on page 306
(B) label Data Matrix codification for factory use
Fig. 14.
(C) label unit identification
on page 70

294 / 866 3DB 16142 JAAA Ed.01
Ref.
Fig. 145.
Optional Interfaces (with optional plugin)

Connector present only when the 1732 E1 plugin is equipped :

para.112.9
SCSI 68 pin Female 1732 E1 64 wires
on page 309
(9)

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
112.3.1 IDU Extension Unit LEDs summary
Three LEDs are present on the front panel of the IDU Extension Unit [position (7) in Fig. 145. on page 294 ]:
GREEN GREEN
1) ON = Power ON (green)
This green LED is ON when the Station Battery is connected, the ON/OFF switch is
ON, and the internal DC/DC is working properly.
2) ODU W = ODU Working (green).
The ODUW led ON identifies the TX activity of the ODU connected to the
EXTENSION unit.
It is OFF in case of:
IDUODU Cable Loss alarm
Mute function activated
ODU switchingoff command activated in 1+1 HSB configuration
3) ANT = Not operative in current SWP version
Fig. 146. LEDs on the IDU Extension Unit front panel
The lamp test pushbutton [position (3) in Fig. 145. on page 294 ] allows the HW test of all LEDs.

3DB 16142 JAAA Ed.01 295 / 866
112.4 Description of E1 Protection box (Tributary Panel)

3 1

Line Side
4 2
6 8
Equipment Side
5 7
Fig. 147. E1 Protection box: views of Equipment Side and Line Side connectors
Tab. 52. Equipment Side and Line Side connectors of E1 Protection box
Ref. Connector
Interface To be connected to
Fig. 147. pinout
Line side: 4 connectors SubD 37 Female
(1) 18 E1
(2) 916 E1
(3) 1724 E1
(4) 2532 E1
Equipment side: 4 connectors SCSI 68 pin Female
samename connector of IDU Main unit
(5) 116 E1
[ (13) in Fig. 143. on page 289 ] para.112.8
samename connector of IDU Extension unit on page 307
(6) 116 E1
[ (4) in Fig. 145. on page 294 ]
samename connector of IDU Main unit
(7) 1732 E1
[ (5) in Fig. 143. on page 289 ] para.112.9
samename connector of IDU Extension unit on page 309
(8) 1732 E1
[ (9) in Fig. 145. on page 294 ]

296 / 866 3DB 16142 JAAA Ed.01
112.4.1 E1 Protection box: pinout of lineside connectors
For usage details, refer to para.112.13.1 on page 316

Tab. 53. E1 tributaries (1 to 8) connector pinout
pin 1
Description Pin # Pin # Description
Not Used 1 20 Not Used
IN+ Trib. 1 2 21 IN Trib. 1
GND 10
29 Not Used
Not Used 11
Out+ Trib. 1 12 30 Out Trib. 1

3DB 16142 JAAA Ed.01 297 / 866

pin 1

GND 10
29 Not Used
Not Used 11

298 / 866 3DB 16142 JAAA Ed.01
pin 1
GND 10
29 Not Used
Not Used 11

3DB 16142 JAAA Ed.01 299 / 866

pin 1

GND 10
29 Not Used
Not Used 11

300 / 866 3DB 16142 JAAA Ed.01
112.5 Description of Services Protection box (Auxiliary Service Panel)
1 2 3 4
Line Side
5 6 7
Equipment Side
Fig. 148. Services Protection box: views of Equipment Side and Line Side connectors
Tab. 57. Equipment Side and Line Side connectors of Services Protection box
Ref. Connector
Interface To be connected to
Fig. 147. pinout
Line side: 4 connectors SubD 15 Female
Alarms + station DDF for Alarms + Housekeeping;
(1)
Housekeeping see point [1] on page 302
NMS V.11 + station DDF for NMS V.11 + Audio 1;
(2)
Audio 1 see point [2] on page 303
NMS G.703 + station DDF for NMS G.703 + Audio 2;
(3)
Audio 2 see point [3] on page 304
User Service station DDF for User Service Channels;
(4)
Channels see point [4] on page 305
Equipment side: 3 connectors SubD 44 Female
Audio1/2 +
samename connector of IDU Extension unit para.112.12
(5) G703_V11 User
[ (6) in Fig. 145. on page 294 ] on page 315
Service Channel
Audio1/2 +
samename connector of IDU Main unit para.112.11
(6) G703_V11 User
Service Channel
samename connector of IDU Main unit para.112.10
(7) ALMNMS

3DB 16142 JAAA Ed.01 301 / 866
112.5.1 Services Protection box: pinout of lineside connectors

[1] ALM connector

Connector present on the line side of the:

Services Protection box [position (1) in Fig. 148. on page 301 ]
Tab. 58. Alarms Housekeeping connector pinout
pin 1
Pin Signal
6 HK_I1
13 HK_I2
7 HK_I3
14 HK_I4
8 HK_I5
15 HK_I6
4 HK_O1
11 HK_O2
5 HK_O3
12 HK_O4
9 COM
1 A_1
2 A_2
3 A_3
10 GND

302 / 866 3DB 16142 JAAA Ed.01
[2] NMSV11AUDIO 1 connector

For usage details, refer to

para.112.13.3 on page 321
and para.112.13.4 on page 322
Tab. 59. NMSV.11 + Audio 1 connector pinout
pin 1
RS422 data in (+) 1 9 RS422 data in ()
RS422 clock in (+) 2 10 RS422 clock in ()
RS422 data out (+) 3 11 RS422 data out ()
RS422 clock out (+) 4 12 RS422 clock out ()
GND NMS 5 13 Audio1 signal from user ()
Audio1 signal from user (+) 6 14 Audio1 signal to user ()
Audio1 signal to user (+) 7 15 Not used
GND Audio 8

3DB 16142 JAAA Ed.01 303 / 866
[3] NMSG703AUDIO 2 connector


Tab. 60. NMSG.703 + Audio 2 connector pinout
pin 1
G703 data in (+) 1 9 G703 data in ()
Not used 2 10 Not used
G703 data out (+) 3 11 G703 data out ()
Not used 4 12 Not used
GND NMS 5 13 Audio2 signal from user ()
Audio2 signal from user (+) 6 14 Audio2 signal to user ()
Audio2 signal to user (+) 7 15 Not used
GND Audio 8

304 / 866 3DB 16142 JAAA Ed.01
[4] ESC connector


Tab. 61. User service channel connector pinout
pin 1
Pin # Signal
2 COD_RX +
9 COD_RX
3 COD_TX +
10 COD_TX
4 RX_ASY
11 TX_ASY
5 CC_RX +
12 CC_RX
6 RX_CK +
13 RX_CK
7 CC_TX +
14 CC_TX
8 CC_TCK +
15 CC_TCK
1 GND

3DB 16142 JAAA Ed.01 305 / 866
112.6 Power Supply connector pinout (Main and Extension units)

Connector present on the front panel of the:

IDU Main Unit [position (1) in Fig. 143. on page 289 ],

and of the IDU Extension Unit [position (1) in in Fig. 145. on page 294 ]
Pin section = 3 x 4 mm2
Tab. 62. Power supply connections
Pin Function
A1 + BATTERY
A2 GROUND
A3 BATTERY
112.7 Connector for IDUODU cable (Main and Extension units)

IDU Main Unit [position (8) in Fig. 143. on page 289 ],
and of the IDU Extension Unit [position (8) in in Fig. 145. on page 294 ]
The transceiver inside the ODU module is connected at IDU side through an IDUODU interconnecting
50 ohm coaxial cable. The connector used is a N male connector.
For details on IDUODU cable connection, see chapter 17 from page 189
ATTENTION
The Ntype connector carries +48 DC voltage for ODU power supply.
Do not connect measuring instruments directly.

306 / 866 3DB 16142 JAAA Ed.01
112.8 1/16 E1 I/O SCSI 68pin Female connector

IDU Main Unit [position (13) in Fig. 143. on page 289 ]

IDU Extension Unit [position (4) in in Fig. 145. on page 294 ]

E1 Protection box [positions (5) and (6) in in Fig. 147. on page 296 ]
Tab. 63. 1/16 E1 I/O SCSI 68pin Female connector
Pin #
Signal name Direction Cable Signal meaning
A B
1 GND
35 GND
2 TTIP_1 OUTPUT OUT+TRIB 1
36 TRING_1 OUTPUT OUTTRIB 1
3 RTIP_1 INPUT IN+TRIB 1
37 RRING_1 INPUT INTRIB 1
3DB 16142 JAAA Ed.01 307 / 866
Pin #
A B


34 GND
68 GND

308 / 866 3DB 16142 JAAA Ed.01
112.9 17/32 E1 I/O SCSI 68pin Female connector



E1 Protection box [positions (7) and (8) in in Fig. 147. on page 296 ]
Tab. 64. 17/32 E1 I/O SCSI 68pin Female connector
Pin #
A B
1 GND
35 GND

3DB 16142 JAAA Ed.01 309 / 866
Pin #
A B


34 GND
68 GND

310 / 866 3DB 16142 JAAA Ed.01
112.10 ALMNMS (G703/V11) SubD 44pin Female connector


Usage notes:
nb1: see para.112.13.2 on page 317
Tab. 65. ALMNMS (G703/V11) SubD 44pin female connector
Pin #
Signal Direction Usage
A B C
1 GND
2 COD_TXP (G703) OUTPUT nb3
3 COD_TXN (G703) OUTPUT
16 GND
17 CC_RXP (V11) INPUT nb2
18 CC_RXN (V11) INPUT
31 GND
32 CC_TXP (V11) OUTPUT

nb2
33 CC_TXN (V11) OUTPUT
4 COD_RXP (G703) INPUT

nb3
5 COD_RXN (G703) INPUT
6 GND
19 RX_CKN (V11) BID

nb2
20 RX_CKP (V11) BID
21 GND
34 CC_TCKP (V11) OUTPUT

nb2
35 CC_TCKN (V11) OUTPUT
36 GND

3DB 16142 JAAA Ed.01 311 / 866
Pin #
Signal Direction Cable Usage

A B C

7
8 GND
9 GND nb2
22
23 GND
24
37 GND
38
39 COM nb3
10 HK_O1 OUTPUT nb1
11 COM
12 A_1 OUTPUT
25 HK_O2 OUTPUT
26 HK_O3 OUTPUT
nb1
27 A_2 OUTPUT
40 HK_O4 OUTPUT
41 A_3 OUTPUT
42 COM_GND
13 COM_GND
14 HK_I1 INPUT
nb1
15 HK_I2 INPUT
28 COM_GND
29 HK_I3 INPUT
30 HK_I4 INPUT
nb1
43 HK_I5 INPUT
44 HK_I6 INPUT

312 / 866 3DB 16142 JAAA Ed.01
112.11 AUDIOUSER SERV SubD 44pin Female connector


Usage notes:
Tab. 66. AudioUser Serv SubD 44pin female connector
Pin #
Signal Usage
A B C
1 GND
2 COD_TXP (G703)
3 COD_TXN (G703)
nb3
16 GND
17 CC_RXP (V11)
18 CC_RXN (V11)
31 GND
32 CC_TXP (V11)
33 CC_TXN (V11)
nb3
4 COD_RXP (G703)
5 COD_RXN (G703)
6 GND
19 RX_CKN (V11)
nb3
20 RX_CKP (V11)
21 GND
34 CC_TCKP (V11)
nb3
35 CC_TCKN (V11)
36 GND
7 RX_ASY (RS232) nb3
8 GND
9 GND
22 TX_ASY (RS232) nb3

3DB 16142 JAAA Ed.01 313 / 866
Pin #
Signal Usage

A B C

23 GND
24 GND
37 GND
38 GND
39 GND
10 1WEOW_IN_P (from user+) (Analog)
nb1
11 1WEOW_IN_N (from user) (Analog)
12 GND
25 GND
26 GND
27 GND
40 2EEOW_IN_P (from user+)
nb2
41 2EEOW_IN_N (from user)
42
13 1WEOW_OUTP (to user+)
nb1
14 1WEOW_OUT_N (to user)
15 GND
28 GND
29 GND
30 GND
43 2EEOW_OUTP (to user+)
nb2
44 2EEOW_OUT_N (to user)

314 / 866 3DB 16142 JAAA Ed.01
112.12 USER SERV SubD 44pin Female connector


Services Protection box, equipment side [position (5) in Fig. 148. on page 301 ]
N.B. this connectors are interconnected to one another in 1+1 configurations only, and only when
the Services Protection box is employed. Thus, there is no customer use for their pins.
Tab. 67. USER SERV SubD 44pin Female connector
Pin #
Signal
A B C
1 GND
2 COD_TXP (G703)
3 COD_TXN (G703)
16 GND
17 CC_RXP (V11)
18 CC_RXN (V11)
31 GND
32 CC_TXP (V11)
33 CC_TXN (V11)
4 COD_RXP (G703)
5 COD_RXN (G703)
6 GND
19 RX_CKN (V11)
20 RX_CKP (V11)
21 GND
34 CC_TCKP (V11)
35 CC_TCKN (V11)
36 GND
7 RX_ASY (RS232)
8 GND
9 GND
22 TX_ASY (RS232)
23 GND
24 GND
37 GND
38 GND

3DB 16142 JAAA Ed.01 315 / 866
112.13 Description of user signals with alternative connectors

112.13.1 E1 signals

As depicted in para.15.3 from page 101 , the E1 Protection Box (Tributary Panel) can or cannot be
present, depending on adopted configuration.
Fig. 149. below shows the connectors used as user interface for E1 signals in above said cases.
N.B. connectors for 1732 E1 can be used only if the 1732 E1 plugin is equipped
Notes for all referenced 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 Chapter 15
on page 69 )
E1 PROTECTION BOX EMPLOYED
1724 E1 18 E1
see Tab. 55. on page 299 see Tab. 53. on page 297
E1 PROTECTION BOX
line side
2532 E1 916 E1
see Tab. 56. on page 300 see Tab. 54. on page 298
E1 PROTECTION BOX NOT EMPLOYED
1732 E1
IDU MAIN UNIT
116 E1
Fig. 149. Alternative connectors for E1 user signal interface

316 / 866 3DB 16142 JAAA Ed.01
112.13.2 Alarms and Housekeeping signals
As depicted in para.15.3 from page 101 and Chapter 18 from page 195 , the Services Protection
Box (Auxiliary Service Panel) can or cannot be present, depending on adopted configuration.
Fig. 150. below shows the connectors used as user interface for Alarms and Housekeeping signals in
above said cases.
SERVICES PROTECTION BOX EMPLOYED
SERVICES PROTECTION BOX

ALM line side
SERVICES PROTECTION BOX NOT EMPLOYED
IDU MAIN UNIT
ALMNMS
Fig. 150. Alternative connectors for Alarms and Housekeeping user signal interface
The pins of Alarms and Housekeeping alternative connectors (pinout in following Tab. 68. ) are divided
in:
3 summarizing discrete alarms equipment outputs (A_1 to A_3); see point [1] on page 318
4 housekeeping controls equipment outputs (HK_O1 to HK_O4); see point [2] on page 319
6 housekeeping alarms equipment inputs (HK_I1 to HK_I6; see point [4] on page 320
1 common wire (COM)
1 ground (GND).
N.B. the SW User Label depicted in Tab. 68. represents the name by which each signal is identified
by the External Points Management (see chapter 312 on page 587 ), and by the Full
Configuration Procedure step N (External Input and Output Points configuration) on page 479

3DB 16142 JAAA Ed.01 317 / 866
Tab. 68. Meaning of Alarms and Housekeeping signals

Pin of Pin of

ALM ALMNMS Signal Direction SW User Label

connector connector
1 12 A_1 OUTPUT FAIL IDU
[1] 2 27 A_2 OUTPUT FAIL ODU CH#1
3 41 A_3 OUTPUT FAIL ODU CH#0
4 10 HK_O1 OUTPUT CPO1

[2]
6 14 HK_I1 INPUT CPI1

[4]
9 COM
see Tab. 65.
10 on page 311 GND
[1] SUMMARIZING DISCRETE ALARMS
The 3 summarizing discrete alarms (equipment outputs) are defined as follows:
A_1 IDU HW Failure alarm ( = IDU Main (or Extension unit) Card fail/missing + Loss of
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 319.

318 / 866 3DB 16142 JAAA Ed.01
[2] HOUSEKEEPING CONTROLS
For the 4 housekeeping controls (equipment outputs), it is possible to choose through CT not only
the manual setting of each one of them, but also the association to one of the system alarms available
in the CT menu lists (including: Major Alarm, Minor Alarm, Loss of Tributaries, Loss of 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. 151. 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).

3DB 16142 JAAA Ed.01 319 / 866
[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 in n
customer
ooo ooo
I3
in 1 out
V4
V3
common (in)
customer
ground
Fig. 152. 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 in n
customer
ooo ooo
I3 in 1 V4
V3
common (in)
customer
ground
Fig. 153. 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.

320 / 866 3DB 16142 JAAA Ed.01
112.13.3 Alternative connectors for Audio, NMS, and User Service Channels signals
As depicted in para.15.3 from page 101 and Chapter 18 from page 195 , the Services Protection
Box (Auxiliary Service Panel) can or cannot be present, depending on adopted configuration.
Fig. 154. below shows the connectors used as user interface for Audio, NMS, and User Service Channels
signals in above said cases.
N.B. Audio, NMS, and User Service Channels can be used only if the Audio + User Service
Channel plugin is equipped.
SERVICES PROTECTION BOX EMPLOYED
SERVICES PROTECTION BOX

line side
NMSV11AUDIO 1 NMSG703AUDIO 2 ESC

see Tab. 59. see Tab. 60. see Tab. 61.
on page 303 on page 304 on page 305
SERVICES PROTECTION BOX NOT EMPLOYED

AUDIOUSER SERV
IDU MAIN UNIT
ALMNMS
Fig. 154. Alternative connectors for Audio, NMS, and User Service Channels user signal interface

3DB 16142 JAAA Ed.01 321 / 866
112.13.4 NMS V11 Audio 1 signals

With reference to Fig. 154. on page 321 , the pins of NMSV11+Audio1 alternative connectors (pinout

in following Tab. 69. ) are divided in:

9 pins dedicated to NMS
and 4 pins dedicated to EOW analog party line.
[1] NMS V11 signals

The NMS V11 is a 64Kb/s PPP channel; 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.
At SW level, the NMS V11 channel can be defined by:
Step I of Full Configuration Procedure: see page 472 (TMNV11)

Craft Terminal screen described in para.38.2.4.4 on page 542 (V11)
[2] Audio 1 signals

Audio1 signals belong to the EOW party line system. Outputs can be squelched by CT/OS selection.
For details, refer to para.18.3.1 and para.18.3.2 on pages 208 to 209
Tab. 69. Signals for NMSV11+Audio1

Pin of
Pin of
connector on
connector on IDU Main
Protection Box
AUDIOUSER
NMSV11AUDIO 1 ALMNMS Description
SERV
1 17 RS422 data in (+)
2 20 RS422 clock in (+)
3 32 RS422 data out (+)
4 34 RS422 clock out (+)
5 16 GND NMS
6 10 Audio1 signal from user (+)
7 13 Audio1 signal to user (+)
8 9 GND Audio
9 18 RS422 data in ()
10 19 RS422 clock in ()
11 33 RS422 data out ()
12 35 RS422 clock out ()
13 11 Audio1 signal from user ()
14 14 Audio1 signal to user ()
15 Not used

322 / 866 3DB 16142 JAAA Ed.01
112.13.5 NMS G703 Audio 2 signals
With reference to Fig. 154. on page 321 , the pins of NMSG703+Audio2 alternative connectors (pinout
in following Tab. 70. ) are divided in:

5 pins dedicated to NMS

and 4 pins dedicated to EOW analog party line.
[1] NMS G703 signals

The NMS G703 is a 64Kb/s PPP channel; 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.
At SW level, the NMS_V11 channel can be defined by:
Step I of Full Configuration Procedure: see page 472 (TMNG703)

Craft Terminal screen described in para.38.2.4.4 on page 542 (G703)
[2] Audio 2 signals

Audio2 signals belong to the EOW party line system. Outputs can be squelched by CT/OS selection.
For details, refer to para.18.3.1 and para.18.3.2 on pages 208 to 209
Tab. 70. Signals for NMSG703+Audio2

Pin of
Pin of
connector on
connector on IDU Main
Protection Box
AUDIOUSER
NMSG703AUDIO 2 ALMNMS Description
SERV
1 4 G703 data in (+)
2 Not used
3 2 G703 data out (+)
4 Not used
5 1 GND NMS
6 40 Audio2 signal from user (+)
7 43 Audio2 signal to user (+)
8 39 GND Audio
9 5 G703 data in ()
10 Not used
11 3 G703 data out ()
12 Not used
13 41 Audio2 signal from user ()
14 44 Audio2 signal to user ()
15 Not used

3DB 16142 JAAA Ed.01 323 / 866
112.13.6 User service channels signals

With reference to Fig. 154. on page 321 , the pins of the alternative connectors (pinout in following

Tab. 71. ) are the interface for the User service channels

Tab. 71. Signals for User service channels
Pin of AUDIOUSER
Pin of ESC connector
SERV connector Signal Direction
(Protection Box)
(IDU Main)
2 4 COD_RX + INPUT
9 5 COD_RX INPUT
3 2 COD_TX + OUTPUT
10 3 COD_TX OUTPUT
4 7 RX_ASY INPUT
11 22 TX_ASY OUTPUT
5 17 CC_RX + INPUT
12 18 CC_RX INPUT
6 20 RX_CK + BID
13 19 RX_CK BID
7 32 CC_TX + OUTPUT
14 33 CC_TX OUTPUT
8 34 CC_TCK + OUTPUT
15 35 CC_TCK OUTPUT
1 1 16 31 GND /
By:
Step M of Full Configuration Procedure on page 478
Craft Terminal screen described in para.38.4.3 on page 556
the user service channel can be used in one of the following modes:
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 above.

The use of signals is depicted in following figures Fig. 155. to Fig. 158.

324 / 866 3DB 16142 JAAA Ed.01
[1] V11 codirectional mode
USER SERVICE CHANNEL V11 CODIR

< USER RADIO >
USER EQUIPMENT IDU AWY
CC_RX +
DATA CC_RX
RX_CK +
CLOCK RX_CK
CC_TX +
CC_TX DATA
CC_TCK +
CC_TCK CLOCK
Fig. 155. User service channel: V11 codirectional interface
[2] V11 contradirectional DCE mode

Note that V11 contradirectional DTE mode (as the userequipment interface) is not supported.
USER SERVICE CHANNEL V11 CONTRADIR DCE
< USER RADIO >
USER SUBORDINATE IDU AWY

EQUIPMENT (DTE)
DCE
CC_RX +
DATA CC_RX
RX_CK +
CLOCK RX_CK
CC_TX +
CC_TX DATA
CC_TCK +
CC_TCK CLOCK
Fig. 156. User service channel: V11 contradirectional interface

3DB 16142 JAAA Ed.01 325 / 866
[3] G.703 mode
USER SERVICE CHANNEL G.703

< USER RADIO >
COD_RX+
COD_RX
DATA&CLOCK
COD_TX+
DATA&CLOCK
COD_TX
Fig. 157. User service channel: G.703 interface
[4] V24/V28 mode
USER SERVICE CHANNEL V28
< USER RADIO >
RX_ASY
DATA&CLOCK
TX_ASY DATA&CLOCK
Fig. 158. User service channel: V24/V28 interface

326 / 866 3DB 16142 JAAA Ed.01
113 DESCRIPTION OF INTERCONNECTION AND SIGNAL CABLES
The use of these cables is explained in:

para.32.1 on page 410 (PCtoNE physical connection)
Tab. 72. List of interconnection and signal cables

DESCRIPTION
Cable
M1 M2 M3 M4 on page
(sorted by P/N) Type Length
n pin n pin n pin n pin
1AB054120027 RS232 CT cable (see Tab. 48. on page 292 )
3CC07759ABAA SubD 37 16 x BNC 75 Ohm 2m 329
3CC07885ABAA SubD 37 16 x1.6/5.6 75 Ohm 2m 330
3CC13477AAxx Light service kit cable (see para.42.12 on page 720 )
3CC52115ABAA SubD 44 Free/15m 331
3CC52116AAAA SubD 44 44 0.5m 332
3CC52117ABAA SCSI 68 68 Free/15m 333
3CC52118AAAA SCSI 68 68 1m 334
3CC52119AAAA SubD 15 9 9 1.6m
335
3CC52120AAAA SubD 15 9 9 6.4m
3CC52121AAAA SubD 37 9 25 1m 336
3CC52130AAAA SubD 15 9 1.6m
337
3CC52131AAAA SubD 15 9 6.4m
3CC52132AAAA SubD 15 9 1m 338
3CC52133AAAA SCSI 68 Terminal strip (Compax) 1.1m 339
SCSI SCSI SubD SubD
3CC52134AAAA 1m 341
SubD 68 37 37
RJ45 Eth
3CC52141Axxx 8 8 115m
Direct
343
RJ45 Eth
3CC52142Axxx 8 8 15m
Cross
3CC52143ABAA SubD 44 44 1.6m
344
3CC52143ACAA SubD 44 44 6.4m
3CC52150AAAA SCSI 68 68 1.6m
345
3CC52150ABAA SCSI 68 68 6.4m
SCSI SCSI Terminal strip
3CC52157AAAA Y cable 1.1m 346
68 68 (Compax)
3DB05594AAAA SubD 15 15m 348
3DB05922AAxx SubD 15 15 1.6m
349
3DB05923AAxx SubD 15 15 6.4m

3DB 16142 JAAA Ed.01 327 / 866
Tab. 72. List of interconnection and signal cables

DESCRIPTION
Cable

M1 M2 M3 M4 on page

(sorted by P/N) Type Length
n pin n pin n pin n pin
3DB10063AAAA SubD 15 9 9 1.6m
350
3DB10064AAAA SubD 15 9 9 6.4m
3DB10087AAAA SubD 15 15 1.6m 351
3DB10088AAAA SubD 15 15 6.4m 351
3DB10089AAAA SubD 15 9 1.6m
352
3DB10091AAAA SubD 15 25 1.6m
353
3DB10092AAAA SubD 15 25 6.4m
354
3DB10095AAAA SubD 15 15 1.6m
355
3DB10096AAAA SubD 15 15 6.4m
3DB10100AAAA SubD 37 9 9 9 1m 355
3DB10101AAAA SubD 15 15 357
3DB16126ABAA SCSI 100 100 18cm 358

328 / 866 3DB 16142 JAAA Ed.01
113.1 Cable 3CC07759ABAA Cable for distributor BNC 8 x 2 Mbit/s (L= 2m)
CONNECTION TABLE
N5 pin SubD37 M1 BNC 75 Ohm Print indication Cable N5 ST212
2 J1 I1 1
3 J2 I2 3
4 J3 I3 5
5 J4 I4 7
6 J5 I5 9
7 J6 I6 11
8 J7 I7 13
9 J8 I8 15
12 J9 O1 2
13 J10 O2 4
14 J11 O3 6
15 J12 O4 8
16 J13 O5 10
17 J14 O6 12
18 J15 O7 14
19 J16 O8 16
N.B. pins 1, 10, 11 free
N.B. pins 20 to 37 are connected to covers shield

3DB 16142 JAAA Ed.01 329 / 866
113.2 Cable 3CC7885ABAA Cable for distributor 1.6/5.6 8 x 2 Mbit/s (L= 2m)

Print information
N.B. pins 1, 10, 11 free
N.B. pins 20 to 37 are connected to covers shield

330 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
M1
113.3 Cable 3CC52115ABAA (L= 15m)
CONNECTION TABLE

9400AWY Rel.2.1 SWP 9400AWY V2.1.3
331 / 866
113.4 Cable 3CC52116AAAA (L= 0.5m)

CONNECTION TABLE M1 M2
Pair Number Pin Pair Number Pin
1 24
1 13
6 31
2 25
2 14
3 26
4 27
3 15
5 42
7 28
4 16
8 29
9 32
5 17
12 33
10 34
6 18
11 35
13 36
7 19
14 39
15 37
8 20
30 38
16 40
9 21
21 41
17 43
10 22
18 44
19 45 Not connected
11 23
20 46 Not connected
22 47 Not connected
12 24
23 48 Not connected

332 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
113.5 Cable 3CC52117ABAA (L= 15m)

9400AWY Rel.2.1 SWP 9400AWY V2.1.3
333 / 866
334 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
113.6 Cable 3CC52118AAAA (L= 1m)

USER MANUAL
113.7 Cable 3CC52119AAAA (L= 1.6) or 3CC52120AAAA (L= 6.4m)
NMS ESC CROSSED CABLE

CONNECTION TABLE (M1M2M3)

M1 M3 (AUDIO)
M2 (NMS) (9pins) Pair colors Pair number
(15pins) (9pins)
1 8 Blue
1
9 4 White
3 1 Violet
2
11 6 Turquoise
2 5 Orange
3
10 9 White
4 7 Violet
4
12 2 Turquoise
5 to connect to shielded cable braid (GND) Green
5
To cut White
6 8 Violet
6
13 4 Turquoise
7 1 Brown
7
14 6 White
To cut Violet
8
To cut Turquoise

3DB 16142 JAAA Ed.01 335 / 866
113.8 Cable 3CC52121AAAA (L= 1m)

LUX 50 ESCESC / ALARMS ADAPTER

M1 (37pins) M2 (9pins) M3 (25pins) Pair number
1 8
1
20 4
2 9
2
21 5
4 1
3
23 6
5 2
4
24 7
11 No connect
3 11
5
6 12
22 no connect 13 no connect
25 no connect 24 no connect
7 7
6
26 20
8 8
7
27 21
9 9
8
28 22
10 10
9
29 23
14 1
10
15 2
32 14
11
33 15
34 16
12
16 3
17 4
13
18 5
35 17
14
36 18
37 19
15
19 6
12 3
16
30 25

336 / 866 3DB 16142 JAAA Ed.01
113.9 Cable 3CC52130AAAA (L= 1.6m) or 3CC52131AAAA (L= 6.4m)
CONNECTION TABLE
M1 Pair colors Pair number M2
7 Blue 1
1
14 White 6
8 Orange 2
2
15 White 7
5 Green 8
3
12 White 4
6 Brown 9
4
13 White 5
1 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
To cut Orange To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

3DB 16142 JAAA Ed.01 337 / 866
113.10 Cable 3CC52132AAAA (L= 1m)

M1 M2
CONNECTION TABLE
12 Blue 9
1
24 White 5
13 Orange 8
2
25 White 4
11 Green 1
3
23 White 6
10 Brown 2
4
22 White 7
6 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

338 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
113.11 Cable 3CC52133AAAA SCSI68 120 Ohm
DETAIL
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
339 / 866
340 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
Note: pins 1, 34, 35 and 68 of M1 connected to GND

USER MANUAL
113.12 Cable 3CC52134AAAA Cord 120 Ohm SCSI68/DSUB37 2 x 16 pairs

3DB 16142 JAAA Ed.01 341 / 866
N.B. the two GND ground wires of the two cables are connected to:
pins 1, 34, 35 and 68 of M1
pins 10 of M1 and M2

342 / 866 3DB 16142 JAAA Ed.01
113.13 RJ45RJ45 Cat.5e Ethernet cables
113.13.1 RJ45RJ45 Cat.5e Direct Ethernet cables 3CC52141Axxx
Code % 3CC52141AAAA 3CC52141ABAA 3CC52141ACAA

Length (m) % 1 5 15
CONNECTION TABLE (Direct Ethernet cables)

Connector Connector
Pin assign. According to TIA/EIA 568B
A B
WhiteBlue (WBL) 5 5
Pair 1
Blue (BL) 4 4
WhiteOrange (WO) 1 1
Pair 2
Orange (O) 2 2
WhiteGreen (WG) 3 3
Pair 3
Green (G) 6 6
WhiteBrown (WBR) 7 7
Pair 4
Brown (BR) 8 8
113.13.2 RJ45RJ45 Cat.5e Cross Ethernet cables 3CC52142Axxx
Code % 3CC52142AAAA 3CC52142ABAA

Length (m) % 1 5
CONNECTION TABLE (Cross Ethernet cables)

Connector Connector
Pin assign. According to IEEE 802.3
A B
WhiteBlue (WBL) 5 8
Pair 1
Blue (BL) 4 7
WhiteOrange (WO) 1 3
Pair 2
Orange (O) 2 6
WhiteGreen (WG) 3 1
Pair 3
Green (G) 6 2
WhiteBrown (WBR) 7 4
Pair 4
Brown (BR) 8 5

3DB 16142 JAAA Ed.01 343 / 866
344 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

113.14 Cable 3CC52143ABAA (L= 1.6m) or 3CC52143ACAA (L= 6.4m)
USER MANUAL
113.15 Cables 3CC52150AAAA (L=1.6 m) and 3CC52150ABAA (L=6.4 m)
SCSI68/SCSI68 M/M CROSS

3DB 16142 JAAA Ed.01 345 / 866
113.16 Cable 3CC52157AAAA 2 SCSI MALE TO 4 TERMINALS MODULES

DETAIL

346 / 866 3DB 16142 JAAA Ed.01
USER MANUAL
Note: pins 1, 34, 35 and 68 of M1/M2 connected to GND

9400AWY Rel.2.1 SWP 9400AWY V2.1.3
347 / 866
113.17 Cable 3DB05594AAA SubD 15pin

M1
CONNECTION TABLE
M1 Pairs color Pair N5
2 Blue
1
9 White
3 Violet
2
10 Turquoise
4 Orange
3
1 White
5 Violet
4
12 Turquoise
6 Green
5
13 White
7 Violet
6
14 Turquoise
8 Brown
7
15 White
11 Violet
8
N.B.3 Turquoise
N.B.3 Cut color turquoise wire, not connected, pair n8

348 / 866 3DB 16142 JAAA Ed.01
113.18 Cable 3DB05922AAAA (L= 1.6m) or 3DB05923AAAA (L= 6.4m)
CONNECTION TABLE
1 Blue 3
1
9 White 11
2 Violet 4
2
10 Turquoise 12
3 Orange 1
3
11 White 9
4 Violet 2
4
12 Turquoise 10
5 Green 5
5
To cut White To cut
6 Violet 7
6
13 Turquoise 14
7 Brown 6
7
14 White 13
8 Violet 8
8
To cut Turquoise To cut

3DB 16142 JAAA Ed.01 349 / 866
113.19 Cable 3DB10063AAAA (L= 1.6) or 3DB10064AAAA (L= 6.4m)

NMS INTERFACE AWY MELODIE IDU

M1 M2 (NMS) M3 (AUDIO)
Pair colors Pair number
(15pins) (9pins) (9pins)
1 8 Blue
1
9 4 White
3 1 Violet
2
11 6 Turquoise
2 9 Orange
3
10 5 White
4 2 Violet
4
12 7 Turquoise
5 to connect to shielded cable braid (GND) Green
5
To cut White
6 8 Violet
6
13 4 Turquoise
7 1 Brown
7
14 6 White
To cut Violet
8
To cut Turquoise

350 / 866 3DB 16142 JAAA Ed.01
CONNECTION TABLE
2 Blue 3
1
9 White 10
3 Violet 2
2
10 Turquoise 9
4 Orange 11
3
1 White 1
5 Violet 7
4
12 Turquoise 14
6 Green 8
5
13 White 15
7 Violet 5
6
14 Turquoise 12
8 Brown 6
7
15 White 13
11 Violet 4
8
To cut Turquoise To cut

3DB 16142 JAAA Ed.01 351 / 866

CONNECTION TABLE
7 Blue 1
1
14 White 6
8 Orange 7
2
15 White 2
5 Green 8
3
12 White 4
6 Brown 9
4
13 White 5
1 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

352 / 866 3DB 16142 JAAA Ed.01
CONNECTION TABLE
5 Blue 13
1
12 White 25
6 Orange 12
2
13 White 24
7 Green 11
3
14 White 23
8 Brown 22
4
15 White 10
To cut Grey To cut
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

3DB 16142 JAAA Ed.01 353 / 866

CONNECTION TABLE
7 Blue 6
1
14 White 1
8 Orange 7
2
15 White 2
5 Green 4
3
12 White 8
6 Brown 5
4
13 White 9
1 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

354 / 866 3DB 16142 JAAA Ed.01
CONNECTION TABLE
2 Blue M211
1
9 White M23
4 Orange M29
2
11 White M21
6 Green M210
3
13 White M22
3 Brown M15
4
10 White M112
5 Grey M13
5
12 White M110
1 Blue M25
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut
113.25 Cable 3DB10100AAAA (L= 1m)

3DB 16142 JAAA Ed.01 355 / 866
CONNECTION TABLE (M1M2)
M1 (37pins) Pair colors Pair number M2 (9pins)

1 Blue 1
1

20 White 6

2 Orange 2
2
21 White 7
4 Green 8
3
23 White 4
5 Brown 9
4
24 White 5
18 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut
7 Blue 1
1
26 White 6
8 Orange 2
2
27 White 7
10 Green 8
3
29 White 4
11 Brown 9
4
30 White 5
18 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut
13 Blue 1
1
32 White 6
14 Orange 2
2
33 White 7
15 Green 8
3
34 White 4
16 Brown 9
4
35 White 5
18 Grey 3
5
To cut White To cut
To cut Blue To cut
6
To cut Red To cut
7
To cut Red To cut
To cut Green To cut
8
To cut Red To cut

356 / 866 3DB 16142 JAAA Ed.01
113.26 Cable 3DB10101AAAA (Adapter ESC/NMS V1)
CONNECTION TABLE
M1 M2
5 1
12 9
6 2
13 10
7 3
14 11
8 12
15 4
1 5

3DB 16142 JAAA Ed.01 357 / 866
113.27 Cable 3DB16126ABAA SCSI100 wire for 1+1

N.B. No pin usage by customer.

END OF HARDWARE INSTALLATION HANDBOOK
a) END OF HARDWARE INSTALLATION HANDBOOK

358 / 866 3DB 16142 JAAA Ed.01
Part B: Technical Handbook
This handbook is the part B of the whole User Manual.
N.B. Only for paper copy: cross references to page numbers 358 are references to the part A
(Hardware Installation Handbook). Such references are essential for information completion,
so that part A must be always available together with this part B.
Contents Page
SECTION 2 : SYSTEM DESCRIPTION 360
SECTION 3 : NE MANAGEMENT BY SOFTWARE APPLICATIONS 401
SECTION 4 : INSTALLATION AND COMMISSIONING 665
SECTION 5 : MAINTENANCE AND UPGRADE 737
SECTION 6 : APPENDICES 827

TECHNICAL HANDBOOK
3DB 16142 JAAA Ed.01 359 / 866
SECTION 2: SYSTEM DESCRIPTION
This section provides the equipment description (at system, IDU and ODU levels), introduces the basic
information regarding the 9400AWY Rel.2.1 HW architecture, and gives its technical characteristics.
Chapter 21 System overview

It gives the 1st level description of the equipment architecture, and system 361
configurations of the 9400AWY Rel.2.1.
Chapter 22 Technical specifications

389
It describes the technical characteristics of the 9400AWY Rel.2.1.

SYSTEM DESCRIPTION
360 / 866 3DB 16142 JAAA Ed.01
21 SYSTEM OVERVIEW
This chapter gives the 1st level description of the equipment architecture, features, and system
configurations of the 9400AWY Rel.2.1 V2.1.3:
Subject On page
Main characteristics 362
Equipment architecture 364
Splitmount architecture 364
IDU (Indoor Unit) 367
ODU (Outdoor Unit) 370
ODU and antenna configurations 372
ODU 1+0 and 1+1 configurations and applications 372
Application and implementation of ODU 1+1 HSB single antenna 373
Applications and implementation of ODU 1+0 374
IDUODU cable 376
System configurations 377
Available system configurations 377
1+0 Unprotected configurations 377
1+1 Protected Configurations 378
Detailed IDU block diagrams 384
IDUODU and station compatibility 387
Provisioning of equipment items (summary) 388
N.B. This chapter deals with the hardware equipment architecture only. For the description of the
software applications for the NE management, refer to the SECTION 3 from page 401

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 361 / 866
21.1 Main characteristics

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) system, providing the

baseband processing and tributaries interfaces as well as service channel and supervision, and an
Outdoor Unit (ODU ) system.
IDU and ODU are connected with one or two standard coaxial cable(s) (max length specified in
para.17.1.1 on page 189 ) carrying the main traffic, the remote power supply voltage for the ODU and
auxiliary information.
As shown in Fig. 159. 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 RADIO LINK
STATION A STATION B
(ULS NE A) ETSI RADIO (ULS NE B)
ODU ODU
CH1 CH1
IDUODU IDUODU
ODU ODU
cable CH1 CH0 CH0 cable CH1
IDUODU IDUODU
ETSI PDH cable CH0 cable CH0 ETSI PDH
ETHERNET ETHERNET
SERVICE CH. SERVICE CH.
IDU SUPERVISION IDU
NETWORK
Fig. 159. 9400AWY radio link
ULS NE has the aim to multiplexer/demultiplexer the main tributaries:

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. 73. :
Tab. 73. Tributaries and modulations

Max Ethernet
Market Max PDH Tributaries Radio Modulation
Tributaries
2xE1 4 x GE 4QAM
4xE1 4 x GE 4QAM
ETSI 8xE1 4 x GE 4QAM / 16QAM
16xE1 4 x GE 4QAM / 16QAM
32xE1 0 16QAM

SYSTEM DESCRIPTION
362 / 866 3DB 16142 JAAA Ed.01
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.
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.
Signal Protection (1+1 configurations only)

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:
the Radio Protection Switching (RPS) is standard in 1+1 configurations
the Equipment Protection Switching (EPS) is optional in 1+1 configurations:
1+1 configurations with EPS are also named fully protected
1+1 configurations without EPS are also named radio protected

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 363 / 866
21.2 Equipment architecture

21.2.1 Splitmount architecture

The 9400AWY system has been designed in a split mount architecture. As shown in Fig. 160. on page
365 , it consists of the Indoor Unit (IDU) and the Outdoor Unit (ODU).
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 para.16.7 on page 175

SYSTEM DESCRIPTION
364 / 866 3DB 16142 JAAA Ed.01
9400AWY R.2.1 (1+0) SPLITMOUNT SYSTEM
ODU Ch#1
Antenna
ODU
IDUODU cable
NE
DISTRIBUTOR SHELF (optional) ULS
D
IDU
IDU MAIN UNIT Ch#1
9400AWY R.2.1 (1+1) SPLITMOUNT SYSTEM
for possible ODU (1+1)

configurations
see Fig. 161. on page 366
ODU
IDUODU cables
NE
ULS
DISTRIBUTOR SHELF (optional)
C D
IDU
B
Legend:
D SERVICE PROTECTION BOX (optional)
C E1 PROTECTION BOX (optional)
B IDU MAIN UNIT Ch#1
A IDU EXTENSION UNIT Ch#0
Fig. 160. 9400AWY R.2.1 splitmount system

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 365 / 866
Antenna CH 0 Antenna CH 1

ODU CH 0 ODU CH 1
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
ODU (1+1) HSB with one antenna
N.B. this drawing is an example referred to the coupler used in

1338 GHz configurations.
Double Polar Antenna
ODU CH 0 ODU CH 1
ODU (1+1) FDAP with one double polar external antenna
Fig. 161. Possible configurations of ODU (1+1)

SYSTEM DESCRIPTION
366 / 866 3DB 16142 JAAA Ed.01
21.2.2 IDU (Indoor Unit)
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. 160. on page 365 , up to 2 active subracks (the Main IDU unit and the Extension IDU
unit) and some additional passive boxes are used as basic elements to build the following configurations:
1+0: this configuration includes:

one Main IDU unit
one optional Service Protection Box
one or two optional IDU Distributor Shelves
and necessary interconnection cables.
Fig. 175. on page 384 shows the block diagram.
1+1: this configuration includes:

one Main IDU unit
one Extension IDU unit
one optional E1 Protection Box
one or two optional IDU Distributor Shelves
and necessary interconnection cables.
The radio protected is the standard 1+1 configuration
The block diagrams are shown in Fig. 176. on page 385 (radio protected) and Fig. 177. on page
386 (fully protected).
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 Licence String
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:

into the Main IDU unit,
and (only in case of required EPS for E1 tributaries in 1+1 fully protected
configurations) also into the IDU Extension unit
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)
only in case of fully protected configurations (EPS for E1 tributaries and for Service Channels
required):
the protection of E1 signals at line side is achieved by the E1 Protection Box or by suitable
E1 Protection Ycable(s)
provided that the AUDIO + USER SERVICE CHANNEL plugin is equipped, the
protection of Service Channels signals at line side is achieved by the Service Protection
Box.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 367 / 866
[1] IDU Main 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.112.2 on page 289 .
[2] IDU Extension 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%
No Fans Unit are foreseen inside the 9400AWY IDU units.
[4] Flash Card and Licence String

A Flash Card (containing the system software, the Licence String, and the NE configuration) is always
plugged onto the Main unit. The Licence String allows flexibility in choosing user interfaces and
modulation.
[5] Protection Boxes and E1 Protection Ycable(s)

The E1 Protection Box and Service Protection Box are passive components shown in Fig. 162.
and Fig. 163. below. Their equipping rules are described:
for 1+1 configurations, in Tab. 76. on page 379
for 1+0 configurations, in para.21.3.2 on page 377
In 1+1 fully protected configurations, they perform the splitting functions of E1 and User Service
Channel signals from/to the Main IDU and Extension IDU units and from/to the User lines, as shown
in Fig. 177. on page 386 . In case the 120 W distributor is employed, the E1 Protection Ycable(s)
is/are used instead of the E1 Protection Box (that is used together with the 75 W distributors).
user line side connectors equipment side connectors
Fig. 162. E1 Protection box
user line side connectors equipment side connectors
Fig. 163. Service Protection Box

SYSTEM DESCRIPTION
368 / 866 3DB 16142 JAAA Ed.01
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.112.4 on page 296 (E1 Protection Box) and to para.112.5 on page 301
(Service Protection Box).
Synonyms for Protection Boxes

In this manual, or in other related documents:
Patch Panel may be found as synonym of E1 Protection Box or Service Protection Box
Tributary Panel may be found as synonym of E1 Protection Box
Auxiliary Service Panel may be found as synonym of Service Protection Box
[6] 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.
[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 57 on page 797.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 369 / 866
21.2.3 ODU (Outdoor Unit)

a) ODU types:

The following ODU types are supported:

ODU 32MbV1 (max 16E1 capacity)
For characteristics, please refer to para.111.2 from page 258
The software autodiscovers the type of ODU connected to the IDU, transparently for the operator.
The compatibility between IDU & ODU in a station, as well that between the two stations of the radio
hop, are specified in para.21.3.5 on page 387
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, with the branching (diplexer) internal to the ODU cabinet; the only differences among the
frequency bands are related to the diplexer and the RF section;
another, where ODU is composed by two independent units: the branching (diplexer) and the
RF section (transceiver).
The ODU presents one output port at which a single polarization full integrated antenna 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. 164. below):
Fig. 164. ODU block diagram
[1] Modem: It consists of a baseband part and an IF part. The main functions are:
Cable interface: DC splitting, echo cancellation, clock recovery
HDB3 coding/decoding
Modulation and demodulation
Digital to analog conversion
Analogue filtering
Upconversion in Tx side in the frequency range of 1 GHz to 2.1 GHz (n.b.1)
Downconversion in Rx side from 675 MHz to base band (n.b.1)
Control function for hardware configuration and dialog with the IDU.

SYSTEM DESCRIPTION
370 / 866 3DB 16142 JAAA Ed.01
[2] FrontEnd. The main functions are:
AGC IF amplification
Upconversion to the RF Tx channel frequency

Transmit power control range of 30 dB

RF loopback (n.b.2)
Double mixers at Rx side (the frequency of the signal sent to the modem board is 675 MHz
whatever the frequency band and shifter).
[3] Synthesizer unit (n.b.1)
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
(n.b.1): in ODU V2 types, these functions are included in the Front End subunit
(n.b.2): WARNING: this feature is available on ODU V1
[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.
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.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 371 / 866
21.2.4 ODU and antenna configurations

21.2.4.1 ODU 1+0 and 1+1 configurations and applications

Tab. 74. ODU 1+0 and 1+1 configurations and applications
9400AWY ODU RF
ODU ANTENNA RF channeling
configuration coupler
1 x ODU 1+0 NO 1 x antenna single polar
1+0 Nonprotected
Usage example in Fig. 166. on page 374
1 x ODU 1+1
1/10 dB
(2 ODUs at same 1 x antenna single polar
1+1 HSB asymmetric
frequency)
single antenna
Applications and advantages: protection against failures
2 x ODUs 1+0 2 x antennas single
NO
at same frequency polar
1+1 HSB SD Applications and advantages: protection against failures;
improvement of performances versus multipath propagation
1 x antenna double
2 x ODUs 1+0
NO polar (nonintegrated
1+1 FD AP at different frequencies only)
2 x antennas single
2 x ODUs 1+0 polar in AP
NO
at different frequencies configuration (same or
crossed polarization) OR
1+1 FD DA
Applications and advantages: protection against failures;
improvement of performances versus multipath propagation
Legend:
AP: Alternate Polar
DA: Double Antenna
FD: Frequency diversity
HSB: Hot Stand By
SD: Space Diversity

SYSTEM DESCRIPTION
372 / 866 3DB 16142 JAAA Ed.01
21.2.4.2 Application and implementation of ODU 1+1 HSB single antenna
This ODU configuration can be used only in association of an IDU 1+1 , as shown in Fig. 165. below:
ODU CH 1 RF
IDUODU Coupler
cable
MODEM IF RF
IDU 1+1
only one RT 1:10
transmits
IDU MAIN UNIT
ODU CH 0
IDU EXTENSION UNIT IDUODU
cable
MODEM IF RF
Fig. 165. ODU 1+1 HSB single antenna
The two ODU transceivers are connected to one antenna by means of a 1dB /10 dB asymmetrical RF
coupler; 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).
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).
[1] Antenna configurations

The ODU 1+1 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 antenna configuration, the pole mounting, and the nose adapter
for the RF coupler, are delivered with the antenna.
a separated antenna, if larger diameters are necessary. In this case, the RF coupler is mounted
on a not integrated antenna pole mounting provided with nose adapter (different Logistical
Items depending on the waveguide dimension), and the antenna is interconnected by a flextwist
directly to the RF coupler.
[2] RF couplers
Different couplers are available, according to frequency, as described in para.111.3 on page 281
[3] Example figures
Frequency range GHz Antenna Example figures

78
1338
The RF coupler is fixed on the pole mounting with 4 catches. The 2 ODUs are connected to the RF
coupler with their 4 catches.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 373 / 866
21.2.4.3 Applications and implementation of ODU 1+0

The ODU 1+0 configuration is used in these system configurations:

[1] 9400AWY 1+0
as shown in Fig. 166. below (1 x ODU 1+0 is necessary).
ODU CH 1
IDU 1+0
IDUODU
cable
IDU MAIN UNIT MODEM IF RF
Fig. 166. 1 x ODU 1+0 used in 9400AWY 1+0 system
[2] 9400AWY 1+1 HSB Space Diversity

as shown in Fig. 167. below (2 x ODUs 1+0 are necessary). With respect to ODU 1+1 HSB single
antenna, this configuration adds a natural Space Diversity, and improves the link budget avoiding
coupler losses on the standby path.
ODU CH 1
IDUODU
cable
MODEM IF RF
IDU 1+1
only one RT
transmits
IDU MAIN UNIT
ODU CH 0
cable
MODEM IF RF
Fig. 167. 2 x ODUs 1+0 used in 9400AWY 1+1 HSB Space Diversity system
[3] 9400AWY 1+1 Frequency Diversity Double Antenna Alternate Polar

as shown in Fig. 168. below (2 x ODUs 1+0 are necessary). This configuration allows a
polarization diversity, and avoids coupler losses on the standby path.
ODU CH 1
IDUODU
cable
MODEM IF RF
IDU 1+1
both RTs AP
transmit
IDU MAIN UNIT
ODU CH 0
cable
MODEM IF RF
Fig. 168. 2 x ODU 1+0 used in 9400AWY 1+1 Frequency Diversity Double Antenna Alternate
Polar system

SYSTEM DESCRIPTION
374 / 866 3DB 16142 JAAA Ed.01
[4] 9400AWY 1+1 Frequency Diversity One Antenna Alternate Polar
as shown in Fig. 169. below (2 x ODUs 1+0 are necessary). This configuration allows a
polarization diversity, minimizes the antenna, and avoids coupler losses on the standby path.
ODU CH 1
IDUODU
cable
MODEM IF RF
IDU 1+1
both RTs
IDU MAIN UNIT transmit
ODU CH 0
cable
MODEM IF RF
Fig. 169. 2 x ODU 1+0 used in 9400AWY 1+1 Frequency Diversity One Antenna Alternate Polar
system
[5] Antenna configurations for ODU 1+0
The ODU 1+0 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, as shown in figures on page 151 ; in Full Integrated antenna configuration, the
pole mounting and the nose adapter (for ODU RF coupling) is delivered with the antenna. The
modification of the polarization is obtained by rotating the ODU and the nose of the antenna.
a separated antenna, if larger diameters are necessary. In this case, the ODU is mounted on
a not integrated antenna pole mounting provided with nose adapter (different Logistical Items
depending on the waveguide dimension), and the antenna is interconnected by a flextwist
directly to the antennaside flange of the nose adapter.
N.B. The configuration of point [4] above can employ only a separated antenna.
[6] Example figures
Frequency range GHz Antenna Example figures

all Fig. 63. and Fig. 64.
not integrated
on page 155
The ODU is connected to the pole mounting with its 4 catches.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 375 / 866
21.2.5 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. 75. 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.22.5 on page
397.

SYSTEM DESCRIPTION
376 / 866 3DB 16142 JAAA Ed.01
21.3 System configurations
21.3.1 Available system configurations

The configurations available are:

Unprotected configurations (1+0)
Protected configurations (1+1)
The (2+0) configuration is not supported.
N.B. for the detailed description of station layouts and equipment interconnections:
at IDU level, refer to Chapter 15 from page 69
at ODU level, refer to Chapter 16 from page 137
21.3.2 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.
one Indoor Unit (MAIN IDU unit) incorporating the baseband processing and offering tributaries
interfacing as well as service channel and supervision.
one/two optional IDU Distributor Shelf/ves
one IDUODU coaxial cable
in 1+0 configurations, the need for the installation of the Service Protection Box depends on how
the signals present on the following IDUMAIN units connectors must be connected:
ALMNMS (see para.112.10 on page 311 )
AUDIOUSER SERV (see para.112.11 on page 313 ), present only when the Audio + User
Service Channel plugin is equipped
N.B. in case of network interconnections for NMS channel and EOW audio continuity, the
Service Protection box is practically always required, and the connections on IDU
ALMNMS connector must be done as specified in Chapter 18 from page 195
Fig. 170. below shows the generic layout and block diagram of a 1+0 IDU+ODU system.
IDU 1+0
interconnections
DISTRIBUTOR SHELF ODU CH 1

IDUODU
SERVICE cable MODEM IF RF
PROTEC.BOX
IDU MAIN UNIT
Fig. 170. 9400AWY (1+0) IDU + ODU generic layout and block diagram
The possible capacities and modulations depend on:

the IDU capacity (see point [7] on page 369 )
the ODU type and capacity [see point a ) on page 370 ]
and the employed Licence String (see Tab. 85. on page 404 )

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 377 / 866
21.3.3 1+1 Protected Configurations

The protected configurations allow to protect the most critical transmission paths.

Subject On page
Description of protections
Protection types herebelow
Types of protected system configurations
Signal protection with RPS and with/without EPS 379
Protection with both RPS and EPS (fully protected configurations) 380
Static Delay Alignment 381
Protection with RPS and without EPS (radio protected configurations) 381
HSB Tx protection type 382
Setting of protection type and manual commands on protection switches 382
IDU (1+1) configurations 383
21.3.3.1 Description of protections

[1] Protection types
According to the radio and IDU configurations, the following protection types are supported:
Radio Protection Switching (RPS): it is always supported in all the 1+1 configurations (FD and
HSB).
Equipment Protection Switching (EPS, named also Mux/Demux Protection) : it can be
optionally supported in all the 1+1 configurations (FD and HSB) (*);
(*) More precisely, through SW configuration, EPS protection can be excluded.
This implies different IDU hardware equipping rules, as shown in Tab. 76. on page 379
HSB Transmission Protection Switching (TPS): it is always supported in the 1+1 HSB radio
configurations.
[2] Types of protected system configurations
According to the presence of EPS protection, the following protected system configurations are
available:
Type of protected configuration Commercially named also as

1+1 HSB with EPS
Fully protected
1+1 FD with EPS
1+1 HSB without EPS
Radio protected
1+1 FD without EPS
N.B. the HSB and FD protection types depend on the ODU and antenna configurations
employed, and are described, together with their subcases, in para.21.2.4 from page 372
N.B. in this manual with EPS and fully protected are synonyms, as well as without EPS and
radio protected.

SYSTEM DESCRIPTION
378 / 866 3DB 16142 JAAA Ed.01
[3] Signal protection with RPS and with/without EPS
The following table resumes the protection types referred to the signals involved, and the hardware
components necessary for the RPS and EPS protection:

Tab. 76. Signal protection with RPS and with/without EPS and related IDU equipping rules
EPS protected
YES (TxRx in tracking) NO

(FULLY PROTECTED) (RADIO PROTECTED)
Tributary RPSRx
EPS Signal
type protected M & E (*) M & E (*)
protection by:
EPS Signal
Protected E1 Service protection
External
Capacity interface Protection Protection Capacity need
location device box
M=16E1 M=16E1
16E1 Y Y M&E Y (**)
E=16E1 E=16E1
N
M=32E1 M=32E1
17 32E1 Y Y M&E Y (**)
E=32E1 E=16E1
Gbit
Ethernet Y N M
(optional)
TMN V11 Y N M
TMN G703 Y Y M
TMN RF Y Y M
User Service
channels Y Y M&E Y N
(optional)
Telephone
Y N M
(optional)
Audio 1 & 2
Y N M
(optional)
Alarms &
Housekeepi Y N M
ng
(*) M=Main IDU unit E=Extension IDU unit
(**) the EPS E1 protection (in FULLY PROTECTED configurations) is achieved through:
the E1 Protection Box, if the AlcatelLucent 75 W distributor (1.6/5.6 or BNC) and the
related AlcatelLucent standard cables are employed
the E1 Protection Ycable, if the AlcatelLucent 120 W distributor is employed

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 379 / 866
[4] Protection with both RPS and EPS (fully protected configurations)

PDH Switch EPS
tributaries Switch EPS PDH

TX sect RX sect tributaries

sw1 sw6
Z PDH PDH
MUX ODU ODU
Demux
IDU MAIN TX sw4 IDU MAIN RX
Squelch TX
sw3 IDU EXT RX
Squelch TX
IDU EXT TX Hitless RX
sw2 sw5 sw7
Z PDH PDH
MUX ODU ODU
Demux
PROTECTION PROTECTION
BOX BOX
Fig. 171. Protection with both RPS and EPS
Hitless switching is always present in 1+1 configuration. The hitless switching functionality is
permanently integrated in the Extension Unit.
Two different protection schemes are supported (see Fig. 171. above):
Equipment Protection Switch (EPS) both at TX and RX side: the aim is to protect circuitry after
Hitless Switching; EPS switching at TX and RX side are in tracking (one single logic drives both
TX and RX EPS). Switch EPS is implemented by:
the switch EPS Input section : the TX Split works on the main tributaries (E1), and on
the user 64 Kb/s service channel; The split functionality is performed by special cables
connecting tributaries external interfaces on Main subrack to Extension subrack and an
input high impedance circuitry driven by EPSTX command to match input impedance.
the switch EPS TX section : it allows for transmission of the same signal over the two
RF channels and allows replacement of main or extension subrack without loss of traffic.
Switches sw1 and sw2 move together.
the switch EPS RX section : when sw6 is closed, sw7 is opened and viceversa.
RX Hitless Radio Protection Switch (RPSRX)

RPS RX (hitless) is a centralized function, that receives the two aggregate signal, aligns them,
and selects the best one, depending on a suitable set of alarms from the two channels.
Both sw4 and sw5, when in (1+1) configuration and if Hitless Switch circuitry is not in failure
always selects the signal coming from sw3.
In a (1+1) HSB system the two SquelchTX commands control (onoff) the emission of RF
power (see point [7] on page 382 ).

SYSTEM DESCRIPTION
380 / 866 3DB 16142 JAAA Ed.01
[5] Static Delay Alignment
A static delay alignment procedure is provided in order to compensate the static delay between two
different signals, involved in the RPS hitless protection scheme, and due to a different length of the
related paths. The alignment is performed inserting delays on the signal in advance.
Two different types of procedure are supported:
Automatic mode
An automatic static delay alignment procedure is activated by the management systems without
providing any parameter. The activation of the procedure of automatic static delay
compensation must be explicitly requested by operator, but the number of delays to insert on
each way in order to reach the alignment is directly determined by the NE.
The automatic static delay compensation procedure cannot be performed if at least an operator
command or a RPS criteria (EW, HBER, SF) is present on one of the signals addressed by the
alignment request or if a manual operation on static delay is already active.
The result of the procedure (alignment obtained or not) is provided to the management system
requiring the operation.
The automatic static delay alignment procedure may imply traffic impact (the delay is applied
to the channel identified by the procedure disregarding the fact that the channel is active or not).
Manual mode
The manual management of the Rx static delay is available to the managements systems
independently from a previous activation of the automatic static delay compensation procedure.
This manual operation must be initiated and terminated by means of explicit commands coming
from management systems. The number of delays to be inserted on each way (direct and
indirect) must be provided by the operator.
When the manual operation is terminated the situation at the activation time of the manual
operation itself is restored. Then, if an automatic alignment procedure had been already
performed, the number of delays previously determined by the automatic alignment procedure
will be reapplied.
[6] Protection with RPS and without EPS (radio protected configurations)
Switch EPS Switch EPS

TX sect RX sect
PDH sw1 sw6 PDH

tributaries PDH tributaries
Z MUX ODU ODU PDH
Demux
IDU MAIN TX sw4 IDU MAIN RX
Squelch TX
sw3 IDU EXT RX
Squelch TX
IDU EXT TX Hitless RX
sw2 sw5 sw7
Z PDH PDH
MUX ODU ODU
Demux
Fig. 172. Protection with RPS and without EPS
This configuration is depicted in Fig. 172. above. With respect to previous Fig. 171. (Protection with
both RPS and EPS), there is the following different behavior:
switches sw1 and sw2 always select the signal coming from IDU Main
switch sw6 is always closed, while switch sw7 is always opened
no functional change for the other switches (related to RPS).

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 381 / 866
[7] HSB Tx protection type
The protection type is 1+1, single ended: at the source end the normal traffic signal is transmitted

by the RPSTx function simultaneously on both working and protection channels and, according to

the condition of the two traffic signals, the TPS logic maintains switched ON the active channel and

switched OFF the standby one.
IDU Only one ODU RFTx

ODU CH0 part is active
TX
ODU CH1
Squelch Tx command is switched

ON/OFF by the IDU TPS logic
Fig. 173. HSB Tx protection type
[8] Setting of protection type and manual commands on protection switches
The setting of protection type is performed by SW, during the commissioning procedure: see
Full Configuration Procedure Step A on page 450
Manual commands on protection switches can be forwarded by SW, as described in chapter

317 from page 635

SYSTEM DESCRIPTION
382 / 866 3DB 16142 JAAA Ed.01
21.3.3.2 IDU (1+1) configurations
The IDU (1+1) system is implemented by:

one Main IDU Unit (mandatory)

one Extension IDU Unit (mandatory)
optionally, one E1 Protection Box, or one (for max 16 E1) or two (for > 16 E1) E1 Protection
Ycable(s)
These components are mandatory only in case the EPS for E1 tributaries is required, as specified
in Tab. 76. on page 379
optionally, one Service Protection Box
The installation of this component:
is necessary in case the EPS for the User Service Channels is required, as specified in Tab. 76.
on page 379
and depends also on how the signals present on the IDUMAIN units connector ALMNMS
(see para.112.10 on page 311 ) must be connected.
N.B. in case of network interconnections for NMS channel and EOW audio continuity, the
Service Protection box is practically always required, and the connections on the
IDUMAIN units connector ALMNMS must be done as specified in Chapter 18 from
page 195
one/two optional IDU Distributor Shelf/Shelves
two IDUODU coaxial cables
cables interconnecting IDU units, protection boxes, and Distributor Shelf/ves.
Fig. 174. below shows the generic layout and block diagram of a 1+1 IDU+ODU system.
IDU 1+1 ODU CH 1

IDUODU
cable
DISTRIBUTOR SHELF MODEM IF RF
interconnections
E1 PROTEC. SERVICE
BOX PROTEC.BOX
N.B.
IDU MAIN UNIT
ODU CH 0
IDU EXTENSION UNIT
MODEM IF RF
IDUODU
cable
N.B. The ODUs and antenna(s) can be arranged to have one of the following system
configurations:
1+1 HSB (Hot StandBy) single antenna see Fig. 165. on page 373
1+1 HSB SD (Space Diversity) double antenna see Fig. 167. on page 374
1+1 FD AP (Frequency Diversity Alternate Polar) see Fig. 168. on page 374
1+1 FD DA (Frequency Diversity Dual Antenna) see Fig. 169. on page 375
Fig. 174. 9400AWY (1+1) IDU + ODU generic layout and block diagram
The possible capacities and modulations depend on:

the (1+1) IDU capacity (see point [7] on page 369 )
the ODU type and capacity [see point a ) on page 370 ]
and the employed Licence String (see Tab. 85. on page 404)

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 383 / 866
21.3.4 Detailed IDU block diagrams

Main board Main IDU
(JBIDUM)
Ethernetdata
4 x 10/100/1000 BaseT plugin
Ethernet plugin EPS
E3/DS3plugin
1732E1 16 E1/DS1plugin MUX/DEMUX

1732E1 plugin
(JAIDUE1) ODU
116E1 IDU ODU
IDUODU
NMS_V11
interface
NMS_G703
Audio channels
Audiochannels PSU
+ +ServiceChannel
V11 + G703 PSU
Service Channel (64Kbit/s) Plugin (JAIDUSC)
Plugin
uPuP
EC / RC
Alarms& housekeepings
RS232 10/100 BaseT
ECT OS (or ECT)
N.B. Ethernet and 1732E1 plugins are in alternative.
Fig. 175. IDU block diagram of 9400AWY R.2.1 (1+0)

SYSTEM DESCRIPTION
384 / 866 3DB 16142 JAAA Ed.01
Extension IDU
Extension board ODU
(JBIDUE)
IDUODU
interface
MUX/DEMUX
PSU
EPS & RPS
Interconnection cable
Main board Main IDU

Ethernet data (JBIDUM)
plug in
Ethernet plugin
Ethernet data
4 x 10/100/1000 BaseT
plug
E3/DS3 pluginin
EPS
16 E1/DS1 plug in
1732E1 1732E1 plugin MUX/DEMUX
(JAIDUE1) ODU
116E1 IDUODU
NMS_V11 interface
NMS_G703
Audio channels
Audio channels
Service Channel (64Kbit/s)
+ +Service Channel
V11 + G703 PSU
Plug in (JAIDUSC)
Plugin
uPuP/ RC
EC
Alarms & housekeepings
RS232 10/100 BaseT
ECT OS (or ECT)
N.B. On IDU Main unit, Ethernet and 1732E1 plugins are in alternative.
Fig. 176. IDU block diagram of 9400AWY R.2.1 (1+1) radio protected (without EPS)

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 385 / 866
N.B.
Extension IDU
386 / 866
E1 PROTECTION BOX
Extension board ODU
OR (JBIDUE)
E1 PROTECTIION YCABLE IDUODU
E3/DS3 plug in
interface
1732E1
16 E1/DS1
E1/DS1 Plug
161732E1 plug in

1732E1 plugin
(JAIDUE1) MUX/DEMUX
116E1
PSU
EPS & RPS
116E1 Service Channel (64Kbit/s)
Interconnection cable
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

Main board Main IDU
Ethernet data (JBIDUM)
plug in
4 x 10/100/1000 BaseT Ethernet data
Ethernet plugin
plug
E3/DS3 pluginin
EPS
1732E1 16 E1/DS1 plug in

1732E1 plugin MUX/DEMUX
(JAIDUE1)
ODU

116E1 IDUODU
NMS_V11 interface
NMS_G703
Audio channels
Audio channels
Service Channels + +Service Channel
V11 + G703 PSU
Service Channel (64Kbit/s)
Plug in (JAIDUSC)
Plugin
On IDU Main unit, Ethernet and 1732E1 plugins are in alternative.

(64Kbit/s) EC
uPuP/ RC
SERVICE
PROTECTION BOX Alarms & housekeepings
RS232 10/100 BaseT
Fig. 177. IDU block diagram of 9400AWY R.2.1 (1+1) fully protected (with EPS)
ECT OS (or ECT)
SYSTEM DESCRIPTION
USER MANUAL
21.3.5 IDUODU and station compatibility
As shown in Tab. 77. below:

all mixed configurations of ODU types in a station are allowed
all mixed configurations of ODU types on the radio hop (air interface) are allowed
constraints are:
ODU units must be always 64Mb type when the IDU capacity is 32E1
IDUs on stations A and B must be homogeneous
Tab. 77. IDUODU and station compatibility

STATION A STATION B
CONFIG. IDU ODU on IDU ODU on IDU IDU ODU on IDU ODU on IDU

MAIN IDU MAIN EXTENSION EXTENSION MAIN IDU MAIN EXTENSION EXTENSION

32Mb or 32Mb or

16E1 64Mb 16E1 64Mb
V1 or V2 V1 or V2

1+0
64Mb 64Mb

32E1 32E1
V1 or V2 V1 or V2
32Mb or 32Mb or 32Mb or 32Mb or

16E1 64Mb 16E1 64Mb 16E1 64Mb 16E1 64Mb
V1 or V2 V1 or V2 V1 or V2 V1 or V2
16E1 16E1
1+1 (without (without
64Mb EPS) 64Mb 64Mb EPS) 64Mb
32E1 32E1
V1 or V2 or V1 or V2 V1 or V2 or V1 or V2
32E1 32E1
(with EPS) (with EPS)

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 387 / 866
21.4 Provisioning of equipment items (summary)

General information to provision equipment items is given in paragraph System configurations on page

377 . Detailed information to provision equipment items can be found:

Item type Reference
IDU items (9400AWY specific items, according to

Para.15.3 from page 101
configuration)
IDU items (racks, TRU, power supply and

grounding cables)
ODU items Chapter 111 from page 249
IDUODU cable Para.17.1 on page 189
Flash Card Tab. 85. on page 404
SWP CDROM Para.31.2.1 on page 407
Cables for PCtoNE local connection Para.32.1 from page 410
Hardware upgrade kits Tab. 109. on page 797
Documentation set Point iv on page 5

SYSTEM DESCRIPTION
388 / 866 3DB 16142 JAAA Ed.01
22 TECHNICAL SPECIFICATIONS
This chapter describes the technical characteristics of the 9400AWY Rel.2.1 in the following RF band
configurations:
Tab. 78. 9400 AWY family

SYSTEM BAND (GHz)
9470AWY 78
9413AWY 13
9415AWY 15
9418AWY 18
9423AWY 23
9425AWY 25
9438AWY 38
Data indicated in this manual must be considered as typical values

The guaranteed values are only those indicated in the contract.
Subject On page
General Characteristics 390
Summary 390
Reference system standards 391
RF channeling 391
Transmitted Power at antenna port 392
99% power channel bandwidth and Emission Designator 393
ETSI System Characteristics 394
Switching system 396
Tributary interfaces 397
Modem 397
Maximum capacity and Modulation type 397
IDUODU cable 397
Manmachine interface 398
Alarms 398
Power supply 398
Mechanical characteristics 398
Environmental conditions 399
Electromagnetic compatibility / safety 399
Dismantling & Recycling 400

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 389 / 866
22.1 General Characteristics

22.1.1 Summary

Version SPLIT MOUNT (IDU+ODU)
Station type Terminal
Configuration 1+0 / 1+1 HSB / 1+1 FD
Reference standard
Refer to para. 22.1.2 page 391
(system)
Transmission capacity ETSI: 2xE1, 4xE1, 8xE1, 16xE1, 32xE1
RF channel spacing Refer to para. 22.1.3 page 391
Tunability Refer to para. 22.1.4 page 392
Transmitted power Refer to para. 22.1.4 page 392
99% power channel
bandwidth and Emission Refer to para. 22.1.5 page 393
Designator
ATPC range 20 dB (Pmax / Pmax20 dB)
ETSI mask compliance till Pmax :
20dB for 4QAM modulation
RTPC range
18dB for 16QAM modulation up to 32Mbps
15dB for 16QAM modulation at 64Mbps
Tx level with Tx mute ON < 30 dBm
RF frequency stability 10 ppm
Synthesizer step 250 kHz
RF spectrum masks Compliant with the relevant ETSI standards
Spurious Compliant with the relevant ETSI standards
emissions Compliant with ERC Rec. 7401
BER receiver threshold
Refer to para. 22.1.6 page 394 (ETSI)
System gain
Rx max input level 20 dBm (for a BER of 103)
Switching system Refer to para. 22.1.7 page 396
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
User service channels 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)
NMSV.11: 1x64 kbit/s V.11 codirectional for TMN (port 1)
NMSG.703: 1x64 kbit/s G.703 codirectional for TMN (port 2)
NMS channels
NMSRF: 1x64 kbit/s radio channel for TMN (internal to the radio
frame)

SYSTEM DESCRIPTION
390 / 866 3DB 16142 JAAA Ed.01
22.1.2 Reference system standards
ETSI standard
Frequency Frequency Standard Tx/Rx

Equipment band range Channeling separation

(GHz) (GHz) (MHz)
150, 154, 160, 161, 168,
7 7.117.9
182, 196, 245
9470 AWY ITUR F.385
119, 126, 151.614, 208,
4&16 QAM ITUR F.386
8 7.7259.5 266, 294.44, 305.56,
311.32
9413 AWY 4QAM ERC 1202
13 GHz 12.7513.25 266
9413 AWY16QAM ITUR Rec 497
9415 AWY 4QAM MEXICO 315
15 GHz 14.415.35 ERC 1207 728
9415 AWY 16QAM ITUR Rec 636 420, 490, 644
9418 AWY 4QAM ERC 1203 1008, 1010
18 GHz 17.719.7 ITUR Rec 595 340, 1560
9418 AWY 16QAM CHINA 1092.5
9423 AWY 4QAM 1008, 1050,
ERC 1302 annex A
23 GHz 21.223.6 1200,1232
9423 AWY 16QAM ITUR Rec 637
1200
9425 AWY 4QAM 24.526.5 ERC 1302
25 GHz 1008
9425 AWY 16QAM ITUR Rec. 748
9438 AWY 4QAM ERC 1201
38 GHz 3739.5 1260
9438 AWY16QAM ITUR Rec 749
For all frequency bands, the ETSI reference standard is the harmonized standard EN 302 217. In this
standard , 4QAM is class 2 and 16QAM is class 4.
22.1.3 RF channelling
ETSI RF CHANNELING
Capacity (Mbit/s) 2x2 4x2 8x2 16x2 32x2
RF Channeling with 4 QAM (MHz) 3.5 7 14 28
3.5
RF Channeling with 16 QAM (MHz) 7 14 28
N.B.
N.B. Channelling 4x2 Mbit/s 16QAM is available with ODU V1 only

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 391 / 866
22.1.4 Transmitted power at antenna port

Tolerance:
2.0 dB in temperature range 33C to +55C for 0 to 20dB RTPC range

Output power
Tx/Rx separation
Equipment dBm
MHz
(Note 1)
For 7 GHz ODUs with external diplexer, refer to

9470 AWY 4QAM 25 shifters in Tab. 20. on page 261
For 7 GHz ODUs with embedded diplexer, refer to
shifters in Tab. 23. on page Tab. 23.
9470 AWY 16QAM 21 For 8 GHz ODUs, refer to shifters in Tab. 22. on
page 262
9413 AWY 4QAM 24 Refer to shifters in:
9413 AWY 16QAM 20 Tab. 26. on page 267 (fixed shifters)

Tab. 28. on page 268 (fixed shifters)
9415 AWY16QAM 20 Tab. 30. on page 271 (variable shifters)

9418 AWY 16 QAM 19 Tab. 34. on page 275 (variable shifters)

9423 AWY 16QAM 16 Tab. 38. on page 278 (variable shifters)


Note 1: Output power at antenna port.

Output power setting (dBm):
ATPC/RTPC range with 1dB step

SYSTEM DESCRIPTION
392 / 866 3DB 16142 JAAA Ed.01
22.1.5 99% power channel bandwidth and Emission Designator
ITUR/CEPT Rec.
99% Power Channel Emission

Radio Type Channel Bandwidth

Bandwidth [MHz] Designator
[MHz]
9400 AWY 4QAM 2E1 2,8 3,5 3M5D7W
9400 AWY 4QAM 4E1 5,5 7 7M0D7W
9400 AWY 4QAM 8E1 10,9 14 14M0D7W
9400 AWY 4QAM 16E1 21,7 28 28M0D7W
9400 AWY 16QAM 4E1 2,8 3,5 3M5D7W
9400 AWY 16QAM 8E1 5,5 7 7M0D7W
9400 AWY 16QAM 16E1 10,9 14 14M0D7W
9400 AWY 16QAM 32E1 21,7 28 28M0D7W

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 393 / 866
22.1.6 ETSI System Characteristics

Data is split into following Tab. 79. to Tab. 83. according to capacity.

Note for all tables: Transmitted PTx tolerance:

2dB @ ODU Operating temperature range 33C + 55C
Tab. 79. ETSI System Characteristics 32E1 (typical values)

System
Characteristics
32 E1
Frequency (GHz) 7/8 13 15 18 23 25 38

QAM
TX Output Power
@ Antenna Port 16 21 20 20 19 16 14 13
(dBm)
103 BER Threshold

@ Antenna Port 16 79 79 79 78 78 77 75
(dBm)
106 BER Threshold

@ Antenna Port 16 78 78 78 77 77 76 74
(dBm)
Net System Gain

@ 103 BER 16 100 99 99 97 94 91 88
Threshold (dB)
Net System Gain

@ 106 BER 16 99 98 98 96 93 90 87
Threshold (dB)

System
Characteristics
16 E1
Frequency (GHz) 7/8 13 15 18 23 25 38

QAM
TX Output Power 4 25 24 24 22 19 17 16
@ Antenna Port
(dBm) 16 21 20 20 19 16 14 13
103 BER Threshold 4 86 86 86 85 85 84 82
@ Antenna Port
(dBm) 16 82 82 82 81 81 80 78
106 BER Threshold 4 85 85 85 84 84 83 81
@ Antenna Port
(dBm) 16 81 81 81 80 80 79 77
Net System Gain 4 111 110 110 107 104 101 98
@ 103 BER
Threshold (dB) 16 103 102 102 100 97 94 91
Net System Gain 4 110 109 109 106 103 100 97
@ 106 BER
Threshold (dB) 16 102 101 101 99 96 93 90

SYSTEM DESCRIPTION
394 / 866 3DB 16142 JAAA Ed.01
System
Characteristics
8 E1
Frequency (GHz) 7/8 13 15 18 23 25 38

QAM
TX Output Power 4 25 24 24 22 19 17 16
@ Antenna Port
(dBm) 16 21 20 20 19 16 14 13
103 BER Threshold 4 89 89 89 88 88 87 85
@ Antenna Port
(dBm) 16 85 85 85 84 84 83 81
106 BER Threshold 4 88 88 88 87 87 86 84
@ Antenna Port
(dBm) 16 84 84 84 83 83 82 80
Net System Gain 4 114 113 113 110 107 104 101
@ 103 BER
Threshold (dB) 16 106 105 105 103 100 97 94
Net System Gain 4 113 112 112 109 106 103 100
@ 106 BER
Threshold (dB) 16 105 104 104 102 99 96 93

System
Characteristics
4 E1
Frequency (GHz) 7/8 13 15 18 23 25 38

QAM
TX Output Power 4 25 24 24 22 19 17 16
@ Antenna Port
(dBm) 16 (*) 21 20 20 19 16 14 13
103 BER Threshold 4 92 92 92 91 91 90 88
@ Antenna Port
(dBm) 16 (*) 88 88 88 87 87 86 84
106 BER Threshold 4 91 91 91 90 90 89 87
@ Antenna Port
(dBm) 16 (*) 87 87 87 86 86 85 83
Net System Gain 4 117 116 116 113 110 107 104
@ 103 BER
Threshold (dB) 16 (*) 109 108 108 106 103 100 97
Net System Gain 4 116 115 115 112 109 106 103
@ 106 BER
Threshold (dB) 16 (*) 108 107 107 105 102 99 96
(*) available with ODU 32MB/64MbV1 only

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 395 / 866
System

Characteristics
2 E1

Frequency (GHz) 7/8 13 15 18 23 25 38
QAM
TX Output Power
@ Antenna Port 4 25 24 24 22 19 17 16
(dBm)
103 BER Threshold

@ Antenna Port 4 95 95 95 94 94 93 90
(dBm)
106 BER Threshold

@ Antenna Port 4 94 94 94 93 93 92 89
(dBm)
Net System Gain

@ 103 BER 4 120 119 119 116 113 110 106
Threshold (dB)
Net System Gain

@ 106 BER 4 119 118 118 115 112 109 105
Threshold (dB)
22.1.7 Protection switching system
[1] EPS (Equipment Protection System, optional)
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.
[2] RPS (Radio Protection System)

RPS, hitlessswitch type, is equipped to provide protection against radio propagation problems.
Available switches
ODU switch
Tx EPS Rx EPS
(HSB)
Select the IDU unit in Tx Select the IDU unit in Rx Select the ODU on line
Not hitless Not hitless Not hitless
Non revertive/Revertive Non revertive/Revertive Non revertive/Revertive
Switch vs. Configuration
Configuration Tx EPS Rx EPS ODU switch
1+1 FD YES YES NO
1+1 HSB YES YES YES

SYSTEM DESCRIPTION
396 / 866 3DB 16142 JAAA Ed.01
22.2 Tributary interfaces
E1
Input / output
ITUT G.703
electrical interface
Code HDB3
75 unbal
Impedance
120 bal
Jitter Generation ITUT G.823
Jitter Tolerance ITUT G.823
ITUT G.736
Jitter Transfer
ITUT G.742
22.3 Modem
Modulation 4/16 QAM
Demodulation Coherent
Equalizer type 19tap FSE
Channel coding Reed Solomon (255,239)
Spectrum shaping Raised cosine
22.4 Maximum capacity and Modulation type
The employed Licence String (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. 85. on page 404.
22.5 IDUODU cable

Coax. connector N (50 ohm)
Coaxial single type, 50 W, dielectric foam and braid
Coax. cable type (single)
(n.b.1)
Depends on:
cable type employed
Guaranteed cable maximum length
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) 39.168 Mbit/s
ETSI (17 to 32xE1) 78.336 Mbit/s
n.b.1 for details on cables that can be employed and relevant cable maximum length, refer to
n.b.2 the HDB3 signal contains the main signal, auxiliary signal and IDUODU service channel.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 397 / 866
22.6 Manmachine interface

Visual (LEDs) 9 (on IDU Main unit) +3 (on IDU Extension unit)

F interface for Personal Computer (WindowsTM) RS232C
TMN interface Ethernet 10/100 BaseT
Other
TMN Data channel 64kbit/s interface RS422/G703
Interface for Telephone Service Channel
22.7 Alarms
3 outputs (IDU HW Failure alarm, ODU Main Failure alarm, ODU Spare
Equipment alarms
Failure alarm)
Housekeeping alarms 6 inputs / 4 outputs
22.8 Power supply
DC nominal voltage (primary) 48 to 60 Vdc 20%

Polarity + or floating (isolated ground)
1+0 : 50W
Max Power Consumption
1+1 : 100W
22.9 Mechanical characteristics
[1] IDU
Configuration Dimensions (H x W x D) (mm) H Weight (kg)

1+0 IDU 43 x 210 x 443 mm 1U < 2.5
1+1 IDU 86 x 210 x 443 mm 2U < 5
[2] ODU
N.B. These values are indicative, as they depend on ODU V1 or V2 type, and on frequency:
ODU type Assembly Dimensions (mm) Weight (kg)

with embedded
TRANSCEIVER + BRANCHING 235 x 235 x 72 3.9
diplexer
TRANSCEIVER 248 x 257 x 93 4.2
with external
BRANCHING 235 x 235 x 73.5 3.2
diplexer
TRANSCEIVER + BRANCHING 248 x 257 x 156.5 7.4
[3] Antenna
Antenna can be:
Integrated with max diameter depending on frequency (refer to para.111.1 on page 250 for
details)
or:
Separated for larger diameters

SYSTEM DESCRIPTION
398 / 866 3DB 16142 JAAA Ed.01
22.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
22.10.1 Operating environmental conditions
Storage EN 300 019 class 1.2

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)
22.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
EN 55022 class B
discharge
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
22.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.

SYSTEM DESCRIPTION
3DB 16142 JAAA Ed.01 399 / 866
22.11 Dismantling & Recycling

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. 84. Reference documentation for dismantling and recycling detail for 9400AWY R.2 equipment
DOC.
Product Code TYPE Denomination
(N.B.)
AWY/S 8BW036840000 EUZZA 9400AWY SCALABLE RADIO SYSTEM ECODECLARATION
N.B. 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

SYSTEM DESCRIPTION
400 / 866 3DB 16142 JAAA Ed.01
SECTION 3: NE MANAGEMENT BY SOFTWARE APPLICATIONS
N.B. This section describes the NE management performed by the SWP TCO Suite. Please read
carefully the point v Notes on used TCO Suite and associated User Manual on page 5

a) BASIC INFORMATION
Chapter 31 Items for SW distribution to Customers
It describes the items foreseen for the system SW (that resident inside the 403
equipment, and that for the NE management).
Chapter 32 Connections between the Craft Terminal and the NE, and
security policy
It describes the types of physical access and the rules to observe (network 409
addresses and security) , to configure and allow the access from the SWP TCO
SUITEbased Craft Terminal to the NE.
Chapter 33 Getting started
It gives the basic information for the use of the SWP TCO SUITE, and of the SWP 423
9400AWY V2.1.3
b) WEB SERVER APPLICATIONS: PROVISIONING TOOL, AND ALARMS &
SETTINGS
Chapter 34 Provisioning Tool
443
It describes in detail the functions of the Main Menus Provisioning Tool.
Chapter 35 Alarms & Settings
481
It describes in detail the Main MenusAlarms & Settings functions.
c) BASIC INFORMATION FOR NEtO APPLICATIONS
Chapter 36 NEtO (Network ElemenT Overview)
497
It describes in detail the functions of NEtO.
Chapter 37 Introduction to 9400AWY WebEML
It describes in detail the organization of the TCO SUITE WebEML for 9400AWY 511
V2.1.3, and sums up its functions.
d) WebEML FUNCTIONS FOR EQUIPMENT CONFIGURATION
MANAGEMENT, AND EQUIPMENT MAINTENANCE
Chapter 38 Configuration
529
It describes the configuration relevant to the equipment management.
Chapter 39 Equipment
It deals with the presentation of the N.E. and the structure of the hierarchical tree, 557
and the types of subracks and boards, that comprise the Network Element.
TABLE CONTINUES

NE MANAGEMENT BY SOFTWARE APPLICATIONS
3DB 16142 JAAA Ed.01 401 / 866

Chapter 310 Line Interface

It describes the operations necessary for the configuration setting and verification 563

of each tributary.
Chapter 311 Radio
573
It deals with the management of the Radio transmission features.
Chapter 312 External input and output points
It describes how to display and set the input/output environmental alarms 587
(housekeeping alarms).
Chapter 313 Management of the security features
It describes how to manage the security features of 9400AWY (by operator profile, 591
by community string, and by access lists).
Chapter 314 MIB Management
599
It describes how to perform the NE MIB backup and restore operations.
e) WebEML FUNCTIONS FOR EQUIPMENT MAINTENANCE
Chapter 315 Alarms Monitor and Event Log Browser
It describes in detail the functions of Alarms Monitor and Event Log Browser 605
embedded in NEtO application.
Chapter 316 Diagnosis
625
It describes the Diagnosis menu commands.
Chapter 317 Protection schemes
635
It deals with the management of the protections in 1+1 configurations
Chapter 318 Loopbacks
It describes the commands for loopback management, for commissioning or 645
maintenance purposes.
Chapter 319 Performance Monitoring
657
It deals with the use of the Performance Monitoring functionalities.

402 / 866 3DB 16142 JAAA Ed.01
31 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS
This chapter describes the items foreseen for the system SW (that resident inside the equipment, and that
for the NE management).
Such a software is distributed to Customers by means of:
the Flash Card
the SWP 9400AWY V2.1.3 CDROM (the SWP this handbook refers to)
the SWP TCO SUITE Rel.1.7 CDROM (the first SWP TCO SUITE release able to manage the
9400AWY Rel.2.1 running with V2.1.3).
Subject On page
Flash Card description 404
Flash Card part numbers and associated Licence Strings 404
Physical description of Flash Cards & Licence Strings 405
Description of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs 407
Part numbers of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs 407
Notes on SWP CDROM identification, and Product Release Note 407
SWP 9400AWY V2.1.3 CDROM contents 408
SWP TCO SUITE Rel.1.7 CDROM contents 408

3DB 16142 JAAA Ed.01 403 / 866
31.1 Flash Card description

31.1.1 Flash Card part numbers and associated Licence Strings

A Flash Card is always plugged into the IDU Main board, as shown in Fig. 143. on page 289 and
Fig. 178. on page 405 ); it contains the whole Equipment programs and configuration data.
Various types of Flash Cards are available; each of them allows a fixed max system throughput [i.e. the
max number of user interfaces, in terms of equivalent Mb/s traffic, and the supported modulation (4QAM
and/or 16QAM) ]. Following Tab. 85. lists the available types:
Tab. 85. Flash Card part numbers and associated Licence Strings
Supported configuration
Logistical Item, Description & Licence String
Int.N# & type Modulation (N.B.)
3DB16079ADXX
64Mb IDU 8Mb 4QAM R213 SW KEY 2E1, 4E1 4QAM
Licence String: 8Mb 4 QAM
3DB16081ADXX
64Mb IDU 16Mb 4QAM R213 SW KEY 2E1, 4E1, 8E1 4QAM
3DB16082ADXX 2E1, 4E1 4QAM

64Mb IDU 16Mb 4/16QAM R213 SW KEY
Licence String: 16Mb 4/16 QAM 8E1 4QAM or 16QAM
3DB16083ADXX
64Mb IDU 32Mb 4QAM R213 SW KEY 2E1, 4E1, 8E1, 16E1 4QAM
3DB16084ADXX 2E1, 4E1 4QAM

64Mb IDU 32Mb 4/16QAM R213 SW KEY
Licence String: 32Mb 4/16 QAM 8E1, 16E1 4QAM or 16QAM
2E1, 4E1 4QAM

3DB16085ADXX
64Mb IDU 64Mb 16QAM R213 SW KEY 8E1, 16E1 4QAM or 16QAM
Licence String: 64Mb 4/16 QAM
32E1 16QAM
N.B. see also Modulation agility in para.111.2 on page 258
The limitations introduced by the Licence String are related only to frame structure and modulation
configuration.
There are no limits related to the NE Configuration type (1+0 or 1+1) . The Licence String value and the
NE configuration (1+0) or (1+1) type are independent.

404 / 866 3DB 16142 JAAA Ed.01
31.1.2 Physical description of Flash Cards & Licence Strings
31.1.2.1 General
The Flash Card is housed inside the IDU Main Unit shelf [see position (17) in Fig. 143. on page 289 ].
Fig. 178. herebelow shows the FLASH CARD profile and insertion direction
CONNECTOR SIDE
INSERTION BOTTOM SIDE
Fig. 178. 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 4) 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. 143. on page 289, 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:
31.1.2.2 Flash Card identification
The Logistical Items for the possible Flash Card types are specified in Tab. 85. on page 404 , which
indicates, for each P/N, also its Licence String. The Flash Card labelling is described in Fig. 179. on page
406:
a) the Flash Card Logistical Item and Licence String are reported on the label affixed on it;
b) moreover, the Licence String is affixed on the label present on the front panel of the IDU Main Unit
( position (A) in Fig. 143. on page 289 ) during the HW installation:
flash card Licence String
For this purpose, the Flash Card clamshell 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 Licence String
c) moreover, the Licence String can be verified by Operators Commands: see point [1] on page 424

3DB 16142 JAAA Ed.01 405 / 866
LABEL AFFIXED ON THE FLASH CARD
A
AND ON THE BOOKLET E

B

C
D
F E
LABEL AFFIXED ON THE BOOKLET
N.B. the booklet is shown in Fig. 17. on page 77
FIELD WRITING (EXAMPLES) MEANING N.B.
A 32Mb 4/16 QAM Licence String n.b.1
B 3DB16084ADXX Logistical item for Customer n.b.1
C 3DB16084ADAA 01 Factory Technical Code + ICS
Software versions loaded in the Flash Card

D V2.1.2 / V2.1.3 n.b.2
banks by AlcatelLucent factory
E Data matrix Supplier Data matrix (for AlcatelLucent internal purpose)
XXXXXXXXXX Supplier Serial Number (for AlcatelLucent internal

F
XXXXXXXXXX purpose)
G Logistical item Bar AlcatelLucent Commercial item Bar Code 128
n.b.1 according to Tab. 85. on page 404
n.b.2 see point [2] on page 425
Fig. 179. Flash Card identification labels

406 / 866 3DB 16142 JAAA Ed.01
31.2 Description of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs
31.2.1 Part numbers of SWP 9400AWY V2.1.3 and SWP TCO SUITE CDROMs
The:
SWP 9400AWY V2.1.3
and:
SWP TCO SUITE Rel.1.7
are distributed by two different CDROMs, each identified by a Technical Description and a Technical
Code, both written on the CDROM itself:
Tab. 86. CDROM part numbers and denominations
Technical Description Technical Code
SWP 9400AWY V2.1.3 CDROM 3DB16131ADAA
SWP TCO SUITE Rel.1.7 CDROM 3DB75005AAAA
N.B. This information may be different from that present on the CDROMs you own, according to the
notes in para.31.2.2 below. In fact, there can be different CDROMs for customization
purposes, or for new patch versions, etc.
31.2.2 Notes on SWP CDROM identification, and Product Release Note
These notes apply both to the SWP TCO SUITE CDROMs, and to the SWP 9400AWY CDROMs:
[1] SWP CDROM identification

each SWP is distributed by means of a specific SWP CDROM
a SWP is identified by its Denomination, P/N (Part Number) and CS (Change Status), that
are printed on the CDROMs label
a SWP with new Version Level, providing main features in addition to those of the previous
Version Level SWP, is distributed by means of a SWP CDROM having new Denomination,
new P/N (Part Number), and CS restarting from 01
a SWP patch version, if any, is created to correct SW bugs, and/or to add minor features, and
is distributed by means of a SWP CDROM, that can be identified:
by the same P/N of the former CDROM, but with an incremented CS number (e.g.
CS=02 instead of previous CS=01)
or by a new P/N, and CS restarting from 01
[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 SWP CDROM nor automatically
delivered to Customers
the Product Release Note is available only on specific request to your AlcatelLucent local
dealer, specifying the SWP TCO SUITE CDROM P/N and ICS (edition) printed on the SWP
CDROM itself (see point [1] above).

3DB 16142 JAAA Ed.01 407 / 866
31.2.3 SWP 9400AWY V2.1.3 CDROM contents

The SWP 9400AWY V2.1.3 CDROM contains the NEspecific software components for the Equipment

Controller and the Peripheral Units of 9400AWY (IDU and ODU).

These SW components are used whenever you have a 9400AWY R.2.1 NE running with SWP version
< V2.1.3, and you want to upgrade it to SWP version V2.1.3 , by means of the SW download function.
N.B. the SWP 9400AWY V2.1.3 CDROM does not contain any NE management SW tool.
31.2.4 SWP TCO SUITE Rel.1.7 CDROM contents
The SWP TCO SUITE Rel.1.7 CDROM:
does not contain the NEspecific software components cited in previous para.31.2.3
contains the NE software tools for the management of the 9400AWY Rel.2.1 NEs running with
V2.1.3.
The following software management tools are contained in the SWP TCO SUITE CDROM:
[1] Main Menu
The Main Menu is the starting point of this SWP, with the screen depicted in Fig. 188. on page 432.
The functions available are:
Provisioning Tool : it starts a wizard tool, which allows to configure completely and easily one
9400AWY V2.1.3 NE, in not NEinteractive (offline), or in NEinteractive (online) modality.
This tool allows also to modify a configuration file created previously, and to get the configuration
file from a running 9400AWY NE, and to convert to the V2.1.3 format a configuration file created
on a previous version 9400AWY NE
Alarms & Settings : it starts a NEinteractive function, allowing the user to login a NE through
the use of the NE web server via a generic Internet browser, to monitor the status of NE alarms
and to get and/or set some NEs parameters
Start of one NEtO session : see point [2] below
Start of 1320CT : it is meant for old 9400AWY NEs backward compatibility only (no use with
9400AWY V2.1.3 NEs)
Acceptance Tool : it is meant to be used in the commissioning phase, to create the document
TRS (Test Report Sheets), taking many parameters directly from the NE
Advanced Settings : functions to install the SWP TCO SUITE in the PC
[2] NEtO, WebEML, and Alarm Monitor
NEtO (Network Element Overview) is the starting point to make a full supervision and control of the
9400AWY V2.1.3 NE.
It allows to perform the following operations on one NE:
start its supervision
perform its login, launching the WebEML application
run the Alarm Monitor function
For additional information, refer to the SWP TCO Suite User Manual present in the SWP TCO SUITE
CDROM.

408 / 866 3DB 16142 JAAA Ed.01
32 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE,
AND SECURITY POLICY
This chapter describes the types of physical access and the rules to observe (network addresses and
security) , to configure and allow the access from the SWP TCO SUITEbased Craft Terminal to the NE.
Subject On page
Types of physical access from the PC to the NE 410
NEs F interface (RS232 serial interface) on IDU MAIN unit 411
NEs Ethernet interface on IDU MAIN unit 412
NEs pointtopoint radio interface and NMS (TMN connections) rings and
413
chains
PCNE network addressing rules 414
NEs management interfaces 414
NEs local IP address and Ethernet Configuration IP address 414
NE reachability from the CT 415
Networking scenarios for PC connection to the NEs local IP address 416
Security 419
Summary of security features 419
Security by operator profile 420
Security by community string 421
Security by access lists 422

3DB 16142 JAAA Ed.01 409 / 866
32.1 Types of physical access from the PC to the NE

The physical access to a 9400AWY NE, for its management by the PC running the SWP TCO SUITE

software , can be on the following interfaces of the 9400AWY NE:

F interface (RS232 serial interface), see point [1] on page 411
Ethernet management interface, see point [2] on page 412
Pointtopoint radio interface and NMS (TMN connections) rings and chains, see point [3] on page
413
Notes for all types of access:
a) Depending on physical interface, the use of some SW management tools has some restrictions.
b) LCT and RCT
The specification of LCT (Local Craft Terminal) and RCT (Remote Craft Terminal), in following tables
Tab. 88. to Tab. 91. , is relevant to the CT characterization for the supervised NE.
This implies different command feasibility behaviors, as described in para.37.8.1 from page 520
(some commands cannot be executed by RCT).
c) Max number of contemporary accesses to the same NE
For the NE access by:
Main Menu NEinteractive functions (online Provisioning Tool and Alarms & Settings), up
to five Ethernet user connections are supported at the same time on a single NE
WebEML (through NEtO) and OS, refer to para.36.2 on page 498
Radio Interface
9400AWY R.2.1 IDU MAIN unit (IDUODU cable)
Management NMS Interface

F Interface
Ethernet Interface (G703 + V11)
Fig. 180. Physical interfaces for the 9400AWY NE management

410 / 866 3DB 16142 JAAA Ed.01
[1] NEs F interface (RS232 serial interface) on IDU MAIN unit ( see Fig. 180. on page 410 )
WARNING: for the use of the F interface, the LLMAN installation and configuration must have
been performed, as described in para.41.4 on page 669

PUBLIC SWITCHED
TELEPHONE NETWORK
PCs modem NE supervised through F interface

F
Modem
PCs RS232 interface RS232 cable
Refer to the Appendix B on page 839 , to know how to implement the connection via the public switched
telephone network.
Tab. 87. Typical AlcatelLucent RS232 cable and adapter

Cable / Adapter P/N Notes
Standard RS232 cable
RS232 cable 1AB054120027
In addition to the standard RS232 cable, for the
usage of the NEs Finterface with any PC having
USB to RS232 adapter 1AF11294AA**
no RS232 serial port (but obviously with USB
ports available)
Tab. 88. Allowed NE management SW tools on NEs F interface

Allowed on NEs TCP/IP address LCT /
SW management tool
Finterface required for NE access RCT
SWP TCO SUITE Main Menu
NEinteractive functions:
Provisioning Tool NO
Alarms & Settings
Acceptance Tool
SWP TCO SUITE WebEML YES NO LCT
Fig. 181. Connections between PC and NE through NEs F Interface

3DB 16142 JAAA Ed.01 411 / 866
[2] NEs Ethernet interface on IDU MAIN unit ( see Fig. 180. on page 410 )

PC Ethernet interface IP NETWORK

NE supervised through Ethernet interface
ETH Eth
SWITCH
crossconnect Ethernet cable

normal (direct) Ethernet cable
Tab. 89. Typical AlcatelLucent Ethernet cables

The suggested AlcatelLucent Ethernet cables are listed in:
type see paragraph on page
normal (direct cable) 113.13.1 343
crossconnect 113.13.2 343
Tab. 90. Allowed NE management SW tools on NEs Ethernet interface

Allowed on NEs TCP/IP address LCT /
SW management tool
Eth.interface required for NE access RCT
NEinteractive functions:
Provisioning Tool YES YES
Alarms & Settings
Acceptance Tool (N.B.)
SWP TCO SUITE WebEML YES YES LCT
N.B. for details on NE access in case of Acceptance Tool use, refer to chapter 43 from page
721
Fig. 182. Ethernet connections between PC and NE

412 / 866 3DB 16142 JAAA Ed.01
[3] NEs pointtopoint radio interface and NMS (TMN connections) rings and chains
9400AWY RADIO LINK

PC connected
locally to Ethernet STATION A STATION B

or F interface of
STATION A ODU ODU
Access to Station B from PC

Local PC connected locally to Station A
Access to Station B from PC

connected remotely to Station A
NE supervised through Radio interface

NMS Eth NMS
Eth F
NMS
TMN system NE supervised through NMS
PUBLIC (G703V11)
SWITCHED Eth
TELEPHONE
IP NETWORK Remote PC NETWORK Other NE
Eth
PC connected remotely to Ethernet or F NE supervised through Ethernet
interface of STATION A interface NMS
Other NE
NMS
NE supervised through NMS
(G703V11) Other NE
Eth
For details on the NMS connections [TMNRF, TMNV11, TMNG703, TMN inframe
interfaces, with PointtoPoint Protocol (PPP)], refer to pages from 472 to 474 ]
Tab. 91. Allowed NE management SW tools on NEs Radio interface and NMS rings and chains
Allowed on NEs TCP/IP
LCT /
SW management tool interface of address required
RCT
STATION A for NE access
NEinteractive functions: F NO
Provisioning Tool
Alarms & Settings Ethernet YES YES
Acceptance Tool (N.B.)
F
SWP TCO SUITE WebEML YES YES RCT
Ethernet
N.B. for details on NE access in case of Acceptance Tool use, refer to chapter 43 from page
721
Fig. 183. Access to NE through NEs radio Interface and NMS rings and chains

3DB 16142 JAAA Ed.01 413 / 866
32.2 PCNE network addressing rules

This paragraph describes the network address rules that must be observed to allow a PC (running the

SWP TCO SUITE) the access to one or more 9400AWY NEs.

32.2.1 NEs management interfaces
For its management by SWP TCO SUITE tools, the 9400AWY NE has:
one Ethernet management interface, which is used to access the NE, and that is identified by its local
IP address and Ethernet Configuration IP address, defined in para.32.2.2 below
one pointtopoint TMNRF interface toward the other NE of the radio link
and one selectable pointtopoint TMNV11 or TMNG703 interface toward another colocated NE
all pointtopoint interfaces (TMNRF, and TMNV11 or TMNG703) are unnumbered and borrow
the IP address from the local IP address
32.2.2 NEs local IP address and Ethernet Configuration IP address
As delivered from AlcatelLucent Factory, the NEs addresses:
local IP address, used to identify uniquely the NE inside the Transmission Management Network
(TMN)
and the Ethernet Configuration IP address, used to identify uniquely the NEs Ethernet
management interface inside the TCP/IP network
are both set at default value 10.0.1.2, as shown in screen below (one of the steps of the Full
Configuration Procedure described in chapter 34 from page 443 )
These values can be maintained only until the NE remains disconnected from the TCP/IP network and
from the TMN, and must be changed to have them different from those of the other NEs present in the
accessible network. Their setting is foreseen in the Commissioning phase, chapter 42 from page 675
In the commissioning phase, you can define the local IP address and Ethernet Configuration IP
address:
with the same value (suggested solution)
or with different values

414 / 866 3DB 16142 JAAA Ed.01
WARNING: if such NE addresses are different, they must not belong to the same subnetwork, as in
following correct example:
local IP address = 151.98.96.221

and Ethernet Configuration IP address = 151.98.97.232

with IP Mask = 255.255.255.0
N.B. in the case these NE addresses are different:
the local IP address is that to be always used to access the NE by NEtO application
the Ethernet Configuration IP address is that to be always used to access the NE

by the NEinteractive Provisioning Tool and Alarms & Settings (web server)
functions.
32.2.3 NE reachability from the CT
[1] Foreword
The CT must be able to reach the NE, through one of the local or remote connections described on
previous pages 411 to 413
The access rules are different according to the type of application used; if you access a NE from your
PC:
1) through the Finterface, and by the NEtO application, the NEs local IP address must be
always used, and there are no network constraints
2) through the Ethernet interface, and by the NEtO application, for which the NEs local IP
address must be always used, it is necessary to build a networking relationship, according to
the PCNE connection scenario, between:
the IP address of the PC

the local IP address of the NE
the Ethernet Configuration IP address of the NE
as described in para.32.2.4 from page 416
3) through the Ethernet interface, and by the NEinteractive Provisioning Tool and Alarms &
Settings applications (web server operations), any problems between the IP addresses of the
PC and the NE are solved automatically, choosing Local or Remote in the application start
screen, as described in para.33.5 from page 434
[2] How to check the NE reachability from the CT
N.B. Usually, these operations have to be performed once only (i.e., whenever you have not
done them previously for the specific NE). This check is not necessary in case of PCNE
connection through the Finterface.
To make this check, open the Windows Command Prompt application and execute the command:
ping <space> NE_address
Verify the connection, then close the command window.
Note: in case the local IP address and Ethernet Configuration IP address are different from each
other, perform this check for both.

3DB 16142 JAAA Ed.01 415 / 866
32.2.4 Networking scenarios for PC connection to the NEs local IP address

These scenarios describe the networking address configurations necessary to allow a PC (running the

SWP TCO SUITE) to access a 9400AWY NE through its local IP address.

N.B. Address values are given as examples. Moreover:
address_value/24 means with IP mask = 255.255.255.0

In this case, if the address_value is that of the subnet 192.168.1.0, all addresses 192.168.1.0
to 192.168.1.255 are stated as belonging to the subnet
address_value/32 means with IP mask = 255.255.255.255

In this case, if the address_value is that of the subnet 192.168.1.0, only the address
192.168.1.0 is stated as belonging to the subnet
[1] NE local access by one PC
the CT accesses the NE using the local IP address; the SNMP traps are sent by NE using the
local IP address as source IP address
it is possible to configure the Ethernet Configuration IP address with the same value used for
local IP address
the subnet must be defined both on the PC and the NE

local IP address = 10.0.1.1
10.0.1.1
9400AWY NE
Eth
.1
subnet = 10.0.1.0/24
.2
[2] NE local and remote access by one PC, with Default Gateway or Static Route, or OSPF
in this scenario, to reach the local and remote NEs by their own local IP address, the PC must
be configured with a Default Gateway or Static Route having as gateway the Ethernet
Configuration IP address of the local NE (192.168.1.1 in the following examples)
at the same time the CT must be reachable by the remote NE using a Static Route on the remote
NE, or enabling OSPF on both local and remote NEs

416 / 866 3DB 16142 JAAA Ed.01
First example
LOCAL NE REMOTE NE
local IP address = 10.0.1.1 local IP address = 10.0.1.2

10.0.1.1
10.0.1.2 9400AWY NE
9400AWY NE
Eth
.1
subnet = 192.168.1.0/24
.2
Set:
Default Gateway = 192.168.1.1
or:
Static Route 10.0.1.0/24 Gateway 192.168.1.1
Second example
LOCAL NE REMOTE NE
10.0.1.1 local IP address = 10.0.1.1 local IP address = 172.16.1.1

172.16.1.1 9400AWY NE
9400AWY NE
Eth
.1
subnet = 192.168.1.0/24
.2
Set:
or:
Static Route 176.16.1.0 /24 Gateway 192.168.1.1
and:
Static Route 10.0.1.0/24 Gateway 192.168.1.1
WARNING: if both the local IP address and the Ethernet Configuration IP address of the local
NE belong to the same subnetwork, the local IP address of the local and remote
NEs must never belong to the same subnetwork. E.g. the following scenario does not
work:
LOCAL NE REMOTE NE
10.0.1.1 reachable local IP address = 10.0.1.1 local IP address = 10.0.1.2

10.0.1.2 unreachable 9400AWY NE
9400AWY NE
Eth
.1
subnet = 10.0.1.0/24
.2

3DB 16142 JAAA Ed.01 417 / 866
[3] NE access by more than one PC

to allow more than one PC to access the NEs in the network, theirlocal IP address, and the

IP addresses of the PCs, must belong to different subnets

10.0.1.1 local IP address = 10.0.1.1 local IP address = 10.0.1.2 10.0.1.1
10.0.1.2 9400AWY NE 10.0.1.2
9400AWY NE
Eth Eth
.1 .1
subnet = 192.168.1.0/24 subnet = 192.168.2.0/24
.2 .2
Set: Set:
Default Gateway = 192.168.1.1 Default Gateway = 192.168.2.1
or: or:
Static Route 10.0.1.0/24 Static Route 10.0.1.0/24
Gateway 192.168.1.1 Gateway 192.168.2.1
[4] Notes on OSPF routing
the OSPF routing protocol can be activated on each pointtopoint interface (TMNRF,
TMNV11, and TMNG703) and on the Ethernet Configuration IP address interface
the 9400AWY NE can act as ABR (Area Border Router) managing a maximum of 4 areas
(Backbone + 3 areas). It is possible to assign different OSPF areas to each pointtopoint
interface, and to the Ethernet Configuration IP address interface
an OSPF area can be configured as Stub Area. Configuring a Stub Area reduces the topological
database size and reduces the memory requirements for NE inside that area for NEs that are
not ABR
the OSPF Area Identifier can take a form similar to an IP address A.B.C.D
the Area 0 or Backbone has Area ID 0.0.0.0
the Area ID has not any correlation with the IP address of the interface that belongs to that area
enabling OSPF, static routing information configured on one NE are automatically redistributed
as OSPF external routes inside the OSPF areas active on this NE
static routings are not redistributed inside the OSPF areas configured as Stub Area
if OSPF is enabled on NEs, static routes, if needed, have to be added only on the NE reached
by Ethernet (called Gateway NE)
in case of CT not directly connected to the Gateway NE, the Ethernet interface of this NE must
be reachable in order to make the software download working

418 / 866 3DB 16142 JAAA Ed.01
an example of OSPF Area configuration is shown in following figure:
9400AWY NE 9400AWY NE 9400AWY NE

local IP address local IP address local IP address

10.0.1.3 10.0.1.1 10.0.1.2

TMN
G703 TMN
or RF
V11 Eth
.1
OSPF Area 1 OSPF Area 2
subnet = 192.168.1.0/24
10.0.1.1
.2
10.0.1.2
OSPF Area 0 10.0.1.3
32.3 Security
32.3.1 Summary of security features
The aim of the security features of 9400AWY system is to protect the NE from all undesired accesses.
The following security features are available:
Security by operator profile, described in detail in para.32.3.2 on page 420

This is a standard feature, allowing the NE access only through a UserName and Password set, valid
for the specific NE.
As delivered from AlcatelLucent factory, the Flash Card contains only one default Administrator
UserName and Password set.
Security by community string, described in detail in para.32.3.3 on page 421

This feature is associated to the NEtO applications, and allows to assign to the NE a community
string. An user who wants to access such a NE, must provide this community string before before
to supervise and login the NE.
Security by access lists, described in detail in para.32.3.4 on page 422

The NE management operations that can be done by means of the SWP TCO SUITE are grouped
in different services: snmp, http, ftp and telnet.
The feature Security by access lists allows to write an access list table, for each one of the services
stated above, containing the IP addresses allowed to perform that specific service.
Both security features by community string and by access lists are optional.
For both these security features, the Flash Card (as delivered from AlcatelLucent factory) contains
default parameters, corresponding to security feature not active.
N.B. The management of the security features is described in chapter 313 on page 591

3DB 16142 JAAA Ed.01 419 / 866
32.3.2 Security by operator profile

[1] UserName and Password

To login a NE, whichever the physical access method, you must have a UserName and Password

set, valid for the specific NE.
UserName and Password are requested by a prompt screen like this:
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.
In the login procedure, the username is displayed on the screen, while the cleartext password is
not displayed on the screen. After 3 times of consecutive unsuccessful NE login attempts, the CTNE
logical interface closes the login procedure. To access the NE, a new login action must be performed.
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.
[2] Login profiles
Each user (identified by a UserName and a Password) is associated to one of the predefined profiles.
The predefined profiles are the following:
Administrator (both for OS interface and CT/MibBrowser interface)

The Administrator can do everything on the NE.
In particular, only the Administrator can manage the security features summed up in
para.32.3.1 on page 419 :
add/remove users, besides changing own password and those of all users
set/change/remove the community string
set/change/remove the access lists
export the access lists from a NE, and import them in another NE.
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.

420 / 866 3DB 16142 JAAA Ed.01
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 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 do 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 manage the security features, but
can change her/his own user password.
viewer (both for OS interface and CT/MibBrowser interface)

This Operator can only explore the NE.
This Operator can change her/his own user password.
[3] Operations allowed to Login profiles, according to functions, access, and local access status
NEinteractive Provisioning Tool (described in point [2] from page 446 )

allowed to the Administrator, CraftPerson and Operator
denied to the Viewer
Alarms & Settings (described in chapter 35 from page 481 )

according to Tab. 94. on page 483
NEinteractive Acceptance Tool (described in chapter 43 from page 721 )

allowed to the Administrator and CraftPerson
denied to the Operator and Viewer
WebEML (described in chapter 37 from page 511 )

refer to para.37.8.1 on page 520
32.3.3 Security by community string
This feature is associated to the NEtO applications only.
As delivered from AlcatelLucent factory, the Flash Card contains the community string = private as
default value. When NEtO is opened, it contains always community string = private as default value.
This condition corresponds to security by community string not active.
The NE Administrator, if modifies the NEs own community string (as described in para.313.2 on page
594 ), must communicate this string to the users who should be authorized to supervise and login the NE.
Any of these users, to be authorized to access such a NE, must provide this community string before
to supervise and login the NE, as described on page 501
For the system behaviors when the community string of a NE is modified, while an user has a NEtO
session opened on the same NE (supervision, WebEML, and Alarms Monitoring), refer to points 2 ) and
3 ) on page 595

3DB 16142 JAAA Ed.01 421 / 866
32.3.4 Security by access lists

This feature is associated to all SWP TCO SUITE applications.

The NE management operations that can be done by means of the SWP TCO SUITE are performed using
the following different services:
snmp: all NEinteractive operations performed accessing the NE by NEtO ( chapter 36 on

page 497 )
http : all NEinteractive operations performed accessing the NE starting from the Main Menu
screen ( Fig. 188. on page 432 ):
NEinteractive Provisioning Tool ( point [2] on page 446 )
Alarms & Settings ( chapter 35 on page 481 )
ftp : all NEinteractive operations corresponding to:

downloading a file from the NE (e.g. the Get Configuration File described in
para.35.2.4 on page 490 )
uploading a file to the NE (e.g. the Configuration Setting described in para.35.2.2
on page 485 )
telnet telnet is the protocol used when the access to the NE is performed by NEtO from a Remote
Craft Terminal [ point b ) on page 410 ]
Note that, to perform some operations, more than one of the stated services are used. For example:
both snmp and telnet are used to login a NE by NEtO from a Remote Craft Terminal
both http and ftp are used to download a file from a NE using the Alarms & Settings functions.
In the Flash Card, for each one of the stated services, there is an Access List table, as shown in
Fig. 325. on page 596
In the Flash Card, as delivered from AlcatelLucent factory, all these four Access List tables contain
0.0.0.0 as default value in the IP Address and in the IP Mask fields.
This condition corresponds to security by access lists not active.
The NE Administrator, if wants to limit the use of one of the stated services to a specific list of managers,
must insert and enable their IP Address and their IP Mask into the corresponding Access List table,
as described in para.313.3 on page 596
After this setting, any user, whose PCs IP Address is not listed in an Access List table, will not be
authenticated for the use of the corresponding service (for the specific NE).

422 / 866 3DB 16142 JAAA Ed.01
33 GETTING STARTED
This chapter gives the basic information for the use of the SWP TCO SUITE, and of the SWP 9400AWY
V2.1.3:
Subject On page
Preparation of the Craft Terminal based on SWP TCO SUITE below
Equipment SW management by SWP TCO SUITE 424
Flash Card 424
Procedures for the management of the NE software 426
Startup and functions of the SWP TCO SUITE Main Menu screen 432
Checks the operator must do before accessing a NE 433
Common behavior of NE login, and application logoff, for the
434
NEinteractive Provisioning Tool and Alarms & Settings
Constraints and preliminary checks 434
NE login procedure 435
Application logoff procedure 439
Close Current Session 440
Operational & Maintenance WebEML 441
Operational & Maintenance 1320CT 442
33.1 Preparation of the Craft Terminal based on SWP TCO SUITE
If not yet done, the first thing you must do is to copy the TCO SUITE software from the TCO SUITE
CDROM to your PC , as described in chapter 41 from page 667, even if some functions can be run
directly from the CDROM.
N.B. The functions that can be run directly from the TCO SUITE CDROM, without performing the
copy procedures of the chapter 41 , are:
Provisioning Tool, see chapter 34 on page 443
Alarms & Settings, see chapter 35 on page 481
Acceptance Tool, see Chapter 43 on page 721
Operational & Maintenance 1320CT, see para.33.8 on page 442
The same chapter 41 explains how to copy in the PC, from the SWP 9400AWY V2.1.3 CDROM, the
SW components to be downloaded to any NE Rel.2.1 presently running with a SW version < V2.1.3

3DB 16142 JAAA Ed.01 423 / 866
33.2 Equipment SW management by SWP TCO SUITE

This paragraph introduces the information regarding the equipment software management.

For the main phases for 9400AWY HW and SW installation refer to para.11.2 on page 26
33.2.1 Flash Card
A Flash Card is always plugged into the IDU Main board; it contains the whole Equipment programs and
configuration data.
33.2.1.1 Flash Card types
Various types of Flash Cards are available; they are listed in Tab. 85. on page 404
Each of them allows a fixed max system throughput [i.e. the max number of user interfaces, in terms of
equivalent Mb/s traffic, and the supported modulation (4QAM and/or 16QAM) ].
33.2.1.2 Flash Card content
The Flash Card contains the whole Equipment programs and configuration data, as shown in
Fig. 184. below:
Fixed Data SERIAL NUMBER

Licence info
Licence Data LICENCE STRING & LICENCE KEY
SW SW
COMMIT STANDBY
SW instances
VERSION VERSION
(ACTIVE) (not active)
NE Data MIB
Fig. 184. Flash Card content
[1] Licence information and its management
The licence information can be read by the CT command Supervision % SW Key ( see para.37.8.8
on page 528 ), which opens the screen of Fig. 185. on page 425 , or by the Licence Info screen
of the Alarms & Settings function (see para.35.2.8 on page 493 ):
the Serial Number is that physically associated to the Flash Card
the Licence String indicates the fixed max system throughput
the Set Licence Key field indicates the licence, associated to the Flash Cards Serial Number,
and implicitly defines its current Licence String.
You can change the max system throughput asking AlcatelLucent a new Licence Key pattern,
associated to the Flash Cards Serial Number, then introducing it (by copy and paste) in the Set
Licence Key field, at last clicking the button Apply.

424 / 866 3DB 16142 JAAA Ed.01
Fig. 185. Flash Card licence information
[2] SW instances
The SW COMMITTED 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.
As supplied by AlcatelLucent factory, 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 cards listed in Tab. 85. on page 404 are:
the SW COMMIT VERSION (V2.1.3)
the SW STANDBY, loaded with the SW version (maintenance release) immediately previous
with respect to the COMMIT one
[3] NE data
N.B. as shown in Fig. 184. on page 424, differently from SW instances, NE data are present
as single instances in the Flash Card.
a) Base configuration
It is defined by the Flash Cards licence information. It means that you can change the system
configuration data only within its throughput limits.
The licence information can be modified as described in previous point [1] on page 424
b) MIB
The MIB (Management Information Base) contains all NE configuration data.

As supplied by AlcatelLucent factory, the NE configuration data are set to default values.

3DB 16142 JAAA Ed.01 425 / 866
33.2.2 Procedures for the management of the NE software

SWP TCO SUITE CDROM SWP 9400AWY V2.1.3 CDROM
It contains the SW tools for the NE It contains the SW components to be
management downloaded to any NE Rel.2.1 presently
running with a SW version < V2.1.3
NE data management PREPARATION OF

CRAFT TERMINAL BASED
ON SWP TCO SUITE
(see chapter 41
from page 667 )
NE SW download & activation

NE DATA (if necessary) N.B.
BACKUP
(see point [3] on page 428 ) 1 NE SW download
NE SWP downloading
from PC to Flash Card
DURATION (about):
30 minutes with
F interface
15 minutes with
Ethernet interface
2 NE SW activation
NE DATA
SWP load from Flash Card
CHANGE
to Equipment Controller
(see point [2] on page 427 )
and peripheral units
(IDU & ODU)
NE DATA
DURATION:
RESTORE
some minutes
N.B. the NE SW download & activation is necessary only in case of upgrading of the NE SWP (see
point [7] on page 430 ).
Fig. 186. Main phases of the equipment SW management

426 / 866 3DB 16142 JAAA Ed.01
The procedures for the management of the NE software, described in the following, are related to the
contents of the Flash Card, described in previous para.33.2.1.2 on page 424 :
Firsttime equipment startup and commissioning

Changing NE data
NE data backup
NE data restore
Flash Card licence management
Flash Card replacement
Upgrading of the NE SWP
System restart
[1] Firsttime equipment startup and commissioning
It must be done according to the instructions given in Chapter 42 from page 675
After the commissioning completion, create a folder, specific for the NE, containing the following files:
the MIB backup .bar file , and the NE configuration backup .qcml file (see point [3] below)
the TRS (Test Result Sheet & Site Acceptance Test Protocol) report by means of the
Acceptance Tool of the TCO SUITEs Main Menu (see Chapter 43 on page 721 ). This can
be used, in the future, to compare the system performance to that verified at the commissioning
phase time.
the printouts of the SW Status screens (for both the committed and standby banks) as shown
in Fig. 434. on page 813 , and in Fig. 435. on page 814
and maintain this folder updated whenever you make changes on the NE data.
[2] Changing NE data
NE data, contained in the MIB, can be changed (within the limits implicitly defined by the employed
Flash Card type), by the suitable commands of:
the Craft Terminal
the NEinteractive Provisioning Tool
the Alarms & Settings functions
Changes of the NE data are submitted to the security policy described in para.32.3 from page 419

3DB 16142 JAAA Ed.01 427 / 866
[3] NE data backup
The NE data backup must be always performed:

at the end of the commissioning ( see para.11.2 on page 26 )

every time you change any NE data ( see point [2] on page 427 )
every time you upgrade the NE SWP ( see point [7] on page 430 )
WARNING: If you change the NE data without performing the backup operations here
described, in case of troubles you will have to create again the NE configuration data
from the beginning, wasting time and with high probability of errors.
Every time you change any NE data, you must always save them by both the following two
procedures (they are both necessary, because some data are present only in one of the two backup
files):
a) MIB back up (.bar file)

Refer to chapter 314 on page 599 (Supervision % MIB Management % Backup)
b) NE configuration backup (.qcml file)

There are two alternative, but equivalent, ways:
using the function Get Configuration File of the Alarms & Settings tool ( see
para.35.2.4 on page 490 ). In this case, after the successful login, the save screen
appears:
or clicking the button Get Configuration from NE in the Start wizard screen of the
NEinteractive Provisioning Tool ( see Fig. 198. on page 446 ). In this case the
following screen appears ( Fig. 187. ), where you must click the Save as ... button:
Fig. 187. Last wizard screen of the SetUp Tool
In both cases, save the file, giving it a mnemonic name and choosing the directory for save.

428 / 866 3DB 16142 JAAA Ed.01
[4] NE data restore
Whenever you must restore in the NE the data you have previously saved by the procedures of
previous point [3] , perform the data restore operations in the following order:
a) at first, perform the NE configuration restore (.qcml file)

There are two alternative, but equivalent, ways:
using the function Configuration Setting of the Alarms & Settings tool (see
para.35.2.2 on page 485 ), at first browsing the backup file, then clicking on the button
Apply Configuration
or clicking the button Open Configuration in the Start wizard screen of the
NEinteractive Provisioning Tool (see Fig. 198. on page 446 ). In this case, the
following file selection screen opens, where you must browse the backup file, and then
click on the button Open:
Then, the screen of Fig. 187. on page 428 opens, but with the button Apply enabled:
click on it to send the configuration file to the NE. In alternative, click on Modify
parameters, to check the configuration before sending it to the NE.
WARNING: In some cases (depending on the data that have been changed), an automatic
system restart is executed (see point [8] on page 430 ), and the CTNE
communication is lost. Therefore, wait the time necessary for the restart
completion, after which you can perform again the NE login.
b) then, perform the MIB restore (.bar file)

Refer to chapter 314 on page 599 (Supervision % MIB Management % Restore)
[5] Flash Card licence management
The Flash Card licence management allows to improve the max system throughput. It can be done
as described in point [1] on page 424
[6] Flash Card replacement
The Flash Card replacement implies always the NE data backup (before the replacement) and
restore operations (after the replacement), described in previous points [3] and [4]
The Flash Card replacement is necessary for corrective maintenance only (i.e. when the Flash Card
is suspected faulty), and must be done according to the instructions given in para.56.2 from page
794

3DB 16142 JAAA Ed.01 429 / 866
[7] Upgrading of the NE SWP

This procedure is envisaged whenever a new NE SWP release (new with respect to that presently

loaded in the system) is supplied to Customer by the relevant NE SWP CDROM.

E.g. the SWP 9400AWY V2.1.3 CDROM is supplied to a Customer owing a 9400AWY R.2.1 NE
running with a SW version < V2.1.3 (V2.1.1, for example).
It means that the SW COMMIT VERSION bank in the Flash Card contains the SW components of
the version V2.1.1 (see point [2] on page 425 ) and must be replaced by those of the version V2.1.3.
With reference to such an example, the SWP upgrade corresponds to make the following operations:
at first, the loading of the new V2.1.3 SW components (previously copied in the PC environment
from the SWP 9400AWY V2.1.3 CDROM) in the Flash Cards SW STANDBY VERSION
bank;
secondly, the swap of the SW COMMIT VERSION and SW STANDBY VERSION banks,
automatically followed by a system restart, which loads the new SW components in all
peripherals.
N.B. the real need for the download to the NE of the new SWP, and its activation, can be
checked as described in para.59.1 on page 812
The NE SW upgrading must be done according to the instructions given in chapter 59 from page
811
[8] System restart
The system restart (reloading of all RAMs present in the system with information stored in the Flash
Card and reset of all peripherals):
is performed automatically in one of the following conditions:

after the activation of a new SWP
after a MIB restore and activation
only in some cases, depending on affected data, after the download of a configuration
.qcml file
after system power off / on
can be performed manually by the operator in one of the following ways:

pushing the reset button on the IDU Main Unit [ see position (10) in Fig. 143. on page
289 ]
with the NE logged in by WebEML, by the command Supervision Restart NE ( see
para.37.8.8 on page 528 ); clicking OK on the confirmation box (Do you really want to
restart this NE?), the system restart begins.
About 2 to 5 minutes are necessary for system restart.
WARNING: at the system restart beginning, the CTNE communication, if open, is lost.
Therefore, if necessary, you must perform again the NEinteractive application,
waiting the time necessary for the restart completion.

430 / 866 3DB 16142 JAAA Ed.01
33.2.3 NE data compatibility between SWP 2.1.x versions
[1] MIB backup file (.bar file)


A MIB backup file created while system was running with any SWP version < V2.1.3 can be
reused on a system running with the SWP version V2.1.3.
A MIB backup file created while system is running with the SWP version V2.1.3 cannot be
reused on a system running with any SWP version < V2.1.3.
[2] Configuration file (.qcml file)

A .qcml configuration file created while system was running with any SWP version < V2.1.3
can be reused on a system running with the SWP version V2.1.3.
A .qcml configuration file created while system is running with the SWP version V2.1.3 cannot
be reused on a system running with any SWP version < V2.1.3.

3DB 16142 JAAA Ed.01 431 / 866
33.3 Startup and functions of the TCO SUITE Main Menu screen

There are two ways to launch the SWP TCO SUITE Main Menu screen:

a) directly from the SWP TCO SUITE CDROM:
1) Verify that your PC meets the requirements described in the TCO Suite User Manual
2) Insert the SWP TCO SUITE CDROM in your PC
3) If never done previously, the startup of the SWP TCO SUITE is performed automatically (it
installs, if necessary, the JRE required version), and the Main Menu screen opens ( Fig. 188.
below)
N.B. in case of problems, or for startup details, refer to the TCO Suite User Manual
b) clicking the shortcut to the Local Copy of the TCO Suite ( Fig. 384. on page 668 )
N.B. To use this modality, the SWP TCO SUITE Local version, and the relevant shortcut, must
have been created previously, as described in para.41.3 on page 668
in both cases, the Main Menu screen of following Fig. 188. opens:
F
G
Fig. 188. Main Menu screen
The functions of the various buttons is summarized below.

N.B. before clicking any button, please read the instructions given in the relevant chapter or
paragraph.
A Provisioning Tool: see chapter 34 on page 443
B Alarms & Settings: see chapter 35 on page 481
C Close Current Session: see para.33.6 on page 440
D Operational & Maintenance WebEML: see para.33.7 on page 441
E Operational & Maintenance 1320CT: see para.33.8 on page 442
F Acceptance Tool: see chapter 43 on page 721
G Advanced Settings: button present only in CDROM version. For its use, please refer to the
TCO Suite User Manual

432 / 866 3DB 16142 JAAA Ed.01
33.4 Checks the operator must do before accessing a NE
The SWP TCO SUITE includes not NEinteractive applications, and NEinteractive applications.
For all NEinteractive applications, the checks that any operator must perform before attempting the
access from her/his PC (running the SWP TCO SUITE) to a 9400AWY NE, are summed up below:
N.B. Usually, these checks have to be performed once only (i.e., whenever you have not done them
previously for the specific NE).
a) the operator must know the NEs local IP address and/or the Ethernet Configuration IP address,
that must have already been defined correctly inside the network from both physical and logical
points of view. Note:
the local IP address is that to be always used to access the NE by NEtO application
the Ethernet Configuration IP address is that to be always used to access the NE by the
NEinteractive Provisioning Tool and Alarms & Settings (web server) functions.
For details, refer to para.32.2.2 on page 414 , and to para.32.2.4 on page 416
b) the PC must be able to reach the NE. To make this check, if necessary, refer to point [2] on page
415
c) if more than one network adapter is present in the PC, you must know which is that used for the
PCNE connection (its identity could be required in the login procedure).
d) if not yet done, it is mandatory to manually disable system and browser proxy configurations prior
to use the web server operations; otherwise, the IP connection from the PCs web server to the NE
cannot take place.
e) the operator must have an UserName and Password set, valid for the NE that must be loggedin.
This information must be provided by the NE Administrator to the user.
Note: the operations allowed, after the successful login, depend on the NE login profile.
For details, refer to para.32.3.2 on page 420
f) only for access by NEtO: if the NE Administrator has defined a community string (different from the
default value) for the specific NE, the operator must know it.
g) if the NE Administrator has defined the security by access lists for the specific NE, the operator must
know whether or not the IP address of her/his PC is enabled to the specific services she/he wants
to perform.

3DB 16142 JAAA Ed.01 433 / 866
33.5 Common behavior of NE login, and application logoff, for the
NEinteractive Provisioning Tool and Alarms & Settings

The NEinteractive Provisioning Tool functions are described in point [2] from page 446
The Alarms & Settings functions are described in chapter 35 from page 481
This paragraph is referenced to by them, for executing the NE login, and the application logoff.
33.5.1 Constraints and preliminary checks
WARNING: as specified in Tab. 88. on page 411 and Tab. 91. on page 413, these functions must
not be launched if the PCNE connection is done through the F interface, whichever the
addressed NE is (local or remote)
Before to run one of these functions (clicking the suitable button of the Main Menu) you must make the
following checks:
a) perform the checks listed in para.33.4 on page 433
b) in addition, if the PCNE connection is physically local (i.e. through the direct connection by a
crossconnect Ethernet cable between the PC and NE Ethernet ports, or by an Ethernet switch), you
must know if:
the IP address of the PC
and the Ethernet Configuration IP address of the NE (see para.32.2.2 on page 414)
belong, or not, to the same subnetwork This implies a different choice between Local or Remote
in the application start screen [ step 4 ) on page 437 ]

434 / 866 3DB 16142 JAAA Ed.01
33.5.2 NE login procedure
1) If necessary, perform Close Current Session, clicking the Main Menu relevant button
N.B. The first time you use the NEinteractive Provisioning Tool or the Alarms & Settings
function, you should not need to perform the Close Current Session. Refer to the step
2 ) on page 439 , to understand this need at a second time. Anyway, if you like to know
the current situation, click this button: the Network settings OK ( Fig. 194. on page 440)
certifies that you start from a clear condition.
2) Launch the application you want (NEinteractive Provisioning Tool below, or Alarms & Settings
on page 436 ) from the Main Menu screen ( Fig. 188. on page 432 ), and enter the connection
parameters:
a) to run the NEinteractive Provisioning Tool, click the specific button:
The screen of Fig. 189. below opens, where you have to specify Connect to NE (1) , then
enter the NE IP address (2) as detailed in step 3 ) on page 436 , then specify Local or Remote
(3) as detailed in step 4 ) on page 437 , and, at last, clicking OK button (4).
If more than one network adapter is found in the PC, the choice of which to use is forwarded
to the user [next step 5 ) on page 437 ]
Otherwise (only one network adapter is found in the PC), if the PCNE connection is correctly
established, the NE login screen appears [next step 6 ) on page 438 ]
(2)
(1)
(4) (3) specify Local or Remote
Fig. 189. Connection parameter screen for the NEinteractive Provisioning Tool

3DB 16142 JAAA Ed.01 435 / 866
b) to run theAlarms & Settings function, click the specific button:

The screen of Fig. 190. below opens, where you have to enter the NE IP address (1) as detailed
in step 3 ) below, then specify Local or Remote (2) as detailed in step 4 ) on page 437, and,
at last, clicking OK button (3).
If more than one network adapter is found in the PC, the choice of which to use is forwarded
to the user [next step 5 ) on page 437 ]
Otherwise (only one network adapter is found in the PC), if the PCNE connection is correctly
established, the NE login screen appears [next step 6 ) on page 438 ]
(1)
(3) (2) specify Local or Remote
Fig. 190. Connection parameter screen for the Alarms & Settings function
3) Specification of NE IP address in Fig. 189. or Fig. 190.
WARNING: if the local IP address and Ethernet Configuration IP address are different, you
must specify the Ethernet Configuration IP address : for details, refer to to

436 / 866 3DB 16142 JAAA Ed.01
4) Specification of Local or Remote in Fig. 189. or Fig. 190.
According to the checks you should have done in para.33.5.1 on page 434 :
a) if the PCNE connection is physically remote (i.e. through IP network, or through Radio
interface, or through NMS rings and chains), specify Remote
b) if the PCNE connection is physically local (i.e. through the direct connection by a
crossconnect Ethernet cable between the PC and NE Ethernet ports, or by an Ethernet
switch), and the IP address of the PC and the Ethernet Configuration IP address of the NE:
belong to the same subnetwork, specify Remote
do not belong to the same subnetwork, specify Local

As a consequence of the Local specification, the application adds semipermanently an
IP address to your PC, to allow it to reach the NE.
This semipermanently added IP address is cleared performing the Close Current
Session [see step 2 ) on page 439 ], or restarting the PC.
5) Choice of the network adapter, if required
The application performs a search on users computer resources in order to find all network adapters
related to active (enabled) network connections [see point c ) on page 433 ]. Then, if more than
one network adapter is found, the user must select the one to use. An example of selection box is
shown in Fig. 191. below:
Fig. 191. 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 will not see the dialog box shown in Fig. 191.
above.
WARNING: the virtual network card you may have created for the LLMAN must never be selected
to connect the PC to the NE, for running the NEinteractive Provisioning Tool and
the Alarms & Settings functions.

3DB 16142 JAAA Ed.01 437 / 866
To know more information about adapters details, by clicking the Details toggle button some
supplemental information are shown as in Fig. 192. :

Fig. 192. Network Adapter details
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.
When the user clicks Apply in screen of Fig. 191. or Fig. 192. , and if, in step 4 ) on page 437
:
Remote has been specified, the PCNE connection is setup using the selected network
adapter (without performing any adaptation)
Local has been specified, a new address is added to the network adapter, to allow the PC
connection with specified NE, and the PCNE connection is setup
At last, if the PCNE connection is correctly established, the NE login screen appears [step 6 )
below]
6) NE login and application opening
If the PCNE connection is correctly established, the NE login screen opens, where user is asked
to provide his/her UserName and Password (for details, see point [1] on page 420 ):
After having filled the fields UserName and Password, followed by the Apply button clicking, if
login successful:
in case of NEinteractive Provisioning Tool, the screen of Fig. 198. on page 446 opens
in case of Alarms & Settings, the screen of Fig. 231. on page 482 opens

438 / 866 3DB 16142 JAAA Ed.01
33.5.3 Application logoff procedure
1) Exit from the application NEinteractive Provisioning Tool or the Alarms & Settings, clicking
of the relevant screen
2) If necessary, perform Close Current Session, clicking the Main Menu relevant button.
Explanation:
After having exiting the application for a certain NE ....
... and if, in step 4 ) on page 437 you have specified:

Remote, you have nothing to do to launch one of the applications NEinteractive
Provisioning Tool or the Alarms & Settings for the same or another NE
Local, you have to decide if the semipermanent change on the used network adapter must:
remain. In this case, if you run again the NEinteractive Provisioning Tool or the Alarms
& Settings, no question is raised, and the connection to the NE previously connected is
established again;
be removed. In this case, click the Close Current Session button and the network settings
restoration message ( Fig. 193. on page 440 ) will appear, certifying that the network
adapter restoration has been done, and that you can now launch one of the applications
NEinteractive Provisioning Tool or the Alarms & Settings for another NE.

3DB 16142 JAAA Ed.01 439 / 866
33.6 Close Current Session

This function is run clicking the following button of Main Menu screen ( Fig. 188. on page 432 ):

This function allows to close current session restoring the network settings modified by a previous run of
the NEinteractive Provisioning Tool or Alarms & Settings in Local mode [as described in step 4 )
on page 437 ].
It means that, if you have previously used one of such functions, and you want to use the same function
with another NE, before clicking the relevant buttons, you must at first click on the button Close Current
Session.
Fig. 193. (example) shows the message certifying the network adapter restoration:
Fig. 193. Close Current Session: network settings restoration message
Fig. 194. shows that you can run the NEinteractive Provisioning Tool or Alarms & Settings starting
from a cleared condition.
Fig. 194. Close Current Session: Network settings OK

440 / 866 3DB 16142 JAAA Ed.01
33.7 Operational & Maintenance WebEML
This button launches the NEtO application. Before to click it, read carefully the following warnings:
WARNING 1: for the use of this function, the Local copy of WebEML (Jusm/CT) must have already
been performed, as described in para.41.3 on page 668
WARNING 2: in case of CTNE connection through the F interface ( see Fig. 181. on page 411 ), before
to click the button Operational & Maintenance WebEML, you must perform all operations
described in point c ) on page 499 , i.e.:
check of LLMAN (Lower Layer MANager) installation and configuration
PC desktop Properties System standby and System hibernates both set to Never
manual start of LLMAN
Standard behavior:
If the Local copy of WebEML (Jusm/CT) has been performed, this function runs the NEtO software
application, opening its first screen:
For NEtO usage, refer to the Chapter 36 on page 497

3DB 16142 JAAA Ed.01 441 / 866
Special conditions:

If the Local copy of WebEML (Jusm/CT) is not found in the default local place, this function asks

the user if there is a previously performed local copy:

Selecting:
Yes, specify the folder where the WebEML is. then function will run NEtO in the specified folder.
No, this function asks if user wants to perform WebEML Local Copy:
If choice No, this function exits. If choice Yes, WebEML in the CDROM is copied from the
CDROM to a specified folder, then NEtO is started.
WARNING: the Local copy of WebEML (Jusm/CT) can be done only from the CDROM.
33.8 Operational & Maintenance 1320CT
This function runs the 1320CT software application previously installed on users PC, and is meant for old
9400AWY NEs backward compatibility.
This function has no use with 9400AWY NEs running with V2.1.3.

442 / 866 3DB 16142 JAAA Ed.01
34 PROVISIONING TOOL
This chapter describes in detail the functions of the Main Menus Provisioning Tool.
Subject On page
Provisioning Tool overview, and startup 444
Not NEinteractive modality (offline) 444
NEinteractive modality 446
Full Configuration Procedure 447
Configuration file conversion feature 447
Full Configuration Procedure 448
Note on the use of the bottom buttons available in the screens 448
Full Configuration Procedure steps 449

3DB 16142 JAAA Ed.01 443 / 866
34.1 Provisioning Tool overview, and startup

N.B. Besides from the Local Copy of the TCO Suite, the Provisioning Tool can be run also directly

from the TCO SUITE CDROM, without performing the copy procedures of the chapter 41

from page 667
This function allows to create, modify and/or apply provisioning files in two ways:
not NEinteractive (offline), point [1] below
or NEinteractive, point [2] on page 446
[1] Not NEinteractive modality (offline)
This modality allows the offline creation and modification of a .qcml configuration provisioning file,
without accessing any NE.
This .qcml file will be after used to configure the NE (after having logged it) with a simple load
command.
The screen of Fig. 195. below opens, where you have to specify Do not connect to NE (offline),
and then click OK
(1)
(2)
Fig. 195. Start of the Not NEinteractive Provisioning Tool

444 / 866 3DB 16142 JAAA Ed.01
After clicking the OK button, the following prompt screen appears, where you must choose the
9400AWY system type Version V2.1.3, and then click OK:
Fig. 196. Not NEinteractive Provisioning Tool: choice of NE version
N.B. For the other versions, refer to the TCO Suite User Manual
After clicking OK, the following screen appears:
Fig. 197. Start wizard screen of the Not NEinteractive Provisioning Tool
This is the first screen of the Full Configuration Procedure, described in point [3] on page 447
See also the Configuration file conversion feature, described in point [4] on page 447

3DB 16142 JAAA Ed.01 445 / 866
[2] NEinteractive modality

By this modality, you access one 9400AWY V2.1.3 NE, not using the Craft Terminal application, but

the NE web server; its main steps are:

launch the application and the connection with the target NE,
recover a configuration file configuration_name.qcml previously created (e.g. through the Not
NEinteractive Provisioning Tool described in previous point [1] on page 444 ), or get
configuration data from the NE
check/modify the configuration,
apply the configuration to the target NE.
WARNING: when the traffic is running, the use of the Provisioning Tool in NEinteractive modality,
may cause E1 and/or Ethernet traffic interruption.
Procedure
a) Start of the application
To start this application, and login the NE, strictly follow instructions given in para.33.5 on
pages 434 to 438
b) Use of the application
After having successfully connected to the NE and loggedin it, the following screen appears:
Fig. 198. Start wizard screen of the NEinteractive Provisioning Tool
This is the first screen of the Full Configuration Procedure, described in point [3] on page
447
See also the Configuration file conversion feature, described in point [4] on page 447
c) Exiting from the application
Strictly follow instructions given in para.33.5.3 on page 439

446 / 866 3DB 16142 JAAA Ed.01
[3] Full Configuration Procedure
This procedure allows a full system configuration through a guided process, based on a reduced set
of screens (steps). The related windows are displayed by a Wizard Tool according to a specific step
sequence.
Clicking the Help button in the Start wizard screen:
of the Not NEinteractive Provisioning Tool ( Fig. 197. on page 445 )

or of the NEinteractive Provisioning Tool ( Fig. 198. on page 446 )
the following help screen opens (specific for 9400AWY R.2.1 V2.1.3):
Fig. 199. Provisioning Tool help on line
To have all information necessary for choosing and filling the various fields of each step, to go forward
and backward within the procedure steps, and to save or get the .qcml configuration file, or apply
the configuration to the NE, follow the instructions given:
in this help on line
and/or in para.34.2 from page 448
[4] Configuration file conversion feature

After having clicked the button Open Configuration in
Fig. 197. on page 445 (not NEinteractive modality, having specified V2.1.3)
or in Fig. 198. on page 446 (NEinteractive modality, having logged in a 9400AWY V2.1.3
NE)
you can also specify a .qcml configuration file that was created on a 9400AWY system running with:
9400AWY R.2.0:
V2.0.4 (only if configured for ETSI market), or V2.0.5, or V2.0.6
9400AWY R.2.1:
V2.1.0, or V2.1.1, or V2.1.2
The result. if successful, will be the file conversion to the target format V2.1.3

3DB 16142 JAAA Ed.01 447 / 866
34.2 Full Configuration Procedure

This procedure can be launched in not NEinteractive (offline) mode, or NEinteractive mode, as

described in para.34.1 on page 444

34.2.1 Note on the use of the bottom buttons available in the screens
The bottom buttons available in the screens depend on the configuration tool started, and are
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 performed:
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.
Cancel: by clicking on this button, the procedure is cancelled
Help: by clicking on this button the operator calls the helpon line ( Fig. 199. on page 447 )

448 / 866 3DB 16142 JAAA Ed.01
34.2.2 Full Configuration Procedure steps
Full Configuration Procedure steps On page

Step A Main NE parameter configuration 450

Step B Tributary configuration 454
PDH tributary port configuration screen 454
Ethernet port configuration screen 456
Step C Vlan Information Configuration 460
Step D Channel configuration 462
Frequency data setting 463
ATPC data setting 465
Step E Link Identifier configuration 467
Step F Automatic restoration criteria configuration 468
Step G OSPF area configuration 469
Step H Configuration of Local IP address, Ethernet and Network Time
470
Protocol
Step I Configuration of TMNRF, TMNV11, and TMNG703 or TMNin
472
frame channels
Step J IP Static Routes Configuration 475
Step K Access List Configuration 477
Step L Trusted Manager Information 477
Step M EOW and Auxiliary Interface Configuration 478
Step N External Input and Output Points Configuration 479
Step O Summary 480
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
N.B. For the steps regarding the NE routing data, refer also to:
and para.32.2 on pages 414 to 419

3DB 16142 JAAA Ed.01 449 / 866
Step A (Main NE parameter configuration)

Fig. 200. below appears as first window of the procedure:

DO NOT USE THIS CHOICE !
Fig. 200. Full 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

450 / 866 3DB 16142 JAAA Ed.01
c) Tributary; choose between:
16E1: max 16xE1 without Enhanced Ethernet plugin
16E1GData: max 16xE1 with Enhanced Ethernet plugin

32E1: max 32xE1

N.B. the number of actually usable tributaries depends on the employed Licence String
d) Power Supply Unit: at the issue date of this manual, only PSU4860 choice is meaningful
N.B. choice PSU2460 is relevant to hardware items not presently available.
e) only in case of 1+1 HSB or 1+1 FD the button Without EPS (RPS only) becomes selectable:
This button Without EPS (RPS only):

must be left blank in case of system with EPS (fully protected)
must be selected in case of system without EPS (radio protected)
For additional information, please refer to para.21.3.3 from page 378
f) if equipped, click on Audio/User Service Channels plugin
g) Market : in this SWP version, only ETSI choice is possible
Area Structure:
h) 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 or 4E1,
only 4QAM modulation scheme is supported.
The association between Radio Capacity and Radio Modulation is shown in Tab. 92. below:
Tab. 92. Radio application: Capacity and modulation
Radio Capacity Radio Modulation
2xE1 4QAM
4xE1 4QAM
8xE1 4QAM / 16QAM
16xE1 4QAM / 16QAM
32xE1 16QAM
N.B. the actually usable Radio Capacity and Modulation types depend on the employed
Licence String (see Tab. 85. on page 404 )

3DB 16142 JAAA Ed.01 451 / 866
WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa)
the Tx power (in case of operation with RTPC) and the ATPC range (in case of

operation with ATPC) of the new modulation scheme must be in the correct range

(refer to para. 311.5 on page 578 ). 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.
i) Country (this feature is named also Regional Settings)
[1] Regional Settings purpose

Via this feature, based on the country configuration files embedded in SWP, the operator selects
the Country (in this release only France and Others are forecasted), the Frequency Band (7
38 GHz), the Capacity (2E1 32E1), the Modulation (4/16 QAM), the Channel Number (1
n), and then, the shifter amplitude, the central frequency and the TX/RX Frequency are
retrieved.
In case of the operator chooses Others, the procedure is the standard one, that is the operator
chooses the Capacity, the Modulation, the Frequency Band, the Shifter and Central Frequency
couple, and the Tx frequency: the Rx frequency is defined automatically.
[2] Frequency Band selection

According to the country selection and the corresponding configuration file, the available
frequency bands, related to this configuration, are listed in the drop box for the frequency band
selection.
[3] Bandwidth (or Spacing for Channel) deduction

The Bandwidth (or Spacing per Channel) is deduced by the Capacity and Modulation.
[4] Channel Number selection

The operator must select one of the authorized Channel Numbers: related to this, the Tx_Low
and Tx_High frequencies are displayed and set consequently.

452 / 866 3DB 16142 JAAA Ed.01
[5] Frequency Parameters calculation
AlcatelLucent divides the frequency band into 2 or 4 subbands (named 1, 1P, 2, 2P) and for
each subband, a special CF is defined, which is different with the Standard Definition for CF
(the central frequency of the whole frequency band). To ensure the shown and set CF
corresponding to a certain TX frequency point is corrected and aligned with the AlcatelLucent
definitions, the retrieved TX frequency is mapped into the correct subband, according to the
TX frequency ranges for each subband also stored in the configuration file. For a certain
frequency band in a certain country, the Shifter Amplitude should be unique and could be
retrieved from the configuration file according to the frequency band selection. The RX
Frequency is computed according to the subband, TX Frequency and Shifter Amplitude.
[6] Tx Frequency Exceptions Management

These exceptions related to the computed TX Frequency are managed:
as the TX frequency ranges of the subband may include some overlapping, when the
computed frequency is in the overlapping zone, a dialogue box is poppedout to notice
and require the operators selection for the expected subband;
if working with the TCO Suite PreProvisioning Tool (not interactive), in case the
computed TX frequency could not be supported by any ODU, a message is shown to
notice to the operator and require the rechosen of the Channel Number;
if working with the TCO Suite SetUp Tool (interactive), when the computed frequency
parameters are not aligned with the actual ODU parameters, a message is shown to notice
the trouble to the operator.
[7] 1+1 HSB configuration

In 1+1 HSB configuration, the frequency band, the capacity, the modulation and the country are
chosen only for the CH1 and applied automatically also on the CH0; consequently, the
bandwidth is deduced and then, the channel number must be chosen by the operator to fix the
Tx and Rx frequencies.
[8] 1+1 FD configuration

In 1+1 FD configuration, the frequency band, the capacity, the modulation and the country must
be chosen for the CH0 and CH1; consequently, the bandwidth is deduced and then, the channel
number has to be chosen by the operator to fix the Tx and Rx frequencies.
N.B. For the Remote NE, parameters belonging to this step cannot be modified.
To modify them, the System Settings menu must be used; refer to para. 38.4.1 on page 553
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 ).

3DB 16142 JAAA Ed.01 453 / 866
Step B (Tributary configuration)

REMIND:


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

in Appendix A on page 829
[1] PDH tributary port configuration screen

The screen shown in Fig. 201. 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. 201. Full 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.

454 / 866 3DB 16142 JAAA Ed.01
HOW TO OPERATE IN CASE OF CONFIGURATION WITH ETHERNET PORTS (I.E. WHEN
ENHANCED ETHERNET PLUGIN IS EQUIPPED)
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. 201. on page 454 ) 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. 201. on page 454 to disable one PDH tributary port.
(*) the allowed number of tributaries is as follows:
Tab. 93. Allowed number of PDH tributaries with Ethernet port(s) enabled
Number of allowed
Ethernet
Radio Capacity Number of allowed Ethernet Ports with
Bandwidth
(n.b.1) PDH (E1) Tributaries Enhanced Ethernet
[N x (E1capacity)]
plugin (n.b.2)
2xE1 E1 1 N2
4xE1 E1 3 N4
GE 4
8xE1 E1 7 N8
(10/100/1000BT)
16xE1 E1 15 N 16
32xE1 E1 16 16 N 32
n.b.1 the actually usable Radio Capacity depends on the employed Licence String (see
Tab. 85. on page 404 )
n.b.2 in any combination.
In the screen displayed in Fig. 201. on page 454 (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. 200. on page 450) you have defined 16E1GData, proceed to next substep [2]
on page 456
Otherwise:
to go to the next step click on button Next.
to go back to the previous step click on button Back.

3DB 16142 JAAA Ed.01 455 / 866
[2] Ethernet port configuration tab panels (with Enhanced Ethernet plugin installed)

The configuration tab panels Ethernet GPorts and GEthernet Configuration, described in the

following points 1 ) below, and 2 ) on page 458 , appear only if in Step A (Fig. 200. on page 450)

you have defined 16E1GData.
N.B. For whole information on Ethernet port characteristics and management, refer to the
Appendix A from page 829 (detailed references to it are given in the following).
1) Ethernet GPorts configuration areas

As shown in Fig. 202. below, the configuration area (one for each Ethernet port) contains the
parameters for:
enabling/disabling the port itself ( see para.61.1 on page 829 ),
autonegotiation ( see point [1] on page 830 ),
flow control enabling ( see para.61.5 on page 830 ),
enabling/disabling the auto link shutdown ( see para.61.7 on page 831 ),
the Ingress Rate Limiting Configuration (see Fig. 205. on page 457 ).
Fig. 202. Full Configuration Procedure Step B: Ethernet GPort screen
The speed area changes depending on whether the autonegotiation is enabled or not: when
the autonegotiation is:
not enabled, the Speed without AutoNegotiation area is shown ( see Fig. 203. )
enabled, the Capability Advertised area is shown ( see Fig. 204. )

456 / 866 3DB 16142 JAAA Ed.01
Fig. 203. Speed without AutoNegotiation area
Fig. 204. Capability Advertised area
As shown in Fig. 205. , selecting the Enable checkbox, it is possible to limit the Ingress Rate:
Fig. 205. Ingress Rate Limiting Configuration area
WARNING 1: 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:
WARNING 2: for the MDI/MDIX crossover (AutoMDI/MDIX) feature, read carefully para.61.2
on page 829

3DB 16142 JAAA Ed.01 457 / 866
2) GEthernet Configuration areas (QoS configuration)
QoS configuration can identify two different QoS types (for detailed information on QoS

configuration, refer to point [8] on page 834 ):

by 802.1p mapping mode, with 8 priorities: see Fig. 206.
by DSCP mapping mode, with 64 priorities to be put into the queues: see Fig. 207.
Fig. 206. QoS configuration: 802.1p mapping mode screen
Fig. 207. QoS configuration: DSCP mapping mode screen
The action of choosing any priority in any queue, calls a function, which:
at first, checks if such a priority has already been chosen in another queue. If already been
chosen in another queue, this selection is cancelled.
secondly, performs the second check: when the user makes any operation in queues 2,
3 and 4, all priority values unchecked by queue 2, 3, and 4 are put into queue 1.

458 / 866 3DB 16142 JAAA Ed.01
When the user pushes the Next button, the system checks whether all priority values must be put
into a queue. If no, a confirm window will pop up ( Fig. 208. ). This window shows all priority values
unchecked by any queue. And, it asks whether the user wishes to put the priorities into queue1: if
user presses:
OK, the system chooses the priorities in queue1 automatically
Cancel, the system will do nothing and goes back to the QoS panel.
Fig. 208. QoS configuration: confirmation window
To go to the next step click on button Next.

To go back to the previous step click on button Back.

3DB 16142 JAAA Ed.01 459 / 866
Step C (Vlan Information Configuration)

This step appears only if in Step A (Fig. 200. on page 450) you have defined 16E1GData.

REMIND:
in interactive modality, these screens are set with values taken from NEs data base
in not interactive modality, these screens are set with default values (no Vlan information defined).
In this step [which includes the tab panels Vlan Table and Vlan Tag, described in the following points a )
below, and b ) on page 461 ], the user can enable 802.1Q or 802.1D portbased configuration VLAN,
set IEEE 802.1Q tag VLAN Enable/Disable, and configuration per port VLAN information.
N.B. For whole information on Vlan characteristics and management, refer to para.61.9 from page
835
a) Vlan Table panel

In Vlan Table panel, User can choose 802.1Q or 802.1D. When 802.1Q Vlan is selected, the user
can add/remove/change a Vlan information ( see Fig. 209. ).
Fig. 209. V802.1Q Vlan Configuration
How to proceed:
Define VLANID, the values configurable are in the range 2 4094.
Define VLAN Name: a text string of up to 32 characters. The character of Vlan name cannot use
, >, <, &
Define all ports member of this VLAN (Port Bitmap). All user Ethernet ports and only Radio port
are possible.
Define among the ports belonging to this VLAN (members) those untagged (in egress the VLAN
will be removed from the frames). All user Ethernet ports shall be considered.
By default, all the ports are members of the VLAN and the Untag flag is set to False, which
means that all frames are transmitted with Tag.
Once IEEE 802.1Q tag VLAN is enabled, the incoming Frames are divided into two types:
802.1Q Tagged Frame and Untagged Frame.

460 / 866 3DB 16142 JAAA Ed.01
b) Vlan Tag panel
On each user Ethernet port, it is possible to configure: Acceptable Frame Types and Port VLAN ( see
Fig. 210. )
Fig. 210. Figure 13 Vlan Tag configuration
If the acceptable frame type is set to Admit all frame, the VLANID and PRI fields configured will
be added in ingress to untagged frames. Only VLANID values already defined and the port
included in the corresponding forward membership can be configured for this purpose.
In case no VLANID and PRI values are configured, the following default values are applied:
VLANID= 1, and PRI=0.


3DB 16142 JAAA Ed.01 461 / 866
Step D (Channel configuration)

REMIND:


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. 211. :
1+0
1+1 HSB
1+1 FD
Fig. 211. Full Configuration Procedure: Channels Configuration (Step D)

462 / 866 3DB 16142 JAAA Ed.01
By this screen, you must set two types of configuration data: frequency data (substep [1] on page 463),
and ATPC data (substep [2] on page 465), 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.
[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.111.2 from page 258 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 [3] on page 577 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, perform ATPC data setting (next substep [2] on page
465). (Note: if you have gone to following Step G, go back to this Step D).

3DB 16142 JAAA Ed.01 463 / 866
2) Non interactive mode
In the screen of Fig. 211. on page 462, click the Frequency Data Help button. The screen of

following Fig. 212. opens.

N.B. If you have used the Regional Settings [ see point i ) on page 452 ], this step must not
be executed (and the Frequency Data Help button is greyed)
Fig. 212. Frequency Data Help: choice of ODU type
According to the ODU system to be configured, click on relevant line. The screen of following
Fig. 213. opens.
values used in
example of
Fig. 214. below
Fig. 213. 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.111.2.1 from page 259 (Part lists of ODUs with external diplexer)
para.111.2.2 from page 263 (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. 211. on page 462.
Following Fig. 214. shows an example of Frequency Data manual setting with values taken
from the table of Fig. 213. above.

464 / 866 3DB 16142 JAAA Ed.01
Fig. 214. Example of Frequency Data manual setting
[2] ATPC data setting

In the Channel Configuration area of Fig. 211. on page 462, 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. 215. )
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. 216. ):
strictly following rules stated in para. 311.5 on pages 578 to 580
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. 215. RTPC setting with ATPC disabled

3DB 16142 JAAA Ed.01 465 / 866
Fig. 216. Setting of enabled ATPC
In case of 1+1 FD, two tabbed panes (as previous Fig. 215. and Fig. 216. ) 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. 217. below).
Fig. 217. ATPC and RTPC Configuration for both channels (1+1 HSB)


466 / 866 3DB 16142 JAAA Ed.01
Step E (Link Identifier configuration)
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. 218. 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 = B

sent identifier = A received identifier = A
STATION A STATION B
When the mismatch detection is enabled and the value of the incoming identifier is different from the
expected one, a Link Identifier Mismatch (LIM) is notified and an AIS signal will be inserted down stream.
Link identifier functionality is managed per NE: in case of 1+1 radio configurations the same link identifier
code is used on both the radio channels.
Link identifier functionality is performed by 5 bits link code, then 32 values link code are allowed.
Fig. 218. Full Configuration Procedure: Link Identifier configuration (Step E)

3DB 16142 JAAA Ed.01 467 / 866
Step F (Automatic restoration criteria configuration)

REMIND:


This step (Fig. 219. 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. 219. Full Configuration Procedure: Automatic restoration criteria configuration (Step F)
To go to the next step click on button Next .

468 / 866 3DB 16142 JAAA Ed.01
Step G (OSPF area configuration)
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. 220. below) allows to configure one or more OSPF Areas (3 areas max.).
Fig. 220. Full Configuration Procedure: OSPF Area Configuration (Step G)
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.

3DB 16142 JAAA Ed.01 469 / 866
Step H (Configuration of Local IP address, Ethernet and Network Time Protocol)

REMIND:


Fig. 221. Full Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step H)
This step (Fig. 221. above) allows to configure the Local IP address, the Ethernet interface IP address,
and the Network Time Protocol:
a) the Local IP address

The Local IP address is the address by means of which the NE is uniquely identified inside the
Transmission Management Network (TMN), whichever the physical access is:
local F interface (RS232), see Fig. 181. on page 411
remote point to point TMNRF, TMNV11 and TMNG703 (see next Step I on page 472 )
and also if the access is made through the Ethernet management interface, described below
b) the Ethernet interface

This Ethernet interface corresponds physically to the NEs Ethernet management interface; see
This Ethernet interface can be Enabled or Disabled by ticking the TMN Ethernet field (default is
Enabled). If enabled, in the relevant fields, enter 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.
These routing data are those necessary to identify uniquely the NEs Ethernet management interface
inside the TCP/IP network, which the TMN is interfaced to.

470 / 866 3DB 16142 JAAA Ed.01
c) Rules for the definition of the local IP address and Ethernet Configuration IP address
Refer to para.32.2.2 on page 414

d) 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.
See also How to configure the NTP in a network on page 534


3DB 16142 JAAA Ed.01 471 / 866
Step I (Configuration of TMNRF, TMNV11, and TMNG703 or TMNin frame channels)

REMIND:


Fig. 222. Full Configuration Procedure: Configuration of TMNRF, TMNV11 and TMNG703 channels
(Step I)
This step (Fig. 222. above) allows to configure the following TMN channels:
a) TMNRF, TMNV11, and TMNG703 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 be managed by a Craft
Terminal or TMN system accessing the remote station of the radio link (see Fig. 183. on page
413 ). Usually, it must be enabled, and left with all default values).
through the TMNV11 or the TMNG703 interface, the NE can be managed, with
PointtoPoint Protocol (PPP) by a TMN system. The physical implementation for wired
interfaces is described in:
para.112.13.4 on page 322 (TMNV11)
para.112.13.5 on page 323 (TMNG703)
In alternative to the TMNG703, the TMN inframe can be defined, as described in
point b ) on page 473
N.B. Refer to para.18.3.2 on page 209 , for additional information (channel continuity in TMN
pointtopoint or ring configurations)
Each TMN channel can be Enabled or Disabled by selection in its own Enable field.
If enabled and active (and in interactive modality only), the IP address of the remote connected point
appears in the readonly field Remote Address (in the case of TMNRF, it is the NEs local IP
address of the other NE of the radio link)

472 / 866 3DB 16142 JAAA Ed.01
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.
b) TMNin frame channel
In alternative to the TMNG703, the TMN inframe can be defined.
With this TMN inframe feature, the 9400AWY equipment is able to introduce in one of the time slots
(TS 131, except TS 16) 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).
WARNING: the E1#1 tributary must be enabled and framed, and the chosen timeslot must be
the same, in all NEs that must be crossed by the TMN inframe, as depicted in
Fig. 223. below:
TMNRF + TMNRF +
TMNin frame TMNin frame
TMNin frame
AWY AWY AWY AWY
TMNin frame TMNin frame

E1#1 framed and enabled
with TMNin frame in timeslot n
(n the same in all NEs)
Fig. 223. Conditions for setting the TMN inframe

3DB 16142 JAAA Ed.01 473 / 866
To activate the TMN inframe feature:

by the screen of Fig. 201. on page 454 , verify (or set) that the first E1 tributary is enabled and

framed

by the screen of Fig. 224. below, in TMN G703 field:
set Mode to InFrame E1
define the chosen timeslot number (default 1) of the E1#1 tributary (only E1#1 is supported)
DO NOT SPECIFY TIMESLOT 16 !

Fig. 224. Full Configuration Procedure: Configuration of TMN inframe (Step I)


474 / 866 3DB 16142 JAAA Ed.01
Step J (IP Static Routes Configuration)
REMIND:
This step (Fig. 225. below) configures one or more Static Routers.
Fig. 225. Full Configuration Procedure: IP Static Routes Configuration (Step J)
The following fields and data are present:
[1] Host Address: allows to define the IP address necessary to reach a specific Host.
[2] Network Address: it is in alternative to the Host Address; allows to define the IP Mask to reach
a network.
[3] Gateway Address: allows to define the address of the next hop gateway.
[4] PPP: it allows to use the point to point interfaces (the 3 NMS channels) available
with the NE.
WARNING: No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.

3DB 16142 JAAA Ed.01 475 / 866
N.B. Default Gateway Routing configuration

It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 225. on page

475 select Network Address. The screen changes to following Fig. 226. :

REMIND:
Fig. 226. Full Configuration Procedure: Default Gateway Routing configuration (Step J)
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

476 / 866 3DB 16142 JAAA Ed.01
Step K (Access List Configuration)
Please refer to para.313.3 from page 596

Step L (Trusted Manager Information)
N.B. This setting is independent from that of TCO Suites Alarms & Settings NAT option on page
493
By this step (Fig. 227. below) a maximum number of 5 of IP Addresses and IP Ports for max corresponding
Trusted Managers can be configured (added, removed or changed) in the Trusted Managers table.
N.B. In case the Provisioning Tool is run:
in not NEinteractive mode (offline), all operators can obviously write the table
in NEinteractive mode (online), only a user with the Administrator profile can read and write
the table, and, at the end of the configuration, can apply it to the NE.
To avoid conflicts, only one Administrator at a time (the first who logs in the NE by the online
Provisioning Tool) can fill the table; the others are excluded till the completion of the job.
The Trusted Manager functionality allows to register in permanent way inside the NE, the managers (the
trusted managers) that have to supervise the NE via SNMP protocol. This means that the Polling
functionality (the registration performed by the manager itself via SNMP to start the NE supervision and
consequent checks NE side) is not anymore necessary for the trusted managers. This registration is
stored in the NE in permanent memory.
Furthermore this functionality can be used to overcome the problems caused by the usage of a static NAT
router between the manager and the NE, including the alarm/event notifications and the endtoend
security check.
The Trusted manager is identified by an IP address and UDP port. When this functionality is used with
a static NAT router, the IP address of the manager must be the one translated by the NAT router. The
association between the internal IP address and the public IP address of the manager has to be configured
statically on NAT router.
N.B. For the relationship between the SNMP Access List table, and the Trusted Manager table,
read carefully point d ) on page 597
Fig. 227. Full Configuration Procedure: Trusted Manager Information (Step L)

3DB 16142 JAAA Ed.01 477 / 866
Step M (EOW and Auxiliary Interface Configuration)

REMIND:


in not interactive modality, fields of this screen are with default values
This step (Fig. 228. 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 52 on page 743 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.112.13.6 on page 324 for details)
the field Party Line Status in the Party Line area allows the operator to squelch (Enabled
unselected) the EOW audio signal (see WARNING and Fig. 115. on page 209 for usage example)
Fig. 228. Full Configuration Procedure: EOW and Auxiliary Interface configuration (Step M)

478 / 866 3DB 16142 JAAA Ed.01
Step N (External Input and Output Points Configuration)
REMIND:
This step (Fig. 229. below) configures the external points (please refer to para.112.13.2 on page 317
for physical implementation).
Fig. 229. Full Configuration Procedure: External Input and Output Points configuration (Step N)
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

3DB 16142 JAAA Ed.01 479 / 866
Step O (Summary)

This is the last step (Fig. 230. below). The screen shown summarizes all the parameters configured during

this procedure and some relevant parameters with default values.

Fig. 230. Full Configuration Procedure: Summary (Step O)
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 463 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.

480 / 866 3DB 16142 JAAA Ed.01
35 ALARMS & SETTINGS
This chapter describes in detail the Main MenusAlarms & Settings functions.
Subject On page
Alarms & Settings overview, startup, and closing below
Alarms & Settings functions 482
Date & Time Setting 484
Configuration Setting 485
Configuration Info 485
Get Configuration File 490
Active Alarms 491
Power Measurement 492
Modem Speed 492
Licence Info 493
NAT option 493
35.1 Alarms & Settings overview, startup, and closing
The Alarms & Settings function is a NEinteractive function, allowing 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.
N.B. Besides from the Local Copy of the TCO Suite, it can be run also directly from the TCO SUITE
CDROM, without performing the copy procedures of the chapter 41 from page 667
Procedure
a) Start of the application

To start this application, and login the NE, strictly follow instructions given in para.33.5 on pages
434 to 438
b) Use of the application

After having successfully connected to the NE and loggedin it, the screen of Fig. 231. on page
482 appears.
c) Exiting from the application

Strictly follow instructions given in para.33.5.3 on page 439

3DB 16142 JAAA Ed.01 481 / 866
35.2 Alarms & Settings functions

Fig. 231. Alarms & Settings Main Menu screen
WARNING 1: when PC to NE connection is established, a timeout for an automatic logout is set, so

that after 5 minutes of connection without user operations, the application logouts
automatically (for security purposes), and user is obliged to repeat again login.
WARNING 2: if, during the usage of the 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 Alarms & Settings session, then verify the NE reachability (e.g. by
ping function), and login it again.

482 / 866 3DB 16142 JAAA Ed.01
The operations allowed according to the Login profile (refer to point [2] on page 420 for details) are:
Tab. 94. Operations allowed in the Alarms & Settings screen according to the Login profile
Function type Operation allowed according to Login profile

and where described Administrator CraftPerson Operator Viewer
Date & Time Setting

set & read read only read only read only
Configuration Setting
YES YES NO NO
Configuration Info
YES YES YES YES
Get Configuration File

YES YES YES YES
Active Alarms
YES YES YES YES
Power Measurement
set & read set & read read only read only
YES
Licence Info
(with licence read only read only read only
management)
Community String
YES NO NO NO
Access List Restore

YES NO NO NO
point [6] on page 598
Access List Backup

YES NO NO NO
point [5] on page 598
Modem Speed
set & read set & read set & read read only
NAT Option
set & read set & read NO 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. 231. on page 482 ) 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.

3DB 16142 JAAA Ed.01 483 / 866
35.2.1 Date & Time Setting

For set & read authorized users ( see Tab. 94. on page 483 ), 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).
The read only authorized users ( see Tab. 94. on page 483 ) cannot make any setting operation.
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. 232. 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. 232. Alarms & Settings Date & Time Setting request
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

484 / 866 3DB 16142 JAAA Ed.01
35.2.2 Configuration Setting
For authorized users ( see Tab. 94. on page 483 ), the Configuration Setting process allows the operator
for sending to NE the operators desired configuration.

The unauthorized users ( see Tab. 94. on page 483 ) cannot see this screen.
Fig. 233. 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 Provisioning Tool), and then click on Apply Configuration button.
35.2.3 Configuration Info
The Configuration Info 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. 234. 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. 234. Alarms & Settings Configuration Info request

3DB 16142 JAAA Ed.01 485 / 866
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.

An example of this file content is shown below:

CONFIGURATION INFO
==================
Site Name: uls213_107
Site Location: tp
INSTALLED SOFTWARE:

[Active SW Package: R94A V02.01.03]
Status: Committed
Operational State: Enabled
SW Units:
OC_R V03.00.01 Size(Bytes): 1334619
EC V03.03.17 Size(Bytes): 2787100
NETWORK EQUIPMENT CONFIGURATION:

NE Configuration Type:1+1 HSB 16E1 GETH (PSU4860) EPS
Market: ETSI
Capacity: 32E1
Modulation: 16QAM
TRIBUTARY CONFIGURATION:

Impedance: Balanced 120 Ohm
E1 Port #1: Signal Mode: Unframed
E1 Port #2: Signal Mode: Unframed
E1 Port #3: Signal Mode: Disabled
DATA CONFIGURATION:

[Ethernet Port 33]
Status: Disabled
Auto Negotiation: Enabled
Speed without AutoNegotiation: 100 Mbit/s
Flow Control Status (tx): Asymmetric
AutoNegAdvertise rate ability:
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
1000base Full Enable
Qos Classification Mode:
802.1p
Vlan Accept Frame Type:
all
Vlan Pvid:
1
Vlan Priority:
0
Autolink Shutdown Status:
Disabled

486 / 866 3DB 16142 JAAA Ed.01
Rate control value:
0
[Ethernet Port 34]
Status: Disabled

10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0
Disabled
Rate control value:
0
[Ethernet Port 35]
Status: Disabled
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0
Disabled
Rate control value:
0
[Ethernet Port 36]
Status: Disabled
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0

3DB 16142 JAAA Ed.01 487 / 866
Disabled
Rate control value:
0

Eth Vlan Bridge Type:

802.1Q
Static Vlan Xconn:

[Vlan Xconn: 1]
vlan name: Default VLAN_1, VID:1, untagPort:15, egressPort:31
RESTORATION CRITERIA:

Radio Protection: Revertive
Mux/DeMux Protection: Revertive
HSBTx Protection: Revertive
RADIO CONFIGURATION:

[Channel 1]
ATPC Status: Disabled
RTPC Tx Power: 10.0 dBm
Tx Frequency: 14500000 kHz
Tx Range: [14500000; 14724000] kHz
Rx Frequency: 14920000 kHz
Rx Range: [14920000; 14920000] kHz
Shifter Central Frequency: 14612000 kHz
Shifter Amplitude: 420000 kHz
[Channel 0]
ATPC Status: Disabled
RTPC Tx Power: 17.0 dBm
Tx Frequency: 14500000 kHz
Tx Range: [14500000; 14724000] kHz
Rx Frequency: 14920000 kHz
Rx Range: [14920000; 14920000] kHz
Shifter Central Frequency: 14612000 kHz
Shifter Amplitude: 420000 kHz
LINK IDENTIFIER:

Expected Mode: Disabled
Expected Value: 0
Sent Value: 0
ETHERNET CONFIGURATION:

Local IP Address:
130.1.1.107
Status: Enabled
IP Address:
172.25.20.107
IP Mask:
255.255.255.0
MAC Address:
00:11:3f:c0:ee:66
Routing Protocol: OSPF

OSPF Area:0
[Network Time Protocol]:

Status: Enabled
Main Server: 151.98.99.242
Spare Server: 151.98.99.244
OSPF AREAS:


488 / 866 3DB 16142 JAAA Ed.01
[Ospf Area 0]
IP Address: 0.0.0.0
Stub Area: OFF
[Ospf Area 1]
IP Address: 130.0.0.0
Stub Area: OFF
[Ospf Area 2]
IP Address: 0.0.0.2
Stub Area: OFF
TMN INTERFACES:

[TMNRF]
Status: Enabled
RF Remote Address: 130.1.1.108
Routing IP Protocol: OSPF
OSPF Area:2
[TMNV11]
Status: Enabled
Remote Address: 130.1.1.108
Mode: Codirectional
OSPF Area:2
[TMNG703]
Status: Enabled
Remote Address: 130.1.1.101
Mode: Codirectional
OSPF Area:0
STATIC ROUTES:

EXTERNAL POINTS STATUS:

[Input Point 1]
User Label:CPI#1a
Polarity: Active Closed
[Input Point 2]
User Label:CPI#2a
Polarity: Active Open
[Input Point 3]
User Label:CPI#3a
[Input Point 4]
User Label:CPI#4a
[Input Point 5]
User Label:CPI#5a
[Input Point 6]
User Label:CPI_6_prova
[Output Point 1]
User Label:fuori1
Working Mode: Manual
External State: Off
[Output Point 2]
User Label:CPO#2222
External State: Off
[Output Point 3]
User Label:CPOtre
Working Mode: Automatic

3DB 16142 JAAA Ed.01 489 / 866
Associated Event: Line side LOS Alarm
[Output Point 4]
User Label:CPO#4444


External State: Off
[Output Point 5]
User Label:FAIL IDU
[Output Point 6]
User Label:FAIL ODU CH#1
[Output Point 7]
User Label:FAIL ODU CH#0
The content above describe a sample configuration report in text format.
35.2.4 Get Configuration File
Just like the Configuration Info function function, the Get Configuration File function 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 the Provisioning Tool. Selecting (by click) this
function from main menu will show the user a Save File screen (Fig. 235. 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. 235. Alarms & Settings Get Configuration File request
This file is an XML standardbased set of configuration information that the Provisioning Tool can preview
in a humanreadable HTML layout and allow the user to modify such configuration using a set of
wizard/simplified steps.

490 / 866 3DB 16142 JAAA Ed.01
35.2.5 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. 236. 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. 237. below).
Fig. 237. 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.

3DB 16142 JAAA Ed.01 491 / 866
35.2.6 Power Measurement

According to Tab. 94. on page 483 , this page ( Fig. 238. below ) allows:

authorized set & read users, to set the power measurement
all users, to read the power measurement result.
Refresh Interval filed allows 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. 238. Alarms & Settings Power Measurement request
35.2.7 Modem Speed
According to Tab. 94. on page 483 , this page ( Fig. 239. below ) allows:
all users, to read the current FInterface speed value
authorized set & read users, to modify it, through a simple combo box.
N.B. see also para.62.7 on page 847
Fig. 239. Alarms & Settings Modem Speed request

492 / 866 3DB 16142 JAAA Ed.01
35.2.8 Licence Info
This screen allows an operator loggingin the NE with the Administrator profile, to read and manage
dynamically the license information, as described in point [1] on page 424

N.B. in case of login profile different from Administrator, the Set Licence key field and Apply button
are not available, so that only the read operation is possible.
Fig. 240. Alarms & Settings Licence Info request
35.2.9 NAT Option
According to Tab. 94. on page 483 , this page ( Fig. 241. below ) allows authorized set & read users,
to set the NAT Option, described in the following.
The unauthorized users (see Tab. 94. on page 483 ) cannot see this screen.
Fig. 241. Alarms & Settings NAT option request
N.B. This setting is independent from that of PreProvisioning and SetUp tools Step L on page
477

3DB 16142 JAAA Ed.01 493 / 866
[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. 242. 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.
[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) when an application payload includes an IP address,

2) the FTP application unless to operate dedicated setting and
3) 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.

494 / 866 3DB 16142 JAAA Ed.01
[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
No registration Standard Access Control
NE Reset NOK OK
Loopback commands NOK OK
Shifter management NOK OK
3) 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

3DB 16142 JAAA Ed.01 495 / 866
496 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
36 NETO (NETWORK ELEMENT OVERVIEW)
This chapter describes in detail the functions of NEtO.
Subject On page
General on NEtO 498
NEtO functions 498
NEtO sessions and constraints 498
NE access constraints 498
Summary of actions 499
Preliminary operations 499
Operations with NEtO 500
Details on NEtO screen 505
Supervision Function 505
Supervision and Alarm Synthesis roundshaped icons 505
NEtO screen minimize and restore 506
NEtO icon in the tray bar 506
NE Configuration 507
Command Buttons 508
How to close the NEtO session 508
NEs List Management 509
Main actions with NEtO On pages
perform the preliminary operations before to startup one NEtO session 499
startup one NEtO session 500
start the supervision of one NE, and choose (if necessary) the PCNE
502 to 504
connection (F or Ethernet or NMS connection)
start the WebEML application on the supervised NE

start the Alarm Monitor application on the supervised NE 508
close the NEtO session

3DB 16142 JAAA Ed.01 497 / 866
36.1 General on NEtO
36.1.1 NEtO functions

NEtO (Network Element Overview) is the starting point for 9400AWY V2.1.3 WebEML application.
Following functions are allowed:
Starting of Supervision of a 9400AWY NE (status and alarms summary)
Starting of WebEML on a supervised 9400AWY NE
Starting of AM (Alarm Monitoring) on a supervised 9400AWY NE
Creation/Save/Retrieve/Modify of one (or more) list of favorite NEs
that are described in detail in the following.
NEtO application allows user to execute its functions through mnemonics keyboard shortcuts, as
described in detail in the following.
36.1.2 NEtO sessions and constraints
[1] NEtO session
NEtO works as a singlesession instance dedicated to one NE only.

It means that if you have one NEtO instance open for one NE (and you want to leave it open), you
must launch another NEtO instance to access another NE.
WARNING: Even if allowed by SW, opening more than one NEtO session (from the same PC)
on the same NE is a forbidden operation, and must be absolutely
avoided.
[2] Max number of contemporaneous NEtO sessions
The number of NEtO sessions, that can be run at the same time (from the same PC), depends on
the PC performance (processor type, RAM size, operating system type, etc.) and the possible
contemporaneous run of RAMeating and processorstressing programs).
As a general rule, the following figures can be considered reasonable:
max 5 NEtO sessions used for NE supervision only (i.e. without logging in the NE for the
WebEML and AM functions)
or max 2 NEtO sessions used for NE management by WebEML and AM
At any rate, the attempt to launch one more NEtO session, in addition to those already running, which
would override the available computer resources, is solved automatically simply ignoring it, without
any error message. Then, you must at first close one of the running NEtO sessions, to open another
one.
36.2 NE access constraints
The following limitations (relevant to the NE access, not to the NEtO session) must be taken into account:
a) the contemporaneous presence on one NE of various managers (LCT, RCT and an OS) is possible,
from different WebEML Craft Terminals or OS. The access disable flag avoids access conflict
between the OS and both RCT and LCT on some operations, like configuration modification and
remote control with access filtering.
b) at most ten OS/LCT/RCT access instances can be active at a time over one NE :
one local LCT access instance only (on NEs Finterface)
plus nine remote RCT/OS instances at most (on NEs Management Ethernet interface, and on
Radio interface and NMS interface
The coexistence of OS, LCT and RCT access instances in the whole network is guaranteed, since
the conflict in accessing the NE is solved locally by the NE itself.

498 / 866 3DB 16142 JAAA Ed.01
36.3 Summary of actions
36.3.1 Preliminary operations

a) Make cable and network connections (if not yet done)
According to the chosen CTNE access type, make, or verify, the relevant physical connection (local
or remote) between the CT and the NE, as depicted in:
Fig. 180. on page 410 (physical interfaces for the 9400AWY NE management)
Fig. 181. on page 411 (access through NEs F Interface)
Fig. 182. on page 412 (access through NEs Ethernet Interface)
Fig. 183. on page 413 (access through NEs radio Interface and NMS rings and chains)
N.B. The CTNE local connection through NEs Ethernet Interface is highly recommended
when commissioning and maintenance tasks must be performed.
Warning about the NE connection to the TCP/IP network and to the NMS network
These connections must not be done until the network routing data of the NE have been
correctly defined. This definition is performed during the firsttime equipment startup and
commissioning ( described in Chapter 42 from page 675 )
b) Power on the PC and wait for its startup (if not yet done)
c) Only in case of CTNE connection through the F interface

WARNING 1: for the use of the F interface, the LLMAN (Lower Layer MANager) installation and
configuration must have already be performed, as described in para.41.4.1 on
page 669
WARNING 2: to use the LLMAN, check/set the suitable PC desktop Properties System standby
and System hibernates, that must be both set to Never, as shown in Fig. 386. on
page 670
WARNING 3: to use the F interface, you must at first start manually the LLMAN. To do that, perform
operations described in point b ) on page 670
d) Only in case of CTNE connection via public switched telephone network (through the F interface):
After having performed operations of previous step c ) , set up the connection on the public switched
telephone network, as described in para.62.6 on page 846
e) Perform the checks listed in para.33.4 on page 433

3DB 16142 JAAA Ed.01 499 / 866
36.3.2 Operations with NEtO

a) Startup one NEtO session

WARNING 1: NEtO can be run only if the Local copy of WebEML (Jusm/CT) has already been
performed, as described in para.41.3 on page 668
WARNING 2: if not yet done, read carefully para.36.1.2 on page 498
WARNING 3: if the PCNE physical connection is made on the serial interface, be sure to have
started LLMAN [ see point c ) on page 499 ]
The startup of one NEtO session can be done:
clicking the Shortcut to the Local copy of WebEML ( see Fig. 385. on page 668 )
AWY_CT_V01_07
or clicking the button Operational & Maintenance WebEML of the Main Menu screen ( see
Fig. 188. on page 432 )
The NEtO initial screen opens, allowing operations depicted in Fig. 243. :
icons for NE list management (see para.36.5 on page 509 )
shrink glass (see para.36.4.3 on page 506 )
insert the NE read

write Community
String of one
NE (if necessary)
[step b )
on page 501 ]
para.36.4.6
on page 508
if present,
ignore this field
start the supervision of one NE

[step c ) on page 502 ]
Fig. 243. NEtO initial screen

500 / 866 3DB 16142 JAAA Ed.01
b) Insert the NE readwrite Community String (if necessary)
N.B. this operation is meaningful only if the NE Administrator has defined a community string
(different from the default value) for the specific NE you want to login (details in
para.32.3.3 on page 421 ). To proceed, you must know this string, and you must write
it before to start the Supervision of such NE.
To make this operation, click the button CS (Community String) on the open NEtO initial screen
(Fig. 243. on page 500 ). The following screen opens:
Insert the Community String, then click OK
(1)
(2)
N.B. the button Use Default resets the community string at the default value, at NEtO side
only.
Now, you can start the Supervision of such NE [ step c ) on page 502 ]
WARNING: in the case you want, in the following, access another NE in the same NEtO session,
you must be aware that this community string setting remains active at NEtO side
until you reset it by the button Use Default, or change it clicking again on button CS,
or when you close the NEtO session.

3DB 16142 JAAA Ed.01 501 / 866
c) Start the Supervision of one NE

WARNING: in the case the NE Administrator has defined a community string (different from the

default value) for the specific NE on which you want to start the supervision, be sure

to have performed the operation described in step b ) on page 501
From the open NEtO initial screen ( Fig. 243. on page 500 ), to start the Supervision of one NE,
operate as depicted in Fig. 244. below (for details refer to para.36.4.1 on page 505 ).
(1) insert the

NE address
(read WARNING below) (2) click
para.36.4.6
on page 508
(3) step d ) on page 503 ,

or step e ) on page 504 ,
or error message,
depending on NE reachability
WARNING: if the local IP address and Ethernet Configuration IP address are different, you
must specify the local IP address : for details, refer to to para.32.2.2 on page 414
Fig. 244. Start Supervision for one NE in NEtO initial screen

502 / 866 3DB 16142 JAAA Ed.01
d) Choice (if necessary) of the network adapter for PCNE connection
If more than one network adapter is found in the PC, the following screen appears (an example),
where user must select the one to use and then click OK.
In the case of PCNE connection by F interface, and provided that LLMAN has been manually
started [see point c ) on page 499 ], you must select the Virtual Network Card that has been
associated to the PC serial interface
N.B. You can know this association by means of the Lower Layers Settings screen, that
can be opened by Windows command Start % Programs % AlcatelLucent %
Lower Layers % Lower Layers Settings
If the connection is correctly established, the NEtO screen changes as in Fig. 245. (NE
supervised).

3DB 16142 JAAA Ed.01 503 / 866
e) Operations possible for a supervised NE

For a supervised NE, operations depicted in Fig. 245. are possible:

[B] [C] [A]
[A] get information regarding the NE Supervision and Alarm Synthesis states
Details in para.36.4.2 on page 505
[B] get/change data regarding the NE Information and/or the NE Description; or move to the
supervision of another NE (closing the current NE supervision)
[C] start WebEML and/or Alarm Monitor, or exit from NEtO

Fig. 245. Operations possible for a supervised NE

504 / 866 3DB 16142 JAAA Ed.01
36.4 Details on NEtO screen
36.4.1 Supervision Function

The supervision function allows operator registering himself/herself as a new manager inside NE MIB and
performing cyclic (periodic) monitoring on connection. To start supervision, operator must specify NE IP
address in the IP Address field, and then simply press OK button (see Fig. 244. on page 502 ).
If supervision succeeds, screen is updated with information retrieved from NE and supervision icon
changes its color from gray to green, stating NE is correctly supervised, as described in para.36.4.2
below.
When a supervision error, a link down or other problems arise during supervision, icon will become red.
Alarm Synthesis area will be updated as well.
To end an ongoing supervision, simply click on Exit button (this will also close NEtO) or change NE IP
address and click OK button to start supervision procedure on a different NE (this will stop previous
supervision).
36.4.2 Supervision and Alarm Synthesis roundshaped icons
Information on supervision status and active alarms are shown in this area ( Fig. 246. ).
Fig. 246. Supervision and Alarm Synthesis roundshaped icons
Roundshaped icons change their colors according to current NEtO functions and situation:
as far as the Supervision icon is concerned:

gray color means that supervision is not active (to be started)
green color means that supervision function is ongoing
red color means that NE link does not work
the Alarm Synthesis area is enabled only if the supervision is active (Supervision icon green).
It contains the possible alarm severities, accompanied by the number of alarms affecting the specific
type. Alarms and supervision state colors for icons are the same and default for all AlcatelLucent
devices):
green color means that no alarms are present
red color is always assigned to the icon of Critical alarms (if any)
orange color is always assigned to the icon of Major alarms (if any)
yellow color is always assigned to the icon of Minor alarms (if any)
cyan color is always assigned to the icon of Warning alarms (if any)
white color is always assigned to the icon of Indeterminate alarms (if any)
More details on the active alarms can be obtained in the Alarm Monitoring screen, that can be opened
by the suitable command button (see para.36.4.6 on page 508 ).

3DB 16142 JAAA Ed.01 505 / 866
36.4.3 NEtO screen minimize and restore

NEtO screen can be minimized using the shrink glass button in the Menu Bar.

Fig. 247. shows the reduced NEtO view, allowing the user to save screen space while continuously
checking supervision and alarms status.
The magnifying glass button allows showing normal NEtO screen.
magnifying glass
Fig. 247. NEtO screen: reduced screen
36.4.4 NEtO icon in the tray bar
Alarm severity icon shown in Fig. 247. will appear in operating system tray bar (see Fig. 248. ), close
to system clock and other system software icons.
Fig. 248. Alarm severity icon in system traybar
This icon will also have a specific tooltip, visible when mouse cursor is moved over it, that will show: name
of application, NE IP address, and highest severity alarms number.
Traybar icon is not interactive and does not present any menu or executable command if clicked either
with left or right mouse button.

506 / 866 3DB 16142 JAAA Ed.01
36.4.5 NE Configuration
The panel is made by these areas:

NE Info section, containing information related to NE addressing;

NE Description section, with information about NE characteristics;
[1] Network Element Information

This area is related to wanted NE identification ( Fig. 249. ).
Fig. 249. NEtO NE Configuration View: NE Information
IP Address parameter displays the actual NE IP address used by NEtO functions. SNMP port is the
default standard number 161, so not shown.
This box shows only IP address information, while status information is provided by the second area
of NEtO window. OK button will start supervision on specified NE, if reachable.
Keyboard shortcut Alt + o behaves as clicking on OK button with mouse.
Whenever a stop supervision is needed, user can both click on Exit button (see Fig. 251. ), so
stopping supervision and closing NEtO, or by simply changing NE IP Address, writing a new one,
and then clicking on OK. This step will stop existing supervision starting supervision on the newly
specified NE.
WARNING: whenever you have written, in step b ) on page 501 , a community string, you must
be aware that this setting remains active at NEtO side until you reset it by the button
Use Default, or change it clicking again on button CS, or when you close the NEtO
session.
Whether IP address is correctly written, other than clicking on OK button, supervision process will
start on specified NE by pressing enter (carriage return) key on keyboard.
[2] Network Element Description

This area ( Fig. 250. ) contains some parameters displaying general information about supervised
NE:
Fig. 250. NEtO NE Configuration View: NE Description
a) The readonly field Type ULS means always 9400AWY NE. The readonly field Version
shows the Flash Cards SW COMMIT VERSION presently running on the NE: see point [2]
on page 425
b) The parameters Site Name and Site Location can be read and modified (and applied to NE
using the Apply button). Please note that changing these labels values will also automatically
update NEtO window title content: window title will always contain Site Name of supervised
NE.
WARNING: Site Name and Site Location name cannot contain special characters, such
as <, >, &, and
Keyboard shortcut Alt + a behaves the same as clicking on Apply button with mouse.

3DB 16142 JAAA Ed.01 507 / 866
36.4.6 Command Buttons

Fig. 251. shows the command buttons available on NEtO screen:

Fig. 251. NEtO NE Configuration View: Command Buttons
Show and Alarm Monitor buttons are enabled only when a NE is supervised:
the Show button starts the WebEML application on the supervised NE.
WARNING: the Show button is greyed (i.e. not selectable) in the case the WebEML
application has already been started.
Notice that, besides from this NEtO screen, the WebEML application can be
launched also through the Navigate from AM to USM function (see
para.315.2.9 on page 617 )
Keyboard shortcut Alt + S behaves as clicking on Show button with mouse.

For details on WebEML, refer to Chapter 37 on page 511
the Alarm Monitor button starts AM application on the supervised NE.

WARNING: the Alarm Monitor button is greyed (i.e. not selectable) in the case the AM
application has already been started on the specific NE.
Notice that, besides from this NEtO screen, the AM application can be launched
also by the WebEML application:
through the command Diagnosis % Alarms % NE Alarms
or through the Navigate from USM to AM function (see para.315.2.10
on page 618 )
Keyboard shortcut Alt + m behaves as clicking on Alarm Monitor button with mouse.
For details on AM, refer to Chapter 315 on page 605
Exit button is always enabled.

The Exit button only ends the NE supervision (if active), and closes the NEtO application.
WARNING: the Exit button does not close other related applications. Therefore, to close one
NEtO session, operate as described in para.36.4.7 below
Keyboard shortcut Alt + E behaves as clicking on Exit button with mouse.
36.4.7 How to close the NEtO session
a) If open, close the NE JUSM window ( Fig. 253. on page 513 ) clicking
b) if open, close the Alarms Monitor window ( Fig. 329. on page 608 ) clicking
c) only when both buttons Show and Alarm Monitor have become black (i.e. selectable), you can
click on Exit button. This ends the NE supervision (if active), and closes the NEtO windows and
application.
N.B. if you try to Exit the NEtO application while the NE JUSM window and/or the Alarms Monitor
window is/are still open, the NEtO screen goes to a permanent hung state, even if, after, you
will close them (in this case, you must close NEtO by Task Manager, or restarting the PC).

508 / 866 3DB 16142 JAAA Ed.01
36.5 NE list management
OPEN (loads a file containing
a list of favorite NEs)

NEW (creates a new OPEN (opens the current

list of favorite NEs) list of favorite NEs)
NEtO can manage and organize one (or more) list(s) of available NEs by showing user a table containing
such data. Using both (New) and (Open) icons, user will be able to open NEs table modal window
(see Fig. 252. ).
Fig. 252. NEtO List Management
While Open icon allows opening a previously saved file containing a list of NEs, New icon allows
creating a new list, specifying file name containing its data only when those data will be saved. Window
allows user managing its NEs data by:
Get Current button is used to read information from main NEtO view. This operation always adds
a new line in NE list table with all information related to currently supervised NE. This happens even
though a NE with corresponding IP address is still present in the list;
New button, adding a new NE from scratch. This allows user to fill the IP Address field only with
its needed NE.
Remove button, removing a selected NE;
Set Current button, filling main NEtO view IP address with datum from selected NE. User must
previously select a valid line in NEs table and then click on Set Current button so filling NEtO main
window data. This operation will automatically close the NE list window but does not start supervision
on set NE;
Save button, saving table list in a specified file.

3DB 16142 JAAA Ed.01 509 / 866
All data are saved in a custom XML format called NEtO and this structured file will contain all data shown
in Fig. 252. related to all NEs added to the list. This XMLbased file is further customized so helping user

easily identifying this kind of files within a huge set of files: instead of using the common .xml file

extension, a specific .NEtO file extension is used, both in file names and in filtering files while

opening/saving.
User can have its own NEs lists repository, containing all .NEtO files that it produced with NEs information
inside. Closing this window is as simple as clicking on Close button. User can see data related to NEs
as shown in Fig. 252.
As for NEtO main window, even NE list window allows using keyboard and hotkeys to perform operations.
Through:
Keyboard shortcut Alt + g behaves as clicking on Get Current button with mouse;
Keyboard shortcut Alt + s behaves as clicking on Set Current button with mouse;
Keyboard shortcut Alt + n behaves as clicking on New button with mouse;
Keyboard shortcut Alt + r behaves as clicking on Remove button with mouse;
Keyboard shortcut Alt + v behaves as clicking on Save button with mouse;
Keyboard shortcut Alt + c behaves as clicking on Close button with mouse.
N.B. Since NEtO list files are XMLbased, they contain simple text characters with specific tags to
identify information. This allows user/operator to possibly modify files by itself, whenever
needed. Anyway, list files not strictly fulfilling XML NEtO grammars and structure cannot be
considered correct and used by NEtO list management. Such manual modification is strongly
discouraged.
Suggested usage sequence for NEtO interface and NE list is:
1) Fill NEtO main view IP Address field with NE IP address;
2) Start supervision by clicking Ok button;
3) Open the NEs table (any method, through New or Open button);
4) Click on Get Current;
5) Save the list and close the list window.
This will produce a clean and uptodate NEs table list. NE table lists wont never be updated if user will
modify, say, NE site name, site location or even IP address. Such data are used for references purposes
but user must take care to keep them updated.

510 / 866 3DB 16142 JAAA Ed.01
37 9400AWY WEBEML
This chapter describes in detail the organization of the TCO SUITE WebEML for 9400AWY V2.1.3, and
sums up its functions, that are described in detail in this or other chapters.
Subject On page
How to open the 9400AWY NE WebEML main view 512
9400AWY view organization 513
View Area 514
Resource Tree Area and Selection Criteria 515
Resource Detail Area 515
Main tool bar 516
Severity alarm synthesis, and Domain alarm synthesis 517
Management state control panel 518
Access state (allow or inhibit NE Craft Terminal access) 519
Switching from the OS to the Craft Terminal access state 519
Switching from the Craft Terminal access state back to the OS access state 519
Introduction to the WebEML menu commands 520
Security by operator profile 520
Menu organization 523
Command button policy 523
Help menu 524
Views menu 525
Configuration menu 526
Diagnosis menu 527
Supervision menu 528
SW download menu 528

3DB 16142 JAAA Ed.01 511 / 866
37.1 How to open the 9400AWY NE WebEML main view

The 9400AWY main view screen (example in Fig. 253. on page 513 ) can be opened for a NE supervised

by NEtO in one of the following ways:

clicking the Show button in its NEtO screen (see para.36.4.6 on page 508 )
or, with its AM (Alarm Monitor) screen already open, through the Navigate from AM to USM function
(see para.315.2.9 on page 617 ).
The login screen opens, where user is asked to provide his/her UserName and Password (for details, see
point [1] on page 420 ):
After having filled the fields UserName and Password, followed by the Apply button clicking, if login
successful:
loading of JUSM is performed, with all data regarding the NE configuration and those related to the
security customization described in para.32.3 on page 419 :
and the 9400AWY main view screen appears (example in Fig. 253. on page 513 ).

512 / 866 3DB 16142 JAAA Ed.01
37.2 9400AWY main view organization
The 9400AWY main view ( Fig. 253. below is an example for the 1+1 configuration ) contains the following
fields, which provide the operator with the information needed to manage the NE:
Area Meaning
View title according to screen
View area see para.37.3 on page 514
Main tool bar see para.37.4 on page 516
Severity alarm synthesis, and Domain alarm synthesis see para.37.5 on page 517
Management state control panel see para.37.6 on page 518
Menu bar see para.37.8 on page 520
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.
Main tool bar Severity alarm synthesis Domain alarm synthesis

View title
Menu bar
Tab panel
RESOURCE
TREE AREA
RESOURCE LIST AREA
View
area
RESOURCE DETAIL AREA
Management state control panel

Fig. 253. 9400AWY Main view organization

3DB 16142 JAAA Ed.01 513 / 866
37.3 View Area

RESOURCE RESOURCE LIST AREA
TREE AREA
RESOURCE DETAIL AREA
The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g.
many windows placed one upon another. Each window is selectable (placing it on top of the others) with
a tab shown on the top.
Each panel represents a set of functions. The area consist of the following sets:
Equipment
External Points
Line Interface
Performance
Radio
Protection Schemes (in 1+1 configuration only)
Loopback
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.

514 / 866 3DB 16142 JAAA Ed.01
37.3.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 or 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.
37.3.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

3DB 16142 JAAA Ed.01 515 / 866
37.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).

Ethernet Port PM configuration
VLAN configuration
Current Configuration view

previous next
screen screen Summary Block Diagram view
not
operative
navigation buttons
Fig. 254. Main tool bar
N.B. previous screen and next screen buttons are enabled according to the context.
Shortcuts available are:

in all equipment configurations:
Summary Block Diagram view: shortcut to menu command:

Diagnosis % Summary Block Diagram View
details in para.316.4 on page 629
Current Configuration view: shortcut to menu command:

Diagnosis % Current Configuration view
and, additionally, only with Enhanced Data plugin configured:
VLAN configuration: shortcut to menu command:

Configuration % Network configuration % VLAN configuration
details in para.38.2.6 on page 545
Ethernet Port PM configuration: shortcut to menu command:

Diagnosis % Ethernet Port Counters Monitoring

516 / 866 3DB 16142 JAAA Ed.01
37.5 Severity alarm synthesis, and Domain alarm synthesis
These areas contain the list of alarms listed by severity, and accompanied by the number of alarms
affecting the specific type:
Tab. 95. Indications of the Severity alarm synthesis, and Domain alarm synthesis areas
Mnemonic Alarm / Status Description Maintenance
Synthesis of alarms that needs immediate
CRI Critical alarm
troubleshooting (typical: NE isolation). (N.B.)
Synthesis of alarms that needs immediate
MAJ Major (Urgent) alarm
troubleshooting. (N.B.)
Synthesis of alarms for which a deferred intervention
MIN Minor (Not urgent) alarm
can be decided. (N.B.)
Synthesis of alarms due to failure of other NE in the
WNG Warning alarm
network. (N.B.)
Synthesis of alarms not associated with the previous
IND Indeterminate alarm
severities. Not operative.
External Point Synthesis of the relevant station alarm incoming as
EXT
(Housekeeping alarm) input housekeeping signals
EQP Equipment alarm Synthesis of alarms of the Equipment domain
TRS Transmission alarm Synthesis of alarms of the Transmission domain
N.B. The Alarm Profile can modify the assignment of each alarm root to the various synthesis.

3DB 16142 JAAA Ed.01 517 / 866
37.6 Management state control panel

GREEN LED: Indicates that the Craft Terminal

has the OS permission to manage the NE
LAC (Local Access Control)
(granted).
(N.B.)
CYAN LED: Indicates that the Craft Terminal has
not the OS permission to manage the NE (denied).
GREEN LED: Identifies the Enable operational
state of the connection between NE and Craft
Terminal ( service link up ).
NE reachable / unreachable
RED LED: Identified the Disable operational
state of the connection between NE and Craft
Terminal ( service link down ).
GREEN LED: NE is under supervision.

Supervision state BROWN LED: NE is not under supervision. Used
in the OS.
GREEN LED: Indicates that the NE is not

Operation System managed by the 1353NM/SH.
(N.B.) RED LED: Indicates that the NE is managed by the
1353NM/SH.
GREEN LED: NTP protocol enabled and both NTP

servers ( Main and Spare ) are unreachable.
Network Time Protocol BROWN LED: NTP protocol disabled.
CYAN LED: NTP protocol enabled and at least one
NTP servers ( Main or Spare ) are reachable.
GREEN LED: Normal operating condition.

Abnormal Condition CYAN LED: Detection of an ABNORMAL
operative condition. E.g. protection switch forcing.
N.B. 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, as
described in following para.37.7

518 / 866 3DB 16142 JAAA Ed.01
37.7 Access state (allow or inhibit NE Craft Terminal 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 reply.
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 in two ways:

switching from the OS to the Craft Terminal access state
switching from the Craft Terminal access state back to the OS access state
37.7.1 Switching from the OS to the Craft Terminal access state
By WebEML, perform Supervision Access State Requested ( see para. 37.8.8 on page 528 ).
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.
37.7.2 Switching from the Craft Terminal access state back to the OS access state
By WebEML, perform Supervision Access State OS ( see para. 37.8.8 on page 528 ).
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 ( para.37.6 on page 518 )
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).

3DB 16142 JAAA Ed.01 519 / 866
37.8 Introduction to the WebEML menu commands

N.B. The conversion of the WebEML menus, which are natively in English, in other languages is

possible, on contact basis (this process is called localization). The following languages are

supported: Spanish, Italian, German, French. Localization is not done in the standard CT
product, but is in charge of AlcatelLucent local units. Please refer to them for additional
information.
37.8.1 Security by operator profile
The security by operator profile has been introduced in para.32.3.2 on page 420
The commands present in the menu bar can be enabled (with black text) or disabled (with greyed text),
as depicted in following example:
commands disabled (greyed text)
command enabled (black text)
all commands enabled (black text)
In fact, the operations allowed by the Craft Terminal depend on the combination of the following security
parameters:
the type of command to be forwarded
the login profile associated to the UserName and Password employed: Administrator, or Constructor,
or Operator, or CraftPerson, or Viewer, described in point [2] on page 420
the CT physical access characterization: LCT (Local Craft Terminal) or RCT (Remote Craft Terminal).
The LCT or RCT characterization for the CT is depicted in tables on pages 411 to 413
In few words: only the CT connected locally to the NEs Finterface or to the NEs Ethernet
management interface has the functionalities of LCT, for that NE only, but not for other NEs that can
be reached through it
and the current LAC status, granted or denied: see para.37.6 on page 518
N.B. In few words, all commands are enabled only when:

the physical access is by LCT,
the login profile associated to the used UserName and Password is Administrator,
the current LAC status is granted

520 / 866 3DB 16142 JAAA Ed.01
To know the security parameters defined above, perform following operations:
1) In the menu bar, perform Help % Tutorial (see para.37.8.4 on page 524 )
In the help screen that opens, click NE Management , then scroll the help page until you find MENU
CONFIGURATION, then click on Profile Management:
2) then, click on Appendix: Craft Terminal Access Control :

3DB 16142 JAAA Ed.01 521 / 866
3) the relevant description screen opens as in example below, where the security parameters are
described by 5 tables, one for each of the login profiles (Administrator, Constructor, Operator,

CraftPerson, and Viewer):

4) The profile management is performed through the CT commands Supervision % Profiles
management (see para.37.8.6 on page 526 )

522 / 866 3DB 16142 JAAA Ed.01
37.8.2 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 38 on page 529 details and operating information on all views are given.
In the menu bar, a number of permanent menu items are always displayed. Starting from the left, the
menus are:
Permanent Menus
Views (first column). See para.37.8.5 on page 525

To navigate among the views and to set the TMN parameters.
Configuration (second column). See para.37.8.6 on page 526

To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
Diagnosis (third column). See para.37.8.7 on page 527

To get information on the NE (alarms, performance monitoring, remote inventory).
Supervision (fourth column). See para.37.8.8 on page 528

To set the supervision states (i.e. Craft Terminal enabling).
SW Download (fifth column). See para. 37.8.9 on page 528

To manage the NE software (download, MIB management).
Help (last column) See para. 37.8.4 on page 524

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.
37.8.3 Command button policy
In all command windows, the possible buttons for commands are the following:
Apply this button activates the modify, but it does not close the window.
Cancel this button closes the window without modifying the parameters displayed in the window.
OK this button activates the modify and closes the window
Close this button closes the window
Help this button provides the help management for the functions of the supporting window.
Critical configuration choices generate a warning message for user confirmation before to be activated.

3DB 16142 JAAA Ed.01 523 / 866
37.8.4 Help menu

This menu presents the following entries:

On Help: this menu entry will show the complete online help available
On Context: selecting this entry will present a context help with respect to selected window area
Glossary: this command will show a list of acronyms and abbreviations that can be useful to explain
used terms
Tutorial: the Tutorial menu entry shows a user guide for the JUSM application. This one, and all
the entries above, is shown ad HTML pages in the default Internet browser.
About: selecting About item, a window will be displayed with the release information of JUSM
application and its components, as in following example:
An example showing the use of the Tutorial menu is given on pages 521 to 522

524 / 866 3DB 16142 JAAA Ed.01
37.8.5 Views menu
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 39 on page 557
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 317 on page 635.
Loopback: Allows to manage the loopbacks available with the equipment.

N.B. It is possible to enter directly any menu Equipment, External Points, Line Interface,
Performance, Radio, Protection Schemes, or Loopback, clicking the view area on the relevant
tab panel.

3DB 16142 JAAA Ed.01 525 / 866
37.8.6 Configuration menu

This menu allows to set the general configuration of the NE and to show or modify some parameters, by

means of the following entries and subentries:

NE Time: Displays and sets the NE local time.
See para. 38.1 on page 530
Network configuration: Allows to manage the NE network configuration

N.B. the submenu Vlan Configuration is available only with Enhanced Data plugin
configured
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.
Profiles management: Allows the CT user profile management

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

526 / 866 3DB 16142 JAAA Ed.01
37.8.7 Diagnosis menu
This menu allows to get diagnostic information regarding the NE, by means of the following entries and
subentries:
Alarms % NE Alarms: Starts the Alarm Monitor (AM) application

See para. 315.2 from page 606
Log Browsing % Event Log: Manages the events stored in the NE

See para. 315.3 from page 621
Log Browsing % Software Trace Log

N.B. The use of the Software Trace Log option is reserved to the AlcatelLucent technicians
for SW debugging purposes
Remote inventory: Displays the equipment Remote inventory information.

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

Displays a global logical view (strictly related to the physical
implementation) highlighting a synthesis of all the alarms and
statuses present in the system (ODU+IDU)
Current configuration View: Displays the current configuration of the NE.

Ethernet Port Counters Monitoring:

Sets and reads the Performance Monitoring on Ethernet Ports
N.B. this menu is available only only with Enhanced Data plugin configured

3DB 16142 JAAA Ed.01 527 / 866
37.8.8 Supervision menu

This menu allows to set the supervision states of the NE, to restart the NE, to manage its MIB, and to show

information regarding the equipped Flash Card, by means of the following entries and subentries:

Access State: Manages the supervision access to the NE, by CT or OS.
Restart NE: See point [8] on page 430
MIB Management: Allows to perform backup and restore operations of the NEs MIB.
See chapter 314 on page 599
SW key: Displays the type of Flash Card equipped in the system and the licence
information ( see point [1] on page 424 )
37.8.9 SW download menu
This menu allows to manage the NE software, by means of the following entries:
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 (*)
(*) For the use of these commands for the SW download, refer to chapter 59 from page 811

528 / 866 3DB 16142 JAAA Ed.01
38 CONFIGURATION
This chapter describes the following Configuration menus: NE Time, Network Configuration, Alarm
Severities, and System Settings.
Subject On page
NE Time 530
Network Configuration 531
Local Configuration 532 WARNING
NTP Configuration 533 WARNING
Ethernet Configuration 535 WARNING
IP Configuration 536
IP static routing configuration 536 WARNING
OSPF Area configuration 540 WARNING
IP Address configuration of PointToPoint Interfaces 542 WARNING
Routing information 544
WARNING
Vlan Configuration 545 for Create
function
Alarm Severities 548
System Settings 553
NE Configuration 553 WARNING
Link Identifier 555 WARNING
Overhead 556 WARNING
WARNING: Setting of these parameters must not be done by these commands at the
firsttime NE setup.
Setting of all parameters for the firsttime NE setup must be done in the
commissioning phase (Chapter 42 from page 675 ), by the NEinteractive
Provisioning Tool described in chapter 34 from page 443
N.B. For the following other Configuration menus:
Profiles management, refer to para.313.1 on page 591
Log Switch, refer to para.315.1 on page 606

3DB 16142 JAAA Ed.01 529 / 866
38.1 NE Time

The NE local time can be displayed and/or realigned to the OS time basis.

From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which you can set the local NE time.
Fig. 255. 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.

530 / 866 3DB 16142 JAAA Ed.01
38.2 Network Configuration
To get access the Network Configuration option select the Configuration pull down menu, as shown
in the following figure.

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

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

which has been configured.
The options are described in next paragraphs.

3DB 16142 JAAA Ed.01 531 / 866
38.2.1 Local Configuration

WARNING 1: read carefully the WARNING on page 529

WARNING 2: read carefully para.32.2.2 on page 414 (NEs local IP address and Ethernet
Configuration IP address)
N.B. This function is equivalent to that of Full Configuration Procedures Step H on page 470
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. 257. on page 532 ) 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. 257. Local Configuration dialogue box

532 / 866 3DB 16142 JAAA Ed.01
38.2.2 NTP Configuration
WARNING: read carefully the WARNING on page 529

By selecting NTP Configuration the dialogbox in Fig. 258. opens, which allows to enable the Network
Time Protocol.
Fig. 258. 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.

3DB 16142 JAAA Ed.01 533 / 866
38.2.2.1 How to configure the NTP in a network

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

Two examples are shown in Fig. 259.

CASE A CASE B
NE1 NE1
NE2 NE3 NE4 NE2 NE3 NE4
NTP signal from Main server

NTP signal from Spare server
Fig. 259. Examples of NTP signal distribution
a) CASE A: the NE1 generates the NTP information, and is the master for all the other NEs. In this case:
1) in NE1, disable the NTP protocol;
2) for the other NEs:
NE2 is set as Slave:

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

in the Spare Server address field enter the Local IP address of NE2.

in the Spare Server address field enter the Local IP address of NE2.
b) CASE B: the NE1 gets the NTP information from a NTP device, but is the master for all the other NEs.
In this case:
1) in NE1:
in the Main Server address field enter the IP address of the Main NTP device;
in the Spare Server address field enter the IP address of the Spare NTP device.
2) for the other NEs, the setting is equal to that of point 2 ) above

534 / 866 3DB 16142 JAAA Ed.01
38.2.3 Ethernet Configuration

WARNING 2: read carefully para.32.2.2 on page 414 (NEs local IP address and Ethernet
Configuration IP address)
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. 260. below 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.
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.

WARNING: after changing the IP address, NE will restart automatically.
Close button closes the dialog without changes of the data.
Fig. 260. Ethernet Configuration dialogue box

3DB 16142 JAAA Ed.01 535 / 866
38.2.4 IP Configuration

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

cascading menu, the IP Configuration option ( see Fig. 261. on page 536).

Fig. 261. IP configuration screen
38.2.4.1 IP static routing configuration
N.B. This function is equivalent to that of Full Configuration Procedures Step J on page 475
The dialogbox opens ( see Fig. 262. on page 537 ) and allows to configure the parameters for IP Static
Routing Configuration.
[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.

536 / 866 3DB 16142 JAAA Ed.01
Fig. 262. IP static routing configuration screen
By pressing Create pushbutton the screen in Fig. 263. on page 538 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.

3DB 16142 JAAA Ed.01 537 / 866
Fig. 263. Create Static routing
If in the screen of Fig. 263. 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. 263. above has been selected the Point To Point Interface Index check box, the
screen in Fig. 264. on page 539 opens.
N.B. It is also possible to define a Default Gateway Routing (refer to para.38.2.4.2 on page 539
for details).

538 / 866 3DB 16142 JAAA Ed.01
Fig. 264. Point To Point Interface Choice
In this screen one of the 3 NMS channels (NMSRF, NMSV11, NMSG703) can be selected.
38.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. 263. on page
538 operate as follows:
a) select Network
b) in IP Address field, write 0.0.0.0
c) in IP Mask field, write 0.0.0.0
d) in Default Gateway IP Address field, write the required destination
e) click OK

3DB 16142 JAAA Ed.01 539 / 866
38.2.4.3 OSPF Area configuration


N.B. This function is equivalent to that of Full Configuration Procedures Step G on page 469
The dialogbox opens ( Fig. 265. below ) 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. 265. OSPF Area configuration screen
WARNING 2: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0
WARNING 3: When the area is a Stub area, all interfaces inside the same Stub Area (NMS and
Ethernet) must be defined Stub.

540 / 866 3DB 16142 JAAA Ed.01
By pressing Create pushbutton the screen in Fig. 266. below opens.
N.B. 3 areas max. can be created.

Fig. 266. Create New OSPF Area
In the screen write the IP address, the IP mask and select the flag (True/False).

3DB 16142 JAAA Ed.01 541 / 866
38.2.4.4 IP Address configuration of PointToPoint Interfaces


N.B. This function is equivalent to that of Full Configuration Procedures Step I on page 472
The dialogbox opens ( see Fig. 267. below) and allows to Enable or Disable the three NMS channels,
which use the PPP protocol.
Fig. 267. 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.

542 / 866 3DB 16142 JAAA Ed.01
In alternative to the G703 NMS, the TMN inframe E1 can be defined.
With this TMN inframe feature, the 9400AWY equipment is able to introduce in one of the time slots (TS
131, except TS 16) 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).
WARNING: the E1#1 tributary must be enabled and framed, and the chosen timeslot must be the
same, in all NEs that must be crossed by the TMN inframe, as depicted in Fig. 223. on
page 473
To activate the TMN inframe feature:
by the screen of Fig. 297. on page 565 , verify (or set) that the first E1 tributary is enabled and
framed
by the screen of Fig. 268. below, in TMN G703 field:
set Mode to InFrame E1
define the chosen timeslot number (default 1) of the E1#1 tributary (only E1#1 is supported)
DO NOT SPECIFY TIMESLOT 16 !
Fig. 268. 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.

3DB 16142 JAAA Ed.01 543 / 866
38.2.5 Routing information

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

cascading menu, the Routing information option.

The dialogbox in Fig. 269. on page 544 opens.
Fig. 269. 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.

544 / 866 3DB 16142 JAAA Ed.01
38.2.6 Vlan Configuration
The Vlan Configuration menu is used to configure Vlan static table entries, and is available only if the
Enhanced Ethernet plugin is installed and has been defined by choice 16E1GData in the Configuration
% System Settings screen of Fig. 282. on page 554
N.B. For whole information on Vlan characteristics and management, refer to para.61.9 from page
835
This menu ( Fig. 270. below ) can be opened by Configuration % Network Configuration % Vlan
Configuration, or clicking the suitable shortcut in the WebEML Main tool bar ( see Fig. 254. on page
516 ).
Fig. 270. Vlan Configuration
Each row of the Vlan table represents a Vlan entry with its own Vlan ID, Vlan name, Vlan ports, and Vlan
untagged ports. There is a default Vlan with ID = 1. This default Vlan cannot be created or changed, it is
generated automatically when Vlan type is 802.1Q.
This menu allows the following operations:
[1] Create (a new Vlan entry)

When create a new Vlan entry, click Create button and a create dialog will be opened.
Fig. 271. Create Vlan

3DB 16142 JAAA Ed.01 545 / 866
The Vlan ID is required unique and between 2 to 4094, the Vlan name must not be longer than 32
characters. By default, all ports are included in Vlan. Put Vlan ID and Vlan name, click OK button

will create a new Vlan. If a port is not in the Vlan ports, it cannot be edited in the Vlan untagged ports.

The character of Vlan name cannot use , >, <, &

The Vlan ID must be unique. If create a duplicated Vlan, the following warning message will be
shown:
Fig. 272. Warning message for duplicated Vlan ID
[2] Change (a Vlan entry)

Choose the Vlan entry from the table, click Change button, user can change its information form the
edit dialog.
Fig. 273. Change Vlan

User can change Vlan name, Vlan ports member and untagged ports member and confirm these
changes by clicking ok button in the edit dialog. The Vlan ID cannot be changed.
Ethernet Ports configured via Ethernet Physical Interface (i.e. if dot1qVlanIndex is equal to dot1qPvid
inside Dot1qPortVlanEntry) cannot be modified (the checkbox is greyed out).
[3] Delete (a Vlan entry)

Choose the Vlan entry from the table and click Delete button can delete it from Vlan table: a delete
confirmation box will appear).
N.B. Vlan with ID=1 cannot be deleted.
Fig. 274. Delete Vlan confirmation dialog box

546 / 866 3DB 16142 JAAA Ed.01
[4] Filter field

Put the Vlan name (or a part of it) in the Filter by name text field, and click Filter button: only
the Vlan name matching the filter condition is shown in Vlan dialog:
Fig. 275. Filter by name
Click the Clear Filter button to clear the filter condition, and show all Vlan information.
[5] Export
User can export Vlan information in a .csv file, clicking Export button.
Fig. 276. Export Vlan Information

3DB 16142 JAAA Ed.01 547 / 866
38.3 Alarm Severities

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

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

548 / 866 3DB 16142 JAAA Ed.01
Fig. 277. Alarm Severities Profile
In the screen of Fig. 277. on page 549 are available 2 buttons:
Close: to close the screen.

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

3DB 16142 JAAA Ed.01 549 / 866
38.3.1 How to create a new Alarm Severity Profile

Select in the screen of Fig. 277. on page 549 the Alarm Profile to be cloned.

Click the Clone pushbutton.
The screen of Fig. 278. on page 550 appears.
Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 278. 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. 279. on page 550).
Fig. 279. Clone of an Alarm Severity Profile

550 / 866 3DB 16142 JAAA Ed.01
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. 280. on page 551).
Fig. 280. Selection of a new severity in the Service Affecting field

3DB 16142 JAAA Ed.01 551 / 866
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. 281. on page 552).

Fig. 281. 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. 281. on page 552).

552 / 866 3DB 16142 JAAA Ed.01
38.4 System Settings
This menu is used to change the configuration of a system already commissioned.

The main window provides tabbedpanels, one for each type of function to be managed:
NE configuration (herebelow)
Link Identifier (on page 555 )
Overhead (on page 556 )
38.4.1 NE Configuration
WARNING 2: If you use this screen to change the capacity and/or modulation, to avoid adjacent channel
traffic impact, you must use the procedure described in chapter 58 on page 809
The user can view and define the NE configuration by selecting the NE Parameters tabbed panel.
The window displayed in following Fig. 282. will appear.
The main areas NE Type and Structure of this screen are practically equal to those of Full Configuration
Procedures Step A screen described on page 450. Please refer to it for details not given in this
paragraph.
the fields in NE Type area are displayed, and can be changed and then submitted clicking the related
Apply button
WARNING: if, during this procedure, a wrong type is selected (i.e. PSU2460 instead of
PSU4860), 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.
in Structure area, the information related to the Capacity and Modulation is shown, and can
be changed individually, taking into account the rules depicted in Tab. 92. on page 451 , and then
applied by clicking the related Apply button.
N.B. the Regional Settings function is not available in this screen, but in the Radio %
Frequency menu ( see para.311.4 on page 576 )
The Tributary Port Configuration area is in the lower part of the window. The Impedance field allows
the operator to configure the impedance of all the E1 tributary (unbalanced 75 ohm or balanced 120 ohm).
The impedance value will be applied by clicking on the related Apply button.

3DB 16142 JAAA Ed.01 553 / 866
DO NOT USE THIS CHOICE !
Fig. 282. System Settings: NE configuration
N.B. After a change request in any field of the NE Type or Structure area, the explicit confirmation
shown in Fig. 283. is required.
Fig. 283. 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.

554 / 866 3DB 16142 JAAA Ed.01
N.B. After the successful change in the NE Type or Structure area (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. 284. USM closing warning message
38.4.2 Link Identifier
The user can view and define the Link Identifier by selecting the Link Identifier tabbed panel.
The window displayed in Fig. 285. below will appear.
The fields of this screen are practically equal to those of Full Configuration Procedures Step E screen
described on page 467 . 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. 285. System Settings: NE configuration

3DB 16142 JAAA Ed.01 555 / 866
38.4.3 Overhead


The Overhead tabbed panel (Fig. 286. below) is present only if the Audio/User Service Channels
plugin is configured (see Fig. 282. on page 554 ) and identifies the parameters for the management
of the phone number (EOW function) and auxiliary channel interface:
The fields in areas Overhead Configuration, Auxiliary Interface Configuration and Party
Line of this screen are practically equal to those of Full Configuration Procedures Step M screen
described on page 478 . 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. 286. 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. 38.3.1
on page 550). 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.

556 / 866 3DB 16142 JAAA Ed.01
39 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,..)
Subject On page
Main screen below
IDU level 559
1+0 configuration 559
1+1 configuration 560
Board level 560
ODU level 561
Tab panels in the Resource Detail Area 561
Alarms 561
Configuration 562
Remote Inventory 562
39.1 Main screen
The main screen of the Equipment tab panel differs according to the configuration:
Fig. 287. on page 558 for 1+0 configuration
Fig. 288. on page 558 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

3DB 16142 JAAA Ed.01 557 / 866
Equipment Status

ODU ODU Status
IDU Status
IDU
Fig. 287. 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. 288. 1+1 Equipment view

558 / 866 3DB 16142 JAAA Ed.01
39.2 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.

39.2.1 1+0 configuration
The screen in Fig. 289. below will appear.
IDU Status
IDU
MAIN BOARD
Status
Fig. 289. 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

3DB 16142 JAAA Ed.01 559 / 866
39.2.2 1+1 configuration

The screen in Fig. 290. below will appear for the Ch#1 and the screen in Fig. 291. below will appear for

the Ch#0.

IDU Status
IDU
MAIN BOARD
Status
Fig. 290. 1+1 IDU/MAIN Ch#1 view
IDU Status
IDU
EXTENSION BOARD
Status
Fig. 291. 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
39.2.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.

560 / 866 3DB 16142 JAAA Ed.01
39.3 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. 292. below will appear.
Fig. 292. ODU view
39.4 Tab panels in the Resource Detail Area
39.4.1 Alarms
The Alarms tab panel provides the fault management, which checks the current state of alarms related
to the selected object (Fig. 293. below).
Fig. 293. 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.

3DB 16142 JAAA Ed.01 561 / 866
39.4.2 Configuration

The User Label field (Fig. 294. 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. 38.3.1 on page 550). To
associate a different Alarm Profile click on the selection button and make the selection among the available
Alarm Profiles.
Fig. 294. Configuration tab panel for a selected object
39.4.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. 295. below):
Fig. 295. Remote Inventory tab panel for a selected object
For detailed information on Remote Inventory, refer to para.316.2.1 on page 627

562 / 866 3DB 16142 JAAA Ed.01
310 LINE INTERFACE
This chapter describes the type of functions available for Line Interface Management.
Subject On page
Areas of the Line Interface domain 564
Tab panels in the Resource Detail Area 565
Configuration 565
Tributaries PDH Configuration tab panel 565
ETSI Market 565 WARNING
NMS interfaces Configuration tab panel 567
Data Tributaries Configuration tab panel 568
Tab panels relevant to all Data Tributaries ports as a whole 568
Alarms Tab panel 568
Configuration and QoS Tab panels 568 WARNING
Tab panels relevant to each Data Tributary port 569
Port status (synthesis) 570
Alarms Tab panel 570
Configuration Tab panel 570 WARNING
VLAN & ALiS Configuration Tab panel 571 WARNING
firsttime NE setup.
Nevertheless, take into account that some features (like Alarm Profile and
Line RAI Insertion) can be set only in the screens of this chapter.

3DB 16142 JAAA Ed.01 563 / 866
310.1 Areas of the Line Interface domain

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. 296. 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. 296. 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.38.4.1 on page 553)
or in Full Configuration Procedures Step A screen (described on page 450 ).

564 / 866 3DB 16142 JAAA Ed.01
310.2 Tab panels in the Resource Detail Area
310.2.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. 39.4.1 on page 561
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.
310.2.2 Configuration
There are different tab panels according to the type of interface:
PDH interface (para. 310.2.3 below)

NMS interface (para. 310.2.4 on page 567 )
Ethernet interface (para. 310.2.5 on page 568 )
310.2.3 Tributaries PDH Configuration tab panel
310.2.3.1 ETSI Market
The window, shown in Fig. 297. below for E1 tributaries, performs all the available functions for a PDH
tributary port.
Fig. 297. Line Interface View: E1 Tributary Port
In Fig. 297. 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

3DB 16142 JAAA Ed.01 565 / 866
The fields, which can be changed, are:

Signal Mode

Line RAI Insertion

Radio RAI Insertion
Alarm Profile
[1] Signal Mode (for E1 tributary only)
The possible values are:

Framed for the framed received signal
Unframed for the unframed received signal
Disabled
The current state can be modified selecting a different signal mode value and then click on the
Apply button to send the new value to NE.
WARNING: In case of configuration with two Ethernet ports, some E1 ports must be disabled in
order to allow the transmission of the Ethernet data.
Refer to Tab. 93. on page 455 and to the relevant explanations in the same page.
[2] 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. 38.3.1 on page
550). 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.

566 / 866 3DB 16142 JAAA Ed.01
310.2.4 NMS interfaces Configuration tab panel
Fig. 298. 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
among the available Alarm Profile.

3DB 16142 JAAA Ed.01 567 / 866
310.2.5 Data Tributaries Configuration tab panels

N.B. For whole information on Ethernet port characteristics and management, refer

to the Appendix A on page 829
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. 282. on page 554
[1] Tab panels relevant to all Data Tributaries ports as a whole
Selecting Tributaries Data in the resource tree, the following Tab panels are available:
Fig. 299. Line Interface View: Data Tributary Port QoS Configuration tab panel
a) Alarms Tab panel

All alarms affecting the Tributaries Data domain are shown
b) Configuration and QoS Tab panels
Configuration and QoS (Quality of Service) information and choices in following Fig. 300. and
Fig. 301. are fully equal to that described in Full Configuration Procedures Step B point
[2] 2 ) GEthernet Configuration areas described on page 458 . Please refer to it for details
not given here.
Screen of Fig. 300. below allows to read the current Vlan configuration, as well as to change
it clicking on desired configuration, and then on the Apply button (a confirmation box appears).
Fig. 300. Line Interface View: Data Tributary Port Configuration tab panel

568 / 866 3DB 16142 JAAA Ed.01
Screen of Fig. 301. below allows to read the current priority queues, as well as to change them
choosing the desired configuration, and then on the Apply button (a confirmation box appears);
for additional information, click on Help button.

Fig. 301. Line Interface View: Data Tributary Port QoS tab panel
[2] Tab panels relevant to each Data Tributary port
The windows shown in Fig. 302. below performs all available functions for one of four selectable Data
tributary port.
Selecting one of the Ethernet Ports in the resource tree, the following Tab panels are available:
a)
b) c) d)
Fig. 302. Line Interface View: individual Data Tributary Port Configuration tab panels
3DB 16142 JAAA Ed.01 569 / 866
a) Port status (synthesis)
In particular, the displayed operative state, and its associate meaning, can be:

Status Displayed Meaning

Disabled Disabled by the Operator
Enabled by the Operator

and
Enabled and working
no alarms on the radio channels are
present
Enabled by the Operator

and
the ALiS (Auto Link Shutdown) is
enabled by the Operator [see point 2 )
Enabled and not working
on page 572 ]
and
one (or more) alarms on the radio
channels is (are) present
b) Alarms Tab panel

All alarms affecting the selected port are shown
c) Configuration Tab panel
Fig. 303. Line Interface View: individual Data Tributary Port Configuration tab panel (for port #33)
N.B. The example screen shown in Fig. 303. above is for the port #33 only, where the
specification supports Jumbo Frame is stated, as described in para.61.3 on page
829 . For the other ports, in fact, such a specification is not stated:

570 / 866 3DB 16142 JAAA Ed.01
Except the field Alarm Profile and the button Restart, the parameters related to a data
port Configuration panel:
Status
Speed without Autonegotiation

AutoNegotiation
Capability Advertised
Ingress Rate Limiting Configuration
are practically equal to that described in Full Configuration Procedures Step B point
[2] 1 ) Ethernet GPorts configuration screen described on page 456 . Please refer
to it for details not given here.
The Restart button allows forcing autonegotiation to begin link renegotiation.
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 among the available Alarm Profile.
For all changes, to confirm the new configuration, click on Apply.
d) VLAN & ALiS Configuration Tab panel
The windows shown in Fig. 304. below performs the following functions for the selected Data
tributary port:
Fig. 304. Line Interface View: individual Data Tributary Port VLAN & ALiS Configuration Tab panel
1) 802.1Q VLAN Configuration panel

The IEEE 802.1Q tag VLAN can be flexibly enabled or disabled. When enabled, the
Ethernet Traffic, which goes through the AWY Network, is managed according to IEEE
802.1Q protocol.
Once IEEE 802.1Q tag VLAN is enabled, the incoming Frames are divided into two types:
802.1Q Tagged Frame and Untagged Frame. For each Ethernet Port concerning the
acceptable Frame, it is configured as one of the two statuses:
3DB 16142 JAAA Ed.01 571 / 866
Admit only tagged frames the untagged frame will be dropped
Admit all frames (tagged and untagged).

Once the Admit all frames has been selected, for individual Ethernet Port, the VLANID

and Priority has to be assigned. the VLANID created in VLAN table whose VLAN ports
list includes this port are put into the VLANID combobox. User can choose one value
from VLANID combobox (Note: choosing blank is not allowed). The valid Priority is in
the range 07 (where 0 is the lower priority).
The default values for VLANID and Priority should be VLANID = 1, Priority = 0.
This is applied only to the untagged frames.
To confirm the new configuration click on Apply.
2) Auto Link Shutdown (ALiS) Configuration panel
N.B. This function is equivalent to the enabling/disabling the auto link shutdown of
the Full Configuration Procedures Step B point [2] 1 ) Ethernet GPorts
configuration screen described on page 456 . Please refer to it for details not
given here.
By selecting or deselecting the Enabled check box in Fig. 304. on page 571, and then
pushing the button Apply, the operator can enable or disable the auto link shutdown
functionality.
N.B. The Enabled or Not Enabled setting of ALiS implies different system
behaviors, as described in point a ) on page 570 , and in para.61.7 from page
831

572 / 866 3DB 16142 JAAA Ed.01
311 RADIO
This chapter deals with the management of the Radio transmission features.
Subject On page
Areas of the Radio domain 574
Alarms 575
Configuration 575
Local or Remote Transmitter Mute 575
ODU service kit 575
Alarm Profile 575
Frequency 576 WARNING
RTPC & ATPC 578 WARNING
ATPC 579 WARNING
RTPC 580 WARNING
Power Measurement 581
Description 581
How to read a Power Measurement file 584
BER measure 586
firsttime NE setup.

3DB 16142 JAAA Ed.01 573 / 866
311.1 Areas of the Radio domain

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. 305. on page 574):
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. 305. Radio Domain View
The following tab panels are present in the Resource Detail Area:
Tab panels of Radio Resource Detail Area On page

Alarms: show the active alarms 575
Configuration: configures some radio parameters 575
Frequency: sets the Radio Frequency 576
RTPC & ATPC: sets the manual operation parameters or the automatic operation
578
parameters
Power Meas: performs the Tx and Rx power measurements 581
BER: performs the BER measurement 586

574 / 866 3DB 16142 JAAA Ed.01
311.2 Alarms
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. 39.4.1 on page 561.
311.3 Configuration
The window shown in Fig. 306. 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. 306. RadioConfiguration menu
311.3.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.
311.3.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.42.12 on page 720 )
311.3.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. 38.3.1 on page 550). 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.

3DB 16142 JAAA Ed.01 575 / 866
311.4 Frequency

The Frequency menu, shown in Fig. 307. below, allows to read and, if necessary, to modify the

frequency parameters. It has the following main fields:

Shifter and Frequency Value
Regional Setting
described in the following.
Fig. 307. Radio Frequency menu
WARNING 1 : read carefully the WARNING on page 573
WARNING 2 : If you use this menu to change the frequency, to avoid adjacent channel traffic impact, you
must use the procedure described in chapter 58 on page 809
WARNING 3 : When you change any frequency parameter, since frequency setting could impact on
traffic and requires a lot of time, following messages are shown in sequence:

576 / 866 3DB 16142 JAAA Ed.01
a) Shifter and Frequency Value fields
Their function is equivalent to that of Full Configuration Procedures Step D on pages 462 to
465 . 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.111.2 from page 258
[1] Rx Tuning Enabled checkbox use

It allows the automatic adjustment of the Rx frequency inside a forecasted range, depends on
the ODU frequency band, but does not depend on the fixed or flexible shifter.
[2] How to operate for 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
N.B. During the command setting the CT is frozen. Waiting time: max 30.
[3] How to operate for 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
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 WARNING: Frequency
parameters are not aligned to standard configuration associated to the selected
Shifter. For more information, refer to technical handbook is written on the
Frequency.
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.
N.B. During the command setting the CT is frozen. Waiting time: max 30.
b) Regional Setting fields

Their function is equivalent to that of the field Country in the Full Configuration Procedures Step
A on pages 452 to 453 , to which reference must be done for detailed information.

3DB 16142 JAAA Ed.01 577 / 866
311.5 RTPC & ATPC

This menu (Fig. 308. below) allows to read and, if necessary, to set the Tx power parameters.

WARNING : read carefully the WARNING on page 573
N.B. This function is equivalent to that of Full Configuration Procedures Step D on pages 465
to 466
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. 308. 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.

578 / 866 3DB 16142 JAAA Ed.01
311.5.1 ATPC
The ATPC can be Enabled or Disabled.

The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the
ATPC Range and ATPC Rx Threshold fields must be filled.
WARNING: In 1+1 Configuration (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.
[1] ATPC Range
The Min Value and Max Value, for Tx Range in the ATPC management, are shown in the Atpc
Range area. The min and max 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. 96. in order to set the ATPC threshold.
The ATPC shape is calculated using the max capacity.
Tab. 96. ATPC Range Rx Threshold for ETSI

TH 7/8 GHz 13 GHz 15 GHz 18 GHz 23 GHz 25 GHz 38 GHz
Min
73 74 74 72 72 71 70
4 Value
QAM Max
60 60 60 60 55 50 50
Value
Min
69 70 70 68 68 67 66
16 Value
QAM Max
60 60 60 60 55 50 50
Value
The applied rule is:

ATPC Rx threshold setting
Frequency Band
Min Value Max Value
7/8, 13, 15 & 18 GHz PRxth + 8 dB 60 dBm
23 GHz PRxth + 8 dB 55 dBm
25 & 38 GHz PRxth + 8 dB 50 dBm
PRxth: Received power level correspondent to BER 106 according to modulation scheme,
payload and ETSI standard

3DB 16142 JAAA Ed.01 579 / 866
311.5.2 RTPC

[1] Nominal Power

The Nominal Value field in the RTPC area is a readonly field and shows the nominal value of the
transmitted power (expressed in dBm).
[2] Tx Power
The Tx Power field in the RTPC area shows the current value of Tx power (expressed in dBm), when
the ATPC is disabled. In this case, it is possible to modify this value ERROR FREE in ATPC Range
(Pnom 20 dB) with 2 dB max step allowed, by writing the new value and by pressing the related
Apply button
N.B. During the command setting the CT is frozen. Waiting time: < 15.
The new value must be within the allowed transmitted power range. This range is shown in the Power
Value label of RTPC area.
If the ATPC is enabled, the Tx power value cannot be modified.

580 / 866 3DB 16142 JAAA Ed.01
311.6 Power Measurement
311.6.1 Description
The Power Measurements capability is performed through the Power Meas tabbed panel in the resource
detail view, which opens the screen of Fig. 309. below:
Fig. 309. 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
4, 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 4 s sample time).
By clicking on the Start button the screen Power Measurement Graphic appears (see Fig. 310.
on page 582 ).

3DB 16142 JAAA Ed.01 581 / 866
The Power Measurement Graphic is available only if the CT is connected to the NE.

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

Through this screen the operator can see, in real time, the power transmitted by the local and remote
transmitter (Tx) and the power received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the
Rx curves (local and remote). Note that the colors represent the linked endpoint of the two NE; for
example, if the local TX is blue, the remote receiver will also have the same color.
The top of the screen offers all the characteristics present in the current measurement:
Radio port: gives the symbolic name associated to the radio channel being analyzed;
Sample time: indicates the frequency used to send the measurement requests to NE;
Start time: is the first request time;
Stop time: is the interval time selected in the previous parameters window, added to the start time;
Time: is the current response time;
Log File: is the complete pathname of the file where the received values are stored.
Fig. 310. Power Measurement Graphic
By clicking on Show details box, on the left side of the Power Measurement Graphic (see Fig. 310.
above), a new table appears ( Fig. 311. on page 583 ); 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.

582 / 866 3DB 16142 JAAA Ed.01
Tx Far End
max TX remote value and date when this value was received for the first time.
min. TX remote value and its current date when this value was received for the first time.

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

PTx = Real Value 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. 311. 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.

3DB 16142 JAAA Ed.01 583 / 866
311.6.2 How to read a Power Measurement file

Click on Read File field and press on the Select File button. The directory of the CT automatically opens

to navigate and get the power measurement file.

N.B. as default, the measurement files are stored in the ALCATEL/CTKv3.x.x directory and have
extension .txt.
Fig. 312. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 309. on page 581 to open the file.
Fig. 313. 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. 314. on page 585).

584 / 866 3DB 16142 JAAA Ed.01
Fig. 314. Example of Power Measurement File Reading (with WordPad)

3DB 16142 JAAA Ed.01 585 / 866
311.7 BER measure

This paragraph describes the nonintrusive BER function, by means of which it is possible to start/stop

and read the BER measure (Fig. 315. below).

Fig. 315. 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.

586 / 866 3DB 16142 JAAA Ed.01
312 EXTERNAL POINTS
This chapter describes the types of functions offered to the user for External Points Management (please
refer to para.112.13.2 on page 317 for physical implementation).
WARNING: Setting of these parameters must not be done by these commands at the firsttime NE
setup.
Setting of all parameters for the firsttime NE setup must be done in the commissioning
phase (Chapter 42 from page 675 ), by the NEinteractive Provisioning Tool described
in chapter 34 from page 443
The function of these commands is equivalent to that of the Full Configuration
Procedures Step N on page 479
There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Fig. 316. on page 588 , 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

3DB 16142 JAAA Ed.01 587 / 866
312.1 Input External Points

An input external point is described by the following parameters ( Fig. 316. 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. 316. Input External Point View
312.2 Output External Points
Seven output external points are available:
The first four external points (CPO#1, 2, 3, 4) ( Fig. 317. on page 589 ) 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.

588 / 866 3DB 16142 JAAA Ed.01
Criteria: Manual or Automatic. The output can be activated manually by the CT by selecting Manual
(Fig. 317. below) or automatically by selecting Automatic ( Fig. 318. below). 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. 317. Output External Points: CP01 ... CP04 (Manual activation)
Fig. 318. Output External Points: CP01 ... CP04 (Automatic activation)

3DB 16142 JAAA Ed.01 589 / 866
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 319. 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.
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.
Fig. 319. Output External Points View: FAIL IDU, FAIL ODU

590 / 866 3DB 16142 JAAA Ed.01
313 MANAGEMENT OF THE SECURITY FEATURES
This chapter describes how to manage the security features of 9400AWY (by operator profile, by
community string, and by access lists).
Subject On page
Management of security by operator profiles below
Management of security by community string 594
Management of security by access lists 596
313.1 Management of security by operator profiles
[1] Description of the security by operator profile feature
[2] Username and Password format
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).
Each user is associated to a predefined profile.
[3] User number
Twentyfive (25) users at most can be created.
[4] User predefined profiles
The predefined profiles are described in point [2] on page 420
The list of supported features for each user profile is shown by the suitable tables available in the
help online [see point 3 ) on page 522 ].
[5] NE scratch behavior
At installation time (NE scratch), a default Administrator user is defined: see point [1] on page 420
[6] Restart NE behavior
All the security information sets (username/password/profile for each user) are stored permanently
in the NE database (MIB data base). After the NE reset, these information sets are not lost and are
recreated as before the NE reset.

3DB 16142 JAAA Ed.01 591 / 866
[7] Change Password procedure

With this procedure, available for all Operator Profiles, any user, after the successful login by

WebEML (Craft Terminal), can change his/her password:

1) Configuration Profiles Management Change Password
Fig. 320. Profile Management options
2) Following screen appears; fill it with old and new passwords, taking into account password
characteristics listed in point [2] on page 591 . The new password will be active at next login
(after having logged out).
Fig. 321. Changing Password screen

592 / 866 3DB 16142 JAAA Ed.01
[8] Users Management procedure
This procedure is available to users with the Administrator profile only, by WebEML (Craft Terminal):
1) Configuration Profiles Management Users Management (see Fig. 320. on page 592)
2) Following screen appears. Click on Help
Fig. 322. Users Management screen
3) Following screen appears. Click inside to explore matters and carry out the desired action.
Fig. 323. Users Management help screen

3DB 16142 JAAA Ed.01 593 / 866
313.2 Management of security by community string

[1] Description of the security by community string feature

[2] Management of the security by community string
This kind of management is available:
only to users with the Administrator profile,
and only after having logged in successfully the NE by the Main Menus Alarms & Settings
function.
Procedures
1) on the Main Menus Alarms & Settings screen ( Fig. 231. on page 482 ), click Community
String. The following screen opens:
Fig. 324. Alarms & Settings Community String request
The values displayed in Fig. 324. are the defaults (present in the Flash Card as delivered from
AlcatelLucent factory):
the Read Community string (default = public ) must not be changed
the Write Community string ( default = private ) can be changed to activate the security
by community string

594 / 866 3DB 16142 JAAA Ed.01
2) How to change the Write Community string
To change the Write Community string:

enter the new string in the field taking into account the following format:
number of characters: 6 at minimum, 10 at maximum
admitted characters are only:
letters a to z, A to Z
digits 0 to 9
then, click Apply
After the successful Write Community string change, the consequences are the following:
at NE side, the change takes effect at once (no NE restart is performed)
at user side, any NEtO session opened on the NE (supervision, WebEML, and Alarms
Monitoring) is lost.
The operator, independently of her/his profile, to supervision again the NE:
first at all, has to close the NEtO window (by Exit button)
then, she/he starts again the NEtO session [ step a ) on page 500 ]
then, she/he inserts the new Community String (that the NE Administrator must
have communicated to the users) as specified in step b ) on page 501
then, she/he proceeds from step c ) on page 502
3) How to reset the Read Community and Write Community strings
To reset the Read Community and Write Community strings at their default values:
in the screen of Fig. 324. on page 594 , click Default
then, click Apply
The consequences of this operation are as in point 2 ) above.
But, in this case, the operator who has lost the CTNE communication, to supervision again the
NE, must not perform the step b ) on page 501 (i.e. must not insert any Community String).
Both the Read Community and Write Community strings are stored permanently in the NE
database (MIB data base), and they are kept at NE restart.

3DB 16142 JAAA Ed.01 595 / 866
313.3 Management of security by access lists

[1] Description of the security by access lists feature

[2] Management of the Access List tables
The Access List tables have the default status shown in Fig. 325. below, which corresponds to the
step K of the Full Configuration Procedure of the Provisioning Tool, described in chapter 34
on page 443 . In case the Provisioning Tool is run:
in not NEinteractive mode (offline), all operators can obviously write the tables
in NEinteractive mode (online), only a user with the Administrator profile can read and write
the tables, and, at the end of the configuration, can apply it to the NE.
To avoid conflicts, only one Administrator at a time (the first who logs in the NE by the online
Provisioning Tool) can fill the Access List tables; the others are excluded till the completion of
the job.
N.B. the content of the Access List tables is not shown to operators logging in the NE with a
profile different from Administrator.
Fig. 325. Access list configuration default screen

To insert and remove the IP Addresses and IP Masks of the enabled Managers PCs in each
Access List table, refer to the online help, clicking the relevant button, and read the following
additional information:
a) Each row of each Access List table enables one or more Managers
I.e., if the first row is the following:
IP: 151.99.98.1 Mask: 255.255.255.255
it means that only one Manager is defined.
Otherwise, if it is:
IP: 151.99.98.1 Mask: 255.255.255.0
then 256 Managers are enabled.
That is, the number of rows does not necessarily indicate the number of Managers,
because, for each row, many Managers can be defined.

596 / 866 3DB 16142 JAAA Ed.01
b) When an Access List table is modified (with respect to the default status) and the button
Next is clicked:
if the IP address of the Administrators PC (from which the Access List table has been
modified) has not been inserted in the table, it is automatically inserted with IP Mask
255.255.255.255 with the following warning message, where OK must be clicked:
the default row with both IP Address and IP Mask = 0.0.0.0 is automatically removed.
c) When all IP Addresses and IP Masks of the previously enabled Managers PCs are
removed from an Access List table, this is automatically reset at the default condition
(only one row, with both IP Address and IP Mask = 0.0.0.0)
d) Relationship between the tables of SNMP Access List, and of the Trusted Manager.
When both the management of the SNMP Access List, and the management of the
Trusted Manager table ( see Step L on page 477 ) are present, and the button Next
is clicked, in the case of:
definition of a Trusted Manager in the Trusted Manager table, but not in the SNMP
Access List table, the system will include automatically the Trusted Manager also in
the SNMP Access List table, by a warning message similar to that of point b ) above
deletion of a Trusted Manager, two scenarios are possible:
first one: the operator deletes a Trusted Manager from the SNMP Access List
table: automatically, the Trusted Manager will be also deleted from the Trusted
Manager table, but warning a message will be displayed towards the operator
to highlight the deletion operation;
second one: the operator deletes a Trusted Manager from the Trusted
Manager table: this manager could be not deleted from the SNMP Access List
table, and so, a confirmation by the operator is requested.

3DB 16142 JAAA Ed.01 597 / 866
[3] Activation of the changes made on the Access List tables
In the case of changes regarding:

theSNMP and http Access List tables, no NE restart is required: changes apply at once, as

soon as, at the end of the configuration procedure by the online Provisioning Tool, the new
configuration file is applied to the NE;
theftp and telnet Access List tables, it is necessary:
at first, to confirm the changes applying the new configuration file to the NE;
then, to perform the NE restart.

The Access List tables are stored permanently in the NE database, and they are kept at NE restart.
[5] Access List Backup from a NE

Once the Access List tables have been defined in a NE (if at least one of them has a content different
from the default), it is possible, only for an user with the Administrator profile, exporting them all on
a suitable backup file, clicking the button Access List Backup on the Main Menus Alarms &
Settings screen ( Fig. 231. on page 482 ), which opens the following screen:
Fig. 326. Alarms & Settings Access List Backup request
[6] Access List Restore to a NE

A backup file obtained as described in point [5] above, can be restored (only by an user with the
Administrator profile) in the same NE, or another AWY 2.1.3 NE, clicking the button Access List
Restore on the Main Menus Alarms & Settings screen ( Fig. 231. on page 482 ), which opens the
following screen:
Fig. 327. Alarms & Settings Access List Restore request

After the successful restore operation, perform the NE restart.

598 / 866 3DB 16142 JAAA Ed.01
314 MIB MANAGEMENT
This chapter describes how to perform the NE MIB backup and restore operations, introduced in
para.33.2.2 from page 426
Subject On page
Default repository folders of MIB backup files 600
Craft Terminal commands for the management of MIB backup files 600
How to perform the MIB backup 601
How to perform the MIB restore 602
How to remove a MIB backup file from the repository folder 604

3DB 16142 JAAA Ed.01 599 / 866
314.1 Default repository folders of MIB backup files

There is one default repository folder of MIB backup files for all NEs having the same SWPrelease.

The folder name is backup, and is under the path where you have performed the Local copy of WebEML
(Jusm/CT): see para.41.3 on page 668 .
This folder is automatically selected when you perform any of the commands listed in following
para.314.2
The example below shows two MIB backup files present in the backup folder under TCO_SUITE_17
root for 9400AWY V2.1.3.
C:\TCO_SUITE_17\AWY_CT_V01.07\AWY_CT_V02.01.03\backup
C:\TCO_SUITE_17\AWY_CT_V01.07\AWY_CT_V02.01.031backup
V020103_uls_107_2009_08_01.bar
V020103_uls_107_2009_10_05.bar
V020103_uls_107_2009_08_01.bar
V020103_uls_107_2009_10_05.bar
WARNING: the file name contains always the version as prefix (V020103_ in the example above,
corresponding to version V2.1.3).
This prefix is inserted automatically by the SW, when the MIB backup file is created ( see
following para.314.3 ), and is used automatically by the SW, when the MIB restore must
be performed ( see following para.314.4 )
Therefore, this prefix must never be changed.
314.2 Craft Terminal commands for the management of MIB backup files

600 / 866 3DB 16142 JAAA Ed.01
314.3 How to perform the MIB backup
Perform the command Supervision % MIB Management % Backup

The Backup screen opens. Proceed as in following example:

file already existing (example)
V020103_uls_107_2009_08_01.bar
V020103 _uls_107_2009_10_05.bar
(1) name the new file to create (example)

(2) click Save
(3) click Yes
V020103_uls_107_2009_08_01.bar
new file added ! V020103_uls_107_2009_10_05.bar

3DB 16142 JAAA Ed.01 601 / 866
314.4 How to perform the MIB restore

Perform the command Supervision % MIB Management % Restore

The Restore screen opens. Proceed as in following example:

V020103_uls_107_2009_08_01.bar
V020103_uls_107_2009_10_05.bar
(1) select the file to restore (example)
V020103_uls_107_2009_08_01.bar
V020103_uls_107_2009_10_05.bar
V020103_uls_107_2009_10_05.bar
(2) click Open
(3) click Yes
(4) continues ..

602 / 866 3DB 16142 JAAA Ed.01
(4) .. continues
At this point, the restored file is present in a Flash Cards temporary area, but has not been activated in
the actual MIB memory. The following question raises:
At this question, if you answer:
Yes, the activation of the restored MIB is started.

This implies an automatic system restart (see point [8] on page 430 ), and the CTNE
communication is lost.
Therefore, wait the time necessary for the restart completion, after which you can perform again the
NEtO startup and the NE login.
No, no action is made, but the restored file is still present in a Flash Cards temporary area.
When you decide to activate it, perform the command:
Supervision % MIB Management % Activate
which operates as answering Yes in the question screen above

3DB 16142 JAAA Ed.01 603 / 866
314.5 How to remove a MIB backup file from the repository folder

Perform the command Supervision % MIB Management % Remove file

The Remove file screen opens. Proceed as in following example:

(1) select the file to remove (example)
V020103_uls_107_2009_08_01.bar
V020103_uls_107_2009_10_05.bar
V020103_uls_107_2009_08_01.bar
(2) click Remove file
(3) click Yes

Result: file has been removed:
V020103_uls_107_2009_10_05.bar

604 / 866 3DB 16142 JAAA Ed.01
315 ALARMS MONITOR AND EVENT LOG BROWSER
This chapter describes in detail the functions of Alarms Monitor and Event Log Browser embedded in NEtO
application.
Subject On page
Log switch 606
Alarms Monitor 606
Alarms Monitor functions 606
Alarms Monitor startup for one single NE 607
Alarms Monitor Overview 607
Multiple NE Alarms Monitor 611
Filters menu 612
File menu 615
Printing the alarms and logs 615
Exporting the alarms and logs 616
Navigate from AM to USM 617
Navigate from USM to AM 618
Shortcut icons 619
Event Log Browser (ELB) 621
ELB scope 621
ELB startup 621
Event Log Table screen 622

3DB 16142 JAAA Ed.01 605 / 866
315.1 Log switch

By default, the recording of:

events in the Event Log is enabled; their browsing is obtained by the ELB application, described
in para.315.3 from page 621
the alarm events in the Alarm Log of AM is enabled; their browsing is obtained by the AM
application, described in para.315.2 from page 606
The Log Switch screen (Fig. 328. below) can be opened in the NE WebEML application, through the
command Configuration % Log Switch.
By this screen, it is possible to verify, and inhibit (Lock) or allow (Unlock), the store of the events and
alarms respectively in the Event Log and Alarm Log (for the specific NE).
Fig. 328. Log Switch screen
315.2 Alarms Monitor
315.2.1 Alarms Monitor functions
Alarms Monitor (AM) is the application from which the operator can have a global view of the current alarm
and also the alarm log for one or more 9400AWY NEs, within the limits (i.e. the max number of NEtO
instances) specified in point [2] on page 498
AM application requires a supervision manager (NEtO instance) opened for each Network Element
monitored.
The user can:
view the alarms currently present on one or more Network Element(s) in real time
view the historical alarms data (raise/clear log)
view the alarms (both current and historical) filtered by one or more properties.
navigate from an alarm in AM to the specific interface in JUSM, and viceversa from an alarm
selected in JUSM to the specific row in AM, to facilitate troubleshooting
print and export data to external file.

606 / 866 3DB 16142 JAAA Ed.01
315.2.2 Alarms Monitor startup for one single NE
The AM application can be launched for a supervised 9400AWY NE in the following ways:
clicking the Alarms Monitor button in its NEtO screen (see para.36.4.6 on page 508 )
or by its WebEML application:
through the command: Diagnosis % Alarms % NE Alarms
or through the Navigate from USM to AM function (see para.315.2.10 on page 618 )
These ways are mutually exclusive (one AM instance only can be active at a time over one NE for one
PC).
The AM screen opens (see Fig. 329. on page 608 ).
315.2.3 Alarms Monitor Overview
After its launch, the AM screen opens: see Fig. 329. on page 608 , and also the Shortcut icons in
para.315.2.11 on page 619 , that, for simplicity, are not shown in following figures).
a) At the top right, the field Synthesis shows the number of active alarms for any severity, with the same
meaning of Fig. 246. on page 505
b) On the left side of the application, below each NE, two global lists of alarms are displayed:
CURRENT_ALARM shows all the equipment alarms currently present,
ALARM_LOG shows all the equipment alarms currently present and the history of the alarms
(i.e. cleared alarms).
N.B. when an alarm is no longer active, it disappears from the CURRENT_ALARM list, and is
displayed in the ALARM_LOG list as a cleared alarm.
Each global list has some default filters (some filters for the CURRENT_ALARM list, and other filters
for the ALARM_LOG list), as follows:
CRI contains all the alarms having a CRITICAL severity
MAJ contains all the alarms having a MAJOR severity
MIN contains all the alarms having a MINOR severity
WRG contains all the alarms having a WARNING severity
IND contains all the alarms having an INDETERMINATE severity
CLR contains all the alarms which are in the CLEARED state, that is, which are no longer active
(this filter is available within the list ALARM_LOG only).
For each list and for each filter, the number of active alarms is shown inside brackets.
These two lists can be filtered using customized filters provided by means of the menu Filters %
Add a Filter .. (see para.315.2.5 from page 612 ).
Single clicking on a filter or on a global list on the left part of the screen shows up on the right side
the relevant tab panel with all the alarms [see point c ) below]

3DB 16142 JAAA Ed.01 607 / 866
c) On the right, the view of the alarms is displayed:

a Tab in the internal window for each filter that the user want to see. By default Current alarms

and Alarm Log tabs are always visible

for each view, the alarms are shown in a Table.
N.B. when the application is opened for the first time, only two tabbed panes are displayed;
demonstrate respectively the global active alarms (see Fig. 329. ) and the alarm log (see
Fig. 330. ).
Severity alarm synthesis, as in Fig. 246. on page 505
Fig. 329. Alarms Monitor Severity alarm synthesis and Current Alarms
Fig. 330. Alarms Monitor Alarm Log
WARNING:
The Alarm Log Table is updated only if the corresponding Log Switch is unlocked (see
para.315.1 on page 606 )
The Alarm Log Table:
on the NE MIB, has a limited size (about 700 rows, depending on the space available in
the Flash Card). When the maximum size is reached, the first element is cleared and the
new one is overwritten on it;
on the AM application, can display a number of rows much higher (anyway limited to max
5000, to avoid system overload), because they are stored in the PC environment.

608 / 866 3DB 16142 JAAA Ed.01
From the category tree in the left, the operator can also view the alarms or logs with specific severity. E.g.
Fig. 331. shows only the major alarms.
Fig. 331. Alarms Monitor Shows only the major alarms
For each alarm row, these fields are shown:
Time & Date: date and time of the alarm raise or clear.
The format of date and time is yyyy/mm/dd hh:mm:ss
Probable cause: name of the probable cause of the alarm
Alarm Type: alarm class:

TRS = Transmission Alarm alarm not created inside the equipment, but generated by a
connected equipment or due to transmission/propagation problems
EQUIPMENT = alarm inside the equipment
Friendly Name: object of the equipment where the alarm occurred.
Severity: alarm severity:

Critical: RED
Mayor: ORANGE
Minor: YELLOW
Warning: CYAN
Indeterminate: GREY
Cleared: GREEN
Additional Text (if any)
Specific problem: for some alarms, additional information is provided about the involved resource
(for instance, when a threshold alarm is raised, it states the specific threshold exceeded).
Clicking into the column header, it is possible to sort the data by the values of the column itself.
Selection of one or more row of a table is allowed.
Rightclicking on an alarm row opens the menu shown below. The various options are described in the
following.

3DB 16142 JAAA Ed.01 609 / 866
The figure below shows an example where many tables are opened at the same time.

To make one table be displayed, click its header. It goes in the front, and becomes the active table.
To close one table, click the cross symbol of its header. To open it again, click it in the category tree on
the left.
put in front close

610 / 866 3DB 16142 JAAA Ed.01
315.2.4 Multiple NE Alarms Monitor
While AM is active for a NE, to start AM contemporaneously on another NE, open another NEtO instance
for it, and perform the same operation described in para.315.2.2 on page 607
Take into account that only one AM instance can be running, whichever the number of NEs monitored.
When AM is active for more than one NE, the AM screen shows all the monitored NEs, as depicted in
following Fig. 332. :
on the left, a tree with the list of NE and subtree with the filters active for each NE is displayed.
on the right, the view of the alarms is displayed:
an internal window for each NE that the user can see
a Tab in the internal window for each filter that the user want to see. By default Current alarms
and Alarm Log tabs are always visible
for each view, the alarms are shown in a Table.
Refer to descriptions on previous pages 607 to 618 , for detailed information regarding the monitoring
of one NE.
N.B. See also Shortcut icons in para.315.2.11 on page 619

first NE Severity alarm synthesis of first NE
tab panels of first NE
second NE Severity alarm synthesis of second NE
tab panels of second NE
Fig. 332. Example of multiple NE Alarms Monitor (2 NEs)

3DB 16142 JAAA Ed.01 611 / 866
315.2.5 Filters menu

The Menu Filters provides the following menus, described in the following:

[1] Add a Filter

This menu allows to create customized logs adding some new specific filters. The windows which
opens is shown in Fig. 333. below:
Fig. 333. Alarms Monitor Add a filter
A filter can be created selecting one of the following fields (or more). To save the created filter click
on the Done pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The
created filter appears on the left side of the application.
Filter Name field

Enter the filter name in the Filter Name field.
Scope field
Select CURRENT to create a filter showing the current alarms only, or select LOG to create
a filter for current and cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs
by selecting one or more NEs using the mouse.

612 / 866 3DB 16142 JAAA Ed.01
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
TRS = Transmission Alarm

EQUIPMENT = Equipment alarm

Perceived severity field

Select Perceived severity and then one or more severity levels and/or Cleared state to filter the
alarm having the selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the
alarms created during that specific time frame only.
Probable Cause field
Select Probable Cause and then choose a specific alarm (one or more) to filter these particular
alarms only.
[2] Delete Filters ...

When this menu is selected, the window shown below opens (example):
Fig. 334. Alarms Monitor Delete Filters ...
By means of this menu the filters previously created can be canceled. Default filters cannot be
canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters)
in the Filters column and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[3] Delete Selected Filter

Default filters cannot be deleted. Selecting a customized filter and selecting Filters % Delete
Selected Filter, the filter is deleted, after having confirmed the following question:
[4] Edit Selected Filter

Default filters cannot be edited. Selecting a customized filter and selecting Filters % Edit Selected
Filter, the same screen of Fig. 333. on page 612 opens, where you can make your changes, then
click Done pushbutton to confirm them.

3DB 16142 JAAA Ed.01 613 / 866
[5] Save Filters As ...

Fig. 335. Alarms Monitor Save Filters As ...
A default filter, or a filter previously created by means of the Add a filter menu, can be saved to be
used for some other Craft Terminals.
Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Name
field, select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[6] Load Filters From ...

Fig. 336. Alarms Monitor Load Filters From ...
A filter previously saved on another Craft Terminal can be loaded on your Craft Terminal by this menu.
Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded
Filters columns will show respectively the NE list and the filters list made available by the selected
file.
Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the
inserted characters are attached before the names of the Loaded Filters. For instance entering
<Vim>, the names of the filters change from APT to VimAPT.

614 / 866 3DB 16142 JAAA Ed.01
315.2.6 File Menu
The File menu allows to Save or Load the AM History:

[1] Save History for selected NE
This menu allows to save a file with one of the two global lists of each NE. Select the global list of
a specific NE, open the Save History menu for the selected NE, and enter filename and relevant
directory in the opening window.
[2] Load History for selected NE
By means of this menu it is possible to display the global list of a certain NE previously saved.
315.2.7 Printing the alarms and logs
As shown below, in AM screen (with mouses right button), select Print current view to launch the print,
then specify the printer.

3DB 16142 JAAA Ed.01 615 / 866
315.2.8 Exporting the alarms and logs

As shown in Fig. 337. , in AM screen (with mouses right button), at first Select All to select all shown

alarms, then Export Alarms (in CSV, HTML, XML, or PDF format), and specify where to save the file;

at last Select None to deselect all alarms previously selected.
N.B. The CSV method defines a model to memorize the data of a table using comma character. The
fields of a single row are separated by one symbol , and the rows of a table are separated by
the NEWLINE character.
Fig. 337. Exporting the alarms and logs

616 / 866 3DB 16142 JAAA Ed.01
315.2.9 Navigate from AM to USM
The AM program gives to the user the possibility to navigate from AM to JUSM (and viceversa).
When a user selects an alarm in AM screen, he/she can request to show the object, on which the alarm
was raised, in JUSM, as in example of Fig. 338.
N.B. If not active, JUSM is automatically started (the login prompt is displayed, with UserName and
Password to be entered).
(1) With mouses left button, select one alarm
(2) On selected alarm, with mouses right

button, select Navigate to USM
(3) JUSM shows the object,

on which the alarm was raised
Fig. 338. Navigate from AM to USM

3DB 16142 JAAA Ed.01 617 / 866
315.2.10 Navigate from USM to AM

This operation is complementary to the Navigate from AM to USM described before.

When a user selects an alarm in JUSM screen, he/she can request to show the same alarm in the AM

screen, as in example of Fig. 339.
N.B. If not active, AM is automatically started.
(1) With mouses left button,

select one alarm (2) With mouses right button,
select Navigate to AM
(3) AM screen opens

with the same alarm selected
Fig. 339. Navigate from USM to AM

618 / 866 3DB 16142 JAAA Ed.01
315.2.11 Shortcut icons
The following shortcut icons, for simplicity not shown in previous figures, are available:
A B C D
E F G H I J
K L M N O P Q R
A and B: these functions are particularly useful during the Multiple NE Alarms Monitor
(para.315.2.4 on page 611 ); A arranges windows vertically, while B arranges windows boxed, as
in following examples:
VERTICAL ARRANGEMENT BOXED ARRANGEMENT
C maximizes Windows
D exits from the AM application
E expands all tree nodes
F collapses all tree nodes
G removes the selected NE from the AM application

3DB 16142 JAAA Ed.01 619 / 866
H, I, and J are related to the filter management ( para.315.2.5 on page 612 ); H adds a new filter,
I deletes the selected filter, and J edits the selected filter.

K and L are related to the management of the rows in the active table; K selects all rows, while J

deselects all rows.
M performs the Navigation to USM ( para.315.2.9 on page 617 ).
N, O, P and Q are related to the Export of the alarms and logs ( para.315.2.8 on page 616 );
their export format is clearly shown by the icon.
R acts as the Print Current View available on all screens.

620 / 866 3DB 16142 JAAA Ed.01
315.3 Event Log Browser (ELB)
315.3.1 ELB scope

An event is meant to be:
a configuration change
a change of the value of an attribute
an automatic switchover
a manual operation carried out by the operator.
ELB is a tool that shows the list of events generated on NE at a specific moment. The main functionalities
offered are:
list of events and main information (time, type, etc.)
print them
export a summary view of events lists to an HTML file, or to a CSV (Comma Separated View) file.
315.3.2 ELB startup
The ELB application can be launched on a loggedin 9400AWY NE through the WebEML command:
Diagnosis % Log Browsing % Event Log
If the NE does not respond at the get request or responds with an ACCESS DENIED message, the
application communicates the problem to the user and does not refresh the tables containing alarms and
event. A special indicator shows to the user that the application is offline until a new user request for
tables refresh succeeds.
After refresh completion, the Event Log Table screen opens.
WARNING: The Event Log Table is updated only if the corresponding Log Switch is unlocked (see

3DB 16142 JAAA Ed.01 621 / 866
315.3.3 Event Log Table screen

At first command execution, or by the user command Refresh, the application retrieves the data about the

events presents on NE in that moment.

[1] Row contents
The events are shown as rows in a table. For each event, the following field are shown:
Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss.
Reference Time (CEST) year.
Notification ID: a unique identifier for the event.
Explanation: a statement built with the event log data to explain what the event represents.
Export the Events data to an external file
Refresh the
Events
table to current
values
Print the Events
Fig. 340. Event Log Table screen

622 / 866 3DB 16142 JAAA Ed.01
[2] Sorting rows
Clicking on columns headers, events can be ordered by the fields values.

[3] Selecting rows
Clicking on rows, the events (one ore more) can be selected. This selection can be used in the screen
of Fig. 341. below.
Clicking the Clear Selection pushbutton in the screen of Fig. 340. on page 622 , all rows are
deselected.
[4] Printing events
Clicking the Printer symbol in the screen of Fig. 340. on page 622 , all events are printed,
independently from the selection you may have done (point [3] above).
[5] Export events to an external file
The application allows to export the content of the events table in the following ways:
in an HTML table
in CSV formatted text

The CSV method defines a model to memorize the data of a table using comma character. The
fields of a single row are separated by one symbol , and the rows of a table are separated by
the NEWLINE character.
as PDF document
in XML format
In both cases, you can choose to export All entries or the Selection you may have done (point
[3] above).
Fig. 341. Export events screen
After having made the selection, and clicked OK pushbutton, a save screen is opened, asking where
save must be done.

3DB 16142 JAAA Ed.01 623 / 866
624 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
316 DIAGNOSIS
This chapter describes the following Diagnosis menus: Log Browsing % Software Trace Log, Remote
Inventory, Abnormal Condition List, Summary Block Diagram View, and Current Configuration
view.
Subject On page
Log Browsing % Software Trace Log 626
Remote Inventory 627
General 627
Remote Inventory display 628
Abnormal Condition List 628
Summary Block Diagram View 629
Current Configuration view 632
Ethernet Port Counters Monitoring 633
General 633
Monitoring on disabled ports 634
Displaying modes 634
N.B. For the following other Diagnosis menu commands:
Alarms % NE Alarms, refer to para. 315.2 from page 606
Log Browsing % Event Log, refer to para. 315.3 from page 621

3DB 16142 JAAA Ed.01 625 / 866
316.1 Software Trace Log

N.B. The use of the Software Trace Log option is reserved to the AlcatelLucent technicians.

Performing Log Browsing % Software Trace Log, the application will try to download the trace log file
from NE, showing a temporary information box:
If successfully, the file content will be displayed in a new window (example below), from which it is possible
to save or print the file.

626 / 866 3DB 16142 JAAA Ed.01
316.2 Remote Inventory
316.2.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. 97. Remote Inventory AlcatelLucent standard format

Information field name Location Length (Byte) Encoding
Format identifier 0 2 ASCII 22
Company identifier 12 4 ASCII
Mnemonic (see Tab. 98. below) 36 8 ASCII
CLEI code 711 10 ASCII
Unit Part Number + ICS 1218 14 ASCII
Software/Firmware PN + ICS 1925 14 ASCII
Factory identifier 2627 4 ASCII
Serial Number 2835 16 ASCII
Date Identifier 36 2 ASCII 00
Date 3739 6 ASCII
Customer field 4062 46 ASCII
Checksum 63 2 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. 98. Remote Inventory mnemonic field

UNIT TYPE MNEMONIC NOTE
IDU Main Unit (without any plugin) M486032
IDU Extension Unit (without any plugin) E486032
4 x Gigabit Ethernet plugin P4DATASW
PDH Tributary optional plugsin P16E1DS1
Audio channels, Service Channel plugin PACSC
ODUE = 32Mb ODU V1
ODU2E = 32Mb ODU V2
ODU unit
ODU32E = 64Mb ODU V1
ODU232E = 64Mb ODU V2

3DB 16142 JAAA Ed.01 627 / 866
316.2.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. 342. Remote Inventory screen (example)
316.3 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions (i.e.
the manual operations) currently active in the NE.
The abnormal conditions can be:
Switch commands Forced or Lockout

Loopback
Tx power manual operation
Tx muting (manual or automatic)
ODU service kit connected
Fig. 343. Abnormal Condition List screen

628 / 866 3DB 16142 JAAA Ed.01
316.4 Summary Block Diagram View
The Summary Block Diagram View of the Diagnosis menu displays a global logical view (strictly
related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in
the system (ODU+IDU). It can also run by the Summary Block Diagram view shortcut of the Main tool
bar (see Fig. 254. on page 516).
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, with or without the Audio/User Service Channel plugin
1+1 HSB with or without the Ethernet ports, with or without the Audio/User Service Channel plugin:
with EPS enabled
with EPS disabled
1+1 FD with or without the Ethernet ports, with or without the Audio/User Service Channel plugin:
with EPS enabled
with EPS disabled
Some examples are shown in following figures:

1+0: Fig. 344.
1+1 with EPS enabled: Fig. 345. to Fig. 347.
1+1 with EPS disabled: Fig. 348.
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.
Loopback indicator: yellow letter L means active loop.
Performance indicator: yellow letter P means active performance.
N.B. In the 1+1 configuration the current position of the switches is also shown.

3DB 16142 JAAA Ed.01 629 / 866
Fig. 344. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports
Fig. 345. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports & EPS enabled

630 / 866 3DB 16142 JAAA Ed.01
Fig. 346. Summary Block Diagram View example: 1+1 HSB 16E1ETH with Audio/User Service
Channel PlugIn (Lockout) & EPS enabled
Fig. 347. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service Channel
PlugIn & EPS enabled
3DB 16142 JAAA Ed.01 631 / 866
Fig. 348. Summary Block Diagram View example: 1+1 HSB or FD 16E1 & EPS disabled
316.5 Current Configuration view
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. 254. on page 516) or
selecting Current Configuration view from the Diagnosis menu, the following readonly screen is
opened:
Fig. 349. Current Configuration view screen
By File Save As, screen content can be saved as text file

632 / 866 3DB 16142 JAAA Ed.01
316.6 Ethernet Port Counters Monitoring
316.6.1 General
This menu is available only if the Enhanced Ethernet plugin is installed and has been defined by choice
16E1GData in the Configuration % System Settings screen of Fig. 282. on page 554
This menu ( Fig. 350. below ) can be opened by Diagnosis % Ethernet Port Counters Monitoring, or
clicking the suitable shortcut in the WebEML Main tool bar ( see Fig. 254. on page 516 ).
Fig. 350. Ethernet Port Counters Monitoring screen
The information related to a Tributary data PM counter are:
TRCO (Total Received Correct Octets): total number of octets of Ethernet frames received correctly
by the Virtual Ethernet Interface, including Ethernet header characters.
TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly by the
Virtual Ethernet Interface.
TRSEF (Total Received Service Errored Frames): it is the sum of three contributions:
TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be
discarded due to buffer congestion.
TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out by
the Virtual Ethernet Interface, including Ethernet header characters.
TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by the Virtual
Ethernet interface.

3DB 16142 JAAA Ed.01 633 / 866
The following items resume the features supported:
Only an Automatic monitoring procedures is forecasted. In this Mode, the values of the Ethernet

Counters are auto refreshed in every period programmable via configuration by the operator.

When push the Start button, the counters reading is start
When push the Clear button, the current counters reading session is cleared and a new one is
started.
When push the Stop button, the counters reading session is frozen.
All the status will be lost when JUSM or NE will be restarted.
316.6.2 Monitoring on disabled ports
If, when the application is started, there are disabled ports, the counters and the elapsed time associated
to these ports, will be set to 0.
If during the application, one or more ports become enabled, the counters reading is performed and the
delta between the current values of the Ethernet counters and the values at the enable time, is displayed.
The elapsed time is updated too, with the time elapsed since the enable of the port.
If during the application, one or more ports become disabled, the counters and the elapsed time related
to these ports shall be frozen to the current values.
316.6.3 Displaying modes
Ethernet Counters is displayed in two different modes: in tabular format and/or in graphic one.
The graphic representation of the Ethernet counters trend, has the horizontal axis which represents the
elapsed time and the vertical axis the counter value (in logarithm scale):
Fig. 351. Graphic View for each port counter values
Each graphic is related to one port and it visualizes and updates automatically the six Ethernet counters
trend.
Operator can choose one port and click graphic view button to open this port graphic view to check port
data trend after start ethernet counters.

634 / 866 3DB 16142 JAAA Ed.01
317 PROTECTION SCHEMES
This domain is present in 1+1 configurations only.
N.B. for the functional description of protections at system and hardware levels, refer to:
Subject On page
Possible Resource Trees below
Radio Protection Management 637
HSB Transmission Protection Management 639
Rx Static Delay 641
Equipment Protection Management 643
317.1 Possible Resource Trees
The protection Schemes domain view consists of the following areas (Fig. 352. below):
Resource Tree Area: as shown, resources displayed depend on system configuration setting: see
NE type area and Without EPS (RPS only) field in Fig. 282. on page 554 , and in Fig. 200.
on page 450
A single left click selection of an element tree causes the activation of the corresponding Graphical
representation displayed in the Resource list area
1+1 HSB without EPS
1+1 HSB with EPS
1+1 FD without EPS
1+1 FD with EPS

Fig. 352. Resource Tree Area of Protection Schemes according to configuration

3DB 16142 JAAA Ed.01 635 / 866
Resource List Area: displays tabular information about the selected resource in tree area. An
example is displayed in the Fig. 360. on page 643

A single left click selection of a resource causes the activation of the corresponding Graphical

representation displayed in the Resource detail 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. An example is displayed in the
To see the current position of the switches enter the menu Diagnosis > Summary Block Diagram View
(refer to para. 316.4 on page 629 ):
Mux/Demux Protection corresponds to the Switch Tx and the Rx output switch in Fig. 346. on
page 631
the Radio protection corresponds to the Switch RPS HS in Fig. 346. on page 631
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. 346. on page 631
The HSB protection is available only if the HSB configuration has been selected.

636 / 866 3DB 16142 JAAA Ed.01
317.2 Radio Protection Management
The Radio Protection Management is performed by selecting the Radio Protection element tree.
The following window (Fig. 353. below) allows a complete view of all NE resource involved in a RPS
protection:
Schema Parameters
Channels Parameters
To read the correct indication on the switch status press here to refresh the screen
Protection Command Status NOT Automatically Updated
Fig. 353. Radio Protection View
317.2.1 Schema Parameters
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).
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.

3DB 16142 JAAA Ed.01 637 / 866
317.2.2 Commands

To enter the Commands menu, click, in the Tree view (Fig. 354. below), on the Spare #0 element or on

the Main #1 element

Fig. 354. Radio Protection Switch (example for Main #1 selected)
The operator can modify the state of the switch through commands Lockout, Forced and Manual.
WARNING: whenever EPS lockout is set (see para.317.5.2 on page 644 ), RPS is switched on CH1,
and these commands are not available (greyed).
Tab. 99. Command priority list

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),
independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in
service Channel 0, independently of the possible active alarms. This command activates signaling
ABN.
Automatic Switch is the normal operation condition: the position of the switch depends on the
commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that can activate an
automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If
this command is active, it will be removed by an incoming alarm. This command does not activate
signaling ABN.
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.

638 / 866 3DB 16142 JAAA Ed.01
317.3 HSB Transmission Protection Management
The Transmission Protection Management is performed selecting Transmission Protection element tree.
The following windows (Fig. 355. below) allows a complete view of all NE resource involved in a TPS
protection:
Schema Parameters
Channels Parameters
Fig. 355. 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.

3DB 16142 JAAA Ed.01 639 / 866
317.3.2 Commands


the Main #1 element

Protection Command Status NOT Automatically Updated
Fig. 356. HSB Tx Protection Commands (example for Main #1 selected)

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
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.

640 / 866 3DB 16142 JAAA Ed.01
317.4 Rx Static Delay
Fig. 357. 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. 358. 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. 359. . The automatic procedure is disabled during
manual operation.

3DB 16142 JAAA Ed.01 641 / 866
Fig. 359. 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.

642 / 866 3DB 16142 JAAA Ed.01
317.5 Mux/Demux Protection (EPS) Management
The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.
The following window (Fig. 360. below) allows a complete view of all NE resource involved in the EPS
protection:
Schema Parameters
Channels Parameters
Fig. 360. Mux Protection
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).
The operator choice for Operation Type will be applied by clicking on Apply button.

3DB 16142 JAAA Ed.01 643 / 866
317.5.2 Commands


the Main #1 element

Fig. 361. Mux Protection Switch (example for Main #1 selected)

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
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.
signaling ABN.

644 / 866 3DB 16142 JAAA Ed.01
318 LOOPBACKS
The functions described in this section allow to perform the test operations by loopbacks.
Subject On page
General information, and Loopback timeout management 646
Hardware implementation 647
Available Loopbacks 649
IDU loopbacks 647
ODU loopbacks 648
Loopback domain views 652
How to activate a loopback 655
How to remove a loopback 656

3DB 16142 JAAA Ed.01 645 / 866
318.1 General information, and Loopback timeout management

To avoid the risk of a permanent disconnection from ECT/NMS of a remote NE after the execution of a

loopback, a timeout mechanism, and a limitation of number of contemporary loopbacks are implemented.

As shown in Fig. 362. below, the click of Loopback Points in the Resource Tree Area opens the
Configuration panel, which:
shows the loopback point presently active, if any.
N.B. only one loopback point can be active at a time on one NE. The request of the second
loopback is refused with an error message.
allows the configuration of the loopback duration:
the time range is from 5 min (default) to max 4 days.

Only the last loopback lifetime applied by the operator is valid (if a lifetime is interrupted and
a new lifetime is fixed, only the new lifetime is performed till to expire).
If a loopback is presently active:
its remaining timelife can be shown by pushing the Refresh button;
the operator can change the loopback lifetime in each instant, before the expire.
once the time out period is applied, the loopback point will become not active, if it is active when
the time is over.
Fig. 362. Loopback Points configuration panel

Notes:
After any NE restart, the activation of each loopback point is lost and must be recreated again, if
needed, starting with a new timeout period.
The presence of a loopback is indicated as an abnormal condition.
Loopbacks on disabled tributaries are not applied (even if no messages are displayed when the
command is sent)

646 / 866 3DB 16142 JAAA Ed.01
318.2 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 V1
1 near end loopback is embedded in the ODU V2
N.B. All loopbacks can be set by both the LCT (local CT) and the RCT (remote CT): the definition
of LCT and RCT is given in tables of para.32.1 from page 410
But, you must be aware that, if the RCT accesses the NE from the Far end NE, some loopbacks
cause the isolation of the Near end NE from such a RCT.
318.2.1 IDU loopbacks
[1] Near end IDU cable loopback internal

Near end Near end Far end Far end
IDU ODU ODU IDU
RF
16E1/E3 LIU FRAME MODEM IF RF IF RF MODEM FRAME LIU 16E1/E3
Station A Station B
Fig. 363. Near end IDU cable loopback
WARNING: if performed by a RCT accessing the NE (Station A) from the Far end NE (Station B),
this loopback causes the isolation of the Near end NE from such a RCT.
Suggestion: use a short timeout period.
[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 RCT.
It is not forbidden (even if not considered here) to use a RCT from station B to activate this loop.
IDU ODU ODU IDU
RF
Station A Station B
Fig. 364. Far end IDU tributary loopback

3DB 16142 JAAA Ed.01 647 / 866
[3] 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 RCT from station B to activate this loop.
Nearend Nearend Far end Far end

IDU ODU ODU IDU
RF
Station A Station B
Fig. 365. Near end tributary loopback
318.2.2 ODU loopbacks
[1] Near end ODU cable loopback internal

IDU ODU ODU IDU
RF
Station A Station B
Fig. 366. Near end ODU cable loopback
[2] Near end RF loopback internal
WARNING: this feature is available on ODU V1
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.
IDU ODU ODU IDU
RF
Station A Station B
Fig. 367. Near end RF loopback

648 / 866 3DB 16142 JAAA Ed.01
318.3 Available Loopbacks
N.B. The DATA block in Fig. 368. is present with the Ethernet port option only.
STATION A STATION B
CTA CTB
IDU ODU ODU IDU
DATA DATA
MUX/ MODEM RF RF MODEM MUX/
DEMUX DEMUX
TRIB TRIB
2 4 5 6 3
1
Fig. 368. Available loopbacks
Tab. 102. Available loopbacks

N.B. Refer to:
Fig. 369. on page 650 (1+0 configurations)
Fig. 370. on page 651 (1+1 configurations)
CT selection in
Loopback Loopback
No. the Resource Location Note
name type
Tree Area
E1
1 Tributaries Near End External line Input loopback at tributary level.
Port#xx
E1 Loopback toward the remote
2 Tributaries Near End Internal
Port#xx station at tributary level.
E1 Loopback in the remote station at
3 Tributaries Far End Internal
Port#xx tributary level.
Loopback at the IDU output at
4 IDU cable Channel 1 Near End External line
aggregate level.
ODU Loopback at the ODU input at
5 Channel 1 Near End External line
cable aggregate level.
RF local loopback.
6 RF Channel 1 Near End External line
(N.B.)
N.B.
WARNING: this feature is available on ODU V1
Before activating this loopback the Remote Tx must be muted (Menu Radio > Configuration)

3DB 16142 JAAA Ed.01 649 / 866
In Fig. 369. 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.

4 IDU
CABLE
1 Tributaries 5 ODU 6 Radio port

(External Line) CABLE (RF loopback)
2 Tributary
Near End Internal
Fig. 369. 1+0 Loopback types
An active loopback is indicated by a yellow letter: L (if white, the loopback is not active)
Switching status are displayed through different dynamic drawings:
If any indication does not correspond to the expected one, press Refresh to actualize the view.
WARNING:
the Tributary Near End Internal loopback (2), if present (yellow), has been activated by the
remote station
the RF loopback (6) is available on ODU V1

650 / 866 3DB 16142 JAAA Ed.01
In Fig. 370. 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 Radio port

5 ODU 6 (RF loopback)
CABLE CABLE
1 Tributaries
(External Line)
2
Tributary
Near End Internal
Fig. 370. 1+1 Loopback types
An active loopback is indicated by a yellow letter: L (if white, the loopback is not active)
Switching status are displayed through different dynamic drawings:
WARNING:
the Tributary Near End Internal loopback (2), if present (yellow), has been activated by the
remote station
the RF loopback (6) is available on ODU V1

3DB 16142 JAAA Ed.01 651 / 866
318.4 Loopback domain views

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. 371. below, the tree will be expanded according to NE configuration.
Fig. 371. Loopback View for PDH Tributaries (1+0)

652 / 866 3DB 16142 JAAA Ed.01
Fig. 372. Loopback View for PDH Tributaries (1+1)
WARNING: the RF loopback (6) is available on ODU V1
Fig. 373. Loopback View for Radio PDH

3DB 16142 JAAA Ed.01 653 / 866
654 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

Fig. 374. Loopback CABLE

USER MANUAL
318.5 How to activate a loopback
WARNING: the RF loopback is available on ODU V1

WARNING: loopbacks on disabled tributaries are not applied (even if no messages are displayed when
the command is sent)
N.B. For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to the
related Channel; for the Tributaries loopbacks must only be forced to the radio switch to Channel
0 or lockout to Channel 1.
To activate a loopback:
[1] Trough the Configuration panel of Fig. 362. on page 646 :
verify that another loop is not active
and set the desired timeout period.
[2] 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.
[3] The screen in Fig. 375. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 375. Loopback activation
[4] Select Active in the Activation field.
[5] Click on Apply.
[6] 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.

3DB 16142 JAAA Ed.01 655 / 866
318.6 How to remove a loopback

To deactivate loopbacks use the following steps:

[1] Trough the Configuration panel of Fig. 362. on page 646 , verify the active loopback, to be removed.
[2] 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.
[3] The screen in Fig. 376. below will appear. (In this screen has been selected the loopback on tributary
E1, Near End).
Fig. 376. Loopback removing
[4] Select Not Active in the Activation field.
[5] Click on Apply.
[6] 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.

656 / 866 3DB 16142 JAAA Ed.01
319 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.
Subject On page
General information on the performance monitoring process below
Performance menu 658
CD (Current Data) 660
CD parameters 660
CD Counters 661
HD (History Data) 662
HD Parameters 662
Threshold tables 663
How to change a threshold table 663
How to create a threshold table 664
Threshold table association 664
319.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. FEC MODEM MODEM FEC PROPR.

FRAMING ENCODE RF RF DECODE FRAMING
Radio Hop (before the switch)
Radio Link (after the switch)
Fig. 377. Radio sections

3DB 16142 JAAA Ed.01 657 / 866
319.2 Performance menu

The performance view allows the user to activate and monitor the PM process on the selected object.

This domain view consists of the following areas (Fig. 378. below):
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. 378. Performance View
The performance reports can be of 2 different types:
15 minutes
24 hours
N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errors
have been occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
Considering one section (see Fig. 377. on page 657), 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:
Errored Seconds
Severely Errored Seconds (N.B.)
Background Block Error
Unavailable Seconds
N.B. 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.

658 / 866 3DB 16142 JAAA Ed.01
To see (and configure) the current report, with reference to Fig. 379. below :
[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).
To see an history log, with reference to Fig. 379. below :
[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. 379.
Fig. 379. 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.

3DB 16142 JAAA Ed.01 659 / 866
319.3 CD (Current Data)

The window displayed in Fig. 380. below allows to start and to read the 15min PM report and 24h PM

report.

Fig. 380. Current Data View
319.3.1 CD parameters
The fields displayed in the upper part of Fig. 380. on page 660 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.

660 / 866 3DB 16142 JAAA Ed.01
319.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 380. on page 660 (Counters Area) allow the
management of performance events.

In the left part of Counters Area, there is a graphical description of the event counter value:
BBE (Errored block)

ES (Errored second)
SES (Severely Errored Second)
UAS (Unavailable second)
N.B. These values refer to the last refresh performed by pressing the Refresh button.
In the right part of Fig. 380. on page 660, 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.

3DB 16142 JAAA Ed.01 661 / 866
319.4 HD (History Data)

The PM process monitors the parameters during a specified interval (i.e. 15min) and stores their values

in history data. A History Data collection is created automatically at the end of each time interval of Current

Data and deleted when the relative CD is deleted.
319.4.1 HD Parameters
The table displayed on the following window (Fig. 381. below) collects the history data for a related PM
report.
Fig. 381. 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).

662 / 866 3DB 16142 JAAA Ed.01
319.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. 319.5.3 Threshold table
association.
319.5.1 How to change a threshold table
Fig. 382. 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.

3DB 16142 JAAA Ed.01 663 / 866
319.5.2 How to create a threshold table

Fig. 383. 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.
319.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.
a) END OF SECTION

664 / 866 3DB 16142 JAAA Ed.01
SECTION 4: SW INSTALLATION IN THE PC, AND COMMISSIONING
This section provides the whole operative instructions for the preparation of the Craft Terminal based on
the SWP TCO SUITE CDROM and the SWP 9400AWY V2.1.3 CDROM, and for the LineUp and
Commissioning of the two NEs making up the radio link.
N.B. For the information concerning the SWP TCO Suite, please read carefully the point v Notes
on used TCO Suite and associated User Manual on page 5
Please read para.11.2 on page 26 for an introduction to the procedures of this

section.
a) Preparation of Craft Terminal
Chapter 41 Preparation of the Craft Terminal based on the SWP TCO SUITE
and the SWP 9400AWY V2.1.3
This chapter describes how to perform the preparation of the Craft Terminal, using
the SWP TCO SUITE CDROM and the SWP 9400AWY V2.1.3 CDROM, to 667
allow all operations executable by the SWP TCO SUITE, and to allow the V2.1.3
SW download function. This chapter describes also how to use LLMAN, after its
installation and configuration.
b) LineUp and Commissioning
Chapter 42 LineUp and Commissioning

This chapter details all phases necessary for the LineUp and Commissioning of 675
the two NEs making up the radio link.
Chapter 43 Use of the Acceptance Tool to write the TRS

This chapter describes in detail the functions of the Main Menus Acceptance
721
Tool, to write the TRS document during the commissioning (acceptance phase)
of the two NEs making up the radio link.

SW INSTALLATION IN THE PC AND COMMISSIONING
3DB 16142 JAAA Ed.01 665 / 866
666 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
41 PREPARATION OF THE CRAFT TERMINAL BASED ON THE SWP TCO
SUITE AND THE SWP 9400AWY V2.1.3

This chapter describes how to perform the preparation of the Craft Terminal, using the SWP TCO SUITE
CDROM and the SWP 9400AWY V2.1.3 CDROM, to allow all operations executable by the SWP TCO
SUITE, and to allow the V2.1.3 SW download function.
This chapter describes also how to use LLMAN, after its installation and configuration.
N.B. Most of these operations, with the exception of that described in para.41.5 on page 673 , are
described in the TCO Suite User Manual [see point b ) on page 5 ], and here are only
referenced.
Subject On page
PC requirements to run and install the SWP TCO SUITE 668
Craft Terminal preparation 668
Operation sequence for the JRE installation, and to perform the Local
668
copy of the TCO Suite and of the WebEML (Jusm/CT)
LLMAN installation and configuration, and use 669
LLMAN installation and configuration 669
How to start and use the LLMAN application 669
Full information regarding the use of the LLMAN application 672
Local Copy of the SWP 9400AWY V2.1.3 673

3DB 16142 JAAA Ed.01 667 / 866
41.1 PC requirements to run and install the SWP TCO SUITE

Please refer to the chapter SWP TCO SUITE scopes and requirements of the TCO Suite User Manual.

41.2 Craft Terminal preparation
For the Craft Terminal preparation, both the SWP TCO SUITE CDROM, and the SWP 9400AWY V2.1.3
CDROM are used, as described in the following:
Used CDROM
Operation
SWP TCO SUITE SWP 9400AWY V2.1.3
JRE installation, and Local copy of the TCO Suite

and of the WebEML (Jusm/CT). X
Para.41.3 below
LLMAN installation and configuration.

X
Para.41.4.1 on page 669
Local Copy of Software Package.

X
Para.41.5 on page 673
41.3 Operation sequence for the JRE installation, and to perform the Local
copy of the TCO Suite and of the WebEML (Jusm/CT)
Please refer to the appendix Preparation of the Craft Terminal based on the SWP TCO SUITE of the TCO
Suite User Manual.
At the end of such operations:
the required version of JRE (Java Runtime Environment) must have been installed,
and the following shortcuts must be available on the desktop of your PC:
TcoSuite.17
Fig. 384. Shortcut to the Local copy of TCO Suite
AWY_CT_V01_07
Fig. 385. Shortcut to the Local copy of WebEML (Jusm/CT)

668 / 866 3DB 16142 JAAA Ed.01
41.4 LLMAN installation and configuration, and use
These operations are necessary if you want to access any 9400AWY through its serialFinterface (see
Fig. 181. on page 411 ).

41.4.1 LLMAN installation and configuration
For the execution of the procedure, please refer to the appendix LLMAN installation, configuration and
use of the TCO Suite User Manual.
WARNING: the version of LLMAN contained in the SWP TCO SUITE Rel.1.7 CDROM is higher than
that of LLMAN contained in the:
SWP 9400AWY V2.0.6 CDROM

SWP 9400AWY V2.1.2 CDROM
SWP TCO SUITE Rel.1.6 CDROM
Therefore, if, in the past, you have used any of such CDROMs to install LLMAN during
the:
1320CTbased Craft Terminal preparation,

or SWP TCO SUITE Rel.1.6based Craft Terminal,
you must install this new version of LLMAN.
N.B. the new version of LLMAN is fully compatible with all 1320CTbased
applications.
Having reached this phase, you have finished the Software transfer from the SWP TCO SUITE Rel.1.7
CDROM into the PC environment. Now, you can extract this CDROM from the PCs CDROM unit.
41.4.2 How to start and use the LLMAN application
LLMAN can be started only if you have successfully performed the LLMAN installation and configuration
described in para.41.4.1 above.
LLMAN must be always started manually before the start of the WebEML (which, in turn, opens the NEtO
screen):
a) Set/check of PC desktop Properties settings for LLMAN
WARNING: After the LLMAN startup, during system hibernate or standby, the LLMAN could not
working correctly after reentering the system.
So, when using LLMAN, it is mandatory that the PC desktop Properties System
standby and System hibernates are both set to Never, as shown in following
Fig. 386. :

3DB 16142 JAAA Ed.01 669 / 866
(2)
(3)
(1)
Fig. 386. PC desktop Properties settings for LLMAN
b) LLMAN startup
1) From WINDOWS screen, start LLMAN performing Start % Programs % AlcatelLucent %

Lower Layers % Lower Layers Manager
2) LLMAN starts, and its animated symbol appears in operating system tray bar.
This animated icon indicates the communication status:
if the physical link between the computer and the equipment is missing, the red icon
appears;

670 / 866 3DB 16142 JAAA Ed.01
during the attempts to establish the communication between the computer and the
connected equipment, the yellow icon appears;
while the communication between the computer and the connected equipment is
established, the AlcatelLucent icon appears.
In this case, doubleclick on the icon, to open the LLMAN screen: see next step 3 )
3) Main fields and command buttons of the LLMAN screen
Green link led means

connection
established on the
serial link
Local IP address of NE
connected to the PC
serial port (or
USB/RS232 adapter)
Closes the screen (but not Closes the

the LLMAN program) LLMAN program
Fig. 387. LLMAN screen
4) Click on Close button to close the screen, leaving the LLMAN program running.
Now you can start NEtO using the NEs F interface.

3DB 16142 JAAA Ed.01 671 / 866
41.4.3 Full information regarding the use of the LLMAN application
Clicking on the Help button of LLMAN screen ( Fig. 387. on page 671 ), the relevant full help is opened;

explore it to find information not given in this Appendix.

N.B. This help can be also obtained performing Start % Programs % AlcatelLucent % Lower
Layers % Lower Layers Manager Help

672 / 866 3DB 16142 JAAA Ed.01
41.5 Local Copy of the SWP 9400AWY V2.1.3
This operation has the scope of making the new equipment software package SWP 9400AWY V2.1.3
available in the PC, for its successive downloading toward the NEs equipment controller and the
peripheral units (such a downloading is explained in chapter 59 from page 811 ).
Operations sequence
1) Insert the SWP 9400AWY V2.1.3 CDROM in the PC
After a while, the following screen opens:
2) Click the button Local Copy of Software Package

In the screen that opens, select the directory where the NE software package must be copied, then
click Open
N.B. If previous AWY releases have already been installed in the PC, it is suggested to use the
same directory previous used (ALCATEL).
3) The SWP 9400AWY V2.1.3 files are copied from the CDROM into the chosen directory:

3DB 16142 JAAA Ed.01 673 / 866
4) Note that, in the SW download to the NE (explained in Step 2 from page 818 ), you will have to select
the descriptor file R94A.DSC from the directory where you have now put all AWY V2.1.3 files:

Fig. 388. Directory selection for the descriptor file R94A.DSC of AWY V2.1.3
Having reached this phase, you have finished the Software transfer from the SWP 9400AWY V2.1.3
CDROM into the PC environment. Now, you can extract this CDROM from the PCs CDROM unit.

674 / 866 3DB 16142 JAAA Ed.01
42 LINEUP AND COMMISSIONING
This chapter details all phases necessary for the equipment lineup and commissioning.
Subject On page
Introduction 676
General 676
SafetyEMCEMFESD norms and Cautions to avoid equipment damage 677
Conventions 678
Summary of the commissioning phases 679
General information about test bench drawings 680
Phase 1: Commissioning of STATION A (NE turn up and data definition) 681
Phase 1: Commissioning of STATION B (NE turn up and data definition) 686
Note on NE login 687
Phase 1: Fine antenna alignment, and preliminary checks (stations A &

687
B)
End of commissioning phase 1 in STATION A 692
Phase 2: Commissioning of station A (acceptance test) 693
Phase 2: Commissioning of station B (acceptance test) 717
Phase 3: Final acceptance of the link 718
Phase 4: Final operations 718
Annex A: fine antenna alignment 719
Annex B: light service kit cable operative information 720

3DB 16142 JAAA Ed.01 675 / 866
42.1 Introduction

42.1.1 General

This chapter details all phases necessary for the equipment lineup, commissioning, and acceptance,
providing the user with the information needed to connect, power on, and perform a minimum turnup of
a radio link comprising two 9400AWY Rel.2.1 Network Elements both running with the SWP 9400AWY
V2.1.3 .
It is assumed that, at both premises (Station A and Station B):
a) the mechanical installation and cabling of the INDOOR and OUTDOOR units is completed, the
antennas are installed and prepositioned, and the IDUODU cable(s) has/have been 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 (part A from page 23 of this
manual).
b) the following documents are available, according to the contract:
Contract, Site Installation Documents & Technical Documentation
Product Release Notes
c) the Flash Card has already been installed in the IDU Main unit; see point [3] on page 77
d) the Flash Card content is as delivered from AlcatelLucent factory, i.e.:
with the SWP 9400AWY V2.1.3 present in the SW COMMIT bank; see point [2] on page 425
Note: the SWP version check is envisaged in para.42.2.4 on page 683
with default NE configuration data ( see point [3] on page 425 ); in particular:
the local IP address and Ethernet IP address, of both the NE 9400AWY stations, are
set at default value 10.0.1.2
there is only one Administrator login profile with Username = initial, and password =
initialing
e) the .qcml configuration provisioning files (one specific for each one of Station A and Station B) have
already been prepared by means of the Not NEinteractive modality Provisioning Tool ( see point
[1] on page 444 ).
These .qcml configuration provisioning files must be consistent with the hardware configuration at
IDU and ODU sides, and with the NE routing data defined in the documents cited in point b ) above.
Suggestion
After the.qcml file loading in the NE, you will have to know the new NE network routing
data (defined in the .qcml file) to login the NE. If you do not know them, open the .qcml
by means of the Not NEinteractive modality Provisioning Tool (see point [1] on page
444), then go to the Step H of the Full Configuration Procedure ( on page 470 ), to read
the Local IP address, and the Ethernet interface IP address with its associated IP Mask
and OSPF area.
N.B. In case the .qcml configuration provisioning files are not available, the NE configuration
data will be defined as described in point [2] on page 685
f) the Craft Terminal (Laptop PC running the supervisory software), has already been prepared, as
described in Chapter 41 from page 667

676 / 866 3DB 16142 JAAA Ed.01
g) all the cables and measurement kits described in following Tab. 103. are supposed to be available:
Tab. 103. Test and commissioning instruments

INSTRUMENT QTY CHARACTERISTICS
Craft Terminal 1 See point f ) on page 676
Cat.5e crossconnect Ethernet cable 1 See para.113.13.2 on page 343
PDH Analyzer Pattern Generator 1 See Site Installation Documents
V.11 G.703 Data Analyzer 1 See Site Installation Documents
In alternative, for Ethernet Data channel

functionality tests:
1 PC + 1 Ethernet cable (for ping
function) Optional See Site Installation Documents, and
or para.42.7.7 from page 706
2 PC (for ping function)
or
2 Ethernet Data Analyzer
Multimeter 1 Voltmeter AC and DC Loop tester
Light service kit cable for ODU Rx

1 See para.42.12 on page 720
power monitoring
A compass and a pair of binoculars 1 For antenna pointing
Document Test Result Sheet & Site Acceptance

TRS 1 Test Protocol to be created and filled as described
in chapter 43 on page 721
Before proceeding with lineup and commissioning, ensure that you have the equipment and accessories
required for that purpose. All these materials should be present in the service bag.
42.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage
If not yet done, read whole chapter 12 from page 35 , and point iii on page 4 : they describe the
operations and/or precautions to be observed to safeguard operating personnel during the working
phases, and to guarantee equipment safety. Read them with accuracy before to start every action on the
equipment.

3DB 16142 JAAA Ed.01 677 / 866
42.1.3 Conventions

To simplify the description of actions, the following symbols are in use:

Symbol used Meaning
.
Manual action
z
n Check/Verify
WebEML On WebEML Select
Select a Menu item
Sub Menu item
The commissioning operations described in this document are for a radio link between a Station A and
a Station B.
If the network includes supervision, station A is the one located between the supervisory station and
station B (see figure below). Installation and commissioning begin at station A.
STATION A STATION B
ODU ODU
IDU & IDU &

DDF DDF
Network
(Supervision Side) Network
Fig. 389. Relative positions of stations A and B

678 / 866 3DB 16142 JAAA Ed.01
42.1.4 Summary of the lineup, commissioning, and acceptance phases
The commissioning procedure is summarized as follows:

[1] Phase 1: Turn up and NE data definition

STATION A STATION B
ODU ODU
CT IDU IDU CT
1) On each NE: preliminary operations, turn up, and NE data definition:

a ) Station A, roughly point the antenna towards station B (if not done in the Hardware
Installation procedure)
b ) Commission station A (phase 1)
c ) Commission station B (phase 1)
2) Fine antenna alignment, and preliminary checks on the link Stations A & B:
d ) Station B, fine align the antenna towards station A, and preliminary checks
e ) Station A, fine align the antenna towards station B, and preliminary checks
[2] Phase 2: Site acceptance tests, by the Acceptance Tool
3) Station A, perform all the commissioning checks and tests

Report the results in the Local Station tab panels of the TRS (Acceptance Tool)
STATION A STATION B
ODU ODU
test loops
CT IDU IDU DDF
4) Station B, perform all the commissioning checks and tests

Report the results in the Remote Station tab panels of the TRS (Acceptance Tool)
STATION A STATION B
ODU ODU
test loops
DDF IDU IDU DDF CT
[3] Phase 3: Final acceptance of the link, by the Acceptance Tool
5) Print and save the final TRS report
[4] Phase 4: Final operations
6) Create the NE operator profiles, and save the NE data.

3DB 16142 JAAA Ed.01 679 / 866
42.1.5 General information about test bench drawings

In the test bench drawings depicted in the following paragraphs of this chapter, take always into

account the following considerations:

[1] Actual station configuration
For detailed information on the layout and equipment interconnections (in all 1+0 and 1+1
configurations):
at IDU level, refer to:

para.15.3 from page 101 (IDU configuration types and cabling)
chapter 18 from page 195 (network interconnections)
at ODU level, refer to:

para.21.2.4 from page 372 (ODU and antenna configurations)
Chapter 16 from page 137 (Outdoor Unit installation)
at IDUODU cable level, refer to chapter 17 from page 189 (IDUODU cable installation)
making reference to the equipment interconnection diagram corresponding to your actual

system layout (refer to your own plant documentation for details)
[2] 1+0 and 1+1 configurations
Test bench drawings refer usually to the 1+0 configuration. When necessary, the additional
material for 1+1 configurations is drawn in dotted line.
[3] Equipment interfaces for test access points, signal meaning and use
The standard equipment interfaces for access points are always considered at Station DDF.
Station DDF is not detailed in the drawings: refer to your own plant documentation for details.
In its turn, the Station DDF is connected, by suitable cables, to:
the lineside connectors of the E1 Protection box and of the Service Protection box,
if employed
or, when protection box(es) is (are) not employed, Station DDF is connected directly to the
IDU MAIN unit connectors.
Consequently:
if AlcatelLucent cables are employed for the connection to the Station DDF, refer to point
[9] from page 83 , where such cables are described in detail (carried signals, twisted pair
color, etc.).
Additional information on AlcatelLucent cables can be found in chapter 113 from page
327
otherwise (AlcatelLucent cables not employed), to retrieve information on user signals

and connector pinouts, refer to:
Tab. 46. on page 288 (summary of customeruse signals)
para.112.13 on pages 316 to 326 , where the customeruse signals, and the
relevant equipment connectors, are described in detail.
[4] CT (Craft Terminal) need
The CT (PC with TCO SUITE software) is always required.

680 / 866 3DB 16142 JAAA Ed.01
42.2 Phase 1: Commissioning of STATION A (NE turn up and data definition)
When 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 the 48v DC voltage for the ODU.
Do not connect or disconnect the IF cable between IDU and ODU while the IDU is
powered on.
Perform following operations in this sequence On page
Preliminary operations before IDU power on 682
Power on the IDU unit(s) 683
Craft Terminal switch on, and PC IP setting 683
Check the SWP running in the NEs Flash Card 683
Define the NE data 684
New IP setting of the PC 686

3DB 16142 JAAA Ed.01 681 / 866
42.2.1 Preliminary operations before IDU power on

a) Visual checks

ALL THESE OPERATIONS ARE PERFORMED WITH THE IDU POWERED OFF
n The antenna of station A (or B) is pointed towards station B (or A) the best as possible (use
binoculars and compass if necessary).
n The hardware configuration of the equipment corresponds to that specified in the Site
Installation Documents
n Make visual inspection for units installation, cabling, and grounding:
the IDU unit(s) allocation according to the station layout
the IDU unit(s) ground connections (if necessary)
the DC power supply voltage is present with the correct polarity at the IDU power supply
input
in 1+1 configuration, check the connections between main and extension IDU units
tributaries and service channel access are cabled on the station DDF
the IDUODU cables ground connections
the ODU(s) ground connections
the IDU(s) / ODU(s) cables are connected to IDU(s) and ODU(s)
the ODU(s) cables connectors waterproofing.
b) CT (Craft Terminal) connection to IDU MAIN unit, before IDU power on
Perform the CT connection as depicted in following Fig. 390.

WARNING: do not connect the Craft Terminal to the NE by the RS232 serial cable.
IDU MAIN unit
Cat.5e crossconnect
Ethernet cable
Craft Terminal (switched off)
Fig. 390. CT connection to IDU MAIN unit, before IDU power on

682 / 866 3DB 16142 JAAA Ed.01
42.2.2 Power on the IDU unit(s)
. Switch on the TRU circuit breaker(s), which supply voltage to the IDU Main unit, and to the IDU
Extension unit (if equipped)

. Then, switch on the IDU Main unit, then the IDU Extension unit (if equipped) by their front panel power
supply switch.
n The green ON LEDs on the IDU Main unit (and to the IDU Extension unit, if equipped) turn on.
. Perform a Lamp Test by pressing the LT pushbutton on the IDU Main unit (and on the IDU
Extension unit, if equipped), to verify if the remaining LEDs are operational.
. Wait 2 minutes for system restart execution
42.2.3 Craft Terminal switch on, and PC IP setting
. Switch on the Craft Terminal (CT)
. Configure the IP settings of the network adapter (used for the CTNE connection) of your PC, to be
on the same subnetwork of the NE default IP address (10.0.1.2). Use for example:
IP address : 10.0.1.99
IP Mask : 255.255.255.0
42.2.4 Check the SWP running in the NEs Flash Card
. Startup one NEtO session [ see point a ) on page 500 ]
. Start the supervision of the connected NE, leaving the default IP address (10.0.1.2), as shown in
point c ) on page 502
n When the NE is supervised, the readonly field Version shows the Flash Cards SW COMMIT
VERSION presently running on the NE (see Fig. 250. on page 507 ).
This version must be V2.1.3. If the version:
is V2.1.3:
close the NEtO session (click EXIT)
then proceed with para.42.2.5 below;
is not V2.1.3:
stop this procedure,
perform the Flash Card upgrade to V2.1.3, as described in chapter 59 from page 811
close the NEtO session (click EXIT)
then proceed with para.42.2.5 below.

3DB 16142 JAAA Ed.01 683 / 866
42.2.5 Define the NE data

There are two alternative ways to define the NE data:

loading the .qcml configuration provisioning file in the NE ( as described in point [1] below ),
or by the NEinteractive Provisioning Tool ( as described in point [2] on page 685 )
[1] Load the .qcml configuration provisioning file in the NE
n The .qcml configuration provisioning file, specific for the NE, must be available in the Craft
Terminal. Its data must be consistent with the Site Installation Documents & Technical
Documentation defined in point b ) on page 676
n Be sure you know the new NE routing data, that will be activated after the loading of the .qcml
configuration provisioning file (see Suggestion on page 676 )
. Open the TCO SUITE Main Menu screen, and click the button Alarms & Settings (for details,
see para.33.3 on page 432 )
. The following screen opens, where you must leave the default IP address (10.0.1.2), and the
default Local specification, then click OK
. If required, specify the network adapter [ see point 5 ) on page 437 ]
. The following login screen opens, where you must enter Username = initial, and Password =
initialing (small letters), then click the Apply button
. In the Alarms & Settings Main Menu screen ( Fig. 231. on page 482 ) , click the button
Configuration Setting, which opens the screen of Fig. 233. on page 485 . Browse the
configuration_name.qcml file, then click the button Apply Configuration, and proceed with

684 / 866 3DB 16142 JAAA Ed.01
[2] Define the NE data by NEinteractive Provisioning Tool
n You must know all NE data that must be defined inside the NEinteractive Full Configuration
procedure. They must be consistent with the Site Installation Documents & Technical
Documentation defined in point b ) on page 676
. Open the TCO SUITE Main Menu screen, and click the button Provisioning Tool (for details,
see para.33.3 on page 432 )
. The following screen opens, where you must leave the default choices Connect to NE, IP
address (10.0.1.2), and the Local specification, then click OK
. If required, specify the network adapter [ see point 5 ) on page 437 ]
. The following login screen opens, where you must enter Username = initial, and Password =
initialing (small letters), then click the Apply button
. Define the NE data by the NEinteractive Full Configuration procedure, as described in

para.34.2 from page 448
. At the end of the NEinteractive Full Configuration procedure, click button Apply to the NE, and
proceed with following para.42.2.6

3DB 16142 JAAA Ed.01 685 / 866
42.2.6 New IP setting of the PC

With the NE data definition, performed in previous para.42.2.5 :

the new configuration data are loaded in the NE Flash Card, after which the NE performs an
automatic restart, and the Craft Terminal NE communication is lost:
in particular, the NE network routing data have no longer the default values (10.0.1.2), but the real
ones, as defined by the Customer network planning.
. Therefore, reconfigure the IP settings of the network adapter (used for the CTNE connection) to
allow the PC to access the NE (for details, refer to para.32.2 from page 414 )
42.3 Phase 1: Commissioning of STATION B (NE turn up and data definition)
. To commission the Station B, perform (at Station B premises) the same operations carried on at
Station APhase 1 ( from para.42.2 on page 681 , to para.42.2.6 on page 686 ).
WARNING: in Step H of Full Configuration Procedure on page 470 , be sure to define the Local
IP address of Station B different from that of Station A.
. For near future tests, establish, on the DDF of Station B, hardware loops on every tributary.

686 / 866 3DB 16142 JAAA Ed.01
42.4 Note on NE login
To simplify the description in the following, the NE login by means of the TCO SUITE tools will not be
described in detail as done in the previous parts of this chapter. The following conventions will be used:
. Login the NE by Provisioning Tool: refer to chapter 34 from page 443
. Login the NE by Alarms & Settings: refer to chapter 35 from page 481
. Login the NE by WebEML: refer to chapter 37 from page 511
. Login the NE by Alarms Monitor: refer to chapter 315 from page 605
When Username and Password are required to login the NE, use those of the default Administrator profile:
Username = initial, and Password = initialing (small letters). Note: the default Administrator profile is not
changed by the NE data definition performed in previous para.42.2.5
42.5 Phase 1: Fine antenna alignment, and preliminary checks (stations A &
B)
Perform following operations in this sequence On page

Wait for the possible ODU SW upgrading below
Fine antenna alignment below
Preliminary checks 688
42.5.1 Wait for the possible ODU SW upgrading
After the completion of the configuration steps in both stations, perform following physical operations, at
first on Station A (at Station A premises), then on Station B (at Station B premises):
. Login the NE by Alarms Monitor
n A Software Download on going alarm may appear to indicate that the IDU is upgrading the ODU.
Wait for this alarm to disappear (20 min per ODU), before to proceed with next para.42.5.2
42.5.2 Fine antenna alignment
When Station A and Station B are fully configured and operational, and assuming that the antenna in
station A (or B) has been previously correctly pointed toward the antenna in station B (or A), you should
receive some field from station B (or A).
Now, proceed to a fine tuning of the antenna to improve as much as possible the received level, in both
Station A (at Station A premises) and Station B (at Station B premises).
To perform the fine antenna alignment, refer to Annex A on page 719

3DB 16142 JAAA Ed.01 687 / 866
42.5.3 Preliminary checks

At first on Station A (at Station A premises), then on Station B (at Station B premises), log in the NE by

WebEML and perform following checks by CT:

Check On page
Verify ODU(s) alarm status below
Transmitter power output check 689
Received power measurement 690
42.5.3.1 Verify ODU(s) alarm status
Purpose: Verify no abnormal communication alarm between IDU(s) and ODU(s)
Procedure:
. WebEML Views Equipment
In the left window, select ODU ch#1
n In the lower right window, verify in the alarms list for that there is no internal communication failure
n In the lower right window, verify in the alarms list that there is no TX failure.
z Repeat for Ch#0 if any (1+1)
Fig. 391. ODU(s) alarm status

688 / 866 3DB 16142 JAAA Ed.01
42.5.3.2 Transmitter power output check
Purpose: Verify via WebEML the ODU(s) transmitted power output.

Procedure:
. WebEML Views Radio
From the left window select Channel #1
From the lower right window select RTPC & ATPC tab panel
n Verify that ATPC is Disabled as already set during the quick step procedure
(If required, change the ATPC status to disable in the ATPC field then Apply)
n Verify that Tx Power value complies with the suitable value already set via the Full Configuration
procedure.
(If required, change the Tx Power in the RTPC field then Apply)
Fig. 392. Transmit power check

3DB 16142 JAAA Ed.01 689 / 866
42.5.3.3 Received power measurement

Purpose: Verify via CT the received power to detect any interference

Procedure:
. WebEML Views Radio
From the left window select Channel #1
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. 393. Received power check
Pressing Start will prompt a graphic monitoring view of the transmitted and received levels:

690 / 866 3DB 16142 JAAA Ed.01
Ticking the box show details in the lower left corner will call a summary view of the TX an Rx levels:
Fig. 394. Received power details
n Verify in the hop calculation (plant documentation) that the calculated received level has been
reached.
n Verify that the current Rx local End received level is < 95 dBm (no interferences)
WARNING:
If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the
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.

3DB 16142 JAAA Ed.01 691 / 866
42.6 End of commissioning phase 1 in STATION A

In Station A, proceed to a final fine alignment of the antenna toward the antenna of Station B.

To perform the fine antenna alignment, refer to Annex A on page 719

At this point of the procedure, the local IP address of the Station B must be surely different from
that of Station A, and, if rules explained in para.32.2 from page 414 have been applied, the CT
connected to the Station A should be able to access both Stations A and B (the station B is accessed
through the TMNRF channel)
STATION A STATION B
ODU ODU
CTNE connection by
Cat.5e crossconnect
Ethernet cable
IDU IDU
CT
In Station A, by two different NEtO sessions:
. Login the Station A NE by WebEML and Alarms Monitor
. and Login the Station B NE by WebEML and Alarms Monitor
in order to verify in both the stations:
n No alarm are shown (except unloaded tributaries)
n Received level complies with hop calculation

692 / 866 3DB 16142 JAAA Ed.01
42.7 Phase 2: Commissioning of station A (acceptance test)
Using the NEinteractive Acceptance Tool, all NE configuration data (of both stations A and B), that have
already been defined in the previous phases of the commissioning procedure, are automatically retrieved
from them, and stored in the Report temporary file, which can be saved as .atml file, and printed as pdf
file.
The commissioning phase 2, described in the following, is a site acceptance test procedure made up of
the required tests to ensure that the equipment is fully operational. Also such results, and the additional
information manually introduced in Steps 5 and 6, are stored in the Report temporary file.
The following table sumsup the Steps of the Acceptance Tool:
Step Test or Operation For configuration On page
Start the NEinteractive Acceptance Tool all 694
1 Indoor installation visual inspection check all 695
2 Outdoor installation visual inspection check, and

all 695
Antenna data
3 Channel protection switch all 1+1 695
Radio Protection all 1+1 696
HSB TX Protection 1+1 HSB only 697
Mux/Demux Protection 1+1 with EPS only 698
Loopback Tests on channel 1 all 699
Near End Loopbacks all 700
Far End Tributary Loopback all 702
Point to point BER loop tests on E1 Tributaries on

all 703
Channel 1
Point to point Tributaries quality test all 704
Check of the E1 Alarm Loss of Signal indication all 705
only with 4 x
Point to point BER loop tests on Ethernet Ch. for
Gigabit Ethernet 706
Radio Channel 1
plugin equipped
Rx level (dBm) tests all 710
4 Housekeeping input alarms acquisition all (optional) 710
Housekeeping output alarms acquisition all (optional) 711
Hop Stability Test on Channel 1 all 712
table continues

3DB 16142 JAAA Ed.01 693 / 866
Step Test or Operation For configuration On page

3&4 Channel 0 functionality tests all 1+1 715

Loopback Tests on channel 0 (Step 3) all 1+1 715
Point to point BER loop tests on E1 Tributaries on

all 1+1 716
Channel 0 (Step 3)
only 1+1 with 4 x

Point to point BER loop tests on Ethernet Ch. for Radio
Gigabit Ethernet 716
Channel 0 (Step 3)
plugin equipped
Hop Stability Test on Channel 0 (Step 4) all 1+1 716
5 Equipment identification, and NE software release all 716
6 Acceptance all 716
7 Summary readonly tab panels, and TRS save and

all 717
print
42.7.1 Start the NEinteractive Acceptance Tool
. Start the Acceptance Tool: see para.43.2 on page 725
. Start the the NEinteractive Acceptance Tool: see para.43.3.1 on page 726
. In screen of Fig. 406. on page 728 , click button Create Report: for details refer to para.43.3.3
from page 730
WARNING 1: at this phase of the commissioning procedure, it is assumed that all NE data (of both
stations A and B) have been completely defined, and have not to be modified in the
following.
With the Create Report action performed above, all NE configuration data (of both
stations A and B) are retrieved from them, and stored in the Report temporary file (that can
be printed and saved at any time, as described on page 731 ).
In the following, only commissioning tests are performed, just reporting OK or NOK for their
result, or adding manually some information, and storing the results and the additional
information in the Report temporary file.
Suggestion: after the Create Report action, print the Report (by the button Generate
Report) to acknowledge the configuration data that have been retrieved from both NEs.
Conclusions: in the following, if you change any of such configuration data, you must
restart the NEinteractive Acceptance Tool from the beginning, by a new Create Report
action, to have the modified data stored in the report file.
WARNING 2: remind that all Acceptance Tool screens have two tab panels (with exception of that of
Fig. 413. on page 734 ) Local Station, and Remote Station
During the commissioning of the STATION A, you must use the Local Station tab panels,
as depicted in para.42.1.4 on page 679

694 / 866 3DB 16142 JAAA Ed.01
42.7.2 Step 1: Indoor installation visual inspection check
According to the Step 1 of the Acceptance Tool ( Fig. 408. on page 732 ) perform the listed checks and
set accordingly OK or NOK in the TRS.

42.7.3 Step 2: Outdoor installation visual inspection check, and Antenna data
According to the Step 2 of the Acceptance Tool ( Fig. 409. on page 732 ):
perform the listed checks and set accordingly OK or NOK in the TRS
and report in the TRS the data of employed antenna(s).
42.7.4 Step 3: Channel protection switch (for 1+1 configurations only)
Purpose: check the functionality of the protections switches.
N.B. for the functional description of protections:
at system and hardware levels, refer to:
at WebEML level, refer to chapter 317 from page 635
a) Display the summary block diagram
. WebEML Diagnosis Summary Block Diagram View: for details refer to para.316.4 from
page 629 .
Leave the Summary Block diagram view open for all the duration of the following functionality tests,
in order to visualize at any time the switching status of the system, that is displayed through different
dynamic drawings:
By clicking on a specific object of the drawing, the operator can navigate to the relevant WebEML
menu view.
b) Execute the tests
As shown in Fig. 410. on page 733 , this step consists of various tests, according to the protection
switches employed in the system configuration ( see Fig. 352. on page 635 ):
For all 1+1 configurations:
Radio Protection: Channel 1 (forced) and Channel 0 (lockout), described on page 696
Only in case of 1+1 HSB configuration:
HSB TX Protection: Channel 1 (forced) and Channel 0 (lockout), described on page 697
Only in case of 1+1 with EPS configuration:
Mux/Demux Protection: Channel 1 (forced) and Channel 0 (lockout), described on page 698

3DB 16142 JAAA Ed.01 695 / 866
[1] Radio Protection, Channel 1 (forced)
This test must be always performed in all 1+1 configurations.

Purpose: force the channel 1 to put channel 0 in service

Procedure:
. WebEML Views menu Protection Schemes (example screen in Fig. 354. on page 638 ):
In the left window Radio Protection Main #1
In the lower right window Commands scroll list Forced Apply
n Check in the summary block diagram that the full channel 0 (TX and RX) path is in service.
Report about the Radio Protection, Channel 1 (forced) in the TRS, setting
accordingly OK or NOK (see Fig. 410. on page 733 )
Restore the automatic switch by the same Radio Protection screen:
In the lower right window Commands scroll list None Apply
[2] Radio Protection, Channel 0 (lockout)

This test must be always performed in all 1+1 configurations.
Purpose: lockout the channel 0 to put channel 1 in service
Procedure:
In the same Radio Protection screen of point [1] above:
In the left window Radio Protection Spare #0
In the lower right window Commands scroll list Lockout Apply
Report about the Radio Protection, Channel 0 (lockout) in the TRS, setting
Restore the automatic switch by the same Radio Protection screen:

696 / 866 3DB 16142 JAAA Ed.01
[3] HSB TX Protection, Channel 1 (forced)
This test must be performed only in case of 1+1 HSB configuration.

Procedure:
In the left window HSB Tx Protection Main #1
n Check in the summary block diagram that the TX channel 0 path is in service.
Report about the HSB TX Protection, Channel 1 (forced) in the TRS, setting
Restore the automatic switch by the same HSB Tx Protection screen:
In the left window HSB Tx Protection Main #1
[4] HSB TX Protection, Channel 0 (lockout)

This test must be performed only in case of 1+1 HSB configuration.
Procedure:
In the same HSB Tx Protection screen of point [3] above:
In the left window HSB Tx Protection Spare #0
n Check in the summary block diagram that the TX channel 1 path is in service.
Report about the HSB TX Protection, Channel 0 (lockout) in the TRS, setting
Restore the automatic switch by the same HSB Tx Protection screen:
In the left window HSB Tx Protection Spare #0

3DB 16142 JAAA Ed.01 697 / 866
[5] Mux/Demux Protection, Channel 1 (forced)
This test must be performed only in case of 1+1 with EPS configuration.


Procedure:
In the left window Mux/Demux Protection Main #1
Report about the Mux/Demux Protection, Channel 1 (forced) in the TRS, setting
Restore the automatic switch by the same Mux/Demux Protection screen:
In the left window Mux/Demux Protection Main #1
[6] Mux/Demux Protection, Channel 0 (lockout)

This test must be performed only in case of 1+1 with EPS configuration.
Procedure:
In the same Mux/Demux Protection screen of point [5] above:
In the left window Mux/Demux Protection Spare #0
Report about the Mux/Demux Protection, Channel 0 (lockout) in the TRS, setting
Restore the automatic switch by the same Mux/Demux Protection screen:
In the left window Mux/Demux Protection Spare #0

698 / 866 3DB 16142 JAAA Ed.01
42.7.5 Step 3: Loopback Tests on channel 1
Purpose: Verify via WebEML the loopback functionality

N.B. for the functional description of loopbacks at hardware and WebEML levels, refer to chapter
318 from page 645 . Remind that:
only one loopback can be active at a time: remove previous loopback before proceeding
with the next one
loopbacks are always timed out. Ensure that the timeout is enough to perform the test
a delay of up to 10 seconds may be observed for each activation/deactivation
. WebEML Diagnosis Summary Block Diagram View : for details refer to para.316.4 from
page 629
Leave the summary Block diagram view open for all the duration of these tests, in order to visualize
at any time the Switching and Loopback status of the system:
an active loopback is indicated by a yellow letter: L
switching status is displayed through different dynamic drawings:
menu view.
b) Only for 1+1 configurations
To be sure to work on channel 1:
c) Execute the tests on channel 1
As shown in Fig. 410. on page 733 , this step consists of the following test procedures:
Near End Loopbacks (Tributary, IDU Cable, and ODU Cable), described in point [1] on page
700
Far End Tributary Loopback, described in point [2] on page 702

3DB 16142 JAAA Ed.01 699 / 866
[1] Near End Loopbacks functionality

Purpose: Verify via CT the near end loopback functionality

Required Instruments: E1 Data Analyzer

Test bench: Connect Data analyzer on one Tributary Access (At the Station DDF)
Procedure:
Three different near end Loopbacks have to be performed (one by one):
IDU ODU
A
N
MUX T
TRIB DEMUX MODEM RF E
E1 1 2 3 N
N
A
(1) Near End Tributary Loopback Point
(2) Near End IDU Cable Loopback Point
(3) Near End ODU Cable Loopback Point
Fig. 395. Near End loopbacks points
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.310.2.3 on page 565
for more details about E1 tributaries configuration
Ensure that the local transmitter is not muted (see para.55.10.9 on page 777 for more details
about TX Mute functionality)
1) Near End Tributary Loopback
. WebEML Views menu Loopback (example screen in Fig. 372. on page 653 ):
In the left window Tributaries TX port# NE (select tributary on which the Data Analyzer
is connected)
In the lower right window Activate Apply
n Data analyzer showing no errors
n The Loopback is shown in the summary block diagram view
Report about the Near End Tributary for Channel 1 in the TRS, setting
Remove the loopback (in the lower right window of loopback screen Deactivate Apply)

700 / 866 3DB 16142 JAAA Ed.01
2) Near End IDU Cable Loopback
. WebEML Views menu Loopback:

In the left window Channel #1 IDU Cable
Report about the Near End IDU cable for Channel 1 in the TRS, setting
3) Near End ODU Cable Loopback
In the left window Channel #1 ODU Cable
Report about the Near End ODU cable for Channel 1 in the TRS, setting

3DB 16142 JAAA Ed.01 701 / 866
[2] Far End Tributary Loopback functionality

Purpose: Verify via CT the Far end loopback functionality

Test bench: Connect Data analyzer on one Tributary Access (at the remote Station
DDF)
N.B. One Far end loopback has to be performed under the same condition as the near end
loopbacks. Moreover, ensure that the remote transmitter like the local transmitter is not muted.
IDU ODU ODU IDU

A A
N N
T T MUX
E E RF MODEM DEMUX TRIB
E1 N N
1 E1
N N
A A
Local station Remote station
Fig. 396. Far End Tributary Loopback point
Procedure:
In the left window Tributaries TX port# FE (select the same tributary # that the one which
is locally connected to the data analyzer)
Report about the Far end Tributary for Channel 1 in the TRS, setting accordingly OK
or NOK (see Fig. 410. on page 733 )
[3] Only for 1+1 configurations
a) At the end of all tests on Channel 1, remove the Lockout action by:
. WebEML Views menu Protection Schemes:
b) Execute the same Loopback tests on Channel 0, as described in para.42.7.12 on page 715

702 / 866 3DB 16142 JAAA Ed.01
42.7.6 Step 3: Point to point BER loop tests on E1 Tributaries on Channel 1
Purpose: Verify the point to point E1 Tributaries quality

Verify the E1 tributaries alarm status monitoring functionality

page 629
Leave the summary Block diagram view open for all the duration of Channel 1 functionality tests,
in order to visualize at any time the Switching and Loopback status of the system:
an active loopback is indicated by a yellow letter: L
switching status is displayed through different dynamic drawings:
menu view.

3DB 16142 JAAA Ed.01 703 / 866
c) E1 Tributary functionality test


Test bench: Connect Data analyzer on Tributary Access (at the remote Station DDF),
as shown in Fig. 397. below:
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN IDU EXTENSION
N.B. IDU MAIN
Tributary loopback N.B.

E1
ERROR ANALYZER
PATTERN GENERATOR
N.B. the diagram indicates the loopback (at remote station) and the connection (at local station)
for the first 16 E1 tributaries. To check the other ones, change connections.
Fig. 397. Test bench for tributary functionality check
Procedure: perform the tests specified in following points [1] and [2]
[1] Point to point Tributaries quality test
Assuming that all the tributaries have been enabled (Unframed status) via WebEML in both
stations and that every tributary are looped at the DDF in the remote station:
z Perform one minute of BER test on each E1 tributary
n Verify that the analyzer detects no error
n Verify on WebEML Line Interface view the tributary alarm status:
. WebEML Views menu Line Interface (example in Fig. 398. on page 705 ):
In the lower right Alarms list, verify that while the data analyzer is connected, the
AlarmLossSignal on the relevant tributary is off.
Leave the Line Interface screen open, to perform following check

704 / 866 3DB 16142 JAAA Ed.01
[2] Check of the E1 Alarm Loss of Signal indication
To create an alarmed condition, remove the Tributary loopback at the Remote station,
then, in the lower right Alarms list, verify that while the data analyzer is connected, the
AlarmLossSignal on the relevant tributary goes on.
Restore the Tributary loopback at the Remote station, and verify that the AlarmLossSignal
on the relevant tributary goes off.
Note: Check also the framed tributaries (if required).
Fig. 398. E1 Tributary alarm status monitoring
Report in the TRS (with reference to Channel 1), under the Point to point BER
loop tests, and setting accordingly OK or NOK (see Fig. 410. on page 733 ):
about the E1 Tributaries
and about the E1 Alarm Loss of Signal indication.

b) Execute the E1 Tributary tests on Channel 0, as described in para.42.7.12 on page 715

3DB 16142 JAAA Ed.01 705 / 866
42.7.7 Step 3: Point to point BER loop tests on Ethernet Ch. for Radio Channel 1 (optional)

N.B. these tests must be performed only if the 4 x Gigabit Ethernet plugin is equipped

Purpose: Verify the quality of point to point Ethernet Data Channels
Required Instruments: in alternative:

1 additional PC and 1 Ethernet cable
2 additional PCs
2 Ethernet Data Analyzers
Procedure:
a) Connect CT to IDU of local station
c) Perform the connectivity test on port #1, according to the chosen test bench:
Test bench with 1 additional PC and 1 Ethernet cable: see point [1] on page 707
Test bench with 2 additional PCs: see point [2] on page 708
Test bench with 2 Ethernet Data Analyzers: see point [3] on page 709
N.B. In this case, leaving the test bench as it is, you can also perform the Hop Stability
Test (Step 4), as described in point [2] on page 714
d) Perform the connectivity test on ports #2 , #3 and #4
If required in plant documentation, repeat the connectivity test [ step c ) above] for the other three
ports, with obvious test bench changes on remote station.
Report about the connectivity test of Ethernet Data Channels in the TRS, under Channel
1, and setting accordingly OK or NOK (see Fig. 410. on page 733 )
b) Execute the Ethernet Ch. tests on Channel 0, as described in para.42.7.12 on page 715

706 / 866 3DB 16142 JAAA Ed.01
[1] Test bench with 1 additional PC and 1 Ethernet cable
a) Connections
On local station, connect the additional PC on Main IDU Ethernet port #1 (testing port)
On remote station, through the Ethernet cable, connect the Main IDU OS Ethernet port to the
Main IDU Ethernet port #1 (port to be tested)
b) Set Enable, Flow Control disable, and Capability Advertised for ports to test
. WebEML with reference to screen of Fig. 302. on page 569 , perform following operations
on each data port (#33 to #36, corresponding to Ethernet ports #1 to #4) of both stations:
Enabled Apply
Flow Control unselect Asymmetric Apply
Capability Advertised 1000 Mb/s Full Apply
c) Perform the connectivity test on port #1
1 ) at local station, on PC connected to Ethernet port #1 (N.B.), ping the remote station (using
the NEs Ethernet Configuration IP address) with 50 packets with 1000 byte length.
N.B. the PCs IP address and the NEs Ethernet Configuration IP address must
belong to the same subnetwork.
Windows OS details, if necessary:
Start Programs Accessories Command Prompt
ping <space> l <space> 1000 <space> n <space> 50 <space> IPAddress <enter>
2 ) the RIGHT LED on the corresponding front panel (see Tab. 50. on page 293 ) blinks with
cable inserted and traffic running
At least 45 packets must pass without any packet loss from the 5th packet
Local station
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
IDU EXTENSION
OS
Port
Port #1
(tested)
CT
Port #1
(testing)
Ethernet cable
PC for ping
Fig. 399. Test bench for optional Ethernet Data Channel functionality with 1 additional PC and 1
Ethernet cable

3DB 16142 JAAA Ed.01 707 / 866
[2] Test bench with 2 additional PCs

a) Connections

On local station, connect the additional PC on Main IDU Ethernet port #1 (testing port)

On remote station, connect the additional PC on Main IDU Ethernet port #1 (port to be tested)
Enabled Apply

1 ) at local station, on PC connected to Ethernet port #1, ping the farend PC with 50 packets
with 1000 byte length.
Windows OS details, if necessary:
Start Programs Accessories Command Prompt
ping <space> l <space> 1000 <space> n <space> 50 <space> IPAddress <enter>
Local station
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
IDU EXTENSION
Port #1
(tested)
CT
Port #1
PC for ping (testing)
PC for ping
Fig. 400. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs

708 / 866 3DB 16142 JAAA Ed.01
[3] Test bench with 2 Ethernet Data Analyzers
a) Connections
On local station, connect the Data analyzer on Main IDU Ethernet port #1 (testing port)
On remote station, connect the Data analyzer on Main IDU Ethernet port #1 (port to be tested)
Enabled Apply

1 ) Start this test after the learning of the MAC address
2 ) Configure the pattern A generator, in order to generate 50 packets with 1000 byte length,
and set the data rate half of the radio capacity (i.e.16 Mb/s for ODU 32 Mb/s, or 32 Mb/s
for ODU 64 Mb/s)
Local station
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN
IDU EXTENSION
Port #1
(tested)
ETHERNET DATA CT
Port #1
ANALYZER
(testing)
Pattern B: ETHERNET DATA

Ethernet loop: Destination ANALYZER
Pattern A MAC address and Source
MAC addresses are swapped
Fig. 401. Test bench for optional Ethernet Data Channel functionality with 2 Ethernet Data Analyzers

3DB 16142 JAAA Ed.01 709 / 866
42.7.8 Step 3: Rx level (dBm) tests

Purpose: Compare the read Rx level with that calculated.

Procedure:
as shown in Fig. 410. on page 733 , the actual Rx level (dBm) is retrieved automatically from the
NEs (CH1 for all configurations, and CH0 for the 1+1 configurations)
the operator has to fill manually the calculated Rx level(s) in the suitable fields of the
TRS
the comparison will be printed in the report.
42.7.9 Step 4: Housekeeping input alarms acquisition (optional)
N.B. This test should be performed only if foreseen in the plant documentation (i.e. if requested by
the Customer).
For additional information not given here, refer to chapter 312 on page 587
Purpose: Configure and test via WebEML the housekeeping external alarm inputs
Procedure:
Six alarm inputs are available to monitor either Relay contact or open collector type external alarms.
. WebEML Views External Points (example screen in Fig. 316. on page 588 )
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.112.13.2 on page 317
n Verify in the WebEML External points view that CPI 1 is showing an alarm
z Repeat with CPI 2 to 6
Report about the Housekeeping input alarm acquisition in the TRS, setting accordingly
OK or NOK (see Fig. 411. on page 733 )

710 / 866 3DB 16142 JAAA Ed.01
42.7.10 Step 4: Housekeeping output alarms acquisition
N.B. This test should be performed only if foreseen in the plant documentation (i.e. if requested by
the Customer).
For additional information not given here, refer to chapter 312 on page 587
Purpose: Configure and test the housekeeping equipment alarms outputs
Required Instruments: One Multimeter (loop tester)
Procedure:
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:
. WebEML Views External Points (example screen in Fig. 317. on page 589 )
In the left window OUTPUT CPO 1 to CPI 4
In the lower right window User Label Write a name for the current equipment or
remote control alarm
Polarity Configure if the contact must be closed or
opened when active
To use the relevant Alarm output as a manual remote control:

Criteria Manual Apply
Then, to activate the remote control External State On Apply
To use the relevant Alarm output as an automatic equipment alarm:

Criteria Automatic
Select in the Event scroll list the equipment alarm to be associated
Apply
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.112.13.2 on page
317.
. WebEML Views External points

In the left window OUTPUT CPO 1
In the lower right window Polarity Active Closed.
Criteria Manual Apply
External State On Apply
n Loop tester must detect a loop (close circuit).
In the lower right window External State Off Apply
n Loop tester does not detect anymore loop (open circuit).
z Repeat with CPO 2 to 4.
Report about the Housekeeping output alarm acquisition in the TRS, setting accordingly
OK or NOK (see Fig. 411. on page 733 )

3DB 16142 JAAA Ed.01 711 / 866
42.7.11 Step 4: Hop Stability Test on Channel 1

Purpose: Verify the Hop stability

a) Only for 1+1 configurations
b) This test can be executed in two alternative ways:
by E1 Tributary loop and one E1 Data Analyzer, described in point [1] on page 713
by Ethernet port and two Ethernet Data Analyzers, described in point [2] on page 714
c) In both cases, the Hop stability test must be performed for two consecutive hours, on one Tributary,
in real working condition whatever the protection configuration (1+ 0 or 1+1).
The two hours stability test must be errorfree in normal propagation conditions (out of fading period).

712 / 866 3DB 16142 JAAA Ed.01
[1] Hop Stability Test by E1 Tributary loop and one E1 Data Analyzer
N.B. this test is in alternative to that described in point [2] on page 714 (performed on one
Ethernet tributary)
Required Instruments: one E1 Data Analyzer

Procedure:
Set up the test bench as shown in Fig. 402. below:
z On local station, connect the E1 Data analyzer on E1 tributary #1 (at the Station DDF)
z On remote station, make a hardware loop on the same E1 tributary #1 (at the Station DDF)
ODU
Remote station ODU
ODU
ODU
IDU EXTENSION
IDU MAIN IDU EXTENSION
IDU MAIN
Tributary loopback
E1
ERROR ANALYZER
PATTERN GENERATOR
Fig. 402. Test bench for hop stability test

. WebEML Views menu Line Interface: see Fig. 297. on page 565
z let only one active tributary in both stations (E1 tributary #1), and check that the Tributary Alarm
Loss is not present
page 629
n Verify in both stations that there are no active software loopbacks or switching requests
. Alarms Monitor: for details refer to chapter 315 from page 605
n Verify in both stations that no alarm is present
z Start the test by the E1 Data analyzer, and make it last the time specified in point c ) on page
712
Report about the Hop Stability Test in the TRS, setting accordingly OK or NOK (see
Fig. 411. on page 733 )
N.B. in 1+1 systems, the Hop Stability Test must be performed also on Channel 0, as
described in point [4] on page 716

3DB 16142 JAAA Ed.01 713 / 866
[2] Hop Stability Test by Ethernet port and two Ethernet Data Analyzers

N.B. this test is in alternative to that described in point [1] on page 713 (performed on one E1

tributary)

Required Instruments: 2 Ethernet Data Analyzers
Procedure:
z Set up the test bench with 2 Ethernet Data Analyzers, as shown in Fig. 401. on page 709
On both stations, connect Data analyzer on Main IDU Ethernet port #1.
z Start this test after the learning of the MAC address
z Configure the pattern A generator, in order to generate continuos traffic, and set the data rate
half to the radio capacity (i.e.16 Mb/s for ODU 32 Mb/s, or 32 Mb/s for ODU 64 Mb/s), and with
packet size of 1518 bytes
z Start the test by the 2 Ethernet Data Analyzers, and make it last the time specified in point c )
on page 712
z Compare the number of TX and Rx Frames on the Pattern A: the number of frames must be
equal in normal propagation conditions (out of fading period).
Report about the Hop Stability Test in the TRS, setting accordingly OK or NOK (see
Fig. 411. on page 733 )
N.B. in 1+1 systems, the Hop Stability Test must be performed also on Channel 0, as
described in point [4] on page 716
a) At the end of the Hop Stability Test on Channel 1, remove the Lockout action by:
b) Execute the Hop Stability Test on Channel 0, as described in para.42.7.12 on page 715

714 / 866 3DB 16142 JAAA Ed.01
42.7.12 Channel 0 functionality tests (1+1 only)
These tests must be performed only in 1+1 configurations.

Purpose: check the Spare channel 0 functionality, with some tests, already done on channel 1
. WebEML Diagnosis Summary Block Diagram View: for details refer to para.316.4 from
page 629 .
Leave the Summary Block diagram view open for all the duration of the following functionality tests,
in order to visualize at any time the switching status of the system, that is displayed through different
dynamic drawings:
menu view.
b) Force to channel 0
c) Execute the tests on channel 0
[1] Step 3: Loopback Tests on channel 0
Repeat the same tests already performed for channel 1, making reference to para.42.7.5 from
page 699 , taking into account that, when:
In the left window Channel #1 XXX is specified in the procedure,
in this case you must set instead:
In the left window Channel #0 XXX
With reference to Fig. 410. on page 733 , report for Channel 0 in the TRS, setting
accordingly OK or NOK:
about the Near End Tributary
about the Near End IDU cable
about the Near End ODU cable
about the Far end Tributary

3DB 16142 JAAA Ed.01 715 / 866
[2] Step 3: Point to point BER loop tests on E1 Tributaries on Channel 0


page 703 , but only for one E1 tributary.

With reference to Fig. 410. on page 733 , report for Channel 0 in the TRS, setting
accordingly OK or NOK:
about the E1 Tributary (one only)
and about the E1 Alarm Loss of Signal indication.

[3] Step 3: Point to point BER loop tests on Ethernet Ch. for Radio Channel 0 (optional)
page 706
Report about the connectivity test of Ethernet Data Channels in the TRS, under
Channel 0, and setting accordingly OK or NOK (see Fig. 410. on page 733 )
[4] Step 4: Hop Stability Test on Channel 0
Repeat the same tests already performed for channel 1, making reference to para.42.7.11
from page 712
Report about the Hop Stability Test in the TRS, setting accordingly OK or NOK
(confirming or not what already reported for Channel 1); see Fig. 411. on page 733
At the end of all tests on Channel 0, remove the Forced action by:
42.7.13 Step 5: Equipment identification, and NE software release
As shown in Fig. 412. on page 734 , this step allows to write manually:
the Product Code and the Serial Number of the equipment items
the NE Software Release Standby version: to retrieve this piece of information, refer to para.59.2
on page 813
N.B. the content of the NE Software Release Active version field is retrieved automatically.
42.7.14 Step 6: Acceptance
This screen ( Fig. 413. on page 734 ) must be filled in during the Final acceptance of the link (last phase
3), as described in para.42.9 on page 718

716 / 866 3DB 16142 JAAA Ed.01
42.7.15 Step 7: Summary readonly tab panels, and TRS save and print
As shown in Fig. 414. on page 735 , this is the last step of the Acceptance Tool procedure:
a) by means of scrollable and readonly tab panels, it shows the results of tests made on STATION A,
as well as the data automatically retrieved from the local and remote NEs
b) you must click on button Save , to save the TRS report in an .atml file, and carry this file to the
STATION B premises, to use it for the execution of the STATION B commissioning, as described in
para.42.8 below
c) if you like, click on button Generate Report, to print the TRS report (which, at this phase, contains
only the results of STATION A commissioning tests) in pdf format: for details, refer to point f ) on
page 731
42.8 Phase 2: Commissioning of station B (acceptance test)
[1] Start the NEinteractive Acceptance Tool
. Start the the not NEinteractive Acceptance Tool: see para.43.4 on page 736 , and:
. Select V2.1.3
. then, click button Modify Report, and load the .atml file that you have saved in step b )
of para.42.7.15 above (i.e., at end of STATION A commissioning phase)
[2] Perform the commissioning of Station B
Repeat in Station B all the tests performed in Station A, making reference to the tests described:
from para.42.7.2 on page 695 (Step 1: Indoor installation visual inspection check)
to para.42.7.13 on page 716 (Step 5: Equipment identification, and NE software release)
but with the exception of the Hop Stability Test, that has to be run only one time for the full hop.
WARNING: remind that all Acceptance Tool screens have two tab panels (with exception of that
of Fig. 413. on page 734 ) Local Station, and Remote Station
During the commissioning of the STATION B, you must use the Remote Station tab
panels, as depicted in para.42.1.4 on page 679
[3] Step 7: Summary readonly tab panels and TRS save and print
As shown in Fig. 414. on page 735 , this is the last step of the Acceptance Tool procedure:
a) by means of scrollable and readonly tab panels, it shows the results of tests made on STATION
A and STATION B, as well as the data automatically retrieved from the local and remote NEs
b) you must click on button Save , to save the TRS report in an .atml file, and take this file to
perform the Final acceptance of the link, as described in para.42.9 on page 718
c) if you like, click on button Generate Report, to print the TRS report (which, at this phase,
contains the results of both STATION A and STATION B commissioning tests) in pdf format:
for details, refer to point f ) on page 731

3DB 16142 JAAA Ed.01 717 / 866
42.9 Phase 3: Final acceptance of the link

[1] Go to Step 6 of the Acceptance Tool

If the NEinteractive Acceptance Tool is still open in the STATION B commissioning phase, go
to Step 6 (Acceptance) by means of the <Prev and Next> buttons
if you have closed it:
. Start the the not NEinteractive Acceptance Tool: see para.43.4 on page 736 , and:
. Select V2.1.3
. then, click button Modify Report, and load the .atml file that you have saved in step
[3]b ) of para.42.8 on page 717 (i.e., at end of STATION B commissioning phase)
. go to Step 6 (Acceptance) by means of the <Prev and Next> buttons
[2] Fill Step 6 (Acceptance)
Fig. 413. on page 734 is self explaining: fill it according to the tests results and the contract.
[3] Print and save the final TRS report
Go to last Step 7 [ see point f ) on page 731 ], and:
a) Click on button Generate Report, to print the final TRS report in pdf format
b) Click on button Save , to save the TRS report in an .atml file.

Store it conveniently, for possible future use.
END OF COMMISSIONING ACCEPTANCE TEST
42.10 Phase 4: Final operations
As introduced in para.11.2 on page 26, complete the commissioning of each NE, creating the NE
operator profiles and saving its data.

718 / 866 3DB 16142 JAAA Ed.01
42.11 Annex A: fine antenna alignment
Safety requirements for workers on antenna pole, and microwave radiations (EMF norms)
SAFETY RULES
When operating on the antenna pole, strictly follow cautions stated in
para.12.3.3 from page 38 , and in para.12.3.7 on page 43 . 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. 1. on page 44
Antenna prepointing should have been done during equipment hardware installation described in
This annex explains how to carry out the antenna fine alignment.
To monitor the received level during alignment in the local station:
use the Light service kit cable for ODU Rx power monitoring in addition to a voltmeter, as
described here below
or, after having logged in the NE, use the Craft Terminal received power measurement facility
described in para.42.5.3.3 on page 690
Alignment procedure using the light service kit cable
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
d) proceed with Vertical alignment, then with Horizontal alignment, as described in para.16.10.1
on page 185 (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.

3DB 16142 JAAA Ed.01 719 / 866
42.12 Annex B: light service kit cable operative information

Fig. 403. herebelow shows this optional cable (P/N 3CC13477AA**):

E
A B
F G
1 1
3
2
3
Black
4 4
5 5
A 6 6 B
7 7 D
8
9
8
9
C
10 10 Red
11 11
12 12
1
E
C D
6 7 7 6
12 12 11
11 5
5 8 8
4 1 4
9 1
10 9 10
3 2 3
2
View following F View following G
LEMO wire 6 = ground

Fig. 403. Light service kit cable
Connector usage:
(A) LEMO connector, to be plugged into LEMO connector on ODU (see Fig. 49. on page 143 and
Fig. 50. on page 144)
(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.311.6 on page 581).
(E) RS232 connector, for AlcatelLucent internal use only.

720 / 866 3DB 16142 JAAA Ed.01
43 USE OF THE ACCEPTANCE TOOL TO WRITE THE TRS
This chapter describes in detail the functions of the Main Menus Acceptance Tool, to write the TRS
document during the commissioning (acceptance phase) of the two NEs making up the radio link:
Subject On page
Acceptance Tool scope 721
Acceptance Tool start 725
Acceptance Tool in NEinteractive modality 726
Bench setup and startup of the NEinteractive Acceptance Tool 726
Main functions of the NEinteractive Acceptance Tool 728
Create Report 730
Acceptance Tool in not NEinteractive modality (offline) 736
43.1 Acceptance Tool scope
The radio link lineup, commissioning, and acceptance phases are summarized in para.42.1.4 on page
679 : the Acceptance Tool is used in the phase 2 (Site acceptance tests) to create the TRS document
(Test Report Sheets & Site Acceptance report), and allows to:
retrieve automatically most of the system information from the equipment (local and remote stations),
as listed in Tab. 104. from page 722 ,
introduce manually the remaining system information (not retrieved automatically), test results and
comments through dedicated screens on the PC:
indoor system installation & cabling visual inspection,
outdoor system installation & cabling visual inspection,
test results,
module identification (P/N & S/N IDU(s), P/N & S/N Flash card, P/N & S/N 1+1 coupler, P/N &
S/N of antenna(s), P/N & S/N ODU(s), P/N & S/N of Plugin card (s), NE SWP standby ),
create a file containing all data (extension .atml), that can be open at a second time and modified
as needed,
generate a final TRS document in Adobe Acrobatt .pdf format, following predefined output
templates.
N.B. the TRS document can be customized with the Customers own logo, as described on
page 729

3DB 16142 JAAA Ed.01 721 / 866
Tab. 104. Parameters retrieved from the equipment

Link Configuration

1 User Label
2 Site Location
3 NE time
4 NE Type
5 Protection type
6 Capacity
7 Modulation
8 Impedance
9 TX Frequency Ch1
10 TX Frequency Ch0
11 RX Frequency Ch1
12 RX Frequency Ch0
13 User Service Channel availability
14 Phone Number
15 Link Identity Code
16 Expected identifier
17 Sent identifier
18 NTP
Radio Power Settings
20 Tx Power Ch1
21 Tx Power Ch0
22 ATPC Ch0
23 ATPC Range PTx Min Ch0
24 ATPC Range PTx Max Ch0
25 ATPC Rx Threshold Low Power Ch0
26 ATPC Ch1
27 ATPC Range PTx Min Ch1
28 ATPC Range PTx Max Ch1
29 ATPC Rx Threshold Low Power Ch1
Automatic Restoration Criteria
30 MUX/DEMUX Protection
31 Radio Protection
32 HSB Tx Protection
Radio Power Measurements
33 Rx Power Ch1
34 Rx Power Ch0
Modules identification
722 / 866 3DB 16142 JAAA Ed.01
39 Plugin types
Network Configuration
42 Local NE IP address
OSPF Areas Configuration
43 Area ID
44 OSPF Area address
45 Stub Area
OS Ethernet Configuration
46 Ethernet OS
47 Ethernet IP
48 Routing protocol
49 IP mask
50 OSPF Area ID
NMS Point to Point Interface Configuration
51 TMN RF
52 TMN RF Remote address
53 TMN RF routing IP protocol
54 TMN RF Associated OSPF Area
55 TMN V.11
56 TMN V.11 Remote address
57 TMN V.11 mode
58 TMN V11 routing IP protocol
59 TMN V.11 Associated OSPF Area
60 TMN G.703
61 TMN G.703 Remote address
62 TMN G.703 mode
63 TMN G703 routing IP protocol
64 TMN G.703 Associated OSPF Area
IP static routing configuration
65 Host or Network
66 IP address
67 IP mask
68 Gateway Address
69 PPP Id
SW version
70 NE SWP active

3DB 16142 JAAA Ed.01 723 / 866

Housekeepings

Input Housekeepings
72 CPI#1 Polarity
73 CPI#1 User label
74 CPI#2 Polarity
75 CPI#2 User label
76 CPI#3 Polarity
77 CPI#3 User label
78 CPI#4 Polarity
79 CPI#4 User label
80 CPI#5 Polarity
81 CPI#5 User label
82 CPI#6 Polarity
83 CPI#6 User label
Output Housekeeping
84 CPO#1 Polarity
85 CPO#1 User label
86 CPO#1 Criteria
87 CPO#1 Associated Event
88 CPO#2 Polarity
89 CPO#2 User label
90 CPO#2 Criteria
92 CPO#3 Polarity
93 CPO#3 User label
94 CPO#3 Criteria
96 CPO#4 Polarity
97 CPO#4 User label
98 CPO#4 Criteria
100 CPO#5 Polarity
101 CPO#5 User label
102 CPO#5 Criteria
104 CPO#6 Polarity
106 CPO#6 Criteria
724 / 866 3DB 16142 JAAA Ed.01

108 CPO#7 Polarity

110 CPO#7 Criteria
Alarms
112 List of active alarms (sorted by Severity) station A
43.2 Acceptance Tool start
N.B. Besides from the Local Copy of the TCO Suite, the Acceptance Tool can be run also directly
from the TCO SUITE CDROM
This function can be run in two ways:
NEinteractive, para.43.3 on page 726
or not NEinteractive (offline), para.43.4 on page 736

3DB 16142 JAAA Ed.01 725 / 866
43.3 Acceptance Tool in NEinteractive modality

43.3.1 Bench setup and startup of the NEinteractive Acceptance Tool

With reference to Fig. 404. below, to use this function:
you must know the Ethernet Configuration IP address of the Local station, and the Local IP
address of the Remote station. Refer to para.32.2.2 on page 414 for details.
for each of the two NEs that must be loggedin, you must have an UserName and Password set. The
allowed Login profile can be only Administrator or CraftPerson. Refer to point [1] on page 420
for details.
WARNING: this function must not be launched if the PCNE connection is done through the F
interface, and must not be launched if the PCNE connection is trough the IP network.
As shown in Fig. 404. below:
setup the bench,
through the ping function, check that both NEs are reachable by the PC (using the addresses stated
above),
start the Acceptance Tool from the Main Menu screen (see para.43.2 on page 725 ),
fill the Local and Remote fields, then click OK.
9400AWY RADIO LINK

CT REMOTE STATION
LOCAL STATION
ODU
ODU
crossconnect
Ethernet cable
Eth IDU IDU
Local = Ethernet Configuration IP address Remote = Local IP address
Fig. 404. Bench setup and startup of NEinteractive Acceptance Tool

726 / 866 3DB 16142 JAAA Ed.01
If both NEs are reachable by the PC, the NE login screen opens, where user is asked to provide his/her
UserName and Password (for details, see point [1] on page 420 ):
Fig. 405. Authentication request for NE login
N.B. two NE login screens must be filled, one for each of the two NEs.

3DB 16142 JAAA Ed.01 727 / 866
43.3.2 Main functions of the NEinteractive Acceptance Tool

If the double NE login of Fig. 405. on page 727 is successful, the following screen opens:

Fig. 406. Main functions of the NEinteractive Acceptance Tool
The following functions are available:
a) Modify Report allows to open an .atml file saved previously [see point f ) on page 731 ]. If you
click this button, a suitable screen will ask you to browse and open the file. After having opened the
file the following screen opens:
Clicking the button Next> in this screen, the first step of the Acceptance Tools Create Report
function opens (see Fig. 408. on page 732 ). Now, you can navigate the report steps to introduce
the changes you like.

728 / 866 3DB 16142 JAAA Ed.01
b) Create Blank Report allows to create a blank .pdf file.
A blank report can be useful for Customers who prefer to fill the information on the printed papers
by hand.
If you click this button:
at first, you are asked to choose a template (N.B):
Fig. 407. Choose report template
then, a suitable screen will ask you to give a name to the file, and to specify where to save it.
N.B. The User can create a customized template folder under <TCOR1.7 installation
folder>/Template directory, in this way:
1) Copy the folder AlcatelLucent default template and paste it (in the same
Template directory, giving it the name you like (e.g. MyTemplate)
2) Open your own new template folder (i.e. following example above: MyTemplate);
you will find the file logo.jpeg: delete it
3) Create your own logo, that can be any .png, .gif, .jpeg, .jpg format, and put it in your
own new template folder with the name logo.xxx (xxx according to format)
4) From now, your own template can be selected in the screen of Fig. 407. above.
Your own logo is automatically converted into size 110*30, and generated in the TRS
report.
c) Create Report allows to create the real NEinteractive report, as detailed in para.43.3.3 on page
730

3DB 16142 JAAA Ed.01 729 / 866
43.3.3 Create Report

Clicking Create Report in the screen of Fig. 406. on page 728 , causes the following operations:

At the end, clicking Next starts the creation of the report.
Some usage notes are added:
a) the report is organized in steps. These steps are described in para.43.3.4 from page 731
b) you can move forward and backward in such steps, by means of the <Prev and Next> buttons:
c) each step has two tabbed panels, one for the Local station, the other for the Remote one:
d) the result of each test must be reported as a simple choice between OK or NOK (OK is the default)

730 / 866 3DB 16142 JAAA Ed.01
e) at any time, you can suspend the report writing, and restart it at a second time, without loosing the
job made before the suspension, in the following way:
clicking repeatedly on Next button, reach the last step [ see point f ) below ], and click the button
Save , to save the report in an .atml file (containing data reported so far)
when you want to resume the job, start again from para.43.3.1 on page 726 , and, in screen
of Fig. 406. on page 728 , click the button Modify Report to reload the .atml file previously
saved.
f) in the last step:
you can click:
Prev , to move to the previous step
Save , to save the report in an .atml file. If you click this button, a suitable screen will ask you
to give a name to the file, and to specify where to save it.
N.B. this Save execution is always strongly suggested.
Generate Report , to save the report in a .pdf file. If you click this button:
at first, you are asked to choose a template (see Fig. 407. on page 729 )
then, a suitable screen will ask you to give a name to the file, and to specify where to save
it.
Cancel , to loose all changes (if Save has not been made), and restart from the screen of
43.3.4 Steps of the Acceptance Tools Create Report
The steps of this procedure, depicted in following figures Fig. 408. to Fig. 413. , must be filled according
to the instructions given in the acceptance test phase of the commissioning procedure (para.42.7 from
page 693 ).
N.B. Following figures Fig. 408. to Fig. 413. are relevant to the 1+1 configurations; in the 1+0
configurations, the screens do not show the information associated to the channel 0, as well as
to the protections.

3DB 16142 JAAA Ed.01 731 / 866
Fig. 408. Step 1 of the Acceptance Tool: Indoor installation visual inspection check
Fig. 409. Step 2 of the Acceptance Tool: Outdoor installation visual inspection check, and Antenna

732 / 866 3DB 16142 JAAA Ed.01
Fig. 410. Step 3 of the Acceptance Tool: Channel protection switch, Loopback tests, Point to point
BER loop tests, and Rx level tests
Fig. 411. Step 4 of the Acceptance Tool: Housekeeping input & output alarm acquisition, and Hop
stability test

3DB 16142 JAAA Ed.01 733 / 866
Fig. 412. Step 5 of the Acceptance Tool: Equipment identification, and NE software release
Fig. 413. Step 6 of the Acceptance Tool: Acceptance

734 / 866 3DB 16142 JAAA Ed.01
The last step 7 of this procedure, by means of scrollable and readonly tab panels (two examples in
Fig. 414. below), shows the results of tests, as well as the data automatically retrieved from the local and
remote NEs.
For the use of the buttons at the screen bottom, refer to point f ) on page 731
Fig. 414. Step 7 of the Acceptance Tool: summary readonly tab panels and interactive buttons

3DB 16142 JAAA Ed.01 735 / 866
43.4 Acceptance Tool in not NEinteractive modality (offline)

Start the Acceptance Tool from the Main Menu screen (see para.43.2 on page 725 ),

select Do not connect to NE (offline), then click OK
after clicking the OK button, the following prompt screen appears, where you must choose the
9400AWY system type Version V2.1.3, and then click OK:
after choice and OK, the following screen opens:
The following functions are available:
Modify Report operates as described in point a ) on page 728
Create Blank Report operates as described in point b ) on page 729
a) END OF SECTION

736 / 866 3DB 16142 JAAA Ed.01
SECTION 5: MAINTENANCE AND UPGRADE
This section contains the whole logical and operative information for the equipment maintenance and
system SW and HW upgrade.
N.B. For the information concerning the SWP TCO Suite, please read carefully the point v Notes
on used TCO Suite and associated User Manual on page 5

MAINTENANCE
Chapter 51 Maintenance Policy
739
It introduces the basic concepts for the equipment maintenance.
Chapter 52 Set and use of EOW functions
It explains how to configure and use the Engineering OrderWire functions of the 743
equipment.
Chapter 53 Maintenance Tools and Spare Parts
It describes the instruments, accessories and the equipment spare parts that are 745
envisaged to carry out the routine and corrective maintenance of the equipment.
Chapter 54 First Level Maintenance
751
It describes the First Level Maintenance (system state display) of the equipment.
Chapter 55 Second Level Maintenance
755
It describes the preventive and corrective maintenance of the equipment.
Chapter 56 Spare Flash Card management, and replacement procedure
It describes how to manage the spare Flash Card and how to replace it, in case of 793
problems.
UPGRADE
Chapter 57 System hardware upgrade
It details all phases necessary to install tributary plugins, or to upgrade 9400AWY 797
system from (1+0) to (1+1) configuration.
Chapter 58 Procedure to change capacity/modulation/frequency
This dedicated procedure must be followed in order to avoid adjacent channel 809
traffic impact
Chapter 59 NE upgrade to V2.1.3 from previous version V2.1.x
It describes how to upgrade to the SWP 9400AWY V2.1.3 any 9400AWY Rel.2.1 811
NE, presently running with a previous SWP V2.1.3.

MAINTENANCE AND UPGRADE
3DB 16142 JAAA Ed.01 737 / 866
738 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
51 MAINTENANCE POLICY
This chapter introduces the basic concepts for the equipment maintenance.
Subject On page
Classification of maintenance levels and operators 740
First Level Maintenance Personnel skill 741
Second Level Maintenance Personnel skill 741
Troubleshooting organization 741

3DB 16142 JAAA Ed.01 739 / 866
51.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 53 on page 745.
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 54 on page 751.
Second Level Maintenance Operator is authorized to make all actions necessary to repair
the system; moreover he should only be authorized to perform routine maintenance.
These actions are described in chapter 55 on page 755.
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 52 on page 743.

740 / 866 3DB 16142 JAAA Ed.01
51.2 First Level Maintenance Personnel skill
First Level Maintenance Personnel must have received:

an adequate technical background on telecommunications. Experience in first level maintenance

activities is a must;
an adequate presentation on the equipment this handbook refers to;
detailed instructions on what to do and/or who must be contacted in the case should he find the
equipment not in its normal conditions.
51.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 point iv
on pag e 5 is usually not enough to properly maintain equipment.
51.4 Troubleshooting organization
[1] The troubleshooting procedure is performed 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.)
[2] The following interfaces are present on the equipment for troubleshooting purposes:
Ethernet interface for:

the Telecommunication Management Network ( TMN )
the Craft Terminal (Local or Remote)
the TCO Suite NEinteractive functionalities
F interface for the Craft Terminal (Local or Remote)
LEDs located on the NEs units.

3DB 16142 JAAA Ed.01 741 / 866
[3] Usually, maintenance is firstly done via software (TMN, or Alarms Monitor, or Local/Remote WebEML
or the NE webserver functionalities) to locate the faulty equipment and the faulty unit or the faulty

path and then on site to physically correct the trouble.

Maintenance can be done:

from a TMN network management center.
By means of the TMN, the maintenance technician can see the alarms generated by each
equipment of the managed network (see the relevant TMN handbooks).
from a Remote Craft Terminal (RCT) management center.

The operator, connected to a local NE, can remotely manage and troubleshoot a network
composed of max 128 NEs, including itself. This handbook applies to this function.
on site.
The operator is on site in case:
a) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT)

b) the equipment is not reachable by the remote manager (TMN or RCT) and therefore is
isolated
c) link problems are present
d) the trouble has been located and a physical replacement is necessary.
In cases a ) , b ) , and c ) , the alarmed equipment is checked by means of the local Craft
Terminal.
[4] The NE is provided with LEDs which indicate Centralized Equipment Alarms.
All alarms detected on the units are collected by the IDU MAIN unit, which delivers centralized
indications (by means of LEDs on the front coverplate). Specifically:
Red LED: detection of a MAJOR (URGENT) alarm.

Red LED: detection of a MINOR (NOT URGENT) alarm.
Yellow LED: alarm condition ATTENDED.
Red LED: detection of a LDI (problem in the local equipment).
Red LED: detection of an RDI (problem in the remote equipment).
In the case of a MAJOR or MINOR alarm, after locating the alarmed unit, the alarm condition can
be attended by pressing the alarm storing push button on the front panel of the IDU MAIN unit.
This condition causes on the front coverplate:
yellow LED ATTENDED to light up
red LEDs MINOR and MAJOR to turn off (free to accept other alarms)
If both LEDs are on, the Attend command should be given twice : one to attend the MINOR
alarm and one to attend the MAJOR alarm.
[5] The troubleshooting operation is done by means of the Craft Terminal, and of the optical indicators
(LEDs) present on the NE.
The Craft Terminal is connected to the relative connector (F or Ethernet interface) on the front
coverplate of the IDU MAIN unit.
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault
location and subsequent removal as indicated in para. 55.8 on page 762.
To correctly execute the troubleshooting operations the technician must know the
equipment configuration (see Equipment applications on the Craft Terminal).

742 / 866 3DB 16142 JAAA Ed.01
52 USE OF EOW FUNCTIONS
Please refer to chapter 51 on page 739 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.
52.1 Setting information
The telephone handset allows to carry out EOW in/out calls at IDU side. It uses DTMF (tone) dialling.
In case of radio link, the EOW functions are possible only if both the IDU MAIN units (of stations A and
B) are equipped with the AUDIO + USER SERVICE CHANNEL plugin.
In case of TMN rings and chains, the EOW functions between two NEs (not belonging to a radio link) are
possible only if there is EOW audio continuity between them ( for details, refer to para.18.3 from page
208 ), and only if both their IDU MAIN units are equipped with the AUDIO + USER SERVICE CHANNEL
plugin.
a) Connection diagram
STATION A STATION B
ODU ODU
1 2 3 3 1 2
4
7
5
8
6
9
IDU IDU 6
9
4
7
5
8
0 # # 0
* *
OFF ON MAIN UNIT MAIN UNIT OFF ON
Telephone handset Telephone handset
N.B. each Telephone handset has its own phone number. Phone number can be in the 10 to
99 range. Telephone handsets must have different phone numbers.
Physical connection on IDU: connect Telephone handsets RJ11 plug to TPH connector on the IDU
MAIN unit [ (7) in Fig. 143. on page 289 ].
b) Telephone handset view
Caution: to operate, set the handset switch to FV.
Set switch to FV
ON/OFF switch
RJ 11 connector
c) Telephone handset keyboard
KEY MEANING
* Force unlocking of the line
# Engage line

3DB 16142 JAAA Ed.01 743 / 866
d) Telephone handset phone number display/setting
Display/setting is done:

by Full Configuration Procedure (see Step M on page 478 )


or by WebEML with the following menus (refer to para.38.4.3 on page 556 for details):
display: Configuration System Settings Overhead Phone Parameter
setting: Configuration System Settings Overhead Phone Parameter phone
number Apply
e) Ways of Calling : two different ways of calling are possible:

SELECTIVE: a connection between two users (dial a number: 10 to 99)
OMNIBUS: a unidirectional connection with all the users (dial digits 00)
f) LEDs indication:
EOW (GREEN): free line
EOW (YELLOW): busy line
Flashing YELLOW: received and recognized call
N.B. position of green/yellow LED on IDU MAIN unit:
EOW
GREEN
GREEN RED RED
YELLOW
GREEN RED RED YELLOW
52.2 Call Setup/End by Telephone handset connected to the IDU Main unit
a) To Call from Handset:
1) Check that line is free (EOWfree green LED on the MAIN unit is on)
2) Set Handset ON/OFF switch to ON
3) On keypad, press # to engage line
4) Check that EOWbusy yellow LED on the MAIN unit is on
5) On keypad, dial twodigit number of station to be called (or 00 for omnibus call)
6) Ring tone is audible in the handset, wait for answer
b) To Answer Call at Handset:
1) EOWbusy yellow LED on the MAIN unit flashes and audible tone is present
2) If not connected, connect handset to IDU, set ON/OFF switch to ON, press # on keypad, speak
c) To End Call from Handset:
1) On keypad, press *
2) Move handset ON/OFF switch to OFF

744 / 866 3DB 16142 JAAA Ed.01
53 MAINTENANCE TOOLS AND SPARE PARTS
53.1 Introduction
maintenance.
This chapter describes the instruments, accessories and the equipment spare parts that are envisaged
to perform the routine and corrective maintenance of the equipment.
Subject On page
Instruments and accessories below
Software tools below
Maintenance, Installation and Station Tool Kits 746
Set of spare parts 748
Types of Spare Parts 748
Number of Spare Parts 749
General rules on spare parts management 749
53.2 Instruments and accessories
53.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 3 from page 401 , while its use for
troubleshooting is summedup in para.55.8 on page 762
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.32.1 from page 410 for an overview on the physical interfaces for the NE
management.

3DB 16142 JAAA Ed.01 745 / 866
53.2.2 Maintenance, Installation and Station Tool Kits

The following Tool Kits are optionally available from AlcatelLucent:

a) The Installation Tool Kit (P/N 3DB01397AA**) includes various types of common usage fixed
spanners, standard and crosshead screwdrivers, polygon spanners, polygon tube spanners, special
fixed spanners, etc.
b) The Maintenance Tool Kit (P/N 3DB01398AA**) is practically equal to the Station Tool Kit, with
the addition of the Antistatic wristband.
c) The Station Tool Kit (P/N 3DB01399AA**) is a bag additionally containing various types of cables
and cable adapters.
The detailed item lists of these Tool Kits can be obtained asking them to your AlcatelLucent local dealer.
N.B. 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. 105. below, which gives also reference to figures where they are
depicted.
Tab. 105. Special items of the Tool Kits

SPECIAL ITEM DESCRIPTION
COMPONENTS OF ANTISTATIC WRISTBAND
Antistatic wristband
Antistatic applications cord
Fig. 1. on page 4
Plug with crocodile pliers
Female button termination
SPECIAL EXTRACTORS
Unhook tool for 1.0/2.3 coax Fig. 415. below
SPECIAL TOOLS AND ITEMS FOR ODU
Lever for ODU mounting/dismounting Fig. 416. on page 747
Fig. 415. Special extractor to remove the coaxial cables 1.0/2.3

746 / 866 3DB 16142 JAAA Ed.01
When, in ODU configurations 1+1 with coupler, you must dismount and then mount one of the
two ODUs for maintenance purposes, the following operations:

UNBLOCK BEFORE DISMOUNT

One at a time, unblock the four ODU blocking levers (A) pushing up the restraint spring
(B) and, contemporarily, turning down the lever (C).
BLOCK AFTER MOUNT
Block the four ODU blocking levers (A)
may produce vibrations that could cause synch loss or other electrical disturbances to the other
ODU still working.
A B
Using the special lever:
allows to do the same unblock/block operations without producing vibrations.

The following photographs should clarify the correct lever handling and usage.
Fig. 416. Lever for ODU mounting/dismounting

3DB 16142 JAAA Ed.01 747 / 866
53.3 Set of spare parts

53.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).
53.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. 111.2.2 on page 263.
for ODUs with external diplexer: the TRANSCEIVER assembly. For the P/Ns refer to:
Tab. 19. on page 260 (7 GHz)
Tab. 21. on page 262 (8 GHz)
As a matter of fact, all other ODUrelated items listed in Chapter 111 on page 249 can be considered
items to be provisioned as spare parts.
53.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 Chapter 110 on page 243 ) 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.21.4 on page 388.
N.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.
b) Spare parts for Flash Card
There are various possible types of Flash Cards. For details refer to para.31.1.1 on page 404
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 Licence String 64Mb 16 QAM could be provisioned instead.
N.B. Read important information regarding the spare Flash Card management in para.56.1
on page 793.

748 / 866 3DB 16142 JAAA Ed.01
53.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.
53.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.

3DB 16142 JAAA Ed.01 749 / 866
750 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
54 FIRST LEVEL MAINTENANCE
maintenance.
This chapter describes the First Level Maintenance of the equipment.
Subject On page
System state display by visual indications
LED test
below
Alarm LEDs on the IDU MAIN unit
Alarm LEDs on the IDU EXTENSION unit
TCO Suite commonly used functions for system status display and
753
checks
Viewing the NE alarms by NEtO Supervision, and Alarm Monitor 753
Viewing the NE status by WebEML 754
54.1 System state display by visual indications
54.1.1 LED test
To be sure to have correct indications, perform the LED test of IDU MAIN unit, pushing pushbutton (9) in
Fig. 418. on page 752: 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. 417. below: while pushed, all leds of EXTENSION unit should be turned on.
54.1.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. 418. on page
752.
54.1.3 Alarm LEDs on the IDU EXTENSION unit
(3) LED test GREEN
(2) ON/OFF switch
LED Normal status

ON (green) ON (if the ON/OFF switch is on)
Fig. 417. LEDs and pushbutton on IDU EXTENSION unit for maintenance purposes

3DB 16142 JAAA Ed.01 751 / 866
(3) Ethernet (or

OS) interface

for Craft Terminal
GREEN RED RED
RED RED YELLOW
(2) ON/OFF switch
(10) Reset
(9) Alarm attending (11) LED test

(12) F interface for
Craft Terminal
LED on Meaning Action
If off (and if the ON/OFF switch is on) there is a problem in the station
Green LED ON A
battery or in the MAIN unit
Red LED LDI There is a failure in the equipment A
Red LED RDI There is a failure in the remote station A
Detection of an URGENT alarm: it means that there is at least one

Red LED MAJ A
alarm (internal and/or external) for which traffic is affected.
Detection of a NOT URGENT alarm: it means that there is at least one

alarm (internal and/or external) for which traffic is not affected (e.g.
Red LED MIN B
something is wrong, but the traffic is recovered by an automatic
protection switch).
Alarm condition ATTENDED: it means that an Operator (by pushbutton

Yellow LED ATTD (8) or by Craft Terminal) has attended the alarm (for details, see para. B
55.6.2 on page 760).
ACTION:
A The immediate intervention of a Second Level Maintenance Operator is required.
B The immediate intervention of a Second Level Maintenance Operator is not required
Fig. 418. LEDs and pushbutton on IDU MAIN unit for maintenance purposes

752 / 866 3DB 16142 JAAA Ed.01
54.2 TCO Suite commonly used functions for system status display and
checks
This paragraph sums up how to use the TCO Suite functions for system status display and checks to be
performed 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:
communicate him the NEs local IP address
verify that the PC used by the First Level Maintenance Operator can access the NE
and, in case the First Level Maintenance Operator has to login the NE:
assign him a Username/Password set
communicate him the NE readwrite Community String, if this security feature is

activated on the NE
insert the PC used by the First Level Maintenance Operator in the suitable access
list tables, if this security feature is activated on the NE
54.2.1 Viewing the NE alarms by NEtO Supervision, and Alarm Monitor
N.B. These operations do not require the NE login.
Proceed as follows:
1) perform the preliminary operations for the PCNE connection, described in para.36.3.1 on
page 499
2) perform the NE supervision by NEtO, as described in para.36.3.2 on pages 500 to 504 , using
the NEs local IP address communicated by the Station Manager
3) interpret the Alarm Synthesis icons as described in para.36.4.2 on page 505
4) more detailed information on NE alarms can be obtained clicking the button Alarm Monitor in
screen of Fig. 245. on page 504 ; for the alarm screen interpretation, refer to para.315.2
from page 606
5) at the end, unless you want to perform the operations described starting from step 3 ) of
following para.54.2.2 , close the Alarm Monitor screen, and close the NEtO session by its
button Exit

3DB 16142 JAAA Ed.01 753 / 866
54.2.2 Viewing the NE status by WebEML

N.B. These operations require the NE login.

Proceed as follows:
1) perform the preliminary operations for the PCNE connection, described in para.36.3.1 on
page 499
2) perform the NE supervision by NEtO, as described in para.36.3.2 on pages 500 to 504 , using
the NEs local IP address communicated by the Station Manager
3) with the NE supervised by NEtO ( Fig. 245. on page 504 ) click button Show
4) the login screen opens ( see para.37.1 on page 512 ), where user must insert the Username
and Password communicated by the Station Manager
5) the 9400AWY Main view opens ( see Fig. 253. on page 513 )
From this screen, according to the user profile assigned through the entered
Username/Password set, you can navigate to make some checks, for example:
Diagnosis Abnormal Condition List, see para.316.3 on page 628
Diagnosis Summary Block Diagram view, see para.316.4 on page 629
Diagnosis Ethernet Port Counters Monitoring (if Ethernet Ports equipped), see
Radio Power Measurement, see para.311.6 on page 581
Radio BER Measure, see para.311.7 on page 586
6) at the end, close the NEtO session, as described in para.36.4.7 on page 508

754 / 866 3DB 16142 JAAA Ed.01
55 SECOND LEVEL MAINTENANCE
maintenance.
This chapter describes the routine and corrective maintenance operations.
Subject On page
Introduction below
Warnings (EMC norms, Safety rules, Cautions to avoid equipment
756
damage)
Routine (preventive) Maintenance 757
Consequences of unit extraction in the IDU 758
Corrective Maintenance general flowchart 759
Alarm acknowledgment and attending 760
TroubleShooting starting with visual indications 761
TroubleShooting via Craft Terminal 762
Alarm and status synthesis indications 763
Details on alarms / statuses 764
Description of alarms and of probable causes 765
Link troubleshooting 767
Hints on the troubleshooting 772
IDU Unit replacement 778
ODU replacement 787
Faulty unit repair and Repair Form 790
55.1 Introduction
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)
The handbook parts that should be read (or known) before starting this chapter are:
chapter 21 on page 361 System overview

chapter 51 on page 739 Maintenance Policy
chapter 53 on page 745 Maintenance Tools and Spare Parts
chapter 54 on page 751 First Level Maintenance
Moreover, the secondlevel maintenance operator must know how to use the TCO SUITEbased Craft
Terminal, and must know in all details the equipment hardware and software configurations of the system
he/she has to operate on.

3DB 16142 JAAA Ed.01 755 / 866
55.2 Warnings

55.2.1 EMC norms

ATTENTION EMC NORMS
WHEN CARRYING OUT THE GIVEN OPERATIONS OBSERVE THE NORMS STATED IN PARA.
12.4.3 ON PAGE 46
55.2.2 Safety rules
The Safety Rules stated in Chapter 12 from page 35 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.
55.2.3 Cautions to avoid equipment damage
Carefully observe statements specified in point iii on page 4

756 / 866 3DB 16142 JAAA Ed.01
55.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. 55.8.4 on page 766 , allows this function.
55.3.1 Routine (preventive) Maintenance every year
It is suggested to perform 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.12.3.6
on page 42).
[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.54.1
on page 751 .
Checks by Craft Terminal

some suggested checks are indicated in para.54.2 on page 753
the commissioning tests, described in Chapter 42 on page 675 , can be useful to perform
equipment functional checks as a whole, in particular as far as checks on radio hop are
concerned.

3DB 16142 JAAA Ed.01 757 / 866
55.4 Consequences of unit extraction in the IDU

Generally, a unit can be extracted from the system for the following reasons:

to replace it with a spare part during corrective maintenance
to check a spare part taken from the spare part stock
to restore the suspected faulty unit (after its successful replacement with a spare unit during
corrective maintenance) to verify that it is really faulty.
The extraction of a unit has always some consequences on system behavior and performance that the
Maintenance Operator must know in advance:
a) Consequences of the MAIN unit extraction
The time taken to extract the MAIN unit must be short and should be limited to the time strictly
necessary for operation and maintenance purposes; it causes:
interruption of the traffic on channel 1
in (1+1) configurations, all protections are lost
the NE not to be supervised because the Equipment controller is installed in this unit.
Note for (1+1) configurations:
before extracting the unit make sure that the traffic is transmitted over channel 0 (on the
Extension unit). Otherwise, force with the CT the traffic onto channel 0.
b) Consequences of the Extension unit extraction
The time taken to extract the Extension unit must be short and should be limited to the time strictly
necessary for operation and maintenance purposes; it causes:
interruption of the traffic on channel 0
all protections lost
Note:
before extracting the unit make sure that the traffic is transmitted over channel 1 (on the MAIN
unit). Otherwise, lockout with the CT the traffic onto channel 1.

758 / 866 3DB 16142 JAAA Ed.01
55.5 Corrective Maintenance general flowchart
START
Alarm acknowledgment and attending

(para.55.6 on page 760 )
TroubleShooting starting with visual indications

(para.55.7 on page 761 )
TroubleShooting starting via Craft Terminal

(para.55.8 on page 762 ).
Identification of a unit to be replaced.
IDU unit replacement ODU replacement

(para.55.11 on page 778 ) (para.55.12 on page 787 )
System check via Craft Terminal
Try again with N

Fault repaired ?
another unit
Y
If possible, restore replaced unit in the system and perform
system check via Craft Terminal, to verify that is really faulty
Possible intermittent N
Fixed fault ?
failure
Y
Restore spare part in the system and perform
system check via Craft Terminal
Send back faulty unit to Repair Centre together with

Repair Form compiled (para.55.13 on page 790 )
END
Fig. 419. Corrective Maintenance general flowchart

3DB 16142 JAAA Ed.01 759 / 866
55.6 Alarm acknowledgment and attending

55.6.1 Alarm acknowledgment

Refer to Fig. 419. on page 759 , 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 perform the alarm attending operation
(see para. 55.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.
55.6.2 Alarm Attending
See Fig. 418. on page 752 :
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.

760 / 866 3DB 16142 JAAA Ed.01
55.7 Troubleshooting starting with visual indications
flowchart.
Some problems may be localized through the LEDs indicated in para. 54.1 on page 751
In any case, the inspection through the Craft Terminal is recommended before any unit replacement.
Flowchart of Fig. 420. indicates LEDs on the MAIN unit that should be considered first.
START
N MAJOR, MINOR,
LDI or RDI LED
END on the MAIN unit
is ON
Try to login NE by WebEML
N Y
Login successful ?
perform procedure in perform procedure in

para.55.10.1 on page 772 para.55.8 on page 762
Fig. 420. Troubleshooting starting with visual indications

3DB 16142 JAAA Ed.01 761 / 866
55.8 Troubleshooting via Craft Terminal

Refer to Fig. 419. on page 759, for the position of this step inside the corrective maintenance general

flowchart.

The LCT/RCT WebEML application includes several types of functions for system maintenance (used in
commissioning operations, too), as depicted in the following table:
FUNCTION FUNCTION DESCRIPTION
Diagnosis menu para.55.8.1 below
Alarm Monitor para.55.8.2 on page 763
Loopbacks para. 55.8.3 on page 766
Operators Controls of the protection switches para. 55.8.4 on page 766
Tx mute functions para. 55.8.5 on page 766
Performance Monitoring para. 55.8.6 on page 766
BER measurement para. 55.8.7 on page 766
Commissioning tests para. 55.8.8 on page 766
Link troubleshooting para. 55.9 on page 767
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.55.11 on page 778
for IDU, or to para.55.12 on page 787 for ODU).
55.8.1 Diagnosis menu
The options available in the Diagnosis menu are (N.B.):
Remote Inventory
Abnormal Condition List
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).
Current Configuration View
Ethernet Port Counters Monitoring
N.B. For further information and operative procedures on above menus, refer to the Chapter
316 from page 625
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 SWP TCO SUITE 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.
For further information and operative procedures on Event Log, refer to para.315.3 from page
621

762 / 866 3DB 16142 JAAA Ed.01
55.8.2 Alarm Monitor
The Alarm Monitor embedded in NEtO allow the Operator to examine the alarms currently present in the
equipment or in the link or in the PDH network.

For full information and operative procedures on Alarm Monitor, refer to para.315.2 from page 606
55.8.2.1 Meaning of the alarm and status icons
With reference to Fig. 421. below:
for the meaning of the indications in the Severity alarm synthesis area, and in the Domain alarm
synthesis areas, refer to para.37.5 on page 517
for the meaning of the indications in the Management state control panel area, refer to para.37.6
on page 518
Severity alarm synthesis Domain alarm synthesis
Management state control panel
Fig. 421. Alarm and status synthesis indications

3DB 16142 JAAA Ed.01 763 / 866
55.8.2.2 Details on alarms / statuses

The troubleshooting proceeds by checking the detailed information on the NE active alarms using the

WebEML as in Fig. 422. 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. 422. 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. 106. 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. 107. on page 765 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.

764 / 866 3DB 16142 JAAA Ed.01
55.8.2.3 Description of alarms and of probable causes
The information provided helps the operator during troubleshooting operations.

Tab. 107. General issues of the alarm meanings and their respective maintenance actions
ALARM MEANING MAINTENANCE ACTION

AIS detection on the tributary in Tx Check the tributary connected
AIS
side or Rx side equipment
ATPC loop problem Problem on the ATPC loop Communication problem
Battery fail Problem on the Station Battery Check the Station Battery
Excessive errors. Check the link
High BER Excessive BER
(propagation problem)
Demodulator failure affecting the
Dem fail Replace the ODU
demodulated signal
Loss of the incoming signal at the Check the link (propagation
Dem LOS
demodulator input problem)
Replace the ODU; if the alarm is still
Cable LOS Problem on the cable or on the ODU
active replace the cable.
Frequency setting incompatible with Change the frequency or change the
Incompatible Frequency
the ODU P/N ODU
Incompatible PTx Output power out of the limits Replace the ODU
Press the Reset pushbutton on the
Internal Communication
ODU not responding MAIN unit. If the alarm is still active,
Problem
replace the ODU
Check the LAN connection or
LAN failure LAN problem
replace the MAIN unit
Check the correct connection of the
cable between the IDU and the
Link Identifier Mismatch Mismatch on the link identifier relevant ODU. If the connection is
correct, check the link (propagation
problem)
LOF at the Tx tributary input or at Rx
tributary output (with framed Check the tributary connected
Loss Of Frame
tributary) or LOF of the Rx equipment or the line
aggregate signal
Loss Of Frame (Aggregate
LOF of the Rx aggregate signal Check the link (errors)
signal)
Loss Of Signal LOS at the Tx tributary input Check the line
Check the link (propagation
Low BER Low BER at the Rx side
problem)
Internal modulator failure affecting
Mod fail Replace the ODU
the modulated signal
Investigate by using the loopback
Mod LOS No signal at the modulator input
facilities with the CT.
Remote Defect Indication Alarm active in the remote station Check the remote station
Replaceable Unit Problem Problem on a replaceable unit Replace the unit

3DB 16142 JAAA Ed.01 765 / 866
Tab. 107. General issues of the alarm meanings and their respective maintenance actions

ALARM MEANING MAINTENANCE ACTION

Replaceable Unit Type Mismatch between the installed unit Change the unit configuration or
Mismatch and the sw configured unit change the unit
Replaceable Unit Type Missing No unit in a configured slot Install the unit
Check the link (propagation
Rx Fail (Radio alarm) No RF received signal
problem)
Performance threshold has been
Threshold Cross Errors on the link
crossed
Tx Fail (Radio alarm) Transmitter failure Replace the ODU
Unconfigured Equipment
Unit present in an unconfigured slot Configure the unit
Present
Mismatch on the software version
Version Mismatch between CT software and Download the software version
equipment software
Housekeeping Active input housekeeping Check the housekeeping
55.8.3 Loopbacks
The loopbacks (settable by WebEML) 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 318 from
page 645 . Usage examples in para.55.9 from page 767
55.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.
For further information and operative procedures, refer to the Chapter 317 on page 635
55.8.5 Tx mute function (local and remote)
This facility allows to switch off the transmitter. This facility can be useful during commissioning to avoid
producing interference if the frequency is not yet properly set.
For further information and operative procedures, refer to the Chapter 311 on page 573 . Usage
examples in para.55.9 from page 767
55.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 319 on page 657
55.8.7 BER measurement
The BER measurement (noonintrusive) can be performed as described in para.311.7 on page 586
55.8.8 Commissioning tests
In some cases, the commissioning tests, described in Chapter 42 from page 675 , can be useful to
perform equipment functional checks as a whole, in particular as far as checks on radio hop are concerned.

766 / 866 3DB 16142 JAAA Ed.01
55.9 Link troubleshooting
55.9.1 Main tools available

[1] Loopbacks
2 loopbacks at IDU level and 1 loopback at ODU level are available. Their activation is done through
WebEML. Herebelow a summary ( for details, refer to Chapter 318 from page 645 )
a) Near end IDU cable loopback

IDU ODU ODU IDU
LIU FRAME MODEM IF RF IF RF MODEM FRAME LIU
This loopback is useful to check the continuity of the signal from the tributaries up to the IDU
cable interface.
b) Near end ODU cable loopback

IDU ODU ODU IDU
LIU FRAME MODEM IFRF IFRF MODEM FRAME LIU
This loopback is useful to check the continuity of the signal from the tributaries up to the cable
interface of the ODU.
c) Far end IDU tributary loopback

IDU ODU ODU IDU
LIU FRAME MODEM IFRF IFRF MODEM FRAME LIU
Station A Station B
This loopback is useful to check the continuity of the signal on the overall path excluding the
LIU interface in the remote station. This loopback can be activated separately on each tributary.
[2] Tx Power mute

The Tx power of the ODU can be muted. This can be useful to perform investigation related to
interferer.
This command is available locally and remotely (see para.55.10.9 on page 777 )
[3] Received Signal Level indication

The received level at the input of the transceiver is available on the ECT. This information is useful
to check the theoretical expected value given by the link budget.

3DB 16142 JAAA Ed.01 767 / 866
55.9.2 Alarms and troubleshooting

The main radio alarms with the associated maintenance actions are described hereafter. Without any

indication, all the maintenance actions are done locally in the station where the alarm is raised.

55.9.2.1 Transmitter alarms
[1] Mod LOS alarm

Meaning : Missing signal at ODU input
Maintenance actions :
Mod LOS alarm
Activate the near end

IDU cable loopback
NO
Tributary signal Change the IDU
OK ?
YES

ODU cable loopback
Tributary signal NO
Check the IDU/ODU
OK ? cable
YES
Change the ODU
[2] Mod Fail alarm

Meaning : Internal modulator failure
Maintenance action : change the ODU
[3] Tx Fail alarm

Meaning : The Tx power level cannot be aligned with the consign. This alarm is raised when
the deviation is at least 6dB. Most of the time, the root cause is a lack of gain in the Tx chain.
Maintenance action : change the ODU

768 / 866 3DB 16142 JAAA Ed.01
55.9.2.2 Receiver alarms
[1] Rx fail alarm

Meaning : The received level is very low or absent.

Rx Fail alarm
Configuration of the remote station NO

(Tx power level, RTPC or ATPC range, Troubleshoot the
Tx frequency) remote station
OK ?
YES
Alignment of NO
Align the antennas
the antennas
OK ?
YES
Normal NO Wait for normal

condition of
condition of propagation
propagation ?
YES
Change the ODU
Note : In case of antenna misalignment or propagation events, both direction should be affected

3DB 16142 JAAA Ed.01 769 / 866
[2] Dem fail alarm
Meaning : The format or the level of the received signal is not the expected one. Therefore, the

synchronization of the demodulator is impossible.


Dem Fail alarm
Received level is in the NO Troubleshoot as for

expected range ? Rx fail alarm
YES
Modulation & rate in NO

Align the configuration
the remote station in the remote station
aligned ?
YES
To check the presence

of an inband interferer,
muteoff the Tx power
in the distant station
Received level NO Presence of an interferer.

< 95 dBm ? Modify the radio planning
YES
Change the ODU

770 / 866 3DB 16142 JAAA Ed.01
[3] HBER alarm
Meaning : The BER on the link in abnormally high (close to 103) .
HBER alarm

IDU cable loopback
NO
HBER alarm Change the IDU
cancelled ?
YES

ODU cable loopback
NO
HBER alarm Check the IDU/ODU
cancelled ? cable
YES
NO in ATPC mode, NO
Received level is in Troubleshoot as for
the expected ATPC Rx threshold Rx fail alarm
range ? set too low ?
YES YES
To check the
presence of an Align the ATPC Rx
inband interferer, threshold as specified
muteoff the Tx power on page 579
in the distant station
Received level NO Presence of an interferer.

< 95 dBm ? Modify the radio planning
YES
Change the ODU
End of Link troubleshooting procedure

3DB 16142 JAAA Ed.01 771 / 866
55.10 Hints on the troubleshooting

This paragraph gives hints on following matters:

Subject On page
Problems with the Craft Terminal
below
PC restart
NE not accessible 773
Craft Terminal not working on NEs local Ethernet interface 773
Craft Terminal not working on NEs Finterface 773
Checks before MAIN unit or FLASH CARD replacement 774
Analog measurements 774
NMS 64 kbit/s V.11 and G.703 775
Loopbacks 775
Remote NE unreachable for deep fading 775
Configuration change from 4 QAM to 16 QAM 775
Correct use of Full Configuration Procedure 775
Abnormal condition list 776
Tx Mute functionality for interferences investigation 777
55.10.1 Problems with the Craft Terminal
With regard to the PC maintenance, refer to the constructors documentation.
55.10.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 all TCO SUITE webserver and NEtO applications
in order to shutdown the PC execute the command :
Start > Shutdown
A window (Windows 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, perform the checks
indicated in following paragraphs 55.10.1.3 (Ethernet interface usage) or 55.10.1.4 (F
interface usage), till paragraph 55.10.1.5 on page 774

772 / 866 3DB 16142 JAAA Ed.01
55.10.1.2 NE not accessible
Provided that you are sure of the NEs local IP address and Ethernet Configuration IP address values,
and you cannot access any local or remote 9400AWY V2.1.3 NE, proceed with the following checks:
verify to use the local IP address or Ethernet Configuration IP address (if they are different),
according to the used TCO Suite application
check the NE reachability from the CT by ping, as described in point [2] on page 415
check that the PC network routing data comply with those necessary, according to the various
scenarios described in para.32.2.4 from page 416
55.10.1.3 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. 182. on page 412 ; that on the right is not for CT
interface).
Restart the Craft Terminal (NE logout, PC switch off/on, NE login).
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. 89. on page 412 ), 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.55.10.1.5 on page 774.
55.10.1.4 Craft Terminal not working on NEs Finterface
Proceed with the following checks:
Verify that the CT serial port is effectively that connected by cable to equipments F interface and that
the cable is correctly connected.
In Windows, verify that the possible selection Start % Programs % AlcatelLucent % 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 performed: refer to
para.41.4 on page 669 to know what to do.
Remind that, before to use the F interface, you must:

set both the PC desktop Properties System standby and System hibernates to Never: see
point a ) on page 669
start manually LLMAN: see point b ) on page 670
3DB 16142 JAAA Ed.01 773 / 866
For the SWP to operate correctly, it is necessary that the Virtual Network Card (that you have
associated to the PCs RS232 serial port is always the first one in the Network Connections list. So,

check for the Network Connections order (refer to the TCO Suite User Manual).

Restart the Craft Terminal (NE logout, PC switch off/on, NE login).
Check that speed is the same:

at PC side ( see para.62.7.3 on page 848 )
at NE side, through the Alarms & Settings function ( see para.35.2.7 on page 492 ).
For additional information, refer to the section Troubleshooting of the LLMAN help online ( see
para.41.4.3 on page 672 ).
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.55.10.1.5 on page 774
55.10.1.5 Checks before MAIN unit or FLASH CARD replacement
After having performed the checks in previous paragraphs 55.10.1.2 to 55.10.1.4 , try to start the NE
supervision by NEtO. If it does not work:
1) push the RESET button on the MAIN unit and wait 10 minutes;
2) after 10 minutes, try again to start the NE supervision by NEtO. If NE supervision is on, proceed
investigating the system state by Alarm Monitor and/or WebEML applications;
3) if, after 10 minutes, the NE supervision still fails, replace the MAIN unit, as indicated in
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.56.2 on page 794
55.10.2 Analog measurements
In case of two CT connected to the NE, as shown in the figure below, and at the same time both open on
the menu Radio Power Meas, the analog measurements relevant to the PTx rem (Tx power of the
Remote NE) and the PRx rem (Rx power of the Remote NE) could have some instabilities (i.e. an
intermittent +99 dBm is reported for the PTx rem and 99 dBm is reported for the PRx rem).
ODU ODU
Station A Station B
IDU IDU

774 / 866 3DB 16142 JAAA Ed.01
55.10.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 Full Configuration Procedures Step I on page 472
55.10.4 Loopbacks
For a correct activation of every loopback (Loopback menu):

the relevant tributary must be enabled ( Full Configuration Procedures Step I point [1] on page
454 )
the local transmitter must be not muted (CT Menu Radio Configuration)
Note 1: The loopback will become active about 67 sec. (24 sec. for the RF loopback) after the loopback
command forward
Note 2: A loopback is never permanent; it is always removed automatically after the timeout expire
(see para.318.1 on page 646 )
55.10.5 Remote NE unreachable for deep fading
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.
Wait for the automatic restart of the Supervision.
If the Supervision does not start, close and open again NEtO.
If the Supervision does not start, switch off and switch on the PC.
55.10.6 Configuration change from 4 QAM to 16 QAM
With 16 QAM the max. Tx power must be typically 3 dB below the max Tx power of the 4 QAM.
55.10.7 Correct use of Full Configuration Procedure
The Full 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).

3DB 16142 JAAA Ed.01 775 / 866
55.10.8 Abnormal condition list

The abnormal condition list is a summary of the abnormal conditions currently active in the NE due to

manual operations such channel protection switching commands (Radio, HST Tx or Mux/Demux), Tx

muting, or any loopback (tributary, IDU, ODU).
Most of the manual operations listed in the abnormal conditions list may affect the traffic and the normal
working condition of the equipment
By WebEML Diagnosis Abnormal condition list
Press Refresh to actualize the list each time it is required.
Fig. 423. Abnormal condition list

776 / 866 3DB 16142 JAAA Ed.01
55.10.9 Tx Mute functionality for interferences investigation
The local and the remote transceiver(s) can be muted by the following procedure:
By WebEML 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. 424. 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.

3DB 16142 JAAA Ed.01 777 / 866
55.11 IDU unit replacement

In general, an IDU unit can be replaced:

a) for spare part stock management:
to check periodically the functionality of spare parts present in the spare part stock
b) or, during corrective maintenance:
to replace a faulty (or suspected faulty) unit with the correspondent spare part
Please refer to Fig. 419. on page 759 , for the position of this step inside the corrective maintenance
general flowchart.
Tab. 108. 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. 108. IDU unit replacement procedures
UNIT PARAGRAPH PAGE
IDU MAIN unit (CH1) 55.11.1 779
IDU EXTENSION unit (CH0) 55.11.2 783
FLASH CARD (housed on MAIN unit) Chapter 56 793
N.B. All these procedures are based, for both 1+0 and 1+1 configurations, on the equipment
interconnection diagrams depicted in Chapter 15 Indoor Unit installation and cabling
from page 69
Please make reference to the equipment interconnection diagram corresponding to your

system actual layout.

778 / 866 3DB 16142 JAAA Ed.01
55.11.1 IDU MAIN unit replacement procedure (CH1)
ON/OFF switch
Flash Card label
Equipment Controller
Reset pushbutton
Flash Card Flash Card cover possible additional

Identification label
identification label
of the upgrade kit
(see point [14]
on page 803)
Fig. 425. Details for IDU MAIN unit or FLASH CARD replacement
General warnings:
Screw fixing
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 Chapter 15
Indoor Unit installation and cabling from page 69

3DB 16142 JAAA Ed.01 779 / 866
Procedure:

[1] Preliminary operations for 1+1 configurations:

Before removing the defective IDU MAIN unit, perform following operations (operations by Craft

Terminal possible if CT working):
results on main traffic

substep operation by CT
and services
enable Force on CH0 Extensions RPS switch

[1]A if set as Revertive, set RPS protection scheme as
No Revertive
enable Force on CH0 Extensions TPS switch

[1]B if set as Revertive, set TPS protection scheme as in general, no
No Revertive alarms/errors on both
NEs (N.B.)
Only in 1+1 fully protected configurations:
enable Force on CH0 Extensions EPS switch
[1]C if set as Revertive, set EPS protection scheme as
No Revertive
(N.B.)
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. 425. on page 779) read the unit
Logistical Item (read also notes in point [14] on page 803, for the possible additional identification
label of the upgrade kit)
[4] Get a spare unit with the same Logistical Item (see para.53.3.5 on page 749 for general cautions).
N.B. If, according to the spare part policy described in para.53.3.3 point a ) on page 748 :
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.57.1 on page 797 (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

780 / 866 3DB 16142 JAAA Ed.01
[6] Turn off the front panel power switch (position O, see Fig. 425. on page 779):
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 performed, 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
Fig. 1. on page 4).
ATTENTION

this avoids the possible damage of the electronic devices for electrostatic discharges
[11] Perform the following operations on the IDU MAIN defective unit (see Fig. 425. on page 779):
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] Perform the following operations on the IDU MAIN spare unit (see Fig. 425. on page 779):
remove the Flash Card cover

insert the Flash Card you have extracted from the IDU MAIN defective unit in previous step [11]
restore the Flash Card cover
[13] Now you can take off the antistatic protection armlet
[14] Install the IDU MAIN spare unit

3DB 16142 JAAA Ed.01 781 / 866
[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 781, 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. 425. on page 779)
[18] Wait for the unit configuration (about 2 minutes)
[19] Switch on CT, start NEtO, and login the NE by WebEML
[20] Additional operation for 1+1 configurations:
operation by CT results on main traffic and services
disable Force on CH0 Extensions RPS switch no alarms/errors on both NEs
Note: the commands Force on Extensions TPS and EPS switches [set in previous steps [1]B
and [1]C on page 780] 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 (N.B.). Note that TPS and RPS
protection scheme setting to Revertive is not error free
N.B. EPS protection scheme is present only in 1+1 fully protected configurations.
[24] Flash Card identifier label affixing
Please read para.31.1.2.2 on page 405.

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

782 / 866 3DB 16142 JAAA Ed.01
55.11.2 IDU EXTENSION unit replacement procedure (CH0)
ON/OFF switch
possible additional identification label Identification label

of the upgrade kit (see point [14] on page 803)
Fig. 426. Details for IDU EXTENSION unit replacement
General warnings:
Screw fixing
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 Chapter
15 Indoor Unit installation and cabling from page 69

3DB 16142 JAAA Ed.01 783 / 866
Procedure:

[1] Preliminary operations:

Before removing the IDU EXTENSION defective unit, by Craft Terminal perform following operations:

substep operation by CT results on main traffic results on services
Enable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[1]A
Mains RPS switch NEs NEs
Enable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[1]B
Mains TPS switch NEs NEs
no alarms/errors on
Only in 1+1 fully no alarms/errors on
remote NE
protected configurations, remote NE
[1]C 12 sec alarm/AIS
enable Lockout on CH1 1 sec Slip or AIS on
Sync Loss on local
Mains EPS switch local NE
NE
[2] On the unit identification label present at unit rear side (see Fig. 426. on page 783) read the unit
Logistical Item (read also notes in point [14] on page 803, for the possible additional identification
label of the upgrade kit)
[3] Get a spare unit with the same Logistical Item (see para.53.3.5 on page 749 for general cautions).
N.B. If, according to the spare part policy described in para.53.3.3 point a ) on page 748 :
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.57.1 on page 797 (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. 426. on page 783):
of the IDU EXTENSION unit to be replaced
of the IDU EXTENSION spare unit

784 / 866 3DB 16142 JAAA Ed.01
[6] if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDU
EXTENSION unit to be replaced.
[7] Disconnect all remaining cables from the front panel of the IDU EXTENSION unit to be replaced, in
the recommended order:

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 performed, 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 785, 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. 426. on page 783)
[13] Wait for the unit configuration (about 2 minutes)

3DB 16142 JAAA Ed.01 785 / 866
[14] perform following operations:

substep operation by CT results on main traffic results on services

no alarms/errors on
Only in 1+1 fully no alarms/errors on
remote NE
protected configurations, remote NE
[14]A 12 sec
disable Lockout on CH1 1 sec Slip or AIS on
alarm/AISSync
Mains EPS switch local NE
Loss on local NE
Disable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[14]B
Mains RPS switch NEs NEs
Disable Lockout on CH1 no alarms/errors on both no alarms/errors on both

[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

786 / 866 3DB 16142 JAAA Ed.01
55.12 ODU replacement
In general, an ODU unit can be replaced:

a) for spare part stock management:

to check periodically the functionality of spare parts present in the spare part stock
b) or, during corrective maintenance:

to replace a faulty (or suspected faulty) unit with the correspondent spare part
Please refer to Fig. 419. on page 759 , 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 Chapter 16 from page 137
SAFETY RULES
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:
CH1 (ODU connected to IDU MAIN unit), perform steps [1]A to [1]C on page 780
CH0 (ODU connected to IDU EXTENSION unit), perform steps [1]A to [1]C on page 784
[3] Switch off the ODU by using the ON/OFF switch of the relevant IDU unit:
for channel 1, operate on MAIN unit (position O, see Fig. 425. on page 779 )
for channel 0, operate on EXTENSION unit (position O, see Fig. 426. on page 783 )
WARNING: this avoids a possible unrecoverable unknown condition of the spare ODU, when
ODU will be switched on in next step [9]

3DB 16142 JAAA Ed.01 787 / 866
[4] If present, remove the solar shield (see Fig. 49. on page 143 , and Fig. 50. on page 144 )

[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. 416. on page 747 ;
in case of 78 GHz ODUs:
a) remove the faulty TRANSCEIVER box in the following way (refer to Fig. 50. on page 144):
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.16.2.2.3.2 on page 146 ), i.e. if the TRANSCEIVER boxs (D) (TX) is coupled
to the:
BRANCHING boxs (B) (HIGH FREQ)
or BRANCHING boxs (C) (LOW FREQ)
b) 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. 51. on page 145 )
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. 50. on page 144 )
[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]

788 / 866 3DB 16142 JAAA Ed.01
[10] Additional operations for (1+1) configurations:
by CT, remove forced traffic condition set in previous step [2]
To do that, if replaced ODU is that of:

CH1 (ODU connected to IDU MAIN unit), perform following operations:
results on main traffic and

substep operation by CT
services
[10]A disable Force on CH0 Extensions RPS switch no alarms/errors on both NEs
[10]B disable Force on CH0 Extensions TPS switch no alarms/errors on both NEs
Only in 1+1 fully protected configurations:

[10]C no alarms/errors on both NEs
disable Force on CH0 Extensions EPS switch
CH0 (ODU connected to IDU EXTENSION unit), perform steps [14]A to [14]C on page 786
[11] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protection
scheme setting to Revertive is not error free.
[12] Check the system status through LED visual inspection and through the Craft Terminal.
End of ODU replacement procedure

3DB 16142 JAAA Ed.01 789 / 866
55.13 Faulty unit repair and Repair Form


flowchart.

55.13.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.
55.13.2 Repair Form filling
To facilitate repair operation, data on the faulty unit must be reported on the form shown in Fig. 427.
on page 791
The repair form must be filledin with as much data as possible and returned to AlcatelLucent
together with the faulty unit.

790 / 866 3DB 16142 JAAA Ed.01
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 EQUIPMENT SOFTWARE PART NUMBER
STATION/RACK SUBRACK SLOT

TO BE FILLED IN BY THE SENDER
MNEMONIC ALCATEL PART NUMBER
SERIAL NUMBER FAULTY UNIT SOFTWARE VERSION
FAULT PHASE REASON FOR REPAIR PRESUMED CAUSE
INSTALLATION / CLEAR FAULT DROP IN PERFORMANCE INTERNAL

TURN ON
LIGHTNING
OPERATION INTERMITTENT FAULT UPGRADE/QUALITY ALERT
EXTERNAL AIR COND.
MAINTENANCE TEMPERATURE FAULT OTHER
DATE NAME OF SENDER

FAULT STILL PRESENT
AFTER REPAIR
COMMENTS
PROCESSING FAULTS DETECTED

TO BE FILLED IN BY THE REPAIR OPERATOR
NO FAULTS FOUND UPGRADE SOLDERING / COMPONENT ADJUSTMENT

WIRING
A I C FL P
STANDARD REPAIRING NOT REPAIRABLE MECHANICAL PRINTED DIRT

(REJECTED) CIRCUIT BOARD
BD M V1 V1 V2
SUBSTITUTED
QUALITY ALERT CORROSION OTHER
I SX V3
NOTE : LETTERS ARE FOR FACTORY USE
COMMENTS
DATE REPAIRING NUMBER REPAIRING CENTRE NAME OF REPAIR OPERATOR
Fig. 427. Repair form

3DB 16142 JAAA Ed.01 791 / 866
792 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
56 SPARE FLASH CARD MANAGEMENT, AND REPLACEMENT PROCEDURE
This chapter, for corrective maintenance purpose, describes how to manage the spare Flash Card and
how to replace it, in case of problems.
Subject On page
Spare Flash Card management below
Flash Card replacement procedure 794
Introduction 794
Execution of the Flash Card replacement 795
56.1 Spare Flash Card management
Please refer to para.31.1 from page 404 for detailed information on Flash Card position, types and
identification.
With reference to the Flash Card content description given in para.33.2.1.2 on page 424 , 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 TCO Suite or
by TMN system.
b) supplied as generic spare part, as delivered from AlcatelLucent factory, contains default SW
information. 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 TCO
Suite or by TMN system after the system installation phase.
WARNING: 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
[2] the .qcml configuration file
If necessary , for details on how to generate NE data backup files, refer to point [3] from
page 428
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.

3DB 16142 JAAA Ed.01 793 / 866
56.2 Flash Card replacement procedure

56.2.1 Introduction

The need for this replacement is for corrective maintenance purposes only, whenever the failure or content
corruption of the Flash Card is suspected.
The Flash Card contains the system software (see para.33.2.1.2 on page 424 ). Many types are
envisaged: their identification is described in para.31.1.2.2 on page 405
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 executed 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.56.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.56.1 on page
793 ):
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.
WARNING
Due to the Flash Card position (on the rear side of the IDU MAIN unit), when the IDU rear side is not
physically accessible, you are obliged to deinstall the IDU MAIN unit, to perform the Flash Card
replacement, and then reinstall it again. E.g.:
the ETSI rack has a fixed rear side panel, so that deinstallation and reinstallation are
necessary
on the contrary, the LABORACK has not a rear side panel, so that deinstallation and
reinstallation are not necessary

794 / 866 3DB 16142 JAAA Ed.01
56.2.2 Execution of the Flash Card replacement
General warnings:
Screw fixing
Procedure:
[1] Read the Flash Card Licence String on the label affixed on IDU MAIN unit ( Ref. (A) in Fig. 143.
on page 289 ) and according to it, retrieve the Flash Card Logistical Item through Tab. 85. on page
404 .
If CT works, you can verify the Flash Card Licence String by Supervision SW Key (example
in point [1] on page 424 )
[2] Get the spare Flash Card with the same Logistical Item (or, the same Licence String) ; 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. 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.
[4] Wear the antistatic protection armlet [ see point b ) on page 4 ] and connect its termination to a
grounded structure
ATTENTION

[5] Switch off the IDU MAIN unit
[6] If the rear side of the IDU MAIN unit is not physically accessible, disconnect all cables from its front,
and deinstall it from the rack
[7] Remove the Flash Card cover ( see Fig. 425. on page 779 ). Store tidily cover and screws for their
successive mount
[8] 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. 178. on page 405 for Flash Card
profile and insertion direction)
[9] If deinstalled in step [6] above, reinstall the IDU MAIN in the rack, and reconnect all cables to
its front

3DB 16142 JAAA Ed.01 795 / 866
[10] Switch on the IDU MAIN unit. The system performs an automatic restart.

[11] After two minutes, login the NE by WebEML.

Now, if you have inserted:

a generic spare Flash Card, proceed with following step [12]
a NEspecific spare Flash Card, proceed with following step [13]
[12] If you have inserted a generic spare Flash Card, perform following checks and operations by
WebEML:
1) verify the SW COMMITTED and STANDBY versions in the Flash Card, as described in
para.59.2 on page 813 :
if the SW COMMITTED version is equal to that previously present with the replaced flash
card (i.e. V2.1.3), proceed with substep 2 ) below;
if the SW COMMITTED version is not equal to that previously present with the replaced
flash card, but the STANDBY version is equal (i.e. V2.1.3), proceed with the swap
between the SW COMMITTED and STANDBY versions, as described in para.59.3.5
on page 822 .
Then, proceed with substep 2 ) 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 (i.e. V2.1.3), as described in chapter 59 from page 811
Then, proceed with substep 2 ) below.
2) restore the specific NE data, as described in point [4] on page 429 (perform at first the .qcml
configuration file restore, then MIB file restore). See WARNING on page 793
In this way, the MIB configuration data are loaded in the Flash Card data base.
With this double restore operation, the system should make one or two automatic restarts.
In alternative to activation by SW, perform the Equipment Controller HW Reset, pushing the
suitable button on IDU MAIN Unit [ Ref (10) in Fig. 143. on page 289 ).
About two minutes are necessary for the supervision process to get data from the new flash
card.
Now, you can reconnect the NE to the supervision network, and proceed with following step [13]
[13] Restore the Flash Card cover removed in previous step [7]
[15] Perform functional checks by Craft Terminal.
End of Flash Card replacement procedure

796 / 866 3DB 16142 JAAA Ed.01
57 SYSTEM HARDWARE UPGRADE
This chapter details all phases necessary to perform the following hardware upgrades:
Subject On page
Installation of plugins below
Upgrade from 1+0 to 1+1 configuration 804
57.1 Installation of plugins
57.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. 109. below lists the plugins presently available.
Tab. 109. Available plugin upgrade kits
Logistical Item Description Notes

3DB16086AAXX 32E1 ON SITE UPGRADE KIT
DATA ENHANCED ON SITE UPGRADE KIT in alternative
3DB16130AAXX
(4 x 10/100/1000 BaseT ports)
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 the IDU Main unit
and into the IDU Extension unit, only for 1+1 fully protected configurations.
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.

3DB 16142 JAAA Ed.01 797 / 866
57.1.2 Procedure

Drawings used to show operations are relevant to the IDU Main unit. Operations to be

performed for IDU Extension unit are exactly the same.

Screw fixing
In all described operations (closing the unit box, fixing subracks to the rack, fixing cables to
connectors, etc.), and unless differently specified, the screw tightening torque must be as stated
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 following operations concern the IDU unit (MAIN or EXTENSION) to be upgraded:
[1] Isolate the power supply, disconnect Craft Terminal and disconnect all cables.
[2] Uninstall the unit and place it on a workbench
[3] Fig. 428. :
if present, dismount both fixing brackets (A and B), there are two screws for each (C)
undo the side screws D (three on each side) for cover unfix
Fig. 428. Dismounting the fixing brackets and cover unfix

798 / 866 3DB 16142 JAAA Ed.01
[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. 429. :
use of fixing bracket to release the cover
sliding out the cover
Fig. 429. Release and sliding out the cover
[5] Wear the antistatic protection armlet and connect its termination to a grounded structure (see Fig. 1.
on page 4 ).
ATTENTION


3DB 16142 JAAA Ed.01 799 / 866
[6] Now, you can remove the cover (Fig. 430. ):

Fig. 430. Removing the cover
[7] Fig. 431. : 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 plate to remove for
AUDIO + USER SERVICE TRIBUTARY plugin
CHANNEL plugin
Fig. 431. Dismounting the metal plate

800 / 866 3DB 16142 JAAA Ed.01
[8] Fig. 432. shows in details the connectors and columns for plugin fixing by screws
2 columns for plugin

fixing by screws 3 columns for plugin
fixing by screws
connectors for plugin
connector
for plugin
Fig. 432. Connectors and columns for plugin fixing by screws
[9] Insert the plugin in its connector(s) depicted in previous Fig. 432. , and fix it:
on the PCB using the 2 or 3 screws on the suitable columns depicted in previous Fig. 432.
to the front panel by the 2 screws or the screw columns
The result must be as shown in following Fig. 433.

3DB 16142 JAAA Ed.01 801 / 866
Details of 1632 E1 plugin installed
Details of Enhanced Ethernet plugin installed
Details of Audio + User Service Channel plugin installed
Fig. 433. Plugin insertion and fix

802 / 866 3DB 16142 JAAA Ed.01
[10] Reinsert the cover
(reverse operation of Fig. 430. on page 800 )
[11] Slide in the cover

(reverse operation of Fig. 429. on page 799 . The fixing brackets use is not necessary)
[13] Fix the cover and, if they were present, mount both fixing brackets
(reverse operation of Fig. 428. on page 798 )
[14] Upgrade kit identification label

After this upgrading, the Unit identification label placed on the box rear side [position (C) in Fig. 143.
on page 289 for the IDU Main Unit, and in Fig. 145. on page 294 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 existing
identification label identification label
of the upgrade kit 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 Chapter 15 from
page 69 , according to the new hardware configuration
system data redefinition (it is different from that previous to upgrading), performing the
NEinteractive full configuration procedure by the Provisioning Tool: details in Chapter 34
from page 443
commissioning procedure, to check the new interface: details in Chapter 42 from page 675
End of procedure for installation of plugins

3DB 16142 JAAA Ed.01 803 / 866
57.2 Upgrade from 1+0 to 1+1 configuration

57.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: upgrade from 1+0 to 1+1 radio protected configuration

In this case:
at IDU level, the hardware upgrade procedure is simpler than that of case b ) below, because
it consists only of installing the IDU EXTENSION unit, and connecting it to the IDU MAIN unit
by the 100pin interconnection cable, with no need to make interventions on user signal
connections (e.g. compare 1+0 layout of para.15.3.3 on page 105 , with the corresponding
1+1 layout of para.15.3.8 on page 112 )
the upgrade can be done with a small traffic interruption time. Nevertheless, the full link
unavailability must be planned for the phase [D] .
b) Second case: upgrade from 1+0 to 1+1 fully protected configuration

In this case:
at IDU level, the hardware upgrade procedure is more complex, because it includes, in addition
to the operations described for the case a ) above, also those necessary to:
disconnect the tributary cables from the IDU MAIN unit
and then to connect the tributary cables to both the IDU MAIN and the IDU EXTENSION
units
E.g. compare 1+0 layout of para.15.3.3 on page 105 , with the corresponding 1+1 layout
of para.15.3.14 on page 121
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.
N.B. Operations by WebEML on each station must be done by local ECT through F or Ethernet
interface only, while the use of RCT is not admitted.
This procedure is particularly detailed in order to:

avoid injuries to personnel (EMF safety)
avoid damages to the equipment
SAFETY RULES

804 / 866 3DB 16142 JAAA Ed.01
57.2.2 Procedure
PHASE [A] : INITIAL CHECKS

[1] For both stations, compare the start 1+0 configuration with the target 1+1 configuration, in
particular as far as the connections at IDU level are concerned (i.e. upgrade to 1+1 radio protected
or 1+1 fully protected configuration)
[2] For both stations, ascertain to have:
all materials necessary for the HW upgrade, at IDU and ODU levels, as well as necessary
installation materials. Materials necessary for hardware upgrade:
for IDU items, refer to:
for ODU items, refer to:
for IDUODU cable, refer to:
Para.17.1 on page 189
the room in the rack to install the additional hardware (see para.15.4 from page 133 )
PHASE [B] : OPERATIONS ON FIRST STATION
[3] Prepare the power supply cable for the IDU EXTENSION unit, and connect it to the TRU (see
para.14.5 from page 64 )
[4] Using the instructions given in Chapter 15 from page 69 :

a) install the IDU EXTENSION unit and connect its power supply cable
N.B. ascertain that its ON/OFF switch is in OFF position and leave it in OFF position till
step [9]
b) connect the 100pin interconnection cable between IDU MAIN and EXTENSION units
[5] Operations to be made only in case of upgrade to 1+1 fully protected configuration (note: full link
unavailability from substep a ) till substep c ) below:
a) switch OFF the IDU MAIN unit, and disconnect from its front panel the tributary cables (with the
exception of Ethernet, if any) and the services cables (in the case the Service Protection box
must be installed)
b) using the instructions given in Chapter 15 from page 69 , and according to the plant
documentation:
install the E1 Protection box, or the E1 Protection Ycable(s), and the Service
Protection box (if foreseen in the plant documentation)
connect the IDU MAIN and EXTENSION units:

to the E1 Protection box, or the E1 Protection Ycable(s)
and to the Service Protection box (if it has been installed), or to the DDF
connect:
the E1 Protection box, or the E1 Protection Ycable(s), to the AlcatelLucent
distributor
and the Service Protection box (if it has been installed) to the station DDF, or as
specified in in Chapter 18 from page 195
c) switch ON the IDU MAIN unit

3DB 16142 JAAA Ed.01 805 / 866
[6] If not connected, connect the Craft Terminal to the IDU MAIN unit, switch it on, start NEtO and login
the NE by WebEML (details in Chapter 36 from page 497 )

[7] Using the instructions given in Chapter 16 from page 137 , in Chapter 17 from page 189 , and

according to the plant documentation, install the second ODU and its IDUODU cable.
Warning: in case of target 1+1 ODU configuration:
a) with two antennas:
install the second ODU with its own antenna (CH0)
perform grounding of the second ODU (CH0)
install, ground, and connect the IDUODU cable to the second ODU (CH0), and to the IDU
EXTENSION unit
b) with (1+1) HSB RF coupler, you must uninstall the existing ODU, install the RF coupler, and then
install the two ODUs on the coupler, performing the following operations (full link unavailability
from substep 3 ) till substep 9 ) below:
1) by WebEML, disable ATPC on CH1 (if enabled): see para.311.5.1 on page 579
2) perform NE logoff (details in para.36.4.7 on page 508 )
3) switch off IDU MAIN unit (CH1)
4) uninstall ODU CH1 from nose adapter, install the (1+1) RF coupler to the nose
adapter, and reinstall the ODU CH1 on the (1+1) RF coupler
5) install the second ODU (CH0) on the (1+1) RF coupler
6) perform grounding of the second ODU (CH0)
7) install the second IDUODU cable (CH0), ground it, and connect it to the second
ODU (CH0) and to the IDU EXTENSION unit
8) switch on IDU MAIN unit (CH1)
9) wait until system restart completion, then start NEtO and login the NE by WebEML
10 ) by WebEML, enable ATPC on CH1 (if necessary): see para.311.5.1 on page 579
[8] By WebEML, perform the following operations:
1) Configuration System Setting NE Configuration 1+1 Configuration: see para.38.4.1

on page 553
2) This configuration change causes the JUSM loss, so that you must login again the NE by NEtO
and WebEML
3) In case of fully protected configuration only, set EPS (Mux/Demux Protection) Lockout: see
para.317.5 subpara.317.5.2 on page 644 WARNING: this operation is not error free
4) Set CH0 Tx Power as follows: with reference to Fig. 308. on page 578 :
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 performed 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. 307. on page 576 :
select Channel #0 click on Frequency insert value in Tx Frequency(kHz) field Apply
[9] Switch on the CH0 Extension IDU unit by its ON/OFF switch

806 / 866 3DB 16142 JAAA Ed.01
[10] By WebEML perform the following operations:
1) Set CH0 Frequency Shifter as follows: with reference to Fig. 307. on page 576 :
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. 307. on page 576 :
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 performed in substep [10]4 ) below
3) In case of fully protected configuration only, remove EPS (Mux/Demux Protection) Lockout:
see para.317.5.2 on page 644 WARNING: this operation is not error free
4) Restart NE: see point [8] on page 430
PHASE [C] : OPERATIONS ON SECOND STATION
[11] Repeat the previous steps from [3] to [10] in the other station of the radio link
PHASE [D] : 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, perform the alignment of the second ODU antenna
(N.B.)
[13] Perform the CH0 functionality test (N.B.).
N.B. For details on commissioning procedures, please refer to the Chapter 42 from page 675
PHASE [E] : NE DATA SAVE
[14] Save data of both NEs as explained in point [3] from page 428
End of procedure for upgrade from 1+0 to 1+1 configuration

3DB 16142 JAAA Ed.01 807 / 866
808 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
58 PROCEDURE TO CHANGE CAPACITY/MODULATION/FREQUENCY
This dedicated procedure must be followed in order to avoid adjacent channel traffic impact:
[1] When change capacity/modulation, firstly check the following Tab. 110. to check if the channel
spacing is increasing or decreasing:
Tab. 110. Capacity, Modulation and Channel Spacing relationship

ODU V1 64Mb Modulation ODU V2 64Mb 4/16 Modulation
4 QAM 16 QAM 4 QAM 16 QAM
Capacity Channel spacing (MHz) Channel spacing (MHz)
2xE1 (4 Mb) 3.5 3.5
4xE1 (8 Mb) 7 3.5 7
8xE1 (16 Mb) 14 7 14 7
16xE1 (32 Mb) 28 14 28 14
32xE1 (64 Mb) 28 28
[2] Then:
if you do not use the Regional Setting, operate as specified in step [3] below
if you use the Regional Setting, operate as specified in step [4] below
[3] Not using Regional Setting:

a) In case of channel space increase (follow the sequence):
1) Firstly, change frequency;
2) Then, change capacity/modulation;
b) In case of channel space decrease (follow the sequence):
1) Firstly, change capacity/modulation;
2) Then, change frequency;
c) Or, do following steps and do not care the channel space increasing or decreasing:
1) Perform Tx mute on Manually;
2) Any sequence of change capacity/modulation and change frequency;
3) Perform Tx mute off Manually;
[4] Using Regional Setting

a) In case of channel space increase (follow the sequence):
1) Perform Tx mute on Manually;
2) Change capacity/modulation;
3) Change channel number
4) Perform Tx mute off manually
b) In case of channel space decrease (follow the sequence):
1) Change capacity/modulation
2) Change Channel number
c) Or, do following steps and do not care the channel space increasing or decreasing:
1) Perform Tx mute on manually;
2) Any sequence of change capacity/modulation and change frequency;
3) Perform Tx mute off manually

3DB 16142 JAAA Ed.01 809 / 866
810 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
59 NE UPGRADE TO V2.1.3 FROM PREVIOUS VERSION V2.1.X
This chapter describes how to upgrade to the SWP 9400AWY V2.1.3 any 9400AWY Rel.2.1 NE, presently
running with a previous SWP V2.1.3.
Subject On page
Introduction and restrictions 812
How to check the SW versions present in the NEs flash card 813
How to perform the SWP download to the NE, and its activation 815
Remotion of the 2 x Fast Ethernet plugin, if equipped (stations A and B) 816
CT startup, and check for the availability of the SWP to be downloaded 816
NE login and initial operations (stations A and B) 816
SW download to the NE (station A) 817
Activation of the new Software Package on the NE (station A) 822
Additional operation for upgrade from V2.1.0 (station A) 824
Operations on station B 824
Functional checks on the radio link (stations A and B) 824
NE data backup (stations A and B) 824
Notes about NE SW downgrade 825

3DB 16142 JAAA Ed.01 811 / 866
59.1 Introduction and restrictions

This chapter details all operations necessary to download inside the NE equipment environment, and then

activate, a SWP having a version greater (or equal) than that presently loaded in the NEs Flash Card.

The procedures in this chapter apply in both these cases [ for explanations, if necessary, refer to point
[1] on page 407 ]:
upgrade to a SWP with new Version Level (with respect to that presently running, e.g. from 9400AWY
SWP V2.1.2 to 9400AWY SWP V2.1.3)
upgrade to a new SWP patch version (with respect to that presently running, e.g. from 9400AWY
SWP V2.1.3 to 9400AWY SWP V2.1.3 patch version).
These procedures operate on the NEs flash card:
Standby bank
and Committed bank.
As a preface to this chapter, if necessary, refer to para.33.2 from page 424 , and in particular to point
[7] on page 430
N.B. If you like to know in advance whether or not the NE SW upgrade is necessary with a certain
SWP, compare the versions of the SW components in the NEs flash card committed bank (see
Fig. 435. on page 814 ) with those listed in the table Software Package Upgrade Component
of the Product Release Note associated to such a SWP [ see point [2] on page 407 ]:
if they all are exactly equal, the NE SW upgrade is not necessary
if any of them is different, the NE SW upgrade is necessary.
RESTRICTION FOR WINDOWS VISTA

With Windows Vista, the SWP download for NE upgrade cannot use LLMAN (therefore the NEs F
interface must not be used for the SWP download).

812 / 866 3DB 16142 JAAA Ed.01
59.2 How to check the SW versions present in the NEs flash card
Proceed as follows:
Perform NE Login by WebEML
From the Menu Bar of the 9400AWY Main view that opens after NE Login ( Fig. 253. on page 513),
perform SW Download SW Status, which opens the screen of Fig. 434. below.
The Flash card, where the NE software is stored, contains 2 banks. The status of one of them can
be displayed selecting [1] or [2] at screen top left side.
V02.01.03
version committed
(active)
V02.01.02
version standby
(not active)
N.B. When the equipment is shipped from factory, two SW versions are present in the flash card:
that committed is the actual SW version defined by the SWP name (e.g. V2.1.3)
that standby is the immediately previous SW version maintenance release (e.g. V2.1.2)
Fig. 434. How to check NE SW version (example)

3DB 16142 JAAA Ed.01 813 / 866
The following information is displayed for each bank:

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.
Clicking the Software Unit Status button on the screen of each bank, the screen of Fig. 435. below
opens, giving additional information on the software components of that specific bank:
EC: software on the Equipment Controller
OC_R: software on the ODU V1 Controller (Radio)
OC_2: software on the ODU V2 Controller (Radio)
the other labels give the FPGA firmware version
Fig. 435. SW Unit Status screen (example)

814 / 866 3DB 16142 JAAA Ed.01
59.3 How to perform the SWP download to the NE, and its activation
WARNING:
You must be aware that these operations must be done on both stations A and B of the radio link.
The suggested sequence of phases is:
Station
Phase Operation Described in para.
A B
Remotion of the 2 x Fast Ethernet plugin,

1 (x) (x) 59.3.1 below
if equipped (V2.1.0 case only)
CT startup, and check for the availability of

2 59.3.2 on page 816
the SWP to be downloaded
NE login and initial operations (stations A and

3 x x 59.3.3 from page 816
B)
4 SW download to the NE (station A) x 59.3.4 from page 817
Activation of the new Software Package on

5 x 59.3.5 from page 822
the NE (station A)
Additional operations for upgrade from V2.1.0

6 x 59.3.6 on page 824
(station A)
7 Operations on station B x 59.3.7 on page 824
Functional checks on the radio link (stations

8 x x 59.3.8 on page 824
A and B)
9 NE data backup (stations A and B) x x 59.3.9 on page 824
59.3.1 Remotion of the 2 x Fast Ethernet plugin, if equipped (stations A and B)
If the former version of 2 x Fast Ethernet plugin is equipped (V2.1.0 case only), it must be removed,
and, if envisaged, the new version of 4 x Gbit Ethernet plugin must be installed; for this purpose, perform
these operations on both stations:
a) using the 1320CTbased Craft Terminal of the SWP 9400AWY V2.1.0, and the instructions given
in the 9400AWY V2.1.0 User Manual:
remove traffic on Fast Ethernet ports
disable both Fast Ethernet ports
unconfigure the 2 x Fast Ethernet plugin
b) physically uninstall the 2 x Fast Ethernet plugin
c) and, if envisaged, install the DATA ENHANCED ON SITE UPGRADE KIT, making reference to
para.57.1 on page 797 of this manual
N.B. ignore the unexpected equipment alarm that arises after the installation of the 4 x Gbit
Ethernet plugin (it is not supported by SWP version V2.1.0)

3DB 16142 JAAA Ed.01 815 / 866
59.3.2 CT startup, and check for the availability of the SWP to be downloaded

a) Power on the PC and wait for its startup

b) Verify that the SWP to be downloaded is available in the PC: the new SWP 9400AWY V2.1.3specific
software components (to be downloaded toward the NE) must be already present in the Craft
Terminal environment ( see para.41.5 on page 673 )
59.3.3 NE login and initial operations (stations A and B)
Perform following operations by WebEML ( for details refer to chapter 37 from page 511 ):
a) Login the 9400AWY station A NE, using the Administrator or CraftPerson UserName & Password
WARNING: as specified in para.59.1 on page 812 , with Windows Vista, the SWP download
for NE upgrade cannot use LLMAN (therefore the NEs F interface must not be used
for the SWP download)
b) Wait for the main Equipment view to appear
c) Verify that the version to be downloaded is greater (or equal, only in case a new SWP patch version)
than those present in both the NE MIB current Standby and Committed banks (check by SW
Download SW Status, and verify both banks)
WARNING: you must be aware that the SWP download, performed 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.59.3.5 on page 822
d) Perform the NE data backup, as described in point [3] on page 428
e) Check that no hardware or radio transmission problems are present [ with exception of the
unexpected equipment alarm stated in point c ) on page 815 ]. Otherwise, solve them before
starting upgrade
f) Close all Performance Monitoring, analog measurement and BER measurement processes, if any
g) 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 the operations described in
para.59.3.7 on page 824 of this procedure
h) 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
i) By another NEtO session, perform on the 9400AWY station B NE the same operations done for
station A

816 / 866 3DB 16142 JAAA Ed.01
59.3.4 SW download to the NE (station A)
Step 1. Server Access Configuration Setup

a) By WebEML, perform SW Download Server Access Configuration
b) The following screen opens:
c) Click the button Use System Default

In this way the systems sets automatically the various fields, that depend on how the login to
the NE has been done:
by Ethernet interface: IP address of the PC to download the software in LAN mode is set
by F interface: IP address of the LLMAN to download in interface F mode is set (remind:

never with Windows Vista)
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.
d) Press OK to confirm values and close the window.

3DB 16142 JAAA Ed.01 817 / 866
Step 2. SW Download
a) By WebEML, perform SW Download Init SW Download

b) The following screen opens (example where no Software Packages are available):
Fig. 436. Empty Init SW download screen
c) Click the button Add

The following screen opens. With reference to the example in Fig. 388. on page 674 , explore
the path where the descriptor file R94A.DSC (associated to the version V2.1.3 to be
downloaded) is present, then click button Open

818 / 866 3DB 16142 JAAA Ed.01
d) Now ( Fig. 437. below) select (1) a specific SWP to download on the NE, then (2) press Init
download to start it.
(1) select
N.B.
(2)
Fig. 437. Init SW download
N.B. normally, the Forced check box must not be used.

You must tick it only in the case you want to download a certain version to a NE whose
flash card is already loaded with the same version (i.e. for corrective maintenance
purposes).
e) Confirm the start of software downloading:
2_1_3
Yes
f) The software downloading in progress is shown by a specific window:

3DB 16142 JAAA Ed.01 819 / 866
Description of the software downloading process:

if, in the Init SW download screen ( Fig. 437. on page 819 ) you have:

unselected the Forced check box (default choice):
at first, the download process compares the versions of the SW components to

be downloaded with those of the corresponding SW components present in the
NEs flash card Standby bank (see Fig. 435. on page 814 ),
then, only the SW components (if any) whose version is higher than that of the
corresponding SW components in the Standby bank are downloaded to it.
selected the Forced check box, all SW components are downloaded to the Standby
bank in any case, also overwriting those whose versions are equal.
The software download from the Craft Terminal to the NEs flash card is performed without
traffic interruption on the user ports, and lasts:
some tens of seconds, if no download is executed (this time is anyway necessary for
the comparison phase, to decide which SW components must be downloaded)
about 30 minutes, if performed locally through the F interface
about 15 minutes, if the local Ethernet interface is used
about 1.5 hour, if the download is performed toward a remote NE, through the NMS
network or the radio interface
WARNING: in this last case (download toward a remote NE), verify that the
download bar does move, even slowly. If it does not move, it means
that the download does not work properly (there are no messages to
the operator). In this case, abort the software download window by
the suitable Abort button, and begin again the software download
procedure.
g) When the download is over, the following window is shown; click OK to close it.
N.B. this message appears even if no download is actually executed.

820 / 866 3DB 16142 JAAA Ed.01
h) After the software download completion, perform SW Download SW Status , select the
Standby bank, and verify (see figure below):
that the downloaded SW is present as Stand by version, and that is the version you
wanted
and that its Operational Status is Enabled (this means that the download took place
without errors)
WARNING: if the Operational Status is Disabled, repeat the download
N.B. clicking on the Software Unit Status button, it is possible to see its components and
their version (see Fig. 435. on page 814 )
V02.01.03

3DB 16142 JAAA Ed.01 821 / 866
59.3.5 Activation of the new Software Package on the NE (station A)

After the software download ( explained in previous para.59.3.4 from page 817 ), 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. Activation of the Standby SW bank
a) By WebEML, perform SW Download SW Status
b) Fig. 438. below: select the Standby SW bank (1), set Activation or Forced Activation (2) in
the Software Management Action field, then click Apply Action (3)
N.B. difference between Activation and Forced Activation:
selecting Activation, the system performs an automatic restart, after the swap,
only if the contents of the Committed and the Stand by banks are different
selecting Forced Activation, the system performs anyway an automatic

restart, after the swap.
(1)
V02.01.03
(2)
V02.01.03
(3)
Fig. 438. Activation of the Standby SW bank

822 / 866 3DB 16142 JAAA Ed.01
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. The JUSM becomes unavailable (the following message appears (click OK to
close)
Effects of the Activation of the Standby SW bank process:
the previous Stand by bank becomes the Committed one, and viceversa
the SW components of the new Committed bank (after the swap) are loaded in the Equipment
Controller and in all peripherals (IDU and ODU)
the equipment data base structure is converted to the structure of the new SWP (only for
upgrade; for downgrade, refer to para.59.4 on page 825 )
Step 2. Logoff and ReLogin
a) Logoff the NE
b) Login the NE and verify, by SW Download SW Status, 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 previous version back to COMMITTED status,
unless you explicitly want to perform the NE SW downgrade, described in para.59.4 on
page 825

3DB 16142 JAAA Ed.01 823 / 866
59.3.6 Additional operations for upgrade from V2.1.0 (station A)

Proceed as follows:

After having performed for the first time:
the V2.1.3 SW download to the NE (para.59.3.4 on page 817 )
and the activation of the V2.1.3 on the NE (para.59.3.5 on page 822 )
perform for the second time:
the V2.1.3 SW download to the NE (para.59.3.4 on page 817 ), but, in phase d ) on page
819 , setting Forced before clicking on Init download
and the activation of the Stand by V2.1.3 on the NE (para.59.3.5 on page 822 )
N.B. Obviously, at the end of this procedure, you will have both SW banks with V2.1.3 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 > V2.1.0, so after the activation of package SWP
V2.1.3, it is necessary to download SWP V2.1.3 again (IN FORCED MODE), to transfer the
new SW component image onto flash card.
59.3.7 Operations on station B
Perform on station B all operations you have performed on station A , described from para.59.3.4 on
page 817 , to para.59.3.6 above.
59.3.8 Functional checks on the radio link (stations A and B)
Perform functional checks on the radio link (e.g. Alarm Monitor, Performance Monitoring, analog
measurement, BER measurement, operations on protection schemes, loopbacks, etc.)
59.3.9 NE data backup (stations A and B)
Perform the NE data backup for both stations, as described in point [3] on page 428
N.B. These backup files are consistent with the data base structure of the new Committed SW bank,
while those created in step d ) on page 816 were consistent with the data base structure of
the old Committed SW bank (that has now become the Stand By bank).

824 / 866 3DB 16142 JAAA Ed.01
59.4 Notes about NE SW downgrade
If, in the Flash Card, the version of the SWP in the Stand by bank (e.g. V2.1.1) is lower than that present
in the Committed bank (e.g. V2.1.3), the activation of the Stand by bank corresponds to the NE SW
downgrade (i.e., following the example above, from V2.1.3 to V2.1.1).
This operation is greatly discouraged for backward data base structure incompatibility.
In fact, when the lower version SWP is activated, the data base is scratched, and you must redefine all
NE data from the beginning.
Additional notes:
the downgraded NE must be managed by the proper SW management tool (e.g. to manage a
9400AWY V2.1.1, you must use the 1320CTbased Craft Terminal installed from the SWP 9400AWY
V2.1.1 CDROM)
the data base, scratched by the downgrade operation (e.g. from V2.1.3 to V2.1.1), remains scratched
even if you perform the upgrade (e.g. from V2.1.1 to V2.1.3); therefore, also in this case, you must
redefine all NE data from the beginning.

3DB 16142 JAAA Ed.01 825 / 866
a)
826 / 866
END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
SECTION 6: APPENDICES
N.B. For the information concerning the SWP TCO Suite, if any, please read carefully the point v
Notes on used TCO Suite and associated User Manual on page 5
Appendix A General on Ethernet port characteristics and management

This Appendix gives summary information that can be useful for the configuration of 829
Ethernet ports.
Appendix B ECTEquipment connection via public switched telephone

network
This Appendix explains the operations necessary to allow the remote connection to 839
the FInterface, from a local PC configurated as ECT, through a switched telephone
line of the standard Public Telephone Network.
Appendix C List of symbols and abbreviations, Glossary of terms 849
Appendix D Customer documentation feedback 863

APPENDICES
3DB 16142 JAAA Ed.01 827 / 866
828 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
APPENDICES
61 APPENDIX A: GENERAL ON ETHERNET PORT CHARACTERISTICS
AND MANAGEMENT
This Appendix gives summary information that can be useful for the configuration and use of the Ethernet
ports:
Subject On page
Ethernet Physical Interface
MDI/MDIX crossover (AutoMDI/MDIX) below
Frame size, Rx checksum and FCS
Ethernet capacity 830
Ethernet flow control 830
Ethernet interface management 830
Auto Link Shutdown 831
Ethernet Switch 833
VLAN characteristics and management 835
61.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.
61.2 MDI/MDIX crossover (AutoMDI/MDIX)
This feature 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 CT/NM management.
N.B. Either the speed or duplex must be set to autonegotiate to enable AutoMDI/MDIX for the
interface. If you explicitly set both the speed and duplex to a fixed value, thus disabling
autonegotiation for both settings, then AutoMDI/MDIX is also disabled.
61.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 up to 2000 bytes (jumbo frame) for ports at 1 Gbit/s.
N.B. Only Ethernet Port 1 (#33) can have jumbo frame.
FCS field, inside each ethernet frame, is checked; if the check is wrong, the packet is discarded.
FCS is always enabled.

APPENDICES
3DB 16142 JAAA Ed.01 829 / 866
61.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. 93. on page 455 .
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.
61.5 Ethernet flow control
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 834 ).
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.
61.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.

APPENDICES
830 / 866 3DB 16142 JAAA Ed.01
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).
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.
61.7 Auto Link Shutdown (ALiS)

[1] Scopes
9400AWY can be configured to provide rapid notification to the external ethernet equipment that
there has been a failure (example: radio failure) or a link quality issue (example: extreme weather
condition or obstacle in RF link path). Notification to the external ethernet equipment (i.e. switch or
router) is provided by shutting down the Ethernet ports connecting the AWY to the network that are
linked to the degraded radio path. The Automatic Link Shutdown (ALiS) feature provides this
functionality.
All the traffic from one radio direction has to be virtually link to one (or more) of the user ethernet ports.
This function is managed properly by ECT/NMS.
[2] Function management

The ALiS function is enabled by ECT, for each gigabit ethernet port; by default, it is disabled.
[3] Feasible radio configurations

This feature can be managed in the 1+0 and in all the 1+1 radio configurations.

APPENDICES
3DB 16142 JAAA Ed.01 831 / 866
[4] Cross connections and links
No physical cross connection is allowed; each gigabit ethernet port can be linked to the radio channel

port and/or among them, by VLAN management.

[5] Behavior to switch off ALiS
When a radio failure criteria is active ( see following point [7] ), only the gigabit ethernet ports where
the operator has enabled the ALiS, will be disabled temporary (standby status), until the radio
failure, which has caused the Ethernet port shutdown, is present, whereas the other ports will work
normally.
[6] Condition to disable ALiS

When one or more radio failure criteria are still raised, it is no possible to disable the ALiS function:
only when all radio failures are expired, then it can be possible to disable it.
[7] Radio criteria

The radio criteria can be split as follows:
the radio signal is destroyed; in this case, the selected radio criteria are the following:
ODU fail
Cable Loss
LOF
the radio signal is degraded; in this case, the selected radio criteria is the following:
EW alarm.
Note: the EW alarm is calculated inside the ODU and sent to IDU; it is always available,
also in 1+0 configuration.
[8] Active channel (1+0 configuration)

In 1+0 configuration, the ALiS mechanism takes effect when a criteria is raised, only on the Ethernet
ports which have enabled this functionality.
[9] Active channel (1+1 configuration)

In 1+1 configuration, the ALiS mechanism takes effect when a radio criteria (see point [7] above)
is raised, only on the Ethernet ports which have enabled this functionality, but only when both
channels are affected by the failure/signal deterioration and then, the 1+1 protections (RPS, TPS and
EPS) will be useless.
[10] From detection to initiation criteria

The total Shutdown time, from the detection of an initiation criteria, is not less than 2 sec.
[11] TPS switching

In case of 1+1 configuration, if the TPS switching protection takes effect, the consequence is the AIS
temporary alarm is generated for few hundreds msec and then, it expires (it is caused because the
TPS switching is not hitless); in this case, a timer is started to check if the AIS alarm is present still
after 2 sec. (it is the fixed delay described in previous point [10] ): if yes, then the alarm is persistent
and then the failure is permanent, so the ALiS on the Ethernet ports where it was enabled, takes
effect, and the shutdown of those ports will be performed; otherwise, no Ethernet ports shutdown will
take effect.
[12] WaitToRestore (WTR) time

The user ethernet ports will be switched on, only the local gigabit ethernet ports which were enabled
before the failure, when the associated radio direction has recovered from its failure (that is, when
the last radio failure is expired or signal BER level is minor of the threshold). The waittorestore
(WTR) time is 30 sec.

APPENDICES
832 / 866 3DB 16142 JAAA Ed.01
61.8 Ethernet Switch
The fundamental component of Enhanced Ethernet 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.
[2] 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.
[6] IEEE 802.1Q (VLAN management)

The IEEE 802.1Q tag VLAN feature can be 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).
In current release, the traffic type IEEE 802.1Q tag is managed by VLAN (the switch looks the tag).
The VLAN management is described in detail in para.61.9 from page 835
[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.
APPENDICES
3DB 16142 JAAA Ed.01 833 / 866
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 point 2 ) on page 458 , and point
b ) on page 568 ] to choose how assign the priority to each packet according to the information in:
a) IEEE std 802.1p mapping

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. 111. 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.
b) DiffServ (DSCP) mapping

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. 112. QoS based on DiffServ
DiffServ priority Queue
111000, 110000, 101110, 101000 Queue 4 (higher priority)
100110, 100100, 100010, 100000, 011110, Queue 3
011100, 011010, 011000
010110, 010100, 010010, 010000, 001110, Queue 2
001100, 001010, 001000, 000000
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.

APPENDICES
834 / 866 3DB 16142 JAAA Ed.01
[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
61.9 VLAN characteristics and management
[1] IEEE 802.1Q tag VLAN Enable/Disable

The IEEE 802.1Q tag VLAN is flexibly enabled or disabled by CT/NMS. When enabled, the Ethernet
Traffic, which goes through the AWY Network, is managed according to IEEE 802.1Q protocol.
[2] Portbased VLAN

The portbased VLAN feature allows partitioning the switch ports into virtual private domains. The
membership of the VLAN is based on the port on which traffic is received (not on packet data), and
each packet received on a specific port will be forwarded only to the ports that belong to the same
virtual private domain.
[3] Enable 802.1Q or 802.1D at NE level

The IEEE 802.1Q and 802.1D protocol standard are defined at NE level (that is, it is valid for all the
ports).
[4] Per Port VLAN Configuration

Once IEEE 802.1Q tag VLAN is enabled, the incoming Frames are divided into two types 802.1Q
Tagged Frame and Untagged Frame.
On each user Ethernet port, it possible to configure:
Acceptable Frame Types:
1) Admit only tagged frame (only tagged frames are allowed in ingress);
2) Admit all frames.
Default value: Admit all frames
Port VLAN: if the acceptable frame type is set to Admit all frame, the VLANID and PRI fields
configured will be added in ingress to untagged frames.
Only VLANID values already defined and the port is included in the corresponding forward
membership (see SR ID 3918) can be configured for this purpose.
The priority values allowed are in the range 0 7.
In case no VLANID and PRI values are configured, the following values are applied:
VLANID=1; PRI=0 (default values).
[5] Untagged Frames

The untagged frames received on one user Ethernet port configured as Admit only tagged frame
are dropped.
[6] Tagged Frames

If one tagged packet with VLAN_ID= X is received on a port which is not member of the VLAN X, the
packet is dropped.

APPENDICES
3DB 16142 JAAA Ed.01 835 / 866
[7] Priority Frames
The priority packets (VLANID=0) received on one user Ethernet port configured as Admit only

tagged frame are dropped.

The priority packets (VLANID=0) received on one user Ethernet port with the Admit all frames

configuration enabled, are managed as untagged frames for VLANID field, while the PRI field are
the same of the received packets.
[8] VLAN Definition

By CT/NMS, it is possible to:
1) define VLANID, the values configurable are in the range 2 4094

2) define VLAN Name: a text string of up to 32 characters
3) define all ports member of this VLAN (Port Bitmap). All user Ethernet ports, and only Radio port,
are possible
4) define among the ports belonging to this VLAN (members) those untagged (in egress the VLAN
are removed from the frames). All user Ethernet ports are considered
5) the rows maximum number of VLAN definition table is fixed to 256 (only the filled rows are
shown)
By default, all the ports are members of the VLAN ID = 1 and the Untag flag is set to False which
means all frames are transmitted with Tag.
The following table provides one logical representation of VLAN definition function:
VLAN ID VLAN Name VLAN Ports Untagged Ports

row 1 2
row 2 35
row 3 725
...
row 256 4094
[9] VLAN Definition: parameters change

Once a VLANID has been defined and stored in the NE, the management systems has the
possibility to change the associated parameters: VLAN name, VLAN member ports, VLAN untagged
ports in egress.
[10] VLAN removal

The management systems has the possibility to delete a VLANID. It is possible to remove a
VLANID from the VLANID table even if this VLANID has been already configured on one or more
user ports, as Port VLANID to be added in ingress to untagged frames. As consequence, the
VLANID 1 is added to the untagged frames received on this port. Before applying this deletion, the
management system asks to the operator the confirmation of the operation, highlighting the
consequence of the operation.
[11] VLAN ID = 1 management

VLANID = 1 is automatically defined by the NE when the 802.1Q bridge type is selected. This
VLANID is shown to the operator but it cannot be neither changed nor deleted by the management
system.
All the user Ethernet ports (enabled and disabled) and all the radio ports are members of the VLAN
1.
In egress, the VLAN 1 is always removed from all the ports.

APPENDICES
836 / 866 3DB 16142 JAAA Ed.01
[12] VLAN Definition: exported table
The button Export allows to export the Port Vlan Configuration table ( see point [8] on page 836)
in a .csv format file.

[13] VLAN Definition: VLAN filter

The button Filter allows to filter the VLAN by name.

APPENDICES
3DB 16142 JAAA Ed.01 837 / 866
838 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
APPENDICES
62 APPENDIX B: ECTEQUIPMENT CONNECTION VIA PUBLIC
SWITCHED TELEPHONE NETWORK
Subject On page
Introduction below
Certified equipment 840
Connection cables 841
Modem setting 842
Setting of Sportster Flash Modem & 3Com 56K Faxmodem 842
TD32 AC Modem setting 844
PC laptop Dell Latitude setting 845
Setting up the connection 846
Changing the ECTequipment connection speed 847
Introduction 847
Configuration at NE side 847
Configuration at PC side 848
62.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. 439. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.
remote side
(equipment side)
local side
(ECT side) F Interface
Port COM
Telephone net-
work
Local Remote
PC/ECT Modem Modem
PCLAPTOP/ECT
with internal modem
Fig. 439. ECTEquipment connection via Public Switched Telephone Network

APPENDICES
3DB 16142 JAAA Ed.01 839 / 866
62.2 Certified equipment

The connection has been successfully tested:

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

characteristics as stated in the TCO SUITE User Manual
2) with internal modem:

PC laptop Dell Latitude:
Processor equipped: PENTIUM III
Operating system: Microsoft Windows 2000 v. 5.00.2195 service pack 2
RAM equipped: 128 Mbytes
Hard disk equipped: 10 Gbytes
Internal Modem: 3COM 56K v.90 Mini PCI MODEM
c) and with the following local/remote combinations:
Local Modem Remote Modem
Sportster Flash
Sportster Flash TD 32 AC
3Com 56K Faxmodem
TD 32 AC
TD 32 AC Sportster Flash
3Com 56K Faxmodem
TD 32 AC
PC laptop Dell Latitude as in
Sportster Flash
point b ) 2 ) above
3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customers charge.

APPENDICES
840 / 866 3DB 16142 JAAA Ed.01
62.3 Connection cables
In the following figures, the cables for the connections are described:
PC/ECT (DTE) Local Modem (DCE)

Cannon 9 pins female Cannon 25 pins male
DCD 1 8 DCD
TD 2 3 TD
RD 3 2 RD
DTR 4 4 RTS
DSR 6 5 CTS
RTS 7 6 DSR
CTS 8 20 DTR
GND 5 7 GND
Fig. 440. ECTLocal external Modem cable
Remote Modem (DCE) F Interface (DCE)

Cannon 25 pins male Cannon 9 pins male
TD 2 3 TD
RD 3 2 RD
RTS 4 7 RTS
CTS 5 8 CTS
DSR 6 6 DSR
CTS 20 4 DTR
GND 7 5 GND
Fig. 441. F InterfaceRemote Modem cable

APPENDICES
3DB 16142 JAAA Ed.01 841 / 866
62.4 Modem setting

62.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. 439. on page 839 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. 440. on
page 841.
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> (Best PC default configuration recall)

ATT<Return> (Tone Dialling instead than Pulse Dialling)
ATX3<Return> (Second Signal disabling, avoids problems with PABX)
AT&W0<Return> (Configuration store in NVRAM 0)
5) Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.

APPENDICES
842 / 866 3DB 16142 JAAA Ed.01
N.B. For confirmation, the modem configuration can be checked writing the command
ATI4<Return> in the HyperTerminal program window.
Information displayed should be as follows:

ATI4
U.S. Robotics Sportster Flash 56000 Settings...
B0 E1 F1 L2 M1 Q0 V1 X3 Y0
BAUD=38400 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE CID=0
&A3 &B1 &C1 &D2 &H1 &I0 &K1

&M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004

S07=060 S08=002 S09=006 S10=014 S11=072 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=001 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=012 S40=000
S41=004 S42=000
LAST DIALED #:
REMOTE MODEM SETTING
To set the remote modem, proceed as follows:
a) carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting
b) execute and store the modem 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> (Autoanswering setting)
c) now, setting has been completed. Modem can be switched off and disconnected, if necessary.
ATI4<Return> in the HyperTerminal program window.
Information displayed should be equal to that displayed for the local modem, with only the
difference for field S00:
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004

APPENDICES
3DB 16142 JAAA Ed.01 843 / 866
62.4.2 TD32 AC Modem setting

This modem requires an initial HW setup via dipswitches and a SW setting via serial port.

To set the modem, both local and remote, proceed as follows:
1) The initial HW setup via dipswitches is indicated in Fig. 442. herebelow:
ON ON ON
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4
SW3 SW2 SW1
ON ON
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
SW5 SW4
Fig. 442. TD32 AC modem dipswitch setting
2) Connect the local modem to the PC/ECT with the cable of Fig. 440. on page 841.
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
5) Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return> (Best PC default configuration recall)

AT&K0<Return> (DTE/DCE flow control disabling)
ATA<Return> (Automatic Answer enabling > Only on Remote modem and
wait the message NO CARRIER)
AT&W0<Return> (Configuration store in NVRAM 0)
AT&Y0<Return> (Configuration Set to load at switchon: NVRAM 0)
6) Now, setting has been completed. Modem can be switched off and disconnected, if necessary.

APPENDICES
844 / 866 3DB 16142 JAAA Ed.01
AT\S<Return> in the HyperTerminal program window.
Information displayed should be as follows:

AT\S
CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION

COUNTRY...........IT &A CHR ABORT OPT.....NO *H NEG. SPEED......HIGH
DTE BPS........38400 &B DTR DIAL OPTION...NO S0 RINGS TO ANS.....002
DTE PARITY.....8NONE &C DCD OPTION........ON S1 RING COUNT.......000
LINE SPEED......NONE &D DTR OPTION.........0 S2 <ESC> CHAR.......043
B BELL MODE........OFF &G GUARD TONE......NONE S3 <CR> CHAR........013
E CMD ECHO..........ON &K FLOW CONTROL....NONE S4 <LF> CHAR........010
F LINE MODE.......AUTO &L NETWORK.........PSTN S5 <BS> CHAR........008
L SPKR VOLUME......LOW &Q ASYNC/SYNC.........5 S7 CONNECT TIME.....060
M SPKR CONTROL....CALL &R RTS/CTS.........AUTO S8 PAUSE TIME.......002
N AUTO MODE.........ON &S DSR OPT............0 S12 ESC GUARD TIME...050
Q QUIET............OFF &T ENABLE RDL........NO S30 CONNECT INACT....000
V RESULT FORM.....LONG &X SYNC CLOCK.......INT S32 XON CHAR.........017
W EC MSG.............0 &Y PROFILE........NVM.0 S33 XOFF CHAR........019
X EXT RESULTS........4 \A MAX BLK SIZE.....192 S36 FALLBACK ACTION..007
Y LONG SPACE DISC...NO \G REMOTE FLOW......OFF S37 MODE SELECT......000
%C COMPRESSION.....BOTH \K BRK OPT............5 S48 V42 NEG CTRL.....007
K EXT. SERVICES......0 \N ECL MODE........AUTO S95 RES. CODE........000
62.5 PC laptop Dell Latitude setting
The following setting must be done:
Control Panel > Alcatel Lower Layer > Serial port > COM3 and Serial port selected

APPENDICES
3DB 16142 JAAA Ed.01 845 / 866
62.6 Setting up the connection
In order to activate the connection and operate the ECT in remote way, proceed as specified herebelow.

Refer to Fig. 439. on page 839 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. 441. on page 841.
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. 440. on page 841.) 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
9) For PC laptop Dell Latitude only, type the following command inside HyperTerminal program:
AT&C0&D0&R1
N.B. this command must be typed every time the Hyper terminal session is opened (this
command is not stored in the modem NV RAM).
10 ) Execute the telephone call from the PC writing the following command in the HyperTerminal
program window:
ATDnnn<Return>
where nnn is the telephone network number associated to the remote telephone line (that
which the remote modem is connected to).
11 ) Wait the message indicating the successful connection between local and remote modems.
N.B. The message text depends on the modem type, as follows:
CONNECT 14400/ARQ/V32/LAPM/V42BIS (Sportster Flash)

CONNECT 38400 (TD 32 AC)
12 ) Close HyperTerminal program.
13 ) Activate the ECT applicative SW as usual.
14 ) At the end of the job, after having logged out from the ECT applicative SW, close the connection
between local and remote modems, switching off the local modem or physically disconnecting
the cable connecting it to the PC.

APPENDICES
846 / 866 3DB 16142 JAAA Ed.01
62.7 Changing the ECTequipment connection speed
62.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.62.7.2 below,
at PC side, the configuration must be setup as explained in the following para.62.7.3 on page 848,
as far as the modem is concerned, please refer to the constructor documentation.
62.7.2 Configuration at NE side
1) Login the NE through the Alarms & Settings function (see para.35.1 on page 481 ) using
a login profile allowing the Modem Speed change (see Tab. 94. on page 483 ),
2) enter the Modem Speed screen and set the required speed (see para.35.2.7 on page 492).

APPENDICES
3DB 16142 JAAA Ed.01 847 / 866
62.7.3 Configuration at PC side

To configure the modem with the relevant speed, enter the menu Settings > Control Panel of the

Operating System and open the Alcatel Lower Layers utility. The menu of Fig. 443. opens.

Fig. 443. 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.

APPENDICES
848 / 866 3DB 16142 JAAA Ed.01
63 APPENDIX C: LIST OF SYMBOLS AND ABBREVIATIONS,
GLOSSARY OF TERMS
63.1 List of symbols
Tab. 113. List of symbols

N.B. This table lists some symbols whose interpretation could be doubtful.
SYMBOL MEANING AND COMMENTS

In this handbook it is not the division symbol. It means from .. to ...
E.g.:
<value1> <value2>
means:
from <value1> (included) to <value2> (included)
A polarization symbol like this:
H V
POLARIZATION can be assumed as either horizontal or vertical
SYMBOLS H
Once you have decided a polarization (e.g. )
the opposite direction symbol will be opposite polarization (e.g. )
V
63.2 List of abbreviations
Tab. 114. 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
9500MPRE Microwave Packet Radio ETSI
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

APPENDICES
3DB 16142 JAAA Ed.01 849 / 866

AIS Alarm indication Signal

ALiS Auto Link Shutdown
AMI Alternate Mark Inversion
AND Alarm on both station batteries
ANSI American National Standard Institute
AP Alternate Polarization
API Access Point Identifier
APS Automatic Protection Switching
APT Active Problem Table
AS Alarm Surveillance
ASAP Alarm Severity Assignment Profile
ASE Application Service Element
ASIC Application Specific Integrated Circuit
AT Attended Alarm
ATL Far Terminal Alarm
ATM Asynchronous transfer Mode
ATPC Automatic Transmit Power Control
ATTD ATTendeD (alarm storing)
AUX AUXiliary
AVC Attribute Value Change
B
BATT Battery
BB Base Band
BBE Background Block Error
BCA Common Battery Dial Pulsing (Telephone Set)
BER Bit Error Rate
BIP Bit Interleaved Parity
BKPV Back Plane Version
BNC Bayonet Not Coupling
BSC Base Station Controller
BTS Base Transceiver Station
C
CAND All power supply units are faulty
CCDP 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
APPENDICES
850 / 866 3DB 16142 JAAA Ed.01
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 Equipment Controller
ECC Embedded Communication Channel
ECS External Communication Service
ECT Equipment Craft Terminal
EE Equipment Engineering
EF Equipment Failure
APPENDICES
3DB 16142 JAAA Ed.01 851 / 866

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
F
F Interface F (for Craft Terminal) or Fuse
FAD Functional Access Domain
FCC Federal Communications Commission
FCS Frame Check Sequence
FD Frequency Diversity
FE Front End Fast Ethernet
FEC Forward Error Correction (Code)
FIT Failure Unit
FPGA Field Programmable Gate Array
FR Failure Rate or Frequency Reuse
FSO Free Space Optics
FTP File Transfer Protocol
G
GA General Alarm or Gate Array
GND Ground
GNE Gateway Network Element
H
H Horizontal (polarization)
HBER High Bit Error Rate
HCS Higher order Connection Supervision
HD History Data
HDBK Handbook
APPENDICES
852 / 866 3DB 16142 JAAA Ed.01
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
LCT Local Craft Terminal
LDI Local Defect Indication
LED Light Emission Diode
LEW Low Early Warning
LIM Link Identifier Mismatch
LLMAN Alcatel Lower Layer MANager
LO Local Oscillator
APPENDICES
3DB 16142 JAAA Ed.01 853 / 866

LOF Loss Of Frame

LOM Loss Of Multiframe
LOS Loss Of Signal
LS Low Speed
M
MAC Media Access Control
MAJ Major (alarm)
MAU Medium Attachment Unit
MCF Message Communication Function
MDT Mean Dawn Time
MEM Memorization
MIB Management Information Base
MIN Minor (alarm)
MLR Manual Laser Restart
MOC Managed Object Class
MOD Modulator
MSOH Multiplex Section OverHead
MSp Manual Switch to protecting channel
MSw Manual Switch to working channel
MTBF Mean Time Between Failures
MTTR Mean Time To Repair
MUX Multiplexer
N
NBF Narrow Band Filter
NDS 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
APPENDICES
854 / 866 3DB 16142 JAAA Ed.01
ODF Optical Distribution Frame

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

APPENDICES
3DB 16142 JAAA Ed.01 855 / 866

Q

QAM Quadrature Amplitude Modulation
QOS 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
RCT Remote 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
APPENDICES
856 / 866 3DB 16142 JAAA Ed.01
S/P Serial to Parallel

SSF Server Signal Fail

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
TDCC P.S.U level 2 48 Vdc distribution frame
TDM Time Division Multiplexer
TEM Transversal Electric Mode
TIM Trace Identifier Mismatch
TL Transmitted Level
TLTS Transmitted Level Threshold Second
TM Transmission and Multiplexing
TMN Telecommunication Management Network
TN Telecommunications Network
TPH Telephone
TP Termination Point
TPS Tx Protection Switching
TR TRansceiver Technical Report
TRCF Total Received Correct Frames
TRCO Total Received Correct Octets
TRIB Tributary
TRSEF Total Received Service Errored Frames
TS Time Slot
TRU Top Rack Unit
TTF Total Transmitted Frames
TTO Total Transmitted Octets
TTP Trail Termination Point
Tx Transmitter/Transmitted
U
U Unavailability
UAS UnAvailable Second
UAT UnAvailable Time
UDR Unpressurized Rectangular Waveguide Type
UG Urgent Alarm
UMTS Universal Mobile Telecommunications System
URG Urgent
APPENDICES
3DB 16142 JAAA Ed.01 857 / 866

URU Underlying Resource Unavailable

USC User Service Channel
USM User Service Manager
USY Urban Haul Synchronous split mount Radio System
UT Unavailability Time
UTRAN Universal Terrestrial Radio Access Network
V
V Vertical (polarization)
VCO Voltage Controller Oscillator
VF Voice Frequency
VLAN Virtual Local Area Network
VSWR Voltage Standing Wave Ratio
W
WAN Wide Access Network
WBF Wide Band Filter
WIP Wireless IP
WLT Wireless Line Terminal
WS Work Station
X
XPD Cross Polar Discrimination
XPIC Cross Polar Interference Canceller
XPI Cross Polar Interference
XPIF Cross Polar Improvement Factor
XPOL Cross Polar/Polarization
NOTES:
(*) Owing to change of name, all documents issued by the two ITU committees (CCIR ND
CCITT) in 1992 (and in some cases even before then) are classified as ITUR and ITUT,
respectively.

APPENDICES
858 / 866 3DB 16142 JAAA Ed.01
63.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.

APPENDICES
3DB 16142 JAAA Ed.01 859 / 866
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITUT (International Telecommunication

Union).

Kilobits per second:
Unit that correspond to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
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.

APPENDICES
860 / 866 3DB 16142 JAAA Ed.01
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.

APPENDICES
3DB 16142 JAAA Ed.01 861 / 866
862 / 866
9400AWY Rel.2.1 SWP 9400AWY V2.1.3

USER MANUAL
APPENDICES
64 APPENDIX D: 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.

APPENDICES
3DB 16142 JAAA Ed.01 863 / 866
CUSTOMER DOCUMENTATION FEEDBACK
Handbook data

Product release, version: 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

Handbook type: USER MANUAL
Handbook part number and edition: 3DB 16142 JAAA Ed.01
General evaluation
SUBJECT 5 (max.) 4 3 2 1 (min.)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Section evaluation
SECTION 5 (max.) 4 3 2 1 (min.)
Front matter
1 : Hardware installation
2 : System description
3 : NE management by TCO Suite and CT
4 : SW Installation in PC and commissioning
5 : Maintenance and upgrade
6 : 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:

APPENDICES
864 / 866 3DB 16142 JAAA Ed.01
INFORMATION FOR ALCATELLUCENT INTERNAL USE ONLY
DATE CHANGE NOTE

ED APPRAISAL AUTHORITY ORIGINATOR
(yymmdd) (ECO)
01 090427 P.Garofoli, Chen Wenyu, A.Goncalves E.Corradini
Editorial information: refer to the last section of the *REVBAR.pdf file present in the zipped source file
folder archived in PDM.

APPENDICES
3DB 16142 JAAA Ed.01 865 / 866
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

COD.MANUALE HDBK P/N:
9400AWY Rel.2.1 SWP 9400AWY V2.1.3
USER MANUAL
HANDBOOK PRINT AND ASSEMBLY INSTRUCTIONS

ISTRUZIONI DI STAMPA ED ASSIEMAGGIO DEL MANUALE
This manual can be printed and assembled in two ways:

w only the HW INSTALLATION HANDBOOK: see chapt.1 on page 868
w whole handbook: see chapt.2 on page 870
Questo manuale pu essere stampato ed assiemato in due modi:

solo il HW INSTALLATION HANDBOOK: vedi cap.1 a pag. 868
intero manuale: vedi cap.2 a pag. 870

Handbook print & assembly
3DB 16142 JAAA Ed.01 867 / 866
1 STAMPA SOLO DELLHW INSTALLATION HANDBOOK

ONLY PRINT OF THE HW INSTALLATION HANDBOOK
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
Pagine numerate
fase Pages numbered
step
da from a to
TARGHETTE DEL VOLUME VOLUME LABELS

Fig. 1. pg.869
N.B. se il manuale viene termorilegato senza cartelletta, le
targhette non servono. Utilizzare il frontespizio, stampato su
1
cartoncino col suo retro, come copertina.
N.B. if handbook is thermobound without binder, labels are not
necessary. Use the front, printed with its back side, as
bookcover.
2 PART A: HW INSTALLATION HANDBOOK 1/866 358/866
fine istruzioni assemblaggio end of assembly instructions

868 / 866 3DB 16142 JAAA Ed.01
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3

HARDWARE INSTALLATION HANDBOOK
VOL.1/1
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3
HARDWARE INSTALLATION HANDBOOK
VOL.1/1
9400AWY Rel.2.1
78131518232538 GHz shorthaul low/medium capacity digital microwave radio links
SWP 9400AWY V2.1.3
3DB 16142 JAAA Ed.01 HARDWARE INSTALLATION HANDBOOK VOL.1/1
9400AWY Rel.2.1
SWP 9400AWY V2.1.3
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3
Fig. 1.

3DB 16142 JAAA Ed.01 869 / 866
2 STAMPA DELLINTERO MANUALE PRINT OF WHOLE HANDBOOK
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 6 SEPARATORI NUMERATI DA 1 A 6

6 SEPARATORS NUMBERED FROM 1 TO 6 ARE NECESSARY
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
TARGHETTE - LABELS
1
Fig. 2. pg. 871
2 PARTE INIZIALE - FRONT MATTER 1/866 22/866
3 INSERIRE SEPARATORE 1 - INSERT SEPARATOR 1
4 PART A: HW INSTALLATION HANDBOOK 23/866 358/866
6 SECTION 2: SYSTEM DESCRIPTION 359/866 400/866
SECTION 3: NE MANAGEMENT BY TCO SUITE AND

8 401/866 664/866
CRAFT TERMINAL
10 SECTION 4: INSTALLATION AND COMMISSIONING 665/866 736/866
12 SECTION 5: MAINTENANCE AND UPGRADE 737/866 826/866
14 SECTION 6: APPENDICES 827/866 866/866

870 / 866 3DB 16142 JAAA Ed.01
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3

USER MANUAL
VOL.1/1
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3
USER MANUAL
VOL.1/1
9400AWY Rel.2.1
SWP 9400AWY V2.1.3
3DB 16142 JAAA Ed.01 USER MANUAL VOL.1/1
9400AWY Rel.2.1
SWP 9400AWY V2.1.3
9400AWY Rel.2.1
78131518232538 GHz
SWP 9400AWY V2.1.3
Fig. 2.

3DB 16142 JAAA Ed.01 871 / 866
END OF PRINT INSTRUCTIONS FINE DELLE ISTRUZIONI DI STAMPA

872 / 866 3DB 16142 JAAA Ed.01

9400AWY User Manual Rel2.1.3

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

9400AWY User Manual Rel2.1.3

Caricato da

Copyright:

Formati disponibili

AlcatelLucent 9400AWY

permitted without written authorization from AlcatelLucent

All rights reserved. Passing on and copying of this

For further information, refer to Acrobat reader help online.

PART A : HARDWARE INSTALLATION HANDBOOK 1

PART B : TECHNICAL HANDBOOK 2

9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

e) Service Personnel skill

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

permitted without written authorization from AlcatelLucent

b) Antistatic protection device kit

Fig. 1. Antistatic protection device kit

c) Screw tightening torque

d) Tightening torque for assembling other equipment parts

e) IDUODU cable disconnection / connection

f) Craft Terminal 9400AWY RS232 cable connection / disconnection

9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

a) 9400AWY V2.1.3 Documentation CDROM (mandatory)

v Notes on used TCO Suite and associated User Manual

if you use the SWP TCO SUITE Rel.1.7:

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

permitted without written authorization from AlcatelLucent

All rights reserved. Passing on and copying of this

vii Notes on present edition

9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

iii Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

v Notes on used TCO Suite and associated User Manual . . . . . . . . . . . . . . 5

vi Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

vii Notes on present edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Part A: Hardware Installation Handbook . . . . . . . . . . . . . . . . . . . . . . . 23

SECTION 1: HARDWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

permitted without written authorization from AlcatelLucent

document, use and communication of its contents not

14 TOP RACK UNIT (TRU) INSTALLATION AND CABLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

15 INDOOR UNIT INSTALLATION AND CABLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

and with distributor 75 Ohm (1.6/5.6 or BNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

16 OUTDOOR UNIT INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

17 IDUODU CABLE INSTALLATION MATERIAL AND INSTALLATION PROCEDURE . . . . 189

permitted without written authorization from AlcatelLucent

document, use and communication of its contents not

All rights reserved. Passing on and copying of this

19 UNPACKING AND WAREHOUSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

110 IDU INSTALLATION COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

111 ODU INSTALLATION COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

9400AWY Rel.2.1 SWP 9400AWY V2.1.3 USER MANUAL

111.1.5 9423 AWY ODU installation components ................................. 255

111.1.6 9425 AWY ODU installation components ................................. 256

111.1.7 9438 AWY ODU installation components ................................. 257

113 DESCRIPTION OF INTERCONNECTION AND SIGNAL CABLES . . . . . . . . . . . . . . . . . . . . 327

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3

permitted without written authorization from AlcatelLucent

document, use and communication of its contents not

Part B: Technical Handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

SECTION 2: SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

22 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

22.1.6 ETSI System Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

22.1.7 Protection switching system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

22.2 Tributary interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

SECTION 3: NE MANAGEMENT BY SOFTWARE APPLICATIONS . . . . . . . . . 401

33 GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY V2.1.3